Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT

看板FB_stable作者時間15年前 (2010/09/23 05:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串4/5 (看更多)
--vAlDtAs5WEb1aNYe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 22, 2010 at 03:58:12PM -0400, jhell wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 09/22/2010 09:28, Kostik Belousov wrote: > > On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreir= a 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 S= ep 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 =3D 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. > >=20 > > Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel > > config ? >=20 > 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. --vAlDtAs5WEb1aNYe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkyaaSEACgkQC3+MBN1Mb4ib1ACfYDtOr1Gyydr0JcTILJ+VLl20 KDsAoIMVJLvn+FwJYFd6S9RZ7YyH/36T =7PW4 -----END PGP SIGNATURE----- --vAlDtAs5WEb1aNYe--
文章代碼(AID): #1CccwFhF (FB_stable)
討論串 (同標題文章)
文章代碼(AID): #1CccwFhF (FB_stable)