/arch/amd64/compile/GENERIC.MP
real mem = 34246377472 (32659MB)
avail mem = 33191153664 (31653MB)
kernel: page fault trap, code = 0
Stopped at SHA512Final: addb %al,0(%rax)
ddb{0}>
ddb{0}> trace
SHA512Final(8271bdf0,8271bd20,2bc11015d414a77c,4b2d3f50a8f5a93c,77ff031..more
kernel: page fault trap, code=0
Stopped at worklist_print+0x26b: addb%al,acpi_pdirpa+0xbfeeac0
ddb trace
worklist_print() at worklist_print+0x26b
ffs_init() at ffs_init+0xa4
vfs_register() at vfs_register+0x94
vfsinit() at vfsinit+0x80
main() at main+0x457
end trace frame: 0x0, count
On Monday, November 24, 2014, Nikos Skalkotos skalk...@grnet.gr wrote:
On 23/11/14 06:27, Philip Guenther wrote:
...
Note the cssize (cylinder summary size) has grown but csaddr hasn't
changed. That means it probably had to relocate allocated blocks. This
being your root disk, it may
I just tried this too. Same result.
Anyway, it is 100% replicable here. Can anybody else confirm this? I
just did an 1G installation of OpenBSD, then I dd-ed the 1G file
(logical block device) to a 100G one. I did all the steps I mentioned
above in rescue mode and corrupted the file system.
-filled,
which it might not be. It may be a good test to try zeroing the new area
with dd before running growfs and see if that makes it behave correctly.
uvm_fault(0x81d97be0, 0x8d2a5811, 0, 2) - e
kernel: page fault trap, code=0
Stopped at worklist_print+0x26b: addb
head, 18 sec
fd1 at fdc0 drive 1: density unknown
uvm_fault(0x81d97be0, 0x8d2a5811, 0, 2) - e
kernel: page fault trap, code=0
Stopped at worklist_print+0x26b: addb%al,acpi_pdirpa+0xbfeeac0
ddb trace
worklist_print() at worklist_print+0x26b
ffs_init() at ffs_init+0xa4
: [] a
Then grow the underlying FFS file system:
# growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something
(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Thank you in advance,
Nikos Skalkotos
What does fsck say after you have grown the fs?
Yoy probably need
file system:
# growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel
the underlying FFS file system:
growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something
the underlying FFS file system:
growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something
file system:
growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs
then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Didn't you read the manual page
On Tue, Nov 11, 2014 at 5:43 AM, Nikos Skalkotos skalk...@grnet.gr wrote:
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition
Hello,
Is there a way to output the rescue disk console on a serial port? It
will help for the copy-paste because I don't have physical access to
the server I'm running the VM's and I'm using VNC to grab the console.
On 11 November 2014 22:21, Philip Guenther guent...@gmail.com wrote:
On Tue,
Can't you make the kvm run the console as a serial and then telnet or
something to get that serial output from the guest?
2014-11-11 22:12 GMT+01:00 Nikos Skalkotos skalk...@gmail.com:
Hello,
Is there a way to output the rescue disk console on a serial port? It
will help for the copy-paste
* Marcin Wilk nic...@nicram.sytes.net [2010-02-12 10:04]:
uvm_fault(0xd0891180, 0x4000, 0, 3) -e
kernel: page fault trap, code=0
Stopped at pf_state_key_detach+0x40: movl %eax0,4(%ecx)
ddb{0}
dmesg:
OpenBSD 4.6 (NICRAM.MP) #0: Wed Feb 10 12:10:36 CET 2010
get stable. and use GENERIC
there was problem:
uvm_fault(0xd0891180, 0x4000, 0, 3) -e
kernel: page fault trap, code=0
Stopped at pf_state_key_detach+0x40: movl %eax0,4(%ecx)
ddb{0}
The problem is i cannot make trace in ddb because computer freeze then
and it do not
respond on anything. After reset i cannot also find any core
Running Aug 24 snapshot, kismet has been running fine many times over
the past day.
Now, just ran it and got the following:
Source 0 (dlink): Opening radiotap_bsd_b source interface rtw0...
Uvm_fault(0xd0598480, 0xd0a25000, 0 1) - e
Kernel: page fault trap, code=0
Stopped at strcmp+0xc: movb 0
On Fri, Aug 26, 2005 at 11:27:38AM -0400, Will H. Backman wrote:
Source 0 (dlink): Opening radiotap_bsd_b source interface rtw0...
Uvm_fault(0xd0598480, 0xd0a25000, 0 1) - e
Kernel: page fault trap, code=0
Stopped at strcmp+0xc: movb 0(%eax),%cl
ddb
Not sure what I should do to capture
-Original Message-
From: Matthias Kilian [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 12:47 PM
To: Will H. Backman
Cc: misc@openbsd.org
Subject: Re: kernel: page fault trap
On Fri, Aug 26, 2005 at 11:27:38AM -0400, Will H. Backman wrote:
Source 0 (dlink): Opening
21 matches
Mail list logo
