Comment 3 for bug 349778
Revision history for this message
| Leann Ogasawara (leannogasawara) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@Ludovico Cavedon and @Javier Jardón, it appears you have different hardware than the original bug reporter. Even though you may be experiencing the same symptoms reported here it really is likely hardware specific. You should open a separate bug report as it will likely require a different set of patches to resolve issues specific to your hardware. Could you also comment if the upstream 2.6.29 kernel resolves the issue as the original bug reporter commented - https:/
@joshual, can you attach your dmidecode:
sudo dmidecode > dmidecode.log
Can you also comment if using the "reboot=b" boot options helps as a workaround? To test using "reboot=b" press 'Escape' key at the 3 second pause by Grub bootloader. Then press 'e' (edit) on the buggy kernel entry, followed by 'e' again on the kernel line. Add "reboot=b" (without quotes) and press 'b' to boot. Thanks in advance.