Date: Thu, 19 Jan 2006 22:01:05 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Julian Elischer <julian@elischer.org> Cc: current@freebsd.org Subject: Re: kernel thread as real threads.. Message-ID: <20060120030105.GA5286@xor.obsecurity.org> In-Reply-To: <43D05151.5070409@elischer.org> References: <43D05151.5070409@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 19, 2006 at 06:56:17PM -0800, Julian Elischer wrote: >=20 > some progrsss.. > as the first few lines show, it's not quite perfect yet but it's most of= =20 > the way there.. > (Like proc 1 isn't init) >=20 > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > panic: blockable sleep lock (sleep mutex) buffer daemon lock @=20 > /usr/src/sys/kern/vfs_bio.c:2048 > cpuid =3D 2 > KDB: enter: panic > [thread pid 0 tid 100051 ] > Stopped at kdb_enter+0x2b: nop =20 > db> ps > pid proc uid ppid pgrp flag stat wmesg wchan cmd > 1 c7cb1000 0 0 0 0000200 [SLPQ g_waitidle=20 > 0xc07239ec][SLP] swapper > 0 c0723c40 0 0 0 0000288 (threaded) swapper > thread 0xc7d6a340 ksegrp 0xc7cb0960 [RUNQ] schedcpu > thread 0xc7d6a4e0 ksegrp 0xc7cb09c0 [RUNQ] nfsiod 3 What about that threads don't show CPU usage or accumulate CPU time? This is annoying enough for user threads but would be a pretty serious usability limitation if it happened for kernel threads too. Kris --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0FJxWry0BWjoQKURAn5dAKCYShVsA/kdeso3tlmt8ueybzyAkQCg9VIk 1Wi/j79j2fOsRUE538/wPwY= =v9eF -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060120030105.GA5286>