From: Jeremy Jackson <jerj@coplanar.net>
To: linux-ide@vger.kernel.org
Subject: 2.4.23 IDE hang on boot with two single-channel controllers
Date: Mon, 26 Jan 2004 09:44:49 -0500 [thread overview]
Message-ID: <401527E1.6040108@coplanar.net> (raw)
Hi All,
Already posted this to linux-kernel.
kdb shows proc_ide_create() stuck in a loop when booting on a Compaq
Armada 7730MT while attached to the docking station.
This is a unique IDE hardware setup. Channel ide0's controller is in
the laptop, while ide1 is a separate controller (pci device) in the
docking station and is not always present.
This seems to be triggering a bug in ide-proc.c:
void proc_ide_create(void)
{
#ifdef CONFIG_BLK_DEV_IDEPCI
ide_pci_host_proc_t *p = ide_pci_host_proc_list;
#endif /* CONFIG_BLK_DEV_IDEPCI */
proc_ide_root = proc_mkdir("ide", 0);
if (!proc_ide_root) return;
create_proc_ide_interfaces();
create_proc_read_entry("drivers", 0, proc_ide_root,
proc_ide_read_drivers, NULL);
#ifdef CONFIG_BLK_DEV_IDEPCI
while (p != NULL) <------------------- INFINITE LOOP HERE
{
if (p->name != NULL && p->set == 1 && p->get_info != NULL)
{
p->parent = proc_ide_root;
create_proc_info_entry(p->name, 0, p->parent,
p->get_info);
p->set = 2;
}
p = p->next;
}
#endif /* CONFIG_BLK_DEV_IDEPCI */
}
I'm not sure if the problem is in the loop or bad data being setup
before it starts.
Assistance fixing it would be appreciated.
Regards,
Jeremy Jackson
next reply other threads:[~2004-01-26 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 14:44 Jeremy Jackson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-26 15:56 2.4.23 IDE hang on boot with two single-channel controllers Jeremy Jackson
2004-02-17 23:34 ` Bartlomiej Zolnierkiewicz
2004-02-24 17:49 ` Jeremy Jackson
2004-07-31 14:37 ` Marcelo Tosatti
2004-07-31 15:37 ` Jeremy Jackson
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=401527E1.6040108@coplanar.net \
--to=jerj@coplanar.net \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).