Hi all, Any ideas on this one? This machine (one of those ancient VALinux 2U boxes, Intel L440GX+ board, dual PIII) hangs for a very long time between the second processor launching and geom_mirror kicking in. It does always boot, but the hang is more than a minute - just enough to make one nervous when rebooting remotely... Is this just the mirror taking a really long time to initialize, or something more sinister? Here's part of the dmesg with an indication of where it hangs: Waiting 5 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 0 lun 0 da0: <SEAGATE ST173404LWV 4301> Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da1 at ahc0 bus 0 target 1 lun 0 da1: <SEAGATE ST173404LWV 4301> Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) SMP: AP CPU #1 Launched! -->> 1 minute+ <<-- GEOM_MIRROR: Device gm0 created (id=3517779574). GEOM_MIRROR: Device gm0: provider da0 detected. GEOM_MIRROR: Device gm0: provider da1 detected. GEOM_MIRROR: Device gm0: provider da1 activated. GEOM_MIRROR: Device gm0: provider da0 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. Trying to mount root from ufs:/dev/mirror/gm0s1a Any info is appreciated, this is just something I wanted to check out before bringing this into production (secondary ns, mx w/pfspamd). Thanks! Charles
I don't know anything about your problem, but does it give good info if you boot with verbose on? Ronald. On Wed, 18 Jul 2007 03:08:29 +0200, Charles Sprickman <spork@bway.net> wrote:> Hi all, > > Any ideas on this one? This machine (one of those ancient VALinux 2U > boxes, Intel L440GX+ board, dual PIII) hangs for a very long time > between the second processor launching and geom_mirror kicking in. It > does always boot, but the hang is more than a minute - just enough to > make one nervous when rebooting remotely... > > Is this just the mirror taking a really long time to initialize, or > something more sinister? > > Here's part of the dmesg with an indication of where it hangs: > > Waiting 5 seconds for SCSI devices to settle > da0 at ahc0 bus 0 target 0 lun 0 > da0: <SEAGATE ST173404LWV 4301> Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing > Enabled > da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: <SEAGATE ST173404LWV 4301> Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing > Enabled > da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) > SMP: AP CPU #1 Launched! > > -->> 1 minute+ <<-- > > GEOM_MIRROR: Device gm0 created (id=3517779574). > GEOM_MIRROR: Device gm0: provider da0 detected. > GEOM_MIRROR: Device gm0: provider da1 detected. > GEOM_MIRROR: Device gm0: provider da1 activated. > GEOM_MIRROR: Device gm0: provider da0 activated. > GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. > Trying to mount root from ufs:/dev/mirror/gm0s1a > > Any info is appreciated, this is just something I wanted to check out > before bringing this into production (secondary ns, mx w/pfspamd). > > Thanks! > > Charles > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"-- Ronald Klop Amsterdam, The Netherlands
Charles Sprickman wrote:> Any ideas on this one? This machine (one of those ancient VALinux 2U > boxes, Intel L440GX+ board, dual PIII) hangs for a very long time > between the second processor launching and geom_mirror kicking in. It > does always boot, but the hang is more than a minute - just enough to > make one nervous when rebooting remotely... > > Is this just the mirror taking a really long time to initialize, or > something more sinister?[snip]> Any info is appreciated, this is just something I wanted to check out > before bringing this into production (secondary ns, mx w/pfspamd).I've got a bunch of these and they all do it. It seems to be something with the floppy controller. During the hang it's accessing the floppy drive (light is on) and if the floppy is disabled, there is no hang. IIRC if you have a floppy in the drive it also does not hang. That's the short version, anyhow. It's been discussed on the list before so you might check the archives for a better/more complete answer. Jim