Re: i386/amd64 kernels hanging on boot

[Carlos Linares <speed_daemon%the-carlos.net@localhost>]

No problems with that, no.

# fdisk wd0
Disk: /dev/rwd0d
NetBSD disklabel disk geometry:
cylinders: 1938018, heads: 16, sectors/track: 63 (1008 sectors/cylinder)
total sectors: 1953523055

BIOS disk geometry:
cylinders: 1024, heads: 240, sectors/track: 63 (15120 sectors/cylinder)
total sectors: 1953523055

Partition table:
0: NetBSD (sysid 169)
    start 63, size 1953522992 (953869 MB, Cyls 0-129201/62/29), Active
1: <UNUSED>
2: <UNUSED>
3: <UNUSED>
Bootselector disabled.
First active partition: 0

But:
# fdisk wd1
fdisk: DIOCGDEFLABEL: Inappropriate ioctl for device
fdisk: DIOCGDINFO: Inappropriate ioctl for device
# fdisk wd1d
Disk: /dev/rwd1d
NetBSD disklabel disk geometry:
cylinders: 1938021, heads: 16, sectors/track: 63 (1008 sectors/cylinder)
total sectors: 1953525168

BIOS disk geometry:
cylinders: 1024, heads: 255, sectors/track: 63 (16065 sectors/cylinder)
total sectors: 1953525168

Partition table:
0: NetBSD (sysid 169)
    start 63, size 1953525105 (953870 MB, Cyls 0-121601/80/63), Active
1: <UNUSED>
2: <UNUSED>
3: <UNUSED>
Bootselector disabled.
First active partition: 0

FWIW, the boot-time problems started while wd1 was still an unformatted but connected drive. BTW, these are the same drive model - is it usual for the above numbers to differ?

<<carlos>>
<<respvblicaest>>

----- Original Message ----
From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: Carlos Linares <speed_daemon%the-carlos.net@localhost>
Cc: current-users%NetBSD.org@localhost
Sent: Wednesday, October 1, 2008 2:57:38 PM
Subject: Re: i386/amd64 kernels hanging on boot

On Tue, Sep 30, 2008 at 08:37:25PM -0700, Carlos Linares wrote:
> Hello all.  For a little while now, amd64 successive -current kernels have been hanging at boot time on one of my machines.  I tried compiling an i386 kernel or two today, and I got the same error.  The last kernel that works for me is an amd64 4.99.72 from late August.  I had one from slightly later that worked, but it got truncated along with the kernel I booted during one of these hanging boots (though more recent kernels have not inflicted such damage).  Here are the error messages:
>
>
>  ixpide0:0:0: recal drive fault
> wd0d: device fault reading fsbn 0 of 0-3 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> ixpide0:0:0: recal drive fault
> wd0d: device fault reading fsbn 0 of 0-3 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> ixpide0:0:0: recal drive fault
> wd0d: device fault reading fsbn 0 of 0-3 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> ...
> wd0: dos partition I/O error
> ixpide0:0:0: recal drive fault
> wd0d: device fault reading fsbn 0 of 0-3 (wd0 bn 0; cn 0 tn 0 sn 0), retrying

Do you also get these messages when typing e.g. fdisk wd0 with your
working kernel ?

--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
    NetBSD: 26 ans d'experience feront toujours la difference
--