Howdy, and thank you for helping to make Ubuntu better. This does not
look like a problem with the particular features offered by Mythbuntu,
but a more general problem (hence the reason it affected you with Ubuntu
desktop). the short answer is that it looks somewhat like a hardware
problem, but it is possible that there was a driver or some other
software problem. Have you been able to resolve or affect it in any
way? Either way, please respond here with what you've tried so that
others can benefit.
Partial extract from the dmesg:
[ 23.249214] svc: failed to register lockdv1 RPC service (errno 97).
[ 23.254652] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
directory
[ 23.261001] NFSD: starting 90-second grace period
[ 25.480013] eth0: no IPv6 routers present
[ 37.042423] usplash:456 freeing invalid memtype
ffffffffe0000000-ffffffffe1000000
[ 240.430097] INFO: task events/0:6 blocked for more than 120 seconds.
[ 240.430155] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mythbuntu
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Mythbuntu 9.10 fails to startup giving kernel hung messages
https://bugs.launchpad.net/bugs/498717
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Invalid
Status in “linux” package in Ubuntu: Incomplete
Bug description:
Clean install of Mythbuntu 9.10 fails to start giving kernel hang messages
during boot. This problem first occurred following an upgrade from Hardy
(Ubuntu Desktop, not Mythbuntu) > Interpid > Jaunty > Karmic. I thought the
problem may be related to the multiple consecutive upgrades, so have now done a
fresh install of Mythbuntu 9.10. Given the described history, this bug may also
affect plain Ubuntu, but I have not tested.
Method of install:
Booted from MythBuntu 9.10 live CD and installed LVM so that I could perform
install onto a new LVM volume (I wanted to retain existing volumes on the
disk). chrooted into new root and installed lvm2 again to regenerate initrd
with lvm modules. Performed a reboot and encountered problem on 1st boot.
Second boot worked OK and I then did a full apt-get upgrade. Now all subsequent
boots fail during startup.
SSH server does start successfully, but login via ssh does not present prompt,
however I am able to execute commands via ssh, hence I have been able to
capture the output of dmesg (see attached). I have not been able to find
anything useful from dmesg despite hours of searching and I am getting beyond
my area of knowledge.
I am running the 64-bit version of MythBuntu on an AMD64 3000 / ASUS K8V-X SE
motherboard. Please let me know what other information is required.
Thanks in advance.
_______________________________________________
Mailing list: https://launchpad.net/~mythbuntu-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~mythbuntu-bugs
More help : https://help.launchpad.net/ListHelp
