From: Daniel Hazelton <dhazelton@enter.net>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Various Errors with recent GIT
Date: Sat, 2 Feb 2008 00:09:55 -0500 [thread overview]
Message-ID: <200802020009.56037.dhazelton@enter.net> (raw)
In-Reply-To: <47A3F4C7.4060406@googlemail.com>
On Friday 01 February 2008 23:42:47 Gabriel C wrote:
> Daniel Hazelton wrote:
> > Another problem is one I wasn't able to find any kind of trigger for,
> > other than just running XChat. Every so often XChat would seem to freeze
> > - but if run from the command line, switching to that terminal window and
> > hitting "ctrl-c" would cause it to rapidly update and become responsive
> > again. The freeze would happen at a random time interval that I couldn't
> > figure out.
>
> I got that Xchat problem on i686 yesterday.
>
> I'm running 2.6.24-06481-gaa62999 right now with near 4h uptime and the
> problem seems fixed.
Hrm... I'll see about updating my local git tree and building a new kernel.
With the x86 merger if it's fixed in 32bit it is probably also fixed in
64bit.
The other problems are a bigger concern, though. I don't like seeing warnings
in my logs - makes me worry about the long-term stability of my systems. And
with the apparent problem in libata I'm not too sure I will be able to
successfully boot into a new kernel - after all, the system just spins on
trying and retrying the drive without any progress. (And it seems random,
though it does appear that the trick to a successful boot is to get the
hardware completely powered down - in other words, a completely cold boot)
DRH
> > DRH
>
> Gabriel
--
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
prev parent reply other threads:[~2008-02-02 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 3:52 Various Errors with recent GIT Daniel Hazelton
2008-02-02 4:42 ` Gabriel C
2008-02-02 5:09 ` Daniel Hazelton [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=200802020009.56037.dhazelton@enter.net \
--to=dhazelton@enter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox