From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: droid 4 in v4.18-rc: grep -r adasfasd /sys/ oopses
Date: Mon, 9 Jul 2018 13:10:37 +0200 [thread overview]
Message-ID: <20180709111036.GB11785@amd> (raw)
In-Reply-To: <20180709103305.GF112168@atomide.com>
On Mon 2018-07-09 03:33:05, Tony Lindgren wrote:
> * Pavel Machek <pavel@ucw.cz> [180708 19:40]:
> > Ok, so it seems to be:
> >
> > user at devuan:~$ cat /sys/kernel/debug/pm_debug/count
> > (oops).
> >
> > The file seems to be world-readable.
> >
> > user at devuan:~$ ls -al /sys/kernel/debug/pm_debug/count
> > -r--r--r-- 1 root root 0 Jan 1 1970 /sys/kernel/debug/pm_debug/count
> >
> > But on PC, that file does not exist.
> >
> > Any ideas?
>
> I'm not seeing this as tested with omap2plus_defconfig and
> not seeing any unclocked module interrupts here.. Can you
> see if the script below produces something for you?
>
> I had to filter out some trace pipes as they seem to hang.
After some more debugging:
+ printk("3...\n");
cm_per_dump(s);
+ printk("4...\n");
cm_per_dump seems to be the problem.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180709/3cbd8614/attachment.sig>
next prev parent reply other threads:[~2018-07-09 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 17:49 droid 4 in v4.18-rc: grep -r adasfasd /sys/ oopses Pavel Machek
2018-07-08 19:37 ` Pavel Machek
2018-07-09 10:28 ` Pavel Machek
2018-07-09 10:49 ` Pavel Machek
2018-07-09 11:25 ` Andy Shevchenko
2018-07-09 10:33 ` Tony Lindgren
2018-07-09 11:09 ` Pavel Machek
2018-07-09 11:10 ` Pavel Machek [this message]
2018-07-09 11:16 ` Pavel Machek
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=20180709111036.GB11785@amd \
--to=pavel@ucw.cz \
--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).