In message
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>
>
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
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
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
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
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
> 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,
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
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
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.)
> >
>
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
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
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.
> >
>
> 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
> 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
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
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
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 ()
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.
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
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
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
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
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
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
#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):
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
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.
29 matches
Mail list logo