Kernel panic on boot at dm_crypt
Stefan Unterweger
232.20711 at chiffre.aleturo.com
Wed Sep 14 06:36:59 PDT 2016
Just a heads-up: I still get pretty much the same problems with
50787d03cd0a. I think it got worse between 4.6 and 4.7 (50787d03cd0a),
but I am not really sure—could also be coincidental.
It’s not as bad as when I originally reported it, but still nasty
enough. The panics are the same (see screenshots), only with different
addresses.
| Fatal trap 12: page fault while in kernel mode
| cpuid = 0; lapic->id = 00000000
| fault virtual address = 0x0
| fault code = supervisor write data, page not present
| instruction pointer = 0x8:0xffffffff80601202
| stack pointer = 0x10:0xffffffe09f84b810
| frame pointer = 0x10:0xffffffe09f84b850
| code segment = base 0x0, limit 0xfffff, type 0x1b
| = DPL 0, pres 1, long 0, def32 0, gran 1
| processor eflags = interrupt enabled, resume, IOPL = 0
| current process = Idle
| current thread = pri 28 (CRIT)
| kernel: type 12 trap, code=0
|
| CPU0 stopping CPUs: 0x00000002
| stopped
| Stopped at mpipe_alloc_callback+0x13d: movq %rcx,(%rax)
| db>
When I try to add LUKS keys once the machine is running, I get a
slightly different panic:
| Fatal trap 9: general protection fault while in kernel mode
| cpuid = 0; lapic->id = 00000000
| instruction pointer = 0x8:0xffffffff805f54ac
| stack pointer = 0x10:0xffffffe09f84b7a0
| frame pointer = 0x10:0xffffffe09f84b7f0
| code segment = base 0x0, limit 0xfffff, type 0x1b
| = DPL 0, pres 1, long 0, def32 0, gran 1
| processor eflags = interrupt enabled, resume, IOPL = 0
| current process = Idle
| current thread = pri 28 (CRIT)
| kernel: type 9 trap, code=0
|
| CPU0 stopping CPUs: 0x00000002
| stopped
| Stopped at objcache_get+0x75: addl $0x1,0xd0(%r12)
| db>
This is a test machine. I can reliably provoke the panic and can
test any patches relatively quickly now. :o)
Thanks,
Stefan
* Stefan Unterweger on Wed, Jul 06, 2016 at 01:04:47AM +0200:
> Since I’m currently stuck staring at rebooting screeny anyway, I thought
> I might as well copy the contents of the kernel page as plain text, for
> easier reference. I hope I haven’t mistyped too many of those horribly
> long memory addresses in the process.
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; lapic->id = 00000000
> fault virtual address = 0xffffffe07ff40318
> fault code = supervisor write data, page not present
> instruction pointer = 0x8:0xffffffff80606056
> stack pointer = 0x10:0xffffffe0b6140810
> frame pointer = 0x10:0xffffffe0b6140850
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 0, def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = Idle
> current thread = pri 28 (CRIT)
> kernel: type 12 trap, code=0
>
> CPU0 stopping CPUs: 0x0000000e
> stopped
> Stopped at mpipe_alloc_callback+0x13d: movq %rcv,(%rax)
> db>
--
▪ Die Internetbleibe. Schick, magisch, leistungsstark. https://internetbleibe.de/
▪ medoly media UG (haftungsbeschränkt) | Hausburgstraße 13, 10249 Berlin
▪ info at medolymedia.de | https://medolymedia.de/ | Tel. 030 609 826‒560 | Fax …‒569
▪ Geschäftsführer: Matthias Nothhaft | HRB 131198 (Amtsgericht Berlin-Charlottenburg), Sitz: Berlin, USt-ID: DE275221203
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 5GIe+bh13 ? ledostar at nur-ab-sal xwd-#00062.png
Type: image/png
Size: 29634 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20160914/a002b918/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 5GIe+bh13 ? ledostar at nur-ab-sal xwd-#00063.png
Type: image/png
Size: 28576 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20160914/a002b918/attachment-0013.png>
More information about the Users
mailing list