acpi unable to boot after toshiba bios update

Bug #492916 reported by konrad-k
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I've updated BIOS on Toshiba Qosmio F30-140 and I can't boot Ubuntu 9.04 or Ubuntu 9.10 with acpi. During start, continously appear character: ^[[B which cancel all important processes. I can boot with option acpi=off or acpi=ht and I am attaching following information collected during acpi=off system startup.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2525 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x44200000 irq 11'
   Mixer name : 'SigmaTel ID 7691'
   Components : 'HDA:83847691,117904f2,00102201 HDA:11c13026,11790001,00100700'
   Controls : 5
   Simple ctrls : 4
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: TOSHIBA Qosmio F30-142
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet nosplash -- acpi=off debian-installer/language=pl console-setup/layoutcode?=pl
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: lucid needs-upstream-testing
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/03/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.90
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.90:bd04/03/2008:svnTOSHIBA:pnQosmioF30-142:pvrPQF32E-00F00VPL:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: Qosmio F30-142
dmi.product.version: PQF32E-00F00VPL
dmi.sys.vendor: TOSHIBA

Revision history for this message
konrad-k (konrad-krol89) wrote :
Adi Roiban (adiroiban)
Changed in ubuntu-translations:
status: New → Invalid
Revision history for this message
konrad-k (konrad-krol89) wrote :

Sorry about posting in ubuntu-translation.
I followed: https://wiki.ubuntu.com/DebuggingACPI
but I can't attach proc/acpi because directory doesn't exist - I can't boot with acpi.
I checked all remaining boot options, like "pic=noacpi" or "noapic", etc. but it doesn't solve the problem.

Revision history for this message
Victor Vargas (kamus) wrote :

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 https://wiki.ubuntu.com/Bugs/FindRightPackage , so I have classified this bug as a bug in linux package.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
konrad-k (konrad-krol89) wrote :

The problem dissapeared after installing 64-bit Ubuntu 9.04 with amd64 architecture. ACPI works correct, I can change CPU frequency, fan speed, set lcd brightness, and all hotkeys work.

Andy Whitcroft (apw)
tags: added: kernel-series-unknown
tags: added: karmic
removed: kernel-series-unknown
Revision history for this message
konrad-k (konrad-krol89) wrote :

I am now sure, that problem is connected to 32-bit Linux systems (all distributions). With 64-bit systems there is no any problem.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Kojot89,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 492916

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
konrad-k (konrad-krol89) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
konrad-k (konrad-krol89) wrote : AplayDevices.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : ArecordDevices.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : BootDmesg.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : CurrentDmesg.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : IwConfig.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : Lspci.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : Lsusb.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : PciMultimedia.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : ProcInterrupts.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : ProcModules.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : UdevDb.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : UdevLog.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote : WifiSyslog.txt

apport information

Revision history for this message
konrad-k (konrad-krol89) wrote :

I tried Ubuntu 10.04 2.6.32-22-generic with i386 and amd64 architecture and the problem appears again. Now the problem also appears on amd64 which previously worked good.
I collected informations using:
apport-collect -p linux 492916
Informations were collected after running in acpi=off mode, because it was not possible to run with acpi working.

Previous posts are quite old, so if you still need more informations, just let me know and I will post them here.

Changed in linux (Ubuntu):
status: Expired → In Progress
Aron Xu (happyaron)
affects: ubuntu-translations → null
Revision history for this message
konrad-k (konrad-krol89) wrote :

After system started I tried:

sudo modprobe -r usbhid
sudo modprobe usbhid

and problem disappeared.

Changed in linux (Ubuntu):
status: In Progress → Triaged
Curtis Hovey (sinzui)
no longer affects: null
Revision history for this message
penalvch (penalvch) wrote :

konrad-k, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
konrad-k (konrad-krol89) wrote :

Hello,
Sorry but my laptop was damaged and I am not able to verify described issue on this specific hardware anymore.
Please close this issue, since I am only reporter.

Revision history for this message
penalvch (penalvch) wrote :

konrad-k, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/492916/comments/29 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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