| To: | jim.houston@xxxxxxxxx |
|---|---|
| Subject: | Re: SMP patche i386 |
| From: | Ethan Solomita <ethan@xxxxxxxxxxxxxxx> |
| Date: | Tue, 07 May 2002 02:06:42 -0700 |
| Cc: | kdb@xxxxxxxxxxx |
| References: | <200205030350.g433oHe01117@linux.local> <3CD69913.8DF9A523@attbi.com> <3CD6DD85.CA1314E1@cs.columbia.edu> <3CD700A5.1A6F8E85@attbi.com> <3CD73AF4.28AAC77@cs.columbia.edu> <3CD75F3F.5B5A6E0F@attbi.com> |
| Sender: | owner-kdb@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc1) Gecko/20020417 |
Jim Houston wrote:
On the first boot I let the system come up to multi-user When I hit pause key it hung. Bummer! 8) It's gotta be a race condition (obviously), and so by printing more stuff you significantly change the timings. You might try turning off the official debugging and adding some extremely terse limited messages.more times. It seemed to be working. You might also look for some of the various while() loops in kdb() and kdb_main_loop() which wait for state to be set, and add a counter. If the loops run more than a certain amount of times, print out a message. Maybe take things one step at a time, and put a single print out at first entry in kdb_ipi, and then remove it and put another one further in. etc. Just some thoughts that come to mind. This can be quite a pain.
-- Ethan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: SMP patche i386, Jim Houston |
|---|---|
| Next by Date: | one more try (at SMP), Ethan Solomita |
| Previous by Thread: | Re: SMP patche i386, Jim Houston |
| Next by Thread: | one more try (at SMP), Ethan Solomita |
| Indexes: | [Date] [Thread] [Top] [All Lists] |