What does the 6 or 6:00 correspond to? It doesn't appear to be a major
or minor device number, or correspond to any entries in /sys that I can
find. If the 6 is not the device (but rather the driver version or
something), is there any part of these messages that indicate which
device is
Chris Tyler wrote:
What does the 6 or 6:00 correspond to? It doesn't appear to be a major
or minor device number, or correspond to any entries in /sys that I can
find. If the 6 is not the device (but rather the driver version or
something), is there any part of these messages that indicate
On Sun, 2009-11-08 at 09:17 +, Andy Campbell wrote:
What does the 6 or 6:00 correspond to? It doesn't appear to be a major
or minor device number, or correspond to any entries in /sys that I can
find. If the 6 is not the device (but rather the driver version or
something), is there any
On 11/08/2009 06:20 AM, Chris Tyler wrote:
On Sun, 2009-11-08 at 09:17 +, Andy Campbell wrote:
What does the 6 or 6:00 correspond to? It doesn't appear to be a major
or minor device number, or correspond to any entries in /sys that I can
find. If the 6 is not the device (but rather the
On Sun, Nov 8, 2009 at 10:25 AM, john wendel jwende...@comcast.net wrote:
Sorry I don't know the exact answer, but I'll bet that you find it by poking
around in /sys.
I'll bet that he'd find it by actually bothering to read his dmesg
like he was told to, since all the devices the kernel found
I'm getting tons of messages in /var/log/messages about 'ata6' or
'ata6:00':
Nov 7 11:16:21 concord3 kernel: ata6.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x6 frozen
Nov 7 11:16:21 concord3 kernel: ata6.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Nov 7 11:16:21 concord3 kernel:
