[gutsy] notebook instantly powered off while loading ubuntu

Bug #137538 reported by Marco Ferragina
14
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

I have a toshiba m30x laptop and I use it with ubuntu since dapper. Now I've updated to gutsy and I have this problem:

With power cable plugged in, ubuntu is loaded until gdm. When I put user and password, during gnome
loading, the laptop is powered off instantly, and with instantly I mean the same as if there was no power at all.

It work well if I boot with 2.6.20 kernel image.

With power cable unplugged (using battery) the laptop is powered off before gdm is loaded.

If I pass the acpi=off parameter to the kernel (2.6.22) the laptop work well but with no acpi I can't use
frequency scaling on my centrino.

This is lspci output:
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
02:04.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller
02:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
02:04.2 Generic system peripheral [0805]: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller
02:04.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc:

Please tell me If you need other info and sorry for my english.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments 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 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
5. Additionally a tarball of your '/proc/acpi' directory would be quite helpful.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Also have you checked to see if there are any BIOS updates available for your system? Thanks in advance!

Changed in linux-source-2.6.22:
assignee: nobody → brian-murray
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Marco Ferragina (ferama) wrote :

I have powered on my laptop several times to take all required info and I have switched as soon as I can to a virtual terminal (Ctrl+Alt+Fx) and logged in to execute the required commands, becouse the laptop was going down after 2 or 3 minutes each time.

So this is the output of uname -a

Linux redbox 2.6.22-11-generic #1 SMP Fri Sep 7 05:07:05 GMT 2007 i686 GNU/Linux

And now the attachments

Revision history for this message
Marco Ferragina (ferama) wrote :
Revision history for this message
Marco Ferragina (ferama) wrote :
Revision history for this message
Marco Ferragina (ferama) wrote :
Changed in linux-source-2.6.22:
assignee: brian-murray → ubuntu-kernel-acpi
status: Incomplete → Triaged
Revision history for this message
Marco Ferragina (ferama) wrote :

If it can help today I've compiled the linux kernel image version 2.6.23rc6 and the problem is still there.

Version 2.6.20-16-generic works well instead

If you need any other info tell me but please solve this problem or my laptop will be unusable with gutsy

Revision history for this message
Marco Ferragina (ferama) wrote :

I've restricted the problem and now my laptop is usable.

It' seem that it's all caused by the battery kernel module.

Now I have battery blacklisted and and my laptop work well

Revision history for this message
Matthias Niess (mniess) wrote :

Hi,

got the same problem. I reported #149033. As I reported, there, I could work around this bug by blacklisting the battery kernel module, so it definiately must have something to do with the changes made there. The one time I was able to completely log in, the difference I saw was the following: Previously (feisty and predecessors) because of the laptops broken DSDT the battery was just reported as not present. What I saw when I logged in was that it reported no power cable present but instead an empty battery. Unfortunately I don't know enough about fixing DSDTs. I tried to fix mine (using common sense) but only got kernel panics.
Please tell me. if you want me to assemble the above mentioned information, too. I could also post the DSDT if that helps.

One other thing: all the ACPI stuff worked perfectly under breezy on that laptop.

Revision history for this message
Matthias Niess (mniess) wrote :

Just a quick update. I found out that Toshiba finally released a BIOS update for my notebook (Satellite M30X). For me that fixed everything. Battery-Monitor works again and the notebook doesn't shut down anymore. Other people might not be that lucky (to get a BIOS update) so I think we should still figure out what change causes laptops with broken DSDTs to shut down. The way I see it Ubuntu "thinks" the battery is empty and thus shuts the computer down.

So it should determine whether the battery-status information is of any value, before using it.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

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!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
Curtis Hovey (sinzui)
Changed in linux-source-2.6.22 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.