From: Pavel Mateja <pavel@netsafe.cz>
To: linux-ide@vger.kernel.org
Subject: Re: ALi SATA problem
Date: Wed, 18 Jul 2007 14:23:08 +0200 [thread overview]
Message-ID: <200707181423.08921.pavel@netsafe.cz> (raw)
In-Reply-To: <469DE14A.60101@gmail.com>
Dne Wednesday 18 of July 2007 11:45:46 jste napsal(a):
> Pavel Mateja wrote:
> > Dne Wednesday 18 of July 2007 11:35:00 jste napsal(a):
> >> Pavel Mateja wrote:
> >>> ata2: exception Emask 0x10 SAct 0x0 SErr 0x4060000 action 0x2 frozen
> >>> ata2: (irq_stat 0x00000040, connection status changed)
> >>> ata4: exception Emask 0x10 SAct 0x0 SErr 0x4060000 action 0x2 frozen
> >>> ata4: (irq_stat 0x00000040, connection status changed)
> >>> ata2: soft resetting port
> >>
> >> Please check power supply and re-cable things.
> >
> > Funny thing is there are no cables to be checked. Nothing is connected to
> > those ports. Just ata1 is occupied by disk.
>
> Sigh... The controller is telling the driver that "there's something
> going on this port (hotplug event), please take look". Can you try
> hotplug some device at those ports and report the resulting kernel log?
Hotplug was working in cca 1 of 8 attemps.
ata4: soft resetting port
ata4: SATA link down (SStatus 1 SControl 300)
ata4: EH complete
ata4: exception Emask 0x10 SAct 0x0 SErr 0x4060000 action 0x2 frozen
ata4: (irq_stat 0x00000040, connection status changed)
ata2: exception Emask 0x10 SAct 0x0 SErr 0x4060000 action 0x2 frozen
ata2: (irq_stat 0x00000040, connection status changed)
ata4: soft resetting port
ata2: soft resetting port
ata2: SATA link down (SStatus 1 SControl 300)
ata2: EH complete
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATA-6: ST3120026AS, 8.05, max UDMA/133
ata4.00: 234375000 sectors, multi 0: LBA48
ata4.00: configured for UDMA/133
ata4: EH complete
Device driver target3:0:0 lacks bus and class support for being resumed.
scsi 3:0:0:0: Direct-Access ATA ST3120026AS 8.05 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdb] 234375000 512-byte hardware sectors (120000 MB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 3:0:0:0: [sdb] 234375000 512-byte hardware sectors (120000 MB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sdb: sdb1
sd 3:0:0:0: [sdb] Attached SCSI disk
--
Pavel Mateja
next prev parent reply other threads:[~2007-07-18 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 9:17 ALi SATA problem Pavel Mateja
2007-07-18 9:35 ` Tejun Heo
2007-07-18 9:38 ` Pavel Mateja
2007-07-18 9:45 ` Tejun Heo
2007-07-18 12:23 ` Pavel Mateja [this message]
2007-07-19 8:01 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707181423.08921.pavel@netsafe.cz \
--to=pavel@netsafe.cz \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).