Hi,
Ok, it looks like it's something deep in the ndis driver itself, and
it's likely that we've not set it all up right.
Trouble is, no, you likely won't get symbols from the .dll. :-) So
someone who likes assembly and can read the NDIS spec needs to figure
it out.
Sorry!
-a
On 29 July 2016
On 07/20/2016 15:34, Adrian Chadd wrote:
it's doing that for transmitting packets. can you load the crashdump
into kgdb and get a debug backtrace?
and/or /var/crash/core.txt.X ?
Hi Adrian,
My kgdb kernel crash stack is below.
Do you know is there a way to also generate .symbols file for
On 07/20/2016 15:34, Adrian Chadd wrote:
it's doing that for transmitting packets. can you load the crashdump
into kgdb and get a debug backtrace?
and/or /var/crash/core.txt.X ?
kgdb shows that the crash occurs in ndis_bcmwl564_sys_drv_data_start().
#5 0x80d5c1dd in trap_pfault
