From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitry Baryshkov <dbaryshkov@gmail.com>
Subject: Re: Linux 2.6.28-rc7
Date: Tue, 2 Dec 2008 08:13:47 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812020804590.3256@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20081202165637.09984819@varda>
On Tue, 2 Dec 2008, Alejandro Riveira Fernández wrote:
>
> from my reply to pazke <pazke@ports.donpac.ru>
> "
> I took the sanpshot of the dmesg after loading the module if my word is not
> enough i can reboot with the module disabled but i do not see the point...
> The truth is that the bug prevented me from loading/installing the nvidia
> module becouse i could not use sudo. Only when i rebooted into single mode
> where the problems went away i could build and install the module...
Ahh, ok. I did wonder if something was up from the timing (ie it was
loaded almost two minutes after bootup).
Since you are apparently a git user, and 2.6.28-rc6-00007-ged31348 was
fine, there's really only 270 commits in between that and 2.6.28-rc7. Can
I ask you to bisect for a couple of runs, which would cut it down to a
handful? (Ie you don't even need to do a full bisect, although that should
really only require about 8 reboots).
Just do
git bisect start
git bisect bad v2.6.27
git bisect good v2.6.28-rc6-00007-ged31348
and off you go. That would help enormously.
There are very few console-related changes in that range, and the most
notably one is actually radeon-specific so it shouldn't be an issue for
you. I'd _suspect_ bca404afdc5206c3bb30168315ee8a98a579ec65 ("fbdev: fix
FB console blanking"), but quite frankly, it could be something random
that just interacted badly. A bisection would narrow things down.
Linus
next prev parent reply other threads:[~2008-12-02 16:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 4:11 Linus Torvalds
2008-12-02 12:14 ` Alejandro Riveira Fernández
2008-12-02 13:11 ` pazke
2008-12-02 14:48 ` Alejandro Riveira Fernández
2008-12-02 15:20 ` Alistair John Strachan
2008-12-02 15:50 ` Alejandro Riveira Fernández
2008-12-02 16:14 ` Alistair John Strachan
2008-12-02 15:54 ` Alejandro Riveira Fernández
2008-12-02 15:50 ` Linus Torvalds
2008-12-02 15:56 ` Alejandro Riveira Fernández
2008-12-02 16:13 ` Linus Torvalds [this message]
2008-12-02 16:29 ` About git-bisect (was: Linux 2.6.28-rc7) Renato S. Yamane
2008-12-02 16:55 ` Sam Ravnborg
2008-12-02 17:05 ` Linus Torvalds
2008-12-02 17:01 ` Linus Torvalds
2008-12-02 18:49 ` Linux 2.6.28-rc7 Alejandro Riveira Fernández
2008-12-02 19:22 ` Alejandro Riveira Fernández
2008-12-02 19:23 ` Linus Torvalds
2008-12-02 19:45 ` Alejandro Riveira Fernández
2008-12-02 20:40 ` Linus Torvalds
2008-12-02 20:29 ` Al Viro
[not found] <fa.IDjfwzrT2B02+NHfmYwtICnzOOA@ifi.uio.no>
[not found] ` <fa.J8MFTCUT8El3sK8BuYDBvaMRaB8@ifi.uio.no>
[not found] ` <fa.q/4H3AtoJGSJ+i8tlXR4X35LFFU@ifi.uio.no>
[not found] ` <fa.98CeSgxJ/GGaLLyZ97s1oHgh7hE@ifi.uio.no>
2008-12-02 17:11 ` Michael B. Trausch
2008-12-02 18:06 ` Alejandro Riveira Fernández
2008-12-02 18:56 ` Michael B. Trausch
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=alpine.LFD.2.00.0812020804590.3256@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ariveira@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®