Re: Oops in 2.6.10-rc1
From: Pekka Enberg (penberg_at_gmail.com)
Date: 11/08/04
- Previous message: Jay Lan: "[PATCH 2.6.9 2/2] enhanced Memory accounting data collection"
- In reply to: Greg KH: "Re: Oops in 2.6.10-rc1"
- Next in thread: Pekka Enberg: "Re: Oops in 2.6.10-rc1"
- Reply: Pekka Enberg: "Re: Oops in 2.6.10-rc1"
- Reply: Christian Kujau: "Re: Oops in 2.6.10-rc1"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 8 Nov 2004 21:18:09 +0200 To: Greg KH <greg@kroah.com>
Hi,
On Mon, 8 Nov 2004 11:00:40 -0800, Greg KH <greg@kroah.com> wrote:
> But 2.6.10-rc1-bk15 does have the problem?
>
> Trying to figure out where the issue is...
No, -bk14 is just the kernel I am running right now (I haven't tried
-bk15) and I haven't had the problem. I cannot reproduce the oops _at
all_ which is why I suspect it's his hardware. I included my lspci and
dmesg output because we have similar (but not exactly the same)
setups.
FWIW, I've asked Christian for an obdump of the kernel to see if I can
track down where it oopses at because I cannot find anything in the
code. I suspected pcibios_enable_irq (which is a function pointer)
might be wrong but looking at his logs, I don't think we get that far.
Pekka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Jay Lan: "[PATCH 2.6.9 2/2] enhanced Memory accounting data collection"
- In reply to: Greg KH: "Re: Oops in 2.6.10-rc1"
- Next in thread: Pekka Enberg: "Re: Oops in 2.6.10-rc1"
- Reply: Pekka Enberg: "Re: Oops in 2.6.10-rc1"
- Reply: Christian Kujau: "Re: Oops in 2.6.10-rc1"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|