[Virtual-pkg-base-maintainers] Bug#637857: Acknowledgement (base: Kernel panic - not syncing: Fatal exception in interrupt when shutdown the system)

[Javier Polo]

Ok, I solved the bug myself, lol.

Exactly, it was VirtualBox (PUEL version 4.1.0.). TODAY (15/08/11) has 
been released a new update (4.1.2) which fixs it!. At changelog of that 
version says:

Linux hosts: fixed random kernel panics on host suspend / shutdown 
(4.1.0 regression; bug #9305 <http://www.virtualbox.org/ticket/9305>)

  Incredible... who would think that *HOST* machine would be freeze with 
a kernel panic because of a virtualization software instead of the guest 
machine...

Bug can be closed.


El 15/08/11 19:35, Javier Polo escribió:
> Ok, I tried with param *nosmp* in grub and it worked. Well "worked" 
> means that I didnt get that kernel panic during shutdown but I was 
> just with 1 CPU!.
>
> So, this morning I tried a new fresh install to catch the error. 
> Conclusions are:
>
> 1) In a fresh installation I cant reproduce the error.
>
> So I started to install/configuring my debian squeeze and until now 
> what I can say is:
>
> A) I configured wireless adding firmware: 
> firmware-iwlwifi_0.28_all.deb: no error.
> B) I configured propietary drivers of Nvidia for getting 
> Compiz+Emerald: no error.
> C) I installed google chrome from repositories.
>
> I thought the problem would be in Nvidia propietary drivers but I was 
> wrong. My last chance is that VirtualBox (PUEL version) will be the 
> guilty.
>
> *
> *El 15/08/11 12:51, Javier Polo escribió:
>> I have 2 bank memories (1 Gb each one). As I read anything referred 
>> to a hardware problem with memory, I tested without them (I took them 
>> off physically one by one) and the problem still remains. :-(
>> MemTest didnt say anything wrong in Quick test neither.
>>
>>
>