[Soekris] ad0 dying during bootup w/FreeBSD 5.2.1 on 4801
ray at atnip.net
Sat Sep 25 02:30:35 UTC 2004
Ok, I have a difference on the boot outputs.
The Sandisk that boots and runs fine shows
ad0: 245MB <SanDisk SDCFH-256> [980/16/32] at ata0-master PIO4
the CF that fails during boot shows
ad0: 245MB <SanDisk SDCFB-256> [980/16/32] at ata0-master WDMA2
So my new (or another) question is why is one showing a PIO4 and the
other a WDMA2?
On Fri 24 Sep at 20:05:21 -0500 ray at atnip.net done said:
> I'm having an interesting problem. I have been working about a month to
> get a
> CF loaded with FreeBSD for a project I'm working on. I've ended up using
> nanobsd which I've modified some to suit my needs using FreeBSD 5.2.1.
> I have built a system and dd'ed it to a SanDisk 256MB CF and the system
> boots and runs fine. The problem is that when I
> take a second SanDisk 256MB CF and dd to it, it boots to a point then dies.
> Here is the last few lines of output.
> ata0: at 0x1f0 irq 14 on atapci0
> ata0: [MPSAFE]
> ata1: at 0x170 irq 15 on atapci0
> ata1: [MPSAFE]
> Geode CBA@ 0x6000
> Timecounter "Geode" frequency 27000000 Hz quality 1000
> pci0: <bridge, PCI-unknown> at device 18.5 (no driver attached)
> pci0: <serial bus, USB> at device 19.0 (no driver attached)
> orm0: <Option ROM> at iomem 0xc8000-0xd1fff on isa0
> pmtimer0 on isa0
> atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A, console
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> Timecounters tick every 2.000 msec
> ipfw2 initialized, divert disabled, rule-based forwarding enabled, default
> to de
> ny, logging disabled
> GEOM: create disk ad0 dp=0xc1820e60
> ad0: 245MB <SanDisk SDCFB-256> [980/16/32] at ata0-master WDMA2
> ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=0
> ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA=0
> ad0: WARNING - READ_DMA interrupt was seen but taskqueue stalled LBA=0
> So what I have is one SanDisk that works fine and another that doesn't
> with the same identical code.
> The CFs were purchased from the same place at the same time.
> Do I have a problem with one of my SanDisks? Or is there something else
> going on?
> I have done this with my own kernel config and I have done the GENERIC
> config as it comes
> with FreeBSD 5.2.1. The results are the same.
> The same CF fails everytime and the other CF works every time.
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
> Soekris-tech mailing list
> Soekris-tech at lists.soekris.com
"If we couldn't laugh, we would all go insane." -- Jimmy Buffett
rm -r /bin/laden
More information about the Soekris-tech