Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Dec 2013 20:08:33 +0200
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        sbruno@freebsd.org
Cc:        "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject:   Re: 10.0 BETA 3 with redports kernel panic
Message-ID:  <20131219180833.GN59496@kib.kiev.ua>
In-Reply-To: <1387473915.2494.0.camel@powernoodle.corp.yahoo.com>
References:  <1384029731.1819.7.camel@powernoodle.corp.yahoo.com> <20131109205030.GF59496@kib.kiev.ua> <1387217065.1407.3.camel@powernoodle.corp.yahoo.com> <1387219558.1407.6.camel@powernoodle.corp.yahoo.com> <20131217120019.GD59496@kib.kiev.ua> <1387285472.2372.2.camel@powernoodle.corp.yahoo.com> <1387473915.2494.0.camel@powernoodle.corp.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--Q3ice8WzhejeCQ7G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 19, 2013 at 09:25:15AM -0800, Sean Bruno wrote:
> On Tue, 2013-12-17 at 05:04 -0800, Sean Bruno wrote:
> > On Tue, 2013-12-17 at 14:00 +0200, Konstantin Belousov wrote:
> > > On Mon, Dec 16, 2013 at 10:45:58AM -0800, Sean Bruno wrote:
> > > > On Mon, 2013-12-16 at 10:04 -0800, Sean Bruno wrote:
> > > > > > What is the source line for memrw+0x195 ?
> > > > >=20
> > > > > My apologies for the delay on this.  Its been frustrating getting=
 a
> > > > > crashdump on these machines due to their very large tmpfs usage.
> > > > > Currently, I am dumping a crash of 13+GB to a third HD that we had
> > > > > installed for this purpose.
> > > > >=20
> > > > > The machines are still running RC3 of 10.0r.
> > > > >=20
> > > > > I will attempt to get the requested information shortly.
> > > > >=20
> > > > > sean
> > > > >=20
> > > > >=20
> > > >=20
> > > > I've updated http://people.freebsd.org/~sbruno/redbuild_panic.txt
> > > >=20
> > > > It looks like its dying in uiomove() ?
> > >=20
> > > I believe I already posted the following patch, with no feedback.
> > >=20
> > > diff --git a/sys/amd64/amd64/mem.c b/sys/amd64/amd64/mem.c
> > > index abbbb21..e371499 100644
> > > --- a/sys/amd64/amd64/mem.c
> > > +++ b/sys/amd64/amd64/mem.c
> > > @@ -98,7 +98,11 @@ memrw(struct cdev *dev, struct uio *uio, int flags)
> > >  kmemphys:
> > >  			o =3D v & PAGE_MASK;
> > >  			c =3D min(uio->uio_resid, (u_int)(PAGE_SIZE - o));
> > > -			error =3D uiomove((void *)PHYS_TO_DMAP(v), (int)c, uio);
> > > +			v =3D PHYS_TO_DMAP(v);
> > > +			if (v < DMAP_MIN_ADDRESS || v >=3D DMAP_MAX_ADDRESS ||
> > > +			    pmap_kextract(v) =3D=3D 0)
> > > +				return (EFAULT);
> > > +			error =3D uiomove((void *)v, (int)c, uio);
> > >  			continue;
> > >  		}
> > >  		else if (dev2unit(dev) =3D=3D CDEV_MINOR_KMEM) {
> >=20
> > Will begin testing immediately
> >=20
> > sean
>=20
>=20
> Huh ... both machines panic'd this morning.  It'll take 30 minutes or so
> to get a crash dump, but it looks like its still in the same place. =20
>=20
> db> whe
> Tracing pid 489 tid 101801 td 0xfffff80322946490
> kdb_enter() at kdb_enter+0x3e/frame 0xfffffe1839d26220
> panic() at panic+0x175/frame 0xfffffe1839d262a0
> vm_fault_hold() at vm_fault_hold+0x14ed/frame 0xfffffe1839d26500
> vm_fault() at vm_fault+0x77/frame 0xfffffe1839d26540
> trap_pfault() at trap_pfault+0x19b/frame 0xfffffe1839d265f0
> trap() at trap+0x5e6/frame 0xfffffe1839d26810
> calltrap() at calltrap+0x8/frame 0xfffffe1839d26810
> --- trap 0xc, rip =3D 0xffffffff80cae47b, rsp =3D 0xfffffe1839d268d0, rbp=
 =3D
> 0xfffffe1839d26920 ---
> copyout() at copyout+0x3b/frame 0xfffffe1839d26920
> memrw() at memrw+0x1b6/frame 0xfffffe1839d26960
> giant_read() at giant_read+0x7a/frame 0xfffffe1839d269a0
> devfs_read_f() at devfs_read_f+0xea/frame 0xfffffe1839d26a00
> dofileread() at dofileread+0x7b/frame 0xfffffe1839d26a40
> kern_readv() at kern_readv+0x65/frame 0xfffffe1839d26a90
> sys_read() at sys_read+0x63/frame 0xfffffe1839d26ae0
> amd64_syscall() at amd64_syscall+0x357/frame 0xfffffe1839d26bf0
> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe1839d26bf0
> --- syscall (3, FreeBSD ELF64, sys_read), rip =3D 0x800b750aa, rsp =3D
> 0x7fffffffd068, rbp =3D 0x7fffffffd0b0 ---
> db> call doadump
>=20

I need to see exact panic and trap messages, as well as I need to know
the source line for memrw+0x1b6 in the patched kernel.

--Q3ice8WzhejeCQ7G
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBAgAGBQJSszYgAAoJEJDCuSvBvK1BNGoP/i5bXZv4pMKiNugodOoCPT/K
6edxpSjkwzmpNAvTI4CEzOtthT+dAL7iGJVLFARuwtE/abxThJFnFaF0nUXhC4pA
oRMrzUDQtZsi98hnHqnu3KZbS18JNdB35q3GpHHaQMKprcxC+Kuv19y+IeQOPEzF
Z1Gr5pJpOrpSJW4iGtKEJIBd2hCYCKlw6k5G46bPABqdC0sEYcpcBm/Fgrg5qJv5
1hCXtNMvVEuKSgzwNOWo3FBbLRJjoMfYL/Nxk/fDe54uezAIopOLIUuj3eNODW3a
Y2BHL/6Ldxxau0AeuIYFZiV433Ezaj4YAhTwuZwsEIT7e0esIm2IBc7F4E3TzRcI
nxCbzk/iHVPL0pJ2bh3OM/oU8gb5fRlgA6sM3I/14J0D4sXzjUw5CZGV4mN7MtjX
t5/Lbje87nobSX/2e9BI21TDzrgdoYRV5x8biQsQ486If1z558gl/XXbikRuMula
Mod6k8cC2yQiN+N/9AJGMxAgv4WW1PTHxIT4foNFfv9vX2bn/F5cZQzTYwOg5kJM
5WBMMoVgN5Xo5N93zM828+49nnofT3wabPy48TWSptz3cTL7WQrm7QFA+0l6udPB
BZDMGgffuAhD10MyqpGfX8cHPgMcHE9pbnt9kb5vQZW/KoOE92RtwS2tL4aT2X0x
jzycG6VqK4gQSBxGuOVI
=WKSY
-----END PGP SIGNATURE-----

--Q3ice8WzhejeCQ7G--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131219180833.GN59496>