Bug ...

XP SP2 RC1
WinDbg 6.3.0011.1

!IrpFind either hangs or takes so god damned long you get tired of waiting
and hit reset.

This is AFTER setting pool tagging and enabling all in Verifier.


Gary G. Little
Seagate Technologies, LLC

On a crash dump, or on a serial connection?

I’ve always found it slow on a serial connection, but it should be zippy
enough on a crash dump or over a 1394 connection (or USB once you start
using that new option.)

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Monday, April 05, 2004 5:41 PM
To: Kernel Debugging Interest List
Subject: [windbg] Bug …

XP SP2 RC1
WinDbg 6.3.0011.1

!IrpFind either hangs or takes so god damned long you get tired of
waiting and hit reset.

This is AFTER setting pool tagging and enabling all in Verifier.


Gary G. Little
Seagate Technologies, LLC


You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Tony,

I’ve posted on the microsoft.public.windbg list, that so far I have
found the 6.3.0011.1 release to be unusable. The GUI is so slow that it was
crashing or locking up on me 4 or more times an hour. I have reverted to
the previous revision and in discussions with customers of mine they have
also. Personally, the newest WinDBG is the WORST BAG I"VE SEEN AND THAT
GOES BACK TO NT 3.5 DAYS!


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

“Tony Mason” wrote in message news:xxxxx@windbg…
On a crash dump, or on a serial connection?

I’ve always found it slow on a serial connection, but it should be zippy
enough on a crash dump or over a 1394 connection (or USB once you start
using that new option.)

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Monday, April 05, 2004 5:41 PM
To: Kernel Debugging Interest List
Subject: [windbg] Bug …

XP SP2 RC1
WinDbg 6.3.0011.1

!IrpFind either hangs or takes so god damned long you get tired of
waiting and hit reset.

This is AFTER setting pool tagging and enabling all in Verifier.


Gary G. Little
Seagate Technologies, LLC


You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

So this one makes a point on the left of my table.

Never change a running | Always stay up to date
system |
------------------------±-------------------------
|
||||| ||||| ||||| | ||||| ||||| |||||
||||| || | ||
|
|
|
Norbert.

“A bend in the road is not the end of the road, unless you fail to
make the turn.”
---- snip ----

also. Personally, the newest WinDBG is the WORST BAG I"VE SEEN AND THAT
GOES BACK TO NT 3.5 DAYS!
---- snip ----

What happened to the proposal Intel made to use USB2.0 for kernel debugging.
Every MB has USB, but 1394 seems to be a problem.

RE 1394 problems:
to add to the collection of 1394 complaints:

My system setup is NEC 1394 chip on board on the host and 1394 add-in card
with VIA chipset
on the target.

Debugguing is flaky. If it manages the initial breakpoint, it mostly works
OK, but it doesn’t manage always :frowning:

I have tried all sorts of things like disabling 1394 adapters on host and/or
target, no SPB devices on the same bus… I even used 1394 drivers from sp2
on the host, it remains flaky.
I 'm thinking of spending somewhat more money and getting 1394 cards with
(the one and only real…) TI chipsets.

All this and the numerous ‘delayed write failed’ problems with the storage
stack is making me believe that MS as a whole has some kind of general
problem with 1394.

Robin Mitra

-----Original Message-----
From: Norbert Kawulski [mailto:xxxxx@stollmann.de]
Sent: Dienstag, 6. April 2004 10:07
To: Kernel Debugging Interest List
Subject: Re: [windbg] Bug …

So this one makes a point on the left of my table.

Never change a running | Always stay up to date
system |
------------------------±-------------------------
|
||||| ||||| ||||| | ||||| ||||| |||||
||||| || | ||
|
|
|
Norbert.

“A bend in the road is not the end of the road, unless you fail to
make the turn.”
---- snip ----
> also. Personally, the newest WinDBG is the WORST BAG I"VE
SEEN AND THAT
> GOES BACK TO NT 3.5 DAYS!
---- snip ----


You are currently subscribed to windbg as: xxxxx@exgate.tek.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Tony,

Serial connection, live debug after the target panicked and crashed. I’m
looking for a memory corruption problem and wanted to see if I had any IRPs
that might give a hint, but irpfind takes a vacation.

Don, on this I disagree. 6.3.0011 has problems it’s predecessor did not, but
I do find it usable, having used it an average of 50 hours a week since I
downloaded it. I remember the days of 5.x when WinDbg crashed more
frequently than the target, and Numega almost got my money.

And irpfind has always been quirky.


Gary G. Little
Seagate Technologies, LLC

“Tony Mason” wrote in message news:xxxxx@windbg…
On a crash dump, or on a serial connection?

I’ve always found it slow on a serial connection, but it should be zippy
enough on a crash dump or over a 1394 connection (or USB once you start
using that new option.)

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Monday, April 05, 2004 5:41 PM
To: Kernel Debugging Interest List
Subject: [windbg] Bug …

XP SP2 RC1
WinDbg 6.3.0011.1

!IrpFind either hangs or takes so god damned long you get tired of
waiting and hit reset.

This is AFTER setting pool tagging and enabling all in Verifier.


Gary G. Little
Seagate Technologies, LLC


You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Gary,

I tried it again last night, after 5 crashes or hangs in an hour, I
stand by my statement. My customers have seen even a higher frequency.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

“Gary G. Little” wrote in message
news:xxxxx@windbg…
> Tony,
>
> Serial connection, live debug after the target panicked and crashed. I’m
> looking for a memory corruption problem and wanted to see if I had any
IRPs
> that might give a hint, but irpfind takes a vacation.
>
> Don, on this I disagree. 6.3.0011 has problems it’s predecessor did not,
but
> I do find it usable, having used it an average of 50 hours a week since I
> downloaded it. I remember the days of 5.x when WinDbg crashed more
> frequently than the target, and Numega almost got my money.
>
> And irpfind has always been quirky.
>
> –
> Gary G. Little
> Seagate Technologies, LLC
>
> “Tony Mason” wrote in message news:xxxxx@windbg…
> On a crash dump, or on a serial connection?
>
> I’ve always found it slow on a serial connection, but it should be zippy
> enough on a crash dump or over a 1394 connection (or USB once you start
> using that new option.)
>
> Regards,
>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
> Sent: Monday, April 05, 2004 5:41 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Bug …
>
> XP SP2 RC1
> WinDbg 6.3.0011.1
>
> !IrpFind either hangs or takes so god damned long you get tired of
> waiting and hit reset.
>
> This is AFTER setting pool tagging and enabling all in Verifier.
>
> –
> Gary G. Little
> Seagate Technologies, LLC
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@osr.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
>

Like me and 1394 debugging. It never works for me.

I remember once when I agreed to assume a mailing list for a Barbershop
chapter of which I was a member. I had to enter over 6000 names and
addresses using a Lisa running as a Macintosh and using a Mac database
program. 2 other members (retirees) volunteered to help. I’d set things up
for them in the morning and then go to work, leaving them to enter data as
long as they had time. All three of us used the same software to do the same
job. But I swear to god, that machine HATED Johnny. When he was doing data
entry, he was forever having problems, where as Bill and I never had one.

Sometimes I think software just simply hates us.


Gary G. Little
Seagate Technologies, LLC

“Don Burn” wrote in message news:xxxxx@windbg…
> Gary,
>
> I tried it again last night, after 5 crashes or hangs in an hour, I
> stand by my statement. My customers have seen even a higher frequency.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>
>
> “Gary G. Little” wrote in message
> news:xxxxx@windbg…
> > Tony,
> >
> > Serial connection, live debug after the target panicked and crashed. I’m
> > looking for a memory corruption problem and wanted to see if I had any
> IRPs
> > that might give a hint, but irpfind takes a vacation.
> >
> > Don, on this I disagree. 6.3.0011 has problems it’s predecessor did not,
> but
> > I do find it usable, having used it an average of 50 hours a week since
I
> > downloaded it. I remember the days of 5.x when WinDbg crashed more
> > frequently than the target, and Numega almost got my money.
> >
> > And irpfind has always been quirky.
> >
> > –
> > Gary G. Little
> > Seagate Technologies, LLC
> >
> > “Tony Mason” wrote in message news:xxxxx@windbg…
> > On a crash dump, or on a serial connection?
> >
> > I’ve always found it slow on a serial connection, but it should be zippy
> > enough on a crash dump or over a 1394 connection (or USB once you start
> > using that new option.)
> >
> > Regards,
> >
> > Tony
> >
> > Tony Mason
> > Consulting Partner
> > OSR Open Systems Resources, Inc.
> > http://www.osr.com
> >
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
> > Sent: Monday, April 05, 2004 5:41 PM
> > To: Kernel Debugging Interest List
> > Subject: [windbg] Bug …
> >
> > XP SP2 RC1
> > WinDbg 6.3.0011.1
> >
> > !IrpFind either hangs or takes so god damned long you get tired of
> > waiting and hit reset.
> >
> > This is AFTER setting pool tagging and enabling all in Verifier.
> >
> > –
> > Gary G. Little
> > Seagate Technologies, LLC
> >
> >
> >
> > —
> > You are currently subscribed to windbg as: xxxxx@osr.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> >
> >
> >
>
>
>