Sony V505BX ATA panic

[Søren Schmidt]

Simon L. Nielsen wrote:
> On 2004.02.14 21:38:37 +0100, Søren Schmidt wrote:
> 
>>Simon L. Nielsen wrote:
>>
>>>On 2004.02.14 20:24:51 +0300, Maxim Konovalov wrote:
>>>
>>>
>>>>Hi Soren,
>>>>
>>>>It seems the following commit broke my Sony V505BX:
>>>>
>>>>%sos         2004/01/30 11:16:08 PST
>>>>%
>>>>%  FreeBSD src repository
>>>>%
>>>>%    Modified files:
>>>>%      sys/dev/ata          ata-all.c ata-queue.c
>>>>%    Log:
>>>>%    Be more robust in the probe. We dont want to get into a loop with
>>>>%    reinitting when we try to identify devices. If they dont interrupt
>>>>%    on identify we retry once. If this fails we simply ignore that 
>>>>device.
>>>>%
>>>>%    Revision  Changes    Path
>>>>%    1.203     +10 -11    src/sys/dev/ata/ata-all.c
>>>>%    1.19      +28 -13    src/sys/dev/ata/ata-queue.c
>>>>
>>>>It panics right after the message
>>>>
>>>>ad0: 57231MB <FUJITSU MHS2060AT> [116280/16/63] at ata0-master UDMA100
>>>>ata1-slave: TIMEOUT - ATAPI_IDENTIFY no interrupt
>>>>ata1-slave: TIMEOUT - ATAPI_IDENTIFY no interrupt
>>>>acd0: CDRW <UJDA745 DVD/CDRW> at ata1-master UDMA33
>>>
>>>
>>>This also makes my IBM Thinkpad R40 boot again.
>>
>>And it disables the LiteOn workaround...
> 
> 
> Yes, exactly... (hardware sucks) I mainly wanted to let other poeple
> with the same hardware know about this workaround.
> 
> Since this is a real panic, and not a hang, I think this workaround just
> hides the real problem which might be somewhere else.  I hope to have a
> look what really goes wrong tomorrow.  I guess it's time to try firewire
> debugging.
> 
> BTW. I haven't told you about the problem before because didn't want to
> bother you with the problem until I could give you a proper error
> report.

Just get a panic with ddb and get me the traceback...

-- 
-Søren