From nobody@FreeBSD.org  Tue Feb  1 10:55:24 2011
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2FC1B1065672
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  1 Feb 2011 10:55:24 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 1D6E48FC23
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  1 Feb 2011 10:55:24 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p11AtNil011066
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 1 Feb 2011 10:55:23 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id p11AtN6b011065;
	Tue, 1 Feb 2011 10:55:23 GMT
	(envelope-from nobody)
Message-Id: <201102011055.p11AtN6b011065@red.freebsd.org>
Date: Tue, 1 Feb 2011 10:55:23 GMT
From: Robert Nagy <robert@bsd.hu>
To: freebsd-gnats-submit@FreeBSD.org
Subject: run_interrupt_driven_hooks: still waiting after 60-300 seconds for xpt_config
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         154432
>Category:       kern
>Synopsis:       [xpt] run_interrupt_driven_hooks: still waiting after 60-300 seconds for xpt_config
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    sbruno
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 01 11:00:17 UTC 2011
>Closed-Date:    Mon Apr 29 05:56:08 UTC 2013
>Last-Modified:  Mon Apr 29 05:56:08 UTC 2013
>Originator:     Robert Nagy
>Release:        8.2-PRERELEASE
>Organization:
>Environment:
FreeBSD siva.hu 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #4: Tue Feb  1 10:49:21 CET 2011     root@siva.hu:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
There is a 900 second wait loop in the kernel while booting.

run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config

--

Copyright (c) 1992-2011 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.2-PRERELEASE #4: Tue Feb  1 10:49:21 CET 2011
    root@siva.hu:/usr/obj/usr/src/sys/GENERIC amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU           E5410  @ 2.33GHz (2341.48-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x10676  Family = 6  Model = 17  Stepping = 6
  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=0xce3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
real memory  = 17179869184 (16384 MB)
avail memory = 16534269952 (15768 MB)
ACPI APIC Table: <INTEL  S5000VSA>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 2 package(s) x 4 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
lapic0: Forcing LINT1 to edge trigger
kbd1 at kbdmux0
acpi0: <INTEL S5000VSA> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
acpi_button0: <Sleep Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xca2,0xca3,0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci2
pci3: <ACPI PCI bus> on pcib3
isp0: <Qlogic ISP 2532 PCI FC-AL Adapter> port 0x4400-0x44ff mem 0xf8a00000-0xf8a03fff irq 16 at device 0.0 on pci3
isp0: [ITHREAD]
isp1: <Qlogic ISP 2532 PCI FC-AL Adapter> port 0x4000-0x40ff mem 0xf8a04000-0xf8a07fff irq 17 at device 0.1 on pci3
isp1: [ITHREAD]
pcib4: <ACPI PCI-PCI bridge> irq 17 at device 1.0 on pci2
pci4: <ACPI PCI bus> on pcib4
mfi0: <LSI MegaSAS 1078> port 0x3000-0x30ff mem 0xf8900000-0xf893ffff,0xf8940000-0xf897ffff irq 17 at device 0.0 on pci4
mfi0: Megaraid SAS driver Ver 3.00 
mfi0: 6722 (349874230s/0x0020/info) - Shutdown command received from host
mfi0: 6723 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1010/8086)
mfi0: 6724 (boot + 3s/0x0020/info) - Firmware version 1.10.02-0180
mfi0: 6725 (boot + 4s/0x0008/info) - Battery temperature is normal
mfi0: 6726 (boot + 4s/0x0008/info) - Battery Present
mfi0: 6727 (boot + 10s/0x0002/info) - Inserted: PD 08(e0/s8)
mfi0: 6728 (boot + 10s/0x0002/info) - Inserted: PD 08(e0/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=0a241a02538e6c3d,0000000000000000
mfi0: 6729 (boot + 10s/0x0002/info) - Inserted: PD 09(e0/s9)
mfi0: 6730 (boot + 10s/0x0002/info) - Inserted: PD 09(e0/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=0a241a0253747235,0000000000000000
mfi0: 6731 (boot + 10s/0x0002/info) - Inserted: PD 0a(e0/s10)
mfi0: 6732 (boot + 10s/0x0002/info) - Inserted: PD 0a(e0/s10) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=0a241a0253736839,0000000000000000
mfi0: 6733 (boot + 10s/0x0042/info) - Global Hot Spare created on PD 08(e0/s8) (global)
mfi0: 6734 (boot + 10s/0x0002/info) - State change on PD 08(e0/s8) from UNCONFIGURED_GOOD(0) to HOT SPARE(2)
mfi0: 6735 (349874276s/0x0020/info) - Time established as 02/01/11 11:17:56; (42 seconds since power on)
mfi0: 6736 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1010/8086)
mfi0: 6737 (boot + 3s/0x0020/info) - Firmware version 1.10.02-0180
mfi0: 6738 (boot + 4s/0x0008/info) - Battery temperature is normal
mfi0: 6739 (boot + 4s/0x0008/info) - Battery Present
mfi0: 6740 (boot + 10s/0x0002/info) - Inserted: PD 08(e0/s8)
mfi0: 6741 (boot + 10s/0x0002/info) - Inserted: PD 08(e0/s8) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=0a241a02538e6c3d,0000000000000000
mfi0: 6742 (boot + 10s/0x0002/info) - Inserted: PD 09(e0/s9)
mfi0: 6743 (boot + 10s/0x0002/info) - Inserted: PD 09(e0/s9) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=0a241a0253747235,0000000000000000
mfi0: 6744 (boot + 10s/0x0002/info) - Inserted: PD 0a(e0/s10)
mfi0: 6745 (boot + 10s/0x0002/info) - Inserted: PD 0a(e0/s10) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=0a241a0253736839,0000000000000000
mfi0: 6746 (boot + 10s/0x0042/info) - Global Hot Spare created on PD 08(e0/s8) (global)
mfi0: 6747 (boot + 10s/0x0002/info) - State change on PD 08(e0/s8) from UNCONFIGURED_GOOD(0) to HOT SPARE(2)
mfi0: [ITHREAD]
pcib5: <ACPI PCI-PCI bridge> irq 18 at device 2.0 on pci2
pci5: <ACPI PCI bus> on pcib5
em0: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x2020-0x203f mem 0xf8820000-0xf883ffff,0xf8400000-0xf87fffff irq 18 at device 0.0 on pci5
em0: Using an MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:15:17:52:dd:48
em1: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x2000-0x201f mem 0xf8800000-0xf881ffff,0xf8000000-0xf83fffff irq 19 at device 0.1 on pci5
em1: Using an MSI interrupt
em1: [FILTER]
em1: Ethernet address: 00:15:17:52:dd:49
pcib6: <ACPI PCI-PCI bridge> at device 0.3 on pci1
pci6: <ACPI PCI bus> on pcib6
pcib7: <PCI-PCI bridge> at device 3.0 on pci0
pci7: <PCI bus> on pcib7
pci0: <base peripheral> at device 8.0 (no driver attached)
pcib8: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci8: <ACPI PCI bus> on pcib8
uhci0: <Intel 631XESB/632XESB/3100 USB controller USB-1> port 0x5080-0x509f irq 23 at device 29.0 on pci0
uhci0: [ITHREAD]
uhci0: LegSup = 0x2f00
usbus0: <Intel 631XESB/632XESB/3100 USB controller USB-1> on uhci0
uhci1: <Intel 631XESB/632XESB/3100 USB controller USB-2> port 0x5060-0x507f irq 22 at device 29.1 on pci0
uhci1: [ITHREAD]
uhci1: LegSup = 0x2f00
usbus1: <Intel 631XESB/632XESB/3100 USB controller USB-2> on uhci1
uhci2: <Intel 631XESB/632XESB/3100 USB controller USB-3> port 0x5040-0x505f irq 23 at device 29.2 on pci0
uhci2: [ITHREAD]
uhci2: LegSup = 0x2f00
usbus2: <Intel 631XESB/632XESB/3100 USB controller USB-3> on uhci2
uhci3: <Intel 631XESB/632XESB/3100 USB controller USB-4> port 0x5020-0x503f irq 22 at device 29.3 on pci0
uhci3: [ITHREAD]
uhci3: LegSup = 0x2f00
usbus3: <Intel 631XESB/632XESB/3100 USB controller USB-4> on uhci3
ehci0: <Intel 63XXESB USB 2.0 controller> mem 0xf8d00400-0xf8d007ff irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus4: EHCI version 1.0
usbus4: <Intel 63XXESB USB 2.0 controller> on ehci0
pcib9: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci9: <ACPI PCI bus> on pcib9
vgapci0: <VGA-compatible display> port 0x1000-0x10ff mem 0xf0000000-0xf7ffffff,0xf8c00000-0xf8c0ffff irq 17 at device 12.0 on pci9
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel 63XXESB2 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x50b0-0x50bf irq 20 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
atapci1: <Intel 63XXESB2 SATA300 controller> port 0x50c8-0x50cf,0x50e4-0x50e7,0x50c0-0x50c7,0x50e0-0x50e3,0x50a0-0x50af mem 0xf8d00000-0xf8d003ff irq 20 at device 31.2 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
atrtc0: <AT realtime clock> port 0x70-0x71,0x74-0x77 irq 8 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]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart1: [FILTER]
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc8fff,0xd1000-0xd1fff,0xd2000-0xd2fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ppc0: cannot reserve I/O port range
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
est4: <Enhanced SpeedStep Frequency Control> on cpu4
p4tcc4: <CPU Frequency Thermal Control> on cpu4
est5: <Enhanced SpeedStep Frequency Control> on cpu5
p4tcc5: <CPU Frequency Thermal Control> on cpu5
est6: <Enhanced SpeedStep Frequency Control> on cpu6
p4tcc6: <CPU Frequency Thermal Control> on cpu6
est7: <Enhanced SpeedStep Frequency Control> on cpu7
p4tcc7: <CPU Frequency Thermal Control> on cpu7
RTC BIOS diagnostic error 5<invalid_time>
Timecounters tick every 1.000 msec
mfi0: 6748 (349874359s/0x0020/info) - Time established as 02/01/11 11:19:19; (42 seconds since power on)
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen3.1: <Intel> at usbus3
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen4.1: <Intel> at usbus4
uhub4: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus4
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
mfid0: <MFI Logical Disk> on mfi0
mfid0: 237464MB (486326272 sectors) RAID volume '' is optimal
uhub4: 8 ports with 8 removable, self powered
ugen0.2: <Peppercon AG> at usbus0
umass0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x0000
ugen2.2: <TEAC> at usbus2
umass1: <TEAC TEAC FD-05PUW, class 0/0, rev 2.00/0.00, addr 2> on usbus2
umass1:  UFI over CBI; quirks = 0x0000
umass0:2:0:-1: Attached to scbus2
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI status: Check Condition
(probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
umass1:3:1:-1: Attached to scbus3
(probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI status: Check Condition
(probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
(probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI status: Check Condition
(probe0:umass-sim1:1:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config
ses0 at isp0 bus 0 scbus0 target 0 lun 5
ses0: <IFT S24F-R1840-4 373O> Fixed Enclosure Services SCSI-4 device 
ses0: 400.000MB/s transfers WWNN 0x200000d02307bed9 WWPN 0x210000d02307bed9 PortID 0x10025
ses0: Command Queueing enabled
ses0: SCSI-3 SES Device
ses1 at isp1 bus 0 scbus1 target 0 lun 0
ses1: <IFT S24F-R1840-4 373O> Fixed Enclosure Services SCSI-4 device 
ses1: 400.000MB/s transfers WWNN 0x200000d02317bed9 WWPN 0x210000d02317bed9 PortID 0x10023
ses1: Command Queueing enabled
ses1: SCSI-3 SES Device
da0 at isp0 bus 0 scbus0 target 0 lun 0
da0: <IFT S24F-R1840-4 373O> Fixed Direct Access SCSI-4 device 
da0: 400.000MB/s transfers WWNN 0x200000d02307bed9 WWPN 0x210000d02307bed9 PortID 0x10025
da0: Command Queueing enabled
da0: 953609MB (1952991232 512 byte sectors: 255H 63S/T 121568C)
da1 at isp0 bus 0 scbus0 target 0 lun 1
da1: <IFT S24F-R1840-4 373O> Fixed Direct Access SCSI-4 device 
da1: 400.000MB/s transfers WWNN 0x200000d02307bed9 WWPN 0x210000d02307bed9 PortID 0x10025
da1: Command Queueing enabled
da1: 15360MB (31457280 512 byte sectors: 255H 63S/T 1958C)
da2 at isp0 bus 0 scbus0 target 0 lun 2
da2: <IFT S24F-R1840-4 373O> Fixed Direct Access SCSI-4 device 
da2: 400.000MB/s transfers WWNN 0x200000d02307bed9 WWPN 0x210000d02307bed9 PortID 0x10025
da2: Command Queueing enabled
da2: 15360MB (31457280 512 byte sectors: 255H 63S/T 1958C)
da3 at isp0 bus 0 scbus0 target 0 lun 3
da3: <IFT S24F-R1840-4 373O> Fixed Direct Access SCSI-4 device 
da3: 400.000MB/s transfers WWNN 0x200000d02307bed9 WWPN 0x210000d02307bed9 PortID 0x10025
da3: Command Queueing enabled
da3: 199135MB (407828480 512 byte sectors: 255H 63S/T 25386C)
da4 at isp0 bus 0 scbus0 target 0 lun 4
da4: <IFT S24F-R1840-4 373O> Fixed Direct Access SCSI-4 device 
da4: 400.000MB/s transfers WWNN 0x200000d02307bed9 WWPN 0x210000d02307bed9 PortID 0x10025
da4: Command Queueing enabled
da4: 199136MB (407830528 512 byte sectors: 255H 63S/T 25386C)
lapic7: Forcing LINT1 to edge trigger
cd0 at umass-sim0 bus 0 scbus2 target 0 lun 0
cd0: <PepperC Virtual Disc 1 0.01> Removable CD-ROM SCSI-3 device 
cd0: 1.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not presentSMP: AP CPU #7 Launched!
lapic5: Forcing LINT1 to edge trigger
SMP: AP CPU #5 Launched!
lapic6: Forcing LINT1 to edge trigger
SMP: AP CPU #6 Launched!
lapic4: Forcing LINT1 to edge trigger
SMP: AP CPU #4 Launched!
lapic1: Forcing LINT1 to edge trigger
SMP: AP CPU #1 Launched!
lapic3: Forcing LINT1 to edge trigger
SMP: AP CPU #3 Launched!
lapic2: Forcing LINT1 to edge trigger
SMP: AP CPU #2 Launched!
da5 at umass-sim1 bus 1 scbus3 target 0 lun 0
da5: <TEAC FD-05PUW 3000> Removable Direct Access SCSI-0 device 
da5: 1.000MB/s transfers
da5: Attempt to query device size failed: NOT READY, Medium not present
GEOM: da0: partition 3 does not start on a track boundary.
GEOM: da0: partition 3 does not end on a track boundary.
GEOM: da0: partition 2 does not start on a track boundary.
GEOM: da0: partition 2 does not end on a track boundary.
GEOM: da0: partition 1 does not start on a track boundary.
GEOM: da0: partition 1 does not end on a track boundary.
Trying to mount root from ufs:/dev/mfid0s1a
em0: link state changed to UP

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi 
Responsible-Changed-By: brucec 
Responsible-Changed-When: Thu Feb 17 09:37:50 UTC 2011 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154432 

From: Bruce Cran <bruce@cran.org.uk>
To: bug-followup@FreeBSD.org, robert@bsd.hu
Cc:  
Subject: Re: kern/154432: [xpt] run_interrupt_driven_hooks: still waiting
 after 60-300 seconds for xpt_config
Date: Thu, 17 Feb 2011 09:39:38 +0000

 This also happens when using ada(4) with Xen on FreeBSD 8.2, but it gives up
 after 60 seconds:
 
 ACPI APIC Table: <Xen HVM>
 ...
 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config ada0 at ata0 bus 0 scbus0 target 0 lun 0
 ada0: <QEMU HARDDISK 0.9.1> ATA-7 device
 ada0: 16.700MB/s transfers (WDMA2, PIO 8192bytes)
 ada0: 10752MB (22020096 512 byte sectors: 16H 63S/T 16383C)
 
 -- 
 Bruce Cran

From: David <monkeyman_stones@comcast.net>
To: bug-followup@FreeBSD.org, robert@bsd.hu
Cc:  
Subject: Re: kern/154432: [xpt] run_interrupt_driven_hooks: still waiting
	after 60-300 seconds for xpt_config
Date: Fri, 30 Sep 2011 19:20:54 -0400

 --=-ZVLAFB154UrOwKLn5r6o
 Content-Type: text/plain; charset=utf-8
 Content-ID: <1317424853.4260.27.camel@Nokia-N900>
 Content-Transfer-Encoding: 7bit
 
 Same result seen in HP HDX-18t Notebook computer during installition attempt of PC-BSD (containing FreeBSD).
 YouTube video of entire installation attempt for this model can be seen here in 1080P: http://www.youtube.com/watch?v=Jn2WAc8b_GE .
 Hardware for this computer is as follows:
 Quanta 3610 Motherboard
 Bios - HP branded
 8GB DDR2 dual channel @ 800MHz (6/6/6/18) 1.8V
 Intel Penryn Core 2 Duo P8600 2.4GHz
 PCI-Express graphics interface
 NVidia Geforce 9600M GT
 Synaptics PS/2 Port Touchpad
 Generic Plug and Play monitor (1920x1080p)
 Realtek RTL8168C(P) NIC (PCI-E)
 Intel WIFI Link 5100 AGN
 Sony BlueRay Comp drive
 Firewire Port
 Other assorted basics (if it makes a difference feel free to ask me - I'm happy to provide any info you need).
 
 David
 Monkeyman_Stones@Comcast.net

 --=-ZVLAFB154UrOwKLn5r6o--
 

From: "Hotmail Monkeyman" <monkeyman_stones@hotmail.com>
To: <bug-followup@FreeBSD.org>,
	<robert@bsd.hu>
Cc:  
Subject: Re: kern/154432: [xpt] run_interrupt_driven_hooks: still waiting after 60-300 seconds for xpt_config
Date: Tue, 4 Oct 2011 19:29:40 -0400

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_0044_01CC82CB.F6423D90
 Content-Type: text/plain;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 I failed to mention that this problem was experienced in the HP HDX18t =
 notebook during the installation attempts of both freeBSD/PC-BSD 8.2 and =
 freeBSD PC-BSD 9.0 Beta 2 in my previous report. The video is an install =
 of PC-BSD/freeBSD 9.0 Beta2 64-bit.
 
 David
 Monkeyman_Stones@Comcast.net

 ------=_NextPart_000_0044_01CC82CB.F6423D90--
 

From: Miljan Vujosevic <info@miljanvujosevic.com>
To: bug-followup@FreeBSD.org, robert@bsd.hu
Cc:  
Subject: Re: kern/154432: [xpt] run_interrupt_driven_hooks: still waiting
 after 60-300 seconds for xpt_config
Date: Mon, 14 Nov 2011 15:33:14 +0000

 --14dae9341263d247cc04b1b39638
 Content-Type: text/plain; charset=windows-1252
 Content-Transfer-Encoding: quoted-printable
 
 I have the same problem with FreeBSD version 8.2 and 9.0RC. In version of
 8.2 i got freeze after installation but in 9 I have error during
 installation.
 
 Hardware [Toshiba Qosmio X300-14v]:
 
    - Intel=AE Centrino=AE 2 Processor
 Technology<http://syndication.intel.com/DistributeModule.aspx?ppc_cid=3DIIP=
 _02105075701&cc=3DCI>featuring
 Intel=AE
    Core=992 Duo processor<http://syndication.intel.com/DistributeModule.asp=
 x?ppc_cid=3DIIP_02105066901&cc=3DCI>P8700,
 Intel=AE PM45 Express chipset and Intel=AE WiFi Link 5100
     clock speed : 2.53 GHz
     Front Side Bus : 1066 MHz
     2nd level cache : 3 MB
    - NVIDIA=AE GeForce=AE 9700M GTS supporting TurboCache=99 technology
     memory amount : 512 MB dedicated VRAM (up to 1,791 MB total available
    graphics memory using TurboCache=99 technology with 3 GB system memory)
     memory type : GDDR3 (800 MHz) Video RAM (resp. Video RAM and system
    memory combined)
     connected bus : 16x PCI Express
    - Other: 5 in 1 Bridge Media Slot, Vista Remote Control1 =D7 DC-in
    - webcam 1.3
    -  1 =D7 RJ-11
    - 1 =D7 RJ-45
    - 1 =D7 i.LINK=AE (IEEE 1394)
    - 1 =D7 external microphone
    - 1 =D7 external monitor
    - 1 =D7 headphone (stereo)
    - 1 =D7 line-in shared with microphone socket
    - 1 =D7 S/PDIF-out (optical) shared with headphone socket
    - 1 =D7 integrated 1.3 Megapixels Web Camera with built-in microphone
    - 1 =D7 HDMI-CEC (REGZA-Link) supporting 1080p signal format
    - 1 (shared with one USB port) =D7 eSATA
    - 1 =D7 line-out shared with headphone socket
    - 1 =D7 5-in-1 Bridge Media slot (supports SD=99 Cards up to 16 GB, Memo=
 ry
    Stick=AE up to 256 MB, Memory Stick Pro=99 up to 4 GB, MultiMedia Card=
 =99 up to 1
    GB and xD-Picture Card=99 up to 2 GB)
    - 4 (Left 2, Right 2) =D7 USB 2.0 (supporting USB Sleep-and-Charge)
    - 1 =D7 DC-in
 
 --14dae9341263d247cc04b1b39638--

From: Jason Wolfe <nitroboost@gmail.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/154432: [xpt] run_interrupt_driven_hooks: still waiting
 after 60-300 seconds for xpt_config
Date: Mon, 14 Nov 2011 12:36:37 -0700

 --f46d044468d3369bc304b1b6fd26
 Content-Type: text/plain; charset=ISO-8859-1
 
 This is happening to me also on a Supermicro X8DTT-H chasis with an LSI2008
 SAS2 controller and 12 drives on 8.2-RELEASE-p4 with the mps driver from
 STABLE.
 
 mps0@pci0:4:0:0:        class=0x010700 card=0x040015d9 chip=0x00721000
 rev=0x02 hdr=0x00
     vendor     = 'LSI Logic (Was: Symbios Logic, NCR)'
     class      = mass storage
     subclass   = SAS
 
 Though the dmesg output is indentical, my problem is a bit different as the
 300 second timeout passes, but it still in some cases takes the server 24+
 _hours_ to finally continue booting.  It hangs after the 300 second message
 until the time it manages to continue booting, and then all messages appear
 as normal.  The cause of this is surely drives stuck in a transient state
 that makes them still look alive to the kernel.  When the drive is popped
 out the server boots immediately.  300 seconds to wait for a drive that you
 think might be alive does seem a bit high, but I would even be happy if
 even that was being honored in my case.  This is an issue across a large
 pool of servers and I have seen the behavior on ~20 different machines from
 different batches of chasis and drives in unique locations.
 
 --f46d044468d3369bc304b1b6fd26--

From: Jason Wolfe <nitroboost@gmail.com>
To: bug-followup@FreeBSD.org, robert@bsd.hu
Cc:  
Subject: Re: kern/154432: [xpt] run_interrupt_driven_hooks: still waiting
 after 60-300 seconds for xpt_config
Date: Thu, 19 Apr 2012 18:33:18 -0700

 Just wanted to make sure this one didn't slip through the cracks, as
 it's still happening to quite a few boxes on my end.  If it would help
 I'm happy to supply to access to a machine that exhibits the issue.
 
 Jason
Responsible-Changed-From-To: freebsd-scsi->sbruno-scsi 
Responsible-Changed-By: sbruno 
Responsible-Changed-When: Thu Apr 11 17:25:59 UTC 2013 
Responsible-Changed-Why:  
Take this pr for monitoring. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154432 
Responsible-Changed-From-To: sbruno-scsi->sbruno 
Responsible-Changed-By: sbruno 
Responsible-Changed-When: Thu Apr 11 17:26:29 UTC 2013 
Responsible-Changed-Why:  
well, actually assign it to myself 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154432 

From: Sean Bruno <seanwbruno@gmail.com>
To: bug-followup@FreeBSD.org, robert@bsd.hu
Cc:  
Subject: Re: kern/154432: [xpt] run_interrupt_driven_hooks: still waiting
 after 60-300 seconds for xpt_config
Date: Thu, 11 Apr 2013 10:25:25 -0700

 --=-0oTAsBKmB9GrOizTfplT
 Content-Type: text/plain; charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 I have tested mps(4) mpt(4) and mfi(4) and can't seem to make this
 happen on any release of stable/9
 
 Is this still happening to you folks? =20
 
 Sean
 
 --=-0oTAsBKmB9GrOizTfplT
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: This is a digitally signed message part
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.13 (FreeBSD)
 
 iQEcBAABAgAGBQJRZvH9AAoJEBkJRdwI6BaHh8MH/jOzhlHKYjgHEdeuHL212ixg
 Jg0/Ohh/ZRMkzCpoZtrtuBNyRTp4iIDzvQgv3De6Hn3YSk9bGcGRJx8r+lSy37cD
 OQq26f9ykaNG7fYNtWodptIUUfJY2ygSmBtcFBhB9hHJmCKUnryKLflVX91xlsd1
 FF/HbnP8ryqTKXIFAfiRHFYQy0Iq8KNjnvN3esit8+hfACrBkgs3nlIp4umJu9oH
 Az43aTHD3dfGjNPL9ia2A84bEX8pGwyI+5/Mj6up7Zh3b+zT/iep1jSXbYzmxIqo
 7lZEvKZUN2kNuvXE7tfyiJ5lfzuZxxMGxg/upZpChWlXyeeY9H0jljzVxWIpBuo=
 =ylgE
 -----END PGP SIGNATURE-----
 
 --=-0oTAsBKmB9GrOizTfplT--
 
State-Changed-From-To: open->feedback 
State-Changed-By: sbruno 
State-Changed-When: Fri Apr 12 22:14:03 UTC 2013 
State-Changed-Why:  
Feedback requested 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154432 
State-Changed-From-To: feedback->closed 
State-Changed-By: sbruno 
State-Changed-When: Mon Apr 29 05:54:52 UTC 2013 
State-Changed-Why:  
This doesn't appear to be happening for Xen nor real adapters. 

If this is still an issue, lets discuss it further on freebsd-scsi. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=154432 
>Unformatted:
