WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1287] Sometimes XenU guest cannot boot up on 32e host.

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1287] Sometimes XenU guest cannot boot up on 32e host.
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 9 Jul 2008 02:28:15 -0700
Delivery-date: Wed, 09 Jul 2008 02:28:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1287-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1287


haicheng.li@xxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #1 from haicheng.li@xxxxxxxxx  2008-07-09 02:28 -------
reproduced it and got some errors from dom0:

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen                
ata1.00: (BMDMA stat 0x24)                                                      
ata1.00: tag 0 cmd 0xca Emask 0x4 stat 0x40 err 0x0 (timeout)                   
hdb: lost interrupt                                                             
ata1.00: qc timeout (cmd 0xec)                                                  
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)                           
ata1.00: revalidation failed (errno=-5)                                         
ata1: failed to recover some devices, retrying in 5 secs                        
ATA: abnormal status 0xD8 on port 0x18C7                                        
ATA: abnormal status 0xD8 on port 0x18C7                                        
ATA: abnormal status 0xD8 on port 0x18C7                                        



hdb: lost interrupt                                                             
ata1.00: qc timeout (cmd 0xec)                                                  
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)                           
ata1.00: revalidation failed (errno=-5)                                         
ata1: failed to recover some devices, retrying in 5 secs                        
ATA: abnormal status 0xD8 on port 0x18C7                                        
ATA: abnormal status 0xD8 on port 0x18C7                                        
ata1.00: qc timeout (cmd 0xec)                                                  
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)                           
ata1.00: revalidation failed (errno=-5)                                         
ata1.00: disabled                                                               
end_request: I/O error, dev sda, sector 28318183                                
Buffer I/O error on device sda1, logical block 3539765                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539766                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539767                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539768                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539769                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539770                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539771                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539772                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539773                          
lost page write due to I/O error on sda1                                        
Buffer I/O error on device sda1, logical block 3539774                          
lost page write due to I/O error on sda1                                        
end_request: I/O error, dev sda, sector 28318287                                
end_request: I/O error, dev sda, sector 527503                                  
EXT3-fs error (device sda1): ext3_get_inode_loc: unable to read inode block -
i.

end_request: I/O error, dev sda, sector 8453751                                 
end_request: I/O error, dev sda, sector 20176559                                
end_request: I/O error, dev sda, sector 20177567                                
journal commit I/O error                                                        
end_request: I/O error, dev sda, sector 8453751                                 
ext3_abort called.                                                              
EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal    
Remounting filesystem read-only                                                 
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22076015                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                
end_request: I/O error, dev sda, sector 22013239                                


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>