[Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages

[Tom Louwrier]

hi

Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment.

Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample:
=============
[19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[19667.508580] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[19668.588712] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[19668.600230] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[19669.717811] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[19669.729373] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[19670.825313] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
[19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[19670.835707] atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
=============
This goes on every second until shut down.

It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution.
It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really.

WORKAROUND: - shutdown the pc
- Remove both battery and AC
- push the 'on' switch several times
- Plug the battery and AC back in

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thomas 1529 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc0000000 irq 16'
   Mixer name : 'SigmaTel STAC9200'
   Components : 'HDA:14f12bfa,14f100c3,00090000 HDA:83847690,102801f6,00102201'
   Controls : 6
   Simple ctrls : 4
CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
CheckboxSystem: d00f84de8a555815fa1c4660280da308
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
MachineType: Dell Inc. Latitude 131L
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Regression: No
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
Tags: lucid
TestedUpstream: Yes
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.1
dmi.board.name: 0PM607??????
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??????:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Latitude 131L
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thomas 1491 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc0000000 irq 16'
   Mixer name : 'SigmaTel STAC9200'
   Components : 'HDA:14f12bfa,14f100c3,00090000 HDA:83847690,102801f6,00102201'
   Controls : 6
   Simple ctrls : 4
CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
CheckboxSystem: d00f84de8a555815fa1c4660280da308
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100201)
MachineType: Dell Inc. Latitude 131L
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro quiet splash
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.utf8
 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
Tags: lucid kconfig needs-upstream-testing
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.1
dmi.board.name: 0PM607??????
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??????:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Latitude 131L
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thomas 1678 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc0000000 irq 16'
   Mixer name : 'SigmaTel STAC9200'
   Components : 'HDA:14f12bfa,14f100c3,00090000 HDA:83847690,102801f6,00102201'
   Controls : 6
   Simple ctrls : 4
CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
CheckboxSystem: d00f84de8a555815fa1c4660280da308
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100201)
MachineType: Dell Inc. Latitude 131L
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro quiet splash
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-23.37-generic 2.6.35.7
Regression: No
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
Tags: maverick kernel-config needs-upstream-testing
Uname: Linux 2.6.35-23-generic x86_64
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.1
dmi.board.name: 0PM607??????
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??????:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Latitude 131L
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

[Tom Louwrier (tom-louwrier)]

output of 'ubuntu-bug -p linux'
(I hope....)

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[harrydb (harrydeboer)]

I have exactly the same messages, but on a Dell inspiron 1501

[Tom Louwrier (tom-louwrier)]

That is logical, since these laptops share (most of) the mainboard.
Inspiron is the home version, Latitude is for business users.

cheers
Tom

[Jeff Dean (jdean10-satx)]

Had the same problem, and found the answer online. Disconnect your laptop from your power supply, and then pop the battery out for a few seconds. Reinsert the battery and the power supply cord and boot up. This should take care of the problem for a while. I've found that the problem tends to reappear when the power supply cord is loose and you get a bootup message stating that the system can't recognize the type of power supply being used. If that happens, pull the power and the battery again.

Good luck!
Jeff

[Tom Louwrier (tom-louwrier)]

hi Jeff,

Yup, found that online as well. Tried it, but it did not really work for me. Thanx anyway.
I do have that message about my charger not being identified but so far contributed that to deveicekit-power (bug 418428). It's probably both due to a bug in the bios, maybe even the same one, although the power thing comes and goes... well comes more recently, I wish it went ;-)
I've seen reports of people using a Dell Inspiron 1501 (same mobo) that got rid of it after getting a new bios in, but mine has been on the latest&greatest for some years now and there we are.

cheers
Tom

[Jeremy Foshee (jeremyfoshee)]

Hi Tom,

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 549741

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

[Tom Louwrier (tom-louwrier)]

hi Jeremy,

This is certainly still an issue. In fact I've been able to trace it on
the web going back several years and releases. I guess I'm just the
first one reporting a bug about it.
Right now I'm running Lucid, updated daily, so I guess it's not been
fixed yet.

I'll run apport-collect in a minute.
Somehow I can't seem to find daily CD's of Maverick yet, so more testing
with that will have to wait.

cheers
Tom

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Bráulio (brauliobo)]

same on a dell vostro 1000 with lucid

[Tom Louwrier (tom-louwrier)]

Here's something that might help: I switched to another power supply; same brand, smaller but still.
The errors have gone from my logs (fine) but also the power management seems to be working as it should (bug 418428).

To me this definitively points to a bug somewhere in the bios, the battery's firmware and/or the power supply (if any).
It may very well even be limited to a specific series of devices.

If that is the case, I don't think there will be a proper fix for it. Maybe addition of a quirk to detect it and activate a workaround (what?).
Of course I'll be happy to do more testing and report the outcome here. Just let me know.

cheers
Tom

[harrydb (harrydeboer)]

its there on maverick as well

[Tom Louwrier (tom-louwrier)]

And I'm sorry to tell you that it is still (or: again) there in Lucid. Changing over my chargers does not seem to stop it as it did.
I'm not trying Maverick just yet, because I want to keep this laptop as stable everyday system. I need it for work.

cheers
Tom

[gibbylinks (gibbylinks)]

Hi
I can confirm it's there in Maverick, as well. Running 10.10 RC on same laptop and get following message flooding my logs

Oct 2 09:39:58 gibbylinks-laptop kernel: [ 2417.426573] atkbd serio0: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
Oct 2 09:39:58 gibbylinks-laptop kernel: [ 2417.426582] atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.

Will try latest kernel and see if still there

Paul

[gibbylinks (gibbylinks)]

Tried running latest Kernel 2.6.36 RC 6 but bug still present. Now running final 64bit release of Maverick on my Dell Inspiron 1501 with 4gb ram and logs are still being filled with this error.

I tried this solution http://ubuntuforums.org/showthread.php?t=1282027 but it didn't work for me.

[Tom Louwrier (tom-louwrier)]

Thanks Gibbylinks.
Still there on Lucid (as expected it would be) but sorry to hear Maverick has it too. I'm going to upgrade sometime next week and hoped to get rid of this one.

cheers
Tom

[gibbylinks (gibbylinks)]

FYI I have just replaced my hard drive with an SSD and done a clean install of 10.10 and the bug has disappeared ??

[Tom Louwrier (tom-louwrier)]

Did an inplace upgrade to Maverick 2 weeks ago and alas still have this issue.
Last week's new kernel did not have any influence either. (sob, sob...)

cheers
Tom

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Tom Louwrier (tom-louwrier)]

apport information

[Keng-Yu Lin (lexical)]

In https://bugzilla.redhat.com/show_bug.cgi?id=454131 says that it can be fixed by removing battery and inserting it back on Inspiron 1501. Does it apply here too?

[Tom Louwrier (tom-louwrier)]

Thanx for the tip, but alas.
Had found that out myself as well, tried it and got no joy. So I filed a
bugreport here.

cheers
Tom

[Tom Louwrier (tom-louwrier)]

OK, decided to give it another go. Here's what I did.
- shutdown the pc
- pull the battery
- pull the AC, leave the charger connected to the pc. light goes out after a couple of seconds
- push the 'on' switch several times (nothing happens, what do you expect...)
- unplug the charger
>>> leave everything for several hours like that: switched off, unplugged, disconnected.
- fit the battery
- boot the pc
- check dmesg, looking good (well now...)
- connect the charger
- plug charger in AC
- check dmesg, still looking good

Been using it for several hours now, still no real problems. There are some messages in dmesg that look like the ones in my original report, but not the flood is used to be.
Disconnected and reconnected the charger several times from the pc, it stays OK.
Seems that's the solution after all.

Attaching output of dmesg.
I'll report back in a couple of days, if it stays OK we can close this one.

cheers
Tom

[Sam Berry (ukberry)]

This general technique worked for me too (I used a slightly modified order):

- shutdown laptop
- disconnect charger
- removed battery
- wait 30 seconds
- reinsert battery
- attach charger
- boot laptop
- check syslog/kernel/dmesg : all fine :-)

Sam

[penalvch (penalvch)]

Tom Louwrier, 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 kernel 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.1

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.

[Tom Louwrier (tom-louwrier)]

hi Chris,

Yup, it does still happen. I just checked and it's a constant 4 messages per second filling up the logs.
I can do the workaround as described above in #72 which may or may not make it go away for a while.

Right now I'm not in a position to go testing alternative kernels. This laptop is very much my working hack so I need it to get myself into next month and the next etc.

Currently running Precise 12.04 amd64, updated daily (including proposed and backports repositories).
Linux laptop-131L 3.2.0-55-generic #85-Ubuntu SMP Wed Oct 2 12:29:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

cheers
Tom

[penalvch (penalvch)]

Tom Louwrier, in addition to providing the information in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/comments/74 , does this also happen with an external USB keyboard?

[Eugene Savelov (savelov)]

For me, this problem is fixed by turning off the power, removing the battery and plugging in everything back. After powering on notebook the error is gone. I have AMD-based DELL Insipron 1501, assuming this is some sort of firmware bug of keyboard controller, and needs to be done once a year or so.

[penalvch (penalvch)]

Eugene Savelov, having a WORKAROUND on different hardware, and an unconfirmed assumption of root cause, doesn't cause this report to be Invalid. For more on Status, please see:
https://wiki.ubuntu.com/Bugs/Status

Despite this, given Tom Louwrier is the original reporter, if he would like to close this, its up to him.

[Eugene Savelov (savelov)]

Contacted Tom, hope he confirms. As I own similar hardware (AMD-based DELL notebook of the same architecture, Inspiron 1501), still running ubuntu fine (up to 18.10 now) with the above mentioned workaround. Actually similar bug raised by me is closed on redhat side https://bugzilla.redhat.com/show_bug.cgi?id=454131 . As the hardware is quite old (more than 12 years old!) no-one will bother to reproduce or fix it, hence the only way forward is just to close it.

Here is my System Information
        Manufacturer: Dell Inc.
        Product Name: Inspiron 1501
        Version: Not Specified
        Serial Number: BZX583J
        UUID: 44454C4C-5A00-1058-8035-C2C04F38334A
        Wake-up Type: Power Switch
        SKU Number: Not Specified
        Family: Not Specified

[penalvch (penalvch)]

Eugene Savelov, RedHat bug 454131 was opened and closed by you (not someone who represents upstream or RedHat):
https://bugzilla.redhat.com/show_activity.cgi?id=454131

Despite this, regarding a way forward here on Launchpad, if you want your problem addressed, it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Eugene Savelov (savelov)]

below article confirms the similarity of the hardware of Dell Vostro 1000, Dell Latitude 131L, Dell Inspiron 1501 which exhibit the issue discussed in this bugreport
https://mikebeach.org/2011/04/24/kernel-atkbd-c-unknown-key-released-messages-on-linux/

[Tom Louwrier (tom-louwrier)]

hi guys,

Well now, that is one old bug I reported.
The 'powerd down, remove battery, restart it all' workaround didn't quite fix it for me but it was no big deal otherwise.
And since the laptop had died since then I have no problem if we close this bug.

cheers
Tom

[penalvch (penalvch)]

Tom Louwrier, this report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/comments/82 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.

[Eugene Savelov (savelov)]

ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: eugene 1974 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
HibernationDevice: RESUME=UUID=7824e0a4-dd46-461a-a5fc-97a61d2fae5a
MachineType: Dell Inc. Inspiron 1501
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ae9b9898-729f-4cdc-9d2a-adc0fa9fcc07 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-15-generic N/A
 linux-backports-modules-4.18.0-15-generic N/A
 linux-firmware 1.175.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: wayland-session cosmic
Uname: Linux 4.18.0-15-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2018-09-29 (139 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/07/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.3
dmi.board.name: 0UW744
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 1501
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Henry Wertz (hwertz10)]

I have an Inspiron 1545 that's doing this (Ubuntu 18.04.5); mine is nowhere near every second though. My battery is toast, a while ago it began (occasionally) having the "0% battery" occasionally drop off then reappear a few seconds later (both in gkrellm and the battery status on the top right near network-manager etc.). Based on the timing in the logs (0x8d then another a few seconds later), I think it sends a 0x8d keystroke both on battery disappearing and once on reappearing.

I'd hesitate to consider it a bug; it's minorly spamming up the logs with a superfluous keystroke the Dell's sending, while causing no harm (if the point of the keystroke is to indicate change in battery status, Linux is already well aware of this via ACPI anyway.)

[penalvch (penalvch)]

Henry Wertz (hwertz10), as this report is closed, it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.