On 30.11.2006 [12:43:09 +1100], David Gibson wrote:
> On Tue, Nov 28, 2006 at 09:56:51PM -0800, Nishanth Aravamudan wrote:
> [snip]
> > > I don't really see that failing after the first child comes back with
> > > a signal is a problem. I don't see any situations where the return
> > > code from t
On Tue, Nov 28, 2006 at 09:56:51PM -0800, Nishanth Aravamudan wrote:
[snip]
> > I don't really see that failing after the first child comes back with
> > a signal is a problem. I don't see any situations where the return
> > code from the second child will be vital for debugging.
>
> Ok, I can ch
On 29.11.2006 [10:15:30 +1100], David Gibson wrote:
> On Tue, Nov 28, 2006 at 01:49:03PM -0800, Nishanth Aravamudan wrote:
> > On 16.11.2006 [10:50:13 +1100], David Gibson wrote:
> > > On Wed, Nov 15, 2006 at 01:09:07PM -0800, Nishanth Aravamudan wrote:
> > > > On 15.11.2006 [10:41:19 +1100], David
On Tue, Nov 28, 2006 at 01:49:03PM -0800, Nishanth Aravamudan wrote:
> On 16.11.2006 [10:50:13 +1100], David Gibson wrote:
> > On Wed, Nov 15, 2006 at 01:09:07PM -0800, Nishanth Aravamudan wrote:
> > > On 15.11.2006 [10:41:19 +1100], David Gibson wrote:
> > > > On Tue, Nov 14, 2006 at 02:33:59PM -0
On 28.11.2006 [16:07:41 -0600], Adam Litke wrote:
> On Tue, 2006-11-28 at 13:49 -0800, Nishanth Aravamudan wrote:
> > On 16.11.2006 [10:50:13 +1100], David Gibson wrote:
> > > On Wed, Nov 15, 2006 at 01:09:07PM -0800, Nishanth Aravamudan wrote:
> > > > On 15.11.2006 [10:41:19 +1100], David Gibson w
On Tue, 2006-11-28 at 13:49 -0800, Nishanth Aravamudan wrote:
> On 16.11.2006 [10:50:13 +1100], David Gibson wrote:
> > On Wed, Nov 15, 2006 at 01:09:07PM -0800, Nishanth Aravamudan wrote:
> > > On 15.11.2006 [10:41:19 +1100], David Gibson wrote:
> > > > On Tue, Nov 14, 2006 at 02:33:59PM -0800, Ni
On 16.11.2006 [10:50:13 +1100], David Gibson wrote:
> On Wed, Nov 15, 2006 at 01:09:07PM -0800, Nishanth Aravamudan wrote:
> > On 15.11.2006 [10:41:19 +1100], David Gibson wrote:
> > > On Tue, Nov 14, 2006 at 02:33:59PM -0800, Nishanth Aravamudan wrote:
> > > > On 14.11.2006 [12:21:36 -0800], Nisha
On Wed, Nov 15, 2006 at 01:09:07PM -0800, Nishanth Aravamudan wrote:
> On 15.11.2006 [10:41:19 +1100], David Gibson wrote:
> > On Tue, Nov 14, 2006 at 02:33:59PM -0800, Nishanth Aravamudan wrote:
> > > On 14.11.2006 [12:21:36 -0800], Nishanth Aravamudan wrote:
> > > > Hi all,
> > > >
> > > > I'm h
On 15.11.2006 [10:41:19 +1100], David Gibson wrote:
> On Tue, Nov 14, 2006 at 02:33:59PM -0800, Nishanth Aravamudan wrote:
> > On 14.11.2006 [12:21:36 -0800], Nishanth Aravamudan wrote:
> > > Hi all,
> > >
> > > I'm hitting a brick wall debugging the linkshare segfaults I'm seeing.
> > >
> > > (T
On Tue, Nov 14, 2006 at 02:33:59PM -0800, Nishanth Aravamudan wrote:
> On 14.11.2006 [12:21:36 -0800], Nishanth Aravamudan wrote:
> > Hi all,
> >
> > I'm hitting a brick wall debugging the linkshare segfaults I'm seeing.
> >
> > (These logs are from my 2-way x86_64, but I'm seeing similar issues
On 14.11.2006 [12:21:36 -0800], Nishanth Aravamudan wrote:
> Hi all,
>
> I'm hitting a brick wall debugging the linkshare segfaults I'm seeing.
>
> (These logs are from my 2-way x86_64, but I'm seeing similar issues on a G5
> (ppc64):
>
> HUGETLB_SHARE=2 xB.linkshare 2 (32):PASS
> HUGETLB_SH
Hi all,
I'm hitting a brick wall debugging the linkshare segfaults I'm seeing.
(These logs are from my 2-way x86_64, but I'm seeing similar issues on a G5
(ppc64):
HUGETLB_SHARE=2 xB.linkshare 2 (32):PASS
HUGETLB_SHARE=2 xB.linkshare 2 (64):PASS
HUGETLB_SHARE=1 xB.linkshare 2 (32):FA
12 matches
Mail list logo