linux-kernel - Re: 2.6.39-rc5-git2 boot crashs

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]

Message-ID: <BANLkTin=zhUfceHOg3i3BomYEa2kZm1cjQ@mail.gmail.com>
Date:	Sun, 1 May 2011 11:20:21 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	werner <w.landgraf@...ru>, Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org, jaxboe@...ionio.com, tj@...nel.org
Subject: Re: 2.6.39-rc5-git2 boot crashs

2011/5/1 werner <w.landgraf@...ru>:
>
> But, now, the 2nd compilation, I made with the slackware huge configuration.
> And this works !! It boots normally, and it also don't crash  if unzipping
> big files.  So you were right, to use a more little config, for find out
> better the reason.

Ok, good. Now we have confirmation that it's not the SATA driver
itself that causes problems, it's some other driver.

So what I'd suggest you try to do is a "config bisect" to see exactly
_what_ config option it is that makes things break. Steve Rostedt
wrote a tool ("ktest") for this exact thing, but I'm not entirely sure
that it will work for your situation. I've added Steve to the email
participants, and I'd suggest you read up on it:

  http://lwn.net/Articles/414064/

would seem to be a good starting point.

Of course, you could just try to do it manually too - just turn one
subsystem at a time from a module in the working slackware config into
a compiled-in thing, so that eventually you end up with the
non-working "almost everything compiled in" case. And see which
subsystem it is that causes problems.

And then when you find the subsystem that makes the problem re-appear,
you'd need to go back and try each driver at a time.

                         Linus
--
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/