Re: a couple of oopses with 2.6.14

[Bernd Schubert <bernd.schubert@pci.uni-heidelberg.de>]

On Friday 10 February 2006 20:29, Andrew Morton wrote:
> Bernd Schubert <bernd.schubert@pci.uni-heidelberg.de> wrote:
> > > Can you test 2.6.15?
> >
> > Yes, 2.6.15.3 works, no oopses.
>
> Some progress.
>
> > Only this information
> >
> > [4294743.341000] scsi0 : ata_piix
> > [4294743.514000] ATA: abnormal status 0x7F on port 0xE407
> >
> > I can't test if sata works, there's just nothing connected.
>
> Has this machine's sata support ever worked?  If so, in which kernel?
> (Apologies if you've already described this).

Don't know, there was never anything connected to the sata ports. It was also 
just an accident that sata was compiled statically into the kernel.
Though, with 2.6.11 we don't get the warnings:

libata version 1.10 loaded.
ata_piix version 1.03
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE802 bmdma 0xDC00 irq 18
ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 18
ata1: SATA port has no device.
scsi0 : ata_piix
ata2: SATA port has no device.
scsi1 : ata_piix
ieee1394: Initialized config rom entry `ip1394'


>
> > Btw, the printk timing information seem to be uninitalized, is this by
> > intentention or is it a bug?
>
> It's expected.  We use a very raw, low-level funtion for the printk
> timestamping because we don't want to be taking locks from within printk.
> The timestamping is mainly for working out the time duration between
> printk's, rather than for absolute time.

Ah, I see.

Thanks,
	Bernd

-- 
Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de
-
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/