Hi folks,
Has anyone had any success debugging Windows (kernel mode) on a
BladeCenter? I’ve been unable to find a way to get windbg successfully
connected to a Windows target on a blade server.
On the target side, I enabled Serial over LAN (via COM2 at 19.2K, as
defined by IBM), and I attempted to connect to this on the windbg client
by setting up a virtual serial port on my windbg client, which is
implemented as a network connection to the BladeCenter’s Management
Module. Anyway, this was all non-trivial and fruitless.
Even though I was able to get serial traffic going back and forth, I
suspect that data is being dropped by either the MM or it’s serial over
LAN infrastructure. I just couldn’t connect the client to the target.
And I didn’t know of any other way to do this.
So, does anyone know? Is there a way? Short of a real serial
connection (which doesn’t exist outside the blade itself other than SOL)
and a non-existent firewire connection, I couldn’t come up with
anything. I suppose folks at IBM use some sort of physical dongle or
something, but what about the outside world of driver folks?
– Charlie
The debug target must either have the real RS-232 hardware (KDCOM.DLL uses
it, it cannot use serial-over-LAN), or the OHCI-compatible 1394 controller
(KD1394.DLL uses it).
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “Suffin, Charlie”
To: “Windows System Software Devs Interest List”
Sent: Friday, May 26, 2006 3:50 AM
Subject: [ntdev] Debugging Windows on an IBM BladeCenter
Hi folks,
Has anyone had any success debugging Windows (kernel mode) on a
BladeCenter? I’ve been unable to find a way to get windbg successfully
connected to a Windows target on a blade server.
On the target side, I enabled Serial over LAN (via COM2 at 19.2K, as
defined by IBM), and I attempted to connect to this on the windbg client
by setting up a virtual serial port on my windbg client, which is
implemented as a network connection to the BladeCenter’s Management
Module. Anyway, this was all non-trivial and fruitless.
Even though I was able to get serial traffic going back and forth, I
suspect that data is being dropped by either the MM or it’s serial over
LAN infrastructure. I just couldn’t connect the client to the target.
And I didn’t know of any other way to do this.
So, does anyone know? Is there a way? Short of a real serial
connection (which doesn’t exist outside the blade itself other than SOL)
and a non-existent firewire connection, I couldn’t come up with
anything. I suppose folks at IBM use some sort of physical dongle or
something, but what about the outside world of driver folks?
– Charlie
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer