Albert Lee schrieb:
It looks like the command is running in PIO polling thread.
The timeout handler is called and the qc is cleared.
So, the PIO polling thread got NULL qc.
Could you post more trace before the timeout occurs, thanks,
Sure. Here it is:
Jan 3 15:21:32 DatenGrab kernel: ata1: command timeout
Jan 3 15:21:32 DatenGrab kernel: ATA: abnormal status 0xFF on port
0xE006821C
Jan 3 15:21:32 DatenGrab kernel: ata1: translated ATA stat/err 0xff/00
to SCSI SK/ASC/ASCQ 0xb/47/00
Jan 3 15:21:32 DatenGrab kernel: ata1: status=0xff { Busy }
Jan 3 15:21:32 DatenGrab kernel: ATA: abnormal status 0xFF on port
0xE006821C
Jan 3 15:21:32 DatenGrab kernel: ATA: abnormal status 0xFF on port
0xE006821C
Jan 3 15:21:32 DatenGrab kernel: ATA: abnormal status 0xFF on port
0xE006821C
Jan 3 15:21:32 DatenGrab kernel: ATA: abnormal status 0xFF on port
0xE006821C
Jan 3 15:21:35 DatenGrab kernel: ata1: unknown timeout, cmd 0xb0 stat 0xff
Jan 3 15:21:35 DatenGrab kernel: ata1: translated ATA stat/err 0xff/00
to SCSI SK/ASC/ASCQ 0xb/47/00
Jan 3 15:21:35 DatenGrab kernel: ata1: status=0xff { Busy }
Jan 3 15:21:35 DatenGrab kernel: Assertion failed! qc !=
NULL,drivers/scsi/libata-core.c,ata_pio_block,line=3216
Jan 3 15:21:35 DatenGrab kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000014
Jan 3 15:21:35 DatenGrab kernel: printing eip:
Jan 3 15:21:35 DatenGrab kernel: e02d9a3e
Jan 3 15:21:35 DatenGrab kernel: *pde = 00000000
Jan 3 15:21:35 DatenGrab kernel: Oops: 0000 [#1]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
