From owner-freebsd-current@FreeBSD.ORG Mon Mar 6 23:52:02 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7803D16A423 for ; Mon, 6 Mar 2006 23:52:02 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id A808643D46 for ; Mon, 6 Mar 2006 23:52:01 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz [193.85.228.13]) by ss.eunet.cz (8.13.3/8.13.1) with ESMTP id k26NpxRj013907 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 7 Mar 2006 00:51:59 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: freebsd-current@freebsd.org Content-Type: text/plain Date: Tue, 07 Mar 2006 00:51:58 +0100 Message-Id: <1141689118.767.50.camel@genius.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: strange result of 'atacontrol cap adX' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2006 23:52:02 -0000 Hello, I've noticed on a couple of days old RELENG_6 that when I issue 'atacontrol cap ad4' there is a message 'ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire' printed to the console. I think that there shouldn't happen anything on ata0 channel when I query ata2 channel. It is probably completely harmless but what does it mean? This is a part of verbose dmesg on the machine with ATA attachments: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf000 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x01 err=0x01 lsb=0x01 msb=0x01 ata0: stat1=0x01 err=0x01 lsb=0x01 msb=0x01 ata0: reset tp2 stat0=01 stat1=01 devices=0x0 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 55 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x01 err=0x01 lsb=0x01 msb=0x01 ata1: stat1=0x01 err=0x01 lsb=0x01 msb=0x01 ata1: reset tp2 stat0=01 stat1=01 devices=0x0 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 56 ata1: [MPSAFE] atapci1: port 0xc000-0xc007,0xc400-0xc403,0xc800-0xc807,0xcc00-0xcc03,0xd000-0xd00f irq 18 at device 31.2 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd000 atapci1: [MPSAFE] ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xc000 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xc400 ata2: reset tp1 mask=01 ostat0=80 ostat1=00 ata2: stat0=0x80 err=0xff lsb=0xff msb=0xff ata2: stat0=0x80 err=0xff lsb=0xff msb=0xff ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xc800 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xcc00 ata3: reset tp1 mask=01 ostat0=80 ostat1=00 ata3: stat0=0x80 err=0xff lsb=0xff msb=0xff ata3: stat0=0x80 err=0xff lsb=0xff msb=0xff ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] Thank you for any insight and hope it's not a sign of a problem. Regards Michal Mertl