kernel 6.5.0-17-generic has just arrived in 23.10 (Mantic) and that
seems to clear the issue.
mount/unmount an external btrfs filesystem no longer produces the
messages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in
My original post said it was a kernel issue, so no idea why it was
logged against konsole.
I've changed it.
** Package changed: konsole (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in
These messages get displayed when a btrfs file system is unmounted (note
they appear 16s after the mount, which would be the unmount).
I have one that is mounted (and unmounted) every 15 minutes and these
show up at every unmount.
[1254622.716595] BTRFS: device label Lacknet-Freq devid 1
I've just tested the laptop where this problem was originally seen and
it's still OK there.
That is now running 23.04 (Lunar) with kernel 6.2.0-33-generic.
So may be similar, but is not the same.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Nothing to do with any screen saver.
Just boot the system, hit Ctl-Alt-F2 (to get to a console) and login.
There they are.
--
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/2009271
Title:
I'm still seeing it on 5.19.0-38-generic
--
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/2009271
Title:
Too many BDL entries regression
Status in linux package in Ubuntu:
Confirmed
FYI:
You can see this every time you login to a terminal screen (not X).
So, Ctl-Alt-F2, then login. You'll generate ~26 of them each time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Might be something different then.
I can insert and mount SD cards on the laptop I originally reported this
for (in #2).
I'm on kinetic, kernel 5.19.0-35-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've updated to 5.11.0-25-generic and can confirm that my laptop now
sees SDH/XC cards OK.
Thanks.
--
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/1929444
Title:
SD card initialization
I can confirm that the "author" kernel fixes the problem on my laptop.
(And for good measure I've also tested it on my old laptop, which didn't
show the problem, and it still works there too).
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which
Sorry for the delay - the notification mail seems to have gone missing.
Good job I decided to look anyway.
The result is that final WORKS:
==
root@gmllaptop:~# uname -a
Linux gmllaptop 5.11.0-19-generic #20 SMP Wed Jun 2 11:33:21 CST 2021 x86_64
x86_64 x86_64 GNU/Linux
root@gmllaptop:~#
The v3 kernel WORKS.
The SD card insertion is detected correctly.
--
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/1929444
Title:
SD card initialization on insertion fails
Status in
I don't have Secure Boot enabled anyway, so that bit's easy.
As for the v2 kernel - it FAILS (with the -84 error).
--
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/1929444
Title:
SD card
I can confirm that that 5.11.0-18-generic kernel fixes the problem,
The SD card is now visible and mountable on insertion.
--
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/1929444
Title:
Further info
I've just rebooted the laptop using the kernel that was left over from the
upgrade from groovy.
The mmc card reader works OK there.
A reboot back to the latest hirsute kernel has it failing again.
So:
5.8.0-53-generic - mmc reader works
5.11.0-17-generic - mmc reader fails
Here's the debug data from card insertion/removal.
** Attachment added: "rtsx debug info"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+attachment/5500291/+files/rtsx.info
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I've tested plugging in an SD card to an older laptop (also on hirsute).
That is OK.
I've also noticed that the:
mmc0: error -84 whilst initialising SD card
message appears at boot time if the mmc card slot is empty.
(the "mmc0: cannot verify signal voltage switch" message also appears on
my
Further information:
Booting the same laptop into MSWindows lets me insert SD cards whilst the
system is running and it all works as expected. (So not a hardware problem).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
If I boot my laptop with an SD card (actually SDXC) in the MMC slot the
system sees it and I can mount and use it.
If I then unmount it, remove it then re-insert it I get this in the
system ,og:
[ 194.673108] mmc0: card e624 removed
[ 205.462065] mmc0: cannot verify
This has been fixed
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1800752
Title:
[regression] Wrong EU count
Good.
I've tested that patch in 4.18.0 and can confirm it works.
https://bugs.freedesktop.org/show_bug.cgi?id=108712#c14
--
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/1800752
Title:
They've found the bug!!
https://bugs.freedesktop.org/attachment.cgi?id=142443
Is there a mechanism for getting this patched into the current Cosmic
kernels (and, presumably, Disco)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I've opened:
https://bugs.freedesktop.org/show_bug.cgi?id=108712
** Bug watch added: freedesktop.org Bugzilla #108712
https://bugs.freedesktop.org/show_bug.cgi?id=108712
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Thanks.
I'll add relevant links (both ways) if I can as I report it on that site.
If the code hasn't changed in the graphics development branch I may submit a
report now anyway...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Or I could post a comment to the commit mentioned in #14 - see what the
author (from Intel) thinks?
Not sure how much printk()s would tell me - the debugfs already shows it
ends up with only 4 EUs pre sub-slice instead of 8. I'll give it a go,
though. But I (might) need signed kernels...I assume
I've been looking (briefly) for some docs on the Intel GPU hardware
layout.
Came across this:
https://01.org/linuxgraphics/documentation/hardware-specification-prms
leading to:
https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-bdw-vol04-configurations_3.pdf
which says that a
apport information
** Tags added: apport-collected
** Description changed:
I run a BOINC project which uses opencl_intel on my Kubunut system
On bioinc the tasks ran in 12,000 +/- 200 seconds.
They've been doing that for ~6 months.
I've now updated the system to cosmic, and the
Only affect Cosmic. Bionic is OK.
--
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/1800752
Title:
[regression] Wrong EU count for i5-5250U, reducing OpenCL performance
Status in beignet
OK. So I have to run as root *while logged in to desktop of the system*.
Just being logged in as root (on a system where I "never" user the
console...) over the network isn't good enough.
Now done. It claims to have submitted data. I'll change the state to
Confirmed.
** Changed in: linux
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1800752/+attachment/5209800/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1800752/+attachment/5209801/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
>> I've installed it - it might now be collecting data...
No, it's not. It fired up the OAuth authorization page, which I
authorized (and got the mail confirmation). Now it just sits there
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
>> Further information may be available in the files (readable only by root,
>> the 0 may be different if you have more than one graphics device):
Info attached (only 0 has those files) for both Cosmic
(4.18.0-10-generic) and Bionic (4.15.0-38-generic) kernels. (The change
mentioned in #14 seems
Here's the Bionic kernel info (couldn't seem to be able to attach two
files to one comment?).
** Attachment added: "4.15.0-38-generic (Bionic) dri info"
https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+attachment/5209781/+files/dri-info.4.15.0-38-generic.log
--
You received
apport-collect 1800752
produced:
>> ERROR: The python3-launchpadlib package is not installed. This functionality
>> is not available.
which might explain why the info wasn't there...
I've installed it - it might now be collecting data...
--
You received this bug notification because you are a
> I may have experienced this issue also on bionic (18.04) with the
current kernel version as of today (4.15.0-13.14).
I have a system running bionic and it's fine (see #34). Always has been. It's
never run anything else (just over 2 weeks old...). It's always had the "new"
I've tested the artful kernel on a UEFI system (and tracked own how the
signed kernel is produced from the unsigned on in the debs at he same
time - see #76).
It fixes the issue (tag already changed).
--
You received this bug notification because you are a member of Kernel
Packages, which is
Well, I *think* I can answer my own question about the signed image.
The signed image was *not* generated by my installing the lp1759920 kernel.
In fact it is the identical file to the one from:
My other system (no UEFI) does seem to be OK on this new kernel - and it
is actually running it:
[parent]: cat /proc/version_signature
Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16
[parent]: cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.13.0-38-generic
root=UUID=ca819911-be41-4822-8720-4536f278aa56
These are the packages I have installed:
root@gmllaptop:/local/configs/packages# dpkg-query -l '*4.13.0-38*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Well, I have a problem testing that kernel.
I've downloaded the linux-image and linux-image extra debs and installed
them with dpkg -i.
Rebooting (with the new microcode) hangs.
But on rebooting and checking /proc/version_signature I see:
Ubuntu 4.13.0-38.43-generic 4.13.16
which makes no sense
> Define *old* microcode
The microcode from 3.20180108.0+really20170707ubuntu17.10.1:
[parent]: dmesg -t | grep -i microcode
microcode: microcode updated early to revision 0x29, date = 2013-06-12
microcode: sig=0x206a7, pf=0x2, revision=0x29
microcode: Microcode Update Driver: v2.2.
If Intel
>> Also ran:
>>
>> https://raw.githubusercontent.com/speed47/spectre-meltdown-checker/master/spectre-meltdown-checker.sh
FWIW: I just ran that on my system with the *old* microcode, and it
reports "NOT VULNERABLE" for all three variants too.
--
You received this bug notification because you
I've since left the 4.13.0-38-generic kernel + 3.20180312 microcode +
apparmor=0 option running for >30 mins (top constantly running plus a
short compilation using all 4 cores in parallel, make -j4, of a github
download).
It still looked OK.
--
You received this bug notification because you are
> if someone affected wanted to boot with the apparmor=0 kernel command
line option (with the latest artful kernel, without the noibpb kernel
command line option, and with the latest intel-microcode package), I'd
really appreciate it.
Just done this:
Downloaded latest microcode (3.20180312).
>> And adding 'noibpb' kernel boot parameter helps, at least in my case.
However, according to:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown/MitigationControls
doing that,
"Disabling these features removes mitigations for CVE-2017-5715 (aka Spectre /
Variant 2).",
> By any chance, do all of you have sssd installed?
No. I don't have it installed on any of my systems, two of which are
affected.
--
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/1759920
This is a similar thread on Arch Linux:
https://bugs.archlinux.org/task/57511
Includes the comment:
"Wasn't the 20180108 microcode update retracted because of issues? Maybe we
should downgrade back to 20171117."
There is no 20180108 download available at Intel now:
>> Well, 4.13.0-32 seems to be unaffected...
Only because it isn't the latest kernel you have, so it has never had
the latest microcode added into it - it will still be loading the
previous (working) version.
--
You received this bug notification because you are a member of Kernel
Packages,
>> Installing or removing intel-microcode only runs update-initramfs for
the latest kernel
I eventually noticed that too.
So it means that the problem follows the microcode - nothing to do with the
kernel version.
--
You received this bug notification because you are a member of Kernel
FYI: These are the signatures for my three systems.
Failing for these on 17.10 (4.13.0-37-generic):
signature 0x000306c3 (and for 4.13.0-38-generic)
signature 0x000206a7
OK for this on 18.04beta (4.15.0-13-generic):
signature 0x000306d4
--
You received this bug notification
For me, on my laptop (Intel(R) Core(TM) i5-4330M CPU @ 2.80GHz) with Kubuntu
17.10, the 4.13.0-38-generic kernel (signed image) has the same problem.
In fact it was slightly worse, a it seems to have wiped out my Ubuntu UEFI
booting (boots straight to Windows - I can get to the Ubuntu menu from
> Could someone test out the 4.13.0-38-generic kernel from artful-proposed
> to see if you experience any lock ups with the 3.20180312.0 microcode?
Any simple install instructions?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Bug #1760095 (mine) reports it for two 17.10 systems (Intel graphics only) both
on 4.13.0-37-generic.
An 18.04beta system 4.15.0-13-generic with the "same" microcode version is OK.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
54 matches
Mail list logo
