Date: Tue, 20 Dec 2011 22:43:51 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Robert Watson <rwatson@FreeBSD.org> Cc: Attilio Rao <attilio@freebsd.org>, mdf@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sleeping thread (tid 100033, pid 16): panic in FreeBSD 10.0-CURRENT/amd64 r228662 Message-ID: <4EF10197.9040207@zedat.fu-berlin.de> In-Reply-To: <alpine.BSF.2.00.1112201552150.65078@fledge.watson.org> References: <4EED2F1C.2060409@zedat.fu-berlin.de> <20111217204514.2fa77ea2@kan.dyndns.org> <CAMBSHm_MHAhTMafuHkMh_CAdOcU4zgJUgbzTNhLvajDFSp45UA@mail.gmail.com> <201112200852.23300.jhb@freebsd.org> <CAJ-FndB7o_vjbJefz1Bxa%2B=DEVZDxBoGPdKcVr5vNHdu-pFEFA@mail.gmail.com> <alpine.BSF.2.00.1112201552150.65078@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig20A5A43AF2403D4621E827F7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 12/20/11 16:55, Robert Watson wrote: > On Tue, 20 Dec 2011, Attilio Rao wrote: >=20 >> As we are here, however, I have a question for Robert here: do you >> think we should support the _ddb() variant of options even in the case= >> DDB is not enabled in the kernel? >=20 > It's possible that _ddb() should be spelled _unlocked(), or perhaps > _debug(), but neither really suggests what the name should actually > imply: using it is safe only in a marginal (debugging) sense, and not i= n > a production code sense. One might also reasonable call them > stack_foo_dontusethis(). >=20 > The _ddb() variants are used in at least two not strictly DDB cases: > redzone support, and Solaris memory allocation. And, I guess, the > current lock debugging case that we're talking about now, but I'm not > sure if those debugging features specifically require DDB in the kernel= > themselves? >=20 > Robert Sorry, I have to come back to the topic of my hijacked thread ;-) I realized that the problem occured when I enabled, just for fun, some features in the kernel config file, in particular were these device ipmi device smbios device vdp device tpm My box in question does not have any IPMI facility, nor does it have a TPM chip or vdp. So I commented out vdp and tpm and the problem seems to be gone. I didn't find any manpage for smbios, the NOTES in amd64 says, it is for DMI informations, but dmidecide works also without explicitely enabling smbios in the kernel. If someone wish that I have to perform another try with those modules enabled, let me know. oh --------------enig20A5A43AF2403D4621E827F7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO8QGXAAoJEOgBcD7A/5N8u9sH/3sK9pN1sIdX8w36eYS5uxrH zWznFtLNuguwYDynDlihC8nYeU5rYnZPu5VVT+FQVvKjJqcMLLAC/HRPsHNp9Xtn oeM6JTxf+iTaKA6XSFfxoVMPlQVjnzKud2W3ovZQHTYXGT7vZp+YKX4atjrFB+HI fnGC2z4ZW52qDjd5gl4CgvmBRek4LvV665DX1C0N+AcBwc+k0dDtd1IdgLtecFus 73C5aAcOxUMa6HfzCrW/eBT3wCg28HBxM2FGYObnJ1Mq4JzUXxs2csde+0+Q+fF5 b2W1cYHoSvfpZpu9ME/uN6V1Tsw3x+PGVw3dQtSWBknoctlkKOy1SAvZLegngX4= =PzsA -----END PGP SIGNATURE----- --------------enig20A5A43AF2403D4621E827F7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF10197.9040207>