From owner-freebsd-stable Fri Mar 22 17:22:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from biliskner.great4.co.uk (biliskner.great4.co.uk [212.111.52.245]) by hub.freebsd.org (Postfix) with ESMTP id CB9FB37B417 for ; Fri, 22 Mar 2002 17:22:26 -0800 (PST) Received: from antaeus (unknown [172.22.1.76]) by biliskner.great4.co.uk (Postfix) with ESMTP id 1214A540B for ; Sat, 23 Mar 2002 01:23:53 +0000 (GMT) Message-ID: <00bf01c1d209$31921380$4c0116ac@antaeus> From: "Andrew Tulloch" To: References: <3C9B9E65.CA168CF1@yahoo.com> Subject: Re: More on ata Trap 12 with tagged queuing enabled Date: Sat, 23 Mar 2002 01:22:26 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm seeing exactly the same panic, I already reported it to Soren as I was dealing with him for a patch for the latest serverworks IDE chipset found in Dell Poweredge 500SC's, which got me off PIO4 to ATA100 (Thanks Soren!) This is obviously with the aformentioned serverworks chipset and although I've not had the machine apart the dmesg indicates the drive is an IBM 60GXP model (20gig) my panic as below: ad0: timeout waiting for READY ad0: invalidating queued requests - resetting done ad0: no read request for tag=0 ad0 invalidating queued requests ad0: READ command timeout tag=0 serv=0 - resetting ad0: invalidating queued requests ata0 resetting devices .. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x70 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01830a8 stack pointer = 0x10:0xc02f3e1c frame pointer = 0x10:0xc02f3e40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam kernel: type 12 trap, code=0 Stopped at tsleep+0x78: cmpl $0,0x70(%ebx) db>trace tsleep(c0bb7e00,10,c02bf1e6,3e8) at tsleep+0x78 ata_command(c0bb7e2c,ec,0,0,0,0,2) at ata_command+0x4bd ata_getparam(c0bb7e2c,ec,c0bee000,c0bbd380,400000) ata ata_getparam+0x23 ata_reinit(c0bb7e00,c0bbd380,co151608,c02f3ef0,c0186001) at ata_reinit+0x1fe ad_timeout(c0bbd380,400000,0,0,ffffffff) at ad_timeout+0x131 softclock(,0,10,10,c02a0010,ffffffff) at softclock+0xd1 doreti_swi() at doreti_swi+0xf Andrew Tulloch Lead Web Developer Great4 Ltd 2nd Floor 200 Grays Inn Road London WC1X 8XZ Tel: 0207 316 3126 Email : andrewt@great4.co.uk http://www.itv-f1.com http://www.bar.net ----- Original Message ----- From: "John Merryweather Cooper" To: Sent: Friday, March 22, 2002 9:13 PM Subject: More on ata Trap 12 with tagged queuing enabled > As requested, I've recompiled my kernel (after cvsupping) with > > options DDB > > With tagged queuing enabled in /boot/loader.conf, I get the following > trap and trace: > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x70 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc017705c > stack pointer = 0x10:0xc02ec6fc > frame pointer = 0x10:0xc02ec720 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = idle > iterrupt mask = net tty bio cam > kernel: type 12 trap, code=0 > Stopped at tsleep+0x74: cmpl $0,0x70(%ebx) > db> trace > tsleep(c1dc8100,10,c02b6ce6,2710) at tsleep+0x74 > ata_command(c1d812c,ec,0,0,0,0,2) at ata_command+0x4ed > ata_getparam(c1dc812c,ec,c1ee9c00,c1dec340,400000) at ata_getparam+0x23 > ata_reinit(c1dc8100,c1dec340,c01482d4,c02ec7d0,c0179ec5) at > ata_reinit+0x1ea > ad_timeout(c1dec340,400000,0,0,ffffffff) at ad_timeout+0x122 > softclock(0,10,10,10,ffffffff) at softclock+0xd1 > doreti_swi() at doreti_swi+oxf > db> > > I hope this helps. > > jmc > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message