Re: USB device programming with ugen [Solved]

From: Martin (nakal_at_web.de)
Date: 07/15/03

  • Next message: Sumit Shah: "Re: RAID and NFS exports (Possible Data Corruption)" 
    To: freebsd-hackers@freebsd.org
Date: 15 Jul 2003 19:01:52 +0200

    On Tue, 2003-07-15 at 09:04, Terry Lambert wrote:
    > The attach should have failed, if it didn't have an interrupt.

    Somehow uhci0 didn't have interrupt, but it managed to find the webcam
    on ugen0. Don't ask me why. I have attached my logs below.
    You can see many devices sharing same irq. I don't know what line 2
    means exactly, but if it means that my USB-controller was assigned
    irq 11, it could lock several important devices at once, if IRQs are
    not handled properly.

    In new logs uhci0 was found configured on irq 9.

    Earlier dmesg (from /var/log/messages):
    Jul 11 20:35:58 xxx kernel: uhci0: <Intel 82371AB/EB (PIIX4) USB
    controller> port 0xc000-0xc01f at device 7.2 on pci0
    Jul 11 20:35:58 xxx kernel: pci_cfgintr: 0:7 INTD routed to irq 11
    ...
    Jul 11 20:35:58 xxx kernel: ugen0: WINBOND W9967CF, rev 1.10/1.10, addr
    2
    ...
    Jul 11 20:35:58 xxx kernel: sym0: <875> port 0xc400-0xc4ff mem
    0xe7002000-0xe7002fff,0xe7001000-0xe70010ff irq 11 at device 11.0 on
    pci0
    ...
    Jul 11 20:35:58 xxx kernel: atapci1: <HighPoint HPT366 UDMA66
    controller> port 0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 11 at
    device 19.0 on pci0
    Jul 11 20:35:58 xxx kernel: ata2: at 0xcc00 on atapci1
    Jul 11 20:35:58 xxx kernel: atapci2: <HighPoint HPT366 UDMA66
    controller> port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at
    device 19.1 on pci0
    Jul 11 20:35:58 xxx kernel: ata3: at 0xd800 on atapci2

    Now dmesg:
    uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xc000-0xc01f irq
    9 at device 7.2 on pci0
    ...
    ugen0: WINBOND W9967CF, rev 1.10/1.10, addr 2
    ...
    sym0: <875> port 0xc400-0xc4ff mem
    0xe7002000-0xe7002fff,0xe7001000-0xe70010ff irq 11 at device 11.0 on
    pci0
    ...
    atapci1: <HighPoint HPT366 UDMA66 controller> port
    0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 11 at device 19.0 on pci0
    ata2: at 0xcc00 on atapci1
    atapci2: <HighPoint HPT366 UDMA66 controller> port
    0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.1 on pci0

    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

  • Next message: Sumit Shah: "Re: RAID and NFS exports (Possible Data Corruption)"

    Relevant Pages

    • USB devices not being created
      ... workstation with a hyperthreading CPU. ... When I plug a mass storage device into the USB port of this machine (but ... pci0: ... irq 16 at device 29.0 on pci0 ...
      (freebsd-current)
    • promise sata tx4 and 3 monitors [long]
      ... irq 16 at device 0.0 on pci1 ... - 1.7.19> port ... pci0: <ACPI PCI bus> on pcib0 ...
      (freebsd-questions)
    • ad0: FAILURE - READ_DMA
      ... FreeBSD complains about DMA problems. ... pci0: ... irq 16 at ... port 0xb800-0xb8ff mem ...
      (freebsd-questions)
    • hard lock-up writing to tape
      ... pcib0: port ... slot 7 INTD is routed to irq 11 ... 0xd0000000-0xd7ffffff at device 0.0 on pci0 ... 1 port with 1 removable, ...
      (freebsd-current)
    • audio - Analog Devices AD1985 AC97 Codec & WINMODEM LT - ???
      ... I have an INTEL i865 motherboard, ... pci0: on pcib0 ... mem 0xffa80000-0xffafffff,0xf0000000-0xf7ffffff irq 11 at device 2.0 ... 2 ports with 2 removable, ...
      (freebsd-questions)