Date: Sat, 25 Apr 2009 11:19:49 +0200 From: Gustau Perez <gperez@entel.upc.edu> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, freebsd-usb@FreeBSD.org, wsk <wsk@gddsn.org.cn> Subject: Re: boot panic on current(04.20) Message-ID: <49F2D5B5.20607@entel.upc.edu> In-Reply-To: <alpine.BSF.2.00.0904241311030.54334@fledge.watson.org> References: <49ED3E7D.8080606@gddsn.org.cn> <200904212123.14016.hselasky@c2i.net> <49F05F8F.5000407@entel.upc.edu> <200904231436.43735.hselasky@c2i.net> <49F1A016.1050003@entel.upc.edu> <alpine.BSF.2.00.0904241311030.54334@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> I think more or less like wsk. Mmmm could it be related to the sysctl >> -a problem discussed today ? Will try recompiling fuse and kqemu. >> Will let you know. > > The above is characteristic of using an old module with a kernel > compiled for the new malloc.h. Rebuilding should fix it. Right. Kqemu and fusefs-kmod were the offending modules. Rebuilding them with against today sources fixed the problem. Instead nvidia driver doesn't have those problems ... There's still one issue that I can't test today (until next monday, because my dock is in the office) and is the hot undocking problem with usb, which seems to be fixed with r191395. I'll report ASAP. Regards, Gus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49F2D5B5.20607>