Bug#846492: linux-image-4.8.0-1-686-pae: frequently crash during boot
Hi, switching to linux-image-4.11.0-1-amd64 it continues to crash but in a non fatal way: you get tty1-6 console and with CTRL-ALT-F7 you also get the GUI. Jul 12 14:31:21 computer kernel: [ 330.676179] [ cut here ] Jul 12 14:31:21 computer kernel: [ 330.676212] WARNING: CPU: 0 PID: 603 at / build/linux-C5oXKu/linux-4.11.6/drivers/gpu/drm/drm_irq.c:1199 drm_wait_one_vblank+0x197/0x1a0 [drm] Jul 12 14:31:21 computer kernel: [ 330.676213] vblank wait timed out on crtc 1 Jul 12 14:31:21 computer kernel: [ 330.676214] Modules linked in: rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd grace fscache snd_hrtimer snd_seq snd_seq_device iTCO_wdt iTCO_vendor_support yenta_socket pcmcia_rsrc acer_wmi tifm_7xx1 tifm_core sparse_keymap lpc_ich mfd_core coretemp nsc_ircc snd_hda_codec_hdmi arc4 irda crc_ccitt snd_hda_codec_realtek snd_hda_codec_generic b43 bcma pcspkr mac80211 joydev cfg80211 rfkill sg serio_raw rng_core snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer battery snd ac soundcore shpchp evdev hwmon_vid parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb crypto_simd cryptd glue_helper aes_x86_64 mbcache sd_mod sr_mod cdrom ata_generic hid_generic usbhid hid psmouse i2c_i801 ahci libahci firewire_ohci Jul 12 14:31:21 computer kernel: [ 330.676266] ata_piix sdhci_pci sdhci firewire_core crc_itu_t libata scsi_mod ssb mmc_core pcmcia pcmcia_core tg3 ptp pps_core libphy i915 ehci_pci thermal wmi uhci_hcd ehci_hcd usbcore video usb_common button i2c_algo_bit drm_kms_helper drm Jul 12 14:31:21 computer kernel: [ 330.676286] CPU: 0 PID: 603 Comm: Xorg Tainted: GW 4.11.0-1-amd64 #1 Debian 4.11.6-1 Jul 12 14:31:21 computer kernel: [ 330.676287] Hardware name: Acer Extensa 5220 /Columbia , BIOS V1.34 04/15/2008 Jul 12 14:31:21 computer kernel: [ 330.676288] Call Trace: Jul 12 14:31:21 computer kernel: [ 330.676295] ? dump_stack+0x5c/0x78 Jul 12 14:31:21 computer kernel: [ 330.676298] ? __warn+0xbe/0xe0 Jul 12 14:31:21 computer kernel: [ 330.676300] ? warn_slowpath_fmt+0x5a/0x80 Jul 12 14:31:21 computer kernel: [ 330.676312] ? drm_wait_one_vblank +0x197/0x1a0 [drm] Jul 12 14:31:21 computer kernel: [ 330.676314] ? remove_wait_queue+0x60/0x60 Jul 12 14:31:21 computer kernel: [ 330.676327] ? drm_atomic_state_clear +0x20/0x20 [drm] Jul 12 14:31:21 computer kernel: [ 330.676379] ? intel_get_load_detect_pipe +0x60f/0x660 [i915] Jul 12 14:31:21 computer kernel: [ 330.676404] ? intel_tv_detect+0x160/0x570 [i915] Jul 12 14:31:21 computer kernel: [ 330.676437] ? __ext4_handle_dirty_metadata+0x41/0x1b0 [ext4] Jul 12 14:31:21 computer kernel: [ 330.676450] ? drm_helper_probe_single_connector_modes+0x2ec/0x550 [drm_kms_helper] Jul 12 14:31:21 computer kernel: [ 330.676455] ? drm_helper_probe_single_connector_modes+0x2ec/0x550 [drm_kms_helper] Jul 12 14:31:21 computer kernel: [ 330.676467] ? drm_mode_getconnector +0x2e2/0x310 [drm] Jul 12 14:31:21 computer kernel: [ 330.676478] ? drm_ioctl+0x1ef/0x440 [drm] Jul 12 14:31:21 computer kernel: [ 330.676490] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] Jul 12 14:31:21 computer kernel: [ 330.676493] ? do_vfs_ioctl+0x9f/0x600 Jul 12 14:31:21 computer kernel: [ 330.676496] ? vfs_write+0x154/0x190 Jul 12 14:31:21 computer kernel: [ 330.676497] ? SyS_ioctl+0x74/0x80 Jul 12 14:31:21 computer kernel: [ 330.676500] ? system_call_fast_compare_end+0xc/0x9b Jul 12 14:31:21 computer kernel: [ 330.676501] ---[ end trace b93fcfebe43b85ad ]--- As suggested here https://bugs.freedesktop.org/show_bug.cgi?id=93782#c40 adding "video=SVIDEO-1:d" disable the S-Video connector and workaround completely the crashes ... Regards! Guido
Mis nooit meer oproepen, of klanten
Vergelijk nu de aanbiedingen voor telefooncentrales voor Dupont J Klik hier http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=https%3A%2F%2Fwww.companeo.be%2Fnl_BE%2Ftelefooncentrales%2Fspoed-offerte-aanvraag%2Fmedia%2F3680_0517%3Fcid%3D%26qcp%3D3680_R0517_DATA_BENL%23utm_source%3Dn%26utm_medium%3De-mail%26utm_campaign%3Dnewsc%26utm_nooverride%3D1&h=67c387c67a7807441d97bd86bc71d9c5&linkid=003B8Y_9965920&type=external&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 . Mijn Account http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=https%3A%2F%2Fuser.companeo.be%2F%3Fcid%3D&h=aba55af993aef317ccfeadd40650f1b1&linkid=003B8Y_24871393&type=external&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 0800 50 600 http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=tel%3A0800%2050%20600&h=eff73169a82b72b8998565ea59ac&linkid=003B8Y_29383130&type=external&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 TELEFOONCENTRALE: KIES VOOR EEN KWALITATIEF ONTHAAL AAN DE TELEFOON http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=https%3A%2F%2Fwww.companeo.be%2Fnl_BE%2Ftelefooncentrales%2Fspoed-offerte-aanvraag%2Fmedia%2F3680_0517%3Fcid%3D%26qcp%3D3680_R0517_DATA_BENL%23utm_source%3Dn%26utm_medium%3De-mail%26utm_campaign%3Dnewsc%26utm_nooverride%3D1&h=67c387c67a7807441d97bd86bc71d9c5&linkid=003B8Y_27656639&type=external&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=https%3A%2F%2Fwww.companeo.be%2Fnl_BE%2Ftelefooncentrales%2Fspoed-offerte-aanvraag%2Fmedia%2F3680_0517%3Fcid%3D%26qcp%3D3680_R0517_DATA_BENL%23utm_source%3Dn%26utm_medium%3De-mail%26utm_campaign%3Dnewsc%26utm_nooverride%3D1&h=67c387c67a7807441d97bd86bc71d9c5&linkid=003B8Y_45376502&type=external&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 Beste , Geniet van alle voordelen van een telefooncentrale: http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=https%3A%2F%2Fwww.companeo.be%2Fnl_BE%2Ftelefooncentrales%2Fspoed-offerte-aanvraag%2Fmedia%2F3680_0517%3Fcid%3D%26qcp%3D3680_R0517_DATA_BENL%23utm_source%3Dn%26utm_medium%3De-mail%26utm_campaign%3Dnewsc%26utm_nooverride%3D1&h=67c387c67a7807441d97bd86bc71d9c5&linkid=003B8Y_71619588&type=external&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 Mobiel: uw smartphones zijn permanent verbonden aan de centrale: beheer van overal uw oproepen en berichten en schakel door. Prijs: goedkopere abonnementen en communicatiekosten tot -60% dankzij bellen via het internet. Gebruiksgemak: u kunt uw toestellen eenvoudig aansluiten/ontkoppelen/verhuizen. Vergelijk de aanbiedingen http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=https%3A%2F%2Fwww.companeo.be%2Fnl_BE%2Ftelefooncentrales%2Fspoed-offerte-aanvraag%2Fmedia%2F3680_0517%3Fcid%3D%26qcp%3D3680_R0517_DATA_BENL%23utm_source%3Dn%26utm_medium%3De-mail%26utm_campaign%3Dnewsc%26utm_nooverride%3D1&h=67c387c67a7807441d97bd86bc71d9c5&linkid=003B8Y_43461909&type=external&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 Companeo nv: EEBIC, Researchdreef 12, 1070 Anderlecht, België - tel: 0800 50 600 Ondernemingsnummer: BE0871.041.687. VU: L. Horwitz, U hebt recht op inzage,correctie en verwijdering van uw gegevens, zoals voorzien in de wet van 8 december 1992 tot de bescherming van het privé-leven. Volg deze link om http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=http%3A%2F%2Flbv5.mperf.com%2Fform.aspx%3FGV1%3DTDGX02L0003D1M001B61A3003B94&h=598d1ef8ec1df96bd831d3354bb0cfbc&linkid=003B8Y_919134&type=form&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 niet langer berichten te ontvangen over Telefooncentrale. Volg deze link om http://tr.info-companeo.be/redirectUrl?GV1=TDGX02L003D1M001B61A30&targetUrl=http%3A%2F%2Flbv5.mperf.com%2Fform.aspx%3FGV1%3DTDGX02L0003D1M001B61A30001GM&h=6776d95ebb8534b59a4e81c9673268a4&linkid=003B8Y_24567504&type=form&source=text&uk=eb0795a027c215ec2aca23f9c2833e85&cardId=8f0861b66b7c2563d4a9a09190399827&domainId=2dcbbd8fc3f1470da25bed1e41f3a752&flag=1 niet langer berichten te ontvangen van Companeo
Bug#868224: linux-image-4.9.0-3-amd64: Upgrade to linux-image-4.9.0-3-amd64 hangs while or after generating initrd
Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
I upgraded to the latest stable kernel via apt-get upgrade. The upgrade
hangs at the following point:
linux-image-4.9.0-3-amd64 (4.9.30-2+deb9u2) wird eingerichtet ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.9.0-3-amd64
After waiting a couple of hours I interrupted the upgrade. After that I
tried dpkg --configure -a or apt-get -f install but the result was
always the same.
I trid to build the initrd file manually via
update-initramfs -u -t
which worked and created the file /boot/initrd.img-4.9.0-3-amd64
Another apt-get -f install leads to the same problem that the upgrade
hangs with
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.9.0-3-amd64
I don't know if that's related to bug #865301
Thanks for any help on that
-- 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=/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/vg00-lvRoot ro quiet
** Tainted: O (4096)
* Out-of-tree module has been loaded.
** Kernel log:
[582958.060279] bond0: first active interface up!
[582958.060290] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[582958.463563] ixgbe :03:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control:
None
[582958.476182] bond0: link status up for interface eth1, enabling it in 200 ms
[582958.684323] bond0: link status definitely up for interface eth1, 1000 Mbps
full duplex
[582976.421902] traps: SHCLIP[4960] general protection ip:7fa1d5eb1865
sp:7fa1b963aa30 error:0
[582976.421909] in libc-2.24.so[7fa1d5e7c000+195000]
[582976.683613] vboxnetflt: 0 out of 724589 packets were not sent (directed to
host)
[58.314841] VBoxNetFlt: attached to 'eth0' / a4:bf:01:13:f4:8c
[584582.164755] vboxnetflt: 0 out of 3993 packets were not sent (directed to
host)
[685004.192759] usb 4-6: USB disconnect, device number 3
[699768.222763] device bond0 left promiscuous mode
[699768.222767] device eth0 left promiscuous mode
[699768.223605] device eth1 left promiscuous mode
[699768.297287] vboxnetflt: 5018 out of 97411155 packets were not sent
(directed to host)
[727534.436845] vboxdrv: c020 VMMR0.r0
[727534.547763] vboxdrv: c0116020 VBoxDDR0.r0
[727534.724402] VBoxNetFlt: attached to 'bond0' / a4:bf:01:13:f4:8c
[727534.744630] device bond0 entered promiscuous mode
[727534.744634] device eth0 entered promiscuous mode
[727534.745463] device eth1 entered promiscuous mode
[762062.166807] bin2asc[15118]: segfault at 13891 ip 00013891 sp
7ffd2323ec58 error 14 in bin2asc[40+3000]
[762072.948390] bin2asc[15471]: segfault at 13891 ip 00013891 sp
7fffc97c9348 error 14 in bin2asc[40+3000]
[919035.967241] mce: [Hardware Error]: Machine check events logged
[919035.967272] {1}Hardware error detected on CPU0
[919035.967275] {1}It has been corrected by h/w and requires no further action
[919035.967276] {1}event severity: corrected
[919035.967279] {1} Error 0, type: corrected
[919035.967280] {1} section_type: memory error
[919035.967282] {1} physical_address: 0x001bcd8f5000
[919035.967284] {1} node: 1 card: 1 module: 0 rank: 0
[919035.967286] {1} error_type: 0, unknown
[919035.967288] {1} DIMM location: not present. DMI handle: 0x0002
[1258407.948266] traps: psppire[11680] trap stack segment ip:7f71e1801b0e
sp:7ffd17ae5260 error:0
[1258407.948277] in libpspp-core-0.10.2.so[7f71e17af000+101000]
[1260703.139751] psppire[43223]: segfault at 2 ip 7f3be1c2a646 sp
7fff505746d8 error 4 in libc-2.24.so[7f3be1baa000+195000]
[1272614.636375] VBoxNetFlt: Failed to allocate packet buffer, dropping the
packet.
[1642221.016282] device bond0 left promiscuous mode
[1642221.016285] device eth0 left promiscuous mode
[1642221.017066] device eth1 left promiscuous mode
[1642221.222923] bond0: Removing slave eth0
[1642221.223201] bond0: Releasing backup interface eth0
[1642221.223204] bond0: the permanent HWaddr of eth0 - a4:bf:01:13:f4:8c - is
still in use by bond0 - set the HWaddr of eth0 to a different address to avoid
conflicts
[1642221.223207] bond0: first active interface up!
[1642221.253609] ixgbe :03:00.0: removed PHC on eth0
[1642221.592821] bond0: Removing slave eth1
[1642221.593074] bond0: Removing an active aggregator
[1642221.593079] bond0: Releasing backup interface eth1
[1642221.617723] ixgbe :03:00.1: removed PHC on eth1
[164.420602] bond0: Setting MII monitoring interval to 10
Processed: severity 867259 important
Processing commands for cont...@bugs.debian.org: > severity 867259 important Bug #867259 [linux-image-4.9.0-3-amd64] Massiv problems with hardware ttySx (RS-232) Severity set to 'important' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 867259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > retitle 846492 vblank wait timed out on crtc error starting from linux- Bug #846492 [src:linux] linux-image-4.8.0-1-686-pae: frequently crash during boot Changed Bug title to 'vblank wait timed out on crtc error starting from linux-' from 'linux-image-4.8.0-1-686-pae: frequently crash during boot'. > image-4.8.0-1 Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 846492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867259: No usage of ttySx any more
Hello,
I have found the following problem that has been fixed in kernel 4.9.5:
https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.5
commit 1f363639eb30c2a4ef9ff125e2fbfe213d82a2f9
Author: Herbert Xu
Date: Sun Dec 11 10:05:49 2016 +0800
Revert "tty: serial: 8250: add CON_CONSDEV to flags"
commit 6741f551a0b26479de2532ffa43a366747e6dbf3 upstream.
This commit needs to be reverted because it prevents people from
using the serial console as a secondary console with input being
directed to tty0.
IOW, if you boot with console=ttyS0 console=tty0 then all kernels
prior to this commit will produce output on both ttyS0 and tty0
but input will only be taken from tty0. With this patch the serial
console will always be the primary console instead of tty0,
potentially preventing people from getting into their machines in
emergency situations.
Fixes: d03516df8375 ("tty: serial: 8250: add CON_CONSDEV to flags")
Signed-off-by: Herbert Xu
Signed-off-by: Greg Kroah-Hartman
Maybe this is the reason causing the problem in kernel 4.9.0?
Best regards
Karsten
Bug#867259: No usage of ttySx any more
Hello kernel developers, i am sorry but i must increase the severity of this bug because i can't use the serial interfaces any more! After i switched off the server and rebooted the interfaces are not working any more. I get permanent input/output errors acessing the serial interfaces. This is independent the driver mcs9865 is loaded. Please help, otherwise Debian 9.0 can't be used if you want to use serial interfaces. Here is some debug output: setserial -g /dev/ttyS[0-7] /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: 16550A, Port: 0xd110, IRQ: 21 /dev/ttyS2, UART: 16550A, Port: 0xd100, IRQ: 21 /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3 stty -F /dev/ttyS2 19200 stty: /dev/ttyS2: Eingabe-/Ausgabefehler Can't Open /dev/ttyS2 dmesg | grep ttyS [1.151893] 00:09: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [1.152344] :01:06.0: ttyS1 at I/O 0xe110 (irq = 21, base_baud = 115200) is a 16550A [1.152428] :01:06.0: ttyS2 at I/O 0xe100 (irq = 21, base_baud = 115200) is a 16550A [ 11.647618] ttyS1: LSR safety check engaged! [ 11.648682] ttyS1: LSR safety check engaged! [ 11.651136] ttyS2: LSR safety check engaged! [ 11.651924] ttyS2: LSR safety check engaged! Best regards Karsten
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 846492 vblank wait timed out on crtc error from linux-image-4.8.0-1 Bug #846492 [src:linux] vblank wait timed out on crtc error starting from linux- Changed Bug title to 'vblank wait timed out on crtc error from linux-image-4.8.0-1' from 'vblank wait timed out on crtc error starting from linux-'. > End of message, stopping processing here. Please contact me if you need assistance. -- 846492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868195: marked as done (The adapter works but does not connect to any network in Kernel 4.9 in Stretch)
Your message dated Thu, 13 Jul 2017 11:59:23 +0100 with message-id <1499943563.2707.127.ca...@decadent.org.uk> and subject line Re: Bug#868195: The adapter works but does not connect to any network in Kernel 4.9 in Stretch has caused the Debian Bug report #868195, regarding The adapter works but does not connect to any network in Kernel 4.9 in Stretch 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.) -- 868195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-atheros Version: 20161130-3 Priority: optional Section: non-free/kernel Source: firmware-nonfree Maintainer: Debian Kernel Team Version: Debian 9 Stable XFCE Affect firmware-atheros package for TP-LINK adapters that works but does not connect to any network in Debian 9 using kernel 4.9. -- Package-specific info: ** Environment settings: INTERFACE="gtk2" ** /home/debian/.reportbugrc: reportbug_version "7.1.7" mode novice ui text realname "package:firmware-atheros" email "leandrocunha...@gmail.com" -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt1.4.6 ii python33.5.3-1 ii python3-reportbug 7.1.7 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate pn emacs24-bin-common | emacs25-bin-common ii exim4 4.89-2+deb9u1 ii exim4-daemon-light [mail-transport-agent] 4.89-2+deb9u1 ii file 1:5.30-1 ii gir1.2-gtk-3.0 3.22.11-1 ii gir1.2-vte-2.910.46.1-1 ii gnupg 2.1.18-6 ii python3-gi 3.22.0-2 ii python3-gi-cairo 3.22.0-2 pn python3-gtkspellcheck pn python3-urwid ii xdg-utils 1.1.1-1 Versions of packages python3-reportbug depends on: ii apt1.4.6 ii file 1:5.30-1 ii python33.5.3-1 ii python3-debian 0.1.30 ii python3-debianbts 2.6.1 ii python3-requests 2.12.4-1 python3-reportbug suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Closing, this is not a driver package. Ben. -- Ben Hutchings Design a system any fool can use, and only a fool will want to use it. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
forwarded #864642 https://bugzilla.kernel.org/show_bug.cgi?id=191201 thanks Am 11.07.2017 um 10:24 schrieb Patrick Matthäi: > found #864642 4.9.30-2+deb9u2 > thanks > > And it still crashes.. > > > Am 22.06.2017 um 14:58 schrieb Patrick Matthäi: >> found #864642 4.9.30-2+deb9u1 >> thanks >> >> >> Am 12.06.2017 um 10:02 schrieb Patrick Matthäi: >>> Package: src:linux >>> Version: 4.9.30-1 >>> Severity: important >>> File: linux >>> >>> Dear Maintainer, >>> >>> *** Reporter, please consider answering these questions, where >>> appropriate *** >>> >>> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to >>> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the >>> "primary" interface this: >>> >>> TCP: ens192: Driver has suspect GRO implementation, TCP performance may >>> be compromised. >>> >>> I can't see any performance impact. This happens on all our vSphere 6.0 >>> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML >>> 350 G9 and so on). >>> >>> Why is this bug important? Because on one VM this also produces a kernel >>> panic after some time (minutes or hours). I just could get the panic >>> attached as screenshot. The only "big" difference between the crashing >>> host and the others may be, that it is also running PM2, NPM, NodeJS and >>> a NFS kernel server. >>> >>> If I boot the VM with 4.9.30-1 and deactivate gro and lro with: >>> ethtool -K ens192 gro off >>> ethtool -K ens192 lro off >>> .. it does not crash. >>> >>> Booting 4.9.18-1 and everything is completly fine ;) >>> >> The VM keeps on crashing after a few hours >> -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Processed: Re: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
Processing commands for cont...@bugs.debian.org: > forwarded #864642 https://bugzilla.kernel.org/show_bug.cgi?id=191201 Bug #864642 [src:linux] vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=191201'. > thanks Stopping processing here. Please contact me if you need assistance. -- 864642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868244: linux-image-4.11.0-1-amd64: Kernel 4.11.0-1 fails to boot with amdgpu and AMD RX560.
Package: src:linux Version: 4.11.6-1 Severity: critical Justification: breaks the whole system Dear Maintainer, With previous kernel 4.9.0-3 everything works as expected with `amdgpu`. After upgrade to 4.11.0-1 system never boots and get stuck on "fb: switching to amdgpudrmfb from EFI VGA". If I specify `nomodeset` as boot parameter, system will boot but Wayland becomes unavailable as desktop option. X.Org does work however it just says "Unknown display" and doesn't see other display at all, am assuming without hardware acceleration. Video of the whole boot process: https://www.youtube.com/watch?v=IvFUICWzja4 More crisp image of boot process without boot_delay at the place of freeze: http://i.imgur.com/eAP3jWt.jpg Hardware in guestion is AMD's RX560. Small note, there's screen corruption seen at the top left. This is not on image, but screen itself. Happens almost always, not sure if it's relevant. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 1402 board_vendor: ASUSTeK COMPUTER INC. board_name: P8B75-M LE board_version: Rev X.0x ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] 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: ivb_uncore Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] 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 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] 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:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:8415] 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:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VG
Re: Bug#865645: Missing USB3503.ko for Arndale development board
Hi,
Cyril Brulebois (2017-06-23):
> Since it seems to be an “USB 2.0 hub controller driver”, I suppose this
> should be in usb-modules and not specifically in nic-usb-modules. Since
> the drivers/usb/misc might have various unneeded things, I've chosen not
> to add this directory to usb-modules, but to include the usb3503 module
> specifically on the two arm{hf,64} archs that ship it.
Refreshed patch against current sid branch attached (context change in
debian/changelog, nothing else).
> Kernel team: Please note that there's a similar driver, usb4604, but
> that one isn't even enabled as a module in the current (sid) kernel
> configuration.
That's still the case.
> A backport of this addition to stretch would be welcome.
I guess this won't be before 9.2 now, adjusted my task list accordingly
to make sure I don't lose track.
KiBi.
From 2767c30050ac65eaa54980cd202573c3bcefd5c0 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois
Date: Fri, 23 Jun 2017 21:36:16 +0200
Subject: [PATCH] [arm64,armhf] udeb: Ship usb3503 module in usb-modules
(Closes: #865645)
This module is needed for e.g. Arndale development boards, thanks to Wei
Liu.
---
debian/changelog | 4
debian/installer/arm64/modules/arm64/usb-modules | 1 +
debian/installer/armhf/modules/armhf-armmp/usb-modules | 1 +
3 files changed, 6 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 6834557..87f9ff3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -237,6 +237,10 @@ linux (4.11.9-1) UNRELEASED; urgency=medium
* Bump ABI to 2
* [rt] Update to 4.11.8-rt5
+ [ Cyril Brulebois ]
+ * [arm64,armhf] udeb: Ship usb3503 module in usb-modules, needed for
+e.g. Arndale development boards, thanks to Wei Liu (Closes: #865645).
+
-- Ben Hutchings Tue, 20 Jun 2017 19:18:44 +0100
linux (4.11.6-1) unstable; urgency=medium
diff --git a/debian/installer/arm64/modules/arm64/usb-modules b/debian/installer/arm64/modules/arm64/usb-modules
index 7614f23..0d2a759 100644
--- a/debian/installer/arm64/modules/arm64/usb-modules
+++ b/debian/installer/arm64/modules/arm64/usb-modules
@@ -1,3 +1,4 @@
#include
dwc2
dwc3
+usb3503
diff --git a/debian/installer/armhf/modules/armhf-armmp/usb-modules b/debian/installer/armhf/modules/armhf-armmp/usb-modules
index 7e20ccb..5917b7f 100644
--- a/debian/installer/armhf/modules/armhf-armmp/usb-modules
+++ b/debian/installer/armhf/modules/armhf-armmp/usb-modules
@@ -1,3 +1,4 @@
#include
omap-ocp2scp
extcon-usb-gpio
+usb3503
--
2.1.4
signature.asc
Description: Digital signature
Processed: Re: Bug#868242: open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13
Processing commands for cont...@bugs.debian.org: > reassign 868242 src:linux Bug #868242 [open-vm-tools] open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13 Bug reassigned from package 'open-vm-tools' to 'src:linux'. No longer marked as found in versions open-vm-tools/2:10.1.5-5055683-4. Ignoring request to alter fixed versions of bug #868242 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 868242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868195: closed by Ben Hutchings (Re: Bug#868195: The adapter works but does not connect to any network in Kernel 4.9 in Stretch)
This package is a firmware for several models of TP-Link boards. So without this firmware the device does not work. This package contains the binary firmware for USB wireless network and Bluetooth cards supported by the ar5523, ath3k, ath6kl_sdio, ath6kl_usb, ath9k_htc or ath10k drivers. * Atheros AR3012 rev 01020001 patch (ar3k/AthrBT_0x01020001.dfu) * Atheros AR3012 rev 01020200 patch (ar3k/AthrBT_0x01020200.dfu) * Atheros AR3012 rev 01020201 patch, version 170 (ar3k/AthrBT_0x01020201.dfu) * Atheros AR3012 rev 1102 patch (ar3k/AthrBT_0x1102.dfu) * Atheros AR3012 rev 11020100 patch (ar3k/AthrBT_0x11020100.dfu) * Atheros AR3012 rev 3101 patch (ar3k/AthrBT_0x3101.dfu) * Atheros AR3012 rev 31010100 patch (ar3k/AthrBT_0x31010100.dfu) * Atheros AR3012 rev 4102 patch (ar3k/AthrBT_0x4102.dfu) * Atheros AR3012 rev 01020001 config (ar3k/ramps_0x01020001_26.dfu) * Atheros AR3012 rev 01020200 26 MHz config (ar3k/ramps_0x01020200_26.dfu) * Atheros AR3012 rev 01020200 40 MHz config (ar3k/ramps_0x01020200_40.dfu) * Atheros AR3012 rev 01020201 26 MHz config (ar3k/ramps_0x01020201_26.dfu) * Atheros AR3012 rev 01020201 40 MHz config (ar3k/ramps_0x01020201_40.dfu) * Atheros AR3012 rev 1102 config (ar3k/ramps_0x1102_40.dfu) * Atheros AR3012 rev 11020100 config (ar3k/ramps_0x11020100_40.dfu) * Atheros AR3012 rev 3101 config (ar3k/ramps_0x3101_40.dfu) * Atheros AR3012 rev 31010100 config (ar3k/ramps_0x31010100_40.dfu) * Atheros AR3012 rev 4102 config (ar3k/ramps_0x4102_40.dfu) * Atheros AR5523 firmware (ar5523.bin) * Atheros AR7010 rev 1.0 firmware (ar7010.fw) * Atheros AR7010 rev 1.1 firmware (ar7010_1_1.fw) * Atheros AR9271 firmware (ar9271.fw) * Qualcomm Atheros QCA4019 rev 1.0 board configuration, version 2 (ath10k/QCA4019/hw1.0/board-2.bin) * Qualcomm Atheros QCA4019 rev 1.0 firmware, version 10.4-3.2.1-00028 (ath10k/QCA4019/hw1.0/firmware-5.bin) * Qualcomm Atheros QCA6174 rev 2.1 board configuration, version 1 (ath10k/QCA6174/hw2.1/board.bin) * Qualcomm Atheros QCA6174 rev 2.1 board configuration, version 2 (ath10k/QCA6174/hw2.1/board-2.bin) * Qualcomm Atheros QCA6174 rev 2.1 firmware, version SW_RM.1.1.1-00157-QCARMSWPZ-1 (ath10k/QCA6174/hw2.1/firmware-5.bin) * Qualcomm Atheros QCA6174 rev 3.0 board configuration, version 1 (ath10k/QCA6174/hw3.0/board.bin) * Qualcomm Atheros QCA6174 rev 3.0 board configuration, version 2 (ath10k/QCA6174/hw3.0/board-2.bin) * Qualcomm Atheros QCA6174 rev 3.0 firmware, version WLAN.RM.2.0-00180-QCARMSWPZ-1 (ath10k/QCA6174/hw3.0/firmware-4.bin) * Qualcomm Atheros QCA9377 rev 1.0 board configuration, version 1 (ath10k/QCA9377/hw1.0/board.bin) * Qualcomm Atheros QCA9377 rev 1.0 board configuration, version 2 (ath10k/QCA9377/hw1.0/board-2.bin) * Qualcomm Atheros QCA9377 rev 1.0 firmware, version WLAN.TF.1.0-00267-1 (ath10k/QCA9377/hw1.0/firmware-5.bin) * Qualcomm Atheros QCA9987 rev 1.0 board configuration, version 1 (ath10k/QCA9887/hw1.0/board.bin) * Qualcomm Atheros QCA9987 rev 1.0 firmware, version 10.2.4-1.0-00013. (ath10k/QCA9887/hw1.0/firmware-5.bin) * Qualcomm Atheros QCA9988 rev 2.0 board configuration, version 2 (ath10k/QCA9888/hw2.0/board-2.bin) * Qualcomm Atheros QCA9988 rev 2.0 firmware, version 10.4-3.2-00072 (ath10k/QCA9888/hw2.0/firmware-5.bin) * Qualcomm Atheros QCA988X board configuration, version 1 (ath10k/QCA988X/hw2.0/board.bin) * Qualcomm Atheros QCA988X firmware, version 10.2.4.45 (ath10k/QCA988X/hw2.0/firmware-4.bin) * Qualcomm Atheros QCA988X firmware, version 10.2.4.70.54 (ath10k/QCA988X/hw2.0/firmware-5.bin) * Qualcomm Atheros QCA9984 rev 1.0 board configuration, version 2 (ath10k/QCA9984/hw1.0/board-2.bin) * Qualcomm Atheros QCA9984 rev 1.0 firmware, version 10.4-3.2-00072 (ath10k/QCA9984/hw1.0/firmware-5.bin) * Qualcomm Atheros QCA99X0 board configuration, version 1 (ath10k/QCA99X0/hw2.0/board.bin) * Qualcomm Atheros QCA99X0 firmware, version 10.4.1.00030-1 (ath10k/QCA99X0/hw2.0/firmware-5.bin) * Atheros AR3011 firmware (ath3k-1.fw) * ath6k/AR6003.1/hw2.1.1/athwlan.bin * ath6k/AR6003.1/hw2.1.1/bdata.SD31.bin * ath6k/AR6003.1/hw2.1.1/bdata.SD32.bin * ath6k/AR6003.1/hw2.1.1/bdata.WB31.bin * ath6k/AR6003.1/hw2.1.1/data.patch.bin * ath6k/AR6003.1/hw2.1.1/endpointping.bin * ath6k/AR6003.1/hw2.1.1/otp.bin * ath6k/AR6003/hw1.0/athwlan.bin.z77 * ath6k/AR6003/hw1.0/bdata.SD31.bin * ath6k/AR6003/hw1.0/bdata.SD32.bin * ath6k/AR6003/hw1.0/bdata.WB31.bin * ath6k/AR6003/hw1.0/data.patch.bin * ath6k/AR6003/hw1.0/otp.bin.z77 * ath6k/AR6003/hw2.0/athwlan.bin.z77 * ath6k/AR6003/hw2.0/bdata.SD31.bin * ath6k/AR6003/hw2.0/bdata.SD32.bin * ath6k/AR6003/hw2.0/bdata.WB31.bin * ath6k/AR6003/hw2.0/data.patch.bin * ath6k/AR6003/hw2.0/otp.bin.z77 * ath6k/AR6003/hw2.1.1/athwlan.bin * ath6k/AR6003/hw2.1.1/bdata.SD31.bin * ath6k/AR6003/hw2.1.1/bdata.SD32.bin * ath6k/AR6003/hw2.1.1/bdata.WB31.bin *
Re: Bug#866130: Missing sunxi_wdt.ko for cubietruck
Hi, Wei Liu (2017-06-27): > Package: debian-installer-9-netboot-armhf > Severity: normal > Tags: d-i > > The cubietruck board uses the onboard watchdog to reset. > > Without the said module d-i can't reboot the board after installation > is finished. I've just had a quick look but even if there are many watchdogs available, there doesn't seem to be any of them shipped in a udeb package, so I'm not sure what to use for a proposed patch… Suggestions welcome. (Item moved from my 9.1 task list to the 9.2 one.) KiBi. signature.asc Description: Digital signature
Processing of linux-latest_80+deb9u1_amd64.changes
linux-latest_80+deb9u1_amd64.changes uploaded successfully to localhost along with the files: linux-latest_80+deb9u1.dsc linux-latest_80+deb9u1.tar.xz linux-doc_4.9+80+deb9u1_all.deb linux-headers-amd64_4.9+80+deb9u1_amd64.deb linux-headers-rt-amd64_4.9+80+deb9u1_amd64.deb linux-image-amd64-dbg_4.9+80+deb9u1_amd64.deb linux-image-amd64_4.9+80+deb9u1_amd64.deb linux-image-rt-amd64-dbg_4.9+80+deb9u1_amd64.deb linux-image-rt-amd64_4.9+80+deb9u1_amd64.deb linux-latest_80+deb9u1_amd64.buildinfo linux-perf_4.9+80+deb9u1_all.deb linux-source_4.9+80+deb9u1_all.deb linux-tools_4.9+80+deb9u1_all.deb xen-linux-system-amd64_4.9+80+deb9u1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-latest_80+deb9u1_amd64.changes is NEW
Mapping stretch to stable. Mapping stable to proposed-updates. binary:linux-image-4kc-malta-dbg is NEW. binary:linux-image-5kc-malta-dbg is NEW. binary:linux-image-686-dbg is NEW. binary:linux-image-686-pae-dbg is NEW. binary:linux-image-amd64-dbg is NEW. binary:linux-image-arm64-dbg is NEW. binary:linux-image-armmp-dbg is NEW. binary:linux-image-armmp-lpae-dbg is NEW. binary:linux-image-loongson-3-dbg is NEW. binary:linux-image-marvell-dbg is NEW. binary:linux-image-octeon-dbg is NEW. binary:linux-image-powerpc64le-dbg is NEW. binary:linux-image-rt-686-pae-dbg is NEW. binary:linux-image-rt-amd64-dbg is NEW. binary:linux-image-s390x-dbg is NEW. binary:linux-image-amd64-dbg is NEW. binary:linux-image-rt-amd64-dbg is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Bug#868195: Note
Remembering that I am doing everything according to the Debian Wiki. Package wireless-tools it installed. My internal Intel adapter is working perfectly. Link Debian Wiki about atheros devices https://wiki.debian.org/ath9k_htc https://packages.debian.org/stretch/wireless-tools https://wiki.debian.org/WiFi/HowToUse Packages affecteds https://packages.debian.org/stretch/linux-image-amd64 https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git https://packages.debian.org/stretch/firmware-atheros So ignoring this error report is ignoring a problem that may be of many users around the world and this would be a big mistake.
Bug#868251: dm-raid.ko not included in md-modules udeb
Source: linux Version: 4.9.30-2 Severity: normal It seems dm-raid.ko isn't in md-modules.udeb, or any other udeb on DVD-1. It'd be useful to have it there to allow install on LVM-RAID (which otherwise just requires an lvcreate or two on the command line). Also useful because it'd presumably allow the rescue mode to be used on such systems. [My apologies if you're not the right folks to ask—not sure if its the kernel team or the d-i team that I should be asking.] -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#868268: initramfs-tools: Please add raid1 to the module added when MODULES=most
Package: initramfs-tools Version: 0.130 Severity: normal Dear Maintainer, When using raid1 lvm root, the raid1 module is not added to the initrd built (raid456 module is in). This will make the system unbootable and goind to the initramfs debug mode Please add raid1 in when selecting MODULES=most As a workaround you can add raid1 to /etc/initramfs-tools/modules and do update-initramfs -k all -u -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 18M Jul 13 23:24 /boot/initrd.img-4.9.0-3-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/VGroot-LVslash ro quiet -- resume RESUME=none -- /proc/filesystems xfs -- lsmod Module Size Used by snd_hda_codec_generic69632 1 snd_hda_intel 36864 0 snd_hda_codec 135168 2 snd_hda_intel,snd_hda_codec_generic snd_hda_core 81920 3 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic snd_hwdep 16384 1 snd_hda_codec snd_pcm 110592 3 snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 32768 1 snd_pcm snd86016 6 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_pcm soundcore 16384 1 snd qxl69632 1 ttm98304 1 qxl drm_kms_helper155648 1 qxl edac_mce_amd 28672 0 drm 360448 4 qxl,ttm,drm_kms_helper ppdev 20480 0 edac_core 57344 0 pcspkr 16384 0 evdev 24576 1 serio_raw 16384 0 joydev 20480 0 virtio_balloon 16384 0 parport_pc 28672 0 virtio_console 24576 0 parport49152 2 parport_pc,ppdev sg 32768 0 acpi_cpufreq 20480 0 button 16384 0 ip_tables 24576 0 x_tables 36864 1 ip_tables autofs440960 2 xfs 1208320 1 raid1 36864 1 dm_raid40960 1 raid456 106496 1 dm_raid async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov md_mod131072 3 dm_raid,raid1,raid456 xor24576 1 async_xor raid6_pq 110592 3 async_pq,raid456,async_raid6_recov libcrc32c 16384 2 xfs,raid456 crc32c_generic 16384 1 dm_mod118784 16 dm_raid hid_generic16384 0 usbhid 53248 0 hid 122880 2 hid_generic,usbhid sr_mod 24576 0 cdrom 61440 1 sr_mod ata_generic16384 0 virtio_net 28672 0 virtio_blk 20480 4 psmouse 135168 0 floppy 69632 0 ata_piix 36864 0 ehci_pci 16384 0 uhci_hcd 45056 0 ehci_hcd 81920 1 ehci_pci usbcore 249856 4 usbhid,ehci_hcd,uhci_hcd,ehci_pci usb_common 16384 1 usbcore virtio_pci 24576 0 virtio_ring24576 5 virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci virtio 16384 5 virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci i2c_piix4 24576 0 libata249856 2 ata_piix,ata_generic scsi_mod 225280 3 libata,sr_mod,sg -- /etc/initramfs-tools/modules raid1 - /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=auto KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : [raid6] [raid5] [raid4] [raid1] unused devices: -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: dmsetup fsck keymap klibc-utils kmod lvm2 resume thermal udev zz-busybox -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.130 ii linux-base4.5 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: ii bash-completion 1:2.1-4.3 -- no debconf information
