Bug#884001: linux-image-4.9.0-4-amd64: Severe graphics corruption on intel graphics after kernel upgrade
Package: src:linux Version: 4.9.65-3 Severity: important Hello, After upgrading the kernel from 4.9.51-1 to 4.9.65-3 i got severe graphics corruption (Screen content shifts sideways, flickers, screen goes black). This gets progressively worse so the system is unusable about 15 minutes after reboot. Often the shifting and flickering seems to be triggered by keystrokes (any, as far as i can tell). This occured right after the upgrade and subsequent reboot. Switching to an older kernel fixes the issue. dmesg says: [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun i'll attach the file regards, Andi -- Package-specific info: ** Version: Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3 (2017-12-03) ** Command line: BOOT_IMAGE=/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/vg1-lv1 ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: LENOVO product_name: 20DSS02300 product_version: ThinkPad L450 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: JDET49WW (1.11 ) board_vendor: LENOVO board_name: Intel powered classmate PC board_version: Not Defined ** Loaded modules: ctr ccm binfmt_misc snd_hda_codec_hdmi btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev snd_hda_codec_realtek snd_hda_codec_generic media snd_hda_intel iTCO_wdt snd_hda_codec iTCO_vendor_support arc4 snd_hda_core intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hwdep i915 irqbypass snd_pcm iwlmvm mac80211 iwlwifi intel_cstate rtsx_pci_ms memstick drm_kms_helper drm snd_timer intel_uncore intel_rapl_perf joydev evdev i2c_algo_bit serio_raw pcspkr thinkpad_acpi nvram mei_me mei lpc_ich cfg80211 snd rfkill sg ac wmi battery video shpchp soundcore button intel_pch_thermal sunrpc 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 sd_mod hid_generic usbhid hid rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ahci libahci aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd rtsx_pci mfd_core psmouse libata i2c_i801 scsi_mod xhci_pci i2c_smbus ehci_pci xhci_hcd ehci_hcd e1000e ptp usbcore pps_core usb_common thermal ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) Subsystem: Lenovo Broadwell-U Host Bridge -OPI [17aa:503c] 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: bdw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:503c] 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:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:503c] 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 Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI]) Subsystem: Lenovo Wildcat Point-LP USB xHCI Controller [17aa:503c] 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 Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03) Subsystem: Lenovo Wildcat Point-LP MEI Controller [17aa:503c] 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 (3) I218-V [8086:15a3] (rev 03) Subsystem: Lenovo Ethernet Connection (3) I218-V [17aa:503c] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
Bug#883935: linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring)
Package: src:linux Version: 4.9.65-3 Followup-For: Bug #883935 Dear Maintainer, I have the same issue, and I find it very annoying. As a workaround I use kernel linux-image-4.12.0-1-amd64, which mostly manages to wake correctly from hibernation. But honestly, I'm a bit overstrained in using a testing kernel on an otherwise stable system. I was hoping that the recent update of 4.9.0 kernel maybe fixed the issue, but unfortunately not. It would be very nice if this could be fixed with a future update. Thank you in advance! Christoph -- Package-specific info: ** Version: Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3 (2017-12-03) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 root=UUID=39cb1350-d7bf-43e6-9a89-f1821f0ae9b9 ro quiet i915.preliminary_hw_support=1 ** Tainted: PUO (4161) * Proprietary module has been loaded. * Userspace-defined naughtiness. * Out-of-tree module has been loaded. ** Kernel log: [ 167.358244] ata1.00: supports DRM functions and may not be fully accessible [ 167.358695] ata1.00: configured for UDMA/133 [ 167.383405] usb 1-4: reset high-speed USB device number 2 using xhci_hcd [ 167.643093] usb 1-7: reset full-speed USB device number 5 using xhci_hcd [ 167.903455] usb 1-6: reset full-speed USB device number 3 using xhci_hcd [ 167.910793] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [ 167.946771] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [ 168.163211] usb 1-9: reset full-speed USB device number 8 using xhci_hcd [ 168.422910] usb 1-8: reset high-speed USB device number 7 using xhci_hcd [ 168.830965] usb 1-4.2: reset low-speed USB device number 6 using xhci_hcd [ 169.387447] usb 1-4.1: reset low-speed USB device number 4 using xhci_hcd [ 169.720828] PM: restore of devices complete after 2684.862 msecs [ 169.721308] usb 1-7:1.0: rebind failed: -517 [ 169.721313] usb 1-7:1.1: rebind failed: -517 [ 169.721665] PM: Image restored successfully. [ 169.721774] PM: Basic memory bitmaps freed [ 169.721780] Restarting tasks ... done. [ 169.731277] thermal thermal_zone2: failed to read out thermal zone (-5) [ 169.739769] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 169.746776] Bluetooth: hci0: Device revision is 5 [ 169.746777] Bluetooth: hci0: Secure boot is enabled [ 169.746778] Bluetooth: hci0: OTP lock is enabled [ 169.746779] Bluetooth: hci0: API lock is enabled [ 169.746779] Bluetooth: hci0: Debug lock is disabled [ 169.746780] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 169.751150] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.sfi [ 169.751153] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 169.865935] e1000e: eth1 NIC Link is Down [ 169.867438] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 170.075048] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 170.075720] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 170.079558] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.082036] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.212136] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.212626] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.309080] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 170.321546] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.323628] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.458950] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.459265] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 170.491370] [drm] RC6 on [ 170.553392] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 170.603365] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 170.629381] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 170.825772] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input23 [ 171.338681] Bluetooth: hci0: Waiting for firmware download to complete [ 171.338772] Bluetooth: hci0: Firmware loaded in 1562047 usecs [ 171.338958] Bluetooth: hci0: Waiting for device to boot [ 171.349737] Bluetooth: hci0: Device booted in 10636 usecs [ 171.349930] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.ddc [ 171.349932] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [ 171.353746] Bluetooth: hci0: Applying Intel DDC parameters completed [ 174.173465] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 182.459087] [drm] GPU HANG: ecode 9:0:0x81ba3c75, in Xorg [709], reason: Hang on render ring, action: reset [ 182.459089] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 182.459090] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 182.459091] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 182.459092] [drm] The gp
Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
FWIW, I run into exact same kernel panic on R810. Downgrading to 3.16.43-2+deb8u5 "resolved" the problem. -- Marek
Bug#884009: firmware: failed to load pci errors in syslog
Package: firmware-atheros Version: 20170823-1 Severity: normal Dear Maintainer, * What led up to the situation? Error showing up during boot. * What exactly did you do (or not do) that was effective (or ineffective)? Start my computer. * What was the outcome of this action? My computer started. * What outcome did you expect instead? Explosions. Dec 10 13:24:42 fdt kernel: [1.405461] ath10k_pci :04:00.0: firmware: failed to load ath10k/pre-cal-pci-:04:00.0.bin (-2) Dec 10 13:24:42 fdt kernel: [1.405471] ath10k_pci :04:00.0: firmware: failed to load ath10k/cal-pci-:04:00.0.bin (-2) Dec 10 13:24:42 fdt kernel: [1.406338] ath10k_pci :04:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/firmware-6.bin Dec 10 13:24:42 fdt kernel: [1.406341] ath10k_pci :04:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Dec 10 13:24:42 fdt kernel: [1.406343] ath10k_pci :04:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 Dec 10 13:24:42 fdt kernel: [1.406672] ath10k_pci :04:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-atheros depends on no packages. firmware-atheros recommends no packages. Versions of packages firmware-atheros suggests: ii initramfs-tools 0.130 -- no debconf information
Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
I encountered this on an old Intel SR1600 box with Westmere Xeons. I have an Ivy Bridge E5-1620v2 physical box that has booted successfully with this kernel, and I haven't seen any problem among the dozen or so VMs that have so far rebooted onto it (VMware ESXi 6.0/6.5, on dual E5 Xeon Sandy Bridge/Ivy Bridge/Haswell/Broadwell). As with previous reporters, reverting to 3.16.43-2+deb8u5 avoids the problem. Details of the problematic system as follows: ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/raid1-root ro quiet ** Tainted: I (2048) * Working around severe firmware bug. ** Kernel log: [ 5.810814] ioatdma :00:16.4: irq 95 for MSI/MSI-X [ 5.811126] ioatdma :00:16.5: irq 96 for MSI/MSI-X [ 5.811438] ioatdma :00:16.6: irq 97 for MSI/MSI-X [ 5.811752] ioatdma :00:16.7: irq 98 for MSI/MSI-X [ 5.875627] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 5.913072] ipmi message handler version 39.2 [ 5.950042] EDAC MC: Ver: 3.0.0 [ 5.962572] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [ 5.962578] ACPI: Sleep Button [SLPB] [ 5.962625] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 5.962627] ACPI: Power Button [PWRF] [ 5.974649] SSE version of gcm_enc/dec engaged. [ 5.978346] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 6.022862] EDAC MC1: Giving out device to module i7core_edac.c controller i7 core #1: DEV :fe:03.0 (POLLED) [ 6.022894] EDAC PCI0: Giving out device to module i7core_edac controller EDAC PCI controller: DEV :fe:03.0 (POLLED) [ 6.023304] EDAC MC0: Giving out device to module i7core_edac.c controller i7 core #0: DEV :ff:03.0 (POLLED) [ 6.023329] EDAC PCI1: Giving out device to module i7core_edac controller EDAC PCI controller: DEV :ff:03.0 (POLLED) [ 6.023600] EDAC i7core: Driver loaded, 2 memory controller(s) found. [ 6.062760] cdc_acm 7-1:1.0: This device cannot do calls on its own. It is not a modem. [ 6.062885] cdc_acm 7-1:1.0: ttyACM0: USB ACM device [ 6.064546] usbcore: registered new interface driver cdc_acm [ 6.064549] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 6.072093] IPMI System Interface driver. [ 6.072121] ipmi_si: probing via ACPI [ 6.072143] ipmi_si 00:02: [io 0x0ca2] regsize 1 spacing 1 irq 0 [ 6.072144] ipmi_si: Adding ACPI-specified kcs state machine [ 6.072156] ipmi_si: probing via SMBIOS [ 6.072158] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0 [ 6.072159] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface [ 6.072161] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 [ 6.122134] input: PC Speaker as /devices/platform/pcspkr/input/input2 [ 6.215855] ipmi_si 00:02: Found new BMC (man_id: 0x000157, prod_id: 0x003e, dev_id: 0x21) [ 6.215869] ipmi_si 00:02: IPMI kcs interface initialized [ 6.639127] hidraw: raw HID events driver (C) Jiri Kosina [ 6.727507] alg: No test for crc32 (crc32-pclmul) [ 6.853789] iTCO_vendor_support: vendor-support=0 [ 6.857666] usbcore: registered new interface driver usbhid [ 6.857668] usbhid: USB HID core driver [ 6.885272] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 6.885304] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [ 6.911461] [drm] Initialized drm 1.1.0 20060810 [ 6.995935] input: Dell Dell USB Keyboard as /devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/0003:413C:2003.0001/input/input3 [ 6.996179] hid-generic 0003:413C:2003.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-:00:1a.1-1/input0 [ 6.996349] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.0/0003:046B:FF10.0002/input/input4 [ 6.996455] hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-:00:1a.2-1/input0 [ 6.996622] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.1/0003:046B:FF10.0003/input/input5 [ 6.996956] hid-generic 0003:046B:FF10.0003: input,hidraw2: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-:00:1a.2-1/input1 [ 7.014469] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround [ 7.565424] Adding 11717628k swap on /dev/sdb5. Priority:-1 extents:1 across:11717628k FS [ 8.905845] XFS (dm-1): Mounting V4 Filesystem [ 8.921306] XFS (dm-2): Mounting V4 Filesystem [ 9.319538] XFS (dm-4): Mounting V4 Filesystem [ 9.484788] XFS (dm-5): Mounting V4 Filesystem [ 9.564591] XFS (dm-5): Starting recovery (logdev: internal) [ 9.666941] XFS (dm-5): Ending recovery (logdev: internal) [ 9.696815] XFS (dm-6): Mounting V4 Filesystem [ 9.718313] XF
Bug#883938: Sun Fire X4200 M2 too
Hi, Reproduced it on a Sun Fire X4200 M2 too, screenshot attached. Could we increase the severity to critical like Debian bug #883294? It downed a production server ;( Downgrading to "3.16.43-2+deb8u5 (2017-09-19)" fixed it. Elmar
Bug#883976: marked as done (nfs-common: Shell script executed by systemd to mount net /home * /var fails)
Your message dated Sun, 10 Dec 2017 15:21:14 + with message-id <1512919274.2723.4.ca...@decadent.org.uk> and subject line Re: Bug#883976: nfs-common: Shell script executed by systemd to mount net /home * /var fails has caused the Debian Bug report #883976, regarding nfs-common: Shell script executed by systemd to mount net /home * /var fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.3.4-2.1 Severity: grave Justification: renders package unusable Netboot file system on /devnfs (except that dev/nfs causes errors) so rootfs is mounted per fstab. Trying to mount nfs file system for var and home and the mount fails. When linux is fully up, and I'm logged into a user, su to root the file systems can be mounted with no error message. Why during boot are the messages: mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/var /var in /etc/fstab mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/home /home in /etc/fstab being generated as though the root id during boot is a normal unprivilaged unser? fstab: proc /proc procdefaults 0 0 /dev/mmcblk0p1 /boot vfatdefaults,ro 0 2 #PARTUUID=62bc0a1f-02/ ext4defaults,noatime 0 1 192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0 #192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0 #192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 #browne:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 tmpfs/tmptmpfs nodev,nosuid,size=1%,mode=1777 0 0 systemctl unit: [Unit] Description=Setup directory tree in var filesystem DefaultDependencies=no After=local-fs.target Before=basic.target [Service] Type=oneshot ExecStart=/usr/bin/setup-var-home.sh [Install] WantedBy=basic.target hostname: b827ebc23849 /usr/bin/setup-var-home.sh: #!/bin/bash H=$(hostname); #H="b827ebc23849"; /bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/var /var"; /bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/home /home"; systemctl status ● setup-var-home.service - Setup directory tree in var filesystem Loaded: loaded (/lib/systemd/system/setup-var-home.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2017-12-09 13:43:43 PST; 22min ago Process: 267 ExecStart=/usr/bin/setup-var-home.sh (code=exited, status=1/FAILURE) Main PID: 267 (code=exited, status=1/FAILURE) Dec 09 13:43:42 b827ebc23849 systemd[1]: Starting Setup directory tree in var filesystem... Dec 09 13:43:43 b827ebc23849 setup-var-home.sh[267]: mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/var /var in /etc/fstab Dec 09 13:43:43 b827ebc23849 setup-var-home.sh[267]: mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/home /home in /etc/fstab Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Main process exited, code=exited, status=1/FAILURE Dec 09 13:43:43 b827ebc23849 systemd[1]: Failed to start Setup directory tree in var filesystem. Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Unit entered failed state. Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Failed with result 'exit-code'. mount command output 192.168.1.10:/nfsroot/r.32.test on / type nfs (rw,relatime,vers=3,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.10,mountvers=3,mountp$ devtmpfs on /dev type devtmpfs (rw,relatime,size=405220k,nr_inodes=101305,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/cpuset type cgrou
Bug#883980: Steps to Duplicate Problem
After a clean reboot, I began experimenting to find repeatable steps to duplicate the problem. I have the following programs running across 9 workspaces (which are always running on my machine): Chromium & gPHPEdit, Web (Ephiphany) & Geany, and Terminator (running a split screen). The problem does not manifest itself yet. I open a Terminal running Screen plus Files (Nautilus) plus Document Viewer (Evince). Then the problem begins to manifest itself, and it grows worse as I experiment. FIRST MANIFESTATION: I open a youtube video in Chromium and it begins playing. When I move my mouse pointer from the surrounding page across the embedded video, or back again, the screen goes black for 1 second. This manifestation is not sporadic. It happens almost every single time, provided the above conditions are met. SECOND MANIFESTATION: When I type something in Terminator, the screen goes black for 1 second. This manifestation is sporadic. It happens from time to time, provided the above conditions are met. THIRD MANIFESTATION: When I open Software, and I type a term in the Search field, the screen goes black for 1 second. This manifestation is sporadic. I happens only sometimes. FOURTH MANIFESTATION: When I type into Bash running in Terminal, the screen goes black for 1 second. This manifestation is sporadic. I happens only sometimes. OBSERVATION: As I experiment and open additional copies of Document Viewer (Evince), the problem seems to get much worse. The screen goes black for longer periods of time, and when it returns, it is frequently scrambled up, goes black again, and then returns to normal. NOTE: I have 8GB of RAM. I have been routinely doing these activities and much more for the past 4 months, with no problems. I do not believe that I am near to maxing out memory. This problem appeared with the upgrade to Debian 9.3. I am looking into how I can downgrade the kernel without causing further problems. This is my only, my primary work machine. I cannot afford to screw it up. I don't have a second computer to experiment with. Sorry. I am happy to help with any reasonable troubleshooting steps. Thanks.
Bug#883938: Same problem with KVM
I had the same problem with my VMs under Proxmox/KVM. After changing CPU structure from "2 socket 1 CPU" to "1 socket 2 CPU" the problem was gone. Only enabling/disabling NUMA didn't work. So I think it's a problem with aktivating second prozessor.
Bug#883938: Sun Fire X4200 M2 Xen
Hi, Update: probably reproduced the bug in Xen on a Sun Fire X4200 M2 ;( After 4.5 hours, it froze so hard that I could not power it off via the iLOM, even Num Lock wouldn't work. After rebooting, lock-ups occurred in about 5-30 minutes. There is nothing in the syslog. After downgrading the Dom0+Xen kernel, the problem persisted. Downgraded all Dom0 kernels as well, waiting for next lockup :I Elmar
Bug#883938: Sun Fire X4200 M2 Xen
Hi, The non-booting machines have multiple CPUs: * X4200M2: 2 AMD 2220, no Xen, LVM * X2200M2: 2 AMD 2347HE The booting machine has multiple CPUs as well, but Xen is configured to give only 1 vCPU to Doms. * X4200M2: 2 AMD 2220, Xen The freezing machine might have a HW problem or might be hit by Debian bug #880554 as even after downgrading all DomU and Dom0 kernels, the freeze still occurs, even though it boots. Elmar
Re: Bug#709879: espeak: Alsa lib underflow and clicking sounds.
Control: reassign -1 linux Hello, Really sorry this apparently went unnoticed for so long. anton, on dim. 26 mai 2013 19:19:32 +1000, wrote: > Espeak does not start normally and throws out the error message: > ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred > Hundreds of times. It does it when the computer has been on for a while. > A reset is needed before it returns to normal for a few hours then the same > problem shows up again. Is it still an issue today? Since espeak is not running all that time along, this really rather looks like a kernel bug, thus reassigning. Samuel
Processed: Re: Bug#709879: espeak: Alsa lib underflow and clicking sounds.
Processing control commands: > reassign -1 linux Bug #709879 [espeak] espeak: Alsa lib underflow and clicking sounds. Bug reassigned from package 'espeak' to 'linux'. No longer marked as found in versions espeak/1.46.02-2. Ignoring request to alter fixed versions of bug #709879 to the same values previously set -- 709879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884061: linux-image-4.9.0-4-amd64: screen scrolls wildly
Package: src:linux Version: 4.9.65-3 Severity: normal Since upgrading to 4.9.65-3, my screen occasionally starts rapidly scrolling sideways, flashing on and off repeatedly... looks almost like the refresh rate or sync was off, and it's displaying the leftmost part of the screen on the rightmost or the top of the display in the middle of the screen and other similar behaviors... When this starts to happen, usually there is a log in the dmesg output like this: [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Closing the lid and openening it again seems to fix it for a while, or makes it less severe (e.g. brief moments where the screen slides around or flickers). I'm going to try to find the last kernel version before I upgraded and see if I the issue is also triggered on that... live well, vagrant -- Package-specific info: ** Version: Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3 (2017-12-03) ** Command line: BOOT_IMAGE=/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/yucca--vg-root ro quiet ** Not tainted ** Kernel log: [ 15.039432] tun: Universal TUN/TAP device driver, 1.6 [ 15.039434] tun: (C) 1999-2004 Max Krasnyansky [ 20.700661] input: BYDPS/2 BYD TouchPad as /devices/platform/i8042/serio1/input/input16 [ 80.954137] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [ 170.836656] PM: Syncing filesystems ... done. [ 170.842268] PM: Preparing system for sleep (mem) [ 170.842382] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 170.843569] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done. [ 170.846679] PM: Suspending system (mem) [ 170.846687] Suspending console(s) (use no_console_suspend to debug) [ 170.846858] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 170.847683] sd 0:0:0:0: [sda] Stopping disk [ 171.622232] PM: suspend of devices complete after 775.439 msecs [ 171.641624] PM: late suspend of devices complete after 19.389 msecs [ 171.642387] xhci_hcd :00:14.0: System wakeup enabled by ACPI [ 171.681571] PM: noirq suspend of devices complete after 39.943 msecs [ 171.681842] ACPI: Preparing to enter system sleep state S3 [ 171.681903] ACPI : EC: event blocked [ 171.681903] ACPI : EC: EC stopped [ 171.681904] PM: Saving platform NVS memory [ 171.681905] Disabling non-boot CPUs ... [ 171.683157] smpboot: CPU 1 is now offline [ 171.683865] Broke affinity for irq 49 [ 171.684874] smpboot: CPU 2 is now offline [ 171.685248] Broke affinity for irq 1 [ 171.685255] Broke affinity for irq 9 [ 171.685260] Broke affinity for irq 12 [ 171.685273] Broke affinity for irq 47 [ 171.685274] Broke affinity for irq 49 [ 171.686288] smpboot: CPU 3 is now offline [ 171.687652] ACPI: Low-level resume complete [ 171.687705] ACPI : EC: EC started [ 171.687706] PM: Restoring platform NVS memory [ 171.688023] Suspended for 4.062 seconds [ 171.688050] Enabling non-boot CPUs ... [ 171.688106] x86: Booting SMP configuration: [ 171.688106] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 171.690656] cache: parent cpu1 should not be sleeping [ 171.690885] CPU1 is up [ 171.690936] smpboot: Booting Node 0 Processor 2 APIC 0x3 [ 171.693606] cache: parent cpu2 should not be sleeping [ 171.694177] CPU2 is up [ 171.694277] smpboot: Booting Node 0 Processor 3 APIC 0x2 [ 171.697493] cache: parent cpu3 should not be sleeping [ 171.698318] CPU3 is up [ 171.706857] ACPI: Waking up from system sleep state S3 [ 171.727103] xhci_hcd :00:14.0: System wakeup disabled by ACPI [ 171.747157] PM: noirq resume of devices complete after 40.223 msecs [ 171.747360] PM: early resume of devices complete after 0.186 msecs [ 171.747431] ACPI : EC: event unblocked [ 171.747529] ath: phy0: ASPM enabled: 0x43 [ 171.757620] sd 0:0:0:0: [sda] Starting disk [ 171.820062] rtc_cmos 00:03: System wakeup disabled by ACPI [ 172.070341] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 172.070732] ata1.00: supports DRM functions and may not be fully accessible [ 172.072477] ata1.00: disabling queued TRIM support [ 172.073107] ata1.00: supports DRM functions and may not be fully accessible [ 172.073834] ata1.00: disabling queued TRIM support [ 172.074067] ata1.00: configured for UDMA/133 [ 172.175151] PM: resume of devices complete after 427.782 msecs [ 172.175516] PM: Finishing wakeup. [ 172.175518] Restarting tasks ... done. [ 172.267311] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 172.295044] usb 1-5: new full-speed USB device number 6 using xhci_hcd [ 172.309093] r8169 :02:00.0 enp2s0: link down [ 172.309140] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 172.310073] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 172.415056] usb 1-5: device descriptor read/64, error -71 [ 172.643192] usb 1-5: device descriptor read/64, error -71 [ 172.875059] usb 1-5: new full-speed USB device number 7 using xhc
Bug#883980: Fifth Manifestation
I was using the latest, built-in version of Firefox ESR 52.5.2 (64-bit), and I noticed that I got the same, consistent problem as with Chromium. When I move the mouse cursor between surrounding page and embedded video (either direction), the screen goes black for 1 second. This behavior is identical to what I experience in Chromium. This is the list of applications for which I have seen this problem so far: Chromium Terminator Terminal running Bash Software Firefox ESR
Bug#883938: HP ProLiant DL360 Gen9
Hi, I also got some hardware refusing to boot with this bug : HP ProLiant DL360 Gen9 The crash is instant, right after GRUB loads the kernel and initramfs. Partial backtrace (re-typed from a KVM screen capture) : [0.649289] Call Trace: [0.649362] [] ? sched_init_smp+0x398/0x452 [0.649437] [] ? mutex_lock+0xe/0x2a [0.649512] [] ? put_online_cpus+0x23/0x80 [0.649587] [] ? stop_machine+0x2c/0x40 [0.649662] [] ? kernel_init_freeable+0xdd/0x1e1 [0.649738] [] ? rest_init+0x80/0x80 [0.649813] [] ? kernel_init+0xa/0xf0 [0.649888] [] ? ret_from_fork+0x58/0x90 [0.649963] [] ? rest_init+0x80/0x80 [0.650037] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e 8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75 [0.653853] RIP [] build_sched_domains+0x72d/0xcf0 [0.653986] RSP [0.654061] ---[ end trace 5d1a1ddbcedef31d ]--- [0.654145] Kernel panic - not syncing: Attempted to kill init! exit code=0x000b [0.654145] [0.654252] ---[ end Kernel panic - not syncing: Attempted to kill init! exit code=0x000b [0.654252] I could only fix the issue by downgrading. It should be noted that even after the downgrade, it reports this error, if there is any chance of relevance : [0.059876] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330) Cheers, -- ラピー ステファン Lapie Stephane 株式会社朝日ネット システム部 AsahiNet, Inc. - System Division
Bug#883938: same issue
Have the same issue (kernel panic) after kernel upgade this night. I had to restore the old kernel+initrd+modules from backup (Linux xxx 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux). Server: HP ProLiant DL380 G6 # lspci 00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 13) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13) 00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 2 (rev 13) 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) 00:04.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 4 (rev 13) 00:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5 (rev 13) 00:06.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 6 (rev 13) 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) 00:08.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 8 (rev 13) 00:09.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 13) 00:0a.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 10 (rev 13) 00:0d.0 Host bridge: Intel Corporation Device 343a (rev 13) 00:0d.1 Host bridge: Intel Corporation Device 343b (rev 13) 00:0d.2 Host bridge: Intel Corporation Device 343c (rev 13) 00:0d.3 Host bridge: Intel Corporation Device 343d (rev 13) 00:0d.4 Host bridge: Intel Corporation 7500/5520/5500/X58 Physical Layer Port 0 (rev 13) 00:0d.5 Host bridge: Intel Corporation 7500/5520/5500 Physical Layer Port 1 (rev 13) 00:0d.6 Host bridge: Intel Corporation Device 341a (rev 13) 00:0e.0 Host bridge: Intel Corporation Device 341c (rev 13) 00:0e.1 Host bridge: Intel Corporation Device 341d (rev 13) 00:0e.2 Host bridge: Intel Corporation Device 341e (rev 13) 00:0e.3 Host bridge: Intel Corporation Device 341f (rev 13) 00:0e.4 Host bridge: Intel Corporation Device 3439 (rev 13) 00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 13) 00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13) 00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13) 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.3 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIB (ICH10) LPC Interface Controller 01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) 01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03) 01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 03) 01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller 01:04.6 IPMI SMIC interface: Hewlett-Packard Company Integrated Lights-Out Standard KCS Interface 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 04:00.0 RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01) 14:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller (rev 11) 3e:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) 3e:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder (rev 02) 3e:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02) 3e:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02) 3e:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 02) 3e:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 02) 3e:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02) 3e:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02) 3e:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers (rev 02) 3e:03.1 Ho
Bug#884069: Kernel crash on boot on IBM BladeCenter HS22
Package: linux-image-3.16.0-4-amd64 Version: 3.16.51-2 Loading Linux 3.16.0-4-amd64 ... Loading initial ramdisk ... [0.604128] general protection fault: [#1] SMP [0.609303] Modules linked in: [0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW 3.16.0-4-amd64 #1 Debian 3.16.51-2 [0.621685] Hardware name: IBM BladeCenter HS22 -[7870SGX]-/68Y8077, BIOS -[P9E163AUS-1.24]- 09/17/2014 [0.631141] task: 8803731392d0 ti: 88037313c000 task.ti: 88037313c000 [0.638684] RIP: 0010:[] [] build_sched_domains+0x72d/0xcf0 [0.647609] RSP: :88037313fdf8 EFLAGS: 00010216 [0.652982] RAX: RBX: RCX: 0012 [0.660175] RDX: 00016f48 RSI: RDI: 0200 [0.667372] RBP: 880372f5d698 R08: 880372f5e0e0 R09: 0139 [0.674566] R10: R11: 88037313fb06 R12: 880372f5e0c0 [0.681761] R13: 0200 R14: 880672e640c0 R15: 0200 [0.688958] FS: () GS:88037fc0() knlGS: [0.697110] CS: 0010 DS: ES: CR0: 8005003b [0.702914] CR2: 88067000 CR3: 01813000 CR4: 07f0 [0.710109] Stack: [0.712183] 8806 880372f5e0d8 880372f5d600 880672e640c0 [0.719940] 880372f53e00 [0.727715] f1c8 [0.735501] Call Trace: [0.738022] [] ? sched_init_smp+0x398/0x452 [0.743930] [] ? mutex_lock+0xe/0x2a [0.749229] [] ? put_online_cpus+0x23/0x80 [0.755050] [] ? stop_machine+0x2c/0x40 [0.760618] [] ? kernel_init_freeable+0xdd/0x1e1 [0.766963] [] ? rest_init+0x80/0x80 [0.772264] [] ? kernel_init+0xa/0xf0 [0.777652] [] ? ret_from_fork+0x58/0x90 [0.783298] [] ? rest_init+0x80/0x80 [0.788595] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e 8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75 [0.812501] RIP [] build_sched_domains+0x72d/0xcf0 [0.819101] RSP [0.822668] ---[ end trace b6ea7a8f78a6ba93 ]--- [0.827375] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [0.827375] [0.836621] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [0.836621]
Bug#883938: HP ProLiant DL360 Gen9
One more bit of info if it helps. I noticed that I had some ProLiant DL360 Gen9 servers that booted fine with that version. The main difference between the ones that failed booting had more CPU cores detected than the ones that succeeded. For reference, the successful one had 20, the failed one had 32. Given the kernel panic seems to be scheduler related, are there any chances this is an edge case for servers with tons of CPUs? Cheers, -- ラピー ステファン Lapie Stephane 株式会社朝日ネット システム部 AsahiNet, Inc. - System Division
Bug#884069: system cannot boot after upgrade to Debian 8.10
Severity: critical
Bug#884069: the same problem on different hardware
Loading Linux 3.16.0-4-amd64 ... Loading initial ramdisk ... [0.349165] general protection fault: [#1] SMP [0.352000] Modules linked in: [0.352000] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW 3.16.0-4-amd64 #1 Debian 3.16.51-2 [0.352000] Hardware name: Sun Microsystems Sun Fire X2200 M2 /S39 , BIOS S39_3B27 02/04/2009 [0.352000] task: 88021b4dd2d0 ti: 88021b4f task.ti: 88021b4f [0.352000] RIP: 0010:[] [] build_sched_domains+0x72d/0xcf0 [0.352000] RSP: :88021b4f3df8 EFLAGS: 00010216 [0.352000] RAX: RBX: RCX: 0002 [0.352000] RDX: 00016cc8 RSI: RDI: 0200 [0.352000] RBP: 88021b5d1d98 R08: 88021b5d0760 R09: 00f4 [0.352000] R10: R11: 88021b4f3b06 R12: 88021b5d0740 [0.352000] R13: 0200 R14: 88021b58cac0 R15: 0200 [0.352000] FS: () GS:880223c0() knlGS: [0.352000] CS: 0010 DS: ES: CR0: 8005003b [0.352000] CR2: 880323fff000 CR3: 01813000 CR4: 07f0 [0.352000] Stack: [0.352000] 8802 88021b5d0758 88021b5d1d00 88021b58cac0 [0.352000] 880323418e00 [0.352000] f1c8 [0.352000] Call Trace: [0.352000] [] ? sched_init_smp+0x398/0x452 [0.352000] [] ? mutex_lock+0xe/0x2a [0.352000] [] ? put_online_cpus+0x23/0x80 [0.352000] [] ? stop_machine+0x2c/0x40 [0.352000] [] ? kernel_init_freeable+0xdd/0x1e1 [0.352000] [] ? rest_init+0x80/0x80 [0.352000] [] ? kernel_init+0xa/0xf0 [0.352000] [] ? ret_from_fork+0x58/0x90 [0.352000] [] ? rest_init+0x80/0x80 [0.352000] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e 8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75 [0.352000] RIP [] build_sched_domains+0x72d/0xcf0 [0.352000] RSP [0.352006] ---[ end trace 68d23c2290c77ca9 ]--- [0.356017] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [0.356017] [0.36] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [0.36]
Bug#884069: Kernel crash on boot on IBM BladeCenter HS22
Control: severity -1 critical On Mon, Dec 11, 2017 at 09:14:27AM +0200, Rolandas Naujikas wrote: Hi, > Package: linux-image-3.16.0-4-amd64 > Version: 3.16.51-2 > > Loading Linux 3.16.0-4-amd64 ... > Loading initial ramdisk ... > [0.604128] general protection fault: [#1] SMP > [0.609303] Modules linked in: > [0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW > 3.16.0-4-amd64 #1 Debian 3.16.51-2 > [0.621685] Hardware name: IBM BladeCenter HS22 -[7870SGX]-/68Y8077, > BIOS -[P9E163AUS-1.24]- 09/17/2014 > [0.631141] task: 8803731392d0 ti: 88037313c000 task.ti: > 88037313c000 > [0.638684] RIP: 0010:[] [] > build_sched_domains+0x72d/0xcf0 > [0.647609] RSP: :88037313fdf8 EFLAGS: 00010216 > [0.652982] RAX: RBX: RCX: > 0012 > [0.660175] RDX: 00016f48 RSI: RDI: > 0200 > [0.667372] RBP: 880372f5d698 R08: 880372f5e0e0 R09: > 0139 > [0.674566] R10: R11: 88037313fb06 R12: > 880372f5e0c0 > [0.681761] R13: 0200 R14: 880672e640c0 R15: > 0200 > [0.688958] FS: () GS:88037fc0() > knlGS: > [0.697110] CS: 0010 DS: ES: CR0: 8005003b > > [0.702914] CR2: 88067000 CR3: 01813000 CR4: > 07f0 > [0.710109] Stack: > [0.712183] 8806 880372f5e0d8 880372f5d600 > 880672e640c0 > [0.719940] > 880372f53e00 > [0.727715] f1c8 > > [0.735501] Call Trace: > [0.738022] [] ? sched_init_smp+0x398/0x452 > > [0.743930] [] ? mutex_lock+0xe/0x2a > [0.749229] [] ? put_online_cpus+0x23/0x80 > > [0.755050] [] ? stop_machine+0x2c/0x40 > > [0.760618] [] ? kernel_init_freeable+0xdd/0x1e1 > > [0.766963] [] ? rest_init+0x80/0x80 > [0.772264] [] ? kernel_init+0xa/0xf0 > > [0.777652] [] ? ret_from_fork+0x58/0x90 > > [0.783298] [] ? rest_init+0x80/0x80 > [0.788595] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd > a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e > 8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75 > > [0.812501] RIP [] build_sched_domains+0x72d/0xcf0 > > [0.819101] RSP > [0.822668] ---[ end trace b6ea7a8f78a6ba93 ]--- > [0.827375] Kernel panic - not syncing: Attempted to kill init! > exitcode=0x000b > [0.827375] > [0.836621] ---[ end Kernel panic - not syncing: Attempted to kill > init! exitcode=0x000b > [0.836621] Seeing the same on two Dell R610 after the point release. Bernhard
Processed: Re: Bug#884069: Kernel crash on boot on IBM BladeCenter HS22
Processing control commands: > severity -1 critical Bug #884069 [linux-image-3.16.0-4-amd64] Kernel crash on boot on IBM BladeCenter HS22 Severity set to 'critical' from 'normal' -- 884069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems