All of lore.kernel.org
 help / color / mirror / Atom feed
* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-05-31 10:35 ` Ian Campbell
  0 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-05-31 10:35 UTC (permalink / raw)
  To: Jason Cooper, Andrew Lunn, Gregory Clement, Sebastian Hesselbarth
  Cc: linux-ide, linux-arm-kernel

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.

Ian.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-05-31 10:35 ` Ian Campbell
  0 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-05-31 10:35 UTC (permalink / raw)
  To: linux-arm-kernel

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.

Ian.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-05-31 10:35 ` Ian Campbell
@ 2015-05-31 18:54   ` Ian Campbell
  -1 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-05-31 18:54 UTC (permalink / raw)
  To: Jason Cooper
  Cc: Andrew Lunn, Gregory Clement, Sebastian Hesselbarth,
	linux-arm-kernel, linux-ide

On Sun, 2015-05-31 at 11:35 +0100, Ian Campbell wrote:
> Hi,
> 
> After updating to 4.0.4 (from the Debian kernel package)

FYI 4.1-rc5 behaves the same.

>  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.
> 
> Ian.



^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-05-31 18:54   ` Ian Campbell
  0 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-05-31 18:54 UTC (permalink / raw)
  To: linux-arm-kernel

On Sun, 2015-05-31 at 11:35 +0100, Ian Campbell wrote:
> Hi,
> 
> After updating to 4.0.4 (from the Debian kernel package)

FYI 4.1-rc5 behaves the same.

>  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.
> 
> Ian.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-05-31 10:35 ` Ian Campbell
@ 2015-06-01  2:37   ` Andrew Lunn
  -1 siblings, 0 replies; 18+ messages in thread
From: Andrew Lunn @ 2015-06-01  2:37 UTC (permalink / raw)
  To: Ian Campbell
  Cc: Jason Cooper, Gregory Clement, Sebastian Hesselbarth, linux-ide,
	linux-arm-kernel

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

I just booted my QNAP TS-119P, and it found its disk. No message about
missing reset.

Since TS-419 is a four driver device, it does not use the internal
SATA controllers for its disks, it uses a PCI controller. So i think
this is somehow PCI related.

Can you do a bissect?

    Andrew

^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-06-01  2:37   ` Andrew Lunn
  0 siblings, 0 replies; 18+ messages in thread
From: Andrew Lunn @ 2015-06-01  2:37 UTC (permalink / raw)
  To: linux-arm-kernel

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

I just booted my QNAP TS-119P, and it found its disk. No message about
missing reset.

Since TS-419 is a four driver device, it does not use the internal
SATA controllers for its disks, it uses a PCI controller. So i think
this is somehow PCI related.

Can you do a bissect?

    Andrew

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-05-31 10:35 ` Ian Campbell
@ 2015-06-01  2:50   ` Andrew Lunn
  -1 siblings, 0 replies; 18+ messages in thread
From: Andrew Lunn @ 2015-06-01  2:50 UTC (permalink / raw)
  To: Ian Campbell
  Cc: Jason Cooper, Gregory Clement, Sebastian Hesselbarth,
	linux-arm-kernel, linux-ide

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.

  Andrew

^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-06-01  2:50   ` Andrew Lunn
  0 siblings, 0 replies; 18+ messages in thread
From: Andrew Lunn @ 2015-06-01  2:50 UTC (permalink / raw)
  To: linux-arm-kernel

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.

  Andrew

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-06-01  2:50   ` Andrew Lunn
@ 2015-06-01 11:14     ` Ian Campbell
  -1 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-06-01 11:14 UTC (permalink / raw)
  To: Andrew Lunn
  Cc: Jason Cooper, Gregory Clement, Sebastian Hesselbarth,
	linux-arm-kernel, linux-ide

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.



^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-06-01 11:14     ` Ian Campbell
  0 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-06-01 11:14 UTC (permalink / raw)
  To: linux-arm-kernel

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.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-06-01 21:07     ` Ian Campbell
@ 2015-06-01 21:07       ` Andrew Lunn
  -1 siblings, 0 replies; 18+ messages in thread
From: Andrew Lunn @ 2015-06-01 21:07 UTC (permalink / raw)
  To: Ian Campbell
  Cc: Jason Cooper, Gregory Clement, Sebastian Hesselbarth,
	linux-arm-kernel, linux-ide

On Mon, Jun 01, 2015 at 10:07:37PM +0100, Ian Campbell wrote:
> On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> > You might also want to try 
> > 
> > http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> > 
> > In particular the first patch.
> 
> That did the trick, thanks!

Great.

A tested-by: for that patch will help grease the path into the kernel.

Thanks
	Andrew

^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-06-01 21:07       ` Andrew Lunn
  0 siblings, 0 replies; 18+ messages in thread
From: Andrew Lunn @ 2015-06-01 21:07 UTC (permalink / raw)
  To: linux-arm-kernel

On Mon, Jun 01, 2015 at 10:07:37PM +0100, Ian Campbell wrote:
> On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> > You might also want to try 
> > 
> > http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> > 
> > In particular the first patch.
> 
> That did the trick, thanks!

Great.

A tested-by: for that patch will help grease the path into the kernel.

Thanks
	Andrew

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-06-01  2:50   ` Andrew Lunn
@ 2015-06-01 21:07     ` Ian Campbell
  -1 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-06-01 21:07 UTC (permalink / raw)
  To: Andrew Lunn
  Cc: Jason Cooper, Gregory Clement, Sebastian Hesselbarth,
	linux-arm-kernel, linux-ide

On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> You might also want to try 
> 
> http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> 
> In particular the first patch.

That did the trick, thanks!

Ian.



^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-06-01 21:07     ` Ian Campbell
  0 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-06-01 21:07 UTC (permalink / raw)
  To: linux-arm-kernel

On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> You might also want to try 
> 
> http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> 
> In particular the first patch.

That did the trick, thanks!

Ian.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-06-01 21:07       ` Andrew Lunn
@ 2015-06-02  7:14         ` Ian Campbell
  -1 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-06-02  7:14 UTC (permalink / raw)
  To: Andrew Lunn
  Cc: Jason Cooper, Gregory Clement, Sebastian Hesselbarth,
	linux-arm-kernel, linux-ide

On Mon, 2015-06-01 at 23:07 +0200, Andrew Lunn wrote:
> On Mon, Jun 01, 2015 at 10:07:37PM +0100, Ian Campbell wrote:
> > On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> > > You might also want to try 
> > > 
> > > http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> > > 
> > > In particular the first patch.
> > 
> > That did the trick, thanks!
> 
> Great.
> 
> A tested-by: for that patch will help grease the path into the kernel.

I think it's already been applied to Gregory's tree, but I replied with
a T-b anyway.

Thanks again,
Ian.


^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-06-02  7:14         ` Ian Campbell
  0 siblings, 0 replies; 18+ messages in thread
From: Ian Campbell @ 2015-06-02  7:14 UTC (permalink / raw)
  To: linux-arm-kernel

On Mon, 2015-06-01 at 23:07 +0200, Andrew Lunn wrote:
> On Mon, Jun 01, 2015 at 10:07:37PM +0100, Ian Campbell wrote:
> > On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
> > > You might also want to try 
> > > 
> > > http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
> > > 
> > > In particular the first patch.
> > 
> > That did the trick, thanks!
> 
> Great.
> 
> A tested-by: for that patch will help grease the path into the kernel.

I think it's already been applied to Gregory's tree, but I replied with
a T-b anyway.

Thanks again,
Ian.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
  2015-06-02  7:14         ` Ian Campbell
@ 2015-06-02 13:38           ` Gregory CLEMENT
  -1 siblings, 0 replies; 18+ messages in thread
From: Gregory CLEMENT @ 2015-06-02 13:38 UTC (permalink / raw)
  To: Ian Campbell, Andrew Lunn
  Cc: Jason Cooper, Sebastian Hesselbarth, linux-arm-kernel, linux-ide

On 02/06/2015 09:14, Ian Campbell wrote:
> On Mon, 2015-06-01 at 23:07 +0200, Andrew Lunn wrote:
>> On Mon, Jun 01, 2015 at 10:07:37PM +0100, Ian Campbell wrote:
>>> On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
>>>> You might also want to try 
>>>>
>>>> http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
>>>>
>>>> In particular the first patch.
>>>
>>> That did the trick, thanks!
>>
>> Great.
>>
>> A tested-by: for that patch will help grease the path into the kernel.
> 
> I think it's already been applied to Gregory's tree, but I replied with
> a T-b anyway.

Yes and it was already pull in the arm-soc tree.

However thanks for testing it.

Gregory

> 
> Thanks again,
> Ian.
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

^ permalink raw reply	[flat|nested] 18+ messages in thread

* QNAP TS-419: sata_mv fails to initialise with "can't set global reset"
@ 2015-06-02 13:38           ` Gregory CLEMENT
  0 siblings, 0 replies; 18+ messages in thread
From: Gregory CLEMENT @ 2015-06-02 13:38 UTC (permalink / raw)
  To: linux-arm-kernel

On 02/06/2015 09:14, Ian Campbell wrote:
> On Mon, 2015-06-01 at 23:07 +0200, Andrew Lunn wrote:
>> On Mon, Jun 01, 2015 at 10:07:37PM +0100, Ian Campbell wrote:
>>> On Mon, 2015-06-01 at 04:50 +0200, Andrew Lunn wrote:
>>>> You might also want to try 
>>>>
>>>> http://comments.gmane.org/gmane.linux.ports.arm.kernel/416589
>>>>
>>>> In particular the first patch.
>>>
>>> That did the trick, thanks!
>>
>> Great.
>>
>> A tested-by: for that patch will help grease the path into the kernel.
> 
> I think it's already been applied to Gregory's tree, but I replied with
> a T-b anyway.

Yes and it was already pull in the arm-soc tree.

However thanks for testing it.

Gregory

> 
> Thanks again,
> Ian.
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

^ permalink raw reply	[flat|nested] 18+ messages in thread

end of thread, other threads:[~2015-06-02 13:38 UTC | newest]

Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

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.