Re: 1394 + WinXP SP2
From: Arne Caspari (arne_caspari_at_nospam)
Date: 08/12/04
- Next message: Hablu: "DmaOperations (_DMA_ADAPTER) compile problem"
- Previous message: Maxim S. Shatskih: "Re: scsi miniports DriverEntry is called but on other function..."
- In reply to: Philip Lukidis: "Re: 1394 + WinXP SP2"
- Next in thread: Philip Lukidis: "Re: 1394 + WinXP SP2"
- Reply: Philip Lukidis: "Re: 1394 + WinXP SP2"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 12 Aug 2004 16:21:49 +0200
Philip Lukidis wrote:
> [snip]
>
> Your driver symbols to not appear to be correct (or the symbols have been
> unloaded as your driver seems to have been, see below), best that you use
> current driver symbols for a stack trace. I have not used the DDK 1394
> samples, so I am not familiar with their structure. But the first entry in
> the trace seems to indicate that your driver has unloaded (hence its symbols
> have been unloaded as well) without having unregistered its bus reset
> routine. Verify that you are unregistering for bus reset notification along
> all unload paths for your device.
Right, the bus reset routine was not unregistered but it should since
HwInitialize returned with an error.
I have fixed that now but I still can not send a single asynchronous
packet after I unplug/replug the device.
Have you tested your device with the SP2 yet? If I uninstall SP2,
everything is fine again...
Thanks,
Arne
- Next message: Hablu: "DmaOperations (_DMA_ADAPTER) compile problem"
- Previous message: Maxim S. Shatskih: "Re: scsi miniports DriverEntry is called but on other function..."
- In reply to: Philip Lukidis: "Re: 1394 + WinXP SP2"
- Next in thread: Philip Lukidis: "Re: 1394 + WinXP SP2"
- Reply: Philip Lukidis: "Re: 1394 + WinXP SP2"
- Messages sorted by: [ date ] [ thread ]