From: "Justin Mattock" <justinmattock@gmail.com>
To: "James Cloos" <cloos@jhcloos.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression: starting X locks box with git master
Date: Thu, 24 Apr 2008 20:39:25 +0000 [thread overview]
Message-ID: <dd18b0c30804241339n34f7e676xee7807c2b1cf71ff@mail.gmail.com> (raw)
In-Reply-To: <m3hcdrqb03.fsf@lugabout.jhcloos.org>
On Thu, Apr 24, 2008 at 7:59 PM, James Cloos <cloos@jhcloos.com> wrote:
> 3dc5063786b273f1aee545844f6bd4e9651ebffe was current when I compiled.
>
> With that kernel, my laptop locks up as soon as I startx.
>
> The Xorg.0.log showed that the radeon driver got as far as starting
> the i2c calls to the M7 video card.
>
> After that the box would reply to ICMP pings and SysRq-B, but was
> otherwise non-responsive. Even SysRq-[KSU] seemed to do nothing.
>
> v2.6.25 works fine.
>
> There are 3562 commits (including merges) between those two, and
> it takes an hour or more for each kernel compile. Bisecting will
> be quite painful. And I only have the one box to work on. But I
> will see what I can do.
>
> Posting before bisecting in case it helps anyone else....
>
> -JimC
> --
> James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
I seem to expiriencing lockups as well, vary annoying, "I'm getting
freezes before X is even started", "and after as well." : (
using nmi_watchdog=1, or nohz=off, or nolapic_timer, or idle=poll
seems to help me with having no freezes, but using powertop
I'm seeing (100%) under AVG residency, which is a bit alarming to me.
If I dont give any boot options and leave my system as it was, I need
to boot and as fast as possible use glxgears to keep the processor at
a certain level, from freezing, but is hard to do.
overall I think this has to do with nohz, right now I have nohz=off
with highress on and the system seems to be behaving properly.
regards;
--
Justin P. Mattock
next prev parent reply other threads:[~2008-04-24 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 19:59 James Cloos
2008-04-24 20:39 ` Justin Mattock [this message]
2008-04-24 20:52 ` James Cloos
2008-04-24 20:52 ` Yinghai Lu
2008-04-24 21:10 ` Justin Mattock
2008-04-24 22:36 ` James Cloos
2008-05-07 21:53 ` Rafael J. Wysocki
2008-05-07 21:58 ` Justin Mattock
2008-05-07 22:06 ` James Cloos
2008-05-07 22:43 ` Justin Mattock
2008-05-08 22:57 ` James Cloos
2008-05-09 0:00 ` Justin Mattock
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=dd18b0c30804241339n34f7e676xee7807c2b1cf71ff@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=cloos@jhcloos.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®