From: Bill Irwin <bill.irwin@oracle.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: David Miller <davem@davemloft.net>,
greg@kroah.com, linux-kernel@vger.kernel.org, akpm@osdl.org,
torvalds@osdl.org, stable@kernel.org, sparclinux@vger.kernel.org
Subject: Re: Linux 2.6.20.3
Date: Wed, 14 Mar 2007 05:40:18 +0000 [thread overview]
Message-ID: <20070314054018.GW18774@holomorphy.com> (raw)
In-Reply-To: <29495f1d0703131729y56a99d9cj15288e7c18e277a8@mail.gmail.com>
On Tue, Mar 13, 2007 at 05:29:17PM -0700, Nish Aravamudan wrote:
> Ok, truly bizarre, I found that I was not running stock 2.6.20.3, but
> had your small hugetlb patch on top.
> So I went back and patched 2.6.20.1 with your patch, rebooted, got a
> soft lockup. Went back to stock 2.6.20.1 and did not.
> I don't see how your patch (C&P below for reference) could make any
> difference...Especially because no hugepages were in use at the time.
> On patched 2.6.20.1, I was just trying to check if my source tree had
> your patch applied (by `patch -p1 < davem.patch`) and got the
> soft-lockup I saw in 2.6.20.3 with the patch applied. I am going to
> try a clean 2.6.20.3 as well, now.
I'm still trying to get on this.
-- wli
WARNING: multiple messages have this Message-ID (diff)
From: Bill Irwin <bill.irwin@oracle.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: David Miller <davem@davemloft.net>,
greg@kroah.com, linux-kernel@vger.kernel.org, akpm@osdl.org,
torvalds@osdl.org, stable@kernel.org, sparclinux@vger.kernel.org
Subject: Re: Linux 2.6.20.3
Date: Tue, 13 Mar 2007 22:40:18 -0700 [thread overview]
Message-ID: <20070314054018.GW18774@holomorphy.com> (raw)
In-Reply-To: <29495f1d0703131729y56a99d9cj15288e7c18e277a8@mail.gmail.com>
On Tue, Mar 13, 2007 at 05:29:17PM -0700, Nish Aravamudan wrote:
> Ok, truly bizarre, I found that I was not running stock 2.6.20.3, but
> had your small hugetlb patch on top.
> So I went back and patched 2.6.20.1 with your patch, rebooted, got a
> soft lockup. Went back to stock 2.6.20.1 and did not.
> I don't see how your patch (C&P below for reference) could make any
> difference...Especially because no hugepages were in use at the time.
> On patched 2.6.20.1, I was just trying to check if my source tree had
> your patch applied (by `patch -p1 < davem.patch`) and got the
> soft-lockup I saw in 2.6.20.3 with the patch applied. I am going to
> try a clean 2.6.20.3 as well, now.
I'm still trying to get on this.
-- wli
next prev parent reply other threads:[~2007-03-14 5:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 18:33 Linux 2.6.20.3 Greg KH
2007-03-13 18:34 ` Greg KH
2007-03-13 21:57 ` Nish Aravamudan
2007-03-13 21:57 ` Nish Aravamudan
2007-03-13 21:58 ` Nish Aravamudan
2007-03-13 21:58 ` Nish Aravamudan
2007-03-13 22:20 ` David Miller
2007-03-13 22:20 ` David Miller
2007-03-13 22:51 ` Nish Aravamudan
2007-03-13 22:51 ` Nish Aravamudan
2007-03-14 0:29 ` Nish Aravamudan
2007-03-14 0:29 ` Nish Aravamudan
2007-03-14 5:40 ` Bill Irwin [this message]
2007-03-14 5:40 ` Bill Irwin
2007-03-14 5:41 ` David Miller
2007-03-14 5:41 ` David Miller
2007-03-14 5:40 ` David Miller
2007-03-14 5:40 ` David Miller
2007-03-14 1:29 ` mdew .
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=20070314054018.GW18774@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.