From: Glyn Astill <glynastill@yahoo.co.uk>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Debian etch on cobalt
Date: Sun, 3 Aug 2008 13:55:58 +0000 (GMT) [thread overview]
Message-ID: <758145.35434.qm@web25805.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20080803065822.GE5392@deprecation.cyrius.com>
Just discovered sarge falls over too, however less frequently. So perhaps it's something else, I'm not sure now.
I've switched the drive out, I actually managed to find the original 20gig unit that came with it.
One thing I observed today is free memory getting rather low whilst compiling, it shows about 187Mb total, and I've watched it go as low as 8mb free. The only other thing I can think of is it's possibly overheating and falling over.
--- On Sun, 3/8/08, Martin Michlmayr <tbm@cyrius.com> wrote:
> From: Martin Michlmayr <tbm@cyrius.com>
> Subject: Re: Debian etch on cobalt
> To: "Glyn Astill" <glynastill@yahoo.co.uk>
> Cc: linux-mips@linux-mips.org
> Date: Sunday, 3 August, 2008, 7:58 AM
> * Glyn Astill <glynastill@yahoo.co.uk> [2008-08-01
> 10:49]:
> > Sarge seems okay, however I'd rather run etch. Is
> there anything else I can check?
>
> I'm not sure.
>
> There used to be a hang connected to DMA and high network
> traffic, but
> this should be fixed in the kernel in etch.
> --
> Martin Michlmayr
> http://www.cyrius.com/
__________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html
prev parent reply other threads:[~2008-08-03 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 21:45 Debian etch on cobalt Glyn Astill
2008-07-25 23:46 ` Martin Michlmayr
2008-08-01 10:49 ` Glyn Astill
2008-08-03 6:58 ` Martin Michlmayr
2008-08-03 13:55 ` Glyn Astill [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=758145.35434.qm@web25805.mail.ukl.yahoo.com \
--to=glynastill@yahoo.co.uk \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.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