Opened 6 years ago
Closed 5 years ago
#14866 closed bug (duplicate)
KDL on boot: PANIC: _mutex_lock(): using uninitialized lock 0xd2054304
Reported by: | pulkomandy | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Network & Internet/Stack | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | #15024 | Blocking: | |
Platform: | All |
Description
[ipro1000] (em) bus_alloc_resource(3, [20], 0x0, 0xffffffff, 0x1,0x2) add_memory_type_range(7423, 0xf252b000, 0x1000, 0) set MTRRs to: mtrr: 0: base: 0xdac00000, size: 0x400000, type: 0 mtrr: 1: base: 0xf0000000, size: 0x10000000, type: 0 mtrr: 2: base: 0xe0000000, size: 0x20000000, type: 1 [ipro1000] (em) using 1024 tx descriptors and 1024 rx descriptors [ipro1000] (em) msix_init qsets capped at 1 [ipro1000] (em) bus_alloc_resource(3, [28], 0x0, 0xffffffff, 0x1,0x2) [ipro1000] (em) Unable to map MSIX table allocate_io_interrupt_vectors: allocated 1 vectors starting from 27 msi_allocate_vectors: allocated 1 vectors starting from 27 [ipro1000] (em) Using an MSI interrupt [ipro1000] (em) allocated for 1 tx_queues [ipro1000] (em) allocated for 1 rx_queues [ipro1000] (em) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x6) msi enabled: 0x0081 if_attach 0xd21facd8 ifmedia_add: Adding Entry... Type: Ethernet SubType: 10baseT/UTP ifmedia_add: Adding Entry... Type: Ethernet SubType: 10baseT/UTP Shared Option[0]: full-duplex ifmedia_add: Adding Entry... Type: Ethernet SubType: 100baseTX ifmedia_add: Adding Entry... Type: Ethernet SubType: 100baseTX Shared Option[0]: full-duplex ifmedia_add: Adding Entry... Type: Ethernet SubType: 1000baseT Shared Option[0]: full-duplex ifmedia_add: Adding Entry... Type: Ethernet SubType: 1000baseT ifmedia_add: Adding Entry... Type: Ethernet SubType: autoselect ifmedia_set: target Type: Ethernet SubType: autoselect ifmedia_set: setting to Type: Ethernet SubType: autoselect ipro1000: init_driver(0x806c1820) loaded driver /boot/system/add-ons/kernel/drivers/dev/net/ipro1000 etherpci: init_driver init_driver: etherpci not found [net/ipro1000/0] compat_open(0x2) register_domain(4, link) PANIC: _mutex_lock(): using uninitialized lock 0xd2054304 Welcome to Kernel Debugging Land... Thread 609 "/dev/net/iprowifi4965/0 consume" running on CPU 2 stack trace for thread 609 "/dev/net/iprowifi4965/0 consume" kernel stack: 0x806d3000 to 0x806d7000 frame caller <image>:function + offset 0 806d6db8 (+ 32) 8014a9da <kernel_x86> arch_debug_stack_trace + 0x12 1 806d6dd8 (+ 16) 800a78e7 <kernel_x86> stack_trace_trampoline(NULL) + 0x0b 2 806d6de8 (+ 12) 8013c4c2 <kernel_x86> arch_debug_call_with_fault_handler + 0x1b 3 806d6df4 (+ 48) 800a9370 <kernel_x86> debug_call_with_fault_handler + 0x60 4 806d6e24 (+ 64) 800a7afb <kernel_x86> kernel_debugger_loop(0x8018e517 "PANIC: ", 0x801894c0 "_mutex_lock(): using uninitialized lock %p", 0x806d6ed0 "CÒÌÌÌ̆", int32: 2) + 0x20f 5 806d6e64 (+ 48) 800a7e9f <kernel_x86> kernel_debugger_internal(0x8018e517 "PANIC: ", 0x801894c0 "_mutex_lock(): using uninitialized lock %p", 0x806d6ed0 "CÒÌÌÌ̆", int32: 2) + 0x77 6 806d6e94 (+ 48) 800a96f2 <kernel_x86> panic + 0x3a 7 806d6ec4 (+ 80) 800959da <kernel_x86> _mutex_lock + 0xea 8 806d6f14 (+ 64) 811243c9 </boot/system/add-ons/kernel/network/stack> fifo_dequeue_buffer(net_fifo*: 0xd2054304, uint32: 0x0 (0), int64: 9223372036854775807, net_buffer*: 0x806d6f9c) + 0x31 9 806d6f54 (+ 96) 81111a4e </boot/system/add-ons/kernel/network/stack> device_consumer_thread(0xd2054298) + 0x172 10 806d6fb4 (+ 48) 8008703e <kernel_x86> common_thread_entry(0x806d6ff0) + 0x3a
I had serial logging enabled, in case that makes a difference.
Change History (2)
comment:1 by , 6 years ago
Component: | Drivers/Network/iprowifi4965 → Network & Internet/Stack |
---|---|
Owner: | changed from | to
comment:2 by , 5 years ago
Blocked By: | 15024 added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
net_fifo objects and their locks are fully managed by the stack; they are fed by calling read() on the device, but that's it. So this isn't a driver bug.