Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010)
Quoting Kostik Belousov : On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira wrote: Hi, I've just began trying chrome web browser from http://chromium.hybridsource.org/ but it triggered 2 panics on my 8.1-STABLE system. $ uname -a FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep 16 09:52:17 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 The panic information is: panic: vm_page_unwire: invalid wire count: 0 cpuid = 0 KDB: enter: panic 0xff006ecce000: tag ufs, type VREG usecount 1, writecount 1, refcount 4 mountedhere 0 flags () v_object 0xff0151489870 ref 0 pages 8 lock type ufs: EXCL by thread 0xff00200947c0 (pid 25025) ino 119526591, on dev ufs/fsusr 0xff011107f938: tag ufs, type VREG usecount 0, writecount 0, refcount 4 mountedhere 0 flags (VV_NOSYNC|VI_DOINGINACT) v_object 0xff0151f7f870 ref 0 pages 1284 lock type ufs: EXCL by thread 0xff01882cc7c0 (pid 26689) ino 263, on dev md0 I've made available 2 ddb textdumps at: http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 I was able to use chrome prior to this latest kernel update. Now, I can reproduce a kernel panic even browsing www.google.com Please, let me know if I can provide any further information. Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel config ? Right on the spot. Removing ZERO_COPY_SOCKETS stopped the panics. The panics restart if I add them again. Regards, -- Mario S F Ferreira - DF - Brazil - "I guess this is a signature." feature, n: a documented bug | bug, n: an undocumented feature ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010)
On 09/22/2010 16:37, Kostik Belousov wrote: > On Wed, Sep 22, 2010 at 03:58:12PM -0400, jhell wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 09/22/2010 09:28, Kostik Belousov wrote: >>> On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira >>> wrote: Hi, I've just began trying chrome web browser from http://chromium.hybridsource.org/ but it triggered 2 panics on my 8.1-STABLE system. $ uname -a FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep 16 09:52:17 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 The panic information is: panic: vm_page_unwire: invalid wire count: 0 cpuid = 0 KDB: enter: panic 0xff006ecce000: tag ufs, type VREG usecount 1, writecount 1, refcount 4 mountedhere 0 flags () v_object 0xff0151489870 ref 0 pages 8 lock type ufs: EXCL by thread 0xff00200947c0 (pid 25025) ino 119526591, on dev ufs/fsusr 0xff011107f938: tag ufs, type VREG usecount 0, writecount 0, refcount 4 mountedhere 0 flags (VV_NOSYNC|VI_DOINGINACT) v_object 0xff0151f7f870 ref 0 pages 1284 lock type ufs: EXCL by thread 0xff01882cc7c0 (pid 26689) ino 263, on dev md0 I've made available 2 ddb textdumps at: http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 I was able to use chrome prior to this latest kernel update. Now, I can reproduce a kernel panic even browsing www.google.com Please, let me know if I can provide any further information. >>> >>> Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel >>> config ? >> >> This is triggered as well on a system without ZERO_COPY_SOCKETS just to >> clear that bit up. > I do not know what did prompted you to decide that the issue is the same. > There is nothing common except the word "panic" in the report by > lioux and your backtraces. > > You could have better luck showing your traces on the fs@ or asking zfs > porters directly. Well taking a stab at it I thought you were involved with that. Considering it is being triggered on the FS level there is somthing in common but that won't always mean the traces will be exact for two different file-systems. It may just as well be two different cases so Ill just forward them on to the correct people. Thanks anyway. Regards, -- jhell,v ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010)
On Wed, Sep 22, 2010 at 03:58:12PM -0400, jhell wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 09/22/2010 09:28, Kostik Belousov wrote: > > On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira > > wrote: > >> Hi, > >> > >>I've just began trying chrome web browser from > >> http://chromium.hybridsource.org/ but it triggered 2 panics on my > >> 8.1-STABLE system. > >> > >> $ uname -a > >> FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep > >> 16 09:52:17 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 > >> > >>The panic information is: > >> > >> > >> panic: vm_page_unwire: invalid wire count: 0 > >> cpuid = 0 > >> KDB: enter: panic > >> > >> 0xff006ecce000: tag ufs, type VREG > >> usecount 1, writecount 1, refcount 4 mountedhere 0 > >> flags () > >> v_object 0xff0151489870 ref 0 pages 8 > >> lock type ufs: EXCL by thread 0xff00200947c0 (pid 25025) > >> ino 119526591, on dev ufs/fsusr > >> > >> 0xff011107f938: tag ufs, type VREG > >> usecount 0, writecount 0, refcount 4 mountedhere 0 > >> flags (VV_NOSYNC|VI_DOINGINACT) > >> v_object 0xff0151f7f870 ref 0 pages 1284 > >> lock type ufs: EXCL by thread 0xff01882cc7c0 (pid 26689) > >> ino 263, on dev md0 > >> > >> > >>I've made available 2 ddb textdumps at: > >> > >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 > >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 > >> > >>I was able to use chrome prior to this latest kernel update. > >> Now, I can reproduce a kernel panic even browsing www.google.com > >> > >>Please, let me know if I can provide any further information. > > > > Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel > > config ? > > This is triggered as well on a system without ZERO_COPY_SOCKETS just to > clear that bit up. I do not know what did prompted you to decide that the issue is the same. There is nothing common except the word "panic" in the report by lioux and your backtraces. You could have better luck showing your traces on the fs@ or asking zfs porters directly. pgpY0ktYoKGOu.pgp Description: PGP signature
Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/22/2010 09:28, Kostik Belousov wrote: > On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira > wrote: >> Hi, >> >> I've just began trying chrome web browser from >> http://chromium.hybridsource.org/ but it triggered 2 panics on my >> 8.1-STABLE system. >> >> $ uname -a >> FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep 16 >> 09:52:17 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 >> >> The panic information is: >> >> >> panic: vm_page_unwire: invalid wire count: 0 >> cpuid = 0 >> KDB: enter: panic >> >> 0xff006ecce000: tag ufs, type VREG >> usecount 1, writecount 1, refcount 4 mountedhere 0 >> flags () >> v_object 0xff0151489870 ref 0 pages 8 >> lock type ufs: EXCL by thread 0xff00200947c0 (pid 25025) >> ino 119526591, on dev ufs/fsusr >> >> 0xff011107f938: tag ufs, type VREG >> usecount 0, writecount 0, refcount 4 mountedhere 0 >> flags (VV_NOSYNC|VI_DOINGINACT) >> v_object 0xff0151f7f870 ref 0 pages 1284 >> lock type ufs: EXCL by thread 0xff01882cc7c0 (pid 26689) >> ino 263, on dev md0 >> >> >> I've made available 2 ddb textdumps at: >> >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 >> >> I was able to use chrome prior to this latest kernel update. >> Now, I can reproduce a kernel panic even browsing www.google.com >> >> Please, let me know if I can provide any further information. > > Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel > config ? This is triggered as well on a system without ZERO_COPY_SOCKETS just to clear that bit up. Kostik, I am going to forward you two core.txt.NN files I had generated on a ZFS system that I used chrome on as well. I can trigger this repeatedly from 20-30 minutes of using chrome. Not sure whats going on here but maybe you can shed some light over both issues that seem to be the same thing. I do not mind if you forward these core.txt.NN files to other devs that may be interested and able to help. I still have the kernels for both of these so if more information is needed just let me know. Regards, - -- jhell,v -BEGIN PGP SIGNATURE- iQEcBAEBAgAGBQJMml/UAAoJEJBXh4mJ2FR+EkIH/j9lfSg1ZTMtn4vRgybvd+3F 0Sy88IgvltQmIicEaQ4MbQ9IpO/owsc362UexQvnbx38zVLRivfJYsDefAmG6Dex OVRuewzJzgr3YWv89t4OxZgWNcsyTFVZCLavCuGiUzbw52m83klc3Fubr0+wXI1G OtIEsaIFqaGHvgVSvGKlHLiv2/Q93bZ1kWCCHdHM3l4QIPG9ARuRR08bOVDQK0Xd GhMUVXfvV7fOF1cwzecQ5+AP4UDaExA3JRrkYf7IC8KkFgATbdA3RLbxypkkOf75 XVqBFmqjAQfIPc8vUvVd9WmC1tNfqJzJPQ3kl3B3HHs2K3g/BoZpeaUEGacXJ8o= =FyGm -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010)
On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > I've just began trying chrome web browser from > http://chromium.hybridsource.org/ but it triggered 2 panics on my > 8.1-STABLE system. > > $ uname -a > FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep 16 > 09:52:17 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 > > The panic information is: > > > panic: vm_page_unwire: invalid wire count: 0 > cpuid = 0 > KDB: enter: panic > > 0xff006ecce000: tag ufs, type VREG > usecount 1, writecount 1, refcount 4 mountedhere 0 > flags () > v_object 0xff0151489870 ref 0 pages 8 > lock type ufs: EXCL by thread 0xff00200947c0 (pid 25025) > ino 119526591, on dev ufs/fsusr > > 0xff011107f938: tag ufs, type VREG > usecount 0, writecount 0, refcount 4 mountedhere 0 > flags (VV_NOSYNC|VI_DOINGINACT) > v_object 0xff0151f7f870 ref 0 pages 1284 > lock type ufs: EXCL by thread 0xff01882cc7c0 (pid 26689) > ino 263, on dev md0 > > > I've made available 2 ddb textdumps at: > > http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 > http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 > > I was able to use chrome prior to this latest kernel update. > Now, I can reproduce a kernel panic even browsing www.google.com > > Please, let me know if I can provide any further information. Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel config ? pgpN8BHEAqKFh.pgp Description: PGP signature
