[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #846492 (http://bugs.debian.org/846492) # Bug title: vblank wait timed out on crtc error from linux-image-4.8.0-1 # * https://bugs.freedesktop.org/show_bug.cgi?id=93782 # * remote status changed: REOPENED -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 846492 + fixed-upstream usertags 846492 - status-REOPENED usertags 846492 + status-RESOLVED resolution-FIXED thanks
Processed: [bts-link] source package src:linux
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:linux > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #846492 (http://bugs.debian.org/846492) > # Bug title: vblank wait timed out on crtc error from linux-image-4.8.0-1 > # * https://bugs.freedesktop.org/show_bug.cgi?id=93782 > # * remote status changed: REOPENED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 846492 + fixed-upstream Bug #846492 [src:linux] vblank wait timed out on crtc error from linux-image-4.8.0-1 Added tag(s) fixed-upstream. > usertags 846492 - status-REOPENED Usertags were: status-REOPENED. Usertags are now: . > usertags 846492 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 846492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 920547 in 4.18.20-2
Processing commands for cont...@bugs.debian.org: > found 920547 4.18.20-2 Bug #920547 [src:linux] Crashes every few hours Marked as found in versions linux/4.18.20-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 920547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920547: Crashes every few hours
Hi Ben, On Mon, Jan 28, 2019 at 12:42:37AM +, Ben Hutchings wrote: > On Sat, 26 Jan 2019 20:03:49 + Toni wrote: > > Package: src:linux > > Version: 4.19.16-1 > > Severity: critical > > File: linux-image-4.19.0-2-amd64 > > Is this a new problem with version 4.19.16-1? Or did it happen with > earlier versions as well? it happened with the 4.18.* kernel as well. The machine came with Ubuntu and 4.13 preinstalled, but I wiped it as soon as I could and installed Debian. So I don't know if it would have worked with Ubuntu - the entire setup was not suitable for my purposes, but I thought that 4.9 might be too old for this hardware. However, the machine came with a 1.3 BIOS, which I updated to 1.6 and then to 1.7. I think, I had 4.18 together with 1.6 running, but closed the corresponding bug report when I noticed that both a newer kernel and a newer BIOS were available. Well, the situation compared has improved a little, compared to that, but it is still very bad. > When you say "data loss", are you talking about data in memory or > corruption of files that were saved and sync'd to disk? I mean, files on disk were destroyed. I noticed some because I use etckeeper with git, and suddenly, I could no longer see my update history because files in /etc/.git were corrupt to the point that no "git fsck" or "git gc" could resurrect the tree. > On x86 laptops thermal management is (by default) done by the system > firmware (BIOS and management engine code). If you didn't override > that, and yet the CPU overheats, this is the manufacturer's fault. Ok... In the BIOS, I set the corresponding parameter from "performance" to "normal", which I hoped would be a more conservative setting, to prevent exactly this problem. Cheers, Toni
Processed: Re: Bug#911023: memory leak in the backlight control of the dell-laptop module
Processing control commands: > close -1 4.19.16-1 Bug #911023 [src:linux] memory leak in the backlight control of the dell-laptop module Marked as fixed in versions linux/4.19.16-1. Bug #911023 [src:linux] memory leak in the backlight control of the dell-laptop module Marked Bug as done -- 911023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911023: memory leak in the backlight control of the dell-laptop module
Control: close -1 4.19.16-1 On Oct 16, Gabriele Mazzotta wrote: > there are a couple of commits queued for 4.19 that fix some memory > leaks: https://patchwork.kernel.org/patch/10594683/ and > https://patchwork.kernel.org/patch/10594681/. Looking at the call > trace I'd say the first patch is going to fix your issue. Confirmed, thank you. -- ciao, Marco signature.asc Description: PGP signature
Bug#920547: Crashes every few hours
On Sun, 27 Jan 2019 15:10:39 -0500 Chris Manougian wrote: > Hi Toni. I have an XPS 15 9570, which, I think, is basically the same > machine, except yours uses an NVIDIA Quadro vs my GeForce GTX 1050Ti as a > 2nd graphics card. > > A lot of problems with that secondary graphics card and linux. Are you > attempting to use it via Bumblebee? > > See this thread (and links within the thread) - BIOS related: > https://bugzilla.redhat.com/show_bug.cgi?id=1610727 > > I did my best to disable the NVIDIA card: > https://wiki.archlinux.org/index.php/Dell_XPS_15_9570 > > One of my more recent "important" gnome-logs file is: > > 03:16:35 kernel: ath10k_pci :3b:00.0: firmware: failed to load > ath10k/cal-pci-:3b:00.0.bin (-2) > 03:16:35 kernel: firmware_class: See https://wiki.debian.org/Firmware for > information about missing firmware > 03:16:35 kernel: ath10k_pci :3b:00.0: firmware: failed to load > ath10k/pre-cal-pci-:3b:00.0.bin (-2) > 03:16:34 kernel: iTCO_wdt iTCO_wdt: can't request region for resource [mem > 0x00c5fffc-0x00c5] > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS10._PLD], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS10._UPC], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS09._PLD], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS09._UPC], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating > [\_SB.PCI0.XHC.RHUB.SS08._PLD], AE_ALREADY_EXISTS (20180531/dswload2-316) > 03:16:34 kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable > (20180531/psloop-542) > 03:16:34 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20180531/psobject-221) > 03:16:34 kernel: ACPI BIOS Error (bug): Failure creating Hi, If it may help (I'm on testing w/ 4.9.12) this bug seems to be NVidia-specific. Never encountered such things on my laptop which has an AMD GPU with the FOSS driver. Reference is Dell Latitude e6540. Rgds,
