From: David Greaves <david@dgreaves.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, xfs@oss.sgi.com
Subject: Re: Regression? 2.6.27-rc3 segfault on cold boot; not on warm boot.
Date: Mon, 30 Mar 2009 17:53:13 +0100 [thread overview]
Message-ID: <49D0F8F9.3010906@dgreaves.com> (raw)
In-Reply-To: <49D0E28B.4090207@sandeen.net>
Eric Sandeen wrote:
> David Greaves wrote:
>> Rafael J. Wysocki wrote:
>>> [Adding CCs]
>>>
>>> [The issue is probably present in 2.6.26 too]
>> Yes, below is a netconsole boot of 2.26.6.3
>>
>> I cold booted - lots of segfaults. I then did a ctrl-Alt-SysRq-S-U-B to a warm
>> boot. No segfaults
>> (lots of #### mark the split)
>>
>> I've just started 2.6.25.14 building for tomorrow to confirm how far back it
>> goes. (I'm 99% sure 2.6.25 is OK)
>>
>> David
>
> (trimming cc's to xfs)
>
> David, did you get anywhere with identifying this further?
>
> Thanks,
> -Eric
Sorry, I didn't.
IIRC I spent a couple of weeks on it and found it too unpredictable to bisect.
I have been running 2.6.27.4 on that machine for a few months (checks... Nov 08)
and it's been good since then.
Linus suspected HW and we got into a habit of warming the machine up before
booting. That habit has long since gone and the last xfs hissy-fit was on 13 Sep 08.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-03-30 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 9:45 Regression? 2.6.27-rc3 segfault on cold boot; not on warm boot David Greaves
2008-08-21 12:47 ` Rafael J. Wysocki
2008-08-21 15:13 ` David Greaves
2008-08-21 18:26 ` Rafael J. Wysocki
2008-08-22 12:38 ` David Greaves
2008-08-23 9:48 ` David Greaves
2009-03-30 15:17 ` Eric Sandeen
2009-03-30 16:53 ` David Greaves [this message]
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=49D0F8F9.3010906@dgreaves.com \
--to=david@dgreaves.com \
--cc=rjw@sisk.pl \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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.