Re: a couple of oopses with 2.6.14

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxxxxx> 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).

> 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.

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux