I believe we do have a warning if we detect that this will happen when one tries to issue a .dump, FWIW.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Tuesday, June 21, 2011 9:10 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] remote kernel debugging on windows vista home premium?
That’s pretty funny, so your debug connection could go from blazing fast
1394 DMA madness to poky and you’d basically be left scratching your head.
Definitely a good thing to keep in mind.
Thanks!
-scott
–
Scott Noone
Consulting Associate and Chief System Problem Analyst OSR Open Systems Resources, Inc.
http://www.osronline.com
“Skywing” wrote in message news:xxxxx@windbg…
Yes, there is.
As I recall, without PhysicalUpperBound support, the debugger is unable to DMA memory above 4GB from the target to the host. This forces the debugger back to the same (slower) mechanism that the other debugger transports have to use for memory reads from the host which means that operations such as writing a dump out from the 1394 link will go much slower than they would on a machine with PhysicalUpperBound (or physical addresses <4GB).
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Tuesday, June 21, 2011 5:40 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] remote kernel debugging on windows vista home premium?
Furthermore TI cards are not ideal for x64 machines with 4GB or more of
RAM given that they do not support the PhysicalUpperBound >register
that LSI hardware (523 chips and later) supports.
Learn something new every day…When you say, “not ideal”, is there a noticeable difference when working with a card that supports this versus one that doesn’t? Obviously it’s going to depend greatly on the memory ranges that you’re looking at, but just curious.
Thanks!
-scott
–
Scott Noone
Consulting Associate and Chief System Problem Analyst OSR Open Systems Resources, Inc.
http://www.osronline.com
“Joe Ballantyne” wrote in message news:xxxxx@windbg…
You don’t have to buy OSR’s TI cards. You can, and probably should given the amount of support you are getting from the site, but ~$10 cards from www.newegg.com should work just fine as long as you use the latest debugger.
Furthermore TI cards are not ideal for x64 machines with 4GB or more of RAM given that they do not support the PhysicalUpperBound register that LSI hardware (523 chips and later) supports.
If I were you I would just get the cheapest Rosewill 1394a cards I could find on Newegg. As long as you use the latest debugger release (specified below), it should work with any OHCI 1394 card in the target machine.
If you don’t have any PCI slots in the newer of your machines, only PCI express, and the machine doesn’t already have 1394, then you will need 1 PCI and 1 PCI express card. The PCI express cards cost more $, but if your machine only has PCI express slots available, then you have no choice.
Read this:
http://en.wikipedia.org/wiki/1394a
Make SURE that neither of you computers has a plug that looks like the plug in the picture of the addin card.
If either do, then you actually already have a 1394 controller, it is just disabled in the BIOS, and you need to go into the BIOS and enable it.
(F2, or Del usually get you into the BIOS configuration.)
DO NOT PUT A 1394 CARD IN YOUR MACHINE, IF IT ALREADY HAS A 1394 CONTROLLER.
If either of your machines has a plug anywhere on it that matches the picture of the plug of the addin 1394 card on Wikipedia, then it HAS a 1394 controller, just figure out how to enable it so it shows up in Windows device manager.
Make sure your debugger is at least 6.12.2.633. If not, then go get it from the Microsoft website.
Read this:
http://en.wikipedia.org/wiki/WinDbg
The link to the Microsoft website to get the debugger is on the RHS in the box.
In windbg, click on the help menu, then click on search.
Type 1394 in the search box and press enter. You should get lots of hits.
Read them.
Bcdedit also gives lots of hits;
Read them.
To enable 1394 debugging on a vista target machine:
Run an elevated (admin privileges) command prompt then type
Bcdedit -dbgsettings 1394 channel:1
Bcdedit -debug on
Then in the host machine open an elevated command prompt, and run
Windbg -k 1394:channel=1
Press ctrl-alt-k twice. (should say will breakin at first symbol load)
Then reboot the target machine.
(shutdown -r -t 0 in the command prompt)
You should connect at boot and the debugger will breakin.
Press g to let the machine boot.
Joe.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
Sent: Monday, June 20, 2011 4:46 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] RE: remote kernel debugging on windows vista home
premium?
Setting up a session after I have all hardware in place is not a problem.
But so far I used only null-modem cable that is why I am asking so many
questions.
To summarize:
I need two 1394 PCI cards (one regular, one express), a cable, and two
available PCI slots.
Anything else?
KD and WinDbg will be able to use the cards.
That’s should be all, correct?
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer