PaulSchulz, thank you for reporting this and helping make Ubuntu better.
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? Please keep in mind the following:
1) The one to test
Selwyn, to clarify, have you tested the commit noted in #31 with your
hardware and confirmed it fixes the issue?
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812561
Title:
** Tags added: cherry-pick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270676
Title:
SD Card Reader broken on UX302LG
To manage notifications about this bug go to:
shadowvzs, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812561
Title:
[MacBookPro11,5] wakes up and suspends in a loop while closed
** Tags added: latest-bios-3304
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595047
Title:
Frequent swapping causes system to hang
To manage notifications about this bug go to:
PaulSchulz, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
To manage notifications about this bug go to:
As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694225/comments/31
.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579410
Title:
Cannot suspend HP ProLiant SE316M1R2
To manage notifications about this bug
Emrah ÖZCAN, please answer all of the following:
1) To clarify, is your computer set to suspend when you close the lid?
2) Did this issue start to happen with your Acer TravelMate 5335 after
an update? If so, which one precisely?
3) To see if this is already resolved in Ubuntu, could you please
** This bug is no longer a duplicate of bug 982299
[Dell Inspiron 1520] Screen stays black after laptop lid is opened
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825219
Title:
Acer Aspire
Emrah ÖZCAN, 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 1825219
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and
** This bug is no longer a duplicate of bug 1825219
Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/449538
Title:
** This bug is no longer a duplicate of bug 1825219
Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442163
Title:
Dell
** This bug is no longer a duplicate of bug 1825219
Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982299
Title:
[Dell
Hark:
1) For one who is using 16.04, an upgrade for the X stack is available
following instructions from
https://wiki.ubuntu.com/Kernel/LTSEnablementStack . Could you please
advise to the results?
2) Regarding the package xserver-xorg-video-ati, this is fixed as per
Hark, thank you for reporting this and helping make Ubuntu better.
1) To confirm a regression, has this always been an issue since you
installed "Ubuntu-Server 10.04 LTS" or is this something that started to
happen after an update?
2) To clarify, did you personally test the WORKAROUNDs noted in
** No longer affects: dia
** Description changed:
+ Upstream report:
+ https://gitlab.gnome.org/GNOME/dia/issues/344
+
What is expected to happen when importing the attached .vdx file
exported from Visio 2007 Professional is that the text does not move
around.
What happens instead is
Hark (cab902), it will help immensely if you filed a new report with Ubuntu by
ensuring you have the package xdiagnose installed, and that you click the Yes
button for attaching additional debugging information running the following
from a terminal:
ubuntu-bug xorg
Also, please feel free to
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Fix Released => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #49201 =>
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
To manage notifications about this bug go to:
Peter Schüller, please advise to all of the following:
1) While attached logs when using an upstream kernel advised one to
contact "the Linux USB developers" (i.e. linux-usb and Maintainer Greg
Kroah-Hartman, as GKH ultimately reviews+approves/declines usb commits,
and this would give him a heads
elhoir:
>"i contacted with a guy with an AMD RX 470 GPU and he says irs working
fine on his system"
Besides mundane root causes (card hardware jacked and needs RMA), there
are other reason why your results differ from others (not all RX 470
cards are equivalent in every way due to OEM
Peter Schüller, if this is confirmed with the latest mainline kernel
(now 5.0.2), then 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 linux-usb CC
Peter Schüller, 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? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily
Peter Schüller, thank you for reporting this and helping make Ubuntu better.
Could you please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1819362
** Changed in: linux-signed-hwe (Ubuntu)
Importance: Undecided
elhoir, if its actually true you personally were able to boot using the
RX470 without WORKAROUNDs, its possible that either when you are
installing older kernels you aren't installing the correct packages, or
you were mistaken and it only booted either with a WORKAROUND or when a
different
elhoir:
1)
>"but i cannot find a working scenario to start with"
To clarify, you stepped through all the Ubuntu kernel versions from
4.19.0-7.8 to 5.0.0-7.8 and the problem is still reproducible?
If so, stepping through versions older than 4.19.0-7.8 until a working
state is found would be
yoshiki2:
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? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily
elhoir, while you are welcome to wait for whenever a maintainer may
respond, given this issue has been reported a regression, it is known
that it helps developers expedite a fix if the offending commit(s) are
identified via bisect.
--
You received this bug notification because you are a member
yoshiki2, 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 1819242
** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)
** Changed in:
yoshiki2, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
yoshiki2, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
elhoir:
1)
Please ensure you are not using non-default kernel parameters. As per most
recent dmesg remove:
acpi_osi=Linux modprobe.blacklist=amdgpu crashkernel=384M-:128M
crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M crashkernel=512M-:192M
crashkernel=512M-:192M
2)
Keep testing
elhoir, the next step is to fully commit bisect from Ubuntu kernel
4.19.0-7.8 to Ubuntu kernel 5.0.0-7.8. This will allow for a direct
review of the offending commit(s) for either reverting, or further
improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection
elhoir:
1)
>"yes, its a copy paste of crash part of dmesg, not entire output."
Then attach a full dmesg as previously advised.
2)
>"GPU (RX 470) is quite new. I tested Ubuntu Cosmic and Ubuntu Dingo."
To confirm, using only the RX470, it worked fine in Cosmic and Dingo.
However, while using
elhoir:
1)
Regarding the dmesg posted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/20 did
you cut/snip it? Please ensure all logs are attached in their entirety (no
cuts, snips, etc.).
2)
To confirm a regression, regarding only the current AMD graphics card
elhoir:
Without evidence (screenshots, recording, logs, etc.) developers cannot
root cause, and fix your issue. Hence, when will you be posting the
video you said will be captured as per your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/13
?
** Tags added:
elhoir:
1)
Regarding your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/9 :
>" No, never, but i never used amdgpu driver before"
I'm afraid this didn't answer my question. Which release precisely did
you have to start using nomodeset to boot?
2)
Regarding your
elhoir:
1) It looks like you installed Ubuntu originally with 11.10, and then
upgraded all the way to 19.04. To clarify, have you always had to use
the kernel parameter nomodeset to boot since 11.10?
2) With all of the following kernel parameters removed (and any
WORKAROUND or other non-default
elhoir (jfarroyo82), it is most helpful if you file a new report. If the
nomodeset WORKAROUND lets you boot, please file a new report via a terminal:
ubuntu-bug linux
Else, use:
https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
Please feel free to subscribe me to it.
--
You received
Kamal Pandey, one may update the BIOS using Windows temporarily
following https://help.ubuntu.com/community/BIOSUpdate .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299104
Title:
[Lenovo G510
** Tags removed: bios-outdated-1.6.1 kernel-bug-exists-upstream-4.7
needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-5.0-rc8 latest-bios-1.6.1
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of
adin:
1)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/comments/34
>"To clarify, when you first installed Ubuntu 16.04 were you able to toggle the
>touchpad?"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/comments/35
>"I was able to toggle it on the command line or
adin:
1) To clarify, when you first installed Ubuntu 16.04 were you able to
toggle the touchpad?
2) Have you tested any release older than 16.04?
3) To keep this relevant to upstream, one would want to periodically
check for, and test the latest mainline kernel (now 5.0-rc8) as it is
released.
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #42843 => None
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #46721 => None
Stephan Berger, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Changed in: linux (Ubuntu)
Importance: Undecided
opensas:
1)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/43
>"Then I tried with several versions from the upstream kernels..."
Which upstream kernels did you test precisely?
2)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/46
>"Any idea about
** Tags added: needs-bisect- needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816947
Title:
[Dell XPS L321X] Touchpad not working after last apt-get upgrade
To manage
opensas, the next step is to fully commit bisect from 4.13.13 to 4.15.
This will allow for a direct review of the offending commit for either
reverting, or further improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was
written for folks
Closing as Ubuntu 15.04 EOL, haven't used xchat in years, and upstream doesn't
maintain it anymore as per them:
https://bugzilla.gnome.org/show_bug.cgi?id=746997#c1
** No longer affects: xchat-gnome
** Changed in: xchat-gnome (Ubuntu)
Importance: High => Low
** Changed in: xchat-gnome
** Tags added: regression-potential
** Description changed:
Hello.
Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-
- WN722N into the USB port, the CPU usage goes to 100%, and there are
- multiple reports of "stack traces" in dmesg.
+ WN722N Version 1.10 into a USB
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792672
Title:
Regression: acpi reports battery state incorrectly after sleep
To
opensas:
To further narrow the regression, in Ubuntu 18.04 or higher, if you
install kernel 4.13.3 from https://wiki.ubuntu.com/Kernel/MainlineBuilds
does the touchpad work again?
** Tags removed: regression-potential
** Tags added: regression-release
--
You received this bug notification
** Tags removed: kernel-bug-exists-upstream latest-bios-1.2.2
** Tags added: bios-outdated-1.6.1 needs-upstream-testing
** Description changed:
- Installed ubuntu 15.10 on alienware 13, touchpad is showing up in xinput list
as expected, but is totally unresponsive. Was working fine on 14.05
-
** Tags removed: kernel-bug-exists-upstream latest-bios-1.2.15
** Tags added: bionic bios-outdated-1.6.1 cosmic needs-upstream-testing
** Summary changed:
- [Dell Alienware 17R3] enable/disable touchpad not working
+ [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working
** Changed
opensas:
To confirm the regression point, could you please test a live
environment of https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes and
advise to the results?
** Description changed:
- The touchpad doesn't work.
+ The touchpad doesn't work unless the cursor is moved slowly.
opensas:
1) To advise, you don't have to apport-collect any further unless
specifically requested to do so.
2) Does the touchpad work in the live environment of 18.04 without using
any WORKAROUND?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
opensas, please advise to all of the following:
1) When discussing this issue, please keep it to only one machine (the
Dell XPS 13 L321X, not multiple) and Ubuntu (not popos! or some other
unsupported distro, unofficial flavor, etc.).
2) Regarding this issue with the Dell XPS 13 L321X, is this
** Description changed:
+ The touchpad doesn't work.
- already filed at:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046
-
- check: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
- synaptics/+bug/1096046/comments/33
-
- affects:
** Summary changed:
- Touchpad not working after last apt-get upgrade
+ [HP Folio 13 Notebook PC] Touchpad not working after last apt-get upgrade in
Precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: cosmic wayland-session
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239110/+files/WifiSyslog.txt
** Attachment removed: "UdevDb.txt"
Tom Louwrier, this report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/comments/82
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
Eugene Savelov, RedHat bug 454131 was opened and closed by you (not someone who
represents upstream or RedHat):
https://bugzilla.redhat.com/show_activity.cgi?id=454131
Despite this, regarding a way forward here on Launchpad, if you want your
problem addressed, it will help immensely if you use
Eugene Savelov, having a WORKAROUND on different hardware, and an unconfirmed
assumption of root cause, doesn't cause this report to be Invalid. For more on
Status, please see:
https://wiki.ubuntu.com/Bugs/Status
Despite this, given Tom Louwrier is the original reporter, if he would
like to
** Description changed:
hi
Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated
twice a day at the moment.
Linux seems not to recognize the keyboard in my laptop well. Starting early
in the boot process (well before X kicks in) I see error messages on the
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812561
Title:
[MacBookPro11,5] wakes up and
Selwyn, as the latest version of Ubuntu is based on 4.19.x, to confirm
this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Selwyn, one may follow the below to confirm results for your hardware:
https://wiki.ubuntu.com/Kernel/KernelBisection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812561
Title:
[MacBookPro11,5]
Selwyn:
>"...all information is in the attachments of the post."
No, its not. You posted one dmesg (multiple requested in article) on a
now old version of upstream kernel (i.e. nearly impossible to keep
upstreams attention as you aren't using a version supported upstream).
>"Anyways this is
Selwyn, given the workaround never worked, this isn't confirmed a usb
problem (although could still be due to usb).
Hence, this report would still be missing the vast majority of the
information requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/comments/5
in order for a
Selwyn:
1) >"...the workaround is invalid..."
What update was applied specifically that afterwards this stopped
working?
2) >"...should I retry sending the email? I did not get any reply."
Based on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/comments/19
you would never get a
Upstream fix commits in 6.2 are confirmed to resolve this:
Version: 6.2.0.3 (x64)
Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/107854
Title:
massimiliano, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
** Description changed:
Similar bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/
The first time suspending works great but after that suspending causes
the laptop to wake up regardless of the method used to suspend.
+
+ WORKAROUND: Disable XHC1 prior to sleeping:
+ #
Marko Muehlberg (markom2), would you be able to confirm the commit from
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
is the root cause for your issue by testing a revert of it following
Closing as upstream issue, reproduced with eol version of Ubuntu and
AbiWord, and may already be fixed in later and supported version of
Ubuntu.
** No longer affects: abiword
** Changed in: abiword (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are
** Changed in: xrdp (Ubuntu)
Assignee: 이동언 (dongeun) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/220005
Title:
xrdp 0.6.1-2 doesn't work via sesman-X11rdp
To manage
Selwyn:
"! I could not send the email though, the email address "linux-
u...@vger.linux.org" seems invalid."
If you post the email source of the message sent, and what you may have
received in a response, then this may be assessed.
--
You received this bug notification because you are a member
Selwyn, 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: linux-usb CC: Mathias Nyman and Greg Kroah-Hartman)?
This article was written for folks who
udippel, it will help immensely if you use Ubuntu with the computer the problem
is reproducible with and file a new report to provide necessary debugging logs
via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
** Description changed:
- The em28xx module is used with a lot of TV and video hardware, and is
- needed also for the video grabber Terratec Grabster AV350MX. However,
- with this external, USB connected device the wrong settings are applied,
- allowing only a (good quality) video picture, but no
Selwyn, could you please provide all of the missing information from
https://wiki.ubuntu.com/DebuggingKernelSuspend ?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Selwyn, thank you for reporting this and helping make Ubuntu better.
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? Please keep in mind the following:
1) The one to test is in
Tudor Holton:
Given you've tested the latest mainline kernel, latest BIOS, and assuming all
the previous test results are the same when not using any non-default kernel
parameters as noted in your Bug Description:
i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013"
it appears one is to wait while
** Tags removed: kernel-bug-exists-upstream-4.2-rc4 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-5.0-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tudor Holton, to confirm a WORKAROUND, in both kernel Ubuntu 4.20 and
mainline 5.0-rc2:
1) If you remove the module iwlwifi prior to suspend, after resuming and
before enabling the module, do you still have crashes, or an issue
successfully resuming?
2) If 1) was successful, if you then enable
** Tags removed: bios-outdated-a17
** Tags added: latest-bios-a17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832
Title:
Suspend issue with Dell Venue 11 Pro 7140
To manage notifications
Michael Gratton:
1) To keep this relevant to upstream, one would want to periodically
check for, and test the latest mainline kernel (now 5.0-rc2) as it is
released. Could you please advise to the results?
2) Did you contact upstream as noted in
Selwyn (siilwyn), it will help immensely if you use Ubuntu with the computer
the problem is reproducible with and file a new report via a terminal to
provide necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you
Steven Ellis, for you personally:
1) Did this problem not occur in a prior Ubuntu or kernel release, and
if so which?
2) If this issue has always occured, could you please advise to the
earliest kernel you tested?
3) To keep this relevant to upstream, one will want to test the latest
mainline
** Summary changed:
- amd_iommu conflict with Marvell Sata controller
+ amd_iommu conflict with Marvell 88SE9230 SATA Controller
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810239
Title:
** Description changed:
- This bug is to confirm that the Marvell 88SE9230 chipset bug presents
- under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
- Kernel
+ Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors:
+
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Pablo Rossy Bernardes Mozinho Ferreira (santoross08-p), it will help immensely
if you use Ubuntu with the computer the problem is reproducible with and file a
new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You
** Also affects: linux
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Changed in: linux
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: linux (Ubuntu)
** Project changed: xserver-xorg-driver-ati => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: freedesktop.org Bugzilla
Eugene Kosogin, here are some ways to engage ASUS on this particular
issue:
1) Advise support the issue is reproduced using Windows 10 x64 (OS precisely
quoted from the ASUS website below) so Consumer Support can't disclaim
responsibility. You will likely get the best traction with them if this
101 - 200 of 46714 matches
Mail list logo
