From: "Dale E Martin" <dmartin@cliftonlabs.com>
To: linux-kernel@vger.kernel.org
Subject: Re: repeatable, hard lockup on boot in linux-2.6.0-test4 (more details)
Date: Tue, 2 Sep 2003 08:30:50 -0400 [thread overview]
Message-ID: <20030902123050.GA854@cliftonlabs.com> (raw)
In-Reply-To: <20030901182335.4c2e220f.akpm@osdl.org>
(I hadn't noticed the call to i8042_check_mux inside the if statement
condition after the loop, doh!)
> Can you try this one please?
Yes, this time it did this loop 4 times:
for (i = 0; i < 4; i++) {
DB();
i8042_init_mux_values(i8042_mux_values + i, i8042_mux_port + i, i);
}
And then I got one more at 590, inside i8042_check_mux:
DB();
if (request_irq(values->irq, i8042_interrupt, SA_SHIRQ,
"i8042", i8042_request_irq_cookie))
return -1;
DB();
This last one did not show up, nor did any inside the conditional loops at
line 878 or 883, nor at line 888. So perhaps it was in request_irq that it
locked up?
I'll be away from this machine for the day, although I can try something
new this evening.
Take care,
Dale
--
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
dmartin@cliftonlabs.com
http://www.cliftonlabs.com
pgp key available
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
(I hadn't noticed the call to i8042_check_mux inside the if statement
condition after the loop, doh!)
> Can you try this one please?
Yes, this time it did this loop 4 times:
for (i = 0; i < 4; i++) {
DB();
i8042_init_mux_values(i8042_mux_values + i, i8042_mux_port + i, i);
}
And then I got one more at 590, inside i8042_check_mux:
DB();
if (request_irq(values->irq, i8042_interrupt, SA_SHIRQ,
"i8042", i8042_request_irq_cookie))
return -1;
DB();
This last one did not show up, nor did any inside the conditional loops at
line 878 or 883, nor at line 888. So perhaps it was in request_irq that it
locked up?
I'll be away from this machine for the day, although I can try something
new this evening.
Take care,
Dale
--
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
dmartin@cliftonlabs.com
http://www.cliftonlabs.com
pgp key available
next prev parent reply other threads:[~2003-09-02 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 15:33 repeatable, hard lockup on boot in linux-2.6.0-test4 Dale E Martin
2003-09-01 18:23 ` repeatable, hard lockup on boot in linux-2.6.0-test4 (more details) Dale E Martin
2003-09-01 19:04 ` Andrew Morton
2003-09-01 19:57 ` Dale E Martin
2003-09-01 22:28 ` Andrew Morton
2003-09-02 0:31 ` Dale E Martin
2003-09-02 1:23 ` Andrew Morton
2003-09-02 12:30 ` Dale E Martin [this message]
2003-09-02 20:03 ` Andrew Morton
2003-09-02 23:45 ` Chris Wright
2003-09-03 12:41 ` Dale E Martin
2003-09-02 11:04 ` repeatable, hard lockup on boot in linux-2.6.0-test4 Maciej Freudenheim
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=20030902123050.GA854@cliftonlabs.com \
--to=dmartin@cliftonlabs.com \
--cc=linux-kernel@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