Bug#994242: linux-image-5.10.0-8-amd64: On a DELL Optiplex 5090 the screen goes black on boot

Package: src:linux Version: 5.10.46-4 Severity: important Dear Maintainer, * What led up to the situation? Installed Debian Bullseye on a new DELL Optiplex 5090 PC * What was the outcome of this action? After the initial boot messages the screen goes blank. * What outcome did you exp

Bug#915008: I've seen a similar problem and managed to work around it.

NAL_DRAM Jul 29 12:13:10 oceanic kernel: [ 16.275045] iwlwifi :00:14.3: FW already configured (0) - re-configuring It is possible that this problem was caused by the laptop battery running completely flat, and the Linux driver or firmware missing some initialisation step. -- *John HUG

Bug#886746: Bug is fixed in vanilla kernel 4.9.77

This bug appears to have been fixed somewhere between 4.9.65 and 4.9.77 -- John Hughes, CalvaEDI S.A.S. -- An Esker Company +33 1 4313 3131

Bug#886746: Bug exists in vanilla kernel 4.9.65

I've compiled a vanilla kernel 4.9.65 (from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git) and the bug is present.  Vanilla kernel 4.9.30 works. I'll roll up my sleeves and start bisecting. -- John Hughes, CalvaEDI S.A.S. -- An Esker Company +33 1 4313 3131

Bug#886746: Bug also present in linux-image-4.9.0-4-amd64 4.9.65-3+deb9u1

Versionn linux-image-4.9.0-3-amd64 seems Ok. -- John Hughes, CalvaEDI S.A.S. -- An Esker Company +33 1 4313 3131

Bug#886746: linux-image-4.9.0-5-amd64: screen connected via displayport hub flashes black

Package: src:linux Version: 4.9.65-3+deb9u2 Severity: normal Dear Maintainer, * What led up to the situation? Installed linux-image-4.9.0-5-amd64 version 4.9.65-3+deb9u2 * What exactly did you do (or not do) that was effective (or ineffective)? Open a gnome-terminal window, wait a w

Bug#772848: This is also 818502

Václav Ovsík, being much smarter than me, has tracked this bug down and found a patch that fixes it. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502 -- John Hughes, CalvaEDI S.A.S. -- An Esker Company +33 1 4313 3131

Bug#772848: ext3 fs gets ext4_mb_release_inode_pa error, remounted read-only

Here's what the fsck looked like. No serious damage. root@olympic:~# fsck -y /dev/olympic/olympic-imap fsck from util-linux 2.20.1 e2fsck 1.42.5 (29-Jul-2012) olympic-imap: recovering journal olympic-imap contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and size

Bug#772848: ext3 fs gets ext4_mb_release_inode_pa error, remounted read-only)

It turns out that this is not the first time I've seen this bug, it happened on another VM (on another physical machine). The storage stack is similar: On the host (3.16-0.bpo.2-amd64): mdadm raid (2 SATA disks) LVM On the guest (3.16-0.bpo.2-amd64) LVM2, ext3 filesystem. Dec 10 22:33:24 cedri

Bug#772848: ext3 fs gets ext4_mb_release_inode_pa error, remounted read-only)

Looks superficaly like: http://thread.gmane.org/gmane.comp.file-systems.ext4/43443/focus=43448 -- 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/5489d609.3000...@calv

Bug#772848: linux-image-3.16-0.bpo.2-amd64: ext3 fs gets ext4_mb_release_inode_pa error, remounted read-only

Package: src:linux Version: 3.16.3-2~bpo70+1 Severity: normal Dear Maintainer, I'm running cyrus imapd on a KVM hosted virtual machine with kernel 3.16-0.bpo.2-amd64 Twice (so far) I've seen the error: [957229.875900] EXT4-fs (dm-4): pa 88001f7ff980: logic 0, phys. 9176576, le$ [957229.8786

Bug#762939: nfs-common: /etc/init.d/nfs-common starts #!/bin/bash

Package: nfs-common Version: 1:1.2.8-9 Severity: wishlist Dear Maintainer, /etc/init.d/nfs-common starts #!/bin/bash, but doesn't seem to contain any bashisms. It'd be nice to use /bin/sh. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111

Bug#740933: This is what lspci (eventualy) shows on 3.13

Just before the system goes into cpu-bound loops: root@russia:~# lspci -vvv -s :01:00.1 ... long delay... 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) Subsystem: Sony Corporation Device 905a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGA

Bug#740933: Bug exists in 3.12, not in 3.11

I've tried 3.12.8-1 and 3.11.10-1 (the kernels I just happened to have lying around). Same behaviour in 3.12 3.11 seems to work ok. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https:/

Bug#740933: linux-image-3.13-1-amd64: sony vaio z1 lspci hangs reading /sys/bus/pci/devices/0000:01:00.1/config

Package: src:linux Version: 3.13.5-1 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded from 3.2.0-4-amd64 to 3.13-1-amd64 * What exactly did you do (or not do) that was effective (or ineffective)? tried to see my pci devices with a lspci * What was the

Bug#731884: Problem is order of partitions seen by mdadm

When the system works it builds the devices from sda and sdb. When it fails its because it tries to build a container from sda3 and sdb. To mdadm sda3 looks like it is part of an imsm container, but it's not. It isn't even a partition! sda and sdb contain a imsm raid0 device that is partiti

Bug#731884: Problem is in detection of partition table after mdadm volume created

What seems to be happening: In the cases where the system boots correctly the mdadm volume is created then a partition table is found. In the cases where the system fails to boot the mdadm volume is created then the kernel says "md126: unknown partition table". Running the kernel without th

Bug#731884: initramfs-tools: randomly /dev/disk/by-uuid doesn't exits, making boot from crypt partition fail

Package: initramfs-tools Version: 0.115 Severity: normal Dear Maintainer, * What led up to the situation? Upgraded * What exactly did you do (or not do) that was effective (or ineffective)? Rebooted * What was the outcome of this action? Fell into busybox shell because couldn

Bug#729567: Debian bug #726676: linux-image-3.10-3-amd64: TCP packet loss when using proxy ARP IP addresses

On 11/24/2013 01:52 AM, Ben Hutchings wrote: On Sat, 2013-11-23 at 16:29 -0800, Andris Kalnozols wrote: Package: src:linux Version: 3.10.11-1 Please close bug report #726676 as the observed problem had nothing to do with proxy-arp. The correct diagnosis was provided by John Hughes who filed

Bug#726676: Debian bug #726676: linux-image-3.10-3-amd64: TCP packet loss when using proxy ARP IP addresses

off make your system work better? -- John Hughes, Atlantic Technologies. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5285f483.4010...@atlantech.com

Bug#729567: When a large TCP segment (created by generic-receive-offload) is split up who is supposed to create the checksums?

So this is what I think is happening. My router machine, running 3.10, has generic-receive-offload set on its LAN port. It happily sticks together five 1354 byte segments to make one nice tasty 6670 byte segment. Which then gets routed to a tun device, going to OpenVPN, so the fat 6670 byt

Bug#729567: Acknowledgement (linux-image-3.10-0.bpo.3-amd64: Forwarding TCP from one LAN to another via an OpenVPN tunnel is extremely slow)

Looking at the traces in more detail "-vv" I see on the receiving system: 11:59:23.025658 IP (tos 0x8, ttl 62, id 42831, offset 0, flags [DF], proto TCP (6), length 1406) caronia.CalvaEDI.COM.33232 > olympic.calvaedi.com.ssh: Flags [.], cksum 0x1003 (incorrect -> 0xb1b9), seq 3073:4427

Bug#726676: Maybe this has some connection to bug 729567

But my problem seems to have nothing to do with ARP. Do my traces look like yours? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5284c379.2040...@atlantech.com

Bug#702108: Info received (Bug#702108: Acknowledgement (linux-image-3.8-trunk-amd64: sd/mmc card reader doesn't work on Sony VAIO Z (2011)))

Seems like we need Device Drivers ---> Multifunction device drivers ---> Support for Realtek PCI-E card reader and then ... MMC/SD/SDIO card support ---> Realtek PCI-E SD/MMC Card Interface Driver and ... --- Sony MemoryStick card support (EXPERIMENTAL) Realtek PCI-E Memstick Ca

Bug#702108: Acknowledgement (linux-image-3.8-trunk-amd64: sd/mmc card reader doesn't work on Sony VAIO Z (2011))

Problem appears to be that in the 3.7 config we have CONFIG_RTS_PSTOR=m # CONFIG_RTS_PSTOR_DEBUG is not set But the 3.8 doesn't. **Greg KH says (http://lkml.indiana.edu/hypermail/linux/kernel/1212.1/01422.html ) We also removed some older drivers (telephony and rts_pstor), Nice

Bug#702108: linux-image-3.8-trunk-amd64: sd/mmc card reader doesn't work on Sony VAIO Z (2011)

Package: src:linux Version: 3.8-1~experimental.1 Severity: normal Dear Maintainer, * What led up to the situation? Wanted to read a sd card * What exactly did you do (or not do) that was effective (or ineffective)? Stuck the card in the reader * What was the outcome of this acti

Bug#608133: nouveau: severe display corruption on NV4E on machines with > 2G RAM

On 01/01/13 01:15, Jonathan Nieder wrote: Hi John, Salah Coronya wrote: As of kernel 3.7, [...] all the errors related to ths bug are gone for me - no distortion, no crashes, and no CACHE_ERROR, even after switching VT and running accelerated programs for over a week. Can you confirm? A 3.7.

Bug#606939: [squeeze -> 2.6.36 regression] holes in characters rendered on screen in X

On 15/02/12 20:47, Jonathan Nieder wrote: tags 606939 + moreinfo quit Jonathan Nieder wrote: If you have a chance to try xserver-xorg-video-intel from experimental (and comment out or remove the debugwait snippet in xorg.conf), that would be interesting. Did you get a chance to t

Bug#659647: initramfs-tools/hooks/cryptroot get_lvm_deps can't cope with vg name containing -

Package: initramfs-tools Version: 0.99 Severity: normal Dear Maintainer, * What led up to the situation? I made a volume group called "coal-vg" holding a root volume called root. (i.e. /dev/mapper/root--vg-root) * What was the outcome of this action? update-initramfs gave the error: cr

Bug#606939: [squeeze -> 2.6.36 regression] holes in characters rendered on screen in X

On 09/02/12 22:53, Jonathan Nieder wrote: If I remember correctly, your kernel is 3.3-rc1 plus an unrelated keyboard handling patch. Yes. Am I correct in guessing that the glitches in font rendering didn't happen again? Since installing the debugwait option the problem seems to have gone away

Bug#606939: [squeeze -> 2.6.36 regression] holes in characters rendered on screen in X

On 28/01/12 13:26, Jonathan Nieder wrote: Symptoms are reminiscent of, though Vítor uses a 915GM and you have a 945GM. Also reminiscent of . Does putting Section "Device" Identifier "Intel"

Bug#606939: [squeeze -> 2.6.36 regression] holes in characters rendered on screen in X

On 26/01/12 09:50, John Hughes wrote: On 26/01/12 00:05, Jonathan Nieder wrote: Sorry for the slow reply. Can you reproduce this with a 3.x.y kernel? If so, can you take a screenshot so we can see what the corrupted glyphs look like? Ok, will do this weekend - currently I'm on 3.3-rc some

Bug#606939: [squeeze -> 2.6.36 regression] holes in characters rendered on screen in X

On 26/01/12 00:05, Jonathan Nieder wrote: Hi, John Hughes wrote: Since installing linux-image-2.6.36-trunk-686 in order to "fix" bug 590251 I'm seeing minor "glitches" in font rendering (seen in gnome-terminal and iceweasel). The glitches take the form of holes in r

Bug#615110: tpm_tis prevents suspend working more than once

The included /etc/pm/sleep.d/10tpm_tis "fixes" the problem for me (/usr/local/bin/tpm_startup is the program posted earlier). #!/bin/bash case $1 in hibernate) echo "Hey guy, we are going to suspend to disk!" ;; suspend) echo "Oh, this time we are doing a suspend to

Bug#615110: tpm_tis prevents suspend working more than once

On 20/01/12 08:46, Jonathan Nieder wrote: There have been some tpm fixes upstream recently, so results from testing v3.3-rc1 or later would be interesting. Jonathan Exactly the same results with v3.3-rc1 Linux carbon 3.3.0-rc1+ #4 SMP Sat Jan 21 15:46:40 CET 2012 i686 GNU/Linux (This is stoc

Bug#615110: tpm_tis prevents suspend working more than once

Exactly same behaviour with stock debian 3.2: Linux carbon 3.2.0-1-686-pae #1 SMP Thu Jan 19 10:56:51 UTC 2012 i686 GNU/Linux ii linux-image-3.2.0-1-686-pae 3.2.1-1 Linux 3.2 for modern PCs Will try with 3.3 rc1 later. -- To UNSUBSCRIBE, email to debian-k

Bug#615110: tpm_tis prevents suspend working more than once

On 20/01/12 08:46, Jonathan Nieder wrote: Thanks. Do you know the commit id of this 3.2-rc2+ kernel? It's one I've been working on to fix Sony Vaio keyboard problems. I'll try an "official" kernel today. There have been some tpm fixes upstream recently, so results from testing v3.3-rc1 or lat

Bug#615110: tpm_tis prevents suspend working more than once

On 19/01/12 01:48, Jonathan Nieder wrote: This is probably fixed by stable release 2.6.37.2 which will be included in Debian version 2.6.37-2 in the next day or two. So, was it? ;-) In suspense, Jonathan No. This bug is still present as of 3.2.0 Linux carbon 3.2.0-rc2+ #2 SMP Thu Dec 8 20:2

Bug#648155: Simple fix for bug that doesn't need kernel patch

h for the ticket to expire a new ticket will be obtained (via pam_krb5) by the screen unlock process. Author: John Hughes Signed-off-by: John Hughes Bug-Debian: http://bugs.debian.org/648155 Bug-Ubuntu: https://launchpad.net/bugs/648155 --- nfs-utils-1.2.5.orig/utils/gssd/gssd_proc.c ++

Bug#648155: Patch to make nfs4 return EKEYEXPIRED to user code

This patch (for 3.1-rc10, probably works for all versions that have this problem) makes nfs4 return the EKEYEXPIRED to user level, which works well with nfs4 mounted home directories on user systems. The normal case will be that the workstation screen will be locked when the ticket expires, th

Bug#648191: linux-image-2.6.32-5-686: latest squeeze kernel doesn't boot on Dell Optiplex GX270 if hyperthreading enabled

On 14/11/11 06:58, Ben Hutchings wrote: Could you test an intermediate version, say, 2.6.32-34squeeze1? Earlier versions are available at . I'm really sorry but I am unable to reproduce this bug. I tried 2.6.32-34squeeze1, it w

Bug#648191: Log of failed boot with hyperthreading enabled

Here's what happens with hyperthreading enabled. After the "bio: create slab at 0" message the system reboots. =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2011.11.10 04:45:51 =~=~=~=~=~=~=~=~=~=~=~= [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.

Bug#648155: Stupid workaround

One stupid workaround I've found is to use krenew. Since I'm logging in using gdm3 I just set my .xsession to something like: /usr/bin/krenew /usr/bin/gnome-session This is not a real solution as it only deals with gdm logins and it won't work when suspend is fixed. -- To UNSUBSCRIBE

Bug#648155: Acknowledgement (nfs-common: nfs mount hangs when kerberos ticket expires. Squeeze used to renew.)

This seems to be Ubuntu bug https://bugs.launchpad.net/ubuntu/+bug/794112 There it is suggested that updating nfs-utils could fix the problem. I don't see how, and anyway, is there a more recent version than what's in sid? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org

Bug#648191: linux-image-2.6.32-5-686: latest squeeze kernel doesn't boot on Dell Optiplex GX270 if hyperthreading enabled

Package: linux-2.6 Version: 2.6.32-38 Severity: normal Previous versions of this package, for example 2.6.32-31, had no problem booting on this hardware. Version 2.6.32-38 spontaneously reboots during the boot process unless hyperthreading is disabled. (Says something about activating 2nd CPU.

Bug#648155: linux-image-3.xx nfs4 mount hangs when kerberos ticket expires. Squeeze used give EPERM

This is a kernel bug not a nfs-common bug. Using the squeeze kernel (2.6.32-5) in place of the current unstable kernel what happens is that attempts to access the nfs4 mounted system get an EPERM instead of hanging and no horrid messages are written to the log. -- To UNSUBSCRIBE, email to

Bug#648155: nfs-common: nfs mount hangs when kerberos ticket expires. Squeeze used to renew.

Package: nfs-common Version: 1:1.2.5-2 Severity: normal Dear Maintainer, We use krb5 nfs4 for mounting our home directories. On squeeze this worked well. On a sid/wheezy system the nfs4 mount hangs when the kerberos ticket expires (but is still renewable). In the syslog on the client we see:

Bug#515754: Old client works with new or old server. New client only works with new server.

On 11/08/2011 10:02 PM, Bastian Blank wrote: On Tue, Nov 08, 2011 at 04:06:07PM +0100, John Hughes wrote: root@olympic:~# exportfs /srv/nfs4 gss/krb5 /srv/nfs4/home gss/krb5 /srv/nfs4/local gss/krb5 Please re-read the exports man-page. You want to use sec=. Not

Bug#515754: Info received (This is a duplicate of #622146)

Ok, I confirm that this is a dup of 622146 and that the "fix" there (install nfs-kernel-server 1:1.2.2-4squeeze1 on the server) works for me. I guess you're out of luck if you have a non-Debian server. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsu

Bug#515754: This is a duplicate of #622146

Which was "closed" by fixing nfs-utils and krb5 in squeeze. Hum. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb94a80.3090...@calva.com

Bug#515754: Old client works with new or old server. New client only works with new server.

I've build a nfs server using unstable: root@coptic:~# uname -a Linux coptic 3.0.0-2-686-pae #1 SMP Wed Nov 2 05:29:50 UTC 2011 i686 GNU/Linux root@coptic:~# dpkg -l nfs-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

Bug#515754: Info received (Bug#515754: Info received (Bug#515754: Info received (Debian bug #515754)))

On 04/11/11 11:58, John Hughes wrote: default_tkt_enctypes = des-cbc-md5 des-cbc-md4 des-cbc-crc to krb5.conf on the nfs4 server as well as the client, but that does nothing for me either. Well, it does something - it breaks kadmin. :-(

Bug#515754: Info received (Bug#515754: Info received (Bug#515754: Info received (Debian bug #515754)))

Hoho - is it possible that this is Redhat bug 652273? https://bugzilla.redhat.com/show_bug.cgi?id=652273 They suggest: Adding "default_tkt_enctypes = des-cbc-md5 des-cbc-md4 des-cbc-crc" to [libdefaults] section of krb5.conf allows the mount to succeed but that does nothing for me, may

Bug#515754: Info received (Bug#515754: Info received (Debian bug #515754))

The bug seems to be in rpc.gssd. If I run the rpc.gssd from 1:1.2.2-4 and try a mount I get: beginning poll handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt15) handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 ' handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt15) proces

Bug#515754: Info received (Debian bug #515754)

Although 1:1.2.2-4 allows me to mount my filesystems it has the disadvantage of tickling the bug reported as Ubuntu bug 794112 - https://bugs.launchpad.net/ubuntu/+bug/794112 Nov 4 09:16:08 cretic kernel: [86004.048735] Error: state manager encountered RPCSEC_GSS session expired against NFSv4

Bug#515754: Debian bug #515754

I'm seeing this bug with nfs-common 1:1.2.5-2 on sid. Downgrading to 1:1.2.2-4 from squeeze works. (with allow_weak_crypto). Anyone have a clue about what I should try to debug? (nfs and krb5 servers are squeeze). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a su

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 28/09/11 11:09, John Hughes wrote: I think you're right about the problems now being userspace. I feel that the "hang after thaw" problems I'm seeing are caused by krb5 - it seems to like to get itself into a situation where it has no krb5 ticket so it can't

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 27/09/11 20:27, Jeff Layton wrote: On Mon, 26 Sep 2011 14:31:32 -0400 Jeff Layton wrote: Not sure what happened here. Looks like the "freeze phase" of the suspend worked. My inclination is to think that this is not due to my patch. What might be helpful is to try suspending without NF

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 23/09/11 17:09, Jeff Layton wrote: I went ahead and attached the latest one to the RHBZ above. If you can grab it from there and test it, that would be great. Ok, I'm now testing the current patch on my Dell GX270 (Pentium-4, ugh) system. Things are not working too well. Sometimes th

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 23/09/11 17:09, Jeff Layton wrote: I went ahead and attached the latest one to the RHBZ above. If you can grab it from there and test it, that would be great. Ok, I'll try that Monday. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe".

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 23/09/11 16:40, Jeff Layton wrote: On Fri, 23 Sep 2011 16:30:36 +0200 John Hughes wrote: Well, after minor modifications (needed to include freezer.h in fs/nfs/inode.c and net/sunrpc/sched.c) I've installed Jeff Layton's patch from https://bugzilla.redhat.com/show_bug.cgi?id

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

Well, after minor modifications (needed to include freezer.h in fs/nfs/inode.c and net/sunrpc/sched.c) I've installed Jeff Layton's patch from https://bugzilla.redhat.com/show_bug.cgi?id=717735 in my 3.1-rc7 kernel... ... and it seems to work. Or at least it works a lot better. I've suspend

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 22/09/11 19:42, Jonathan Nieder wrote: So it could be worth testing 3.1-rc6 from experimental, too. I built my own kernel from github (3.1-rc7). Linux version 3.1.0-rc7 (john@medic) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Fri Sep 23 12:15:59 CEST 2011 Same problem. [ 95.56886

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 23/09/11 09:31, John Hughes wrote: On 22/09/11 19:42, Jonathan Nieder wrote: So it could be worth testing 3.1-rc6 from experimental, too. Ah, I didn't see that message. I'll try that. Nothing later than 3.1-rc4 in experimental that I can see. And that behaves in exactly th

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 22/09/11 19:42, Jonathan Nieder wrote: Thanks! That bug log has a message: | seems to be fixed in 3.1.0-0.rc6.git0.0.fc16.x86_64 and I don't see any relevant patches in the Fedora tree at . So it could be worth testing 3.1-rc6 from

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

On 22/09/11 19:34, Jonathan Nieder wrote: Hi John, John Hughes wrote: On different machines (Dell Optiplex GX270, GX280, 390) with different versions of the Kernel (x86 2.6.35, amd64 3.0.0) suspend from the kernel fails if a user who's home directory is on a krb5/nfs4 server. The k

Bug#642409: Acknowledgement (linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in)

Redhat has a similar sounding bug: https://bugzilla.redhat.com/show_bug.cgi?id=717735 With a patch. I'll see if I can test it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://l

Bug#642409: linux-2.6: "suspend" from gnome shutdown fails when krb5/nfs4 user logged in

Package: linux-2.6 Severity: normal On different machines (Dell Optiplex GX270, GX280, 390) with different versions of the Kernel (x86 2.6.35, amd64 3.0.0) suspend from the kernel fails if a user who's home directory is on a krb5/nfs4 server. The kernel seems to be unable to freeze user tasks do

Bug#606939: This looks like kernel.org bug 26002

https://bugzilla.kernel.org/show_bug.cgi?id=26002 It doesn't look the same as what's being reported as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613317 I.E. I see just little dropped bits of characters, rather than the scrambling reported there. -- To UNSUBSCRIBE, email to debian-k

Bug#615110: linux-image-2.6.37-1-686: tpm_tis prevents suspend working more than once

Package: linux-2.6 Version: 2.6.37-1 Severity: normal On a sony vaio tx3 when tpm_tis is loaded suspend only works once. This is the same behaviour as bug #591031 which was closed. dmesg shows [ 1859.244142] legacy_suspend(): pnp_bus_suspend+0x0/0x57 returns 38 [ 1859.244150] PM: Device 00:07

Bug#607439: linux-image-2.6.32-5-686: sony_laptop doesn't handle some keys on vaio tx3

Package: linux-2.6 Version: 2.6.32-29 Severity: normal On my aging sony vaio tx3 sony_laptop doesn't tell anyone about the EJECT key and gets the VOLUME UP/VOLUME DOWN buttons wrong. For the EJECT key the sony_laptop debugging info shows: sony-laptop: event ([32] [21]) at port 0x1080(+0x12) (a

Bug#591031: Bug still in 2.6.37-rc5-686

j...@carbon:~$ uname -a Linux carbon 2.6.37-rc5-686 #1 SMP Sat Dec 11 20:11:38 UTC 2010 i686 GNU/Linux dpkg -l | grep linux-image ii linux-image-2.6.37-rc5-686 2.6.37~rc5-1~experimental.3 Linux 2.6.37-rc5 for modern PCs -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debia

Bug#591031: Acknowledgement (linux-image-2.6.35-rc6-686: suspend works for a while (once?) then stops working)

This bug is still present in linux-image-2.6.36-trunk-686 2.6.36-1~experimental.1 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1292249710.7462.1.ca...@carbon.a

Bug#591031: linux-image-2.6.35-rc6-686: suspend works for a while (once?) then stops working

On Mon, 2010-08-02 at 02:33 +0100, Ben Hutchings wrote: > I see that there is a fix for this in Linux 2.6.35, which I will upload > to experimental shortly. I see the bug marked as closed, but there appears to be no 686 version, so I can't test it. -- To UNSUBSCRIBE, email to debian-kernel

Bug#591031: linux-image-2.6.35-rc6-686: suspend works for a while (once?) then stops working

On Sun, 2010-08-01 at 19:01 +0100, Ben Hutchings wrote: > Please send the output of 'readlink /sys/devices/pnp0/00:07/driver'. $ readlink /sys/devices/pnp0/00:07/driver ../../../bus/pnp/drivers/tpm_tis -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "u

Bug#591031: linux-image-2.6.35-rc6-686: suspend works for a while (once?) then stops working

Package: linux-2.6 Version: 2.6.35~rc6-1~experimental.1 Severity: normal Suspend to ram (closing laptop lid) works for a few times (maybe only once?) then starts failing "legacy_suspend(): pnp_bus_suspend+0x0/0x57 returns 38" Here's what it looked like when it worked: [10619.731187] PM: Syncing f

Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync

maximilian attems wrote: hmm, so does 2.6.33 contain a fix for it? I think not. please checkout the experimental 2.6.33 image, But I'll give it a try later this week. if it does we need to find the patch for 2.6.32. if not please contact upstream on bugzilla.kernel.org Already done t

Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync

Ben Hutchings wrote: On Wed, Feb 24, 2010 at 05:02:41PM +0100, John Hughes wrote: Package: linux-2.6 Version: 2.6.32-8 Severity: normal Running 8 copies of bonnie++ on 8 different filesystems on 8 disks seems to produce a deadlock in sync(2). Initialy all the bonnie++ processes seem to be

Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync

maximilian attems wrote: On Wed, Feb 24, 2010 at 11:00:17PM +, Ben Hutchings wrote: On Wed, Feb 24, 2010 at 05:02:41PM +0100, John Hughes wrote: Package: linux-2.6 Version: 2.6.32-8 Severity: normal Running 8 copies of bonnie++ on 8 different filesystems on 8 disks seems to

Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync

Package: linux-2.6 Version: 2.6.32-8 Severity: normal Running 8 copies of bonnie++ on 8 different filesystems on 8 disks seems to produce a deadlock in sync(2). Initialy all the bonnie++ processes seem to be running ok, but after a while only 2-3 of the disks are showing any I/O activiy and the

Bug#472455: initramfs-tools: initramfs doesn't include grep, printf, basename, tr, sed, needed by splashy

Package: initramfs-tools Version: 0.91e Severity: important Splashy 0.3.8-1 fails to start from initramfs because many busybox provided functions are missing from /bin. Maybe something to do with bug #338405 -- Package-specific info: -- /proc/cmdline root=/dev/mapper/VG1-root ro single -- /pr