From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux-pm mailing list <linux-pm@vger.kernel.org>
Subject: Re: droid 4 in v4.18-rc: grep -r adasfasd /sys/ oopses
Date: Mon, 09 Jul 2018 14:25:33 +0300 [thread overview]
Message-ID: <79db809d74dcbe84b7ed3001dd7c82649227783a.camel@linux.intel.com> (raw)
In-Reply-To: <20180709104943.GA5212@amd>
On Mon, 2018-07-09 at 12:49 +0200, Pavel Machek wrote:
> Hi!
>
> > > > grep in /sys produces a nasty oops:
> > > >
> > > > I guess next step is trying to find out which file that is..
> > >
> > > Let me see...
> > >
> > > openat(6, "suspend",
> > > O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW) = 4
> > > fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> > > read(4, 0x4d2000, 32768) = -1 EINVAL (Invalid
> > > argument)
> > > write(2, "grep: ", 6grep: ) = 6
> > > write(2, "/sys/kernel/debug/pm_debug/cefus"...,
> > > 47/sys/kernel/debug/pm_debug/cefuse_pwrdm/suspend) = 47
> > > write(2, ": Invalid argument", 18: Invalid argument) = 18
> > > write(2, "\n", 1
> > > ) = 1
> > > close(4) = 0
> > > close(6) = 0
> > > openat(5, "time",
> > > O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW)
> > > = 4
> > > fstat64(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> > > read(4, "cefuse_pwrdm (OFF),OFF:641441757"..., 32768) = 849
> > > read(4, "", 28672) = 0
> > > close(4) = 0
> > > openat(5, "count",
> > > O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW) = 4
> > > Connection to usb closed by remote host.
> > > Connection to usb closed.
> > > pavel@half:~$
> > >
> > > Ok, so it seems to be:
> > >
> > > user@devuan:~$ cat /sys/kernel/debug/pm_debug/count
> > > (oops).
> > >
> > > The file seems to be world-readable.
> > >
> > > user@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.
> >
> > Ok, it is easier to reproduce like this:
> >
> > sudo mount /dev/zero -t debugfs /sys/kernel/debug/
> > sudo cat /sys/kernel/debug/pm_debug/count
> >
> > I tried adding debugging like this:
>
> Confused.
>
>
> > seq_printf(s, "%s->%s (%d)\n", clkdm->name, clkdm-
> > >pwrdm.ptr->name,
> > clkdm->usecount);
>
> I replaced seq_prinf with printk, and it still crashes, after
> producing reasonable output.
>
You need to add printk to the show function as well. It might be last
item in the list which is problematic (or one after cefuse CLK domain.
> [ 74.852508] cmp...
> [ 74.855773] printf...
> [ 74.859313] l4_cfg_clkdm->core_pwrdm (0)
> [ 74.864532] done...
> [ 74.867889] cmp...
> [ 74.871154] printf...
> [ 74.874694] l4_cefuse_clkdm->cefuse_pwrdm (0)
> [ 74.880340] done...
> [ 74.883728] ------------[ cut here ]------------
> [ 74.889709] WARNING: CPU: 0 PID: 2127 at
> drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x23c/0x380
> [ 74.900695] 44000000.ocp:L3 Custom Error: MASTER MPU TARGET L4PER2
> (Read): Data Access in User mode during Functional access
> [ 74.915222] Modules linked in:
> [ 74.919982] CPU: 0 PID: 2127 Comm: cat Not tainted
> 4.18.0-rc4-88970-gf075a2c-dirty #763
> [ 74.929870] Hardware name: Generic OMAP4 (Flattened Device Tree)
> [ 74.937805] [<c010f6cc>] (unwind_backtrace) from [<c010ba50>]
> (show_stack+0x10/0x14)
>
>
> Pavel
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-07-09 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180708174939.GA10002@amd>
2018-07-08 19:37 ` droid 4 in v4.18-rc: grep -r adasfasd /sys/ oopses Pavel Machek
2018-07-09 10:28 ` Pavel Machek
2018-07-09 10:49 ` Pavel Machek
2018-07-09 11:25 ` Andy Shevchenko [this message]
2018-07-09 10:33 ` Tony Lindgren
2018-07-09 11:09 ` Pavel Machek
2018-07-09 11:10 ` Pavel Machek
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=79db809d74dcbe84b7ed3001dd7c82649227783a.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sre@kernel.org \
--cc=tony@atomide.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 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).