Re: Kernel hangs during boot (new GEOM problem)

2002-12-18 Thread walt
walt wrote:


I built world+kernel about an hour ago ( Dec 17 about 23:00 UTC)
and the kernel hangs in the middle of printing phk's GEOM diagnostics:


diagnostics snipped

I noticed some GEOM-related commits in today's cvsup, but unfortunately
they didn't solve this problem.  The kernel still hangs before printing
any of the geom diagnostics for the 2nd IDE drive, and responds only to
the hard reset button.

Meanwhile I'm running with NO_GEOM.

I'd be happy to do any diagnostic tests that might be helpful, but I'm
new to kernel debugging so I'd need some fairly detailed hints first.


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



Kernel hangs during boot (new GEOM problem)

2002-12-17 Thread walt
I built world+kernel about an hour ago ( Dec 17 about 23:00 UTC)
and the kernel hangs in the middle of printing phk's GEOM diagnostics:

ad0: 76319MB ST380021A [155061/16/63] at ata0-master UDMA100
ad2: 42934MB WDC WD450AA-00BAA0 [87233/16/63] at ata1-master UDMA66
acd0: CD-RW R/RW 4x4x24 at ata1-slave PIO4

snip slices 5 to 14 on ad0

MBREXT Slice 15 on ad0s4:
   00 01 c1 ff a5 fe ff ff 3f 00 00 00 bd 08 fa 00  |?...|
[0] f:00 typ:165 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:16386237
   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ||
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0

This is where the latest kernel hangs--between the first and second IDE
disks.  When I boot the previous kernel it continues normally with the 2nd
disk as follows:

MBREXT Slice 5 on ad2s4:
   00 01 c1 ff 0b fe ff ff 3f 00 00 00 de 4d 94 00  |?M..|
[0] f:00 typ:11 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:9719262
   00 00 c1 ff 05 fe ff ff 1d 4e 94 00 bd 86 bb 00  |.N..|
[1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:9719325 l:12289725
MBREXT Slice 6 on ad2s4:
   00 01 c1 ff 83 fe ff ff 3f 00 00 00 7e 86 bb 00  |?...~...|
[0] f:00 typ:131 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:12289662
   00 00 c1 ff 05 fe ff ff da d4 4f 01 86 7c fc 00  |..O..|..|
[1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:22009050 l:16546950
MBREXT Slice 7 on ad2s4:
   00 01 c1 ff 83 fe ff ff 3f 00 00 00 47 7c fc 00  |?...G|..|
[0] f:00 typ:131 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:16546887
   00 00 c1 ff 05 fe ff ff 50 a8 04 03 7e 04 7d 00  |P...~.}.|
[1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:50636880 l:8193150
MBREXT Slice 8 on ad2s4:
   00 01 c1 ff 07 fe ff ff 3f 00 00 00 3f 04 7d 00  |?...?.}.|
[0] f:00 typ:7 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:8193087
   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ||
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
Mounting root from ufs:/dev/ad0s3a
snip

# fdisk ad2
*** Working on device /dev/ad2 ***
parameters extracted from in-core disklabel are:
cylinders=87233 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=87233 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 169 (0xa9),(NetBSD)
start 63, size 7373772 (3600 Meg), flag 0
	beg: cyl 0/ head 1/ sector 1;
	end: cyl 458/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 7373835, size 17607240 (8597 Meg), flag 80 (active)
	beg: cyl 459/ head 0/ sector 1;
	end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
start 24981138, size 4112577 (2008 Meg), flag 0
	beg: cyl 1023/ head 1/ sector 1;
	end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
sysid 15 (0x0f),(Extended DOS (LBA))
start 29093715, size 58830030 (28725 Meg), flag 0
	beg: cyl 1023/ head 0/ sector 1;
	end: cyl 1023/ head 254/ sector 63



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