Bug#1011196: patch sent

2022-08-26 Thread Lennert Van Alboom
With some quick hints from the kernel's USB audio maintainer, the appropriate 
quirk has been identified and patch sent:

https://mailman.alsa-project.org/pipermail/alsa-devel/2022-August/205214.html

Waiting for upstream. In the meantime, this works (bluntly, for those who don't 
have multiple USB audio devices):

# rmmod snd_usb_audio
# modprobe snd_usb_audio vid=0x2522 pid=0x0007 quirk_flags=0x1

publickey - lennert@vanalboom.org - 0x0320C886.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#1011196: git bisect done, commit identified

2022-08-25 Thread Lennert Van Alboom
I went through a rather long process of git bisect on the kernel source and the 
offending commit has been identified:


root@Nesbitt:/linux# git bisect badbf6313a0ff766925462e97b4e733d5952de02367 is 
the first bad commit
commit bf6313a0ff766925462e97b4e733d5952de02367
Author: Takashi Iwai 
Date:   Mon Nov 23 09:53:31 2020 +0100

    ALSA: usb-audio: Refactor endpoint management

    This is an intensive surgery for the endpoint and stream management
    for achieving more robust and clean code.

    The goals of this patch are:
    - More clear endpoint resource changes
    - The interface altsetting control in a single place
    Below are brief description of the whole changes.

    First off, most of the endpoint operations are moved into endpoint.c,
    so that the snd_usb_endpoint object is only referred in other places.
    The endpoint object is acquired and released via the new functions
    snd_usb_endpoint_open() and snd_usb_endpoint_close() that are called
    at PCM hw_params and hw_free callbacks, respectively.  Those are
    ref-counted and EPs can manage the multiple opens.

    The open callback receives the audioformat and hw_params arguments,
    and those are used for initializing the EP parameters; especially the
    endpoint, interface and altset numbers are read from there, as well as
    the PCM parameters like the format, rate and channels.  Those are
    stored in snd_usb_endpoint object.  If it's the secondary open, the
    function checks whether the given parameters are compatible with the
    already opened EP setup, too.

    The coupling with a sync EP (including an implicit feedback sync) is
    done by the sole snd_usb_endpoint_set_sync() call.

    The configuration of each endpoint is done in a single shot via
    snd_usb_endpoint_configure() call.  This is the place where most of
    PCM configurations are done.  A few flags and special handling in the
    snd_usb_substream are dropped along with this change.

    A significant difference wrt the configuration from the previous code
    is the order of USB host interface setups.  Now the interface is
    always disabled at beginning and (re-)enabled at the last step of
    snd_usb_endpoint_configure(), in order to be compliant with the
    standard UAC2/3.  For UAC1, the interface is set before the parameter
    setups since there seem devices that require it (e.g. Yamaha THR10),
    just like how it was done in the previous driver code.

    The start/stop are almost same as before, also single-shots.  The URB
    callbacks need to be set via snd_usb_endpoint_set_callback() like the
    previous code at the trigger phase, too.

    Finally, the flag for the re-setup is set at the device suspend
    through the full EP list, instead of PCM trigger.  This catches the
    overlooked cases where the PCM hasn't been running yet but the device
    needs the full setup after resume.

    Tested-by: Keith Milner 
    Tested-by: Dylan Robinson 
    Link: https://lore.kernel.org/r/20201123085347.19667-26-ti...@suse.de
    Signed-off-by: Takashi Iwai 

 sound/usb/card.c     |   8 +-
 sound/usb/card.h     |  11 +-
 sound/usb/clock.c    |  13 +-
 sound/usb/endpoint.c | 662 ++-
 sound/usb/endpoint.h |  40 ++--
 sound/usb/pcm.c      | 616 +++
 6 files changed, 616 insertions(+), 734 deletions(-)




publickey - lennert@vanalboom.org - 0x0320C886.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#1011196: linux-image-5.17.0-2-amd64: Geek Out USB sound card fails to initialise

2022-08-24 Thread Lennert Van Alboom
Will be difficult, I think. It's a device from... 2014, I believe. Long past 
end of sales. eBay still has a few: https://www.ebay.com/itm/265844830824, 
https://www.ebay.com/itm/14437678.

Currently trying to setup a build environment to do kernel bisects because the 
current sid binutils makes a kernel build of 5.10 fail (yay). Fingers crossed.
--- Original Message ---
On Tuesday, August 23rd, 2022 at 17:33, Renato Gallo  
wrote:


> where can I buy one ?I am curious to test it on 6.0-rc2
> 

> On Tue, Aug 23, 2022 at 5:30 PM Lennert Van Alboom  
> wrote:
> 

> > Quick update, still broken in 5.18 (unstable) and 5.19 (experimental).
> > 

> > Some potentially useful syslog from trying with 5.19.0-trunk-amd64:
> > 

> > Aug 23 17:12:30 Nesbitt kernel: [ 188.154086] usb 3-6: new high-speed USB 
> > device number 5 using xhci_hcd
> > Aug 23 17:12:30 Nesbitt kernel: [ 188.303314] usb 3-6: New USB device 
> > found, idVendor=2522, idProduct=0007, bcdDevice=15.02
> > Aug 23 17:12:30 Nesbitt kernel: [ 188.303323] usb 3-6: New USB device 
> > strings: Mfr=1, Product=3, SerialNumber=0
> > Aug 23 17:12:30 Nesbitt kernel: [ 188.303325] usb 3-6: Product: Geek Out HD 
> > Audio 1V5
> > Aug 23 17:12:30 Nesbitt kernel: [ 188.303327] usb 3-6: Manufacturer: LH Labs
> > Aug 23 17:12:30 Nesbitt mtp-probe: checking bus 3, device 5: 
> > "/sys/devices/pci:00/:00:14.0/usb3/3-6"
> > Aug 23 17:12:30 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
> > Aug 23 17:12:30 Nesbitt kernel: [ 188.389783] usb 3-6: 1:2 : unsupported 
> > format bits 0x1
> > Aug 23 17:12:31 Nesbitt kernel: [ 188.460882] usbcore: registered new 
> > interface driver snd-usb-audio
> > Aug 23 17:12:31 Nesbitt mtp-probe: checking bus 3, device 5: 
> > "/sys/devices/pci:00/:00:14.0/usb3/3-6"
> > Aug 23 17:12:31 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
> > Aug 23 17:12:31 Nesbitt systemd-udevd[2217]: controlC1: Process 
> > '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime 
> > restore 1' failed with exit code 99.
> > Aug 23 17:12:31 Nesbitt systemd[1208]: Reached target Sound Card.
> > Aug 23 17:12:36 Nesbitt kernel: [ 193.658813] usb 3-6: 1:1: 
> > usb_set_interface failed (-110)
> > Aug 23 17:12:36 Nesbitt kernel: [ 193.659333] usb 3-6: 1:0: 
> > usb_set_interface failed (-71)
> > Aug 23 17:12:36 Nesbitt kernel: [ 193.660249] usb 3-6: 1:0: 
> > usb_set_interface failed (-71)
> > Aug 23 17:12:36 Nesbitt kernel: [ 193.661022] usb 3-6: 1:1: 
> > usb_set_interface failed (-71)
> > Aug 23 17:12:36 Nesbitt kernel: [ 193.661169] usb 3-6: 1:0: 
> > usb_set_interface failed (-71)
> > 

> > 

> > Relevant thread at Arch about what appears to be the same issue: 
> > https://bugs.archlinux.org/task/70636
> > 

> > Relevant thread on linux-usb mailinglist: 
> > https://www.spinics.net/lists/linux-usb/msg228518.html

publickey - lennert@vanalboom.org - 0x0320C886.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#1011196: linux-image-5.17.0-2-amd64: Geek Out USB sound card fails to initialise

2022-08-23 Thread Lennert Van Alboom
Quick update, still broken in 5.18 (unstable) and 5.19 (experimental).

Some potentially useful syslog from trying with 5.19.0-trunk-amd64:

Aug 23 17:12:30 Nesbitt kernel: [  188.154086] usb 3-6: new high-speed USB 
device number 5 using xhci_hcd
Aug 23 17:12:30 Nesbitt kernel: [  188.303314] usb 3-6: New USB device found, 
idVendor=2522, idProduct=0007, bcdDevice=15.02
Aug 23 17:12:30 Nesbitt kernel: [  188.303323] usb 3-6: New USB device strings: 
Mfr=1, Product=3, SerialNumber=0
Aug 23 17:12:30 Nesbitt kernel: [  188.303325] usb 3-6: Product: Geek Out HD 
Audio 1V5
Aug 23 17:12:30 Nesbitt kernel: [  188.303327] usb 3-6: Manufacturer: LH Labs
Aug 23 17:12:30 Nesbitt mtp-probe: checking bus 3, device 5: 
"/sys/devices/pci:00/:00:14.0/usb3/3-6"
Aug 23 17:12:30 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
Aug 23 17:12:30 Nesbitt kernel: [  188.389783] usb 3-6: 1:2 : unsupported 
format bits 0x1
Aug 23 17:12:31 Nesbitt kernel: [  188.460882] usbcore: registered new 
interface driver snd-usb-audio
Aug 23 17:12:31 Nesbitt mtp-probe: checking bus 3, device 5: 
"/sys/devices/pci:00/:00:14.0/usb3/3-6"
Aug 23 17:12:31 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
Aug 23 17:12:31 Nesbitt systemd-udevd[2217]: controlC1: Process 
'/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime 
restore 1' failed with exit code 99.
Aug 23 17:12:31 Nesbitt systemd[1208]: Reached target Sound Card.
Aug 23 17:12:36 Nesbitt kernel: [  193.658813] usb 3-6: 1:1: usb_set_interface 
failed (-110)
Aug 23 17:12:36 Nesbitt kernel: [  193.659333] usb 3-6: 1:0: usb_set_interface 
failed (-71)
Aug 23 17:12:36 Nesbitt kernel: [  193.660249] usb 3-6: 1:0: usb_set_interface 
failed (-71)
Aug 23 17:12:36 Nesbitt kernel: [  193.661022] usb 3-6: 1:1: usb_set_interface 
failed (-71)
Aug 23 17:12:36 Nesbitt kernel: [  193.661169] usb 3-6: 1:0: usb_set_interface 
failed (-71)


Relevant thread at Arch about what appears to be the same issue: 
https://bugs.archlinux.org/task/70636 

Relevant thread on linux-usb mailinglist: 
https://www.spinics.net/lists/linux-usb/msg228518.html

publickey - lennert@vanalboom.org - 0x0320C886.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#1011196: linux-image-5.17.0-2-amd64: Geek Out USB sound card fails to initialise

2022-05-18 Thread Lennert Van Alboom
I only noticed now that I still have snd_hda_intel.dmic_detect=0 in my boot 
arguments, which is a relic from olden times. Just removed it and can confirm 
that this does NOT make a difference.



--- Original Message ---
On Wednesday, May 18th, 2022 at 08:41, Lennert Van Alboom 
 wrote:


> 

> 

> Package: src:linux
> Version: 5.17.6-1
> Severity: normal
> X-Debbugs-Cc: lennert+deb...@vanalboom.org
> 

> My Geek Out USB sound card (Bus 003 Device 005: ID 2522:0007 LH Labs Geek Out 
> HD Audio 1V5) fails to initialise on all recent debian-provided kernels:
> 

> usb 3-6: uac_clock_source_is_valid(): cannot get clock validity for id 41
> usb 3-6: clock source 41 is not valid, cannot use
> usb 3-6: 1:0: usb_set_interface failed (-71)
> 

> Booting into linux-image-5.10.0-8-amd64 fixes this, and the card works as 
> expected. The exact spot where the problem was introduced is unclear; the
> issue is present in linux-image-5.14.0-trunk-amd64 and all more recent 
> kernels. Kernels between 5.10.0-8 and 5.14.0-trunk were not tested.
> 

> 

> -- Package-specific info:
> ** Version:
> Linux version 5.17.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
> 11.3.0-1) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT 
> Debian 5.17.6-1 (2022-05-11)
> 

> ** Command line:
> BOOT_IMAGE=/vmlinuz-5.17.0-2-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet 
> snd_hda_intel.dmic_detect=0
> 

> ** Not tainted
> 

> ** Kernel log:
> [66136.185642] usb 3-6: uac_clock_source_is_valid(): cannot get clock 
> validity for id 41
> [66136.185643] usb 3-6: clock source 41 is not valid, cannot use
> [66136.185956] usb 3-6: 1:0: usb_set_interface failed (-71)
> [66136.186183] usb 3-6: 1:0: usb_set_interface failed (-71)
> [66136.186354] usb 3-6: uac_clock_source_is_valid(): cannot get clock 
> validity for id 41
> [66136.186355] usb 3-6: clock source 41 is not valid, cannot use
> [66136.186667] usb 3-6: 1:0: usb_set_interface failed (-71)
> [66136.186889] usb 3-6: 1:0: usb_set_interface failed (-71)
> [66136.187053] usb 3-6: uac_clock_source_is_valid(): cannot get clock 
> validity for id 41
> [66136.187053] usb 3-6: clock source 41 is not valid, cannot use
> [66136.187403] usb 3-6: 1:0: usb_set_interface failed (-71)
> [66136.187658] usb 3-6: 1:0: usb_set_interface failed (-71)
> 

> ** Model information
> sys_vendor: LENOVO
> product_name: 81Q9
> product_version: Lenovo Yoga C940-14IIL
> chassis_vendor: LENOVO
> chassis_version: Lenovo Yoga C940-14IIL
> bios_vendor: LENOVO
> bios_version: AUCN45WW
> board_vendor: LENOVO
> board_name: LNVNB161216
> board_version: SDK0R32862 WIN
> 

> ** Loaded modules:
> tun
> dummy
> snd_usb_audio
> snd_usbmidi_lib
> snd_rawmidi
> uhid
> vmw_vsock_vmci_transport
> vsock
> vmw_vmci
> ctr
> ccm
> rfcomm
> exfat
> snd_seq_dummy
> snd_hrtimer
> snd_seq
> snd_seq_device
> cmac
> algif_hash
> algif_skcipher
> af_alg
> qrtr
> ipmi_devintf
> ipmi_msghandler
> cpufreq_powersave
> cpufreq_userspace
> cpufreq_ondemand
> cpufreq_conservative
> bnep
> sunrpc
> binfmt_misc
> sd_mod
> sg
> btusb
> btrtl
> btbcm
> btintel
> btmtk
> bluetooth
> jitterentropy_rng
> uvcvideo
> videobuf2_vmalloc
> videobuf2_memops
> sha512_ssse3
> videobuf2_v4l2
> sha512_generic
> videobuf2_common
> videodev
> drbg
> ansi_cprng
> ecdh_generic
> mc
> ecc
> joydev
> snd_sof_pci_intel_icl
> snd_sof_intel_hda_common
> soundwire_intel
> soundwire_generic_allocation
> soundwire_cadence
> snd_sof_intel_hda
> snd_sof_pci
> snd_sof_xtensa_dsp
> snd_sof
> snd_soc_hdac_hda
> snd_hda_codec_hdmi
> snd_hda_ext_core
> snd_soc_acpi_intel_match
> snd_soc_acpi
> hid_sensor_accel_3d
> hid_sensor_trigger
> hid_sensor_iio_common
> snd_soc_core
> industrialio_triggered_buffer
> kfifo_buf
> industrialio
> hid_sensor_custom
> snd_hda_codec_realtek
> snd_compress
> soundwire_bus
> snd_hda_codec_generic
> uas
> iwlmvm
> hid_sensor_hub
> ledtrig_audio
> x86_pkg_temp_thermal
> usb_storage
> intel_powerclamp
> scsi_mod
> wacom
> snd_hda_intel
> coretemp
> intel_ishtp_hid
> snd_intel_dspcfg
> iTCO_wdt
> scsi_common
> usbhid
> hid_multitouch
> mac80211
> snd_intel_sdw_acpi
> intel_pmc_bxt
> iTCO_vendor_support
> kvm_intel
> hid_generic
> snd_hda_codec
> libarc4
> mei_hdcp
> watchdog
> kvm
> iwlwifi
> intel_rapl_msr
> snd_hda_core
> irqbypass
> wmi_bmof
> intel_wmi_thunderbolt
> crc32_pclmul
> ghash_clmulni_intel
> rapl
> intel_cstate
> intel_uncore
> pcspkr
> snd_hwdep
> xhci_pci
> cfg80211
> 

Bug#1011196: linux-image-5.17.0-2-amd64: Geek Out USB sound card fails to initialise

2022-05-17 Thread Lennert Van Alboom
Package: src:linux
Version: 5.17.6-1
Severity: normal
X-Debbugs-Cc: lennert+deb...@vanalboom.org

My Geek Out USB sound card (Bus 003 Device 005: ID 2522:0007 LH Labs Geek Out 
HD Audio 1V5) fails to initialise on all recent debian-provided kernels:

usb 3-6: uac_clock_source_is_valid(): cannot get clock validity for id 41
usb 3-6: clock source 41 is not valid, cannot use 
usb 3-6: 1:0: usb_set_interface failed (-71)

Booting into linux-image-5.10.0-8-amd64 fixes this, and the card works as 
expected. The exact spot where the problem was introduced is unclear; the
issue is present in linux-image-5.14.0-trunk-amd64 and all more recent kernels. 
Kernels between 5.10.0-8 and 5.14.0-trunk were not tested. 


-- Package-specific info:
** Version:
Linux version 5.17.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.3.0-1) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 
5.17.6-1 (2022-05-11)

** Command line:
BOOT_IMAGE=/vmlinuz-5.17.0-2-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet 
snd_hda_intel.dmic_detect=0

** Not tainted

** Kernel log:
[66136.185642] usb 3-6: uac_clock_source_is_valid(): cannot get clock validity 
for id 41
[66136.185643] usb 3-6: clock source 41 is not valid, cannot use
[66136.185956] usb 3-6: 1:0: usb_set_interface failed (-71)
[66136.186183] usb 3-6: 1:0: usb_set_interface failed (-71)
[66136.186354] usb 3-6: uac_clock_source_is_valid(): cannot get clock validity 
for id 41
[66136.186355] usb 3-6: clock source 41 is not valid, cannot use
[66136.186667] usb 3-6: 1:0: usb_set_interface failed (-71)
[66136.186889] usb 3-6: 1:0: usb_set_interface failed (-71)
[66136.187053] usb 3-6: uac_clock_source_is_valid(): cannot get clock validity 
for id 41
[66136.187053] usb 3-6: clock source 41 is not valid, cannot use
[66136.187403] usb 3-6: 1:0: usb_set_interface failed (-71)
[66136.187658] usb 3-6: 1:0: usb_set_interface failed (-71)

** Model information
sys_vendor: LENOVO
product_name: 81Q9
product_version: Lenovo Yoga C940-14IIL
chassis_vendor: LENOVO
chassis_version: Lenovo Yoga C940-14IIL
bios_vendor: LENOVO
bios_version: AUCN45WW
board_vendor: LENOVO
board_name: LNVNB161216
board_version: SDK0R32862 WIN

** Loaded modules:
tun
dummy
snd_usb_audio
snd_usbmidi_lib
snd_rawmidi
uhid
vmw_vsock_vmci_transport
vsock
vmw_vmci
ctr
ccm
rfcomm
exfat
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
cmac
algif_hash
algif_skcipher
af_alg
qrtr
ipmi_devintf
ipmi_msghandler
cpufreq_powersave
cpufreq_userspace
cpufreq_ondemand
cpufreq_conservative
bnep
sunrpc
binfmt_misc
sd_mod
sg
btusb
btrtl
btbcm
btintel
btmtk
bluetooth
jitterentropy_rng
uvcvideo
videobuf2_vmalloc
videobuf2_memops
sha512_ssse3
videobuf2_v4l2
sha512_generic
videobuf2_common
videodev
drbg
ansi_cprng
ecdh_generic
mc
ecc
joydev
snd_sof_pci_intel_icl
snd_sof_intel_hda_common
soundwire_intel
soundwire_generic_allocation
soundwire_cadence
snd_sof_intel_hda
snd_sof_pci
snd_sof_xtensa_dsp
snd_sof
snd_soc_hdac_hda
snd_hda_codec_hdmi
snd_hda_ext_core
snd_soc_acpi_intel_match
snd_soc_acpi
hid_sensor_accel_3d
hid_sensor_trigger
hid_sensor_iio_common
snd_soc_core
industrialio_triggered_buffer
kfifo_buf
industrialio
hid_sensor_custom
snd_hda_codec_realtek
snd_compress
soundwire_bus
snd_hda_codec_generic
uas
iwlmvm
hid_sensor_hub
ledtrig_audio
x86_pkg_temp_thermal
usb_storage
intel_powerclamp
scsi_mod
wacom
snd_hda_intel
coretemp
intel_ishtp_hid
snd_intel_dspcfg
iTCO_wdt
scsi_common
usbhid
hid_multitouch
mac80211
snd_intel_sdw_acpi
intel_pmc_bxt
iTCO_vendor_support
kvm_intel
hid_generic
snd_hda_codec
libarc4
mei_hdcp
watchdog
kvm
iwlwifi
intel_rapl_msr
snd_hda_core
irqbypass
wmi_bmof
intel_wmi_thunderbolt
crc32_pclmul
ghash_clmulni_intel
rapl
intel_cstate
intel_uncore
pcspkr
snd_hwdep
xhci_pci
cfg80211
efi_pstore
snd_pcm
xhci_hcd
i2c_i801
i2c_smbus
snd_timer
mei_me
processor_thermal_device_pci_legacy
usbcore
snd
processor_thermal_device
processor_thermal_rfim
mei
processor_thermal_mbox
ucsi_acpi
processor_thermal_rapl
soundcore
typec_ucsi
intel_rapl_common
ideapad_laptop
intel_ish_ipc
i2c_hid_acpi
roles
platform_profile
int340x_thermal_zone
i2c_hid
intel_lpss_pci
sparse_keymap
intel_lpss
thunderbolt
rfkill
idma64
intel_ishtp
usb_common
typec
intel_soc_dts_iosf
hid
wmi
battery
soc_button_array
int3400_thermal
acpi_thermal_rel
intel_pmc_core
acpi_pad
ac
button
acpi_tad
parport_pc
ppdev
lp
parport
fuse
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
i915
i2c_algo_bit
drm_kms_helper
cec
rc_core
crc32c_intel
ttm
nvme
aesni_intel
drm
nvme_core
crypto_simd
cryptd
evdev
t10_pi
crc_t10dif
crct10dif_generic
crct10dif_pclmul
serio_raw
crct10dif_common
video

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Ice Lake-LP Processor Host 
Bridge/DRAM Registers [8086:8a12] (rev 03)
Subsystem: Lenovo Ice Lake-LP Processor Host Bridge/DRAM Registers 
[17aa:3801]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisIN

Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

2020-04-21 Thread Lennert Van Alboom
‐‐‐ Original Message ‐‐‐
On Sunday, 19 April 2020 17:02, Lennert Van Alboom  
wrote:
> ‐‐‐ Original Message ‐‐‐
> On Sunday, 19 April 2020 15:56, Uwe Kleine-König u...@kleine-koenig.org wrote:
> > Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your
> > custom kernel? (If only the former: Do you suffer from the reported
> > problem when you add intel_iommu=on to the kernel command line?)
> 

> I started with the stock Debian 5.5-rc config, and just did make oldconfig 
> from there on (don't like to stray too far from the official packages). So 
> the option should be identical to the Debian kernels.
> 

> $ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config
> CONFIG_INTEL_IOMMU=y
> CONFIG_INTEL_IOMMU_SVM=y
> 

> CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> 

> =
> 

> CONFIG_INTEL_IOMMU_FLOPPY_WA=y
> CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y
> 

> I don't reboot often, but I'll very likely run into the i915 hang above again 
> soon, so I'll try the intel_iommu=on then.


Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume without 
issues.

publickey - lennert@vanalboom.org - 0x0320C886.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

2020-04-19 Thread Lennert Van Alboom
‐‐‐ Original Message ‐‐‐
On Sunday, 19 April 2020 15:56, Uwe Kleine-König  wrote:

> Hello Lennert,
> 

> On Sat, Apr 18, 2020 at 11:29:42PM +, Lennert Van Alboom wrote:
> 

> > \ Original Message 
> > On 19 Apr 2020, 00:42, Uwe Kleine-König < u...@kleine-koenig.org> wrote:
> > 

> > > @Lennert: I assume you can still reproduce the problem. Do you care to
> > > test with intel_iommu=off and report about the result? Just to make
> > > sure you and I see the same problems?
> > 

> > I'm afraid I can't test this anymore - due to serious i915 issues I've
> > been building and running my own kernel packages. Currently running
> > 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh).
> 

> So the newer kernels don't fix your problems? In my experience the i915
> guys are quite responsive and willing to help if you run a recent
> kernel.

They don't. I've reported a bug for it a good while back:

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

https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/183
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2352

Awfully quiet there. There seem to be multiple similar bugs around; so far the 
only response I got upstream was the bug being closed and moved to "mesa" 
(which I don't really get either). Debian bug didn't get any acknowledgement or 
comment.


> > . I haven't seen the poweroff/suspend problem in a good while.
> 

> Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your
> custom kernel? (If only the former: Do you suffer from the reported
> problem when you add intel_iommu=on to the kernel command line?)

I started with the stock Debian 5.5-rc config, and just did make oldconfig from 
there on (don't like to stray too far from the official packages). So the 
option should be identical to the Debian kernels.

$ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config
CONFIG_INTEL_IOMMU=y
CONFIG_INTEL_IOMMU_SVM=y
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_FLOPPY_WA=y
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y


I don't reboot often, but I'll very likely run into the i915 hang above again 
soon, so I'll try the intel_iommu=on then.




publickey - lennert@vanalboom.org - 0x0320C886.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

2020-04-18 Thread Lennert Van Alboom
\ Original Message 
On 19 Apr 2020, 00:42, Uwe Kleine-König < u...@kleine-koenig.org> wrote:
@Lennert: I assume you can still reproduce the problem. Do you care to test 
with intel\_iommu=off and report about the result? Just to make sure you and I 
see the same problems? Best regards Uwe

I'm afraid I can't test this anymore - due to serious i915 issues I've been 
building and running my own kernel packages. Currently running 5.7.0-rc1 (which 
is still just as broken as 5.4, 5.5 and 5.6... sigh) . I haven't seen the 
poweroff/suspend problem in a good while.

publickey - lennert@vanalboom.org - 0x0320C886.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#950010: linux-image-5.4.0-3-amd64: System fan doesn't spin up anymore after suspend/resume

2020-01-28 Thread Lennert Van Alboom
Package: src:linux
Version: 5.4.13-1
Severity: important

After resuming from sleep, my laptop's system fan doesn't spin up
anymore, regardless of system load/temperature. It's capable of working
with passive cooling only, but the least bit of load immediately pushes
the CPU to 80°C and more. 

Only solution is rebooting. 

Can't say whether the same thing happens in 5.5-rc5 since suspend-to-ram
is broken in that kernel.




-- Package-specific info:
** Version:
Linux version 5.4.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20200117 (Debian 9.2.1-24)) #1 SMP Debian 5.4.13-1 (2020-01-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.4.0-3-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet

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

** Kernel log:
[ 1979.596397] mce: CPU6: Package temperature/speed normal
[ 1979.596398] mce: CPU4: Core temperature/speed normal
[ 1979.596398] mce: CPU0: Core temperature/speed normal
[ 1979.596399] mce: CPU2: Package temperature/speed normal
[ 1979.596399] mce: CPU7: Package temperature/speed normal
[ 1979.596400] mce: CPU4: Package temperature/speed normal
[ 1979.596401] mce: CPU0: Package temperature/speed normal
[ 2279.602445] mce: CPU7: Core temperature above threshold, cpu clock throttled 
(total events = 23581)
[ 2279.602446] mce: CPU3: Core temperature above threshold, cpu clock throttled 
(total events = 23581)
[ 2279.602447] mce: CPU4: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602448] mce: CPU5: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602449] mce: CPU0: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602450] mce: CPU1: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602452] mce: CPU6: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602453] mce: CPU2: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602453] mce: CPU3: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602455] mce: CPU7: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.610462] mce: CPU3: Core temperature/speed normal
[ 2279.610463] mce: CPU7: Core temperature/speed normal
[ 2279.610464] mce: CPU1: Package temperature/speed normal
[ 2279.610464] mce: CPU4: Package temperature/speed normal
[ 2279.610465] mce: CPU2: Package temperature/speed normal
[ 2279.610466] mce: CPU0: Package temperature/speed normal
[ 2279.610466] mce: CPU5: Package temperature/speed normal
[ 2279.610467] mce: CPU6: Package temperature/speed normal
[ 2279.610467] mce: CPU7: Package temperature/speed normal
[ 2279.610468] mce: CPU3: Package temperature/speed normal
[ 2330.044453] PM: suspend entry (s2idle)
[ 2330.058903] Filesystems sync: 0.014 seconds
[ 2330.059649] (NULL device *): firmware: direct-loading firmware 
i915/icl_dmc_ver1_07.bin
[ 2330.059780] (NULL device *): firmware: direct-loading firmware 
intel/ibt-19-32-4.ddc
[ 2330.059930] (NULL device *): firmware: direct-loading firmware 
iwlwifi-Qu-c0-hr-b0-48.ucode
[ 2330.060126] (NULL device *): firmware: direct-loading firmware 
intel/ibt-19-32-4.sfi
[ 2330.060135] (NULL device *): firmware: direct-loading firmware 
iwlwifi-Qu-c0-hr-b0-50.ucode
[ 2330.060408] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 2330.062077] OOM killer disabled.
[ 2330.062077] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 2330.063460] printk: Suspending console(s) (use no_console_suspend to debug)
[ 2330.068369] wlan0: deauthenticating from aa:db:03:14:80:7c by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 2331.423122] ACPI: EC: interrupt blocked
[ 2333.893013] ACPI: EC: interrupt unblocked
[ 2335.079220] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[ 2335.226967] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[ 2335.234651] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
[ 2335.471736] OOM killer enabled.
[ 2335.471737] Restarting tasks ... done.
[ 2335.496153] PM: suspend exit
[ 2335.673379] userif-2: sent link down event.
[ 2335.673381] userif-2: sent link up event.
[ 2335.991316] PM: suspend entry (s2idle)
[ 2336.002299] Filesystems sync: 0.010 seconds
[ 2336.002742] Freezing user space processes ... (elapsed 0.821 seconds) done.
[ 2336.824365] OOM killer disabled.
[ 2336.824366] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 2336.825852] printk: Suspending console(s) (use no_console_suspend to debug)
[ 2337.477791] ACPI: EC: interrupt blocked
[58827.790024] ACPI: EC: interrupt unblocked
[58828.840539] ideapad_laptop: Unknown event: 10
[58828.998404] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[58829.646084] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[58

Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

2020-01-15 Thread Lennert Van Alboom
Package: src:linux
Version: 5.5~rc5-1~exp1
Severity: normal

Neither shutdown nor suspend works in this kernel version. Systemd seems
to indicate it is trying at least, but the system hangs either right
before shutdown (clean situation, requiring a poweroff with the power
button) or before sleep (hung system, can't do anything except also hard
powering off and rebooting later).

Syslog from a suspend action:

Jan 16 06:43:53 Nesbitt NetworkManager[749]:   [1579153433.6342] manager: 
sleep: sleep requested (sleeping: no  enabled: yes)
Jan 16 06:43:53 Nesbitt NetworkManager[749]:   [1579153433.6343] device 
(p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Jan 16 06:43:53 Nesbitt NetworkManager[749]:   [1579153433.6345] manager: 
NetworkManager state is now ASLEEP
Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep.
Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend...
Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle)
Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system...





-- Package-specific info:
** Version:
Linux version 5.5.0-rc5-amd64 (debian-kernel@lists.debian.org) (gcc version 
9.2.1 20200104 (Debian 9.2.1-22)) #1 SMP Debian 5.5~rc5-1~exp1 (2020-01-06)

** Command line:
BOOT_IMAGE=/vmlinuz-5.5.0-rc5-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet

** Not tainted

** Kernel log:
[   11.240204] usb 3-10: config 1 interface 1 altsetting 0 endpoint 0x3 has 
wMaxPacketSize 0, skipping
[   11.240207] usb 3-10: config 1 interface 1 altsetting 0 endpoint 0x83 has 
wMaxPacketSize 0, skipping
[   11.240213] usb 3-10: New USB device found, idVendor=8087, idProduct=0026, 
bcdDevice= 0.02
[   11.240215] usb 3-10: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[   11.268290] mc: Linux media interface: v0.10
[   11.269619] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   11.272214] SCSI subsystem initialized
[   11.275443] usb-storage 4-1:1.0: USB Mass Storage device detected
[   11.275734] scsi host0: usb-storage 4-1:1.0
[   11.275814] videodev: Linux video capture interface: v2.00
[   11.275824] usbcore: registered new interface driver usb-storage
[   11.277009] usbcore: registered new interface driver uas
[   11.285112] uvcvideo: Found UVC 1.00 device Integrated Camera (13d3:56b2)
[   11.303110] uvcvideo 3-1:1.0: Entity type for entity Extension 4 was not 
initialized!
[   11.303111] uvcvideo 3-1:1.0: Entity type for entity Extension 3 was not 
initialized!
[   11.303112] uvcvideo 3-1:1.0: Entity type for entity Processing 2 was not 
initialized!
[   11.303112] uvcvideo 3-1:1.0: Entity type for entity Camera 1 was not 
initialized!
[   11.303150] input: Integrated Camera: Integrated C as 
/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/input/input21
[   11.303195] usbcore: registered new interface driver uvcvideo
[   11.303195] USB Video Class driver (1.1.1)
[   11.309377] Bluetooth: Core ver 2.22
[   11.309386] NET: Registered protocol family 31
[   11.309386] Bluetooth: HCI device and connection manager initialized
[   11.309388] Bluetooth: HCI socket layer initialized
[   11.309390] Bluetooth: L2CAP socket layer initialized
[   11.309391] Bluetooth: SCO socket layer initialized
[   11.313933] usbcore: registered new interface driver btusb
[   11.315171] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017
[   11.316154] Bluetooth: hci0: Device revision is 2
[   11.316169] Bluetooth: hci0: Secure boot is enabled
[   11.316169] Bluetooth: hci0: OTP lock is enabled
[   11.316169] Bluetooth: hci0: API lock is enabled
[   11.316170] Bluetooth: hci0: Debug lock is disabled
[   11.316170] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.317265] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-19-32-4.sfi
[   11.317267] Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi
[   12.307973] scsi 0:0:0:0: Direct-Access USB  Disk 3.0 0009 
PQ: 0 ANSI: 6
[   12.318811] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[   12.321712] sd 0:0:0:0: [sda] 60825600 512-byte logical blocks: (31.1 
GB/29.0 GiB)
[   12.322349] sd 0:0:0:0: [sda] Write Protect is off
[   12.322367] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[   12.323064] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[   12.346647]  sda: sda1
[   12.347847] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   12.400600] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[   12.419559] audit: type=1400 audit(1579159022.895:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=734 comm="apparmor_parser"
[   12.420287] audit: type=1400 audit(1579159022.895:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=730 
comm="apparmor_parser"
[   12.420374] audit: type=1400 audit(1579159022.895:4): apparmor="STATUS" 
operation="profile_load" profile="un

Bug#945076: firmware-linux: Missing firmware for i915 on Intel 1065G7 (Ice Lake)

2020-01-15 Thread Lennert Van Alboom
On kernel 5.5, firmware i915/icl_dmc_ver1_09.bin is also requested (and 
currently missing). Firmware is also available on kernel.org.


signature.asc
Description: Digital signature


Bug#949019: firmware-linux-nonfree: Missing firmware for Ice Lake sound card renders it disabled

2020-01-15 Thread Lennert Van Alboom
Package: firmware-linux-nonfree
Version: 20190717-2
Severity: normal

Missing firmware intel/sof/sof-icl.ri makes that the sound card is not
working in kernel 5.5 (only sound output is "dummy", until I plug in an
USB sound card).

Please update the firmware packages with more recent blobs than those of
six months ago :-) recent hardware depends on it.




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

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

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20190717-2
ii  firmware-misc-nonfree  20190717-2

Versions of packages firmware-linux-nonfree recommends:
ii  amd64-microcode  3.20191218.1
ii  intel-microcode  3.20191115.2

firmware-linux-nonfree suggests no packages.

-- no debconf information



Bug#945071: Fixed in linux-image-5.4.0-trunk-amd64 5.4.2-1~exp1.

2019-12-06 Thread Lennert Van Alboom
Confirmed that this no longer happens with linux-image-5.4.0-trunk-amd64 
5.4.2-1~exp1.


signature.asc
Description: Digital signature


Bug#945077: firmware-linux: Missing firmware for Intel bluetooth device 22560 makes adapter not available

2019-11-19 Thread Lennert Van Alboom
Package: firmware-linux
Version: 20190717-2
Severity: important

Nov 16 16:35:17 Nesbitt kernel: [   11.106019] bluetooth hci0: firmware: failed 
to load intel/ibt-19-32-4.sfi (-2)
Nov 16 16:35:17 Nesbitt kernel: [   11.106021] bluetooth hci0: Direct firmware 
load for intel/ibt-19-32-4.sfi failed with error -2

Bluetooth adapter is not working without this file ("no adapters found"). After 
manually
adding the firmware file (and the .ddc) it does work. 



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

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

Versions of packages firmware-linux depends on:
ii  firmware-linux-free 3.4
ii  firmware-linux-nonfree  20190717-2

Versions of packages firmware-linux recommends:
ii  amd64-microcode  3.20191021.1
ii  intel-microcode  3.20191115.1

firmware-linux suggests no packages.

-- no debconf information



Bug#945076: firmware-linux: Missing firmware for i915 on Intel 1065G7 (Ice Lake)

2019-11-19 Thread Lennert Van Alboom
Package: firmware-linux
Version: 20190717-2
Severity: normal

Syslog shows complaints about missing firmware:

Nov 16 16:35:17 Nesbitt kernel: [9.977154] i915 :00:02.0: firmware: 
failed to load i915/icl_dmc_ver1_07.bin (-2)
Nov 16 16:35:17 Nesbitt kernel: [9.977160] i915 :00:02.0: Direct 
firmware load for i915/icl_dmc_ver1_07.bin failed with error -2

This firmware is present upstream, which seems to suggest that the
firmware-linux package is in need of an update.

After manually adding i915/icl_dmc_ver1_07.bin, I noticed that
mkinitramfs also complained about bxt_huc_ver01_8_2893.bin. 





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

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

Versions of packages firmware-linux depends on:
ii  firmware-linux-free 3.4
ii  firmware-linux-nonfree  20190717-2

Versions of packages firmware-linux recommends:
ii  amd64-microcode  3.20191021.1
ii  intel-microcode  3.20191115.1

firmware-linux suggests no packages.

-- no debconf information



Bug#945071: linux-image-5.3.0-2-amd64: Intel Sensor Hub floods dmesg with "hid_field_extract() called with n (192) > 32!"

2019-11-19 Thread Lennert Van Alboom
Package: src:linux
Version: 5.3.9-2
Severity: normal

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850600 and 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547 . 

Nothing serious, but it's a lot of unnecessary noise:

$ sudo head -1 /var/log/syslog
Nov 16 16:35:17 Nesbitt systemd-sysusers[456]: Creating group systemd-coredump 
with gid 999.
$ date
Tue 19 Nov 11:34:10 CET 2019
$ sudo grep hid_field_extract /var/log/syslog | wc -l
87976



-- Package-specific info:
** Version:
Linux version 5.3.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191109 (Debian 9.2.1-19)) #1 SMP Debian 5.3.9-2 (2019-11-12)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-2-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[163488.514078] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.614221] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.614222] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.614223] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.614223] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.713945] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.713946] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.713946] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.713947] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.814074] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.814075] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.814076] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163488.814076] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163502.115180] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163502.115181] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163502.115183] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163502.115184] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163504.614575] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163504.614576] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163504.614577] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163504.614578] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163507.481440] wlan0: disconnect from AP e8:65:49:6a:2f:c1 for new auth to 
e8:65:49:8d:5e:11
[163507.485185] wlan0: authenticate with e8:65:49:8d:5e:11
[163507.486463] wlan0: send auth to e8:65:49:8d:5e:11 (try 1/3)
[163507.540531] wlan0: authenticated
[163507.541928] wlan0: associate with e8:65:49:8d:5e:11 (try 1/3)
[163507.606002] wlan0: RX ReassocResp from e8:65:49:8d:5e:11 (capab=0x431 
status=0 aid=8)
[163507.608155] wlan0: associated
[163507.925160] wlan0: Limiting TX power to 1 dBm as advertised by 
e8:65:49:8d:5e:11
[163514.014694] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163514.014695] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163514.014695] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163514.014696] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163519.220457] wlan0: Connection to AP e8:65:49:8d:5e:11 lost
[163520.494067] wlan0: authenticate with e8:65:49:6a:2f:c1
[163520.497158] wlan0: send auth to e8:65:49:6a:2f:c1 (try 1/3)
[163520.521807] wlan0: authenticated
[163520.522015] wlan0: associate with e8:65:49:6a:2f:c1 (try 1/3)
[163520.524456] wlan0: RX AssocResp from e8:65:49:6a:2f:c1 (capab=0x431 
status=0 aid=1)
[163520.527704] wlan0: associated
[163520.550298] wlan0: Limiting TX power to 1 dBm as advertised by 
e8:65:49:6a:2f:c1
[163520.550564] iwlwifi :00:14.3: Unhandled alg: 0x707
[163551.416238] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163551.416239] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called 
with n (192) > 32! (kworker/3:1)
[163551.416240] hid-sensor-hub 001F:8087:0AC2.0003: hid_fiel

Bug#866055: linux-image-4.9.0-3-amd64: Broadwell laptop hangs during light usage since upgrading to stretch

2017-07-20 Thread Lennert Van Alboom
I've been running 5+ days on 4.9.0-3-rt-amd64 now. Not going to cry victory yet
though, the previous run with 4.9.0-3-amd64 (4.9.30-2+deb9u2) lasted 8 days
before going belly up.


signature.asc
Description: Digital signature


Bug#866055: linux-image-4.9.0-3-amd64: Broadwell laptop hangs during light usage since upgrading to stretch

2017-07-14 Thread Lennert Van Alboom
Bug confirmed to still be around in 4.9.30-2+deb9u2. Took longer to hit than I 
expected (and I already hoped it was gone), but same symptoms.


signature.asc
Description: Digital signature


Bug#866055: linux-image-4.9.0-3-amd64: Broadwell laptop hangs during light usage since upgrading to stretch

2017-06-27 Thread Lennert Van Alboom
On a sidenote, I have had similar issues with 4.9 in sid before too, on my
laptop (i7-4600U). Hard lockups, quite often within 30 seconds after resuming
from sleep. I didn't investigate much further since newer kernels were
available (4.10-trunk, now 4.11). But it might be related.


signature.asc
Description: Digital signature


Bug#866055: linux-image-4.9.0-3-amd64: Broadwell laptop hangs during light usage since upgrading to stretch

2017-06-27 Thread Lennert Van Alboom
Package: src:linux
Version: 4.9.30-2+deb9u1
Followup-For: Bug #866055


Same problems reported here on a VMware VM with Xeon E5-1650 v2 CPUs.
After a while, one CPU core goes bananas at 100% straight (as visible in
the VMware management interface) and the entire machine becomes
unresponsive - nothing via network, nothing via local console. Needs to
be reset via the hypervisor. 

Tasty detail: I installed and configured watchdog+softdog in the VM,
added "debug" to the kernel cmdline and remounted /var/log with "sync".
There appears absolutely nothing out of the ordinary in the logs - one
line is a cronjob running or other trivial nonsense, the next line is
the machine starting up after my manual reset.

Whatever is causing this is nasty enough to prevent watchdog from
triggering a reset.


Regards,


Lennert


-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/SYSTEM-ROOT ro quiet 
log_buf_len=32M debug

** Not tainted

** Kernel log:
[2.770507] ata_piix :00:07.1: version 2.13
[2.775037] scsi host1: ata_piix
[2.779660] scsi host2: ata_piix
[2.779707] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1060 irq 14
[2.779726] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1068 irq 15
[2.950742] ata1.00: ATAPI: VMware Virtual IDE CDROM Drive, 0001, max 
UDMA/33
[2.955299] ata1.00: configured for UDMA/33
[2.956669] scsi 1:0:0:0: CD-ROMNECVMWar VMware IDE CDR00 1.00 
PQ: 0 ANSI: 5
[3.070757] ACPI: bus type USB registered
[3.071116] usbcore: registered new interface driver usbfs
[3.071523] usbcore: registered new interface driver hub
[3.071880] usbcore: registered new device driver usb
[3.078152] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[3.087854] ehci-pci: EHCI PCI platform driver
[3.088502] ehci-pci :02:01.0: EHCI Host Controller
[3.088839] ehci-pci :02:01.0: new USB bus registered, assigned bus 
number 1
[3.089325] ehci-pci :02:01.0: cache line size of 32 is not supported
[3.089685] ehci-pci :02:01.0: irq 19, io mem 0xfd5ff000
[3.107324] ehci-pci :02:01.0: USB 2.0 started, EHCI 1.00
[3.107849] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[3.108205] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[3.108550] usb usb1: Product: EHCI Host Controller
[3.108892] usb usb1: Manufacturer: Linux 4.9.0-3-amd64 ehci_hcd
[3.109217] usb usb1: SerialNumber: :02:01.0
[3.109646] hub 1-0:1.0: USB hub found
[3.110012] hub 1-0:1.0: 6 ports detected
[3.128056] uhci_hcd: USB Universal Host Controller Interface driver
[3.128113] uhci_hcd :02:00.0: UHCI Host Controller
[3.128171] uhci_hcd :02:00.0: new USB bus registered, assigned bus 
number 2
[3.128229] uhci_hcd :02:00.0: detected 2 ports
[3.128349] uhci_hcd :02:00.0: irq 18, io base 0x2000
[3.128446] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[3.128504] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[3.128561] usb usb2: Product: UHCI Host Controller
[3.128619] usb usb2: Manufacturer: Linux 4.9.0-3-amd64 uhci_hcd
[3.128676] usb usb2: SerialNumber: :02:00.0
[3.128845] hub 2-0:1.0: USB hub found
[3.128909] hub 2-0:1.0: 2 ports detected
[3.146084] sd 0:0:0:0: Attached scsi generic sg0 type 0
[3.146476] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[3.167814] VMware vmxnet3 virtual NIC driver - version 1.4.a.0-k-NAPI
[3.168186] vmxnet3 :0b:00.0: # of Tx queues : 2, # of Rx queues : 2
[3.169467] vmxnet3 :0b:00.0 eth0: NIC Link is Up 1 Mbps
[3.252600] input: PC Speaker as /devices/platform/pcspkr/input/input3
[3.260651] input: VirtualPS/2 VMware VMMouse as 
/devices/platform/i8042/serio1/input/input5
[3.261207] input: VirtualPS/2 VMware VMMouse as 
/devices/platform/i8042/serio1/input/input4
[3.266905] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 
10737418240 ms ovfl timer
[3.267287] RAPL PMU: hw unit of domain pp0-core 2^-0 Joules
[3.267647] RAPL PMU: hw unit of domain package 2^-0 Joules
[3.267991] RAPL PMU: hw unit of domain dram 2^-0 Joules
[3.332155] random: crng init done
[3.400463] ppdev: user-space parallel port driver
[3.416093] sr 1:0:0:0: [sr0] scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw 
xa/form2 cdda tray
[3.416460] cdrom: Uniform CD-ROM driver Revision: 3.20
[3.417612] sr 1:0:0:0: Attached scsi CD-ROM sr0
[3.442714] vmxnet3 :0b:00.0 ens192: renamed from eth0
[3.455024] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[3.495702] EDAC MC: Ver: 3.0.0
[3.503188] EDAC sbridge: Seeking for: PCI ID 8086:0ea0
[3.503229] EDAC sbridge:  Ver

Bug#728706: Debian-installer crashes on IA64 in HPVM (Integrity Virtual Machines)

2013-11-04 Thread Lennert Van Alboom
On Mon, Nov 04, 2013 at 04:25:06PM +0100, Bastian Blank wrote:
> Control: severity -1 important
> Control: reassign -1 src:linux 3.2.46-1
> 
> On Mon, Nov 04, 2013 at 02:41:43PM +0100, Lennert Van Alboom wrote:
> > Severity: grave
> 
> Not really, it is not broken for many people.

Fair enough.

> 
> > Booting debian 7.x installer isos in an Integrity VM (virtualization on top 
> > of
> > HP-UX/IA64) causes a guest crash after loading the initrd (the menu does 
> > work,
> > and the crash happens regardless of selecting 'Install' or 'Expert'):
> 
> So the kernel crashes somewhere.  There is no real development for ia64
> in Debian, so I'm not sure who can help.

Me neither. Support for ia64 has been degrading for a while - it's bad news
that the only properly working version of debian on HPVM is still 5.10. If it
hadn't ever worked I wouldn't worry, but first the SCSI drivers stopped working
(6.x) and now it won't even boot the kernel anymore :-)

> > There is a 3911856 byte vm.core file which I presume is the dump mentioned 
> > in
> > the console. 
> 
> Can you try if the "crash" util is able to read this?

Afraid not - when trying:

crash: vm.core: not a supported file format



Thanks,



Lennert


signature.asc
Description: Digital signature


Bug#557527: (no subject)

2009-11-22 Thread Lennert Van Alboom
Package: linux-2.6
Version: 2.6.31-2
Severity: normal

When the battery is being charged, its charge will rise steadily until it
reaches 99%, after which its charge_now jumps to the value held by 
charge_full_design. This basically means that charge_now will hold a value 
larger than the one in charge_full, which confuses (for an example) gkrellm 
up to a point that it reports the battery to suddenly be at "130% full". 

I reported this as a bug in gkrellm initially (http://bugs.debian.org/551518)
but it turned out rather quickly to be a sysfs thing.

I noticed this oddity first in kernel 2.6.30-1-686, and upgraded to
2.6.31-1-686 following the gkrellm maintainer's advice. This didn't change
the behaviour.

Kind regards,


Lennert


-- Package-specific info:
** Version:
Linux version 2.6.31-1-686 (Debian 2.6.31-2) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Nov 15 20:39:33 UTC 2009

** Command line:
root=/dev/mapper/SYSTEM-ROOT ro quiet vga=773

** Not tainted

** Kernel log:
[   22.116394] phy0: Selected rate control algorithm 'iwl-3945-rs'
[   22.189802] HDA Intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 
21
[   22.192250] HDA Intel :00:1b.0: setting latency timer to 64
[   22.305041] usb 3-1: new high speed USB device using ehci_hcd and address 2
[   22.342616] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input7
[   22.393409] input: HDA Intel Mic at Ext Left Jack as 
/devices/pci:00/:00:1b.0/sound/card0/input8
[   22.395989] input: HDA Intel HP Out at Ext Left Jack as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   22.426783] ide-cd driver 5.00
[   22.431754] ide-cd: hda: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache
[   22.434430] Uniform CD-ROM driver Revision: 3.20
[   22.439777] usb 3-1: New USB device found, idVendor=4146, idProduct=d2b5
[   22.442507] usb 3-1: New USB device strings: Mfr=16, Product=32, 
SerialNumber=48
[   22.445133] usb 3-1: Product:
[   22.447754] usb 3-1: Manufacturer: 
[   22.450342] usb 3-1: SerialNumber: 0005011200032
[   22.452963] usb 3-1: configuration #1 chosen from 1 choice
[   22.744909] Initializing USB Mass Storage driver...
[   22.747594] scsi2 : SCSI emulation for USB Mass Storage devices
[   22.750288] usb-storage: device found at 2
[   22.750290] usb-storage: waiting for device to settle before scanning
[   22.750295] usbcore: registered new interface driver usb-storage
[   22.752989] USB Mass Storage support registered.
[   22.960066] usb 7-1: new full speed USB device using uhci_hcd and address 2
[   23.114710] usb 7-1: New USB device found, idVendor=0b97, idProduct=7761
[   23.117500] usb 7-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   23.120311] usb 7-1: configuration #1 chosen from 1 choice
[   23.125758] hub 7-1:1.0: USB hub found
[   23.129697] hub 7-1:1.0: 4 ports detected
[   23.413724] usb 7-1.2: new full speed USB device using uhci_hcd and address 3
[   23.537718] usb 7-1.2: New USB device found, idVendor=0b97, idProduct=7772
[   23.540607] usb 7-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[   23.543369] usb 7-1.2: Product: O2Micro CCID SC Reader
[   23.546120] usb 7-1.2: Manufacturer: O2
[   23.549043] usb 7-1.2: configuration #1 chosen from 1 choice
[   24.298455] loop: module loaded
[   25.778608] XFS mounting filesystem dm-4
[   27.748259] usb-storage: device scan complete
[   27.749101] scsi 2:0:0:0: Direct-Access I0MEGA   UMni1GB*IOM2J4   1.00 
PQ: 0 ANSI: 2
[   27.753695] sd 2:0:0:0: [sdb] 2031616 512-byte logical blocks: (1.04 GB/992 
MiB)
[   27.757137] sd 2:0:0:0: [sdb] Write Protect is off
[   27.759956] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
[   27.759958] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   27.765219] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   27.767979]  sdb: sdb1 sdb2
[   27.773214] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   27.776046] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[   30.416096] Ending clean XFS mount for filesystem: dm-4
[   30.537037] XFS mounting filesystem dm-3
[   31.197412] Ending clean XFS mount for filesystem: dm-3
[   31.317270] Adding 1998840k swap on /dev/mapper/SYSTEM-SWAP.  Priority:-1 
extents:1 across:1998840k 
[   32.690116] iwl3945 :0c:00.0: firmware: requesting iwlwifi-3945-2.ucode
[   32.759647] iwl3945 :0c:00.0: loaded firmware version 15.32.2.9
[   32.835948] Registered led device: iwl-phy0::radio
[   32.839032] Registered led device: iwl-phy0::assoc
[   32.841798] Registered led device: iwl-phy0::RX
[   32.844454] Registered led device: iwl-phy0::TX
[   32.864931] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.999621] tg3 :09:00.0: PME# disabled
[   33.002345] tg3 :09:00.0: irq 29 for MSI/MSI-X
[   33.062080] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   36.662000] wlan0: authenticate with AP 00:14:bf:04:5b:cd
[   36.667169] wlan0: authenticated
[   36.6671