[Bug 1902981] Re: AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are known to fail on AMD K8, K10 and Intel Kentsfield platforms
As said there: https://lkml.org/lkml/2021/5/13/752 The bug was also reproduced on Intel Kentsfield platform (Core 2 Quad Q6600 (with VIA PT880/VT82xx) with R300 and TeraScale GPUs. ** Summary changed: - AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are known to fail on K8 and K10 platforms + AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are known to fail on AMD K8, K10 and Intel Kentsfield platforms -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902981 Title: AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are known to fail on AMD K8, K10 and Intel Kentsfield platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc2
** Summary changed: - PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 + PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
I've reproduced the issue on Piledriver platform with AMD 9590 CPU, with both ATI and Nvidia PCI GPUs. With the ATI GPU, I get the usual symptom of the computer freezing display while the GNOME desktop is partially loaded. It's possible to open a TTY console by switching consoles but once returned to the graphical desktop, the computer becomes definitely unresponsive. This is similar to what is seen on older hardware like K10 or K8 platforms. With the Nvidia GPUs, I get garbage (we can even notice some parts of the GNOME desktop), and the computer is unresponsive. Sometime the display is lost then returns and it cycles like that. This is the usual symptom seen on older hardware like K10 and K8 platforms. ** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS rev.2 PCI on Piledriver PCIe host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5432604/+files/20201109-110741-000.nvidia-geforce-8400gsr2-pci+piledriver.jpg ** Summary changed: - PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 + PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable
See patch and comments on https://lkml.org/lkml/2020/11/5/308 Patch was rewritten in a way the message is shorter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
See patch and comments on https://lkml.org/lkml/2020/11/5/307 Patch was rewritten in a way the message is shorter and comment uses better language. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
** Description changed: - This is an issue I found while investigating #1899304 + This is an issue I faced before #1899304 but becomes more critical with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304 The big concern is that if AGP is disabled, there is no fallback display option on those platforms. After having discovered some K8 and K10 computers running AGP cards stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to try some PCI cards to know if problems came from AGP or something else, and I've discovered another issue instead. Note that I'm not talking about PCI express, but good old PCI. The other issue I found is that PCI graphics on AMD K8/K10 platform is broken since years. This got probably unnoticed because such hardware works on Intel platform and those cards are not very common, so the chance to fulfill all the requirements to reproduce the bug are not that high. To make the test significant enough I used two PCI devices from two makers, and some that are not so old: they both support OpenGL 3.3, have 512MB of VRAM, and one of them even have HDMI. - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA I've driven tests on four computers: - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU (quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU (dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI Both PCI GPU work on the Intel based computer, and I get performances that looks correct for those GPU given they are PCI ones. You can find real-life use case test result here (look for “PCI”): https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix I tested two Ubuntu versions and multiple kernels: Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic All those configurations fail with those two PCI GPUs on AMD K8/K10 platforms. I got some logs and screenshots, so I will add them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable
This reverts commit ba806f98f868ce107aa9c453fef751de9980e4af. Disabling AGP leaves some hardware without working alternative on some platforms. For example, PCI GPUs are known to be broken on K8 and K10 platforms since years: the breakage was reproduced from Linux 4.4 on Ubuntu 16.04 Xenial to Linux 5.10-rc1 on Ubuntu 20.04 Focal, and it is expected to be older than Linux 4.4. Also, there may be some bugs specific to AGP GPUs being driven as PCI ones since fixing some PCI bugs introduces newer bugs that are very specific to AGP GPUs driven as PCI ones and not to PCI native ones. Some AGP GPUs are still relevant to this day, like the high-end ATI Radeon HD 4670 AGP (RV730 XT), a very capable TeraScale GPU designed for OpenGL 3.3 and OpenCL 1.0 and featuring HDMI port and 1GB of VRAM. This GPU was distributed by various manufacturers and was still sold as brand new in 2012, for example this one: http://www.hisdigital.com/un/product2-448.shtml https://web.archive.org/web/2012/https://www.amazon.com/gp/product/B003CYKCG8/ As an example, this AGP GPU still gets 140+ fps on the competitive Xonotic game in 2020, as verified during the XDWC 2020 event, also when compared to other games on the Unvanquished GPU compatibility matrix, we can notice that to outperform such GPU, Intel users have to acquire an UHD 600 graphic chip from 2016, and Nvidia users relying on the free open source nouveau driver have to acquire a GTX 1060 from 2016: https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix Motherboards compatible with powerful CPUs like the quad core AMD AM3 Phenom II CPU X4 970 (3.5GHz) supporting virtualization, 16GB of RAM and featuring AGP and PCI slots (not PCI Express ones) were sold, like this motherboard from 2006 supporting this CPU from 2010: https://www.asrock.com/mb/nvidia/am2nf3-vsta/ https://www.cpu-world.com/cgi-bin/IdentifyPart.pl?PART=HDZ970FBK4DGM This is basically among the best the market had to offer in 2012 for AGP users. Disabling AGP turns such very capable computers and their AGP GPUs into paperweights. Even if PCI and AGP-as-PCI issues are fixed, disabling AGP is expected to strongly affect performance of such GPUs, and disabling AGP may hide bugs that may be introduced after the disablement. A boot command line switch to disable AGP to rely on PCI fallback may be welcome to help testing the PCI code and prevent it to rot as it is easier to find AGP cards than PCI ones. See related bugs: - https://bugs.launchpad.net/bugs/1899304 (this one) > AGP disablement leaves GPUs without working alternative > (PCI fallback is broken), makes very-capable ATI TeraScale GPUs > unusable - https://bugs.launchpad.net/bugs/1902981 > AGP GPUs driven as PCI ones (when AGP is disabled at kernel build > time) are known to fail on K8 and K10 platforms - https://bugs.launchpad.net/bugs/1902795 > PCI graphics broken on AMD K8/K10 platform (while it works on Intel) > verified from Linux 4.4 to 5.10-rc1 ** Patch added: "PATCH: Revert ba806f9 "drm/radeon: disable AGP by default"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5431457/+files/0001-Revert-drm-radeon-disable-AGP-by-default.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable
Before bisecting, I investigated the PCI issue: https://bugs.launchpad.net/bugs/1902795 I've faced the PCI issue before the AGP one, but it was less critical. I've submitted a patch that may fix some issues (with drawback of being non-optimal on platforms were PCI graphics are known to already work) but not everything is fixed. To be clear: that does not fix PCI GPU failure on K8 / K10 neither AGP-as-PCI failure, but that is at least a step forward, and would help specialists to investigate more the issue. At this point I may have reached my skill cap on such topic. Because PCI and AGP-as-PCI behaves differently and the later code may have specific bugs, I opened an issue dedicated to track bugs when AGP cards are driven as PCI ones: https://bugs.launchpad.net/bugs/1902981 I did not bisected anything after having identified the breakage was introduced by 5.9-rc1, and I directly tried to revert commit ba806f98f868ce107aa9c453fef751de9980e4af that disabled AGP at kernel build. I reverted this commit over the 5.10-rc2 tag from the torvalds branch and both the ATI Radeon HD 4670 on the K10 computer and the ATI Radeon X1950 PRO on the AMD K8 computer started to work again immediately. Game performance was as expected and desktop experience was really smooth like we can expect from such aging but high end hardware from its time. It looks like I misread your first comment, I believed you were asking me to try the 5.10-rc1 build like if that commit was already reverted (the only action that seems to be able to fix the issue at this point). After this commit is reverted, I have not yet noticed the other issues I've reported (disk IO seems to be OK, I have not tested audio yet), so the other ones may have been collateral damage of the AGP/PCI one. So, you were right, the regression was introduced by the "drm/radeon: disable AGP by default" commit. It sounds too early to disable without alternative some hardware that was still sold as brand new in 2012 (the ATI Radeon HD 4670 AGP was). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902981] Re: AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are known to fail on K8 and K10 platforms
** Summary changed: - AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms + AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are known to fail on K8 and K10 platforms -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902981 Title: AGP GPUs driven as PCI ones (when AGP is disabled at kernel build time) are known to fail on K8 and K10 platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902981] Re: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms
On a side note, because we see a clear behaviour difference when applying the PCI patch we can assume the driver catch the `rdev->flags & RADEON_IS_PCI` test instead of the `rdev->flags & RADEON_IS_AGP` one when running an AGP GPU with AGP disabled in kernel at build time. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: amd64 focal kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902981 Title: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable
** Tags added: kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
** Tags added: amd64 focal ** Tags added: kernel-bug ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902981] Re: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms
It looks like comment #3 had been truncated, the interesting part of the dmesg log that is missing is: ``` [ 66.755306] radeon :01:00.0: ring 0 stalled for more than 31248msec [ 66.755317] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 66.840372] radeon :01:00.0: Saved 25 dwords of commands on ring 0. [ 66.840402] radeon :01:00.0: GPU softreset: 0x0019 [ 66.840408] radeon :01:00.0: R_008010_GRBM_STATUS = 0xA27034A1 [ 66.840414] radeon :01:00.0: R_008014_GRBM_STATUS2 = 0x0102 [ 66.840419] radeon :01:00.0: R_000E50_SRBM_STATUS = 0x200028C0 [ 66.840424] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x0400 [ 66.840429] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010100 [ 66.840434] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x8C80 [ 66.840438] radeon :01:00.0: R_008680_CP_STAT = 0x808182E7 [ 66.840443] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 67.364934] radeon :01:00.0: Wait for MC idle timedout ! [ 67.364940] radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x7F6B [ 67.365005] radeon :01:00.0: SRBM_SOFT_RESET=0x0100 [ 67.367106] radeon :01:00.0: R_008010_GRBM_STATUS = 0x3028 [ 67.367110] radeon :01:00.0: R_008014_GRBM_STATUS2 = 0x0002 [ 67.367114] radeon :01:00.0: R_000E50_SRBM_STATUS = 0x200028C0 [ 67.367118] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 67.367122] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x [ 67.367126] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x [ 67.367130] radeon :01:00.0: R_008680_CP_STAT = 0x [ 67.367134] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 67.367152] radeon :01:00.0: GPU reset succeeded, trying to resume [ 67.842179] radeon :01:00.0: Wait for MC idle timedout ! [ 68.068765] radeon :01:00.0: Wait for MC idle timedout ! [ 68.082273] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [ 68.082448] radeon :01:00.0: WB enabled [ 68.082454] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 68.082459] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 68.088977] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 [ 68.374095] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 68.374176] [drm:rv770_resume [radeon]] *ERROR* r600 startup failed on resume ``` This is what happens when applying the patch to force 32-bit DMA bit mask on PCI devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902981 Title: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902981] Re: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms
To get a better picture of such top-of-the-line AGP GPU performance, when comparing to others GPUs on Unvanquished GPU compatibility matrix: https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix we can see the ATI Radeon HD 4670 AGP (RV730 XT, TeraScale 1) performs: - better than the PCI Express ATI Radeon HD 7450 from Q1 2012 (RV910, Caicos, TeraScale 2), - like the mobile Nvidia GeForce GT 740M from Q2 2013 with nvidia driver (NVE7, GK107M, Kepler), - like the mobile Quadro K1100M from Q3 2013 with nvidia driver (NVE7, GK107GLM, Kepler), - like the integrated Intel HD 4600 from Q1 2014 (i7-4810MQ, Haswell, Gen7 GT2), - like the integrated Intel HD 520 from Q3 2015 (i3-6100U, Skylake, Gen9 GT2), - like the PCI Express GeForce GTX 1050 Ti from Q4 2016 when running the nouveau driver (Pascal). On Nvidia side, to outperform this GPU on Linux with the free open source nouveau driver it is required to acquire at least a GeForce GTX 1060 from 2016 (NV136, GP106-300-A1, Pascal). Intel users may had to wait for the UHD 600 series (2016) to outperform this ATI AGP GPU. To this day the first verified Intel GPU that is known to outperform this ATI AGP GPU is the UHD 620 from Q3 2019. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902981 Title: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902981] Re: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms
When applying patch from https://bugs.launchpad.net/bugs/1902795 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431335/+files/0001 -drm-radeon-make-all-PCI-GPUs-use-32bits-DMA-bit-mask.patch which reduces the breakage (but not fix completely) the issues faced with PCI GPUs on K8 and K10 hosts by setting DMA bit mask to 32-bits for all PCI GPUs, we can see those this that is fixed on PCI GPUs is not fixed on AGP-as-PCI GPUs (and there is even more errores before that): ``` [ 5.242322] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) ``` Things even go that wrong we even don't see those other errors that are expected to be seen after that: ``` [ 5.242359] radeon :01:00.0: disabling GPU acceleration ``` ``` [ 34.558889] trying to bind memory to uninitialized GART ! ``` Instead, the kernel loops before reaching those errors, trying desperately to pass this r600_ring_test step. But before r600_ring_test failure message is printed, more and newer issues about ring 0 being stalled and GU lockup occurs with AGP-as-PCI GPUs that are never seen with PCI-native GPUs, especially when taken in account PCI GPUs can at least pass the r600_ring_test with the patch. Also, after the r600_ring_test failure message, instead of getting the message telling GPU acceleration is disabled, we get a message about r600 startup failing on resume which is new. This is why it is believed that fixing PCI GPUs may not be enough to fix AGP GPUs running as PCI ones when AGP is disabled at kernel build time. Here are the issues that is only seen with AGP-as-PCI GPUs, occurring before and after the r600_ring_test failure message: ``` [ 45.763336] radeon :01:00.0: ring 0 stalled for more than 10256msec [ 45.763349] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 46.275324] radeon :01:00.0: ring 0 stalled for more than 10768msec [ 46.275335] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 46.787322] radeon :01:00.0: ring 0 stalled for more than 11280msec [ 46.787332] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 47.299336] radeon :01:00.0: ring 0 stalled for more than 11792msec [ 47.299346] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 47.811320] radeon :01:00.0: ring 0 stalled for more than 12304msec [ 47.811332] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 48.323331] radeon :01:00.0: ring 0 stalled for more than 12816msec [ 48.323344] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 48.835307] radeon :01:00.0: ring 0 stalled for more than 13328msec [ 48.835318] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 49.347328] radeon :01:00.0: ring 0 stalled for more than 13840msec [ 49.347341] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 49.859316] radeon :01:00.0: ring 0 stalled for more than 14352msec [ 49.859326] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 50.371471] radeon :01:00.0: ring 0 stalled for more than 14864msec [ 50.371483] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 50.883318] radeon :01:00.0: ring 0 stalled for more than 15376msec [ 50.883328] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 51.395315] radeon :01:00.0: ring 0 stalled for more than 15888msec [ 51.395327] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 51.907325] radeon :01:00.0: ring 0 stalled for more than 16400msec [ 51.907338] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 52.419319] radeon :01:00.0: ring 0 stalled for more than 16912msec [ 52.419330] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 52.931321] radeon :01:00.0: ring 0 stalled for more than 17424msec [ 52.931331] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 53.443321] radeon :01:00.0: ring 0 stalled for more than 17936msec [ 53.44] radeon :01:00.0: GPU lockup (current fence id 0x0001 last fence id 0x0002 on ring 0) [ 53.955335]
[Bug 1902981] Re: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms
As a reminder, this is a dmesg captured when running ATI Radeon HD 4670 AGP on a K10 host on Linux 5.9 (vanilla). The ATI Radeon HD 4670 AGP (RV730 XT) is a very capable TeraScale GPU, supporting OpenGL 3.3 (Directx 10 on Windows) and OpenCL 1.0, and featured HDMI output and 1GB of VRAM. The host is also a very capable AMD Phenom II quad core CPU with 16GB of ram. To verify if its performances match 2020 expectations, I just engaged it (running Ubuntu 20.04) in 2020 Xonotic Defrag World Championship which is currently running (https://xdwc.teichisma.info/), and I got feedback from some players reporting this hardware may be better than their own hardware they compete with. In fact competitive games like Xonotic run at 144fps on 1920×1080 resolution. The last kernel able to drive this GPU on Ubuntu 20.04 LTS is the 5.4.0-47-generic one, the 5.4.0-48-generic one is believed to have backported the AGP disablement from 5.9-rc1 (ba806f9). So, when running on 5.4.0-48-generic kernel from Ubuntu repositories, or here, 5.9 vanilla compiled by myself, interesting parts from dmesg log may be: ``` [5.242322] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [5.242359] radeon :01:00.0: disabling GPU acceleration ``` and: ``` [ 34.558889] trying to bind memory to uninitialized GART ! [ 34.559048] WARNING: CPU: 1 PID: 2516 at drivers/gpu/drm/radeon/radeon_gart.c:299 radeon_gart_bind+0xdf/0xf0 [radeon] [ 34.559050] Modules linked in: zram snd_usb_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core snd_hwdep snd_pcm snd_seq_midi kvm_amd snd_seq_midi_event ccp joydev kvm snd_seq snd_rawmidi input_leds snd_timer snd_seq_device snd soundcore k10temp mac_hid serio_raw binfmt_misc sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear uas usb_storage hid_generic usbhid hid radeon i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm psmouse forcedeth i2c_nforce2 [ 34.559107] CPU: 1 PID: 2516 Comm: gnome-shell Not tainted 5.9.0 #1 [ 34.559109] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AM2NF3-VSTA, BIOS P3.20 10/09/2009 [ 34.559178] RIP: 0010:radeon_gart_bind+0xdf/0xf0 [radeon] [ 34.559184] Code: 00 48 89 ef 48 8b 40 60 e8 0e 2f 44 df 31 c0 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 c7 c7 38 6f 6b c0 e8 23 0c 6d de <0f> 0b b8 ea ff ff ff eb dc 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [ 34.559187] RSP: 0018:c030838f7a28 EFLAGS: 00010282 [ 34.559191] RAX: RBX: a0cf6b88eb80 RCX: 0027 [ 34.559193] RDX: 0027 RSI: 0086 RDI: a0cf6fc98d08 [ 34.559196] RBP: c030838f7b28 R08: a0cf6fc98d00 R09: 0004 [ 34.559198] R10: R11: 0001 R12: c030838f7b28 [ 34.559201] R13: a0cf6a622868 R14: a0cf6c7cc6e8 R15: c030838f7b28 [ 34.559204] FS: 7f46ae245cc0() GS:a0cf6fc8() knlGS: [ 34.559207] CS: 0010 DS: ES: CR0: 80050033 [ 34.559210] CR2: 56494261c1c8 CR3: 00040bfe6000 CR4: 06e0 [ 34.559212] Call Trace: [ 34.559286] radeon_ttm_backend_bind+0x58/0x210 [radeon] [ 34.559305] ttm_tt_bind+0x32/0x60 [ttm] [ 34.559321] ttm_bo_handle_move_mem+0x236/0x590 [ttm] [ 34.559339] ttm_bo_validate+0x16c/0x180 [ttm] [ 34.559407] ? drm_ioctl_kernel+0xe9/0xf0 [drm] [ 34.559422] ttm_bo_init_reserved+0x2ae/0x320 [ttm] [ 34.559438] ttm_bo_init+0x6d/0xf0 [ttm] [ 34.559504] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 34.559569] radeon_bo_create+0x184/0x210 [radeon] [ 34.559634] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 34.559703] radeon_gem_object_create+0xa9/0x180 [radeon] [ 34.559773] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.559840] radeon_gem_create_ioctl+0x66/0x120 [radeon] [ 34.559850] ? tomoyo_path_number_perm+0x66/0x1d0 [ 34.559918] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.559968] drm_ioctl_kernel+0xaa/0xf0 [drm] [ 34.560021] drm_ioctl+0x1ec/0x390 [drm] [ 34.560090] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.560152] radeon_drm_ioctl+0x49/0x80 [radeon] [ 34.560160] __x64_sys_ioctl+0x83/0xb0 [ 34.560167] do_syscall_64+0x33/0x80 [ 34.560174] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 34.560179] RIP: 0033:0x7f46b369550b [ 34.560183] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 34.560186] RSP: 002b:7ffdb7421658 EFLAGS: 0246 ORIG_RAX: 0010 [ 34.560189] RAX: ffda RBX: 7ffdb74216d0 RCX: 7f46b369550b [
[Bug 1902981] [NEW] AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms
Public bug reported: This bug is to track specific issues faced by AGP GPUs when running as PCI devices (when AGP support is disabled at kernel build time), unless otherwise proven it is believed fixing #1902795 (PCI GPUs support being broken) may not fix all issues for AGP GPUs running as PCI ones (more to come on that topic). See related bugs: - https://bugs.launchpad.net/bugs/1902795 > PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified > from Linux 4.4 to 5.10-rc1 - https://bugs.launchpad.net/bugs/1899304 > AGP disablement leaves GPUs without working alternative (PCI fallback is > broken), makes very-capable ATI TeraScale GPUs unusable ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902981 Title: AGP GPU on PCI mode (when AGP is disabled at kernel build time) known to fail on K8 and K10 platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale AGP GPUs unusable
** Summary changed: - Linux 5.4.0-48 (and later) causes AGP GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues + AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale AGP GPUs unusable ** Summary changed: - AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale AGP GPUs unusable + AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: AGP disablement leaves GPUs without working alternative (PCI fallback is broken), makes very-capable ATI TeraScale GPUs unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes AGP GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Summary changed: - Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues + Linux 5.4.0-48 (and later) causes AGP GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes AGP GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
Just a reupload of the previously posted patch, fixing some typos. ** Patch removed: "PATCH: drm/radeon: make all PCI GPUs use 32 bits DMA bit mask (not enough to fix the issue and ATI specific)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431266/+files/0001-drm-radeon-make-all-PCI-GPUs-use-32bits-DMA-bit-mask.patch ** Patch added: "PATCH: drm/radeon: make all PCI GPUs use 32 bits DMA bit mask (not enough to fix the issue and ATI specific)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431335/+files/0001-drm-radeon-make-all-PCI-GPUs-use-32bits-DMA-bit-mask.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
Here is a dmesg log from september, running the PCI Nvidia 8400GS rev.2 with nouveau on a K8 non-AGP host with Nvidia C51 PCI Express bridge. The GPU is driven by proprietary non-free closed nvidia driver. Yet again, this PCI GPU is known to work with nvidia driver when plugged into an Intel platform. Here may be the interesting parts: ``` [ 76.927044] NVRM: GPU at PCI::05:00: GPU-d18ccf5d-6557-e114-0ca8-23449bccf157 [ 76.927050] NVRM: Xid (PCI::05:00): 6, PE0002 [ 78.018458] NVRM: Xid (PCI::05:00): 8, Channel 0001 [ 80.010804] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 82.017647] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 90.401898] NVRM: Xid (PCI::05:00): 8, Channel 007e [ 92.385614] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 96.321610] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 106.785733] NVRM: Xid (PCI::05:00): 8, Channel 007e [ 108.785676] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 112.785766] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 123.169763] NVRM: Xid (PCI::05:00): 8, Channel 007e [ 125.153618] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 129.153612] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 138.079318] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than pnp 00:06 [mem 0x000ce000-0x000c] [ 138.079726] caller os_map_kernel_space+0x6d/0xb0 [nvidia] mapping multiple BARs [ 145.569349] NVRM: GPU at PCI::05:00: GPU-d18ccf5d-6557-e114-0ca8-23449bccf157 [ 145.569386] NVRM: Xid (PCI::05:00): 6, PE0002 [ 146.689722] NVRM: Xid (PCI::05:00): 8, Channel 0001 [ 148.689670] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 150.690247] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 159.009723] NVRM: Xid (PCI::05:00): 8, Channel 007e [ 161.009666] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 165.009757] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 175.393763] NVRM: Xid (PCI::05:00): 8, Channel 007e [ 177.393696] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 181.393788] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 191.61] NVRM: Xid (PCI::05:00): 8, Channel 007e [ 193.505609] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context [ 197.717628] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context ``` Note that there is two things you can ignore from this log, this part: ``` [ 47.301362] NVRM: The NVIDIA GeForce 6150 LE GPU installed in this system is NVRM: supported through the NVIDIA 304.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 340.108 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [ 47.301582] NVRM: ignoring the legacy GPU :00:05.0 [ 47.302069] nvidia: probe of :00:05.0 failed with error -1 ``` This motherboard features an onboard soldered Geforce 6150 LE GPU usually accessed through HyperTransport bus when there is no add-on card on PCIe slots. The BIOS is expected to disable the onboard GPU when there is an add-on one, and it usually disables that onboard GPU when there is an add-on one (usually on PCI Express port), except when this Nvidia PCI card is plugged. Anyway, the driver ignores it. The part that can be ignored is this one: ``` [ 55.661641] NVRM: Your system is not currently configured to drive a VGA console [ 55.661645] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver [ 55.661646] NVRM: requires the use of a text-mode VGA console. Use of other console [ 55.661648] NVRM: drivers including, but not limited to, vesafb, may result in [ 55.661648] NVRM: corruption and stability problems, and is not supported. ``` It's a warning the proprietary non-free closed driver is printing to ask the user to plug an useless screen on the VGA port (that will not be able to display anything and will not be made available to the user to extend the desktop) so the user can use a screen on the DVI port properly. This is just an Nvidia weirdness among **many**, and this has nothing to do with the current bug, this weirdness can be experimented with select other Nvidias GPU including PCIe ones that work on this host and on others. The nouveau driver does not ask to plug the VGA to an useless screen to use the DVI port correctly,
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
Here is a dmesg log from september, running the PCI Nvidia 8400GS rev.2 with nouveau on a K8 non-AGP host with Nvidia C51 PCI Express bridge. The GPU is driven by nouveau. So at this time I at least managed to connect through SSH while there was no display. The dmesg log reports a GPU lockup. Yet again, this PCI GPU is known to work with nouveau driver when plugged into an Intel platform. Here may be the interesting parts: ``` [ 52.256093] nouveau :05:00.0: DRM: core notifier timeout [ 54.256228] nouveau :05:00.0: DRM: base-0: timeout [ 54.256455] Console: switching to colour frame buffer device 240x67 [ 54.256542] nouveau :05:00.0: fifo: DMA_PUSHER - ch 1 [DRM] get 00 put 00 ib_get 0002 ib_put 0003 state a000 (err: IB_EMPTY) push 00406040 [ 54.256633] nouveau :05:00.0: fifo: DMA_PUSHER - ch 1 [DRM] get 00 put 00 ib_get 0003 ib_put 0011 state a000 (err: IB_EMPTY) push 00406040 [ 54.256687] nouveau :05:00.0: fifo: DMA_PUSHER - ch 1 [DRM] get 00 put 00 ib_get 0011 ib_put 0020 state a000 (err: IB_EMPTY) push 003020b0 [ 54.256740] nouveau :05:00.0: fifo: DMA_PUSHER - ch 1 [DRM] get 00 put 00 ib_get 0020 ib_put 0033 state a000 (err: IB_EMPTY) push 00406040 [ 54.256811] nouveau :05:00.0: fifo: DMA_PUSHER - ch 1 [DRM] get 00 put 00 ib_get 0033 ib_put 0049 state a000 (err: IB_EMPTY) push 003020b0 [ 54.725747] nouveau :05:00.0: DRM: GPU lockup - switching to software fbcon [ 54.808979] nouveau :05:00.0: fb0: nouveaudrmfb frame buffer device [ 54.809352] [drm] Initialized nouveau 1.3.1 20120801 for :05:00.0 on minor 1 ``` ** Attachment added: "dmesg on Linux 5.4.0-47-generic, K8 platform (PCIe host, C51 bridge), Nvidia 8400GS rev.2 PCI with nouveau" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431331/+files/dmesg.linux-5.4.0-47.Dell_OptiPlex_740+K8-C51_Nvidia-8400GSr2_PCI-nouveau.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
** Attachment added: "dmesg on Linux 5.8 vanilla on K10 host running the HD 4350 PCI GPU" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431287/+files/dmesg.linux-5.8-vanilla_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4350-PCI.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
** Attachment added: "dmesg on Linux 5.8 with 32bit dma patch on K10 host running the HD 4350 PCI GPU, demonstrating some errors being workarounded (not all)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431288/+files/dmesg.linux-5.8-dma32fix_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4350-PCI.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
I noticed a similar bug was reported on 3.2 kernel in year 2012: https://bugzilla.redhat.com/show_bug.cgi?id=785375 At the time the bug was fixed by switching the PCI DMA bit mask from 40-bits to 32-bits: https://bugzilla.redhat.com/attachment.cgi?id=603278 The initial patch was testing against the GPU chip family, but that seems wrong because now we see the same GPUs working with 40-bits mask on some Intel platforms and not on some AMD platforms. This patch makes all PCI GPU use 32-bit masks. This is expected to be non-optimal platforms supporting 40-bits DMA masks, but is safest. An alternative would be to test against the platforms. This patch is not enough to fix PCI GPUs working on K8 and K10 platforms, also, this patch only concern Radeon hardware, while Nvidia hardware are both affected on those platforms (both running nouveau or nvidia). This patch makes enough to workaround this error on ATI PCI devices on K10: ``` [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) radeon :03:00.0: disabling GPU acceleration ``` And this one on both ATI PCI devices on K10 and ATI AGP devices on Linux 5.9 (AGP disabled?): ``` trying to bind memory to uninitialized GART ! ``` This is not enough to fix PCI GPUs on K8 (K8T800) and K10 (nForce3), also, non-ATI Nvidia PCI GPUs are affected by at least one other bug that may be in common. This is not a call to disable AGP, and other bug(s) left such AGP hardware unusable once AGP is disabled. This patch has been written against Linux 5.8 vanilla but applies correctly on on 5.9 and 5.10-rc2. ** Bug watch added: Red Hat Bugzilla #785375 https://bugzilla.redhat.com/show_bug.cgi?id=785375 ** Patch added: "PATCH: drm/radeon: make all PCI GPUs use 32 bits DMA bit mask (not enough to fix the issue and ATI specific)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5431266/+files/0001-drm-radeon-make-all-PCI-GPUs-use-32bits-DMA-bit-mask.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
So, the 5.4.0-48 error is the same as the one that appears with 5.9 (and the one we see with PCI GPUs): ``` [0.00] Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 (Ubuntu 5.4.0-48.52-generic 5.4.60) … [3.366387] PCI Interrupt Link [LKLN] enabled at IRQ 21 [3.426007] [drm] radeon kernel modesetting enabled. [3.435680] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe000 -> 0xefff [3.456237] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xfebe -> 0xfebe [3.478847] checking generic (e000 13) vs hw (e000 1000) [3.478853] fb0: switching to radeondrmfb from VESA VGA [3.490892] Console: switching to colour dummy device 80x25 [3.490909] radeon :01:00.0: vgaarb: deactivate vga console [3.491182] PCI Interrupt Link [LNKD] enabled at IRQ 19 [3.491321] [drm] initializing kernel modesetting (RV730 0x1002:0x9495 0x1002:0x0028 0x00). [3.491325] [drm] Forcing AGP to PCIE mode [3.491353] resource sanity check: requesting [mem 0x000c-0x000d], which spans more than PCI Bus :00 [mem 0x000d-0x000d window] [3.491359] caller pci_map_rom+0x71/0x18c mapping multiple BARs [3.492982] ATOM BIOS: RV730XT [3.493101] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [3.493104] radeon :01:00.0: GTT: 1024M 0x4000 - 0x7FFF [3.493108] [drm] Detected VRAM RAM=1024M, BAR=256M [3.493110] [drm] RAM width 128bits DDR [3.493193] [TTM] Zone kernel: Available graphics memory: 8231890 KiB [3.493195] [TTM] Zone dma32: Available graphics memory: 2097152 KiB [3.493198] [TTM] Initializing pool allocator [3.493203] [TTM] Initializing DMA pool allocator [3.493221] [drm] radeon: 1024M of VRAM memory ready [3.493223] [drm] radeon: 1024M of GTT memory ready. [3.493230] [drm] Loading RV730 Microcode [3.493316] [drm] Internal thermal controller without fan control [3.512582] [drm] radeon: dpm initialized [3.512696] [drm] GART: num cpu pages 262144, num gpu pages 262144 [3.534540] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [3.534726] radeon :01:00.0: WB enabled [3.534730] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x(ptrval) [3.534733] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x(ptrval) [3.541143] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 and cpu addr 0x(ptrval) [3.541147] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.541149] [drm] Driver supports precise vblank timestamp query. [3.541151] radeon :01:00.0: radeon: MSI limited to 32-bit [3.541204] [drm] radeon: irq initialized. … [5.677888] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [5.677934] radeon :01:00.0: disabling GPU acceleration [5.696050] [drm] Radeon Display Connectors [5.696054] [drm] Connector 0: [5.696055] [drm] VGA-1 [5.696057] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [5.696059] [drm] Encoders: [5.696061] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [5.696062] [drm] Connector 1: [5.696063] [drm] HDMI-A-1 [5.696064] [drm] HPD2 [5.696066] [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c [5.696068] [drm] Encoders: [5.696069] [drm] DFP2: INTERNAL_UNIPHY1 [5.696070] [drm] Connector 2: [5.696072] [drm] DVI-I-1 [5.696073] [drm] HPD1 [5.696074] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c [5.696076] [drm] Encoders: [5.696077] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [5.696079] [drm] DFP1: INTERNAL_UNIPHY … [5.905120] [drm] fb mappable at 0xE034D000 [5.905124] [drm] vram apper at 0xE000 [5.905126] [drm] size 8294400 [5.905127] [drm] fb depth is 24 [5.905129] [drm]pitch is 7680 [5.905201] fbcon: radeondrmfb (fb0) is primary device [5.933430] Console: switching to colour frame buffer device 240x67 … [5.983571] radeon :01:00.0: fb0: radeondrmfb frame buffer device [5.996432] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on minor 0 … … [ 36.254301] [ cut here ] [ 36.254305] trying to bind memory to uninitialized GART ! [ 36.254467] WARNING: CPU: 3 PID: 2559 at drivers/gpu/drm/radeon/radeon_gart.c:299 radeon_gart_bind+0xef/0x100 [radeon] [ 36.254469] Modules linked in: zram snd_hda_intel snd_intel_dspcfg snd_usb_audio snd_hda_codec snd_hda_core snd_usbmidi_lib snd_hwdep mc snd_pcm snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi snd_seq edac_mce_amd snd_seq_device
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "dmesg on Linux 5.4.0-48-generic on Ubuntu 20.04, K10 platform, ATI Radeon HD 4670 (truncated because it was weighting 62MB)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430878/+files/dmesg.ubuntu-20.04.linux-5.4.0-48-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
Related and similar issue with PCI graphic cards (not AGP ones): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795 While PCI graphic cards are broken on AMD K8/K10 platform for years (I've reproduced on Linux 4.4, 4.8 and 4.15 from Ubuntu 16.04 Xenial), AGP cards started to break on Ubuntu with 5.4.0-48-generic (was still working with 5.4.0-47-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "dmesg on Linux 5.10.0-051000rc1-generic on Ubuntu 20.04, K10 platform, ATI Radeon HD 4670 AGP" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430875/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "dmesg on Linux 5.9 vanilla on Ubuntu 20.04, K10 platform, ATI Radeon HD 4670 AGP" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430874/+files/dmesg.ubuntu-20.04.linux-5.9-vanilla_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
For some reason I was able to compile v5.4 and v5.5 from torvalds branchs with `make -j$(nproc) deb-pkg` but starting with v5.6 I had to use `make -j$(nproc) bindeb-pkg`, in the end I lacked some modules (like my network driver, that did not helped me) but radeon one was there so tests could have been done. The GNOME desktop opened properly with 5.4, 5.5, 5.6, 5.7 and 5.8. But when v5.9, I just got the desktop (GDM is configured to autologin) restarting again and again, only showing me a mouse cursor before dying. The errors in dmesg were similar to the one I found with PCI devices (not AGP ones!) on the same AMD K8 or K10-based motherboard I reproduce issue with AGP devices. Also, the errors in vanilla 5.9 look to be the same as the one seen in 5.10-rc1 from mainline PPA. Here is a sample of captured dmesg error on vanilla 5.9: ``` [5.242322] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [5.242359] radeon :01:00.0: disabling GPU acceleration … [ 34.558885] [ cut here ] [ 34.558889] trying to bind memory to uninitialized GART ! [ 34.559048] WARNING: CPU: 1 PID: 2516 at drivers/gpu/drm/radeon/radeon_gart.c:299 radeon_gart_bind+0xdf/0xf0 [radeon] [ 34.559050] Modules linked in: zram snd_usb_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core snd_hwdep snd_pcm snd_seq_midi kvm_amd snd_seq_midi_event ccp joydev kvm snd_seq snd_rawmidi input_leds snd_timer snd_seq_device snd soundcore k10temp mac_hid serio_raw binfmt_misc sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear uas usb_storage hid_generic usbhid hid radeon i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm psmouse forcedeth i2c_nforce2 [ 34.559107] CPU: 1 PID: 2516 Comm: gnome-shell Not tainted 5.9.0 #1 [ 34.559109] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AM2NF3-VSTA, BIOS P3.20 10/09/2009 [ 34.559178] RIP: 0010:radeon_gart_bind+0xdf/0xf0 [radeon] [ 34.559184] Code: 00 48 89 ef 48 8b 40 60 e8 0e 2f 44 df 31 c0 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 c7 c7 38 6f 6b c0 e8 23 0c 6d de <0f> 0b b8 ea ff ff ff eb dc 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [ 34.559187] RSP: 0018:c030838f7a28 EFLAGS: 00010282 [ 34.559191] RAX: RBX: a0cf6b88eb80 RCX: 0027 [ 34.559193] RDX: 0027 RSI: 0086 RDI: a0cf6fc98d08 [ 34.559196] RBP: c030838f7b28 R08: a0cf6fc98d00 R09: 0004 [ 34.559198] R10: R11: 0001 R12: c030838f7b28 [ 34.559201] R13: a0cf6a622868 R14: a0cf6c7cc6e8 R15: c030838f7b28 [ 34.559204] FS: 7f46ae245cc0() GS:a0cf6fc8() knlGS: [ 34.559207] CS: 0010 DS: ES: CR0: 80050033 [ 34.559210] CR2: 56494261c1c8 CR3: 00040bfe6000 CR4: 06e0 [ 34.559212] Call Trace: [ 34.559286] radeon_ttm_backend_bind+0x58/0x210 [radeon] [ 34.559305] ttm_tt_bind+0x32/0x60 [ttm] [ 34.559321] ttm_bo_handle_move_mem+0x236/0x590 [ttm] [ 34.559339] ttm_bo_validate+0x16c/0x180 [ttm] [ 34.559407] ? drm_ioctl_kernel+0xe9/0xf0 [drm] [ 34.559422] ttm_bo_init_reserved+0x2ae/0x320 [ttm] [ 34.559438] ttm_bo_init+0x6d/0xf0 [ttm] [ 34.559504] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 34.559569] radeon_bo_create+0x184/0x210 [radeon] [ 34.559634] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 34.559703] radeon_gem_object_create+0xa9/0x180 [radeon] [ 34.559773] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.559840] radeon_gem_create_ioctl+0x66/0x120 [radeon] [ 34.559850] ? tomoyo_path_number_perm+0x66/0x1d0 [ 34.559918] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.559968] drm_ioctl_kernel+0xaa/0xf0 [drm] [ 34.560021] drm_ioctl+0x1ec/0x390 [drm] [ 34.560090] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.560152] radeon_drm_ioctl+0x49/0x80 [radeon] [ 34.560160] __x64_sys_ioctl+0x83/0xb0 [ 34.560167] do_syscall_64+0x33/0x80 [ 34.560174] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 34.560179] RIP: 0033:0x7f46b369550b [ 34.560183] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 34.560186] RSP: 002b:7ffdb7421658 EFLAGS: 0246 ORIG_RAX: 0010 [ 34.560189] RAX: ffda RBX: 7ffdb74216d0 RCX: 7f46b369550b [ 34.560192] RDX: 7ffdb74216d0 RSI: c020645d RDI: 000e [ 34.560194] RBP: c020645d R08: 0011 R09: 0005 [ 34.560197] R10: 56494245c010 R11: 0246 R12:
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
** 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/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** 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/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
** Summary changed: - PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) + PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
Here may be the interesting dmesg part when running the ATI Radeon 4350 PCI card on the K10 AGP host with Ubuntu 20.04 Focal and Linux 5.10-rc1 kernel. Note that those messages repeats infinitely and very quickly in a way the whole journal becomes full rapidly (dropping earlier entries): ``` [ 46.802991] trying to bind memory to uninitialized GART ! [ 46.803170] WARNING: CPU: 2 PID: 2610 at drivers/gpu/drm/radeon/radeon_gart.c:297 radeon_gart_bind+0xf1/0x100 [radeon] [ 46.803173] Modules linked in: zram snd_hda_codec_hdmi binfmt_misc snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep edac_mce_amd mc snd_seq_midi snd_pcm snd_seq_midi_event snd_rawmidi snd_seq joydev snd_seq_device snd_timer input_leds kvm_amd snd ccp soundcore kvm k10temp serio_raw mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear radeon i2c_algo_bit ttm drm_kms_helper syscopyarea hid_generic sysfillrect sysimgblt fb_sys_fops uas usbhid cec usb_storage hid rc_core psmouse drm forcedeth i2c_nforce2 [ 46.803296] CPU: 2 PID: 2610 Comm: gnome-shell Not tainted 5.10.0-051000rc1-generic #202010291359 [ 46.803300] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AM2NF3-VSTA, BIOS P3.20 10/09/2009 [ 46.803376] RIP: 0010:radeon_gart_bind+0xf1/0x100 [radeon] [ 46.803383] Code: 00 4c 89 e7 48 8b 40 60 e8 7c 53 3b cd 31 c0 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 c7 c7 48 1a 75 c0 e8 65 90 f6 cc <0f> 0b b8 ea ff ff ff eb dc 66 0f 1f 44 00 00 0f 1f 44 00 00 55 48 [ 46.803387] RSP: 0018:b0da81f57a38 EFLAGS: 00010282 [ 46.803393] RAX: RBX: 98801231c6e8 RCX: 98832fd18988 [ 46.803396] RDX: ffd8 RSI: 0027 RDI: 98832fd18980 [ 46.803400] RBP: b0da81f57a70 R08: R09: b0da81f57818 [ 46.803403] R10: b0da81f57810 R11: 8e752ca8 R12: 988007a4f580 [ 46.803406] R13: b0da81f57b08 R14: 988011b19200 R15: 98801231c6e8 [ 46.803411] FS: 7f6e1d3dbcc0() GS:98832fd0() knlGS: [ 46.803415] CS: 0010 DS: ES: CR0: 80050033 [ 46.803418] CR2: 55b0490a78f8 CR3: 000106534000 CR4: 06e0 [ 46.803421] Call Trace: [ 46.803501] radeon_ttm_tt_bind+0x7e/0x110 [radeon] [ 46.803519] ttm_bo_handle_move_mem+0x484/0x4a0 [ttm] [ 46.803534] ttm_bo_validate+0x137/0x150 [ttm] [ 46.803552] ttm_bo_init_reserved+0x29f/0x320 [ttm] [ 46.803567] ttm_bo_init+0x69/0xe0 [ttm] [ 46.803639] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 46.803712] radeon_bo_create+0x186/0x200 [radeon] [ 46.803784] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 46.803859] radeon_gem_object_create+0xad/0x190 [radeon] [ 46.803934] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon] [ 46.804090] radeon_gem_create_ioctl+0x69/0x120 [radeon] [ 46.804182] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon] [ 46.804279] drm_ioctl_kernel+0xae/0xf0 [drm] [ 46.804353] drm_ioctl+0x245/0x400 [drm] [ 46.804435] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon] [ 46.804452] ? usb_hcd_irq+0x2c/0x40 [ 46.804521] radeon_drm_ioctl+0x4e/0x80 [radeon] [ 46.804530] __x64_sys_ioctl+0x91/0xc0 [ 46.804537] do_syscall_64+0x38/0x90 [ 46.804546] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ``` I don't see wrong things in dmesg when running the 4.8 kernel on Xenial (while experiencing the same bugs), or they are not obviously wrong enough for me to notice them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
I've added a screenshot (screen photo) of the GNOME desktop being stuck and unresponsive while running the ATI Radeon 4350 PCI on the K8 AGP host. You'll notice this is the exact same symptom I get with ATI Radeon AGP cards on this host starting with kernel 5.4.0-48-generic and later (while that AGP card worked flawlessly on 5.4.0-47-generic), see #1899304 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304 On the K8 PCie host, the display goes off immediately at kernel launch, right after GRUB launches it, so there is absolutely nothing to see. If I'm right, the lockup is so hard the system does not run in background and I cannot connect through SSH (right, this is the same symptom I get with the Nvidia PCI card). I don't have access to recent enough (GL 3) Nvidia AGP cards to compare symptoms with that GL 3 Nvidia PCI card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
** Attachment added: "Screenshot of GNOME desktop frozen on ATI Radeon HD 4350 PCI on K8 AGP host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430844/+files/20201103-001858-000.ati-radeon-hd4350pci+k8.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
I added two screenshots (screen photos) of graphical glitches taken while running the Nvidia Geforce 8400GS rev.2 PCI on K8 AGP and K10 AGP hosts. That's the last thing an user can see (it remains on screen), the desktop never displays. In those case I get dmesg logs through SSH. On the K8 PCie host, the display goes off immediately at kernel launch, right after GRUB launches it, so there is absolutely nothing to see. If I'm right, the lockup is so hard the system does not run in background and I cannot connect through SSH. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS rev.2 PCI on K8 AGP host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430842/+files/20201103-002441-000.nvidia-geforce-8400gsr2-pci+k8.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS rev.2 PCI on K10 AGP host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430843/+files/20201102-174932-000.nvidia-geforce-8400gsr2-pci+k10.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
The interesting thing on Nvidia GS 8400GS rev.2 may be: [ 20.107995] nouveau :03:00.0: DRM: GPU lockup - switching to software fbcon [ 20.180130] nouveau :03:00.0: [drm] fb0: nouveaudrmfb frame buffer device [ 20.195263] [drm] Initialized nouveau 1.3.1 20120801 for :03:00.0 on minor 0 You'll find the same lines in 4.8 (Xenial) and 5.10-rc1 (Focal) dmesg, either on K8 (the one with AGP port) and K10 (which also has AGP port). I forgot to say I also tested this configuration and then, reproduced the bug for both Nvidia and ATI PCI cards: Ubuntu 20.04 Focal LTS Linux 5.10.0-051000rc1-generic (from mainline Ubuntu PPA). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
** Attachment added: "dmesg on Linux 5.10-rc1 on Ubuntu 20.04, K10 platform, Nvidia Geforce 8400GS rev.2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430839/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_Nvidia-Geforce-8400GSr2-PCI.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
** Attachment added: "dmesg on Linux 5.10-rc1 on Ubuntu 20.04, K10 platform, ATI Radeon HD 4350 PCI" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430838/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4350-PCI.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
** Attachment added: "dmesg on Linux 4.8.0-36 on Ubuntu 16.04, K8 platform, Nvidia Geforce 8400GS rev.2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430841/+files/dmesg.ubuntu-16.04.linux-4.8.0-36-generic_MSI-MS-6702E+K8_Nvidia-Geforce-8400GSr2-PCI.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
** Attachment added: "dmesg on Linux 4.8.0-36 on Ubuntu 16.04, K8 platform, ATI Radeon HD 4350 PCI" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5430840/+files/dmesg.ubuntu-16.04.linux-4.8.0-36-generic_MSI-MS-6702E+K8_ATI-Radeon-HD-4350-PCI.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
Hmm, minor issues in the host list, fixed: - K10 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU (quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI - K8 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU (dual core), Intel 82801 PCI Bridge, 1GB DDR3 1066MHz, PCIe + PCI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] [NEW] PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel)
Public bug reported: This is an issue I found while investigating #1899304 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304 The big concern is that if AGP is disabled, there is no fallback display option on those platforms. After having discovered some K8 and K10 computers running AGP cards stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to try some PCI cards to know if problems came from AGP or something else, and I've discovered another issue instead. Note that I'm not talking about PCI express, but good old PCI. The other issue I found is that PCI graphics on AMD K8/K10 platform is broken since years. This got probably unnoticed because such hardware works on Intel platform and those cards are not very common, so the chance to fulfill all the requirements to reproduce the bug are not that high. To make the test significant enough I used two PCI devices from two makers, and some that are not so old: they both support OpenGL 3.3, have 512MB of VRAM, and one of them even have HDMI. - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA I've driven tests on four computers: - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU (quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU (dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI Both PCI GPU work on the Intel based computer, and I get performances that looks correct for those GPU given they are PCI ones. You can find real-life use case test result here (look for “PCI”): https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix I tested two Ubuntu versions and multiple kernels: Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic All those configurations fail with those two PCI GPUs on AMD K8/K10 platforms. I got some logs and screenshots, so I will add them. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics seems to be broken since years on AMD K8/K10 platform (work on Intel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
I built the v5.5.0 version from torvalds's branch and it works. So, if it does not work on Ubuntu's 5.4.0-48 I can assume it's was broken by some Ubuntu custom patch or some backports, making it harder for me to identify what may have introduced the regression. I'll try to find the vanilla version that started to fail anyway, that will be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
Hi, thank you for your answer and your attention, This issue is confirmed again. 1. 5.10.0-rc1 does not fix the problem introduced in 5.4.0-48 regarding ATI/AMD AGP GPU. 2. PCI GPUs are broken on AMD K8/K10 platform since years but they work on Intel platform, GPU being ATI/AMD or Nvidia doesn't make a difference, so there is no display fallback if AGP is disabled. 3. Present issue not only reports graphical performance regression, but global performance regression on the computers as a whole: slow disk IO, audio glitches… Because the commit you talked about seems to be related to Radeon and AGP and I've experienced bugs with PCI nVidia hardware too, I've done more testing. I previously reported issues with the PCI Nvidia GeForce 8400 GS rev.2 on 5.4.0-48 kernel, but at the time I did not tried if this one worked on 5.40.0-47 on this host computer. This is now done and in fact, this hardware does not work on this host computer on 4.15.0-118-generic kernel from Ubuntu 16.04 LTS (Xenial), either on 4.8.0-36 and 4.4.0-190 (Xenial). I'm not saying such hardware does not work at all, such hardware works on Intel based computers, they work on Intel-based PCIe computer with Ubuntu 20.04 (I have not tested older). I've tested Nvidia and ATI PCI GPUs on the K8 AGP-based computer, the K10 AGP-based computer, a K8 PCIe based computer, and an Intel based computer. Teh tested PCI ATI GPU is an ATI Radeon HD 4350, a not-so-old GPU (TeraScale generation) with HDMI output. Either ATI or Nvidia, those GPU works on Intel based computer but not in AMD K8 AGP or K10 AGP and even not on K8 PCIe-based computer. So, here is the list of GPU tested: AGP ATI Radeon HD 4670 (RV730 XT, TeraScale 1), HDMI + DVI-I + VGA AGP ATI Radeon X1950 PRO (RV570, R500), DVI-I + DVI-I PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA AGP GPUs worked up to 5.4.0-47 and stopped working with 5.4.0-48, they still does not work on 5.10.0-rc1, I reproduced the issue on 5.10.0-rc1 on both K8 and K10 AGP based computers. I don't have access right now to Intel-based AGP computers to test them. Those are the computers tested: K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU (quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI K10 AGP based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual core), Nvidia C51 host bridge, C51 PCI Express bridge, 6GB DDR2 667MHz, PCIe + PCI K8 PCIe based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU (dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI On all K8 or K10-based computers with AGP, the screen may displays garbage but host can be accessed through SSH, so I got some logs (more to come). So to sum it up: - PCI Graphics are broken in kernel since ages on K8/K10 platform but went probably unnoticed since they work on Intel platform and those GPU are not very commons. - AGP Graphics regressed starting with 5.4.0-48. Because PCI graphics seems to be broken for ages on K8/K10 computers, when AGP is disabled in kernel, there is no fallback available to run a display, at all. On a side note, I'm surprised to hear hardware support like AGP may have been disabled less than six months after the release of an Long Term Support distribution that is expected to be supported for multiple years. Six months is even shorter than the usual support for non-LTS versions. Also, while PCIe was introduced a long time ago (2004?), AGP lived very lately, as demonstrated by this not-so-obsolete machine featuring a quad core CPU with hardware virtualization, 16GB of RAM and a TeraScale (OpenGL 3.3, OpenCL 1.0 capable) GPU with 1GB of VRAM. The motherboard is from 2006, GPU is from 2008, and CPU is from end of the year 2010. It seems to be a bit early to end support for them. This is among the best the market had to offer in 2010. Here can be found some documentation on the hardware: Motherboard: https://www.asrock.com/mb/nvidia/am2nf3-vsta/ GPU: http://www.hisdigital.com/us/product2-448.shtml CPU: https://www.cpu-world.com/CPUs/K10/AMD-Phenom%20II%20X4%20970%20Black%20Edition%20-%20HDZ970FBK4DGM%20(HDZ970FBGMBOX).html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
Here is another photo of display glitch happening when the computer hangs. I got it with both the Radeon X1950 and the Radeon HD 4670. What happens it at startup, the GNOME Shell desktop makes an animation, expanding itself from the center of the screen. In such screenshot, we see the computer hang before the full size of the screen is reached (blues square is the frame of the screen). ** Attachment added: "Screen photo of GNOME Shell hanging on Linux 5.4.0-52 with ATI Radeon HD 4670 AGP" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5429842/+files/20201027-215858-000.gnome-shell-hang-on-ati-radeon-hd4670-agp.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
I reproduce the bug on another computer, using 5.4.0-52-generic kernel: Motherboard: Asrock AM2NF3 VSTA CPU: AMD Phenom II X4 970 (Quad core) RAM: 16GB DDR2 800MHz (4×4 GB) GPU: ATI Radeon HD 4670 AGP VRAM: 1GB DDR3 Of course the same computer works flawlessly with 5.4.0-47-generic kernel. I noticed that if I plug a Radeon 9250 instead of the Radeon HD 4670, the desktop uses LLVMpipe software and GNOME manages to start successfully but this is so slow I can see the desktop being drawn. Note that LLVMpipe rendering on that same GPU but on 5.4.0-47-generic kernel is not that slow. When running 5.4.0-53-generic I can see the pixels being painted, that say so much how slow Ubuntu becomes on kernel greater than 5.4.0-47-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
I reproduce the bug with 5.4.0-51-generic and 5.4.0-52-generic. The 5.4.0-47-generic one is the last known kernel to work on that system. ** Summary changed: - Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues + Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
I reproduce the bug with the 5.4.0-49-generic kernel from `proposed` when running the Radeon X1950 PRO. Note: I previously joined a dmesg log file about GPU lockup, such lockup is not always logged but the GNOME Shell session is stuck anytime it is started. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "Screen photo of display garbage on Linux 5.4.0-48 with Nvidia GeForce 8400 GS rev.2 (PCI)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5421058/+files/20201011-231213-000.display-garbage-on-nvidia-geforce-8400gs2-pci.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "Screen photo of GNOME Shell hanging on Linux 5.4.0-48 with ATI Radeon X1950 PRO (AGP)." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5421057/+files/20201011-014117-000.gnome-shell-hang-on-ati-radeon-x1950pro-agp.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
I forgot to say that when I manage to get a non-composited LXDE desktop running on Radeon X1950 PRO, started by hand using `startx`, and I run the Unvanquished game, more than 51% of the CPU time is spent on OpenAL thread, i.e. the audio thread, which is wrong. This thread is usually really lightweight compared to other threads. Also, sound crackling is heard. ** Attachment added: "Orbit profiler screenshot showing abnormally high openal load" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5421056/+files/20201010-115833-000.linux-5.4.0-48-unexpected-openal-high-cpu-load.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Summary changed: - Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable + Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable
** Attachment added: "dmesg on linux 5.4.0-48 and ATI Radeon HD 4670 (AGP) experiencing GPU lockup" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5421055/+files/dmesg.linux-5.4.0-48-generic.ati-radeon-hd4670-agp.gpu-lockup.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable
I tested with another ATI GPU, the Radeon HD 4670 (AGP) one, an high-end TeraScale 1 generation card. The computer did not manage to display the desktop, the dmesg was full of errors about GPU lockup, and I did not managed to reboot properly the computer (had to uses magic SysRq keys). I tested with an Nvidia GPU, the GeForce 8400 GS rev.2 (PCI), a low-end Tesla 1.0 generation card, running nouveau. The computer did not manage to display the desktop (but displayed garbage instead). Though, I noticed nothing relevant in dmesg and could reboot properly from another host through SSH. I entirely reinstalled the 5.4.0-48-generic kernel and modules packages, regenerated initramfs, problem is still there. I noticed that at the time the 5.4.0-48-generic kernel was installed many other packages were upgraded as well (including some related to firmwares and initramfs) so to rules them out I regenerated the 5.4.0-47-generic again, making sure this one is generated against the same files and with the same tools, and I still don't reproduce the bug on 5.4.0-47-generic kernel. So, that looks really kernel related, all the other packages are the same, and when using other kernel, that other kernel runs with exact same files or files generated with exact same tools without reproducing the bug. I also tested the system on another computer but could not reproduce the bug on that other computer. So, it looks like the bug is tied to the 5.4.0-48-generic kernel on that particular hardware. This bug makes Ubuntu 20.04 and this hardware completely unusable once the 5.4.0-48-generic kernel is installed and used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable
I forgot to mention: After switching from the 5.4.0-47-generic kernel to the 5.4.0-48-generic one, it becomes very very slow for the game to load the levels and related assets from filesystem (textures, etc.), so the issue is likely to no be only about graphical performance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable
** Description changed: This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July 2020). There is two kernels available on this system: - 5.4.0-47-generic - 5.4.0-48-generic With kernel 5.4.0-47-generic, - GNOME shell loads properly on Radeon X1950 PRO, - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution. Everything looks consistent with the limits and the age of the hardware. With kernel 5.4.0-48-generic - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen is displayed and keyboard shortcuts does not respond, or the top bar is stuck between the center and the top of the screen and the shell does not respond, or the top bar on the top of the screen but the shell does not respond, to get a desktop I run `sudo systemctl stop display-manager` then `startx /usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone xterm started with startx leads to same issues. - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution. Note: for unknown reasons, GNOME Shell loads properly on the ATI Radeon 9500 but not on the Radeon X1950 PRO. Everything is slow. When the game is running, a very high load is reported by htop, which does not look like the experience seen on the 5.4.0-47-generic kernel. When the game is running cycling between windows using Alt-Tab takes a lot of second while it's immediate on 5.4.0-47-generic kernel. Also, even without the game running or on a lightweight desktop like LXDE, cycling windows is not smooth and window refreshing is slow enough to be noticeable. About the hardware, note that: - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 939), - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale), - there is 3GB of DDR RAM, - - there is no swap, + - there is no on-disk swap but zram-based swap in compressed ram is used, - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 port, - /tmp is a tmpfs ram disk, - CPU is set to performance profile, - the install is not really messy and not many packages are installed, this USB key is purposed for hardware/system testing and to diagnose such issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: illwieckz 7503 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: illwieckz 7503 F pulseaudio CasperMD5CheckResult: skip Date: Sun Oct 11 01:47:48 2020 InstallationDate: Installed on 2020-07-09 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: - enp0s11 no wireless extensions. - - lono wireless extensions. + enp0s11 no wireless extensions. + + lono wireless extensions. MachineType: MSI MS-6702E ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.4.0-48-generic N/A - linux-backports-modules-5.4.0-48-generic N/A - linux-firmware1.187.3 + linux-restricted-modules-5.4.0-48-generic N/A + linux-backports-modules-5.4.0-48-generic N/A + linux-firmware1.187.3 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080011 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-6702E dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-6702E dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Description changed: This system runs Ubuntu
[Bug 1899304] [NEW] Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable
Public bug reported: This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July 2020). There is two kernels available on this system: - 5.4.0-47-generic - 5.4.0-48-generic With kernel 5.4.0-47-generic: - GNOME shell loads properly on Radeon X1950 PRO, - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution. Everything looks consistent with the limits and the age of the hardware. With kernel 5.4.0-48-generic: - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen is displayed and keyboard shortcuts does not respond, or the top bar is stuck between the center and the top of the screen and the shell does not respond, or the top bar on the top of the screen but the shell does not respond, to get a desktop I run `sudo systemctl stop display-manager` then `startx /usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone xterm started with startx leads to same issues. - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution. Note: for unknown reasons, GNOME Shell loads properly on the ATI Radeon 9500 but not on the Radeon X1950 PRO. Everything is slow. When the game is running, a very high load is reported by htop, which does not look like the experience seen on the 5.4.0-47-generic kernel. When the game is running cycling between windows using Alt-Tab takes a lot of second while it's immediate on 5.4.0-47-generic kernel. Also, even without the game running or on a lightweight desktop like LXDE, cycling windows is not smooth and window refreshing is slow enough to be noticeable. About the hardware, note that: - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 939), - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale), - there is 3GB of DDR RAM, - there is no on-disk swap but zram-based swap in compressed ram is used, - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 port, - /tmp is a tmpfs ram disk, - CPU is set to performance profile, - the install is not really messy and not many packages are installed, this USB key is purposed for hardware/system testing and to diagnose such issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: illwieckz 7503 F pulseaudio CasperMD5CheckResult: skip Date: Sun Oct 11 01:47:48 2020 InstallationDate: Installed on 2020-07-09 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp0s11 no wireless extensions. lono wireless extensions. MachineType: MSI MS-6702E ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080011 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-6702E dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-6702E dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Huge performance regression, Unvanquished game goes from 70fps to 7fps, GNOME Shell never finishes to load, GNOME desktop unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic
This bug seems to not affect Ubuntu 20.04 stock kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813509 Title: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1813509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867998] [NEW] GIMP crashed while restarting GNOME Shell
Public bug reported: Bug information provided by GIMP: ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.2.1-9ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) using babl version 0.1.72 (compiled against version 0.1.72) using GEGL version 0.4.18 (compiled against version 0.4.18) using GLib version 2.62.3 (compiled against version 2.62.1) using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Abandon Stack trace: ``` # Stack traces obtained from PID 29995 - Thread 29995 # [New LWP 30002] [New LWP 30003] [New LWP 30004] [New LWP 30005] [New LWP 30007] [New LWP 30008] [New LWP 30009] [New LWP 30010] [New LWP 30011] [New LWP 30012] [New LWP 30013] [New LWP 30049] [New LWP 30058] [New LWP 31231] [New LWP 26911] [New LWP 27030] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __libc_read (nbytes=256, buf=0x7fff5879f8d0, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7faaadebb500 (LWP 29995) "gimp-2.10" __libc_read (nbytes=256, buf=0x7fff5879f8d0, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7faaab8f7700 (LWP 30002) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7faaab0f6700 (LWP 30003) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f8f5700 (LWP 30004) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f0f4700 (LWP 30005) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7faaa98f3700 (LWP 30007) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7faaa3fff700 (LWP 30008) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7faaa90f2700 (LWP 30009) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7faaa37fe700 (LWP 30010) "gmain" 0x7faaad21dc2f in __GI___poll (fds=0x55b46e0234d0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7faaa2ffd700 (LWP 30011) "gdbus" 0x7faaad21dc2f in __GI___poll (fds=0x55b46e0359b0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7faa7c31f700 (LWP 30012) "gimp-2.10" futex_abstimed_wait_cancelable (private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55b46e232748) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 12 Thread 0x7faa6b98d700 (LWP 30013) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7faa57fff700 (LWP 30049) "threaded-ml"0x7faaad21dc2f in __GI___poll (fds=0x7faa50007170, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 14 Thread 0x7faa6b18c700 (LWP 30058) "swap writer"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 15 Thread 0x7faa68e97700 (LWP 31231) "paint" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7faa2cfd7700 (LWP 26911) "pool-gimp-2.10" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 17 Thread 0x7faa25ffb700 (LWP 27030) "pool-gimp-2.10" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 17
[Bug 1838860] Re: convert translates upside down some picture when converting from jpg to tga
Bad news, sometime the converted png from jpg displays properly but is
then set upside-down when converting from png to tga.
I updated the screenshot of the bug:
https://dl.illwieckz.net/b/imagemagick/bugs/convert-jpg-to-tga-upside-down/convert-jpg-to-tga-upside-down.png
And the script to reproduce:
https://dl.illwieckz.net/b/imagemagick/bugs/convert-jpg-to-tga-upside-down/convert-jpg-to-tga-upside-down.sh
Which now looks like this:
for i in *.jpg
do
n="$(basename "${i}" '.jpg')"
convert "${i}" "${n}.png"
convert "${i}" "${n}.tga"
convert "${n}.png" "${n}.png.tga"
done
When I said converting from jpg to png to tga worked, in fact I had only
tested with one file. It's not always true. With the provided
"noships.jpg" file, the bug is carried over the png.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838860
Title:
convert translates upside down some picture when converting from jpg
to tga
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1838860/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838860] [NEW] convert translates upside down some picture when converting from jpg to tga
Public bug reported:
When I convert some jpg image to tga format, the tga image is upside
down.
The bug only appears with some jpg images, not all. I can convert
thousands of jpg images without problems but in some rare images the bug
occurs.
You can find three jpg images that are known to fail there:
https://dl.illwieckz.net/b/imagemagick/bugs/convert-jpg-to-tga-upside-down/convert-jpg-to-tga-upside-down-samples.zip
I also attach to this bug report the smallest sample I have.
If I convert from jpg to png, the png is ok
If I convert from jpg to png then from png to tga, the tga is ok
If I convert from jpg to tga, the tga is upside down
You can reproduce by downloading the samples, then run this code in the
directory containing the samples:
for i in *.jpg
do
n="$(basename "${i}" '.jpg')"
convert "${i}" "${n}.png"
convert "${i}" "${n}.tga"
done
You can have a look of the result there:
https://dl.illwieckz.net/b/imagemagick/bugs/convert-jpg-to-tga-upside-down/convert-jpg-to-tga-upside-down.png
You can also download this script there:
https://dl.illwieckz.net/b/imagemagick/bugs/convert-jpg-to-tga-upside-down/convert-jpg-to-tga-upside-down.sh
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: imagemagick-6.q16 8:6.9.10.14+dfsg-7ubuntu2.2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Aug 4 01:59:00 2019
SourcePackage: imagemagick
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
** Affects: imagemagick (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug disco
** Attachment added: "noships.jpg"
https://bugs.launchpad.net/bugs/1838860/+attachment/5280694/+files/noships.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838860
Title:
convert translates upside down some picture when converting from jpg
to tga
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1838860/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808702] Re: Bubblewrap integration broke user thumbnailers
Hi, I'm getting the exact same problem with my thumbnailer: https://github.com/illwieckz/crunch-thumbnailer After investigations using "G_MESSAGES_DEBUG=all" I discovered the thumbnailer is called by nautilus this way: bwrap --ro-bind /usr /usr --ro-bind /etc/ld.so.cache /etc/ld.so.cache --ro-bind /bin /bin --ro-bind /lib64 /lib64 --ro-bind /lib /lib --ro- bind /sbin /sbin --ro-bind-try /var/cache/fontconfig /var/cache/fontconfig --proc /proc --dev /dev --chdir / --setenv GIO_USE_VFS local --unshare-all --die-with-parent --setenv G_MESSAGES_DEBUG all --bind /tmp/gnome-desktop-thumbnailer-M7A75Z /tmp --ro-bind /home/illwieckz/Mapping/Unvanquished/InterstellarOasis/build/test/map- metro_test.dpkdir/textures/metro/alumb_t.crn /tmp/gnome-desktop-file-to- thumbnail.crn crunch-thumbnailer -s 256 /tmp/gnome-desktop-file-to- thumbnail.crn /tmp/gnome-desktop-thumbnailer.png My thumbnailer is calling the "convert" tool from ImageMagick, but convert is an "alternative": $ readlink /usr/bin/convert /etc/alternatives/convert $ readlink /etc/alternatives/convert /usr/bin/convert-im6.q16 Since "/etc/alternatives" is not bound by bwrap, the thumnailer fails. Any ETA for the fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808702 Title: Bubblewrap integration broke user thumbnailers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835589] [NEW] extracted data is corrupted
Public bug reported: I faced the bug using `msiextract` tool from `msitools` package that relies on `libgcab`. Someone already reported the bug on msitools side, there is reproduceable steps there: https://gitlab.gnome.org/GNOME/msitools/issues/6 They said the bug is in libgcab, it was already reported and upstream seams to be fixed now: https://bugzilla.redhat.com/show_bug.cgi?id=1608301 I see the libgcab package is currently the same in disco and eoan: https://packages.ubuntu.com/search?keywords=libgcab=names=all=all It would be good to get the fix imported into Ubuntu before eoan release, and if possible, backported to disco. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgcab-1.0-0 1.2-2 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 5 23:45:22 2019 SourcePackage: gcab UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 ** Affects: gcab (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835589 Title: extracted data is corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcab/+bug/1835589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic
@paed808 see my comment on that thread, as a dmesg from the faulty kernel would be useful to compare. By the way I would be surprised the bugs are the same because you really use a very far more recent hardware (mine is perhaps four years older than yours), but if the bug is in a shared component it's possible. Note that I'm able to run a 4.20 kernel from liquorix (was the easiest way for me to try out a newer kernel at this point, but I may try an official ubuntu kernel from kernel ppa instead) so it looks like the bug I face is fixed upstream. May be good to backport on official current kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813509 Title: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1813509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
Can you provide a new dmesg output from 4.18 kernel since you discovered you are able to boot on recovery mode? Just dump it somewhere so you can recover it once booted graphically with another kernel. Basically once you are in front of the recovery screen, select the option to enable network, not because of network but because it's known to also mount filesystems in write mode, then select the option to open a root console, then type that: dmesg > /var/log/dmesg.$(uname -r) It will produce a file named like /var/log/dmesg.4.18.0-14-generic Then reboot on a non-faulty kernel and attach this file there, you can delete it from your computer after that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813509] [NEW] [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic
Public bug reported: After updated an old laptop to Ubuntu Cosmic (was running Xenial before) the graphic hangs at startup, nothing is displayed but a grey screen (grub residual), note that the recovery boot option using `nodmodeset` displays a text console and I'm still able to log-in over a serial tty on normal boot so kernel is alive but computer is not usable due to lack graphic support. Computer is a Thinkpad X61 Tablet plugged on an X6 Tablet UltraBase - http://www.thinkwiki.org/wiki/Category:X61_Tablet - http://www.thinkwiki.org/wiki/ThinkPad_X6_Tablet_UltraBase GPU is an Intel GMA X3100 - http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100 Some information: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic # uname -a Linux arwen 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # lspci -vvv -nn -s 00:02.0 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 8b 52 08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 [2.709180] RSP: 0018:c2718067b978 EFLAGS: 00010287 [2.709180] RAX: c27190303000 RBX: 9e5533e87200 RCX: c27190303044 [2.709180] RDX: RSI: 01a8 RDI: 0150 [2.709180] RBP: c2718067b988 R08: 0001 R09: 0002 [2.709180] R10: 0001 R11: 9e5533e87200 R12: 0202 [2.709180] R13: 9e5533e87200 R14: 9e553380ac00 R15: 9e5533ab8000 [2.709180] FS: 7fd9f63c88c0() GS:9e557e40() knlGS: [2.709180] CS: 0010 DS: ES: CR0: 80050033 [2.709180] CR2: 0008 CR3: 34302000 CR4: 06f0 [2.709180] Call Trace: [2.709180] i915_request_alloc+0x24e/0x370 [i915] [2.709180] i915_gem_init+0x26b/0x470 [i915] [2.709180] i915_driver_load+0xab8/0xd80 [i915] [2.709180] ? mutex_lock+0x12/0x30 [2.709180] i915_pci_probe+0x46/0x60 [i915] [2.709180] local_pci_probe+0x46/0x90 [2.709180] pci_device_probe+0x11c/0x1a0 [2.709180] driver_probe_device+0x2e3/0x460 [2.709180] __driver_attach+0xe4/0x110 [2.709180] ? driver_probe_device+0x460/0x460 [2.709180] bus_for_each_dev+0x74/0xb0 [2.709180] ? kmem_cache_alloc_trace+0x1c4/0x1d0 [2.709180] driver_attach+0x1e/0x20 [2.709180] bus_add_driver+0x159/0x230 [2.709180] ? 0xc0474000 [2.709180] driver_register+0x70/0xc0 [2.709180] ? 0xc0474000 [2.709180] __pci_register_driver+0x57/0x60 [2.709180] i915_init+0x55/0x58 [i915] [2.709180] do_one_initcall+0x4a/0x1c4 [2.709180] ? _cond_resched+0x19/0x30 [2.709180] ? kmem_cache_alloc_trace+0xb8/0x1d0 [2.709180] ? do_init_module+0x27/0x220 [2.709180] do_init_module+0x60/0x220 [2.709180] load_module+0x14f4/0x1890 [2.709180] __do_sys_finit_module+0xbd/0x120 [2.709180] ? __do_sys_finit_module+0xbd/0x120 [2.709180] __x64_sys_finit_module+0x1a/0x20 [2.709180] do_syscall_64+0x5a/0x110 [2.709180] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [2.709180] RIP: 0033:0x7fd9f6e4d219 [2.709180] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 47 fc 0c 00 f7 d8 64 89 01 48 [2.709180] RSP: 002b:7ffc11865868 EFLAGS: 0246 ORIG_RAX: 0139 [2.709180] RAX: ffda RBX: 5580d38f98c0 RCX: 7fd9f6e4d219 [2.709180] RDX: RSI: 7fd9f6d31cad RDI: 0012 [2.709180] RBP: 7fd9f6d31cad R08: R09: [2.709180] R10: 0012 R11: 0246 R12: [2.709180] R13: 5580d3913ae0 R14: 0002 R15: 5580d38f98c0 [2.709180] Modules linked in: gpio_ich i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sdhci_pci sysimgblt cqhci ahci psmouse libahci pata_acpi lpc_ich sdhci firewire_ohci firewire_core fb_sys_fops crc_itu_t drm e1000e(+) video [2.709180] CR2: 0008 [6.662940] ---[ end trace f94080e81515a639 ]--- [6.718286] RIP: 0010:gen4_render_ring_flush+0x60/0x110 [i915] You'll notice the `console=tty0 console=ttyS0,9600n8` kernel boot options I added for serial fallback, the hang also occurs without them of course. Removing the `quiet splash` kernel boot options does not help. Note that some people reported slowness with this
[Bug 1392887] Re: serial wacom devices gone after upgrade to utopic/14.10
Thanks littlelion for the workaround, it was broken here too (Thinkpad X61 Tablet) and the .rules file fixed it. After upgrading from Trusty to Utopic, there was no /lib/udev/rules.d/69-xserver-xorg-input-wacom.rules and no /lib/udev/rules.d/69-wacom.rules/wacom.rules at all here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392887 Title: serial wacom devices gone after upgrade to utopic/14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1392887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126143] Re: XQF: Enemy Territory player names garbled
Hi, this bug was fixed upstream: https://github.com/XQF/xqf/issues/55 XQF 1.0.6.1 was released yesterday and is entering Debian unstable, cf. https://tracker.debian.org/pkg/xqf So Ubuntu will probably ship un updated version someday. In fact XQF only filtered ^[0-9] and ^[a-o], not ^[a-z], It seems that players didn't used ^[p-z] before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/126143 Title: XQF: Enemy Territory player names garbled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xqf/+bug/126143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156925] Re: Mouse disabled after selecting server
Hi, you can run xqf with several options like that: xqf --debug=3 or xqf --debug=6 (many things in stdout, probably too much for you) I can't reproduce here (Ubuntu 14.4, XQF 1.0.5-2). An updated version was released yesterday (2014-10-26) : https://github.com/XQF/xqf/releases/tag/xqf-1.0.6.1 This code was dormant since many years and there is many deprecated things in it that can explains what you have experienced. A large cleaning is underway. XQF 1.0.6 is entering Debian unstable: https://tracker.debian.org/pkg/xqf So Ubuntu will probably ship un updated version someday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156925 Title: Mouse disabled after selecting server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xqf/+bug/1156925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737915] Re: projectM starts with a black screen instead of the visualization
Same problem here, ProjectM 2.1.0, Ubuntu 14.04.1 Without the “LC_NUMERIC=C” workaround, projectM displays a black screen. My system’s default is “LC_NUMERIC=fr_FR.UTF-8”, and with this locale ProjectM displays nothing. The fix does not work or was reverted… $ apt-cache show libprojectm2 Package: libprojectm2 Priority: optional Section: universe/libs Installed-Size: 671 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Architecture: amd64 Source: projectm Version: 2.1.0+dfsg-1build2 Replaces: libprojectm-data ( 2.0.1) Depends: projectm-data, ttf-dejavu-core, libc6 (= 2.14), libftgl2 (= 2.1.3~rc5), libgcc1 (= 1:4.1.1), libgl1-mesa-glx | libgl1, libglew1.10 (= 1.10.0), libstdc++6 (= 4.4.0) Filename: pool/universe/p/projectm/libprojectm2_2.1.0+dfsg-1build2_amd64.deb Size: 214622 MD5sum: 208b59f067b76e84be30064e16f583ed SHA1: 3b9f41d829075daff5df3250f9f797269bcc851f SHA256: 3d68a7c2f37125b17114fa26fac927a44e9f81c582a3b7939ef00401dd1f8e61 Description-en: Advanced Milkdrop-compatible music visualization library libprojectm is an iterative music visualization library which uses OpenGL for hardware acceleration. It is compatible with Milkdrop presets. . This package contains the library and essential data needed for the visualization library to work. Description-md5: 25811eb3de3a571679c9894cb51cc24e Homepage: http://projectm.sf.net Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu $ apt-cache show projectm-pulseaudio Package: projectm-pulseaudio Priority: optional Section: universe/sound Installed-Size: 148 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Architecture: amd64 Source: projectm Version: 2.1.0+dfsg-1build2 Depends: pulseaudio, libc6 (= 2.4), libgcc1 (= 1:4.1.1), libprojectm-qt1, libpulse0 (= 1:0.99.1), libqtcore4 (= 4:4.6.1), libqtgui4 (= 4:4.5.3), libstdc++6 (= 4.4.0) Filename: pool/universe/p/projectm/projectm-pulseaudio_2.1.0+dfsg-1build2_amd64.deb Size: 35892 MD5sum: f403d9f7b07e1331401957032bf9fb6c SHA1: 43a5f65a318d6f02a9eb32f45ef1b0f5626a71ad SHA256: a6d71f9b1e6bdc1025f3f2014b6da7ce4d98aa0e9d0a9883b431bb099d7cdca6 Description-fr: module PulseAudio projectM Projectm est une bibliothèque de visualisation de musique interactive qui utilise OpenGL pour l'accélération matérielle. Il est compatible avec les préréglages de Milkdrop. . Ce paquet contient une application pour visualiser les flux de PulseAudio. Description-md5: 44a16c06a84a1f8ddd00695ab96b0946 Homepage: http://projectm.sf.net Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737915 Title: projectM starts with a black screen instead of the visualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/projectm/+bug/737915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772270] Re: initramfs uses bad lvm lvname to mount /
Hum, sorry, I forgot to mention here that I had investigated. It was in fact a bug inside a lilo-compatibility layer in grub (or initramfs-tools, I do not know since the time) when using grub. A lilo- compatibility layer reconfigured encrypted bootdrive management regardless of the kernel boot parameter. Another solution was to configure crypttab with less information so the lilo-compatibility layer failed and and let grub do its job… This is very old but it is probable that the bug is still there in more recent distribtuions. The bug appears only when you are too verbose in crypttab, so the default installation does not seem affected. I will reproduce the test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772270 Title: initramfs uses bad lvm lvname to mount / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/772270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576602] Re: Fancontrol relies on the module load order
To rectify, don't forget to put a space before *and* after the keyword 'pre:' You can test the workaround in this way (adapt with your modules names): Checks that the modules are loaded: root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' ' fam15h_power k10temp it87 Removes all modules: root@ubuntu ~ # modprobe -r it87 k10temp fam15h_power Checks that all modules are unloaded: root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' ' [nothing] Load the module to be loaded first: root@ubuntu ~ # modprobe it87 Checks that it is alone: root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' ' it87 Remove this module: root@ubuntu ~ # modprobe -r it87 Checks that all modules are unloaded: root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' ' [nothing] Load the module to be loaded last: root@ubuntu ~ # modprobe fam15h_power Checks that all the other modules are loaded: root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' ' fam15h_power k10temp it87 You can adapt this workaround to your computer, this is better than blacklisting a module to load it succesfully, otherwise in a few years when you read your code you do not understand what it will mean. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/576602 Title: Fancontrol relies on the module load order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors-3/+bug/576602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576602] Re: Fancontrol relies on the module load order
Same problem here with Ubuntu 13.4 To solve the problem I launch pwmconfig, and search those lines (may differ on your computer) : […] Found the following devices: hwmon0/device is it8721 hwmon1/device is k10temp hwmon2/device is fam15h_power […] Then I write (as root) a config file named /etc/modprobe.d/fancontrol.conf with this content (modules names can differ a little to names given by pwmconfig, use lsmod to find them) : softdep fam15h_power pre:k10temp softdep k10temp pre: it87 Then I rebuild initramfs root@ubuntu # update-initramfs -k all -u […] At boot time, fam15h_power module can't be loaded before k10temp module, and k10temp module can't be loaded before it87 module. It forces module load order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/576602 Title: Fancontrol relies on the module load order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors-3/+bug/576602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054538] [NEW] conflict between two packets name for fonts-bpg-georgian
Public bug reported: Seems fonts-bpg-georgian_0.5a-6ubuntu1_all.deb is a new name for ttf- bpg-georgian- fonts 0.5a-2ubuntu1, but replacement seems not be handle properly (crashed when do-release-upgrade -d, I solved it like this: apt-get remove ttf-bpg-georgian-fonts apt-get install -f apt-get dist-upgrade) _ Preparing to replace fonts-bpg-georgian 0.5a-2ubuntu1 (using .../fonts-bpg-georgian_0.5a-6ubuntu1_all.deb) ... Unpacking replacement fonts-bpg-georgian ... dpkg: error processing /var/cache/apt/archives/fonts-bpg-georgian_0.5a-6ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Elite.ttf', which is also in package ttf-bpg-georgian- fonts 0.5a-2ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) _ apt-cache show fonts-bpg-georgian Package: fonts-bpg-georgian Priority: optional Section: universe/fonts Installed-Size: 579 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian Fonts Task Force pkg-fonts-de...@lists.alioth.debian.org Architecture: all Version: 0.5a-6ubuntu1 Replaces: ttf-bpg-georgian-fonts (= 0.5a-2) Provides: ttf-bpg-georgian-fonts Pre-Depends: dpkg (= 1.15.7.2~) Breaks: ttf-bpg-georgian-fonts (= 0.5a-2) Filename: pool/universe/f/fonts-bpg-georgian/fonts-bpg-georgian_0.5a-6ubuntu1_all.deb Size: 351096 MD5sum: d1827f08b0970309f89c490a7eb9d2bc SHA1: 9da73b67b556fe959843e0877ac3c3f97d420146 SHA256: 7ae3022199a585cd6660172ad2bc6832193549705d6e013a92a34f984c31ea3b Description-en: BPG Georgian fonts This package provides a collection of three Georgian fonts, provided by BPG-InfoTech. Description-md5: ad67e8d83ae24347c088ff5f7f0551f5 Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: edubuntu-desktop-kde, edubuntu-desktop-gnome, ubuntustudio-font-meta Package: fonts-bpg-georgian Status: install ok installed Priority: optional Section: fonts Installed-Size: 27 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: all Version: 0.5a-2ubuntu1 Pre-Depends: dpkg (= 1.15.7.2) Description-en: BPG Georgian fonts This package provides a collection of three Georgian fonts, provided by BPG-InfoTech. Original-Maintainer: Debian Fonts Task Force pkg-fonts-de...@lists.alioth.debian.org _ apt-cache show ttf-bpg-georgian-fonts Package: ttf-bpg-georgian-fonts Priority: optional Section: universe/x11 Installed-Size: 27 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian Fonts Task Force pkg-fonts-de...@lists.alioth.debian.org Architecture: all Source: fonts-bpg-georgian Version: 0.5a-6ubuntu1 Depends: fonts-bpg-georgian Filename: pool/universe/f/fonts-bpg-georgian/ttf-bpg-georgian-fonts_0.5a-6ubuntu1_all.deb Size: 1336 MD5sum: 3be7d407cf456e3e82dd07407bc4ef3c SHA1: 3ee2bb0765378ff500988c501b847c46d619bfbb SHA256: dc48f0085b24884916ca2d53edc593e50bcd028c3e6edb0c53263c5cb6bc0246 Description-en: transitional dummy package This package is a dummy transitional package. It can be safely removed. Description-md5: d022b4cd65360a59d321e029d730c59e Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Package: ttf-bpg-georgian-fonts Status: install ok installed Priority: optional Section: oldlibs Installed-Size: 561 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: all Source: fonts-bpg-georgian Version: 0.5a-2ubuntu1 Depends: fonts-bpg-georgian Description-en: transitional dummy package This package is a dummy transitional package. It can be safely removed. Original-Maintainer: Debian Fonts Task Force pkg-fonts-de...@lists.alioth.debian.org ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-bpg-georgian 0.5a-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sat Sep 22 13:14:59 2012 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: fonts-bpg-georgian UpgradeStatus: Upgraded to quantal on 2012-09-22 (0 days ago) ** Affects: fonts-bpg-georgian (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054538 Title: conflict between two packets name for fonts-bpg-georgian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-bpg-georgian/+bug/1054538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1054538] Re: conflict between two packets name for fonts-bpg-georgian
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054538 Title: conflict between two packets name for fonts-bpg-georgian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-bpg-georgian/+bug/1054538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 630947] Re: rt2500 wifi pcmcia card does kernel oops
: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1GET41WW(1.13):bd10/18/2006:svnIBM:pn2653N4G:pvrNotAvailable:rvnIBM:rn2653N4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2653N4G dmi.product.version: Not Available dmi.sys.vendor: IBM ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/630947 Title: WARNING: at /build/buildd/linux-2.6.35/drivers/pci/pci.c:105 pci_ioremap_bar+0x4f/0x60() Status in “linux” package in Ubuntu: Incomplete Bug description: rt2500 wifi pcmcia card does kernel oops The kernel oops each time I insert this pcmcia wifi card. I have tested it under Lucid and Maverick, and the bug appears on this two versions. I noticed it's a regression because in the past I used this pcmcia wifi card every days with ubuntu without problem. But for a long time I don't have to use it and some ubuntu versions was released. Today I do not have previous versions older than lucid, I can't said which versions introduces the regression. ProblemType: KernelOops DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-19-generic 2.6.35-19.28 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Annotation: Your system might become unstable now and might need to be restarted. AplayDevices: List of PLAYBACK Hardware Devices card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel 82801CA-ICH3] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: illwieckz 1544 F pulseaudio CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'I82801CAICH3'/'Intel 82801CA-ICH3 with AD1881A at irq 11' Mixer name : 'Analog Devices AD1881A' Components : 'AC97a:41445348' Controls : 31 Simple ctrls : 21 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1GHT18WW-1.05' Mixer name : 'ThinkPad EC 1GHT18WW-1.05' Components : '' Controls : 2 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 14 Mono: Playback 4 [29%] [on] Date: Sun Sep 5 17:42:43 2010 Failure: oops HibernationDevice: RESUME=UUID=864bc3a9-da87-490e-a5e4-c1b8ee42a7b3 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100831.2) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 0ace:1211 ZyDAS ZEW 2501 802.11bg Wireless Adapter Bus 001 Device 002: ID 04b3:4481 IBM Corp. Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 2653N4G ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-19-generic root=/dev/mapper/hostname-hostname--disk ro quiet splash RelatedPackageVersions: linux-firmware 1.38 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: WARNING: at /build/buildd/linux-2.6.35/drivers/pci/pci.c:105 pci_ioremap_bar+0x4f/0x60() dmi.bios.date: 10/18/2006 dmi.bios.vendor: IBM dmi.bios.version: 1GET41WW (1.13 ) dmi.board.name: 2653N4G dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1GET41WW(1.13):bd10/18/2006:svnIBM:pn2653N4G:pvrNotAvailable:rvnIBM:rn2653N4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2653N4G dmi.product.version: Not Available dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/630947/+subscriptions -- Thomas DEBESSE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/630947 Title: WARNING: at /build/buildd/linux-2.6.35/drivers/pci/pci.c:105 pci_ioremap_bar+0x4f/0x60() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/630947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772270] [NEW] initramfs uses bad lvm lvname to mount /
Public bug reported:
Binary package hint: initramfs-tools
First symptom : at boot, the message No init found. Try passing init= bootarg.
Boot fails.
I'm upgrading to Natty from Maverick
My configuration :
/dev/sda1 : /boot
/dev/sda5 : an encrypted luks volume containing an LVM physical volume
the volume groupe name is arwen, the logical volume name for / is racine
the device containing rootfs is named /dev/mapper/arwen-racine
hence, my grub menuentry looks like this :
menuentry 'Ubuntu, avec Linux 2.6.38-8-generic' --class ubuntu --class
gnu-linux --class gnu --class os {
recordfail
savedefault
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root
uuiduuid-uuid-uuid-uuid-uuiduuiduuid
linux /vmlinuz-2.6.38-8-generic root=/dev/mapper/arwen-racine ro
quiet splash vt.handoff=7
initrd /initrd.img-2.6.38-8-generic
}
Sometimes, the error is more verbose, I've get yersterday a message which said
the system attempt to mount /dev/mapper/arwen on initramfs' /root, but it's a
mistake, my rootfs is on /dev/mapper/arwen-racine.
The root= kernel argument is correct, but an initramfs script mades a mistake.
From initramfs' shell I've mounted my /boot partition, then create a new
initrd.img hardcoding /dev/mapper/arwen-racine path on the line 91 of
scripts/local, then reboot, then choose my new initramfs from the grub editor…
The boot does'nt complain and I'm writing this bug report from Natty. :)
So, there is a bug in one script into initramfs which troncate the volume group
name of / .
I've not found where.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: initramfs-tools 0.98.8ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Thu Apr 28 12:21:09 2011
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=fr_FR:en
PATH=(custom, user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to natty on 2011-04-21 (6 days ago)
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772270
Title:
initramfs uses bad lvm lvname to mount /
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772270] Re: initramfs use bad lvm lvname to mount /
** Summary changed: - initramfs use bad lvm lvname to mount / + initramfs uses bad lvm lvname to mount / -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772270 Title: initramfs uses bad lvm lvname to mount / -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772270] Re: initramfs uses bad lvm lvname to mount /
For people which encounter same problem, here a detailed howto to
temporarily repare your distro :
# from initramfs'hell :
# mount correctly your rootfs
mount /dev/mapper/vgname-lvname /root
# and the bootfs
mount /dev/sda1 /root/boot
# then chroot into rootfs
chroot /root /bin/bash
# create a clean directory then go into
mkdir /plop; cd plop
# uncompress an initrd
gunzip /boot/initrd.img-2.6.38-8-generic | cpio -idmv
# edit the local script (which mount local file system)
vim scripts/local
# comment the line 91
mount ${roflag} ${FSTYPE:+-t ${FSTYPE} }${ROOTFLAGS} ${ROOT} ${rootmnt}
# then hardcode your device
mount ${roflag} ${FSTYPE:+-t ${FSTYPE} }${ROOTFLAGS}
/dev/mapper/vgname-lvname ${rootmnt}
# close your favorite editor and build a new initramfs
find . | cpio -ov -H newc | gzip /boot/initrd.img-rescue
# add a grub custom entry into /boot/grub/custom.cfg
# coppying an actual entry from /boot/grub/grub.cfg
vim /boot/grub/grub.cfg /boot/grub/custom.cfg
# mine looks like this :
menuentry 'rescue' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root
uuiduuid-uuid-uuid-uuid-uuiduuiduuid
linux /vmlinuz-2.6.38-8-generic root=/dev/mapper/vgname-lvname ro
quiet splash vt.handoff=7
initrd /initrd.img-rescue
}
# then... reboot, and to next boot, choose rescue in grub menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772270
Title:
initramfs uses bad lvm lvname to mount /
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772270] Re: initramfs uses bad lvm lvname to mount /
** Description changed:
Binary package hint: initramfs-tools
First symptom : at boot, the message No init found. Try passing init=
bootarg.
Boot fails.
I'm upgrading to Natty from Maverick
My configuration :
/dev/sda1 : /boot
/dev/sda5 : an encrypted luks volume containing an LVM physical volume
the volume groupe name is arwen, the logical volume name for / is racine
the device containing rootfs is named /dev/mapper/arwen-racine
hence, my grub menuentry looks like this :
menuentry 'Ubuntu, avec Linux 2.6.38-8-generic' --class ubuntu --class
gnu-linux --class gnu --class os {
- recordfail
- savedefault
- set gfxpayload=$linux_gfx_mode
- insmod part_msdos
- insmod ext2
- set root='(hd0,msdos1)'
- search --no-floppy --fs-uuid --set=root
uuiduuid-uuid-uuid-uuid-uuiduuiduuid
- linux /vmlinuz-2.6.38-8-generic root=/dev/mapper/arwen-racine ro
quiet splash vt.handoff=7
- initrd /initrd.img-2.6.38-8-generic
+ recordfail
+ savedefault
+ set gfxpayload=$linux_gfx_mode
+ insmod part_msdos
+ insmod ext2
+ set root='(hd0,msdos1)'
+ search --no-floppy --fs-uuid --set=root uuiduuid-uuid-uuid-uuid-uuiduuiduuid
+ linux/vmlinuz-2.6.38-8-generic root=/dev/mapper/arwen-racine ro
quiet splash vt.handoff=7
+ initrd /initrd.img-2.6.38-8-generic
}
- Sometimes, the error is more verbose, I've get yersterday a message which
said the system attempt to mount /dev/mapper/arwen on initramfs' /root, but
it's a mistake, my rootfs is on /dev/mapper/arwen-racine.
+ Sometimes, the error is more verbose, I've get yesterday a message which said
the system attempt to mount /dev/mapper/arwen on initramfs' /root, but it's a
mistake, my rootfs is on /dev/mapper/arwen-racine.
The root= kernel argument is correct, but an initramfs script mades a mistake.
From initramfs' shell I've mounted my /boot partition, then create a new
initrd.img hardcoding /dev/mapper/arwen-racine path on the line 91 of
scripts/local, then reboot, then choose my new initramfs from the grub editor…
The boot does'nt complain and I'm writing this bug report from Natty. :)
So, there is a bug in one script into initramfs which troncate the volume
group name of / .
I've not found where.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: initramfs-tools 0.98.8ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Thu Apr 28 12:21:09 2011
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
PackageArchitecture: all
ProcEnviron:
- LANGUAGE=fr_FR:en
- PATH=(custom, user)
- LANG=fr_FR.UTF-8
- SHELL=/bin/bash
+ LANGUAGE=fr_FR:en
+ PATH=(custom, user)
+ LANG=fr_FR.UTF-8
+ SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to natty on 2011-04-21 (6 days ago)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772270
Title:
initramfs uses bad lvm lvname to mount /
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 630947] [NEW] rt2500 wifi pcmcia card does kernel oops
Public bug reported: The kernel oops each time I insert this pcmcia wifi card. I have tested it under Lucid and Maverick, and the bug appears on this two versions. I noticed it's a regression because in the past I used this pcmcia wifi card every days with ubuntu without problem. But for a long time I don't have to use it and some ubuntu versions was released. Today I do not have previous versions older than lucid, I can't said which versions introduces the regression. ProblemType: KernelOops DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-19-generic 2.6.35-19.28 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Annotation: Your system might become unstable now and might need to be restarted. AplayDevices: List of PLAYBACK Hardware Devices card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel 82801CA-ICH3] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: illwieckz 1544 F pulseaudio CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'I82801CAICH3'/'Intel 82801CA-ICH3 with AD1881A at irq 11' Mixer name : 'Analog Devices AD1881A' Components : 'AC97a:41445348' Controls : 31 Simple ctrls : 21 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1GHT18WW-1.05' Mixer name : 'ThinkPad EC 1GHT18WW-1.05' Components : '' Controls : 2 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 14 Mono: Playback 4 [29%] [on] Date: Sun Sep 5 17:42:43 2010 Failure: oops HibernationDevice: RESUME=UUID=864bc3a9-da87-490e-a5e4-c1b8ee42a7b3 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100831.2) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 0ace:1211 ZyDAS ZEW 2501 802.11bg Wireless Adapter Bus 001 Device 002: ID 04b3:4481 IBM Corp. Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 2653N4G ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-19-generic root=/dev/mapper/hostname-hostname--disk ro quiet splash RelatedPackageVersions: linux-firmware 1.38 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: WARNING: at /build/buildd/linux-2.6.35/drivers/pci/pci.c:105 pci_ioremap_bar+0x4f/0x60() dmi.bios.date: 10/18/2006 dmi.bios.vendor: IBM dmi.bios.version: 1GET41WW (1.13 ) dmi.board.name: 2653N4G dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1GET41WW(1.13):bd10/18/2006:svnIBM:pn2653N4G:pvrNotAvailable:rvnIBM:rn2653N4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2653N4G dmi.product.version: Not Available dmi.sys.vendor: IBM ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-net kernel-oops maverick needs-upstream-testing regression-potential -- rt2500 wifi pcmcia card does kernel oops https://bugs.launchpad.net/bugs/630947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 630947] Re: rt2500 wifi pcmcia card does kernel oops
** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546594/+files/AcpiTables.txt ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546595/+files/AlsaDevices.txt ** Attachment added: ArecordDevices.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546596/+files/ArecordDevices.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546597/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546598/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546599/+files/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546600/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546601/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546602/+files/Dependencies.txt ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546603/+files/IwConfig.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546604/+files/Lspci.txt ** Attachment added: OopsText.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546605/+files/OopsText.txt ** Attachment added: PccardctlIdent.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546606/+files/PccardctlIdent.txt ** Attachment added: PccardctlStatus.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546607/+files/PccardctlStatus.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546608/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546609/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546610/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546612/+files/ProcModules.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546616/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546619/+files/UdevLog.txt ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/630947/+attachment/1546621/+files/WifiSyslog.txt -- rt2500 wifi pcmcia card does kernel oops https://bugs.launchpad.net/bugs/630947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459940] Re: A few Gnome applications do not start (Could not load classifier cascade)
installing LiVES install frei0r too, but ca'nt be installed without frei0r (removing frei0r automatically remove LiVES). We can use totem and kdenlive if we don't install frei0r but we must choose between totem (and so other gnome apps) or LiVES. -- A few Gnome applications do not start (Could not load classifier cascade) https://bugs.launchpad.net/bugs/459940 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 479156] [NEW] gnome-app-install instead of ubuntu-software-center
Public bug reported: Binary package hint: ubuntustudio-menu at the end of /usr/share/ubuntustudio-menu/menus/applications.menu the add/remove software entry is gnome-app-install.desktop instead of ubuntu-software-center.desktop like in /etc/xdg/menus/applications.menu . ProblemType: Bug Architecture: i386 Date: Mon Nov 9 14:19:27 2009 DistroRelease: Ubuntu 9.10 Package: ubuntustudio-menu 0.12ubuntu1 PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: ubuntustudio-menu Uname: Linux 2.6.31-14-generic i686 ** Affects: ubuntustudio-menu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- gnome-app-install instead of ubuntu-software-center https://bugs.launchpad.net/bugs/479156 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 479156] Re: gnome-app-install instead of ubuntu-software-center
** Attachment added: corrected /usr/share/ubuntustudio-menu/menus/applications.menu http://launchpadlibrarian.net/35419448/applications.menu ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35419449/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/35419450/XsessionErrors.txt -- gnome-app-install instead of ubuntu-software-center https://bugs.launchpad.net/bugs/479156 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459940] Re: A few Gnome applications do not start (Could not load classifier cascade)
seems to appear when installing frei0r-plugins (example: for kdenlive). When removing frei0r-plugins from my karmic I've no error messages at all, and totem (and other apps) runs fine. -- A few Gnome applications do not start (Could not load classifier cascade) https://bugs.launchpad.net/bugs/459940 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
