From: Andrew Morton <akpm@osdl.org>
To: "Dale E Martin" <dmartin@cliftonlabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: repeatable, hard lockup on boot in linux-2.6.0-test4 (more details)
Date: Mon, 1 Sep 2003 15:28:09 -0700 [thread overview]
Message-ID: <20030901152809.0311f46f.akpm@osdl.org> (raw)
In-Reply-To: <20030901195706.GA853@cliftonlabs.com>
"Dale E Martin" <dmartin@cliftonlabs.com> wrote:
>
> > Are you able to plug any PS/2 devices into the machine, see if that makes
> > a difference?
>
> Yes, plugging in a PS/2 mouse in addition to the USB mouse does allow the
> machine to boot up. (Just tried it, thanks for the suggestion.)
OK, don't go away yet ;)
Could you please add this patch and see how far it gets? If you're keen,
keep adding more DB() statements, narrow it down further?
drivers/input/serio/i8042.c | 23 ++++++++++++++++++-----
include/linux/kernel.h | 1 +
2 files changed, 19 insertions(+), 5 deletions(-)
diff -puN drivers/input/serio/i8042.c~a drivers/input/serio/i8042.c
--- 25/drivers/input/serio/i8042.c~a 2003-09-01 15:24:02.000000000 -0700
+++ 25-akpm/drivers/input/serio/i8042.c 2003-09-01 15:25:31.000000000 -0700
@@ -831,36 +831,49 @@ int __init i8042_init(void)
{
int i;
+ DB();
dbg_init();
+ DB();
if (i8042_platform_init())
return -EBUSY;
i8042_aux_values.irq = I8042_AUX_IRQ;
i8042_kbd_values.irq = I8042_KBD_IRQ;
+ DB();
if (i8042_controller_init())
return -ENODEV;
+ DB();
if (i8042_dumbkbd)
i8042_kbd_port.write = NULL;
- for (i = 0; i < 4; i++)
+ for (i = 0; i < 4; i++) {
+ DB();
i8042_init_mux_values(i8042_mux_values + i, i8042_mux_port + i, i);
+ }
- if (!i8042_nomux && !i8042_check_mux(&i8042_aux_values))
- for (i = 0; i < 4; i++)
+ if (!i8042_nomux && !i8042_check_mux(&i8042_aux_values)) {
+ for (i = 0; i < 4; i++) {
+ DB();
i8042_port_register(i8042_mux_values + i, i8042_mux_port + i);
- else
- if (!i8042_noaux && !i8042_check_aux(&i8042_aux_values))
+ }
+ } else {
+ if (!i8042_noaux && !i8042_check_aux(&i8042_aux_values)) {
+ DB();
i8042_port_register(&i8042_aux_values, &i8042_aux_port);
+ }
+ }
+ DB();
i8042_port_register(&i8042_kbd_values, &i8042_kbd_port);
init_timer(&i8042_timer);
i8042_timer.function = i8042_timer_func;
mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
+ DB();
register_reboot_notifier(&i8042_notifier);
return 0;
diff -puN include/linux/kernel.h~a include/linux/kernel.h
--- 25/include/linux/kernel.h~a 2003-09-01 15:24:02.000000000 -0700
+++ 25-akpm/include/linux/kernel.h 2003-09-01 15:25:55.000000000 -0700
@@ -236,4 +236,5 @@ extern void BUILD_BUG(void);
#define __FUNCTION__ (__func__)
#endif
+#define DB() printk("%s:%d\n", __FILE__, __LINE__)
#endif
_
next prev parent reply other threads:[~2003-09-01 22:27 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 [this message]
2003-09-02 0:31 ` Dale E Martin
2003-09-02 1:23 ` Andrew Morton
2003-09-02 12:30 ` Dale E Martin
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=20030901152809.0311f46f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=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