Turns out "pcie_aspm=off" effectively disables AER because Linux doesn't
request AER control when it doesn't advertise ASPM support (see
ACPI_PCIE_REQ_SUPPORT). That explains why "pcie_aspm=off" would avoid
the error reporting.
This report was from a v3.11-based kernel. v3.11 is from Mon Sep 2
1
Also, if you do see this issue, some have reported that "pcie_aspm=off"
avoids the errors. If that's the case for you, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6
and help me investigate it!
--
You received this bug notification because you are a member of Kernel
Generally we should not see reproducible PCIe Correctable Errors in
significant numbers. Some have reported that "pcie_aspm=off" avoids the
errors. If that's the case for you, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6
and help me investigate it!
--
You received
We should not need to use "pci=noaer". Generally we should not see
reproducible PCIe Correctable Errors in significant numbers. Some have
reported that "pcie_aspm=off" avoids the errors. If that's the case for
you, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6
and h
Is this reproducible? Is it related to suspend/resume? Even if the
kernel hang is not reproducible, I'm interested in the PCIe Corrected
Errors. Some have reported that "pcie_aspm=off" avoids the errors. If
that's the case for you, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/204366
We should not need to use "pci=noaer". Generally we should not see
reproducible PCIe Correctable Errors in significant numbers. Some have
reported that "pcie_aspm=off" avoids the errors. If that's the case for
you, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6
and h
We should not need to use "pci=noaer". Generally we should not see
reproducible PCIe Correctable Errors in significant numbers. Some have
reported that "pcie_aspm=off" avoids the errors. If that's the case for
you, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6
and h
There are a couple mentions of "pcie_aspm=off" making a difference here.
If that's the case, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6
and help me look at this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
If this is still reproducible, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/comments/6
--
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/1798880
Title:
PCIe Bus Error: s
Thank you! "pci=noaer" definitely sweeps this dust under the carpet,
and it would be much better to avoid that.
Narcis (comment #157) reported that "pcie_aspm=off" is a workaround and
is much more specific than "pci=noaer".
If we can collect complete dmesg and "sudo lspci -vv" output when
bootin
The "pcie_aspm=off" kernel parameter hides a problem. I would really
like to fix the underlying problem so the parameter isn't needed.
If anybody sees this problem and is willing to help fix it, please open
a bug report at https://bugzilla.kernel.org/, product Drivers/PCI,
mention the hardware pla
Sometimes the "pcie_aspm=off" kernel parameter hides this problem. I
would really like to fix the underlying problem so the parameter isn't
needed.
If anybody sees this problem and is willing to help fix it, please open
a bug report at https://bugzilla.kernel.org/, product Drivers/PCI,
mention the
The "pcie_aspm=off" kernel parameter hides a problem. I would really
like to fix the underlying problem so the parameter isn't needed.
If anybody is willing to help fix it, please open a bug report at
https://bugzilla.kernel.org/, product Drivers/PCI, mention the hardware
platform, and attach:
Original report mentions "pci=noaer". If this is needed, it most likely
is working around a kernel defect, and I'd like to fix the defect.
If "pci=noaer" is needed, PLEASE report it to linux-...@vger.kernel.org.
Then we can try to fix the underlying problem so the parameter is not
needed for futu
Is this still an issue? If so, can somebody add a complete dmesg log
and "sudo lspci -vv" output from a current kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/671979
Title:
Repe
Is this still an issue? If so, can somebody add a complete dmesg log and
"sudo lspci -vv" output from a current kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER:
These freezes look pretty terrible. Looks like you're running a v5.15
kernel. Are they reproducible on a more recent kernel, e.g., v6.2?
--
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/200
No worries, your report and testing so far has been an immense help, so
thank you for that!
https://git.kernel.org/linus/07eab0901ede ("efi/x86: Remove
EfiMemoryMappedIO from E820 map") is essentially the same as the test
patch from comment #62, and it appeared in v6.2-rc1, so just wait for a
kern
This is a duplicate of bug 1878279. I hope to fix it with this series:
https://lore.kernel.org/all/20221202211838.1061278-1-helg...@kernel.org/
This series will probably *not* help if this Clevo NL4XLU (or NL41LU2)
system has a BIOS switch to boot in a "legacy" or "CSM" mode. If that
switch exis
N.B. Comment #149 came from bugzilla.kernel.org, NOT from launchpad, and
the bug 216565 mentioned is a kernel.org bug number:
https://bugzilla.kernel.org/show_bug.cgi?id=216565.
Launchpad mistakenly linkified "bug 216565" it to an unrelated launchpad
bug with the same number.
** Bug watch added:
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product N
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product N
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product N
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product N
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product Name, and Board Name. This isn't
an ideal solution because there are li
The Unsupported Request errors look like the same issue as
https://bugzilla.kernel.org/show_bug.cgi?id=215453 and should be
resolved by https://git.kernel.org/linus/c01163dbd1b8 ("PCI/PM: Always
disable PTM for all devices during suspend"), which appeared in
v6.1-rc1.
I don't know whether the NIC
I don't know what's in the 5.18.10-76051810-generic kernel (I assume that's
v5.18 + some Ubuntu patches). The upstream fixes for this went into v5.19:
https://git.kernel.org/linus/3cc30140dbe2
I think v5.18 + the following patches (which somebody added in the "Bug
Description" at the very begin
v5.19-rc1 was tagged Sun Jun 5 17:18:54 2022 -0700. Final release
likely to be July 24 or 31. The crystal ball:
https://hansen.beer/~dave/phb/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Should be fixed by https://git.kernel.org/linus/d341838d776a, which will
appear in v5.19-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/1884232
Title:
touchpad and touchscreen doesn
The "ACPI region does not cover" errors are not related to the AER PCIe
bus error.
Neither is the nouveau MMIO read fault (that looks like a null pointer
problem).
Naveen Naidu is looking at the AER problem, so I hope we'll have a patch
that makes "pci=noaer" unnecessary.
--
You received this b
Chime in on this email thread if interested:
https://lore.kernel.org/r/20200723201403.GA1450503@bjorn-Precision-5520
There are instructions at the bottom of that page about how to reply to the
thread.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Yes, I think that kernel is fine.
You can leave the i8042.nopnp=1 in your kernel command line parameters.
Otherwise it looks right.
--
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/1884232
1) Sorry, I don't have a PPA or similar kernel image for you to try.
2) I expected that Windows would move 00:1f.5 BAR 0 to be inside the
windows reported by the PCI0 _CRS, but the AIDA64 report shows
otherwise:
B00 D1F F05: Intel Ice Point-LP PCH - SPI (Flash) Controller
It looks like a BIOS bug to me.
But Windows does work, and Linux should, too. It looks like there's
plenty of available space for 00:1f.5 BAR 0. Can you try a current
version of Linux, e.g., v5.8-rc1 with the command line argument
'dyndbg="file drivers/pci/* +p"'? There were some significant re
This looks like a BIOS defect. BIOS programmed BAR 0 to [mem
0xfe01-0xfe010fff], but according to the PCI0 _CRS method, that area
is not routed to the PCI bus:
ACPI: PCI Root Bridge [PCI0] (domain [bus 00-fe])
pci_bus :00: root bus resource [mem 0x000a-0x000b window]
pc
I'm not using Mint. I started with Ubuntu 18.04 in June 2018, installed
the "cinnamon" package, and recently updated to 20.04. I don't know if
this is a regression because I didn't start using this configuration
until after moving to 20.04. Pretty sure cinnamon came from the ubuntu
repo; my only
I'm sure it's not a Linux kernel bug. I don't have any idea *where* the
bug is, and https://wiki.ubuntu.com/Bugs/FindRightPackage suggested
"linux" as a safe bet.
Sorry, I didn't realize Cinnamon wasn't supported by Ubuntu. I will
either live with the behavior or switch to the supported Ubuntu d
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379897/+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/1881644/+attachment/5379885/+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/1881644
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379888/+files/Lsusb-t.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/1881
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379893/+files/ProcModules.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/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379891/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379882/+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/1881644
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379894/+files/PulseList.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/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379883/+files/CurrentDmesg.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
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379886/+files/Lspci-vt.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/18
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379884/+files/IwConfig.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/18
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379890/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379887/+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/1881644
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379896/+files/UdevDb.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/1881644
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379892/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379889/+files/Lsusb-v.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/1881
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1881644/+attachment/5379895/+files/RfKill.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/1881644
apport information
** Tags added: apport-collected focal
** Description changed:
Dell 5520 laptop -> Dell Thunderbolt dock -> HDMI -> external monitor.
Running 20.04, i915 driver.
Laptop lid closed, using external monitor only. When external monitor
turns off (after sleep-display-ac)
** Summary changed:
- 20.04 i915 laptop external monitor turns off when inactive, must open lid to
turn it on
+ 20.04 i915 laptop external monitor doesn't resume from power-save, must open
lid to turn it on
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification bec
John, can you also include a little more detail about what the failure
looks like to a user? Does this result in AER errors being logged?
When we come up with a patch that works, I'd like to include a hint
about what user-visible problems it fixes in the changelog. I see from
the initial report t
Please try the attached patch. It makes it so that if the device does
not support ECRC generation or checking, we don't enable those features.
Currently (without this patch), we *do* enable ECRC generation and
checking if _HPX allows, i.e., if the platform can support ECRC.
The ACPI dump confirms
https://bugzilla.kernel.org/show_bug.cgi?id=92351#c1 reports the problem occurs
with LSI FW 18.
https://bugzilla.kernel.org/show_bug.cgi?id=92351#c8 reports the problem does
NOT occur with LSI FW 19. So upgrading the adapter firmware to version 19 may
be a fix.
There is a patch at
https://bugz
>From the Linux kernel point of view, changing the BIOS option is not a
good fix, and "pci=realloc=off" is just a workaround and not a real fix
either. Linux should be able to work even without that, or at least
give meaningful error messages.
The original problem appears to be that:
- BIOS al
** Bug watch added: Linux Kernel Bug Tracker #92351
http://bugzilla.kernel.org/show_bug.cgi?id=92351
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=92351
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of K
There's a test patch at
https://bugzilla.kernel.org/show_bug.cgi?id=175391 Any test reports
would be welcome.
--
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/1627496
Title:
radeon broken
Related problem report:
https://bugzilla.kernel.org/show_bug.cgi?id=109691
Brief analysis of AER issue:
http://lkml.kernel.org/r/20151229155822.GA17321@localhost
I did say in that analysis that I was going to work on fixing this, but
I haven't had time. It would be great if somebody would jump i
The register in question is the Advanced Error Capabilities and Control
register, at offset 0x18 in the Advanced Error Reporting capability,
which starts at 0x148 in the config space of device 80:02.0.
In the pre-boot value of 0x00a0, the following bits are set (per PCIe
spec r3.0, sec 7.10.7, the
This looks related to https://bugzilla.kernel.org/show_bug.cgi?id=111601
Is "pci=noaer" (without using "pci=nomsi") sufficient to allow the
system to boot?
If you boot with "pci=noaer", does it still take a long time to boot?
If so, can you collect a dmesg log with timestamps so we can see where
The git link in comment #17 is stale because it references a branch
name, which is often re-used.
I think
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?h=9a6d7298b0833614c411f774c46514efb1bd5651
is a permanent link to the same thing.
--
You received this bug notification be
For Micro-Star MS-7253 systems, this should be fixed by:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=841137170961
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a97f4f5e524b
which appeared upstream in v3.3. This should fix the proble
"pci=use_crs" is a workaround but not a fix. If anybody who has this
problem can attach a complete dmesg log, we should be able to fix the
kernel so it works without having to boot with "pci=use_crs".
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Thanks for the bug report, Cristian. There's definitely something wrong
here. There are several similar reports of invalid UUID, and I just
don't believe they're all caused by BIOS bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=17792 (your report)
https://bugzilla.kernel.org/show_bug.cgi?id=3
This is not a duplicate of bug 438335.
This bug is caused by something wrong with the BARs of 00:0b.0:
pci :00:0b.0: BAR 1: error updating (0x001001 != 0x01)
pci :00:0b.0: BAR 4: error updating (0x4004 != 0x36850264)
pci :00:0b.0: BAR 4: error updating (high 0x00 !=
https://bugzilla.kernel.org/show_bug.cgi?id=63661 claims to be the same
as this bug and that the problem is caused by "pci: Rework ASPM disable
code" from commit 3c076351c4027a56d5005a39a0b518a4ba393ce2.
I'm not 100% sure that's the case, because comment #8 reports that
"pci=conf1" is a workaround
Oops, I screwed up. Please try this patch.
** Attachment added: "Revert EISA changes"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+attachment/3951225/+files/eisa-revert
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
StefanF, I took care of attaching these to the upstream report
(https://bugzilla.kernel.org/show_bug.cgi?id=59311). Thanks a lot for
collecting them. I apologize that I haven't had time to make progress
on this issue.
--
You received this bug notification because you are a member of Kernel
Pack
Fernando, can you attach the dmesg log and "lspci -vv" output from the
newest working kernel, so we can compare them with those from the non-
working 3.11 kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Probably the same as this upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=63861
** Bug watch added: Linux Kernel Bug Tracker #63861
http://bugzilla.kernel.org/show_bug.cgi?id=63861
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This is an upstream kernel issue. The upstream bug report is
https://bugzilla.kernel.org/show_bug.cgi?id=59311
If anyone is in a position to reproduce the problem with the v3.11 upstream
kernel, please attach the following to the upstream bug report:
- Complete dmesg log
- "lspci -vv" output
75 matches
Mail list logo
