Bug#935969: linux-image-5.2.0-2-amd64: Missing firmware for new driver rtwpci
Package: src:linux Version: 5.2.9-2 Severity: normal Dear Maintainer, My laptop has a Realtek Wifi card identified as such by lspci: 04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter (PCI IDs are 10ec:b822) I'm currnetly using a 5.1.0 kernel compiled from source, under which this card uses the r8822be driver, and works fine. (The reason I'm using a custom kernel is the MMC card reader, whose driver was buggy in the stock kernel previously shipped by Debian, but I'm pretty sure said stock kernel also used the same driver and that the Wifi card worked.) I now upgraded to the 5.2.0-2 kernel in the repos, which appears to be using a new driver for this card, called rtwpci. As indicated in the subject, this driver requires firmware which is not present, and which does not appear to exist in any free or non-free package: Aug 28 15:13:44 wolf kernel: [ 94.051293] rtw_pci :04:00.0: firmware: failed to load rtw88/rtw8822b_fw.bin (-2) Aug 28 15:13:44 wolf kernel: [ 94.052482] rtw_pci :04:00.0: Direct firmware load for rtw88/rtw8822b_fw.bin failed with error -2 Aug 28 15:13:44 wolf kernel: [ 94.053714] rtw_pci :04:00.0: failed to request firmware Aug 28 15:13:44 wolf kernel: [ 94.060506] rtw_pci :04:00.0: failed to load firmware Aug 28 15:13:44 wolf kernel: [ 94.061764] rtw_pci :04:00.0: failed to setup chip efuse info Aug 28 15:13:44 wolf kernel: [ 94.063027] rtw_pci :04:00.0: failed to setup chip information Aug 28 15:13:44 wolf kernel: [ 94.066942] rtw_pci: probe of :04:00.0 failed with error -22 I did find a firmware file by that name on some random site that didn't seem too sketchy, and tried using it, but apparently to no avail: Aug 28 15:33:21 wolf kernel: [ 1217.459956] rtw_pci :04:00.0: firmware: direct-loading firmware rtw88/rtw8822b_fw.bin Aug 28 15:33:21 wolf kernel: [ 1217.463521] rtw_pci :04:00.0: mac power on failed Aug 28 15:33:21 wolf kernel: [ 1217.463530] rtw_pci :04:00.0: failed to power on mac Aug 28 15:33:21 wolf kernel: [ 1217.463532] rtw_pci :04:00.0: failed to setup chip efuse info Aug 28 15:33:21 wolf kernel: [ 1217.463535] rtw_pci :04:00.0: failed to setup chip information Aug 28 15:33:21 wolf kernel: [ 1217.464711] rtw_pci: probe of :04:00.0 failed with error -114 Whether that's due to some other technical issue or because the file I downloaded was the wrong one somehow, I have no way to tell. Anyway, if the appropriate firmware cannot be found or otherwise included, I would suggest disabling this rtwpci driver and revert to the r8822be driver, if possible. -- Fredrik Tolf -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20NECTO1WW product_version: ThinkPad E495 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: R11ET25W (1.05 ) board_vendor: LENOVO board_name: 20NECTO1WW board_version: Not Defined ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP
Bug#709525: nfs-common: After upgrade to 1.2.8-2, rpc.gssd segfaults on startup
Package: nfs-common Version: 1:1.2.8-2 Severity: important Dear Maintainer, After upgrading to 1.2.8-2 as part of normal Jessie upkeep, rpc.gssd started segfaulting immediately on startup, and I'm not really able to wrap my head around just why. The crash happens in libgssglue, in __gss_get_mechanism_cred, called by gss_init_sec_context, at g_init_sec_context.c:153 (still in libgssglue). It is rather clear that the crash happens because the copy of mglueP.h that is shipped with the source of libgssglue does not match that which is shipped with libkrb5. In the latter, the struct `gss_union_cred_t' has gained a new field called `loopback', and lost its `auxinfo' field, and when inspecting the gss_union_cred_t that has been passed to __gss_get_mechanism_cred, it clearly matched the definition from libkrb5. However, the fault does not seem to be lying with libgssglue, since the segafult only happens when nfs-common is upgraded, and downgrading nfs-common back to 1.2.6-3 makes it start working again. A simple guess from my side is that nfs-common has (erroneously?) been compiled against libkrb5 in some place where it should be compiled against libgssglue, perhaps? The structure and dependencies between the various packages involved is, however, far from obvious to me. (At the face of it, it seems like a hack, to begin with, that libgssglue has a local copy of a private header file from MIT Kerberos.) Whatever the problem is, it makes rpc.gssd, and therefore Kerberized NFS mounts, entirely unusable. Fix pl0x. :) -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000211 udp 33453 nlockmgr 1000213 udp 33453 nlockmgr 1000214 udp 33453 nlockmgr 1000211 tcp 54248 nlockmgr 1000213 tcp 54248 nlockmgr 1000214 tcp 54248 nlockmgr 172 udp708 ypbind 171 udp708 ypbind 172 tcp709 ypbind 171 tcp709 ypbind 1000241 udp 38590 status 1000241 tcp 43595 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD=yes NEED_GSSD=yes -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = dolda2000.com [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- home.nfs:/home /home nfs4sec=krb5i 0 0 home.nfs:/usr/site /usr/site nfs hard,intr,tcp 0 0 home.nfs:/video /home/pub/video nfs4sec=krb5i 0 0 -- /proc/mounts -- home.nfs:/home /home nfs4 rw,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.1.181,minorversion=0,local_lock=none,addr=192.168.1.1 0 0 home.nfs:/usr/site /usr/site nfs rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.1,mountvers=3,mountport=50152,mountproto=tcp,local_lock=none,addr=192.168.1.1 0 0 home.nfs:/video /home/pub/video nfs4 rw,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.1.181,minorversion=0,local_lock=none,addr=192.168.1.1 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-41 ii libc6 2.17-3 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.5-1.1 ii libdevmapper1.02.1 2:1.02.74-7 ii libevent-2.0-5 2.0.19-stable-3 ii libgssglue1 0.4-2 ii libk5crypto31.10.1+dfsg-5 ii libkeyutils11.5.5-7 ii libkrb5-3 1.10.1+dfsg-5 ii libmount1 2.20.1-5.4 ii libnfsidmap20.25-4 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-24 ii lsb-base4.1+Debian9 ii rpcbind 0.2.0-8 ii ucf 3.0025+nmu3 Versions of packages nfs-common recommends: ii python 2.7.3-5 Versions of packages nfs-common suggests: pn open-iscsi none pn watchdognone -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:
Bug#494444: linux-image-2.6.26-1-686: Another confirmation
Package: linux-image-2.6.26-1-686 Version: 2.6.26-11 Followup-For: Bug #49 I'd just like to file a me too on this bug. I can confirm that kacpid and kacpi_notify take ~90% of my CPU time together after I've had the laptop suspended to RAM, and also that, when I try to suspend to RAM again after that, it will not wake up again. It worked when I was running 2.6.24 (and I only recently upgrade, because previous 2.6.26 kernels had another, unrelated bug). My computer is a Dell Latitude D610. Dmidecode reports the BIOS version as A02. Unfortunately, I have no constructive information to add at this time. I'll try to find something out. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-11) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Nov 26 19:14:11 UTC 2008 ** Command line: root=/dev/sda6 ro ** Not tainted ** Kernel log: [28249.056071] PM: Writing back config space on device :00:1d.1 at offset f (was 200, writing 20a) [28249.056071] PM: Writing back config space on device :00:1d.1 at offset 8 (was 1, writing bf61) [28249.056071] usb usb2: root hub lost power or was reset [28249.056071] uhci_hcd :00:1d.2: enabling device ( - 0001) [28249.056071] ACPI: PCI Interrupt :00:1d.2[C] - GSI 18 (level, low) - IRQ 18 [28249.056071] PCI: Setting latency timer of device :00:1d.2 to 64 [28249.056071] PM: Writing back config space on device :00:1d.2 at offset f (was 300, writing 309) [28249.056071] PM: Writing back config space on device :00:1d.2 at offset 8 (was 1, writing bf41) [28249.056071] usb usb3: root hub lost power or was reset [28249.056071] uhci_hcd :00:1d.3: enabling device ( - 0001) [28249.056071] ACPI: PCI Interrupt :00:1d.3[D] - GSI 19 (level, low) - IRQ 19 [28249.056071] PCI: Setting latency timer of device :00:1d.3 to 64 [28249.056071] PM: Writing back config space on device :00:1d.3 at offset f (was 400, writing 405) [28249.056071] PM: Writing back config space on device :00:1d.3 at offset 8 (was 1, writing bf21) [28249.056071] usb usb4: root hub lost power or was reset [28249.069391] ACPI: PCI Interrupt :00:1d.7[A] - GSI 16 (level, low) - IRQ 16 [28249.069417] PCI: Setting latency timer of device :00:1d.7 to 64 [28249.069534] usb usb5: root hub lost power or was reset [28249.076160] ehci_hcd :00:1d.7: debug port 1 [28249.076160] PCI: cache line size of 32 is not supported by device :00:1d.7 [28249.076160] PM: Writing back config space on device :00:1e.0 at offset 9 (was 10001, writing 1fff1) [28249.076160] PM: Writing back config space on device :00:1e.0 at offset 8 (was 0, writing dfb0dfb0) [28249.076160] PM: Writing back config space on device :00:1e.0 at offset 7 (was 2280e0f0, writing 22802020) [28249.076160] PM: Writing back config space on device :00:1e.0 at offset 6 (was 20030300, writing 20070300) [28249.076160] PM: Writing back config space on device :00:1e.0 at offset 1 (was 15, writing 100107) [28249.076160] PCI: Setting latency timer of device :00:1e.0 to 64 [28249.076160] PM: Writing back config space on device :00:1e.2 at offset f (was 100, writing 10b) [28249.076160] PM: Writing back config space on device :00:1e.2 at offset 7 (was 0, writing dd00) [28249.076160] PM: Writing back config space on device :00:1e.2 at offset 6 (was 0, writing de00) [28249.076160] PM: Writing back config space on device :00:1e.2 at offset 5 (was 1, writing ec41) [28249.076160] PM: Writing back config space on device :00:1e.2 at offset 4 (was 1, writing ed01) [28249.076160] PM: Writing back config space on device :00:1e.2 at offset 1 (was 290, writing 293) [28249.076160] ACPI: PCI Interrupt :00:1e.2[A] - GSI 16 (level, low) - IRQ 16 [28249.076160] PCI: Setting latency timer of device :00:1e.2 to 64 [28250.170128] PM: Writing back config space on device :00:1e.3 at offset f (was 200, writing 20a) [28250.170184] PM: Writing back config space on device :00:1e.3 at offset 5 (was 1, writing ec81) [28250.170205] PM: Writing back config space on device :00:1e.3 at offset 4 (was 1, writing ee01) [28250.170234] PM: Writing back config space on device :00:1e.3 at offset 1 (was 290, writing 291) [28250.170287] ACPI: PCI Interrupt :00:1e.3[B] - GSI 17 (level, low) - IRQ 17 [28250.170315] PCI: Setting latency timer of device :00:1e.3 to 64 [28251.176343] PM: Writing back config space on device :00:1f.0 at offset 1 (was 207, writing 2000107) [28251.189495] PM: Writing back config space on device :00:1f.2 at offset f (was 200, writing 20a) [28251.189536] PM: Writing back config space on device :00:1f.2 at offset 9 (was d, writing 0) [28251.189618] ACPI: PCI Interrupt :00:1f.2[B] - GSI 17 (level, low) - IRQ 17 [28251.189642] PCI: Setting latency timer of device :00:1f.2 to 64 [28251.189698] PM: Writing back
Bug#489995: linux-image-2.6.24-1-amd64: Kernel NULL pointer dereference in NFS server
Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-7 Severity: normal I'm not sure what triggers it (it seems completely random), but every once in a while, my NFS server will log an Oops message in the kernel NFS server. It does seem to be recoverable, but I doubt it's a good thing. The dmesg from the event is as follows: Unable to handle kernel NULL pointer dereference at 0018 RIP: [882b8f7e] :sunrpc:rpc_shutdown_client+0xb5/0xd2 PGD 328c8067 PUD 1eb84067 PMD 0 Oops: [1] SMP CPU 1 Modules linked in: tcp_diag inet_diag des_generic cbc blkcipher nfs nfsd lockd nfs_acl exportfs ppdev parport_pc lp parport wlan_scan_ap sit tunnel4 sch_sfq cls_u32 cls_fw sch_htb ipt_REJECT iptable_filter xt_tcpudp ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 ipt_owner xt_DSCP xt_dscp xt_MARK iptable_mangle ip_tables x_tables xfs reiserfs nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack ipv6 rpcsec_gss_krb5 auth_rpcgss sunrpc loop snd_hda_intel psmouse ath_rate_sample pcspkr ath_pci wlan ath_hal(P) snd_pcm snd_timer snd soundcore serio_raw k8temp snd_page_alloc i2c_nforce2 i2c_core pl2303 usblp usbserial evdev ext3 jbd mbcache dm_mirror dm_snapshot dm_mod generic sd_mod amd74xx sata_nv ide_core r8169 forcedeth firewire_ohci firewire_core crc_itu_t sata_sil ata_generic ohci_hcd libata scsi_mod ehci_hcd Pid: 16606, comm: nfs4_cb_probe Tainted: P2.6.24-1-amd64 #1 RIP: 0010:[882b8f7e] [882b8f7e] :sunrpc:rpc_shutdown_client+0xb5/0xd2 RSP: 0018:8100018ade90 EFLAGS: 00010246 RAX: fffb RBX: RCX: 810001436fa0 RDX: 0002 RSI: fffb RDI: RBP: 810007482e00 R08: 882e2750 R09: 81000176e000 R10: 81000176e000 R11: 80273a34 R12: 0018 R13: R14: 80578f20 R15: FS: 2b898a7b1270() GS:81003f5e0a40() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: 0018 CR3: 3a173000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 4ff0 DR7: 0400 Process nfs4_cb_probe (pid: 16606, threadinfo 8100018ac000, task 81003d904800) Stack: 80578f20 0282 0282 81003e04c080 882be0ff fffb 810007482ec0 810007482e00 8100399dbbd0 884f34b2 Call Trace: [882be0ff] :sunrpc:rpc_put_task+0x6d/0x81 [884f34b2] :nfsd:do_probe_callback+0x48/0x6a [884f346a] :nfsd:do_probe_callback+0x0/0x6a [80247f03] kthread+0x47/0x74 [8020cc48] child_rip+0xa/0x12 [80247ebc] kthread+0x0/0x74 [8020cc3e] child_rip+0x0/0x12 Code: 4c 39 63 18 0f 85 73 ff ff ff 48 89 df e8 ec fd ff ff 48 83 RIP [882b8f7e] :sunrpc:rpc_shutdown_client+0xb5/0xd2 RSP 8100018ade90 CR2: 0018 ---[ end trace f553cdd2937e7544 ]--- -- Package-specific info: ** Version: Linux version 2.6.24-1-amd64 (Debian 2.6.24-7) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Sat May 10 09:28:10 UTC 2008 ** Command line: rw root=/dev/disk/by-label/root console=ttyS0,115200 ** Tainted: P (129) ** Kernel log: doldacond[4805]: segfault at 12615e0 rip 417790 rsp 7fff6c9733b0 error 6 nfs4_cb: server 192.168.2.253 not responding, timed out UDP: bad checksum. From 93.80.151.26:53 to 82.182.133.20:1937 ulen 464 nfs4_cb: server 192.168.2.253 not responding, timed out nfs4_cb: server 192.168.2.253 not responding, timed out Unable to handle kernel NULL pointer dereference at 0018 RIP: [882b8f7e] :sunrpc:rpc_shutdown_client+0xb5/0xd2 PGD 328c8067 PUD 1eb84067 PMD 0 Oops: [1] SMP CPU 1 Modules linked in: tcp_diag inet_diag des_generic cbc blkcipher nfs nfsd lockd nfs_acl exportfs ppdev parport_pc lp parport wlan_scan_ap sit tunnel4 sch_sfq cls_u32 cls_fw sch_htb ipt_REJECT iptable_filter xt_tcpudp ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 ipt_owner xt_DSCP xt_dscp xt_MARK iptable_mangle ip_tables x_tables xfs reiserfs nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack ipv6 rpcsec_gss_krb5 auth_rpcgss sunrpc loop snd_hda_intel psmouse ath_rate_sample pcspkr ath_pci wlan ath_hal(P) snd_pcm snd_timer snd soundcore serio_raw k8temp snd_page_alloc i2c_nforce2 i2c_core pl2303 usblp usbserial evdev ext3 jbd mbcache dm_mirror dm_snapshot dm_mod generic sd_mod amd74xx sata_nv ide_core r8169 forcedeth firewire_ohci firewire_core crc_itu_t sata_sil ata_generic ohci_hcd libata scsi_mod ehci_hcd Pid: 16606, comm: nfs4_cb_probe Tainted: P2.6.24-1-amd64 #1 RIP: 0010:[882b8f7e] [882b8f7e]
