Date: Thu, 29 Apr 2010 11:17:03 +0200 From: =?UTF-8?Q?Marius_N=C3=BCnnerich?= <marius@nuenneri.ch> To: yuri@rawbw.com Cc: freebsd-hackers@freebsd.org Subject: Re: How to troubleshoot why VirtualBox kernel module freezes the system? Message-ID: <h2zb649e5e1004290217z34f771f6wfaee378398ec4153@mail.gmail.com> In-Reply-To: <4BD8980A.9000706@rawbw.com> References: <4BD8980A.9000706@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 28, 2010 at 22:18, Yuri <yuri@rawbw.com> wrote: > VirtualBox kernel module (port emulators/virtualbox-ose-kmod) began to cause > system freezes from some kernel change around the end of January. > Once the system freezes it has to be rebooted. Soundcard, if it was playing > something, begins to cycle some very short piece. > Nothing is logged into /var/log/messages. > > Is there any way to troubleshoot this, like enabling some kernel > configuation options? > What is normally done in such case? > Should I run system under kernel debugger? But would it detect something if > it's not a SEGV but the freeze? It freezes for me too after a short while when I use the nvidia blob (8.0-RELEASE/amd64). Does your machine have firewire and do you have a second machine with firewire? I heard that it should be possible to read the ram contents of a frozen machine over firewire. I only have one firewire machine so I can't test.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?h2zb649e5e1004290217z34f771f6wfaee378398ec4153>