From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: Markus Dahms <mad@automagically.de>
Cc: sparclinux <sparclinux@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Odp: possible endless loop in PROM initialization
Date: Mon, 20 Aug 2007 10:50:28 +0200 [thread overview]
Message-ID: <46c955d43d407@wp.pl> (raw)
In-Reply-To: <20070820075949.GA5927@vimes.madsworld.lan>
Dnia 20-08-2007 o godz. 9:59 Markus Dahms napisał(a):
> Hey,
>
> while trying to define a non-unique devalias at the Sun PROM prompt
> (the SPARCclassic X has wrong aliases for scsi, disk1, etc. in the
> PROM, at least mine) I fell over a bug resulting in an endless loop
> while booting the kernel.
>
> The problem is the getting the properties list of the /aliases
node.
> As the next element in this list is identified by name and the
> function which retrieves this property always returns the first
> occurrence this goes forever....
>
Could you give name of the function which contains this endless loop?
When I looked into the tree.c file for the first time I thought
it had a bug
in handling the prom_nextprop, but later I concluded that this is ok.
Maybe there is a bug there after all.
Regards,
Krzysztof
----------------------------------------------------
Wielka siatkówka we wrześniu w Starych Jabłonkach
zobacz gwiazdy siatkówki plażowej na żywo!
Mistrzostwa Świata w siatkówce plażowej 5-9.09.2007
Kliknij: http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fstarejablonki.html&sid=1262
next prev parent reply other threads:[~2007-08-20 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 7:59 possible endless loop in PROM initialization Markus Dahms
2007-08-20 8:06 ` David Miller
2007-08-20 10:53 ` Markus Dahms
2007-08-20 11:43 ` Chris Newport
2007-08-20 13:19 ` Markus Dahms
2007-08-20 18:19 ` Krzysztof Helt
2007-08-20 8:50 ` Krzysztof Helt [this message]
2007-08-20 10:34 ` Odp: " Markus Dahms
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=46c955d43d407@wp.pl \
--to=krzysztof.h1@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mad@automagically.de \
--cc=sparclinux@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