From simon at optinet.com Fri Apr 3 00:56:56 2009 From: simon at optinet.com (Simon) Date: Fri Apr 3 01:03:24 2009 Subject: amr driver issues in 7.1-RELEASE In-Reply-To: <497E252C.2010502@comcast.net> Message-ID: <20090403075656.3721F8FC14@mx1.freebsd.org> It appears this has not been fixed in 7.1-p4 I've been waiting to upgrade due to this but was forced after latest root exploit was found recently. Upon MySQL upgrade, running mysql_upgrade which upgrades and checks all the tables, I got 2 of these messages while a large ,1.4G, mysql table was being dumped to array so it could be repaired. I don't know what to make of this error and are not sure if it could be safely ignored. amr0: Too many retries on command 0xc71ceaa8. Controller is likely dead amr0: Too many retries on command 0xc71cdce8. Controller is likely dead Thank you in advance! -Simon On Mon, 26 Jan 2009 16:03:40 -0500, Steve Polyack wrote: >Steve Polyack wrote: >> Scott Long wrote: >>> The fix for this that I was thinking of is already in 7.1. There >>> might still be a driver bug, but I'm leaning more towards the >>> controller simply being busy. Do you have a reproducible test case >>> that I could >>> try? >>> >>> Scott >>> >So far, I have not been able to reliably reproduce this. It pops up >every now and then during our backups, which at the moment aren't that >disk intensive. I'll let you know if I come across anything else. >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From spolyack at collaborativefusion.com Fri Apr 3 05:33:09 2009 From: spolyack at collaborativefusion.com (Steve Polyack) Date: Fri Apr 3 05:33:16 2009 Subject: [Fwd: Re: amr driver issues in 7.1-RELEASE] In-Reply-To: <49D5E2A7.8060105@comcast.net> References: <49D5E2A7.8060105@comcast.net> Message-ID: <49D5FFA7.3090408@collaborativefusion.com> > It appears this has not been fixed in 7.1-p4 I've been waiting to upgrade due > to this but was forced after latest root exploit was found recently. Upon MySQL > upgrade, running mysql_upgrade which upgrades and checks all the tables, > I got 2 of these messages while a large ,1.4G, mysql table was being dumped > to array so it could be repaired. I don't know what to make of this error and > are not sure if it could be safely ignored. > > amr0: Too many retries on command 0xc71ceaa8. Controller is likely dead > amr0: Too many retries on command 0xc71cdce8. Controller is likely dead > > Thank you in advance! > > -Simon > > We still see these as well. I've also been ensured that these are harmless messages. As far as I can tell from my own investigation, the behavior has not changed other than the addition of tracking of how many retries there have been when submitting commands to the controller. When the controller mailbox is "busy", the driver must wait before submitting a command. If the driver has to retry 1000 times twice within one second, it logs the messages you are seeing. This logging was simply not present before 7.1. As I've said and been told, the message is harmless if your machine is still responding. From simon at optinet.com Fri Apr 3 05:34:19 2009 From: simon at optinet.com (Simon) Date: Fri Apr 3 05:34:25 2009 Subject: [Fwd: Re: amr driver issues in 7.1-RELEASE] In-Reply-To: <49D5FFA7.3090408@collaborativefusion.com> Message-ID: <20090403123418.6C9FC8FC28@mx1.freebsd.org> >> It appears this has not been fixed in 7.1-p4 I've been waiting to upgrade due >> to this but was forced after latest root exploit was found recently. Upon MySQL >> upgrade, running mysql_upgrade which upgrades and checks all the tables, >> I got 2 of these messages while a large ,1.4G, mysql table was being dumped >> to array so it could be repaired. I don't know what to make of this error and >> are not sure if it could be safely ignored. >> >> amr0: Too many retries on command 0xc71ceaa8. Controller is likely dead >> amr0: Too many retries on command 0xc71cdce8. Controller is likely dead >> >> Thank you in advance! >> >> -Simon >> >> >We still see these as well. I've also been ensured that these are >harmless messages. As far as I can tell from my own investigation, the >behavior has not changed other than the addition of tracking of how many >retries there have been when submitting commands to the controller. >When the controller mailbox is "busy", the driver must wait before >submitting a command. If the driver has to retry 1000 times twice >within one second, it logs the messages you are seeing. This logging >was simply not present before 7.1. >As I've said and been told, the message is harmless if your machine is >still responding. Well, I have several machines with same megaraid controller and I'm only seeing this on one of them thus far. The load on this one is not grossly different from that of others, so now I wonder why I only get it on this machine. Thanks for your input! -Simon From exemys at exemys.com Mon Apr 6 05:50:00 2009 From: exemys at exemys.com (Exemys) Date: Mon Apr 6 05:50:07 2009 Subject: Modbus I/O Module - Analog / Digital Message-ID: <7b689ba2b86b5113e62541e1b4e6899d@www.hostmailing.com> This is a message in multipart MIME format. Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly. From lists at freebsdonline.com Mon Apr 20 06:59:09 2009 From: lists at freebsdonline.com (ovi freebsd) Date: Mon Apr 20 06:59:16 2009 Subject: Problem with GELI and hifn (soekris vpn1401 and vpn 1411) Message-ID: <49EC18BA.8020801@freebsdonline.com> Hello I just bought two soekris vpn1401 and vpn 1411 cards (minipci and pci) and I've tried to make it work under FreeBSD. The card is detected properly, still I have no improvments in performance when using crypto hardware and also when I transfer file to an encrypted partition it locks itself and I must reboot. hifn0 mem 0xe0080000-0xe0080fff,0xe00c0000-0xe00c1fff,0xe0100000-0xe0107fff irq 9 at device 12.0 on pci0 hifn0: [ITHREAD] hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801 GEOM_ELI: Device da0s1g.eli created. GEOM_ELI: Encryption: AES-CBC 256 GEOM_ELI: Crypto: hardware I've also tried with AES 128. Same result. After it locks i must reboot and then the encryptend partition cannot be mount. Trying to fsck the partition (after attaching it) it still locks: fsck is not doing anything. last pid: 1162; load averages: 0.00, 0.00, 0.00 up 0+03:06:34 16:02:33 30 processes: 1 running, 29 sleeping Mem: 25M Active, 976K Inact, 12M Wired, 1804K Cache, 34M Buf, 199M Free Swap: 700M Total, 700M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 965 root 1 -8 0 31812K 12016K physrd 0:01 0.00% fsck_ufs 642 root 1 44 0 5876K 2296K select 0:00 0.00% sendmail fs# fsck -t ufs /dev/da0s1g.eli ** /dev/da0s1g.eli ***** FILE SYSTEM STILL DIRTY ***** ** Last Mounted on /usr/home/fileserver ** Phase 1 - Check Blocks and Sizes And it stays at Phase 1 like forver (fsck-ing for 4-5 hours now). Removing hifn module, detaching and attaching the geli partition it fscks ok. I've checked, everything is setup ok, I've tried with compiled kernel or modules loaded at boot. I've tried a test with OpenSSL: time dd if=/dev/zero bs=1m count=100 | openssl des3 -pass pass:test -engine cryptodev -out /dev/null results: Without hardware encryption --------------------------- Code: engine "cryptodev" set. 100+0 records in 100+0 records out 104857600 bytes transferred in 46.245892 secs (2267393 bytes/sec) With hardware encryption ------------------------ Code: engine "cryptodev" set. 100+0 records in 100+0 records out 104857600 bytes transferred in 21.653051 secs (4842625 bytes/sec) It works 2x with hardware (as advertised by others on mailing lists), so I think is a problem with geli+hifn. If you have any experience with this issue please advice. Tests were made on PCEngines Alix board with mini pci soekris vpn1411 and a regular PC with PCI soekris vpn1401. best regards, ovi From exemys at exemys.com Mon Apr 20 07:17:59 2009 From: exemys at exemys.com (Exemys) Date: Mon Apr 20 07:18:07 2009 Subject: TCP/IP Sensors and Transducers Message-ID: This is a message in multipart MIME format. Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly. From olivas at new.digiflux.org Mon Apr 20 12:17:54 2009 From: olivas at new.digiflux.org (Stacy Olivas) Date: Mon Apr 20 12:18:00 2009 Subject: Cardbus0 problems: Xircom X3201 10/100BaseTX Message-ID: <49EC67E6.6080400@new.digiflux.org> Hello, Got a quick question about the Xircom X3201 PCMCIA card with FreeBSD 7.2-PRERELEASE. I recently upgraded from 6.2-STABLE to 7.2-PRERELEASE, and after the upgrade, I noticed that my Xircom card was not working. Here is what I get when the system boots or I remove and re-insert the card: cardbus0: Unable to allocate resource to read CIS. cardbus0: Unable to allocate resources for CIS dc0: port 0x1100-0x117f mem 0x88000000-0x880007ff,0x88001000-0x880017ff irq 11 at device 0.0 on cardbus0 dc0: No station address in CIS! device_attach: dc0 attach returned 6 Anyone else having this issue? I"ve found this patch that was supposed to fix the issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F115623&cat= Not sure if it was actually incorporated into 7.2-PRERELEASE though. Ideas? Thanks -Stacy From ryan at rbftpnetworks.com Fri Apr 24 23:08:27 2009 From: ryan at rbftpnetworks.com (ryan@rbftpnetworks.com) Date: Fri Apr 24 23:08:40 2009 Subject: Gaming news link Message-ID: <14ac907b54cf8f794ca66e5e08697443@www.list.flyawaysimulation.com> Dear Sir / Madam, We are interested in posting our gaming news and information site on your links section. Our site is GamerBeef.com and can be found at http://www.gamerbeef.com Our site includes daily updated gaming news from all genres and consoles, with focus on PC gaming. We also have a new discussion forum, cheats and screenshots section. We would of course offer a link back to your site in return. Let me know your thoughts. Best Regards, Ryan -- Ryan Barclay Managing Director RBFTP Networks Limited. DDI: +44 (0)870 490 1870 WWW: http://www.rbftpnetworks.com RBFTP Networks Limited Registered in England No 05718807 Registered Office: 68 Aldersbrook Road, London, E12 5DL. From ashley.moran at patchspace.co.uk Sat Apr 25 18:57:04 2009 From: ashley.moran at patchspace.co.uk (Ashley Moran) Date: Sat Apr 25 18:57:11 2009 Subject: Sapphire Radeon HD 3450 Message-ID: Hi I've bought a Sapphire Radeon HD 3450 PCI Express card that won't work under PC-BSD 7.1 (64-bit and 32-bit) on my Asus M2V-TVM machine's motherboard. It hangs at the bit where it tries to identify the monitor's refresh rate (apologies for lack of exact error message). Should this card work under FreeBSD or not? If so I might have another go. If it's either known or suspected to not work, anyone want to take it off my hands to debug the driver? I'm not inclined to spend too much longer trying to make it work, so if someone else can do something useful with it they will be welcome. I'm not on the list so please CC me if you reply. Thanks Ashley -- http://www.patchspace.co.uk/ http://www.linkedin.com/in/ashleymoran http://aviewfromafar.net/ http://twitter.com/ashleymoran From smallpox at gmail.com Sun Apr 26 00:38:34 2009 From: smallpox at gmail.com (smallpox) Date: Sun Apr 26 00:38:40 2009 Subject: altus 1300 / penguincomputing major issues with hard disks Message-ID: <49F3A5C1.8030801@gmail.com> I acquired a few of these last year and apparently they're perfect for linux, they're a bit outdated but I cannot stand linux. I've run one of these servers pretty stable with SATA150 and SATA300 drives but I received two 'FACTORY RECERTIFIED' drives back from Seagate (yes, they're a mess) but these were the older 500GIG 7200.10 ones. I popped them in at the datacente rand immediately came the box: Apr 24 17:03:48 x kernel: ad6: 114473MB at ata3-master SATA150 Apr 24 17:03:48 x kernel: GEOM_MIRROR: Device mirror/gm0 launched (1/1). Apr 24 17:03:48 x kernel: ad10: 476940MB at ata5-master SATA300 then i rebooted it to add the second 500 gig drive and: Apr 24 17:07:42 x kernel: ad6: 114473MB at ata3-master SATA150 Apr 24 17:07:42 x kernel: ad8: 476940MB at ata4-master SATA300 Apr 24 17:07:42 x kernel: GEOM_MIRROR: Device mirror/gm0 launched (1/1). Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA48 status=51 error=84 LBA=976773151 Apr 24 17:07:42 x kernel: ad10: 476940MB at ata5-master SATA300 Apr 24 17:07:42 x kernel: SMP: AP CPU #1 Launched! Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=128 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=128 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51 error=84 LBA=128 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51 error=84 LBA=16 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51 error=84 LBA=0 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:07:42 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:07:42 x kernel: ad8: FAILURE - READ_DMA status=51 error=84 LBA=512 Apr 24 17:07:42 x kernel: Trying to mount root from ufs:/dev/mirror/gm0s1a after some major lag and lock ups.. Apr 24 17:12:09 x kernel: ad6: 114473MB at ata3-master SATA150 Apr 24 17:12:09 x kernel: ad8: 476940MB at ata4-master SATA300 Apr 24 17:12:09 x kernel: ad10: 476940MB at ata5-master SATA300 Apr 24 17:12:09 x kernel: SMP: AP CPU #1 Launched! Apr 24 17:12:09 x kernel: GEOM_MIRROR: Device mirror/gm0 launched (1/1). Apr 24 17:12:09 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 then again major lag / lockup Apr 24 17:13:44 x kernel: ad10: FAILURE - device detached Apr 24 17:13:44 x kernel: subdisk10: detached Apr 24 17:13:44 x kernel: ad10: detached Apr 24 17:13:57 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:13:58 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=16 Apr 24 17:13:58 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:13:59 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 Apr 24 17:13:59 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:14:00 x kernel: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=512 Apr 24 17:14:00 x kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad8. Apr 24 17:14:05 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=9856 Apr 24 17:14:10 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=11392 Apr 24 17:14:16 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=17792 Apr 24 17:14:21 x kernel: ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=23296 Apr 24 17:14:57 x kernel: ad8: FAILURE - device detached Apr 24 17:14:57 x kernel: subdisk8: detached Apr 24 17:14:57 x kernel: ad8: detached Apr 24 17:14:57 x kernel: GEOM_MIRROR: Cannot write metadata on ad8 (device=gm0, error=6). Apr 24 17:14:57 x kernel: GEOM_MIRROR: Cannot clear metadata on disk ad8 (error=6). Apr 24 17:14:57 x kernel: GEOM_MIRROR: Synchronization request failed (error=6). ad8[WRITE(offset=11927552, length=131072)] Apr 24 17:14:57 x kernel: GEOM_MIRROR: Device gm0: provider ad8 disconnected. Apr 24 17:14:57 x kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad8 stopped. the two replacement drives that i got failed to work. took them home, ran short/long smart tests on both and they passed, now i'm at the office testing both of them and they seem fine. i was running 7.1-p3 amd64. so overall, this is what is happening. one system is ad4: 381554MB at ata2-master SATA150 (giving me a million g_vfs_done) errors and i could link you to a pic, not sure if i'm allowed to so i will hope to see responses then do it. stuff like this "g_vfs_done() :ad4s1a[WRITE(offset=87081893888, length=16384)]error = 6" another system ad4: 1430799MB at ata2-master SATA300 ad6: 1430799MB at ata3-master SATA300 ad8: 190782MB at ata4-master SATA150 smart shows both ad4/ad6 have read errors and some reallocated sectors, seagate says those firmware shouldn't be involved in their disgusting problems. and the system that's giving me the hard time locally which i tried the two 500 gig drives in it had two 120GB drives, both seagate. luckily i started using the second one last month as the main one just died or i think it died. what are the odds that i'm having an unlucky streak with these new/old drives and it's NOT my sata controller? i've been having this trouble for a while now on BSD on one of them so i was forced to use CentOS (without issues) but i dislike it. is there anything i could run? i have remote kvm access to the one with the g_vfs problems and the local one too but prefer not to break the local one. is this hardware just too old for freebsd to support it? as far as new support cause it seems like it just barely works. i guess i will get two western digital drives and try it on the local one next weekend.. i just need to figure this out asap. thanks. John From ashley.moran at patchspace.co.uk Mon Apr 27 16:46:59 2009 From: ashley.moran at patchspace.co.uk (Ashley Moran) Date: Mon Apr 27 16:47:06 2009 Subject: Sapphire Radeon HD 3450 In-Reply-To: <49F44B26.2090009@bah.homeip.net> References: <49F44B26.2090009@bah.homeip.net> Message-ID: <7CE25A36-A4FA-495F-9E16-CA386977384B@patchspace.co.uk> On 26 Apr 2009, at 12:53, Bernt Hansson wrote: > What driver do you use? > I've got a radeon 3870 on amd64 and it works. Hmmm... the default with PC-BSD :-S I'll have to dig further and see what it's using. Unfortunately I've had to leave the machine behind at my parents' as I wouldn't have had time to look at it soon. You seem confident it should work, so next time I get chance I'll see if I can find/change the driver and report back. Cheers Ashley -- http://www.patchspace.co.uk/ http://www.linkedin.com/in/ashleymoran http://aviewfromafar.net/ http://twitter.com/ashleymoran From christof.schulze at gmx.net Wed Apr 29 23:55:06 2009 From: christof.schulze at gmx.net (Christof Schulze) Date: Wed Apr 29 23:55:14 2009 Subject: Logitech Communicate STX + gspca Message-ID: <200904300128.19286.christof.schulze@gmx.net> Hello everyone, this is my first post to this list, I hope my problem belongs here. I have a Logitech Communicate STX webcam which works under Linux using the gspca driver but not using FreeBSD. When booting and loading the kernel module I get the [2] in dmesg, usbdevs is showing [1] I would love to use my webcam for skype with video but I am not sure what information needs to be provided, and what I can do to help fix the problem. This seems to be my Webcam: 0x08d7 Searching for that has turned up this site http://www.lissyara.su/?id=1850 which unfortunately is not readable by me. I would appreciate it if anyone could look into this. kind Regards Christof Schulze [1] output from usbdevs -v (shortened) % usbdevs addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 2: product 0x08d7, vendor 0x046d addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 2: Kyocera Mita FS-1020D, Kyocera Mita addr 3: USB Receiver, Logitech addr 1: EHCI root hub, Intel 1:20 eri.erika% usbdevs --help % usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, product 0x08d7(0x08d7), vendor 0x046d(0x046d), rev 1.00 Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: full speed, self powered, config 1, Kyocera Mita FS-1020D(0x000e), Kyocera Mita(0x0482), rev 0.00 port 2 addr 3: low speed, power 98 mA, config 1, USB Receiver(0xc518), Logitech(0x046d), rev 42.00 Controller /dev/usb4: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 [1] dmesg (shortened) gspca_attach_bridge: USB GSPCA camera found.(ZC3XX) spca5xx_probe: [spca5xx_probe:4259] Camera type JPEG zc3xx_config: [zc3xx_config:616] Find Sensor HV7131R(c) spca5xx_getcapability: [spca5xx_getcapability:1239] maxw 640 maxh 480 minw 176 minh 144 0 [1117] video_register_device: to be fixed but ok for now ldev0: vendor 0x046d product 0x08d7, rev 1.10/1.00, addr 2 uaudio0: on uhub1 uaudio0: audio rev 1.00 pcm1: on uaudio0 ulpt0: on uhub3 ulpt0: using bi-directional mode ums0: on uhub3 ums0: 16 buttons and Z dir. uhid0: on uhub3 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ZFS filesystem version 6 ZFS storage pool version 6 acd0: CDRW at ata0-master UDMA33 ad1: DMA limited to UDMA33, controller found non-ATA66 cable ad1: 190782MB at ata0-slave UDMA33 ad4: 78533MB at ata2-master SATA150 ad6: 238475MB at ata3-master SATA150 ad10: 238475MB at ata5-master SATA150 Waiting 5 seconds for SCSI devices to settle pcm0: pcm0: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s2a fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 drm0: on vgapci0 info: [drm] Initialized radeon 1.25.0 20060524 info: [drm] Setting GART location based on new memory map info: [drm] Loading R300 Microcode info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] 67540 [1081] video_devdata: not complete but ok for now spca5xx_set_light_freq: [spca5xx_set_light_freq:1920] Sensor currently not support light frequency banding filters. gspca_set_isoc_ep: [gspca_set_isoc_ep:936] ISO EndPoint found 0x81 AlternateSet 7 ldev_ioctl: called linux: pid 2021 (skype): ioctl fd=9, cmd=0x7601 ('v',1) is not implemented 69568 [ 959] usb_kill_urb: not complete but try something 69569 [ 766] ldev_isoc_handler: usbd_cancelled 0xc6609a00 69571 [ 766] ldev_isoc_handler: usbd_cancelled 0xcc0cb200 69572 [ 766] ldev_isoc_handler: usbd_cancelled 0xcc0b2a00 69573 [ 766] ldev_isoc_handler: usbd_cancelled 0xcbef3e00 69576 [ 959] usb_kill_urb: not complete but try something 69576 [ 959] usb_kill_urb: not complete but try something 69576 [ 959] usb_kill_urb: not complete but try something 9456429 [1081] video_devdata: not complete but ok for now spca5xx_set_light_freq: [spca5xx_set_light_freq:1920] Sensor currently not support light frequency banding filters. gspca_set_isoc_ep: [gspca_set_isoc_ep:936] ISO EndPoint found 0x81 AlternateSet 7 9457653 [ 770] ldev_isoc_handler: status 16 9457669 [ 770] ldev_isoc_handler: status 16 9457684 [ 770] ldev_isoc_handler: status 16 9457762 [ 770] ldev_isoc_handler: status 16 9459407 [ 959] usb_kill_urb: not complete but try something 9459410 [ 959] usb_kill_urb: not complete but try something 9459410 [ 959] usb_kill_urb: not complete but try something 9459410 [ 959] usb_kill_urb: not complete but try something -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20090429/c938529f/attachment.pgp