Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
Matthew Jacob wrote: I must have missed something here. What's the problem that causes contigmalloc to be called here? If this is to do with 4GB of memory, that was fixed in -CURRENT over a month ago. He's using 6.0-RELEASE. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
Kris Kennaway wrote: On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: Kris Kennaway wrote: On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press Enter key. How can I resolve this issue? Please explain what you mean: why do you have to manually press Enter? It is not booting, - appears on screen and waits forever. When I press Enter key on keyboard it starts booting. Ganbold Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
On Mon, Apr 03, 2006 at 03:15:54PM +0900, Ganbold wrote: Kris Kennaway wrote: On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: Kris Kennaway wrote: On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press Enter key. How can I resolve this issue? Please explain what you mean: why do you have to manually press Enter? It is not booting, - appears on screen and waits forever. When I press Enter key on keyboard it starts booting. That's a completely separate issue. I don't know why it's happening though. Kris pgpAcJlxDBp7s.pgp Description: PGP signature
Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
On Mon, 3 Apr 2006, Scott Long wrote: Matthew Jacob wrote: I must have missed something here. What's the problem that causes contigmalloc to be called here? If this is to do with 4GB of memory, that was fixed in -CURRENT over a month ago. He's using 6.0-RELEASE. A reason to allow an MFC ? :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
Matthew Jacob wrote: On Mon, 3 Apr 2006, Scott Long wrote: Matthew Jacob wrote: I must have missed something here. What's the problem that causes contigmalloc to be called here? If this is to do with 4GB of memory, that was fixed in -CURRENT over a month ago. He's using 6.0-RELEASE. A reason to allow an MFC ? :-) I'm fully intending for it to get MFC'd, I just want a chance to test it in our FC environment first so that any problems don't become emergencies. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
Kris Kennaway wrote: On Mon, Apr 03, 2006 at 03:15:54PM +0900, Ganbold wrote: Kris Kennaway wrote: On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: Kris Kennaway wrote: On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press Enter key. How can I resolve this issue? Please explain what you mean: why do you have to manually press Enter? It is not booting, - appears on screen and waits forever. When I press Enter key on keyboard it starts booting. That's a completely separate issue. I don't know why it's happening though. Same problem exists under FreeBSD-6.1-PRERELEASE, machine is not booting, - appears on screen and waits forever. When I press Enter key on keyboard it starts booting. On CURRENT even worse, I tested yesterday's CURRENT, boot panics saying CPU class not configured. Ganbold Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot problem in HP Proliant ML370 G4
Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. 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 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC MPTable: HP PROLIANT Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.12-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,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=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD Features=0x2000LM Hyperthreading: 2 logical CPUs real memory = 1073688576 (1023 MB) avail memory = 1041793024 (993 MB) ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic2: Assuming intbase of 48 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 npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: HP P50 on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA irq 3 on acpi0 pci_link1: ACPI PCI Link LNKB irq 3 on acpi0 pci_link2: ACPI PCI Link LNKC irq 3 on acpi0 pci_link3: ACPI PCI Link LNKD irq 3 on acpi0 pci_link4: ACPI PCI Link LNKE irq 0 on acpi0 pci_link5: ACPI PCI Link LNKF irq 3 on acpi0 pci_link6: ACPI PCI Link LNKG irq 3 on acpi0 pci_link7: ACPI PCI Link LNKH irq 3 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 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: MPTable PCI-PCI bridge at device 2.0 on pci0 pci2: PCI bus on pcib1 pcib2: MPTable PCI-PCI bridge at device 0.0 on pci2 pci3: PCI bus on pcib2 mpt0: LSILogic 1030 Ultra4 Adapter port 0x4000-0x40ff mem 0xfdee-0xfdef,0xfdec-0xfded irq 31 at device 3.0 on pci3 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt1: LSILogic 1030 Ultra4 Adapter port 0x4400-0x44ff mem 0xfdea-0xfdeb,0xfde8-0xfde9 irq 27 at device 3.1 on pci3 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.14.0 mpt1: Unhandled Event Notify Frame. Event 0xa. pcib3: MPTable PCI-PCI bridge at device 0.2 on pci2 pci7: PCI bus on pcib3 bge0: Broadcom BCM5703X Gigabit Ethernet, ASIC rev. 0x1100 mem 0xfdff-0xfdff irq 49 at device 3.0 on pci7 miibus0: MII bus on bge0 brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:14:c2:60:1e:fc pcib4: MPTable PCI-PCI bridge at device 4.0 on pci0 pci11: PCI bus on pcib4 pcib5: MPTable PCI-PCI bridge at device 5.0 on pci0 pci14: PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x2000-0x201f irq 9 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 9 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 9 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 9 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 0xfbef-0xfbef03ff irq 9 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 pcib6: MPTable PCI-PCI bridge at device 30.0 on pci0 pci1: PCI bus on pcib6 pci1: display, VGA at device 3.0 (no driver attached) pci1: base peripheral at device 4.0 (no driver
contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. Kris pgpOJLSwsV7LE.pgp Description: PGP signature
Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
Kris Kennaway wrote: On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press Enter key. How can I resolve this issue? Is there any known solution? In any case I will try first RELENG_6 then CURRENT on this machine. thanks, Ganbold Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote: Kris Kennaway wrote: On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press Enter key. How can I resolve this issue? Please explain what you mean: why do you have to manually press Enter? Kris pgpqSTt0JsDWE.pgp Description: PGP signature
RE: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)
I must have missed something here. What's the problem that causes contigmalloc to be called here? If this is to do with 4GB of memory, that was fixed in -CURRENT over a month ago. -Original Message- From: Ganbold [mailto:[EMAIL PROTECTED] Sent: Sunday, April 02, 2006 10:28 PM To: Kris Kennaway Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; freebsd-stable@FreeBSD.org Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) Kris Kennaway wrote: On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote: Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE. Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) line and continues. I will try to upgrade again to 6.1-PRERELEASE later today. I did before and the problem still was there. The mpt driver calls contigmalloc in a way that takes ages to run because it was poorly rewritten some time ago. Scottl partially fixed it on 7.0 (after the problem became much worse there - it was taking over 40 minutes instead of 4) but the change is not complete enough to back-port yet. I see. Yes, it eventually becomes up after 3-4 minutes. However what annoying is every time I reboot/restart the server I have to manually press Enter key. How can I resolve this issue? Is there any known solution? In any case I will try first RELENG_6 then CURRENT on this machine. thanks, Ganbold Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
boot problem in HP Proliant ML370 G4
Hi, I have strange problem when booting FreeBSD-6.x in HP Proliant ML370 G4. The problem is - appears on the screen and it never boots unless somebody hits the Enter key. Sometimes even PS2 keyboard doesn't respond during that time. Tried with USB keyboard, same problem. The machine has dual Xeon 3.2 GHz, 1GB of RAM and LSI Logic (mpt-5.0.5.20.00 bios) LSI1030-IT controller and one Compaq BD1468A4B5 146GB SCSI disk. It didn't even boot with WITNESS and INVARIANTS options, scrolls very fast and forever showing some SCSI stuffs. How to solve this problem? Does anybody have this kind of issues before? thanks, Ganbold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
