On Fri, 21 Dec 2007 22:51:45 +0100 Mariusz Kozlowski <[EMAIL PROTECTED]> wrote:
> > Here's a test patch:
>
> Tested on 2.6.23 and 2.6.24-rc5-mm1. The patch fixes the bug.
>
> Thanks a lot to both of you.
Thank you for testing -mm (especially on sparc64) and for reporting
the bug and for
Hello,
> > > [ 145.128915] TSTATE: 004411009603 TPC: 005119ac TNPC:
> > > 005119b0 Y: Not tainted
> > > [ 145.128940] TPC:
> >
> > My suspicion at this point is that with certain RAM layouts, simply
> > iterating over PFN's is simply not working out.
>
> That
Hello,
[ 145.128915] TSTATE: 004411009603 TPC: 005119ac TNPC:
005119b0 Y: Not tainted
[ 145.128940] TPC: kpagecount_read+0x94/0xe0
My suspicion at this point is that with certain RAM layouts, simply
iterating over PFN's is simply not working out.
On Fri, 21 Dec 2007 22:51:45 +0100 Mariusz Kozlowski [EMAIL PROTECTED] wrote:
Here's a test patch:
Tested on 2.6.23 and 2.6.24-rc5-mm1. The patch fixes the bug.
Thanks a lot to both of you.
Thank you for testing -mm (especially on sparc64) and for reporting
the bug and for testing the
From: Matt Mackall <[EMAIL PROTECTED]>
Date: Thu, 20 Dec 2007 19:06:55 -0600
> @@ -707,7 +707,10 @@ static ssize_t kpagecount_read(struct fi
> return -EIO;
>
> while (count > 0) {
> - ppage = pfn_to_page(pfn++);
> + ppage = 0;
> + if
On Thu, Dec 20, 2007 at 04:17:26PM -0800, David Miller wrote:
> From: Mariusz Kozlowski <[EMAIL PROTECTED]>
> Date: Thu, 20 Dec 2007 20:47:55 +0100
>
> > [ 145.128915] TSTATE: 004411009603 TPC: 005119ac TNPC:
> > 005119b0 Y: Not tainted
> > [ 145.128940] TPC:
>
From: Mariusz Kozlowski <[EMAIL PROTECTED]>
Date: Thu, 20 Dec 2007 20:47:55 +0100
> [ 145.128915] TSTATE: 004411009603 TPC: 005119ac TNPC:
> 005119b0 Y: Not tainted
> [ 145.128940] TPC:
My suspicion at this point is that with certain RAM layouts, simply
Hello,
> > > Actually, you may only need these two:
> > >
> > > > maps4-add-proc-kpagecount-interface.patch
> > > > maps4-add-proc-kpageflags-interface.patch
> >
> > Yes these two were enough, and exporting fs/proc/base.c's
> > mem_lseek().
> >
> > As hard as I try, I can't reproduce this at
On Thu, Dec 20, 2007 at 04:53:59AM -0800, David Miller wrote:
> From: Matt Mackall <[EMAIL PROTECTED]>
> Date: Mon, 17 Dec 2007 08:55:54 -0600
>
> > On Sun, Dec 16, 2007 at 10:39:17PM -0800, Andrew Morton wrote:
> > Actually, you may only need these two:
> >
> > >
From: Matt Mackall <[EMAIL PROTECTED]>
Date: Mon, 17 Dec 2007 08:55:54 -0600
> On Sun, Dec 16, 2007 at 10:39:17PM -0800, Andrew Morton wrote:
> Actually, you may only need these two:
>
> > maps4-add-proc-kpagecount-interface.patch
> > maps4-add-proc-kpageflags-interface.patch
Yes these two were
From: Matt Mackall [EMAIL PROTECTED]
Date: Mon, 17 Dec 2007 08:55:54 -0600
On Sun, Dec 16, 2007 at 10:39:17PM -0800, Andrew Morton wrote:
Actually, you may only need these two:
maps4-add-proc-kpagecount-interface.patch
maps4-add-proc-kpageflags-interface.patch
Yes these two were enough,
On Thu, Dec 20, 2007 at 04:53:59AM -0800, David Miller wrote:
From: Matt Mackall [EMAIL PROTECTED]
Date: Mon, 17 Dec 2007 08:55:54 -0600
On Sun, Dec 16, 2007 at 10:39:17PM -0800, Andrew Morton wrote:
Actually, you may only need these two:
maps4-add-proc-kpagecount-interface.patch
Hello,
Actually, you may only need these two:
maps4-add-proc-kpagecount-interface.patch
maps4-add-proc-kpageflags-interface.patch
Yes these two were enough, and exporting fs/proc/base.c's
mem_lseek().
As hard as I try, I can't reproduce this at all. I tried
both on
From: Mariusz Kozlowski [EMAIL PROTECTED]
Date: Thu, 20 Dec 2007 20:47:55 +0100
[ 145.128915] TSTATE: 004411009603 TPC: 005119ac TNPC:
005119b0 Y: Not tainted
[ 145.128940] TPC: kpagecount_read+0x94/0xe0
My suspicion at this point is that with certain RAM
On Thu, Dec 20, 2007 at 04:17:26PM -0800, David Miller wrote:
From: Mariusz Kozlowski [EMAIL PROTECTED]
Date: Thu, 20 Dec 2007 20:47:55 +0100
[ 145.128915] TSTATE: 004411009603 TPC: 005119ac TNPC:
005119b0 Y: Not tainted
[ 145.128940] TPC:
From: Matt Mackall [EMAIL PROTECTED]
Date: Thu, 20 Dec 2007 19:06:55 -0600
@@ -707,7 +707,10 @@ static ssize_t kpagecount_read(struct fi
return -EIO;
while (count 0) {
- ppage = pfn_to_page(pfn++);
+ ppage = 0;
+ if
Hello,
> > 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
> >
On Sun, Dec 16, 2007 at 10:39:17PM -0800, Andrew Morton wrote:
> On Sun, 16 Dec 2007 20:26:11 -0800 (PST) David Miller <[EMAIL PROTECTED]>
> wrote:
>
> > From: Matt Mackall <[EMAIL PROTECTED]>
> > Date: Sun, 16 Dec 2007 20:11:49 -0600
> >
> > > But as the function doesn't actually show up in
On Sun, Dec 16, 2007 at 10:39:17PM -0800, Andrew Morton wrote:
On Sun, 16 Dec 2007 20:26:11 -0800 (PST) David Miller [EMAIL PROTECTED]
wrote:
From: Matt Mackall [EMAIL PROTECTED]
Date: Sun, 16 Dec 2007 20:11:49 -0600
But as the function doesn't actually show up in your stack trace,
Hello,
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
On Sun, 16 Dec 2007 20:26:11 -0800 (PST) David Miller <[EMAIL PROTECTED]> wrote:
> From: Matt Mackall <[EMAIL PROTECTED]>
> Date: Sun, 16 Dec 2007 20:11:49 -0600
>
> > But as the function doesn't actually show up in your stack trace,
> > something else is probably wrong. So I'd also try
From: Matt Mackall <[EMAIL PROTECTED]>
Date: Sun, 16 Dec 2007 20:11:49 -0600
> 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.
Some piece of state is being
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
> >
Witam,
> > > > cat /proc/kpageflags on sparc64 causes the box to lock.
> > > > I can not write on any terminal - but I can issue sysrqs and switch
> > > > between consoles.
> > > >
> > > > cat process hangs in read(3, ...
> > >
> > > cat /proc/kpagecount produces similar symptoms. box
> > > cat /proc/kpageflags on sparc64 causes the box to lock.
> > > I can not write on any terminal - but I can issue sysrqs and switch
> > > between consoles.
> > >
> > > cat process hangs in read(3, ...
> >
> > cat /proc/kpagecount produces similar symptoms. box is locked - sysrq-w
>
On Sun, Dec 16, 2007 at 12:40:53PM +0100, Mariusz Kozlowski wrote:
> > cat /proc/kpageflags on sparc64 causes the box to lock.
> > I can not write on any terminal - but I can issue sysrqs and switch
> > between consoles.
> >
> > cat process hangs in read(3, ...
>
> cat /proc/kpagecount
> cat /proc/kpageflags on sparc64 causes the box to lock.
> I can not write on any terminal - but I can issue sysrqs and switch
> between consoles.
>
> cat process hangs in read(3, ...
cat /proc/kpagecount produces similar symptoms. box is locked - sysrq-w sshd
trace:
__down
Hello
> Will reply soon with correct data.
Ok here it goes:
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
sysrq-w shows:
syslogd D 0069240c
> cat /proc/kpageflags on sparc64 causes the box to lock.
> I can not write on any terminal - but I can issue sysrqs and switch
> between consoles.
>
> cat process hangs in read(3, ...
>
> sysrq-w shows:
>
> syslogd D 0069240c 0 2470 1
> Call Trace:
>
Hello,
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
sysrq-w shows:
syslogd D 0069240c 0 2470 1
Call Trace:
[00692224]
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
From: Matt Mackall [EMAIL PROTECTED]
Date: Sun, 16 Dec 2007 20:11:49 -0600
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.
Some piece of state is being
On Sun, 16 Dec 2007 20:26:11 -0800 (PST) David Miller [EMAIL PROTECTED] wrote:
From: Matt Mackall [EMAIL PROTECTED]
Date: Sun, 16 Dec 2007 20:11:49 -0600
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
Hello,
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
sysrq-w shows:
syslogd D 0069240c 0 2470 1
Call Trace:
[00692224]
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
sysrq-w shows:
syslogd D 0069240c 0 2470 1
Call Trace:
[00692224]
Hello
Will reply soon with correct data.
Ok here it goes:
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
sysrq-w shows:
syslogd D 0069240c
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
cat /proc/kpagecount produces similar symptoms. box is locked - sysrq-w sshd
trace:
__down
On Sun, Dec 16, 2007 at 12:40:53PM +0100, Mariusz Kozlowski wrote:
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
cat /proc/kpagecount produces
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
cat /proc/kpagecount produces similar symptoms. box is locked - sysrq-w
sshd trace:
Witam,
cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.
cat process hangs in read(3, ...
cat /proc/kpagecount produces similar symptoms. box is locked - sysrq-w
40 matches
Mail list logo
