From: Ralf Baechle <ralf@linux-mips.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Tester with IP27/IP30 needed
Date: Tue, 15 Jan 2008 13:11:45 +0000 [thread overview]
Message-ID: <20080115131145.GA5189@linux-mips.org> (raw)
In-Reply-To: <20080115112420.GA7347@alpha.franken.de>
On Tue, Jan 15, 2008 at 12:24:20PM +0100, Thomas Bogendoerfer wrote:
> we are facing a strange problem with lenny/sid chroots on IP28. The
> machine locks up after issuing a few ls/ps commands in a chroot
> bash. This only happens with a lenny/sid chroot, but not with etch.
> The major difference is probably the updare to glibc2.7. Since
> IP28 isn't really a nice R10k machine, it would be good, if someone
> with a working IP27/IP30 could try a lenny/sid chroot and tell us,
> if it's working/not working.
Which CPU revision do you hit these problems on?
Ralf
next prev parent reply other threads:[~2008-01-15 13:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 11:24 Tester with IP27/IP30 needed Thomas Bogendoerfer
2008-01-15 11:27 ` Florian Lohoff
2008-01-17 0:40 ` Thomas Bogendoerfer
2008-01-17 8:27 ` Florian Lohoff
2008-01-17 10:00 ` Thomas Bogendoerfer
2008-01-17 15:10 ` Ralf Baechle
2008-01-19 19:12 ` Thomas Bogendoerfer
2008-01-17 11:59 ` Ralf Baechle
2008-01-22 15:20 ` Kumba
2008-01-22 15:49 ` Ralf Baechle
2008-01-26 3:12 ` Kumba
2008-01-26 14:39 ` Thomas Bogendoerfer
2008-02-02 22:08 ` Kumba
2008-02-03 2:16 ` Ralf Baechle
2008-02-03 6:27 ` Florian Lohoff
2008-02-05 7:11 ` Kumba
2008-02-05 12:22 ` Thiemo Seufer
2008-02-06 3:25 ` Kumba
2008-02-06 8:56 ` Florian Lohoff
2008-02-06 14:22 ` Ralf Baechle
2008-02-08 17:23 ` Florian Lohoff
2008-02-08 19:05 ` Thiemo Seufer
2008-02-08 19:29 ` Ralf Baechle
2008-02-07 5:30 ` Kumba
2008-02-05 15:23 ` Ralf Baechle
2008-01-23 8:47 ` peter fuerst
2008-01-15 13:11 ` Ralf Baechle [this message]
2008-01-15 13:53 ` Ralf Baechle
2008-01-15 18:18 ` Ralf Baechle
2008-01-16 16:03 ` Ralf Baechle
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=20080115131145.GA5189@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.