Markus Baumann, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754759/comments/24
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yello
** Attachment removed: "results.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+attachment/5146961/+files/results.log
** Attachment removed: "dmidecode.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+attachment/5146962/+files/dmidecode.log
** Changed
Kafabih Rahmat:
A) Regarding your comment:
>"When I turned on the bluetooth and connected to my bluetooth mouse
It's happened random segmentation fault. The bluetooth device is Atheros
AR3012."
Two follow up questions:
1. To advise, the scope of this report is regarding your wireless network car
** Tags removed: kernel-bug-exists-upstream-4.17.2 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.18-rc1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Kafabih Rahmat, to confirm, when you were using the previous release
Ubuntu 16.04.1, did this issue not happen?
--
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/1775772
Title:
Atheros Wire
Merlin:
1) For you personally with your hardware, what was the most recent
kernel/release where this issue did not happen?
2) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full manufacturer and model?
3)
Kafabih Rahmat, the issue you are reporting is an upstream one. Could
you please report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: QCA ath9k Development and Johannes Berg CC: linux-wireless)?
Please provide a direct
** Tags added: kernel-fixed-upstream-4.18-rc1
--
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/1773581
Title:
[Samsung NP900X3G-S01US] Horizontal lines after update to 4.13.0-43
Status in
Could you please advise what supported release you have reproduced this
in?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Merlin:
I) The scope of LP#1300349 is how a pre-3.18-rc4 kernel had an issue,
which 3.18-rc4 fixed. However, you are using a 4.15 kernel. Hence, the
scope and root cause are different (i.e. not relevant).
II) In order to allow additional upstream mainline kernel developers to examine
the issue,
*** This bug is a duplicate of bug 1773520 ***
https://bugs.launchpad.net/bugs/1773520
** This bug has been marked a duplicate of bug 1773520
After update to 4.13-43 Intel Graphics are Laggy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Thomas Diesenreiter, a potential fix for your problem is in the Proposed
repository. See https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed.
If you test this and it addresses the issue, this is likely a duplicate
of LP#1773520, so feel free to mark it
James (jamestheawesomedude), it will help immensely if you use the computer the
problem is reproducible with, file a new report with Ubuntu by first ensuring
the package xdiagnose is installed, and click the Yes button for attaching
additional debugging information after running the following fr
** Tags removed: performing-bisect
** Tags added: bisect-done reverse-bisect-done
--
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/1773520
Title:
After update to 4.13-43 Intel Graphics are
Not Fix Released as defined by https://wiki.ubuntu.com/Bugs/Status .
** Changed in: linux (Ubuntu)
Status: Fix Released => Incomplete
--
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/
** Package changed: linux (Arch Linux) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** No longer affects: linux (Ubuntu)
** Package changed: fedora => ubuntu
** Changed in: ubuntu
Importance: Medium => Undecided
** Changed in: ubuntu
Status: Won't
** Summary changed:
- System freeze on high memory usage
+ System freeze on high memory usage when DMA is disabled
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
jecks (slayerproof32), this report is poorly defined, and not root caused as no
debugging logs have been provided by the original reporter. However, what
little is known is that the issue for the original reporter was correlated to
when DMA was disabled in the BIOS, using a now old, and unsuppor
jecks (slayerproof32), it is most unhelpful to post comments or
attachments here, or give pastebin links. If you want to motivate
developers to want to look into your issue, file a new report. If you
want developers to ignore your problem, continue posting here.
marco (nazgul17), one may always fi
Markus Baumann:
>"Does it make sense to try the mainline kernel, since the error is
obviously fixed with 18.04?"
No, it doesn't. Given you reproduced this in 17.10 (which is EOL July
2018 as per https://wiki.ubuntu.com/Releases ), when you upgrade soon to
18.04, the issue would be gone.
--
You
whl2:
1) To clarify, when you were using 16.04, were you using the nvidia or
nouveau driver? If nvidia, which version precisely?
2) If you uninstall the nvidia driver in your current OS, and use
nouveau is there any change?
3) To keep this relevant to upstream, one will want to test the latest
m
** Tags added: cosmic
--
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/1784998
Title:
After a while touchpad doesn't work
Status in linux package in Ubuntu:
Incomplete
Status in xorg-se
fokedFromTheLife:
1) Regarding the following non-default kernel parameters in use, could you
please advise to each individually on why it was put in place, and if it is
necessary for the touchpad to work:
nouveau.modeset=0
tpm_tis.interrupts=0
acpi_osi=Linux
i915.preliminary_hw_support=1
idle=no
** This bug is no longer a duplicate of bug 847001
Adjusting display brightness is very slow on several Dell laptops
--
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/828296
Title:
[Lati
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: regression-release
--
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/1770166
Title:
The brightness of th
tazesimit (simitcii), it will help immensely if you use the computer the
problem is reproducible with, and provide necessary debugging logs by filing a
new report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Changed in: linux (Ubuntu)
Status: Co
Donk, to confirm, you tested a kernel with the noted commit in place and
the problem was reproducible. Then, you tested a kernel with that commit
reverted, and the problem was gone. Correct?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: kernel-fixed-upstream-4.17.13 kernel-fixed-upstream-4.18-rc8
** Tags added: reverse-bisect-done
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
** Tags removed: kernel-bug-exists-upstream-4.17
** Tags added: kernel-bug-exists-upstream-4.18.5
--
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/1775717
Title:
CPU/GPU Fans suddenly go 1
Luís Correia, you don't have the same problem as this report is not
scoped to 18.04, or any Dell machine.
Hence, if you want your problem addressed, use the computer the problem is
reproducible with, and provide necessary debugging logs by filing a new report
with Ubuntu via a terminal:
ubuntu-b
** Summary changed:
- System freeze on high memory usage when DMA is disabled
+ When DMA is disabled system freeze on high memory usage
** Tags removed: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Donk, to see if this is already resolved in ubuntu, could you please
test http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
** Package changed: fedora => xorg (Fedora)
** Changed in: xorg (Fedora)
Importance: High => Undecided
** Changed in: xorg (Fedora)
Status: Confirmed => New
** Changed in: xorg (Fedora)
Remote watch: freedesktop.org Bugzilla #54133 => None
** No longer affects: linux (Ubuntu Quantal)
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** 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/1771204
Title:
Ho
Anders Kvist:
>"Christopher, I believe the solution is in the redhat bug mentioned earlier.
https://bugzilla.redhat.com/show_bug.cgi?id=1565131";
What is most helpful is if one confirms with their hardware via adding
and reverting the potential fix commit that it does indeed address their
issue.
Thomas Diesenreiter, to advise, given you have the hardware, it is best
if you test reverting/adding of the potential regression commit, to
confirm it is, in fact, the correct commit. When you aren't as busy,
feel free to check out the bisect article as it is written for folks who
know nothing abou
Release EOL, and don't have hardware anymore.
** No longer affects: broadcom-sta
** Changed in: bcmwl (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-apport-collect needs-upstream-testing
** Changed in: linux (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Tags removed: needs-reverse-bisect
** Tags added: needs-bisect
--
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 connect
Battant:
>"I have dowlowded a deb archive and install it..."
The way this is worded indicates only one .deb file was installed, which
would be why it didn't show up in GRUB. Did you get a chance to review
https://wiki.ubuntu.com/Kernel/MainlineBuilds for guidance?
>"but when I tried to compile t
** Description changed:
The screen brightness cannot be changed.
In 16.04, I could change the brightness via:
xrandr --output eDP-1 --brightness 0.7
WORKAROUND: Execute at a terminal:
xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
+
+ WORKAROUND: https://extensions.gnome
marvin, regarding comment #30:
1)
>"assuming you only need the log files."
Unfortunately, this isn't the case.
2) Regarding attachments, the article requested separate attachments for
each command (not combined into one). This is to help developers know
what it is they are looking at, versus gue
Battant:
1) Unfortunately, doing an apport-collect while booted into the mainline
kernel provides no useful logs. Hence, it is best if you just make a
comment on which ones you test and the results.
2) In the apport-collect data it was noticed you are using the
lowlatency variant. Is this because
Battant:
<"Could you help me please"
Sure, could you please advise to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773643/comments/40
?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Battant, please advise to all of the following:
1) At this point, apport-collecting further isn't necessary.
2) Regarding your tests, you reported this while using the generic
Ubuntu kernel, but you just tested the lowlatency mainline kernel. Were
you at some point using lowlatency Ubuntu kernels
Zakhar, thank you for reporting this and helping make Ubuntu better.
Please execute the following command only once, as it will automatically gather
debugging information, in a terminal:
apport-collect 1774845
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubu
** Description changed:
- This is the automated ubuntu-bug linux
+ Booting into a installed environment takes a few more seconds than
+ normal.
- as requested per ticket
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682921
-
- From the original bug where I posted (1731784) and the ti
** Tags added: kernel-bug-exists-upstream-drm-tip-20180507 regression-
update xenial
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774845/+attachment/5148098/+files/Dependencies.txt
** Attachment removed: "ProcCpuinfoMinimal.txt"
https://b
** Description changed:
- Booting into a installed environment takes a few more seconds than
+ Booting into a installed environment takes a few more minutes than
normal.
WORKAROUND: Use kernel parameter:
video=SVIDEO-1:d
- ---
+ ---
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd6
** Summary changed:
- TV-out timeouts in i965 driver (since recent kernels ~4.4)
+ [Dell Inspiron 1525] Booting takes a couple more minutes than normal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Zakhar, please advise to all of the following:
1) Regarding both issues of couple minutes delay of boot, and sluggish
system, for clarity this report is scoped to the first. Once the scope
of this report is resolved for you, the second issue can be re-visited.
2) In order to allow additional upst
** Tags removed: kernel-bug-exists-upstream-drm-tip-20180507
** Tags added: kernel-bug-exists-upstream-drm-tip-20180603
--
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/1774845
Title:
[Del
Zakhar, one thing to keep in mind, there is no guarantee that the
problem you reported won't get worse as new updates come down into
Ubuntu, or that the WORKAROUND will continue to work as expected. As you
tested the latest drm-tip, where new kernel updates may be pulled from
to ultimately be place
Harsh Patel, there is no support for 2.x kernels either downstream or upstream.
For more on this, please see:
https://wiki.ubuntu.com/Releases
https://www.kernel.org/
For more on ARM and Ubuntu, please see
https://www.ubuntu.com/download/server/arm
--
You received this bug notification because
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream-3.5-rc5 needs-upstream-testing
** Changed in: linux (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
** Tags removed: kernel-bug-exists-upstream-3.5-rc5
** Tags added: kernel-bug-exists-upstream-3.5-rc7
--
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/1019672
Title:
8086:4230 [Lenovo Thin
Mitch, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767611/comments/8
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and
** Summary changed:
- i2c_hid: probe of i2c-ELAN0732:00 failed with error -61
+ [HP Envy x360 M6-ar004dx] Touchscreen not working
** Tags removed: bios-outdated-f11 kernel-bug-exists-upstream
** Tags added: bios-outdated-f20 needs-upstream-testing
--
You received this bug notification because y
** Tags added: bios-outdated-f.17 kernel-bug-exists-upstream-4.16-rc1
needs-upstream-testing
--
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/1752437
Title:
[HP ENVY x360 - 15-bq102ng] Tou
** Description changed:
The touch screen on my HP ENVY x360 15-bq102ng does not work with stock
kernel or with mainline kernel 4.16-rc3.
marc@snapbug:~$ xinput
⎡ Virtual core pointerid=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer
*** This bug is a duplicate of bug 1756455 ***
https://bugs.launchpad.net/bugs/1756455
** This bug has been marked a duplicate of bug 1756455
Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004
on battery
--
You received this bug notification because you are a mem
Kafabih Rahmat, thank you for taking the time to report this bug and helping to
make Ubuntu better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1775772
** Changed in: linux (Ubuntu)
Importance: Undecided
Dmitry Malykhanov, the next step is to fully commit bisect from Ubuntu
kernel 4.15.0-10.11 to Ubuntu kernel 4.15.0-12.13, in order to identify
the last good kernel commit, followed immediately by the first bad one.
This will allow for a more expedited analysis of the root cause of your
issue. Could
Mijail Febres Soria, to see if this is already resolved in Ubuntu, could
you please test http://cdimage.ubuntu.com/daily-live/current/ and advise
to the results?
** No longer affects: network-manager (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (
Markus Baumann, thank you for reporting this and helping make Ubuntu
better.
1) To clarify, if you don't adjust the MTU does the LAN network still
connection cycle?
2) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to t
*** This bug is a duplicate of bug 1753227 ***
https://bugs.launchpad.net/bugs/1753227
** This bug has been marked a duplicate of bug 1753227
Ubuntu 17.10 freezes randomly
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
** Tags added: bios-outdated-300
--
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/1753227
Title:
Ubuntu 17.10 freezes randomly
Status in linux package in Ubuntu:
Incomplete
Bug descrip
Matteo:
1) Could you please post the output of the following terminal command (not
manually attach files):
ls -la /var/crash
2) Could you please post the output of the following terminal command:
sudo cat /var/lib/whoopsie/whoopsie-id
3) Please provide the output of the following terminal comma
*** This bug is a duplicate of bug 1473200 ***
https://bugs.launchpad.net/bugs/1473200
** This bug has been marked a duplicate of bug 1473200
adaptec starfire fails to initialize with pae kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is s
** Tags added: kernel-bug-exists-upstream-4.14-rc1 needs-upstream-
testing xenial
** Description changed:
Adaptec ethernet adapter using starfire driver fails to initialize when
a pae-enabled kernel is used. Adapted initializes correctly with a non-
pae kernel:
From dmesg:
[3.154
Steve Holton:
1) To clarify, for the modification of
drivers/net/ethernet/adaptec/starfire.c at line 653 did you test this in
both 32-bit and 64-bit environments and had no issues using it?
2) To keep this relevant to upstream, it is best to continue to test the
latest mainline kernel (now 4.17.1
Mijail Febres Soria, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/comments/139
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the
whl2, please execute the following command only once, as it will automatically
gather debugging information, in a terminal:
apport-collect 1775717
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Nando, in addition to providing the test results from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/comments/4
:
1) As per TP-Link there are three versions of this device https://www
.tp-link.com/us/download/TL-WN722N.html. Which version do you have?
2) As per the sticker of the co
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #44161 => None
**
** Tags added: bionic kernel-bug-exists-upstream-4.17
--
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/1775230
Title:
TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
Status
whl2, Ubuntu kernel only. My bad for not specifying precisely.
--
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/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status
Nando:
1) Could you please provide the full motherboard manufacturer and model?
2) Could you please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
3) To keep this relevant to upstream, one will want to test the latest
m
** Description changed:
- I see high cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2. I tested various kernels from Ubuntu and mainline (3.5.0-x, 3.6.x,
3.7.0-rcx) and they all showed the same behavior. This does not always happen.
- I wasn't able to determine on which basis
Mio, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: Rafael J. Wysocki and Len Brown CC: linux-acpi)?
Please provide a direct URL to your po
Mio, please don't change the Description. It is filled with old,
irrelevant, and speculative statements that confuse and hinder
developers resolving the problem.
Despite this, have you reported this upstream as noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/73
?
**
Mio, if you want an upstream developer to review your problem and submit
a fix patch, you *need* to file a *new* upstream report as previously
advised (not continue to post here on Launchpad). Otherwise your issue
may never be addressed.
** Tags removed: regression-potential
** Tags added: needs-f
Anupam Datta, the next step is to fully commit bisect from kernel 4.4 to
4.15 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https://wiki.u
Anupam Datta, could you please run the following command from a terminal
as it will automatically gather and attach updated debug information to
this report:
apport-collect 1751198
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecid
stre...@bluewin.ch, please respond to all of the following:
1) Could you please perform the following in Ubuntu 17.10 to gather information
about your working setup via a terminal:
apport-collect 1769331
2) Could you please provide debugging logs from a live environment of
http://cdimage.ubuntu.
marvin, please address the all of the following:
1. When using 16.10, were you able to adjust the brightness via keyboard
key press, or you could only adjust the brightness via xrandr?
2. In order to allow additional upstream mainline kernel developers to examine
the issue, at your earliest conv
Jacob Zimmermann, in order to allow additional upstream mainline kernel
developers to examine the issue, at your earliest convenience, could you please
test the latest mainline kernel available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) T
Scott Testerman, the next step is to fully commit bisect from kernel
4.7.10 to 4.8 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https://w
Thomas, the next step is to fully commit bisect from kernel 4.4 to 4.15
in order to identify the last good kernel commit, followed immediately
by the first bad one. This will allow for a more expedited analysis of
the root cause of your issue. Could you please do this following
https://wiki.ubuntu.
Sandy Patterson, please address all of the following:
1. Is this something that started to happen after an update? If so,
which and when precisely?
2. In order to allow additional upstream mainline kernel developers to examine
the issue, at your earliest convenience, could you please test the la
Jochen Schroeder, please respond to all of the following:
1) To capture relevant debugging logs, could you please undo the WORKAROUND,
boot into a Ubuntu kernel (not upstream) and execute the following in a
terminal:
apport-collect 1767701
2) The next step is to fully reverse commit bisect from
Mitch, please address all of the following:
1) To gather system debugging information, could you please execute the
following via a terminal:
apport-collect 1767611
2) To clarify, this issue only happens after resuming from suspend (i.e.
after booting from a shutdown, performing subsequent power
Philip Taylor, please advise to all of the following:
1) While booted into default Ubuntu kernel 4.15 and having removed all
WORKAROUNDs, could you please execute the following from a terminal to gather
relevant debug logs:
apport-collect 1767603
2) The next step is to fully commit bisect from
Frew Schmidt, please address all of the following:
1) Could you please execute the following via a terminal to attach debugging
logs:
apport-collect 1767452
2) The next step is to fully reverse commit bisect from kernel 4.16.6 to
4.17-rc3 in order to identify the last bad commit, followed immedi
Rod B., the next step is to fully reverse commit bisect from kernel 4.4
to 4.16 in order to identify the last bad commit, followed immediately
by the first good one. Once this good commit has been identified, it may
be reviewed for backporting. Could you please do this following
https://wiki.ubuntu
deeks9000, in order to allow additional upstream mainline kernel developers to
examine the issue, at your earliest convenience, could you please test the
latest mainline kernel available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) The one
Bob, to confirm this is an upstream issue, could you please test the
latest mainline kernel available (4.17-rc5) and advise to the results?
Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.
** Tags removed: kernel-bug-exists
Maximilian Federle, the next step is to fully reverse commit bisect from
kernel 4.16.3 to 4.17-rc1 in order to identify the last bad commit,
followed immediately by the first good one. Once this good commit has
been identified, it may be reviewed for backporting. Could you please do
this following
Daniel Nespoulous, please advise to all of the following:
1) To see if this still affects upstream, could you please test the
latest mainline kernel (now 4.17-rc5) and advise to the results?
Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it be
Anil Gobburi, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766006/comments/21
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow
101 - 200 of 20804 matches
Mail list logo
