Bug#597828: linux-image-2.6.32-5-amd64: [xen] debug options + sysrq-t => sending NMI to all CPUs: BUG: unable to handle kernel paging request

2010-09-23 Thread Timo Juhani Lindfors
Ian Campbell writes: > I guess the right thing to do would be to using some existing paravirt > interface to send the IPI instead of tweaking the APIC directly, or if Is void xen_send_IPI_one(unsigned int cpu, enum ipi_vector vector); in xen/events.h perhaps already this? -- To UNSUBSCRIB

Bug#597904: phonet crahes when network namespace is destroyed

2010-09-23 Thread Ben Hutchings
Package: linux-2.6 Version: 2.6.32-23 If the phonet module is loaded, destroying a network namespace crashes the kernel. This bug is known to be triggered by using Chromium (which creates a network namespace) and some Nokia phones (which trigger loading of phonet): http://code.google.com/p/chrom

Bug#597729: #7303: linux-image-2.6-amd64: page allocation, failure. order:0, mode:0x20

2010-09-23 Thread Het Hooghuis
Okay; Thank you. We will continue using the work-around using "e1000"; we haven't experienced the issue using that configuration. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lis

Bug#597865: Xen domU randomly loose network

2010-09-23 Thread Ian Campbell
On Thu, 2010-09-23 at 21:00 +0200, Guillaume Seigneuret wrote: > Is there any explanation to this issue ??? > I can't get no error log of this weird behavior and it's driving me > mad ! Please see bug 596635 which this one is now merged with. In a nutshell smartpoll mode is not reliable (causing

Bug#597865: Xen domU randomly loose network

2010-09-23 Thread Guillaume Seigneuret
Is there any explanation to this issue ??? I can't get no error log of this weird behavior and it's driving me mad ! Cordialement, *Guillaume Seigneuret* *Network and System Security Architect Web : http://www.omegacube.fr Address :* Hôtel Technologique - BP 100 Technopôle de Château G

Processed: reassign 597865 to linux-2.6, forcibly merging 596635 597865

2010-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 597865 linux-2.6 Bug #597865 [linux-image-2.6.32-5-xen-amd64] Xen domU randomly loose network Bug reassigned from package 'linux-image-2.6.32-5-xen-amd64' to 'linux-2.6'. > forcemerge 596635 597865 Bug#596635: linux-image-2.6.32-5-xen-amd

Processed: tagging 596635

2010-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 596635 + pending Bug #596635 [linux-2.6] linux-image-2.6.32-5-xen-amd64: Xen vif bridge failure / netfront smartpoll bugfix Added tag(s) pending. > End of message,

Bug#597865: Xen domU randomly loose network

2010-09-23 Thread Ian Campbell
There's a very high chance this is the same issue as described in #596635. I'm just about to add a patch for this to SVN (which will become 2.6.32-24). On Thu, 2010-09-23 at 20:00 +0200, Guillaume Seigneuret wrote: > Package: linux-image-2.6.32-5-xen-amd64 > Version: 2.6.32-23 > > domU's random

Bug#596419: Acknowledgement (xen-linux-system-2.6.32-5-xen-amd64: causes a system hangup by the shutdown of the system, aacraid (sw raid) involved in hangup)

2010-09-23 Thread Artur Linhart - Linux communication
>-Original Message- >From: Konrad Rzeszutek Wilk [mailto:konrad.w...@oracle.com] >Sent: Monday, September 20, 2010 6:08 PM >To: Artur Linhart - Linux communication >Cc: 'Ian Campbell'; 596...@bugs.debian.org >Subject: Re: Bug#596419: Acknowledgement (xen-linux-system-2.6.32-5-xen-amd64: >

Bug#597865: Xen domU randomly loose network

2010-09-23 Thread Guillaume Seigneuret
Package: linux-image-2.6.32-5-xen-amd64 Version: 2.6.32-23 domU's randomly loose network, not at the same time. The only solution for the network to comes back is to reboot the virtual machine. Distrib version : Debian squeeze # dpkg -l | grep xen ii libxenstore3.0 3.4.3~

Re: 3 system freezes after upgrading to 2.6.32-23: advice needed

2010-09-23 Thread Pedro Bulach Gapski
On Wed, Sep 22, 2010 at 8:29 PM, Ben Hutchings wrote: > On Wed, 2010-09-22 at 18:33 -0300, Pedro Bulach Gapski wrote: >> I have blacklisted the brcm80211 module and worked all day without a problem. >> >> I googled to http://linuxwireless.org/en/users/Drivers/brcm80211, >> where it is stated that

[bts-link] source package linux-2.6

2010-09-23 Thread bts-link-upstream
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #591622 (http://bugs.debian.org/591622) # * http://bugzilla.kernel.org/show_bug.cgi

Bug#597582: marked as done (initramfs-tools should not ignore failing hook scripts)

2010-09-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Sep 2010 14:13:49 + with message-id <20100923141349.gc5...@vostochny.stro.at> and subject line Re: Bug#597582: initramfs-tools should not ignore failing hook scripts has caused the Debian Bug report #597582, regarding initramfs-tools should not ignore failing hook sc

Bug#388721: was festivities Standard

2010-09-23 Thread larger Al
for and recognizable he dissolved for Systems a Italian -- 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/debian-kernel

Processed: Re: Bug#597817: base: Realtek RTL8111/8168B doesn't always work

2010-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 597817 linux-2.6 Bug #597817 [base] base: Realtek RTL8111/8168B doesn't always work Bug reassigned from package 'base' to 'linux-2.6'. > thanks Stopping processing here. Please contact me if you need assistance. -- 597817: http://bugs.d

Bug#597820: linux-image-2.6.32-5-amd64: 2.6.32 doesn't support the f71889fg sensor chip

2010-09-23 Thread Mike Hommey
Package: linux-2.6 Version: 2.6.32-23 Severity: wishlist Tags: squeeze I installed a fresh squeeze on a new PC with a MSI P55M-GD45 motherboard that uses a f71889fg sensor chip. Unfortunately, while lm-sensors' sensor-detect is able to find the chip and suggest a kernel module, the module doesn't

Re: Bug#597817: base: Realtek RTL8111/8168B doesn't always work

2010-09-23 Thread Holger Levsen
reassign 597817 linux-2.6 thanks On Donnerstag, 23. September 2010, Aniruddha wrote: > Package: base > Severity: important > > > Every other boot I don't have internet access, eth0 doesn't get an ip > address assigned from the dhcp server. ifdown eth0 / ifup eth0 doens't > work either. When I reb

Processed: Re: framebuffer gone for intel i915 starting 2.6.32-21

2010-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 595511 595103 Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets Bug#595103: framebuffer gone for intel i915 starting 2.6.32-21 Bug#595521: i915: system locks up when star

Bug#595103: framebuffer gone for intel i915 starting 2.6.32-21

2010-09-23 Thread jidanni
forcemerge 595511 595103 severity 595511 grave thanks Even /etc/init.d/console-setup is affected I believe. Normally during boot the console messages disappear, then reappear but now getting printed at a smaller size. This corresponds to the point things start getting logged in /var/log/boot. The f

Processed: severity of 595103 is normal

2010-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 595103 normal Bug #595103 [linux-2.6] framebuffer gone for intel i915 starting 2.6.32-21 Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 595103: http://bugs.debian.o

Bug#595103: framebuffer gone for intel i915 starting 2.6.32-21

2010-09-23 Thread Julien Cristau
On Thu, Sep 23, 2010 at 08:59:54 +0800, jida...@jidanni.org wrote: > However, until it is fixed, one cannot dream of running X windows. Even > just running on the console will eventually lead to a black screen, and > the need to reboot, disks having been synced or not. > This is not true. You ca