#263076108 EFI RT page fault in init pid = 1

such a message at shutdown : > >> > >> > >> > >> Fatal trap 12: page fault while in kernel mode > >> cpuid = 0; apic id = 00 > >> fault virtual address = 0x0 > >> fault code = supervisor read data, page not present > >> instruction pointer = 0

Re: EFI RT page fault in init pid = 1

On 1/4/25 06:45, Konstantin Belousov wrote: On Fri, Jan 03, 2025 at 06:43:55PM -0500, Dennis Clarke wrote: I wonder if anyone else has seen such a message at shutdown : Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code

Re: EFI RT page fault in init pid = 1

On Fri, Jan 03, 2025 at 06:43:55PM -0500, Dennis Clarke wrote: > > I wonder if anyone else has seen such a message at shutdown : > > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x0 > fault code

Re: EFI RT page fault in init pid = 1

On Fri, 3 Jan 2025 18:43:55 -0500 Dennis Clarke wrote: > > I wonder if anyone else has seen such a message at shutdown : > > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x0 > fault code = sup

EFI RT page fault in init pid = 1

I wonder if anyone else has seen such a message at shutdown : Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0x7c38f87a stack pointer

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

e.  Unfortunately the backtrace does not tell what was the > callout.  When was the previous update to look what could change? > > On 10.12.2021 11:24, Larry Rosenman wrote: >> FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #15 >> main-n251537-ab639f2398b: Thu Dec

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

t; FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #15 >> main-n251537-ab639f2398b: Thu Dec  9 19:45:37 CST 2021 >> r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL >> amd64 >> >> VMCORE *IS* available. >> >> >> >&

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

te to look what could change? > > On 10.12.2021 11:24, Larry Rosenman wrote: >> FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #15 >> main-n251537-ab639f2398b: Thu Dec  9 19:45:37 CST 2021 >> r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL 

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

available. > >> > >> > >> > >> > >> Unread portion of the kernel message buffer: > >> kernel trap 12 with interrupts disabled > >> > >> > >> Fatal trap 12: page fault while in kernel mode > >>

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

code segment    = base 0x0, limit 0xf, type 0x1b     = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags    = resume, IOPL = 0 current process = 82990 (c++) trap number = 12 panic: page fault cpuid = 0 time = 163998 KDB: stack backtrac

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

51537-ab639f2398b: Thu Dec  9 19:45:37 CST 2021 r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL  amd64 VMCORE *IS* available. Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

    r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL  amd64 VMCORE *IS* available. Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 20 fault virtual address   = 0x0 fault

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 20 > fault virtual address   = 0x0 > fault code  = supervisor write data, page not present > instruction pointer = 0x20:0x804e0db4 > stack p

Panic: Page Fault in Kernel: Yesterday's CURRENT

interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 20 fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x20:0x804e0db4 stack pointer = 0x0:0xfe0434de4e10 frame pointer

Re: page fault due to close(2), possibly drm and i915kms related

On Thu, 3 Dec 2020 11:45+0100, Mateusz Guzik wrote: > This should be fixed by r368271 Thank you, guys. I'll upgrade my laptop when I get home. -- Trond. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-cur

Re: page fault due to close(2), possibly drm and i915kms related

On 12/3/20 11:43 AM, Trond Endrestøl wrote: [160176] --- trap 0xc, rip = 0x808cbd2c, rsp = 0xfe018500e700, rbp = 0xfe018500e780 --- [160176] __mtx_lock_sleep() at 0x808cbd2c = __mtx_lock_sleep+0xfc/frame 0xfe018500e780 [160176] doselwakeup() at 0x8095fbee = d

Re: page fault due to close(2), possibly drm and i915kms related

Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > [160176] > [160176] > [160176] Fatal trap 12: page fault while in kernel mode > [160176] cpuid = 0; apic id = 00 >

page fault due to close(2), possibly drm and i915kms related

nditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: [160176] [160176] [160176] Fatal tr

Re: "panic: page fault" in iwn signal handler(?) at r367127

On Fri, 2020-10-30 at 05:37 -0700, David Wolfskill wrote: > I've copied the dump and core.txt files to > http://www.catwhisker.org/~david/FreeBSD/head/r367127/ > > Here's a copy/paste of the stack trace (from the core.txt.3 file): > p 12: page fault while in kernel mode

Re: "panic: page fault" in iwn signal handler(?) at r367127

On Fri, 2020-10-30 at 05:37 -0700, David Wolfskill wrote: > I've copied the dump and core.txt files to > http://www.catwhisker.org/~david/FreeBSD/head/r367127/ > > Here's a copy/paste of the stack trace (from the core.txt.3 file): > p 12: page fault while in kernel mode

"panic: page fault" in iwn signal handler(?) at r367127

I've copied the dump and core.txt files to http://www.catwhisker.org/~david/FreeBSD/head/r367127/ Here's a copy/paste of the stack trace (from the core.txt.3 file): p 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0xf8084000 fault code =

Re: Possible deadlock on IO / page fault

On Tue, Sep 29, 2020 at 04:35:47PM +0300, Michael Zhilin wrote: > Thank you, Kostya and Mark! > I will update to head. :) Be sure to pick up r366252 or later: there is a related bug in the initial OpenZFS import that is fixed by that revision. > On Tue, Sep 29, 2020 at 4:32 PM Mark Johnston wrot

Re: Possible deadlock on IO / page fault

Thank you, Kostya and Mark! I will update to head. :) On Tue, Sep 29, 2020 at 4:32 PM Mark Johnston wrote: > On Tue, Sep 29, 2020 at 04:20:26PM +0300, Konstantin Belousov wrote: > > On Tue, Sep 29, 2020 at 02:59:43PM +0300, Michael Zhilin wrote: > > > Hi, > > > > > > I'm using FreeBSD 13-CURRENT

Re: Possible deadlock on IO / page fault

On Tue, Sep 29, 2020 at 04:20:26PM +0300, Konstantin Belousov wrote: > On Tue, Sep 29, 2020 at 02:59:43PM +0300, Michael Zhilin wrote: > > Hi, > > > > I'm using FreeBSD 13-CURRENT (pre-ZoF, r359724) on my laptop with installed > > Gnome. Sometimes > > (once a week/month) gnome hangs and the system

Re: Possible deadlock on IO / page fault

n() at fast_syscall_common+0x101/frame > 0xfe00b0708bf0 > --- syscall (33, FreeBSD ELF64, sys_access), rip = 0x800fd0eba, rsp = > 0x7fffe268, rbp = 0x7fffe380 --- > > All other locked threads look more interesting. Thread 100747 is trying to > write > into file a

Possible deadlock on IO / page fault

call (33, FreeBSD ELF64, sys_access), rip = 0x800fd0eba, rsp = 0x7fffe268, rbp = 0x7fffe380 --- All other locked threads look more interesting. Thread 100747 is trying to write into file and waiting for page, but thread 101436 is trying to handle page fault and waiting for a shared lock of lo

Re: panic: page fault head/amd64 @r361830

On Fri, Jun 05, 2020 at 06:41:27AM -0700, David Wolfskill wrote: > My build machine had no issues with the upgrade from r361784 to r361830, > but my laptop panicked during the transition from single- to multi-user > mode, just after bpf was attached. > . Thanks to Hans Petter Selasky (who aske

Re: panic: page fault head/amd64 @r361830

RUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED <118>Feeding entropy: . <6>wlan0: bpf attached <6>wlan0: bpf attached Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x0 fault code = supervisor read instru

panic: page fault head/amd64 @r361830

ATTACH,CACHED <118>Feeding entropy: . <6>wlan0: bpf attached <6>wlan0: bpf attached Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x0 fault code = supervisor read instruction, page not present instruction pointer

Re: Page fault in midi/sequencer.c

On Mon, Oct 22, 2018 at 11:00:41AM +0200, Hans Petter Selasky wrote: > On 10/20/18 6:56 PM, Peter Holm wrote: > > I can trigger this on 13.0-CURRENT r339445 with a non-root test program: > > > > Hi, > > The following commits should fix the issues you experience: > > https://svnweb.freebsd.org/c

Re: Page fault in midi/sequencer.c

On 10/20/18 6:56 PM, Peter Holm wrote: I can trigger this on 13.0-CURRENT r339445 with a non-root test program: Hi, The following commits should fix the issues you experience: https://svnweb.freebsd.org/changeset/base/339581 https://svnweb.freebsd.org/changeset/base/339582 https://svnweb.fre

Re: Page fault in midi/sequencer.c

kern_pwritev+0x5f #7 0x80c0277d at sys_pwrite+0x8d #8 0x81070af7 at amd64_syscall+0x2a7 #9 0x8104a4ad at fast_syscall_common+0x101 Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex seqflq (seqflq) r = 0 (0xf80003860c08) locked @ dev/sound

Re: Page fault in midi/sequencer.c

#5 0x80c02a87 at dofilewrite+0x97 > #6 0x80c0287f at kern_pwritev+0x5f > #7 0x80c0277d at sys_pwrite+0x8d > #8 0x81070af7 at amd64_syscall+0x2a7 > #9 0xffff8104a4ad at fast_syscall_common+0x101 > Kernel page fault with the following non-sleepable lo

Page fault in midi/sequencer.c

sys_pwrite+0x8d #8 0x81070af7 at amd64_syscall+0x2a7 #9 0x8104a4ad at fast_syscall_common+0x101 Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex seqflq (seqflq) r = 0 (0xf80003860c08) locked @ dev/sound/midi/sequencer.c:952 stack backtrace: #0

Re: udp6: Page fault panics

On 9/17/18 4:17 AM, Andrey V. Elsukov wrote: > On 16.09.2018 03:04, Larry Rosenman wrote: >> vpanic() at vpanic+0x1a3/frame 0xfe00ca17c150 >> panic() at panic+0x43/frame 0xfe00ca17c1b0 >> trap_fatal() at trap_fatal+0x35f/frame 0xfe00ca17c200 >> trap_pfault() at trap_pfault+0x49/frame 0x

Re: udp6: Page fault panics

On 16.09.2018 03:04, Larry Rosenman wrote: > vpanic() at vpanic+0x1a3/frame 0xfe00ca17c150 > panic() at panic+0x43/frame 0xfe00ca17c1b0 > trap_fatal() at trap_fatal+0x35f/frame 0xfe00ca17c200 > trap_pfault() at trap_pfault+0x49/frame 0xfe00ca17c260 > trap() at trap+0x2ba/frame 0xfff

Re: udp6: Page fault panics

On 9/15/18 8:04 PM, Larry Rosenman wrote: > I've got 2 of these: > > Fatal trap 12: page fault while in kernel mode > cpuid = 4; apic id = 04 > fault virtual address = 0x7c > fault code = supervisor read data, page not present > instruction pointer

udp6: Page fault panics

I've got 2 of these: Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x7c fault code = supervisor read data, page not present instruction pointer = 0x20:0x80631428 stack pointer = 0x28:0xfe00ca17c440

Re: page fault in ip6_output

Quoting Sean Bruno (from Sun, 2 Sep 2018 08:52:11 -0600): I think, you have hit this, no? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230950 Looks like it. I've added me to the CC list of the PR. Thanks, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2

Re: page fault in ip6_output

inferior *find_inferior_pid(int): > Assertion `pid != 0' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Create a core file of GDB? (y or n) [answered Y; input not from terminal] > Abort trap (core dumped) > ---snip--- > > ke

page fault in ip6_output

unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] Abort trap (core dumped) ---snip--- kernel panic: ---snip--- Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 5; apic id = 13 fault virtual addres

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Wed, 29 Aug 2018 11:21:05 +0200 Michael Gmelin wrote: > On Sun, 26 Aug 2018 16:04:35 +0300 > Konstantin Belousov wrote: > > > On Sat, Aug 25, 2018 at 07:21:28PM +0200, Michael Gmelin wrote: > > > Now, with the patch applied correctly, the machine actually boots. > > > > > > Before call

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Sun, 26 Aug 2018 16:04:35 +0300 Konstantin Belousov wrote: > On Sat, Aug 25, 2018 at 07:21:28PM +0200, Michael Gmelin wrote: > > Now, with the patch applied correctly, the machine actually boots. > > > > Before calling init_ops.mp_bootaddress in > > getmemsize (machdep.c), physmap looks li

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Sat, Aug 25, 2018 at 07:21:28PM +0200, Michael Gmelin wrote: > Now, with the patch applied correctly, the machine actually boots. > > Before calling init_ops.mp_bootaddress in > getmemsize (machdep.c), physmap looks like this: > > physmap_idx: 8 > i mem atop > 0 0x0 0x0 > 1 0x3 0x30 > 2 0x

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

>> On 24. Aug 2018, at 22:39, Konstantin Belousov wrote: >> >> On Fri, Aug 24, 2018 at 10:32:06PM +0200, Michael Gmelin wrote: >> >> >>> On 24. Aug 2018, at 21:59, Konstantin Belousov wrote: >>> Please apply the following debugging patch on top of the previous 'fix'. >>> You need debug.late

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Fri, Aug 24, 2018 at 10:32:06PM +0200, Michael Gmelin wrote: > > > > On 24. Aug 2018, at 21:59, Konstantin Belousov wrote: > > Please apply the following debugging patch on top of the previous 'fix'. > > You need debug.late_console=0. > > Unfortunately debug.late_console=0 doesn???t work on

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 24. Aug 2018, at 21:59, Konstantin Belousov wrote: > >> On Thu, Aug 23, 2018 at 12:10:34AM +0200, Michael Gmelin wrote: >> >> On 22. Aug 2018, at 23:15, Konstantin Belousov wrote: On Wed, Aug 22, 2018 at 10:03:54PM +0200, Michael Gmelin wrote: >> On 22. A

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Thu, Aug 23, 2018 at 12:10:34AM +0200, Michael Gmelin wrote: > > > > On 22. Aug 2018, at 23:15, Konstantin Belousov wrote: > > > >> On Wed, Aug 22, 2018 at 10:03:54PM +0200, Michael Gmelin wrote: > >> > >> > On 22. Aug 2018, at 17:46, Konstantin Belousov > wrote: > >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 22. Aug 2018, at 23:15, Konstantin Belousov wrote: > >> On Wed, Aug 22, 2018 at 10:03:54PM +0200, Michael Gmelin wrote: >> >> On 22. Aug 2018, at 17:46, Konstantin Belousov wrote: On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote: >> On 20. A

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Wed, Aug 22, 2018 at 10:03:54PM +0200, Michael Gmelin wrote: > > > > On 22. Aug 2018, at 17:46, Konstantin Belousov wrote: > > > >> On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote: > >> > >> > On 20. Aug 2018, at 17:09, Konstantin Belousov > wrote: > >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 22. Aug 2018, at 17:46, Konstantin Belousov wrote: > >> On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote: >> >> On 20. Aug 2018, at 17:09, Konstantin Belousov wrote: On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote: See here for a

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote: > > > > On 20. Aug 2018, at 17:09, Konstantin Belousov wrote: > > > >> On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote: > >> > >> See here for a screenshot (also including the output of "show pte > >> 0xf8000100

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 20. Aug 2018, at 17:09, Konstantin Belousov wrote: > >> On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote: >> >> See here for a screenshot (also including the output of "show pte >> 0xf8000100"): >> >> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658#

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote: > > See here for a screenshot (also including the output of "show pte > 0xf8000100"): > > https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658#file-ddb1-png It is too early for ddb routines to register. Ok can you

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

060 0x100600 > > 10 0x0 0x0 > > mptramp_pagetables is 0x4 > > > > So a three page gap was made at 0x4 (atop(idx 2) is now 0x43 > > instead of 0x40) > > > > In the current version (using atop), the loop in mp_bootaddress > > looks like

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

ysmap[i], physmap[i + 1], atop(physmap[i + 1]), Maxmem > 8 0x1 0x10060 0x100600 0x100600 > 6 0x100 0x7bf7a000 0x7bf7a 0x100600 > > And physmap looks like this afterwards: > > physmap_idx: 8 > i mem atop > 0 0x0 0x0 > 1 0x3 0x30 > 2 0x4 0x40 >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Fri, 17 Aug 2018 10:02:08 +0100 John Baldwin wrote: > On 8/17/18 9:54 AM, Michael Gmelin wrote: > > > > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: > >> > >>> On 8/16/18 1:58 PM, Michael Gmelin wrote: > >>> > >>> > On 15. Aug 2018, at 15:55, Konstantin Belousov > m

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 17. Aug 2018, at 12:13, Konstantin Belousov wrote: > >> On Fri, Aug 17, 2018 at 10:02:08AM +0100, John Baldwin wrote: >>> On 8/17/18 9:54 AM, Michael Gmelin wrote: >>> >>> > On 17. Aug 2018, at 08:17, John Baldwin wrote: > > On 8/16/18 1:58 PM, Michael Gmelin wrote: >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Fri, Aug 17, 2018 at 10:02:08AM +0100, John Baldwin wrote: > On 8/17/18 9:54 AM, Michael Gmelin wrote: > > > > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: > >> > >>> On 8/16/18 1:58 PM, Michael Gmelin wrote: > >>> > >>> > On 15. Aug 2018, at 15:55, Konstantin Belousov

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On 8/17/18 9:54 AM, Michael Gmelin wrote: > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: >> >>> On 8/16/18 1:58 PM, Michael Gmelin wrote: >>> >>> On 15. Aug 2018, at 15:55, Konstantin Belousov >>> > wrote: > On Wed, Aug 15, 2018 at 03:52:37PM +020

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 17. Aug 2018, at 08:17, John Baldwin wrote: > >> On 8/16/18 1:58 PM, Michael Gmelin wrote: >> >> >>> On 15. Aug 2018, at 15:55, Konstantin Belousov >> > wrote: >>> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >> On 15.

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On 8/16/18 1:58 PM, Michael Gmelin wrote: > > > On 15. Aug 2018, at 15:55, Konstantin Belousov > wrote: > >> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >>> >>> On 15. Aug 2018, at 15:04, Konstantin Belousov >>> >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 15. Aug 2018, at 15:55, Konstantin Belousov wrote: > >> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >> >> On 15. Aug 2018, at 15:04, Konstantin Belousov wrote: On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: Reviving this old thre

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: > > > > On 15. Aug 2018, at 15:04, Konstantin Belousov wrote: > > > >> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: > >> Reviving this old thread, since I just updated to r337818 and a similar > >> problem is hap

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> On 15. Aug 2018, at 15:04, Konstantin Belousov wrote: > >> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: >> Reviving this old thread, since I just updated to r337818 and a similar >> problem is happening again. Since the fix in r334799 (review >> https://reviews.freebsd.org

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: > Reviving this old thread, since I just updated to r337818 and a similar > problem is happening again. Since the fix in r334799 (review > https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, > so maybe this is related

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

l was > > > > > > > > > delivered with SeaBIOS 20131018_145217-build121-m2). > > > > > > > > > So I didn't flash anything (didn't feel like bricking > > > > > > > > > it). > > > > > > > >

Re: Page fault in udp_usrreq.c:823

The need of the many outweighs the greed of the few. > > > > > > > > > In message > > il.com> > > > , Matthew Macy writes: > > >> Try updating. It should be fixed. > > >> > > >> On Thu, Jun 21, 2018 at 6:14 PM, C

Re: Page fault in udp_usrreq.c:823

of the few. > > > > > > In message > il.com> > > , Matthew Macy writes: > >> Try updating. It should be fixed. > >> > >> On Thu, Jun 21, 2018 at 6:14 PM, Cy Schubert > >> wrot > >> e: > >> > In message &

Re: Page fault in udp_usrreq.c:823

Cy Schubert w > rot > >> e: > >> > In message <20180620090957.ga...@x2.osted.lan>, Peter Holm writes: > >> >> 20180620 10:32:47 all (1/1): udp.sh > >> >> Kernel page fault with the following non-sleepable locks held: > >> >> s

Re: Page fault in udp_usrreq.c:823

80620090957.ga...@x2.osted.lan>, Peter Holm writes: >> >> 20180620 10:32:47 all (1/1): udp.sh >> >> Kernel page fault with the following non-sleepable locks held: >> >> shared rw udpinp (udpinp) r = 0 (0xf80bbc808d78) locked @ netinet/in_p >> cb. >>

Re: Page fault in udp_usrreq.c:823

; > On Thu, Jun 21, 2018 at 6:14 PM, Cy Schubert wrot > e: > > In message <20180620090957.ga...@x2.osted.lan>, Peter Holm writes: > >> 20180620 10:32:47 all (1/1): udp.sh > >> Kernel page fault with the following non-sleepable locks held: > >> shared r

Re: Page fault in udp_usrreq.c:823

Try updating. It should be fixed. On Thu, Jun 21, 2018 at 6:14 PM, Cy Schubert wrote: > In message <20180620090957.ga...@x2.osted.lan>, Peter Holm writes: >> 20180620 10:32:47 all (1/1): udp.sh >> Kernel page fault with the following non-sleepable locks held: >> shar

Re: Page fault in udp_usrreq.c:823

In message <20180620090957.ga...@x2.osted.lan>, Peter Holm writes: > 20180620 10:32:47 all (1/1): udp.sh > Kernel page fault with the following non-sleepable locks held: > shared rw udpinp (udpinp) r = 0 (0xf80bbc808d78) locked @ netinet/in_pcb. > c:2398 >

Page fault in udp_usrreq.c:823

20180620 10:32:47 all (1/1): udp.sh Kernel page fault with the following non-sleepable locks held: shared rw udpinp (udpinp) r = 0 (0xf80bbc808d78) locked @ netinet/in_pcb.c:2398 stack backtrace: #0 0x80c00733 at witness_debugger+0x73 #1 0x80c01b11 at witness_warn+0x461 #2

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

x45 Stepping=1 > > > > > > > > > > Features=0xbfebfbff > > > > > > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > > > > > Features2=0x4ddaebbf > > > > > > > > >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

t; > > > > > CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > > > > Features2=0x4ddaebbf > > > > > > > > xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND> > > > > &

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

res=0x2c100800 > > > > > > > > AMD Features2=0x21 Structured Extended > > > > > > > > Features=0x2603 > > > > > > > > XSAVE Features=0x1 VT-x: (disabled in BIOS) > > > > > > > > PAT,HLT,MTF,PAUSE,EPT

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

gt; > > > > > > > > > > > > > AMD Features=0x2c100800 AMD > > > > > > > Features2=0x21 Structured Extended > > > > > > > Features=0x2603 XSAVE > > > > > > > Features=0x1 VT-x: (disabled in BIOS) > > > > > &

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> > > > > > > > > > AMD Features=0x2c100800 AMD > > > > > > Features2=0x21 Structured Extended > > > > > > Features=0x2603 XSAVE > > > > > > Features=0x1 VT-x: (disabled in BIOS) > > > >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

> > > > Features2=0x21 Structured Extended > > > > > Features=0x2603 XSAVE > > > > > Features=0x1 VT-x: (disabled in BIOS) > > > > > PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, > > > > > performance statistics real

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

performance statistics real memory = 4301258752 (4102 MB) > > > > avail memory = 1907572736 (1819 MB) Event timer "LAPIC" quality > > > > 600 ACPI APIC Table: > > > What does this mean ? Did you flashed coreboot ? > > > > T

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

D TSC: P-state invariant, performance > > > statistics real memory = 4301258752 (4102 MB) > > > avail memory = 1907572736 (1819 MB) > > > Event timer "LAPIC" quality 600 > > > ACPI APIC Table: > > What does this mean ? Did you flashed cor

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

hat does this mean ? Did you flashed coreboot ? This machine comes with it by default (my model was delivered with SeaBIOS 20131018_145217-build121-m2). So I didn't flash anything (didn't feel like bricking it). > > > kernel trap 12 with interrupts disabled > > >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

; avail memory = 1907572736 (1819 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: What does this mean ? Did you flashed coreboot ? > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fau

Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

;LAPIC" quality 600 ACPI APIC Table: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address= 0xf8000100 fault code = supervisor write data, protection violation instruction

Re: head -r325997: Fatal trap 12: page fault while in kernel mode (during a buildworld, virtualbox guest context) [2nd example]

empting a dump failed. I'm afraid all for >> information is the below. The kernel was a >> non-debug kernel (with debug information). >> >> The following is hand typed from a screen shot: >> >> Fatal trap 12: page fault while in kernel mode >> c

Re: head -r325997: Fatal trap 12: page fault while in kernel mode (during a buildworld, virtualbox guest context) [2nd example]

he following is hand typed from a screen shot: > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xff53f000e2b0 New one: 0x806b49010 > fault code= supervisor read data, page not present New one

head -r325997: Fatal trap 12: page fault while in kernel mode (during a buildworld, virtualbox guest context)

Attempting a dump failed. I'm afraid all for information is the below. The kernel was a non-debug kernel (with debug information). The following is hand typed from a screen shot: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xff53f00

Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

Am Fri, 14 Apr 2017 20:18:57 +0300 Konstantin Belousov schrieb: > On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > > Fatal trap 12: page fault while in kernel mode > > cpuid = 2; apic id = 02 > > fault virtual address = 0xf8001282fb00 > > fault cod

Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

nn wrote: > > > > Fatal trap 12: page fault while in kernel mode > > > > cpuid = 2; apic id = 02 > > > > fault virtual address = 0xf8001282fb00 > > > > fault code = supervisor read instruction, protection > > > > viol

Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

On Sat, Apr 15, 2017 at 11:18:41AM +0200, O. Hartmann wrote: > Am Fri, 14 Apr 2017 20:18:57 +0300 > Konstantin Belousov schrieb: > > > On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > > > Fatal trap 12: page fault while in kernel mode > > > cp

Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

Am Fri, 14 Apr 2017 20:18:57 +0300 Konstantin Belousov schrieb: > On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > > Fatal trap 12: page fault while in kernel mode > > cpuid = 2; apic id = 02 > > fault virtual address = 0xf8001282fb00 > > fault cod

Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

On Fri, Apr 14, 2017 at 06:58:27PM +0200, O. Hartmann wrote: > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 02 > fault virtual address = 0xf8001282fb00 > fault code = supervisor read instruction, protection violation > ??() at 0xf

Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

: link state changed to UP > > igb1.2: link state changed to UP > > igb1.66: link state changed to UP > > igb1.111: link state changed to UP > > igb1.10: link state changed to UP > > tun0: link state changed to UP > > link state changed to down > > igb0: lin

Re: CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

> tun0: link state changed to UP > link state changed to down > igb0: link state changed to DOWN > Bump sched buckets to 64 (was 0) > Link state changed to up > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address =

CURRENT (r316844): Fatal trap 12: page fault while in kernel mode (syslogd)

ed to UP igb1.66: link state changed to UP igb1.111: link state changed to UP igb1.10: link state changed to UP tun0: link state changed to UP link state changed to down igb0: link state changed to DOWN Bump sched buckets to 64 (was 0) Link state changed to up Fatal trap 12: page fault while in k

Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held [ssh on rpi2 comparison]

Em 21/06/2016 19:45, Keith White escreveu: On Tue, 21 Jun 2016, Ian Lepore wrote: On Tue, 2016-06-21 at 08:11 -0300, Otacílio wrote: Em 21/06/2016 07:33, Keith White escreveu: In an earlier message Ian said that he thought he knew what the problem was... Here the problem occurs when using

Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held [ssh on rpi2 comparison]

On Tue, 2016-06-21 at 15:30 -0700, Mark Millard wrote: > Ian Lepore ian at freebsd.org wrote on Tue Jun 21 17:55:28 UTC 2016 > : > > > On Tue, 2016-06-21 at 08:11 -0300, Otacílio wrote: > > > Em 21/06/2016 07:33, Keith White escreveu: > > > > In an earlier message Ian said that he thought he knew

Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held [ssh on rpi2 comparison]

On Tue, 21 Jun 2016, Ian Lepore wrote: On Tue, 2016-06-21 at 08:11 -0300, Otacílio wrote: Em 21/06/2016 07:33, Keith White escreveu: In an earlier message Ian said that he thought he knew what the problem was... Here the problem occurs when using wifi. I do not have tested wired because I d

  1   2   3   4   5   >