Comment 2 for bug 90271

Hi Mark,

By "hangs" I mean it just sits there being totally unresponsive to any input
(keyboard etc). The only way to get around this is to hold the power button
to do a forced power off.

BTW, the place where it gets stuck is when it tries to load to the Realtek
8139cp module then tries to load the 8139too module. Right after it loads
the 8139too module it completely freezes.

This does not happen on on Ubuntu 5.10 but anything after that does not
work. So to install Ubuntu 6.10, I have to install 5.10 then upgrade
to 6.04then
6.10. All the while, using the same kernel from 5.10.

If I want to use any later kernel versions I have to blacklist these modules
(8139cp & 8139too) to prevent them from being loaded on bootup. But this is
kind of useless since I need an internet connection to do anything
meaningful.

This issue is common around the net as I did some research and lots of
people are running into this problem where they cannot even run the Live CD
of any ubuntu version after 5.10.

I hope this answers your question. I cannot provide a log of this since the
machine freezes completely. If you need anything else let me know as I'd
like to see this fixed in Feisty before its released. Or else I will be
stuck in Windows hell, esp. Vista hell since that is what this machine comes
pre-loaded with.

Regards,
Nik

On 3/6/07, Mark Reitblatt <email address hidden> wrote:

> Could you please explain what you mean by "hangs"? Does the kernel
> 'Oops' or does it just sit there for a long time? How do you know where
> it is hanging?
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => linux-source-2.6.20
> Importance: Undecided => High
> Status: Unconfirmed => Needs Info
>
> --
> RealTek 8139 hard-locks system on installation/modprobe
> https://launchpad.net/bugs/90271
>