Bug 30860
| Summary: | [hang] While install after "Mounting root from ufs:/dev/md0c" hang's and wont continiue | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Thomas Gallaway <dubstar911> |
| Component: | i386 | Assignee: | Remko Lodder <remko> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Thomas Gallaway
2001-09-27 06:00:01 UTC
Similar problem solved on P-233MMX/256 RAM/6.4+30 GB HDD/Spacewalker/Shuttle/HOT-569A-Intel 430TX chipset! 4.4-RELEASE installation requires enabling of 'Assign IRQ for USB' option in AWARD BIOS. 4.3-RELEASE doesn't require it. State Changed From-To: open->feedback Hi! I have an phoenix bios and no option to assign ICQ to an USB ... i have no usb options in my bios. It still hangs.. thanx From: "Lyubomir Russev" <Lyubomir.Russev@equant-bg.com> To: <freebsd-gnats-submit@FreeBSD.org>, <dubstar911@lycos.de> Cc: Subject: Re: i386/30860: While install after "Mounting root from ufs:/dev/md0c" hang's and wont continiue Date: Mon, 5 Nov 2001 21:44:30 +0200 Similar problem solved on P-233MMX/256 RAM/6.4+30 GB HDD/Spacewalker/Shuttle/HOT-569A-Intel 430TX chipset! 4.4-RELEASE installation requires enabling of 'Assign IRQ for USB' option in AWARD BIOS. 4.3-RELEASE doesn't require it. State-Changed-From-To: open->feedback State-Changed-By: dwmalone State-Changed-When: Mon Nov 5 11:56:55 PST 2001 State-Changed-Why: I have a Pentium 166/MMX that hanges at Mounting root from ufs: on 4.4 no matter what I do. Seems that 4.3 works ok. Ok, I changed the bios from: Assign an IRQ to USB: Disabled to Enabled and it booted up. This is annoying, I don't want to Enable this option, would fix it myself but don't know the first place to look, oh well... <shrug>... <sigh>. Why did this PR go to "feedback"? Near as I can tell the originator claims the suggestion didn't solve his original problem. If this PR is now tracking why an IRQ must be assigned for USB, is a costly[1] HW workaround to something that crept into 4.4 considered a solution? Is there a different PR for IRQ/USB issue? I was initially trying to see if this was fixed in 4.5. Thanks, -Jed [1]Costly (adj.): something that wastes an ISA IRQ to no apparent purpose -Murphy's Unabridged Dictionary of Computer Terms. I just downloaded the boot floppies (kern.flp and mfsroot.flp) in the 4.6 release directory. These boot floppies seem to be the same boot floppies as the ones from the 4.4 release (it seems that way, since that is the version string printed out during boot). I am also encountering a problem similar to PR 30902 and PR 30860 where the FreeBSD boot process does not go past the message "Mounting root from ufs:/dev/md0c" Unlike Lyubomir, the BIOS on my laptop is from Phoenix, and does not have the option to "Assign an IRQ to USB". How can I solve this problem with a Phoenix BIOS? My hardware is a Winbook N3: http://www.winbookcorp.com/support/n3/n3_support.html The boot messages that are printed out just before the hang are: eisa0: unknown card DF@0020 (0x10c00020) at slot 1 orm0: <Option ROMs> at iomem 0xc0000-0xcbfff,0xe4000-0xe7fff on isa0 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: <Generic ISA VGA> at port 0x3c0-03df iomem 0xa000-0xbffff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio09 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 9250 sio1: configured irq 3 not in bitmap of probed irqs 0 pppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: <PLIP network interface> on ppbus0 ad0: 19077MB <TOSHIBA MK2018GAP> [38760/16/63] at ata0-master UDMA100 acd0: CD-RW <TOSHIBA DVD-ROM SD-R2002> at ata1-master using PIO4 Moeisa0: unknown card DF@0020 (0x10c00020) at slot 1 orm0: <Option ROMs> at iomem 0xc0000-0xcbfff,0xe4000-0xe7fff on isa0 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: <Generic ISA VGA> at port 0x3c0-03df iomem 0xa000-0xbffff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio09 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 9250 sio1: configured irq 3 not in bitmap of probed irqs 0 pppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: <PLIP network interface> on ppbus0 ad0: 19077MB <TOSHIBA MK2018GAP> [38760/16/63] at ata0-master UDMA100 acd0: CD-RW <TOSHIBA DVD-ROM SD-R2002> at ata1-master using PIO4 Mounting root from ufs:/dev/md0cunting root from ufs:/dev/md0c Hi, Just to follow up on this, I just tried the boot floppy for FreeBSD 5.0-DP1 CURRENT. The problem did NOT occur with this version. I'm not sure about older FreeBSD versions. This looks like a problem in the 4.4-4.6 boot floppies. On Mon, Jul 01, 2002 at 10:46:59PM -0400, Craig Rodrigues wrote: > I just downloaded the boot floppies (kern.flp and mfsroot.flp) in the 4.6 > release directory. These boot floppies seem to be the same boot > floppies as the ones from the 4.4 release (it seems that way, > since that is the version string printed out during boot). > > I am also encountering a problem similar to PR 30902 and PR 30860 where > the FreeBSD boot process does not go past the message > "Mounting root from ufs:/dev/md0c" > > Unlike Lyubomir, the BIOS on my laptop is from Phoenix, and does > not have the option to "Assign an IRQ to USB". How > can I solve this problem with a Phoenix BIOS? > > My hardware is a Winbook N3: > http://www.winbookcorp.com/support/n3/n3_support.html > State Changed From-To: feedback->open Feedback has been requested and received; throw this PR back open. Well, I experience same problem in FreeBSD 4.8 As long as I use the original kernel, the one I created during the installation, everything works fine. But everytime I try to compile a custome kernel and reboot I get stuck at that point: Mounting root from ufs: /dev/ad0s1a State Changed From-To: open->feedback Hi, Does this still occur on a FreeBSD 5.4 or 6.0 version? or perhaps even the beta's ? Responsible Changed From-To: freebsd-i386->remko Grab the PR so that i can keep track of the feedback State Changed From-To: feedback->closed The submitter seem to vanished from the email address he used at the time. I will declare this PR closed till someone can either tell me that it is indeed solved or that someone proves me wrong. |
