previous linux security update fixed my ipw2100, but last one broke it again

More information about freezing: there are 2 different types of messages in syslog:

1. kernel: [ 856.828000] ipw2100: Fatal interrupt. Scheduling firmware restart.
2. kernel: [ 8556.332000] NETDEV WATCHDOG: eth1: transmit timed out

The first one is well known and I thought that it is inevitable.
Second one sometimes follows the freezing without the first message and after the second message transmission is restored.

I was happy with 2.6.20-16.31 because it fixed both problems, but 2.6.20-16.32 returned them back.

Now it looks like freezing with 2.6.20-16.31 happens with NETDEV WATCHDOG timeout, but it is rare.

Part of my /var/log/messages here, no fatal interrups from ipw2100:

Sep 30 17:25:46 x10 -- MARK --
Sep 30 17:41:32 x10 kernel: [13031.128000] NETDEV WATCHDOG: eth1: transmit timed out
Sep 30 17:55:54 x10 kernel: [13893.128000] NETDEV WATCHDOG: eth1: transmit timed out
Sep 30 17:57:20 x10 kernel: [13979.436000] NET: Registered protocol family 17
Sep 30 18:25:48 x10 -- MARK --
Sep 30 18:30:20 x10 kernel: [15959.560000] NETDEV WATCHDOG: eth1: transmit timed out
Sep 30 18:45:48 x10 -- MARK --
Sep 30 19:05:48 x10 -- MARK --
Sep 30 19:25:48 x10 -- MARK --
Sep 30 19:45:49 x10 -- MARK --
Sep 30 19:59:36 x10 kernel: [21315.280000] NETDEV WATCHDOG: eth1: transmit timed out

Previous log was captured while running 2.6.20-16.31

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to test the new kernel using the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

The ipw2100 driver has not changed at all since January of 2007 so it seems unlikely that the security updates are related to your particular issue. Additionally, in regards to your "Fatal interrupt" message this is bug 24776 regarding the ipw2100 driver. This is a known issue with the ipw2100 driver and you can learn more about it in that bug and the corresponding upstream bug report.

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!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!