similar to: How to map ata#.# numbers to /dev/sd numbers?

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Got a bunch of servers from Penguin. Supermicro m/b's H8QG6. We put a 3tb drive in for additional workspace for the users, and some of them won't read, others will go for weeks, then spit out DRDY errors. lshw shows the controller as an ATI SB7x0/SB8x0/SB9x0 SATA. I did notice that it shows *-storage description: SATA controller product: SB7x0/SB8x0/SB9x0 SATA

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of my Ubuntu machines without success. It keeps giving errors like this: [ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10 frozen [ 9.115550] ata9.00: failed command: READ FPDMA QUEUED [ 9.115556] ata9.00: cmd 60/04:00: d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in [ 9.115557]

Observed on Linux 3.2.9 after the controller/disk flaked in-out. (The world still needs a SCSI error decoding tool to tell normal people what cmd and res are about.) [ 157.732885] device label srv devid 4 transid 11292 /dev/sdf [ 157.733201] btrfs: disk space caching is enabled [ 172.936515] device label srv devid 4 transid 11292 /dev/sdf [44106.091461] ata4.01: exception Emask 0x0 SAct 0x0

Hello, I was wondering if anyone could point me in the right direction? I am receiving these in my log file and do not know what they mean or what to look for; Mar 8 04:03:56 bms kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 8 04:03:56 bms kernel: ata3.00: cmd 25/00:28:42:d3:37/00:00:13:00:00/e0 tag 0 cdb 0x0 data 20480 in Mar 8 04:03:56 bms kernel: res

I've two machines with almost identical hardware (slightly different CPUs). The SATA/RAID controller is SiI 3114. One of the servers was installed a while ago by someone else, it's running Fedora Core 5 and RAID is enabled: # df -m Filesystem 1M-blocks Used Available Use% Mounted on /dev/dm-6 125931 2990 116441 3% / /dev/dm-1 99

On Fri 06/Sep/2013 10:12:29 +0200 Ian Campbell wrote: > On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: >> >> I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then >> crashes when used=2837436K free=4127432K. > > On a modern dom0 kernel you need to specify the maximum memory as well, > i.e. dom0_mem=8192M,max:8192M

I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware. Despite the error messages, the disks seem to be working with no problems. Could someone please tell me what these error are and if there is some known way to prevent them? I searched the Net for these errors and they seem

I finished to try to install Asterisk Now 1.4.0 on an AMD 3800 dual processor machine. The install lookups on the search for the Sata drive, since however it loads the sata_sil driver it doesn't work. Did someone knows what version of Linux is using on Asterisk Now? Thanks, Carlos Alperin -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Fri, 2013-09-06 at 16:39 +0200, Alessandro Vesely wrote: Both sets of log contain stuff like: > Sep 6 15:22:53 pcale kernel: [ 126.828195] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x6 frozen > Sep 6 15:22:53 pcale kernel: [ 126.828199] ata4: SError: { 10B8B } > Sep 6 15:22:53 pcale kernel: [ 126.828201] ata4.00: failed command: SMART > Sep 6 15:22:53 pcale

Hi folks, I have just installed a PCI SATA controller based on the SIL3112A chipset into my Centos-3 (latest kernel patches applied) system and moved an existing (not the boot disk) SATA drive from the onboard controller to the SIL-based one so I can setup software RAID with two 300GB drives. Kudzu/Linux found the controller and drives straight away and they've appeared as 'hda' and

Hi, I have a SATA PCIe 6Gbps 4 port controller card made by Startech. The kernel (Linux viz1 2.6.32-220.4.1.el6.x86_64) sees it as Marvell Technology Group Ltd. 88SE9123 I use it to provide extra SATA ports to a raid system. The HD's are all "WD2003FYYS" and so run at 3Gbps on the 6Gbps controller. However I am seeing lots of instances of errors like this

I''m struggling to get Xen to boot on a FC4 Opteron box. I''ve included the tail of the boot log below [1]. I suspect that the problems relates to the software RAID 1 root and boot partitions, and how it relates to the initrd image. The RAID volumes fail to mount. I compiled the Xen snapshot from the 23rd September, and the only change I''ve made is to enable the

For some time I have been seeing disk errors in the syslog every seven days. Until today it always happens Sunday morning at 8:13 AM, plus or minus a minute or two. Yesterday it happened at 1:13 AM. Here are the pertinent log entries for the latest occurrence: Jan 6 01:12:29 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:12:29 g2 kernel: ata9.00: BMDMA stat

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=339 ------- Additional Comments From scrizt@ludd.ltu.se 2006-06-26 17:57 MET ------- Is this bug forgotten ? Anyhow, I ran into it when setting up this strange network of mine.. I dont think my setup is causing anything strange however.. It appears even if no machine is connected to the "inner" port of the bridge.. I

Hello fellow CentOS'ers- I've got a system running CentOS 5.0. The motherboard has two onboard SATA ports with two drives attached. I installed the system on a RAID1 setup. However, I'd like to add a hotspare disk to the array. Since there are no additional SATA ports, I've installed an additional controller. After partitioning, the additional drive was easily and successfully