Further debugging

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Further debugging

bv_arvind
Hi,

I experience a double fault and I dont see a core dump happening. I checked
the params for core file generation seem to be fine. Not sure how to
collect further information. Any pointers will be helpful.

 Trying to mount root from ufs:/dev/ad0s1d
WARNING: / was not properly dismounted

Fatal double fault
rip = 0xffffffff804c5128
rsp = 0xfffffffeb3cb4ff8
rbp = 0xfffffffeb3cb5010
cpuid = 0; apic id = 00
kernel trap 12 with interrupts disabled
ÿÿÿÿÖnÿÿÿÿ) held by 0xffffff0028f0c350 (tid 100022) too long
Process name: irq28: xenpci0
Backtrace:
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled

With image built using debug kernel, this is where the debugger stopped and
backtrace appears as follows:

Trying to mount root from ufs:/dev/ad0s1d

db> ?
Bad character
?
db> bt
Tracing pid 23 tid 100022 td 0xffffff0028f0c350
kdb_enter() at kdb_enter+0x41
panic() at panic+0x26d
_mtx_lock_sleep() at _mtx_lock_sleep+0x181
_mtx_lock_flags() at _mtx_lock_flags+0xa1
trap_pfault() at trap_pfault+0xeb
trap() at trap+0x2fa
calltrap() at calltrap+0x8
--- trap 0xc, rip = 0xffffffff806d0f2d, rsp = 0xffffffff9457e3c0, rbp =
0xffffffff9457e3d0 ---
ffo_disable_com2() at ffo_disable_com2+0xd
panic() at panic+0x230
_mtx_lock_sleep() at _mtx_lock_sleep+0x181
_mtx_lock_flags() at _mtx_lock_flags+0xa1
trap_pfault() at trap_pfault+0xeb
trap() at trap+0x2fa
calltrap() at calltrap+0x8
--- trap 0xc, rip = 0xffffffff806d0f2d, rsp = 0xffffffff9457e730, rbp =
0xffffffff9457e740 ---
ffo_disable_com2() at ffo_disable_com2+0xd
panic() at panic+0x230
_mtx_lock_sleep() at _mtx_lock_sleep+0x181

However this doesnt look like a real reson for faulting

Thanks
Arvind
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "[hidden email]"