Bug#931930: firmware-misc-nonfree: Please, include i915/icl_dmc_ver1_07.bin
On Wed, 19 Feb 2020 17:02:13 +0100 Romain Perier wrote: > On Fri, Jan 31, 2020 at 06:10:01PM -0800, Todd Troxell wrote: > > Is there a reason why it's not included? I can make a patch and try it... > > Hi, > > icl_dmc_ver1_07.bin and bxt_huc_ver01_8_2893.bin seems to be included already, > see https://salsa.debian.org/kernel-team/firmware-nonfree/blob/master/debian/config/misc-nonfree/defines > > At least in 20190717-1. > > Messages about "W: Possible missing firmware for module " is > thrown by the hook functions of initramfs-tools, when a kmod requires > firmware images not found on your systemd in /lib/firmware. Are you sure > that your firmware packages are up-to-date ? Hello, I have installed 20190717-2 and they are still missing https://packages.debian.org/bullseye/all/firmware-misc-nonfree/filelist Moreover tgl_dmc_ver2_04.bin isn't in that list but it has been in the linux-firmware repo since tag 20190923 Regards, Sergio
Bug#949178: linux-image-5.4.0-2-amd64: system freeze with i915 with error: 0000:00:02.0: Resetting rcs0 for hang on rcs0
I am seeing very similar problems to this since switching from Buster to Bullseye a couple of weeks ago. I similarly suspected the change in Kernel to be the culprit as whilst using Buster I had no issues. Is there some relatively simple way to test the 5.5 Kernel or any idea when it might be available for Bullseye?
Bug#949178: linux-image-5.4.0-2-amd64: system freeze with i915 with error: 0000:00:02.0: Resetting rcs0 for hang on rcs0
I am seeing very similar problems to this since switching from Buster to Bullseye a couple of weeks ago. I similarly suspected the change in Kernel to be the culprit as whilst using Buster I had no issues. Is there some relatively simple way to test the 5.5 Kernel or any idea when it might be available for Bullseye?
Bug#942563: Any progress on getting a fix for this?
This is a record of all the restarts for the last ~24 hours: Feb 23 08:24:49 debiant kernel: [260162.902256] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 10:00:37 debiant kernel: [265911.64] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 11:52:27 debiant kernel: [272621.545283] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 17:20:56 debiant kernel: [292329.572778] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 18:21:08 debiant kernel: [295942.240028] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 19:02:22 debiant kernel: [298416.101106] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 19:23:29 debiant kernel: [299682.797195] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 19:30:00 debiant kernel: [300074.260841] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 23 19:40:08 debiant kernel: [300681.853074] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 24 06:16:21 debiant kernel: [301294.103572] Restarting tasks ... done. Feb 24 07:57:08 debiant kernel: [307340.793350] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 24 08:12:55 debiant kernel: [308288.569309] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 24 08:15:08 debiant kernel: [308421.082506] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Feb 24 08:22:09 debiant kernel: [308842.138632] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. I believe this is also the cause of constant crashes in the inetd service running on this machine.
Bug#947356: missing firmware rtl8125a-3.fw
On Tue, 14 Jan 2020 20:07:18 +0100 didier wrote: > Same problem here > > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for > module r8169 > > firmware-realtek 20190717-2 > > kernel ; 5.4.0-2-amd64 #1 SMP Debian 5.4.8-1 (2020-01-05) x86_64 > > > > Same here Processing triggers for libvlc-bin:amd64 (1:3.0.8-dmo14) ... Processing triggers for initramfs-tools (0.136) ... update-initramfs: Generating /boot/initrd.img-5.4.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 root@canne:~# ^C root@canne:~# uname -a Linux canne 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux root@canne:~# -- m.vr.gr. Luc Castermans mailto:luc.casterm...@gmail.com
Bug#867067: create directory for nfsdcltrack
Control: found -1 1.3.4-2.5 Control: severity -1 grave Hi all, this bug causes kernel panics at least on i386 and x86-64 running nfsv4 servers so set severity to grave. * Hieu Luu [2017-09-26 21:24 +0700]: > Hello Stephen, > > I was able to resolve this by following these steps (after doing strace > nfsdcltrack init to find out why it returned -13) **[1]** > > 1. `# mkdir /var/lib/nfs/nfsdcltrack` > 2. `# nfsdcltrack init` > 3. check if file `/var/lib/nfs/nfsdcltrack/main.sqlite` is present > 4. check with `sqlite /var/lib/nfs/nfsdcltrack/main.sqlite` > * querying `.tables` gives `clients` and `parameters` > * querying `.schema clients` gives `CREATE TABLE clients (id BLOB PRIMARY > KEY, time INTEGER, has_session INTEGER);` > * querying `.schema parameters` gives `CREATE TABLE parameters (key TEXT > PRIMARY KEY, value TEXT);` > 5. `# systemctl restart nfs-server` I can confirm that the above workaround doesn't cause kernel panics anymore. Thanks Elimar -- We all know Linux is great... it does infinite loops in 5 seconds. -Linus Torvalds
Processed: Re: create directory for nfsdcltrack
Processing control commands: > found -1 1.3.4-2.5 Bug #867067 [nfs-kernel-server] nfs-kernel-server: nfsdcltrack fails to init database There is no source info for the package 'nfs-kernel-server' at version '1.3.4-2.5' with architecture '' Unable to make a source version for version '1.3.4-2.5' Marked as found in versions 1.3.4-2.5. > severity -1 grave Bug #867067 [nfs-kernel-server] nfs-kernel-server: nfsdcltrack fails to init database Severity set to 'grave' from 'important' -- 867067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952446: nfs-utils: Please update to latest nfs-utils
Source: nfs-utils Version: 1.3.4-2.5+b1 Severity: wishlist Dear maintainers, meanwhile version 2-4-3 is available at http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=tags Sigh -- Elimar
Processed: Re: Bug#867067: create directory for nfsdcltrack
Processing control commands: > severity -1 important Bug #867067 [nfs-kernel-server] nfs-kernel-server: nfsdcltrack fails to init database Severity set to 'important' from 'grave' -- 867067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867067: create directory for nfsdcltrack
Control: severity -1 important On Mon, 2020-02-24 at 16:01 +0100, Elimar Riesebieter wrote: > Control: found -1 1.3.4-2.5 > Control: severity -1 grave > > Hi all, > > this bug causes kernel panics at least on i386 and x86-64 running > nfsv4 servers so set severity to grave. [...] This bug is assigned to nfs-kernel-server, which only contains the programs used to *configure* the NFS server in the kernel. The kernel crash needs to be assigned to the kernel, i.e. src:linux. You should open a separate bug for that, using "reportbug kernel". Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false. signature.asc Description: This is a digitally signed message part
Bug#952452: initramfs-tools: prefers serial console over framebuffer console
Package: initramfs-tools Version: 0.136 Severity: minor Dear kernel team, I'm using Debian on an arm64 chromebook, and not setting "console=tty1" in the kernel command line results in a number of weird behaviours related to the initramfs. During an ordinary boot, plymouth doesn't show the futureprototype boot splash. Instead, it shows the init log; but pressing ESC does switch to plymouth (but with what I'm assuming is the text theme instead). If I use "break" (even "break=init") in the kernel command line, I don't see an initramfs shell prompt and the keyboard does nothing. If plymouth is installed, I see the "Spawning shell within the initramfs" message but rest is the same (plymouth quits in it's panic hook). When I'm trying to boot from an encrypted root (different installation), I don't see the "Please unlock disk" cryptsetup prompt and can't type a passphrase; unless plymouth is installed. I'm able to boot the encrypted system as a QEMU virtual machine and I get similar behaviour there, no messages or prompts are printed to the graphical console and instead all go to the serial console. However having plymouth doesn't make the cryptsetup prompt ask in the graphical console in the virtual machine. All these are fixed by simply adding "console=tty1" to the command line, is that something a user is supposed to do manually (e.g. GRUB configs)? Should the initramfs (or maybe the kernel itself) be detecting when graphics are working and automatically switch outputs/prompts to that? I want to work on this, what would be the best way to proceed? -- Might be relevant: -- /proc/consoles: ttyS2-W- (EC p a)4:66 tty0 -WU (E p )4:7 -- Some dmesg lines that might be useful: [0.00] Booting Linux on physical CPU 0x00 [0x410fd034] [0.00] Linux version 5.4.0-4-arm64 (...) [0.00] Machine model: Google Kevin [0.001029] Console: colour dummy device 80x25 [0.001038] printk: console [tty0] enabled [0.044788] Serial: AMBA PL011 UART driver [1.853700] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [1.855861] ff1a.serial: ttyS2 at MMIO 0xff1a (irq = 39, base_baud = 150) is a 16550A [1.856046] printk: console [ttyS2] enabled [1.857318] Serial: AMBA driver [1.857898] msm_serial: driver initialized [2.103745] ttyS2 - failed to request DMA [2.159994] Run /init as init process [2.785121] rockchip-drm display-subsystem: bound ff8f.vop (ops rockchip_drm_fini [rockchipdrm]) [2.787381] rockchip-drm display-subsystem: bound ff90.vop (ops rockchip_drm_fini [rockchipdrm]) [2.794270] rockchip-drm display-subsystem: bound ff97.edp (ops rockchip_drm_fini [rockchipdrm]) [2.794439] rockchip-drm display-subsystem: bound fec0.dp (ops rockchip_drm_fini [rockchipdrm]) [2.794446] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [2.794449] [drm] No driver support for vblank timestamp query. [2.824898] cdn-dp fec0.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn [3.076232] Console: switching to colour frame buffer device 300x100 [3.132091] rockchip-drm display-subsystem: fb0: rockchipdrmfb frame buffer device [3.144856] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0 [4.972935] systemd[1]: systemd 244.3-1 running in system mode. (...) -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 12M Jan 19 11:20 /boot/initrd.img-5.4.0-2-arm64 -rw-r--r-- 1 root root 16M Feb 8 12:52 /boot/initrd.img-5.4.0-3-arm64 -rw-r--r-- 1 root root 16M Feb 19 14:25 /boot/initrd.img-5.4.0-4-arm64 -- /proc/cmdline cros_secure kern_guid=7849fbba-1fb3-4f0b-9989-952567ef5a3c root=PARTUUID=3518689e-a82c-4448-9ec2-c79b13f88d8e rootwait quiet splash -- resume RESUME=UUID=490bfb86-ee41-4944-8bcf-4f4b2211026d -- /proc/filesystems ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by vhost_net 32768 0 vhost 49152 1 vhost_net tap32768 1 vhost_net uhid 24576 1 algif_hash 20480 1 algif_skcipher 16384 1 af_alg 28672 6 algif_hash,algif_skcipher rfcomm 81920 16 fuse 139264 5 xt_CHECKSUM16384 1 xt_MASQUERADE 20480 3 xt_conntrack 16384 1 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 20480 6 nft_compat 20480 13 nft_counter16384 30 nft_chain_nat 16384 8 nf_nat 45056 2 nft_chain_nat,xt_MASQUERADE nf_conntrack 159744 3 xt_conntrack,nf_nat,xt_MASQUERADE nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack libcrc32c 16384 2 nf_conntrack,nf_nat nf_tables 151552 102 nft_compat
Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc
Hi, i purged linux 5.4.19-1 and installed from scratch: <<<- ● apt install linux-image-5.4.0-4-amd64-unsigned linux-headers-5.4.0-4-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-headers-5.4.0-4-common (5.4.19-1) linux-kbuild-5.4 (5.4.19-1) Suggested packages: linux-doc-5.4 (5.4.19-1) debian-kernel-handbook (1.0.19) The following NEW packages will be installed: linux-headers-5.4.0-4-amd64 (5.4.19-1) linux-headers-5.4.0-4-common (5.4.19-1) linux-image-5.4.0-4-amd64-unsigned (5.4.19-1) linux-kbuild-5.4 (5.4.19-1) 0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/57.4 MB of archives. After this operation, 333 MB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package linux-headers-5.4.0-4-common. (Reading database ... 267753 files and directories currently installed.) Preparing to unpack .../linux-headers-5.4.0-4-common_5.4.19-1_all.deb ... Unpacking linux-headers-5.4.0-4-common (5.4.19-1) ... Selecting previously unselected package linux-kbuild-5.4. Preparing to unpack .../linux-kbuild-5.4_5.4.19-1_amd64.deb ... Unpacking linux-kbuild-5.4 (5.4.19-1) ... Selecting previously unselected package linux-headers-5.4.0-4-amd64. Preparing to unpack .../linux-headers-5.4.0-4-amd64_5.4.19-1_amd64.deb ... Unpacking linux-headers-5.4.0-4-amd64 (5.4.19-1) ... Selecting previously unselected package linux-image-5.4.0-4-amd64-unsigned. Preparing to unpack .../linux-image-5.4.0-4-amd64-unsigned_5.4.19-1_amd64.deb ... Unpacking linux-image-5.4.0-4-amd64-unsigned (5.4.19-1) ... Setting up linux-headers-5.4.0-4-common (5.4.19-1) ... Setting up linux-kbuild-5.4 (5.4.19-1) ... Setting up linux-image-5.4.0-4-amd64-unsigned (5.4.19-1) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-4-amd64/modules.builtin.bin' depmod: ERRO
Bid Writing Workshops
NFP WORKSHOPS 18 Blake Street, York YO1 8QG Bid Writing Workshops for Charities, Schools and Public Sector Organisations. UNSUBSCRIBES To unsubscribe please reply back replacing the subject line with debian-kernel@lists.debian.org Unsubscribes will take effect within seven days. QUESTIONS To ask a question please reply back replacing the subject line with question You will usually receive a response within 24 hours. Due to our training and travel commitments we are unable to accept questions by phone. BOOKING DETAILS You can book any workshop online and pay using a debit card, credit card or paypal. Just google nfp workshops to go to our website. BID WRITING: THE BASICS Start 09.00 Finish 11.30 Cost £95 Do you know the most common reasons for rejection? Are you gathering the right evidence? Are you making the right arguments? Are you using the right terminology? Are your numbers right? Are you learning from rejections? Are you assembling the right documents? Do you know how to create a clear and concise standard funding bid? Are you communicating with people or just excluding them? Do you know your own organisation well enough? Are you thinking through your projects carefully enough? Do you know enough about your competitors? Are you answering the questions funders will ask themselves about your application? Are you submitting applications correctly? BID WRITING: ADVANCED Start 12.00 Finish 14.30 Cost £95 Are you applying to the right trusts? Are you applying to enough trusts? Are you asking for the right amount of money? Are you applying in the right ways? Are your projects the most fundable projects? Are you carrying out trust fundraising in a professional way? Are you delegating enough work? Are you highly productive or just very busy? Are you looking for trusts in all the right places? How do you compare with your competitors for funding? Is the rest of your fundraising hampering your bids to trusts? Do you understand what trusts are ideally looking for? ATTENDEES Staff members, volunteers, trustees or board members of charities, schools or public sector organisations who intend to submit grant funding applications to charitable grant making trusts and foundations. People who provide advice to these organisations are also welcome. LOCATIONS, DATES & VENUES LONDON 23 Mar 2020 - 27 Apr 2020 - 08 Jun 2020 - 15 Jun 2020 200A Pentonville Road, Kings Cross, London N1 9JP SOUTHAMPTON 17 Mar 2020 - 09 Jun 2020 Jurys Inn, Charlotte Place, Southampton SO14 0TB BRISTOL 18 Mar 2020 - 10 Jun 2020 The Waterfront Meeting Rooms, Welsh Back, Bristol BS1 4SB EDINBURGH 19 Mar 2020 - 11 Jun 2020 Courtyard, 1-3 Baxter's Place, Edinburgh EH1 3AF NEWCASTLE 20 Mar 2020 - 12 Jun 2020 Jurys Inn, Scotswood Road, Newcastle upon Tyne NE1 4AD NOTTINGHAM 24 Mar 2020 - 16 Jun 2020 Jurys Inn, Station Street, Nottingham NG2 3BJ BIRMINGHAM 25 Mar 2020 - 17 Jun 2020 Jurys Inn, 245 Broad Street, Birmingham B1 2HQ MANCHESTER 26 Mar 2020 - 18 Jun 2020 Jurys Inn, 56 Great Bridgewater Street, Manchester M1 5LE LEEDS 27 Mar 2020 - 19 Jun 2020 Jurys Inn, Brewery Wharf, Brewery Place, Leeds LS10 1NE
