Hi,
The key wasn’t there because I’ve moved to debugging using the com port
instead of firewire :).
When I boot the target machine with /debugport=1394 the key is there, but
still no debugging for me…
As I mentioned before, at some occasions when I try to break-in using
windbg, the target machine will hang but I will get no response from windbg.
Here is the contents of the registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCI\Debug]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCI\Debug\0]
“Bus”=dword:00000005
“Slot”=dword:00000009
“DebugAddress”=hex(b):08,01,02,00,00,00,00,00
“NoBus”=dword:00000000
Shahar
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Monday, April 18, 2005 8:13 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 Debugging with XP+SP2 host
If that key isn’t there on the target system, then 1394 debug won’t work.
It means that the hal failed to find and initialize the 1394 controller
(seen mostly on laptops/tablets, not so much desktops). What is the
make/model of the target system?
Which brings up an interesting issue. You said debug worked previously,
although the absense of they reg key suggests that it should never work,
regardless of host. Can you confirm this key’s existence on a 1394 debug
session which is currently working for you?
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Monday, April 18, 2005 11:45 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 Debugging with XP+SP2 host
I’ve upgraded the host machines to use SP2. My target machines are also
running with SP2, but the problems only started when I upgraded the host
machines.
I have no such key on my target machines. Am I supposed to?
Thanks,
Shahar
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Monday, April 18, 2005 6:20 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 Debugging with XP+SP2 host
Upgraded the host machine like in your previous example, or upgraded target
machines to SP2?
Does this key exist on the target systems?
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\PCI\Debug
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Sunday, April 17, 2005 4:51 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 Debugging with XP+SP2 host
Hi,
I’ve installed SP2 on two other machines and got the same problem…
Is there anything I might be doing wrong?
Shahar
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Friday, April 15, 2005 3:31 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] 1394 Debugging with XP+SP2 host
Hi Jason,
I’m not using a hub and I’ve tried re-pluging the cable and also plugging it
in other ports on the bus. Nothing helped. This problem is consistent,
rebooting any of the machines doesn’t work either.
Shahar
“Jason Shay” wrote in message
news:xxxxx@windbg…
I have seen this on my dev box from time to time, and if I remember
correctly, it means the bus state is a little funny. I fix it by unplugging
and replugging in the cables. Are you using a hub, as I’ve also heard of
some 1394 hubs causing problems in this area…
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Thursday, April 14, 2005 2:52 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 Debugging with XP+SP2 host
Hi Jason,
When pressing ctrl-D in kd I’m getting the following output repeatedly:
“
READ: Error 80070014.
READ: Wait for type 7 packet
”
(80070014 = The system cannot find the device specified.)
Shahar
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Thursday, April 14, 2005 9:57 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] 1394 Debugging with XP+SP2 host
It is somewhat surprising, actually. We’ve seen nothing but improvements
for the 1394 debug experience in XPSP2. What happens if
you:
Start kd, and press “ctrl-D” in KD. Then boot the 1394 target?
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Thursday, April 14, 2005 1:47 PM
To: Kernel Debugging Interest List
Subject: [windbg] 1394 Debugging with XP+SP2 host
Hi,
Since I installed SP2 on my machine I’m not able to break into targets using
1394 debugging.
WinDbg just says:
“Using 1394 for debugging
Opened \.\DBG1394_INSTANCE10
Waiting to reconnect…”
And nothing happens. When I’m starting windbg with “-b” option and reboot
the target machine, The target machine will hang during boot, but still no
response from windbg.
After uninstalling SP2 from the host everything works fine again.
Is there something I need to configure so this will work on SP2? Is there a
known bug in windbg for this?
Am I doing something wrong?
Thanks,
Shahar
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@safend.com To unsubscribe
send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com