Date: Tue, 21 Jun 2005 16:18:36 +0200 From: Frode Nordahl <frode@nordahl.net> To: delphij@delphij.net Cc: freebsd-stable@freebsd.org, Robert Watson <rwatson@FreeBSD.org> Subject: Re: propagate_priority panic Message-ID: <A43FA80D-E2EB-4BFF-A57C-8609C146F30E@nordahl.net> In-Reply-To: <1118146251.755.4.camel@spirit> References: <2D2A5D81-9E95-4D83-B479-D61BBB39C25F@nordahl.net> <1118146251.755.4.camel@spirit>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7. jun. 2005, at 14.10, Xin LI wrote: > Hi, Frode, > > =E5=9C=A8 2005-06-07=E4=BA=8C=E7=9A=84 09:32 +0200=EF=BC=8CFrode = Nordahl=E5=86=99=E9=81=93=EF=BC=9A > >> Dear colleagues, >> > [snip] > >> db> trace >> Tracing pid 86 tid 100089 td 0xc54a1e10 >> propagate_priority(c54a1e10,c08f3750,c54c6960,c0901ae0,c54a1e10) at >> propagate_priority+0x7f >> turnstile_wait(c56f6a80,c0901ae0,c54c6960) at turnstile_wait+0x2e1 >> _mtx_lock_sleep(c0901ae0,c54a1e10,0,0,0) at _mtx_lock_sleep+0xf9 >> nfsrv_rcv(c5b32b64,c5b5b580,1) at nfsrv_rcv+0x4e >> sowakeup(c5b32b64,c5b32bb4) at sowakeup+0xad >> udp_append(c5a8c870,c5c96810,c5a99200,1c,ee83dc60) at udp_append=20 >> +0x158 >> udp_input(c5a99200,14,8e009fc3,0,0) at udp_input+0x5fb >> ip_input(c5a99200) at ip_input+0x4f1 >> netisr_processqueue(c08f5718) at netisr_processqueue+0xa3 >> swi_net(0) at swi_net+0xf2 >> ithread_loop(c5455e00,ee83dd48) at ithread_loop+0x159 >> fork_exit(c0605048,c5455e00,ee83dd48) at fork_exit+0x75 >> fork_trampoline() at fork_trampoline+0x8 >> --- trap 0x1, eip =3D 0, esp =3D 0xee83dd7c, ebp =3D 0 --- >> > > This looks like what I have been observed within a recent -CURRENT > kernel, which indicates a bug that was fixed recently. > > Would you please try the patch here: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/=20 > kern_switch.c.diff?r1=3D1.111&r2=3D1.112 > > You can safely ignore failed patch of Hunk #1, but if Hunk #2 and/=20 > or #3 > has been failed, please let us know your ident /sys/kern/kern_switch.c > output. Running with this patch the system livelocks instead, I have the =20 following trace from it: Tracing pid 84 tid 100087 td 0xc54a7a80 kdb_enter(c0854f33) at kdb_enter+0x2b siointr1(c55b8000) at siointr1+0xce siointr(c55b8000) at siointr+0x5e intr_execute_handlers(c53fb490,ee837b0c,4,ee837b5c,c07c3f53) at =20 intr_execute_handlers+0x7d lapic_handle_intr(34) at lapic_handle_intr+0x2e Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip =3D 0xc0617871, esp =3D 0xee837b50, ebp =3D = 0xee837b5c --- _mtx_lock_sleep(c090fac0,c54a7a80,0,0,0) at _mtx_lock_sleep+0xb9 nfsrv_rcv(c5ac7a20,c5c41c80,1) at nfsrv_rcv+0x4e sowakeup(c5ac7a20,c5ac7a70) at sowakeup+0xad udp_append(c5ac9870,c5c20810,caaae700,1c,ee837c60) at udp_append+0x158 udp_input(caaae700,14,8e009fc3,0,0) at udp_input+0x5fb ip_input(caaae700) at ip_input+0x4f1 netisr_processqueue(c09036f8) at netisr_processqueue+0xa3 swi_net(0) at swi_net+0xf2 ithread_loop(c5495000,ee837d48) at ithread_loop+0x159 fork_exit(c060bb38,c5495000,ee837d48) at fork_exit+0x75 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xee837d7c, ebp =3D 0 --- db> Any ideas? Thanks! Frode Nordahl frode@nordahl.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A43FA80D-E2EB-4BFF-A57C-8609C146F30E>