Re: Keystone 2 boards boot failure

2016-02-08 Thread Arnd Bergmann
On Friday 05 February 2016 19:11:06 Grygorii Strashko wrote: > On 02/05/2016 06:18 PM, Arnd Bergmann wrote: > > On Thursday 04 February 2016 18:25:08 Grygorii Strashko wrote: > > @@ -1173,7 +1189,8 @@ static int netcp_tx_submit_skb(struct netcp_intf > > *netcp, > > } > > > > set_words(

Re: Keystone 2 boards boot failure

2016-02-05 Thread Murali Karicheri
On 02/03/2016 03:13 PM, santosh shilimkar wrote: > On 2/3/2016 10:47 AM, Murali Karicheri wrote: >> On 02/03/2016 12:08 PM, santosh shilimkar wrote: >>> On 2/3/2016 8:35 AM, Arnd Bergmann wrote: > > [..] > It would be nice to give this a go once the network driver problem is solved. >>>

Re: Keystone 2 boards boot failure

2016-02-05 Thread Grygorii Strashko
hi Arnd, On 02/05/2016 06:18 PM, Arnd Bergmann wrote: > On Thursday 04 February 2016 18:25:08 Grygorii Strashko wrote: >>> >>> I have another version for testing below. That removes the logic that >>> splits and reassembles the 64-bit values, but leaves the other changes >>> in place. Can you try

Re: Keystone 2 boards boot failure

2016-02-05 Thread Arnd Bergmann
On Thursday 04 February 2016 18:25:08 Grygorii Strashko wrote: > > > > I have another version for testing below. That removes the logic that > > splits and reassembles the 64-bit values, but leaves the other changes > > in place. Can you try this? > > > > Nop. It crashes kernel Ah. too bad. >

Re: Keystone 2 boards boot failure

2016-02-04 Thread Grygorii Strashko
On 02/04/2016 03:07 PM, Arnd Bergmann wrote: > On Thursday 04 February 2016 14:19:54 Grygorii Strashko wrote: >> On 02/03/2016 10:40 PM, Arnd Bergmann wrote: >>> On Wednesday 03 February 2016 18:31:00 Grygorii Strashko wrote: On 02/03/2016 06:20 PM, Arnd Bergmann wrote: > On Wednesday 03 F

Re: Keystone 2 boards boot failure

2016-02-04 Thread Grygorii Strashko
On 02/03/2016 06:20 PM, Arnd Bergmann wrote: > On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: >> On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: >>> On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: > So only making this change on the latest master with no oth

Re: Keystone 2 boards boot failure

2016-02-04 Thread Arnd Bergmann
On Thursday 04 February 2016 14:19:54 Grygorii Strashko wrote: > On 02/03/2016 10:40 PM, Arnd Bergmann wrote: > > On Wednesday 03 February 2016 18:31:00 Grygorii Strashko wrote: > >> On 02/03/2016 06:20 PM, Arnd Bergmann wrote: > >>> On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: >

Re: Keystone 2 boards boot failure

2016-02-04 Thread Grygorii Strashko
Hi Arnd, On 02/03/2016 10:40 PM, Arnd Bergmann wrote: > On Wednesday 03 February 2016 18:31:00 Grygorii Strashko wrote: >> On 02/03/2016 06:20 PM, Arnd Bergmann wrote: >>> On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote:

Re: Keystone 2 boards boot failure

2016-02-03 Thread Arnd Bergmann
On Wednesday 03 February 2016 11:41:40 Murali Karicheri wrote: > > > > This looks wrong: I was getting the build warnings originally > > because of 64-bit dma_addr_t, and that should be the only way that > > this driver can operate, because in some configurations on keystone > > there is no memory

Re: Keystone 2 boards boot failure

2016-02-03 Thread Arnd Bergmann
On Wednesday 03 February 2016 18:31:00 Grygorii Strashko wrote: > On 02/03/2016 06:20 PM, Arnd Bergmann wrote: > > On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: > >> On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: > >>> On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: > >

Re: Keystone 2 boards boot failure

2016-02-03 Thread santosh shilimkar
On 2/3/2016 10:47 AM, Murali Karicheri wrote: On 02/03/2016 12:08 PM, santosh shilimkar wrote: On 2/3/2016 8:35 AM, Arnd Bergmann wrote: [..] It would be nice to give this a go once the network driver problem is solved. Big endian kernel has worked on Keystone in past. Yes, this was on a

Re: Keystone 2 boards boot failure

2016-02-03 Thread Murali Karicheri
On 02/03/2016 12:08 PM, santosh shilimkar wrote: > On 2/3/2016 8:35 AM, Arnd Bergmann wrote: >> On Tuesday 02 February 2016 19:19:13 Franklin S Cooper Jr. wrote: >>> On 02/02/2016 05:26 PM, Arnd Bergmann wrote: On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: > On 02/02/2016 03:

Re: Keystone 2 boards boot failure

2016-02-03 Thread santosh shilimkar
On 2/3/2016 8:35 AM, Arnd Bergmann wrote: On Tuesday 02 February 2016 19:19:13 Franklin S Cooper Jr. wrote: On 02/02/2016 05:26 PM, Arnd Bergmann wrote: On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: On 02/02/2016 03:26 PM, Arnd Bergmann wrote: On Tuesday 02 February 2016 15:01:3

Re: Keystone 2 boards boot failure

2016-02-03 Thread Murali Karicheri
On 02/03/2016 11:31 AM, Grygorii Strashko wrote: > On 02/03/2016 06:20 PM, Arnd Bergmann wrote: >> On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: >>> On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: >> > So only

Re: Keystone 2 boards boot failure

2016-02-03 Thread Murali Karicheri
On 02/03/2016 11:20 AM, Arnd Bergmann wrote: > On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: >> On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: >>> On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: > So only making this change on the latest master with no oth

Re: Keystone 2 boards boot failure

2016-02-03 Thread Arnd Bergmann
On Tuesday 02 February 2016 19:19:13 Franklin S Cooper Jr. wrote: > On 02/02/2016 05:26 PM, Arnd Bergmann wrote: > > On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: > >> On 02/02/2016 03:26 PM, Arnd Bergmann wrote: > >>> On Tuesday 02 February 2016 15:01:33 Franklin S Cooper Jr. wrote:

Re: Keystone 2 boards boot failure

2016-02-03 Thread Grygorii Strashko
On 02/03/2016 06:20 PM, Arnd Bergmann wrote: On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: So only making this change on the latest master with no other changes I see t

Re: Keystone 2 boards boot failure

2016-02-03 Thread Arnd Bergmann
On Wednesday 03 February 2016 16:21:05 Grygorii Strashko wrote: > On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: > > On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: > >>> > >> So only making this change on the latest master with no > >> other changes I see the boot problem again. > > ye

Re: Keystone 2 boards boot failure

2016-02-03 Thread Franklin S Cooper Jr.
On 02/03/2016 08:21 AM, Grygorii Strashko wrote: > Hi Arnd, > > On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: >> On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: >>> On 02/02/2016 05:26 PM, Arnd Bergmann wrote: On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: > On 0

Re: Keystone 2 boards boot failure

2016-02-03 Thread Grygorii Strashko
Hi Arnd, On 02/03/2016 04:11 PM, Franklin S Cooper Jr. wrote: > On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: >> >> On 02/02/2016 05:26 PM, Arnd Bergmann wrote: >>> On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: On 02/02/2016 03:26 PM, Arnd Bergmann wrote: > On Tuesday

Re: Keystone 2 boards boot failure

2016-02-03 Thread Franklin S Cooper Jr.
On 02/02/2016 07:19 PM, Franklin S Cooper Jr. wrote: > > On 02/02/2016 05:26 PM, Arnd Bergmann wrote: >> On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: >>> On 02/02/2016 03:26 PM, Arnd Bergmann wrote: On Tuesday 02 February 2016 15:01:33 Franklin S Cooper Jr. wrote: > Yes. He

Re: Keystone 2 boards boot failure

2016-02-02 Thread Franklin S Cooper Jr.
On 02/02/2016 05:26 PM, Arnd Bergmann wrote: > On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: >> On 02/02/2016 03:26 PM, Arnd Bergmann wrote: >>> On Tuesday 02 February 2016 15:01:33 Franklin S Cooper Jr. wrote: Yes. Here is a boot log on the latest master with the below th

Re: Keystone 2 boards boot failure

2016-02-02 Thread Arnd Bergmann
On Tuesday 02 February 2016 16:59:34 Franklin Cooper wrote: > On 02/02/2016 03:26 PM, Arnd Bergmann wrote: > > On Tuesday 02 February 2016 15:01:33 Franklin S Cooper Jr. wrote: > >> > >> Yes. Here is a boot log on the latest master with the below > >> three patches reverted. > >> http://pastebin.co

Re: Keystone 2 boards boot failure

2016-02-02 Thread Franklin Cooper
On 02/02/2016 03:26 PM, Arnd Bergmann wrote: > On Tuesday 02 February 2016 15:01:33 Franklin S Cooper Jr. wrote: >> >> Yes. Here is a boot log on the latest master with the below >> three patches reverted. >> http://pastebin.com/W7RWSHpE (Working) >> >> I reverted these three patches. The two lates

Re: Keystone 2 boards boot failure

2016-02-02 Thread Arnd Bergmann
On Tuesday 02 February 2016 15:01:33 Franklin S Cooper Jr. wrote: > > Yes. Here is a boot log on the latest master with the below > three patches reverted. > http://pastebin.com/W7RWSHpE (Working) > > I reverted these three patches. The two latest patches seem > to be trying to correct/expand upo

Re: Keystone 2 boards boot failure

2016-02-02 Thread Franklin S Cooper Jr.
On 02/02/2016 02:41 PM, Arnd Bergmann wrote: > On Tuesday 02 February 2016 10:50:41 Franklin S Cooper Jr. wrote: >> Latest mainline is currently failing to boot for Keystone 2 >> Hawking but I'm assuming its true for other Keystone 2 >> boards. Bisect shows that this issue popped up after the >>

Re: Keystone 2 boards boot failure

2016-02-02 Thread Arnd Bergmann
On Tuesday 02 February 2016 10:50:41 Franklin S Cooper Jr. wrote: > Latest mainline is currently failing to boot for Keystone 2 > Hawking but I'm assuming its true for other Keystone 2 > boards. Bisect shows that this issue popped up after the > patch "netcp: try to reduce type confusion in descrip

Keystone 2 boards boot failure

2016-02-02 Thread Franklin S Cooper Jr.
Hi All, Latest mainline is currently failing to boot for Keystone 2 Hawking but I'm assuming its true for other Keystone 2 boards. Bisect shows that this issue popped up after the patch "netcp: try to reduce type confusion in descriptors" (commit 89907779) was introduced. There was another patch "