Random Panic/Freeze due to BUG: unable to handle kernel NULL pointer dereference at 00000024(?)
https://bugzilla.kernel.org/show_bug.cgi?id=14994
Marc H. Thoben <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #3 from Marc H. Thoben <[email protected]> 2010-04-11 09:51:05 --- I'm having the same kernel panics. i5 750, P55A-UD4, 4 sata harddisks, 1 ide cdrom. Running Debian's latest 2.6.32 kernel from sid/unstable.
Like Dario I've been using netconsole to see this:
Kernel panic - not syncing: Fatal exception in interrupt
...
# BUG: unable to handle kernel NULL pointer dereference at 0000000000000048 # IP: [<ffffffffa0afe288>] ide_complete_rq+0x10/0x3b [ide_core]
...
Call Trace of the kernel oops:
<IRQ> [<ffffffffa0e2fe01>] ? cdrom_newpc_intr+0x6f9/0x72a [ide_cd_mod] [<ffffffffa0e2f708>] ? cdrom_newpc_intr+0x0/0x72a [ide_cd_mod] [<ffffffffa0afdedd>] ? ide_intr+0x170/0x1ff [ide_core] [<ffffffff81093c50>] ? handle_IRQ_event+0x58/0x126 [<ffffffff810170cd>] ? read_tsc+0xa/0x20 [<ffffffff81095536>] ? handle_fasteoi_irq+0x7d/0xb5 [<ffffffff81013957>] ? handle_irq+0x17/0x1d [<ffffffff81012fb1>] ? do_IRQ+0x57/0xb6 [<ffffffff810114d3>] ? ret_from_intr+0x0/0x11 <EOI> [<ffffffff8102b5ac>] ? hpet_msi_next_event+0x0/0x8 [<ffffffffa00e14ff>] ? acpi_idle_enter_bm+0x273/0x2a5 [processor] [<ffffffffa00e14f8>] ? acpi_idle_enter_bm+0x26c/0x2a5 [processor] [<ffffffff81231ae3>] ? cpuidle_idle_call+0x95/0xee [<ffffffff8100fea5>] ? cpu_idle+0xa2/0xda
Call Trace of the kernel panic:
<IRQ> [<ffffffff812f19e9>] ? panic+0x86/0x141 [<ffffffff81068078>] ? up+0xe/0x36 [<ffffffff8104e215>] ? release_console_sem+0x17e/0x1af [<ffffffff81014a7a>] ? oops_end+0xa7/0xb4 [<ffffffff810322b8>] ? no_context+0x1e9/0x1f8 [<ffffffff8103246d>] ? __bad_area_nosemaphore+0x1a6/0x1ca [<ffffffff8103fa5c>] ? __wake_up+0x30/0x44 [<ffffffff811ef53c>] ? credit_entropy_bits+0x7b/0x97 [<ffffffff812f3c35>] ? page_fault+0x25/0x30 [<ffffffffa0afe288>] ? ide_complete_rq+0x10/0x3b [ide_core] [<ffffffffa0afe2a2>] ? ide_complete_rq+0x2a/0x3b [ide_core] [<ffffffffa0e2fe01>] ? cdrom_newpc_intr+0x6f9/0x72a [ide_cd_mod] [<ffffffffa0e2f708>] ? cdrom_newpc_intr+0x0/0x72a [ide_cd_mod] [<ffffffffa0afdedd>] ? ide_intr+0x170/0x1ff [ide_core] [<ffffffff81093c50>] ? handle_IRQ_event+0x58/0x126 [<ffffffff810170cd>] ? read_tsc+0xa/0x20 [<ffffffff81095536>] ? handle_fasteoi_irq+0x7d/0xb5 [<ffffffff81013957>] ? handle_irq+0x17/0x1d [<ffffffff81012fb1>] ? do_IRQ+0x57/0xb6 [<ffffffff810114d3>] ? ret_from_intr+0x0/0x11 <EOI> [<ffffffff8102b5ac>] ? hpet_msi_next_event+0x0/0x8 [<ffffffffa00e14ff>] ? acpi_idle_enter_bm+0x273/0x2a5 [processor] [<ffffffffa00e14f8>] ? acpi_idle_enter_bm+0x26c/0x2a5 [processor] [<ffffffff81231ae3>] ? cpuidle_idle_call+0x95/0xee [<ffffffff8100fea5>] ? cpu_idle+0xa2/0xda
As a workaround I have blacklisted ide-cd_mod from loading.
Please let me know if I can help by providing more data. I'd really like to get this cdrom going again :)
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
Borislav Petkov <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #4 from Borislav Petkov <[email protected]> 2010-04-11 11:09:38 --- Hi,
can you send me the whole dmesg with the oops, also your kernel config. Also, you could try reproducing the bug after having enabled ide-cd debugging. For that, you'll need to apply the following patchlet and rebuild your kernel:
drivers/ide/ide-cd.c +2 -1
@@ -1707,6 +1707,8 @@ static int ide_cd_probe(ide_drive_t *drive)struct gendisk *g;struct request_sense sense; + drive->debug_mask =0xffffffff ; +ide_debug_log (IDE_DBG_PROBE ,"driver_req: %s, media: 0x%x" , drive->driver_req, drive->media);
@@ -1716,7 +1718,6 @@ static int ide_cd_probe(ide_drive_t *drive)if (drive->media != ide_cdrom && drive->media != ide_optical) goto failed; - drive->debug_mask = debug_mask; drive->irq_handler = cdrom_newpc_intr; info =kzalloc (sizeof (struct cdrom_info ),GFP_KERNEL );
drivers/ide/ide-cd.h +1 -1
@@ -8,7 +8,7 @@#include <linux/cdrom.h> #include <asm/byteorder.h> -#define IDECD_DEBUG_LOG 0 +#define IDECD_DEBUG_LOG 1#if IDECD_DEBUG_LOG #define ide_debug_log(lvl, fmt, args...) __ide_debug_log(lvl, fmt, ## args)
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #5 from Marc H. Thoben <[email protected]> 2010-04-11 12:12:29 --- Hello Borislav,
I'm happy you are willing to take a look at this. I'll attach the syslog excerpt (which looks a bit messy due to netconsole, I believe) and the kernel config now.
Admittedly I've been sinning for some years and have just returned to Linux when I bought the new hardware... which means it'll take me a while to remember how to compile the kernel myself. But I'll get there again :)
I can easily reproduce the crash by loading ide-cd_mod, activating composite tweaks in xfce4 and running glxgears in a window. As soon as the terminal is supposed to show the FPS I'll get the kernel panic.
Googling lead me to believe this is caused by the massive interrupt calls that the closed-source nvidia driver is doing. I had the same crash, but not so easily reproducable with the closed-source ati driver.. yes.. I switched graphic cards on the hunt for these kernel panics. Until I found the netconsole module and knew it's the ide/cdrom.
Sorry, I'm drifting off. I will post the debugging info as soon as possible.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #6 from Marc H. Thoben <[email protected]> 2010-04-11 12:14:28 --- Created an attachment (id=25946)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25946)
dmesg -n 8 output via netconsole
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #7 from Marc H. Thoben <[email protected]> 2010-04-11 12:16:28 --- Created an attachment (id=25947)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25947)
kernel config, 2.6.32-4-amd4 of debian sid 2.6.32-11
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
Marc H. Thoben <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #25947|kernel config, |kernel config,
description|2.6.32-4-amd4 of debian sid |2.6.32-4-amd64 of debian
|2.6.32-11 |sid 2.6.32-11Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #8 from Dario Ernst <[email protected]> 2010-04-11 13:09:38 --- Hi,
i just tried 2.6.33.2, still the same problem.
Nvidia driver problems could be as i'm also using them, haven't tried without (as my kinda special dualhead setup doesn't work without).
I'll also try the patchlet with debugging enabeled as soon as i find some time. Thanks to you too for contributing! :P
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #9 from Borislav Petkov <[email protected]> 2010-04-11 15:52:01 --- Hi Dario and Marc,
the fact that you guys both are running into this and that you both run the closed source nvidia driver (not the nouveau thing that just went upstream, right?) is suspicious and since closed source drivers are known to break the kernel, I'd suggest you both give a kernel a try without those closed source drivers, before doing anything else.
When testing this, please make sure the nvidia kernel module is removed so that it doesn't get loaded at all and not simply blacklisting it.
Thanks,
Boris.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #10 from Marc H. Thoben <[email protected]> 2010-04-11 17:45:32 --- Hi Borislav,
when I got the new hardware I bought it with an ATI card. For 2 weeks it kept crashing - no matter if ran the closed-source driver or without. Blaming the ATI driver I bought an Nvidia card and had the same problem. I ran Xorg with the nvidia driver, with nv and with vesa. It happened for all of them (yes, I made sure the kernel wasn't tainted by nvidia's driver).
I found out about the netconsole module later, so I can't guarantee the problem now is the same problem as with the ATI card previously - but it for sure does seem so to me. I still have the ATI card here and could give it a try again if we need to know for sure.
In the meantime I have compiled the ide-cd_mod module with the changes you suggested and got two nice & big dmesg to report. This time I loaded netconsole before syslog is started, so you can see all kernel messages. I hope that's what you meant with "whole dmesg" - otherwise I'm sorry for the spam in those logs.
While doing tests I got one step further and I believe this is important: The kernel panic only shows up if there is no CD in the cdrom!
For the first test I booted the full system, loaded the new ide-cd_mod driver, made sure there is _no_ CD in the drive and then ran glxgears in a window with composite extension enabled (as mentioned above, this is the quickest way I found to reproduce the kernel panic). It crashes after a few seconds. It does so every time. This is in the first log I will attach after writing this.
For the second test I booted the full system, loaded the new ide-cd_mod driver, made sure there _is_ a CD in the drive, then ran glxgears for a bit, then ejected the CD (check for "Remove CD from CDROM" which I wrote to syslog with logger) and it crashed almost immediately. I haven't yet tried to reproduce this, but I saw it happen twice to me before. This is in the second log attached.
After these two tests I booted again as previously but this time kept the CD in the drive and went for dinner. That's about 50 minutes ago now - glxgears is still running without a kernel panic. I never before took care whether there is a CD in the drive or not, but it seems to prevent the kernel panic from happening.
Maybe my assumptions are all wrong - after all, I have no idea how to read those debugging messages. Thank you very much again for looking into this.
Best regards,
Marc
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #11 from Marc H. Thoben <[email protected]> 2010-04-11 17:49:02 --- Created an attachment (id=25959)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25959)
dmesg, debug ide-cd_mod, without CD in drive
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #12 from Marc H. Thoben <[email protected]> 2010-04-11 17:52:57 --- Created an attachment (id=25960)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25960)
dmesg, debug ide-cd_mod, with CD in drive at first then removed
For some reason netconsole didn't manage to transmit all of the last kernel panic message. Please let me know if you need me to recreate this.
Attachment size limit hit, gzipped.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #13 from Borislav Petkov <[email protected]> 2010-04-11 19:17:08 --- (In reply to comment #10)
Quoted 5 lines
when I got the new hardware I bought it with an ATI card. For 2 weeks it kept crashing - no matter if ran the closed-source driver or without. Blaming the ATI driver I bought an Nvidia card and had the same problem. I ran Xorg with the nvidia driver, with nv and with vesa. It happened for all of them (yes, I made sure the kernel wasn't tainted by nvidia's driver).
Nope, you can't do that. When you load a proprietary driver, your kernel is automatically tainted. It is in the oops:
Apr 11 18:34:29 sunshade [ 332.126868] Pid: 0, comm: swapper Tainted: P 2.6.32-4-amd64+mht.1 #1 P55A-UD4
The P means "Proprietary module has been loaded."
And there was a reason I asked you to try this without the proprietary nvidia driver. Especially if you have a bunch of nvidia-driver functions in the backtrace:
Apr 11 18:34:29 sunshade [ 332.127092] [<ffffffffa0ac506c>] ? cdrom_newpc_intr+0x819/0x84a [ide_cd_mod] Apr 11 18:34:29 sunshade [ 332.127095] [<ffffffffa0ac4853>] ? cdrom_newpc_intr+0x0/0x84a [ide_cd_mod] Apr 11 18:34:29 sunshade [ 332.127101] [<ffffffffa010df5c>] ? ide_intr+0x17c/0x20f [ide_core] Apr 11 18:34:29 sunshade [ 332.127105] [<ffffffff81048985>] ? default_wake_function+0x0/0xf Apr 11 18:34:29 sunshade [ 332.127109] [<ffffffff81092dd4>] ? handle_IRQ_event+0x55/0x109 Apr 11 18:34:29 sunshade [ 332.127112] [<ffffffff8109489d>] ? handle_fasteoi_irq+0x76/0xac Apr 11 18:34:29 sunshade [ 332.127171] [<ffffffff81013843>] ? handle_irq+0x17/0x1d Apr 11 18:34:29 sunshade [ 332.127174] [<ffffffff81012f0f>] ? do_IRQ+0x54/0xb2 Apr 11 18:34:29 sunshade [ 332.127177] [<ffffffff81011413>] ? ret_from_intr+0x0/0x11 Apr 11 18:34:29 sunshade [ 332.127299] [<ffffffffa05bbf09>] ? _nv005370rm+0x20/0x22 [nvidia] Apr 11 18:34:29 sunshade [ 332.127429] [<ffffffffa040aa19>] ? _nv012025rm+0x35/0xe1 [nvidia] Apr 11 18:34:29 sunshade [ 332.127561] [<ffffffffa04728f3>] ? _nv011220rm+0x1498/0x15a7 [nvidia] Apr 11 18:34:29 sunshade [ 332.127680] [<ffffffffa04feb15>] ? _nv008600rm+0x37d/0x813 [nvidia] Apr 11 18:34:29 sunshade [ 332.127798] [<ffffffffa04fdfc6>] ? _nv008603rm+0x66/0x90 [nvidia] Apr 11 18:34:29 sunshade [ 332.127907] [<ffffffffa05bcbc0>] ? _nv003827rm+0xa0/0xd3 [nvidia] Apr 11 18:34:29 sunshade [ 332.128017] [<ffffffffa05c2853>] ?
rm_isr_bh+0x5a/0x8d [nvidia]
See all those _nv0* things, they may very well be puzzling your cdrom drive. I know its crazy. So yes, please try the whole thing _without_ the nvidia driver and catch the logs again exactly as you've done it now.
Thanks,
Boris.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #14 from Marc H. Thoben <[email protected]> 2010-04-11 19:59:13 --- Yes, you are right. But I was talking about previous tests. This computer is crashing for 6 weeks already. At the moment it's tainted. But 6 weeks is a long time and I tried a lot scenarios, also without the Nvidia driver even being installed (not just not loaded into the kernel or unloaded). Too bad I didn't know about netconsole at the beginning.
Most of the other crash traces start at cpu_idle() calls, without mentioning any _nv0* things.
I'll reproduce without again. It'll take a while though, because without the Nvidia driver the panic is a bit harder to reproduce.
There is no way to reduce the amount of debugging messages, is there? The server with the remote syslog only has a small /var/log partition..
Thanks,
Marc.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #15 from Borislav Petkov <[email protected]> 2010-04-11 20:21:56 --- (In reply to comment #14)
Quoted 2 lines
There is no way to reduce the amount of debugging messages, is there? The server with the remote syslog only has a small
/var/logpartition..
You could try changing /etc/syslog.conf settings like so:
change:
*.*;auth,authpriv.none -/var/log/syslog
to
auth,authpriv.none -/var/log/syslog
and comment out all lines which have the kern.* facility:
kern.* -/var/log/kern.log
(at least this is what I have here). netconsole logging should still work though.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #16 from Marc H. Thoben <[email protected]> 2010-04-12 18:06:59 --- Created an attachment (id=25967)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25967)
dmesg, normal ide-cd_mod, untainted kernel
This is still with the non-debug ide-cd_mod module. Crash happened randomly, without nvidia module on harddisk, Xorg running with nouveau driver.
Will run the debug module now with modified syslog.conf.
Thank you!
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #17 from Dario Ernst <[email protected]> 2010-04-12 18:21:40 --- Same here, tried 1.5 days (and night) without loaded nvidia (and without GUI running) ... had one of the crashes (ide-cd compiled in kernel, not as module)
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #18 from Marc H. Thoben <[email protected]> 2010-04-12 19:06:27 --- Created an attachment (id=25968)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25968)
dmesg, debug ide-cd_mod, untainted kernel, request sense failure
Not sure this is connected.. while trying to force the kernel panic.. I mounted, unmounted, opened, closed.. ran some applications and suddenly got this (without CD in drive):
hda: request sense failure: status=0xc0 { Busy }
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: possibly failed opcode: 0xa0
hda: drive not ready for command
There's a call trace following. I rebooted, since the ide-cd module no longer logged anything.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #19 from Marc H. Thoben <[email protected]> 2010-04-13 18:22:58 --- Created an attachment (id=25992)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25992)
dmesg, debug ide-cd_mod, untainted kernel, request sense failure 2
Same as last time. Didn't touch the cdrom this time - didn't even run anything that could possibly try to check for an inserted medium.
Borislav, is this even slightly interesting? Or rather some bug with hald-addon-storage?
Couldn't make the kernel panic with the module being in debug mode.. about to give up soon.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #20 from Anonymous Emailer <[email protected]> 2010-04-14 08:08:28 ---
Reply-To: [email protected]
From: [email protected]
Date: Tue, Apr 13, 2010 at 06:23:05PM +0000
(switching to mail)
Quoted 8 lines
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #19 from Marc H. Thoben <[email protected]> 2010-04-13 18:22:58 --- Created an attachment (id=25992)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25992)
Quoted 8 lines
--> (https://bugzilla.kernel.org/attachment.cgi?id=25992)
dmesg, debug ide-cd_mod, untainted kernel, request sense failure 2Same as last time. Didn't touch the cdrom this time - didn't even run anything that could possibly try to check for an inserted medium.
Borislav, is this even slightly interesting? Or rather some bug with hald-addon-storage?
Ok, no, these are follow-up traces of hung tasks. I'm looking into the original oops. In the meantime, can you guys both try whether the problem still occurs with the latest kernel - 2.6.34-rc4 is that currently.
Thanks.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
From: [email protected]
Date: Tue, Apr 13, 2010 at 06:23:05PM +0000
(switching to mail)
Quoted 11 lines
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #19 from Marc H. Thoben <[email protected]> 2010-04-13 18:22:58 --- Created an attachment (id=25992)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25992)
dmesg, debug ide-cd_mod, untainted kernel, request sense failure 2
Quoted 5 lines
Same as last time. Didn't touch the cdrom this time - didn't even run anything that could possibly try to check for an inserted medium.
Borislav, is this even slightly interesting? Or rather some bug with hald-addon-storage?
Ok, no, these are follow-up traces of hung tasks. I'm looking into the original oops. In the meantime, can you guys both try whether the problem still occurs with the latest kernel - 2.6.34-rc4 is that currently.
Thanks.
Signature · 2 lines
Regards/Gruss,
Boris.https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #21 from Marc H. Thoben <[email protected]> 2010-04-14 18:42:53 --- Created an attachment (id=26001)
--> (https://bugzilla.kernel.org/attachment.cgi?id=26001)
dmesg, normal ide-cd_mod, tainted kernel 2.6.34-rc4
Pity I couldn't get Nouveau working with 2.6.34-rc4 without recompiling X/Mesa
- which I am not able to.
So I ran Nvidia again - but it's the same kernel panic, I believe.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
From: Borislav Petkov <[email protected]>
Date: Wed, Apr 14, 2010 at 10:07:37AM +0200
Hi,
[ Mark, please try replying with a simple mail instead over bugzilla since it is much easier to work that way, thanks ]
Quoted 9 lines
--- Comment #21 from Marc H. Thoben <[email protected]> 2010-04-14 18:42:53 --- Created an attachment (id=26001)
--> (https://bugzilla.kernel.org/attachment.cgi?id=26001)
dmesg, normal ide-cd_mod, tainted kernel 2.6.34-rc4Pity I couldn't get Nouveau working with 2.6.34-rc4 without recompiling X/Mesa
- which I am not able to.So I ran Nvidia again - but it's the same kernel panic, I believe.
No, tainted kernel doesn't help. The only info I get from this is that it might be that the proprietary crap interferes with the cdrom. How do I know it doesn't?
Well, I don't because I can't look at the source code. So the reason I'm asking you to retry without the nvidia driver is so that we can be really sure whether there's a bug.
Alternatively, if feel like you must use the nvidia driver, you can always try libata and use the scsi sr_mod driver for your cdrom. Simply enable CONFIG_BLK_DEV_SR or since you're using distro kernel, simply blacklist ide-cd_mod and load sr_mod (or something to that extent - there should be some description how to do this the debian way so use your favourite search engine).
Signature · 2 lines
Regards/Gruss,
Boris.https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #22 from Anonymous Emailer <[email protected]> 2010-04-14 20:48:26 ---
Reply-To: [email protected]
From: Borislav Petkov <[email protected]>
Date: Wed, Apr 14, 2010 at 10:07:37AM +0200
Hi,
[ Mark, please try replying with a simple mail instead over bugzilla since it is much easier to work that way, thanks ]
Quoted 2 lines
--- Comment #21 from Marc H. Thoben <[email protected]> 2010-04-14 18:42:53 --- Created an attachment (id=26001)
--> (https://bugzilla.kernel.org/attachment.cgi?id=26001)
Quoted 7 lines
--> (https://bugzilla.kernel.org/attachment.cgi?id=26001)
dmesg, normal ide-cd_mod, tainted kernel 2.6.34-rc4Pity I couldn't get Nouveau working with 2.6.34-rc4 without recompiling X/Mesa
- which I am not able to.So I ran Nvidia again - but it's the same kernel panic, I believe.
No, tainted kernel doesn't help. The only info I get from this is that it might be that the proprietary crap interferes with the cdrom. How do I know it doesn't?
Well, I don't because I can't look at the source code. So the reason I'm asking you to retry without the nvidia driver is so that we can be really sure whether there's a bug.
Alternatively, if feel like you must use the nvidia driver, you can always try libata and use the scsi sr_mod driver for your cdrom. Simply enable CONFIG_BLK_DEV_SR or since you're using distro kernel, simply blacklist ide-cd_mod and load sr_mod (or something to that extent - there should be some description how to do this the debian way so use your favourite search engine).
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #23 from Marc H. Thoben <[email protected]> 2010-04-16 17:19:08 --- Hello Borislav,
Thank you for that hint to finally start figuring out how to switch from IDE to LIBATA. It took me a while but it was worth it.
No kernel panics anymore using libata & pata_it8213 & sr_mod! :)
Quoted 7 lines
No, tainted kernel doesn't help. The only info I get from this is that it might be that the proprietary crap interferes with the cdrom. How do I know it doesn't?
Well, I don't because I can't look at the source code. So the reason I'm asking you to retry without the nvidia driver is so that we can be really sure whether there's a bug.
Well, I would have thought that showing the same kernel panic with the call traces showing the oops in the same functions over and over again, no matter whether the kernel is tainted or not, had made it obvious that the tainted status doesn't matter. Pity I couldn't get Nouveau working with 2.6.34. But running a single monitor setup for days just to wait for the randomly occurring crash wasn't an option. But yeah - I wish I didn't have to use the closed-source nvidia driver either.
Anyways.. Thank you very much again for taking time to look into this. I hope you'll find the cause. Let me know if anything comes up that you would like me to test or try out.
Cheers,
Marc
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #24 from Dario Ernst <[email protected]> 2010-04-28 21:39:04 --- Heho,
i've also tried again - with 2.6.34-rc4 and nouveau driver (propi one not even installed). Crash happened after ~1h (used the cdrom in between - without issues), netconsole truncated the output a bit, but the main portion looked like the good old problem.
Thanks for all of your time looking into this! Hoping it'll work out somehow in the future :P.
Thanks again
Reagards
- Dario
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #24 from Dario Ernst <[email protected]> 2010-04-28 21:39:04 --- Heho,
i've also tried again - with 2.6.34-rc4 and nouveau driver (propi one not even installed). Crash happened after ~1h (used the cdrom in between - without issues), netconsole truncated the output a bit, but the main portion looked like the good old problem.
Thanks for all of your time looking into this! Hoping it'll work out somehow in the future :P.
Thanks again
Reagards
- Dario
--- Comment #25 from Borislav Petkov <[email protected]> 2010-04-29 07:03:56 --- Hi Dario,
did you try switching to libata as Marc did?
Thanks,
Boris.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #26 from Dario Ernst <[email protected]> 2010-05-02 19:13:50 --- Okay, tried switching, now it actually seems to work.
Thanks alot!
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=14994
Alan <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |OBSOLETESignature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.