Why use 60 sec on da0 during boot?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Why use 60 sec on da0 during boot?

Ingeborg Hellemo
Fresh new ProLiant dl380 2 CPU/dual core
Fresh new FreeBSD 6.0-RELEASE  


During boot I arrive at

da0 at ciss0 bus 0 target 0 lun 0
da0: <COMPAQ RAID 1  VOLUME OK> Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)

then nothing happens for about 60 seconds and then everything proceedes as
usual (starting daemons, mounting NFS-disks etc.)

During the period the lights are on on both disks and floppy-station.

I had some problems during install with the partitioning of the disk. When i
chose to use the rest of the disk for the last partition I got an error
message along the lines of "Disk too large" (don't remember the exact
wording). I got around this by pressing 'A' and letting the installer choose
the partition sizes.

Is this a problem with the disk layout? Where shall I begin the debugging?


Full dmesg.boot:

Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD 6.0-RELEASE #0: Thu Nov  3 09:36:13 UTC 2005
    [hidden email]:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: <HP     00000083>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3400.14-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf43  Stepping = 3
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x649d<SSE3,RSVD2,MON,DS_CPL,EST,CNTX-ID,CX16,<b14>>
  AMD Features=0x20000000<LM>
  Hyperthreading: 2 logical CPUs
real memory  = 2147430400 (2047 MB)
avail memory = 2096619520 (1999 MB)
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
ioapic2 <Version 2.0> irqs 48-71 on motherboard
ioapic3 <Version 2.0> irqs 72-95 on motherboard
ioapic4 <Version 2.0> irqs 96-119 on motherboard
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <HP P51> on motherboard
acpi0: Power Button (fixed)
pci_link0: <ACPI PCI Link LNKA> irq 5 on acpi0
pci_link1: <ACPI PCI Link LNKB> irq 5 on acpi0
pci_link2: <ACPI PCI Link LNKC> irq 5 on acpi0
pci_link3: <ACPI PCI Link LNKD> irq 5 on acpi0
pci_link4: <ACPI PCI Link LNKE> irq 0 on acpi0
pci_link5: <ACPI PCI Link LNKF> irq 5 on acpi0
pci_link6: <ACPI PCI Link LNKG> irq 5 on acpi0
pci_link7: <ACPI PCI Link LNKH> irq 5 on acpi0
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_perf0: <ACPI CPU Frequency Control> on cpu0
pcib0: <ACPI Host-PCI bridge> on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci2: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci2
pci3: <ACPI PCI bus> on pcib2
bge0: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2100> mem
0xfdef0000-0xfdefffff irq 25 at device 1.0 on pci3
miibus0: <MII bus> on bge0
brgphy0: <BCM5704 10/100/1000baseTX PHY> on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX-FDX, auto
bge0: Ethernet address: 00:14:38:bf:dd:6f
bge1: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2100> mem
0xfdee0000-0xfdeeffff irq 26 at device 1.1 on pci3
miibus1: <MII bus> on bge1
brgphy1: <BCM5704 10/100/1000baseTX PHY> on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX-FDX, auto
bge1: Ethernet address: 00:14:38:bf:dd:6e
pcib3: <ACPI PCI-PCI bridge> at device 0.2 on pci2
pci4: <ACPI PCI bus> on pcib3
ciss0: <HP Smart Array 6i> port 0x4000-0x40ff mem 0xfdff0000-0xfdff1fff,0xfdf80
000-0xfdfbffff irq 51 at device 3.0 on pci4
ciss0: [GIANT-LOCKED]
pcib4: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci5: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 0.0 on pci5
pci6: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> at device 0.2 on pci5
pci10: <ACPI PCI bus> on pcib6
uhci0: <Intel 82801EB (ICH5) USB controller USB-A> port 0x2000-0x201f irq 16
at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82801EB (ICH5) USB controller USB-A> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 82801EB (ICH5) USB controller USB-B> port 0x2020-0x203f irq 19
at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <Intel 82801EB (ICH5) USB controller USB-B> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 82801EB (ICH5) USB controller USB-C> port 0x2040-0x205f irq 18
at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <Intel 82801EB (ICH5) USB controller USB-C> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: <Intel 82801EB (ICH5) USB controller USB-D> port 0x2060-0x207f irq 16
at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <Intel 82801EB (ICH5) USB controller USB-D> on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfbef0000-0xfbef03ff irq 23 at
device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <EHCI (generic) USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
pcib7: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci1: <ACPI PCI bus> on pcib7
pci1: <display, VGA> at device 3.0 (no driver attached)
pci1: <base peripheral> at device 4.0 (no driver attached)
pci1: <base peripheral> at device 4.2 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH5 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x3
76,0x500-0x50f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
acpi_tz0: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
sio0: <Standard PC COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
fdc0: <floppy drive controller (FDE)> port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xee000-0xefff
f on isa0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 3400138193 Hz quality 800
Timecounters tick every 1.000 msec
atapci0: <Intel ICH5 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x3
76,0x500-0x50f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
acpi_tz0: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
sio0: <Standard PC COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
fdc0: <floppy drive controller (FDE)> port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xee000-0xefff
f on isa0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 3400138193 Hz quality 800
Timecounters tick every 1.000 msec
acd0: DVDROM <DV-28E-N/C.6B> at ata0-master UDMA33
da0 at ciss0 bus 0 target 0 lun 0
da0: <COMPAQ RAID 1  VOLUME OK> Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)
Trying to mount root from ufs:/dev/da0s1a



--Ingeborg
--
Ingeborg Østrem Hellemo  --  [hidden email]  (Univ. of Tromsø, Norway)


_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Why use 60 sec on da0 during boot?

Lukas Ertl-2
On 11/9/05, Ingeborg Hellemo <[hidden email]> wrote:

> Fresh new ProLiant dl380 2 CPU/dual core
> Fresh new FreeBSD 6.0-RELEASE
>
>
> During boot I arrive at
>
> da0 at ciss0 bus 0 target 0 lun 0
> da0: <COMPAQ RAID 1  VOLUME OK> Fixed Direct Access SCSI-0 device
> da0: 135.168MB/s transfers
> da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)
>
> then nothing happens for about 60 seconds and then everything proceedes as
> usual (starting daemons, mounting NFS-disks etc.)

I see this behaviour on my DL380s, too.  I don't have a fix, but a
workaround: disable the floppy drive in the BIOS.

cheers,
le
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Why use 60 sec on da0 during boot?

Jim Pingle
Lukas Ertl wrote:

> On 11/9/05, Ingeborg Hellemo <[hidden email]> wrote:
>
>>Fresh new ProLiant dl380 2 CPU/dual core
>>Fresh new FreeBSD 6.0-RELEASE
>>
>>
>>During boot I arrive at
>>
>>da0 at ciss0 bus 0 target 0 lun 0
>>da0: <COMPAQ RAID 1  VOLUME OK> Fixed Direct Access SCSI-0 device
>>da0: 135.168MB/s transfers
>>da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)
>>
>>then nothing happens for about 60 seconds and then everything proceedes as
>>usual (starting daemons, mounting NFS-disks etc.)
>
>
> I see this behaviour on my DL380s, too.  I don't have a fix, but a
> workaround: disable the floppy drive in the BIOS.

I also see this behavior, though I see it on a few systems which are all
Dual CPU PIII 800MHz. They each have different SCSI or RAID controllers (one
has an amr card, one has an mlx controller, and one I believe just had an
ahc controller. The motherboards all have Intel serverworks chipsets.

These are all fresh installs of FreeBSD 6.0 (and updated to -STABLE). It
happens with GENERIC and with a lightly modified custom kernel (remove
unused cpu types, add smp)

In each case, during this pause the floppy light is on solid, so I'm not
sure it has anything to do with the SCSI controller(s).

For me, it goes like so:

...
Waiting 5 seconds for SCSI devices to settle
amrd0: <LSILogic MegaRAID logical drive> on amr0
amrd0: 17364MB (35561472 sectors) RAID 0 (optimal)
amrd1: <LSILogic MegaRAID logical drive> on amr0
amrd1: 34728MB (71122944 sectors) RAID 0 (optimal)
sa0 at ahc0 bus 0 target 0 lun 0
sa0: <SONY SDX-500C 0107> Removable Sequential Access SCSI-2 device
sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
SMP: AP CPU #1 Launched!
[long pause]
Trying to mount root from ufs:/dev/amrd0s1a
...

I haven't tried to time the pause, but I believe it was a different duration
on each system. (Particularly long with a higher end Mylex card)

For me it's just a minor annoyance, everything works fine otherwise.

If anyone wants more information I can try to gather some next week when I'm
back in the office.

Jim
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Why use 60 sec on da0 during boot?

Lukas Ertl-2
On 11/19/05, Jim Pingle <[hidden email]> wrote:

> Lukas Ertl wrote:
> > On 11/9/05, Ingeborg Hellemo <[hidden email]> wrote:
> >
> >>Fresh new ProLiant dl380 2 CPU/dual core
> >>Fresh new FreeBSD 6.0-RELEASE
> >>
> >>
> >>During boot I arrive at
> >>
> >>da0 at ciss0 bus 0 target 0 lun 0
> >>da0: <COMPAQ RAID 1  VOLUME OK> Fixed Direct Access SCSI-0 device
> >>da0: 135.168MB/s transfers
> >>da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C)
> >>
> >>then nothing happens for about 60 seconds and then everything proceedes as
> >>usual (starting daemons, mounting NFS-disks etc.)
> >
> >
> > I see this behaviour on my DL380s, too.  I don't have a fix, but a
> > workaround: disable the floppy drive in the BIOS.
>
> I also see this behavior, though I see it on a few systems which are all
> Dual CPU PIII 800MHz. They each have different SCSI or RAID controllers (one
> has an amr card, one has an mlx controller, and one I believe just had an
> ahc controller. The motherboards all have Intel serverworks chipsets.
>
> These are all fresh installs of FreeBSD 6.0 (and updated to -STABLE). It
> happens with GENERIC and with a lightly modified custom kernel (remove
> unused cpu types, add smp)
>
> In each case, during this pause the floppy light is on solid, so I'm not
> sure it has anything to do with the SCSI controller(s).

It has nothing to do with the SCSI controller, it's all about the
floppy drive.  It seems like the fdc driver doesn't recognize that
there's no disk in the drive and tries to access it on and on and on.
As I said, disable the floppy drive in the BIOS (or even put a floppy
into the drive), then the boot process goes on as usual.

cheers,
le
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Why use 60 sec on da0 during boot?

Antony Mawer-6
On 20/11/2005 7:32 AM, Lukas Ertl wrote:
> It has nothing to do with the SCSI controller, it's all about the
> floppy drive.  It seems like the fdc driver doesn't recognize that
> there's no disk in the drive and tries to access it on and on and on.
> As I said, disable the floppy drive in the BIOS (or even put a floppy
> into the drive), then the boot process goes on as usual.

Indeed - I saw this just the other day on a purely Serial ATA/IDE
system. Just after detecting the IDE disks, the system paused for about
60 seconds, with the floppy drive light coming on. After ~60sec it then
continued without a problem.

Slightly alarming, but apparently harmless...

-Antony

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"