I just received 9.3 today and installed it on my workstation. I had to add 'mem=2000m' to the kernel boot options get it to boot up after the install. Is this a known problem? Here are some hardware details: tyan S2885 motherboard 2 opteron 248 cpus 8GB ram nvidia 6800 video card lsilogic megaraid pci-x card I'm also getting the following during bootup. The megaraid_mm and megaraid_mbox modules are loaded and the raid array seems to be operating ok. Although it seems quite a bit slower. kobject_register failed for megaraid (-17) Call Trace:<ffffffff80221ea6>{kobject_register+70} <ffffffff8028db37>{bus_add_driver+103} <ffffffff8022e4de>{pci_register_driver+110} <ffffffff8807a06e>{:megaraid:megaraid_init+110} <ffffffff801525de>{sys_init_module+6542} <ffffffff8016b012>{handle_mm_fault+418} <ffffffff8807a000>{:megaraid:megaraid_init+0} <ffffffff8016eaa6>{do_munmap+918} <ffffffff80336931>{__down_read+49} <ffffffff802243e0>{__up_write+48} <ffffffff8010e9de>{system_call+126} Mark
On Sat, Apr 23, 2005 at 12:15:01AM -0400, Mark Horton wrote:
I just received 9.3 today and installed it on my workstation. I had to add 'mem=2000m' to the kernel boot options get it to boot up after the install. Is this a known problem?
No. Can you post a serial console log of a bootup without the option? -Andi
Andi Kleen wrote:
On Sat, Apr 23, 2005 at 12:15:01AM -0400, Mark Horton wrote:
I just received 9.3 today and installed it on my workstation. I had to add 'mem=2000m' to the kernel boot options get it to boot up after the install. Is this a known problem?
No. Can you post a serial console log of a bootup without the option?
-Andi
I got a serial cable hooked up and the output is below. Mark Bootdata ok (command line is root=/dev/hda4 vga=0x317 selinux=0 console=tty0 desktop elevator=as splash=verbose console=tty0 console=ttyS0,115200) Linux version 2.6.11.4-20a-smp (geeko@buildhost) (gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)) #1 SMP Wed Mar 23 21:52:37 UTC 2005 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable) BIOS-e820: 00000000bfff0000 - 00000000bffff000 (ACPI data) BIOS-e820: 00000000bffff000 - 00000000c0000000 (ACPI NVS) BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 0000000240000000 (usable) SRAT: PXM 0 -> APIC 0 -> Node 0 SRAT: PXM 1 -> APIC 1 -> Node 1 SRAT: Node 0 PXM 0 100000-bfffffff SRAT: Node 1 PXM 1 140000000-23fffffff SRAT: Node 0 PXM 0 0-bfffffff node 1 shift 24 addr 140000000 conflict 0 node 1 shift 25 addr 1fe000000 conflict 0 Bootmem setup node 0 0000000000000000-00000000bfffffff Bootmem setup node 1 0000000140000000-000000023fffffff ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfa9fe000] gsi_base[24]) IOAPIC[1]: apic_id 3, version 17, address 0xfa9fe000, GSI 24-27 ACPI: IOAPIC (id[0x04] address[0xfa9ff000] gsi_base[28]) IOAPIC[2]: apic_id 4, version 17, address 0xfa9ff000, GSI 28-31 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Setting APIC routing to flat ACPI: HPET id: 0x102282a0 base: 0xfec01000 Using ACPI (MADT) for SMP configuration information Checking aperture... CPU 0: aperture @ f0000000 size 128 MB CPU 1: aperture @ f0000000 size 128 MB Built 2 zonelists Kernel command line: root=/dev/hda4 vga=0x317 selinux=0 console=tty0 desktop elevator=as splash=verbose console=tty0 console=ttyS0,115200 bootsplash: verbose mode. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 14.318180 MHz HPET timer. time.c: Detected 2193.023 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) Memory: 7219276k/9437184k available (2280k kernel code, 0k reserved, 1179k data, 212k init) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 256 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 0(1) -> Node 0 checking if image is initramfs... it is ACPI: Looking for DSDT in initrd... not found! not found! Using local APIC NMI watchdog using perfctr0 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 0(1) -> Node 0 CPU0: AMD Opteron(tm) Processor 248 stepping 08 per-CPU timeslice cutoff: 1023.71 usecs. task migration cache decay timeout: 2 msecs. Booting processor 1/1 rip 6000 rsp ffff810144537f58 Initializing CPU#1 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 1(1) -> Node 1 AMD Opteron(tm) Processor 248 stepping 08 Total of 2 processors activated (8699.90 BogoMIPS). Using local APIC timer interrupts. Detected 12.460 MHz APIC timer. checking TSC synchronization across 2 CPUs: passed. time.c: Using HPET based timekeeping. Brought up 2 CPUs NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050211 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) Unable to handle kernel paging request at 0000000000002730 RIP: <ffffffff80120ed3>{iounmap+323} PGD 0 Oops: 0000 [1] SMP CPU 1 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.11.4-20a-smp RIP: 0010:[<ffffffff80120ed3>] <ffffffff80120ed3>{iounmap+323} RSP: 0018:ffff810144471be8 EFLAGS: 00010293 RAX: ffff8100fa8fd000 RBX: ffff810144541bc0 RCX: 000000000000001a RDX: ffffffff7fffffff RSI: 0000000000002000 RDI: 00000000fa8fd000 RBP: ffffc20000004000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: ffffffff80470ff8 R12: ffffffff803d8670 R13: ffff81014451da00 R14: ffff810144550800 R15: ffff81014451de00 FS: 0000000000000000(0000) GS:ffffffff804e3300(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000002730 CR3: 00000000bfe80000 CR4: 00000000000006e0 Process swapper (pid: 1, threadinfo ffff810144470000, task ffff8100bffc3750) Stack: ffffffff803d8670 ffffc20000004000 00000000000001ea ffffffff8022dc77 0000000000000000 0000000000000000 ffff81014451da00 ffffffff803d82a0 ffff810144550800 ffffffff803d8670 Call Trace:<ffffffff8022dc77>{quirk_usb_early_handoff+871} <ffffffff8022d008>{pci_fixup_device+136} <ffffffff8022b53c>{pci_scan_single_device+1084} <ffffffff8022b59e>{pci_scan_slot+30} <ffffffff8022bc0f>{pci_scan_child_bus+31} <ffffffff8022baa6>{pci_scan_bridge+390} <ffffffff8022bc5b>{pci_scan_child_bus+107} <ffffffff8022be09>{pci_scan_bus_parented+377} <ffffffff80261c6a>{acpi_pci_root_add+650} <ffffffff80263f63>{acpi_bus_driver_init+52} <ffffffff80264df7>{acpi_bus_add+2204} <ffffffff80264f70>{acpi_bus_scan+271} <ffffffff8050b95f>{acpi_scan_init+166} <ffffffff8010c232>{init+482} <ffffffff8010f6bb>{child_rip+8} <ffffffff8010c050>{init+0} <ffffffff8010f6b3>{child_rip+0} Code: 49 8b 88 30 27 00 00 76 2a 48 b8 00 00 00 80 00 81 ff ff 48 RIP <ffffffff80120ed3>{iounmap+323} RSP <ffff810144471be8> CR2: 0000000000002730 <0>Kernel panic - not syncing: Attempted to kill init!
Mark Horton wrote:
Andi Kleen wrote:
On Sat, Apr 23, 2005 at 12:15:01AM -0400, Mark Horton wrote:
I just received 9.3 today and installed it on my workstation. I had to add 'mem=2000m' to the kernel boot options get it to boot up after the install. Is this a known problem?
No. Can you post a serial console log of a bootup without the option?
-Andi
I read a post today from Rainer where he disabled SRAT in the bios and was able to boot up with over 4GB of ram. This worked for me as well. The tyan bios has a "ACPI SRAT support" option. I disabled it and it booted up fine. Mark
Mark Horton wrote: [...]
I'm also getting the following during bootup. The megaraid_mm and megaraid_mbox modules are loaded and the raid array seems to be operating ok. Although it seems quite a bit slower.
kobject_register failed for megaraid (-17)
Call Trace:<ffffffff80221ea6>{kobject_register+70} <ffffffff8028db37>{bus_add_driver+103} <ffffffff8022e4de>{pci_register_driver+110} <ffffffff8807a06e>{:megaraid:megaraid_init+110} <ffffffff801525de>{sys_init_module+6542} <ffffffff8016b012>{handle_mm_fault+418} <ffffffff8807a000>{:megaraid:megaraid_init+0} <ffffffff8016eaa6>{do_munmap+918} <ffffffff80336931>{__down_read+49} <ffffffff802243e0>{__up_write+48} <ffffffff8010e9de>{system_call+126}
I figured out the cause of this. During the 9.3 install it assigned both megaraid_mbox and megaraid to INITRD_MODULES. This resulted in the error above during bootup. It also resulted in performance degradation. When I took megaraid out of INITRD_MODULES and ran initrd it fixed both the error and the performance issue. Just wanted to report this in case anyone else has a lsilogic megaraid card. Mark
participants (2)
-
Andi Kleen
-
Mark Horton