linux-kernel - Re: Regression? 2.6.27-rc3 segfault on cold boot; not on warm boot.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 Aug 2008 13:38:31 +0100
From:	David Greaves <david@...eaves.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
	xfs@....sgi.com, linux-fsdevel@...r.kernel.org,
	Dave Chinner <david@...morbit.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Regression? 2.6.27-rc3 segfault on cold boot; not on warm boot.

Rafael J. Wysocki wrote:
> [Adding CCs]
> 
> [The issue is probably present in 2.6.26 too]
> 
> On Thursday, 21 of August 2008, David Greaves wrote:
>> I have a desktop system that has started having problems booting up in the morning.
>>
>> It appears to just happen on more recent kernels.
>> I was having unrelated CDROM problems with a driver in an old kernel and decided
>> to test 2.6.27-rcX
>> The CDROM problem is fine now.
>>
>> However I started having problems on -rc1. I found that the machine was hanging
>> soon after booting and needed a reboot. After a reboot it would work fine for
>> the rest of the day.
>> When -rc3 came out I tried that and the problem still appears to be there.
>>
>> The normal process is now to boot to single-user, ctrl-alt-sysreq-SUB and then
>> reboot to multi-user. This isn't ideal.
>>
>>
>> If I cold boot 2.6.25.3 the problem doesn't occur.
>> I will try different versions over the next few days.

As promised, I tried 2.6.26.3 this morning and didn't have the problem. I will
try again a few times to confirm.
Nb Although the log had an XFS failure, I think the real issue is the segfaults;
I think XFS is a casuality, not a cause. Th problem almost always results in an
XFS crash at some point - but usually preceded by many segfaults in random binaries.

David

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/