Re: usb/128418: [panic] [rum] loading if_rum causes panic, looks like in usb stack
The following reply was made to PR usb/128418; it has been noted by GNATS. From: Kevin Downey [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Subject: Re: usb/128418: [panic] [rum] loading if_rum causes panic, looks like in usb stack Date: Sat, 1 Nov 2008 20:59:26 -0700 Gar. I had to rebuild the kernel with all the debugging stuffs. Then loading the usb modules just locked up the laptop, no dumps, so now the usb modules are compiled into the kernel. #0 doadump () at pcpu.h:246 #1 0xc05927ae in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xc0592a82 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xc048a287 in db_panic (addr=Could not find the frame base for db_panic. ) at /usr/src/sys/ddb/db_command.c:478 #4 0xc048a8b1 in db_command (last_cmdp=0xc08a8e9c, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:445 #5 0xc048aa0a in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #6 0xc048c86d in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:229 #7 0xc05bf686 in kdb_trap (type=12, code=0, tf=0xc3bc0bbc) at /usr/src/sys/kern/subr_kdb.c:534 #8 0xc07ddd3f in trap_fatal (frame=0xc3bc0bbc, eva=56) at /usr/src/sys/i386/i386/trap.c:920 #9 0xc07ddf60 in trap_pfault (frame=0xc3bc0bbc, usermode=0, eva=56) at /usr/src/sys/i386/i386/trap.c:842 #10 0xc07de923 in trap (frame=0xc3bc0bbc) at /usr/src/sys/i386/i386/trap.c:522 #11 0xc07c334b in calltrap () at /usr/src/sys/i386/i386/exception.s:165 #12 0xc05110f4 in ehci_idone (ex=0xc3fca600) at /usr/src/sys/dev/usb/ehci.c:914 #13 0xc0511a9a in ehci_softintr (v=0xc4012000) at /usr/src/sys/dev/usb/ehci.c:802 #14 0xc052a1e2 in usb_schedsoftintr (bus=0xc4012000) at /usr/src/sys/dev/usb/usb.c:848 #15 0xc051362e in ehci_intr1 (sc=0xc4012000) at /usr/src/sys/dev/usb/ehci.c:631 #16 0xc0514105 in ehci_intr (v=0xc4012000) at /usr/src/sys/dev/usb/ehci.c:590 #17 0xc0573ee5 in intr_event_execute_handlers (p=0xc3d617d4, ie=0xc3da0b00) at /usr/src/sys/kern/kern_intr.c:1134 #18 0xc0574b5f in ithread_loop (arg=0xc4056be0) at /usr/src/sys/kern/kern_intr.c:1147 #19 0xc0571ca8 in fork_exit (callout=0xc0574ac0 ithread_loop, arg=0xc4056be0, frame=0xc3bc0d38) at /usr/src/sys/kern/kern_fork.c:815 #20 0xc07c33c0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb/128418: loading if_rum causes panic, looks like in usb stack
The following reply was made to PR usb/128418; it has been noted by GNATS. From: Kevin Downey [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: Re: usb/128418: loading if_rum causes panic, looks like in usb stack Date: Mon, 27 Oct 2008 12:09:02 -0700 actual uname: FreeBSD circe.nexus.lan 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Sun Oct 26 07:45:58 PDT 2008 root@:/usr/obj/usr/src/sys/CIRCE8 i386 log output: Oct 27 09:48:36 circe kernel: rum0: could not transmit buffer: TIMEOUT Oct 27 09:48:36 circe kernel: rum0: device timeout Oct 27 09:49:59 circe syslogd: restart Oct 27 09:49:59 circe syslogd: kernel boot file is /boot/kernel/kernel Oct 27 09:49:59 circe kernel: Oct 27 09:49:59 circe kernel: Oct 27 09:49:59 circe kernel: Fatal trap 12: page fault while in kernel mode Oct 27 09:49:59 circe kernel: cpuid = 1; apic id = 01 Oct 27 09:49:59 circe kernel: fault virtual address = 0x67001c Oct 27 09:49:59 circe kernel: fault code= supervisor read, page not present Oct 27 09:49:59 circe kernel: instruction pointer = 0x20:0xc0572c20 Oct 27 09:49:59 circe kernel: stack pointer = 0x28:0xe76e9ca0 Oct 27 09:49:59 circe kernel: frame pointer = 0x28:0xe76e9cd4 Oct 27 09:49:59 circe kernel: code segment = base 0x0, limit 0xf, type 0x1b Oct 27 09:49:59 circe kernel: = DPL 0, pres 1, def32 1, gran 1 Oct 27 09:49:59 circe kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Oct 27 09:49:59 circe kernel: current process = 1207 (usbtask-dr) Oct 27 09:49:59 circe kernel: trap number = 12 Oct 27 09:49:59 circe kernel: panic: page fault Oct 27 09:49:59 circe kernel: cpuid = 1 Oct 27 09:49:59 circe kernel: Uptime: 3m11s Oct 27 09:49:59 circe kernel: Physical memory: 1005 MB Oct 27 09:49:59 circe kernel: Dumping 160 MB: 145 129 113 97 81 65 49 33 17 1 Oct 27 09:49:59 circe kernel: Dump complete Oct 27 09:49:59 circe kernel: Automatic reboot in 15 seconds - press a key on the console to abort Oct 27 09:49:59 circe kernel: panic: bufwrite: buffer is not busy??? Oct 27 09:49:59 circe kernel: cpuid = 1 Oct 27 09:49:59 circe kernel: Rebooting... Oct 27 09:49:59 circe kernel: cpu_reset: Stopping other CPUs -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Logitech xbox gamepad as a uhid
On Feb 4, 2008 7:39 AM, Markus Brueffer [EMAIL PROTECTED] wrote: Am Mittwoch, 30. Januar 2008 20:47:48 schrieb Kevin Downey: I have a wireless xbox (not xbox 360) gamepad that I would like to use as a remote control for media stuff in X. I figure a first step in that direction is to get it recognized as a uhid device. I find it hard to believe that I am the first person to do this on a freebsd box, yet googling the only hits I get are about xbox360 gamepad support. uhub7: Logitech Wingman Wireless Xbox Controller (hub), class 9/0, rev 1.10/1.03, addr 2 on uhub1 uhub7: 3 ports with 2 removable, bus powered id-bInterfaceClass 0x58 ugen0: vendor 0x046d product 0xca84, class 0/0, rev 1.10/1.03, addr 3 on uhub7 ... My idea was maybe I could just add a case for this controller. Does anyone have any pointers(har har), besides read the source for how to get this working? A first start would be to get it recognized by uhid(4). Please provide a descriptor dump of the device using sysutils/udesc_dump from ports. Markus pasted and incase gmail mangles it, http://thelastcitadel.com/lab/udesc_dump_logitech_wireless_xbox.txt Standard Device Descriptor: bLength18 bDescriptorType01 bcdUSB 0110 bDeviceClass 00 bDeviceSubClass00 bDeviceProtocol00 bMaxPacketSize 8 idVendor 046d idProduct ca84 bcdDevice 0103 iManufacturer 0 iProduct 0 iSerialNumber 0 bNumConfigurations 1 Configuration 0: Standard Configuration Descriptor: bLength 9 bDescriptorType 02 wTotalLength32 bNumInterface 1 bConfigurationValue 1 iConfiguration 0 bmAttributes80 bMaxPower 50 (100 mA) Standard Interface Descriptor: bLength9 bDescriptorType04 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass58 bInterfaceSubClass 42 bInterfaceProtocol 00 iInterface 0 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 81 (in) bmAttributes 03 (Interrupt) wMaxPacketSize 32 bInterval4 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 02 (out) bmAttributes 03 (Interrupt) wMaxPacketSize 32 bInterval4 -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Logitech xbox gamepad as a uhid
I have a wireless xbox (not xbox 360) gamepad that I would like to use as a remote control for media stuff in X. I figure a first step in that direction is to get it recognized as a uhid device. I find it hard to believe that I am the first person to do this on a freebsd box, yet googling the only hits I get are about xbox360 gamepad support. uhub7: Logitech Wingman Wireless Xbox Controller (hub), class 9/0, rev 1.10/1.03, addr 2 on uhub1 uhub7: 3 ports with 2 removable, bus powered id-bInterfaceClass 0x58 ugen0: vendor 0x046d product 0xca84, class 0/0, rev 1.10/1.03, addr 3 on uhub7 the id-bInterfaceClass 0x58 is from a printf I added after line 208 in /sys/dev/usb/uhid.c /* The Xbox 360 gamepad doesn't use the HID class. */ printf(id-bInterfaceClass 0x%x\n,id-bInterfaceClass); if (id-bInterfaceClass != UICLASS_VENDOR || id-bInterfaceSubClass != UISUBCLASS_XBOX360_CONTROLLER || id-bInterfaceProtocol != UIPROTO_XBOX360_GAMEPAD) return (UMATCH_NONE); My idea was maybe I could just add a case for this controller. Does anyone have any pointers(har har), besides read the source for how to get this working? -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Call for Testers: FreeBSD webcam driver (and more)
On 1/30/07, Luigi Rizzo [EMAIL PROTECTED] wrote: I think I reached a first interesting milestone in my project to build an emulation layer to compile linux device drivers on FreeBSD. I managed to build a FreeBSD port of the linux 'gspca' driver (which claims to support 228 different webcams) with basically no modifications to the original source. So it would be good if someone could give a try to this code, either on -current or -stable, keeping in mind that this is NOT PRODUCTION READY yet. More details on how the thing works are at http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html together of course with source code, and even binary modules for FreeBSD 6.2. Basically I would like to know how it builds/works on -current, have reports on cameras that work with it and those which don't and so on. The driver supports the Video4Linux API so it should be useful for a variety of applications. very cool. But how do you know if it works? what applications can be used with this and how do you set them to use this? I have a Quickcam Chat which apears to be supported by the linux gscpa driver(sorry I am away from it right now or I would post a dmesg). How would I access the cameras video feed? -- The biggest problem with communication is the illusion that it has occurred. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
