Re: RELENG_5: ata interrupt problems

From: Simon L. Nielsen <simon_at_FreeBSD.org>
Date: Sun, 22 Aug 2004 16:05:30 +0200
On 2004.08.22 15:17:54 +0200, Søren Schmidt wrote:
> Simon L. Nielsen wrote:
> >On 2004.08.22 14:27:37 +0200, Søren Schmidt wrote:
> >
> >>Randy Bush wrote:
> >>
> >>>>The actual errors from a 5.3-BETA from today (hand transcribed):
> >>>
> >>>>ad0: 73863MB <HTS548080M9AT00/MG40A50A> [150071/16/63] at ata0-master 
> >>>>UDMA100
> >>>>ATAPI_RESET time = 150us
> >>>>ata1-slave: FAILURE - ATAPI_IDENTIFY timed out
> >>>>ATAPI_RESET time = 150us
> >>>>acd0: CDRW <UJDA740 DVD/CDRW/1.04> at ata1-master UDMA33
> >>>>Mounting root from ufs:/dev/ad0s2a
> >>>>[...]
> >>>>ad0: WARNING - READ_DME interupt was seen but timeout fired LBA=41574224
> >>>>[...]
> >>>>ad0: WARNING - READ_DME interupt was seen but timeout fired LBA=41562160
> >>>>ad0: WARNING - READ_DME interupt was seen but timeout fired LBA=41562160
> >>>>ad0: WARNING - READ_DME interupt was seen but taskqueue stalled 
> >>>>LBA=41562160
> >>>>Slab at 0xc1c3ff70, freei 3 = 0
> >>>>
> >>>>The "[...]" is just normal startup.  It goes as far as the script that
> >>>>attaches my GDBE partition before it panics.
> >>>>
> >>>>And then it panics like below:
> >>>
> >>>yep.  same on a thinkpad t40p
> 
> Could I have you try the below patch and mail me the output from dmesg 
> on a failed boot please?. I need to know what kind of state those damned 
> fakeslave devices are in to be able to fix this problem.

It just says "status=00 error=00", but complete dmesg is attached (as
much as dcons(4) has on boot).  BTW. this is RELENG_5.

> Or someone get me one of those crappy drives that does this here in the 
> lab to disect...

Since the drives use some special laptop connector it's probably not
really useful without a compatible IBM laptop...

-- 
Simon L. Nielsen
FreeBSD Documentation Team

Received on Sun Aug 22 2004 - 12:05:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:07 UTC