NDISulator bug on amd64

[Paul B Mahol]

On 1/16/10, Paul B Mahol <onemda at gmail.com> wrote:
> On 1/11/10, Paul B Mahol <onemda at gmail.com> wrote:
>> On 1/11/10, Bob Johnson <fbsdlists at gmail.com> wrote:
>>> On 1/9/10, Paul B Mahol <onemda at gmail.com> wrote:
>>>> On 12/16/09, Bob Johnson <fbsdlists at gmail.com> wrote:
>>>>> I'm using an ExpressCard for wireless networking because there seems
>>>>> to be no driver for the internal card in my laptop (and NDIS panics
>>>>> the system). The Expresscard shows up as a PCI device and works fine,
>>>>
>>>> How are you using NDIS and when system panic what is displayed?
>>>
>>> I tried to use ndisgen with the internal Dell 1397 card. I don't have
>>> details available right now, although if you need them I can try it
>>> again. When I did the kldload the system spit out error messages about
>>> unknown symbols and then panic-ed. I did some searching of the
>>> archives and found a message describing the same symptoms, and the
>>> response posted was that it indicated that the Windows driver made API
>>> calls that were not implemented in the NDIS wrapper.
>>>
>>> This was a 64-bit Windows driver and an amd64 FreeBSD system. Similar
>>> results in both
>>> FreeBSD 7.2 and 8.0.
>>>
>>> It appears that kern/132672 is describing the same or a very similar
>>> issue.  It also suggests that there is a more fundamental problem than
>>> the unrecognized symbols.
>>>
>>> I can try to reproduce the problem tonight if you want me to.
>>>
>>> Thanks,
>>
>> If you have debug kernel, then make breakpoint for MSCALL2 (kldload
>> ndis.ko before that): `break MSCALL2'
>
> Should be `break w86_64_call2'
>> Then load ndisgen module.
>>
>> Then single step it with `s' it should panic after few steps.
>> At least this is issue I'm experiencing on amd64, it fails in
>> DriverEntry().
>
> with the same virtual address as in kern/132672.

I fixed bug that caused panic on amd64 in DriverEntry().

Code is available from here:

www.gitorious.org/NDISulator