Date: Wed, 24 Mar 2004 05:09:28 +1100 From: Andrew Milton <akm@theinternet.com.au> To: S?ren Schmidt <sos@DeepCore.dk> Cc: current@freebsd.org Subject: Re: ata - interrupt seen but task queue stalled Message-ID: <20040323180928.GQ4875@camelot.theinternet.com.au> In-Reply-To: <405FFB04.1090005@DeepCore.dk> References: <6.0.3.0.2.20040323011610.03842e70@mail.nls.net> <20040323062914.GL4875@camelot.theinternet.com.au> <6.0.3.0.2.20040323023317.03842be0@error404.nls.net> <405FEC11.7050001@DeepCore.dk> <6.0.3.0.2.20040323033603.0383c040@error404.nls.net> <405FFB04.1090005@DeepCore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
+-------[ S?ren Schmidt ]----------------------
| Ketrien I. Saihr-Kesenchedra wrote:
| >At 02:49 AM 3/23/2004, S?ren Schmidt wrote:
| >
| >>Didn't you say it was on a ROSB4 chipset ? The ROSB4 doesn't really
| >>support DMA on ATAPI devices, and has severe HW bugs that can cause
| >>problems with UDMA on disks as well..
| >
| >
| >Yes, but this and sysctl's are a non-issue. The controller is set to
| >PIO4 and actually locked there. The drive itself doesn't do anything but
| >PIO4, being a slim CD-ROM. The OS resides on an ips. ie; This is a
| >genuinely new issue, and I can say with a fair degree of certainty that
| >it's something that's been changed. I can't break to debug either, but
| >the kernel configuration didn't change between working and non-working.
|
| Hmm, if you could provide us with a bit more information as to which
| date it worked at and which date it broke, and the output of dmesg, then
| we could do some qualified support, but without that, ENOCLUE...
My pioneer DVD hasn't been reliable for months...
This is from a cvsup around 48 hours ago.
This is stuff from a verbose boot that didn't panic or hang.
atapci0: <VIA 8235 UDMA133 controller> port 0xa400-0xa40f at device 17.1 on pci0
ata0: reset tp1 mask=03 ostat0=50 ostat1=00
ata0-master: stat=0x10 err=0x01 lsb=0x14 msb=0xeb
ata0-slave: stat=0x00 err=0x01 lsb=0x14 msb=0xeb
ata0: reset tp2 mask=03 stat0=10 stat1=00 devices=0xc<ATAPI_SLAVE,ATAPI_MASTER>
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: reset tp1 mask=03 ostat0=20 ostat1=30
ata1-master: stat=0x20 err=0x20 lsb=0x20 msb=0x20
ata1-slave: stat=0x30 err=0x30 lsb=0x30 msb=0x30
ata1: reset tp2 mask=03 stat0=20 stat1=30 devices=0x0
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
ata0-slave: pio=0x0c wdma=0x22 udma=0x44 cable=80pin
ata0-master: pio=0x0c wdma=0x22 udma=0x42 cable=40pin
ata0-master: setting PIO4 on VIA 8235 chip
ata0-slave: setting PIO4 on VIA 8235 chip
acd0: <ASUS CD-S400/V1.10> CDROM drive at ata0 as master
acd0: read 1031KB/s (6875KB/s), 128KB buffer, PIO4
acd0: Reads: CDR, CDRW, CDDA stream, packet
acd0: Writes:
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray, unlocked
acd0: Medium: CD-ROM 120mm audio disc
acd1: <Pioneer DVD-ROM ATAPIModel DVD-120/1.23> DVDROM drive at ata0 as slave
acd1: read 6875KB/s (6875KB/s), 256KB buffer, PIO4
acd1: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet
acd1: Writes:
acd1: Audio: play, 256 volume levels
acd1: Mechanism: ejectable tray, unlocked
acd1: Medium: no/blank disc
This is the panic I get:
acd1: WARNING - MODE_SENSE_BIG read data overrun 65438 > 34
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc321f2e0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0461df6
stack pointer = 0x10:0xd5597cac
frame pointer = 0x10:0xd5597ccc
code segment = base 0x0, limit 0xffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 24 (irq14: ata0)
trap number = 12
panic : page fault
at line 815 in file /usr/src/sys/i386/i386/trap.c
When the system hangs I normally see something like.
acd1: WARNING - READ_TOC read data overrun 65438 > 20
let me know if you want any other information.
--
Totally Holistic Enterprises Internet| | Andrew Milton
The Internet (Aust) Pty Ltd | M:+61 416 022 411 |
ACN: 082 081 472 ABN: 83 082 081 472 |akm@theinternet.com.au| Carpe Daemon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040323180928.GQ4875>