From: Greg KH <gregkh@suse.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: v2.6.28-rc7: error in panic code? (NULL pointer dereference at 0000004c)
Date: Fri, 19 Dec 2008 16:46:06 -0800 [thread overview]
Message-ID: <20081220004606.GA608@suse.de> (raw)
In-Reply-To: <84144f020812191235u4106766bhee28134632c302e2@mail.gmail.com>
On Fri, Dec 19, 2008 at 10:35:57PM +0200, Pekka Enberg wrote:
> Hi Greg,
>
> On Fri, Dec 19, 2008 at 06:19:43PM +0100, Vegard Nossum wrote:
> > Fixes what? It might be quite difficult to revert that patch now, as
> > the infrastructure is no longer in place to use a private pci device
> > list, that code is long gone.
>
> Vegard forced one oops but got two! The first one is expected and but
> the second one shouldn't probably be there:
"Second" oopses are known to not be reliable, I wouldn't count it as a
real problem unless it happens on its own.
> >> > [ 0.040993] EIP: [<c13b41dc>] klist_next+0x10/0x8d SS:ESP 0068:c165dd48
>
> Looks like the patch Vegard identified breaks something in the oops path?
Very wierd, I also don't understand how reverting the specific patch
would even make a buildable system.
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-20 1:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 22:06 v2.6.28-rc7: error in panic code? (NULL pointer dereference at 0000004c) Vegard Nossum
2008-12-19 17:19 ` Vegard Nossum
2008-12-19 17:39 ` Greg KH
2008-12-19 20:35 ` Pekka Enberg
2008-12-20 0:46 ` Greg KH [this message]
2008-12-20 8:52 ` Vegard Nossum
2008-12-20 8:58 ` Greg KH
2008-12-20 10:56 ` [PATCH] pci: fix no_pci_devices() Vegard Nossum
2008-12-20 11:14 ` [PATCH] pci: fix no_pci_devices() #2 Vegard Nossum
2008-12-20 23:31 ` Greg KH
2009-01-05 19:09 ` Jesse Barnes
2009-01-07 0:42 ` Greg KH
2009-01-16 18:41 ` Jesse Barnes
2009-01-16 19:21 ` Vegard Nossum
2009-01-27 18:41 ` Jesse Barnes
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=20081220004606.GA608@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
/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