[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#676971: marked as done (3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors)



Your message dated Tue, 13 Aug 2013 23:14:34 +0200
with message-id <20130813211434.GC559@inutil.org>
and subject line Re: xen i/o errors
has caused the Debian Bug report #676971,
regarding 3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
676971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676971
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 3.2.0-0
Severity: important

When booting with the xen/hypervisor kernel the system hangs with i/o
errors thrown in console. The standard kernel is working fine and the
disk has been tested and swapped.
Errors include:
ata1.00: failed command: READ DMA
task xend:1404 blocked for more than 120 seconds
Buffer I/O error on device sda1
end_request: I/O error, dev sda

I am using Debian Squeeze, kernel 3.2.0-0.bpo.2-686-pae.
The same error seems to exists in xen-linux-system-2.6.32-45, as far
as I tested.



--- End Message ---
--- Begin Message ---
On Sun, Jun 10, 2012 at 06:09:08PM -0500, Jonathan Nieder wrote:
> tags 676971 + moreinfo
> quit
> 
> Hi Kacper,
> 
> Kacper wrote:
> 
> > When booting with the xen/hypervisor kernel the system hangs with i/o
> > errors thrown in console. The standard kernel is working fine and the
> > disk has been tested and swapped.
> > Errors include:
> > ata1.00: failed command: READ DMA
> > task xend:1404 blocked for more than 120 seconds
> 
> Please contact xen-users@lists.xen.org to track down the cause of
> this.

No further feedback, closing the bug. If this bug still occurs in the Wheezy
kernel or later, please reopen.

Cheers,
        Moritz

--- End Message ---

Reply to: