Repeated Error Message Almost In Every Second: "toshiba_acpi: Unknown key 401"

Bug #1402252 reported by Rendy Eko Prastiyo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

First of all, sorry for my bad English.

I'm using Ubuntu 14.04 32bit on my Toshiba L645 core i3. The problem is: something is like firing a key up when I press and hold a key. It happened not just in terminal, but everywhere. I guess the problem is caused by toshiba_acpi as the syslog said (10 recent lines):

$ cat /var/log/syslog
Dec 14 01:18:08 rendy-pc kernel: [ 7013.622025] toshiba_acpi: Unknown key 401
Dec 14 01:18:09 rendy-pc kernel: [ 7014.663953] toshiba_acpi: Unknown key 401
Dec 14 01:18:10 rendy-pc kernel: [ 7015.693972] toshiba_acpi: Unknown key 401
Dec 14 01:18:11 rendy-pc kernel: [ 7016.730425] toshiba_acpi: Unknown key 401
Dec 14 01:18:12 rendy-pc kernel: [ 7017.760327] toshiba_acpi: Unknown key 401
Dec 14 01:18:13 rendy-pc kernel: [ 7018.800344] toshiba_acpi: Unknown key 401
Dec 14 01:18:14 rendy-pc kernel: [ 7019.843628] toshiba_acpi: Unknown key 401
Dec 14 01:18:15 rendy-pc kernel: [ 7020.902850] toshiba_acpi: Unknown key 401
Dec 14 01:18:16 rendy-pc kernel: [ 7021.961199] toshiba_acpi: Unknown key 401
Dec 14 01:18:17 rendy-pc kernel: [ 7023.026371] toshiba_acpi: Unknown key 401

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-40-generic 3.13.0-40.69
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rendyep 2108 F.... pulseaudio
 /dev/snd/controlC0: rendyep 2108 F.... pulseaudio
CRDA:
 country ID:
  (2402 - 2482 @ 40), (N/A, 20)
CurrentDesktop: Unity
Date: Sun Dec 14 01:08:53 2014
HibernationDevice: RESUME=UUID=5382428b-07d7-4d49-ae75-c302ed615c52
InstallationDate: Installed on 2014-12-08 (5 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: TOSHIBA Satellite L645
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=44a12f7a-9626-4c9f-b5be-e00df35a1a2a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-40-generic N/A
 linux-backports-modules-3.13.0-40-generic N/A
 linux-firmware 1.127.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.90
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.90:bd12/31/2010:svnTOSHIBA:pnSatelliteL645:pvrPSK0LL-02600D:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L645
dmi.product.version: PSK0LL-02600D
dmi.sys.vendor: TOSHIBA

Revision history for this message
Rendy Eko Prastiyo (rendyep) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Rendy Eko Prastiyo, thank you for reporting this and helping make Ubuntu better. As per http://toshiba-asia.com/sg/support/drivers an update to your BIOS is available (2.70). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Rendy Eko Prastiyo (rendyep) wrote :

I confirm that upgrading my BIOS to version 2.70 helps me solving this problem.

Thank you for the assistance, Mr. Penalver.

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Rendy Eko Prastiyo, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402252/comments/5 regarding this being fixed with a BIOS update. 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: Confirmed → 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.