[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Sorry about that! I initially filed this bug, but I'm no long-time user
of the bug system. If 1956422 is marked dup and pointed here, it's fine
with me!
Still, as for GCP kernel specifically, a bot auto-generated the request
to test against GCP kernel. I wonder how many drivers GCP kernel is
missing (that'll be why the touchpad and lid switch didn't work.) I
think for GCP kernel specifically, it won't matter if this patch is
applied or not, no integrated GPUs so they won't be running affected
hardware.
I suppose first start is to attach any relevant logs and info -- does
kern.log or dmesg show anything interesting when you suspend & resume?
If you can ssh into the machine, does the machine lock solid on resume,
or does it have a black screen but still running? You probably provided
this info in 1956422 already but if it's being dup'ed to here, feel free
to put it here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
I don't think this patch is intended to fix suspend/resume bug, that's
not the problem I was seeing at any rate. That said...
Does this bug apply to GCP kernel? I'm assuming GCP is "Google Cloud
Platform", so I'm not sure they are even using affected hardware. AMD
CPUs are fairly power-efficient, so I could see Google using them, but
probably not the ones with built-in GPU (in favor of getting ones with
more CPU cores instead). I assume if they want to support CUDA-style
workloads they'd thrown some monster GPUs into their "GPU compute" cloud
systems. (That said, that all means for the use case of GCP kernel, it
should be fine either way, apply or not apply this patch.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
I'm assuming the 5.14.15 or 5.14.16 amdgpu and amdkfd has been backported to the 5.13 Ubuntu kernel. Here's the patch in 5.14.17 that specifically addresses this. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.14.17=7883e13c249461877ea3be7b24a5935fc8946e46 The other amd-related patches for 5.14.17 largely appear to be fixes to DCN3.1 support (newest GPU models from last 6 months or so.) This is a fairly serious regression for those affected (I may have only gotten to a desktop because I"m using Gnome Flashback so no compositor trying to exercise the 3D hardware for desktop use. I've simply gone back to 5.13.0-22 for now.) If the plan is to ship a quick update, I could see just patching in that one patch; if it'll be fixed in 5.13.0-23 at a usual schedule I could see incorporating all of them to benefit DCN 3.1 users. Not to dissemble, but kudos to the open source GPU driver developers, the Intel support's amazing (it's amusing on my friends Sandybridge, that he can run DX11 games in steam through Proton that it would not be able to run in Windows since Intel never shipped DX11 drivers for it...), and amdgpu has run every game I've thrown at it so far, generally at very good frame rates. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Additional note, I did notice one "un-regression" -- I have a build of rocm where I've tried enabling "GFX902" support for my card, this is an unsupported configuration so I don't know if I have it 100% functional but rocminfo (which as the name suggests dumps info about the rocm install and any video or compute cards it detects that can use. ) With the 5.4.0-91-generic kernel I can run rocminfo and it dumps some info about the card. On 5.13.0-22 it prints: hsa api call failure at: /home/hwertz/ROCm/rocminfo/rocminfo.cc:1143 Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events. On 5.13.0-23, although opengl is hosed the rocminfo didn't pause and printed the rocm-related information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: New Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
** Attachment added: "Some kernel log showing amdgpu errors and others resulting from it" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+attachment/5551255/+files/wow.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: New Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] [NEW] amdgpu hangs for 90 seconds at a time
Public bug reported: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: New Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
"1) Do you actually have superflous key strokes, along with that which is logged in dmesg?" Nope, totally asymptomatic. "2) Could you please test the latest mainline kernel (now 5.9.1) and advise to the results?" Here ya go. I can attach entire dmesg if you want, but from 5.9.1 dmesg: [ 256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known. "3) Did you personally test this with your Inspiron 1545 in a prior version of Ubuntu" No. I don't think it started logging this (at least often enough to notice) until my battery went from holding like a minute or two of battery life to holding 0, which only happened in the last 2-4 weeks. Honestly, I'd be totally fine if it was closed "wontfix" (I guess launchpad doesn't have that) or "invalid", the kernel's logging a non- standard keystroke sent by the Dell, which seems legitimate and harmless (it'd be a nuisance if it was every second but it's not close to that); in addition the Dell is effectively sending it in response to a hardware failure, so I could see "if you don't want this in your kernel log, replace your battery" being a legitimate response. Let me know and I'll set it! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: On my Dell Inspiron 1545 dmesg, I get: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kernel. My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
"1) Do you actually have superflous key strokes, along with that which is logged in dmesg?" Nope, totally asymptomatic. "2) Could you please test the latest mainline kernel (now 5.9.1) and advise to the results?" Here ya go. I can attach entire dmesg if you want, but from 5.9.1 dmesg: [ 256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known. "3) Did you personally test this with your Inspiron 1545 in a prior version of Ubuntu" No. I don't think it started logging this (at least often enough to notice) until my battery went from holding like a minute or two of battery life to holding 0, which only happened in the last 2-4 weeks. Honestly, I'd be totally fine if it was closed "wontfix" (I guess launchpad doesn't have that) or "invalid", the kernel's logging a non- standard keystroke sent by the Dell, which seems legitimate and harmless (it'd be a nuisance if it was every second but it's not close to that); in addition the Dell is effectively sending it in response to a hardware failure, so I could see "if you don't want this in your kernel log, replace your battery" being a legitimate response. Let me know and I'll set it! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: On my Dell Inspiron 1545 dmesg, I get: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kernel. My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1901083] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425627/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425636/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425629/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
(uname -a: Linux inspiron-1545.local 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ) I've been using 5.7.19 by default, but I'm on 5.4.0-52-generic for this since it's a supported kernel. (These atkbd messages are identical in both.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1901083] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425624/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425628/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425632/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425631/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425634/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425625/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425635/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425633/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425626/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425630/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hwertz 3637 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 1545 Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 StagingDrivers: ashmem_linux Tags: bionic staging Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra _MarkForUpload: True dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
apport information ** Tags added: apport-collected staging ** Description changed: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: hwertz 3637 F pulseaudio + CurrentDesktop: GNOME-Flashback:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-09-09 (774 days ago) + InstallationMedia: + + MachineType: Dell Inc. Inspiron 1545 + Package: linux (not installed) + ProcEnviron: + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off + ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-52-generic N/A + linux-backports-modules-5.4.0-52-generic N/A + linux-firmware1.173.19 + StagingDrivers: ashmem_linux + Tags: bionic staging + Uname: Linux 5.4.0-52-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra + _MarkForUpload: True + dmi.bios.date: 12/07/2009 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.name: 0G848F + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Inspiron 1545 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425623/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) Status in linux package in Ubuntu: Incomplete Bug description: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on
[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
** Description changed: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each - time the battery status changes. + time the battery status changes. Not sure what the point of the 0x8d + is, but it's harmless for Linux to ignore, it's well aware of the status + changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: - + ProcEnviron: - TERM=screen.xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: + I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
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.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: 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 ' 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 ' 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 ' 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 ' 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 ' 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 ' 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 ' 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: USERPID 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 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 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
