Re: kernel: fatal trap 12 on CURRENT, when using WireGuard

Am 09.01.24 um 21:40 schrieb Gleb Smirnoff: Rainer, On Tue, Jan 09, 2024 at 09:23:54PM +0100, Rainer Hurling wrote: R> I tried to update my 15.0-CURRENT box from n267335-499e84e16f56 to a very R> recent commit. The build and install went fine. After booting with new R> base, I got a page faul

Re: kernel: fatal trap 12 on CURRENT, when using WireGuard

Rainer, On Tue, Jan 09, 2024 at 09:23:54PM +0100, Rainer Hurling wrote: R> I tried to update my 15.0-CURRENT box from n267335-499e84e16f56 to a very R> recent commit. The build and install went fine. After booting with new R> base, I got a page fault with the following error: Sorry for that, my

kernel: fatal trap 12 on CURRENT, when using WireGuard

0x80ca66ac at iflib_rxeof+0xe4c #16 0x80ca0b5a at _task_fn_rx+0x7a #17 0x80ba0118 at gtaskqueue_run_locked+0xa8 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x3 fault code = supervisor read data, page not present

Re: Fatal trap 12: if_io_tqg_11: ~main-n248851-0d55bc8eb2a:

are > active), current rev: ( 22997b755013bdde60119fdc781769192ab7e1e0 Sat Aug 7 > 21:25:36 2021 +0100 ) > > crash info: > -- > ... > <118>Starting devd. > <118>Starting Network: igb1. > <118>igb1: flags=8822 metric 0 mtu 1500 > <118> > > opt

Fatal trap 12: if_io_tqg_11: ~main-n248851-0d55bc8eb2a:

>Starting Network: igb1. <118>igb1: flags=8822 metric 0 mtu 1500 <118> options=4e507bb <118> ether b4:96:91:95:97:ed Fatal trap 12: page fault while in kernel mode cpuid = 11; apic id = 0b fault virtual address = 0x128 fault code = supervisor read data

Re: drm-kmod kernel crash fatal trap 12

On Jun 19, 2021, at 4:19 PM, Thomas Laus wrote: > > On 6/19/21 2:21 PM, Bakul Shah wrote: >> >> You may wish to see if Andriy Gapon's method (LOCAL_MODULES_DIR, >> LOCAL_MODULES) >> works better for you. >> >> I trust Makefile* to do the right thing with META_MODE and CCACHE (and if >> they >

Re: drm-kmod kernel crash fatal trap 12

On 6/19/21 2:21 PM, Bakul Shah wrote: > > You may wish to see if Andriy Gapon's method (LOCAL_MODULES_DIR, > LOCAL_MODULES) > works better for you. > > I trust Makefile* to do the right thing with META_MODE and CCACHE (and if they > don't, it is a bug that would need to be fixed) so I personally

Re: drm-kmod kernel crash fatal trap 12

On Jun 18, 2021, at 7:05 AM, Thomas Laus wrote: > > On 6/10/21 11:13 AM, Bakul Shah wrote: >> This is what I did: >> >> git clone https://github.com/freebsd/drm-kmod >> ln -s $PWD/drm-kmod /usr/local/sys/modules >> >> Now it gets compiled every time you do make buildkernel. >> If things break y

Re: drm-kmod kernel crash fatal trap 12

On 6/10/21 11:13 AM, Bakul Shah wrote: > This is what I did: > > git clone https://github.com/freebsd/drm-kmod > ln -s $PWD/drm-kmod /usr/local/sys/modules > > Now it gets compiled every time you do make buildkernel. > If things break you can do a git pull in the drm-kmod dir > and rebuild. > Tha

Re: drm-kmod kernel crash fatal trap 12

On 6/15/21 11:22 AM, Bakul Shah wrote: On Jun 15, 2021, at 9:03 AM, John Baldwin wrote: On 6/10/21 8:13 AM, Bakul Shah wrote: On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod upda

Re: drm-kmod kernel crash fatal trap 12

On Jun 15, 2021, at 9:03 AM, John Baldwin wrote: > > On 6/10/21 8:13 AM, Bakul Shah wrote: >> On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: >>> The drm-kmod module is the latest from the pkg server. It all >>> worked this past Monday after the recent drm-kmod update. >> This is what I did: >>

Re: drm-kmod kernel crash fatal trap 12

On 6/10/21 8:13 AM, Bakul Shah wrote: On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod update. This is what I did: git clone https://github.com/freebsd/drm-kmod ln -s $PWD/drm-kmod

Re: drm-kmod kernel crash fatal trap 12

On 10/06/2021 18:13, Bakul Shah wrote: On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod update. This is what I did: git clone https://github.com/freebsd/drm-kmod ln -s $PWD/drm-kmo

Re: drm-kmod kernel crash fatal trap 12

On Jun 10, 2021, at 9:49 AM, Philipp Ost wrote: > > On 6/10/21 5:13 PM, Bakul Shah wrote: >> On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: >>> The drm-kmod module is the latest from the pkg server. It all >>> worked this past Monday after the recent drm-kmod update. >> This is what I did: >>

Re: drm-kmod kernel crash fatal trap 12

In message <4894bd36-92bd-596e-cc18-cd3e6aafe...@selasky.org>, Hans Petter Sela sky writes: > On 6/9/21 4:43 PM, Thomas Laus wrote: > > I updated my system this morning to main-n247260-dc318a4ffab June 9 2012 > > and the first boot after the kernel was loaded I received: &g

Re: drm-kmod kernel crash fatal trap 12

On 6/10/21 5:13 PM, Bakul Shah wrote: On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod update. This is what I did: git clone https://github.com/freebsd/drm-kmod ln -s $PWD/drm-kmod

Re: drm-kmod kernel crash fatal trap 12

Bakul Shah [ba...@iitbombay.org] wrote: > > This is what I did: > > git clone https://github.com/freebsd/drm-kmod > ln -s $PWD/drm-kmod /usr/local/sys/modules > > Now it gets compiled every time you do make buildkernel. > If things break you can do a git pull in the drm-kmod dir > and rebuild. >

Re: drm-kmod kernel crash fatal trap 12

Hans Petter Selasky [h...@selasky.org] wrote: > > When you use -current, you need to compile this pkg from the latest ports. > I'm not sure if that happens automatically when you install the binary > package. > I just built drm-current-kmod as a port and things work. Building a kernel in the past

Re: drm-kmod kernel crash fatal trap 12

On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: > The drm-kmod module is the latest from the pkg server. It all > worked this past Monday after the recent drm-kmod update. This is what I did: git clone https://github.com/freebsd/drm-kmod ln -s $PWD/drm-kmod /usr/local/sys/modules Now it gets c

Re: drm-kmod kernel crash fatal trap 12

On 6/10/21 4:13 PM, Thomas Laus wrote: The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod update. When you use -current, you need to compile this pkg from the latest ports. I'm not sure if that happens automatically when you install

Re: drm-kmod kernel crash fatal trap 12

Hans Petter Selasky [h...@selasky.org] wrote: > > Make sure you also re-build the drm-kmod module. > The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod update. Things are good at n247230. I cleaned my source today and checked out fres

Re: drm-kmod kernel crash fatal trap 12

On 6/9/21 4:43 PM, Thomas Laus wrote: I updated my system this morning to main-n247260-dc318a4ffab June 9 2012 and the first boot after the kernel was loaded I received: 'fatal trap 12' fault virtual address = 0x0 fault code = supervisor write data, page not present instruction poin

drm-kmod kernel crash fatal trap 12

I updated my system this morning to main-n247260-dc318a4ffab June 9 2012 and the first boot after the kernel was loaded I received: 'fatal trap 12' fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x20:0x82fc3d1b stack poin

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 when booting with fuse in /boot/loader.conf

; /usr/src Revision: 338177 > > /usr/ports Revision: 43 > > When I try to boot with the fuse module in /boot/loader.conf I get > something like this: > > Fatal trap 12: > > ... > > fault virtual address = 0xcd > instruction pointer = 0x20:0x80eec062 &

Fatal trap 12 when booting with fuse in /boot/loader.conf

/boot/loader.conf I get something like this: Fatal trap 12: ... fault virtual address = 0xcd instruction pointer = 0x20:0x80eec062 stack pointer = 0x20:0x8420e580 frame pointer = 0x20:0x8420e670 ... Then there is a prompt: db> or something, but it doesn't re

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)

On Sun, 19 Aug 2018 19:16:42 +0300 Konstantin Belousov wrote: > On Sun, Aug 19, 2018 at 04:59:51PM +0200, Michael Gmelin wrote: > > > > > > On Fri, 17 Aug 2018 10:02:08 +0100 > > John Baldwin wrote: > > > > > On 8/17/18 9:54 AM, Michael Gmelin wrote: > > > > > > > > > > > >> On 1

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

On Sun, Aug 19, 2018 at 04:59:51PM +0200, Michael Gmelin wrote: > > > 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 Gmel

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: 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: Fatal trap 12

On Sat, May 26, 2018 at 01:46:42PM +0200, Manuel Stühn wrote: Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing several "Fatal traps 12". Before the update i did not have any of those. In all cases the traps occured some time after resume. I tried to debug this further by

Re: Fatal trap 12

On Sat, May 26, 2018 at 08:32:17PM +0800, blubee blubeeme wrote: Aren't you the guy using the drm-kmod if yes, your custom complied kernel and not the default kernel causing those issues. Best, Owen I'm indeed using graphics/drm-stable-kmod, but i do not use a custom kernel: uname -r

Re: Fatal trap 12

at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:167 >from /boot/kernel/linuxkpi.ko > #15 0xf80007804828 in ?? () > #16 0xf80007804828 in ?? () > #17 0x0030 in ?? () > #18 0x in ?? () > (kgdb) > > > Fatal trap 12: page f

Fatal trap 12

000 in ?? () (kgdb) Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x3 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80cc60cb stack pointer = 0x28:0xfe0056508560 frame pointe

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-04 14:40 GMT+01:00 Andriy Gapon : > On 04/02/2018 11:50, Maurizio Vairani wrote: > > I have added a socket in the ifioctl() call as in the > > /usr/src/sys/nfs/bootp_subr.c source. > > Please let me know if you prefer a patch. > > A patch here https://reviews.freebsd.org/ would be the best

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-07 19:29 GMT+01:00 John Nielsen : > > On Feb 7, 2018, at 6:07 AM, Maurizio Vairani > wrote: > > > > 2018-02-06 23:02 GMT+01:00 John Nielsen : > > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > > >> > > >> Apparently s

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

> On Feb 7, 2018, at 6:07 AM, Maurizio Vairani wrote: > > 2018-02-06 23:02 GMT+01:00 John Nielsen : > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > >> > >> Apparently sending a NULL socket pointer to ifioctl hasn't worked > >> s

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-06 23:02 GMT+01:00 John Nielsen : > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > >> > >> Apparently sending a NULL socket pointer to ifioctl hasn't worked > >> since this commit in 2011: > >> https://svnweb.freebsd.org/b

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

> On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: >> >> Apparently sending a NULL socket pointer to ifioctl hasn't worked >> since this commit in 2011: >> https://svnweb.freebsd.org/base?view=revision&revision=218757 >> >> So I'm going t

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > > > > On Feb 6, 2018, at 10:54 AM, John Nielsen > > wrote: > > > > > > > > > > > On Feb 4, 2018, at 2:50 AM, Maurizio Vairani > > com> wrote: > > > > > > 2018-01-29 18:38 GMT+01:00 John Nielsen : > > > [ resending from correct email ad

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

> On Feb 6, 2018, at 10:54 AM, John Nielsen wrote: > >> >> On Feb 4, 2018, at 2:50 AM, Maurizio Vairani wrote: >> >> 2018-01-29 18:38 GMT+01:00 John Nielsen : >> [ resending from correct email address ] >> >>> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani >>> wrote: >>> >>> I am running >

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

> On Feb 4, 2018, at 2:50 AM, Maurizio Vairani wrote: > > 2018-01-29 18:38 GMT+01:00 John Nielsen : > [ resending from correct email address ] > >> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani wrote: >> >> I am running >> # uname >> -a >> >> FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r32

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

> On Feb 4, 2018, at 2:50 AM, Maurizio Vairani wrote: > > 2018-01-29 18:38 GMT+01:00 John Nielsen : > [ resending from correct email address ] > >> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani wrote: >> >> I am running >> # uname >> -a >> >> FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

On 04/02/2018 11:50, Maurizio Vairani wrote: > I have added a socket in the ifioctl() call as in the > /usr/src/sys/nfs/bootp_subr.c source. > Please let me know if you prefer a patch. A patch here https://reviews.freebsd.org/ would be the best. -- Andriy Gapon __

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-01-29 18:38 GMT+01:00 John Nielsen : > [ resending from correct email address ] > > On Jan 29, 2018, at 6:05 AM, Maurizio Vairani > wrote: > > I am running > # uname > -a > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 > UTC 2018 r...@releng3.nyi.freebsd.or

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

[ resending from correct email address ] > On Jan 29, 2018, at 6:05 AM, Maurizio Vairani wrote: > > I am running > # uname > -a > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 > UTC 2018 > r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC

Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

I am running # uname -a FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 UTC 2018 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 After compiling the kernel module as discussed in this thread : https://lists.freebsd.org/pipermail/freebsd-

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)

Am Sat, 15 Apr 2017 12:33:34 +0300 Konstantin Belousov schrieb: > 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. Hartma

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: Fatal trap 12

On Thu, 23 Jun 2016 16:45:30 + "Bjoern A. Zeeb" wrote: > Hi, > > can you try checking out svn://svn.freebsd.org/base/projects/vnet and > see if a kernel from there works better? > > It contains further pf/pflog/pfsync changes; mostly for VIMAGE which > will go into head the next days. >

Re: Fatal trap 12

Hi, can you try checking out svn://svn.freebsd.org/base/projects/vnet and see if a kernel from there works better? It contains further pf/pflog/pfsync changes; mostly for VIMAGE which will go into head the next days. Thanks /bz ___ freebsd-curre

Re: Fatal trap 12

On Thu, 23 Jun 2016 10:54:46 +0200 Johan Hendriks wrote: > I have the following in my kernel config > # pf > options ALTQ > options ALTQ_CBQ > options ALTQ_RED > options ALTQ_RIO > options ALTQ_HFSC > options ALTQ_CDNR > options ALTQ_PRIQ > device pf > device

Re: Fatal trap 12

I just removed the following from my kernel file #device pf #device pflog #device pfsync Changed back the SI_SUB_PSEUDO in sys/netpfil/pf/if_pflog.c Rebuild the kernel and now the kernel is booting normally. regards Johan Op 23/06/16 om 02:01 schreef Bjoern A. Zeeb: > On 22 Ju

Re: Fatal trap 12

I have the following in my kernel config # pf options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_CDNR options ALTQ_PRIQ device pf device pflog device pfsync I can not alter the order the modules load as far as I

Re: Fatal trap 12

On 22 Jun 2016, at 17:56, Ivan Klymenko wrote: On Wed, 22 Jun 2016 20:45:26 +0300 Ivan Klymenko wrote: On Wed, 22 Jun 2016 20:36:36 +0300 Ivan Klymenko wrote: Hello. After update from r302000 to r302083 i have panic http://i.imgur.com/YfvvhdS.png Thanks. Sorry, the first time discovered

Re: Fatal trap 12

Just a me too. Build yesterday (revision unclear) and starts fine, today a rebuild and a panic. But I do not see the panic message as it reboots right away. The latest line I see is atkbd0: irq 1 on atkbdc0 Then a real quick panic and then it reboots. I captured it by filming and then pause it

Re: Fatal trap 12

On Wed, 22 Jun 2016 20:45:26 +0300 Ivan Klymenko wrote: > On Wed, 22 Jun 2016 20:36:36 +0300 > Ivan Klymenko wrote: > > > Hello. > > After update from r302000 to r302083 i have panic > > http://i.imgur.com/YfvvhdS.png > > > > Thanks. > Sorry, the first time discovered a revision r302060. T

Re: Fatal trap 12

On Wed, 22 Jun 2016 20:36:36 +0300 Ivan Klymenko wrote: > Hello. > After update from r302000 to r302083 i have panic > http://i.imgur.com/YfvvhdS.png > > Thanks. Sorry, the first time discovered a revision r302060. ___ freebsd-current@freebsd.org mail

Fatal trap 12

Hello. After update from r302000 to r302083 i have panic http://i.imgur.com/YfvvhdS.png Thanks. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsu

  1   2   3   >