Re: a couple of oopses with 2.6.14

[Bernd Schubert <bernd-schubert@gmx.de>]

Hello Andrew and James,

thanks for your help.


On Friday 10 February 2006 00:27, Andrew Morton wrote:
> Bernd Schubert <bernd.schubert@pci.uni-heidelberg.de> wrote:
> > Hi,
> >
> > here's a machine that works perfectly with 2.6.11, but gives oopes during
> > the boot process with 2.6.14. Unfortunately its everytime another oops.
> > Usually I would assume its a memory issue, but the machine really works
> > perfectly with 2.6.11.
>
> scsi has had a few problems with error recovery lately.
>
> > We will run a memory test over the weekend, but so far I don't believe it
> > will find anything.
>
> No, I wouldn't bother doing that.

Ok.

>
> > ------------- example 1
> > ------------------------------------------------------
> >
> > [4294676.669000] scsi0 : ata_piix
> > [4294676.831000] ATA: abnormal status 0x7F on port 0xE407
>
> So we have a sata problem.  It triggered two scsi bugs.  The first (a
> warning) is being fixed.  I don't know if the second has been fixed.

I'm not sure if its only a sata problem, I saw several of other oopses, one 
was related to Firewire/scsi (ok, could be a consequence of the previous sata 
problem), one came from bluesmoke (external patch) and some of them I 
couldn't associate to anything (but those I couldn't also capture via 
netconsole).


>
> Can you test 2.6.15?
>

Sure, I will test 2.6.15 this evening. I will also enable most debugging 
information for this testkernel, ok?


Thanks,
	Bernd


PS: For production we unfortunately can't use 2.6.15 - reiserfs trouble (well, 
I could try to revert commit 5fa8ad644faa114c4190484ac50e15236fc7cdd9, but 
I'm still waiting for an offical statement of the reiserfs poeple) and 
Win4Lin patches are available up to 2.6.14 only (its the PC of our secretary 
and she really wouldn't like that ;) ).

-- 
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html