gutsy tribe 5 hangs after reboot

ATA timeouts look kernel related. Speculative punting from Ubuntu -> linux-source-2.6.22 .

Could you please attach the information requested in https://wiki.ubuntu.com/KernelTeamBugPolicies ?

My system hangs so I cannot log in and attach the info asked. But I have written out the output that appears on the screen by hand. This is the exact output.

[216.923582] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[216.923665] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 4096 in

BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu4)
Built-in shall (ash)
Enter 'help' list of built -in commands
/bin/sh: can't access tty;
job control turned off"

[247.270842] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[247.270924] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 4096 in

[277.618079] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[277.618144] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 4096 in

[278.068442] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[278.115019] sd 2:0:0:0: [sdc] Assuming drive cache: write through

Possibly linked to issue 133666. That issue indicates a recognized issue with ATA / IDE detection. As indicated in the other issue, a patch has been created, but not yet applied in Ubuntu.

This issue is similar to bug #95857. I have also this problem, I see messages like this
end_request: I/O error, dev fd0, sector 0
and this
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in
on Dell Latitude C640 with Ubuntu 7.10 (final). The boot halts for about 2 minutes, after that it continues.

It seems that this bug affects most severely the debian based distros. In my case 20+ kernels. Feisty and every release before run without a hitch, also etch. Yesterday, I installed open suse, with the same kernel as ubuntu, and it installed without any problem. But I cannot install neither ubuntu nor sidux, both report the same problem discribed above, and both debian based. I also tried sabayon. It also reported similar problems as ubuntu but after that it installed properly and I can use it, the only inconvenience is that at each boot up it goes through the same error massages and it takes time but other than that no problem; but ubuntu gutsy is useless, I cannot even boot it up, it just hangs.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

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!