This is very interested "the kernel did non panic". Where is memcmp in
sys? When I run bsd.rd end mount filesystem I can't find memcmp.
------------------------------------------------
http://wklej.org/hash/e5591ccc88f/
.
.
.
cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
uvm_fault(0xd0c230c0, 0xd0f2f000, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at memcmp+0x11: repe cmpsl (%esi),%es:(%edi)
------------------------------------------------
ddb> show panic
the kernel did not panic
------------------------------------------------
ddb> trace
memcmp(d3182800,681,9,1b) at memcmp+0x11
k7_powernow_init(d31810c0,d0ec2f08,d022931e,d0c70730,d0a217fd) at
k7_powernow_i
nit+0xf8
amd_family6_setperf_setup(d0c70730) at amd_family6_setperf_setup+0x1c
mainbus_attach(0,d31810c0,0) at mainbus_attach+0x15e
config_attach(0,d0c0335c,0,0) at config_attach+0x184
config_rootfound(d09cb92c,0) at config_rootfound+0xc0
cpu_configure(944dfcd2,ec0000,ecf000,0,d02004ce) at cpu_configure+0x29
main(0,0,0,0,0) at main+0x478
ddb>
------------------------------------------------
Regards,
Krzych
W dniu 14.10.2017 o 11:58, Philip Guenther pisze:
On Fri, Oct 13, 2017 at 12:21 PM, Krzysztof Strzeszewski
<[email protected] <mailto:[email protected]>> wrote:
When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic.
It's unfortunate that no one has submitted to [email protected]
<mailto:[email protected]> the dmesg from that hardware since February
2016. Please consider doing so every time you upgrade your kernel, so
that we have a record of what is working.
...
cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
uvm_fault(0xd0c589b0, 0xd0f32000, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at memcmp+0x11: repe cmpsl (%esi),%es:(%edi)
ddb>
https://www.openbsd.org/ddb.html
Without a backtrace, all we can see is that a copy operation in the
kernel faulted, with no indication of *which* copy operation did so.
Philip Guenther
