Bug#699269: Info received (IPv6 slow and hangs over failed bonding link)

2013-01-30 Thread Gasha
Hi, I think, that i have found real source of this bug, but not in Debian. https://www.virtualbox.org/ticket/9380 Did some tests, and found that slowness is only in one direction (virtual->real). Unplugged cable was coincidence. This bug should be closed. Gasha -- To UNSUBSCRIBE, email to

Bug#699406: linux-image-3.2.0-4-amd64: HD Audio early patching ignored

2013-01-30 Thread Andres Cimmarusti
Package: src:linux Version: 3.2.35-2 Severity: normal Due to BIOS issues, a lot of systems advertise several HDMI pins even though physically only one is reachable. In my case, a LC2131 (SP13R) laptop shows the following available pins: $ aplay -l List of PLAYBACK Hardware Devices car

Bug#695182: [RFC] Reproducible OOM with just a few sleeps

2013-01-30 Thread Ben Hutchings
On Thu, 2013-01-31 at 06:40 +1100, paul.sz...@sydney.edu.au wrote: > Dear Pavel and Dave, > > > The assertion was that 4GB with no PAE passed a forkbomb test (ooming) > > while 4GB of RAM with PAE hung, thus _PAE_ is broken. > > Yes, PAE is broken. Still, maybe the above needs slight correction:

Re: an issue with crash(8) perhaps?

2013-01-30 Thread Ben Hutchings
On Wed, 2013-01-30 at 14:50 -0500, David Magda wrote: > It appears that it may be an issue with the "crash" package. From the > release notes: > > 5.1.6 - Fixed several typos in the updated crash.8 man page. > (bob.montgom...@hp.com) > [...] >- Fix to support Linux 3.x version n

Processed: Re: [experimental] boot fails as xen domU: xc_dom_find_loader: no loader found

2013-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 699381 src:xen 4.0.1-5.5 Bug #699381 {Done: Julien Cristau } [src:linux] linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found Bug reassigned from package 'src:linux' to 'src:xen'. No longer marked as

Bug#699381: marked as done (linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found)

2013-01-30 Thread Debian Bug Tracking System
Your message dated Wed, 30 Jan 2013 22:43:00 +0100 with message-id <20130130214300.gq8...@radis.cristau.org> and subject line Re: Bug#699381: linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found has caused the Debian Bug report #699381, regarding linux-image-3.7

Bug#699381: linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found

2013-01-30 Thread Timo Juhani Lindfors
Julien Cristau writes: > What's your hypervisor? You need one with xz support, see 695056. xen-hypervisor-4.0-amd64 4.0.1-5.5 I guess we could try upgrading the dom0 to testing (wheezy) in a non-production environment but that'll take several weeks at least. -- To UNSUBSCRIBE, email to debia

Bug#699381: linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found

2013-01-30 Thread Julien Cristau
On Wed, Jan 30, 2013 at 21:59:59 +0200, Timo Juhani Lindfors wrote: > Package: src:linux > Version: 3.7.3-1~experimental.1 > Severity: normal > > With the following configuration the kernel fails to boot as xen domU: > What's your hypervisor? You need one with xz support, see 695056. Cheers, J

an issue with crash(8) perhaps?

2013-01-30 Thread David Magda
It appears that it may be an issue with the "crash" package. From the release notes: 5.1.6 - Fixed several typos in the updated crash.8 man page. (bob.montgom...@hp.com) [...] - Fix to support Linux 3.x version number change. Without the patch, the crash session fails wit

Bug#699381: linux-image-3.7-trunk-amd64: boot fails as xen domU: xc_dom_find_loader: no loader found

2013-01-30 Thread Timo Juhani Lindfors
Package: src:linux Version: 3.7.3-1~experimental.1 Severity: normal With the following configuration the kernel fails to boot as xen domU: pyGRUB version 0.6 ┌┐ │ Debian GNU/Linux, with Linux 3.7-trunk-amd64

Bug#695182: [RFC] Reproducible OOM with just a few sleeps

2013-01-30 Thread paul . szabo
Dear Pavel and Dave, > The assertion was that 4GB with no PAE passed a forkbomb test (ooming) > while 4GB of RAM with PAE hung, thus _PAE_ is broken. Yes, PAE is broken. Still, maybe the above needs slight correction: non-PAE HIGHMEM4G passed the "sleep test": no OOM, nothing unexpected; whereas

Bug#699361: linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and CPU intensive

2013-01-30 Thread Adrien Kunysz
Package: src:linux Version: 3.2.35-2~bpo60+1 Severity: normal Tags: upstream patch *** Please type your report below this line *** We are running a NFSv4 server on Debian Squeeze with 3.2.0-0.bpo.4-amd64 and recently started observing performance degradation in the form of slower response time fo

Bug#695182: [RFC] Reproducible OOM with just a few sleeps

2013-01-30 Thread Dave Hansen
On 01/30/2013 04:51 AM, Pavel Machek wrote: > Are you saying that HIGHMEM configuration with 4GB ram is not expected > to work? Not really. The assertion was that 4GB with no PAE passed a forkbomb test (ooming) while 4GB of RAM with PAE hung, thus _PAE_ is broken. -- To UNSUBSCRIBE, email to d

Bug#695182: [RFC] Reproducible OOM with just a few sleeps

2013-01-30 Thread Pavel Machek
Hi! > > I understand that more RAM leaves less lowmem. What is unacceptable is > > that PAE crashes or freezes with OOM: it should gracefully handle the > > issue. Noting that (for a machine with 4GB or under) PAE fails where the > > HIGHMEM4G kernel succeeds and survives. > > You have found a de

Bug#666108: Thanks for fixing.

2013-01-30 Thread Martin Stern
Hello, we got some "LSI Logic / Symbios Logic MegaRAID SAS 9240 (rev 03) / Dell PERC H310 Mini Monolithics" RAID-Controllers. Until Firmware Version 20.10.1-0084 there were running nice with linux-image-2.6.32-5-openvz-amd64 version 2.6.32-46. FW-Version 20.11.0-0002 only works with kerne-pack