Wierd hangs (kinda) after dist-upgrade

[mhauber]

Alright. So far I really like Intrepid, and my upgrade from 8.04 (kde3) seemed to go without a hitch. And this being my first commitment to KDE4 is really saying a lot (for me). Major, major kudos to the folks who have made the improvements since 4s first couple of alpha releases.

I do have an interesting problem, but I assume my own ignorance is what is keeping me from figuring it out. During the booting process, the system seems to hang at several intervals. They are as follows:

/script/local-top
Waiting for root filesystem

Each time, I have gotten past it by pressing any key 10 times.

/script/init-bottom

Each time, I have gotten past it by pressing any key 3 times.

Starting basic networking

Each time, I have gotten past it by pressing any key 1 time.

This is repeatable at every boot, btw. Everything appears to go without a hitch after that.

I'm not seeing anything of interest in dmesg and was wondering where I would look this up in a log (or is there a verbose setting somewhere I can get a better idea of what is going on?)

Thanks if anyone has any ideas.

MHauber

[Snowhog]

Re: Wierd hangs (kinda) after dist-upgrade

Question: Do you by chance, have your filesystem encrypted?

What does your /etc/fstab file look like (post it please)?

[mhauber]

Re: Wierd hangs (kinda) after dist-upgrade

I'll even do better than that...

$ sudo fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x89d189d1

$ sudo blkid
/dev/sda1: UUID="5d99c38f-ae55-4a2e-aa9f-ed7426b3bae8" TYPE="ext3"
/dev/sda5: TYPE="swap" UUID="4d37cc81-084a-4f4e-9a10-800617cce1f6"

$ sudo mount
/dev/sda1 on / type ext3 (rw,relatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
lrm on /lib/modules/2.6.27-7-generic/volatile type tmpfs (rw,mode=755)
none on /proc/bus/usb type usbfs (rw,devgid=128,devmode=664)
securityfs on /sys/kernel/security type securityfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

$ sudo lsfs
sudo: lsfs: command not found

Um....

$ sudo cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=5d99c38f-ae55-4a2e-aa9f-ed7426b3bae8 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda5
UUID=4d37cc81-084a-4f4e-9a10-800617cce1f6 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# usbfs is the USB group in fstab file:
none /proc/bus/usb usbfs devgid=128,devmode=664 0 0

I noticed today that those "any keys" I'm pressing to get through the boot process also include the shift, alt, fn and control keys. It literally doesn't matter what keys I press.

Thanks

[Fintan]

Re: Wierd hangs (kinda) after dist-upgrade

Hmm.. that does look strange.

or is there a verbose setting somewhere I can get a better idea of what is going on?

Go to your /boot/grub/menu.lst and delete quiet and splash from the line:

title Intrepid Main 8.10, kernel 2.6.27-7-generic
uuid 149ae850-fbce-4cee-9bf3-c48e4c636846
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=149ae850-fbce-4cee-9bf3-c48e4c636846 ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic

this will give you verbose during boot.

Apart from that and maybe snowhogs encryption suspicion I can't really help any further.

[Snowhog]

Re: Wierd hangs (kinda) after dist-upgrade

The output of sudo mount (on my system) matches yours (except for the additional partitions I have) except for a single entry in yours:

binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

I don't have this, and I haven't a clue what it is or what it is for. You also have this in your fstab:

# usbfs is the USB group in fstab file:
none /proc/bus/usb usbfs devgid=128,devmode=664 0 0

I don't have this either, and I don't know why it is in yours. Did you put it there?

[Guest]

Re: Wierd hangs (kinda) after dist-upgrade

I've got the same problem on my Acer TM280 after upgrading to kernel 2.6.27-7. I have to press random keys or tickle the touchpad to 'keep it awake'. it's kinda talking with my old grandma
With the 2.6.24-21 kernel I have no problems so I don't think it's a fstab issue...

Any clue?

[mhauber]

Re: Wierd hangs (kinda) after dist-upgrade

I went ahead and did a backup and then a clean install to see if that made a difference. It did not. I did notice however that turning the wireless switch on, off, on, off (etc.) seems to keep the booting process going too.

In fact, the install CD did the same thing.

Pretty funny... I'd report a bug, but what would I report?

This weekend, I'll download and install the 32-bit version and see if that makes a difference.

MHauber

[Snowhog]

Re: Wierd hangs (kinda) after dist-upgrade

By any chance, does your BIOS have a power saving settings? It's a shot, and easy to check.

[mhauber]

Re: Wierd hangs (kinda) after dist-upgrade

This is a Compaq Presario F700 laptop. It's BIOS options are few more than setting the date and time. Pretty sorry, I know but it's still my fault. Next time I buy a laptop, I'll take a more objective look at whom/what I'm casting my pearls to.

I did find a solution at the following link, but it's not the solution that I'm looking for (power management doesn't seem to work right with this option there):

http://ubuntuforums.org/showpost.php?p=6121602

The poster (Josueped at post #9) suggests to add the acpi=noirq option to menu.lst, and I'm still looking up the downside to adding this, but it does solve the problem at boot.

Like I said though... This is probably not the desired solution, but it's a step in the right direction I think.

HTH

Mhauber