Bug#577054: acpi: After upgrade, computer does not turn off

2011-10-04 Thread Jonathan Nieder
fixed 577054 linux-2.6/2.6.32-35squeeze2 found 577054 linux-2.6/2.6.32-9 quit Γιώργος Πάλλας wrote: I'm sending you the logs requested. I can't remember anything about when the problem was fixed... Thanks again, and sorry for the noise. -- To UNSUBSCRIBE, email to

Processed: Re: acpi: After upgrade, computer does not turn off

2011-10-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: fixed 577054 linux-2.6/2.6.32-35squeeze2 Bug #577054 {Done: Jonathan Nieder jrnie...@gmail.com} [linux-2.6] acpi: After upgrade, computer does not turn off Bug Marked as fixed in versions linux-2.6/2.6.32-35squeeze2. found 577054

Bug#642977: Requested Information

2011-10-04 Thread Hostmaster
Sep 26 07:26:57 srv03044 kernel: [ 373.475130] Pid: 5200, comm: nmbd Not tainted 2.6.32-5-vserver-amd64 #1 Sep 26 07:26:57 srv03044 kernel: [ 373.475131] Call Trace: Sep 26 07:26:57 srv03044 kernel: [ 373.475135] [812a1d5b] ? udp_sendmsg+0x5b9/0x69c Sep 26 07:26:57 srv03044 kernel: [

Processed: mundane linux-2.6 bug triage

2011-10-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # Taking some bugs off the radar. # # Bug: http://bugs.debian.org/538158 # Submitter: Arcady Genkin agen...@cdf.toronto.edu # Submitter: Juan Miguel Corral Cano cde_ruylo...@yahoo.es # Summary: [lenny] soft lockup in default_idle # Status:

Bug#644236: installation fails when rpcbind is disabled, although nfs-common is disabled there too

2011-10-04 Thread Martin Steigerwald
Package: nfs-common Version: 1:1.2.5-2 Severity: important Dear Maintainer, I have found a bug on upgrading nfs-common that might be nfs-common init script header or insserv related: * What led up to the situation? Upgrading nfs-common when nfs-common and (!) rpcbind is disabled in

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

2011-10-04 Thread John Hughes
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 access my home directory which

Processed: Re: linux-image-3.0.0-1-rt-amd64: Suspend to ram hangs

2011-10-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # hangs in processors test of pm_test (i.e., offlining or onlining # nonboot cpus). Waiting for more data from John upstream. Many # thanks to John and Uwe for their work so far. forwarded 643301

Bug#644212: linux-image-2.6.32-5-amd64: kernel BUG at kernel/exit.c:1035: invalid opcode: 0000

2011-10-04 Thread Faidon Liambotis
On Tue, Oct 04, 2011 at 03:29:50AM +0100, Ben Hutchings wrote: On Tue, 2011-10-04 at 03:51 +0300, Faidon Liambotis wrote: Package: linux-2.6 Version: 2.6.32-35 Severity: normal The stack trace can be seen below; if it matters, note that the machine a) is running under KVM, b) has

Bug#623177: linux-2.6: Please enable CONFIG_CRASH_DUMP on x86 architectures

2011-10-04 Thread Sven Ulland
Seconded. Also reported in [1]. The status of this issue is also the same in Wheezy's linux-image-3.0.0-1-amd64 and experimental's linux-image-3.1.0-rc7-amd64_3.1.0~rc7-1~experimental.1_amd64.deb I haven't been able to figure out if enabling CONFIG_CRASH_DUMP adds any overhead at all. Are there

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread PICCORO McKAY Lenz
Package: linux-2.6 Version: 2.6.38-5~bpo60+1 Justification: breaks the whole system Severity: critical Tags: d-i upstream The system (independient of kernel even backport version or oficial ) hangs, and stops, i investigated with dmesg, and so then found this trace : irq 10: nobody cared (try

Bug#644281: linux-image-3.0.0-1-amd64: problem after changing mtu size on jme kernel module

2011-10-04 Thread kantacki
Package: linux-2.6 Version: 3.0.0-3 Severity: important Tags: upstream Hello, When I try to execute: ifconfig eth0 mtu 4000 up or ifconfig eth0 mtu 7198 up my nic stops working and changing back to mtu 1500 does not help. To use my nic again I have to execute: rmmod jme modprome jme and the the

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread Ben Hutchings
On Tue, Oct 04, 2011 at 01:34:30PM -0430, PICCORO McKAY Lenz wrote: Package: linux-2.6 Version: 2.6.38-5~bpo60+1 [...] What about 3.0 (currently in testing and unstable)? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking.

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread PICCORO McKAY Lenz
err currently i'm prefer stable.. this trend for lasted software its a windoze think i' talking ab out stable kernel bug, what about that? i'm running 2.6.39, quite more stable, but previosly i update alsa state of mixer, and also install a few packages..but acpi also fail with 2.6.39 too, and

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread Jonathan Nieder
Hi, PICCORO McKAY Lenz wrote: i' talking ab out stable kernel bug, what about that? A 3.x kernel (to help us debug, not as a long-term solution) should not require any dependencies except for linux-base and initramfs-tools from outside squeeze. [...] but acpi also fail with 2.6.39 too, and

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread PICCORO McKAY Lenz
ok thanks, i will test again, currently 2.6.39 works well, more stable and do not hang too much, but what about squeeze brand 2.6.32, this fails too! On Tue, Oct 4, 2011 at 3:30 PM, Jonathan Nieder jrnie...@gmail.com wrote: Hi, PICCORO McKAY Lenz wrote: i' talking ab out stable kernel

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread Jonathan Nieder
PICCORO McKAY Lenz wrote: i will test again, currently 2.6.39 works well, more stable and do not hang too much, ... when you add the acpi=off boot-time parameter. I wouldn't call that working. but what about squeeze brand 2.6.32, this fails too! Actually, we don't care about 2.6.39 at all,

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread PICCORO McKAY Lenz
On Tue, Oct 4, 2011 at 3:47 PM, Jonathan Nieder jrnie...@gmail.com wrote: PICCORO McKAY Lenz wrote: i will test again, currently 2.6.39 works well, more stable and do not hang too much, ... when you add the acpi=off boot-time parameter.  I wouldn't call that working. ok obviously this its

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread Ben Hutchings
On Tue, Oct 04, 2011 at 03:22:17PM -0430, PICCORO McKAY Lenz wrote: err currently i'm prefer stable.. this trend for lasted software its a windoze think i' talking ab out stable kernel bug, what about that? [...] I'm asking you to test 3.0, to see whether the bug has been fixed upstream. I

Bug#644279: linux-image-2.6.38-bpo.2-686: Disabling IRQ 10 hang and crash laptops, ALL KERNELS on squeeze backports

2011-10-04 Thread Jonathan Nieder
Jonathan Nieder wrote: PICCORO McKAY Lenz wrote: but what about squeeze brand 2.6.32, this fails too! Actually, we don't care about 2.6.39 at all, except when it is relevant to fixing 2.6.32 or 3.x. Ah, sorry, that was less helpful than it should have been. I didn't actually answer your

Re: Bug#636123: Info received (Bug#636123: linux-image-2.6.39-2-amd64: root filesystem not recognised - new bug report)

2011-10-04 Thread Luke Kenneth Casson Leighton
right - _finally_ i've encountered a requirement to upgrade a 2nd system that has lvm2 and (in this 2nd case 2.6.18-486) a linux kernel image, and have encountered the *exact* same problem as is in bugs 636123 and 638896. this time, however, i was anticipating that something might go wrong, so