Processing of linux_4.9.30-2+deb9u3_multi.changes

2017-08-06 Thread Debian FTP Masters
linux_4.9.30-2+deb9u3_multi.changes uploaded successfully to localhost
along with the files:
  linux_4.9.30-2+deb9u3.dsc
  linux_4.9.30-2+deb9u3.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#871216: debian/bin/test-patches does not build arch-indep packages

2017-08-06 Thread Joachim Breitner
Package: src:linux
Version: 4.12.2-1~exp1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

following the advice on
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html
under “Simple patching and building” I used debian/bin/test-patches to
apply some patches I need to test. Unfortunately, this produces only the
arch dependent file:
../linux-headers-4.12.0-trunk-amd64_4.12.2-1~exp1a~test_amd64.deb
../linux-image-4.12.0-trunk-amd64_4.12.2-1~exp1a~test_amd64.deb
../linux-image-4.12.0-trunk-amd64-dbg_4.12.2-1~exp1a~test_amd64.deb
and linux-headers-4.12.0-trunk-amd64 depends on
linux-headers-4.12.0-trunk-common (= 4.12.2-1~exp1a~test)
which does not exist. Since the package version was adjusted, I cannot
just use the version of the archive.

I believe debian/bin/test-patches should also build the arch independent
packages, to produce an actually installable set of .debs.

Thanks,
Joachim



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

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

-BEGIN PGP SIGNATURE-

iHAEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCWYeoMRMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBswD8AljP9fp1cG0WLpCsxjjwGFJcQAzkAmwZb
uXg4dDzM0ZrLDdR7u2si9kLP
=635T
-END PGP SIGNATURE-


Bug#871049: MMC_SDHCI_XENON: arm64!

2017-08-06 Thread Christoph Egger
Hi!

Seems it's missing so far: This is about arm64 kernel

Thanks!

  Christoph



Bug#871049: Acknowledgement (linux: please enable MMC_SDHCI_XENON)

2017-08-06 Thread Christoph Egger
Hi again

Also adding CONFIG_MVNETA would be great. It's the right driver for the
hardware and missing on arm64.

Christoph



Bug#871049: linux: please enable MMC_SDHCI_XENON

2017-08-06 Thread Christoph Egger
Source: linux
Version: 4.12.2-1~exp1
Severity: normal

Hi there!

Please consider enabling MMC_SDHCI_XENON on the 4.12 and later
kernels. With this modification I can successfully boot plain debian
kernels from Espressobin using the SD card.

it needs two patches for devicetree which should be on the way for
4.14 latest:

http://git.infradead.org/linux-mvebu.git/commit/9be778f6c6d8f90ff2fad88d1770e2a7843aee43
http://git.infradead.org/linux-mvebu.git/commit/1208d2f0c84120d4e3eb2caf663a9a8b784b38ba

Though I'm not sure you're going to include those two already.

  Christoph

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

Kernel: Linux 4.11.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#865361: linux-image-4.9.0-3-amd64: kernel stuck at boot on HP ProLiant DL360 G4p

2017-08-06 Thread Dominik George
Hi,

> After upgrading my systems to debian 9.0, which provides a 4.9.0-3-amd64 
> kernel
> our HP ProLiant DL360 G4p Systems stop booting the kernel and complain about
> a bug (NMI watchdog: BUG: soft lockup). This concerns all our DL360 G4p 
> devices,
> others seem to work so far. On the affected machines I need to boot the former
> active 3.16.43-2 kernel.

We also ran into this problem yesterday when setting up an old system as
our new firewall.

It turned out that disabling the APIC table (MSP table) in the BIOS
helps, but only at first boot. Once the kernel itself has set up the
tables, after a reboot, it will be stuck again and the machine must be
power-cycled.

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Phone: +49 228 92934581 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature


Bug#864529: firmware-amd-graphics: missing firmware for AMD Radeon RX 560,570,580

2017-08-06 Thread Jesse Kaukonen

I'm confirming that this happens with RX 580. I did a clean install of Stretch 
and upgraded to Buster. After installing firmware-amd-graphics the system 
freezes on boot.

Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 
GNU/Linux

Package: firmware-amd-graphics
Status: install ok installed
Priority: optional
Section: non-free/kernel
Installed-Size: 14962
Maintainer: Debian Kernel Team 
Architecture: all
Multi-Arch: foreign
Source: firmware-nonfree
Version: 20161130-3

Relevant part extracted from syslog:

Aug  6 11:37:21 gekkoslovakia kernel: [4.068243] amdgpu :22:00.0: 
firmware: direct-loading firmware amdgpu/polaris10_uvd.bin
Aug  6 11:37:21 gekkoslovakia kernel: [4.068248] [drm] Found UVD firmware 
Version: 1.79 Family ID: 16
Aug  6 11:37:21 gekkoslovakia kernel: [4.068525] amdgpu :22:00.0: fence 
driver on ring 12 use gpu addr 0x01165420, cpu addr 0xb1918325a420
Aug  6 11:37:21 gekkoslovakia kernel: [4.069114] amdgpu :22:00.0: 
firmware: direct-loading firmware amdgpu/polaris10_vce.bin
Aug  6 11:37:21 gekkoslovakia kernel: [4.069119] [drm] Found VCE firmware 
Version: 52.4 Binary ID: 3
Aug  6 11:37:21 gekkoslovakia kernel: [4.069232] amdgpu :22:00.0: fence 
driver on ring 13 use gpu addr 0x000200d8, cpu addr 0x9f7aca9f50d8
Aug  6 11:37:21 gekkoslovakia kernel: [4.069265] amdgpu :22:00.0: fence 
driver on ring 14 use gpu addr 0x000200e8, cpu addr 0x9f7aca9f50e8
Aug  6 11:37:21 gekkoslovakia kernel: [4.069443] amdgpu :22:00.0: 
firmware: failed to load amdgpu/polaris10_k_smc.bin (-2)
Aug  6 11:37:21 gekkoslovakia kernel: [4.069450] amdgpu :22:00.0: 
Direct firmware load for amdgpu/polaris10_k_smc.bin failed with error -2
Aug  6 11:37:21 gekkoslovakia kernel: [4.069498] 
[drm:amdgpu_cgs_get_firmware_info [amdgpu]] *ERROR* Failed to request firmware
Aug  6 11:37:21 gekkoslovakia kernel: [4.073598] Adding 1951740k swap on 
/dev/sda1.  Priority:-1 extents:1 across:1951740k SSFS
Aug  6 11:37:21 gekkoslovakia kernel: [4.168058] usbcore: registered new 
interface driver snd-usb-audio
Aug  6 11:37:21 gekkoslovakia kernel: [4.616937] amdgpu: [powerplay] Failed 
to send Message.
Aug  6 11:37:21 gekkoslovakia kernel: [5.179101] amdgpu: [powerplay] SMU 
Firmware start failed!
Aug  6 11:37:21 gekkoslovakia kernel: [5.181664] amdgpu :22:00.0: 
firmware: direct-loading firmware amdgpu/polaris10_smc_sk.bin
Aug  6 11:37:21 gekkoslovakia kernel: [5.744970] amdgpu: [powerplay] Failed 
to send Message.
Aug  6 11:37:21 gekkoslovakia kernel: [6.307138] amdgpu: [powerplay] SMU 
Firmware start failed!
Aug  6 11:37:21 gekkoslovakia kernel: [6.307139] amdgpu: [powerplay] Failed 
to load SMU ucode.
Aug  6 11:37:21 gekkoslovakia kernel: [6.307140] amdgpu: [powerplay] smc 
start failed
Aug  6 11:37:21 gekkoslovakia kernel: [6.307218] [drm:amdgpu_device_init 
[amdgpu]] *ERROR* hw_init of IP block  failed -22
Aug  6 11:37:21 gekkoslovakia kernel: [6.307223] amdgpu :22:00.0: 
amdgpu_init failed
Aug  6 11:37:21 gekkoslovakia kernel: [6.375991] [ cut here 
]
Aug  6 11:37:21 gekkoslovakia kernel: [6.375995] kernel BUG at 
/build/linux-C5oXKu/linux-4.11.6/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c:6930!
Aug  6 11:37:21 gekkoslovakia kernel: [6.375998] invalid opcode:  [#1] 
SMP
Aug  6 11:37:21 gekkoslovakia kernel: [6.376000] Modules linked in: 
eeepc_wmi asus_wmi sparse_keymap rfkill video edac_mce_amd edac_core 
snd_usb_audio amdkfd snd_usbmidi_lib evdev joydev snd_rawmidi kvm 
snd_hda_intel(+) snd_seq_device irqbypass snd_hda_codec xpad crct10dif_pclmul 
ff_memless amdgpu(+) crc32_pclmul efi_pstore ghash_clmulni_intel pcspkr 
snd_hda_core ttm efivars snd_hwdep sg drm_kms_helper snd_pcm drm snd_timer 
i2c_algo_bit sp5100_tco mfd_core snd soundcore ccp rng_core shpchp wmi button 
acpi_cpufreq efivarfs ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic 
fscrypto ecb mbcache sd_mod hid_cherry hid_generic usbhid hid uas usb_storage 
crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper ahci libahci 
xhci_pci xhci_hcd i2c_piix4 libata r8169 mii usbcore scsi_mod usb_common 
gpio_amdpt gpio_generic i2c_designware_platform
Aug  6 11:37:21 gekkoslovakia kernel: [6.376054]  i2c_designware_core
Aug  6 11:37:21 gekkoslovakia kernel: [6.376059] CPU: 15 PID: 420 Comm: 
systemd-udevd Not tainted 4.11.0-1-amd64 #1 Debian 4.11.6-1
Aug  6 11:37:21 gekkoslovakia kernel: [6.376065] Hardware name: System 
manufacturer System Product Name/PRIME B350-PLUS, BIOS 0805 06/20/2017
Aug  6 11:37:21 gekkoslovakia kernel: [6.376071] task: 9f7ac6b3a140 
task.stack: b19182b4c000
Aug  6 11:37:21 gekkoslovakia kernel: [6.376098] RIP: 
0010:gfx_v8_0_kiq_set_interrupt_state+0xc3/0xd0 [amdgpu]
Aug  6 11:37:21 gekkoslovakia kernel: [6.376102] RSP: 0018:b19182b4f978 

Bug#857198: iwlwifi firmware load failures are actually normal

2017-08-06 Thread Jerome
I looked into this and the failures are actually normal, and loading the 
iwlwifi-7265D-22.ucode is the best that can be done on the Stretch kernel.


Not all version numbers of the Intel WiFi microcode are released, and 
when a kernel version is frozen the best version is not known in 
advance. This is why the kernel will try a range. Source:

   https://bugzilla.redhat.com/show_bug.cgi?id=1326591#c6

The list of released microcode versions is here:
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release
One can see that the version jumps from 22 to 29. The Stretch kernel 
tries from 26 downward. So 22 is the best it can use, and is covered. If 
one uses a more recent kernel, then it can make sense to download a more 
recent version from the above page.


So it seems this bug can be closed.