You are not logged in.

#1 2009-07-28 17:06:47

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

[Solved] Kernel Oops continues. Need help from someone who know this..

Edit: It turned out to be my wireless dongle who tainted the kernel. Instead of loading the ra73 module I'll use ndiswrapper until the issue is solved.


I have a kernel oops as soon as I try to launch X with the nvidia module. I posted about this problem on the Nvidia Linux forum and someone there suggested that this is not a nvidia problem, but rather a kernel issue.

So here we go again...
I have a Zotac IONITX-B mother board with the Nvidia GeForce 9400M chipset. Whenever I try to launch X with the nvidia module it results in a kernel Oops and X is unusable.

As soon as I try to load X (xorg-server 1.6.2) the pc crashes with a kernel Oops. The pc is equipped with 4Gb of DDR2 800Mhz RAM. No other perhiperals are used except for one wifi usb dongle and a usb keyboard. The pc is hooked up to a 40" lcd tv via HDMI.

This is what I have done so far to try pin pointing the problem:

* Installed the nvidia package from the ArchLinux repositories = results in kernel Oops when trying to run X.
* unistalled the ArchLinux nvidia package and installed the driver available on the nvidia website (the .run file) = results in kernel Oops when trying to run X.
* Removed one stick of ram and tested each stick individually on both slots on the motherboard = results in kernel Oops on all tries when trying to run X.
* Installed xf86-video-vesa from the ArchLinux repositories and used that module in xorg.conf = results in no kernel Oops and a well working X environment.

My xorg.conf is very minimal as it depends on HAL to detect what needs to be loaded.

As I said earlier, the nvidia guys says it is kernel related. How do I determine what is causing this? I am so close to having a perfect setup but this stuff is beyond me. Would it help if I compiled my own kernel?
Any help is much appreciated!

Last edited by antis (2009-08-01 13:37:15)

Offline

#2 2009-07-28 17:11:46

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

This is the output from dmesg as I try to boot into X. The full nvidia bug  report is available if needed.

Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.0 20090630 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Jul 20 11:20:32 UTC 2009
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  NSC Geode by NSC
  Cyrix CyrixInstead
  Centaur CentaurHauls
  Transmeta GenuineTMx86
  Transmeta TransmetaCPU
  UMC UMC UMC UMC
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bffa0000 (usable)
 BIOS-e820: 00000000bffa0000 - 00000000bffae000 (ACPI data)
 BIOS-e820: 00000000bffae000 - 00000000bfff0000 (ACPI NVS)
 BIOS-e820: 00000000bfff0000 - 00000000e0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ff700000 - 0000000100000000 (reserved)
DMI present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
last_pfn = 0xbffa0 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CFFFF write-protect
  D0000-DFFFF uncachable
  E0000-EFFFF write-through
  F0000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 0E0000000 mask 0E0000000 uncachable
  1 base 000000000 mask 000000000 write-back
  2 disabled
  3 disabled
  4 disabled
  5 disabled
  6 disabled
  7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
 modified: 0000000000000000 - 0000000000010000 (reserved)
 modified: 0000000000010000 - 000000000009fc00 (usable)
 modified: 000000000009fc00 - 00000000000a0000 (reserved)
 modified: 00000000000e0000 - 0000000000100000 (reserved)
 modified: 0000000000100000 - 00000000bffa0000 (usable)
 modified: 00000000bffa0000 - 00000000bffae000 (ACPI data)
 modified: 00000000bffae000 - 00000000bfff0000 (ACPI NVS)
 modified: 00000000bfff0000 - 00000000e0000000 (reserved)
 modified: 00000000fec00000 - 00000000fec01000 (reserved)
 modified: 00000000fee00000 - 00000000fee01000 (reserved)
 modified: 00000000ff700000 - 0000000100000000 (reserved)
init_memory_mapping: 0000000000000000-00000000377fe000
 0000000000 - 0000400000 page 4k
 0000400000 - 0037400000 page 2M
 0037400000 - 00377fe000 page 4k
kernel direct mapping tables up to 377fe000 @ 10000-15000
RAMDISK: 7ff4d000 - 7ffef6c4
Allocated new RAMDISK: 0062a000 - 006cc6c4
Move RAMDISK from 000000007ff4d000 - 000000007ffef6c3 to 0062a000 - 006cc6c3
ACPI: RSDP 000fa810 00024 (v02 ACPIAM)
ACPI: XSDT bffa0100 0005C (v01 050809 XSDT1106 20090508 MSFT 00000097)
ACPI: FACP bffa0290 000F4 (v04 050809 FACP1106 20090508 MSFT 00000097)
ACPI: DSDT bffa04a0 070E9 (v02  A108P A108PD08 00000D08 INTL 20051117)
ACPI: FACS bffae000 00040
ACPI: APIC bffa0390 00080 (v02 050809 APIC1106 20090508 MSFT 00000097)
ACPI: MCFG bffa0410 0003C (v01 050809 OEMMCFG  20090508 MSFT 00000097)
ACPI: WDRT bffa0450 00047 (v01 050809 NV-WDRT  20090508 MSFT 00000097)
ACPI: OEMB bffae040 00079 (v01 050809 OEMB1106 20090508 MSFT 00000097)
ACPI: HPET bffaa4a0 00038 (v01 050809 OEMHPET0 20090508 MSFT 00000097)
ACPI: NVHD bffae0c0 00284 (v01 050809  NVHDCP  20090508 MSFT 00000097)
ACPI: Local APIC address 0xfee00000
2183MB HIGHMEM available.
887MB LOWMEM available.
  mapped low ram: 0 - 377fe000
  low ram: 0 - 377fe000
  node 0 low ram: 00000000 - 377fe000
  node 0 bootmap 00011000 - 00017f00
(9 early reservations) ==> bootmem [0000000000 - 00377fe000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
  #2 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
  #3 [0000100000 - 0000626e44]    TEXT DATA BSS ==> [0000100000 - 0000626e44]
  #4 [000009fc00 - 0000100000]    BIOS reserved ==> [000009fc00 - 0000100000]
  #5 [0000627000 - 00006291bf]              BRK ==> [0000627000 - 00006291bf]
  #6 [0000010000 - 0000011000]          PGTABLE ==> [0000010000 - 0000011000]
  #7 [000062a000 - 00006cc6c4]      NEW RAMDISK ==> [000062a000 - 00006cc6c4]
  #8 [0000011000 - 0000018000]          BOOTMAP ==> [0000011000 - 0000018000]
found SMP MP-table at [c00ff780] ff780
Zone PFN ranges:
  DMA      0x00000010 -> 0x00001000
  Normal   0x00001000 -> 0x000377fe
  HighMem  0x000377fe -> 0x000bffa0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x000bffa0
On node 0 totalpages: 786223
free_area_init_node: node 0, pgdat c04c3380, node_mem_map c1000200
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3951 pages, LIFO batch:0
  Normal zone: 1744 pages used for memmap
  Normal zone: 221486 pages, LIFO batch:31
  HighMem zone: 4368 pages used for memmap
  HighMem zone: 554642 pages, LIFO batch:31
Using APIC driver default
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
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: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
ACPI: IRQ14 used by override.
ACPI: IRQ15 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x10de8201 base: 0xfed00000
SMP: Allowing 4 CPUs, 2 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Allocating PCI resources starting at e2000000 (gap: e0000000:1ec00000)
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 11 pages at c2810000, static data 24444 bytes
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 780079
Kernel command line: root=/dev/disk/by-uuid/62597412-49e3-4f7c-9e01-eebaa5be4bd3 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
NR_IRQS:512
PID hash table entries: 4096 (order: 12, 16384 bytes)
Extended CMOS year: 2000
Fast TSC calibration using PIT
Detected 1599.749 MHz processor.
spurious 8259A interrupt: IRQ7.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Initializing HighMem for node 0 (000377fe:000bffa0)
Memory: 3112388k/3145344k available (2905k kernel code, 31576k reserved, 1052k data, 392k init, 2236040k highmem)
virtual kernel memory layout:
    fixmap  : 0xfff4e000 - 0xfffff000   ( 708 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
      .init : 0xc04e3000 - 0xc0545000   ( 392 kB)
      .data : 0xc03d647f - 0xc04dd6a8   (1052 kB)
      .text : 0xc0100000 - 0xc03d647f   (2905 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
hpet clockevent registered
HPET: 4 timers in total, 0 timers will be used for per-cpu timer
Calibrating delay loop (skipped), value calculated using timer frequency.. 3200.81 BogoMIPS (lpj=5332496)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 24K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
using mwait in idle threads.
Checking 'hlt' instruction... OK.
ACPI: Core revision 20090320
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Atom(TM) CPU  230   @ 1.60GHz stepping 02
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3201.29 BogoMIPS (lpj=5333268)
CPU: L1 I cache: 32K, L1 D cache: 24K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: Intel(R) Atom(TM) CPU  230   @ 1.60GHz stepping 02
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
Total of 2 processors activated (6402.10 BogoMIPS).
CPU0 attaching sched-domain:
 domain 0: span 0-1 level SIBLING
  groups: 0 1
CPU1 attaching sched-domain:
 domain 0: span 0-1 level SIBLING
  groups: 1 0
net_namespace: 1056 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base fc000000 segment 0 buses 0 - 31
PCI: Not using MMCONFIG.
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=7
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MCFG configuration 0: base fc000000 segment 0 buses 0 - 31
PCI: MCFG area at fc000000 reserved in ACPI motherboard resources
PCI: Using MMCONFIG for extended config space
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:03.0: reg 10 io port: [0x4f00-0x4fff]
pci 0000:00:03.2: reg 10 io port: [0x4900-0x493f]
pci 0000:00:03.2: reg 20 io port: [0x4d00-0x4d3f]
pci 0000:00:03.2: reg 24 io port: [0x4e00-0x4e3f]
pci 0000:00:03.2: PME# supported from D3hot D3cold
pci 0000:00:03.2: PME# disabled
pci 0000:00:03.5: reg 10 32bit mmio: [0xfae80000-0xfaefffff]
pci 0000:00:04.0: reg 10 32bit mmio: [0xfae7f000-0xfae7ffff]
pci 0000:00:04.0: supports D1 D2
pci 0000:00:04.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:04.0: PME# disabled
pci 0000:00:04.1: reg 10 32bit mmio: [0xfae7ec00-0xfae7ecff]
pci 0000:00:04.1: supports D1 D2
pci 0000:00:04.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:04.1: PME# disabled
pci 0000:00:06.0: reg 10 32bit mmio: [0xfae7d000-0xfae7dfff]
pci 0000:00:06.0: supports D1 D2
pci 0000:00:06.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:06.0: PME# disabled
pci 0000:00:06.1: reg 10 32bit mmio: [0xfae7e800-0xfae7e8ff]
pci 0000:00:06.1: supports D1 D2
pci 0000:00:06.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:06.1: PME# disabled
pci 0000:00:08.0: reg 10 32bit mmio: [0xfae78000-0xfae7bfff]
pci 0000:00:08.0: PME# supported from D3hot D3cold
pci 0000:00:08.0: PME# disabled
pci 0000:00:0a.0: reg 10 32bit mmio: [0xfae7c000-0xfae7cfff]
pci 0000:00:0a.0: reg 14 io port: [0xd080-0xd087]
pci 0000:00:0a.0: reg 18 32bit mmio: [0xfae7e400-0xfae7e4ff]
pci 0000:00:0a.0: reg 1c 32bit mmio: [0xfae7e000-0xfae7e00f]
pci 0000:00:0a.0: supports D1 D2
pci 0000:00:0a.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:0a.0: PME# disabled
pci 0000:00:0b.0: reg 10 io port: [0xd000-0xd007]
pci 0000:00:0b.0: reg 14 io port: [0xcc00-0xcc03]
pci 0000:00:0b.0: reg 18 io port: [0xc880-0xc887]
pci 0000:00:0b.0: reg 1c io port: [0xc800-0xc803]
pci 0000:00:0b.0: reg 20 io port: [0xc480-0xc48f]
pci 0000:00:0b.0: reg 24 32bit mmio: [0xfae76000-0xfae77fff]
pci 0000:00:0c.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:0c.0: PME# disabled
pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:10.0: PME# disabled
pci 0000:00:15.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:15.0: PME# disabled
pci 0000:00:16.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:16.0: PME# disabled
pci 0000:00:17.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:17.0: PME# disabled
pci 0000:00:18.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:18.0: PME# disabled
pci 0000:00:09.0: transparent bridge
pci 0000:03:00.0: reg 10 32bit mmio: [0xfb000000-0xfbffffff]
pci 0000:03:00.0: reg 14 64bit mmio: [0xe0000000-0xefffffff]
pci 0000:03:00.0: reg 1c 64bit mmio: [0xf8000000-0xf9ffffff]
pci 0000:03:00.0: reg 24 io port: [0xec00-0xec7f]
pci 0000:03:00.0: reg 30 32bit mmio: [0xfafe0000-0xfaffffff]
pci 0000:00:10.0: bridge io port: [0xe000-0xefff]
pci 0000:00:10.0: bridge 32bit mmio: [0xfaf00000-0xfbffffff]
pci 0000:00:10.0: bridge 64bit mmio pref: [0xe0000000-0xf9ffffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IXVE._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P6._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P7._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P8._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN0A] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN0B] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN0C] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN0D] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN1A] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN1B] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN1C] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN1D] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN2A] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN2B] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN2C] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN2D] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN3A] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN3B] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN3C] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN3D] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN4A] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN4B] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN4C] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN4D] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN5A] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN5B] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN5C] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN5D] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN6A] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN6B] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN6C] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LN6D] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LUB0] (IRQs 20 21 22 23) *15
ACPI: PCI Interrupt Link [LUB2] (IRQs 20 21 22 23) *10
ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22 23) *10
ACPI: PCI Interrupt Link [LAZA] (IRQs 20 21 22 23) *15
ACPI: PCI Interrupt Link [SGRU] (IRQs 20 21 22 23) *10
ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22 23) *11
ACPI: PCI Interrupt Link [LPMU] (IRQs 20 21 22 23) *9
ACPI: PCI Interrupt Link [LSA0] (IRQs 20 21 22 23) *5
ACPI: PCI Interrupt Link [LATA] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [UB11] (IRQs 20 21 22 23) *11
ACPI: PCI Interrupt Link [UB12] (IRQs 20 21 22 23) *9
ACPI: PCI Interrupt Link [LRP0] (IRQs 20 21 22 23) *10
ACPI: PCI Interrupt Link [LRP1] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LRP2] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LRP3] (IRQs 20 21 22 23) *11
ACPI: PCI Interrupt Link [LRP4] (IRQs 20 21 22 23) *9
ACPI: PCI Interrupt Link [LRP5] (IRQs 20 21 22 23) *15
ACPI: PCI Interrupt Link [LRP6] (IRQs 20 21 22 23) *14
PCI: Using ACPI for IRQ routing
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 12 devices
ACPI: ACPI bus type pnp unregistered
system 00:05: ioport range 0x4d0-0x4d1 has been reserved
system 00:05: ioport range 0x800-0x80f has been reserved
system 00:05: ioport range 0x4000-0x407f has been reserved
system 00:05: ioport range 0x4080-0x40ff has been reserved
system 00:05: ioport range 0x4400-0x447f has been reserved
system 00:05: ioport range 0x4480-0x44ff has been reserved
system 00:05: ioport range 0x4800-0x487f has been reserved
system 00:05: ioport range 0x4880-0x48ff has been reserved
system 00:05: iomem range 0xfefe2000-0xfefe3fff has been reserved
system 00:05: iomem range 0xfefe1000-0xfefe1fff has been reserved
system 00:05: iomem range 0xfee01000-0xfeefffff has been reserved
system 00:08: iomem range 0xfec00000-0xfec00fff has been reserved
system 00:08: iomem range 0xfee00000-0xfee00fff has been reserved
system 00:09: ioport range 0xa00-0xa0f has been reserved
system 00:09: ioport range 0xa10-0xa1f has been reserved
system 00:0a: iomem range 0xfc000000-0xfdffffff has been reserved
system 00:0b: iomem range 0x0-0x9ffff could not be reserved
system 00:0b: iomem range 0xc0000-0xcffff could not be reserved
system 00:0b: iomem range 0xe0000-0xfffff could not be reserved
system 00:0b: iomem range 0x100000-0xdfffffff could not be reserved
system 00:0b: iomem range 0xfec00000-0xffffffff could not be reserved
pci 0000:00:09.0: PCI bridge, secondary bus 0000:01
pci 0000:00:09.0:   IO window: disabled
pci 0000:00:09.0:   MEM window: disabled
pci 0000:00:09.0:   PREFETCH window: disabled
pci 0000:00:0c.0: PCI bridge, secondary bus 0000:02
pci 0000:00:0c.0:   IO window: disabled
pci 0000:00:0c.0:   MEM window: disabled
pci 0000:00:0c.0:   PREFETCH window: disabled
pci 0000:00:10.0: PCI bridge, secondary bus 0000:03
pci 0000:00:10.0:   IO window: 0xe000-0xefff
pci 0000:00:10.0:   MEM window: 0xfaf00000-0xfbffffff
pci 0000:00:10.0:   PREFETCH window: 0x000000e0000000-0x000000f9ffffff
pci 0000:00:15.0: PCI bridge, secondary bus 0000:04
pci 0000:00:15.0:   IO window: disabled
pci 0000:00:15.0:   MEM window: disabled
pci 0000:00:15.0:   PREFETCH window: disabled
pci 0000:00:16.0: PCI bridge, secondary bus 0000:05
pci 0000:00:16.0:   IO window: disabled
pci 0000:00:16.0:   MEM window: disabled
pci 0000:00:16.0:   PREFETCH window: disabled
pci 0000:00:17.0: PCI bridge, secondary bus 0000:06
pci 0000:00:17.0:   IO window: disabled
pci 0000:00:17.0:   MEM window: disabled
pci 0000:00:17.0:   PREFETCH window: disabled
pci 0000:00:18.0: PCI bridge, secondary bus 0000:07
pci 0000:00:18.0:   IO window: disabled
pci 0000:00:18.0:   MEM window: disabled
pci 0000:00:18.0:   PREFETCH window: disabled
pci 0000:00:09.0: setting latency timer to 64
ACPI: PCI Interrupt Link [LRP0] enabled at IRQ 23
pci 0000:00:0c.0: PCI INT A -> Link[LRP0] -> GSI 23 (level, low) -> IRQ 23
pci 0000:00:0c.0: setting latency timer to 64
pci 0000:00:10.0: setting latency timer to 64
ACPI: PCI Interrupt Link [LRP3] enabled at IRQ 22
pci 0000:00:15.0: PCI INT A -> Link[LRP3] -> GSI 22 (level, low) -> IRQ 22
pci 0000:00:15.0: setting latency timer to 64
ACPI: PCI Interrupt Link [LRP4] enabled at IRQ 21
pci 0000:00:16.0: PCI INT A -> Link[LRP4] -> GSI 21 (level, low) -> IRQ 21
pci 0000:00:16.0: setting latency timer to 64
ACPI: PCI Interrupt Link [LRP5] enabled at IRQ 20
pci 0000:00:17.0: PCI INT A -> Link[LRP5] -> GSI 20 (level, low) -> IRQ 20
pci 0000:00:17.0: setting latency timer to 64
ACPI: PCI Interrupt Link [LRP6] enabled at IRQ 23
pci 0000:00:18.0: PCI INT A -> Link[LRP6] -> GSI 23 (level, low) -> IRQ 23
pci 0000:00:18.0: setting latency timer to 64
pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
pci_bus 0000:01: resource 3 io:  [0x00-0xffff]
pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffff]
pci_bus 0000:03: resource 0 io:  [0xe000-0xefff]
pci_bus 0000:03: resource 1 mem: [0xfaf00000-0xfbffffff]
pci_bus 0000:03: resource 2 pref mem [0xe0000000-0xf9ffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 649k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1248794877.657:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1714
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:03:00.0: Boot video device
pcieport-driver 0000:00:0c.0: irq 24 for MSI/MSI-X
pcieport-driver 0000:00:0c.0: setting latency timer to 64
pcieport-driver 0000:00:15.0: irq 25 for MSI/MSI-X
pcieport-driver 0000:00:15.0: setting latency timer to 64
pcieport-driver 0000:00:16.0: irq 26 for MSI/MSI-X
pcieport-driver 0000:00:16.0: setting latency timer to 64
pcieport-driver 0000:00:17.0: irq 27 for MSI/MSI-X
pcieport-driver 0000:00:17.0: setting latency timer to 64
pcieport-driver 0000:00:18.0: irq 28 for MSI/MSI-X
pcieport-driver 0000:00:18.0: setting latency timer to 64
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:01: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 392k freed
SCSI subsystem initialized
libata version 3.00 loaded.
ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 22
pata_acpi 0000:00:0b.0: PCI INT A -> Link[LSA0] -> GSI 22 (level, low) -> IRQ 22
pata_acpi 0000:00:0b.0: setting latency timer to 64
pata_acpi 0000:00:0b.0: PCI INT A disabled
ahci 0000:00:0b.0: version 3.0
ahci 0000:00:0b.0: PCI INT A -> Link[LSA0] -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:0b.0: irq 29 for MSI/MSI-X
ahci 0000:00:0b.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl IDE mode
ahci 0000:00:0b.0: flags: 64bit ncq sntf led pmp pio slum part 
ahci 0000:00:0b.0: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76100 irq 29
ata2: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76180 irq 29
ata3: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76200 irq 29
ata4: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76280 irq 29
ata5: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76300 irq 29
ata6: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76380 irq 29
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link down (SStatus 0 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: CFA: ST650211CF, 3.08, max UDMA/33
ata1.00: 9767520 sectors, multi 16: LBA 
ata1.00: applying bridge limits
ata1.00: configured for UDMA/33
ata1.00: configured for UDMA/33
ata1: EH complete
scsi 0:0:0:0: Direct-Access     ATA      ST650211CF       3.08 PQ: 0 ANSI: 5
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0: [sda] 9767520 512-byte hardware sectors: (5.00 GB/4.65 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
JFS: nTxBlock = 8192, nTxLock = 65536
rtc_cmos 00:07: RTC can wake from S4
rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
udev: starting version 141
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
ACPI: Power Button [PWRF]
input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
ACPI: Power Button [PWRB]
processor ACPI_CPU:00: registered as cooling_device0
ACPI: Processor [P001] (supports 8 throttling states)
processor ACPI_CPU:01: registered as cooling_device1
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21
forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 21 (level, low) -> IRQ 21
forcedeth 0000:00:0a.0: setting latency timer to 64
forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 3, addr 00:01:2e:26:12:b8
forcedeth 0000:00:0a.0: highdma csum pwrctl gbit lnktim msi desc-v3
ACPI: WMI: Mapper loaded
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
sd 0:0:0:0: Attached scsi generic sg0 type 0
input: PC Speaker as /devices/platform/pcspkr/input/input3
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 20
ehci_hcd 0000:00:04.1: PCI INT B -> Link[LUB2] -> GSI 20 (level, low) -> IRQ 20
ehci_hcd 0000:00:04.1: setting latency timer to 64
ehci_hcd 0000:00:04.1: EHCI Host Controller
ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:04.1: debug port 1
ehci_hcd 0000:00:04.1: cache line size of 32 is not supported
ehci_hcd 0000:00:04.1: irq 20, io mem 0xfae7ec00
ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ACPI: PCI Interrupt Link [UB12] enabled at IRQ 23
ehci_hcd 0000:00:06.1: PCI INT B -> Link[UB12] -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:06.1: setting latency timer to 64
ehci_hcd 0000:00:06.1: EHCI Host Controller
ehci_hcd 0000:00:06.1: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:06.1: debug port 1
ehci_hcd 0000:00:06.1: cache line size of 32 is not supported
ehci_hcd 0000:00:06.1: irq 23, io mem 0xfae7e800
ehci_hcd 0000:00:06.1: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
i2c-adapter i2c-0: nForce2 SMBus adapter at 0x4d00
i2c-adapter i2c-1: nForce2 SMBus adapter at 0x4e00
usb 1-6: new high speed USB device using ehci_hcd and address 3
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 22
ohci_hcd 0000:00:04.0: PCI INT A -> Link[LUB0] -> GSI 22 (level, low) -> IRQ 22
ohci_hcd 0000:00:04.0: setting latency timer to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:04.0: irq 22, io mem 0xfae7f000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 6 ports detected
ACPI: PCI Interrupt Link [UB11] enabled at IRQ 21
ohci_hcd 0000:00:06.0: PCI INT A -> Link[UB11] -> GSI 21 (level, low) -> IRQ 21
ohci_hcd 0000:00:06.0: setting latency timer to 64
ohci_hcd 0000:00:06.0: OHCI Host Controller
ohci_hcd 0000:00:06.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:06.0: irq 21, io mem 0xfae7d000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
Linux agpgart interface v0.103
usb 1-6: configuration #1 chosen from 1 choice
usb 3-3: new low speed USB device using ohci_hcd and address 2
usb 3-3: configuration #1 chosen from 1 choice
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
    (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
ACPI: PCI Interrupt Link [SGRU] enabled at IRQ 20
nvidia 0000:03:00.0: PCI INT A -> Link[SGRU] -> GSI 20 (level, low) -> IRQ 20
nvidia 0000:03:00.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86 Kernel Module  185.18.14  Wed May 27 02:23:13 PDT 2009
usbcore: registered new interface driver hiddev
input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/input/input4
generic-usb 0003:0518:0001.0001: input,hidraw0: USB HID v1.10 Keyboard [Plus More Enterprise LTD. USB-compliant keyboard] on usb-0000:00:04.0-3/input0
input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.1/input/input5
generic-usb 0003:0518:0001.0002: input,hidraw1: USB HID v1.10 Mouse [Plus More Enterprise LTD. USB-compliant keyboard] on usb-0000:00:04.0-3/input1
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
HDA Intel 0000:00:08.0: power state changed by ACPI to D0
ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 23
HDA Intel 0000:00:08.0: PCI INT A -> Link[LAZA] -> GSI 23 (level, low) -> IRQ 23
HDA Intel 0000:00:08.0: setting latency timer to 64
hda_codec: Unknown model for ALC662, trying auto-probe from BIOS...
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:08.0/input/input6
phy0: Selected rate control algorithm 'minstrel'
Registered led device: rt73usb-phy0::radio
Registered led device: rt73usb-phy0::assoc
Registered led device: rt73usb-phy0::quality
usbcore: registered new interface driver rt73usb
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
rt73usb 1-6:1.0: firmware: requesting rt73.bin
wlan0: authenticate with AP 00:90:d0:ec:71:05
wlan0: authenticated
wlan0: associate with AP 00:90:d0:ec:71:05
wlan0: RX AssocResp from 00:90:d0:ec:71:05 (capab=0x411 status=0 aid=1)
wlan0: associated
BUG: unable to handle kernel paging request at 000d8a0b
IP: [<c016c19c>] m_show+0x9c/0x1a0
*pde = 00000000 
Oops: 0000 [#1] PREEMPT SMP 
last sysfs file: /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/resource
Modules linked in: ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables snd_hda_codec_nvhdmi arc4 ecb snd_hda_codec_realtek rt73usb crc_itu_t rt2x00usb rt2x00lib led_class input_polldev joydev snd_seq_dummy snd_hda_intel mac80211 snd_seq_oss usbhid snd_seq_midi_event hid snd_hda_codec snd_seq snd_seq_device cfg80211 nvidia(P) snd_pcm_oss snd_mixer_oss snd_hwdep snd_pcm snd_timer snd agpgart ohci_hcd soundcore psmouse i2c_nforce2 shpchp ehci_hcd pcspkr snd_page_alloc serio_raw sg pci_hotplug usbcore wmi i2c_core forcedeth evdev thermal processor fan button battery ac rtc_cmos rtc_core rtc_lib jfs sd_mod ahci ata_generic pata_acpi libata scsi_mod

Pid: 1971, comm: X Tainted: P           (2.6.30-ARCH #1) To Be Filled By O.E.M.
EIP: 0060:[<c016c19c>] EFLAGS: 00210282 CPU: 0
EIP is at m_show+0x9c/0x1a0
EAX: 00000000 EBX: f6745a80 ECX: 00000f59 EDX: 00000000
ESI: f9dc8740 EDI: 000d8a0b EBP: f9dc8870 ESP: f5e25eb4
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process X (pid: 1971, ti=f5e24000 task=f5e20400 task.ti=f5e24000)
Stack:
 f6745a80 c0458a98 fa04058c 00011884 f9dc8744 f5e25f30 c03d3398 647d5c20
 c03e1768 f6745a80 f9dc8744 f5e25f30 c01eea13 f5d9c9f8 c01b3e41 0000007c
 00000000 b7f8a022 f6745aa8 000003de 00000022 f5ca9d80 f5e25f90 0000001b
Call Trace:
 [<c03d3398>] ? mutex_lock+0x18/0x40
 [<c01eea13>] ? seq_read+0x263/0x470
 [<c01b3e41>] ? __do_fault+0x351/0x430
 [<c01ee7b0>] ? seq_read+0x0/0x470
 [<c0219e89>] ? proc_reg_read+0x79/0xc0
 [<c01d1b43>] ? vfs_read+0xc3/0x1a0
 [<c0219e10>] ? proc_reg_read+0x0/0xc0
 [<c01d1d28>] ? sys_read+0x58/0xb0
 [<c0103c73>] ? sysenter_do_call+0x12/0x28
Code: 10 31 c0 81 c5 2c 01 00 00 39 ef 74 2d 66 90 8b 47 08 89 1c 24 c7 44 24 04 98 8a 45 c0 83 c0 0c 89 44 24 08 e8 06 24 08 00 8b 3f <8b> 07 0f 18 00 90 39 ef 75 da b8 01 00 00 00 8b 96 d4 00 00 00 
EIP: [<c016c19c>] m_show+0x9c/0x1a0 SS:ESP 0068:f5e25eb4
CR2: 00000000000d8a0b
---[ end trace 9da229b657f2dd53 ]---

Offline

#3 2009-07-29 00:42:25

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

What is a kernel oops?  Kermel panic?


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#4 2009-07-29 07:37:20

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

As far as I understand a kernel oops is a milder form of a kernel panic.
The only difference is that the system doesn't get to a state where the error is completely unrecoverable. Some features stops working but others continue to work as normal. The system might become unstable though and will probably not work as intended.

The problem is (for me) that I have no idea how to diagnose the problem. sad

Last edited by antis (2009-07-29 07:39:46)

Offline

#5 2009-07-29 11:10:56

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

I suppose you could file a bug report for the kernel. They might be able to help. It might also be useful to a do a git bisect on the kernel sources to determine when the problem started.


Website - Blog - arch-home
Arch User since March 2005

Offline

#6 2009-07-29 15:50:02

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

Perhaps you can try the "kernel panics "(method 2) in the wiki which re-installs the kernel and mkinitcpio.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#7 2009-07-29 20:18:05

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

I actually just made a reinstall of the kernel package. I first removed it from the pacman cache and simply did a "pacman -Sy kernel26". To be on the safe side I also reinstalled he nvidia package.

Lo and behold... at the first reboot everything seemed to work and I had no problem starting X. To really makes sure that this was not just a fluke I rebooted again and... there the error was again sad

If the hardware somehow is not supported, I feel that I would never be able to boot. But now, when it works on and off, I really don't have a clue what to do.

Offline

#8 2009-07-29 20:29:52

Pyntux
Member
From: Serbia
Registered: 2008-12-21
Posts: 391

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

This is offtopic, bu just a question for @antis...Why don`t you try to compile kernel old school way? I think its better...

http://wiki.archlinux.org/index.php/Ker … rom_Source

Last edited by Pyntux (2009-07-29 20:30:26)


I do not speak English, but I understand...

Offline

#9 2009-07-29 21:05:31

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

@Pyntux: That has crossed my mind but I really don't know what I could do that the Arch developers hasn't already done. Also, for some one like me who have never compiled a kernel before, it feels like a mountain to climb smile

Offline

#10 2009-07-29 21:13:29

mutlu_inek
Member
From: all over the place
Registered: 2006-11-18
Posts: 683

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

antis, you could try one of the kernels in the AUR, for example kernel26zen-git: http://aur.archlinux.org/packages.php?ID=13900 It is not more difficult that building other PKGUILDs.

This package builds an (unstable) kernel with a nice set of patches. It tracks the most recent release candidates and is therefore most of the time a little ahead of the stable kernel. Right now it is at 2.6.31-rc4.

Of course, unstable software may eat your breakfast. Or your data.

Edit: I just realized that the nvidia module will probably not run with such a recent kernel. sad Scratch that.

Last edited by mutlu_inek (2009-07-29 21:16:19)

Offline

#11 2009-07-29 23:40:47

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

Perhaps your memory is flaky...

Perhaps try changing the chips around.....


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#12 2009-07-30 07:27:40

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

lilsirecho wrote:

Perhaps your memory is flaky...

Perhaps try changing the chips around.....

I have already done that. I have two 2Gb modules and I have tried running both of them separately in both slots but it doesn't matter, I still get the Oops. Maybe the memory isn't at all compatible with the motherboard? I think I will email Zotac and ask.

Again, what is strange is that it all runs well without the nvidia module. With runlevel 3 or with vesa loaded it seems that I can run this machine through the roof without having any problems.

Thanks alot so far for all ideas!

Offline

#13 2009-07-30 10:05:05

connexion2000
Member
Registered: 2006-10-15
Posts: 116

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

As for now, please try to install and use xf86-video-nouveau instead of nvidia driver and tell us if it works as expected. Then you should file a bug report for nvidia or kernel.

Offline

#14 2009-07-30 15:41:49

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

@connexion2000: I installed the nouveau driver and I can launch X alright. I do however see on the nouveau website that the driver is not expected to work on the 9400 series cards which is what I have on the Zotac ionitx-b motherboard.

But as I said, I can get into X without a kernel oops but I don't get the performance out of the driver as I wish. I want to run xbmc but the screen goes black when I start it.

Now I see though, that I get an Oops when issuing "lsmod". Sigh...
I have decided to do this the hard way and install another distro to see what happens.
If that also gives me an oops I'm gonna go to the local park and play some frisbee golf with this motherboard.

Edit: I changed my mind. I will borrow some DDR2 memory from a friend tomorrow to absolutely make sure that this isn't causing the problems. Then I will reinstall... and THEN I will play frisbee golf.

Last edited by antis (2009-07-30 15:47:06)

Offline

#15 2009-07-30 20:18:53

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

Alrighty then. This might be on it's way to being marked as solved.

I browsed the bug section of the Arch website to learn how to file a good kernel bug report. Right at the top I found this: http://bugs.archlinux.org/task/15270

It applies exactly to my problem where my usb wifi dongle uses the rt73 module which seems to be broken. I removed it and have now started X 3-4 times without any errors. Hurray!

I'll keep testing this for a few more days before I really trust that this solves the problem.

Meanwhile, a big thanks to you all for giving me input on this problem.
I really appreciate it!

Offline

#16 2009-08-02 13:43:54

ould
Member
Registered: 2007-05-22
Posts: 124

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

How is the setup working now? I am think of getting the same board and running Arch so want to make sure everything is kosher before I order. I won't be using wifi at all so I will just disable it.

Offline

#17 2009-08-02 15:19:10

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

ould wrote:

How is the setup working now? I am think of getting the same board and running Arch so want to make sure everything is kosher before I order. I won't be using wifi at all so I will just disable it.

It is working very very good.
My plan was to run this set up completely fanless which is why I opted for the single core instead of the 330 dual core. However, I have a pretty small case (Silverstone LC09) and it just gets too hot to not have the cpu fan mounted. With this knowledge I would probably have bought the dual core instead.

Other that that, it plays pretty much everything I have thrown at it. I am yet to try true HD (1080) though but 720-material is no problem. Divx and mp3 is of course a piece of cake.

As far as hardware compatibility goes Arch looks to support everything out of the box. I have done nothing extra in order to get eg vdpau and sound over hdmi to work.

It's a motherboard that is easy to recommend.

Offline

#18 2009-08-03 13:13:21

ould
Member
Registered: 2007-05-22
Posts: 124

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

antis wrote:
ould wrote:

How is the setup working now? I am think of getting the same board and running Arch so want to make sure everything is kosher before I order. I won't be using wifi at all so I will just disable it.

It is working very very good.
My plan was to run this set up completely fanless which is why I opted for the single core instead of the 330 dual core. However, I have a pretty small case (Silverstone LC09) and it just gets too hot to not have the cpu fan mounted. With this knowledge I would probably have bought the dual core instead.

Other that that, it plays pretty much everything I have thrown at it. I am yet to try true HD (1080) though but 720-material is no problem. Divx and mp3 is of course a piece of cake.

As far as hardware compatibility goes Arch looks to support everything out of the box. I have done nothing extra in order to get eg vdpau and sound over hdmi to work.

It's a motherboard that is easy to recommend.

Thanks makes my decision easier, I thought you had the dual core, I guess I misread, I am definitely getting the dual core when the time comes. Is the XBMC interface snappy? That was the only concern I had, I don't generally use a crazy skin like Aeon so I should be ok I think, any comments on skins?

Thanks again,

Kevin

Offline

#19 2009-08-03 15:49:44

antis
Member
From: sweden
Registered: 2007-05-18
Posts: 108

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

We're going off topic here but hey, this is fun! Someone stop us if necessary smile

The interface is quite snappy although Aeon feels a bit heavy. I'm new to xbmc so I'm still testing things out to see what skin, plugins and other features I'll use. PM3HD is working very well as a lightweight example for a skin.

With Openbox running in the background and a handful of daemons also working (sshd, apache etc) the footprint is pretty low. Memory usage is right now 230Mb of (over sized) 4Gb. When at the home screen in xbmc the cpu usage varies between 2-20%. I don't know why it varies so much even though it's not processing anything.

Offline

#20 2009-08-06 19:28:52

ould
Member
Registered: 2007-05-22
Posts: 124

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

antis wrote:

We're going off topic here but hey, this is fun! Someone stop us if necessary smile

The interface is quite snappy although Aeon feels a bit heavy. I'm new to xbmc so I'm still testing things out to see what skin, plugins and other features I'll use. PM3HD is working very well as a lightweight example for a skin.

With Openbox running in the background and a handful of daemons also working (sshd, apache etc) the footprint is pretty low. Memory usage is right now 230Mb of (over sized) 4Gb. When at the home screen in xbmc the cpu usage varies between 2-20%. I don't know why it varies so much even though it's not processing anything.

Thanks for the update. Try out the "Transparency!" skin. It is what I am currently using and love it. Minimal with great looks and functionality.

Hopefully I can order my setup soon and begin tinkering. I think I may try to do a network boot so I don't have to worry about a hard drive. :-)

Offline

#21 2009-10-08 14:50:20

JuanSinMiedo
Member
Registered: 2009-10-08
Posts: 5

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

Hi there.
Would you please publish your Xorg.conf
I'm a newbie in Archlinux. I'm having a few problems with my Zotac ION itx D motherboard. Every time I startx it freezes with a white smal (320x240 more or less) screen on the top left corner (rest is blank). It seems it doesn't load the nvidia driver and goes with vesa. I'd like your Xorg.conf as an example for mine.
Thanks a lot.

Offline

#22 2009-10-08 17:00:58

ould
Member
Registered: 2007-05-22
Posts: 124

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

Are you sure the white box in the corner isn't an Xterm? That is usually what loads in X by default if you have not modified your .xinitrc to load what you want i.e. xbmc/gnome/kde/whatever... in any event here is my xorg.conf for your reference.

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder57)  Fri Jul 31 22:36:17 PDT 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option         "HWCursor"  "false"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "NoLogo" "True"
    Option      "TwinView" "0"
    Option      "DynamicTwinView" "0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

as you can see it is very basic.

Hope it helps,

Kevin

Offline

#23 2009-10-25 10:50:31

JuanSinMiedo
Member
Registered: 2009-10-08
Posts: 5

Re: [Solved] Kernel Oops continues. Need help from someone who know this..

Thanks a lot Kevin. It helped. Finally I got Xterm working (it was that screen, but I had it frozen).
Now I have another problem starting XBMC, but I've opened another thread (don't want to kidnapp this one).
If you'd like to take a look it's: http://bbs.archlinux.org/viewtopic.php? … 48#p643448

As I said, thanks for your help.

Last edited by JuanSinMiedo (2009-10-25 10:52:25)

Offline

Board footer

Powered by FluxBB