Bug#660425: Possible bugg in linux-image-3.2.0-0.bpo.4-amd64 (resent)

2013-01-29 Thread Mattias Eriksson
Hi! I have rebooted the server, dom0 is now running the 3.2.35-2 image from backports, with the "nosmap" command line option as suggested. Previous oopses occurred after some time, a few days or so, so I'll watch and see what happens. Thanks for taking the time. BR // Mattias Den 28 January 2

Bug#660425: Possible bugg in linux-image-3.2.0-0.bpo.4-amd64 (resent)

2013-01-28 Thread Ian Campbell
Thanks Ben, not sure how I missed 660425 the first time around. On Wed, 2013-01-23 at 14:50 +, Ben Hutchings wrote: > On Tue, 2013-01-22 at 10:15 +0100, Mattias Eriksson wrote: > > Hi! > > > > I have switched back to the current stable kernel in squeeze, 2.6.32-46, > > since I need the > > m

Bug#660425: Possible bugg in linux-image-3.2.0-0.bpo.4-amd64 (resent)

2013-01-25 Thread Ben Hutchings
On Tue, 2013-01-22 at 10:15 +0100, Mattias Eriksson wrote: > Hi! > > I have switched back to the current stable kernel in squeeze, 2.6.32-46, > since I need the > machine to be up and running. And now it is just as stable as it was before. > > Even though I have never had any real issues using x

Re: Possible bugg in linux-image-3.2.0-0.bpo.4-amd64 (resent)

2013-01-20 Thread Ben Hutchings
On Fri, 2012-12-28 at 11:23 +0100, Mattias Eriksson wrote: > Hi! > > I'm using linux kernel 3.2.32 from backports, > linux-image-3.2.0-0.bpo.4-amd64, with squeeze. > The system is running xen (4.0.1 from squeeze) on a > VIA VB8001-16 motherboard and I get easily triggered kernel oops:es in > domU.

Possible bugg in linux-image-3.2.0-0.bpo.4-amd64 (resent)

2012-12-28 Thread Mattias Eriksson
Hi! I'm using linux kernel 3.2.32 from backports, linux-image-3.2.0-0.bpo.4-amd64, with squeeze. The system is running xen (4.0.1 from squeeze) on a VIA VB8001-16 motherboard and I get easily triggered kernel oops:es in domU. All PV guests are running Squeeze with linux 3.2.32 from bpo. I also hav