Public bug reported:
Installation stalled and didn't complete.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
ApportVersion:
** Information type changed from Public Security to Public
--
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/1970453
Title:
DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
Status in
Public bug reported:
I ran the software update after a fresh install of 22.10. I had another
instance yesterday where I had a similar issue, but I didn't send a
report for it. I have 3 VMs of Ubuntu 22.10.
ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: linux-firmware
** Information type changed from Public to Public Security
--
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/1970453
Title:
DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
Status in
I have verified the kernel pps_api only looks at CD by building a patch
cable to map the PPS signal into the CD pin and now all the pps_api
calls work as expected.
It is still my position that the kernel pps_api should look at all
commonly used control lines for PPS just like the pps-tools
According to linux/drivers/pps/clients/Kconfig
config PPS_CLIENT_LDISC
tristate "PPS line discipline"
depends on TTY
help
If you say yes here you get support for a PPS source connected
with the CD (Carrier Detect) pin of your serial port.
If this is
A possible cause for this bug has occurred to me, but I wouldn't know
where in the kernel code to check for this.
Note: When I talk about a control line, I am using the DTE, i.e
computer, end connector reference.
In years past there was no standardization for which line on a serial
port carried
I have rebooted with the oldest installed kernel, 5.4.0-54, and it too
has the bug.
--
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/1938626
Title:
PPS API broken
Status in linux package
. As I
recall, it is just hold down a key while rebooting to get to the menu to select
a kernel, but don't remember which key.
On Wednesday, August 4, 2021, 6:30:46 AM PDT, Kleber Sacilotto de Souza
<1938...@bugs.launchpad.net> wrote:
Hello Jim,
Did it work before with your
Public bug reported:
The kernel PPS API appears to be broken. I have a serial GPS with PPS
attached to /dev/ttyS4. If I use gpsd to create /dev/pps0, gpsd fails to
see PPS data. If I disable gpsd and create /dev/pps0 with ldattach, any
app or tool run against ttyS4 works fine and does see the CTS
Public bug reported:
As also reported on the Raspberry Pi bug report:
https://github.com/raspberrypi/linux/issues/3981
I'm experiencing this with all 5.x kernels usually within a day or 2 of a
restart:
Jun 29 20:20:35 tiny-myth kernel: [85834.433030] xhci_hcd :04:00.0: WARN
Cannot submit
Thank you for responding. Today I booted using 5.8.0-55-generic and the
touchpad works again. It must've been something other than the kernel
update. Sorry for the false alarm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
Ubuntu 20.04.2 LTS
Lenovo ThinkPad P14s Gen 1
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Alex, just to make sure that I reinstalled one of the kernels that was
supposed to be good (perhaps by accident I reinstalled a bad one), could
you direct me to a good kernel on your ftp site? best, Jim
--
You received this bug notification because you are a member of Kernel
Packages
Hi Alex,
unfortunately that bug has come back. It just took longer to manifest
itself after booting. It also affects recognition of the power state and
the brightness buttons, which I hadn't noticed before. --Jim
--
You received this bug notification because you are a member of Kernel
I tried many different ways to resolve this issue manually adding and
removing modules or editing driver files as suggested in different
forums and it didn't work (I only have a basic knowledge of Linux)
anyway I'm pleased to say that it is working again from Kernel 5.4.0-67.
--
You received
Problem is back in 5.4.0-62-generic. That version was recently released by
Ubuntu and installed on my system during a regular update. However, when I run
it and with that TP-Link AC-600 installed, I am again seeing the symptoms I
observed in my original bug
I reported bug 1907764, deemed a duplicate of this.
I've installed the latest proposed Ubuntu kernel, 5.4.0-61-generic, under AMD64
and the system is stable with my TP-Link AC-600 adapter installed. It even
works!
--
You received this bug notification because you are a member of Kernel
I tried running that command and I get
ERROR: The python3-launchpadlib package is not installed. This
functionality is not available.
However as I had to uninstall 5.4.0-58 I don't know if this will show
any information, the mouse does not move and if I run lsusb on 5.4.0-58
it shows:
Bus 001
.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: jim 3040 F pulseaudio
/dev/snd/controlC1: jim 3040 F pulseaudio
/de
ease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/contro
name: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: jim3040 F pulseaudio
/dev/snd/controlC1: jim3040 F pulseaudio
/dev/snd/controlC0: jim3040 F.
s this card just fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
USERPID
Hi Alex,
I see that I am currently running 5.4.0-48-generic, which I think is the
same version that you originally sent me. But livepatch alters the
running kernel without changing its version number, doesn't it?
That's what makes me still wonder if it is the culprit.
thanks--Jim
On Tue, 3
Hi Alex,
my problem came back. Is it possible that livepatch has replaced my
working kernel with the broken one again? --Jim
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482
last one you sent with the commit? It is working.
On Fri, 25 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> can you give kernel in #24 a try?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Title:
>
thanks a lot Alex
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482/fixes/
>
> The patch in #23 requires three precedent patches. See SRU.log file for
> more details.
>
> Note it is rebased
that one seems to be fine.
On Thu, 24 Sep 2020, Alex Hung wrote:
> Next one:
> https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Title:
>
that one also seems to be good.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Next one is @
> https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
>
this one seems to be good
On Wed, 23 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> Thanks for testing. The next is available @
> https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => In Progress
>
> ** Changed in:
okay, so that kernel has the problem again.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Thanks mfo for helping out how to disable secure boot and install kernel
>
> I uploaded a test kernel @
> https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/
>
> There are 17 patches so it
ok, that's not such a big problem. I'll keep all the versions' deb
packages in separate directories so I can easily switch back to one of
them if needed.
On Wed, 23 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hi Jim,
>
> You can install on top of the previous ones without remo
Hi, if I install this on top of the previous one using dpkg -i * will that
be sufficient? Or do I have to remove the previous packages first?
It seems like my grub configuration is somehow set to keeping only two
kernels in the boot list. It would be nice if it would keep them all so I
don't
ok, I can do that
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hey Jim,
>
> That's very good news!
>
> I believe Alex should send you more test kernels,
> with different sets of patches included/removed,
> so to bisect/identify which specific patch(es)
Looks like it is working! At any rate the old kernel started having the
problem much sooner while this one is still fine. Thanks very much for
your help with this!
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
thanks, I fixed that and will start testing
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> It looks like you have secure boot enabled.
> Unfortunately test kernels are unsigned and thus require it to be disabled in
> your BIOS/EFI menu.
>
> --
> You received this bug notification
Hi Maricio, I did as you suggested, but cannot boot,
error:/boot/vmlinuz-5.4.0-47-generic has invalid signature
loading initial ramdisk
error: you need to load the kernel first
--Jim
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hi Jim,
>
> This is a conflict between the (
-47.51_all.deb
linux-headers-5.4.0-47-generic_5.4.0-47.51_amd64.deb
linux-modules-5.4.0-47-generic_5.4.0-47.51_amd64.deb
linux-modules-extra-5.4.0-47-generic_5.4.0-47.51_amd64.deb
seem to have installed properly.
Should I go ahead and reboot? regards, Jim
On Tue, 22 Sep 2020, Jim Cline wrote
This bug still exists in 18.04 LTS (and has been present for many
versions).
Verified on an Acer Travelmate 2420. Blacklisting the module solves the
problem at the expense of the buttons/switch not functioning properly.
This fix should be ported into the kernel.
--
You received this bug
Hi! I'm on Debian and I'm getting this issue with the following kernel:
4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26)
I feel like this isn't the best place to report this, but can someone
point me to the best place to report this issue? Can't find any
discussion on it from the past year but
Please close. Regressed to prior kernel to proceed, then next kernel
upgrade contained the wifi fix. Apparently, the first package push of
5.3 was incomplete.
On 2/4/20 2:45 AM, Kai-Heng Feng wrote:
> Please attach `dmesg`, `dkms status` and `sudo lspci -k`.
>
--
You received this bug
Public bug reported:
Kernel came in with regular maintenance. I DID notice some error
messages in Update Manager log about broadcom drivers, but didn't
realize it was for real. Upon boot, couldn't access wifi. Booted using
5.0 kernel and all is well again.
ubuntu-bug linux output -- N/A
Hi Adrian... that worked !! Is this just a temporary fix or something
that would be in future releases ? 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/1848883
Title:
(Lenovo
mmc0: cqhci: Task clr: 0x | SSC1: 0x00010004
--
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/1848883
Title:
(Lenovo S130-11IGM) emmc not working in 19.04
Status in linux package
Hi Adrian, thanks for the pointers.
I ran the following (I already set grub to default to 4.15.0-20 unlessI select
an alternate);
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
-b linux-5.4.y
cd linux/
wget
Hi Adrian, if booting from the kernel fails, it obviously hangs as there's no
physical disk device to use. Is there a way to write or get the kernel messages
to another device at this point? or is my only option to build on usb, then
build a new patched kernel on the usb and boot from it ?
Tried 4.18-rc1. Couldn't compile...
drivers/mmc/host/sdhci-pci-core.c: In function ‘glk_cqe_enable’:
drivers/mmc/host/sdhci-pci-core.c:758:7: error: implicit declaration of
function ‘FIELD_GET’; did you mean ‘FOLL_GET’?
[-Werror=implicit-function-declaration]
if (FIELD_GET(mask, val) != 4) {
First test with 5.5-rc1 failed with the same issue using these steps
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux/
git tag
git checkout v5.5-rc1
wget
Thanks Adrian, I'll test this as soon as I can.
Could you confirm the steps.. I assume I need to apply this to 4.16-rc1. I
think it is ..
$ apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ wget
Hi Adrian, is there anything else that would be useful to provide for
this bug ? 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/1848883
Title:
(Lenovo S130-11IGM) emmc not
** Attachment added: "binary acpidump. all in zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5308679/+files/acpidump_binary.zip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Attached dump from 4.15.0-20. Would acpidump show any difference running
from a newer kernel ?
--
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/1848883
Title:
(Lenovo S130-11IGM) emmc not
** Attachment added: "acpidump_4.15.0-20-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5307033/+files/acpidump_4.15.0-20-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Totally over my head :)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.16-rc1=8ee82bda230fc972c7ee3bb15ce1260eefb4721c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I guess if https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883
can be resolved, there is no need to look at this as live CDs on 19.04
work fine with this touchpad.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Kai-Heng... here is the bisect output.
root@ubuntu:~/mainline/tmp/linux# git bisect bad
8ee82bda230fc972c7ee3bb15ce1260eefb4721c is the first bad commit
commit 8ee82bda230fc972c7ee3bb15ce1260eefb4721c
Author: Adrian Hunter
Date: Wed Nov 29 15:41:06 2017 +0200
mmc: sdhci-pci: Add CQHCI
Hi Kai-Heng.. Please ignore #29/#30/#31. For some reason launchpad took text
from firefox on each reboot! I am working through each bisect testing the
kernels. Each one takes about 1 hour to build. Also quite surprised to see how
many changes were made to sdhci-acpi in this -rc.
Thanks Kai-Heng. I have identified the last working mainline is 4.15-rc9
and from 4.16-rc1 it fails. I will try and follow the bisect steps. I
assume the "git bisect good" command should be "git bisect good
4.15-rc9. Looking at the bisect visualise I can see 2/3 commits made for
emmc devices.
--
Thanks Kai-Heng. I have identified the last working mainline is 4.15-rc9
and from 4.16-rc1 it fails. I will try and follow the bisect steps.
After running "git bisect start", what should be the complete "git
bisect good" command based on the kernel versions I determined were
good/bad ??
--
You
Hi, thanks for this update. So I know all the 4.15.0 kernels work with
this emmc hardware but the only others I have tried are part of 19.04
(so 4.18) onwards which fail. Does this mean I should start from
4.15-rc9 and then 4.18-rc1 until I find a broken kernel ? Then do the
bisect ?
--
You
Attaching dmesg from 4.15.0-20
** Attachment added: "dmesg from 4.15.0-20"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849141/+attachment/5304743/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Thanks Kai-Heng. Tested 5.4-rc4 but still the same issue. Cannot boot up
using this kernel. Also tried on a 14inch version of the same laptop
with the same error. There is some kind of timeout (shown in the dmesg
attached) but I don't understand what is causing it.
--
You received this bug
Also tried the latest update 4.15.0-66 but touchpad still fails to
function.
--
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/1849141
Title:
(Lenovo S130-11IGM) No touchpad after update
Hi Kai-Heng. Thanks for this suggestion. I have tested 5.4-rc4 but this kernel
causes the same issue as the following bug so I am not able to boot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883
--
You received this bug notification because you are a member of Kernel
Packages,
** Summary changed:
- (Lenovo S130-11IGM) No touchpad in 18.04 4.15.0-65
+ (Lenovo S130-11IGM) No touchpad after update to 18.04 4.15.0-65
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
- Laptop works fine out of the box with 18.04 4-15.0-20. After the software
update to 4.15.0-65, the touchpad is no longer detected. Cannot use 19.04 as
seems to be a problem with emmc support
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883).
+ Laptop
Adding /var/log/_usr_lib_xorg_Xorg.0.crash
** Attachment added: "_usr_lib_xorg_Xorg.0.crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849141/+attachment/5298982/+files/_usr_lib_xorg_Xorg.0.crash
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298978/+files/ProcModules.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: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298969/+files/Card0.Codecs.codec.0.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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298971/+files/CurrentDmesg.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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298975/+files/ProcCpuinfo.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: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298968/+files/Card0.Amixer.values.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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298979/+files/RfKill.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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298981/+files/WifiSyslog.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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298967/+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/1849141
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298970/+files/Card0.Codecs.codec.2.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: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298966/+files/AplayDevices.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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298977/+files/ProcInterrupts.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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298976/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298972/+files/IwConfig.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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298973/+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/1849141
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298980/+files/UdevDb.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: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1849141/+attachment/5298974/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected bionic
** Description changed:
Laptop works fine out of the box with 18.04 4-15.0-20. After the software
update to 4.15.0-65, the touchpad is no longer detected. Cannot use 19.04 as
seems to be a problem with emmc support
Public bug reported:
Laptop works fine out of the box with 18.04 4-15.0-20. After the software
update to 4.15.0-65, the touchpad is no longer detected. Cannot use 19.04 as
seems to be a problem with emmc support
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883).
Currently dropped
Is this not the same issue as this affecting several Lenovo models ??
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930815
Something seems to be broken since 4.18
** Bug watch added: Debian Bug tracker #930815
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930815
--
You received this
run apport-collect after booting from lubuntu 19.04 CD1
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1848883
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298587/+files/RfKill.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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298588/+files/UdevDb.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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298583/+files/ProcCpuinfo.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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298586/+files/ProcModules.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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298581/+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/1848883
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298579/+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/1848883
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298582/+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/1848883
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298580/+files/CurrentDmesg.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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298585/+files/ProcInterrupts.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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298584/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1848883/+attachment/5298589/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Hi,
I don't think this is the same issue as ;
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
although I have read a lot of issues with emmc disks.
Booting from lubuntu CD1 19.04 takes
attaching 4.15.0-20 lspci output for comparison
** Attachment added: "lspci-vnvn-4.15.0-20.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298448/+files/lspci-vnvn-4.15.0-20.log
** Summary changed:
- Lenovo S130-11IGM Unable to read emmc
+ (Lenovo S130-11IGM)
1 - 100 of 296 matches
Mail list logo
