All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@debian.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jason Cooper <jason@lakedaemon.net>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	linux-arm-kernel@lists.infradead.org, linux-ide@vger.kernel.org
Subject: Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
Date: Mon, 01 Jun 2015 12:14:03 +0100	[thread overview]
Message-ID: <1433157243.15036.116.camel@debian.org> (raw)
In-Reply-To: <20150601025050.GB11354@lunn.ch>

On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> On Sun, May 31, 2015 at 11:35:34AM +0100, Ian Campbell wrote:
> > Hi,
> > 
> > After updating to 4.0.4 (from the Debian kernel package) my TS-419 can
> > no longer see its SATA disks. In dmesg I see:
> > 
> > [    2.599060] SCSI subsystem initialized
> > [    2.662882] libata version 3.00 loaded.
> > [    2.664776] sata_mv 0000:01:00.0: version 1.28
> > [    2.664888] pci 0000:00:01.0: enabling device (0140 -> 0143)
> > [    2.687579] sata_mv: can't set global reset
> > [    2.691825] sata_mv 0000:01:00.0: Driver probe function unexpectedly returned 1
> > [    2.734954] sata_mv f1080000.sata: version 1.28
> > [    2.735222] sata_mv f1080000.sata: slots 32 ports 2
> > [    2.773358] scsi host0: sata_mv
> > [    2.785712] scsi host1: sata_mv
> > [    2.796204] ata1: SATA max UDMA/133 irq 35
> > [    2.800359] ata2: SATA max UDMA/133 irq 35
> > [    3.120986] ata1: SATA link down (SStatus 0 SControl F300)
> > [    3.444974] ata2: SATA link down (SStatus 0 SControl F300)
> > 
> > The last version I tried which worked was the 3.18.5 package.
> > 
> > This is using kirkwood-ts419-6281.dtb, which given this I think is the
> > correct one:
> > 
> > [    0.000000] Linux version 4.0.0-2-kirkwood (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-18) ) #1 Debian 4.0.4-1 (2015-05-26)
> > [    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
> > [    0.000000] CPU: VIVT data cache, VIVT instruction cache
> > [    0.000000] Machine model: QNAP TS419 family
> > [...]
> > [    0.044889] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
> > 
> > I can also see both PCI devices which IIRC is the main difference
> > between the 6281 and 6282.
> > 
> > I don't see anything in the git logs after 4.0 which looks like an
> > obviously related fix, but I'm currently building 4.1-rc5 to have a
> > check.
>  
> Hi Ian
> 
> You might also want to try 
> 
> http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> 
> In particular the first patch.

Thanks, I'll try those before I bother with a bisect.

Ian.



WARNING: multiple messages have this Message-ID (diff)
From: ijc@debian.org (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
Date: Mon, 01 Jun 2015 12:14:03 +0100	[thread overview]
Message-ID: <1433157243.15036.116.camel@debian.org> (raw)
In-Reply-To: <20150601025050.GB11354@lunn.ch>

On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> On Sun, May 31, 2015 at 11:35:34AM +0100, Ian Campbell wrote:
> > Hi,
> > 
> > After updating to 4.0.4 (from the Debian kernel package) my TS-419 can
> > no longer see its SATA disks. In dmesg I see:
> > 
> > [    2.599060] SCSI subsystem initialized
> > [    2.662882] libata version 3.00 loaded.
> > [    2.664776] sata_mv 0000:01:00.0: version 1.28
> > [    2.664888] pci 0000:00:01.0: enabling device (0140 -> 0143)
> > [    2.687579] sata_mv: can't set global reset
> > [    2.691825] sata_mv 0000:01:00.0: Driver probe function unexpectedly returned 1
> > [    2.734954] sata_mv f1080000.sata: version 1.28
> > [    2.735222] sata_mv f1080000.sata: slots 32 ports 2
> > [    2.773358] scsi host0: sata_mv
> > [    2.785712] scsi host1: sata_mv
> > [    2.796204] ata1: SATA max UDMA/133 irq 35
> > [    2.800359] ata2: SATA max UDMA/133 irq 35
> > [    3.120986] ata1: SATA link down (SStatus 0 SControl F300)
> > [    3.444974] ata2: SATA link down (SStatus 0 SControl F300)
> > 
> > The last version I tried which worked was the 3.18.5 package.
> > 
> > This is using kirkwood-ts419-6281.dtb, which given this I think is the
> > correct one:
> > 
> > [    0.000000] Linux version 4.0.0-2-kirkwood (debian-kernel at lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-18) ) #1 Debian 4.0.4-1 (2015-05-26)
> > [    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
> > [    0.000000] CPU: VIVT data cache, VIVT instruction cache
> > [    0.000000] Machine model: QNAP TS419 family
> > [...]
> > [    0.044889] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
> > 
> > I can also see both PCI devices which IIRC is the main difference
> > between the 6281 and 6282.
> > 
> > I don't see anything in the git logs after 4.0 which looks like an
> > obviously related fix, but I'm currently building 4.1-rc5 to have a
> > check.
>  
> Hi Ian
> 
> You might also want to try 
> 
> http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> 
> In particular the first patch.

Thanks, I'll try those before I bother with a bisect.

Ian.

  reply	other threads:[~2015-06-01 11:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 10:35 QNAP TS-419: sata_mv fails to initialise with "can't set global reset" Ian Campbell
2015-05-31 10:35 ` Ian Campbell
2015-05-31 18:54 ` Ian Campbell
2015-05-31 18:54   ` Ian Campbell
2015-06-01  2:37 ` Andrew Lunn
2015-06-01  2:37   ` Andrew Lunn
2015-06-01  2:50 ` Andrew Lunn
2015-06-01  2:50   ` Andrew Lunn
2015-06-01 11:14   ` Ian Campbell [this message]
2015-06-01 11:14     ` Ian Campbell
2015-06-01 21:07   ` Ian Campbell
2015-06-01 21:07     ` Ian Campbell
2015-06-01 21:07     ` Andrew Lunn
2015-06-01 21:07       ` Andrew Lunn
2015-06-02  7:14       ` Ian Campbell
2015-06-02  7:14         ` Ian Campbell
2015-06-02 13:38         ` Gregory CLEMENT
2015-06-02 13:38           ` Gregory CLEMENT

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=1433157243.15036.116.camel@debian.org \
    --to=ijc@debian.org \
    --cc=andrew@lunn.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.