Hi! > core 2 duo, 2gigs of mem, 2 sata II disks, raid0, raid1 (both 0.9), lvm2, > ext3 above all of it. > > Modules: > Module Size Used by > tun 11012 1 <----- Using vpn! > bitrev 2240 1 tun > ipv6 269736 36 > arc4 2432 2 > ecb 3584 2 > crypto_blkcipher 18052 1 ecb > cryptomgr 3712 0 > crypto_algapi 15872 4 arc4,ecb,crypto_blkcipher,cryptomgr > ath5k 104640 0 > mac80211 140240 1 ath5k > crc32 4416 2 tun,mac80211 > sr_mod 15748 0 > rtc_cmos 10232 0 > rtc_core 17220 1 rtc_cmos > floppy 64488 0 > cfg80211 27920 2 ath5k,mac80211 > cdrom 37800 1 sr_mod > ohci1394 31412 0 > rtc_lib 3328 1 rtc_core > ieee1394 90808 1 ohci1394 > evdev 11584 5 > usbhid 49952 0 > hid 73664 1 usbhid > ff_memless 6088 1 usbhid > ehci_hcd 37388 0 One useful trick is trying to boot with init=/bin/bash, and see if the problem persists. If it is gone, it is likely one of the modules, and those may be binary-searched -- which is often easier than bisect. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
