search for: scontrol

...0 loaded. [ 1.879093] ata1: DUMMY [ 1.879096] ata2: DUMMY [ 1.879099] ata3: SATA max UDMA/133 abar m524288 at 0xc5700000 port 0xc5700200 irq 136 [ 1.879102] ata4: SATA max UDMA/133 abar m524288 at 0xc5700000 port 0xc5700280 irq 137 [ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.183893] ata3.00: qc timeout (cmd 0xec) [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.183960] ata4.00: qc timeout (cmd 0xa1) [ 7.183974] ata4.00: failed to IDENTIFY (I/O error, err_mask...

...16:29:27 sauron kernel: ata5: SATA max UDMA/133 cmd 0xF8874300 ctl 0x0 bmdma 0x0 irq 58 Jul 26 16:29:27 sauron kernel: ata6: SATA max UDMA/133 cmd 0xF8874380 ctl 0x0 bmdma 0x0 irq 58 Jul 26 16:29:27 sauron kernel: scsi1 : ahci Jul 26 16:29:27 sauron kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Jul 26 16:29:27 sauron kernel: ata1.00: qc timeout (cmd 0xec) Jul 26 16:29:27 sauron kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x104) Jul 26 16:29:27 sauron kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Jul 26 16:29:27 sauron kernel: ata1.00: qc timeout (cmd 0xa...

> > [ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 7.183893] ata3.00: qc timeout (cmd 0xec) > [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 7.183960] ata4.00: qc timeout (cmd 0xa1) > [ 7.183974] ata4.00: failed to IDEN...

On Mon, Jun 24, 2019 at 3:35 AM Pete Biggs <pete at biggs.org.uk> wrote: > On Sun, 2019-06-23 at 22:13 -0400, doug schmidt wrote: > > Hi, > > I'm having an issue with my Thinkpad P70 laptop/workstation. This system > is > > a dual boot, > > windows 10 pro and centos 7. I have not needed to use the cdrom until > now, > > however the system does not

I''m trying to set up Xen 4.1 on Ubuntu 12.04 server (x64) and when booting the dom0 it fails while apparently attempting to initialize the SATA devices. It does find one device (ata3) but then just halts and hangs apparently forever. Any suggestions as to what could be causing this, or whether upgrading to 13.04/Xen 4.2 might fix the issue?

...m, the drives have a working fan directly blowing on the drives, and the case its in has very good airflow. ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 193 ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 193 scsi0 : sata_nv ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 320173056 sectors: LBA48 ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : sata_nv ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7, max UDMA/133, 320173056 sectors: LBA48 ata2.00: ata2: dev 0 multi count 16 ata2.00:...

...ingle 160 GiB OS drive (with CentOS 5.0) and 4x500 GiB drives setup in a RAID-5 configuration. All drives are setup for 3.0 GiB SATA link, and the motherboard also supports that. Looking in dmesg when the system comes up, I see that reflected as well: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32) ata2.00: configured for UDMA/133 scsi2 : ahci ata...

...10105]          res 40/00:04:3f:da:79/00:00:6a:00:00/40 Emask 0x60 (host bus error) Mar  9 23:56:28 ftp2 kernel: [121492.610108] ata8.00: status: { DRDY } Mar  9 23:56:28 ftp2 kernel: [121492.610116] ata8: hard resetting link Mar  9 23:56:30 ftp2 kernel: [121494.160055] ata7: failed to resume link (SControl 3B8) Mar  9 23:56:30 ftp2 kernel: [121494.180035] ata8: failed to resume link (SControl 4F0) Mar  9 23:56:30 ftp2 kernel: [121494.340046] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 3B8) Mar  9 23:56:30 ftp2 kernel: [121494.360070] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 4F0) Mar  9...

...ives are set as RAID1 SATA2: HD extra SATA3: DVD SATA4: external USB disk Snip from dmesg shows the ATAPI device being detected. ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xe400 irq 10 ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xe408 irq 10 ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATAPI: PIONEER BD-ROM BDC-202, 1.01, max UDMA/66 ata3.00: configured for UDMA/66 ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata4.00: ATA-7: ST3500630AS, 3.AAC, max UDMA/133 ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) ata4.00: configured for UDMA/133 sda...

I am trying to get a pv_ops dom0 working for testing, but I am running into an elf_init error: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Full output attached. >From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructions on:

...tting latency timer of device 0000:00:05.0 to 64 ata1: SATA max UDMA/133 cmd 0xC480 ctl 0xC402 bmdma 0xBC00 irq 58 ata2: SATA max UDMA/133 cmd 0xC080 ctl 0xC002 bmdma 0xBC08 irq 58 scsi0 : sata_nv input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 781422768 sectors: LBA48 NCQ (depth 0/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : sata_nv ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7, max UDMA/133, 781422768 sectors: LBA48 NCQ (depth 0/32) ata2.00: a...

I am having problems getting my 64-bit Debian Squeeze (Xen version 4.0, Linux Kernel 2.6.32) dom0 to recognize a harddrive connected to a secondary sata controller. My motherboard is a Gigabyte GA-X79-UP4 and has two sata controllers. The first is controlled by an Intel X79 chipset and the second is controlled by a Marvell 88SE9172 chip. During the initial install of Debian everything is fine and

...I should replace it. But which one of the physical disks is sda?? The machine boots fine from either one of the disks, (and the booting disk of course is always called sda). In the messages log I see entries like this: Apr 29 02:21:07 a134-224 kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) By noticing which SATA link (ata1, ata2) is up and which is down, I can find out which physical disk is connected to ata1 and which to ata2. If both disks are connected, will the hd in ata1 become sda, and the hd in ata2 become sdb?? - Jussi

https://bugs.freedesktop.org/show_bug.cgi?id=67161 Priority: medium Bug ID: 67161 Assignee: nouveau at lists.freedesktop.org Summary: Blank video after resuming from S3 or S4 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mauromol at tiscali.it

Ok, got a quickie. I have an eSATA drive, a 750GB Seagate in an eSATA external enclosure, and a Silicon Image sil3132 ExpressCard controller for my laptop. The disk and controller work great in CentOS 5 (or F7, for that matter), if I specifically mount it. This is not how I want to have to use this drive, however. I want to hotplug it; that is, plug the controller into the laptop, and then

...sing /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period 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) ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1: soft resetting port 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 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1: soft resetting port ata1....

https://bugs.freedesktop.org/show_bug.cgi?id=82843 Priority: medium Bug ID: 82843 Assignee: nouveau at lists.freedesktop.org Summary: [NV96][Regression][Bisected] Failure to resume QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: trevor.davenport

...em 0xfd1fc000 [ 15.051204] usb usb3: configuration #1 chosen from 1 choice [ 15.051228] hub 3-0:1.0: USB hub found [ 15.051236] hub 3-0:1.0: 3 ports detected [ 15.107086] usb 1-1: new full speed USB device using ohci_hcd and address 2 [ 15.119952] ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 15.151896] ata17.00: ATA-7: HITACHI HDS7250SASUN500G 0648KPU78F, K2AOAJ0A, max UDMA/133 [ 15.151898] ata17.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 15.151905] ata17.00: max_sectors limited to 256 for NCQ [ 15.153868] usb usb3: New USB device found, idVendor=1d6b, idP...

Hey all, Just downloaded the new Xen 4.0 and ran Make xen Make tools Make stubdom Copied the new files from dist/install Im already running pv_ops 2.6.31.6 kernel. When I boot i get (XEN) Panic on CPU 0: (XEN) IO-APIC + timer doesn''t work! I have tried booting with noapic boot option but makes no difference. The system worked fine on 3.4.2 CPU is AMD.

...[ 0.620698] PM: Hibernation image not present or could not be loaded. [ 0.620704] registered taskstats version 1 [ 0.621163] Magic number: 0:334:509 [ 0.621264] rtc_cmos 00:06: setting system clock to 2012-10-23 01:31:06 UTC (1350955866) [ 0.895249] ata6: SATA link down (SStatus 0 SControl 300) [ 0.895257] ata7: SATA link down (SStatus 0 SControl 300) [ 0.895282] ata3: SATA link down (SStatus 0 SControl 300) [ 0.895313] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 0.895338] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 0.895359] ata4: SATA link u...