Bug#1065112: linux-image-6.1.0-18-amd64: System unresponsive after resume from suspend when WoWLAN enabled in iwlwifi

[David Balch]

Package: src:linux
Version: 6.1.76-1
Severity: normal
X-Debbugs-Cc: da...@balch.co.uk

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I am trying to get WoWLAN working on an old DELL via a PCIe WiFi card ( 
https://www.amazon.co.uk/dp/B0BTCNG9TD?psc=1=ppx_yo2ov_dt_b_product_details 
)
that uses the Intel 7265 chipset ( 
https://www.intel.com/content/www/us/en/products/sku/83635/intel-dual-band-wirelessac-7265/specifications.html
 ).

The card's result from lspci:
  03:00.0 Network controller [0280]: "Intel Corporation Wireless 7265 
[8086:095a] (rev 59)"



   * What exactly did you do (or not do) that was effective (or
 ineffective)?

1. Enabled WoWLAN with magic-packet with `iw phy0 wowlan enable magic-packet`
2. Suspend PC with `echo "mem" > /sys/power/state`
3. After suspend, press a key.

I also tried this with a pristine build of linux 6.7.6, and encountered the 
same problem.


   * What was the outcome of this action?

The display lit up, showing the same information as before suspend, but the 
mouse and keyboard don't respond.
Magic SysRq does respond.


I found my way to seeing the kernel crash message (via preventing 
console_suspend, and tweaking /proc/sys/kernel/{prink,sysrq} values),
as shown in the image at: https://imgur.com/a/E7dD0ND


Initial analysis of that photo from iam_tj[m]1 on irc #debian-kernel 
(2024-02-29 19:48):

>From your photo we see  
>`drivers/net/wireless/intel/iwlwifi/iwl-trans.c::iwl_trans_txq_enable_cfg()` 
>report "bad state" and that is called from 
>`drivers/net/wireless/intel/iwlwifi/mvm/d3.c::iwl_mvm_send_wowlan_get_status()`
> that reports "failed to query wakeup status (-5)".
>From reading the code around WoWLAN it seems a special WoWLAN firmware should 
>be loaded into the device on suspend and on resume the driver is checking it 
>is (still) there.
If not the driver should cause a full device reset.
`asm_exc_invalid_op` is a TRAP leading to 
`arch/x86/kernel/traps.c::handle_invalid_op()` which may imply the code in RAM 
has been corrupted (in the function `iwl_pcie_tx_start()` presumably).
Doesn't seem too likely though since code (.text sections) should be read-only 
unless the RAM itself is faulty - but if that one wouldn't expect the same 
error every time.



   * What outcome did you expect instead?

The system resumes from suspend and is fully interactive (as it does when 
WoWLAN is disabled).





-- Package-specific info:
** Version:
Linux version 6.1.0-18-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64 
root=UUID=b15802a9-4b38-4cb9-9109-fdf1cad881b0 ro quiet crashkernel=384M-:128M

** Not tainted

** Kernel log:
[4.039828] mei_me :00:16.0: enabling device ( -> 0002)
[4.064801] input: PC Speaker as /devices/platform/pcspkr/input/input9
[4.066671] ee1004 0-0051: 512 byte EE1004-compliant SPD EEPROM, read-only
[4.066685] ee1004 0-0053: 512 byte EE1004-compliant SPD EEPROM, read-only
[4.110654] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=4, 
TCOBASE=0x0400)
[4.112303] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.4)
[4.113931] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[4.128354] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
[4.128506] cfg80211: Loaded X.509 cert 'b...@debian.org: 
577e021cb980e0e820821ba7b54b4961b8b4fadf'
[4.128645] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[4.128783] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[4.128917] cfg80211: Loaded X.509 cert 'wens: 
61c038651aabdcf94bd0ac7ff06c7248db18c600'
[4.133009] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[4.133129] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[4.133616] input: Dell WMI hotkeys as 
/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input10
[4.154628] Intel(R) Wireless WiFi driver for Linux
[4.166726] pcieport :00:1d.0: Intel SPT PCH root port ACS workaround 
enabled
[4.166880] iwlwifi :03:00.0: enabling device (0100 -> 0102)
[4.169833] iwlwifi :03:00.0: firmware: direct-loading firmware 
iwlwifi-7265D-29.ucode
[4.169856] iwlwifi :03:00.0: Found debug destination: EXTERNAL_DRAM
[4.169857] iwlwifi :03:00.0: Found debug configuration: 0
[4.170045] iwlwifi :03:00.0: loaded firmware version 29.4063824552.0 
7265D-29.ucode op_mode iwlmvm
[4.184779] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102)
[4.187148] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms 
ovfl timer
[4.187150] RAPL PMU: hw unit of domain 

bump to 20240115 + bookworm backport

[David Heidelberg]

Hello!

Could I please request bumping  + optimally official backport to 
bookworm? It would be very useful for our Mesa3D CI builds!


Thank you for your work!
David

--
David Heidelberg

Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot

[Erwan David]

Le 22/01/2024 à 13:49, Erwan David a écrit :

Le 23/12/2023 à 21:26, Erwan David a écrit :

Le 19/12/2023 à 19:34, Diederik de Haas a écrit :

On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote:
Same behaviour with 6.6.3-1 from experimental (that's what apt gave 
me,

maybe tomoroow the 6.6.4).
Either your APT cache should be updated or you're using a mirror 
which is

rather severely out of date.
6.6.4-1 was uploaded to Debian on 2023-12-03, a day after .3-1.


it was 6.6.4. I tried with my Aten Dock : same thing.

I disabled the virtualbox service so that the virtualbox modules are 
not loaded : it does not hang immediately, but waits a few minutes 
before doing it.




Some more details :

1) problem does not come from ethernet Nics, but rather from Wifi 
chipset, blocking appears when it is deactivated either by BIOS (when 
connecting Ethernet) or manually (through nm-applet in KDE) Wifi 
chipset is 02:00.0 Network controller: Intel Corporation Wireless 8265 
/ 8275 (rev 78)



Sorry, mail sent too fast :

It seems to work better with kernel 6.6.11 (6.6.9 still had the bug).

I'll do some other tests when possible (this laptop is my work laptop, 
and I cannot do tests leading to possible crash as often as I would wa nt



--
Erwan David

Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot

[Erwan David]

Le 23/12/2023 à 21:26, Erwan David a écrit :

Le 19/12/2023 à 19:34, Diederik de Haas a écrit :

On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote:

Same behaviour with 6.6.3-1 from experimental (that's what apt gave me,
maybe tomoroow the 6.6.4).
Either your APT cache should be updated or you're using a mirror 
which is

rather severely out of date.
6.6.4-1 was uploaded to Debian on 2023-12-03, a day after .3-1.


it was 6.6.4. I tried with my Aten Dock : same thing.

I disabled the virtualbox service so that the virtualbox modules are 
not loaded : it does not hang immediately, but waits a few minutes 
before doing it.




Some more details :

1) problem does not come from ethernet Nics, but rather from Wifi 
chipset, blocking appears when it is deactivated either by BIOS (when 
connecting Ethernet) or manually (through nm-applet in KDE) Wifi chipset 
is 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 
(rev 78)


--
Erwan David

Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot

[Erwan David]

Le 19/12/2023 à 19:34, Diederik de Haas a écrit :

On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote:

Same behaviour with 6.6.3-1 from experimental (that's what apt gave me,
maybe tomoroow the 6.6.4).

Either your APT cache should be updated or you're using a mirror which is
rather severely out of date.
6.6.4-1 was uploaded to Debian on 2023-12-03, a day after .3-1.


it was 6.6.4. I tried with my Aten Dock : same thing.

I disabled the virtualbox service so that the virtualbox modules are not 
loaded : it does not hang immediately, but waits a few minutes before 
doing it.

Bug#1058937: /usr-move: Do we support upgrades without apt?

[David Kalnischkies]

On Thu, Dec 21, 2023 at 02:42:56PM +, Matthew Vernon wrote:
> On 21/12/2023 09:41, Helmut Grohne wrote:
> > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > using apt unsupported until we no longer deal with aliasing?
> 
> I incline towards "no"; if an upgrade has failed part-way (as does happen),
> people may then reasonably use dpkg directly to try and un-wedge the upgrade
> (e.g. to try and configure some part-installed packages, or try installing
> some already-downloaded packages).

You can configure half-installed packages, no problem, this is about
unpacking (which is the first step in an install, where only Conflicts
and Pre-Depends matter, if you are not deep into dpkg vocabulary)


The "try installing" part is less straight forward. In general, you
are running into dpkg "features" (e.g. not handling pre-depends) or
into dpkg bugs (e.g. #832972, #844300): In the best case your system
state became a bit worse and hence harder to "un-wedge". In the worst
case a maintainer script has run amok as nobody tested this.
But yeah, most of the time you will indeed be lucky and hence come to
the unreasonable conclusion that its reasonable to call dpkg directly.


Anyway, if your upgrade failed part-way, you are probably in luck given
that its more likely the upgrade failed in unpack/configure than in
removal – so if you aren't too eager to install more packages by hand
but limit yourself to e.g. (re)installing the ones who failed you are
fine as apt will have removed the conflictors already for you (or
upgraded them, if that can resolve the conflict).


But lets assume you are not:
As you are driving dpkg by hand you also have the time to read what it
prints, which in the problematic case is (as exampled by #1058937):
| dpkg: considering removing libnfsidmap-regex:amd64 in favour of 
libnfsidmap1:amd64 ...
| dpkg: yes, will remove libnfsidmap-regex:amd64 in favour of libnfsidmap1:amd64
(and the same for libnfsidmap2:amd64 as well. If your terminal supports
 it parts of these messages will be in bold)

Note that the similar "dpkg: considering deconfiguration of …" which is
the result of Breaks relations is not a problematic case.

(Also note that this exact situation is indeed another reason why
 interacting with dpkg by hand is somewhat dangerous as you might not
 expect packages to be removed from your system while you just told
 dpkg to unpack something… just remember that the next time you happen
 to "dpkg -i" some random deb file onto your system.)

That is of course no hint that a file might have been lost due to
aliasing if you don't know that this could be the case, but on the
upside it is not entirely a silent file lose situation either. We could
write something in the release notes if someone happens to read them AND
also encounters this message.


Query your memory: Did you encounter this message before? Nothing in
the /usr merge plan makes that particularly more likely to be encountered
for a user and not all of the encounters will actually exhibit the file
lose. So if you haven't – and I would argue that most people haven't –
there is a pretty good chance you wont have a problem in the future
either…


So, in summary: Yes, there are theoretic relatively easy ways to trigger
it with dpkg directly. That isn't the question. The question is if a real
person who isn't actively trying to trigger it is likely to run into it
by accident (and/or if such a person can even reasonably exist) so that
we have to help them by generating work for many people and potentially
new upgrade problems for everyone – or if we declare them, existing or
not, a non-issue at least for the upgrade to trixie.


And on a sidenote: I would advise to reconsider interacting with dpkg
too casually – but luck is probably on your side in any case.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#1058937: /usr-move: Do we support upgrades without apt?

[David Kalnischkies]

On Thu, Dec 21, 2023 at 03:31:55PM +0100, Marc Haber wrote:
> On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote:
> > On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> > > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > > using apt unsupported until we no longer deal with aliasing?
> > 
> > I think so, yes. I don't think it's likely that there are people doing
> > upgrades on running systems not using apt.
> 
> Do those GUI frontends that work via packagekit or other frameworks
> count as "using apt"?

I explained that in full detail in my mail to the pause-thread:
https://lists.debian.org/debian-devel/2023/12/msg00039.html

In short: helmuts "apt" (my "APT") includes everything that uses libapt.
That is apt, apt-get, python-apt, aptitude, synaptics, everything based
on packagekit, …

I know of only cupt and dselect which don't count, but I have some
suspicion that they would work anyhow. IF you don't run into other
problems with them, like that they do not implement Multi-Arch.


So this thread is really about:
How much are people REALLY fiddling with dpkg directly in an upgrade
and can we just say its unsupported – because, at least that is my view,
in practice nobody does it and its therefore also completely untested.

Case in point: We have this thread not because someone found it while
working with dpkg directly even through they had potentially years, but
because Helmut ended up triggering an edge case in which apt interacts
with dpkg in this way and only after that people looked for how to
trigger it with dpkg because triggering it with apt is hard (= as Helmut
checked, no package (pair) in current unstable is known to exhibit the
required setup).

(I will write another mail in another subthread about the finer details
 of what interacting with dpkg in an upgrade means and what might be
 problematic if you aren't careful – in general, not just with aliasing)


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot

[Erwan David]

Le 19/12/2023 à 09:10, Salvatore Bonaccorso a écrit :

Control: tags -1 + moreinfo

On Tue, Dec 19, 2023 at 08:49:45AM +0100, Erwan David wrote:

Package: src:linux
Version: 6.5.13-1
Severity: important

On a Dell Latitude 7490, with 1 intergated e1000e nic, and an extrenal Dock 
with Realtek8153. If ethernet on one of those NICs is
connected at boot, it runs OK. However, if a NIC is connected to network while 
the kernel runs (or when coming back from
hibernation), system hangs, any network related process is stuck (even a simple 
ip a) and load climbs.
Clean shutdown is not possible because disk cannot be unmounted because of 
those processes.

Status here is obviously on a fresh booted system, without the problem. I know 
how to reproduce, and there is a small time window
where I might be able to launch some diagnostic commands at the beginning of 
the problem.

As there won't be any further updates in the 6.5.y series and we will
move at some point to the 6.6.y one, can you test it against the
version which is currently in experimental? (6.6.4-1~exp1).

Regards,
Salvatore

Same behaviour with 6.6.3-1 from experimental (that's what apt gave me, 
maybe tomoroow the 6.6.4). I tested with a Lenovo T590 on an Aten dock 
with also a realtek5183 NIC. It works with 6.5.0-5 On the Dell it works 
with 6.5.0-4 which makes me think the hardware is good.


One difference between the lenovo and the Dell : since the Dell has a 
smaller disk and was installed in 2020 then upgraded, the /boot is small 
and initramfs is in "dep" mode, with some modules forced for the dock. 
At the end of week I'll be able to test the Dell on same Dock as the 
lenovo (not the other way around, Dell and its dock are work issued and 
I cannot connect a personnal laptop on the dock), and try to use the 
"most mode for initramfs. I'll also check carefully the differences 
between the package lists, especially firmwares.

Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot

[Erwan David]

Package: src:linux
Version: 6.5.13-1
Severity: important

On a Dell Latitude 7490, with 1 intergated e1000e nic, and an extrenal Dock 
with Realtek8153. If ethernet on one of those NICs is
connected at boot, it runs OK. However, if a NIC is connected to network while 
the kernel runs (or when coming back from
hibernation), system hangs, any network related process is stuck (even a simple 
ip a) and load climbs.
Clean shutdown is not possible because disk cannot be unmounted because of 
those processes.

Status here is obviously on a fresh booted system, without the problem. I know 
how to reproduce, and there is a small time window
where I might be able to launch some diagnostic commands at the beginning of 
the problem.


-- Package-specific info:
** Version:
Linux version 6.5.0-5-amd64 (debian-kernel@lists.debian.org) (gcc-13 (Debian 
13.2.0-7) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC 
Debian 6.5.13-1 (2023-11-29)

** Command line:
BOOT_IMAGE=/vmlinuz-6.5.0-5-amd64 root=/dev/mapper/ot--port--eda--vg-root ro 
net.ifnames=0 quiet splash

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[   16.693178] iwlwifi :02:00.0: Detected crf-id 0xbadcafe, cnv-id 0x10 
wfpm id 0x8000
[   16.693235] iwlwifi :02:00.0: PCI dev 24fd/0050, rev=0x230, 
rfid=0xd5d5
[   16.702693] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-8265-36.ucode
[   16.706377] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_ops [i915])
[   16.706678] iTCO_vendor_support: vendor-support=0
[   16.712182] iwlwifi :02:00.0: loaded firmware version 36.ca7b901d.0 
8265-36.ucode op_mode iwlmvm
[   16.712575] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040380
[   16.712592] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[   16.726905] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=4, 
TCOBASE=0x0400)
[   16.726812] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   16.727471] ee1004 8-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[   17.003787] Bluetooth: Core ver 2.22
[   17.003802] NET: Registered PF_BLUETOOTH protocol family
[   17.003803] Bluetooth: HCI device and connection manager initialized
[   17.003806] Bluetooth: HCI socket layer initialized
[   17.003808] Bluetooth: L2CAP socket layer initialized
[   17.003811] Bluetooth: SCO socket layer initialized
[   17.057532] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3246: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   17.057539] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   17.057542] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   17.057545] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0
[   17.057546] snd_hda_codec_realtek hdaudioC1D0:inputs:
[   17.057548] snd_hda_codec_realtek hdaudioC1D0:  Mic=0x12
[   17.092741] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
8265, REV=0x230
[   17.092813] thermal thermal_zone7: failed to read out thermal zone (-61)
[   17.099820] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[   17.118484] i2c_hid_acpi i2c-MELF0410:00: device returned incorrect report 
(209 vs 4 expected)
[   17.118602] hid-multitouch 0018:1FD2:7007.0008: failed to fetch feature 4
[   17.118933] input: MELF0410:00 1FD2:7007 as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-7/i2c-MELF0410:00/0018:1FD2:7007.0008/input/input22
[   17.119033] hid-multitouch 0018:1FD2:7007.0008: input,hidraw5: I2C HID v1.00 
Device [MELF0410:00 1FD2:7007] on i2c-MELF0410:00
[   17.124742] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1f.3/sound/card1/input20
[   17.156389] iwlwifi :02:00.0: base HW address: ac:67:5d:ec:95:96, OTP 
minor version: 0x0
[   17.173097] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   17.186889] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1f.3/sound/card1/input21
[   17.266984] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card1/input24
[   17.275704] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   17.331264] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card1/input25
[   17.331334] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card1/input26
[   17.339518] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4 
subsystem
[   17.340772] EXT4-fs (nvme0n1p2): mounted filesystem 
2b049359-11a3-45fc-ad13-dda0e015c96f r/w without journal. Quota mode: none.
[   17.340878] input: DELL081C:00 044E:121F Mouse as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-9/i2c-DELL081C:00/0018:044E:121F.0009/input/input27
[   17.341209] input: DELL081C:00 044E:121F Touchpad as 

Bug#1057786: firmware-misc-nonfree: Split firmware firmware-misc-nonfree based on architecture

[David Heidelberg]

Package: firmware-misc-nonfree
Version: 20230625-1
Severity: wishlist

Dear Maintainer,

would be lovely to have a firmware-misc-nonfree based on architecture.
Multiple of these firmwares are bound to arm64, x86_64 or other archs.

Installing them for example in the CI for x86_64 leads to needing using:

dpkg -L firmware-misc-nonfree | grep -v "i915" | xargs rm # drop extra 50M

or similar commands, which doesn't seems very good
for the long-term maintainance.

Would be acceptable to split firmwares by arch where they can be used?

Thank you

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.142

-- no debconf information

Bug#1029968: And some patches

[Dr. David Alan Gilbert]

As well as the fixes in 6.6, we also need this patchup series here:

https://lore.kernel.org/linux-media/ZWibhE350L3BTRK8@gallifrey/T/#t

These seem to make it pretty nicely.
-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: fixed in 6.6

[Dr. David Alan Gilbert]

This looks like it's fixed in 6.6, I think they had a major rewrite
in there.
It's a conversion to vb2 in the series starting with
d1846d72587e9241e73a18da14a325b43700013b

There are a couple of minor oddities with that
(they list the sequence cost the bttv had) but that's relatively minor.

Dave

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1053601: linux-image-6.5.0-1-amd64: iwlwifi crash returning from sleep (NULL pointer dereference)

[Erwan David]

Le 07/10/2023 à 10:45, Diederik de Haas a écrit :

On Saturday, 7 October 2023 10:26:05 CEST Erwan David wrote:

Package: src:linux
Version: 6.5.3-1
Severity: important

After the computer went to sleep, I get no wifi, journalctl shows a crash of
iwlwifi with a NULL pointer dereference

There appears to be a new 6.5.x version in the works and it would be useful to
know if this issue would be fixed by that.
Assuming this issue didn't happen with previous kernels, can you share what
the latest version was where everything did work properly?



It worked with linux-image-6.4.0-4-amd64  6.4.13-1 . However it 
is not systematic sometimes it works.




here are the logs :

[   23.510358] thermal thermal_zone7: failed to read out thermal zone (-61)

Probably unrelated, but it did catch my eye as it does not sound good.
You may want to keep an eye out for that.


I'll have a look, thanks.

Bug#1053601: linux-image-6.5.0-1-amd64: iwlwifi crash returning from sleep (NULL pointer dereference)

[Erwan David]

Package: src:linux
Version: 6.5.3-1
Severity: important

After the computer went to sleep, I get no wifi, journalctl shows a crash of
iwlwifi with a NULL pointer dereference

here are the logs :

oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Failed to load 
firmware chunk!
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: iwlwifi transaction 
failed, dumping registers
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: iwlwifi device 
config registers:
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: : 9df08086 
00100406 02800030 0080 dd738004   
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0020:  
  00348086  00c8  01ff
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0040: 00928010 
1ec0 00100c10     
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0060:  
00080812 0405     
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0080: 800f0011 
2000 3000     
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 00a0:  
      
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 00c0:  
 c823d001 0d08 00804005   
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 00e0:  
      
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0100: 14c0 
ff00 00ff 00462031  2000  
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0120:  
      
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0140:  
  16410018  0001001e 00481e1f 
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: iwlwifi device 
memory mapped registers:
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: : 00c89002 
0040      
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: 0020: 0011 
0c040005 0312 d5d5 d5d5 d5d5 80008040 001f0042
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Could not load the 
[0] uCode section
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Failed to start INIT 
ucode: -110
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Failed to run INIT 
ucode: -110
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Failed to start RT 
ucode: -110
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: iwl_trans_send_cmd 
bad state = 0
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Failing on timeout 
while stopping DMA channel 8 [0xa5a5a5a2]
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Device gone - 
scheduling removal!
oct. 07 10:09:03 maine-ocean kernel: [ cut here ]
oct. 07 10:09:03 maine-ocean kernel: Hardware became unavailable upon resume. 
This could be a software issue prior to suspend or a hardware issue.
oct. 07 10:09:03 maine-ocean kernel: WARNING: CPU: 2 PID: 66 at 
net/mac80211/util.c:2568 ieee80211_reconfig+0xa9/0x1660 [mac80211]
oct. 07 10:09:03 maine-ocean kernel: Modules linked in: rpcsec_gss_krb5 
auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ctr ccm rfcomm 
cmac algif_hash algif_skcipher af_alg bnep uinput sunrpc binfmt_misc nls_ascii 
nls_cp437 vfat fat snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation snd_sof_intel_hda_mlink 
snd_hda_codec_hdmi soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils soundwire_bus intel_pmc_core_pltdrv 
intel_pmc_core snd_soc_skl iwlmvm x86_pkg_temp_thermal btusb intel_powerclamp 
snd_soc_hdac_hda snd_ctl_led snd_hda_ext_core btrtl snd_soc_sst_ipc btbcm 
coretemp snd_soc_sst_dsp snd_hda_codec_realtek btintel snd_soc_acpi_intel_match 
btmtk kvm_intel snd_soc_acpi bluetooth mac80211 snd_hda_codec_generic 
snd_soc_core libarc4 kvm snd_compress snd_hda_intel snd_intel_dspcfg 
snd_intel_sdw_acpi sha3_generic uvcvideo jitterentropy_rng snd_hda_codec 
iwlwifi videobuf2_vmalloc uvc videobuf2_memops irqbypass videobuf2_v4l2 
snd_hda_core rapl snd_hwdep drbg
oct. 07 10:09:03 maine-ocean kernel:  mei_pxp mei_hdcp intel_rapl_msr videodev 
snd_pcm_oss intel_cstate videobuf2_common thinkpad_acpi intel_uncore 
snd_mixer_oss cfg80211 mc ansi_cprng snd_pcm 
processor_thermal_device_pci_legacy iTCO_wdt nvram processor_thermal_device 
intel_pmc_bxt ecdh_generic think_lmi snd_timer ledtrig_audio 
processor_thermal_rfim iTCO_vendor_support ecc pcspkr platform_profile 
firmware_attributes_class intel_wmi_thunderbolt wmi_bmof 

Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security

[David da Silva Polverari]

On Sat, Sep 16, 2023 at 11:15:42PM +0200, Salvatore Bonaccorso wrote:
> 
> Can you verify if it's this issue known upstream?
> 
> https://lore.kernel.org/regressions/5dhv0s.d0f751zf65...@gmail.com/
> 
Yes, it is the same issue. Sorry for taking too long to reply. I was
juggling with low partition space on my /boot to install a upstream
kernel on my laptop.

> Does reverting the mentioned patch fix the issue?
>
Yes, I checked v6.1.46 out from linux stable, built it, and tried to
boot. It presented the same problem as Debian's 6.1.0-12 (6.1.52-1).
After reverting commit 8ee39ec479147e29af704639f8e55fce246ed2d9 and
building it again, booting went fine.  Hope it helps.

Regards,
David

Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security

[David da Silva Polverari]

Package: src:linux
Version: 6.1.52-1
Severity: important

Dear Maintainer(s),

After upgrading the kernel from linux-image-6.1.0-11-amd64 (6.1.38-4) to
linux-image-6.1.0-12-amd64 (6.1.52-1) from bookworm-security on my
laptop (a Dell XPS 9560), the kernel fails to find the nvme disk, making
it impossible for the initrd to decrypt the drive using LUKS, and as
such there are no boot messages. On the previous kernel it boots fine.
With tha 6.1.0-12 kernel, dmesg shows the following:

[   42.074878] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
[   42.074879] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
[   42.120786] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
[   42.121007] nvme nvme0: Removing after probe failure status: -19
[   42.136737] nvme0n1: detected capacity change from 1000215216 to 0

When I tried using the suggested parameters, I could boot, boot soon
afterwards the system hung. I also tried some variations, as trying
either only nvm_core.default_ps_max_latency_us=0 or pcie_aspm=off, but
neither one worked.

I attached the dmesg output from the laptop into this email.

Regards,
David
[0.00] microcode: microcode updated early to revision 0xf4, date = 
2023-02-23
[0.00] Linux version 6.1.0-12-amd64 (debian-kernel@lists.debian.org) 
(gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 
SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-6.1.0-12-amd64 
root=/dev/mapper/mercurius--vg-root ro acpi_rev_override=1 mitigations=off quiet
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x6a305fff] usable
[0.00] BIOS-e820: [mem 0x6a306000-0x6a306fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x6a307000-0x6a307fff] reserved
[0.00] BIOS-e820: [mem 0x6a308000-0x7838dfff] usable
[0.00] BIOS-e820: [mem 0x7838e000-0x7874afff] reserved
[0.00] BIOS-e820: [mem 0x7874b000-0x78791fff] ACPI data
[0.00] BIOS-e820: [mem 0x78792000-0x78e85fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x78e86000-0x7951] reserved
[0.00] BIOS-e820: [mem 0x7952-0x795fefff] type 20
[0.00] BIOS-e820: [mem 0x795ff000-0x795f] usable
[0.00] BIOS-e820: [mem 0x7960-0x7f7f] reserved
[0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved
[0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00047e7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.40 by American Megatrends
[0.00] efi: ACPI=0x7875a000 ACPI 2.0=0x7875a000 SMBIOS=0x79367000 
SMBIOS 3.0=0x79366000 TPMFinalLog=0x78b27000 ESRT=0x792bd198 MEMATTR=0x75be0018 
MOKvar=0x79363000 
[0.00] secureboot: Secure boot disabled
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.28.0 03/23/2022
[0.00] tsc: Detected 2800.000 MHz processor
[0.00] tsc: Detected 2799.927 MHz TSC
[0.000717] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.000720] e820: remove [mem 0x000a-0x000f] usable
[0.000730] last_pfn = 0x47e800 max_arch_pfn = 0x4
[0.000844] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.001398] last_pfn = 0x79600 max_arch_pfn = 0x4
[0.009942] found SMP MP-table at [mem 0x000fced0-0x000fcedf]
[0.009956] esrt: Reserving ESRT space from 0x792bd198 to 
0x792bd1d0.
[0.009966] Kernel/User page tables isolation: disabled on command line.
[0.009967] Using GB pages for direct mapping
[0.010344] RAMDISK: [mem 0x304b3000-0x34250fff]
[0.010349] ACPI: Early table checksum verification disabled
[0.010352] ACPI: RSDP 0x7875A000 24 (v02 DELL  )
[0.010356] ACPI: XSDT 0x7875A0D0 00011C (v01 DELL   CBX3 
01072009 AMI  00010013)
[0.010361] ACPI: FACP 0x7877FA78 00010C (v05 DELL   CBX3 
01072009 AMI  00010013)
[0.010366] ACPI: DSDT 0x7875A278 0257FF (v02 DELL   CBX3 
01072009 

Bug#1042543: Known upstream regression in 6.4: audio distortion on ThinkPad X1 Gen 11

[David Heidelberg]

Patch is included in recent stable release, available in unstable. Until 
it gets into testing, this should help:


 $ apt install -t unstable linux-image-amd64

I assume the bug can be closed.

David

On 18/08/2023 04:42, David wrote:

Version: 6.4.4-3

Hello,

1. the bug is still present

2. Dell XPS 9310 is also affected.

It's still not included in stable series, but got merged into for-next 
branch already [1].


Please apply.

Thank you

David

[1] https://www.spinics.net/lists/alsa-devel/msg163701.html

On Sat, 29 Jul 2023 19:58:50 -0700 Josh Triplett 
 wrote:

> Package: src:linux
> Version: 6.4.4-1
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: j...@joshtriplett.org
>
> See https://github.com/thesofproject/linux/issues/4482 and
> https://bugzilla.kernel.org/show_bug.cgi?id=217673 for the bug, and
> https://github.com/thesofproject/linux/pull/4484 for the fix.
>
> I can confirm that 6.4 has intermittent audio distortion on my system,
> and 6.3 does not.
>
> Please consider applying the fix.


--
David Heidelberg
Certified Linux Magician

Bug#1050406: linux-headers-6.4.0-3-amd64: cannot install because of dkms problem

[Erwan David]

Package: linux-headers-6.4.0-3-amd64
Version: 6.4.11-1
Severity: normal

At install time I get following error, which prevents installation (and yes I 
need virtualbox)

Setting up linux-headers-6.4.0-3-amd64 (6.4.11-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.4.0-3-amd64.
Sign command: /lib/modules/6.4.0-3-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.4.0-3-amd64 -C /lib/modules/6.4.0-3-amd64/build 
M=/var/lib/dkms/virtualbox/7.0.10/build(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.4.0-3-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.10/build/make.log for more information.
dkms autoinstall on 6.4.0-3-amd64/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.4.0-3-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at 
/var/lib/dpkg/info/linux-headers-6.4.0-3-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.4.0-3-amd64 (--configure):
 installed linux-headers-6.4.0-3-amd64 package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-amd64:
 linux-headers-amd64 depends on linux-headers-6.4.0-3-amd64 (= 6.4.11-1); 
however:
  Package linux-headers-6.4.0-3-amd64 is not configured yet.

dpkg: error processing package linux-headers-amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up linux-image-6.4.0-3-amd64 (6.4.11-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.4.0-3-amd64.
Sign command: /lib/modules/6.4.0-3-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.4.0-3-amd64 -C /lib/modules/6.4.0-3-amd64/build 
M=/var/lib/dkms/virtualbox/7.0.10/build(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.4.0-3-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.10/build/make.log for more information.
dkms autoinstall on 6.4.0-3-amd64/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.4.0-3-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.4.0-3-amd64 (--configure):
 installed linux-image-6.4.0-3-amd64 package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-6.4.0-3-amd64 (= 6.4.11-1); however:
  Package linux-image-6.4.0-3-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-6.4.0-3-amd64
 linux-headers-amd64
 linux-image-6.4.0-3-amd64
 linux-image-amd64




-- System Information:
Debian Release: trixie/sid
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'testing'), (800, 
'stable-security'), (500, 'proposed-updates'), (500, 'unstable'), (400, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-headers-6.4.0-3-amd64 depends on:
ii  linux-compiler-gcc-13-x86 6.4.11-1
ii  linux-headers-6.4.0-3-common  6.4.11-1
ii  linux-kbuild-6.4.0-3  6.4.11-1

linux-headers-6.4.0-3-amd64 recommends no packages.

linux-headers-6.4.0-3-amd64 suggests no packages.


Other package implied :
ii  virtualbox-dkms7.0.10-dfsg-2 amd64 

-- no debconf information

Bug#1042543: Known upstream regression in 6.4: audio distortion on ThinkPad X1 Gen 11

[David]

Version: 6.4.4-3

Hello,

1. the bug is still present

2. Dell XPS 9310 is also affected.

It's still not included in stable series, but got merged into for-next 
branch already [1].


Please apply.

Thank you

David

[1] https://www.spinics.net/lists/alsa-devel/msg163701.html

On Sat, 29 Jul 2023 19:58:50 -0700 Josh Triplett  
wrote:

> Package: src:linux
> Version: 6.4.4-1
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: j...@joshtriplett.org
>
> See https://github.com/thesofproject/linux/issues/4482 and
> https://bugzilla.kernel.org/show_bug.cgi?id=217673 for the bug, and
> https://github.com/thesofproject/linux/pull/4484 for the fix.
>
> I can confirm that 6.4 has intermittent audio distortion on my system,
> and 6.3 does not.
>
> Please consider applying the fix.

Bug#1043434: linux-headers-amd64 cannot be upgraded to 6.1.38-3 (dependency is unavailable)

[David Masover]

Package: linux-headers-amd64
Version: 6.1.38-2
Severity: important
X-Debbugs-Cc: d...@forkbox.net

Dear Maintainer,

It looks like linux-headers-amd64 6.1.38-3 depends on
linux-headers-6.1.0-11-amd64 (=6.1.38-3), which makes sense.
Unfortunately, the only version of linux-headers-6.1.0-11-amd64
available is 6.1.38-4. There is no newer version of linux-headers-amd64
available right now.

I marked this "important" because trying to upgrade now will upgrade the
kernel, but not the headers. This means my system's latest kernel has no
headers, which breaks DKMS, and in particular, nvidia-kernel-dkms.
My system didn't attempt to bring up a GUI without nvidia_drm loaded.

I'm not entirely sure I understand what else went wrong here. I think I
tried reinstalling nvidia-kernel-dkms, which skipped the current kernel
because it couldn't find headers, but seemed to also skip the previous
kernel. This would explain why, when I tried rebooting into
6.1.0-10-amd64, I still had no GUI. Reinstalling nvidia-kernel-dkms
while booted into 6.1.0-10-amd64 got my GUI back.


-- System Information:
Debian Release: 12.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-headers-amd64 depends on:
ii  linux-headers-6.1.0-10-amd64  6.1.38-2

linux-headers-amd64 recommends no packages.

linux-headers-amd64 suggests no packages.

-- no debconf information

Bug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ...

[David Reviejo]

Hi, Nathan

I have similar warnings with the last longterm 6.1.27 image from
bookworm, in my case when suspending to RAM.

Seems to be an amdgpu bug introduced two or three kernel releases ago, as
you can see googling around; for example here:

https://bugzilla.redhat.com/show_bug.cgi?id=2191739

or here:

https://gitlab.freedesktop.org/drm/amd/-/issues/2522

If it's this bug, the fix seems to be in yesterday's latest upstream
kernel update: 6.3.3 (and 6.1.29 for the stable longterm).

We can only hope that the developers are not too busy with the bookworm
release to apply these patches ASAP ;)

Cheers,
--
David

Bug#1032642: iproute2: ip tunnel change ip6gre to gre crashes with stack smash

[David Ahern]

On 4/3/23 9:24 AM, Stephen Hemminger wrote:
> ted
>>
>> This happens because iproute2 just assumes the tunnel is ipv4, but the
>> kernel "knows" it's actually ip6gre so when calling the SIOCGETTUNNEL
>> ioctl it writes back a struct ip6_tnl_parm2 into the struct
>> ip_tunnel_parm which is smaller, so the stack gets overwritten. Is
>> there any way to tell from userspace whether a gre is v4 or v6 before
>> doing an ioctl? The ioctls don't take/return a size parameter as far
>> as I can see...
> 
> Ip uses and IPv4 UDP socket when it thinks it is talking to GRE.
> And a IPv6 UDP socket when it is talking to GRE6.
> 
> So the kernel could check and error out?
> 

Does seem like a kernel bug and a well known design flaw in ioctl
interface (assuming buffer of a specific size). The best iproute2 can do
is have `old_p` be a larger size (e.g., ip6_tnl_parm2) to avoid the
overrun, but then the result is nonsense with no way for it no an ipv6
struct was passed back. The crash at least indicates something is off.

Bug#1032140: [External] Re: Bug#1032140: Lenovo Z16 Install issue

[David Ober]

Not the result I was expecting, here is the dmesg logs where it still failed to 
load the firmware


[   26.626868] ath11k_pci :04:00.0: BAR 0: assigned [mem 
0xb000-0xb01f 64bit]
[   26.627223] ath11k_pci :04:00.0: MSI vectors: 32
[   26.627228] ath11k_pci :04:00.0: wcn6855 hw2.1
[   26.630080] NET: Registered PF_QIPCRTR protocol family
[   26.785089] mhi mhi0: Requested to power ON
[   26.785102] mhi mhi0: Power on setup success
[   26.785400] mhi mhi0: firmware: failed to load ath11k/WCN6855/hw2.1/amss.bin 
(-2)
[   26.785407] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   26.785422] mhi mhi0: firmware: failed to load ath11k/WCN6855/hw2.1/amss.bin 
(-2)
[   26.785425] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/amss.bin 
failed with error -2
[   26.785430] mhi mhi0: Error loading firmware: -2
[   26.785589] ath11k_pci :04:00.0: failed to power up mhi: -110
[   26.785596] ath11k_pci :04:00.0: failed to start mhi: -110
[   26.785600] ath11k_pci :04:00.0: failed to power up :-110
[   26.820002] ath11k_pci :04:00.0: failed to create soc core: -110
[   26.820018] ath11k_pci :04:00.0: failed to init core: -110
[   27.036908] ath11k_pci: probe of :04:00.0 failed with error -110

David

-Original Message-
From: Cyril Brulebois  
Sent: Wednesday, March 1, 2023 3:23 AM
To: 1032...@bugs.debian.org
Cc: David Ober ; Steve McIntyre ; 
debian-kernel@lists.debian.org
Subject: Re: Bug#1032140: [External] Re: Bug#1032140: Lenovo Z16 Install issue

Control: reassign -1 src:linux 6.1.12-1
Control: forwarded -1 
https://salsa.debian.org/kernel-team/linux/-/merge_requests/667
Control: tag -1 patch

Cyril Brulebois  (2023-03-01):
> Thanks for this confirmation, I'll file the MR against linux later on.

Doing so now.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

RE: Bug#1032140: [External] Re: Bug#1032140: Lenovo Z16 Install issue

[David Ober]

Test worked as you expected the network card driver looks to be enabled but 
cannot load firmware.  I can test if you want or you can wait until the next 
formal build

David

-Original Message-
From: Cyril Brulebois  
Sent: Tuesday, February 28, 2023 4:41 PM
To: David Ober ; 1032...@bugs.debian.org
Cc: Steve McIntyre ; debian-kernel@lists.debian.org
Subject: Re: Bug#1032140: [External] Re: Bug#1032140: Lenovo Z16 Install issue

David Ober  (2023-02-28):
> Happy to test it

Great!

Here's a minimal netboot-gtk mini.iso, to test just the loading aspect:
  https://people.debian.org/~kibi/bug-1032140/

It adds qrtr-mhi (and its dependency qrtr), and both can be loaded just fine in 
QEMU (manually).

This should help ath11k_pci work better (probing shouldn't fail, at least), and 
the next step is probably getting an error about missing firmware. That's 
expected with this small build, but once we make sure ath11k_pci loads and 
probes fine, I'm happy to build a full netinst if you want to go through the 
whole installation process. Otherwise, we can stash the change in linux.git and 
that should get included in the next Debian Installer release.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

RE: [External] Re: Bug#1032140: Lenovo Z16 Install issue

[David Ober]

Happy to test it 

David

-Original Message-
From: Cyril Brulebois  
Sent: Tuesday, February 28, 2023 12:52 PM
To: Steve McIntyre ; 1032...@bugs.debian.org
Cc: David Ober ; debian-kernel@lists.debian.org
Subject: [External] Re: Bug#1032140: Lenovo Z16 Install issue

Hi David,

and thanks for your installation report.

David Ober  (2023-02-28):
> Related dmesg Logs
> [   30.324093] ath11k_pci :04:00.0: BAR 0: assigned [mem 
> 0xb000-0xb01f 64bit]
> [   30.324449] ath11k_pci :04:00.0: MSI vectors: 32
> [   30.324454] ath11k_pci :04:00.0: wcn6855 hw2.1
> [   30.325448] ath11k_pci :04:00.0: failed to initialize qmi handle: -517
> [   30.325450] ath11k_pci :04:00.0: failed to initialize qmi :-517
> [   30.325450] ath11k_pci :04:00.0: failed to create soc core: -517
> [   30.325451] ath11k_pci :04:00.0: failed to init core: -517

Steve McIntyre  (2023-02-28):
> If possible, could you also please grab a full copy of the file 
> /var/log/syslog from the installer? That should help us more...

I don't think we actually need it, given this:
  
https://patchwork.kernel.org/project/linux-wireless/patch/20221202130600.883174-1-...@lst.de/

This doesn't seem to have been reviewed at all, let alone made its way into 
mainline master… and I can't check latest sid branch on 
https://salsa.debian.org/kernel-team/linux since GitLab won't let me, but what 
I have locally doesn't mention anything qrtr-mhi related at the moment. Maybe 
something we could stash in the wireless nic udeb, which ships a lot from 
drivers but also bits of crypto, math, etc. (in addition to the obvious 80211 
parts).

David, are you happy to run a test using a minimal, patched image I'd build 
locally?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Bug#1029968: Info received (Bug#1029968: Info received (Bug#1029968: Info received (Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3

[Dr. David Alan Gilbert]

It's a bit messy...

a) The patch I bisected to is not the root cause of the bug; it just
triggers a ~9 year old bug in the v4l code - so this patch isn't going
to get changed.

b) The ~9 year old bug is in a particularly hairy piece of memory management
code  in v4l that I doubt anyone is going to fix.

c) The plan is all the drivers using that API are to either be retired
or rewritten using a new API; that's already been done for some of the
drivers and the bttv one is a few months out.  I'm not sure that's
any use to this version of Debian though.

d) The work arounds are:
  1) Disable iommu
  2) some v4l tools can use an mmap interface rather than the read(2)
interface; that seems to be OK.

Dave

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Info received (Bug#1029968: Info received (Bug#1029968: Info received (Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3

[Dr. David Alan Gilbert]

I sent this upstream report:
https://lore.kernel.org/linux-iommu/Y9qSwkLxeMpffZK%2F@gallifrey/T/#u
-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Info received (Bug#1029968: Info received (Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)))

[Dr. David Alan Gilbert]

Confirmed still happens on upstream 6.2.0-rc6
-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

[Dr. David Alan Gilbert]

* Diederik de Haas (didi.deb...@cknow.org) wrote:

> Thanks for that thorough analyses!

Thanks for the reply,

> If you're 'penguin42' on IRC,

Yep, that's me.

> then I'd suggest to present your findings to
> io...@lists.linux.dev as both the author and the reviewer are highly likely 
> subscribed to that list.
> 
> scripts/get_maintainer.pl drivers/iommu/dma-iommu.c
> scripts/get_maintainer.pl kernel/dma/Makefile
> 
> list them both and both results have also that ML in their result.

Yep, will do; I'm just going to try a 6.2rc as well just in case it's
got fixed very recently, and have a poke about in case I can see
any obvious cause now I know the change that triggered it.
I'll include the linux-media list as well since it's just as likely
that it's a fault on the v4l/bttv driver.

Dave

> HTH


-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Info received (Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0))

[Dr. David Alan Gilbert]

0() GS:9679efdc() 
knlGS:
[   78.988343] CS:  0010 DS:  ES:  CR0: 80050033
[   78.988346] CR2: bd7fc110 CR3: 00022ce02000 CR4: 06e0

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

[Dr. David Alan Gilbert]

bisected:
GOOD [37fcacb50be7071d146144a6c5c5bf0194b9a1cf] phy: PHY_FSL_LYNX_28G should 
depend on ARCH_LAYERSCAPE
BAD [f5ff79fddf0efecca538046b5cc20fb3ded2ec4f] dma-mapping: remove 
CONFIG_DMA_REMAP
GOOD [e62c17f0455a74b182ce6373e2777817256afaa1] MAINTAINERS: update maintainer 
list of DMA MAPPING BENCHMARK
GOOD [0fb3436b4b36cf69f4544385aa2bb8c5a4913509] sparc: Remove usage of the 
deprecated "pci-dma-compat.h" API
GOOD [fba09099c6e506608e05e08ac717bf34501f821b] media: v4l2-pci-skeleton: 
Remove usage of the deprecated "pci-dma-compat.h" API

dg@major:~/kernel/kernel-clone$ git bisect good
f5ff79fddf0efecca538046b5cc20fb3ded2ec4f is the first bad commit
commit f5ff79fddf0efecca538046b5cc20fb3ded2ec4f
Author: Christoph Hellwig 
Date:   Sat Feb 26 16:40:21 2022 +0100

dma-mapping: remove CONFIG_DMA_REMAP

That sounds like a believable cause given that it's IOMMU related
and device related.

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

[Dr. David Alan Gilbert]

Upstream 5.17 works
Upstream 5.18 fails

(with intel_iommu=on)

Let the bisect begin.

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

[Dr. David Alan Gilbert]

This is IOMMU related.

Upstream 6.1 and 5.18 *do* exhibit the bug, but only with intel_iommu=on
where as Debian seems to default it to on.

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

[Dr. David Alan Gilbert]

I built upstream kernels 5.18.0 and 6.1.0 and both of them work for me.
Which makes life much more painful to find.

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: bisecting we go...

[Dr. David Alan Gilbert]

Note an easier way to trigger the bug iscat /dev/vbi0 > /dev/null

   WORKS 
https://snapshot.debian.org/archive/debian/20220101T024315Z/pool/main/l/linux-signed-amd64/linux-image-5.10.0-9-amd64_5.10.70-1_amd64.deb
   linux-image-5.10.0-9-amd64_5.10.70-1_amd64.deb - kexecing in works

   WORKS 
https://snapshot.debian.org/archive/debian/20220101T024315Z/pool/main/l/linux-signed-amd64/linux-image-5.15.0-2-amd64_5.15.5-2_amd64.deb
   5.15.5-2

   FAILS 
https://snapshot.debian.org/archive/debian/20220701T034227Z/pool/main/l/linux-signed-amd64/linux-image-amd64_5.18.5-1_amd64.deb
 [   98.154835] BUG: unable to handle page fault for address: 
bc2480f4
[   98.154848] #PF: supervisor write access in kernel mode
[   98.154853] #PF: error_code(0x000b) - reserved bit violation

That 5.18 failure is a bit different, but the backtrace is similar;
somewhere between 5.18 it's changed from a BUG to a WARN but
back in 5.15 it just worked.

Dave

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)

[Dr. David Alan Gilbert]

   WORKS 
https://snapshot.debian.org/archive/debian/20220601T031637Z/pool/main/l/linux-signed-amd64/linux-image-5.17.0-1-amd64_5.17.3-1_amd64.deb
   5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1


So I think it's time to move upstream and bisect between 5.17 and 5.18

Dave

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#1029968: bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0

[David Alan Gilbert]

Package: src:linux
Version: 6.1.4-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

This was triggered when trying to capture video via a bt878 card using the
https://github.com/ali1234/vhs-teletext  script.  Note 'xawtv' is working
fine, so the card is generally happy.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I ran 'teletext record -d /dev/vbi0 > capture.vbi' from the above package
that triggers a read from vbi0; an strace shows:
[pid  6466] read(3, 0x27feb20, 65536)   = -1 ENOMEM (Cannot allocate memory)

and the WARN_ON in the dmesg

   * What was the outcome of this action?

a WARNING in the dmesg, see below; and the python script backtraced
with apparently an -ENOMEM; but there's plenty of RAM:
dg@major:~/vhs-teletext$ free -m
   totalusedfree  shared  buff/cache   available
Mem:7937 7892963   244847147
Swap:974   0 974

   * What outcome did you expect instead?
Happy gathered video.

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 6.1.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-1-amd64 
root=UUID=bce3fb05-edb4-4c73-b71d-86707031ffd1 ro intremap=nosid quiet

** Tainted: WI (2560)
 * kernel issued warning
 * workaround for bug in platform firmware applied

** Kernel log:
[ 5398.299139] kauditd_printk_skb: 15 callbacks suppressed
[ 5398.299142] audit: type=1400 audit(1675007035.570:27): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="libreoffice-oosplash" pid=4269 comm="apparmor_parser"
[ 5398.365964] audit: type=1400 audit(1675007035.638:28): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="libreoffice-senddoc" pid=4272 comm="apparmor_parser"
[ 5403.855538] audit: type=1400 audit(1675007041.126:29): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="libreoffice-soffice" 
pid=4275 comm="apparmor_parser"
[ 5403.879158] audit: type=1400 audit(1675007041.150:30): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="libreoffice-soffice//gpg" pid=4275 comm="apparmor_parser"
[ 5403.927433] audit: type=1400 audit(1675007041.198:31): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="libreoffice-xpdfimport" pid=4278 
comm="apparmor_parser"
[ 7268.952515] [ cut here ]
[ 7268.952518] WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 
__vmap_pages_range_noflush+0x3e0/0x4d0
[ 7268.952529] Modules linked in: rfkill qrtr binfmt_misc tuner_simple 
tuner_types tuner tda7432 tvaudio intel_powerclamp coretemp msp3400 kvm_intel 
bttv tveeprom kvm snd_hda_codec_via videobuf_dma_sg snd_hda_codec_generic 
videobuf_core irqbypass tea575x snd_hda_codec_hdmi ledtrig_audio sha512_ssse3 
sha512_generic snd_hda_intel videodev snd_intel_dspcfg snd_intel_sdw_acpi 
intel_cstate iTCO_wdt snd_hda_codec snd_bt87x intel_uncore mc snd_hda_core 
serio_raw intel_pmc_bxt snd_hwdep iTCO_vendor_support pcspkr i7core_edac 
watchdog snd_pcm snd_timer joydev snd soundcore acpi_cpufreq evdev sg 
firewire_sbp2 msr parport_pc ppdev lp parport fuse configfs efi_pstore 
ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi 
crc64_rocksoft crc64 crc_t10dif crct10dif_generic crct10dif_common hid_generic 
usbhid hid nouveau mxm_wmi video wmi i2c_algo_bit drm_display_helper cec 
rc_core ahci ata_generic drm_ttm_helper libahci pata_via ttm libata 
drm_kms_helper r8169 ehci_pci realtek
[ 7268.952592]  firewire_ohci psmouse ehci_hcd scsi_mod drm mdio_devres 
crc32c_intel usbcore libphy firewire_core i2c_i801 crc_itu_t i2c_smbus lpc_ich 
scsi_common usb_common button
[ 7268.952603] CPU: 6 PID: 6164 Comm: teletext Tainted: G  I
6.1.0-1-amd64 #1  Debian 6.1.4-1
[ 7268.952605] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./P55M Pro, BIOS P1.50 09/10/2009
[ 7268.952607] RIP: 0010:__vmap_pages_range_noflush+0x3e0/0x4d0
[ 7268.952610] Code: 48 48 83 c6 08 4d 39 d6 0f 85 39 fd ff ff 48 83 c4 58 31 
c0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 0f 0b e9 5f fc ff ff <0f> 0b b8 
f4 ff ff ff e9 bd fc ff ff 48 8b 4c 24 18 48 31 cf 48 21
[ 7268.952611] RSP: 0018:ac9307073b50 EFLAGS: 00010246
[ 7268.952613] RAX: 00023b68 RBX: 9ab8cbb7f480 RCX: eeafad0aae40
[ 7268.952614] RDX: 00011db42ab9 RSI:  RDI: 00011db42ab9
[ 7268.952615] RBP:  R08: 0476 R09: ac93072a
[ 7268.952617] 

No puedo conectarme a una red wifi

[Pedro David Monzón]

Buenas tardes: Tengo el siguiente problema: Mi Pc del programa JUANA 
MANSO con software linux debian, no detecta redes wifi. He buscado 
soluciones por internet pero solo funcionan temporalmente. Estoy 
sospechando que sea la comunicación entre el router y la tarjeta wifi. 
Algo parecido pasa con la impresora epson cuando imprimía por wireless. 
cuando cambiaba la dirección IP de la impresora, debía hacer el cambio 
manual en la PC para que se pudieran comunicar. Creo que puede ser algo 
de eso lo que está pasando entre el router y la pc con la conección 
wifi. En este momento estoy conectada a una red por un adaptador de 
cable ethernet.


Good afternoon: I have the following problem: My PC with the JUANA MANSO 
program with linux debian software does not detect Wi-Fi networks. I 
have searched for solutions on the internet but they only work 
temporarily. I am suspecting that it is the communication between the 
router and the wifi card. Something similar happens with the Epson 
printer when it printed wirelessly. when I changed the IP address of the 
printer, I had to make the change manually on the PC so they could 
communicate. I think it may be something like that that is happening 
between the router and the PC with the Wi-Fi connection. Right now I am 
connected to a network by an ethernet cable adapter.

Bug#919652: ath10k - QCA6174 - Surface Go - missing board data - fix .bin included extracted form official .msi

[David Kalnischkies]

Control: tags -1 + fixed-upstream

On Tue, 19 Jul 2022 23:46:17 +0300 Dmitry Baryshkov  
wrote:
> I'd suggest submitting the board files to the ath10k-firmware repo,
> which will then find it's way into linux-firmware.

fwiw this (or, well an update of the existing one) actually happened
already at the end of 2021 [0], but Debian hasn't seen an update so far.

[0] 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4d74f4dec175363fa24c95702dd86f477cef232c


With that board file wlan works even through the kernel (at least on
bullseye, not tested others) still complains about missing firmware:

ath10k_pci :01:00.0: firmware: failed to load 
ath10k/pre-cal-pci-:01:00.0.bin (-2)
fimeware_class: See https://wiki.debian.org/Firmware for information about 
missing firmware
ath10k_pci :01:00.0: firmware: failed to load 
ath10k/cal-pci-:01:00.0.bin (-2)
(followed by messages about successfully loading firmware-6.bin and board-2.bin)

The internet says these files are optional, which is somewhat confirmed
by having working wlan even without them, and I fail to find them – but
find some references to them in Debian forums as e.g. also d-i shows its
missing firmware message for those files (even if you have the firmware
cd variant, which is both annoying and confusing).

Not well versed in kernel code, but while [1] claims (at least for the
cal file) that it is optional and should print no warning it happily
still does anyhow? Or perhaps its ath10k_fetch_fw_file() doing a
firmware_request_nowarn() to then go on and ERR_PTR() on its own… [2]
Anyway, not really the point of this bugreport, just at the off chance
someone has an idea how to proceed on this somewhat related front.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c#n1227
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c#n882


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Re: Please update non-free firmware to the latest version

[David Liu]

Dear Maintainer,

It has been a while, Is there any update on this package? Please consider 
packaging it in Debian, It will support more new hardware, Thanks!

Best Regards,
David Liu

发件人: David Liu<mailto:wbsdty...@outlook.com>
发送时间: 2022年5月22日 14:08
收件人: sub...@bugs.debian.org<mailto:sub...@bugs.debian.org>
主题: Please update non-free firmware to the latest version

Package: firmware-linux-nonfree
Version: 20210818-1

Hello,
I have noticed the firmware-linux-nonfree has been no update since 20210818, in 
Linux Kernel git the latest release is 20220509 
(https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/), 
Please update it, Thanks.

Best Regards

Bug#1013728: mount: exfat filesystem mtime's are wrong

[David Christensen]

Package: src:linux
Version: 5.10.113-1
Severity: normal
X-Debbugs-Cc: dpchr...@holgerdanske.com

Dear Maintainer,

Please see:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001306


David



-- Package-specific info:
** Version:
Linux version 5.10.0-14-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.113-1 (2022-04-29)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-14-amd64 
root=UUID=ca7232ce-9982-46a0-b7b2-ed819ed6068e ro noresume

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: Latitude E6520
product_version: 01
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A22
board_vendor: Dell Inc.
board_name: 0J4TFW
board_version: A01

** Loaded modules:
exfat
uas
usb_storage
md4
sha512_ssse3
sha512_generic
cmac
nls_utf8
cifs
dns_resolver
fscache
libdes
vboxnetadp(OE)
vboxnetflt(OE)
vboxdrv(OE)
cpufreq_conservative
cpufreq_powersave
cpufreq_ondemand
cpufreq_userspace
zfs(POE)
zunicode(POE)
zzstd(OE)
zlua(OE)
zavl(POE)
icp(POE)
zcommon(POE)
znvpair(POE)
spl(OE)
intel_rapl_msr
snd_hda_codec_hdmi
intel_rapl_common
snd_hda_codec_idt
snd_hda_codec_generic
snd_hda_intel
snd_intel_dspcfg
soundwire_intel
x86_pkg_temp_thermal
intel_powerclamp
soundwire_generic_allocation
coretemp
iwldvm
snd_soc_core
kvm_intel
uvcvideo
snd_compress
mac80211
dell_rbtn
soundwire_cadence
videobuf2_vmalloc
videobuf2_memops
libarc4
mei_wdt
mei_hdcp
videobuf2_v4l2
dell_laptop
snd_hda_codec
kvm
videobuf2_common
ledtrig_audio
snd_hda_core
iwlwifi
irqbypass
videodev
dell_wmi
snd_hwdep
dell_smm_hwmon
dell_smbios
rapl
joydev
mc
soundwire_bus
intel_cstate
cfg80211
wmi_bmof
pcspkr
dcdbas
snd_pcm
sparse_keymap
at24
dell_wmi_descriptor
intel_uncore
serio_raw
iTCO_wdt
snd_timer
intel_pmc_bxt
snd
sg
iTCO_vendor_support
mei_me
watchdog
soundcore
rfkill
mei
evdev
dell_smo8800
ac
firewire_sbp2
parport_pc
ppdev
lp
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
hid_generic
sd_mod
sr_mod
t10_pi
cdrom
crc_t10dif
crct10dif_generic
usbhid
hid
i915
nouveau
mxm_wmi
crct10dif_pclmul
crct10dif_common
crc32_pclmul
ttm
crc32c_intel
ahci
i2c_algo_bit
libahci
firewire_ohci
ghash_clmulni_intel
drm_kms_helper
libata
e1000e
ehci_pci
sdhci_pci
firewire_core
cqhci
i2c_i801
ehci_hcd
sdhci
cec
ptp
aesni_intel
drm
usbcore
libaes
crypto_simd
mmc_core
scsi_mod
cryptd
psmouse
glue_helper
i2c_smbus
lpc_ich
crc_itu_t
pps_core
wmi
usb_common
battery
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller 
[1028:0494]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 
00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Dell 2nd Generation Core Processor Family Integrated 
Graphics Controller [1028:0494]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Dell 6 Series/C200 Series Chipset Family MEI Controller 
[1028:0494]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) [8086:1502] (rev 04)
DeviceName:  Onboard LAN
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville) 
[1028:0494]
   

Re: virtio_balloon regression in 5.19-rc3

[David Hildenbrand]

On 20.06.22 20:49, Ben Hutchings wrote:
> I've tested a 5.19-rc3 kernel on top of QEMU/KVM with machine type
> pc-q35-5.2.  It has a virtio balloon device defined in libvirt as:
> 
> 
>function="0x0"/>
> 
> 
> but the virtio_balloon driver fails to bind to it:
> 
> virtio_balloon virtio4: init_vqs: add stat_vq failed
> virtio_balloon: probe of virtio4 failed with error -5
> 

Hmm, I don't see any recent changes to drivers/virtio/virtio_balloon.c

virtqueue_add_outbuf() fails with -EIO if I'm not wrong. That's the
first call of virtqueue_add_outbuf() when virtio_balloon initializes.


Maybe something in generic virtio code changed?

-- 
Thanks,

David / dhildenb

Please update firmware-nonfree

[David Liu]

Hello,

The Linux-firmware-nonfree (https://tracker.debian.org/pkg/firmware-nonfree) 
has been no update about one year. Please update it.

I have submit a new bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011410.

Thanks!

Bug#956752: Bug 956752: linux-image-rt-amd64: No access to EFI variables possible with rt kernels

[David Müller]

Hi Diederik

Diederik de Haas schrieb am 07.06.22 um 15:11:


Is this still true with current kernels? At least with 5.10 from Stable, but
preferably with newer ones (evt from stable-backports).


Yes, the problem is still present (even in the latest backportss kernel)
as shown in the attachment.
root@debian:~# uname -a
Linux debian-test 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 
GNU/Linux
root@debian:~# ls -lR /sys/firmware/efi/
/sys/firmware/efi/:
total 0
-r--r--r--  1 root root 4096 Jun  8 14:48 config_table
drwxr-xr-x  2 root root0 Jun  8 14:47 efivars
-r--r--r--  1 root root 4096 Jun  8 14:48 fw_platform_size
-r--r--r--  1 root root 4096 Jun  8 14:48 fw_vendor
drwxr-xr-x  2 root root0 Jun  8 14:48 mok-variables
-r--r--r--  1 root root 4096 Jun  8 14:48 runtime
drwxr-xr-x 17 root root0 Jun  8 14:48 runtime-map
-r  1 root root 4096 Jun  8 14:48 systab

/sys/firmware/efi/efivars:
total 0
-rw-r--r-- 1 root root   85 Jun  8 14:47 
AMITSESetup-c811fa38-42c8-4579-a9bb-60e94eddfb34
-rw-r--r-- 1 root root8 Jun  8 14:47 
AcpiGlobalVariable-af9ffd67-ec10-488a-9dfc-6cbf5ee22c2e
-rw-r--r-- 1 root root  134 Jun  8 14:47 
Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  224 Jun  8 14:47 
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  409 Jun  8 14:47 
Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  122 Jun  8 14:47 
Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root6 Jun  8 14:47 
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root8 Jun  8 14:47 
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   12 Jun  8 14:47 
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   72 Jun  8 14:47 
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   72 Jun  8 14:47 
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   34 Jun  8 14:47 
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   34 Jun  8 14:47 
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root5 Jun  8 14:47 
ConsoleLock-368cda0d-cf31-4b9b-8cf6-e7d1bfff157e
-rw-r--r-- 1 root root5 Jun  8 14:47 
DebuggerSerialPortsEnabledVar-97ca1a5b-b760-4d1f-a54b-d19092032c90
-rw-r--r-- 1 root root   12 Jun  8 14:47 
DriverHealthCount-7459a7d4-6533-4480-bba7-79e25a4443c9
-rw-r--r-- 1 root root   12 Jun  8 14:47 
DriverHlthEnable-0885f288-418c-4be1-a6af-8bad61da08fe
-rw-r--r-- 1 root root   34 Jun  8 14:47 
ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   34 Jun  8 14:47 
ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root8 Jun  8 14:47 
FPDT_Variable-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   12 Jun  8 14:47 
GnvsAreaVar-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   12 Jun  8 14:47 
HobRomImage-dde1bc72-d45e-4209-ab85-14462d2f5074
-rw-r--r-- 1 root root   48 Jun  8 14:47 
IccAdvancedSetupDataVar-7b77fb8b-1e0d-4d7e-953f-3980a261e077
-rw-r--r-- 1 root root7 Jun  8 14:47 
Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root7 Jun  8 14:47 
LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   22 Jun  8 14:47 
LegacyDevOrder-a56074db-65fe-45f7-bd21-2d2bdd8e9652
-rw-r--r-- 1 root root   30 Jun  8 14:47 
MeBiosExtensionSetup-1bad711c-d451-4241-b1f3-8537812e0c70
-rw-r--r-- 1 root root8 Jun  8 14:47 
MemCeil.-40312829-7891-4abd-b200-0c541b061939
-rw-r--r-- 1 root root   68 Jun  8 14:47 
MemoryTypeInformation-4c19049f-4137-4dd3-9c10-8b97a83ffdfa
-rw-r--r-- 1 root root8 Jun  8 14:47 
MonotonicCounter-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root 3052 Jun  8 14:47 
MrcS3Resume-87f22dcb-7304-4105-bb7c-317143ccc23b
-rw-r--r-- 1 root root5 Jun  8 14:47 
NBGopPlatformData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root   17 Jun  8 14:47 
NBPlatformData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root8 Jun  8 14:47 
NetworkStackVar-d1405d16-7afc-4695-bb12-41459d3695a2
-rw-r--r-- 1 root root  140 Jun  8 14:47 
NvRamSpdMap-717fc150-abd9-4614-8015-0b3323eab95c
-rw-r--r-- 1 root root   28 Jun  8 14:47 
OA3MSDMvariable-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   14 Jun  8 14:47 
OemCpuData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root   22 Jun  8 14:47 
OldLegacyDevOrder-a56074db-65fe-45f7-bd21-2d2bdd8e9652
-rw-r--r-- 1 root root7 Jun  8 14:47 
PNP0400_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031
-rw-r--r-- 1 root root   13 Jun  8 14:47 
PNP0400_0_VV-560bf58a-1e0d-4d7e-953f-2980a261e031
-rw-r--r-- 1 root root7 Jun  8 14:47 
PNP0501_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031
-rw-r--r-- 1 root root   13 Jun  8 14:47 
PNP0501_0_VV-560bf58a-1e0d-4d7e-953f-2980a261e031
-rw-r--r-- 1 root root7 Jun  8 14:47 
PNP0501_1_NV-560bf58a-1e0d-4d7e-953f-2980a261e031
-rw-r--r-- 1 root root   13 Jun  8 14:47 

Bug#1010333: linux-image-4.9.0-18-amd64: USB keyboard and mouse erratic behavior and USB ports stop working

[David Christensen]

Package: src:linux
Version: 4.9.303-1
Severity: important

Dear Maintainer,

The USB keyboard and mouse have been intermittently misbehaving on
Debian 9, 10, and 11 for over a year:

- Random mouse and/or keyboard event storms when I move the mouse.
- Repeating keys when no key is pressed.
- Keyboard and mouse stop functioning completely.

I have been discussing these symptoms on the debian-user mailing list:

https://www.mail-archive.com/debian-user@lists.debian.org/msg781396.html

Tonight, I was erasing USB flash drives.  After a several drives, I
inserted another drive and it was not recognized.  I removed it, and
tried again -- no help.  I rebooted.  I then continued.  When I
insert a USB flash drive into a USB 3.0 port, both ports on that
chipset stopped working.

I do not have sudo configured.  I have pasted dmesg(1) output at the
end of this bug report.

David



-- Package-specific info:
** Version:
Linux version 4.9.0-18-amd64 (debian-kernel@lists.debian.org) (gcc version 
6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.303-1 (2022-03-07)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-18-amd64 
root=UUID=9e15b950-3239-41ee-9f35-afb6e515d63a ro noresume

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: 
product_name: 
product_version: 
chassis_vendor: 
chassis_version: 
bios_vendor: Intel Corp.
bios_version: SWQ6710H.86A.0068.2017.0601.1423
board_vendor: Intel Corporation
board_name: DQ67SW
board_version: AAG12527-310

** Loaded modules:
uas
usb_storage
nls_utf8
cifs
sha256_ssse3
cmac
md4
des_generic
arc4
dns_resolver
fscache
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
cpufreq_userspace
cpufreq_powersave
cpufreq_conservative
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
coretemp
iTCO_wdt
iTCO_vendor_support
snd_hda_codec_hdmi
kvm_intel
kvm
snd_hda_codec_realtek
snd_hda_codec_generic
evdev
irqbypass
i915
intel_cstate
intel_uncore
intel_rapl_perf
lpc_ich
pcspkr
snd_hda_intel
serio_raw
video
mfd_core
snd_hda_codec
snd_hda_core
snd_hwdep
snd_pcm
drm_kms_helper
sg
snd_timer
snd
drm
soundcore
mei_me
i2c_algo_bit
mei
shpchp
button
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
mbcache
algif_skcipher
af_alg
dm_crypt
dm_mod
sr_mod
cdrom
sd_mod
hid_generic
usbhid
hid
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
ata_generic
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
psmouse
xhci_pci
ahci
firewire_ohci
ehci_pci
libahci
i2c_i801
xhci_hcd
i2c_smbus
firewire_core
ehci_hcd
crc_itu_t
libata
e1000e
usbcore
ptp
usb_common
pps_core
scsi_mod

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Intel Corporation 2nd Generation Core Processor Family DRAM 
Controller [8086:2008]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snb_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2008]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Intel Corporation 6 Series/C200 Series Chipset Family MEI 
Controller [8086:2008]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:16.2 IDE interface [0101]: Intel Corporation 6 Series/C200 Series Chipset 
Family IDE-r Controller [8086:1c3c] (rev 04) (prog-if 85 [Master SecO PriO])
Subsystem: Intel Corporation 6 Series/C200 Series Chipset 

Bug#1009618: Firmware "beige-goby*", for Radeon RX6500XT, missing from package

[David Steele]

Package: firmware-amd-graphics

Version: 20210818-1

Severity: Normal

thanks


The RX6500XT was released in January. It requires the "beige-goby" line 
of firmware files, which were added upstream September of last year [1].


A refresh of the package is needed.


[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=62fd279be67cd6e46aa33a342579f6356ea60634

Bug#1007799: Backport to bullseye

[David Schiller]

Hi!

Any chance we can get this into the bullseye kernel?

Best regards,
David


signature.asc
Description: This is a digitally signed message part

Bug#1007864: linux-source-4.19: Kernel compilation error when CONFIG_BPF_SYSCALL not set

[David McIntosh]

Package: linux-source-4.19
Version: 4.19.232-1

When attempting to build the kernel without enabling CONFIG_BPF_SYSCALL I
run into the following compilation error:

  CC  arch/x86/kernel/cpu/bugs.o
arch/x86/kernel/cpu/bugs.c: In function 'spectre_v2_select_mitigation':
arch/x86/kernel/cpu/bugs.c:973:34: error: implicit declaration of function
'unprivileged_ebpf_enabled' [-Werror=implicit-function-declaration]
  if (mode == SPECTRE_V2_EIBRS && unprivileged_ebpf_enabled())
  ^
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:309: arch/x86/kernel/cpu/bugs.o] Error
1
make[2]: *** [scripts/Makefile.build:549: arch/x86/kernel/cpu] Error 2
make[1]: *** [scripts/Makefile.build:549: arch/x86/kernel] Error 2
make: *** [Makefile:1060: arch/x86] Error 2

The issue appears to be the security patches applied to include/linux/bpf.h.

In the upstream version of the source the unprivileged_ebpf_enabled
function has a 2nd definition that is included when CONFIG_BPF_SYSCALL is
not set:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/include/linux/bpf.h?id=v4.19.234#n653

In the debian version of this file the 2nd definition is present but is
omitted unless CONFIG_BPF_SYSCALL is set so it's never included.

Bug#1006791: /lib/modules/5.10.0-11-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko: Multiple serious issues with my Intel Centrino Wireless-N 1000 [Condor Peak] wi-fi card

[David Calman]

Package: src:linux
Version: 5.10.92-1
Severity: important
File: 
/lib/modules/5.10.0-11-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
X-Debbugs-Cc: alt.people.davidcal...@gmail.com

Dear Maintainer,


   * What led up to the situation?
I upgraded to bullseye
   * What exactly did you do (or not do) that was effective (or ineffective)?
I fiddled with the modprobe options (enabling TX AMPDU or whatever it's called, 
later also enabling software
crypto and disabling active BT "coexistence"). I also frequently disable power 
management for the Wi-Fi card.
   * What was the outcome of this action?
I still have to reenter the WPA passphrase a lot. Throughput and latency are 
still terribad (over 1000 ping
to my router!) and the card often goes down to a 1Mbps link speed.
   * What outcome did you expect instead?
I expect a passable Wi-Fi experience from any operating system given I have an 
802.11n card. I've had better
experiences with an 802.11g card and Windows XP.



-- Package-specific info:
** Version:
Linux version 5.10.0-11-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.92-1 (2022-01-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-11-amd64 
root=UUID=8437935f-671c-43d1-8b96-67fd26904688 ro quiet

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[11915.742913] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[11915.745893] wlp3s0: authenticated
[11915.746636] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 1/3)
[11915.767868] wlp3s0: RX AssocResp from 1a:59:c0:31:cb:d2 (capab=0x1431 
status=0 aid=5)
[11915.777158] wlp3s0: associated
[12017.521936] wlp3s0: authenticate with 1a:59:c0:31:cb:d2
[12017.525769] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[12017.637704] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 2/3)
[12017.640887] wlp3s0: authenticated
[12017.641632] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 1/3)
[12017.661839] wlp3s0: RX AssocResp from 1a:59:c0:31:cb:d2 (capab=0x1431 
status=0 aid=5)
[12017.668060] wlp3s0: associated
[12091.285409] wlp3s0: authenticate with 1a:59:c0:31:cb:d2
[12091.289889] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[12091.396031] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 2/3)
[12091.398533] wlp3s0: authenticated
[12091.399960] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 1/3)
[12091.427283] wlp3s0: RX AssocResp from 1a:59:c0:31:cb:d2 (capab=0x1431 
status=0 aid=5)
[12091.455113] wlp3s0: associated
[12186.373615] wlp3s0: authenticate with 1a:59:c0:31:cb:d2
[12186.377287] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[12186.487209] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 2/3)
[12186.499899] wlp3s0: authenticated
[12186.503072] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 1/3)
[12186.520495] wlp3s0: RX AssocResp from 1a:59:c0:31:cb:d2 (capab=0x1431 
status=0 aid=5)
[12186.530797] wlp3s0: associated
[12198.597884] wlp3s0: disassociated from 1a:59:c0:31:cb:d2 (Reason: 
2=PREV_AUTH_NOT_VALID)
[12199.169285] wlp3s0: authenticate with 1a:59:c0:31:cb:d2
[12199.175163] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[12199.198741] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 2/3)
[12199.220054] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 3/3)
[12199.242063] wlp3s0: authentication with 1a:59:c0:31:cb:d2 timed out
[12205.599065] wlp3s0: authenticate with 1a:59:c0:31:cb:d2
[12205.601989] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[12205.606863] wlp3s0: authenticated
[12205.607821] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 1/3)
[12205.634387] wlp3s0: RX AssocResp from 1a:59:c0:31:cb:d2 (capab=0x1431 
status=0 aid=5)
[12205.653125] wlp3s0: associated
[12214.074606] wlp3s0: deauthenticating from 1a:59:c0:31:cb:d2 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[12214.115631] iwlwifi :03:00.0: Radio type=0x0-0x0-0x3
[12214.179464] iwlwifi :03:00.0: Radio type=0x0-0x0-0x3
[12215.146818] iwlwifi :03:00.0: Radio type=0x0-0x0-0x3
[12215.211806] iwlwifi :03:00.0: Radio type=0x0-0x0-0x3
[12215.714556] wlp3s0: authenticate with 1a:59:c0:31:cb:d2
[12215.718040] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[12215.828090] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 2/3)
[12215.846615] wlp3s0: authenticated
[12215.848058] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 1/3)
[12215.886409] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 2/3)
[12215.930001] wlp3s0: RX AssocResp from 1a:59:c0:31:cb:d2 (capab=0x1431 
status=0 aid=5)
[12215.944982] wlp3s0: associated
[12215.990218] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[12228.022021] wlp3s0: disassociated from 1a:59:c0:31:cb:d2 (Reason: 
2=PREV_AUTH_NOT_VALID)
[12228.653350] wlp3s0: authenticate with 1a:59:c0:31:cb:d2
[12228.657174] wlp3s0: send auth to 1a:59:c0:31:cb:d2 (try 1/3)
[12228.672359] wlp3s0: authenticated
[12228.676489] wlp3s0: associate with 1a:59:c0:31:cb:d2 (try 1/3)
[12228.705944] wlp3s0: 

Bug#1005972: sourced functions when run from set -e shells are suprising

[David]

On Sat, 19 Feb 2022 at 00:21, Thomas Stewart  wrote:

> I think all functions that are
> sourced should be audited to handle "set -e" and all initramfs-tools
> eventually modified to use "set -e".

Dear Maintainer,

There is a view among shell-script experts that adding "set -e"
anywhere is to be discouraged [1][2][3].

So I suggest that in any situation where remediation is required,
"set -e" should be removed, not added.

"set -e" is a fantasy to have "automatic" error handling in shell
scripts, but it breaks in all kinds of non-naive situations. The best
practice for shell scripts is to actually handle errors where they
occur:
 command || exit 1
This is not difficult, if that behaviour is desired.

It would be better if Debian policy was modified to be clearer about this.

Kind regards
David

[1] https://lists.gnu.org/archive/html/help-bash/2017-05/msg00020.html
[2] http://mywiki.wooledge.org/BashFAQ/105
[3] https://fvue.nl/wiki/Bash:_Error_handling

Bug#1001359: linux-image-5.10.0-9-amd64: exfat filesystem mtime's are wrong

[David Christensen]

Package: src:linux
Version: 5.10.70-1
Severity: normal
X-Debbugs-Cc: dpchr...@holgerdanske.com

Dear Maintainer,

Please see fowarded message, below.

David



 Forwarded Message 
Subject: Re: Bug#1001306: mount: exfat filesystem mtime's are wrong
Date: Wed, 8 Dec 2021 18:13:06 +0100
From: Chris Hofstaedtler 
To: David Christensen , 1001...@bugs.debian.org

Hello,

* David Christensen  [211208 05:12]:
> Package: mount
> Version: 2.36.1-8
> Severity: normal
> X-Debbugs-Cc: dpchr...@holgerdanske.com
> 
> Dear Maintainer,
> 
> Please see:
> 
> https://www.mail-archive.com/debian-user@lists.debian.org/msg776840.html

Sorry, I have absolutely no idea why this should be a bug in the
mount program. mount(1) is not involved in processing timestamps of
filesystems.

Please find another package (maybe the kernel?) that is involved and
reassign the bug there.

Best,
Chris



-- Package-specific info:
** Version:
Linux version 5.10.0-9-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.70-1 (2021-09-30)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 
root=UUID=94ca25af-1993-445a-a5ed-2c2e73d57588 ro noresume quiet

** Not tainted

** Kernel log:
[   33.904211] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[   33.916910] dell_laptop: Using i8042 filter function for receiving events
[   33.921211] Intel(R) Wireless WiFi driver for Linux
[   33.921441] iwlwifi :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   33.974865] iwlwifi :03:00.0: firmware: direct-loading firmware 
iwlwifi-6000g2a-6.ucode
[   33.975111] iwlwifi :03:00.0: loaded firmware version 18.168.6.1 
6000g2a-6.ucode op_mode iwldvm
[   33.975163] iwlwifi :03:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[   33.975188] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   34.004011] audit: type=1400 audit(1639014946.659:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=675 comm="apparmor_parser"
[   34.004016] audit: type=1400 audit(1639014946.659:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=669 comm="apparmor_parser"
[   34.004019] audit: type=1400 audit(1639014946.659:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=672 
comm="apparmor_parser"
[   34.004023] audit: type=1400 audit(1639014946.659:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=676 
comm="apparmor_parser"
[   34.004026] audit: type=1400 audit(1639014946.659:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=676 comm="apparmor_parser"
[   34.004029] audit: type=1400 audit(1639014946.663:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=674 comm="apparmor_parser"
[   34.005386] audit: type=1400 audit(1639014946.663:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=671 
comm="apparmor_parser"
[   34.005391] audit: type=1400 audit(1639014946.663:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=671 
comm="apparmor_parser"
[   34.005394] audit: type=1400 audit(1639014946.663:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=671 
comm="apparmor_parser"
[   34.008237] audit: type=1400 audit(1639014946.667:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/libexec/ibus-engine-hangul" pid=679 comm="apparmor_parser"
[   34.107395] Adding 976892k swap on /dev/mapper/sda2_crypt.  Priority:-2 
extents:1 across:976892k SSFS
[   34.226861] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_FHD 
(05ca:181c)
[   34.231212] input: Laptop_Integrated_Webcam_FHD: I as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input13
[   34.231269] usbcore: registered new interface driver uvcvideo
[   34.231270] USB Video Class driver (1.1.1)
[   34.267591] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[   34.267594] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[   34.267596] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[   34.267598] iwlwifi :03:00.0: Detected Intel(R) Cent

Bug#991685: please add rtl_bt/rtl8761b_fw.bin and friends

[David Schmitt]

Apologies for the multiple messages. I coulda had that all in one:

Here's the commit adding the files to upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtl_bt?id=7118987b2f7aff733573121607bc9640a4880296

On Fri, 30 Jul 2021 at 10:47, David Schmitt  wrote:
>
> Reading through the docs a bit, I realize that this request should go
> to the linux-firmware.git repo instead.

Bug#991685: please add rtl_bt/rtl8761b_fw.bin and friends

[David Schmitt]

Reading through the docs a bit, I realize that this request should go
to the linux-firmware.git repo instead.

Bug#991685: please add rtl_bt/rtl8761b_fw.bin and friends

[David Schmitt]

Package: firmware-realtek
Version: 20210315-3

To support the RTL8761B bluetooth chips from realtek, please add the
files as described in
https://www.raspberrypi.org/forums/viewtopic.php?t=294634 .

I can confirm that it enables the device for me.

Thanks in advance,

David

$ sha256sum /lib/firmware/rtl_bt/rtl8761b_*
~david/Downloads/20201202_mpow_BH456A_driver+for+Linux.7z
6ddeb15f23588053e00cb08d25588bd7cf98d60fa93d9478efcef4ae8064a7ac
/lib/firmware/rtl_bt/rtl8761b_config.bin
0dbb791141172660fb355db75d8015610efc725e620a2424264184159103c6aa
/lib/firmware/rtl_bt/rtl8761b_fw.bin
25de05daaecbc698504e3b87f14cf24dd6cec97551ce3f2b720f5e559919d98b
/home/david/Downloads/20201202_mpow_BH456A_driver+for+Linux.7z

Re: Bug#989539: apt upgrade reports "possibly missing firmware" causing undue concern.

[David Kalnischkies]

Control: reassign -1 initramfs-tools-core

Hi,

On Sun, Jun 06, 2021 at 06:00:52PM -0400, ? wrote:
> This is a known issue that when users perform an apt-upgrade that
> upgrades system/kernel components.
> 
> Actual Result: "Possibly missing firmware ..."  E.g. i915
> Expected Result: No messages that firmware may be missing.

I don't know if more than it already checks is technically possible or
if your suggestion would help (I don't have the slightest idea from
which year the hardware is I am using or the exact model name without
looking it up, so adding that info would confuse me just as much if not
more I guess…).

In either case apt has and can not do anything about it. It is output
produced by one of the packages which are installed/upgraded. In this
case a codesearch over Debian suggests one of the methods from
/usr/share/initramfs-tools/hook-functions which is contained in
initramfs-tools-core.

I am therefore reassign this bug to them.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#986124: linux-image-4.19.0-16-amd64: Version 4.19.0-16 breaks lirc and vdr

[David Ruetti]

Package: src:linux
Version: 4.19.181-1
Severity: important

Upgraded to latest packages and with Kernel 4.19.0-16 lirc stopped working. It 
cannot find /sys/class/rc and fills every second syslog:

Mar 30 00:09:45 supply lircd[296]: lircd-0.10.1[296]: Error: No /sys/class/rc/ 
devices found
Mar 30 00:09:45 supply lircd-0.10.1[296]: Error: No /sys/class/rc/ devices found

Booting into 4.19.0-14, lirc work as expected. Breaking of lirc presumably 
affects vdr (vdr_2.4.1-4~etobi2_amd64.deb / packages.e-tobi.net 
vdr-experimental buster) as well. Vdr is working as expected on 4.19.0-14 
kernel.

root@iris:~# cat /etc/lirc/lircd.conf.d/devinput.lircd.conf
# Rename to devinput.lircd.dist if not using devinput driver
# Re-generate for current kernel using lirc-make-devinput
#
# Generated by lirc-make-devinput on 4.19.0-14-amd64
# Date: Sun Mar 21 14:29:15 UTC 2021

begin remote
namedevinput-64
bits16
eps 30
aeps100
pre_data_bits   16
pre_data0x0001
post_data_bits  32
post_data   0x0001
gap 132799
toggle_bit  0
driver  devinput

begin codes
[...]


-- Package-specific info:
** Version:
Linux version 4.19.0-16-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.181-1 (2021-03-19)

** Command line:
root=/dev/xvda1 ro module.sig_enforce=1 quiet

** Not tainted

** Kernel log:
[0.767391] PTP clock support registered
[0.767398] EDAC MC: Ver: 3.0.0
[0.767559] PCI: System does not support PCI
[0.768390] clocksource: Switched to clocksource xen
[0.780534] VFS: Disk quotas dquot_6.6.0
[0.780554] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[0.780586] hugetlbfs: disabling because there are no supported hugepage 
sizes
[0.780674] AppArmor: AppArmor Filesystem Enabled
[0.780693] pnp: PnP ACPI: disabled
[0.782345] NET: Registered protocol family 2
[0.782528] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 
bytes)
[0.782541] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[0.782588] TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
[0.782607] TCP: Hash tables configured (established 4096 bind 4096)
[0.782647] UDP hash table entries: 256 (order: 1, 8192 bytes)
[0.782653] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[0.782703] NET: Registered protocol family 1
[0.782709] NET: Registered protocol family 44
[0.782712] PCI: CLS 0 bytes, default 64
[0.782759] Unpacking initramfs...
[0.877237] Freeing initrd memory: 87484K
[0.878003] Initialise system trusted keyrings
[0.878018] Key type blacklist registered
[0.878090] workingset: timestamp_bits=40 max_order=17 bucket_order=0
[0.879648] zbud: loaded
[1.129067] Key type asymmetric registered
[1.129069] Asymmetric key parser 'x509' registered
[1.129090] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
247)
[1.129123] io scheduler noop registered
[1.129124] io scheduler deadline registered
[1.129177] io scheduler cfq registered (default)
[1.129178] io scheduler mq-deadline registered
[1.129305] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[1.129663] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[1.130027] Linux agpgart interface v0.103
[1.130054] AMD IOMMUv2 driver by Joerg Roedel 
[1.130054] AMD IOMMUv2 functionality not available on this system
[1.130163] i8042: PNP: No PS/2 controller found.
[1.130163] i8042: Probing ports directly.
[1.130984] i8042: No controller found
[1.131038] mousedev: PS/2 mouse device common for all mice
[1.131089] ledtrig-cpu: registered to indicate activity on CPUs
[1.131384] NET: Registered protocol family 10
[1.148036] Segment Routing with IPv6
[1.148070] mip6: Mobile IPv6
[1.148074] NET: Registered protocol family 17
[1.148109] mpls_gso: MPLS GSO support
[1.148205] mce: Using 2 MCE banks
[1.148228] sched_clock: Marking stable (1147023133, 187741)->(1150917806, 
-3706932)
[1.148522] registered taskstats version 1
[1.148523] Loading compiled-in X.509 certificates
[1.205521] Loaded X.509 cert 'Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
[1.205539] Loaded X.509 cert 'Debian Secure Boot Signer 2021 - linux: 
4b6ef5abca669825178e052c84667ccbc0531f8c'
[1.205565] zswap: loaded using pool lzo/zbud
[1.205694] AppArmor: AppArmor sha1 policy hashing enabled
[1.205913] xenbus_probe_frontend: Device with no driver: device/vbd/51713
[1.205914] xenbus_probe_frontend: Device with no driver: device/vbd/51714
[1.205914] xenbus_probe_frontend: Device with no driver: device/vif/0
[1.205939] hctosys: unable to open rtc device (rtc0)
[1.207650] Freeing unused kernel image 

Bug#924690: Schöne Grüße.

[David Pearl]

Guten Tag, ich bin David Pearl. Ich möchte etwas mit Ihnen besprechen.
Bitte kontaktieren Sie mich so schnell wie möglich.

Bug#962788:

[David Roundy]

I'm running into this bug also, and would love to know how to work around
it.

David Roundy

Bug#976644: linux-image-4.19.0-13-amd64: apcupsd usb connection with UPS fails since upgrade to 4.19.0-13-amd64

[David Garabana Barro]

Package: src:linux
Version: 4.19.160-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Upgrade to linux-image-4.19.0-13-amd64 makes apcupsd unable to
contact UPS through USB
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Downgrading to 4.19.0-12 makes apcupsd contact UPS again
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.19.0-13-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-13-amd64 root=/dev/mapper/system_vg-root_lv ro quiet

** Not tainted

** Kernel log:

[0.00] Linux version 4.19.0-13-amd64 (debian-kernel@lists.debian.org) 
(gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.19.0-13-amd64 
root=/dev/mapper/system_vg-root_lv ro quiet
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xbff9] usable
[0.00] BIOS-e820: [mem 0xbffa-0xbffadfff] ACPI data
[0.00] BIOS-e820: [mem 0xbffae000-0xbffd] ACPI NVS
[0.00] BIOS-e820: [mem 0xbffe-0xbfff] reserved
[0.00] BIOS-e820: [mem 0xff70-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00013fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.3 present.
[0.00] DMI: System manufacturer System Product Name/A8R32-MVP Deluxe, 
BIOS 0701 03/03/2007
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 2205.048 MHz processor
[0.007363] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.007366] e820: remove [mem 0x000a-0x000f] usable
[0.018480] AGP: No AGP bridge found
[0.018583] last_pfn = 0x14 max_arch_pfn = 0x4
[0.018588] MTRR default type: uncachable
[0.018589] MTRR fixed ranges enabled:
[0.018591]   0-9 write-back
[0.018592]   A-E uncachable
[0.018594]   F-F write-protect
[0.018594] MTRR variable ranges enabled:
[0.018596]   0 base 00 mask FF write-back
[0.018598]   1 base 01 mask FFC000 write-back
[0.018600]   2 base 00C000 mask FFC000 uncachable
[0.018600]   3 disabled
[0.018601]   4 disabled
[0.018602]   5 disabled
[0.018602]   6 disabled
[0.018603]   7 disabled
[0.019120] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.019185] e820: update [mem 0xc000-0x] usable ==> reserved
[0.019194] last_pfn = 0xbffa0 max_arch_pfn = 0x4
[0.024428] found SMP MP-table at [mem 0x000ff780-0x000ff78f]
[0.056784] RAMDISK: [mem 0x34a0d000-0x364fdfff]
[0.056794] ACPI: Early table checksum verification disabled
[0.057190] ACPI: RSDP 0x000FAD00 24 (v02 ACPIAM)
[0.057194] ACPI: XSDT 0xBFFA0100 44 (v01 A_M_I_ OEMXSDT  
03000703 MSFT 0097)
[0.057201] ACPI: FACP 0xBFFA0290 F4 (v03 A_M_I_ OEMFACP  
03000703 MSFT 0097)
[0.057208] ACPI: DSDT 0xBFFA0430 006E70 (v01 A0466  A0466001 
0001 INTL 02002026)
[0.057212] ACPI: FACS 0xBFFAE000 40
[0.057215] ACPI: FACS 0xBFFAE000 40
[0.057218] ACPI: APIC 0xBFFA0390 5C (v01 A_M_I_ OEMAPIC  
03000703 MSFT 0097)
[0.057221] ACPI: MCFG 0xBFFA03F0 3C (v01 A_M_I_ OEMMCFG  
03000703 MSFT 0097)
[0.057225] ACPI: OEMB 0xBFFAE040 7B (v01 A_M_I_ AMI_OEM  
03000703 MSFT 0097)
[0.057238] ACPI: Local APIC address 0xfee0
[0.057370] Scanning NUMA topology in Northbridge 24
[0.057417] No NUMA configuration found
[0.057418] Faking a node at [mem 0x-0x00013fff]
[0.057424] NODE_DATA(0) allocated [mem 0x13fff8000-0x13fffcfff]
[0.057492] Zone ranges:
[0.057493]   DMA  [mem 0x1000-0x00ff]
[0.057495]   DMA32[mem 0x0100-0x]
[0.057496]   Normal   [mem 0x0001-0x00013fff]
[0.057498]   Device   empty
[0.057499] Movable zone start for each node
[0.057500] Early memory node ranges
[0.057502]   node   0: [mem 0x1000-0x0009efff]
[0.057503]   node   0: [mem 

Bug#970699: linux: Enable amd_energy driver

[David Schiller]

On Fri, 2020-11-13 at 14:56 +0100, Salvatore Bonaccorso wrote:
> If we are going to enable this for our builds, then we might need to
> check that https://bugzilla.redhat.com/show_bug.cgi?id=1897402 is not
> opened accordingly.
> 
> This relates to
> 
> https://support.lenovo.com/lu/uk/product_security/LEN-50481
> 
> and probably the reason for
> 
> https://lore.kernel.org/stable/238e3cf7-582f-a265-5300-9b4494810...@roeck-us.net/T/#m11dee15be8c238d8858aafdf1a57e9ad7e0b9670

Thanks for the response!

I skimmed through the paper covering the CVE and they mostly focused on Intel
SGX and only touched upon AMD briefly. They did there measurements with disabled
boost and fixed frequency, a configuration that no system in the wild actually
uses. Moreover the energy counters are exposed as an MSR, so in my opinion this
is more of a CPU-level bug. 

Personally I feel like recent security efforts are often crippling usability for
negligible gains.
 
Just my two cents!



signature.asc
Description: This is a digitally signed message part

Bug#970699: linux: Enable amd_energy driver

[David Schiller]

Source: linux
Severity: wishlist
X-Debbugs-Cc: david.schil...@gmx.at

Hi!

Could you please enable CONFIG_SENSORS_AMD_ENERGY as a module. This
provides RAPL energy monitoring on AMD Zen processors and has been
available since kernel 5.8.

Thanks in advance!

Dave


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-1-amd64 (SMP w/24 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#964812: closed by Debian FTP Masters (reply to Ben Hutchings ) (Bug#964812: fixed in linux 5.8.3-1~exp1)

[David Awogbemila]

> -- Forwarded message --
> From: David Awogbemila 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Fri, 10 Jul 2020 18:21:14 +
> Subject: linux: Pulling Google Compute Engine Virtual Ethernet Driver into 
> Debian
> Source: linux
> Severity: wishlist
>
> Dear Maintainer,
>
> Google would like to have its cloud networking driver, the Google
> Compute Engine Virtual Ethernet driver (GVE) pulled into Debian
> releases.
>
> This driver has been accepted into the upstream Linux kernel
> since version 5.2:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/ethernet/google?h=v5.4.46).
>
> I understand that the first step towards this is enabling the driver
> in Debian's unstable and testing releases so I have attached the
> relevant Kconfig file for GVE to this bug report.
>
> GVE can be configured in the kernel's config file with:
>
> CONFIG_GVE=m
> CONFIG_NET_VENDOR_GOOGLE=y
>
> We're also looking to have the driver backported into Debian 10
> source.
>
> Please let me know other steps we need to take to accomplish the goals
> listed above.
>
> Best
> David
>
> -- System Information:
> Debian Release: 10.4
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.19.0-9-cloud-amd64 (SMP w/16 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

Thank you for the update! Just to confirm, does this mean the driver
will be available to future versions on Debian
(i.e. have the config options set so that the driver is available in
Debian Images)?
If so, what versions of Debian will this affect? (I'm guessing the
ones starting with linux 5.8?)
Thanks.
David

Bug#964118: Bug corrected in 5.7.0-2

[Erwan David]

The bug is corrected in 5.7.0-2

Bug#955329: linux-image-4.9.0-12-amd64 breaks LUKS root

[David Christensen]

On 2020-07-26 18:15, David wrote:

On Mon, 27 Jul 2020 at 09:47, David Christensen
 wrote:

On 2020-03-30 02:58, deloptes wrote:

David Christensen wrote:



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955329


I updated/ upgraded the system today and whatever broke LUKS when I
'apt-get dist-upgrade' and installed kernel 4.9.0-12-amd64 several
months ago now breaks LUKS when I try to boot the kernel that I have
been using prior and since -- 4.9.0-11-amd64.  Fortunately, LUKS still
works with my oldest available kernel, 4.9.0-9-amd64.


lsinitramfs will give you the content of the initrd


Any other suggestions?


Hi, just a few thoughts from a dumb onlooker ...

I notice that your bug 955329 is filed against the linux-image
package around 4 months ago, and that there has been no reply from the
maintainers.

Looking around for similar bugs, I found [1] this comment by one of
the maintainers:


LUKS volumes are recognised and set uo by userland, so are you sure
this is due to the kernel upgrade?


So maybe it's not helpful to focus on the kernel, and I wonder if you
would get a response or debugging assistance if you were to report
this against the cryptsetup-initramfs package.

Another suggestion, although I am far from an expert in these matters,
I wonder if (per man initramfs-tools) you have tried using a kernel
boot parameter 'break=premount' and then see what happens if you try
to run your cryptsetup command in the initramfs shell.

For example, I would try:
(initramfs) blkid
(initramfs) cryptsetup open /dev/whatever/blkid/says somename
(initramfs) blkid

and expect to see /dev/mapper/somename in the output of the last
command if it succeeds, or some clue if it does not.

You can also run commands like
(initramfs) mount
(initramfs) ls
(initramfs) cat /cryptroot/crypttab
to investigate further.

I confirm all these commands do work for me on a Debian 10 machine.

Also, if that fails, it might be useful to confirm that the drive can be
decrypted when temporarily connected to another working system.

Hope this helps.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827342#10


Thanks for the suggestions.


Given the motherboard is circa 2011, Debian 9 has reached end of 
maintenance, and the lack of response on my initial bug report, I doubt 
this bug will be fixed.  Even if I had some success in debugging the 
issue and submitted reports and/or patches, I don't know if or what the 
Debian project would do with them.



It's time to put in a fresh system drive and try something newer that is 
actively supported.



David

Bug#955329: linux-image-4.9.0-12-amd64 breaks LUKS root

[David]

On Mon, 27 Jul 2020 at 09:47, David Christensen
 wrote:
> On 2020-03-30 02:58, deloptes wrote:
> > David Christensen wrote:

> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955329
>
> I updated/ upgraded the system today and whatever broke LUKS when I
> 'apt-get dist-upgrade' and installed kernel 4.9.0-12-amd64 several
> months ago now breaks LUKS when I try to boot the kernel that I have
> been using prior and since -- 4.9.0-11-amd64.  Fortunately, LUKS still
> works with my oldest available kernel, 4.9.0-9-amd64.
>
> > lsinitramfs will give you the content of the initrd
>
> Any other suggestions?

Hi, just a few thoughts from a dumb onlooker ...

I notice that your bug 955329 is filed against the linux-image
package around 4 months ago, and that there has been no reply from the
maintainers.

Looking around for similar bugs, I found [1] this comment by one of
the maintainers:

> LUKS volumes are recognised and set uo by userland, so are you sure
> this is due to the kernel upgrade?

So maybe it's not helpful to focus on the kernel, and I wonder if you
would get a response or debugging assistance if you were to report
this against the cryptsetup-initramfs package.

Another suggestion, although I am far from an expert in these matters,
I wonder if (per man initramfs-tools) you have tried using a kernel
boot parameter 'break=premount' and then see what happens if you try
to run your cryptsetup command in the initramfs shell.

For example, I would try:
(initramfs) blkid
(initramfs) cryptsetup open /dev/whatever/blkid/says somename
(initramfs) blkid

and expect to see /dev/mapper/somename in the output of the last
command if it succeeds, or some clue if it does not.

You can also run commands like
(initramfs) mount
(initramfs) ls
(initramfs) cat /cryptroot/crypttab
to investigate further.

I confirm all these commands do work for me on a Debian 10 machine.

Also, if that fails, it might be useful to confirm that the drive can be
decrypted when temporarily connected to another working system.

Hope this helps.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827342#10

Bug#955329: linux-image-4.9.0-12-amd64 breaks LUKS root

[David Christensen]

On 2020-03-30 02:58, deloptes wrote:

David Christensen wrote:



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955329


I updated/ upgraded the system today and whatever broke LUKS when I 
'apt-get dist-upgrade' and installed kernel 4.9.0-12-amd64 several 
months ago now breaks LUKS when I try to boot the kernel that I have 
been using prior and since -- 4.9.0-11-amd64.  Fortunately, LUKS still 
works with my oldest available kernel, 4.9.0-9-amd64.




lsinitramfs will give you the content of the initrd


I was unable to understand your other suggestions, but tried to use this 
one:


2020-07-26 16:35:36 root@po ~
# lsinitramfs -l /boot/initrd.img-4.9.0-9-amd64 > 
lsinitramfs-l-initrd.img-4.9.0-9-amd64.out


2020-07-26 16:35:57 root@po ~
# lsinitramfs -l /boot/initrd.img-4.9.0-11-amd64 > 
lsinitramfs-l-initrd.img-4.9.0-11-amd64.out



The listings are very large:

2020-07-26 16:40:08 root@po ~
# wc lsinitramfs-l-initrd.img-4.9.0-*
  1243  11247 128364 lsinitramfs-l-initrd.img-4.9.0-11-amd64.out
  1243  11247 127485 lsinitramfs-l-initrd.img-4.9.0-9-amd64.out
  2486  22494 255849 total


And there are a lot of changes:

2020-07-26 16:40:50 root@po ~
# diff lsinitramfs-l-initrd.img-4.9.0-9-amd64.out 
lsinitramfs-l-initrd.img-4.9.0-11-amd64.out | grep '>' | wc

9779878  112569

2020-07-26 16:40:52 root@po ~
# diff lsinitramfs-l-initrd.img-4.9.0-9-amd64.out 
lsinitramfs-l-initrd.img-4.9.0-11-amd64.out | grep '>' | head

> drwxr-xr-x  10 root root0 Jul 26 15:46 .
> drwxr-xr-x   3 root root0 Jul 26 15:46 conf
> drwxr-xr-x   2 root root0 Jul 26 15:46 conf/conf.d
> -rw-r--r--   1 root root   76 Jul 26 15:46 
conf/conf.d/cryptroot

> -rw-r--r--   1 root root   16 Jul 26 15:46 conf/arch.conf
> drwxr-xr-x   2 root root0 Jul 26 15:46 sbin
< lrwxrwxrwx   1 root root   12 Jan  9  2020 sbin/mount.ntfs 
-> /bin/ntfs-3g
> lrwxrwxrwx   1 root root   12 Jul 26 15:46 
sbin/mount.ntfs -> /bin/ntfs-3g
< lrwxrwxrwx   1 root root   12 Jan  9  2020 
sbin/mount.ntfs-3g -> /bin/ntfs-3g
> lrwxrwxrwx   1 root root   12 Jul 26 15:46 
sbin/mount.ntfs-3g -> /bin/ntfs-3g



I doubt I can find the needle(s) in that haystack.


Any other suggestions?


David

Bug#955329: Acknowledgement (linux-image-4.9.0-12-amd64: cryptsetup (sda3_crypt) : unknown fstype, bad password or options)

[David Christensen]

On 2020-03-29 17:15, Debian Bug Tracking System wrote:


If you wish to submit further information on this problem, please
send it to 955...@bugs.debian.org.



I have been running kernel 4.9.0-11-amd64 prior to and since filing the 
subject bug report.



I have updated/ upgraded my system via 'apt-get update' and 'apt-get 
upgrade' since filing the bug, and avoiding 'apt-get dist-upgrade'.



When I updated/ upgraded today and rebooted, the problem appeared again. 
 Console session follows.



So, whatever broke LUKS with kernel 4.9.0-12-amd64 has reverted even 
deeper and now breaks LUKS with kernel 4.9.0-11-amd64.



The work-around is to boot the only earlier kernel I have available, 
4.9.0-9-amd64.



When whatever broke 4.9.0-12-amd64 and now 4.9.0-11-amd64 breaks 
4.9.0-9-amd64, my system will be useless.



David



2020-07-26 15:44:55 root@po ~
# time apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
	The following package was automatically installed and is no longer 
required:

  libmicrodns0
Use 'apt autoremove' to remove it.
The following packages have been kept back:
  linux-image-amd64
The following packages will be upgraded:
	  base-files cups cups-bsd cups-client cups-common cups-core-drivers 
cups-daemon cups-ppdc cups-server-common dbus dbus-user-session dbus-x11 
e2fslibs e2fsprogs firefox-esr
	  gir1.2-rsvg-2.0 glib-networking glib-networking-common 
glib-networking-services imagemagick imagemagick-6-common 
imagemagick-6.q16 libcomerr2 libcups2 libcupscgi1 libcupsimage2
	  libcupsmime1 libcupsppdc1 libdbus-1-3 libexif12 libgnutls30 
libmagickcore-6.q16-3 libmagickcore-6.q16-3-extra libmagickwand-6.q16-3 
libmariadbclient18 libneon27-gnutls libopenjp2-7
	  libperl5.24 libpoppler-glib8 libpoppler64 libpython3.5 
libpython3.5-minimal libpython3.5-stdlib librsvg2-2 librsvg2-common 
libservlet3.1-java libss2 perl perl-base perl-doc
	  perl-modules-5.24 poppler-utils python3.5 python3.5-minimal tzdata 
wpasupplicant xdg-utils

57 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 83.4 MB of archives.
After this operation, 438 kB disk space will be freed.
Do you want to continue? [Y/n] y
	Get:1 http://security.debian.org/debian-security stretch/updates/main 
amd64 e2fslibs amd64 1.43.4-2+deb9u2 [208 kB]
	Get:2 http://ftp.us.debian.org/debian stretch/main amd64 base-files 
amd64 9.9+deb9u13 [67.6 kB]
	Get:3 http://security.debian.org/debian-security stretch/updates/main 
amd64 e2fsprogs amd64 1.43.4-2+deb9u2 [948 kB]
	Get:4 http://ftp.us.debian.org/debian stretch/main amd64 libperl5.24 
amd64 5.24.1-3+deb9u7 [3527 kB]
	Get:5 http://security.debian.org/debian-security stretch/updates/main 
amd64 libpoppler-glib8 amd64 0.48.0-2+deb9u3 [123 kB]
	Get:6 http://security.debian.org/debian-security stretch/updates/main 
amd64 libopenjp2-7 amd64 2.1.2-1.1+deb9u5 [123 kB]
	Get:7 http://security.debian.org/debian-security stretch/updates/main 
amd64 poppler-utils amd64 0.48.0-2+deb9u3 [154 kB]
	Get:8 http://security.debian.org/debian-security stretch/updates/main 
amd64 libpoppler64 amd64 0.48.0-2+deb9u3 [1286 kB]
	Get:9 http://security.debian.org/debian-security stretch/updates/main 
amd64 libpython3.5 amd64 3.5.3-1+deb9u2 [1371 kB]
	Get:10 http://security.debian.org/debian-security stretch/updates/main 
amd64 python3.5 amd64 3.5.3-1+deb9u2 [230 kB]
	Get:11 http://security.debian.org/debian-security stretch/updates/main 
amd64 libpython3.5-stdlib amd64 3.5.3-1+deb9u2 [2169 kB]
	Get:12 http://security.debian.org/debian-security stretch/updates/main 
amd64 python3.5-minimal amd64 3.5.3-1+deb9u2 [1695 kB]
	Get:13 http://security.debian.org/debian-security stretch/updates/main 
amd64 libpython3.5-minimal amd64 3.5.3-1+deb9u2 [575 kB]
	Get:14 http://security.debian.org/debian-security stretch/updates/main 
amd64 libcomerr2 amd64 1.43.4-2+deb9u2 [63.8 kB]
	Get:15 http://security.debian.org/debian-security stretch/updates/main 
amd64 libss2 amd64 1.43.4-2+deb9u2 [68.0 kB]
	Get:16 http://security.debian.org/debian-security stretch/updates/main 
amd64 librsvg2-common amd64 2.40.21-0+deb9u1 [16.6 kB]
	Get:17 http://security.debian.org/debian-security stretch/updates/main 
amd64 librsvg2-2 amd64 2.40.21-0+deb9u1 [108 kB]
	Get:18 http://security.debian.org/debian-security stretch/updates/main 
amd64 gir1.2-rsvg-2.0 amd64 2.40.21-0+deb9u1 [15.3 kB]
	Get:19 http://security.debian.org/debian-security stretch/updates/main 
amd64 libservlet3.1-java all 8.5.54-0+deb9u3 [404 kB]
	Get:20 http://ftp.us.debian.org/debian stretch/main amd64 perl amd64 
5.24.1-3+deb9u7 [218 kB]
	Get:21 http://ftp.us.debian.org/debian stretch/main amd64 perl-base 
amd64 5.24.1-3+deb9u7 [1346 kB]
	Get:22 http://ftp.us.debian.org/debian stretch/main amd64 
perl-modules-5.24 all 5.24.1-3+deb9u7 [2723 kB]
	Get:23 http

Bug#964118: linux-image-5.7.0-1-amd64 : completely garbled USB sound on Dell Dock

[Erwan David]

Package: src:linux
Version: 5.7.6-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

With 5.7.0-1 sound is not working correctly on my Dell Dock (the USB Audio card 
it presents).
Dock is identified as follows in the logs
Jul  1 08:16:28 ot-port-124 kernel: [  488.790917] usb 2-1.2: Dell TB16 Dock, 
disable RX aggregation

lsusb -v -t shows

   |__ Port 5: Dev 6, If 2, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
|__ Port 5: Dev 6, If 0, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
|__ Port 5: Dev 6, If 3, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
|__ Port 5: Dev 6, If 1, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
for this audio component

Sound works correctly when booting on linux-image-5.6.0-2-amd64  version 
5.6.14-2 and same userland, thus reporting a kernel bug

-- Package-specific info:
** Version:
Linux version 5.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-14), GNU ld (GNU Binutils for Debian) 2.34) #1 SMP Debian 5.7.6-1 
(2020-06-24)

** Command line:
BOOT_IMAGE=/vmlinuz-5.7.0-1-amd64 root=/dev/mapper/ot--port--eda--vg-root ro 
net.ifnames=0 quiet

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[   22.603251] iwlwifi :02:00.0: enabling device ( -> 0002)
[   22.606066] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms 
ovfl timer
[   22.606067] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[   22.606068] RAPL PMU: hw unit of domain package 2^-14 Joules
[   22.606068] RAPL PMU: hw unit of domain dram 2^-14 Joules
[   22.606069] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[   22.606069] RAPL PMU: hw unit of domain psys 2^-14 Joules
[   22.606222] Bluetooth: Core ver 2.22
[   22.606230] NET: Registered protocol family 31
[   22.606231] Bluetooth: HCI device and connection manager initialized
[   22.606233] Bluetooth: HCI socket layer initialized
[   22.606235] Bluetooth: L2CAP socket layer initialized
[   22.606238] Bluetooth: SCO socket layer initialized
[   22.650143] r8152 2-1.2:1.0: firmware: failed to load rtl_nic/rtl8153a-3.fw 
(-2)
[   22.650187] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   22.650233] r8152 2-1.2:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw 
failed with error -2
[   22.650235] r8152 2-1.2:1.0: unable to load firmware patch 
rtl_nic/rtl8153a-3.fw (-2)
[   22.660696] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-8265-36.ucode
[   22.661128] iwlwifi :02:00.0: loaded firmware version 36.8fd77bb3.0 
8265-36.ucode op_mode iwlmvm
[   22.661147] iwlwifi :02:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[   22.661184] iwlwifi :02:00.0: Direct firmware load for 
iwl-debug-yoyo.bin failed with error -2
[   22.668989] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040380
[   22.668998] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[   22.669298] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   22.686526] r8152 2-1.2:1.0 eth1: v1.11.11
[   22.692317] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (1bcf:2b96)
[   22.724120] audit: type=1400 audit(1593670793.162:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/haveged" pid=787 
comm="apparmor_parser"
[   22.724553] audit: type=1400 audit(1593670793.162:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=786 comm="apparmor_parser"
[   22.724769] audit: type=1400 audit(1593670793.162:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=784 comm="apparmor_parser"
[   22.727265] audit: type=1400 audit(1593670793.162:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=785 
comm="apparmor_parser"
[   22.727268] audit: type=1400 audit(1593670793.162:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=785 
comm="apparmor_parser"
[   22.727270] audit: type=1400 audit(1593670793.162:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=785 
comm="apparmor_parser"
[   22.727271] audit: type=1400 audit(1593670793.162:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=781 

Bug#959472: initramfs-tools (0.137): E: /usr/share/initramfs-tools/hooks/plymouth failed

[John David Anglin]

Package: initramfs-tools
Version: 0.137
Severity: normal

Dear Maintainer,

update-initramfs fails:

Processing triggers for initramfs-tools (0.137) ...
update-initramfs: Generating /boot/initrd.img-5.2.17+
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.2.17+ with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Version 0.136 was okay.

Regards,
Dave Anglin

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 12M Apr 11  2015 /boot/initrd.img-3.12.40+
-rw-r--r-- 1 root root 11M Sep 27  2016 /boot/initrd.img-3.18.42+
-rw-r--r-- 1 root root 20M Apr 16 20:38 /boot/initrd.img-4.14.176+
-rw-r--r-- 1 root root 20M Apr 24 21:57 /boot/initrd.img-4.14.177+
-rw-r--r-- 1 root root 11M Aug 21  2016 /boot/initrd.img-4.4.19+
-rw-r--r-- 1 root root 12M Sep 22  2017 /boot/initrd.img-4.9.51+
-rw-r--r-- 1 root root 37M Aug 21  2019 /boot/initrd.img-5.2.0-2-parisc64
-rw-r--r-- 1 root root 20M Apr 24 19:43 /boot/initrd.img-5.2.17+
-rw-r--r-- 1 root root 20M Sep 17  2019 /boot/initrd.img-5.2.8+
-- /proc/cmdline
root=LABEL=ROOT2 console=ttyS0 HOME=/ rootfstype=xfs clocksource=jiffies 
TERM=xterm palo_kernel=2/vmlinuz

-- /proc/filesystems
cramfs
xfs
ext2
ext3
ext4

-- lsmod
Module  Size  Used by
binfmt_misc13075  1
ext4  693225  3
ext2  113644  1
crc16   1655  1 ext4
jbd2  122319  1 ext4
mbcache 9772  2 ext4,ext2
sg 53216  0
ipmi_watchdog  25830  0
ipmi_si72878  1
ipmi_poweroff  12981  0
ipmi_devintf   14622  0
ipmi_msghandler60860  4 ipmi_devintf,ipmi_si,ipmi_watchdog,ipmi_poweroff
nfsd  166379  11
ip_tables  26100  0
x_tables   35419  1 ip_tables
ipv6  587774  146
autofs446898  2
xfs  1118276  2
libcrc32c   1618  1 xfs
crc32c_generic  3086  7
raid10 80659  0
raid1  59399  0
raid0  13504  0
multipath  11251  0
linear  6392  0
md_mod222868  5 raid1,raid10,raid0,linear,multipath
ses12759  0
enclosure  13195  1 ses
scsi_transport_sas 46247  1 ses
sd_mod 59912  10
sr_mod 24407  0
cdrom  44396  1 sr_mod
uas24743  0
usb_storage76116  2 uas
ata_generic 5378  0
ohci_pci5280  0
tg3   257464  0
pata_cmd64x10355  0
ptp20391  1 tg3
ohci_hcd   43731  1 ohci_pci
ehci_pci5759  0
ehci_hcd   62336  1 ehci_pci
sym53c8xx 111720  6
pps_core   13769  1 ptp
libata282335  2 pata_cmd64x,ata_generic
scsi_transport_spi 38311  1 sym53c8xx
usbcore   270368  6 
ohci_hcd,ehci_pci,usb_storage,ehci_hcd,ohci_pci,uas
scsi_mod  247013  10 
ses,scsi_transport_sas,sd_mod,scsi_transport_spi,usb_storage,uas,sym53c8xx,libata,sg,sr_mod
usb_common  3118  1 usbcore

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = yes

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=auto
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto
RUNSIZE=10%

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid10] 
unused devices: 

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
dmsetup
fsck
fuse
keymap
klibc-utils
kmod
mdadm
ntfs_3g
plymouth
resume
thermal
udev
xfs
zz-busybox


-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.177+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.137
ii  linux-base4.6

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.10-1

-- no debconf information

Bug#956752: linux-image-rt-amd64: No access to EFI variables possible with rt kernels

[David Müller]

Package: linux-image-rt-amd64
Version: 4.19+105+deb10u3
Severity: important

Dear Maintainer,

Using the rt kernel packages (4.19.0-8-rt-amd64 or 5.4.0-0.bpo.4-rt-amd64) no 
access to
the EFI variables under /sys/firmware/efi/efivars is possible.
With the non-rt kernels, all is fine as shown below:

root@debian:~# uname -a
Linux debian 4.19.0-8-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.98-1 (2020-01-26) 
x86_64 GNU/Linux
root@debian:~# ls -lR /sys/firmware/efi/
/sys/firmware/efi/:
total 0
-r--r--r-- 1 root root 4096 Apr 15 07:09 config_table
dr-xr-xr-x 2 root root0 Apr 15 07:09 efivars
-r--r--r-- 1 root root 4096 Apr 15 07:09 fw_platform_size
-r--r--r-- 1 root root 4096 Apr 15 07:09 fw_vendor
-r--r--r-- 1 root root 4096 Apr 15 07:09 runtime
-r 1 root root 4096 Apr 15 07:09 systab

/sys/firmware/efi/efivars:
total 0


root@debian:~# uname -a
Linux debian 5.4.0-0.bpo.4-rt-amd64 #1 SMP PREEMPT_RT Debian 5.4.19-1~bpo10+1 
(2020-03-09) x86_64 GNU/Linux
root@debian:~# ls -lR /sys/firmware/efi/
/sys/firmware/efi/:
total 0
-r--r--r-- 1 root root 4096 Apr 15 07:11 config_table
dr-xr-xr-x 2 root root0 Apr 15 07:10 efivars
-r--r--r-- 1 root root 4096 Apr 15 07:11 fw_platform_size
-r--r--r-- 1 root root 4096 Apr 15 07:11 fw_vendor
-r--r--r-- 1 root root 4096 Apr 15 07:11 runtime
-r 1 root root 4096 Apr 15 07:11 systab

/sys/firmware/efi/efivars:
total 0


root@debian:~# uname -a
Linux debian 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 
GNU/Linux
root@debian:~# ls -lR /sys/firmware/efi/
/sys/firmware/efi/:
total 0
-r--r--r--  1 root root 4096 Apr 15 07:06 config_table
drwxr-xr-x  2 root root0 Apr 15 07:06 efivars
-r--r--r--  1 root root 4096 Apr 15 07:06 fw_platform_size
-r--r--r--  1 root root 4096 Apr 15 07:06 fw_vendor
-r--r--r--  1 root root 4096 Apr 15 07:06 runtime
drwxr-xr-x  7 root root0 Apr 15 07:06 runtime-map
-r  1 root root 4096 Apr 15 07:06 systab
drwxr-xr-x 83 root root0 Apr 15 07:06 vars

/sys/firmware/efi/efivars:
total 0
-rw-r--r-- 1 root root   12 Apr 15 07:06 
AcpiGlobalVariable-af9ffd67-ec10-488a-9dfc-6cbf5ee22c2e
-rw-r--r-- 1 root root5 Apr 15 07:06 
AoacWakeStatus-23771b23-e15a-4805-920a-4f1e84b54abc
-rw-r--r-- 1 root root   72 Apr 15 07:06 
BmEssentialVariableNames-0b7646a4-6b44-4332-8588-c8998117f2ef
-rw-r--r-- 1 root root   46 Apr 15 07:06 
Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   54 Apr 15 07:06 
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   70 Apr 15 07:06 
Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   68 Apr 15 07:06 
Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   66 Apr 15 07:06 
Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   68 Apr 15 07:06 
Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   70 Apr 15 07:06 
Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   66 Apr 15 07:06 
Boot0007-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   71 Apr 15 07:06 
Boot0008-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   71 Apr 15 07:06 
Boot0009-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   71 Apr 15 07:06 
Boot000A-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   71 Apr 15 07:06 
Boot000B-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   71 Apr 15 07:06 
Boot000C-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   71 Apr 15 07:06 
Boot000D-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   73 Apr 15 07:06 
Boot000E-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   64 Apr 15 07:06 
Boot000F-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   68 Apr 15 07:06 
Boot0010-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   72 Apr 15 07:06 
Boot0011-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   74 Apr 15 07:06 
Boot0012-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   68 Apr 15 07:06 
Boot0013-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  134 Apr 15 07:06 
Boot0014-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root6 Apr 15 07:06 
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root8 Apr 15 07:06 
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   32 Apr 15 07:06 
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   30 Apr 15 07:06 
BootOrderDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  294 Apr 15 07:06 
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   50 Apr 15 07:06 
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   34 Apr 15 07:06 
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   34 Apr 15 07:06 
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root5 Apr 15 07:06 
CpuCmpSmt-f31bce44-4db9-40fc-93ab-4de140657b91
-rw-r--r-- 1 root root5 

Bug#955329: linux-image-4.9.0-12-amd64: cryptsetup (sda3_crypt) : unknown fstype, bad password or options

[David Christensen]

Package: src:linux
Version: 4.9.210-1
Severity: important

Dear Maintainer,

When I upgrade the kernel:

2020-03-29 16:48:15 root@po ~
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-image-4.9.0-12-amd64
The following packages will be upgraded:
  linux-image-amd64
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 39.3 MB of archives.
After this operation, 193 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.us.debian.org/debian stretch/main amd64 
linux-image-4.9.0-12-amd64 amd64 4.9.210-1 [39.3 MB]
Get:2 http://ftp.us.debian.org/debian stretch/main amd64 
linux-image-amd64 amd64 4.9+80+deb9u10 [7158 B]
Fetched 39.3 MB in 28s (1381 kB/s)  
   
Reading changelogs... Done
Selecting previously unselected package linux-image-4.9.0-12-amd64.
(Reading database ... 106066 files and directories currently installed.)
Preparing to unpack .../linux-image-4.9.0-12-amd64_4.9.210-1_amd64.deb 
...
Unpacking linux-image-4.9.0-12-amd64 (4.9.210-1) ...
Preparing to unpack .../linux-image-amd64_4.9+80+deb9u10_amd64.deb ...
Unpacking linux-image-amd64 (4.9+80+deb9u10) over (4.9+80+deb9u9) ...
Setting up linux-image-4.9.0-12-amd64 (4.9.210-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.9.0-11-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.9.0-11-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.9.0-12-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.9.0-12-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.9.0-12-amd64
cryptsetup: WARNING: target sda2_crypt has a random key, skipped
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found background image: .background_cache.png
Found linux image: /boot/vmlinuz-4.9.0-12-amd64
Found initrd image: /boot/initrd.img-4.9.0-12-amd64
Found linux image: /boot/vmlinuz-4.9.0-11-amd64
Found initrd image: /boot/initrd.img-4.9.0-11-amd64
Found linux image: /boot/vmlinuz-4.9.0-9-amd64
Found initrd image: /boot/initrd.img-4.9.0-9-amd64
done
Setting up linux-image-amd64 (4.9+80+deb9u10) ...

And then reboot:

Please unlock disk /dev/disk/by-partuuid/-xx (sda3_crypt):
cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
Please unlock disk /dev/disk/by-partuuid/-xx (sda3_crypt):
cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
Please unlock disk /dev/disk/by-partuuid/-xx (sda3_crypt):
cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
cryptsetup (sda3_crypt) : maximum number of tries exceeded
cryptsetup: going to sleep for 60 seconds...


The root LUKS container will not unlock with the correct key.


My work-around is to boot the previous kernel.  LUKS then works.


David



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: 
product_name: 
product_version: 
chassis_vendor: 
chassis_version: 
bios_vendor: Intel Corp.
bios_version: SWQ6710H.86A.0068.2017.0601.1423
board_vendor: Intel Corporation
board_name: DQ67SW
board_version: AAG12527-310

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Intel Corporation 2nd Generation Core Processor Family DRAM 
Controller [8086:2008]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snb_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Inte

Bug#946922: linux-image-5.3.0-3-amd64: Power regression from 5.2 to 5.3: FIXED

[David Purton]

Hi,

This issue has been fixed in linux-image-5.5-rc5, which is currently in
experimental.

I think it corresponds to this upstream issue:
https://gitlab.freedesktop.org/drm/intel/issues/614

Power usage is back to what it was with Linux 5.2 and package C states
are correctly reported.


So this Debian bug can now be closed as I guess things should be all
good once Linux 5.5 enters unstable.


Thanks,

David

-- 
David Purton
e: dcpur...@marshwiggle.net
m: 0413 626 862


signature.asc
Description: PGP signature

Bug#949539: linux-image-4.19.0-6-cloud-amd64: virtio-rng.ko moduel is not present

[David Magda]

Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: normal

Dear Maintainer,

The virtio-rng.ko is not present cloud image kernel package:

debian@dm-test1:~$ locate virtio
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/block/virtio_blk.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/char/virtio_console.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/net/virtio_net.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/scsi/virtio_scsi.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio/virtio.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio/virtio_balloon.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio/virtio_input.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio/virtio_mmio.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio/virtio_pci.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio/virtio_ring.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/net/vmw_vsock/vmw_vsock_virtio_transport.ko
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/net/vmw_vsock/vmw_vsock_virtio_transport_common.ko

This can further be confirmed via the package file list

https://packages.debian.org/buster/amd64/linux-image-4.19.0-6-cloud-amd64/filelist

However, the module is present in the non-cloud package:

https://packages.debian.org/buster/amd64/linux-image-4.19.0-6-amd64/filelist

It is also present in the cloud package of the buster-packports package:

https://packages.debian.org/buster-backports/amd64/linux-image-5.4.0-0.bpo.2-cloud-amd64/filelist


If it is preset in the non-cloud package, and the backported cloud package,
shouldn't it also be present in the 'default' cloud package as well?


-- Package-specific info:
** Version:
Linux version 4.19.0-6-cloud-amd64 (debian-kernel@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-cloud-amd64 
root=UUID=d187d85e-8a80-4664-8b5a-dce4d7ceca9e ro biosdevname=0 net.ifnames=0 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0 
systemd.show_status=true

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: OpenStack Foundation
product_name: OpenStack Nova
product_version: 18.2.1
chassis_vendor: QEMU
chassis_version: pc-i440fx-bionic
bios_vendor: SeaBIOS
bios_version: 1.10.2-1ubuntu1

** Loaded modules:
kvm_intel
kvm
irqbypass
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
evdev
virtio_console
virtio_balloon
serio_raw
qemu_fw_cfg
button
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
ata_generic
virtio_net
net_failover
virtio_blk
failover
crc32c_intel
ata_piix
libata
aesni_intel
scsi_mod
aes_x86_64
crypto_simd
cryptd
glue_helper
virtio_pci
virtio_ring
virtio

** PCI devices:
not available

** USB devices:
not available


-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-cloud-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-6-cloud-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod26-1
ii  linux-base  4.6

Versions of packages linux-image-4.19.0-6-cloud-amd64 recommends:
ii  apparmor 2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-4.19.0-6-cloud-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02+dfsg1-20
pn  linux-doc-4.19  

Versions of packages linux-image-4.19.0-6-cloud-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Bug#946922: linux-image-5.3.0-3-amd64: Power regression from 5.2 to 5.3

[David Purton]

Package: src:linux
Version: 5.3.15-1
Severity: normal

Dear Maintainer,

Since upgrading to Linux 5.3, I am seeing a power usage regression.

With Linux 5.2, powertop reported an idle battery discharge rate of
between 3 and 4 W and CPU package states seemed normal (majority of time
spent in pc7).

However, with Linux 5.3, powertop reports an idle battery dischage rate
of between 5 and 6 W. The CPU package states are all reported as
follows all of the time:

C2 (pc2)0.0%
C3 (pc3)0.0%
C6 (pc6)0.0%
C7 (pc7)0.0%
C8 (pc8)0.0%
C9 (pc9)0.0%
C10 (pc10)  0.0%

I noticed this with the first version of Linux 5.3 to be included into
Testing.

I just upgrade the UEFI BIOS from 1.55 to 1.61 to see if that would make
any difference, but it didn't.


Thanks,

David


-- Package-specific info:
** Version:
Linux version 5.3.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.15-1 (2019-12-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-3-amd64 
root=UUID=da639ab9-70f5-403b-8a6d-1d4a7f2fa064 ro quiet

** Not tainted

** Kernel log:
[4.270015] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input17
[4.270044] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input18
[4.316627] iwlwifi :00:14.3: base HW address: 50:e0:85:3a:71:90
[4.319477] intel_rapl_common: Found RAPL domain package
[4.319484] intel_rapl_common: Found RAPL domain core
[4.319485] intel_rapl_common: Found RAPL domain uncore
[4.319486] intel_rapl_common: Found RAPL domain dram
[4.384601] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[4.384814] thermal thermal_zone5: failed to read out thermal zone (-61)
[4.446311] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[4.513157] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
[4.534842] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[4.630596] Bluetooth: Core ver 2.22
[4.630607] NET: Registered protocol family 31
[4.630607] Bluetooth: HCI device and connection manager initialized
[4.630610] Bluetooth: HCI socket layer initialized
[4.630612] Bluetooth: L2CAP socket layer initialized
[4.630615] Bluetooth: SCO socket layer initialized
[4.640979] battery: new extension: ThinkPad Battery Extension
[4.641016] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input9
[4.642832] usbcore: registered new interface driver btusb
[4.664217] Lockdown: powertop: tracefs is restricted; see 
https://wiki.debian.org/SecureBoot
[4.950235] usb 1-10: new full-speed USB device number 5 using xhci_hcd
[5.099134] usb 1-10: config 1 interface 1 altsetting 0 endpoint 0x3 has 
wMaxPacketSize 0, skipping
[5.099137] usb 1-10: config 1 interface 1 altsetting 0 endpoint 0x83 has 
wMaxPacketSize 0, skipping
[5.099141] usb 1-10: New USB device found, idVendor=8087, idProduct=0aaa, 
bcdDevice= 0.02
[5.099142] usb 1-10: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[5.107103] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[5.108116] Bluetooth: hci0: Device revision is 2
[5.108117] Bluetooth: hci0: Secure boot is enabled
[5.108118] Bluetooth: hci0: OTP lock is enabled
[5.108118] Bluetooth: hci0: API lock is enabled
[5.108119] Bluetooth: hci0: Debug lock is disabled
[5.108120] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[5.109229] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-17-16-1.sfi
[5.109233] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[5.196023] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[5.228194] thinkpad_acpi: battery 1 registered (start 0, stop 100)
[5.228197] battery: ACPI: Battery Slot [BAT0] (battery present)
[5.267792] irq 31: nobody cared (try booting with the "irqpoll" option)
[5.268317] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.3.0-3-amd64 #1 
Debian 5.3.15-1
[5.268317] Hardware name: LENOVO 20Q0CTO1WW/20Q0CTO1WW, BIOS N2JET83W (1.61 
) 11/22/2019
[5.268318] Call Trace:
[5.268320]  
[5.268324]  dump_stack+0x66/0x90
[5.268326]  __report_bad_irq+0x38/0xad
[5.268328]  note_interrupt.cold+0xb/0x6e
[5.268329]  handle_irq_event_percpu+0x72/0x80
[5.268330]  handle_irq_event+0x3c/0x5c
[5.268331]  handle_fasteoi_irq+0xa3/0x160
[5.268333]  handle_irq+0x1f/0x30
[5.268334]  do_IRQ+0x4b/0xd0
[5.268336]  common_interrupt+0xf/0xf
[5.268336]  
[5.268339] RIP: 0010:cpuidle_enter_state+0xc4/0x420
[5.268340] Code: e8 41 3c ae ff 80 7c 24 0f 00 74 17 9c 58 0f 1f 44 00 00 
f6 c4 02 0f 85 39 03 00 00 31 ff e8 63 51 b4 ff fb 66 0f 1f 44 00 00 <45> 85 e4 
0f 89 cf 01 00 00 c7 45 10 00 00 00 00 48 83 c4 18 44 89
[5.268340] RSP: 0018:9ba03e58 EFLAGS: 0

Bug#945914: Sound broken on Intel Baytrail and Broadwell platforms (regression from bug 940726)

[David Ward]

Package: linux
Version: 5.3.7-1
Severity: important
Owner: Salvatore Bonaccorso 
Tags: patch

The kernel configuration change from Debian bug 940726 is invalid, 
according to Intel: https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15


The options for the SST and SOF drivers for Baytrail/Broadwell cannot 
both be set. This will be enforced via Kconfig beginning in Linux 5.5-rc1:


   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=df7257e544faf838c3e7ad6b4e89ffe59e87f5e1
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=a6955fe0e2309feeab5ec71e4b0dcbe498f4f497

Intel does not consider SOF ready on these platforms yet. 
https://github.com/thesofproject/linux/pull/1382#discussion_r344755772


The following two lines that were just added in 
debian/config/amd64/config need to be removed:


   CONFIG_SND_SOC_SOF_BAYTRAIL_SUPPORT=y
   CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT=y

This is applicable to sid, bullseye, and buster-backports. Thank you.
diff --git a/debian/config/amd64/config b/debian/config/amd64/config
index 1e35491..161a760 100644
--- a/debian/config/amd64/config
+++ b/debian/config/amd64/config
@@ -295,8 +295,6 @@ CONFIG_SND_SOC_SOF_ACPI=m
 ## file: sound/soc/sof/intel/Kconfig
 ##
 CONFIG_SND_SOC_SOF_INTEL_TOPLEVEL=y
-CONFIG_SND_SOC_SOF_BAYTRAIL_SUPPORT=y
-CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT=y
 CONFIG_SND_SOC_SOF_MERRIFIELD_SUPPORT=y
 CONFIG_SND_SOC_SOF_APOLLOLAKE_SUPPORT=y
 CONFIG_SND_SOC_SOF_GEMINILAKE_SUPPORT=y

Bug#940726: linux-source-5.2: Enable SOF audio driver and back-port fixes required to 5.2 kernel

[David Ward]

On 11/10/19 1:05 PM, David Ward wrote:
Unfortunately, this has caused a regression. The SST and SOF drivers 
cannot both be enabled for the same Intel platform in the kernel 
configuration, according to Intel. 
https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15


To clarify, the statement above applies to the Baytrail and Broadwell 
platforms (only).



These lines that were just added in debian/config/amd64/config need to 
be removed:


   CONFIG_SND_SOC_SOF_BAYTRAIL_SUPPORT=y
   CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT=y

This will be enforced via Kconfig beginning in Linux 5.5-rc1:

   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=df7257e544faf838c3e7ad6b4e89ffe59e87f5e1
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=a6955fe0e2309feeab5ec71e4b0dcbe498f4f497


The SOF drivers/firmware for the Broadwell and Baytrail platforms have 
issues, and Intel does not consider them ready for use in distributions yet:

https://github.com/thesofproject/linux/pull/1382#discussion_r344755772


Thank you.

Bug#900821: Reproduced on Apache container images for Docker/Kubernetes

[David Sánchez Herrero]

Hi all,

I experienced this problem while working with Apache container images
deployed on a Kubernetes cluster on Azure (the containers are based on
Debian).

root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# hostname
apache-nodeport-test-6595bf6579-5vsl6
root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# uname -a
Linux apache-nodeport-test-6595bf6579-5vsl6 4.15.0-1060-azure #65-Ubuntu
SMP Wed Sep 18 08:55:51 UTC 2019 x86_64 GNU/Linux
root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# cat
/etc/debian_version
10.2
root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# cat
/etc/apt/sources.list
# deb http://snapshot.debian.org/archive/debian/20191118T00Z buster main
deb http://deb.debian.org/debian buster main
# deb http://snapshot.debian.org/archive/debian-security/20191118T00Z
buster/updates main
deb http://security.debian.org/debian-security buster/updates main
# deb http://snapshot.debian.org/archive/debian/20191118T00Z
buster-updates main
deb http://deb.debian.org/debian buster-updates main
root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# apachectl -v
Server version: Apache/2.4.41 (Unix)
Server built:   Nov 23 2019 00:34:14

I have tested 2 Apache 2.4.X containers, one from Azure, and one from
Bitnami, with the same behaviour.

Greetings, David.

Bug#944956: linux-image-4.19.0-6-amd64: NVMe drive not detected

[David MacDonald]

Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: important

Dear Maintainer,

Installing NVMe SSD on Asus UX430UA laptop (SSD is ADATA ZPG SX8200 Pro). Goal 
was dual boot Windows 10 (already on drive) and Debian
10. Neither Debian 10 installer nor Deb 10.2 Live USB key
could detect NVMe drive. lsblk did not show drive, no /dev/nvme* files were 
present. Drive works on Windows on same machine, and
works on Debian 9 on my desktop machine.

dmesg showed error nvme :03:00.0: Refused to change power state, currently 
in D3
/dev/disk/by-id and /dev/disk/by-type had links for the partitions on the NVMe 
drive - correct number of partitions, but broken links
to /dev/nvme* files that didn't exist.

Added this line to startup in GRUB: nvme_core.default_ps_max_latency_us=0 (also 
tried 5500, which worked)

That seems to have solved the problem, though I imagine that is at the cost of 
proper power management.

As I mentioned, this drive worked on my desktop Deb 9 and on Windows on the 
same laptop. Ideally, it would work without having to 
disable APST so that Debian 10 can run without the extra power drain.

Thanks


-- Package-specific info:
** Version:
Linux version 4.19.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
root=UUID=5a3fe95c-c293-4153-9685-6d090c4f29b8 ro 
nvme_core.default_ps_max_latency_us=5500 quiet

** Not tainted

** Kernel log:
[7.462791] kauditd_printk_skb: 5 callbacks suppressed
[7.462793] audit: type=1400 audit(1574017435.750:16): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/evince" pid=490 
comm="apparmor_parser"
[7.463199] audit: type=1400 audit(1574017435.750:17): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/bin/evince//sanitized_helper" pid=490 comm="apparmor_parser"
[7.464208] audit: type=1400 audit(1574017435.750:18): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" 
pid=490 comm="apparmor_parser"
[7.464463] audit: type=1400 audit(1574017435.750:19): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/bin/evince-previewer//sanitized_helper" pid=490 
comm="apparmor_parser"
[7.464971] audit: type=1400 audit(1574017435.750:20): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/bin/evince-thumbnailer" pid=490 comm="apparmor_parser"
[9.954030] audit: type=1400 audit(1574017438.242:21): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-soffice" 
pid=466 comm="apparmor_parser"
[9.954736] audit: type=1400 audit(1574017438.242:22): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-soffice//gpg" 
pid=466 comm="apparmor_parser"
[   10.046272] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.046274] Bluetooth: BNEP filters: protocol multicast
[   10.046278] Bluetooth: BNEP socket layer initialized
[   10.282108] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   10.541054] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   10.822616] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   10.904097] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   12.033151] fuse init (API version 7.27)
[   14.340048] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   15.062746] wlp2s0: authenticate with 00:26:5a:d0:55:bc
[   15.072080] wlp2s0: send auth to 00:26:5a:d0:55:bc (try 1/3)
[   15.078665] wlp2s0: authenticated
[   15.081387] wlp2s0: associate with 00:26:5a:d0:55:bc (try 1/3)
[   15.085349] wlp2s0: RX AssocResp from 00:26:5a:d0:55:bc (capab=0x431 
status=0 aid=2)
[   15.089785] wlp2s0: associated
[   15.163549] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[   22.383573] Bluetooth: RFCOMM TTY layer initialized
[   22.384011] Bluetooth: RFCOMM socket layer initialized
[   22.384016] Bluetooth: RFCOMM ver 1.11
[  161.405575] PM: suspend entry (deep)
[  161.405577] PM: Syncing filesystems ... done.
[  161.407478] (NULL device *): firmware: direct-loading firmware 
iwlwifi-8000C-36.ucode
[  161.407524] Freezing user space processes ... (elapsed 0.001 seconds) done.
[  161.408999] OOM killer disabled.
[  161.409000] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[  161.410162] Suspending console(s) (use no_console_suspend to debug)
[  161.410518] wlp2s0: deauthenticating from 00:26:5a:d0:55:bc by local choice 
(Reason: 3=DEAUTH_LEAVING)
[  161.727163] ACPI: EC: interrupt blocked
[  161.782211] ACPI: Preparing to enter system sleep state S3
[  161.786436] ACPI: EC: event blocked
[  161.786438] ACPI: EC: EC stopped
[  161.786440] PM: Saving platform NVS memory
[  161.786537] Disabling non-boot CPUs ...
[  161.802787] smpboot: CPU 1 is now offline
[  161.828298] smpboot: CPU 2 is now offline
[  161.850681] smpboot: CPU 3 is now offline

Bug#940726: linux-source-5.2: Enable SOF audio driver and back-port fixes required to 5.2 kernel

[David Ward]

Unfortunately, this has caused a regression. The SST and SOF drivers 
cannot both be enabled for the same Intel platform in the kernel 
configuration, according to Intel. 
https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15


As described in the bug, this change causes a loss of sound on the Intel 
Broadwell platform (and even significantly degrades system performance 
when attempting to play sound).

Bug#941450: linux-image-4.19.0-6-amd64: e1000e driver periodically resets card

[Christopher David Howie]

Package: linux-image-4.19.0-6-amd64
Version: 4.19.67-2+deb10u1

This issue looks like it might be related to #657689, or at least the
symptoms are similar.

Periodically, my network link goes down for ~35 seconds at a time.  I
have not been able to determine what traffic pattern or set of other set
of circumstances that causes this and it doesn't happen on a regular
schedule.  It could happen dozens of times an hour, then not happen for
many hours.

Here is the most recent sample of the error from my kernel log:

> [1816352.315998] e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
>TDH  
>TDT  <47>
>next_to_use  <47>
>next_to_clean
>  buffer_info[next_to_clean]:
>time_stamp   <11b0fc627>
>next_to_watch<10>
>jiffies  <11b0fc789>
>next_to_watch.status <0>
>  MAC Status <80083>
>  PHY Status <796d>
>  PHY 1000BASE-T Status  <7800>
>  PHY Extended Status<3000>
>  PCI Status <10>
> [1816354.293145] e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
>TDH  
>TDT  <47>
>next_to_use  <47>
>next_to_clean
>  buffer_info[next_to_clean]:
>time_stamp   <11b0fc627>
>next_to_watch<10>
>jiffies  <11b0fc978>
>next_to_watch.status <0>
>  MAC Status <80083>
>  PHY Status <796d>
>  PHY 1000BASE-T Status  <7800>
>  PHY Extended Status<3000>
>  PCI Status <10>
> [1816356.313154] e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
>TDH  
>TDT  <47>
>next_to_use  <47>
>next_to_clean
>  buffer_info[next_to_clean]:
>time_stamp   <11b0fc627>
>next_to_watch<10>
>jiffies  <11b0fcb71>
>next_to_watch.status <0>
>  MAC Status <80083>
>  PHY Status <796d>
>  PHY 1000BASE-T Status  <7800>
>  PHY Extended Status<3000>
>  PCI Status <10>
> [1816358.293101] e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
>TDH  
>TDT  <47>
>next_to_use  <47>
>next_to_clean
>  buffer_info[next_to_clean]:
>time_stamp   <11b0fc627>
>next_to_watch<10>
>jiffies  <11b0fcd60>
>next_to_watch.status <0>
>  MAC Status <80083>
>  PHY Status <796d>
>  PHY 1000BASE-T Status  <7800>
>  PHY Extended Status<3000>
>  PCI Status <10>
> [1816358.420838] e1000e :00:1f.6 enp0s31f6: Reset adapter unexpectedly
> [1816358.421364] br0: port 1(enp0s31f6) entered disabled state
> [1816362.315470] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
> [1816362.315560] br0: port 1(enp0s31f6) entered blocking state
> [1816362.315565] br0: port 1(enp0s31f6) entered listening state
> [1816377.364603] br0: port 1(enp0s31f6) entered learning state
> [1816392.468385] br0: port 1(enp0s31f6) entered forwarding state
> [1816392.468388] br0: topology change detected, propagating

I did not really notice this issue until I placed the interface into a
bridge (which it shares with qemu-kvm virtual interfaces to bridge them
to the physical network).  Placing it into the bridge adds 30 seconds of
bridge learning/listening time that exacerbates the issue and makes it
much easier to notice.

To clarify, this driver issue causes the physical interface to be down
for ~5 seconds only.  However, during that time the physical link
appears down to the bridge, which then adds another 30 seconds of
downtime after the physical link is restored.

Additional information:

> $ uname -a
> Linux chowie-desktop 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) 
> x86_64 GNU/Linux

> $ dpkg -l linux-image-\* | grep ^i
> ii  linux-image-4.19.0-5-amd64  4.19.37-5+deb10u2 amd64Linux 
> 4.19 for 64-bit PCs (signed)
> ii  linux-image-4.19.0-6-amd64  4.19.67-2+deb10u1 amd64  

Bug#935245: Problem found

[David Purton]

I found the problem.

5.2.7-1 had
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set

5.2.9-1 had
CONFIG_INTEL_IOMMU_DEFAULT_ON=y

5.2.9-2 has
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y

Only 5.2.7-1 boots on my system.

I can successfully boot 5.2.9-2 if I pass intel_iommu=off to the kernel
command line.

Bug#935245: Successful boot of mainline 5.3.0-rc6

[David Purton]

I built mainline 5.3.0-rc6 in the following way:

$ make distclean
$ make localmodconfig
$ scripts/config --disable DEBUG_INFO
$ make -j5 bindeb-pkg LOCALVERSION=-mainline

while running linux-image-5.0.0-trunk-amd64_5.0.2-1~exp1.

I was able to successfully boot this kernel.

Since my previous attempt to build 5.0.0 using the config from the
current Debian 5.2 kernel also wouldn't boot, it probably means that
some new config option that Debian is using for 5.2, not used (but
available) in 5.0 causes my machine problems.

Happy to help find this issue. But I wouldn't know where to start (other
than a diff of /boot/config-5.2.0-2-amd64 and /boot/config-5.0.0-trunk-amd64).

-- 
David Purton
e: dcpur...@marshwiggle.net
m: 0413 626 862

Bug#920937: 20190502-1?

[David Moreno]

Is this also happening with 20190502-1 from Sid?

Bug#928191: firmware-iwlwifi: WiFi-breaking regression in latest Stretch point release (9.9), pkg ver 20161130-5 (includes solved workaround)

[David]

Package: firmware-iwlwifi
Version: 20161130-5
Severity: important
Tags: upstream

After the most recent point release upgrade, performed on a stock Debian Stable
amd64 system with 'apt-get update ; apt-get dist-upgrade', in which the package
firmware-iwlwifi was upgraded to a newer version (amongside many other packages
- I cannot be certain this one is positively the cause), all tested WiFi
internet connections that worked fine previously no longer connect. Instead,
the NetworkManager applet in my desktop panel only shows the "connecting"
animation for about 10 seconds, then silently fails to the standard
"disconnected" icon, with no successful internet connection. Previously these
tested connections were successful within one or two seconds of selecting the
desired network from the NM drop-down list.

Hardware info (with the "#" sign at the start of a line indicating a root
command prompt):

# lspci -nnvv | grep Network
...
03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235
[8086:088e] (rev 24)
...

This is a very common card and hopefully other users are not being impacted in
the same way I have been


Successful solved workaround:

Unload and reload the two kernel modules 'iwlwifi' and 'iwldvm'. I perform this
with these commands:

# rmmod iwldvm
# rmmod iwlwifi
# modprobe iwlwifi

After this, the connections all work correctly and as expected and experienced
before the 9.9 release.

Thank you to all the Debian Developers, Maintainers, and all other excellent
people working to make technology that helps the world.



-- System Information:
Debian Release: 9.9
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.130

-- no debconf information

Bug#906189: linux-image-4.17.0-1-amd64: Laptop does not suspend in 4.17 - worked up to 4.16

[David Bremner]

Felix Hagemann  writes:

> Package: src:linux
> Version: 4.17.17-1
> Followup-For: Bug #906189
>
> Dear Maintainer,
>
> I do see exactly the same behaviour on a Thinkpad X1 Carbon (Gen. 2).
>

I had the same problem on my dell e7270, but it was fixed by a BIOS
upgrade. Something to try?

d

Re: Status of this bug

[David Goodenough]

On Monday, 23 July 2018 14:30:06 BST Lisandro Damián Nicanor Pérez Meyer wrote:

> This has happened so far:

>

> From the Debian side maxy added haveged as a sddm recommendation and as a

> workaround.

>

> From the Qt side Thiago from upstream is trying to determine what changed in

> the kernel side, as this clearly started to happen with 4.16 and got worse

> with 4.17.

>

> Ben, linux maintainers: if you could give us a hand to determine what

> changed from the kernel side it would be much much appreciated. If we find

> that there are valid changes then we might have an opportunity to make Qt

> upstreams reconsider the issue.

>

> Cheers, Lisandro.

Interesting to note that on a system with sysvinit (and 4.17 kernel) there is 
no noticeable delay in sddm startup.



David

Bug#900442: other source of error

[David Garfield]

I've had the same error happen ("generic_make_request: Trying to write
to read-only block-device "...) when running os-prober through grub on
my basically "wheezy" system.  I removed os-prober, to stop having to do
a 12 hour resync of the raid5 array every time I updated the kernel.

Bug#898344: linux-image-4.9.0-6-amd64: NFS fails to mount with sec=krb5

[LEGGETT, DAVID]

Package: src:linux
Version: 4.9.88-1+deb9u1
Severity: normal

Dear Maintainer,

After updating to 4.9.0-6-amd64 nfs mounts fail with these messages:
[  687.358529] NFS: nfs4_discover_server_trunking unhandled error -5.
Exiting with error EIO
[  687.364094] gss_marshal: gss_get_mic FAILED (851968)
[  687.364094] RPC: couldn't encode RPC header, exit EIO

This worked fine on 4.9.0-4-amd64.

The upstream discussion at https://patchwork.kernel.org/patch/10311831/
suggests that a fix to nfs is required.

-- Package-specific info:
** Version:
Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 
root=UUID=5edca1e0-e09d-40dd-b7c2-92a8a76c5aba ro quiet

** Not tainted

** Kernel log:
[4.129126] systemd[1]: Listening on Syslog Socket.
[4.279767] lp: driver loaded but no devices found
[4.362699] RPC: Registered named UNIX socket transport module.
[4.362700] RPC: Registered udp transport module.
[4.362700] RPC: Registered tcp transport module.
[4.362701] RPC: Registered tcp NFSv4.1 backchannel transport module.
[4.389170] ppdev: user-space parallel port driver
[4.780666] BTRFS info (device sda2): disk space caching is enabled
[4.958672] systemd-journald[308]: Received request to flush runtime journal 
from PID 1
[5.038838] hv_vmbus: registering driver hyperv_fb
[5.039283] checking generic (f800 30) vs hw (f800 30)
[5.039283] fb: switching to hyperv_fb from EFI VGA
[5.039313] Console: switching to colour dummy device 80x25
[5.039381] hyperv_fb: Screen resolution: 1152x864, Color depth: 32
[5.040258] Console: switching to colour frame buffer device 144x54
[5.112914] hv_utils: Registering HyperV Utility Driver
[5.112915] hv_vmbus: registering driver hv_util
[5.113976] hv_utils: Using TimeSync version 3.0
[5.218467] input: PC Speaker as /devices/platform/pcspkr/input/input1
[5.219037] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 
10737418240 ms ovfl timer
[5.219038] RAPL PMU: hw unit of domain pp0-core 2^-0 Joules
[5.219038] RAPL PMU: hw unit of domain package 2^-0 Joules
[5.219039] RAPL PMU: hw unit of domain dram 2^-0 Joules
[5.219039] RAPL PMU: hw unit of domain pp1-gpu 2^-0 Joules
[5.299212] EFI Variables Facility v0.08 2004-May-17
[5.416819] pstore: using zlib compression
[5.416827] pstore: Registered efi as persistent store backend
[5.428587] hv_vmbus: registering driver hyperv_keyboard
[5.429283] input: AT Translated Set 2 keyboard as 
/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0004:00/VMBUS:00/d34b2567-b9b6-42b9-8778-0a4ec0b955bf/serio0/input/input2
[5.547629] sd 0:0:0:0: Attached scsi generic sg0 type 0
[5.547688] sd 0:0:0:3: Attached scsi generic sg1 type 0
[5.547746] sd 0:0:0:2: Attached scsi generic sg2 type 0
[5.547804] sr 0:0:0:1: Attached scsi generic sg3 type 5
[5.598620] EDAC MC: Ver: 3.0.0
[5.600666] EDAC sbridge: Seeking for: PCI ID 8086:2fa0
[5.600667] EDAC sbridge:  Ver: 1.1.1 
[5.976307] sd 0:0:0:0: [storvsc] Sense Key : Illegal Request [current] 
[5.976310] sd 0:0:0:0: [storvsc] Add. Sense: Invalid command operation code
[5.976312] sd 0:0:0:2: [storvsc] Sense Key : Illegal Request [current] 
[5.976313] sd 0:0:0:2: [storvsc] Add. Sense: Invalid command operation code
[5.976369] sd 0:0:0:3: [storvsc] Sense Key : Illegal Request [current] 
[5.976371] sd 0:0:0:3: [storvsc] Add. Sense: Invalid command operation code
[5.976472] sd 0:0:0:2: [storvsc] Sense Key : Illegal Request [current] 
[5.976475] sd 0:0:0:2: [storvsc] Add. Sense: Invalid command operation code
[5.976597] sd 0:0:0:3: [storvsc] Sense Key : Illegal Request [current] 
[5.976599] sd 0:0:0:3: [storvsc] Add. Sense: Invalid command operation code
[5.977054] sd 0:0:0:0: [storvsc] Sense Key : Illegal Request [current] 
[5.977055] sd 0:0:0:0: [storvsc] Add. Sense: Invalid command operation code
[6.077315] Adding 67106812k swap on /dev/sdc1.  Priority:-1 extents:1 
across:67106812k FS
[6.798733] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: 
(null)
[9.268384] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[9.268390] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[9.378533] ip6_tables: (C) 2000-2006 Netfilter Core Team
[9.775192] Ebtables v2.0 registered
[9.803676] FS-Cache: Loaded
[9.833643] FS-Cache: Netfs 'nfs' registered for caching
[9.867215] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   10.532879] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   10.942879] Netfilter messages via NETLINK v0.30.
[   10.972610] ip_set: protocol 6
[   12.896088] fuse init (API version 7.26)
[   26.908478] Key type dns_resolver 

Bug#890326: linux: Thinkpad X61 brightness reset to 0% on each boot

[David Banks]

FWIW, I am also seeing this bug after a recent kernel upgrade.  The
laptop is Asus UX303UA.

I enclose the kernel information from reportbug in the attachment.
Also I can confirm that the workaround given above works for me.

-- 
David Banks  <amoe...@gmail.com>


reportbug-kernel-info.out
Description: Binary data

Bug#886417: linux-source-4.9: Kernel sources do not compile

[David Reviejo]

Hi,

I have the same error with a very old machine, a Pentium-M one, (and so
no SMP...) trying to compile the source from 4.9.65-3+deb9u2 with a
custom config.

The problem is: the "load_new_mm_cr3" function in arch/x86/mm/tlb.c is
compiled only when SMP config is defined, but is used in code compiled
for no SMP machines (line 160); because of this the
"implicit-function-declaration" error.

Trying your sugestion, upstream 4.9.75 compile without problems: the
tlb.c there has no SMP special code (the header says something about:
"formerly SMP-only"...).

Cheers,
-- 
David

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

[David Loup]

On Tue, 12 Dec 2017 01:57:48 + Ben Hutchings wrote:
> [This message is bcc'd to all bug reporters.]
>
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix it. An updated package is
> available at:
>
> 
https://people.debian.org/~benh/packages/jessie-pu/linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64.deb

>
> There is a signed .changes file in the same directory that you can use
> to authenticate it.
>
> Please report back (to the bug address) whether this fixes the
> regression for you.
>
> If you need i386 packages, let me know and I will upload them too.
>
> Ben.
>
> --
> Ben Hutchings
> Unix is many things to many people,
> but it's never been everything to anybody.

The fix worked for me, thanks !

Bug#870484: linux-image-4.9.0-3-amd64: nf_conntrack_ftp does not detect passive data connection as related

[David Guyot]

Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: normal

Hello, there.

I just encounter a situation which seems to indicate that
nf_conntrack_ftp does not work as it should. The affected server has
the following iptables rules regarding FTP:
Chain INPUT (policy DROP 4 packets, 208 bytes)
 pkts bytes target prot opt
in out source   destination
   87 13850 ACCEPT all  
--  lo *   0.0.0.0/00.0.0.0/0/* loopbac
k@localhost */
144 ACCEPT tcp  
--  ens3   *   0.0.0.0/00.0.0.0/0tcp dpt:21
flags:0x17/0x02 limit: avg 5/min burst 50 recent: SET name: FTP side:
source mask: 255.255.255.255
0 0 LOGDROPtcp  
--  ens3   *   0.0.0.0/00.0.0.0/0tcp dpt:21
flags:0x17/0x02 recent: UPDATE seconds: 60 hit_count: 6 TTL-Match name:
FTP side: source mask: 255.255.255.255
   17   769 ACCEPT tcp  
--  ens3   *   0.0.0.0/00.0.0.0/0tcp dpt:21
0 0 ACCEPT tcp  
--  ens3   *   0.0.0.0/00.0.0.0/0tcp
dpts:5:50500 ctstate RELATED,ESTABLISHED
[…]
Chain OUTPUT (policy DROP 0 packets, 0 bytes)
 pkts bytes target prot opt
in out source   destination
  466 75053 ACCEPT all  
--  *  lo  0.0.0.0/00.0.0.0/0/* loopbac
k@localhost */
   14  1184 ACCEPT tcp  
--  *  ens30.0.0.0/00.0.0.0/0tcp spt:21
0 0 ACCEPT tcp  
--  *  ens30.0.0.0/00.0.0.0/0tcp
spts:5:50500 ctstate RELATED,ESTABLISHED
[…]

As you can see, iptables is configured to let passive FTP connections
pass, on the same port range than the one configured on the FTP
service:
root@pern /h/david {⌗0/⬓2}[0]꩜# cat /etc/pure-
ftpd/conf/PassivePortRange 
5 50500

Still, the passive FTP connection can't be established, as it freezes
when the client tries to open the passive data connection:
13:55:36.066536 IP client.59494 > server.ftp: Flags [S], seq
2083620944, win 32120, options [mss 1460], length
0   
13:55:36.066589 IP server.ftp > client.59494: Flags [S.], seq
2534440145, ack 2083620945, win 29200, options [mss 1460], length 0
13:55:36.101446 IP client.59494 > server.ftp: Flags [.], ack 1, win
32120, length 0   
13:55:41.111237 IP server.ftp > client.59494: Flags [P.], seq 1:320,
ack 1, win 29200, length 319: FTP: 220-- Welcome to Pure-FTPd
[privsep] [TLS] --
13:55:41.144917 IP client.59494 > server.ftp: Flags [.], ack 320, win
31801, length 0
13:55:41.983515 IP client.59494 > server.ftp: Flags [P.], seq 1:11, ack
320, win 32120, length 10: FTP: AUTH TLS
13:55:41.983551 IP server.ftp > client.59494: Flags [.], ack 11, win
29200, length
0 
13:55:41.983654 IP server.ftp > client.59494: Flags [P.], seq 320:365,
ack 11, win 29200, length 45: FTP: 500 This security scheme is not
implemented
13:55:42.017240 IP client.59494 > server.ftp: Flags [.], ack 365, win
32075, length 0
13:55:42.743558 IP client.59494 > server.ftp: Flags [P.], seq 11:21,
ack 365, win 32120, length 10: FTP: AUTH
SSL
13:55:42.743750 IP server.ftp > client.59494: Flags [P.], seq 365:410,
ack 21, win 29200, length 45: FTP: 500 This security scheme is not
implemented
13:55:42.777386 IP client.59494 > server.ftp: Flags [.], ack 410, win
32075, length 0
13:55:43.503046 IP client.59494 > server.ftp: Flags [P.], seq 21:36,
ack 410, win 32120, length 15: FTP: USER **removed for
security**   
13:55:43.503210 IP server.ftp > client.59494: Flags [P.], seq 410:451,
ack 36, win 29200, length 41: FTP: 331 User **removed for security**
OK. Password required
13:55:43.536807 IP client.59494 > server.ftp: Flags [.], ack 451, win
32079, length 0
13:55:44.303051 IP client.59494 > server.ftp: Flags [P.], seq 36:63,
ack 451, win 32120, length 27: FTP: PASS **removed for security**
13:55:44.328143 IP server.ftp > client.59494: Flags [P.], seq 451:483,
ack 63, win 29200, length 32: FTP: 230 OK. Current directory is /
13:55:44.361804 IP client.59494 > server.ftp: Flags [.], ack 483, win
32088, length 0  
13:55:45.103442 IP client.59494 > server.ftp: Flags [P.], seq 63:69,
ack 483, win 32120, length 6: FTP: SYST   
13:55:45.103606 IP server.ftp > client.59494: Flags [P.], seq 483:502,
ack 69, win 29200, length 19: FTP: 215 UNIX Type: L8
13:55:45.137252 IP client.59494 > server.ftp: Flags [.], ack 502, win
32101, length 0  
13:55:45.983146 IP client.59494 > server.ftp: Flags [P.], seq 69:75,
ack 502, win 32120, length 6: FTP: FEAT   
13:55:45.983254 IP server.ftp > client.59494: Flags 

Bug#868682: nouveau: nouveau_pmops_runtime_suspend / kworker/2:1:59 blocked for more than 120 seconds

[David R. Hedges]

Package: src:linux
Version: 4.11.6-1
Severity: important
File: nouveau

Dear Maintainer,

I performed a fresh installation from the 2017-07-04 daily d-i netinst on
amd64. After booting into the system, messages appeared on the console /
syslog about task kworker blocked for more than 120 seconds. The stack trace
most notably included nouveau_pmops_runtime_suspend as a likely culprit.
Shutting down or rebooting the system through normal means (e.g. shutdown
-(h|r)) would apparently never succeed, repeating a similar message.

I found an old thread[1] that recommended booting with nouveau.runpm=0, so
I tried that. It appears to have remedied the situation.

[1] https://lists.gt.net/linux/kernel/2312697


-- Package-specific info:
** Version:
Linux version 4.11.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.11.6-1 (2017-06-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.11.0-1-amd64 
root=UUID=65cc09ff-bde8-4e73-9cb0-8bc3a5549087 ro nouveau.runpm=0 quiet

** Not tainted

** Kernel log:
[3.473899] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
[3.473900] ACPI: Power Button [PWRB]
[3.473932] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
[3.473933] ACPI: Power Button [PWRF]
[3.474152] tpm_inf_pnp 00:09: Found TPM with ID IFX0102
[3.483453] wmi: Mapper loaded
[3.486381] EFI Variables Facility v0.08 2004-May-17
[3.488308] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[3.490255] (NULL device *): hwmon_device_register() is deprecated. Please 
convert the driver to use hwmon_device_register_with_info().
[3.493255] mei_me :00:16.0: enabling device ( -> 0002)
[3.553070] sd 0:0:0:0: Attached scsi generic sg0 type 0
[3.553250] sr 2:0:0:0: Attached scsi generic sg1 type 5
[3.555977] iTCO_vendor_support: vendor-support=0
[3.557290] pstore: using zlib compression
[3.557820] pstore: Registered efi as persistent store backend
[3.558212] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[3.558950] iTCO_wdt: Found a Intel PCH TCO device (Version=4, 
TCOBASE=0x0400)
[3.559450] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[3.564518] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms 
ovfl timer
[3.564519] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[3.564519] RAPL PMU: hw unit of domain package 2^-14 Joules
[3.564520] RAPL PMU: hw unit of domain dram 2^-14 Joules
[3.564520] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[3.564521] RAPL PMU: hw unit of domain psys 2^-14 Joules
[3.578328] ppdev: user-space parallel port driver
[3.579138] [drm] Memory usable by graphics device = 4096M
[3.579140] checking generic (f000 76) vs hw (1ff000 1000)
[3.579141] [drm] Replacing VGA console driver
[3.579427] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - 
Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
[3.579593] checking generic (f000 76) vs hw (c000 1000)
[3.579594] checking generic (f000 76) vs hw (d000 200)
[3.580063] EXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. 
Opts: user_xattr
[3.580125] nouveau :01:00.0: NVIDIA GP107 (137000a1)
[3.611506] hp_wmi: query 0x4 returned error 0x5
[3.636319] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.636319] [drm] Driver supports precise vblank timestamp query.
[3.668908] intel_rapl: Found RAPL domain package
[3.668908] intel_rapl: Found RAPL domain core
[3.668909] intel_rapl: Found RAPL domain uncore
[3.668909] intel_rapl: Found RAPL domain dram
[3.690086] nouveau :01:00.0: bios: version 86.07.39.00.0b
[3.691359] hp_wmi: query 0x4 returned error 0x5
[3.692510] hp_wmi: query 0xd returned error 0x5
[3.692537] input: HP WMI hotkeys as /devices/virtual/input/input9
[3.693753] nouveau :01:00.0: fb: 2048 MiB GDDR5
[3.693761] nouveau :01:00.0: priv: HUB0: 00d054 0007 (1f408216)
[3.693914] hp_wmi: query 0x5 returned error 0x3
[3.694939] [TTM] Zone  kernel: Available graphics memory: 8108870 kiB
[3.694939] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[3.694939] [TTM] Initializing pool allocator
[3.694941] [TTM] Initializing DMA pool allocator
[3.694950] nouveau :01:00.0: DRM: VRAM: 2048 MiB
[3.694951] nouveau :01:00.0: DRM: GART: 1048576 MiB
[3.694952] nouveau :01:00.0: DRM: BIT table 'A' not found
[3.694953] nouveau :01:00.0: DRM: BIT table 'L' not found
[3.694953] nouveau :01:00.0: DRM: TMDS table version 2.0
[3.694954] nouveau :01:00.0: DRM: DCB version 4.1
[3.694955] nouveau :01:00.0: DRM: DCB outp 00: 01800f56 04600020
[3.694956] nouveau :01:00.0: DRM: DCB outp 01: 01000f52 04620020
[3.694956] nouveau :01:00.0: DRM: DCB 

Bug#856328: sid_nfs-utils_1.3.4-2.debdiff

[Rafael David Tinoco]

sid_nfs-utils_1.3.4-2.debdiff
Description: Binary data

Bug#856328: Fix nfs-mountd dependency on rpcbind

[Rafael David Tinoco]

Package: nfs-utils
Version: 1:1.3.4-2
Severity: important
Tags: patch, fixed-upstream, sid,

Hello maintainer,

I'm fixing this behavior in Ubuntu and I think fixing it in Debian is needed:

https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799

You can follow the upstream discussion for this fix:

https://www.spinics.net/lists/linux-nfs/msg62022.html

"""
Following commit 91da135f - it replaced "rpcbind.target" by "rpcbind.socket" in
some unit files - "rpcbind.socket" should also be added to "nfs-mountd.service"
as a dependency to avoid race conditions.

Usually "rpcbind.socket" is either started as a "sockets.target" dependency, or
as a dependency for "nfs-server.service", when unit files include it in
"BindsTo" or "After". Unfortunately there is a possilibility to have
"nfs-mountd.service" started when the rpcbind socket is not yet created:

systemd[1]: Starting NFS Mount Daemon...
systemd[1]: nfs-mountd.service: Control process exited, code=exited status=1
systemd[1]: Failed to start NFS Mount Daemon.
systemd[1]: nfs-mountd.service: Unit entered failed state.
systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.

Nowadays "nfs-mountd.service" uses "BindTo" directive to "nfs-server.service".
That, per se, doesn't guarantee ordering for NFS server to start rpcbind and for
nfs-mountd to depend on it.

https://bugs.launchpad.net/bugs/1590799

Signed-off-by: Rafael David Tinoco <rafael.tinoco@x>
"""

These comments show the problem when nfs-kernel-server starts before
rpcbind.service is brought online (by rpcbind.socket):

https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/comments/24

Explanation:

https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/comments/25
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/comments/30

Bug#855003: ATA HD race conditions at boot-time

[David Lawyer]

Package: linux-image-686-pae
Version: 4.9.0-1

When I booted my PC it hung at one point for 30 seconds and then resumed
booting.  Here's part of the dmesg for it.  Note that it happened 17 seconds
into the boot.


:
[0.00] Linux version 4.9.0-1-686-pae (debian-kernel@lists.debian.org) 
(gcc version 6.3.0 20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2 
(2017-01-12)
<snip) Below is the first mention of ata3.  Note jump from 7.0638421 sec
to ~30 sec. later:
[7.063842] input: PC Speaker as /devices/platform/pcspkr/input/input5
[   37.872045] ata3: drained 65536 bytes to clear DRQ
[   37.978315] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x8 action 0x6 
frozen
[   37.978401] ata3: SError: { 10B8B }
[   37.978474] ata3.00: failed command: READ DMA
[   37.978544] ata3.00: cmd c8/00:08:80:1e:81/00:00:00:00:00/e0 tag 0 dma 4096 
in
res 40/00:00:00:01:80/00:00:00:00:00/00 Emask 0x4 
(timeout)
[   37.978651] ata3.00: status: { DRDY }
[   37.978728] ata3: hard resetting link
[   38.290817] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   38.296561] ata3.00: configured for UDMA/100
[   38.296645] ata3: EH complete

I found a report on the Inet that finds a similar error:
http://www.smythies.com/~doug/network/hd_race/;>Linux ata hard disk 
access race condition. WWW.Smythies.com
This error doesn't repeat so I think it's a race condition.  The SATA
drive is one I installed about a couple of months ago and may have booted the PC
with it perhaps 60 times with no delay like this.  However, I upgraded the
kernel to -pae perhaps a couple of weeks ago.  There are now 2 HD's on my
PC, one SATA (ata30) and the other a slower PATA with a ribbon cable.

    David Lawyer

Bug#827604: linux-image-4.6.0-1-amd64: Only mounts XFS drive as read-only

[David McMackins]

I haven't received any further notifications on this bug. This has
remained an issue for me for all Linux versions higher than 4.5.


Happy Hacking,

David E. McMackins II
Associate Member, Free Software Foundation (#12889)

www.mcmackins.org www.delwink.com
www.gnu.org www.fsf.org

On 06/18/2016 11:51 AM, Ben Hutchings wrote:
> It looks like systemd is failing to remount David's filesystems as
> read/write on Linux 4.6, but not on 4.5.
> 
> Can you suggest how to get a log that would help diagnose this?
> 
> Ben.
> 
> On Sat, 2016-06-18 at 09:44 -0500, David McMackins wrote:
>> Package: src:linux
>> Version: 4.6.2-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> All of the releases of Linux 4.6 in Debian Sid so far have failed to
>> mount my primary disk in read-write mode. I have not tested my other XFS
>> disks, because failure to correctly mount all my OS partitions causes
>> numerous other daemons to fail to start (for instance, NetworkManager).
>>
>> I'm not really educated on managing the kernel, so I'm not sure what
>> logs I'm supposed to be providing here. It should be noted that I can
>> only look at historical logs (if they're even kept), because I can only
>> submit this report while falling back to Linux 4.5.
>>
>> Let me know what information I can provide to accelerate the resolution
>> of this big problem for me.
> 
> 

Bug#827604: linux-image-4.6.0-1-amd64: Only mounts XFS drive as read-only

[David McMackins]

Package: src:linux
Version: 4.6.2-1
Severity: important

Dear Maintainer,

All of the releases of Linux 4.6 in Debian Sid so far have failed to
mount my primary disk in read-write mode. I have not tested my other XFS
disks, because failure to correctly mount all my OS partitions causes
numerous other daemons to fail to start (for instance, NetworkManager).

I'm not really educated on managing the kernel, so I'm not sure what
logs I'm supposed to be providing here. It should be noted that I can
only look at historical logs (if they're even kept), because I can only
submit this report while falling back to Linux 4.5.

Let me know what information I can provide to accelerate the resolution
of this big problem for me.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor:
product_name:
product_version:
chassis_vendor:
chassis_version:
bios_vendor: Intel Corp.
bios_version: WYLPT10H.86A.0026.2014.0514.1714
board_vendor: Intel Corporation
board_name: D54250WYK
board_version: H13922-304

** Network interface configuration:

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM
Controller [8086:0a04] (rev 09)
Subsystem: Intel Corporation Haswell-ULT DRAM Controller [8086:2054]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: hsw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT
Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA
controller])
DeviceName:  CPU1
Subsystem: Intel Corporation Haswell-ULT Integrated Graphics Controller
[8086:2054]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio
Controller [8086:0a0c] (rev 09)
Subsystem: Intel Corporation Haswell-ULT HD Audio Controller [8086:2054]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC
[8086:9c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Intel Corporation 8 Series USB xHCI HC [8086:2054]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 8 Series HECI
#0 [8086:9c3a] (rev 04)
Subsystem: Intel Corporation 8 Series HECI [8086:2054]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet
Connection I218-V [8086:1559] (rev 04)
DeviceName:  ILAN
Subsystem: Intel Corporation Ethernet Connection I218-V [8086:2054]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio
Controller [8086:9c20] (rev 04)
DeviceName:  AUDIO1
Subsystem: Intel Corporation 8 Series HD Audio Controller [8086:2054]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1d.0 USB controller [0c03]: Intel Corporation 8 Series USB EHCI #1
[8086:9c26] (rev 04) (prog-if 20 [EHCI])
Subsystem: Intel Corporation 8 Series USB EHCI [8086:2054]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC Controller
[8086:9c43] (rev 04)
Subsystem: Intel Corporation 8 Series LPC Controller [8086:2054]

Bug#814288: Generates corrupt (?) initrd images

[Christopher David Howie]

On 2/10/2016 11:10 AM, Ben Hutchings wrote:
> Which boot loader are you using?

Grub 2.

> diffoscope (https://try.diffoscope.org/) agrees with that.
> 
> This works for me:
> 
> kvm -m 1G -kernel /boot/vmlinuz-3.16.0-4-amd64 -initrd 
> initrd.img-3.16.0-4-amd64.broken

Huh.  This is only making me more confused.  The .broken initrd image
consistently gives me "no cpio magic" panics.

The machine is a VirtualBox VM.  Perhaps I can produce a small VM image
that reproduces the problem.  Since the failure is in loading the
initrd, an image with just a /boot volume should be sufficient to
reproduce this specific failure.

> Of course the initramfs can't find your root device, but it eventually
> drops to a rescue shell.  Which I can't use because... is that 
> Dvorak layout?

It is.

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.



signature.asc
Description: OpenPGP digital signature

Bug#814288: Generates corrupt (?) initrd images

[Christopher David Howie]

Package: initramfs-tools
Version: 0.120

I have a rather odd case where update-initramfs sometimes generates good
initrds and sometimes it does not.  I'm not sure if the bug lies here or
in the kernel, but after sinking hours into investigating this issues
I'm very confident there is a bug somewhere.  I figure I will start with
this package and see where we get.

Kernel info, for the record:

-
Linux debian-workstation 3.16.0-4-amd64 #1 SMP Debian
3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux
-

Every initrd generated on the target machine with "update-initramfs -k
all -u" causes a kernel panic on the next boot:

-
Initramfs unpacking failed: no cpio magic
/bin/sh: error while loading shared libraries: libc.so.6: cannot open
shared object file: No such file or directory
(usual "attempted to kill init" flood)
-

However, if I boot from the amd64-8.1.0 netinstall CD in rescue mode and
select the options that will chroot me into the root volume of the
target machine and run the same update-initramfs command there, then the
machine boots.

I captured an example of a working and a broken initrd.  If I extract
them (gunzip < $file | cpio -i -dv) and diff the two trees, only one
file reports as being different: /etc/boottime.kmap.gz .  If I gunzip
this file in both trees, diff reports no differences.

I am at a total loss to explain this behavior.  The same
update-initramfs / mkinitramfs are used to build both, since I am
chroot'd into the root volume when building from the rescue CD.  The
only different pieces are the running kernel, and various mounts (/dev,
/proc, etc.).  The same kernel is used to actually boot both generated
initrds.

Since the initrds are not small, I'm linking them instead of attaching them.

Working:


Broken:


Thanks for your time,

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.





signature.asc
Description: OpenPGP digital signature