Mario Sergio Fujikawa Ferreira
2010-Sep-19 22:31 UTC
Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010)
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 lioux@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
0xffffff006ecce000: tag ufs, type VREG
usecount 1, writecount 1, refcount 4 mountedhere 0
flags ()
v_object 0xffffff0151489870 ref 0 pages 8
lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025)
ino 119526591, on dev ufs/fsusr
0xffffff011107f938: tag ufs, type VREG
usecount 0, writecount 0, refcount 4 mountedhere 0
flags (VV_NOSYNC|VI_DOINGINACT)
v_object 0xffffff0151f7f870 ref 0 pages 1284
lock type ufs: EXCL by thread 0xffffff01882cc7c0 (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.
Regards,
--
Mario S F Ferreira - DF - Brazil - "I guess this is a signature."
feature, n: a documented bug | bug, n: an undocumented feature
Kostik Belousov
2010-Sep-22 13:28 UTC
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 lioux@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 > > 0xffffff006ecce000: tag ufs, type VREG > usecount 1, writecount 1, refcount 4 mountedhere 0 > flags () > v_object 0xffffff0151489870 ref 0 pages 8 > lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025) > ino 119526591, on dev ufs/fsusr > > 0xffffff011107f938: tag ufs, type VREG > usecount 0, writecount 0, refcount 4 mountedhere 0 > flags (VV_NOSYNC|VI_DOINGINACT) > v_object 0xffffff0151f7f870 ref 0 pages 1284 > lock type ufs: EXCL by thread 0xffffff01882cc7c0 (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 ? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100922/3e60a31d/attachment.pgp
Mario Sergio Fujikawa Ferreira
2010-Oct-01 18:47 UTC
Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010)
Quoting Kostik Belousov <kostikbel@gmail.com>:> 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 >> lioux@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 >> >> 0xffffff006ecce000: tag ufs, type VREG >> usecount 1, writecount 1, refcount 4 mountedhere 0 >> flags () >> v_object 0xffffff0151489870 ref 0 pages 8 >> lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025) >> ino 119526591, on dev ufs/fsusr >> >> 0xffffff011107f938: tag ufs, type VREG >> usecount 0, writecount 0, refcount 4 mountedhere 0 >> flags (VV_NOSYNC|VI_DOINGINACT) >> v_object 0xffffff0151f7f870 ref 0 pages 1284 >> lock type ufs: EXCL by thread 0xffffff01882cc7c0 (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