From: Andi Kleen <andi@firstfloor.org>
To: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, DSA <debian-admin@lists.debian.org>,
linux-input@vger.kernel.org
Subject: Re: 2.6.32.1: BUG and panic: unable to handle kernel NULL pointer dereference at 000000000000001f
Date: Sat, 26 Dec 2009 18:12:02 +0100 [thread overview]
Message-ID: <20091226171202.GB10256@basil.fritz.box> (raw)
In-Reply-To: <20091224130425.GW13850@anguilla.noreply.org>
On Thu, Dec 24, 2009 at 02:04:25PM +0100, Peter Palfrader wrote:
> On Tue, 22 Dec 2009, Peter Palfrader wrote:
>
> > On Tue, 22 Dec 2009, Peter Palfrader wrote:
> >
> > > > If that doesn't help perhaps disable CONFIG_HID_GYRATION,
> > > > but from your other oops something more seems to be broken anyways.
> > >
> > > This is a static kernel - no module support. Anyway, I also tried
> > > without CONFIG_USB_HID (which pulls in all the other HID_* things) but
> > > no luck.
> >
> > However, disabling all of HID (CONFIG_HID_SUPPORT=n) makes the system
> > boot (Previously HID, HIDRAW and HID_SUPPORT were still enabled).
It's suspicious if you don't have such devices, that would
point to something being confused in the driver probing
layer.
>
> However, I still see panics on boot occassionally, tho not so often or
> reproducible. So far only on dl385 (opteron) systems.
Multiple systems and the same oopses?
>
> And all of the backtraces go through sysfs_new_dirent() near the top.
Please post full oopses.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-12-26 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091215162736.GS13850@anguilla.noreply.org>
2009-12-22 12:04 ` 2.6.32.1: BUG and panic: unable to handle kernel NULL pointer dereference at 000000000000001f Andi Kleen
2009-12-22 18:33 ` Peter Palfrader
2009-12-22 18:42 ` Andi Kleen
2009-12-22 19:01 ` Peter Palfrader
2009-12-22 18:57 ` Peter Palfrader
2009-12-24 13:04 ` Peter Palfrader
2009-12-26 17:12 ` Andi Kleen [this message]
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=20091226171202.GB10256@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=debian-admin@lists.debian.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).