From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 14994] Random Panic/Freeze due to BUG: unable to handle kernel NULL pointer dereference at 00000024(?)
Date: Sun, 11 Apr 2010 12:13:02 GMT [thread overview]
Message-ID: <201004111213.o3BCD22R017565@demeter.kernel.org> (raw)
In-Reply-To: <bug-14994-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=14994
--- Comment #5 from Marc H. Thoben <kernelbug@develz.org> 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.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-04-11 12:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14994-11633@https.bugzilla.kernel.org/>
2010-04-11 9:51 ` [Bug 14994] Random Panic/Freeze due to BUG: unable to handle kernel NULL pointer dereference at 00000024(?) bugzilla-daemon
2010-04-11 11:09 ` bugzilla-daemon
2010-04-11 12:13 ` bugzilla-daemon [this message]
2010-04-11 12:14 ` bugzilla-daemon
2010-04-11 12:17 ` bugzilla-daemon
2010-04-11 12:18 ` bugzilla-daemon
2010-04-11 13:09 ` bugzilla-daemon
2010-04-11 15:52 ` bugzilla-daemon
2010-04-11 17:45 ` bugzilla-daemon
2010-04-11 17:49 ` bugzilla-daemon
2010-04-11 17:53 ` bugzilla-daemon
2010-04-11 19:17 ` bugzilla-daemon
2010-04-11 19:59 ` bugzilla-daemon
2010-04-11 20:22 ` bugzilla-daemon
2010-04-12 18:07 ` bugzilla-daemon
2010-04-12 18:21 ` bugzilla-daemon
2010-04-12 19:06 ` bugzilla-daemon
2010-04-13 18:23 ` bugzilla-daemon
2010-04-14 8:07 ` Borislav Petkov
2010-04-14 20:46 ` Borislav Petkov
2010-04-14 8:08 ` bugzilla-daemon
2010-04-14 18:43 ` bugzilla-daemon
2010-04-14 20:50 ` bugzilla-daemon
2010-04-16 17:19 ` bugzilla-daemon
2010-04-28 21:40 ` bugzilla-daemon
2010-04-29 7:04 ` bugzilla-daemon
2010-05-02 19:13 ` bugzilla-daemon
2012-06-18 14:29 ` bugzilla-daemon
[not found] <bug-14994-11633@http.bugzilla.kernel.org/>
2010-01-19 15:45 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004111213.o3BCD22R017565@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.