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 11:09:51 GMT [thread overview]
Message-ID: <201004111109.o3BB9pff021216@demeter.kernel.org> (raw)
In-Reply-To: <bug-14994-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=14994
Borislav Petkov <bbpetkov@yahoo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bbpetkov@yahoo.de
--- Comment #4 from Borislav Petkov <bbpetkov@yahoo.de> 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:
diff --git a/drivers/ide/ide-cd.c b/drivers/ide/ide-cd.c
index 64207df..4713094 100644
--- a/drivers/ide/ide-cd.c
+++ b/drivers/ide/ide-cd.c
@@ -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);
diff --git a/drivers/ide/ide-cd.h b/drivers/ide/ide-cd.h
index 93a3cf1..613542a 100644
--- a/drivers/ide/ide-cd.h
+++ b/drivers/ide/ide-cd.h
@@ -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)
--
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 11:09 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 [this message]
2010-04-11 12:13 ` bugzilla-daemon
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=201004111109.o3BB9pff021216@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.