All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:59:21 GMT	[thread overview]
Message-ID: <201004111959.o3BJxLdS015954@demeter.kernel.org> (raw)
In-Reply-To: <bug-14994-11633@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=14994





--- Comment #14 from Marc H. Thoben <kernelbug@develz.org>  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.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-04-11 19:59 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
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 [this message]
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=201004111959.o3BJxLdS015954@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.