Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

t; 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) > > >>>> during a -j4 buildworld. The backtrace reports > > >>>> > > >>>> panic: non-current pmap 0xa00020eab8f0 > > >>> > > >>> Could you show the out

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote: > >>>> Still seeing non-current pmap panics on the Pi3, this time a B+ running > >>>> 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) > >>>> during a -j4 buildworld. The ba

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

rent pmap panics on the Pi3, this time a B+ running >>>> 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) >>>> during a -j4 buildworld. The backtrace reports >>>> >>>> panic: non-current pmap 0xa00020eab8f0 >>> >>> Could

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

On Tue, Oct 20, 2020 at 11:55:30AM -0700, bob prohaska wrote: > On Tue, Oct 20, 2020 at 12:30:05PM -0400, Mark Johnston wrote: > > > > I set up a RPi3 to try and repro this and have so far managed to trigger > > it once using Peter Holm's stress2 suite, so I'll keep investigating. I > > hadn't

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

On Tue, Oct 20, 2020 at 12:30:05PM -0400, Mark Johnston wrote: > > I set up a RPi3 to try and repro this and have so far managed to trigger > it once using Peter Holm's stress2 suite, so I'll keep investigating. I > hadn't configured a dump device, but I was able to confirm from DDB that >

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

On Mon, Oct 19, 2020 at 04:09:09PM -0700, bob prohaska wrote: > On Mon, Oct 19, 2020 at 04:39:54PM -0400, Mark Johnston wrote: > > > > I think vmspace_exit() should issue a release fence with the cmpset and > > an acquire fence when handling the refcnt == 1 case, but I don't see why > > that

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

On Mon, Oct 19, 2020 at 04:39:54PM -0400, Mark Johnston wrote: > > I think vmspace_exit() should issue a release fence with the cmpset and > an acquire fence when handling the refcnt == 1 case, but I don't see why > that would make a difference here. So, if you can test a debug patch, > this one

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) > >> during a -j4 buildworld. The backtrace reports > >> > >> panic: non-current pmap 0xa00020eab8f0 > > > > Could you show the output of "show procvm" from the debugger? > > I s

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

The backtrace reports >> >> panic: non-current pmap 0xa00020eab8f0 > > Could you show the output of "show procvm" from the debugger? I see same panic too, in my case its very rare - typical scenario is rebuild of kf5 ports (~250, 2 days of full load). Any idea ho

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote: > Still seeing non-current pmap panics on the Pi3, this time a B+ running > 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) > during a -j4 buildworld. The backtrace reports > > panic: non-current pmap 0xf

panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

Still seeing non-current pmap panics on the Pi3, this time a B+ running 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) during a -j4 buildworld. The backtrace reports panic: non-current pmap 0xa00020eab8f0 cpuid = 0 time = 1601947137 KDB: stack backtrace: db_trace_self

Re: Rpi3 panic: non-current pmap 0xfffffd001e05b130

Earlier panics didn't have any proximate warnings on the console, but > they're > probably the same story. > > apologies for the noise! > > bob prohaska > > > > > panic: non-current pmap 0xfd001e05b130 > > cpuid = 0 > > time = 1575161361 > > KDB:

Re: Rpi3 panic: non-current pmap 0xfffffd001e05b130

/usr/src/sys/vm/vm_object.c:777 cpuid = 3 time = 1575164255 Earlier panics didn't have any proximate warnings on the console, but they're probably the same story. apologies for the noise! bob prohaska > panic: non-current pmap 0xfd001e05b130 > cpuid = 0 > time = 1575161361 >

Rpi3 panic: non-current pmap 0xfffffd001e05b130

A Pi3 running r355024 reported a panic while doing a -j3 make of www/chromium: panic: non-current pmap 0xfd001e05b130 cpuid = 0 time = 1575161361 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0x00729e4c lr = 0x001066c8 sp

Re: Panic with Current 351901 ISO image

On 9/8/19 6:03 PM, Curtis Hamilton wrote: I'm encountering (randomly) the below error when trying to install 351901 from CD/DVD. On what type of system ? -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional

Panic with Current 351901 ISO image

I'm encountering (randomly) the below error when trying to install 351901 from CD/DVD. timeout stopping cpus panic: acquiring blockable sleep lock with spinlock or critical section held (sleep mutex) vm map (system) @ /usr/src/sys/vm/vm_map.c:4066 cpuid = 0 time = 1 KDB: stack backtrace:

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Fri, Mar 23, 2018 at 4:19 PM, Konstantin Belousov wrote: > On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > > I ran into the original issue with r330539 on a Fusion VM. Trying this > > patch causes a different panic: > > > >

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Fri, Mar 16, 2018 at 2:56 AM, Konstantin Belousov wrote: > On Thu, Mar 15, 2018 at 09:38:56PM -0500, Peter Lei wrote: > > Some recent UEFI implementations have begun to leave the CPU with page > > write protection enabled in CR0. > > > > With r330539 which enables kernel

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Fri, Mar 23, 2018 at 04:44:36PM -0700, Mark Peek wrote: > On Fri, Mar 23, 2018 at 4:19 PM, Konstantin Belousov > wrote: > > > On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > > > I ran into the original issue with r330539 on a Fusion VM. Trying this > > >

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > I ran into the original issue with r330539 on a Fusion VM. Trying this > patch causes a different panic: > > https://people.freebsd.org/~mp/r330539-patched.png > > Thoughts? r331290 should fixed this issue. What is your kernel

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Thu, Mar 15, 2018 at 09:38:56PM -0500, Peter Lei wrote: > Some recent UEFI implementations have begun to leave the CPU with page > write protection enabled in CR0. > > With r330539 which enables kernel page protections, interesting things > happen during boot (aka panic) when protection is

amd64: panic on -CURRENT @r330539 for certain UEFI hosts

Some recent UEFI implementations have begun to leave the CPU with page write protection enabled in CR0. With r330539 which enables kernel page protections, interesting things happen during boot (aka panic) when protection is already enabled, including a write protection fault from an explicit

Re: panic on current during shutdown: panic: racct_adjust_resource: resource 4 usage < 0

On 20/01/2017 02:09, Larry Rosenman wrote: > Thu Jan 19 18:03:38 CST 2017 > > FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #13 r311997: Sat Jan > 14 22:35:29 CST 2017 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER > amd64 > > panic: racct_adjust_resource: resource 4 usage <

panic on current during shutdown: panic: racct_adjust_resource: resource 4 usage < 0

Thu Jan 19 18:03:38 CST 2017 FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #13 r311997: Sat Jan 14 22:35:29 CST 2017 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER amd64 panic: racct_adjust_resource: resource 4 usage < 0 GNU gdb (GDB) 7.12 [GDB v7.12 for FreeBSD]

reproducible kernel panic on CURRENT, I/O related

Dear all, since approximately three weeks I am seeing kernel panics on CURRENT that are in so far reproducible as that they typically occur when I run svn up on the ports tree. Hence, it seems I/O related to me. Sorry that I only now got around to reporting it! The system is a CURRENT amd64

Re: Panic on current amd64

On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote: H M I get the following panic on current svn ver r280793: H M H M Sat Mar 28 14:41:28 PDT 2015 H M H M FreeBSD/amd64 (pozo.com) (ttyu0) H M H M panic: Invalid CPU in callout 16 H H The same happened to me in the OFED code. After

Re: Panic on current amd64

On Mon, Mar 30, 2015 at 02:30:04PM -0700, Adrian Chadd wrote: A Would you mind filing a PR for it so it isn't forgotten? If I could provide enough information to fix that, I would either fix myself or forward information to someone confident in build. Creating PR with what I have now means

Re: Panic on current amd64

On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote: M I get the following panic on current svn ver r280793: M M Sat Mar 28 14:41:28 PDT 2015 M M FreeBSD/amd64 (pozo.com) (ttyu0) M M panic: Invalid CPU in callout 16 The same happened to me in the OFED code. After investigation

Re: Panic on current amd64

On 03/30/15 23:19, Gleb Smirnoff wrote: On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote: M I get the following panic on current svn ver r280793: M M Sat Mar 28 14:41:28 PDT 2015 M M FreeBSD/amd64 (pozo.com) (ttyu0) M M panic: Invalid CPU in callout 16 The same happened to me

Re: Panic on current amd64

On Tue, Mar 31, 2015 at 12:30:04AM +0200, Hans Petter Selasky wrote: H On 03/30/15 23:19, Gleb Smirnoff wrote: H On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote: H M I get the following panic on current svn ver r280793: H M H M Sat Mar 28 14:41:28 PDT 2015 H M H M FreeBSD

Re: Panic on current amd64

Hi, Would you mind filing a PR for it so it isn't forgotten? -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Panic on current amd64

On Tue, Mar 31, 2015 at 01:41:04AM +0300, Gleb Smirnoff wrote: On Tue, Mar 31, 2015 at 12:30:04AM +0200, Hans Petter Selasky wrote: H On 03/30/15 23:19, Gleb Smirnoff wrote: H On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote: H M I get the following panic on current svn ver

Re: Panic on current amd64

, Manfred Antar wrote: H M I get the following panic on current svn ver r280793: H M H M Sat Mar 28 14:41:28 PDT 2015 H M H M FreeBSD/amd64 (pozo.com) (ttyu0) H M H M panic: Invalid CPU in callout 16 H H The same happened to me in the OFED code. After investigation H

Re: Panic on current amd64

On Sat, Mar 28, 2015 at 3:02 PM, Manfred Antar n...@pozo.com wrote: I get the following panic on current svn ver r280793: Revert to r280784. This should fix. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo

Panic on current amd64

I get the following panic on current svn ver r280793: Sat Mar 28 14:41:28 PDT 2015 FreeBSD/amd64 (pozo.com) (ttyu0) login: panic: Invalid CPU in callout 16 cpuid = 2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe023705f370 panic() at panic+0x1c1

Re: Panic on current amd64

At 03:06 PM 3/28/2015, Davide Italiano wrote: On Sat, Mar 28, 2015 at 3:02 PM, Manfred Antar n...@pozo.com wrote: I get the following panic on current svn ver r280793: Revert to r280784. This should fix. That works Thanks || n...@pozo.com

Memory modified after free Kernel panic with current (r278031)

Hallo, I'm still fighting with MinnowBoard... When I set the network interface I get a bunch of Memory modified after free messages. If I wait long enough (a couple of minutes) I get a kernel panic. Here an example with the dmesg (https://pastebin.mozilla.org/8657938) I've tested it using

Re: ZFS panic in -CURRENT

the panic. Cheers ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: ZFS panic in -CURRENT

on 01/04/2014 16:57 R. Tyler Croy said the following: On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon a...@freebsd.org wrote: on 01/04/2014 02:22 R. Tyler Croy said the following: ... Also in addition to the photo from before of the panic, here's another reproduction photo:

Re: ZFS panic in -CURRENT

On Wed, 02 Apr 2014 09:58:37 +0300 Andriy Gapon a...@freebsd.org wrote: on 01/04/2014 16:57 R. Tyler Croy said the following: On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon a...@freebsd.org wrote: on 01/04/2014 02:22 R. Tyler Croy said the following: ... Also in addition to the

Re: ZFS panic in -CURRENT

on 02/04/2014 19:48 R. Tyler Croy said the following: On Wed, 02 Apr 2014 09:58:37 +0300 Andriy Gapon a...@freebsd.org wrote: on 01/04/2014 16:57 R. Tyler Croy said the following: On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon a...@freebsd.org wrote: on 01/04/2014 02:22 R. Tyler Croy

Re: ZFS panic in -CURRENT

on 01/04/2014 02:22 R. Tyler Croy said the following: Bumping this with more details On Fri, 28 Mar 2014 09:53:32 -0700 R Tyler Croy ty...@monkeypox.org wrote: Apologies for the rough format here, I had to take a picture of this failure because I didn't know what else to do.

Re: ZFS panic in -CURRENT

On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon a...@freebsd.org wrote: on 01/04/2014 02:22 R. Tyler Croy said the following: Bumping this with more details On Fri, 28 Mar 2014 09:53:32 -0700 R Tyler Croy ty...@monkeypox.org wrote: Apologies for the rough format here, I had to take

Re: ZFS panic in -CURRENT

Bumping this with more details On Fri, 28 Mar 2014 09:53:32 -0700 R Tyler Croy ty...@monkeypox.org wrote: Apologies for the rough format here, I had to take a picture of this failure because I didn't know what else to do. http://www.flickr.com/photos/agentdero/13469355463/ I'm building

ZFS panic in -CURRENT

Apologies for the rough format here, I had to take a picture of this failure because I didn't know what else to do. http://www.flickr.com/photos/agentdero/13469355463/ I'm building off of the GitHub freebsd.git mirror here, and the latest commit in the tree is neel@'s Add an ioctl to suspend..

Re: panic with -CURRENT @Boot [r259130]

On 10.12.13 03:52, Larry Rosenman wrote: On 2013-12-09 16:04, Aleksandr Rybalko wrote: On Mon, 9 Dec 2013 10:36:34 -0600 Larry Rosenman l...@lerctr.org wrote: Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root:

Re: panic with -CURRENT @Boot [r259130]

On Mon, 9 Dec 2013 10:36:34 -0600 Larry Rosenman l...@lerctr.org wrote: Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 259130

Re: panic with -CURRENT @Boot [r259130]

On 2013-12-09 16:04, Aleksandr Rybalko wrote: On Mon, 9 Dec 2013 10:36:34 -0600 Larry Rosenman l...@lerctr.org wrote: Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID:

Re: [panic] 10-CURRENT r239865: General protection fault (sysctl)

On Tue, Sep 11, 2012 at 6:32 PM, Glen Barber g...@freebsd.org wrote: I'd blame this one: http://lists.freebsd.org/pipermail/svn-src-head/2012-September/040236.html Yes, reverting that commit allows the system to boot. Hi, Same problem on my side (under Virtualbox or on an IBM 3550 M2).

Re: [panic] 10-CURRENT r239865: General protection fault (sysctl)

Am 09/12/12 09:30, schrieb Olivier Cochard-Labbé: On Tue, Sep 11, 2012 at 6:32 PM, Glen Barber g...@freebsd.org wrote: I'd blame this one: http://lists.freebsd.org/pipermail/svn-src-head/2012-September/040236.html Yes, reverting that commit allows the system to boot. Hi, Same

Re: [panic] 10-CURRENT r239865: General protection fault (sysctl)

on 12/09/2012 10:30 Olivier Cochard-Labbé said the following: On Tue, Sep 11, 2012 at 6:32 PM, Glen Barber g...@freebsd.org wrote: I'd blame this one: http://lists.freebsd.org/pipermail/svn-src-head/2012-September/040236.html Yes, reverting that commit allows the system to boot. Hi,

[panic] 10-CURRENT r239865: General protection fault (sysctl)

Hi, I upgraded to head/ r239865 (Last Changed Date: 2012-09-11 09:29:50). My laptop now panics with on boot with the new kernel. Backtrace (and hopefully some useful) information is attached. I can provide any additional information necessary. Regards, Glen Script started on Tue Sep 11

Re: [panic] 10-CURRENT r239865: General protection fault (sysctl)

On Tue, Sep 11, 2012 at 12:12:34PM -0400, Glen Barber wrote: G Hi, G G I upgraded to head/ r239865 (Last Changed Date: 2012-09-11 09:29:50). G G My laptop now panics with on boot with the new kernel. G G Backtrace (and hopefully some useful) information is attached. I can G provide any

Re: [panic] 10-CURRENT r239865: General protection fault (sysctl)

Hi, On Tue, Sep 11, 2012 at 08:19:54PM +0400, Gleb Smirnoff wrote: G I upgraded to head/ r239865 (Last Changed Date: 2012-09-11 09:29:50). G G My laptop now panics with on boot with the new kernel. G I'd blame this one:

Re: Tmpfs panic in -current

On (27/06/2012 13:29), Kevin Lo wrote: Kevin Lo wrote: Konstantin Belousov wrote: On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: Konstantin Belousov wrote: On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent -current several

Re: Tmpfs panic in -current

: I've observed a panic in recent -current several times but I only have a picture of the backtrace: http://people.freebsd.org/~kevlo/panic_tmpfs.jpg Does this look at all familiar to anyone? Can you look up the line corresponding to tmpfs_reg_resize

Re: Panic on current from yesterday during boot

on 27/06/2012 08:27 Andrey Fesenko said the following: On Wed, Jun 27, 2012 at 9:06 AM, Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Hi, I am getting a panix when I boot a newly compiled system with sources downloaded yesterday. The panic was still there with the sources from three

Re: Panic on current from yesterday during boot

Hi, On Wednesday 27 June 2012 13:20:10 Andriy Gapon wrote: on 27/06/2012 08:27 Andrey Fesenko said the following: On Wed, Jun 27, 2012 at 9:06 AM, Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Hi, I am getting a panix when I boot a newly compiled system with sources downloaded

Re: Panic on current from yesterday during boot

on 27/06/2012 11:39 Erich Dollansky said the following: Anyway, What would be a save way to get a trace to a disk as I do not have a backup system with me? Assuming I understand the question correctly your options are: - remote console (serial/firewire/etc) from another machine - digital camera

Re: Panic on current from yesterday during boot

Hi, On Wednesday 27 June 2012 15:42:43 Andriy Gapon wrote: on 27/06/2012 11:39 Erich Dollansky said the following: Anyway, What would be a save way to get a trace to a disk as I do not have a backup system with me? Assuming I understand the question correctly your options are: - remote

Re: Panic on current from yesterday during boot

On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon a...@freebsd.org wrote: on 27/06/2012 11:39 Erich Dollansky said the following: Anyway, What would be a save way to get a trace to a disk as I do not have a backup system with me? Assuming I understand the question correctly your options are: -

Re: Panic on current from yesterday during boot

on 27/06/2012 11:49 Erich Dollansky said the following: Hi, On Wednesday 27 June 2012 15:42:43 Andriy Gapon wrote: on 27/06/2012 11:39 Erich Dollansky said the following: Anyway, What would be a save way to get a trace to a disk as I do not have a backup system with me? Assuming I

Re: Panic on current from yesterday during boot

On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko f0and...@gmail.com wrote: On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon a...@freebsd.org wrote: on 27/06/2012 11:39 Erich Dollansky said the following: Anyway, What would be a save way to get a trace to a disk as I do not have a backup system

Re: Panic on current from yesterday during boot

on 27/06/2012 13:44 Andrey Fesenko said the following: On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko f0and...@gmail.com wrote: On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon a...@freebsd.org wrote: on 27/06/2012 11:39 Erich Dollansky said the following: Anyway, What would be a save way to

Re: Removing an SDHC card causes a kernel panic on -current

On 06/26/12 22:29, Kenneth D. Merry wrote: On Tue, Jun 26, 2012 at 19:41:07 -0400, Benjamin Kaduk wrote: On Tue, 26 Jun 2012, Michael Butler wrote: As follows, in g_disk_providergone, a NULL pointer reference?: g_disk_providergone() is new in r237518 (by ken); ken cc'd. Can you try the

Re: Tmpfs panic in -current

On Wed, Jun 27, 2012 at 01:29:14PM +0800, Kevin Lo wrote: Kevin Lo wrote: Konstantin Belousov wrote: On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: Konstantin Belousov wrote: On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent

Re: Removing an SDHC card causes a kernel panic on -current

On Wed, Jun 27, 2012 at 10:22:59 -0400, Michael Butler wrote: On 06/26/12 22:29, Kenneth D. Merry wrote: On Tue, Jun 26, 2012 at 19:41:07 -0400, Benjamin Kaduk wrote: On Tue, 26 Jun 2012, Michael Butler wrote: As follows, in g_disk_providergone, a NULL pointer reference?:

Re: Panic on current from yesterday during boot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-06-27 07:07:40 -0400, Andriy Gapon wrote: on 27/06/2012 13:44 Andrey Fesenko said the following: On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko f0and...@gmail.com wrote: On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon a...@freebsd.org

Re: Tmpfs panic in -current

: I've observed a panic in recent -current several times but I only have a picture of the backtrace: http://people.freebsd.org/~kevlo/panic_tmpfs.jpg Does this look at all familiar to anyone? Can you look up the line corresponding to tmpfs_reg_resize + 0x627

Re: Panic on current from yesterday during boot

Hi, On Wednesday 27 June 2012 23:20:09 Jung-uk Kim wrote: On 2012-06-27 07:07:40 -0400, Andriy Gapon wrote: on 27/06/2012 13:44 Andrey Fesenko said the following: On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko f0and...@gmail.com wrote: On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon

Re: Tmpfs panic in -current

On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: Konstantin Belousov wrote: On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent -current several times but I only have a picture of the backtrace: http://people.freebsd.org/~kevlo

Removing an SDHC card causes a kernel panic on -current

As follows, in g_disk_providergone, a NULL pointer reference?: imb@toshi:/home/imb sudo less /var/crash/core.txt.4 toshi.auburn.protected-networks.net dumped core - see /var/crash/vmcore.4 Tue Jun 26 08:59:01 EDT 2012 FreeBSD toshi.auburn.protected-networks.net 10.0-CURRENT FreeBSD 10.0-CURRENT

Re: Removing an SDHC card causes a kernel panic on -current

On Tue, 26 Jun 2012, Michael Butler wrote: As follows, in g_disk_providergone, a NULL pointer reference?: g_disk_providergone() is new in r237518 (by ken); ken cc'd. -Ben Kaduk imb@toshi:/home/imb sudo less /var/crash/core.txt.4 toshi.auburn.protected-networks.net dumped core - see

Re: Tmpfs panic in -current

Konstantin Belousov wrote: On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: Konstantin Belousov wrote: On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent -current several times but I only have a picture of the backtrace: http

Re: Removing an SDHC card causes a kernel panic on -current

On Tue, Jun 26, 2012 at 19:41:07 -0400, Benjamin Kaduk wrote: On Tue, 26 Jun 2012, Michael Butler wrote: As follows, in g_disk_providergone, a NULL pointer reference?: g_disk_providergone() is new in r237518 (by ken); ken cc'd. Can you try the attached patch to sys/geom/geom_disk.c? Also,

Panic on current from yesterday during boot

Hi, I am getting a panix when I boot a newly compiled system with sources downloaded yesterday. The panic was still there with the sources from three days ago. The panic regards /usr/src/sys/vm/uma_core/c line 2040. The machine is a Lenovo X220. I do not expect anything specific loaded yet as

Re: Panic on current from yesterday during boot

On Wed, Jun 27, 2012 at 9:06 AM, Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Hi, I am getting a panix when I boot a newly compiled system with sources downloaded yesterday. The panic was still there with the sources from three days ago. The panic regards /usr/src/sys/vm/uma_core/c

Re: Tmpfs panic in -current

Kevin Lo wrote: Konstantin Belousov wrote: On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: Konstantin Belousov wrote: On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent -current several times but I only have a picture

Re: Tmpfs panic in -current

On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent -current several times but I only have a picture of the backtrace: http://people.freebsd.org/~kevlo/panic_tmpfs.jpg Does this look at all familiar to anyone? Can you look up the line corresponding

Re: Tmpfs panic in -current

) kgdb backtrace 6) kgdb up 4 7) kgdb up 6 -- Up to line number 4. 7 -- Up to the next line. Best Regards, - Araujo 2012/6/25 Konstantin Belousov kostik...@gmail.com On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent -current several times but I only

Re: Tmpfs panic in -current

Konstantin Belousov wrote: On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: I've observed a panic in recent -current several times but I only have a picture of the backtrace: http://people.freebsd.org/~kevlo/panic_tmpfs.jpg Does this look at all familiar to anyone? Can you

Tmpfs panic in -current

I've observed a panic in recent -current several times but I only have a picture of the backtrace: http://people.freebsd.org/~kevlo/panic_tmpfs.jpg Does this look at all familiar to anyone? Kevin ___ freebsd-current@freebsd.org mailing list

Panic on current when enabling SUJ

Boot into single user-mode # tunefs -j enable / # tunefs -j enable /usr # tunefs -j enable /tmp # tunefs -j enable /var # reboot The machine then panics. Looks like the machine is trying to write to a read-only filesystem. ___

Re: Panic on current when enabling SUJ

On Thu, 3 Jun 2010, John Doe wrote: Boot into single user-mode # tunefs -j enable / # tunefs -j enable /usr # tunefs -j enable /tmp # tunefs -j enable /var # reboot The machine then panics. Looks like the machine is trying to write to a read-only filesystem. Can you please give me

Re: Panic on current when enabling SUJ

From: Jeff Roberson jrober...@jroberson.net To: John Doe lex...@ymail.com Cc: curr...@freebsd.org Sent: Thu, June 3, 2010 7:19:59 PM Subject: Re: Panic on current when enabling SUJ On Thu, 3 Jun 2010, John Doe wrote: Boot into single user-mode # tunefs -j

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... I saved that environment (documented elsewhere ini the thread), then performed the normal (for me) daily update, this time, to r207911. Again, I see a panic during transition from single-user mode to

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

Please try 207949 Thanks, Kip On Tue, May 11, 2010 at 6:18 AM, David Wolfskill da...@catwhisker.org wrote: On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... I saved that environment (documented elsewhere ini the thread), then performed

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

On Tue, May 11, 2010 at 08:30:09PM -0700, K. Macy wrote: Please try 207949 ... The panic (this time) didn't show up until about 10 seconds after the login: prompt showed up on the serial console. Here's what it looks like: ... 3 Select option, [Enter] for default 3 3 or [Space]

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

On Tue, May 11, 2010 at 9:24 PM, David Wolfskill da...@catwhisker.org wrote: On Tue, May 11, 2010 at 08:30:09PM -0700, K. Macy wrote: Please try 207949 ... The panic (this time) didn't show up until about 10 seconds after the login: prompt showed up on the serial console.  Here's what

Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

During transition to multi-user mode on first reboot after upgrading from r207812 - r207844; from the sserial console: 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 0 3 @DY GDB: no debug ports present KDB: debugger

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote: ... You don't happen to have a backtrace? Oops -- sorry; got caught up in getting ready to head in to work: db bt Tracing pid 20 tid 100067 td 0xc5a19000 _mtx_lock_flags(58,0,c0cd2d5b,570,80,...) at _mtx_lock_flags+0x46

RE: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while inkernel mode

Subject: Re: Panic @r207844;current process: flowcleaner Fatal trap 12: page fault while inkernel mode On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote: ... You don't happen to have a backtrace? Oops -- sorry; got caught up in getting ready to head in to work: db bt Tracing

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

Could you please try with 207902? Thanks, Kip On Mon, May 10, 2010 at 11:26 AM, David Wolfskill da...@catwhisker.org wrote: On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote: ... You don't happen to have a backtrace? Oops -- sorry; got caught up in getting ready to head in to

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

On Mon, May 10, 2010 at 2:32 PM, K. Macy km...@freebsd.org wrote: Could you please try with 207902? And if not, please get a coredump with a backtrace with symbols. Thanks ___ freebsd-current@freebsd.org mailing list

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... First, thanks for the response. OK; I grabbed r207902 applied it (via patch -p1), then rebuilt the kernel rebooted; here's the panic now: 3 Select option, [Enter] for default 3 3 or

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

Are you not able to dump core? Thanks, Kip On Mon, May 10, 2010 at 3:08 PM, David Wolfskill da...@catwhisker.org wrote: On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... First, thanks for the response. OK; I grabbed r207902 applied it (via

Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode

On Mon, May 10, 2010 at 03:52:07PM -0700, David Wolfskill wrote: On Mon, May 10, 2010 at 03:39:11PM -0700, K. Macy wrote: Are you not able to dump core? Here's the crash summary; I can put the dump on my Web server on request. (It weighs in at 89MB.) Compression reduced the

[CURRENT] Panic in -CURRENT of 20031105

Hi All, I get panics at random times of the day with -CURRENT from 20031105, with absolutely no load on the machine. The machine acts as a dial-up server/gateway/firewall for my local lan. I managed to get a coredump. The contents of the rt pointer passed to RTFREE() does really not look right

Re: [CURRENT] Panic in -CURRENT of 20031105

On Friday 07 November 2003 07:49 am, Jaco H. van Tonder wrote: Hi All, I get panics at random times of the day with -CURRENT from 20031105, with absolutely no load on the machine. The machine acts as a dial-up server/gateway/firewall for my local lan. I managed to get a coredump. The

Re: panic with -current kernel ata_timeout

On Tue, Oct 14, 2003 at 10:14:37PM +0200, Soren Schmidt wrote: It seems Christoph P. Kukulies wrote: Help! Am I alone with this? I cvsuped again today built world,kernel. Still this panic. Soeren, do you get this also? You have the Motherboard P4S8X which I donated a couple of months ago.

  1   2   3   >