Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

In message

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On Sun, Jan 28, 2018 at 7:38 PM, Cy Schubert wrote: > In message <2effa324-c428-6135-371b-acb00c803...@freebsd.org>, Allan > Jude write > s: > > On 2018-01-28 16:28, Warner Losh wrote: > > > On Sun, Jan 28, 2018 at 2:22 PM, thomas masper < > thomas.mas...@gmail.com> >

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On 2018-01-28 21:29, Warner Losh wrote: > > I've been seeing this today while working on my laptop. > > 1) insert USB stick. > 2) mount UFS partition to /mnt > 3) copy a file off > 4) umount /mnt > 5) remove usb stick > 6) instant panic > > Oddly, it is the same

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

In message <2effa324-c428-6135-371b-acb00c803...@freebsd.org>, Allan Jude write s: > On 2018-01-28 16:28, Warner Losh wrote: > > On Sun, Jan 28, 2018 at 2:22 PM, thomas masper > > wrote: > > > >> Hi, > >> similar panic happen to me when extracting a pendrive from laptop

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On Jan 28, 2018 6:41 PM, "Allan Jude" wrote: On 2018-01-28 16:28, Warner Losh wrote: > On Sun, Jan 28, 2018 at 2:22 PM, thomas masper > wrote: > >> Hi, >> similar panic happen to me when extracting a pendrive from laptop USB port >> (I tried 3

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On 2018-01-28 16:28, Warner Losh wrote: > On Sun, Jan 28, 2018 at 2:22 PM, thomas masper > wrote: > >> Hi, >> similar panic happen to me when extracting a pendrive from laptop USB port >> (I tried 3 different pendrive). >> No issue if I reboot or shutdown. I don't know

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On 01/28/2018 22:28, Warner Losh wrote: > On Sun, Jan 28, 2018 at 2:22 PM, thomas masper > wrote: > >> Hi, >> similar panic happen to me when extracting a pendrive from laptop USB port >> (I tried 3 different pendrive). >> No issue if I reboot or shutdown. I don't know

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

> Do you have a reproducible test case? Ideally, it would be 'insert and > remove usb thumb drive' but maybe there's more steps between insert and > removal. Exactly! Just insert and remove the usb thumb drive. Happen in both USB3 and USB2 ports of the laptop. Regards thomas On Sun, Jan 28,

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On Sun, Jan 28, 2018 at 2:22 PM, thomas masper wrote: > Hi, > similar panic happen to me when extracting a pendrive from laptop USB port > (I tried 3 different pendrive). > No issue if I reboot or shutdown. I don't know if those two issues are > related. > Do you have a

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

Hi, similar panic happen to me when extracting a pendrive from laptop USB port (I tried 3 different pendrive). No issue if I reboot or shutdown. I don't know if those two issues are related. panic: Releasing 6 with cnt = -559038242 GNU gdb (GDB) 8.0.1 [GDB v8.0.1 for FreeBSD] Copyright (C) 2017

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On Fri, Jan 26, 2018 at 07:47:48AM -0700, Warner Losh wrote: > On Fri, Jan 26, 2018 at 5:29 AM, David Wolfskill > wrote: > > > This is on my "build machine" (laptop is still building updated ports > > for today, so I don't know yet whether or not it encounters this.) > > >

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On Fri, Jan 26, 2018 at 5:29 AM, David Wolfskill wrote: > This is on my "build machine" (laptop is still building updated ports > for today, so I don't know yet whether or not it encounters this.) > Running a kernel with INVARIANTS, right? > I had performed a

Re: Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

On Fri, Jan 26, 2018 at 04:29:47AM -0800, David Wolfskill wrote: > This is on my "build machine" (laptop is still building updated ports > for today, so I don't know yet whether or not it encounters this.) > The laptop did the same source-based update, and did not exhibit the panic. (On

Panic on shutdown @r328436: "Unholding 6 with cnt = -559038242"

This is on my "build machine" (laptop is still building updated ports for today, so I don't know yet whether or not it encounters this.) I had performed a source-based update from r328393 to r328436, rebooted, performed "make delete-old-libs", and all seemed well. I then issued "sudo shutdown

Re: Panic at shutdown

2015-11-29 0:10 GMT+01:00 Garrett Cooper : > > > On Nov 28, 2015, at 12:32, Ranjan1018 . <21474...@gmail.com> wrote: > > > > Hi, > > > > sometimes I have the panic in the photo at shutdown: > > > > http://imgur.com/mXrgFLp > > > > Unfortunately this happens randomly. > > >

Re: Panic at shutdown

> On Dec 8, 2015, at 08:09, Ranjan1018 . <21474...@gmail.com> wrote: … > Probably the panic is caused by some memory already freed, the hex value of > 16045693110842147038 is 0xdeadc0dedeadc0de. > To solve the panic I need some tips form someone more expert than me in ZFS > code. Good

Panic at shutdown

Hi, sometimes I have the panic in the photo at shutdown: http://imgur.com/mXrgFLp Unfortunately this happens randomly. I am running: $ uname -a FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r291160M: Sun Nov 22 17:10:38 CET 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC amd64 Regards,

Re: Panic at shutdown

> On Nov 28, 2015, at 12:32, Ranjan1018 . <21474...@gmail.com> wrote: > > Hi, > > sometimes I have the panic in the photo at shutdown: > > http://imgur.com/mXrgFLp > > Unfortunately this happens randomly. > > I am running: > > $ uname -a > > FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT

Re: Panic on shutdown, r243674M

on 30/11/2012 00:36 Ed Maste said the following: Rev 243674 with some minor local changes. Please try this patch: http://people.freebsd.org/~avg/acpi_cpu_notify.2.diff I should have committed this earlier, but the fact that we were not getting much problems when updating resources in place lead

Re: Panic on shutdown, r243674M

Please try this patch: http://people.freebsd.org/~avg/acpi_cpu_notify.2.diff I should have committed this earlier, but the fact that we were not getting much problems when updating resources in place lead me to believe that we would not get more problems when first deleting and then

Panic on shutdown, r243674M

Rev 243674 with some minor local changes. #12 0x80bfd775 in trap_fatal (frame=0xff800025e870, eva=value optimized out) at /home/emaste/src/head-ro/sys/amd64/amd64/trap.c:867 #13 0x80bfda3a in trap_pfault (frame=0x0, usermode=0) at

Re: Panic on shutdown, r243674M

On 29 November 2012 17:36, Ed Maste ema...@freebsd.org wrote: #14 0x80bfd226 in trap (frame=0xff800025e870) at /home/emaste/src/head-ro/sys/amd64/amd64/trap.c:463 #15 0x80be71a2 in calltrap () at /tmp/exception-N6d6io.s:179 #16 0x808bb9c0 in rman_set_bustag ()

Re: video drivers are locked up; panic during shutdown

On Saturday, May 19, 2012 7:41:37 pm deeptec...@gmail.com wrote: A perhaps more useful crashinfo output, gathered with the use of the original (non-debug) kernel. It seems like the mutex was zero'd which can result in this panic when it tries to adaptively spin (it sees a thread owner of

video drivers are locked up; panic during shutdown

So while the unstable, reverse-engineered ATI drivers were locked up (which is usual, it happens ~5 times a day on average), I pressed the ATX power button to initiate a clean shutdown (statistically, this usually succeeds). During the shutdown procedure, a panic occurred. (As a result

panic during shutdown from vfs_umountall()

Running with a MAC kernel, about to try booting identical but non-MAC; I'm not able to reproduceit , however. bgfsck may have been running during the shutdown. Apparently the device vnode for /usr is vrele()'d one too many times at some point during the run, resulting in a panic. This is with

panic during shutdown in lockmgr()

Hi, with a -CURRENT kernel built today I am consistently getting a panic during shutdown. Unfortunately a debug kernel refuses to do a core dump, so I only have a naked stack trace: panic: lockmgr: thread 0xc1918720, not exclusive lock holder 0xc06b5660 unlocking #0 0xc04fc40a in doadump () #1

lockmgr panic on shutdown

I can confirm the lockmgr panic on shutdown reported by someone else earlier (whose message I mistakenly deleted). It looks like swapper is trying to undo a lock from pagedaemon and runs into trouble. This is probably related to the Giant pushdown of vm_pageout() that alc did last week. I'm

Re: lockmgr panic on shutdown

/i386/trap.c:1012 #15 0xc065d91d in Xint0x80_syscall () at {standard input}:144 On Sat, 1 Nov 2003, Doug White wrote: I can confirm the lockmgr panic on shutdown reported by someone else earlier (whose message I mistakenly deleted). It looks like swapper is trying to undo a lock from pagedaemon

RE: lockmgr panic on shutdown

I can confirm the lockmgr panic on shutdown reported by someone else earlier (whose message I mistakenly deleted). It looks like swapper is trying to undo a lock from pagedaemon and runs into trouble. This is probably related to the Giant pushdown of vm_pageout() that alc did last week. I'm

RE: lockmgr panic on shutdown

the lockmgr panic on shutdown reported by someone else earlier (whose message I mistakenly deleted). It looks like swapper is trying to undo a lock from pagedaemon and runs into trouble. This is probably related to the Giant pushdown of vm_pageout() that alc did last week. I'm building

RE: lockmgr panic on shutdown

up the whole thing to before the commit for the struct mount locking until jeff kan can straighten things out. On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote: I can confirm the lockmgr panic on shutdown reported by someone else earlier (whose message I mistakenly deleted). It looks like

RE: lockmgr panic on shutdown

For giggles I'm rolling back vfs_default.c back to 1.87 since its along the backtrace path. This didn't work so -CURRENT is fully broke. I'd suggest staying on 10/30 not before 4PM PST if you want to not crash on shutdown. The patch worked for me. (Well, a slightly modified one: I passed 0

RE: lockmgr panic on shutdown

On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote: For giggles I'm rolling back vfs_default.c back to 1.87 since its along the backtrace path. This didn't work so -CURRENT is fully broke. I'd suggest staying on 10/30 not before 4PM PST if you want to not crash on shutdown. The patch

RE: lockmgr panic on shutdown

On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote: The obvious solution might be to change line 1161 of ffs_vfsops to pass vget() curthread rather than td. I assume there's a good reason why thread0 is passed from boot(), but I can't see why that's of any use to the vnode locking. Passing thread0

panic on shutdown

Hey Guys, i got this panic on doing shutdown -r now. Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0100 fault virtual address = 0xdeadc0de fault code = supervisor read, page not present instruction pointer = 0x8:0xc0521678 stack pointer

Re: panic on shutdown

I should have added that this is a kernel todays sources on an smp system. FreeBSD bender 5.1-CURRENT FreeBSD 5.1-CURRENT #73: Sat Oct 25 20:30:56 CEST 2003 [EMAIL PROTECTED]:/space/obj/space/src/sys/BENDER i386 Florian C. Smeets wrote: Hey Guys, i got this panic on doing shutdown -r now

Kernel panic on shutdown of X server.

This problem started about Feb 19 and continues thru today's updates. Everything seems to work great until I shut down the X server at which time I get a fatal 'page fault while in kernel mode.' I have two -CURRENT machines at the moment and only the one with the nVidia driver (and kernel module)

Re: Kernel panic on shutdown of X server.

walt wrote: This problem started about Feb 19 and continues thru today's updates. Everything seems to work great until I shut down the X server at which time I get a fatal 'page fault while in kernel mode.' I have two -CURRENT machines at the moment and only the one with the nVidia driver

Re: Kernel panic on shutdown of X server.

Terry Lambert wrote: walt wrote: This problem started about Feb 19 and continues thru today's updates. Everything seems to work great until I shut down the X server at which time I get a fatal 'page fault while in kernel mode.' I have two -CURRENT machines at the moment and only the one with the

Re: Kernel panic on shutdown of X server.

On 11:50-0800, Feb 23, 2003, walt wrote: This problem started about Feb 19 and continues thru today's updates. Everything seems to work great until I shut down the X server at which time I get a fatal 'page fault while in kernel mode.' I have two -CURRENT machines at the moment and only the

Re: panic at shutdown, ums related?

On Wed, Apr 24, 2002 at 04:53:32PM -0700, Peter Wemm wrote: USB is pretty hosed. :-( For a while, removing the mouse didn't get detected and you had to kill moused manually. Then the removal event happened. A new moused would start but it was impossible to kill -9 the old moused. If

Re: panic at shutdown, ums related?

On 24 Apr, Terry Lambert wrote: USB is pretty hosed. :-( For a while, removing the mouse didn't get detected and you had to kill moused manually. Then the removal event happened. A new moused would start but it was impossible to kill -9 the old moused. If you remove the mouse again, it

panic at shutdown, ums related?

Hi, backtrace from the console, no core dump: panic: Removing other than first element usb_transfer_complete uhci_device_intr_abort usbd_ar_pipe usbd_abort_pipe ums_disable ums_close spec_close ... It seems I may get it at every shutdown, so if there's something I should look at... Bye,

Re: panic at shutdown, ums related?

Peter Wemm wrote: USB is pretty hosed. :-( For a while, removing the mouse didn't get detected and you had to kill moused manually. Then the removal event happened. A new moused would start but it was impossible to kill -9 the old moused. If you remove the mouse again, it instantly

Re: panic at shutdown

2. cvsup to r1.96 of tty_cons.c, which should fix this, but due to lack of testers and the inability to reproduce it here, is unverified. I've been testing it, and haven't had any panics, but since the panic was irregular anyway it's hard to say that it's fixed. Bill To Unsubscribe: send

Re: panic at shutdown

In article local.mail.freebsd-current/[EMAIL PROTECTED] you write: For about a week, I've been getting panics at shutdown, caused by cn_devopen() calling devsw() with a NULL dev argument. I imagine it may be related to recent changes in the console code. If it's of any interest, I have -Dh in

panic at shutdown

For about a week, I've been getting panics at shutdown, caused by cn_devopen() calling devsw() with a NULL dev argument. I imagine it may be related to recent changes in the console code. If it's of any interest, I have -Dh in my /boot.config. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED]

Re: panic at shutdown

On 1 Aug, Bill Fumerola wrote: #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); type 'bt', this tells us just about as much as if you said "it crashed". though, by the panic message, this seems to be a known bug.. If I see the same

Re: panic at shutdown

#7 0xc017a726 in vput (vp=0xc8710840) at vnode_if.h:794 #8 0xc01aee87 in ffs_sync (mp=0xc0ade800, waitfor=2, cred=0xc0721700, p=0xc026d5e0) at ../../ufs/ffs/ffs_vfsops.c:955 Change the vput(vp) call at line 955 of ffs_vfsops.c back to two separate calls (see previous revision):

panic at shutdown

I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: .. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2998272 initial pcb at 25b1c0 panicstr:

Re: panic at shutdown

On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote: I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: .. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as

Re: panic at shutdown

And Bill Fumerola spoke: On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote: I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: .. There is absolutely no warranty for GDB. Type "show warranty" for details.