[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrVBTWvvJvziAoDzdUyC10jSKHmx38qyNXxJKVVpaB+7Pg@mail.gmail.com>
Date: Thu, 30 Aug 2012 09:57:48 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Jan Engelhardt <jengelh@...i.de>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-ide@...r.kernel.org, Bjoern Franke <bjo@...d-west.org>,
Borislav Petkov <bp@...en8.de>,
Tim Nufire <linux_ide_tim@...nk.com>
Subject: Re: Which disk is ata4?
On Thu, Aug 30, 2012 at 9:14 AM, Jan Engelhardt <jengelh@...i.de> wrote:
> On Thursday 2012-08-30 06:38, Andy Lutomirski wrote:
>
>>One of my disks went out to lunch for a while. Logs below.
>>
>>[784786.047673] ata4.00: exception Emask 0x10 SAct 0x7800 SErr 0x0
>>action 0x6 frozen
>>
>>Which one is it? The only useful thing in /sys/class/ata_port/ata4 is
>>the device symlink, which points at
>>/sys/devices/pci0000:00/0000:00:1f.2/ata4.
>
> For example, ata2 here:
>
> $ cd /sys/devices
> $ find . -name ata2
> ./pci0000:00/0000:00:1f.2/ata2
> ./pci0000:00/0000:00:1f.2/ata2/ata_port/ata2
> $ cd ./pci0000:00/0000:00:1f.2/ata2
> $ ls -dl host*/targ*
> drwxr-xr-x 4 root root 0 Aug 30 18:09 host1/target1:0:0
Aha! This works on 3.5 but not on 3.2. Mystery solved (except on my
poor Ubuntu LTS box that has the host directories under the pci device
instead of under the ata devices).
Consider this report solved by "fixed in newer kernel". I thought I
had checked for that.
It would be nice if the dmesg startup logs showed the serial number
along with the model number.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists