Lock up during on Phillips Freevents x53

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

By the looks of it (research etc), its the 8139too module that is hanging the ethdetect. What happens if we enable CONFIG_8139TOO_OLD_RX_RESET?

chuck

Sorry I haven't got back to you.

I can't get the boot process to get as far as running uname -a dmesg, so
I can't give you precise details of the build nor hardware found.

I have tried to recompile the 6.10 kernel with the
CONFIG_8139TOO_OLD_RX_RESET setting, but it still hangs looking for a
valid file system. This might be a nother issue with my kernel build
(built on a VMWare virtual PC) but I haven't had to much chance to
experiment.

I am more than happy to help with the testing of this new release as I
am reduced to running VMWare from Windows or struggling with FreeBSD
(which does boot).

Cheers

John

ChuckShort wrote:
> By the looks of it (research etc), its the 8139too module that is
> hanging the ethdetect. What happens if we enable
> CONFIG_8139TOO_OLD_RX_RESET?
>
> chuck
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Assignee: Cristian Aravena Romero => ChuckShort
>
>

Seems to be a duplicate of Bug #90271, but that one was filed 2007-03-07 (ie, later) but it has been confirmed and marked as high priority.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!