devp-pccard Memory Fault

Hi,
I’m having some trouble with the devp-pccard server on an x86 system. If
pci-bios is running (which it is automatically) and I try to execute
devp-pccard it just returns with error message “Memory Fault”, but if I
slay pci-bios it works perfectly.
I’m not sure what the effects of slaying pci-bios are since so far I see
no difference except in PCMCIA, but I’m guessing there are downsides
to slaying it…
Well, what should I do? The PCMCIA controller is Intel 82092AA (or
something like that) compatible, it isn’t listed on the supported
hardware on qnx website, but my 3c589 network card works perfectly when
devp-pccard is running…

//David Holm

Please will you do the following:

  1. slay devp-pccard
  2. slay pci-bios
  3. pci-bios -vvv
  4. devp-pccard -vvv
  5. sloginfo > file
  6. Post the output ‘file’

Thanks, Hugh.

Previously, David Holm wrote in qdn.public.qnxrtp.os:

Hi,
I’m having some trouble with the devp-pccard server on an x86 system. If
pci-bios is running (which it is automatically) and I try to execute
devp-pccard it just returns with error message “Memory Fault”, but if I
slay pci-bios it works perfectly.
I’m not sure what the effects of slaying pci-bios are since so far I see
no difference except in PCMCIA, but I’m guessing there are downsides
to slaying it…
Well, what should I do? The PCMCIA controller is Intel 82092AA (or
something like that) compatible, it isn’t listed on the supported
hardware on qnx website, but my 3c589 network card works perfectly when
devp-pccard is running…

//David Holm

Hugh Brown wrote:

Please will you do the following:

  1. slay devp-pccard
  2. slay pci-bios
  3. pci-bios -vvv
  4. devp-pccard -vvv
  5. sloginfo > file
  6. Post the output ‘file’

Thanks, Hugh.

Previously, David Holm wrote in qdn.public.qnxrtp.os:

Hi,
I’m having some trouble with the devp-pccard server on an x86 system. If
pci-bios is running (which it is automatically) and I try to execute
devp-pccard it just returns with error message “Memory Fault”, but if I
slay pci-bios it works perfectly.
I’m not sure what the effects of slaying pci-bios are since so far I see
no difference except in PCMCIA, but I’m guessing there are downsides
to slaying it…
Well, what should I do? The PCMCIA controller is Intel 82092AA (or
something like that) compatible, it isn’t listed on the supported
hardware on qnx website, but my 3c589 network card works perfectly when
devp-pccard is running…

//David Holm

\

Thanks… Here is the log

You have an Omega Micro 82C092 chipset in your machine which we don’t
support. I don’t even have any documentation on this chipset. There is
something strange in the register setup that is causing devp-pccard to
fault.

Previously, David Holm wrote in qdn.public.qnxrtp.os:

Hugh Brown wrote:

Please will you do the following:

  1. slay devp-pccard
  2. slay pci-bios
  3. pci-bios -vvv
  4. devp-pccard -vvv
  5. sloginfo > file
  6. Post the output ‘file’

Thanks, Hugh.

Previously, David Holm wrote in qdn.public.qnxrtp.os:

Hi,
I’m having some trouble with the devp-pccard server on an x86 system. If
pci-bios is running (which it is automatically) and I try to execute
devp-pccard it just returns with error message “Memory Fault”, but if I
slay pci-bios it works perfectly.
I’m not sure what the effects of slaying pci-bios are since so far I see
no difference except in PCMCIA, but I’m guessing there are downsides
to slaying it…
Well, what should I do? The PCMCIA controller is Intel 82092AA (or
something like that) compatible, it isn’t listed on the supported
hardware on qnx website, but my 3c589 network card works perfectly when
devp-pccard is running…

//David Holm





Thanks… Here is the log
Time Sev Major Minor Args
Oct 23 21:05:48 5 17 0 pci_server: shutting down pci 8056428
Oct 23 21:05:49 5 6 200 Installing /dev/par port 378
Oct 23 21:13:19 1 8 0 1868982384 1482191982 1635021600 1684370546 541806368 1329930285 943128651
Oct 23 21:13:25 5 9 0 Start: /usr/photon/bin/devi-hirun kbd fd -d/dev/kbd ps2 mousedev

Oct 23 21:16:04 5 17 0 pci_server: Aug 23 2001 18:12:15
Oct 23 21:16:04 5 17 0 Low memory CPU 1000000 - PCI 1000000
Oct 23 21:16:04 5 17 0 High memory CPU ffefffff - PCI fff00000
Oct 23 21:16:04 5 17 0 Low port CPU 200 - PCI 200
Oct 23 21:16:04 5 17 0 High port CPU fefe - PCI feff
Oct 23 21:16:04 5 17 0 Found host bridge 0 0
Oct 23 21:16:04 5 17 0 Configure bridge - bus 0 - devfunc 0
Oct 23 21:16:04 5 17 0 cb Bus 0 - Devfn 0 - dword ff0000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 alloc_bus 0 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 0 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 406 Index 0 ClassCode 60000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Setup bridge 0 - Lastbus = 1
Oct 23 21:16:04 5 17 0 Bus 0 - Device 1 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 8 Index 0 ClassCode 60100
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 1 - Function 1
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 601 Index 0 ClassCode 10100
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Range failed 174 - 28c
Oct 23 21:16:04 3 17 0 Range check failed (IO) - Dev 601 - Vend 1039 - Class 10100 - Addr 174 - Size 28c
Oct 23 21:16:04 5 17 0 IO 174 28c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 174 - Size 28c
Oct 23 21:16:04 2 17 0 Alloc failed 175 - Size 28c
Oct 23 21:16:04 5 17 0 Range failed 1f4 - 20c
Oct 23 21:16:04 3 17 0 Range check failed (IO) - Dev 601 - Vend 1039 - Class 10100 - Addr 1f4 - Size 20c
Oct 23 21:16:04 5 17 0 IO 1f4 20c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 1f4 - Size 20c
Oct 23 21:16:04 2 17 0 Alloc failed 1f5 - Size 20c
Oct 23 21:16:04 5 17 0 IO 374 8c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 374 - Size 8c
Oct 23 21:16:04 2 17 0 Alloc failed 375 - Size 8c
Oct 23 21:16:04 5 17 0 IO 3f4 c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 3f4 - Size c
Oct 23 21:16:04 2 17 0 Alloc failed 3f5 - Size c
Oct 23 21:16:04 5 17 0 IO 174 28c
Oct 23 21:16:04 5 17 0 IO 1f4 20c
Oct 23 21:16:04 5 17 0 IO 374 8c
Oct 23 21:16:04 5 17 0 IO 3f4 c
Oct 23 21:16:04 5 17 0 Bus 0 - Device 6 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1023 Device 9660 Index 0 ClassCode 30000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 MEM 8000000 400000
Oct 23 21:16:04 5 17 0 MEM 8800000 10000
Oct 23 21:16:04 5 17 0 MEM 8400000 400000
Oct 23 21:16:04 5 17 0 ROM c0000 - 10000
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr c0000 - Size 10000
Oct 23 21:16:04 5 17 0 MEM 8000000 400000
Oct 23 21:16:04 5 17 0 MEM 8800000 10000
Oct 23 21:16:04 5 17 0 MEM 8400000 400000
Oct 23 21:16:04 5 17 0 Bus 0 - Device 13 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 119b Device 1221 Index 0 ClassCode 60500
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 IO 3e0 4
Oct 23 21:16:04 5 17 0 IO 3e0 4
Oct 23 21:16:04 5 17 0 reserve IRQ 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 14 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 119b Device 1221 Index 1 ClassCode 60500
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 IO 3e4 4
Oct 23 21:16:04 5 17 0 IO 3e4 4
Oct 23 21:16:04 5 17 0 reserve IRQ 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:27 5 17 0 io_open for id = 3
Oct 23 21:16:27 5 17 0 Alloc IRQ 7 - Flags c01
Oct 23 21:16:27 5 17 0 Alloc IRQ 7 - Flags c01
Oct 23 21:16:27 5 17 0 io_close_ocb
Oct 23 21:16:27 5 17 0 Free IRQ 7
Oct 23 21:16:27 5 17 0 IRQ Free Failed

Yes, I know you don’t support it, but still, it seems to be working fine
(well, only 2 of the 3 pcmcia slots seems to be working, but that
doesn’t matter), at least after I slay pci-bios.
Do I need to have pci-bios loaded after boot? What would the downsides be?

Hugh Brown wrote:

You have an Omega Micro 82C092 chipset in your machine which we don’t
support. I don’t even have any documentation on this chipset. There is
something strange in the register setup that is causing devp-pccard to
fault.

Previously, David Holm wrote in qdn.public.qnxrtp.os:

Hugh Brown wrote:


Please will you do the following:

  1. slay devp-pccard
  2. slay pci-bios
  3. pci-bios -vvv
  4. devp-pccard -vvv
  5. sloginfo > file
  6. Post the output ‘file’

Thanks, Hugh.

Previously, David Holm wrote in qdn.public.qnxrtp.os:


Hi,
I’m having some trouble with the devp-pccard server on an x86 system. If
pci-bios is running (which it is automatically) and I try to execute
devp-pccard it just returns with error message “Memory Fault”, but if I
slay pci-bios it works perfectly.
I’m not sure what the effects of slaying pci-bios are since so far I see
no difference except in PCMCIA, but I’m guessing there are downsides
to slaying it…
Well, what should I do? The PCMCIA controller is Intel 82092AA (or
something like that) compatible, it isn’t listed on the supported
hardware on qnx website, but my 3c589 network card works perfectly when
devp-pccard is running…

//David Holm




Thanks… Here is the log
Time Sev Major Minor Args
Oct 23 21:05:48 5 17 0 pci_server: shutting down pci 8056428
Oct 23 21:05:49 5 6 200 Installing /dev/par port 378
Oct 23 21:13:19 1 8 0 1868982384 1482191982 1635021600 1684370546 541806368 1329930285 943128651
Oct 23 21:13:25 5 9 0 Start: /usr/photon/bin/devi-hirun kbd fd -d/dev/kbd ps2 mousedev

Oct 23 21:16:04 5 17 0 pci_server: Aug 23 2001 18:12:15
Oct 23 21:16:04 5 17 0 Low memory CPU 1000000 - PCI 1000000
Oct 23 21:16:04 5 17 0 High memory CPU ffefffff - PCI fff00000
Oct 23 21:16:04 5 17 0 Low port CPU 200 - PCI 200
Oct 23 21:16:04 5 17 0 High port CPU fefe - PCI feff
Oct 23 21:16:04 5 17 0 Found host bridge 0 0
Oct 23 21:16:04 5 17 0 Configure bridge - bus 0 - devfunc 0
Oct 23 21:16:04 5 17 0 cb Bus 0 - Devfn 0 - dword ff0000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 alloc_bus 0 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 0 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 406 Index 0 ClassCode 60000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Setup bridge 0 - Lastbus = 1
Oct 23 21:16:04 5 17 0 Bus 0 - Device 1 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 8 Index 0 ClassCode 60100
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 1 - Function 1
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 601 Index 0 ClassCode 10100
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Range failed 174 - 28c
Oct 23 21:16:04 3 17 0 Range check failed (IO) - Dev 601 - Vend 1039 - Class 10100 - Addr 174 - Size 28c
Oct 23 21:16:04 5 17 0 IO 174 28c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 174 - Size 28c
Oct 23 21:16:04 2 17 0 Alloc failed 175 - Size 28c
Oct 23 21:16:04 5 17 0 Range failed 1f4 - 20c
Oct 23 21:16:04 3 17 0 Range check failed (IO) - Dev 601 - Vend 1039 - Class 10100 - Addr 1f4 - Size 20c
Oct 23 21:16:04 5 17 0 IO 1f4 20c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 1f4 - Size 20c
Oct 23 21:16:04 2 17 0 Alloc failed 1f5 - Size 20c
Oct 23 21:16:04 5 17 0 IO 374 8c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 374 - Size 8c
Oct 23 21:16:04 2 17 0 Alloc failed 375 - Size 8c
Oct 23 21:16:04 5 17 0 IO 3f4 c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 3f4 - Size c
Oct 23 21:16:04 2 17 0 Alloc failed 3f5 - Size c
Oct 23 21:16:04 5 17 0 IO 174 28c
Oct 23 21:16:04 5 17 0 IO 1f4 20c
Oct 23 21:16:04 5 17 0 IO 374 8c
Oct 23 21:16:04 5 17 0 IO 3f4 c
Oct 23 21:16:04 5 17 0 Bus 0 - Device 6 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1023 Device 9660 Index 0 ClassCode 30000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 MEM 8000000 400000
Oct 23 21:16:04 5 17 0 MEM 8800000 10000
Oct 23 21:16:04 5 17 0 MEM 8400000 400000
Oct 23 21:16:04 5 17 0 ROM c0000 - 10000
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr c0000 - Size 10000
Oct 23 21:16:04 5 17 0 MEM 8000000 400000
Oct 23 21:16:04 5 17 0 MEM 8800000 10000
Oct 23 21:16:04 5 17 0 MEM 8400000 400000
Oct 23 21:16:04 5 17 0 Bus 0 - Device 13 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 119b Device 1221 Index 0 ClassCode 60500
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 IO 3e0 4
Oct 23 21:16:04 5 17 0 IO 3e0 4
Oct 23 21:16:04 5 17 0 reserve IRQ 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 14 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 119b Device 1221 Index 1 ClassCode 60500
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 IO 3e4 4
Oct 23 21:16:04 5 17 0 IO 3e4 4
Oct 23 21:16:04 5 17 0 reserve IRQ 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:27 5 17 0 io_open for id = 3
Oct 23 21:16:27 5 17 0 Alloc IRQ 7 - Flags c01
Oct 23 21:16:27 5 17 0 Alloc IRQ 7 - Flags c01
Oct 23 21:16:27 5 17 0 io_close_ocb
Oct 23 21:16:27 5 17 0 Free IRQ 7
Oct 23 21:16:27 5 17 0 IRQ Free Failed

Previously, David Holm wrote in qdn.public.qnxrtp.os:

Yes, I know you don’t support it, but still, it seems to be working fine
(well, only 2 of the 3 pcmcia slots seems to be working, but that
doesn’t matter), at least after I slay pci-bios.
Do I need to have pci-bios loaded after boot? What would the downsides be?

The pci-bios is only used when drivers for a PCI device start and stop. If
this is not the case for you, then you can do without pci-bios.

Hugh Brown wrote:

You have an Omega Micro 82C092 chipset in your machine which we don’t
support. I don’t even have any documentation on this chipset. There is
something strange in the register setup that is causing devp-pccard to
fault.

Previously, David Holm wrote in qdn.public.qnxrtp.os:

Hugh Brown wrote:


Please will you do the following:

  1. slay devp-pccard
  2. slay pci-bios
  3. pci-bios -vvv
  4. devp-pccard -vvv
  5. sloginfo > file
  6. Post the output ‘file’

Thanks, Hugh.

Previously, David Holm wrote in qdn.public.qnxrtp.os:


Hi,
I’m having some trouble with the devp-pccard server on an x86 system. If
pci-bios is running (which it is automatically) and I try to execute
devp-pccard it just returns with error message “Memory Fault”, but if I
slay pci-bios it works perfectly.
I’m not sure what the effects of slaying pci-bios are since so far I see
no difference except in PCMCIA, but I’m guessing there are downsides
to slaying it…
Well, what should I do? The PCMCIA controller is Intel 82092AA (or
something like that) compatible, it isn’t listed on the supported
hardware on qnx website, but my 3c589 network card works perfectly when
devp-pccard is running…

//David Holm




Thanks… Here is the log
Time Sev Major Minor Args
Oct 23 21:05:48 5 17 0 pci_server: shutting down pci 8056428
Oct 23 21:05:49 5 6 200 Installing /dev/par port 378
Oct 23 21:13:19 1 8 0 1868982384 1482191982 1635021600 1684370546 541806368 1329930285 943128651
Oct 23 21:13:25 5 9 0 Start: /usr/photon/bin/devi-hirun kbd fd -d/dev/kbd ps2 mousedev

Oct 23 21:16:04 5 17 0 pci_server: Aug 23 2001 18:12:15
Oct 23 21:16:04 5 17 0 Low memory CPU 1000000 - PCI 1000000
Oct 23 21:16:04 5 17 0 High memory CPU ffefffff - PCI fff00000
Oct 23 21:16:04 5 17 0 Low port CPU 200 - PCI 200
Oct 23 21:16:04 5 17 0 High port CPU fefe - PCI feff
Oct 23 21:16:04 5 17 0 Found host bridge 0 0
Oct 23 21:16:04 5 17 0 Configure bridge - bus 0 - devfunc 0
Oct 23 21:16:04 5 17 0 cb Bus 0 - Devfn 0 - dword ff0000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 alloc_bus 0 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 0 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 406 Index 0 ClassCode 60000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Setup bridge 0 - Lastbus = 1
Oct 23 21:16:04 5 17 0 Bus 0 - Device 1 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 8 Index 0 ClassCode 60100
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 1 - Function 1
Oct 23 21:16:04 5 17 0 Vendor 1039 Device 601 Index 0 ClassCode 10100
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Range failed 174 - 28c
Oct 23 21:16:04 3 17 0 Range check failed (IO) - Dev 601 - Vend 1039 - Class 10100 - Addr 174 - Size 28c
Oct 23 21:16:04 5 17 0 IO 174 28c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 174 - Size 28c
Oct 23 21:16:04 2 17 0 Alloc failed 175 - Size 28c
Oct 23 21:16:04 5 17 0 Range failed 1f4 - 20c
Oct 23 21:16:04 3 17 0 Range check failed (IO) - Dev 601 - Vend 1039 - Class 10100 - Addr 1f4 - Size 20c
Oct 23 21:16:04 5 17 0 IO 1f4 20c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 1f4 - Size 20c
Oct 23 21:16:04 2 17 0 Alloc failed 1f5 - Size 20c
Oct 23 21:16:04 5 17 0 IO 374 8c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 374 - Size 8c
Oct 23 21:16:04 2 17 0 Alloc failed 375 - Size 8c
Oct 23 21:16:04 5 17 0 IO 3f4 c
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr 3f4 - Size c
Oct 23 21:16:04 2 17 0 Alloc failed 3f5 - Size c
Oct 23 21:16:04 5 17 0 IO 174 28c
Oct 23 21:16:04 5 17 0 IO 1f4 20c
Oct 23 21:16:04 5 17 0 IO 374 8c
Oct 23 21:16:04 5 17 0 IO 3f4 c
Oct 23 21:16:04 5 17 0 Bus 0 - Device 6 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 1023 Device 9660 Index 0 ClassCode 30000
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 MEM 8000000 400000
Oct 23 21:16:04 5 17 0 MEM 8800000 10000
Oct 23 21:16:04 5 17 0 MEM 8400000 400000
Oct 23 21:16:04 5 17 0 ROM c0000 - 10000
Oct 23 21:16:04 2 17 0 Unable to seed resource Addr c0000 - Size 10000
Oct 23 21:16:04 5 17 0 MEM 8000000 400000
Oct 23 21:16:04 5 17 0 MEM 8800000 10000
Oct 23 21:16:04 5 17 0 MEM 8400000 400000
Oct 23 21:16:04 5 17 0 Bus 0 - Device 13 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 119b Device 1221 Index 0 ClassCode 60500
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 IO 3e0 4
Oct 23 21:16:04 5 17 0 IO 3e0 4
Oct 23 21:16:04 5 17 0 reserve IRQ 0
Oct 23 21:16:04 5 17 0 Bus 0 - Device 14 - Function 0
Oct 23 21:16:04 5 17 0 Vendor 119b Device 1221 Index 1 ClassCode 60500
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 IO 3e4 4
Oct 23 21:16:04 5 17 0 IO 3e4 4
Oct 23 21:16:04 5 17 0 reserve IRQ 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:04 5 17 0 find_bus 0
Oct 23 21:16:04 5 17 0 Busmap Pri 0 - Sec 0 - Sub 0
Oct 23 21:16:27 5 17 0 io_open for id = 3
Oct 23 21:16:27 5 17 0 Alloc IRQ 7 - Flags c01
Oct 23 21:16:27 5 17 0 Alloc IRQ 7 - Flags c01
Oct 23 21:16:27 5 17 0 io_close_ocb
Oct 23 21:16:27 5 17 0 Free IRQ 7
Oct 23 21:16:27 5 17 0 IRQ Free Failed

\