linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ivo.g.dimitrov.75@gmail.com (Ivaylo Dimitrov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] memory: omap-gpmc: Add Kconfig option for debug
Date: Fri, 8 Jan 2016 07:13:58 +0200	[thread overview]
Message-ID: <568F4596.8020206@gmail.com> (raw)
In-Reply-To: <20160108022619.GS12777@atomide.com>

Hi

On  8.01.2016 04:26, Tony Lindgren wrote:
>
> Yes it seems there's some other issue too. Maybe you can run git bisect
> again and carry the fix along as an extra patch?
>

No sane way to bisect, I don't really know what triggers the issue. 
Neither it is triggered regularly. It might happen on the first reboot 
or on the tenth, or ... And it looks like the problems happens sometimes 
on oops too. Not to say that it seems I should have fully booted 
userspace (so there is enough pressure on the ubi/mdt/nand subsystems), 
which is impossible with upstream without some n900 specific patches :(

Maybe we can get some ideas on what and where to look from ubifs people? 
Though I don't know whom to cc, feel free to help :)

My best bet aiui, is comparing what nokia omap1 kernel does vs upstream. 
Or looking at the commit log in ubi/mtd/onenand - who knows, I might get 
lucky once again the same way as with that phonet oops in 
__netif_receive_skb_core.

>
> OK then it really seems like we do have another bug lurking around.

:nod:

> Maybe you can figure out an easier way to reproduce it?
>

I doubt, but who knows.

>> The problem is that between NOLO and kernel there is u-boot. And even if I
>> am almost sure it doesn't touch onenand configs, I can't be absolutely sure.
>> So those timings are not 100% reliable IMO, though close to that.
>
> Hmm yes I'm only booting with u-boot here as my device sits in my rack.
>

I booted the device via flasher with initrd from the so-called rescueos 
(https://n900.quitesimple.org/rescueOS/rescueOS-1.2/) - it provides 
shell with tons of useful tools if your device is in bootloop etc. CS0 
registers were the same as with u-boot, so it is not that one.

>
> OK will push it out then.
>

Thanks,
Ivo

  reply	other threads:[~2016-01-08  5:13 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 21:21 [PATCH 0/2] omap gpmc changes for parsing devices and working debug Tony Lindgren
2015-05-20 21:21 ` [PATCH 1/2] memory: omap-gpmc: Fix parsing of devices Tony Lindgren
2015-05-20 21:21 ` [PATCH 2/2] memory: omap-gpmc: Add Kconfig option for debug Tony Lindgren
2015-05-20 22:50   ` Paul Walmsley
2015-05-20 22:56     ` Tony Lindgren
2015-05-21  1:06       ` Paul Walmsley
2015-08-27  6:25   ` Hannes Schmelzer
     [not found]   ` <OFCA2F1DCE.C787A961-ONC1257EAE.001D79BC-C1257EAE.00203AFF@br-automation.com>
2015-08-27 16:59     ` Tony Lindgren
2015-08-28  4:44       ` Hannes Schmelzer
2015-09-01 12:35     ` Roger Quadros
2015-09-01 13:31       ` Antwort: " Hannes Schmelzer
2015-09-02 14:43         ` Roger Quadros
2015-09-01 12:35     ` Roger Quadros
2016-01-01 11:29   ` Ivaylo Dimitrov
2016-01-04 17:02     ` Tony Lindgren
2016-01-04 17:34       ` Pali Rohár
2016-01-04 17:40         ` Tony Lindgren
2016-01-04 18:59           ` Ivaylo Dimitrov
2016-01-05  4:13             ` Tony Lindgren
2016-01-05  8:49               ` Pali Rohár
2016-01-05 22:49                 ` Tony Lindgren
2016-01-06  8:55                   ` Ivaylo Dimitrov
2016-01-06  9:05                     ` Pali Rohár
2016-01-06 16:44                       ` Tony Lindgren
2016-01-06 17:36                   ` Aaro Koskinen
2016-01-06 17:40                   ` Sebastian Reichel
2016-01-06 17:47                     ` Tony Lindgren
2016-01-06 18:01                       ` Ivaylo Dimitrov
2016-01-06 18:26                         ` Tony Lindgren
2016-01-06 18:39                           ` Ivaylo Dimitrov
2016-01-07 18:07                             ` Tony Lindgren
2016-01-07 21:45                               ` Ivaylo Dimitrov
2016-01-08  2:26                                 ` Tony Lindgren
2016-01-08  5:13                                   ` Ivaylo Dimitrov [this message]
2016-01-08  7:59                                     ` Pali Rohár
2016-01-09  0:23                                       ` Ivaylo Dimitrov
2016-01-21  9:14                                         ` Pali Rohár
2016-02-02  9:33                                           ` Ivaylo Dimitrov
2016-02-02 23:39                                             ` Tony Lindgren
2016-02-03  0:00                                               ` Tony Lindgren
2016-02-03  7:03                                                 ` Ivaylo Dimitrov
2016-02-03 16:50                                                   ` Ivaylo Dimitrov
2016-02-05  6:10                                                     ` Tony Lindgren
2016-02-05 14:43                                                       ` Ivaylo Dimitrov
2016-01-08 17:10                                     ` Tony Lindgren
2016-01-08  7:56                                   ` Pali Rohár
2016-01-08 17:04                                     ` Tony Lindgren

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=568F4596.8020206@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).