kernel 2.6.22 crash on toshiba m30x-127

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug inlinux-source-2.6.22

could you attach teh output of the following command to this bug please ? (https://wiki.ubuntu.com/KernelTeamBugPolicies)

    * uname -a > uname-a.log
    * cat /proc/version_signature > version.log
    * dmesg > dmesg.log
    * sudo lspci -vvnn > lspci-vvnn.log

   thanks,

      Koen

Hi Bruno,

Thank you for attaching this information. However, this info is from when you boot the 2.6.20 kernel. What is going to most helpful to us is the information from when you boot with the 2.6.22 kernel, particularly the dmesg output. This will be tricky though because of the automatic shutdown you run into. There a few things you can try, boot into the 2.6.22 kernel and let it automatically shutdown. Then boot into the known good 2.6.20 kernel. Check /var/log/kern.log.0 and see if it captured anything from when you booted the 2.6.22 kernel. If so, please attach this file. The other option you can try is booting with the 2.6.22 kernel but remove 'quiet' and 'splash' from you kernel command line? This can be done with the following:

1) Press 'Escape' key at the 3 second pause by Grub bootloader.
2) Then press 'e' (edit) on the 2.6.24 kernel entry, followed by 'e' again on the kernel line.
3) Then remove the 'splash' and 'quiet' keywords and press 'b' to boot.

If can can take a digital photo of any errors you see prior to it automatically shutting down, this will help us out with debugging. Then just attach the photo to this report. Thanks!

hi Leann,

I did what you suggest me and i did not found anything on kern.log.0, however i did found at kern.log, which i will attach here anyway, However, i dont know much about how linux works, but i think that the problem is not the kernel alone, because if i switch the computer on and leave on the log in area (GDM), it will stay there as long as necessary without shutdown, i always fault that was the battery manager.

On failsafe GNOME, the battery manager do not recognize the battery status, and the system stay longer than the normal boot.

hi leann,

i was wrong, the problem is everywhere even on the log in area. i recorded in quick time extension and i will make it available for you to see it on

http://bruno.dyn-o-saur.com/movies.html

There are nothing special there, however it can see more or less the problem, but not the soluttion, i hope that is useful for you otherwise contact me and i will see if i can help you more than that

Hmm. I've a theory -- based on what others are reporting about the Intel 82801 IDE controllers.

When you boot into the 2.6.20 kernel and run 'lsmod', do you have the 'sis5513' module listed amongst the list? If so, that could be the problem. The Ubuntu kernel folk chose to disable the sis5513 module for the 2.6.22 kernels. No explanation given, and its causing quite a bit of grief to those that use hardware supported by this module.

Cheers!

hi David,

 i checked the lsmod but the 'sis5513' is not enabled.
I also attached a log of the lsmod.

i hope that help to improve ubuntu!!!

cheers!!

Hi Bruno,

Per David's comment, I'm curious how comfortable you would be compiling your own kernel and enabling the sis5513 module? It would help us to know if that indeed does resolve the issue. The following wiki can help guide you through building your own kernel:

https://help.ubuntu.com/community/Kernel/Compile

Please let us know if you need any help as we'll do our best to guide you through the process. Thanks!

See Bug 152820. Another SiS 5513 user there tried both upgrading and a fresh install. For him, the upgrade caused boot issues, but the install worked fine. I have made a few tweaks to my /etc/fstab file and am now using the stock Gutsy kernels. My changes are noted in the other bug. the original contributer here indicates that his issue includes problems even from the live CD. So, I don't think this is the same issue.

Cheers!

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.

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".

Specifically, please let us know if the bug still exists in Intrepid, and if so, please attach the information requested back in Comment 1 again, with the latest kernel in Intrepid.

Thanks again!