Urgent problem - 7.x doesn't work on HP servers
Ivan Voras
--------------enigF136B2DD0C3EA6F8A7362CD0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi,
I've again encountered the problem of FreeBSD 7 not wanting to boot on a
HP server. The last time was early in 7.x development on a HP blade
(2xdual-core Opteron), without any solution (reported on this list about
a year ago). This time it's on a ML 350 G5 machine, with a quad-core Xeon=
=2E
The problem is very hard to diagnose - the entire machine locks up
during pci bus/device detection - the kernel debugger doesn't work, the
keyboard lights (PS/2 keyboard) don't work, it's completely frozen.
This is on both i386 and AMD64 kernels.
The machine freezes after detecting pcib6. The working 6.x kernel
detects upto pcib16, and the first device detected after pcib6 is the
CISS controller, so maybe it's the controller driver, but the first
machine (the blade) didn't have CISS controllers.
Any ideas?
--------------enigF136B2DD0C3EA6F8A7362CD0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHuXJgldnAQVacBcgRAnNPAKDS1/juRp0ToElGFQM1fYx8241wOQCeO0Go
pb8gBnptMfbuoEIOXyM6NvA=
=qyeN
-----END PGP SIGNATURE-----
--------------enigF136B2DD0C3EA6F8A7362CD0--
Eygene Ryabinkin
Mon, Feb 18, 2008 at 12:56:10PM +0100, Ivan Voras wrote:
> I've again encountered the problem of FreeBSD 7 not wanting to boot on a
> HP server. The last time was early in 7.x development on a HP blade
> (2xdual-core Opteron), without any solution (reported on this list about
> a year ago). This time it's on a ML 350 G5 machine, with a quad-core Xeon.
>
> The problem is very hard to diagnose - the entire machine locks up
> during pci bus/device detection - the kernel debugger doesn't work, the
> keyboard lights (PS/2 keyboard) don't work, it's completely frozen.
>
> This is on both i386 and AMD64 kernels.
>
> The machine freezes after detecting pcib6. The working 6.x kernel
> detects upto pcib16, and the first device detected after pcib6 is the
> CISS controller, so maybe it's the controller driver, but the first
> machine (the blade) didn't have CISS controllers.
>
> Any ideas?
I have a couple of BL640c and older BL<something>p running 7.0 --
no problems encountered. While this is not the direct answer to
your question, had you tried to update the blade firmware to the
latest versions with Firmware Maintenance CD? Sometimes it helps...
--
Eygene
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Marian Hettwer
On Mon, 18 Feb 2008 12:56:10 +0100, Ivan Voras <ivo...@freebsd.org> wrote:
> Hi,
>
> I've again encountered the problem of FreeBSD 7 not wanting to boot on a
> HP server. The last time was early in 7.x development on a HP blade
> (2xdual-core Opteron), without any solution (reported on this list about
> a year ago). This time it's on a ML 350 G5 machine, with a quad-core
Xeon.
>
I don't have a ML 350 G5 machine at hand, but fwiw I do have a HP BL465c G1
blade. It's a 2 dual core AMD Opteron blade.
Right now it's running FreeBSD 7.0-BETA4. I'm running make world right now
to get a recent RELENG_7
Meanwhile:
[root@marian46-23] <~>uname -a
[12:01:36 on 08-02-18]
FreeBSD marian46-23 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Tue Dec 18 12:07:27 CET
2007 root@marian46-23:/usr/obj/usr/src/sys/MOBILE amd64
dmesg:
Copyright (c) 1992-2007 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 7.0-BETA4 #0: Tue Dec 18 12:07:27 CET 2007
root@marian46-23:/usr/obj/usr/src/sys/MOBILE
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Dual-Core AMD Opteron(tm) Processor 2218 (2600.11-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x40f13 Stepping = 3
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x2001<SSE3,CX16>
AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8>
Cores per package: 2
usable memory = 4280225792 (4081 MB)
avail memory = 4118867968 (3928 MB)
ACPI APIC Table: <HP 00000083>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
ioapic0 <Version 1.1> irqs 0-15 on motherboard
ioapic1 <Version 1.1> irqs 16-31 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
hptrr: HPT RocketRAID controller driver v1.1 (Dec 18 2007 12:07:17)
acpi0: <HP A13> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x920-0x923 on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on
acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
cpu0: <ACPI CPU> on acpi0
powernow0: <PowerNow! K8> on cpu0
cpu1: <ACPI CPU> on acpi0
powernow1: <PowerNow! K8> on cpu1
cpu2: <ACPI CPU> on acpi0
powernow2: <PowerNow! K8> on cpu2
cpu3: <ACPI CPU> on acpi0
powernow3: <PowerNow! K8> on cpu3
pcib0: <ACPI Host-PCI bridge> on acpi0
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0x1000-0x10ff mem
0xe8000000-0xefffffff,0xf7ff0000-0xf7ffffff irq 20 at device 3.0 on pci0
pci0: <base peripheral> at device 4.0 (no driver attached)
pci0: <base peripheral> at device 4.2 (no driver attached)
uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 21 at device
4.4 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <(0x103c) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
pci0: <serial bus> at device 4.6 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 13.0 on pci1
pci2: <ACPI PCI bus> on pcib2
bce0: <Broadcom NetXtreme II BCM5706 1000Base-SX (A2)> mem
0xfa000000-0xfbffffff irq 22 at device 3.0 on pci2
miibus0: <MII bus> on bce0
brgphy0: <BCM5706 10/100/1000baseTX/SX PHY> PHY 1 on miibus0
brgphy0: 1000baseSX-FDX, auto
bce0: Ethernet address: 00:1c:c4:aa:08:58
bce0: [ITHREAD]
bce0: ASIC (0x57060021); Rev (A2); Bus (PCI-X, 64-bit, 100MHz); F/W
(0x01090605); Flags( MSI )
bce1: <Broadcom NetXtreme II BCM5706 1000Base-SX (A2)> mem
0xf8000000-0xf9ffffff irq 23 at device 4.0 on pci2
miibus1: <MII bus> on bce1
brgphy1: <BCM5706 10/100/1000baseTX/SX PHY> PHY 1 on miibus1
brgphy1: 1000baseSX-FDX, auto
bce1: Ethernet address: 00:1c:c4:aa:08:88
bce1: [ITHREAD]
bce1: ASIC (0x57060021); Rev (A2); Bus (PCI-X, 64-bit, 100MHz); F/W
(0x01090605); Flags( MSI )
isab0: <PCI-ISA bridge> at device 6.2 on pci0
isa0: <ISA bus> on isab0
ohci0: <OHCI (generic) USB controller> port 0x1c00-0x1cff mem
0xf7ee0000-0xf7ee0fff irq 5 at device 7.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <OHCI (generic) USB controller> on ohci0
usb1: USB revision 1.0
uhub1: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> port 0x3000-0x30ff mem
0xf7ed0000-0xf7ed0fff irq 5 at device 7.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb2: OHCI version 1.0, legacy support
usb2: SMM does not respond, resetting
usb2: <OHCI (generic) USB controller> on ohci1
usb2: USB revision 1.0
uhub2: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> port 0x3400-0x34ff mem
0xf7ec0000-0xf7ec0fff irq 5 at device 7.2 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb1 usb2
usb3: <EHCI (generic) USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: <(0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
uhub3: 4 ports with 4 removable, self powered
pcib3: <ACPI Host-PCI bridge> on acpi0
pci4: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 15.0 on pci4
pci5: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> irq 20 at device 16.0 on pci4
pci12: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> irq 19 at device 17.0 on pci4
pci19: <ACPI PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 0.0 on pci19
pci20: <ACPI PCI bus> on pcib7
pcib8: <PCI-PCI bridge> at device 4.0 on pci20
pci21: <PCI bus> on pcib8
ciss0: <HP Smart Array E200i> port 0x4000-0x40ff mem
0xfdf80000-0xfdffffff,0xfdf70000-0xfdf77fff irq 19 at device 8.0 on pci20
ciss0: [ITHREAD]
pcib9: <ACPI PCI-PCI bridge> irq 18 at device 18.0 on pci4
pci22: <ACPI PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> irq 17 at device 19.0 on pci4
pci25: <ACPI PCI bus> on pcib10
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]
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <Standard PC COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0
sio0: type 16550A, console
sio0: [FILTER]
orm0: <ISA Option ROMs> at iomem
0xc0000-0xcafff,0xcb000-0xcefff,0xcf000-0xd07ff,0xe6000-0xe7fff on isa0
ppc0: cannot reserve I/O port range
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
ukbd0: <HP Virtual Keyboard, class 0/0, rev 1.10/0.02, addr 2> on uhub0
kbd2 at ukbd0
ums0: <HP Virtual Keyboard, class 0/0, rev 1.10/0.02, addr 2> on uhub0
ums0: X report 0x0002 not supported
device_attach: ums0 attach returned 6
uhub4: <HP Virtual Hub, class 9/0, rev 1.10/0.01, addr 3> on uhub0
uhub4: 7 ports with 7 removable, self powered
Timecounters tick every 1.000 msec
hptrr: no controller detected.
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
da0 at ciss0 bus 0 target 0 lun 0
da0: <COMPAQ RAID 1 VOLUME OK> Fixed Direct Access SCSI-5 device
da0: 135.168MB/s transfers
da0: 69973MB (143305920 512 byte sectors: 255H 32S/T 17562C)
Trying to mount root from ufs:/dev/da0s1a
HTH,
Marian
Robert Watson
On Mon, 18 Feb 2008, Ivan Voras wrote:
> I've again encountered the problem of FreeBSD 7 not wanting to boot on a HP
> server. The last time was early in 7.x development on a HP blade
> (2xdual-core Opteron), without any solution (reported on this list about a
> year ago). This time it's on a ML 350 G5 machine, with a quad-core Xeon.
>
> The problem is very hard to diagnose - the entire machine locks up during
> pci bus/device detection - the kernel debugger doesn't work, the keyboard
> lights (PS/2 keyboard) don't work, it's completely frozen.
>
> This is on both i386 and AMD64 kernels.
>
> The machine freezes after detecting pcib6. The working 6.x kernel detects
> upto pcib16, and the first device detected after pcib6 is the CISS
> controller, so maybe it's the controller driver, but the first machine (the
> blade) didn't have CISS controllers.
FYI, I'm not seeing anything like this on the two DL 145 boxes I'm using for
10gbps testing with 7.x / 8.x. I did have problems with at least a couple of
the BIOS revs in the past, so I'd repeat the advice offered elsewhere in the
thread and make sure that it's up-to-date. There was one BIOS rev where I
couldn't use a boot loader cross-built from i386 to amd64, but both the i386
boot loader and the natively built amd64 boot loader worked fine. The BIOS
upgrade made the problem entirely go away, go figure...
Otherwise, you're probably down to the printf model for debugging, unless you
have an NMI button that can get into DDB? Mine have NMI buttons on the
botherboard, I believe, but it requires opening the case to get to.
Robert N M Watson
Computer Laboratory
University of Cambridge
Morten Strårup
Hi!
It is possible to invoke an NMI through the Intregrated LightsOut
management system that is built into the server.
Look under Diagnostics when you get into the iLO system.
Kind regards
Morten Strårup
Ivan Voras
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Eygene Ryabinkin wrote:
> I have a couple of BL640c and older BL<something>p running 7.0 --
> no problems encountered. While this is not the direct answer to
> your question, had you tried to update the blade firmware to the
> latest versions with Firmware Maintenance CD? Sometimes it helps...
Thanks for the suggestion, but the blade server is deployed now and will =
stay with 6.x until there's a reason to move.
--------------enig09E1F125CEB83C1CA440C171
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHudLwldnAQVacBcgRAiEoAJ9NWoWdPk+/IM+WHLZexfGUFZtJxQCg0buZ
VKKMGy774gtf6cT7JVmhDZ8=
=Tx90
-----END PGP SIGNATURE-----
--------------enig09E1F125CEB83C1CA440C171--
Ivan Voras
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Morten Str=C3=A5rup wrote:
> Robert Watson wrote:
>>
>> FYI, I'm not seeing anything like this on the two DL 145 boxes I'm=20
>> using for 10gbps testing with 7.x / 8.x. I did have problems with at =
>> least a couple of the BIOS revs in the past, so I'd repeat the advice =
>> offered elsewhere in the thread and make sure that it's up-to-date. =20
>> There was one BIOS rev where I couldn't use a boot loader cross-built =
>> from i386 to amd64, but both the i386 boot loader and the natively=20
>> built amd64 boot loader worked fine. The BIOS upgrade made the=20
>> problem entirely go away, go figure...
>>
>> Otherwise, you're probably down to the printf model for debugging,=20
>> unless you have an NMI button that can get into DDB? Mine have NMI=20
>> buttons on the botherboard, I believe, but it requires opening the=20
>> case to get to.
>>
>=20
> Hi!
>=20
> It is possible to invoke an NMI through the Intregrated LightsOut=20
> management system that is built into the server.
>=20
> Look under Diagnostics when you get into the iLO system.
Thanks for the ideas, Robert and Morten - I'll try them. The reason I=20
thought it was something well known/common was that this is the second=20
HP system I tried 7.0 on (very different from each other) and both of=20
them failed in what looks as the same place :( It might just be bad luck.=
I have the machine on my desk so any other hardware-related ideas are=20
also welcome.
--------------enig3CF956B1B906DF44B7276FFD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHudSGldnAQVacBcgRAoC1AJ0ZJ3d2eEN0cvIpYBLtnOUSqlvlPwCeJg8H
mvv5t5OR39uN7zWbhDV7N5o=
=Jk8r
-----END PGP SIGNATURE-----
--------------enig3CF956B1B906DF44B7276FFD--
Eygene Ryabinkin
Mon, Feb 18, 2008 at 07:48:07PM +0100, Ivan Voras wrote:
>> I have a couple of BL640c and older BL<something>p running 7.0 --
>> no problems encountered. While this is not the direct answer to
>> your question, had you tried to update the blade firmware to the
>> latest versions with Firmware Maintenance CD? Sometimes it helps...
>
> Thanks for the suggestion, but the blade server is deployed now and will
> stay with 6.x until there's a reason to move.
But you can try to update firmware images on the ML350. Firmware
Maintenance CD 7.91 supports this beast:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3279711&prodTypeId=15351&prodSeriesId=1121586&swLang=8&taskId=135&swEnvOID=2026#2913
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=1121586&prodNameId=3279711&swEnvOID=2026&swLang=8&mode=2&taskId=135&swItem=MTX-26a0f9e294764a91b76b282f2a
--
Eygene
Ulf Zimmermann
>
> On Mon, 18 Feb 2008, Ivan Voras wrote:
>
> >I've again encountered the problem of FreeBSD 7 not wanting to boot on a
> >HP server. The last time was early in 7.x development on a HP blade
> >(2xdual-core Opteron), without any solution (reported on this list about a
> >year ago). This time it's on a ML 350 G5 machine, with a quad-core Xeon.
> >
> >The problem is very hard to diagnose - the entire machine locks up during
> >pci bus/device detection - the kernel debugger doesn't work, the keyboard
> >lights (PS/2 keyboard) don't work, it's completely frozen.
> >
> >This is on both i386 and AMD64 kernels.
> >
> >The machine freezes after detecting pcib6. The working 6.x kernel detects
> >upto pcib16, and the first device detected after pcib6 is the CISS
> >controller, so maybe it's the controller driver, but the first machine
> >(the blade) didn't have CISS controllers.
>
> for 10gbps testing with 7.x / 8.x. I did have problems with at least a
> couple of the BIOS revs in the past, so I'd repeat the advice offered
> elsewhere in the thread and make sure that it's up-to-date. There was one
> BIOS rev where I couldn't use a boot loader cross-built from i386 to amd64,
> but both the i386 boot loader and the natively built amd64 boot loader
> worked fine. The BIOS upgrade made the problem entirely go away, go
> figure...
>
> you have an NMI button that can get into DDB? Mine have NMI buttons on the
> botherboard, I believe, but it requires opening the case to get to.
You can generate NMI from the iLO and iLO2 interface.
--
Regards, Ulf.
---------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204
You can find my resume at: http://www.Alameda.net/~ulf/resume.html
Ivan Voras
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Eygene Ryabinkin wrote:
> Ivan,
>=20
> Mon, Feb 18, 2008 at 07:48:07PM +0100, Ivan Voras wrote:
>>> I have a couple of BL640c and older BL<something>p running 7.0 --
>>> no problems encountered. While this is not the direct answer to
>>> your question, had you tried to update the blade firmware to the
>>> latest versions with Firmware Maintenance CD? Sometimes it helps...
>> Thanks for the suggestion, but the blade server is deployed now and wi=
ll=20
>> stay with 6.x until there's a reason to move.
>=20
> But you can try to update firmware images on the ML350. Firmware
> Maintenance CD 7.91 supports this beast:
Updating the firmware didn't help. I generated a NMI and have the
debugger running. Apparently it's stuck in DELAY; the trace (transcribed
by hand) is:
DELAY()
vpd_nextbyte()
pci_read_device()
pci_add_children()
acpi_pci_attach()
device_attach()
bus_generic_attach()
acpi_pcib_attach()
acpi_pcib_pci_attach()
device_attach()
bus_generic_attach()
=2E..
this stack goes on... note repetition of device_attach in the stack,
it's repeated at least three more times. I don't know if this is normal.
Any suggestion what to do while in the debugger?
--------------enig9F389B210ED1CA22E2867B53
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHutKbldnAQVacBcgRAn8ZAKDGuwFnXMJfyw7+U/+c/UMYvk4z8wCg+ysm
l8b+8NoVweKb9NuNak76oEI=
=i5kj
-----END PGP SIGNATURE-----
--------------enig9F389B210ED1CA22E2867B53--
Ivan Voras
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Ivan Voras wrote:
> Updating the firmware didn't help. I generated a NMI and have the
> debugger running. Apparently it's stuck in DELAY;=20
Hmm, new data! It works on 8-CURRENT!
Something's fishy here. I'll try and investigate more, but if anyone has
more ideas about where to look, I'd appreciate them - I don't want to
run a -CURRENT system in production.
--------------enig9182DA1F112D4581AC91CA91
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHutr5ldnAQVacBcgRAnHvAJ0RAuTQqoZNTCHDXUlJjNMSDm1D3wCglxbp
51XYFM7b/8WwrG6vv2W7QWQ=
=KhSB
-----END PGP SIGNATURE-----
--------------enig9182DA1F112D4581AC91CA91--
Xin LI
Hash: SHA1
Ivan Voras wrote:
> Ivan Voras wrote:
>
>> Updating the firmware didn't help. I generated a NMI and have the
>> debugger running. Apparently it's stuck in DELAY;
>
> Hmm, new data! It works on 8-CURRENT!
>
> Something's fishy here. I'll try and investigate more, but if anyone has
> more ideas about where to look, I'd appreciate them - I don't want to
> run a -CURRENT system in production.
Would you please try to see if the latest snapshot, say, a RC3 image
would work? IIRC there was a known issue with ciss(4) which is widely
used on HP servers in RC2, which was fixed (new code disabled by
default) now.
Cheers,
- --
Xin LI <del...@delphij.net> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFHvKACi+vbBBjt66ARAsjFAKCAyi47CwSgg3Mo3YAL8tyMvX8NzwCdHbsD
XWPam/if/74bor3oevab9C4=
=tlrW
-----END PGP SIGNATURE-----
Ivan Voras
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Xin LI wrote:
> Ivan Voras wrote:
>> Ivan Voras wrote:
>=20
>>> Updating the firmware didn't help. I generated a NMI and have the
>>> debugger running. Apparently it's stuck in DELAY;=20
>> Hmm, new data! It works on 8-CURRENT!
>=20
>> Something's fishy here. I'll try and investigate more, but if anyone h=
as
>> more ideas about where to look, I'd appreciate them - I don't want to
>> run a -CURRENT system in production.
>=20
> Would you please try to see if the latest snapshot, say, a RC3 image
> would work? IIRC there was a known issue with ciss(4) which is widely
> used on HP servers in RC2, which was fixed (new code disabled by
> default) now.
I cannot find RC3 images on
ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/7.0/ but
booting a RELENG_7 kernel works (!) so your it looks like you have
found the problem!
--------------enigAD80273E7F1D53ED1B8E7477
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD4DBQFHvMIildnAQVacBcgRAkQpAJMHyZYX4EF1drQcl8uCQ5vdcIa/AJ9KT/Ea
PrnvCR5KhbW5nss+mIMAtw==
=+zXH
-----END PGP SIGNATURE-----
--------------enigAD80273E7F1D53ED1B8E7477--