I can confirm mainline/vanilla kernels work, distribution kernel
doesn't.
The config diff isn't too long::
--- mainline
+++ distribution
+CONFIG_AUFS_BDEV_LOOP=y
+CONFIG_AUFS_BRANCH_MAX_127=y
+CONFIG_AUFS_BR_FUSE=y
+CONFIG_AUFS_BR_RAMFS=y
+CONFIG_AUFS_FS=m
+CONFIG_AUFS_HINOTIFY=y
As #16 says I receive a prompt to run fsck reporting that there was an
unexpected inconsistency as the last superblock write was (exactly) one
hour in the future. Not sure if it is relevant but I wondered if there
was an inconsistency between how Karmic was tracking time and I ran
** Summary changed:
- [Karmic] Hangs during shutdown
+ [Karmic] Hangs during shutdown with kernel 2.6.31rc7
--
[Karmic] Hangs during shutdown with kernel 2.6.31rc7
https://bugs.launchpad.net/bugs/418509
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Confirmed: Latest Kernel 2.6.31-7 fails to Shutdown! Older Kernel
releases work fine.
--
[Karmic] Hangs during shutdown with kernel 2.6.31rc7
https://bugs.launchpad.net/bugs/418509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can not get any of my 4 up to date installs of 9.10 64bit to shut down
right.
Not only that but they will not boot up either. Will boot somewhat to
recovery mode but not except password for terminal.
Installed another A4, no updates. Can boot it and boot to recovery menu
on others from
thinkpad t61p / nvidia 185 / 64 bits
even after sysrq-I (kill-all-tasks), the killall5 process from
rc6.d/sendsigs stay alive in the tasks list. Stack trace varies, here is
a sample one;
Aug 26 22:57:22 gug-laptop kernel: [ 237.267529] killall5 R running task
0 3759 3737
