Bug #2641

Panic when loading natapci as module

Added by tuxillo 2 months ago. Updated 2 months ago.

Status:NewStart date:02/17/2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Feature request
Target version:3.8.0

Description

Hi,

DragonFly v3.7.1.703.gfeabe-DEVELOPMENT

A panic occurs after loading natapci as module:

>Tue Feb 18 00:04:45 UTC 2014
atapci0: <nVidia nForce MCP61 SATA300 controller> port 0xc880-0xc88f,0xcc00-0xcc03,0xd000-0xd007,0xd080-0xd083,0xd400-0xd407 mem 0xfbdfc000-0xfbdfcfff irq 21 at device 8.0 on pci0

Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic->id = 00000000
fault virtual address = 0x38
fault code = supervisor read data, page not present
instruction pointer = 0x8:0xffffffff80715b92
stack pointer = 0x10:0xffffffe0644eb560
frame pointer = 0x10:0xffffffe0644eb568
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 1714
current thread = pri 6
kernel: type 12 trap, code=0

CPU0 stopping CPUs: 0x00000002
stopped
Physical memory: 2007 MB
Dumping 495 MB: 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 1

This panic occurred while trying to debug a ATA timeout problem. natapci was built and loaded as module from a customer kernel with no NATA compiled in.

Dump available on: http://leaf.dragonflybsd.org/~tuxillo/archive/crash/natapci_load.txz

Best regards,
Antonio Huete

History

#1 Updated by swildner 2 months ago

  • Category changed from Driver to Feature request

Also available in: Atom PDF