This appears to fix the issue for me on mantic (23.10) using the mantic-
proposed repo.
45.2-0ubuntu5 - for: gir1.2-mutter-13 libmutter-13-0 mutter-common
mutter
I did have to purge the ppa to get get to install. Maybe I did something
to get those vv version pinned.
I confirmed that I don't get
This appears to fix the issue for me on mantic (23.10) using the mantic-
proposed repo.
45.2-0ubuntu5 - for: gir1.2-mutter-13 libmutter-13-0 mutter-common
mutter
I did have to purge the ppa to get get to install. Maybe I did something
to get those vv version pinned.
I confirmed that I don't get
This bug affects me. Is there any kind of workaround? I'm using up to
date 20.04 which includes mutter 3.36.9-0ubuntu0.20.04.1.
I'm trying to figure out if there's some way to have my vim not use wl-
copy as it crashes gnome-shell every time I copy something which is hard
to remember.
Oh, and it
This bug affects me. Is there any kind of workaround? I'm using up to
date 20.04 which includes mutter 3.36.9-0ubuntu0.20.04.1.
I'm trying to figure out if there's some way to have my vim not use wl-
copy as it crashes gnome-shell every time I copy something which is hard
to remember.
Oh, and it
This bug affects me. Is there any kind of workaround? I'm using up to
date 20.04 which includes mutter 3.36.9-0ubuntu0.20.04.1.
I'm trying to figure out if there's some way to have my vim not use wl-
copy as it crashes gnome-shell every time I copy something which is hard
to remember.
Oh, and it
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1902578
Title:
Ethernet no link lights after reboot
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902578
Title:
Ethernet no link lights after reboot (Intel i225-v
kaihengfeng: I also attempted to cherry pick the commit referenced above
into the ubuntu-focal master branch:
$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git
$ git checkout -b test Ubuntu-5.4.0-52.57
$ git cherry-pick bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0
$ make localmodconfig
$
kaihengfeng: I also attempted to cherry pick the commit referenced above
into the ubuntu-focal master branch:
$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git
$ git checkout -b test Ubuntu-5.4.0-52.57
$ git cherry-pick bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0
$ make localmodconfig
$
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902578
Title:
Ethernet no link lights after reboot (Intel i225-v 2.5G)
To manage
** 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/1902578
Title:
Ethernet no link lights after reboot (Intel i225-v
I believe the bisect is done:
Building this commit causes the ethernet to work after reboots. (a PHY
problem seems to make sense as there's no link lights).
bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0 is the first new commit
commit bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0
Author: Sasha Neftin
I believe the bisect is done:
Building this commit causes the ethernet to work after reboots. (a PHY
problem seems to make sense as there's no link lights).
bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0 is the first new commit
commit bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0
Author: Sasha Neftin
Public bug reported:
I've found that on stock focal the ethernet device on my ASUS ROG Strix
B550-F wifi motherboard gets no link lights after rebooting. I am able
to cold boot it with the network cable unplugged and then the ethernet
works as expected after re-plugging the ethernet.
Workaround:
Public bug reported:
I've found that on stock focal the ethernet device on my ASUS ROG Strix
B550-F wifi motherboard gets no link lights after rebooting. I am able
to cold boot it with the network cable unplugged and then the ethernet
works as expected after re-plugging the ethernet.
Workaround:
@ppedemon Well, I'm the OP so WORKAROUND 2 does work for me (obviously).
I deployed these laptops with it after testing that it was stable so I
don't have access to them anymore. I did look into the git history of
grub and it seems to be related to some patches around TPM where it
fails to perform
** Description changed:
Sometimes on reboots and quick cold boots (poweroff then hit power
immediately) I get
```
error: Command failed. -repeated a number of times then
error: you need to load the kernel first.
Press any key to continue...
```
* cold booting usually
** Description changed:
Sometimes on reboots and quick cold boots (poweroff then hit power
immediately) I get
```
error: Command failed. -repeated a number of times then
error: you need to load the kernel first.
Press any key to continue...
```
* cold booting usually
Upon some further research, it looks like this bug is similar:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892
However, that bug seems to happen all the time where as for me it's
intermittent.
I tried the workaround from the linked bug and can confirm that when I
experience the
Public bug reported:
Sometimes on reboots and quick cold boots (poweroff then hit power
immediately) I get
```
error: Command failed. -repeated a number of times then
error: you need to load the kernel first.
Press any key to continue...
```
* cold booting usually fixes this and I'm able to
** Description changed:
After a fresh install of 20.04 Additional drivers shows confusing
results. (I selected to install these drivers during installation). It
- is a dell inspiron 7559
+ is a dell inspiron 7559.
+
+ I also confirmed this happens using the 20.04 iso image I installed from.
** Description changed:
After a fresh install of 20.04 Additional drivers shows confusing
results. (I selected to install these drivers during installation). It
- is a dell inspiron 7559
+ is a dell inspiron 7559.
+
+ I also confirmed this happens using the 20.04 iso image I installed from.
Public bug reported:
After a fresh install of 20.04 Additional drivers shows confusing
results. (I selected to install these drivers during installation). It
is a dell inspiron 7559
```
Intel Corporation: Wireless 3165
This device is not working
* [grayed] Using iwlwifi driver backport in DKMS
Public bug reported:
After a fresh install of 20.04 Additional drivers shows confusing
results. (I selected to install these drivers during installation). It
is a dell inspiron 7559
```
Intel Corporation: Wireless 3165
This device is not working
* [grayed] Using iwlwifi driver backport in DKMS
When building both kernel and kernel-headers from the same folder the
kernel-headers currently get built inside the tree while kernel is built
outside. This changes kernel-headers to also get built out-of-tree with
OOT=KEEP so as not to break some kernel builds.
Signed-off-by: Sandy Patterson
Sure thing, V2 coming, thanks for the pointers.
On Wed, Feb 26, 2020 at 12:46 PM Michael Olbrich
wrote:
> On Tue, Feb 25, 2020 at 10:20:34AM -0500, Sandy Patterson wrote:
> > I am not sure if the following patch is what was intended with the change
> > to OOT=KEEP change for
I am not sure if the following patch is what was intended with the change
to OOT=KEEP change for kernel. We have a folder within our BSP with a
kernel tree and we symlink to that folder using local_src/kernel.
and local_src/kernel-header..
We use an external kernel source tree and kernel headers
Kai-Heng Feng: I did some more testing and I don't see the problem in the
cosmic proposed kernel 4.18.0-9.10.
1) the live CD appeared to boot fine, but I didn't totally trust the test
procedure.
2) I installed cosmic 4.18.0-9.10 from
Kai-Heng Feng: I did some more testing and I don't see the problem in the
cosmic proposed kernel 4.18.0-9.10.
1) the live CD appeared to boot fine, but I didn't totally trust the test
procedure.
2) I installed cosmic 4.18.0-9.10 from
Kai-Heng Feng: I am working on testing with cosmic. I think I need some
time though. I can't figure out how to change the grub menu in the usb
live image. I need to add apci_osi='!Windows 2015" and I think my typing
screws with the startup timing. Do you know of a way to change the grub
config on
Kai-Heng Feng: I am working on testing with cosmic. I think I need some
time though. I can't figure out how to change the grub menu in the usb
live image. I need to add apci_osi='!Windows 2015" and I think my typing
screws with the startup timing. Do you know of a way to change the grub
config on
Kai-Heng Feng,
I also found the problem commit but I'm not sure how to properly tag
this bug report.
--
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/1768139
Title:
Kernel crash when
Kai-Heng Feng,
Yes it does. I just confirmed the issue is still present in
4.15.0-34-generic. I also upgraded my bios to the latest 1.2.8. See
attached syslog which contains backtrace. I don't notice any difference.
I was also able to find another workaround by removing "splash" from the
kernel
Kai-Heng Feng,
Yes it does. I just confirmed the issue is still present in
4.15.0-34-generic. I also upgraded my bios to the latest 1.2.8. See
attached syslog which contains backtrace. I don't notice any difference.
I was also able to find another workaround by removing "splash" from the
kernel
Kai-Heng Feng,
I also found the problem commit but I'm not sure how to properly tag
this bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
Title:
Kernel crash when booting laptop
I can confirm that I was seeing the message before installing proposed
kernel for bionic
"kernel: wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from
hardware (-22)"
after updating to latest proposed
Linux version 4.15.0-24-generic (buildd@lgw01-amd64-056) (gcc version 7.3.0
(Ubuntu
I can confirm that I was seeing the message before installing proposed
kernel for bionic
"kernel: wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from
hardware (-22)"
after updating to latest proposed
Linux version 4.15.0-24-generic (buildd@lgw01-amd64-056) (gcc version 7.3.0
(Ubuntu
I also built ubuntu-bionic: Ubuntu-4.15.0-23.25 reverting
d8a077b6271ef3d7620f0e95d4a343ec1661fe5d (which is the same commit in
the ubuntu-bionic repo).
I see that there is a brief text terminal between grub and the ubuntu
loading screen, but at least it seems to boot reliably with a second
I also built ubuntu-bionic: Ubuntu-4.15.0-23.25 reverting
d8a077b6271ef3d7620f0e95d4a343ec1661fe5d (which is the same commit in
the ubuntu-bionic repo).
I see that there is a brief text terminal between grub and the ubuntu
loading screen, but at least it seems to boot reliably with a second
bisect result: lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable
shows this commit.
I built using the mainline config-4.15.0-041500rc2-generic file and
accepted default options. I also had to apply
ff6fa2d396b0476988c749664f600b1e177bcf9b in order to get the neighboring
commits to build.
it
bisect result: lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable
shows this commit.
I built using the mainline config-4.15.0-041500rc2-generic file and
accepted default options. I also had to apply
ff6fa2d396b0476988c749664f600b1e177bcf9b in order to get the neighboring
commits to build.
it
Using the lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable
repository, I was able to narrow the issue down to between two tags:
Ubuntu-4.15.0-0 (issue present) and Ubuntu-4.14.0-17.20 (ubuntu-bionic,
no issue present). I also tried Ubuntu-4.14.0-11.13 from the unstable
branch which doesn't
Using the lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable
repository, I was able to narrow the issue down to between two tags:
Ubuntu-4.15.0-0 (issue present) and Ubuntu-4.14.0-17.20 (ubuntu-bionic,
no issue present). I also tried Ubuntu-4.14.0-11.13 from the unstable
branch which doesn't
Timo Aaltonen:
I had tested rc7 I think for 4.17. I'm attaching the dmesg from startup
using 4.17.0 with drm.debug=0x4 too (I just tried 4.17.0).
I'll start on the unstable repo, It'll take a few days probably as I
haven't figured out how to do a really incremental build. Please let me
know if
Timo Aaltonen:
I had tested rc7 I think for 4.17. I'm attaching the dmesg from startup
using 4.17.0 with drm.debug=0x4 too (I just tried 4.17.0).
I'll start on the unstable repo, It'll take a few days probably as I
haven't figured out how to do a really incremental build. Please let me
know if
** Attachment added: "drm.debug.0x4_nocrash.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+attachment/5147056/+files/drm.debug.0x4_nocrash.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I got some help from #ubuntu-kernel Thadeu Cascardo suggested I try
drm.debug=0x4
The crash seems to happen every time when the laptop has been off for a
while, but sometimes it doesn't if I power it down then bootup. So I
captured two logs attached, one where the system booted normally, and
one
I got some help from #ubuntu-kernel Thadeu Cascardo suggested I try
drm.debug=0x4
The crash seems to happen every time when the laptop has been off for a
while, but sometimes it doesn't if I power it down then bootup. So I
captured two logs attached, one where the system booted normally, and
one
** Attachment added: "drm.debug.0x4_nocrash.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+attachment/5147056/+files/drm.debug.0x4_nocrash.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Joshua R. Poulson:
I will try reverting that patch, but I see the same behavior in
Ubuntu-4.15.0-9.10 which I believe is before that commit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Joshua R. Poulson:
I will try reverting that patch, but I see the same behavior in
Ubuntu-4.15.0-9.10 which I believe is before that commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
Few final comments on the work I did to narrow this:
* Issue is present in ubuntu but not in mainline (4.15.17 I think is closest? I
have tried a bunch though 4.15.0, 4.15.18, 4.15.16...)
* I compiled mainline kernel 4.15.17 from linux-stable with ubuntu config from
Few final comments on the work I did to narrow this:
* Issue is present in ubuntu but not in mainline (4.15.17 I think is closest? I
have tried a bunch though 4.15.0, 4.15.18, 4.15.16...)
* I compiled mainline kernel 4.15.17 from linux-stable with ubuntu config from
** Description changed:
When I boot a Dell Inspiron 7559 with an external monitor connected to
the hdmi port, it usually shows only a blank screen after grub and I
have to hard power off the laptop. The issue is present when the bios
and grub are in mirror mode to both screens. I can see
** Description changed:
When I boot a Dell Inspiron 7559 with an external monitor connected to
the hdmi port, it usually shows only a blank screen after grub and I
have to hard power off the laptop. The issue is present when the bios
and grub are in mirror mode to both screens. I can see
Christopher Penalver:
1) I removed the kernel parameters and I am getting the same behavior.
I'll leave it off, I had to set it to boot the live cd. There is a bug
report somewhere where I found this workaround. It seems to work now,
perhaps this acpi problem has been fixed.
2) I'd say probably
Christopher Penalver:
1) I removed the kernel parameters and I am getting the same behavior.
I'll leave it off, I had to set it to boot the live cd. There is a bug
report somewhere where I found this workaround. It seems to work now,
perhaps this acpi problem has been fixed.
2) I'd say probably
** Description changed:
When I boot a Dell Inspiron 7559 with an external monitor connected to
- the hdmi port, it consistently shows only a blank screen after grub and
- I have to hard power off the laptop. I can see the following stack trace
- in journalctl:
+ the hdmi port, it usually shows
** Description changed:
When I boot a Dell Inspiron 7559 with an external monitor connected to
- the hdmi port, it consistently shows only a blank screen after grub and
- I have to hard power off the laptop. I can see the following stack trace
- in journalctl:
+ the hdmi port, it usually shows
Christopher Penalver:
>"To clarify, you were able to test 4.15.0-17.18 successfully?"
Yes. I was able to test 4.15.0-17.18 which exhibited the issue.
>"To advise, you are performing a reverse bisect. Hence, you are looking
for the next most recent kernel after 4.15.0-9-generic 4.15.0-9.10 where
Christopher Penalver:
>"To clarify, you were able to test 4.15.0-17.18 successfully?"
Yes. I was able to test 4.15.0-17.18 which exhibited the issue.
>"To advise, you are performing a reverse bisect. Hence, you are looking
for the next most recent kernel after 4.15.0-9-generic 4.15.0-9.10 where
Christopher Penalver:
I figured out the modules thing. It seems older kernels don't have
separate debs for the modules. I needed the extra package regardless (if
both linux-modules-extra and linux-image-extra were missing I don't
think the test is right).
I went back further:
Christopher Penalver:
I figured out the modules thing. It seems older kernels don't have
separate debs for the modules. I needed the extra package regardless (if
both linux-modules-extra and linux-image-extra were missing I don't
think the test is right).
I went back further:
Small update. I've gone back to try and see what I can learn from
installing pre-built kernels:
1) for some reason when I reboot sometimes I see the grub screen in
mirror mode and sometimes one monitor is blank. This issue happens
whenever grub is mirrored between both monitors. It is always
Small update. I've gone back to try and see what I can learn from
installing pre-built kernels:
1) for some reason when I reboot sometimes I see the grub screen in
mirror mode and sometimes one monitor is blank. This issue happens
whenever grub is mirrored between both monitors. It is always
re building. I think i've gotten it building. "time fakeroot
debian/rules binary" takes a long time, but seems to be working
re your questions:
1) it's consistent. only when booting right after grub I get a kernel crash.
Every time when my monitor is connected via the HDMI connector on my
re building. I think i've gotten it building. "time fakeroot
debian/rules binary" takes a long time, but seems to be working
re your questions:
1) it's consistent. only when booting right after grub I get a kernel crash.
Every time when my monitor is connected via the HDMI connector on my
I also found the mapping between ubuntu versions and mainline versions
and so tried mainline linux-image-4.15.17-041517-generic which also did
not exhibit the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also found the mapping between ubuntu versions and mainline versions
and so tried mainline linux-image-4.15.17-041517-generic which also did
not exhibit the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Christopher Penalver:
> Without providing which kernels you tested nobody may understand why this
> happened.
I hadn't finished my testing. But i did test some of the mainline kernels
below. I'm not certain that I installed them correctly. I was hoping to get the
ubuntu kernels to build to see
Christopher Penalver:
> Without providing which kernels you tested nobody may understand why this
> happened.
I hadn't finished my testing. But i did test some of the mainline kernels
below. I'm not certain that I installed them correctly. I was hoping to get the
ubuntu kernels to build to see
penalvch, I'm having a bit of trouble. Is there instructions on building
the ubuntu kernel from git? I wasn't able to find a mainline kernel
which fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
penalvch, I'm having a bit of trouble. Is there instructions on building
the ubuntu kernel from git? I wasn't able to find a mainline kernel
which fails.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1) This started when I did a clean install of 18.04. I was running 17.10
on the same hardware with the same kernel parameters (the
"acpi_osi=!Windows 2015"). I'm afraid I can't tell you which kernel
exactly, but I keep things up to date. I upgraded a few days before this
report. I think it was
1) This started when I did a clean install of 18.04. I was running 17.10
on the same hardware with the same kernel parameters (the
"acpi_osi=!Windows 2015"). I'm afraid I can't tell you which kernel
exactly, but I keep things up to date. I upgraded a few days before this
report. I think it was
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136293/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136299/+files/ProcEnviron.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/1768139/+attachment/5136300/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136301/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136297/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136304/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136303/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I also confirmed the issue still persists as I captured the apport data.
--
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/1768139
Title:
Kernel crash when booting laptop with hdmi monitor
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136298/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136302/+files/PulseList.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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136296/+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/1768139
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136294/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136305/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136295/+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/1768139
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136292/+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/1768139
apport information
** Tags added: apport-collected
** Description changed:
When I boot a Dell Inspiron 7559 with an external monitor connected to
the hdmi port I get a crash on bootup. I can see the following stack
trace in journalctl:
syslog contains:
kernel: Missing switch
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136296/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136304/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136305/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136297/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
I also confirmed the issue still persists as I captured the apport data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
Title:
Kernel crash when booting laptop with hdmi monitor connected
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136294/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136293/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136303/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1768139/+attachment/5136302/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768139
1 - 100 of 170 matches
Mail list logo
