Bug#589690: linux-image-2.6.35-rc5-amd64: The Kernel panics on starting X using latest xorg-intel driver
Hi Martin, martin wrote: This is actually working with the current stable kernel, sorry I thought I'd closed all my Xorg bugs. Thanks for a followup. To clarify, do you mean that you are using 2.6.32-34squeeze1 now? That wouldn't rule out the bug having been introduced and fixed in later versions. Most of them were due to memory issues that didn't show up with the x86memtester+ and for some reason didn't show up with lenny. Still changing out the memory fixed all my remaining issues, I can't be sure if this one was a memory of bug, either way it's now closed. Weird. Kurt commented on the upstream report; maybe he can make better sense of this. It hadn't sounded machine-specific to me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589690: linux-image-2.6.35-rc5-amd64: The Kernel panics on starting X using latest xorg-intel driver
On 13/06/11 07:51, Jonathan Nieder wrote: Hi Martin, martin wrote: This is actually working with the current stable kernel, sorry I thought I'd closed all my Xorg bugs. Thanks for a followup. To clarify, do you mean that you are using 2.6.32-34squeeze1 now? That wouldn't rule out the bug having been introduced and fixed in later versions. Yes, I'm using squeeze standard now. Most of them were due to memory issues that didn't show up with the x86memtester+ and for some reason didn't show up with lenny. Still changing out the memory fixed all my remaining issues, I can't be sure if this one was a memory of bug, either way it's now closed. Weird. Kurt commented on the upstream report; maybe he can make better sense of this. It hadn't sounded machine-specific to me. It may not have been machine specific and as I remember all the kernel xorg intel bugs were fixed for me some time ago, then I started getting vfs kernel issues which lead to me changing out the memory. I suggest you just close it, if your desperate for a tester it will take me a few days (before I get chance) to get testing running again on the spare partition but I can do it. Regards, M -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589690: linux-image-2.6.35-rc5-amd64: The Kernel panics on starting X using latest xorg-intel driver
tags 589690 + moreinfo quit martin wrote: It may not have been machine specific and as I remember all the kernel xorg intel bugs were fixed for me some time ago, then I started getting vfs kernel issues which lead to me changing out the memory. That sounds promising. I suggest you just close it, if your desperate for a tester it will take me a few days (before I get chance) to get testing running again on the spare partition but I can do it. Yes, it would be nice to confirm the fix but we can certainly wait a few days. :) It should not be necessary to install testing; just the kernel will do. In fact trying with a squeeze userland would be better, for two reasons: (1) the bug is apparently not triggered by newer versions of xserver-xorg-video-intel --- strictly speaking, checking for the same bug would require installing the package from [1], but (2) learning what happens with the standard X driver in squeeze would be best because relevant for ensuring a smooth squeeze → wheezy upgrade path. Thanks. [1] http://people.debian.org/~kibi/packages/xserver-xorg-video-intel/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589690: linux-image-2.6.35-rc5-amd64: The Kernel panics on starting X using latest xorg-intel driver
On Mon, Jun 13, 2011 at 01:51:05AM -0500, Jonathan Nieder wrote: Most of them were due to memory issues that didn't show up with the x86memtester+ and for some reason didn't show up with lenny. Still changing out the memory fixed all my remaining issues, I can't be sure if this one was a memory of bug, either way it's now closed. Weird. Kurt commented on the upstream report; maybe he can make better sense of this. It hadn't sounded machine-specific to me. My machine has an i830 in it. I have tried way too many different kernels to still make any sense of this bug. But it's clear to me that 2.6.38 is one of the first kernels that works reasonable for me. But I'm using KMS right now, since UMS has always been a problem since that 2.12 version and I don't think the current xorg intel driver still supports it. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589690: linux-image-2.6.35-rc5-amd64: The Kernel panics on starting X using latest xorg-intel driver
Hi, martin wrote: The Kernel panics on starting X [...] I'm using the _latest_ intel driver: context: http://ikibiki.org/blog/2010/07/04/We_need_you_redux/ [...] 2.12.0-1+ickle2 Hardware: 965GM on a Sony SZ680 [...] [ 23.000937] BUG: unable to handle kernel NULL pointer dereference at (null) [ 23.000947] IP: [(null)] (null) [ 23.000954] PGD 13de10067 PUD 13be07067 PMD 0 [ 23.000965] Oops: 0010 [#1] SMP [ 23.000972] last sysfs file: /sys/devices/virtual/backlight/acpi_video0/brightness [...] [ 23.001009] Call Trace: [ 23.001009] [a017c6b6] ? i915_irq_emit+0x18a/0x1e5 [i915] [ 23.001009] [81300e45] ? _lock_kernel+0x58/0x8f [ 23.001009] [a02723ab] ? drm_ioctl+0x258/0x32d [drm] [ 23.001009] [81052de6] ? signal_wake_up+0x20/0x2f [ 23.001009] [81053185] ? __send_signal+0x260/0x284 [ 23.001009] [810f3dc6] ? vfs_ioctl+0x23/0x93 [ 23.001009] [810f4657] ? do_vfs_ioctl+0x45d/0x497 [ 23.001009] [81303e2d] ? do_page_fault+0x28c/0x2ce [ 23.001009] [810f46dc] ? sys_ioctl+0x4b/0x6f [ 23.001009] [810089c2] ? system_call_fastpath+0x16/0x1b Chris Wilson says it was fixed by two commits included in 2.6.38-rc5 (see the upstream report). Can you confirm that, for example by testing with a kernel from testing or sid? Thanks for reporting it. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
