Sorry hit enter before I was done typing, message continues:
On 9/5/07, Rob Hussey <robjhussey@xxxxxxxxx> wrote:
> I receive a kernel panic with rt2500pci built-in, but if built as a
> module, I can insmod it without problem. I don't have a serial
> console, and I tried to capture the panic with netconsole (using a
> different interface of course) but the panic happens immediately after
> rt2500pci is initialized, or in other words, too soon for netconsole.
>
> I'd rather not copy over everything unless necessary. Here's the first portion:
>
> ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 18
> phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 0201, rf: 0003,
> rev: 00000004
> WARNING: at lib/kref.c:33 kref_get()
> [<c0229da9>] kref_get+0x3d/0x44
kobject_get
kobject_shadow
kobject_set_name
device_add
wiphy_register
ieee80211_register_hw
rt2x00lib_probe_dev
rt2x00pci_probe
pci_match_device
pci_device_probe
driver_probe_device
klist_next
__driver_attach
bus_for_each_dev
driver_attach
__driver_attach
bus_add_driver
__pci_register_driver
kernel_init
... can't type everything... skipping
BUG: unable to handle kernel NULL pointer dereference at virtual
address 00000024
printing eip:
c01a9966
*pde = 00000000
Oops: 0000 [#1]
PREEMPT SMP
Modules linked in:
CPU: 1
EIP: 0060:[<c01a9966>] Not tainted VLI
EIP is at sysfs_addrm_start+0x21/0x87
skipping...
Call Trace:
create_dir
sysfs_create_dir
kobject_get
kobject_shadow_add
kobject_set_name
device_add
wiphy_register
ieee80211_register_hw
rt2x00lib_prove_dev
rt2x00pci_probe
pci_match_device
pci_device_probe
driver_probe_device
klist_next
__driver_attach
bus_for_each_dev
driver_attach
__driver_attach
bus_add_driver
__pci_register_driver
kernel_init
schedule_tail
ret_from_fork
kernel_init
kernel_init
kernel_thread_helper
...
Kernel panic - not syncing: Attempting to kill init!
I likely left out important parts, if so, just tell me and I'll try to
post them.
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
