Now, actually, using either the 2.6.22-386 or 2.6.22-generic kernel, my
/var/log/messages looks like this (except repeated for thousands of
lines):

Jul 13 08:02:44 localhost kernel: [   66.191750] device-mapper: ioctl: error 
adding target to table
Jul 13 08:02:44 localhost kernel: [   66.192253] device-mapper: ioctl: error 
adding target to table
Jul 13 08:02:44 localhost kernel: [   66.192755] device-mapper: ioctl: error 
adding target to table
...
Jul 13 08:12:55 localhost kernel: [  679.351106] device-mapper: ioctl: error 
adding target to table
Jul 13 08:12:55 localhost kernel: [  679.351630] device-mapper: ioctl: error 
adding target to table
Jul 13 08:12:55 localhost kernel: [  679.352143] device-mapper: ioctl: error 
adding target to table

It seems that the kernel or device-mapper ( I can't tell which), is
taking over the processes. The desktop (and even tty1, etc.) are
completely unusable and manual reboot is required. I can load my
computer using the 2.6.20-16-386 kernel which I THINK came with Feisty.

What should I do?

-- 
device-manager - failure when launch application ?
https://bugs.launchpad.net/bugs/124641
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to