From: Matt Mackall <mpm@selenic.com>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
davem@davemloft.net
Subject: Re: 2.6.24-rc5-mm1: problems with cat /proc/kpageflags
Date: Sun, 16 Dec 2007 20:11:49 -0600 [thread overview]
Message-ID: <20071217021149.GC19691@waste.org> (raw)
In-Reply-To: <200712162010.11028.m.kozlowski@tuxland.pl>
On Sun, Dec 16, 2007 at 08:10:10PM +0100, Mariusz Kozlowski wrote:
> > > Can you change line 710 of fs/proc/proc_misc.c to:
> > >
> > > ppage = NULL;
> >
> > Sure.
> >
> > > ..and see if it still breaks?
> >
> > Yes it does - the same way as eariler. Box is locked, processes stuck in D state
> > and after a while "BUG: soft lockup - CPU#0 stuck for 11s!".
>
> My mistake. I run cat /proc/kpageflags in the first place - so how
> could anything change :)
>
> cat /proc/kpagecount on the other hand - with the change in line 710
> - locks the box. Sysrq works, changing consoles works, but there is
> no "BUG: soft lockup ..." message. After a while the box becomes
> totaly unresponsive - even caps lock doesn't work, no responses to
> ping.
Well I'm baffled. There's basically two things in that function that
do anything interesting: pfn_to_page and put_user. access_ok is
"return 1" on Sparc64. atomic_read is a simple read.
My usual approach at this point would be to litter it with printks and
see where its hanging.
But as the function doesn't actually show up in your stack trace,
something else is probably wrong. So I'd also try commenting out
pieces of that function until it started working.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-12-17 2:12 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 10:40 2.6.24-rc5-mm1 Andrew Morton
2007-12-13 11:59 ` 2.6.24-rc5-mm1 kobject changes broken with hvcs driver on powerpc - regression Kamalesh Babulal
2007-12-13 16:22 ` Greg KH
2007-12-13 12:28 ` 2.6.24-rc5-mm1 Gautham R Shenoy
2007-12-13 21:15 ` 2.6.24-rc5-mm1 Andrew Morton
2007-12-14 9:49 ` 2.6.24-rc5-mm1 Andrew Morton
2007-12-14 13:15 ` 2.6.24-rc5-mm1 Gregory Haskins
2007-12-13 14:18 ` 2.6.24-rc5-mm1 Pierre Peiffer
2007-12-13 15:01 ` 2.6.24-rc5-mm1 Benjamin Thery
2007-12-13 16:07 ` 2.6.24-rc5-mm1 Borislav Petkov
2007-12-13 17:54 ` 2.6.24-rc5-mm1 Adrian Bunk
2007-12-13 17:45 ` 2.6.24-rc5-mm1 David Miller
2007-12-14 2:08 ` 2.6.24-rc5-mm1 Herbert Xu
2007-12-14 19:26 ` 2.6.24-rc5-mm1 David Miller
2007-12-13 14:56 ` 2.6.24-rc5-mm1 regression - kernel warning on tcp_fastretrans_alert() Kamalesh Babulal
2007-12-13 19:55 ` Andrew Morton
2007-12-13 15:16 ` 2.6.24-rc5-mm1 - build failures due to kobject changes Kamalesh Babulal
2007-12-13 16:21 ` Greg KH
2007-12-13 17:46 ` (was Re: 2.6.24-rc5-mm1) crypto/authenc.c select symbol in Kconfig Borislav Petkov
2007-12-14 8:53 ` Herbert Xu
2007-12-14 5:32 ` 2.6.24-rc5-mm1 Dave Young
2007-12-14 15:44 ` 2.6.24-rc5-mm1 Alan Stern
2007-12-17 1:14 ` 2.6.24-rc5-mm1 Dave Young
2007-12-19 7:49 ` 2.6.24-rc5-mm1 Dave Young
2007-12-19 16:07 ` 2.6.24-rc5-mm1 Alan Stern
2007-12-20 0:43 ` 2.6.24-rc5-mm1 Dave Young
2007-12-20 3:34 ` 2.6.24-rc5-mm1 Alan Stern
2007-12-20 4:32 ` 2.6.24-rc5-mm1 Dave Young
2007-12-14 14:08 ` 2.6.24-rc5-mm1 Dhaval Giani
2007-12-15 19:20 ` 2.6.24-rc5-mm1 Alexey Dobriyan
2007-12-16 9:10 ` 2.6.24-rc5-mm1 Andrew Morton
2007-12-15 23:59 ` broken suspend, sometimes (drm related) [Was: 2.6.24-rc5-mm1] Jiri Slaby
2007-12-17 16:55 ` Jesse Barnes
2007-12-16 0:18 ` 2.6.24-rc5-mm1: cat /proc/net/packet -> oops Mariusz Kozlowski
2007-12-16 3:07 ` Herbert Xu
2007-12-16 3:41 ` [PACKET]: Fix /proc/net/packet crash due to bogus private pointer Herbert Xu
2007-12-16 10:48 ` Mariusz Kozlowski
2007-12-16 22:04 ` David Miller
2007-12-16 10:11 ` 2.6.24-rc5-mm1: problems with cat /proc/kpageflags Mariusz Kozlowski
2007-12-16 10:14 ` Mariusz Kozlowski
2007-12-16 10:41 ` Mariusz Kozlowski
2007-12-16 11:40 ` Mariusz Kozlowski
2007-12-16 18:27 ` Matt Mackall
2007-12-16 18:48 ` Mariusz Kozlowski
2007-12-16 19:10 ` Mariusz Kozlowski
2007-12-17 2:11 ` Matt Mackall [this message]
2007-12-17 4:26 ` David Miller
2007-12-17 6:39 ` Andrew Morton
2007-12-17 14:55 ` Matt Mackall
2007-12-20 12:53 ` David Miller
2007-12-20 17:45 ` Matt Mackall
2007-12-20 19:47 ` Mariusz Kozlowski
2007-12-21 0:17 ` David Miller
2007-12-21 1:06 ` Matt Mackall
2007-12-21 3:15 ` David Miller
2007-12-21 21:51 ` Mariusz Kozlowski
2007-12-22 5:00 ` Andrew Morton
2007-12-17 19:05 ` Mariusz Kozlowski
2007-12-17 22:44 ` 2.6.24-rc5-mm1 - wonky disk cache and CDROM behavior Valdis.Kletnieks
2007-12-17 22:56 ` Andrew Morton
2007-12-18 2:07 ` Valdis.Kletnieks
2007-12-18 2:37 ` Dave Young
2007-12-18 2:52 ` Andrew Morton
2007-12-19 1:22 ` David Howells
2007-12-19 1:33 ` Dave Young
2007-12-19 2:04 ` Andrew Morton
2007-12-19 3:30 ` Jeff Dike
2007-12-18 5:52 ` Valdis.Kletnieks
2007-12-18 6:10 ` 2.6.24-rc5-mm1 - IPv6 throws section mismatches Valdis.Kletnieks
2007-12-18 15:12 ` Daniel Lezcano
2007-12-20 16:55 ` 2.6.24-rc5-mm1 Jason Wessel
2007-12-20 23:11 ` 2.6.24-rc5-mm1 Andrew Morton
2007-12-21 13:46 ` 2.6.24-rc5-mm1 Jason Wessel
2007-12-20 20:57 ` 2.6.24-rc5-mm1 - SCSI/blkdev probing hang Rik van Riel
2007-12-20 21:22 ` Andrew Morton
2007-12-24 15:12 ` Rik van Riel
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=20071217021149.GC19691@waste.org \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=sparclinux@vger.kernel.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