search for: ata6

...0-0xd3001fff irq 22 at device 8.0 on pci0 ata4: <ATA channel 0> on atapci2 ata5: <ATA channel 1> on atapci2 atapci3: <SiI SiI 3114 SATA150 controller> port 0x9000-0x9007,0x9400-0x9403,0x9800-0x9807,0x9c00-0x9c03,0xa000-0xa00f mem 0xd2000000-0xd20003ff irq 19 at device 10.0 on pci5 ata6: <ATA channel 0> on atapci3 ata7: <ATA channel 1> on atapci3 ata8: <ATA channel 2> on atapci3 ata9: <ATA channel 3> on atapci3 Also, there are lines of the form "ata0: [ITHREAD]" for all of ata0, ata1, atapci1, ata2, ata3, atapci2, ata4, ata5, atapci3, ata6, ata7,...

...procedure I can follow / patch I could apply to salvage my data while ignoring media errors ? logs/OOPS at the end of this mail, please let me know if more information is needed, Best regards, Vincent ----------------------------------------------------------------------- [ 129.241636] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 129.241640] ata6.00: BMDMA stat 0x24 [ 129.241643] ata6.00: failed command: READ DMA EXT [ 129.241649] ata6.00: cmd 25/00:08:5f:dc:2f/00:00:70:00:00/e0 tag 0 dma 4096 in [ 129.241651] res 51/40:00:61:dc:2f/40:00...

...xa2439180 irq 136 [??? 1.433226] ata3: SATA max UDMA/133 abar m2048 at 0xa2439000 port 0xa2439200 irq 136 [??? 1.433238] ata4: SATA max UDMA/133 abar m2048 at 0xa2439000 port 0xa2439280 irq 136 [??? 1.433250] ata5: SATA max UDMA/133 abar m2048 at 0xa2439000 port 0xa2439300 irq 136 [??? 1.433262] ata6: SATA max UDMA/133 abar m2048 at 0xa2439000 port 0xa2439380 irq 136 [??? 1.438562] i915 0000:00:02.0: irq 137 for MSI/MSI-X [??? 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X [??? 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X [??? 1.720568] ixgbe 0000:01:00.0: irq 140 for MSI/MSI-X [??...

...sauron kernel: ata3: SATA max UDMA/133 cmd 0xF8874200 ctl 0x0 bmdma 0x0 irq 58 Jul 26 16:29:27 sauron kernel: ata4: SATA max UDMA/133 cmd 0xF8874280 ctl 0x0 bmdma 0x0 irq 58 Jul 26 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 t...

...3226] ata3: SATA max UDMA/133 abar m2048 at 0xa2439000 port > 0xa2439200 irq 136 > [ 1.433238] ata4: SATA max UDMA/133 abar m2048 at 0xa2439000 port > 0xa2439280 irq 136 > [ 1.433250] ata5: SATA max UDMA/133 abar m2048 at 0xa2439000 port > 0xa2439300 irq 136 > [ 1.433262] ata6: SATA max UDMA/133 abar m2048 at 0xa2439000 port > 0xa2439380 irq 136 > [ 1.438562] i915 0000:00:02.0: irq 137 for MSI/MSI-X > [ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X > [ 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X > [ 1.720568] ixgbe 0000:01:00.0: i...

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''m not sure exactly what happened with my box here, but something caused a hiccup on multiple sata disks... May 9 16:40:33 sol scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci10de,5c at 9/pci-ide at a/ide at 0 (ata6): May 9 16:47:43 sol scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci-ide at 7/ide at 1 (ata3): May 9 16:47:43 sol timeout: abort request, target=0 lun=0 May 9 16:47:43 sol scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci-ide at 7/ide at 1 (ata3): May 9 16:40:33 sol scsi: [ID...

...ormal status 0x7F on port 0xB487 ACPI: PCI Interrupt Link [LSA2] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:05.2[C] -> Link [LSA2] -> GSI 23 (level, low) -> IRQ 233 PCI: Setting latency timer of device 0000:00:05.2 to 64 ata5: SATA max UDMA/133 cmd 0xB000 ctl 0xAC02 bmdma 0xA480 irq 233 ata6: SATA max UDMA/133 cmd 0xA880 ctl 0xA802 bmdma 0xA488 irq 233 scsi4 : sata_nv ata5: SATA link down (SStatus 0 SControl 300) ATA: abnormal status 0x7F on port 0xB007 scsi5 : sata_nv ata6: SATA link down (SStatus 0 SControl 300) ATA: abnormal status 0x7F on port 0xA887 md: Autodetecting RAID arrays....

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:

I have brand new PC with this components: CPU Intel? Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1) When I restart the machine sometimes enp1s0 is missing. It is not

On my C5 machine (a Dell XPS420) I have a 500Gb disk on the internal SATA controller. I also have a SiI3132 dual-port multi-device eSATA card. This is connected to an external SATA array of disks. Now occasionally I see something like this in my logs ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x0 ata7.01: irq_stat 0x00060002, device error via D 2H FIS ata7.01: cmd

...offsitetmp# Drives are raidz ad1: 1430799MB <Seagate ST31500341AS CC1H> at ata3-master SATA300 ad2: 1430799MB <Seagate ST31500341AS CC1H> at ata4-master SATA300 ad3: 1430799MB <Seagate ST31500341AS CC1H> at ata5-master SATA300 ad4: 1430799MB <Seagate ST31500341AS CC1H> at ata6-master SATA300 on ich9 ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994...

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

...atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 6 ports detected ata2: <ATA channel 0> on atapci1 ata2: [ITHREAD] ata3: <ATA channel 1> on atapci1 ata3: [ITHREAD] ata4: <ATA channel 2> on atapci1 ata4: [ITHREAD] ata5: <ATA channel 3> on atapci1 ata5: [ITHREAD] ata6: <ATA channel 4> on atapci1 ata6: [ITHREAD] ata7: <ATA channel 5> on atapci1 ata7: [ITHREAD] ichsmb0: <Intel 631xESB/6321ESB (ESB2) SMBus controller> port 0x1100-0x111f irq 19 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] smbus0: <System Management Bus> o...

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

I just installed centos 5.5 x86_64 on a new HP laptop. It has the core i5 processor. only 1 cpu is detected should be 2. This has happened before. Is upstream not keeping up with new processors released and updating the kernel? I'd rather not go through the process again of putting a newer kernel on the machine and having something different out there than "stock" centos. Jerry

Hi, Doing some extensive benchmarks on BTRFS, I encountered a kernel bug in BTRFS (as reported in dmesg) Maybe the information below can help you making btrfs better. Situation Doing an intensive sequential write on a SAS 3TB disk drive (SEAGATE ST33000652SS) with 128 threads with Sysbench. Device is connected through an HBA. Blocksize was 256k ; Kernel is 3.3.0 (x86_64) ; Btrfs is version

...UDMA/133 abar m2048 at 0xdb325000 port 0xdb325100 irq 29 [ 1.553067] ata2: SATA max UDMA/133 abar m2048 at 0xdb325000 port 0xdb325180 irq 29 [ 1.553068] ata3: DUMMY [ 1.553070] ata4: DUMMY [ 1.553073] ata5: SATA max UDMA/133 abar m2048 at 0xdb325000 port 0xdb325300 irq 29 [ 1.553076] ata6: SATA max UDMA/133 abar m2048 at 0xdb325000 port 0xdb325380 irq 29 [ 1.553513] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 1.590043] firewire_ohci 0000:86:06.0: added OHCI v1.10 device as card 0, 4 IR + 4 IT contexts, quirks 0x11 [ 1.678230]...

...csi2 : ahci scsi3 : ahci scsi4 : ahci scsi5 : ahci ata1: SATA max UDMA/133 irq_stat 0x00000040, connection status changed irq 18 ata2: SATA max UDMA/133 irq_stat 0x00000040, connection status changed irq 18 ata3: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970200 irq 18 ata4: DUMMY ata5: DUMMY ata6: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970380 irq 18 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-6: WDC WD360GD-00FLA2, 31.08F31, max UDMA/133 ata1.00: 72303840 sectors, multi 0: LBA48 ata1.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA WDC W...

...gt; 0xdb325100 irq 29 > [ 1.553067] ata2: SATA max UDMA/133 abar m2048 at 0xdb325000 port > 0xdb325180 irq 29 > [ 1.553068] ata3: DUMMY > [ 1.553070] ata4: DUMMY > [ 1.553073] ata5: SATA max UDMA/133 abar m2048 at 0xdb325000 port > 0xdb325300 irq 29 > [ 1.553076] ata6: SATA max UDMA/133 abar m2048 at 0xdb325000 port > 0xdb325380 irq 29 > [ 1.553513] e1000e 0000:00:19.0: Interrupt Throttling Rate > (ints/sec) set to dynamic conservative mode > [ 1.590043] firewire_ohci 0000:86:06.0: added OHCI v1.10 device as > card 0, 4 IR + 4 IT contexts, q...