Hi,

Sounds like he's got the same chipset as I do.  Same symptoms, see:

http://www.freebsd.org/cgi/query-pr.cgi?pr=40003

It took me a while but I got a trace with Julian and DES's help, it's
attached to the pr now.  In one of the past threads on this, there's this
response:

-----
(kgdb) p adp
$2 = (struct ad_softc *) 0x68c040
(kgdb) p atadev
$3 = (struct ata_device *) 0xc075b650
(kgdb) p *adp
Cannot access memory at address 0x68c040.
(kgdb) p *atadev
$4 = {channel = 0xc075b600, unit = 16, name = 0xc04503b0 "ad1", param = 0x0,
 driver = 0x0, flags = 0, mode = 0, cmd = 0, result = 0x0}

ad_attach() is trying to dereference atadev->param, which is NULL.
-----

I'm still set up with remote gdb ready to go if you need any other info.

I also used to get the "falling back to PIO" delays/resets, regardless of
whether I turn off dma in loader.conf.

Thanks,

Charles

--
Charles Sprickman
[EMAIL PROTECTED]


On Fri, 2 Aug 2002, Soeren Schmidt wrote:

> It seems Martin Blapp wrote:
> > We get repeatable panics on a old machine, where a ATA
> > disk seems to have problems.
> >
> > It works fine on 4.4 (beside some timeout messages),
> > panics reproducable at startup every time at the same
> > place.
> >
> > With 4.4 we got:
> >
> > ad0: READ command timeout tag=0 serv=0 - resetting
> > ata0: resetting devices .. done
> > ad0: READ command timeout tag=0 serv=0 - resetting
> > ata0: resetting devices .. done
> > ad0: READ command timeout tag=0 serv=0 - resetting
> > ata0: resetting devices .. done
> > ad0: READ command timeout tag=0 serv=0 - resetting
> > ad0: trying fallback to PIO mode
> > ata0: resetting devices .. done
> >
> > Everything worked. Now, after a upgrade to 4.6 STABLE
> > we get a panic after "ad0: trying fallback to PIO mode".
>
> dmesg ? !?!
>
> > Set the device in BIOS to PIO mode doesn't help too.
>
> That changes nothing at all..
>
> Maybe you could disable DMA from the loader, does it work then ?
>
> -Søren
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to