Bug#885570: Duplicate of 884061 ?
Hi, I got the same issue on my i915 notebook (Dell E7450) and I had to boot on previous kernel (linux-image-4.9.0-3-amd64) This bug report seems the same and suggest a tested revert on commit 7de694782cbe7840f2c0de6f1e70f41fc1b8b6e8 : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884061 Thanks, Adrien
Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c
On 25/12/17 23:09, Ben Hutchings wrote: > On Sat, 2017-12-23 at 12:42 +, Chris Boot wrote: >> Severity: serious >> Justification: kernel panic >> >> I experimented a little and disabled cgroupv2 on that server. Because I >> had some issues during boot I attempted to enable >> NetworkManager-wait-online.service using systemd, but that instantly >> resulted in the following kernel panic: > [...] >> I don't know that this is the same bug at all, but I'm keeping it on >> this report for now as it seems at least related somehow. > > The log messages don't look even slightly related, so please move this > to a separate bug report. I'm still not so certain - both sets of stack dumps fall somewhere within cgroup space, and disabling systemd's cgroup accounting (not enabled by default) avoids these conditions. I like to run this system with the following all enabled in /etc/systemd/system.conf: DefaultCPUAccounting=yes DefaultIOAccounting=yes DefaultBlockIOAccounting=yes DefaultMemoryAccounting=yes These are useful for tools like systemd-cgtop for example. With cgroupv2, I can avoid the error by disabling DefaultMemoryAccounting. I was running for nearly 48 hours with this configuration before rebooting to try without cgroupv2. Without cgroupv2, it's DefaultCPUAccounting I need to disable to avoid the panics when I run 'systemd daemon-reload'. I have yet to run into the warning or OOM killer with memory accounting enabled but I'll let you know if it happens. What makes me suspicious that these are related is that neither happens with a 4.13 kernel, but I get both of these cgroup-related problems with 4.14. I wouldn't mind trying to bisect this, but I haven't done that for many years. Is there a nice way to do this with the Debian packaging or am I better off seeing if I can reproduce with vanilla upstream kernels and bisecting that? Or shall I give 4.15~rc5 from experimental a whirl instead? Thanks, Chris -- Chris Boot bo...@debian.org
Bug#878018: [solved]linux-image-4.9.0-3-amd64: Sound broken with snd_fm801
Great, sound was still broken with 4.9.0-3 (4.9.30-2+deb9u5) but works again properly now with linux-image-4.9.0-4-amd64 (4.9.65-3+deb9u1). Thanks!! Michael
Bug#885846: Recurring Atheros Driver Crash
Package: firmware-atheros Version: 20170823-1 The firmware crashes every now and then with following traceback in dmesg: [ 3686.668988] wlp2s0: AP 4c:f9:5d:50:15:34 changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) [ 3686.704719] ath10k_pci :02:00.0: firmware crashed! (guid n/a) [ 3686.704756] ath10k_pci :02:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 11ad:08a6 [ 3686.704766] ath10k_pci :02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [ 3686.706206] ath10k_pci :02:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7 [ 3686.706938] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a [ 3686.706952] ath10k_pci :02:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 3686.708975] ath10k_pci :02:00.0: firmware register dump: [ 3686.708993] ath10k_pci :02:00.0: [00]: 0x05020001 0x15B3 0x00985B3A 0x00955B31 [ 3686.709004] ath10k_pci :02:00.0: [04]: 0x00985B3A 0x00060730 0x0004 0x [ 3686.709013] ath10k_pci :02:00.0: [08]: 0x00955A00 0x00438830 0x00450888 0x00420970 [ 3686.709021] ath10k_pci :02:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6 [ 3686.709030] ath10k_pci :02:00.0: [16]: 0x00952CC4 0x0091080D 0x 0x0091080D [ 3686.709039] ath10k_pci :02:00.0: [20]: 0x40985B3A 0x0040E788 0x0040 0x00421888 [ 3686.709049] ath10k_pci :02:00.0: [24]: 0x809BF546 0x0040E7E8 0x00426470 0xC0985B3A [ 3686.709059] ath10k_pci :02:00.0: [28]: 0x809B90D8 0x0040E958 0x0018 0x0042EA0C [ 3686.709074] ath10k_pci :02:00.0: [32]: 0x809B859A 0x0040E9A8 0x0040E9CC 0x00428D74 [ 3686.709082] ath10k_pci :02:00.0: [36]: 0x8091D252 0x0040E9C8 0x 0x0001 [ 3686.709089] ath10k_pci :02:00.0: [40]: 0x809EDD7B 0x0040EA78 0x00437544 0x00429428 [ 3686.709096] ath10k_pci :02:00.0: [44]: 0x809EB6A6 0x0040EA98 0x00437544 0x0001 [ 3686.709103] ath10k_pci :02:00.0: [48]: 0x80911210 0x0040EAE8 0x0010 0x004041D0 [ 3686.709111] ath10k_pci :02:00.0: [52]: 0x80911154 0x0040EB28 0x0040 0x [ 3686.709118] ath10k_pci :02:00.0: [56]: 0x8091122D 0x0040EB48 0x 0x00400600 [ 3686.709125] ath10k_pci :02:00.0: Copy Engine register dump: [ 3686.709143] ath10k_pci :02:00.0: [00]: 0x00034400 5 5 3 3 [ 3686.709159] ath10k_pci :02:00.0: [01]: 0x00034800 21 21 322 323 [ 3686.709175] ath10k_pci :02:00.0: [02]: 0x00034c00 47 47 110 111 [ 3686.709191] ath10k_pci :02:00.0: [03]: 0x00035000 17 17 18 17 [ 3686.709208] ath10k_pci :02:00.0: [04]: 0x00035400 3703 3703 125 61 [ 3686.709224] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 0 0 [ 3686.709239] ath10k_pci :02:00.0: [06]: 0x00035c00 28 28 28 28 [ 3686.709252] ath10k_pci :02:00.0: [07]: 0x00036000 1 1 1 1 [ 3686.729788] ieee80211 phy0: Hardware restart was requested [ 3687.423884] ath10k_pci :02:00.0: device successfully recovered The hardware from `lspci -vnn` is 02:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Subsystem: Lite-On Communications Inc QCA9377 802.11ac Wireless Network Adapter [11ad:08a6]
Processed: Re: Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter
Processing control commands: > tags -1 + pending confirmed Bug #885348 [src:linux] Latest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter Added tag(s) pending and confirmed. -- 885348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter
Control: tags -1 + pending confirmed
Hi Timo,
On Wed, Dec 27, 2017 at 03:07:36AM +0100, Timo van Roermund wrote:
> Hi Salvatore,
>
>
> On 26-12-2017 16:37, Salvatore Bonaccorso wrote:
> > Hi Timo,
> >
> > On Tue, Dec 26, 2017 at 03:38:24PM +0100, T.A. van Roermund wrote:
> > > Package: src:linux
> > > Version: 4.14.7-1
> > > Severity: critical
> > > Tags: patch upstream
> > > Justification: breaks the whole system
> > >
> > > Dear Maintainer,
> > >
> > > This morning, I updated the Linux kernel from linux-image-4.13.0-1-amd64
> > > to linux-image-4.14.0-2-amd64.
> > > Afterwards, my Intel Gigabit adapter (details below) did not work
> > > properly anymore (no link).
> > > When booting back into the previous kernel (4.13), everything works
> > > properly again.
> > >
> > > It seems like others experience the same behavior, see:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=198047
> > >
> > > According to that thread, this bug was introduced in v4.14.3 through
> > > commit 830466993daf09adbd179e4c74db07279a088f8c
> > > ("e1000e: Separate signaling for link check/link up", upstream:
> > > 19110cfbb34d4af0cdfe14cd243f3b09dc95b013).
> > >
> > > The thread also includes a patch that (apparently) fixes the problem:
> > > https://bugzilla.kernel.org/attachment.cgi?id=261183=diff==1=raw
> > >
> > > Could you please apply this patch to the Debian kernel, until it is
> > > included in upstream?
> > Sorry to hear that. Would it be possible for you to confirm that the
> > patch fixes your issue, following:
> >
> > https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2
> >
> > Regards,
> > Salvatore
>
> I followed these instructions to build a patched kernel:
> Linux 4.14.0-2-amd64 #1 SMP Debian 4.14.7-1a~test (2017-12-27) x86_64
> GNU/Linux
>
> With this kernel, the link of my Intel Gigabit adapter comes up again and
> works normally.
>
> So yes, I can hereby confirm that the patch fixes my issue.
FTR, and sorry for the delay: The change is pending por the next
upload.
https://anonscm.debian.org/cgit/kernel/linux.git/commit/?h=sid=6a221d27b1ef3406e2dc4a822bb7fe9b4318590d
Regards,
Salvatore
