From: Marc ZYNGIER <mzyngier@freesurf.fr>
To: Alexander Viro <viro@math.psu.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
"David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac14
Date: 16 Jun 2001 10:20:46 +0200 [thread overview]
Message-ID: <wrpn178u97l.fsf@hina.wild-wind.fr.eu.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0106160322510.10605-100000@weyl.math.psu.edu>
In-Reply-To: Alexander Viro's message of "Sat, 16 Jun 2001 03:37:15 -0400 (EDT)"
>>>>> "Al" == Alexander Viro <viro@math.psu.edu> writes:
Al> Very odd. Could somebody try vanilla 2.4.6-pre1 on a PPC box? I _really_
Al> doubt that it might be an architecture-specific problem in directory
Al> code - it would simply fail the lookup for /dev in that case.
I have 2.4.6-pre3 running. Machine is a PowerMac clone with a G3 CPU.
It gets loads of bogus interrupts (known problem with this machine),
but otherwise runs fine (that is, for the time being).
maz@crisis:~$ uname -a
Linux crisis 2.4.6-pre3 #1 Sat Jun 16 01:35:36 CEST 2001 ppc unknown
maz@crisis:~$ cat /proc/cpuinfo
processor : 0
cpu : 750
temperature : 0 C
clock : 240MHz
revision : 2.2
bogomips : 478.91
zero pages : total: 0 (0Kb) current: 0 (0Kb) hits: 0/0 (0%)
machine : Power Macintosh
motherboard : AAPL,e407 MacRISC
memory : 144MB
l2cr override : 0xa5000000
pmac-generation : OldWorld
Al> I'll try to find a PPC nearby, but it may be tricky on weekend. So
Al> if somebody wants to help... Notice that problem was on read-only
Al> mount, so it can be tested without risking fs corruption - just
Al> try to boot with init=/bin/sh and do ls -lR, etc.
Been there, done that. Just works.
Would 2.4.6-pre1 be a better test ? I can dig into that if you want.
M.
--
Places change, faces change. Life is so very strange.
next prev parent reply other threads:[~2001-06-16 8:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200106162255.SAA02119@olimpo.networx.com.br.suse.lists.linux.kernel>
[not found] ` <E15B0vv-000780-00@the-village.bc.nu.suse.lists.linux.kernel>
[not found] ` <15146.33742.299279.102372@pizda.ninka.net.suse.lists.linux.kernel>
2001-06-16 5:57 ` Linux 2.4.5-ac14 Andi Kleen
2001-06-16 6:15 ` Alexander Viro
2001-06-16 7:37 ` Alexander Viro
2001-06-16 8:20 ` Marc ZYNGIER [this message]
2001-06-16 8:36 ` Alexander Viro
2001-06-17 20:47 ` Olaf Hering
2001-06-16 16:33 ` David S. Miller
2001-06-16 19:53 ` pci_disable_device() vs. arch Benjamin Herrenschmidt
2001-06-16 20:06 ` Jeff Garzik
2001-06-16 20:32 ` Benjamin Herrenschmidt
2001-06-16 20:45 ` Jeff Garzik
2001-06-16 21:14 ` Benjamin Herrenschmidt
2001-06-16 21:28 ` Jeff Garzik
2001-06-16 23:23 ` Benjamin Herrenschmidt
2001-06-15 2:33 Linux 2.4.5-ac14 Dieter Nützel
2001-06-15 2:30 ` John Cavan
2001-06-15 3:32 ` Dieter Nützel
2001-06-15 4:55 ` Dieter Nützel
[not found] ` <200106150442.AAA22505@spqr.damncats.org>
2001-06-15 11:24 ` John Cavan
2001-06-15 10:01 ` Christoph Rohland
-- strict thread matches above, loose matches on Subject: below --
2001-06-14 22:44 Alan Cox
2001-06-15 21:05 ` Thiago Vinhas de Moraes
2001-06-15 21:15 ` Alan Cox
2001-06-15 21:37 ` Andreas Dilger
2001-06-16 20:56 ` Thiago Vinhas de Moraes
2001-06-16 21:14 ` Arnaldo Carvalho de Melo
2001-06-15 21:53 ` David S. Miller
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=wrpn178u97l.fsf@hina.wild-wind.fr.eu.org \
--to=mzyngier@freesurf.fr \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).