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

Please ignore this. updating to the latest revision fixed the problem. On Sun, Aug 22, 2021 at 11:12 PM Oleg Ginzburg wrote: > Hi, > > One of my regularly updated hosts on the 14-CURRENT started to reboot > constantly when initializing the network stack (both IPv4/V6 stacks are > active), curren

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

> On 23. Aug 2018, at 01:02, Per Gunnarsson wrote: > > Sorry for possibly mentioning this twice. > > FreeBSD konjak 12.0-ALPHA2 FreeBSD 12.0-ALPHA2 #0 r338177: Wed Aug 22 > 08:46:40 CEST 2018 > root@konjak:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > /usr/src Revision: 338177 > >

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)

On Wed, 6 Jun 2018 01:06:25 +0200 Michael Gmelin wrote: > On Tue, 5 Jun 2018 16:11:35 +0300 > Konstantin Belousov wrote: > > > On Mon, Jun 04, 2018 at 11:17:56PM +0200, Michael Gmelin wrote: > > > > > > > > > On Mon, 4 Jun 2018 14:06:55 +0300 > > > Konstantin Belousov wrote: > > >

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

On Tue, 5 Jun 2018 16:11:35 +0300 Konstantin Belousov wrote: > On Mon, Jun 04, 2018 at 11:17:56PM +0200, Michael Gmelin wrote: > > > > > > On Mon, 4 Jun 2018 14:06:55 +0300 > > Konstantin Belousov wrote: > > > > > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > >

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

On Mon, Jun 04, 2018 at 11:17:56PM +0200, Michael Gmelin wrote: > > > On Mon, 4 Jun 2018 14:06:55 +0300 > Konstantin Belousov wrote: > > > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > > > > > > > On Sun, 3 Jun 2018 23:53:40 +0300 > > > Konstantin Belousov wrote: > >

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

On Mon, 4 Jun 2018 14:06:55 +0300 Konstantin Belousov wrote: > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > > > > On Sun, 3 Jun 2018 23:53:40 +0300 > > Konstantin Belousov wrote: > > > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > >

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

On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > On Sun, 3 Jun 2018 23:53:40 +0300 > Konstantin Belousov wrote: > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > > Konstantin Belousov wrote: > >

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

On Sun, 3 Jun 2018 23:53:40 +0300 Konstantin Belousov wrote: > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > Konstantin Belousov wrote: > > > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > >

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

On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > On Sun, 3 Jun 2018 18:04:23 +0300 > Konstantin Belousov wrote: > > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > > Konstantin Belousov wrote: > >

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

On Sun, 3 Jun 2018 18:04:23 +0300 Konstantin Belousov wrote: > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > > > > On Sun, 3 Jun 2018 16:21:10 +0300 > > Konstantin Belousov wrote: > > > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > > > >

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

On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote: > > > On Sun, 3 Jun 2018 16:21:10 +0300 > Konstantin Belousov wrote: > > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > > > Hi, > > > > > > After upgrading CURRENT to r333992 (from something at least a year >

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

On Sun, 3 Jun 2018 16:21:10 +0300 Konstantin Belousov wrote: > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > > Hi, > > > > After upgrading CURRENT to r333992 (from something at least a year > > old, quite some changes in mp_machdep.c since), this machine crashes > > on boo

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

On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote: > Hi, > > After upgrading CURRENT to r333992 (from something at least a year > old, quite some changes in mp_machdep.c since), this machine crashes > on boot: > > Copyright (c) 1992-2018 The FreeBSD Project. > Copyright (c) 1979, 198

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

On Sat, May 26, 2018, 19:52 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. > > Below there is some output found in /va

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

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

Re: Fatal trap 12: page fault while in kernel mode (FUSE related?)

On Fri, Nov 1, 2013 at 6:03 AM, Alexey Dokuchaev wrote: > On Thu, Oct 31, 2013 at 09:59:42AM -0700, Kevin Oberman wrote: > > On Tue, Oct 29, 2013 at 3:24 AM, Alexey Dokuchaev wrote: > > > I was running out of space on my UFS partition and decided to use big > NTFS > > > one I also have on the dr

Re: Fatal trap 12: page fault while in kernel mode (FUSE related?)

On Thu, Oct 31, 2013 at 09:59:42AM -0700, Kevin Oberman wrote: > On Tue, Oct 29, 2013 at 3:24 AM, Alexey Dokuchaev wrote: > > I was running out of space on my UFS partition and decided to use big NTFS > > one I also have on the drive. I've mounted it with ntfs-3g and our native > > fuse.ko. I ne

Re: Fatal trap 12: page fault while in kernel mode (FUSE related?)

FYI, works fine after changed to pkg0.isc.FreeBSD.org. # pkg update Updating repository catalogue digests.txz 100% 960KB 240.0KB/s 80.0KB/s 00:04 packagesite.txz 100% 5258KB 309.3KB/s 498.5KB/s 00:17 Incremental update completed, 0 packages processed: 0 packages updated, 0 removed and 21724

Re: Fatal trap 12: page fault while in kernel mode (FUSE related?)

On Tue, Oct 29, 2013 at 3:24 AM, Alexey Dokuchaev wrote: > Hi again, > > I was running out of space on my UFS partition and decided to use big NTFS > one I also have on the drive. I've mounted it with ntfs-3g and our native > fuse.ko. I needed the scratch space to built Open/LibreOffice on it *

Re: Fatal trap 12 with process cambio on USB attach

On Sat, Jan 19, 2013 at 11:49:24AM -0500, Alexander Kabaev wrote: > On Sat, 19 Jan 2013 10:10:54 -0500 > Glen Barber wrote: > > > Hi, > > > > I am running one-day-old -CURRENT: > > > > root@nucleus:~ # uname -a > > FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #51 r245605: Fri > > Jan 18

Re: Fatal trap 12 with process cambio on USB attach

On Sat, 19 Jan 2013 10:10:54 -0500 Glen Barber wrote: > Hi, > > I am running one-day-old -CURRENT: > > root@nucleus:~ # uname -a > FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #51 r245605: Fri > Jan 18 11:25:40 EST 2013 > root@nucleus:/usr/obj/usr/src/sys/NUCLEUS amd64 > > I attached a

Re: Fatal trap 12: page fault while in kernel mode -- Stopped at atomic_subtract_int+0x4

Fabian Keil wrote: > Fabian Keil wrote: > > > I pretty reproducible get the following (handtranscribed) panic > > when sending an zfs snapshot to geli provider based on an USB > > stick that disappears (due to a bug, or because it's unplugged): > > > > Fatal trap 12: page fault while in kerne

Re: Fatal trap 12: page fault while in kernel mode -- Stopped at atomic_subtract_int+0x4

Fabian Keil wrote: > I pretty reproducible get the following (handtranscribed) panic > when sending an zfs snapshot to geli provider based on an USB > stick that disappears (due to a bug, or because it's unplugged): > > Fatal trap 12: page fault while in kernel mode > cpuid = 0: apic id = 00 >

Re: "Fatal trap 12: page fault while in kernel mode" with latest-CURRENT

On Tue, 12 Aug 2003, David Taylor wrote: > I've been getting this occasionally (a few times a day) since I upgraded > to -CURRENT yesterday. I tried installing Bosko's Intel Data Corruption > patch today, to see if that changed anything, but it doesn't appear to > have worked. > [snip] *sigh*

RE: Fatal trap 12 under RELENG_5_1, anyone who can help?

On 01-Aug-2003 Eivind Olsen wrote: > Hello. > My FreeBSD RELENG_5_1 server (cvsupped 4 days ago) seems to have problems - > it crashes from time to time (approx. once a day). > > I've rebuilt the kernel with debug-symbols and enabled the debugger and > caught a crash tonight: > > Here's what I

Re: Fatal trap 12: page fault while in kernel mode

At Wed, 23 Jul 2003 13:31:31 -0700 (PDT), Doug White wrote: > > On Mon, 21 Jul 2003, Bjoern A. Zeeb wrote: > > > Thanks. This works fine. Is there any "global" solution to the problem > > so that I won't need to patch again the time 5.2R comes out ? > > Smells like a good candiate for a TUNABLE.

Re: Fatal trap 12: page fault while in kernel mode

On Mon, 21 Jul 2003, Bjoern A. Zeeb wrote: > Thanks. This works fine. Is there any "global" solution to the problem > so that I won't need to patch again the time 5.2R comes out ? Smells like a good candiate for a TUNABLE. -- Doug White| FreeBSD: The Power to Serve [EMAIL P

Re: Fatal trap 12: page fault while in kernel mode

On Tue, 22 Jul 2003, M. Warner Losh wrote: Hi, > In message: <[EMAIL PROTECTED]> > "Bjoern A. Zeeb" <[EMAIL PROTECTED]> writes: > : On Mon, 21 Jul 2003, Noriyoshi Kawano wrote: > : > : > I have similar problem. > : > disable re-route interrupts. > : > It's works fine. > : > > : > ---

Re: Fatal trap 12: page fault while in kernel mode

In message: <[EMAIL PROTECTED]> "Bjoern A. Zeeb" <[EMAIL PROTECTED]> writes: : On Mon, 21 Jul 2003, Noriyoshi Kawano wrote: : : > I have similar problem. : > disable re-route interrupts. : > It's works fine. : > : > --- /sys/dev/pci/pci.c.orig Tue Jul 1 23:08:32 2003 : > +++ /sys/dev/

Re: Fatal trap 12: page fault while in kernel mode

On Mon, 21 Jul 2003, Noriyoshi Kawano wrote: > I have similar problem. > disable re-route interrupts. > It's works fine. > > --- /sys/dev/pci/pci.c.orig Tue Jul 1 23:08:32 2003 > +++ /sys/dev/pci/pci.cMon Jul 21 11:04:55 2003 > @@ -800,7 +800,7 @@ > } > > if (cfg->intpin > 0

Re: Fatal trap 12: page fault while in kernel mode

Hi, I have similar problem. disable re-route interrupts. It's works fine. --- /sys/dev/pci/pci.c.orig Tue Jul 1 23:08:32 2003 +++ /sys/dev/pci/pci.c Mon Jul 21 11:04:55 2003 @@ -800,7 +800,7 @@ } if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) { -#if defined(__ia

Re: Fatal trap 12: page fault while in kernel mode

Hi I recompiled the official nv driver with debugging symbols: X works as expected. My apologies if I alarmed anyone. John Baldwin wrote: On 22-Jan-2003 Peter Kostouros wrote: Hi I am having a similar problem to what has been reported previously regarding X. Basically I get a fatal trap 12.

RE: Fatal trap 12: page fault while in kernel mode

On 22-Jan-2003 Peter Kostouros wrote: > Hi > > I am having a similar problem to what has been reported previously > regarding X. Basically I get a fatal trap 12. (cvsup'ed about one hour > ago.) I have attached a backtrace I hope is useful. > > When I started X within gdb, I received the followi

Re: Fatal trap 12

On Sep 30 at 17:19, John Baldwin spoke: > > On 30-Sep-2002 Hanspeter Roth wrote: > > 416 and 556 denote linenumbers in kern_exec.c. > > Thanks! That's here: > > if (ps_arg_cache_limit >= i + sizeof(struct pargs)) { > bcopy(imgp->stringbase, newargs->ar_args, i); >

Re: Fatal trap 12

On 30-Sep-2002 Hanspeter Roth wrote: > On Sep 30 at 15:16, John Baldwin spoke: > >> Hmm, unfortunately generic_bcopy() is in asm, and so it doesn't have >> a "true" frame and we end up skipping over the frame in execve() >> where it is called from. There are only 3 bcopy's in execve(), but >>

Re: Fatal trap 12

On Sep 30 at 15:16, John Baldwin spoke: > Hmm, unfortunately generic_bcopy() is in asm, and so it doesn't have > a "true" frame and we end up skipping over the frame in execve() > where it is called from. There are only 3 bcopy's in execve(), but > I'm not sure which is likely to have been the

Re: Fatal trap 12

On 30-Sep-2002 Hanspeter Roth wrote: > On Sep 30 at 15:16, John Baldwin spoke: > >> > Fatal trap 12: page fault while in kernal mode >> > fault virtual address = 0xdeadc0de >> >> This means someone is trying to access memory that has been free'd. > > How do I make someone not to do such bad

Re: Fatal trap 12

On Sep 30 at 15:16, John Baldwin spoke: > > Fatal trap 12: page fault while in kernal mode > > fault virtual address = 0xdeadc0de > > This means someone is trying to access memory that has been free'd. How do I make someone not to do such bad things? :-) > Hmm, unfortunately generic_bcopy()

Re: Fatal trap 12

On 30-Sep-2002 Hanspeter Roth wrote: > On Sep 30 at 11:59, John Baldwin spoke: > >> >> These messages above that you left out are very important. :( >> Also, if you can get a trace by typing 't' at the db> prompt >> that can be very helpful as well. > > Ok. I hope there aren't to many mistak

Re: Fatal trap 12

On Sep 30 at 11:59, John Baldwin spoke: > > These messages above that you left out are very important. :( > Also, if you can get a trace by typing 't' at the db> prompt > that can be very helpful as well. Ok. I hope there aren't to many mistakes. vga0: at port 0x3c0-0x3df iomem 0xa-0xbf

RE: Fatal trap 12

On 29-Sep-2002 Hanspeter Roth wrote: > On Sep 29 at 12:25, Mitsuru IWASAKI spoke: > >> If you think this is caused by acpi.ko, just disable acpi.ko loading. >> Please read thru loader(8) and device.hints(5). > > Yes, this is it. I've now disabled acpi and the boot process comes > further. >

Re: Fatal trap 12 on kernel from sometime Nov. 30.

Alfred, Thanks for the suggestions. The first thing I tried was the kernel.old but somehow I managed to have the same problem. It just dawned on me that I could build a Generic kernel on my laptop burn it on a cd (don't have a floppy) and install it on the sick machine. That is what I did an

Re: Fatal trap 12 on kernel from sometime Nov. 30.

Manfred Antar wrote: >At 07:12 PM 12/1/2001 -0800, Edwin Culp wrote: > >>Andrew, >> >>Thanks. Now my problem is that I can't cvsup. Any ideas on how to update my >sources? >>Maybe someone could email me a patch and I could take it over with a floppy. Right >now >>I have no access to the ne

Re: Fatal trap 12 on kernel from sometime Nov. 30.

At 07:12 PM 12/1/2001 -0800, Edwin Culp wrote: >Andrew, > >Thanks. Now my problem is that I can't cvsup. Any ideas on how to update my >sources? >Maybe someone could email me a patch and I could take it over with a floppy. Right >now >I have no access to the network with the machine that ha

Re: Fatal trap 12 on kernel from sometime Nov. 30.

Edwin, The following is the current fix in place: Index: ip_output.c === RCS file: /home/ncvs/src/sys/netinet/ip_output.c,v retrieving revision 1.142 retrieving revision 1.143 diff -u -r1.142 -r1.143 --- ip_output.c 4 Nov 2001 22:56

Re: Fatal trap 12 on kernel from sometime Nov. 30.

* Edwin Culp <[EMAIL PROTECTED]> [011201 21:25] wrote: > Andrew, > > Thanks. Now my problem is that I can't cvsup. Any ideas on how to > update my sources? > Maybe someone could email me a patch and I could take it over with a > floppy. Right now > I have no access to the network with the

Re: Fatal trap 12 on kernel from sometime Nov. 30.

Andrew, Thanks. Now my problem is that I can't cvsup. Any ideas on how to update my sources? Maybe someone could email me a patch and I could take it over with a floppy. Right now I have no access to the network with the machine that has the fatal trap. Thanks, ed Andrew R. Reiter wrote

Re: Fatal trap 12 on kernel from sometime Nov. 30.

cvsup -- this was "fixed" sometime within the last 24hours. On Sat, 1 Dec 2001, Edwin Culp wrote: :With my kernel and with a Generic kernel, I am getting a Fatal trap 12 :when trying to access the network. :The first thing that happens on the network seems to cause the panic. : The followi

RE: Fatal trap 12 with recent current (notebook with network pc-

On Wed, 31 Oct 2001, John Baldwin wrote: > Please provide a backtrace. (trace in ddb should do the trick) Sorry, foggot that. db> Context switches not allowed in the debugger. db> trace device_set_flags(0,8,c11e3c80,c126ec00,0) at device_set_flags+0x9 allocate_driver(c09aa200,c1264700,c69

RE: Fatal trap 12 with recent current (notebook with network pc-

On 31-Oct-01 Ilmar S. Habibulin wrote: > > I have Mitac 7020 notebook with Apollo 10/100M Fast Ethernet PC Card. > Today i cvsuped recent current and now kernel panics ufter card insertion > with the folowing message: > > pccard: card inserted, slot 0 > mobile pccardd[186]: Card "Dual Speed"("

Re: fatal trap 12 after lastest kernel build

> did you follow Peter Wemm's instructions on the new config changes? Muchos thanks to Warner Losh for his src/UPDATE service. It really saved my butt a couple of times. :) Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the mess

Re: fatal trap 12 after lastest kernel build

Oh ok. well then I have no idea... :-) I thought that could be the problem... = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at

Re: fatal trap 12 after lastest kernel build

Kenneth Wayne Culver wrote: > > did you follow Peter Wemm's instructions on the new config changes? Actually, I did. In fact, I built 2 or 3 kernels after the changes went into effect with no problems. It's just the sources that I cvsup'd as of an hour ago that's causing the problems. > On T

  1   2   >