Bug#1014793: linux-image-5.10.0-16-amd64: Kernel crashes while serving NFS

Den 2022-07-15 kl. 21:58, skrev Salvatore Bonaccorso: I would be interested to either pinpoint the regressing commit upstream beween 5.10.120 and 5.10.127 or conversely the fixing commit beween 5.10.127 upstream and 5.10.130 where you are not able anymore to reproduce the error. What I can say, I

Bug#1014793: linux-image-5.10.0-16-amd64: Kernel crashes while serving NFS

Sorry for the late reply. Den 2022-07-13 kl. 12:07, skrev Salvatore Bonaccorso: Control: tags -1 + moreinfo Hello Arne, ... As you seem to reliably reproduce the issue, do you have the possiblity (on the nonproduction instance) to try to bisect down the problem? Additionally to the bisect

Bug#1014793: linux-image-5.10.0-16-amd64: Kernel crashes while serving NFS

Package: src:linux Version: 5.10.127-1 Severity: normal Dear Maintainer, The new kernel in Debian 11.4 seems unstable and crashes when serving NFS. On two different computers, these lockups happens within minutes, typically when a client runs firefox on an NFS-mounted home directory. Typica

Bug#897917: Stretch kernel 4.9.88-1 breaks startup of RPC, KDC services

I have also seen this on a couple of SSD-only systems. I think the problem is that the random number generator takes about two minutes to initialize, long enough for systemd to give up on these processes. Unbound is similar, but there unit file keeps trying until the random numbers are available.

Bug#886768: Acknowledgement (linux-headers-3.16.0-5-amd64: inode_change_ok() missing, breaks openafs module build)

Newer OpenAFS versions replace code = inode_change_ok(inode, &newattrs); by code = setattr_prepare(file_dentry(afile->filp), &newattrs); The file_dentry() helper is not present in linux-headers-3.16.0-5 either, but code = setattr_prepare(afile->filp->f_path.dentry, &newattrs); at least seems

Bug#753732: NFS sec=krb5 does not work with cross-realm

the content of /etc/idmapd.conf. There are several options for translating principals, and if user names are the same in both realms a simple line like Local-Realms: DAPADAM.NL, UMRK.NL might do it. Arne Nordmark -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org wit

Re: Bogus(?) /dev/sda appearing with linux-image-3.2.0-4-amd64 3.2.65-1

Den 2015-01-11 18:18, Arne Nordmark skrev: > With the latest Wheezy kernel I am seeing a new device /dev/sda that has > not been seen in previous kernels. The claim of the device being new was not correct. I though I had online logs going back before the latest reboot. Checking offline

Bogus(?) /dev/sda appearing with linux-image-3.2.0-4-amd64 3.2.65-1

Should it be reported as a bug? Arne Nordmark -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b2b056.1010...@mech.kth.se

Bug#661581: Fails to resume from suspend on ASUS P67-M mainboard

2012-03-01 16:31, Jonathan Nieder skrev: tags 661581 = upstream forwarded 661581 http://thread.gmane.org/gmane.linux.kernel/1240187/focus=52118 quit Arne Nordmark wrote: Some newer ASUS mainboards fails to resume from suspend on Linux. Instead the computer immediately restarts a few times

Bug#661581: Fails to resume from suspend on ASUS P67-M mainboard

2012-03-01 16:31, Jonathan Nieder skrev: tags 661581 = upstream forwarded 661581 http://thread.gmane.org/gmane.linux.kernel/1240187/focus=52118 quit Arne Nordmark wrote: Some newer ASUS mainboards fails to resume from suspend on Linux. Instead the computer immediately restarts a few times

Bug#661581: linux-image-3.2.0-0.bpo.1-amd64: Fails to resume from suspend on ASUS P67-M mainboard

Package: linux-2.6 Version: 3.2.4-1~bpo60+1 Severity: normal Tags: patch Some newer ASUS mainboards fails to resume from suspend on Linux. Instead the computer immediately restarts a few times, and then does a full boot. This has been traced to an ACPI problem, and a symtom is the kernel message

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

Ben Hutchings wrote: On Fri, 2010-06-18 at 16:40 +0200, Arne Nordmark wrote: My problem seems related to those in Ubuntu report #55 <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/55>. If I unload the 3c59x module, I can no longer reproduce this problem, and wireless is

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

My problem seems related to those in Ubuntu report #55 . If I unload the 3c59x module, I can no longer reproduce this problem, and wireless is stable. With the 3c59x module loaded, b43 wireless is essentially unusable, since the m

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

644991] [] ? kthread+0x0/0x66 May 8 09:35:48 dhcp190 kernel: [ 1830.645012] [] ? kernel_thread_helper+0x7/0x10 Arne Nordmark -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive:

Sarge 2.6.8 kernel suitable for NFS?

From the discussion regarding whether to stick with 2.6.8 in sarge , one gets the impression that there are NFS problems in the sarge 2.6.8 kernel. Are these severe enough to not recommend this kernel for NFS server and/or client use

Bug#276134: kernel-source-2.6.8: Minolta DIMAGE cameras stopped working with usb-st orage in 2.6.8

Horms wrote: > Thanks, > > that looks good to me. I will put the patch into SVN and it should > appear in the next release. Just to clarify: I did try the patch and it solved my problem. Many thanks, Arne -- Arne Nordmark Tel: +46 8 - 790 71 92 KTH/Mekanik

Bug#276134: kernel-source-2.6.8: Minolta DIMAGE cameras stopped working with usb-st orage in 2.6.8

Package: kernel-source-2.6.8 Version: 2.6.8-7 Severity: normal A change form 2.6.7 to 2.6.8 in the error return handling of usb_stor_Bulk_max_lun() in usb-storage/transport.c exposed a problem with Minolta DIMAGE cameras, causing probing to fail, and thus these cameras cannot be used with 2.6.8. Th