similar to: XEN 3.4.x - boot problem

I''m testing xen 3.4 on my servers, and I''m having problem with controller driver, he can''t load itself properly so the system isn''t booting. The system is debian 5.0 with kernel 2.6.26-2-xen from distribution and 2.6.29-5 compiled, the problem occure with both kernels ouput from debian 5.0/kernel 2.6.26-2-xen/xen-3.4.1-rc2 4.306723] PNP: No PS/2

I have an IBM System x 3250 that successfully boots using the standard kernel (2.6.18-8.1.10.el5) but fails to boot with the xen kernel. The kernel appears to fail when it attempts to initialize the driver for the onboard SAS controller (LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS). Can anyone provide any advice? Here's the relevant info. Please let me know if any other

I am unable to boot Dom0 on a machine with Reiser file systems. Reiser support is built into the xen0 kernel. I have similar setup with ext3 file systems working just fine, so I don''t think it is a setup problem. I have tried booting with and without and initrd file, booting with the original Linux distro initrd file, etc, but nothing seems to work. I recall seeing a thread about ReiserFS

Hi List, Any ideas what is wrong with controller? It is running latest 5.x series of centos and driver spills out following warnings at random times: mptbase: ioc0: WARNING - IOC is in FAULT state (1600h)!!! mptbase: ioc0: WARNING - Issuing HardReset from mpt_fault_reset_work!! mptbase: ioc0: Initiating recovery mptbase: ioc0: WARNING - IOC is in FAULT state!!! mptbase: ioc0: WARNING -

Hi, all! I want to change current RHEL 4.0 ES into CentOS 4.2 on Sun X4100 server. The server has SAS SCSI based two 2.5" hard disks. I could only install RHEL 4.0 Update 1 because the server is equipped with RHEL 4.0 Update 1's device driver only. I've included below the boot process messages concerned with SCSI controller. If it's possible for me to install CentOS 4.0 on my

Every few hours we get the following in /var/log/messages: Oct 19 20:56:20 wltracp1a kernel: mptscsi: ioc0: bus reset: SUCCESS (sc=0000010190c56080) Oct 19 20:56:20 wltracp1a kernel: mptscsi: ioc0: attempting task abort! (sc=0000010190c56080) Oct 19 20:56:20 wltracp1a kernel: scsi4 : destination target 2, lun 0 Oct 19 20:56:20 wltracp1a kernel: command = Test Unit Ready 00 00 00 00 00 Oct

I have the exact same issue on several Sunfire v20z (hardware LSI RAID controler). Under high IO load, the raid controler starts complaining with disk errors : [163442.483878] mptbase: ioc0: LogInfo(0x11070000): F/W: DMA Error [163445.172333] sd 2:0:0:0: [sda] Unhandled error code [163445.172338] sd 2:0:0:0: [sda] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK [163445.172345] sd 2:0:0:0:

> -----Original Message----- > From: Jason Pyeron > Sent: Saturday, February 07, 2015 22:54 > > NOTE: this is happening on Centos 6 x86_64, > 2.6.32-504.3.3.el6.x86_64 not Centos 5 > > Dell PowerEdge 2970, Seagate SATA drive, non-raid. > > I have this server which has been dying randomly, with no logs. Here is a console picture. http://i.imgur.com/ZYHlB82.jpg

> -----Original Message----- > From: Chris Murphy > Sent: Tuesday, February 17, 2015 3:58 > > I think the panic is the consequence of drive write failure. > So the actual > problem is before the panic call trace. Most of the time it panics without any warning, but once there was: > > -----Original Message----- > > From: Jason Pyeron > > Sent: Sunday,

Basically the issue comes down to my Volume Groups not being found by this initrd, causing good ole kernel panic. initrd-2.6.12.6-xen3_12.1_rhel4.1.img [root@xen01 lvm]# uname -a Linux xen01.inside.***.com 2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 17:13:01 EST 2006 i686 i686 i386 GNU/Linux [root@xen01 lvm]# cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 2) Everything

> -----Original Message----- > From: Jason Pyeron > Sent: Sunday, February 08, 2015 0:00 > > > -----Original Message----- > > From: Jason Pyeron > > Sent: Saturday, February 07, 2015 22:54 > > > > NOTE: this is happening on Centos 6 x86_64, > > 2.6.32-504.3.3.el6.x86_64 not Centos 5 > > > > Dell PowerEdge 2970, Seagate SATA drive,

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal After giving xen a shoot with the fresh lenny packages, an annoying bug comes up right after trying to boot into the new system. I'll provide further informations if needed. Please see serial debug output below and here http://plzk.de/xen-lenny (maxlines got extended for comfortable reading) XEN) Xen version 3.2-1

On Xen-3.4 (unstable version), I have created CentOS PV guest and dedicated 1068 SAS controller but I am not able to see the disk which is connected to 1068 SAS controller when I do fdisk -l (vtd support is enabled in Xen). Looks like the pci device(SAS controller) is getting dedicated successfully as I can see the device in the list of pci devices shown by lspci. 05:00.0 SCSI storage

Originally, the test is on a tiger with RHEL installed. The fs is ext3 as default. Then the oops came up. I've installed the test kernel on another tiger with Suse, reiserfs as default. The kernel can boot successfully without any trouble. Is it a known issue? Or what causes this happen? thanks, -zhen -----Original Message----- From: Wang, Zhenyu Z Sent: 2004?7?20? 16:59 To: linux-ia64 at

NOTE: this is happening on Centos 6 x86_64, 2.6.32-504.3.3.el6.x86_64 not Centos 5 Dell PowerEdge 2970, Seagate SATA drive, non-raid. I have this server which has been dying randomly, with no logs. I had a tail -f over ssh for a week, when this just happened. Feb 8 00:10:21 thirteen-230 kernel: mptscsih: ioc0: attempting task abort! (sc=ffff880057a0a080) Feb 8 00:10:21 thirteen-230 kernel:

I had been running CentOS 5 happily on my Sun Fire X4200 M2 systems, then I upgraded the BIOS and iLOM firmware. Now I'm running into what seems to be a fairly common problem with newer motherboards. I cannot boot unless I use the 'noapic' kernel option. If I try to boot the kernel normally, I get the error: "MP-BIOS bug: 8254 timer not connected to IO-APIC" I can

Hello, I have a weird problem after adding new PV do LMV volume group. It seems the error comes out only during boot time. Please read the story. I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm. First pair of disks has always two arrays (md0, md1). Small md0 is used for booting and the rest - md1

Hi, I have samba server joined to ADS domain (Windows Server 2003 r2) It seems it works ok besides I can't see right access mask and edit them (if logged user is ownder of directory or file). smb.conf workgroup = CXX security = ads passdb backend = tdbsam realm = CXX.INTERNAL.COM password server = main [u] path = /mnt/u readonly = no browseable = yes acl group control

Hi, I''m running OpenSuse 12.2 with kernel 3.5.3 HBA= LSI 1068e using the MPTSAS driver (patched) (https://patchwork.kernel.org/patch/1379181/) SANOS1:/media # uname -a Linux SANOS1 3.5.3 #3 SMP Sun Sep 2 18:44:37 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux I''ve tried to simulate a disk replacement but it seems that now /dev/sdg is stuck in the btrfs pool (RAID10) SANOS1:/media #

All. I am running Xen on an ES7000 system with 4 procs and 4 GB memory. I am running Suse Sles-9 (32-bit) on the machine. I have compiled Xen (the tip on the unstable tree : 6552) with PAE enabled (XEN_TARGET_X86_PAE=y). The system boots fine. I started xend and when I tried to bring up a virtual machine, the system gave me the following error on the command line. On the serial port, I saw an