On Wed, May 01, 2013 at 08:28:30AM -0700, Hugh Dickins wrote:
> On Tue, 30 Apr 2013, Johannes Weiner wrote:
> > On Wed, Apr 24, 2013 at 08:50:01PM -0700, Hugh Dickins wrote:
> > > On Wed, 24 Apr 2013, Johannes Weiner wrote:
> > > > On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
> >
On Tue, 30 Apr 2013, Johannes Weiner wrote:
> On Wed, Apr 24, 2013 at 08:50:01PM -0700, Hugh Dickins wrote:
> > On Wed, 24 Apr 2013, Johannes Weiner wrote:
> > > On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
> > > > On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
> > > > > On Thu,
On Tue, 30 Apr 2013, Johannes Weiner wrote:
On Wed, Apr 24, 2013 at 08:50:01PM -0700, Hugh Dickins wrote:
On Wed, 24 Apr 2013, Johannes Weiner wrote:
On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
On Thu, Apr 18, 2013 at
On Wed, May 01, 2013 at 08:28:30AM -0700, Hugh Dickins wrote:
On Tue, 30 Apr 2013, Johannes Weiner wrote:
On Wed, Apr 24, 2013 at 08:50:01PM -0700, Hugh Dickins wrote:
On Wed, 24 Apr 2013, Johannes Weiner wrote:
On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
On Wed
On Wed, Apr 24, 2013 at 08:50:01PM -0700, Hugh Dickins wrote:
> On Wed, 24 Apr 2013, Johannes Weiner wrote:
> > On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
> > > On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
> > > > On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens
On Wed, Apr 24, 2013 at 08:50:01PM -0700, Hugh Dickins wrote:
On Wed, 24 Apr 2013, Johannes Weiner wrote:
On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
Ok,
On Wed, 24 Apr 2013, Johannes Weiner wrote:
> On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
> > On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
> > > On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
> > > > Ok, thanks for verifying! I'll look into it; hopefully I can
On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
> On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
> > On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
> > > Ok, thanks for verifying! I'll look into it; hopefully I can reproduce it
> > > here as well.
> >
> > That
On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
> On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
> > Ok, thanks for verifying! I'll look into it; hopefully I can reproduce it
> > here as well.
>
> That seems to be a common code bug. I can easily trigger the VM_BUG_ON()
> below
On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
> Ok, thanks for verifying! I'll look into it; hopefully I can reproduce it
> here as well.
That seems to be a common code bug. I can easily trigger the VM_BUG_ON()
below (when I force the system to swap):
[ 48.347963]
On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
Ok, thanks for verifying! I'll look into it; hopefully I can reproduce it
here as well.
That seems to be a common code bug. I can easily trigger the VM_BUG_ON()
below (when I force the system to swap):
[ 48.347963] [
On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
Ok, thanks for verifying! I'll look into it; hopefully I can reproduce it
here as well.
That seems to be a common code bug. I can easily trigger the VM_BUG_ON()
below (when I
On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
Ok, thanks for verifying! I'll look into it; hopefully I can reproduce it
here as well.
That seems to be a
On Wed, 24 Apr 2013, Johannes Weiner wrote:
On Wed, Apr 24, 2013 at 03:18:51PM +0200, Michal Hocko wrote:
On Wed 24-04-13 12:42:55, Heiko Carstens wrote:
On Thu, Apr 18, 2013 at 09:13:03AM +0200, Heiko Carstens wrote:
Ok, thanks for verifying! I'll look into it; hopefully I can reproduce
On Thu, Apr 18, 2013 at 02:27:45AM -0400, Zhouping Liu wrote:
> Hello Heiko,
> > If you have some time, could you please repeat your test with the kernel
> > command line option " user_mode=home "?
>
> I tested the system with the kernel parameter, but the issue still appeared,
> I just to say it
Hello Heiko,
- Original Message -
> From: "Heiko Carstens"
> To: "Zhouping Liu"
> Cc: linux...@kvack.org, "LKML" , "caiqian"
> , "Caspar Zhang"
> , "Martin Schwidefsky"
> Sent: Tuesday, April 16, 2013 3:50:
: Tuesday, April 16, 2013 3:50:47 PM
Subject: Re: [BUG][s390x] mm: system crashed
On Mon, Apr 15, 2013 at 02:16:55PM +0800, Zhouping Liu wrote:
On 04/15/2013 01:56 PM, Heiko Carstens wrote:
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
� 16109.346170¨ Call Trace
On Thu, Apr 18, 2013 at 02:27:45AM -0400, Zhouping Liu wrote:
Hello Heiko,
If you have some time, could you please repeat your test with the kernel
command line option user_mode=home ?
I tested the system with the kernel parameter, but the issue still appeared,
I just to say it takes
On Tue, Apr 16, 2013 at 03:56:59PM +0800, Simon Jeons wrote:
> Hi Heiko,
> >If you have some time, could you please repeat your test with the kernel
> >command line option " user_mode=home "?
>
> What's the meaning of this command line? I can't find it in
> Documentation/kernel-parameters.txt/
Hi Heiko,
On 04/16/2013 03:50 PM, Heiko Carstens wrote:
On Mon, Apr 15, 2013 at 02:16:55PM +0800, Zhouping Liu wrote:
On 04/15/2013 01:56 PM, Heiko Carstens wrote:
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
� 16109.346170¨ Call Trace:
� 16109.346179¨ (� <00100920>¨
On Mon, Apr 15, 2013 at 02:16:55PM +0800, Zhouping Liu wrote:
> On 04/15/2013 01:56 PM, Heiko Carstens wrote:
> >On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
> >>� 16109.346170¨ Call Trace:
> >>� 16109.346179¨ (� <00100920>¨ show_trace+0x128/0x12c)
> >>� 16109.346195¨ �
On Mon, Apr 15, 2013 at 02:16:55PM +0800, Zhouping Liu wrote:
On 04/15/2013 01:56 PM, Heiko Carstens wrote:
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
� 16109.346170¨ Call Trace:
� 16109.346179¨ (� 00100920¨ show_trace+0x128/0x12c)
� 16109.346195¨ �
Hi Heiko,
On 04/16/2013 03:50 PM, Heiko Carstens wrote:
On Mon, Apr 15, 2013 at 02:16:55PM +0800, Zhouping Liu wrote:
On 04/15/2013 01:56 PM, Heiko Carstens wrote:
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
� 16109.346170¨ Call Trace:
� 16109.346179¨ (� 00100920¨
On Tue, Apr 16, 2013 at 03:56:59PM +0800, Simon Jeons wrote:
Hi Heiko,
If you have some time, could you please repeat your test with the kernel
command line option user_mode=home ?
What's the meaning of this command line? I can't find it in
Documentation/kernel-parameters.txt/
It switches
On 04/15/2013 01:56 PM, Heiko Carstens wrote:
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
Hi All,
I hit the below crashed when doing memory related tests[1] on s390x:
--- snip -
� 15929.351639¨ � <0021c0a6>¨
On 04/15/2013 01:56 PM, Heiko Carstens wrote:
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
Hi All,
I hit the below crashed when doing memory related tests[1] on s390x:
--- snip -
� 15929.351639¨ � 0021c0a6¨
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
> Hi All,
>
> I hit the below crashed when doing memory related tests[1] on s390x:
>
> --- snip -
> � 15929.351639¨ � <0021c0a6>¨ shrink_inactive_list+0x1c6/0x56c
> � 15929.351647¨ �
Hi All,
I hit the below crashed when doing memory related tests[1] on s390x:
--- snip -
� 15929.351639¨ � <0021c0a6>¨ shrink_inactive_list+0x1c6/0x56c
� 15929.351647¨ � <0021c69e>¨ shrink_lruvec+0x252/0x56c
� 15929.351654¨ �
Hi All,
I hit the below crashed when doing memory related tests[1] on s390x:
--- snip -
� 15929.351639¨ � 0021c0a6¨ shrink_inactive_list+0x1c6/0x56c
� 15929.351647¨ � 0021c69e¨ shrink_lruvec+0x252/0x56c
� 15929.351654¨ � 0021ca44¨
On Sun, Apr 14, 2013 at 11:28:40PM -0400, Zhouping Liu wrote:
Hi All,
I hit the below crashed when doing memory related tests[1] on s390x:
--- snip -
� 15929.351639¨ � 0021c0a6¨ shrink_inactive_list+0x1c6/0x56c
� 15929.351647¨ � 0021c69e¨
30 matches
Mail list logo
