| To: | jim.houston@xxxxxxxxx |
|---|---|
| Subject: | Re: SMP patche i386 |
| From: | Ethan Solomita <ethan@xxxxxxxxxxxxxxx> |
| Date: | Mon, 06 May 2002 19:24:52 -0700 |
| Cc: | kdb@xxxxxxxxxxx |
| References: | <200205030350.g433oHe01117@linux.local> <3CD69913.8DF9A523@attbi.com> <3CD6DD85.CA1314E1@cs.columbia.edu> <3CD700A5.1A6F8E85@attbi.com> |
| Sender: | owner-kdb@xxxxxxxxxxx |
As an update -- the other problem I was having with my sparc64 8p
system was an I/O driver related issue, not a kdb thing. With the
two-line fix I just emailed, I can't reproduce a problem on my sparc64
8p anymore. Jim -- do you have any specific sequences of kdb commands
that typically make things go wrong? Do the problems still occur when
you set kdb_flags to 0xffff0000 to get all the debugging info?
-- Ethan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: SMP patche i386, Ethan Solomita |
|---|---|
| Next by Date: | Re: SMP patche i386, Jim Houston |
| Previous by Thread: | Re: SMP patche i386, Ethan Solomita |
| Next by Thread: | Re: SMP patche i386, Jim Houston |
| Indexes: | [Date] [Thread] [Top] [All Lists] |