Am Sonntag 02 Oktober 2011, 22:34:25 schrieb J.Marcos Sitorus: > Hi Volker, > I just update VirtualBox from 4.0.8 to 4.1.2 today, and when emerge > finished I read the message that I need to manually put virtualbox > modules to /etc/conf.d/modules. > The module I said that I set to autoload on boot was the kernel module > (kvm-amd and several other modules). That mean that I never put > virtualbox modules to autoload on boot. > > And today I get another crash when I copy somefiles to my backup > partition on LVM (virtualbox not running, although now I set the > virtualbox modules to autoload on boot).
but you had them loaded: Modules linked in: btrfs libcrc32c vboxnetflt vboxnetadp vboxdrv snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device nls_cp437 vfat fat fuse sr_mod cdrom virtio_pci virtio_net virtio_ring virtio vhost_net tun kvm_amd kvm bridge stp llc usb_storage usbhid snd_hda_codec_realtek sg snd_hda_intel snd_hda_codec snd_pcm thermal snd_timer processor rtc firewire_ohci snd thermal_sys r8169 ohci_hcd firewire_core mii ehci_hcd k10temp i2c_piix4 snd_page_alloc crc_itu_t You are also using btrfs AND reiser4. Hint: only use one unstable fs at a time. Get 2.6.38. Patch it with reiser4. Retry. If your box still crashes, report it on reiserfs-devel mailing list. If not, well, everything past 2.6.38 is pretty much broken (and known as broken). Your X hangups are caused by that first crash. Btw, invalid opcode here, null pointers there and a biostar mainboard - which itself is worrisome. Make sure that you have the latest bios installed. This whole thing smells really fishy. Hardwarish... > > I have attached the dmesg after the crash. I notice this messages: > ------------[ cut here ]------------ > kernel BUG at fs/reiser4/block_alloc.c:151! > invalid opcode: 0000 [#1] > last sysfs file: /sys/devices/virtual/hwmon/hwmon2/temp1_input > CPU 0 > > Does it mean something wrong with my CPU? I have check the CPU > temperature from BIOS and it's normal, only 52 Celcius. no, you can ignore that line. It just tells you the last accessed sysfs file. Which is pretty much not an issue. > > What is the cause of this crash? maybe your bios is missing the latest microcode update maybe your hardware has gone bad maybe it is a bad interaction between the in-kernel amd graphics drivers and reiser4 maybe it is a bad interaction between virtualbox and the rest. maybe it is caused by the fact that you are still using a non-vanilla, plain 2.6.38 -- #163933
