I am sorry, you are still experiencing this, and that the Intel
developers do not seem to have time to deal with this.
Does somebody know if this is a regression, that means did it work in
the past for example with firmware `iwlwifi-7260-16.ucode` from August
2015 [1], or another Linux kernel vers
Jonathan, thank you for the feedback. Please share the mainboard model
and firmware, and the used memory for the record.
--
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/1690085
Title:
Ryz
[Please remove the quote next time from your reply. If you look at the
Web interface, the comments get needlessly long because of that.]
(In reply to cspadijer from comment #20)
[…]
> Okay yes. I will mark as fixed and open up new for other issues you
> clarified as linux. Thanks for your help
> Aug 3 20:44:16 UTC 2021
> [ 6.958699] nvidia_uvm: module uses symbols from proprietary module
> nvidia, inheriting taint.
> [ 8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type
> mismatch - Found [Buffer], ACPI requires [Package] (20201113/nsarguments-61)
Fi
As the ASUS X541UVK is a different device, please create a new bug
report with all the necessary information included/attached.
--
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/1521173
Title
Agmon, thank you for your report. Please open a separate issue with the
full output of `dmesg` attached, and the output of `acpidump`. Please
reference the issues here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
(In reply to Ashesh Ambasta from comment #736)
[…]
> I also see the following when looking at all similar messages:
>
> |╰─$ journalctl| grep 'xhci.*Mismatch' ||
> ||Jun 13 14:43:09 quasar-nixos-tr kernel: xhci_hcd :09:00.3:
> Mismatch between completed Set TR Deq Ptr command &
(In reply to Ashesh Ambasta from comment #720)
> I can confirm that in my case, all the suggested alternatives in this
> thread didn't work (the ones that were applicable to my use-case anyway).
>
> In the end, I threw my hands up and did an RMA. And that was over a
> month ago. It seems to have
nt take on the CPU.
>
> On 7/12/20 3:58 PM, bugzilla-dae...@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=196683
> >
> > --- Comment #698 from raulvior@gmail.com ---
> > Did you ask for an RMA? Did it work?
> > (In reply to Ashesh
(In reply to Ashesh Ambasta from comment #680)
> I've been facing the same issue since I've bought this machine and setting
> my BIOS power settings to "Typical current idle" has only partially fixed
> things (the system still crashes every 1-2 weeks during idle: I leave my
> desk, screensaver fire
(In reply to Rafal Kupiec from comment #675)
> (In reply to Paul Menzel from comment #674)
> > (In reply to Charles Lim from comment #673)
> >
> > > For those who are looking for a solution or already found a solution,
> there
> > > is a new update of AGESA rolling out. The new version 1.0.0.4 cla
(In reply to Charles Lim from comment #673)
> For those who are looking for a solution or already found a solution, there
> is a new update of AGESA rolling out. The new version 1.0.0.4 claims:
>
> * Improved system stability when switching through ACPI power states.
>
> It has arrived on my Asu
(In reply to onox from comment #607)
To prevent misunderstandings, let me repeat what I previously wrote,
from a different angle: ASRock X370 Taichi firmware version v5.50 is
worse than previous versions in that it removes the "Power Supply Idle
Control" option off the configuration screen. As a r
The latest firmware for X370 Taichi, v5.50 (2019/4/24), removes the "Power
Supply Idle Control" option off the configuration UI; downgrading is not
supported (but effectively possible at least from Windows). It is still
possible to set "Power Supply Idle Control" (C6 package) via MSR using e.g.
Should this be added to the stable series too?
--
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/1748565
Title:
Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
(0x0
This Bug seems to affect even basic HCI functionality:
"hcitool inq" is never returning in my case. dmesg gives me said error message.
I have tried two different USB-Bluetooth Dongles:
[ ] usb 2-2: New USB device found, idVendor=04b4, idProduct=f901, bcdDevice=
1.12
[ ] usb 2-2: New USB device st
Ben, Alan, Rafael, could you please close it then?
--
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/952080
Title:
laptop immediately resumes after sending to standby
Status in Linux:
In
(In reply to Antoine Pitrou from comment #398)
> @Daniel what makes you think this bug is fixed? It certainly isn't for me.
> I have a ASRock Fatal1ty X370 Gaming X motherboard, a Ryzen 7 1700 CPU, have
> updated the motherboard BIOS to its latest version (4.80 with
> PinnaclePI-AM4_1.0.0.2 Patch
The title of the bug should be changed to include Ryzen 7 1700X, and the
reporter should follow up, if the problem still occurs with Linux 4.18.
For the other issues, separate bug reports should be submitted. Though
the mailing lists might be the better forum for this, as the Linux
kernel develope
19 matches
Mail list logo
