From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Date: Mon, 08 Nov 2004 19:18:09 +0000 Subject: Re: Oops in 2.6.10-rc1 Message-Id: <84144f02041108111816dc0b3a@mail.gmail.com> List-Id: References: <418D7959.4020206@g-house.de> <20041107130553.M49691@g-house.de> <418E4705.5020001@g-house.de> <20041107182155.M43317@g-house.de> <418EB3AA.8050203@g-house.de> <418F6E33.8080808@g-house.de> <84144f0204110810444400761f@mail.gmail.com> <20041108190040.GC27386@kroah.com> In-Reply-To: <20041108190040.GC27386@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg KH Cc: Christian Kujau , Kernel Mailing List , Linus Torvalds , alsa-devel@lists.sourceforge.net, linux-sound@vger.kernel.org, penberg@cs.helsinki.fi Hi, On Mon, 8 Nov 2004 11:00:40 -0800, Greg KH 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