[12:28] <kimo> Hi, I reported my toshiba laptop was not turning off in dapper, someone suggested reboot=h, I am here to report that YES this solves the problem ... bye
[02:50] <zul> heylo
[04:52] <zul> gah...i hate it when users complain that the bug is not fixed in the most recent kernel...read the damn changelog
[09:32] <bluefoxicy> hey guys, question, has anyone taken note of the new stuff in DRM in 2.6.16?  The 2.6.15 kernel in Dapper as of 1 month ago still crashed due to bugs in the via DRM code if using the X driver "via"
[09:33] <bluefoxicy> I'm about to try building a 2.6.16 kernel and test the via driver against that in current Ubuntu (AMD64 K8) kernel to see if it appears stable
[09:33] <crimsun> is it backportable to our current source?
[09:34] <bluefoxicy> crimsun:  I am not sure, I have doubts though.  I glanced through the 2.6.16 patch from 2.6.15, there's a large amount of extra code in DRM, some in the drm_dma and drm_mm code, so I'm guessing DRM got a slight rework?
[09:34] <bluefoxicy> crimsun:  backporting it would be nice though
[09:34] <mjg59> bluefoxicy: How can you tell it's a DRM bug?
[09:34] <mjg59> Can we have a bug number?
[09:34] <bluefoxicy> https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/29586
[09:35] <bluefoxicy> mjg59:  my biggest hint was the system hard-hanging after several complaints (Oopses) from the kernel if I use Driver "via" in Xorg.conf, which goes away if I use Driver "vesa"
[09:35] <mjg59> bluefoxicy: That's still quite possibly an issue on the X side
[09:35] <bluefoxicy> average uptime is an hour with the via driver, days or weeks with vesa; and the oopses come up in the via code
[09:35] <mjg59> (well, the mesa side)
[09:35] <bluefoxicy> mjg59:  X should be able to trash kernel space?
[09:36] <mjg59> bluefoxicy: Not really, and it does indicate that there's some issue with the drm code. But that's not necssarily what's causing the hangs
[09:36] <mjg59> "via driver is shit" certainly wouldn't be news
[09:37] <bluefoxicy> Feb 23 07:52:06 localhost kernel: [33790.181303]  <1>Unable to handle kernel paging request at 0000000005fdc288 RIP:
[09:37] <bluefoxicy> Feb 23 07:52:06 localhost kernel: [33790.187430]  <ffffffff88440e6a>{:via:via_mmFreeMem+10}
[09:37] <bluefoxicy> mjg59:  *shrug*  I dunno then.
[09:38] <bluefoxicy> I always assumed trashing the kernel's memory space would need to happen in the kernel.
[09:38] <mjg59> The kernel's memory space is not necessarily trashed
[09:38] <mjg59> It may just be trusting user input (stupid, but, well)
[09:38] <mjg59> The irq backtrace in the last comment is entirely unrelated
[09:38] <bluefoxicy> yes, yes it is.
[09:39] <bluefoxicy> I threw 'irqpoll' into the kernel command line
[09:39] <bluefoxicy> failed to boot
[09:40] <mjg59> Ah. Now, there /is/ a 64-bit related bug
[09:41] <mjg59> Can you grab the ubuntu kernel source and apply the patch from http://webcvs.freedesktop.org/dri/drm/shared-core/via_mm.c?r1=1.21&r2=1.22&makepatch=1&diff_format=u ?
[09:43] <bluefoxicy> mjg59:  ah, yay, no need to do a full move to 2.6.16?  :)
[09:44] <bluefoxicy> mjg59: int != long on 64 bit?
[09:44] <Mithrandir> bluefoxicy: correct
[09:44] <bluefoxicy> time to replace my gints with glongs
[09:44] <Mithrandir> just store pointer types in pointers and ints in ints and you're fine.
[09:46] <bluefoxicy> mjg59:  how do I build this thing?  I don't feel like manually configuring it (I've done that enough times while running gentoO)
[09:46] <mjg59> bluefoxicy: dpkg-buildpackage -rfakeroot -nc
[09:47] <mjg59> delete all the config.something files in debian/config/amd64/ so you just have config and config.whatever
[09:47] <mjg59> Otherwise you'll build loads of images
[09:50] <bluefoxicy> there's no debian directory.
[09:52] <mjg59> What source did you get?
[09:52] <bluefoxicy> linux-source-2.6.15
[09:52] <mjg59> How?
[09:53] <bluefoxicy> via apt-get
[09:53] <bluefoxicy> and then bzcat | tar x on the file it put in /usr/src
[09:53] <mjg59> Do apt-get source linux-image-whatever
[09:58] <bluefoxicy> apt-get build-something .. uh
[09:58] <bluefoxicy> builddep?
[10:08] <bluefoxicy> drivers/ide/ide-acpi.c:537: warning: format %x expects type unsigned int, but argument 4 has type long unsigned int
[10:08] <mjg59> Ignore
[10:08] <mjg59> Fixed in the next release
[10:08] <bluefoxicy> alright.
[10:09] <bluefoxicy> arch/x86_64/pci/mmconfig.c:49: warning: return makes pointer from integer without a cast
[10:09] <bluefoxicy> It just makes me wonder
[10:10] <bluefoxicy> do you think anyone actually knows the fundamental difference between a warning and an error?
[10:12] <bluefoxicy> mjg59:  Once this is compiled I'll need about 6 hours to be sure it's actually working.  The bug is probabilistic; depending on what's going on I'll have problems, but I can view movies and switch desktops without a problem for a while.  Usually what kills me is wandering away from the machine and letting the screensaver come on ;)
[10:13] <bluefoxicy> and usually within an hour of running, though I've had it stay up all day once or twice before I realized what the problem was.
[10:13] <bluefoxicy> it's stupid, I don't have a button marked "Crash System" to press
[10:49] <m_tadeu> hi everyone...
[10:50] <m_tadeu> I think there's a problem with the kernel/nforce chipsets
[10:51] <m_tadeu> I'm trying to enable my pcmcia modem( using a pci adaptor ) and only with my mb I'm unable to talk with the modem
[10:52] <m_tadeu> is there any issue known about this?
[11:14] <bluefoxicy> linux-image-2.6.15-21-amd64-k8_2.6.15-21.32_amd64.deb
[11:14] <bluefoxicy> \
[11:15] <bluefoxicy> alright reboot time
[11:19] <m_tadeu> where can i find that?
[11:20] <bluefoxicy> mjg59:  Okay, it still bitched about the IRQ but that's immaterial.  The question is, can I hammer it and not die
[11:20] <bluefoxicy> mjg59: bluefox@icebox:~$ glxgears
[11:20] <bluefoxicy> Error: couldn't get an RGB, Double-buffered visual
[11:20] <bluefoxicy> mjg59:  any ideas on this one yet?
[11:22] <m_tadeu> bluefoxicy, where can i find that kernel packge?
[11:22] <bluefoxicy> m_tadeu:  what package?
[11:22] <bluefoxicy> m_tadeu:  the one I'm using I just built
[11:22] <bluefoxicy> from a source package in dapper
[11:24] <m_tadeu> bluefoxicy, sory :) though that was for me :)
[11:31] <mjg59> bluefoxicy: Uh. Are you using the via driver or the vesa one?
[11:32] <bluefoxicy> via
[11:32] <mjg59> Check dmesg?
[11:34] <bluefoxicy> it's fine so far.
[11:34] <bluefoxicy> mjg59:  the double buffer thing always happens.
[11:34] <mjg59> Oh, right. Dunno, then
[11:36] <bluefoxicy> https://launchpad.net/distros/ubuntu/+source/xserver-xorg-driver-ati/+bug/29493  It's like this one