Re: [gentoo-user] X hang / occasionally after using LVM
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: [#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
Re: [gentoo-user] X hang / occasionally after using LVM
Am Freitag 30 September 2011, 18:34:48 schrieb J.Marcos Sitorus: do you have any crashes when virtualbox was not started and no virtualbox modules are loaded? I was suffer another crash when I backup my data to the other partition on LVM, when virtualbox not running I set virtualbox modules to autoload on boot then don't load them and retry. are you able to reproduce the problem with a vanilla kernel? Make sure you are using 2.6.38 - not .1 or greater. Reiser4 sometimes breaks with stable releases - and 2.6.38.X was very broken... I never use vanilla kernel. I always though that kernel with rX always better that the kernel without rX which is not true for reiser4. And vanilla kernels are the ones you should use whenever you are patching yourself. Less likely to get hit by strange interaction. -- #163933
Re: [gentoo-user] X hang / occasionally after using LVM
do you have any crashes when virtualbox was not started and no virtualbox modules are loaded? I was suffer another crash when I backup my data to the other partition on LVM, when virtualbox not running I set virtualbox modules to autoload on boot btw the logs after a crash not after a clean boot are the usefull ones ;) that's the problem. I was suffering this problem about a week ago. So I don't have that log :( are you able to reproduce the problem with a vanilla kernel? Make sure you are using 2.6.38 - not .1 or greater. Reiser4 sometimes breaks with stable releases - and 2.6.38.X was very broken... I never use vanilla kernel. I always though that kernel with rX always better that the kernel without rX On Thu, Sep 29, 2011 at 11:11 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: Am Donnerstag 29 September 2011, 09:11:09 schrieb J.Marcos Sitorus: Hi Volker, Thanks for the reply. I have attach dmesg, xorg log, xsession-error, and kdm log. So - get back to your last working versions - oh and those lvm volumes are on new disks? Nope. Previously I have two separate partition. Then I delete both partition and create LVM from the free space. ok - did you check that the devices are error-free (with badblocks)? You did not knock the ram loose while putting them in? What do you mean by knock the ram loose? Sorry, English is not my mother language. M. Mol answered that. Since you did not put in new disks, you have hardly done any damage ;) btw the logs after a crash not after a clean boot are the usefull ones ;) A couple of questions: do you have any crashes when virtualbox was not started and no virtualbox modules are loaded? do you have any other odd behaviour - occasional segfaults etc? which options did you use when you run mkfs.reiser4? are you able to reproduce the problem with a vanilla kernel? Make sure you are using 2.6.38 - not .1 or greater. Reiser4 sometimes breaks with stable releases - and 2.6.38.X was very broken... -- #163933 -- Salam, J.Marcos S. Sent from X1™
Re: [gentoo-user] X hang / occasionally after using LVM
Am Donnerstag 29 September 2011, 09:11:09 schrieb J.Marcos Sitorus: Hi Volker, Thanks for the reply. I have attach dmesg, xorg log, xsession-error, and kdm log. So - get back to your last working versions - oh and those lvm volumes are on new disks? Nope. Previously I have two separate partition. Then I delete both partition and create LVM from the free space. ok - did you check that the devices are error-free (with badblocks)? You did not knock the ram loose while putting them in? What do you mean by knock the ram loose? Sorry, English is not my mother language. M. Mol answered that. Since you did not put in new disks, you have hardly done any damage ;) btw the logs after a crash not after a clean boot are the usefull ones ;) A couple of questions: do you have any crashes when virtualbox was not started and no virtualbox modules are loaded? do you have any other odd behaviour - occasional segfaults etc? which options did you use when you run mkfs.reiser4? are you able to reproduce the problem with a vanilla kernel? Make sure you are using 2.6.38 - not .1 or greater. Reiser4 sometimes breaks with stable releases - and 2.6.38.X was very broken... -- #163933
Re: [gentoo-user] X hang / occasionally after using LVM
Am Mittwoch 28 September 2011, 09:25:56 schrieb J.Marcos Sitorus: Hi list, I have started using LVM about a week ago. I have created one volume group name and two logical volume. Both of the logical volume formatted with reiser4 file system, one volume as my backup home and the other volume used for VirtualBox. Since I use this setting, X ofter hang/crash. Sometime it happen when I use VirtualBox, the other time occur when I copy the files on the home folder to my backup home. Is this bug from LVM or only me suffer this? Attached is the /var/log/messages and emerge --info. plain dmesg + xorg.0.log and maybe .xession-errors probably would have more usefull. I guess you updated your kernel/graphics drivers. You get a general protection fault, and a null pointer deference and everytime virtualbox is there. So - get back to your last working versions - oh and those lvm volumes are on new disks? You did not knock the ram loose while putting them in? -- #163933
Re: [gentoo-user] X hang / occasionally after using LVM
On Wed, Sep 28, 2011 at 10:11 PM, J.Marcos Sitorus gkj...@gmail.com wrote: You did not knock the ram loose while putting them in? What do you mean by knock the ram loose? Sorry, English is not my mother language. He's asking if you may have bumped your RAM modules when connecting new hard drives. (Which you've now said aren't new, anyway, so that's irrelevant) -- :wq
