From owner-freebsd-usb@FreeBSD.ORG Sun Jul 4 23:44:41 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1E96106564A for ; Sun, 4 Jul 2010 23:44:41 +0000 (UTC) (envelope-from osp@aloha.com) Received: from relay.pixi.com (relay.pixi.com [206.127.224.101]) by mx1.freebsd.org (Postfix) with ESMTP id AF23C8FC17 for ; Sun, 4 Jul 2010 23:44:41 +0000 (UTC) Received: from leka.aloha.com (leka.aloha.com [206.127.224.85]) by relay.pixi.com (8.13.8+Sun/8.13.6) with ESMTP id o64MmgNl004340 for ; Sun, 4 Jul 2010 12:48:42 -1000 (HST) Received: from [10.0.1.10] (atm-251-63.pixi.com [206.127.251.63]) by leka.aloha.com (8.13.8+Sun/8.12.11) with ESMTP id o64Mmf6w004336 for ; Sun, 4 Jul 2010 12:48:42 -1000 (HST) From: Gary Dunn To: freebsd-usb@freebsd.org Content-Type: text/plain; charset="us-ascii" Organization: Open Slate Project Date: Sun, 04 Jul 2010 12:48:41 -1000 Message-ID: <1278283721.1518.23.camel@slate01> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Supprt for touch panel digitizer X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2010 23:44:42 -0000 I posted some questions on freebsd-general and got some pointers but nothing specific. Then I saw this and thought I should ask here in case someone is working this issue: > From: Norikatsu Shigemura FreeBSD.org> > Subject: usb touch screen support? > Newsgroups: gmane.os.freebsd.devel.usb > Date: 2009-07-04 19:08:52 GMT (52 weeks, 1 day, 3 hours and 25 minutes ago) > Hi. > > I got a usb touch screen device A.K.A. eGalax. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > ugen4.4: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > In this time, however, FreeBSD doesn't support usb touch screen. > So I researched Linux's (drivers/input/touchscreen/usbtouchscreen.c) > and NetBSD's (uep(4)) implementations. It's too simple. > > I considered making modified ums(4) to adapt usb touch screen. > But I noticed that ums(4) should be become a mouse subsystem > like ucom(4), and I gave up. Anyone, do you have any idea? In my case it is a Fujitsu T-1010 tablet PC with a passive USB digitizer. Looks to me like I need to write a new driver rather than modify ums. The last question I asked was, how do I get the kernel to use my driver (assuming I write one) rather than ums? Or is that the wrong approach? -- Gary Dunn, Honolulu osp@aloha.com http://openslate.net/ http://e9erust.blogspot.com/ Sent from Slate001 From owner-freebsd-usb@FreeBSD.ORG Mon Jul 5 11:07:05 2010 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F7841065673 for ; Mon, 5 Jul 2010 11:07:05 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8D4488FC18 for ; Mon, 5 Jul 2010 11:07:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o65B75od079355 for ; Mon, 5 Jul 2010 11:07:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o65B744L079353 for freebsd-usb@FreeBSD.org; Mon, 5 Jul 2010 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Jul 2010 11:07:04 GMT Message-Id: <201007051107.o65B744L079353@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 11:07:05 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/148189 usb [usbdevs] [usb8] [patch] provide descriptive string fo o usb/148080 usb usbconfig(8) sometimes does not turn off the device o usb/148052 usb Documentation error on u3g.4 man page o usb/147516 usb [umass] [usb67] kernel unable to deal with Olympus USB a usb/147196 usb [usbdevs] [patch] Please add a USB-HDD to usb_quirk.c o usb/147190 usb [usbdevs] [patch] Add USR5422 to upgt wlan driver a usb/146907 usb [rue] [patch] OQO model01 network does not work on Fre o usb/146871 usb [usbdevs] [usb8] [patch] provide descriprive string fo o usb/146840 usb [hang] FreeBSD 7.2 / 7.3 / 8.0 hang at startup after e o usb/146799 usb usbdevs(8) missing in ObsoleteFiles.inc p usb/146693 usb [rum] Edimax EW‐7318USG not found in usbdevs or o usb/146153 usb [axe] [usb8] Hosts in network doesn't receive any pack o usb/146054 usb [urtw] [usb8] urtw driver potentially out of date f usb/145513 usb [usb8] New USB stack: no new devices after forced usb o usb/145455 usb [usb8] [patch] USB debug support cannot be disabled o usb/145415 usb [umass] [usb8] USB card reader does not create slices a usb/145184 usb GENERIC can't mount root from USB on Asus EEE o usb/145165 usb [keyboard] [usb8] ukbd_set_leds_callback: error=USB_ER f kern/144938 usb [keyboard] [boot] Boot Failure with Apple (MB869LL/A) o usb/144751 usb [ukbd] [usb8] kernel without keyboard support won't co o usb/144423 usb [usb8] [patch] if_run panic with USB-N13 o usb/144387 usb [run] [panic] if_run panic o usb/144043 usb [umass] [usb8] USB DLT tape drive throws random errors o usb/143790 usb [boot] can not boot from usb hdd f usb/143620 usb [cdce] [usb8] the module if_cdce doesn't support my Op o usb/143448 usb [usbdevs] [usb8] [patch] QUIRK: JMicron JM20336 USB/SA f usb/143294 usb [usb8] copying process stops at some time (10 - 50 sec o usb/143286 usb [ukbd] [usb8] [boot] boot failures on RELENG_8 system f usb/143186 usb [usbdevs] [usb8] [patch] add USB device IDs for Google a usb/143139 usb [umass] [usb8] [patch] Quirk for Century EX35SW4_SB4 J o usb/143045 usb [umass] [usb8] [patch] mounting Fujitsu 2600Z camera d o usb/142991 usb [uftdi] [usb67] [patch] Patch to add Crystalfontz 533 f usb/142989 usb [usb8] canon eos 50D attaches but detaches after few s f usb/142957 usb [umass] [usb8] [patch] patch for USB disk SYNCHRONIZE o usb/142719 usb [urtw] [usb8] AirLive WL-1600USB (RTL8187L chipset) fa o usb/142713 usb [usb67] [panic] Kernel Panik when connecting an IPhone f usb/142276 usb [umass] [usb8] Cache Synchronization Error with Olympu o usb/142229 usb [ums] [usb8] [hang] connecting a USB mouse to a Dell P o usb/141680 usb [uath] [usb8] Netgear WG111T not working with uath dri o usb/141664 usb [pcm] [usb8] Logitech USB microphone failure [regressi o usb/141474 usb [boot] [usb8] FreeBSD 8.0 can not install from USB CDR a usb/141467 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/141327 usb [ukbd] [usb67] USB kbd not working with 7.1+PAE on IBM o usb/141212 usb [ukbd] [usb8] ukbd_set_leds_callback:700: error=USB_ER o kern/141011 usb [usb] Encrypted root, geli password at boot; enter key o usb/140928 usb [u3g] [usb8] [patch] ZTE CDMA2000 1X EV-DO (MG478/AC87 o usb/140920 usb [install] [usb8] USB based install fails on 8.0-RELEAS o usb/140893 usb [urtw] [usb8] WPA2 not working on rtl8187b f usb/140883 usb [axe] [usb8] USB gigabit ethernet hangs after short pe o kern/140849 usb [ums] [usb8] USB mouse doesn't work under FreeBSD 8.0- a usb/140810 usb [uftdi] [usb8] 8.X copy and paste problem / tty overfl o kern/140614 usb [uplcom] [patch] adding support for Radio Shack Gigwar o usb/140590 usb [bluetooth] [usb8] ng_ubt(4) ng_l2cap_process_cmd_rej o usb/140477 usb [umass] [usb8] [patch] allow boot-time attachment of d o usb/140259 usb [libusb] [patch] [usb8] libusb-1.0 portability/compati o usb/140236 usb [msdosfs] [usb8] Labels wiped on external Journaled US o usb/140160 usb [usb8] [acpi] USB ports are no longer "active" after A s usb/139990 usb [panic] [patch] [usb67] Kernel frequently panics after a usb/139598 usb [umass] [usb8] CAM reports "xptioctl: put "device pass o usb/139243 usb [uhci] [usb67] unplug prolific USB serial -> uhci_abor o usb/138915 usb [patch] [usb8] [usb67] add support for SheevaPlug seri a usb/138904 usb [rum] [panic] [usb67] unpluging USB wifi card panics s f usb/138882 usb [ohci] [panic] [usb67] Can't install FreeBSD 7.2 due t a usb/138879 usb [uftdi] [patch] Patch to add support for CTI USB-Mini o usb/138798 usb [boot] [usb8] 8.0-BETA4 can't boot from USB flash driv o usb/138659 usb [usb8][uftdi] driver broken in RELENG_8/CURRENT o usb/138570 usb [usb] [panic] USB mass device panics current 7.2-STABL o usb/138175 usb [usb67] [boot] System cannot boot, when USB reader wit o usb/138172 usb [u3g] [patch] [usb67] Additional dev id for u3g (Optio o usb/138138 usb [u3g] [patch] [usb67] Novatel U760 for u3g (Verizon an o usb/138124 usb [snd_uaudio] [usb8] Axed uaudio functionality in the u o usb/138119 usb [usb67] [usb8] MultiBay CDROM (probably on USB bus) is o usb/137872 usb [usb67] [boot] slow booting on usb flash drive o usb/137806 usb [ukbd] [usb67] USB keyboard doesn't work until it's un o usb/137763 usb [usb67][ukbd] Logitech wireless keyboard media keys no o usb/137616 usb [usb67][usb8][usbdevs] [patch]: usbdevs update: Please o usb/137377 usb [usb8] request support for Huawei E180 o usb/137341 usb [usb8][rum] driver if_rum doesn't work at all and thro f usb/137190 usb [usb8][patch] inhibit spurious button releases for som o usb/137189 usb [usb8][patch] create and use sysctl nodes for HID repo p usb/137188 usb [usb8][patch] correctly handle USB report descriptors f bin/137180 usb [build] [patch] building world for 8.0-BETA2 fails on o usb/137129 usb [ums] [usb8] SteelSeries Ikari USB laser mouse not att p usb/136761 usb [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H o usb/135938 usb [aue] [usb67] aue driver only passes traffic in promis o usb/135575 usb [usbdevs] [patch] [usb67] Add HTC Wizard phone vid/pid o usb/135542 usb [keyboard] boot loader does not work with a usb keyboa o usb/135348 usb [umass] [patch] USB Drive Hangs with ZFS (JMicron USB2 o usb/135206 usb machine reboots when inserted USB device o usb/135200 usb SAMSUNG i740 usb mass: Synchronize cache failed, statu o usb/135182 usb UMASS quirk - Olympus FE20 camera o usb/134950 usb Lowering DTR for USB-modem via ubsa is not possible o usb/134633 usb Add support for WILLCOM03(SHARP smart phone) o usb/134631 usb [usbdevs] [patch] WiSPY DBx support requires usb tweak o usb/134299 usb Kernel Panic plugging in MF626 USB UMTS Stick u3g o usb/134193 usb System freeze on usb MP3 player insertion o usb/134117 usb [Patch] Add support for 'Option GlobeTrotter HSDPA Mod o usb/134085 usb [umass] Adding usb quirk for Sony USB flash drive o usb/133989 usb [usb8] [ukbd] USB keyboard dead at mountroot> prompt o usb/133712 usb [ural] [patch] RE: Fixed an issue with ural(4) that wa o usb/133390 usb umass crashes system in 7.1 when Olympus D-540 attache o usb/133296 usb [rum] driver not working properly in hostap mode p usb/132799 usb [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA o usb/132785 usb [usb] [patch] Gemtech remote powersocket is classed as o usb/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb [hang] Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] [rum] Kernel panic after NOMEM caused by o usb/132066 usb [ukbd] Keyboard failure USB keyboard DELL 760 o usb/132036 usb [panic] page fault when connecting Olympus C740 camera o usb/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb [usbdevs] [patch] Additional product identification co o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c o usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [usb8] DVD drive detects as 'da' device o usb/129945 usb [usb67] [usbdevs] [patch] add u3g support for Longchee o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [usb67] [patch] add support for ZTE AC8700 mode o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [usb67] [patch] Liebert UPS being assigned u o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb67] [patch] uaudio is not full duplex p usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive o usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup p usb/127549 usb [umass] [usb67] [patch] Meizu MiniPlayer M6 (SL) requi f usb/127543 usb [patch] [ubsa] Support Option Globetrotter HSDPA modem s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should p docs/127406 usb [patch] update umodem man page: Sony Ericsson W810i o usb/127342 usb [boot] [panic] enabling usb keyboard and mouse support o usb/127248 usb [ucom] panic while uplcom devices attach and detach o usb/127222 usb [ohci] Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c o usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o kern/124130 usb [usb] gmirror fails to start usb devices that were pre o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122621 usb [new driver] [patch] New driver for Sierra Wireless 3G o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122025 usb [uscanner] [patch] uscanner does not attach to Epson R o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] [panic] FreeBSD fails to boot with usb legacy s o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [snd_uaudio] [patch] Not possible to record with Plant o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [usb67] [usb8] [umass] [patch] Problem with connection o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff o usb/113060 usb [usb67] [ulpt] [patch] Samsung printer not working in o usb/110856 usb [usb67] [ugen] [patch] interrupt in msgs are truncated s usb/108344 usb [usb67] [atausb] [panic] kernel with atausb panics whe o usb/107827 usb [usb67] [ohci] [panic] ohci_add_done addr not found o usb/107388 usb [usb67] [usb8] [new driver] [patch] add utoppy device o usb/107243 usb [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q o usb/106041 usb [usb67] [usb8] [request] FreeBSD does not recognise Mu o usb/105361 usb [usb67] [panic] Kernel panic during unmounting mass st s usb/103917 usb [usb67] [uhub] USB driver reports "Addr 0 should never o usb/103418 usb [usb67] [usb8] [patch] [request] usbhidctl(8) add abil o usb/103046 usb [usb67] [ulpt] [patch] ulpt event driven I/O with sele o usb/101775 usb [usb67] [usb8] [libusbhid] [patch] possible error in r o usb/101761 usb [usb67] [patch] [request] usb.h: increase maximal size o usb/100746 usb [usb67] [ukbd] system does not boot due to USB keyboar o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o kern/99200 usb [bluetooth] SMP-Kernel crashes reliably when Bluetooth o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91629 usb [usb] usbd_abort_pipe() may result in infinite loop o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [sound] [hang] Use of sound mixer causes system freeze o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75797 usb [sound] [regression] 5.3-STABLE(2005 1/4) detect USB h o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 359 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Jul 5 17:28:00 2010 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A747106566C for ; Mon, 5 Jul 2010 17:28:00 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 312758FC1A for ; Mon, 5 Jul 2010 17:27:59 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o65HRx8r007074 for ; Mon, 5 Jul 2010 11:27:59 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o65HRxEw007071 for ; Mon, 5 Jul 2010 11:27:59 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 5 Jul 2010 11:27:59 -0600 (MDT) From: Warren Block To: usb@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (wonkity.com [127.0.0.1]); Mon, 05 Jul 2010 11:27:59 -0600 (MDT) Cc: Subject: usbhidctl(1) with 8.x X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 17:28:00 -0000 Is usbhidctl(1) functional under 8.x? With a USB joystick and 8-stable: Unknown USB device: vendor 0x046d product 0xc207 bus uhub8 uhid0: on usbus3 % ls -l /dev/uhid* crw-r--r-- 1 root operator 0, 122 Jul 5 11:25 /dev/uhid0 % usbhidctl -f /dev/uhid0 -a usbhidctl: USB_SET_IMMED: Device not configured From owner-freebsd-usb@FreeBSD.ORG Mon Jul 5 17:34:50 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD5BA1065688 for ; Mon, 5 Jul 2010 17:34:50 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe14.swip.net [212.247.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id 5DE6B8FC19 for ; Mon, 5 Jul 2010 17:34:49 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=wbKXeunVgZ0A:10 a=8nJEP1OIZ-IA:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=YDqYQW4guw463Qz4-f8A:9 a=S0moPsi2btWnHufTyiLeWUXvxEEA:4 a=wPNLvfGTeEIA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe14.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 638230153; Mon, 05 Jul 2010 19:34:48 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 5 Jul 2010 19:31:54 +0200 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; amd64; ; ) References: In-Reply-To: X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201007051931.54891.hselasky@c2i.net> Cc: Subject: Re: usbhidctl(1) with 8.x X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 17:34:50 -0000 On Monday 05 July 2010 19:27:59 Warren Block wrote: > Is usbhidctl(1) functional under 8.x? With a USB joystick and 8-stable: > > Unknown USB device: vendor 0x046d product 0xc207 bus uhub8 > uhid0: > on usbus3 > > % ls -l /dev/uhid* > crw-r--r-- 1 root operator 0, 122 Jul 5 11:25 /dev/uhid0 > % usbhidctl -f /dev/uhid0 -a > usbhidctl: USB_SET_IMMED: Device not configured Yes, it should work, but I have not tested it recently. To enable more debugging: sysctl hw.usb.uhid.debug=15 --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Jul 5 18:33:07 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6A291065674 for ; Mon, 5 Jul 2010 18:33:07 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A27A28FC16 for ; Mon, 5 Jul 2010 18:33:07 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o65IX3YU007344; Mon, 5 Jul 2010 12:33:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o65IX3WS007341; Mon, 5 Jul 2010 12:33:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 5 Jul 2010 12:33:03 -0600 (MDT) From: Warren Block To: Hans Petter Selasky In-Reply-To: <201007051931.54891.hselasky@c2i.net> Message-ID: References: <201007051931.54891.hselasky@c2i.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (wonkity.com [127.0.0.1]); Mon, 05 Jul 2010 12:33:03 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: usbhidctl(1) with 8.x X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 18:33:08 -0000 On Mon, 5 Jul 2010, Hans Petter Selasky wrote: > On Monday 05 July 2010 19:27:59 Warren Block wrote: >> Is usbhidctl(1) functional under 8.x? With a USB joystick and 8-stable: >> >> Unknown USB device: vendor 0x046d product 0xc207 bus uhub8 >> uhid0: >> on usbus3 >> >> % ls -l /dev/uhid* >> crw-r--r-- 1 root operator 0, 122 Jul 5 11:25 /dev/uhid0 >> % usbhidctl -f /dev/uhid0 -a >> usbhidctl: USB_SET_IMMED: Device not configured > > Yes, it should work, but I have not tested it recently. > > To enable more debugging: > > sysctl hw.usb.uhid.debug=15 It shows a little more: ugen3.3: at usbus3 uhid_probe: uhid_probe: uhid_probe: uhid_attach: sc=0xc6c8aa80 uhid0: on usbus3 Another USB joystick shows sc=0xc6c89700 and also "Device not configured". From owner-freebsd-usb@FreeBSD.ORG Tue Jul 6 11:13:35 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE934106566C; Tue, 6 Jul 2010 11:13:35 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 413FC8FC16; Tue, 6 Jul 2010 11:13:34 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=zcK-Oe5qyR4A:10 a=yQWWgrYGNuUA:10 a=Q9fys5e9bTEA:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=dNvloOHWiUI_r7XJeSMA:9 a=PFLahZhmV4UC2N9BT3kA:7 a=ndzm61dUKtlIsfxLIV2CvRwUo5IA:4 a=PUjeQqilurYA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 353928684; Tue, 06 Jul 2010 13:13:33 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Tue, 6 Jul 2010 13:10:40 +0200 User-Agent: KMail/1.12.4 (FreeBSD/8.1-PRERELEASE; KDE/4.3.4; amd64; ; ) References: <201006230709.o5N79dxc081653@www.freebsd.org> In-Reply-To: <201006230709.o5N79dxc081653@www.freebsd.org> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201007061310.40333.hselasky@c2i.net> Cc: freebsd-gnats-submit@freebsd.org, "Dmitry S. Luhtionov" Subject: Re: usb/148080: usbconfig sometimes does not turn off the device X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 11:13:36 -0000 On Wednesday 23 June 2010 09:09:39 Dmitry S. Luhtionov wrote: > >Number: 148080 > >Category: usb > >Synopsis: usbconfig sometimes does not turn off the device > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Jun 23 07:10:04 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Dmitry S. Luhtionov > >Release: 8.0-STABLE amd64 > >Organization: > >Environment: > > FreeBSD po.netcom.dp.ua 8.0-STABLE FreeBSD 8.0-STABLE #0: Sun Jun 20 > 03:30:29 EEST 2010 > mitya@po.netcom.dp.ua:/usr/src/sys/amd64/compile/lan amd64 Update: There are going to be some patches into 9-current soon. --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Jul 6 11:20:04 2010 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F1F9106564A for ; Tue, 6 Jul 2010 11:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0E8AB8FC24 for ; Tue, 6 Jul 2010 11:20:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o66BK3jv090106 for ; Tue, 6 Jul 2010 11:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o66BK312090105; Tue, 6 Jul 2010 11:20:03 GMT (envelope-from gnats) Date: Tue, 6 Jul 2010 11:20:03 GMT Message-Id: <201007061120.o66BK312090105@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/148080: usbconfig sometimes does not turn off the device X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 11:20:04 -0000 The following reply was made to PR usb/148080; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: "Dmitry S. Luhtionov" , freebsd-gnats-submit@freebsd.org Subject: Re: usb/148080: usbconfig sometimes does not turn off the device Date: Tue, 6 Jul 2010 13:10:40 +0200 On Wednesday 23 June 2010 09:09:39 Dmitry S. Luhtionov wrote: > >Number: 148080 > >Category: usb > >Synopsis: usbconfig sometimes does not turn off the device > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Jun 23 07:10:04 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Dmitry S. Luhtionov > >Release: 8.0-STABLE amd64 > >Organization: > >Environment: > > FreeBSD po.netcom.dp.ua 8.0-STABLE FreeBSD 8.0-STABLE #0: Sun Jun 20 > 03:30:29 EEST 2010 > mitya@po.netcom.dp.ua:/usr/src/sys/amd64/compile/lan amd64 Update: There are going to be some patches into 9-current soon. --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Jul 6 18:20:03 2010 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D0671065678 for ; Tue, 6 Jul 2010 18:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 129C58FC14 for ; Tue, 6 Jul 2010 18:20:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o66IK204011299 for ; Tue, 6 Jul 2010 18:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o66IK2v2011298; Tue, 6 Jul 2010 18:20:02 GMT (envelope-from gnats) Date: Tue, 6 Jul 2010 18:20:02 GMT Message-Id: <201007061820.o66IK2v2011298@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Eimar Koort Cc: Subject: Re: usb/140928: [u3g] [usb8] [patch] ZTE CDMA2000 1X EV-DO (MG478/AC8700) is not working X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eimar Koort List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 18:20:03 -0000 The following reply was made to PR usb/140928; it has been noted by GNATS. From: Eimar Koort To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/140928: [u3g] [usb8] [patch] ZTE CDMA2000 1X EV-DO (MG478/AC8700) is not working Date: Tue, 6 Jul 2010 21:14:56 +0300 Works with 8.1. I think that this can be closed. From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 19:12:47 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD78F106564A for ; Wed, 7 Jul 2010 19:12:47 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 9E3B88FC1F for ; Wed, 7 Jul 2010 19:12:46 +0000 (UTC) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta10.westchester.pa.mail.comcast.net with comcast id f0FJ1e0041wpRvQ5A6zXAo; Wed, 07 Jul 2010 18:59:31 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta18.westchester.pa.mail.comcast.net with comcast id f6zV1e00Y3LrwQ23e6zWp4; Wed, 07 Jul 2010 18:59:31 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7111D9B423; Wed, 7 Jul 2010 11:59:28 -0700 (PDT) Date: Wed, 7 Jul 2010 11:59:28 -0700 From: Jeremy Chadwick To: "Mikhail T." Message-ID: <20100707185928.GA16180@icarus.home.lan> References: <4C34C5DE.7040007@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C34C5DE.7040007@aldan.algebra.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: re@freebsd.org, tom@hur.st, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 19:12:47 -0000 On Wed, Jul 07, 2010 at 02:22:22PM -0400, Mikhail T. wrote: > I'm upgrading several systems these days to the 8.1 (pre-release) > and have hit the following troubles... I could file a formal PR for > each, I suppose, but, maybe, this way will get the right people's > attention sooner. > > 2. > FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and > thus not an "option") -- the kernel-config files, that worked with > 7.x, break without this option in them (in addition to all the > nuisance, that's documented in UPDATING -- which, somehow, makes > the breakage acceptable). config(8) would not warn about this, but > kernel build fails. We don't use this option (meaning it's removed from our kernels). It's definitely not required. All it does is ensure your kernel can comprehend executables/binaries built on 7.x. > 3. > Likewise, having "device ugen" breaks config(8) -- another > undocumented incompatibility. This sounds like you not including all of the necessary USB/device framework in your kernel configuration. You're not providing enough output for us to help diagnose the problem, though. Be aware that config(8) changed during recent days and requires a rebuild, although the build infrastructure normally instructs you to do this (otherwise kernel won't build). I noticed it when upgrading from an "early" version of RELENG_8 to a more recent version, and it was kind enough to tell me to rebuild it. > 4. > The sio(4) is described in UPDATING as "removed", but rouses no > complaint from config(8) either. It just breaks the kernel > build... It should be an alias for uart, IMHO -- all I want is for > my serial ports to be usable, whether their driver is called > "Serial Input/Output" or "Universal Asynchronous Receiver and > Transmitter". I disagree (re: "it should be an alias"). sio(4) is deprecated (meaning it's not used by default any more), and it's left in the driver tree solely as a fall-back method if someone runs into uart(4) problems. I'm sure it'll eventually be removed, but for now, it remains. The point I'm going to make here is this: sio(4) is different than uart(4). "Aliasing" one to the other will do nothing but confuse folks. If we're going to do that, why not rename all of our Ethernet interfaces "ethX" and so on? ;-) I'll take a moment to point out that your complaints about the kernel configuration file, so far, seem to stem from you not "migrating" your kernel configuration from 7.x to 8.x. Things change -- that's the reality of the situation. The way I do this is, when upgrading major releases (7.x->8.x), to "start fresh" using GENERIC as my base template and then adding/adjusting while comparing against the older kernels' config. Others do it differently, this is just how I do it. > (BTW, about the /dev-entries -- do we /really/ have to change the > names of the serial port-devices every couple of years? It is > rather painful to reconfigure the fax- and ppp-software, etc.) How > does the Microsoft world manage to stay with the COM1, COM2 for > decades?) Like I said: things change. > 5. > One of the upgraded systems would repeatedly hang at boot, until I > disabled the on-board firewire-device through the BIOS... It was > not a problem under 7.x, although I don't know, whether the device > actually worked. This is a commonly-reported problem, assuming "at boot" you mean "while the kernel is starting". Or unless you're using a certain model of Shuttle box, but that turned out to be literally a BIOS bug: http://koitsu.wordpress.com/2009/05/22/shuttle-sg45h7-firewire-bug-in-bios-sg45u10o/ > 6. > Despite the reported improvements in the USB area, my USB keyboard > /still/ does not work during boot. It during POST and then after > the booting is complete. But in single-user mode -- no... Had to > fish-out the PS2 keyboard... This is also a commonly-reported problem (and one I've harped on as well). When you say "during boot": does it work during loader (the screen with the "FreeBSD" logo on it)? If the keyboard works during loader but not once the kernel + kernel USB stack loads (e.g. when booting into single-user), then look at the very bottom of this page for a couple things to try: http://wiki.freebsd.org/BugBusting/Commonly_reported_issues If the keyboard DOES NOT work during loader, then it sounds like your BIOS isn't setting the system up so that USB keyboards get emulated as PS/2 (this setup gets stomped by the kernel later, obviously). Usually BIOSes offer an option like "USB Legacy Enable" or "USB Keyboard Enable" which provides this functionality. It's important to remember that there is no USB stack loaded via the bootstraps, which focus on your system/BIOS. Linux and Solaris have the same problem, as I understand it. Welcome to PC architecture "evolution", if you can call it that. :-) Regardless, this is one of the reasons I still have not made the move to USB keyboards and stick with PS/2 keyboards on FreeBSD. > 7. > All my "dangerously dedicated" disks lost the "s1" in the > subdevice-names after the upgrade: /dev/da1s1d became /dev/da1d, > etc. I like the shorter names (and there are, indeed, no "slices" > there), but having to fix them manually upon reboot was unpleasant > and uncalled for. As with uart/sio, backward-compatibility aliases > are a fine idea and really improves user's experience... Again: things change. "Dangerously dedicated" disks are commonly deprecated at this point (as I understand it folks are trying to get away from them). GEOM takes care of this situation better than it used to. You'll probably find some other situations (using bsdlabel, etc. vs. using gpart (don't confuse this with GPT)) where things may get a little hairy based on your setup. I would have formatted the disk and gone from a clean slate. Re: aliases: see above. > 8. > I tried to do an install on one of the systems via netbooting > (pxeload) the disk1-image. It booted, but the sysinstall had to be > started manually and, once started, did not act the same as when > booted off of CD-ROM. Seems like a simple bit to correct so that > setting "init" to /usr/sbin/sysinstall/manually on every boot/ is > not necessary... Can't reproduce: http://jdc.parodius.com/freebsd/pxeboot_serial_install.html > 9. > The k8temp utility (installed by sysutils/k8temp > ), which worked fine on > both of my AMD-machines, no longer works on the Athlon one (still > works on the Opteron-based server). I reinstalled the port, but > that did not help -- the utility runs, but does not say anything. > Requeting debug-info is of little help: > > *root*@quokka:~ (101) k8temp > *root*@quokka:~ (102) k8temp -d > CPUID: Vendor: AuthenticAMD, 0x6a0: Model=0a Family=6+0 Stepping=0 > Advanced Power Management=0x1 > Temperature sensor: Yes > Frequency ID control: No > Voltage ID control: No > THERMTRIP support: No > HW Thermal control: No > SW Thermal control: No > 100MHz multipliers: No > HW P-State control: No > TSC Invariant: No Try loading the kernel module amdtemp and see if things improve. Be sure to read the man page. Hardware monitoring/thermal monitoring at this point is often implemented into the sysctl tree (Intel CPUs are done this way with coretemp(4), and ACPI thermal zones too). HTH. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 19:16:14 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 433BF106566C; Wed, 7 Jul 2010 19:16:14 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.swipnet.se [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id 486C18FC13; Wed, 7 Jul 2010 19:16:12 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=3vXfOHqyassA:10 a=hO-oPbc3tlwA:10 a=kj9zAlcOel0A:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=6I5d2MoRAAAA:8 a=7ZPwSmUIkKDfCbhwi0UA:9 a=Kj5IHaox4LK5jQf5aFUA:7 a=bJC06uc2dnVEk673HOXFIBPbPg8A:4 a=CjuIK1q_8ugA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 1206394479; Wed, 07 Jul 2010 21:16:11 +0200 From: Hans Petter Selasky To: Sam Leffler Date: Wed, 7 Jul 2010 21:13:16 +0200 User-Agent: KMail/1.12.4 (FreeBSD/8.1-PRERELEASE; KDE/4.3.4; amd64; ; ) X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201007072113.16320.hselasky@c2i.net> Cc: freebsd-current@freebsd.org, PseudoCylon , freebsd-usb@freebsd.org Subject: [panic] Race in IEEE802.11 layer towards device drivers X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 19:16:14 -0000 Hi, When supplying wpa_supplicant.conf with incorrect passwords, but a valid SSID, I have seen kernel panics several times when using USB based WLAN dongles. When only supplying a valid password, no panic has been seen. How to reproduce: 1) configure invalid password 2) wpa_cli: reconfigure 3) configure valid password 4) wpa_cli: reconfigure 5) goto 1 The USB commands which are executed inside the newstate callback usually take very little time, but still not as little time as PCI read/writes. I've forced slower operation in the newstate callback, and can reproduce warning printouts from the IEEE802.11 layer in FreeBSD. Try to apply the following patch to your USB code: http://p4web.freebsd.org/@@180604?ac=10 In my opinion the deferring of all states to a single task is wrong. There should be at least one task per possible state, and the queuing mechanism should follow the last-queued is last executed rule. This is not the case with the task-queue mechanism in the kernel. See the USB code's task-queue replacement which I think the IEEE802.11 stack in FreeBSD could take advantage of. src/sys/dev/usb/usb_process.c Description of panics. I didn't have core dump enabled on this box, so please bear over with the following hand-written notes: 1) A vap->iv_bss == NULL, inside ratectl task in RUM driver. 2) A memcpy() fails inside the iee80211...newstate_cb() 3) This and similar printouts are seen: wlan0: ieee80211_new_state_locked: pending AUTH -> ASSOC transition lost --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 19:21:29 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53B1E1065670; Wed, 7 Jul 2010 19:21:29 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id 8CCED8FC17; Wed, 7 Jul 2010 19:21:28 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o67IMM2q011821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jul 2010 14:22:23 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o67IMM55026248; Wed, 7 Jul 2010 14:22:22 -0400 Message-ID: <4C34C5DE.7040007@aldan.algebra.com> Date: Wed, 07 Jul 2010 14:22:22 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-stable@freebsd.org, re@freebsd.org, freebsd-usb@freebsd.org, tom@hur.st Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 19:21:29 -0000 I'm upgrading several systems these days to the 8.1 (pre-release) and have hit the following troubles... I could file a formal PR for each, I suppose, but, maybe, this way will get the right people's attention sooner. In no particular order: 1. A picture, that one of the systems was displaying at boot (and then used as a screen-saver), stopped showing properly. The colors are right, but the picture is distorted beyond recognition. The relevant part of loader.conf is: splash_pcx_load="YES" vesa_load="YES" bitmap_load="YES" bitmap_name="/boot/187426-9-quokka-dreaming.pcx" the picture file is identified as: PCX 772x551 772x551+0+0 8-bit PseudoClass 256c 454KB 0.039u 0:00.093 2. FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and thus not an "option") -- the kernel-config files, that worked with 7.x, break without this option in them (in addition to all the nuisance, that's documented in UPDATING -- which, somehow, makes the breakage acceptable). config(8) would not warn about this, but kernel build fails. 3. Likewise, having "device ugen" breaks config(8) -- another undocumented incompatibility. 4. The sio(4) is described in UPDATING as "removed", but rouses no complaint from config(8) either. It just breaks the kernel build... It should be an alias for uart, IMHO -- all I want is for my serial ports to be usable, whether their driver is called "Serial Input/Output" or "Universal Asynchronous Receiver and Transmitter". (BTW, about the /dev-entries -- do we /really/ have to change the names of the serial port-devices every couple of years? It is rather painful to reconfigure the fax- and ppp-software, etc.) How does the Microsoft world manage to stay with the COM1, COM2 for decades?) 5. One of the upgraded systems would repeatedly hang at boot, until I disabled the on-board firewire-device through the BIOS... It was not a problem under 7.x, although I don't know, whether the device actually worked. 6. Despite the reported improvements in the USB area, my USB keyboard /still/ does not work during boot. It during POST and then after the booting is complete. But in single-user mode -- no... Had to fish-out the PS2 keyboard... 7. All my "dangerously dedicated" disks lost the "s1" in the subdevice-names after the upgrade: /dev/da1s1d became /dev/da1d, etc. I like the shorter names (and there are, indeed, no "slices" there), but having to fix them manually upon reboot was unpleasant and uncalled for. As with uart/sio, backward-compatibility aliases are a fine idea and really improves user's experience... 8. I tried to do an install on one of the systems via netbooting (pxeload) the disk1-image. It booted, but the sysinstall had to be started manually and, once started, did not act the same as when booted off of CD-ROM. Seems like a simple bit to correct so that setting "init" to /usr/sbin/sysinstall/manually on every boot/ is not necessary... 9. The k8temp utility (installed by sysutils/k8temp ), which worked fine on both of my AMD-machines, no longer works on the Athlon one (still works on the Opteron-based server). I reinstalled the port, but that did not help -- the utility runs, but does not say anything. Requeting debug-info is of little help: *root*@quokka:~ (101) k8temp *root*@quokka:~ (102) k8temp -d CPUID: Vendor: AuthenticAMD, 0x6a0: Model=0a Family=6+0 Stepping=0 Advanced Power Management=0x1 Temperature sensor: Yes Frequency ID control: No Voltage ID control: No THERMTRIP support: No HW Thermal control: No SW Thermal control: No 100MHz multipliers: No HW P-State control: No TSC Invariant: No If any of the above can be corrected or, at least, documented, before release, we stand a little bit better chance of getting the praise otherwise well-deserved by FreeBSD... Thanks. Yours, -mi From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 19:35:11 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D852F1065676; Wed, 7 Jul 2010 19:35:11 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 844CC8FC16; Wed, 7 Jul 2010 19:35:11 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id o67JYtRG008224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 7 Jul 2010 12:34:55 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 786CD1CC0D; Wed, 7 Jul 2010 12:34:55 -0700 (PDT) To: "Mikhail T." In-reply-to: Your message of "Wed, 07 Jul 2010 14:22:22 EDT." <4C34C5DE.7040007@aldan.algebra.com> Date: Wed, 07 Jul 2010 12:34:55 -0700 From: "Kevin Oberman" Message-Id: <20100707193455.786CD1CC0D@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-07-07_03:2010-02-06, 2010-07-07, 2010-07-07 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-1005130000 definitions=main-1007070089 Cc: re@freebsd.org, tom@hur.st, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 19:35:11 -0000 > Date: Wed, 07 Jul 2010 14:22:22 -0400 > From: "Mikhail T." > Sender: owner-freebsd-stable@freebsd.org > > I'm upgrading several systems these days to the 8.1 (pre-release) and > have hit the following troubles... I could file a formal PR for each, I > suppose, but, maybe, this way will get the right people's attention sooner. > > In no particular order: > > 1. > A picture, that one of the systems was displaying at boot (and > then used as a screen-saver), stopped showing properly. The > colors are right, but the picture is distorted beyond recognition. > The relevant part of loader.conf is: > > splash_pcx_load="YES" > vesa_load="YES" > bitmap_load="YES" > bitmap_name="/boot/187426-9-quokka-dreaming.pcx" > > the picture file is identified as: > > PCX 772x551 772x551+0+0 8-bit PseudoClass 256c 454KB 0.039u > 0:00.093 > > 2. > FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and > thus not an "option") -- the kernel-config files, that worked with > 7.x, break without this option in them (in addition to all the > nuisance, that's documented in UPDATING -- which, somehow, makes > the breakage acceptable). config(8) would not warn about this, but > kernel build fails. FREEBSD_COMPAT7 is certainly an option. I build without it just fine. But "the kernel-config files, that worked with 7.x, break without this option in them" I think points to your real problem. > 3. > Likewise, having "device ugen" breaks config(8) -- another > undocumented incompatibility. It certainly does. ugen is no longer a valid device with the new USB stack in 8. (It is essentially built into the base USB driver.) It seems that you expect to be able to build a kernel for V8 using a V7 configuration file. THIS WILL NOT WORK! You must always re-do customizations when performing a major version upgrade. You should always start with GENERIC for a major version and make the required changes to it. I believe the current recommendation is to "include GENERIC" in your custom kernel configuration and then add or delete options and devices as desired. (This probably works best if your config file is close to GENERIC.) > 4. > The sio(4) is described in UPDATING as "removed", but rouses no > complaint from config(8) either. It just breaks the kernel > build... It should be an alias for uart, IMHO -- all I want is for > my serial ports to be usable, whether their driver is called > "Serial Input/Output" or "Universal Asynchronous Receiver and > Transmitter". > (BTW, about the /dev-entries -- do we /really/ have to change the > names of the serial port-devices every couple of years? It is > rather painful to reconfigure the fax- and ppp-software, etc.) How > does the Microsoft world manage to stay with the COM1, COM2 for > decades?) This would be nice, but the sio and uart drivers have co-existed for quite a while. They could not have the same name. Of course, a it would have been possible to rename the uart driver to sio when sio was removed or make it an alias, but that was not done. I suspect primarily to not break things when people discovered that sio and uart are NOT the same in the way they work. Not an issue for most, since they are close. > 5. > One of the upgraded systems would repeatedly hang at boot, until I > disabled the on-board firewire-device through the BIOS... It was > not a problem under 7.x, although I don't know, whether the device > actually worked. Odd. Sounds like a bug. I don't have a firewire port, so I have no idea about this. > 6. > Despite the reported improvements in the USB area, my USB keyboard > /still/ does not work during boot. It during POST and then after > the booting is complete. But in single-user mode -- no... Had to > fish-out the PS2 keyboard... All I can say is that it works fine for me. It may be tied to your building a V8 kernel with a V7 config. It may also be tied to having libusb from ports installed. Since libusb is now part of the base system, having the ports version around can break lots of USB stuff. > 7. > All my "dangerously dedicated" disks lost the "s1" in the > subdevice-names after the upgrade: /dev/da1s1d became /dev/da1d, > etc. I like the shorter names (and there are, indeed, no "slices" > there), but having to fix them manually upon reboot was unpleasant > and uncalled for. As with uart/sio, backward-compatibility aliases > are a fine idea and really improves user's experience... No, this one is due to a major re-structuring of how disks work in V8. As has been oft noted, "dangerously dedicated" is called that because it IS dangerous. While commonly used, it does not play nicely with standards and is prone to some fairly serious potential issues on upgrade. "dangerously dedicated" has been marked as "use it at your own risk", so you are likely to see issues (in this case a fairly minor one). > 8. > I tried to do an install on one of the systems via netbooting > (pxeload) the disk1-image. It booted, but the sysinstall had to be > started manually and, once started, did not act the same as when > booted off of CD-ROM. Seems like a simple bit to correct so that > setting "init" to /usr/sbin/sysinstall/manually on every boot/ is > not necessary... Have not tried this. > 9. > The k8temp utility (installed by sysutils/k8temp > ), which worked fine on > both of my AMD-machines, no longer works on the Athlon one (still > works on the Opteron-based server). I reinstalled the port, but > that did not help -- the utility runs, but does not say anything. > Requeting debug-info is of little help: > > *root*@quokka:~ (101) k8temp > *root*@quokka:~ (102) k8temp -d > CPUID: Vendor: AuthenticAMD, 0x6a0: Model=0a Family=6+0 Stepping=0 > Advanced Power Management=0x1 > Temperature sensor: Yes > Frequency ID control: No > Voltage ID control: No > THERMTRIP support: No > HW Thermal control: No > SW Thermal control: No > 100MHz multipliers: No > HW P-State control: No > TSC Invariant: No k8temp is for older AMD system running K8 cores. It has been mostly replaced with amdtemp which works on newer cores. I'm not sure if amdtemp will work on K8 cores, though. > If any of the above can be corrected or, at least, documented, before > release, we stand a little bit better chance of getting the praise > otherwise well-deserved by FreeBSD... Thanks. Yours, Documentation in FreeBSD seems quite a bit better than that of other open source projects, but it is not perfect and the handbook, in particular, will always lag a bit. Feel free to contribute suggested changes to the documentation team (doc@). I hope to spend a bit of time in this area after I retire. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 20:17:44 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2EA3106564A; Wed, 7 Jul 2010 20:17:44 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id 638048FC19; Wed, 7 Jul 2010 20:17:44 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o67KHgdt002213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jul 2010 16:17:43 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o67KHgwY031390; Wed, 7 Jul 2010 16:17:42 -0400 Message-ID: <4C34E0E6.9070801@aldan.algebra.com> Date: Wed, 07 Jul 2010 16:17:42 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: Jeremy Chadwick References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> In-Reply-To: <20100707185928.GA16180@icarus.home.lan> Content-Type: multipart/mixed; boundary="------------000305090006040403060807" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: re@freebsd.org, tom@hur.st, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 20:17:44 -0000 This is a multi-part message in MIME format. --------------000305090006040403060807 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 07.07.2010 14:59, Jeremy Chadwick ???????(??): >> FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and >> thus not an "option") -- the kernel-config files, that worked with >> 7.x, break without this option in them (in addition to all the >> nuisance, that's documented in UPDATING -- which, somehow, makes >> the breakage acceptable). config(8) would not warn about this, but >> kernel build fails. >> > We don't use this option (meaning it's removed from our kernels). It's > definitely not required. All it does is ensure your kernel can > comprehend executables/binaries built on 7.x. > Attached is the kernel config-file (i386), that worked fine under 7.x. The kernel-compile will break (some *freebsd7* structs undefined), without the COMPAT_FREEBSD7 option. Try it for yourself... >> 3. Likewise, having "device ugen" breaks config(8) -- another >> undocumented incompatibility. >> > This sounds like you not including all of the necessary USB/device > framework in your kernel configuration. You're not providing enough > output for us to help diagnose the problem, though. > Put "device ugen" back into the attached kernel-config file and see config's error yourself. >> 4. The sio(4) is described in UPDATING as "removed", but rouses no >> complaint from config(8) either. It just breaks the kernel >> build... It should be an alias for uart, IMHO -- all I want is for >> my serial ports to be usable, whether their driver is called >> "Serial Input/Output" or "Universal Asynchronous Receiver and >> Transmitter". >> > I disagree (re: "it should be an alias"). sio(4) is deprecated (meaning > it's not used by default any more), and it's left in the driver tree > solely as a fall-back method if someone runs into uart(4) problems. If it were merely "deprecated" it would've still worked. It does not -- put "device sio" into the attached kernel-config and try building -- you'll get the compile-error. Whether deliberately or through bit-rot, uart /replaced/ sio... > I'll take a moment to point out that your complaints about the kernel > configuration file, so far, seem to stem from you not "migrating" your > kernel configuration from 7.x to 8.x. Things change -- that's the > reality of the situation. > > The way I do this is, when upgrading major releases (7.x->8.x), to > "start fresh" using GENERIC as my base template and then > adding/adjusting while comparing against the older kernels' config. > Others do it differently, this is just how I do it. > Yes, your way is fine. But so is mine. It is perfectly reasonable to expect my method to work just as well -- the 7->8 is not revolutionary, but simply the next step. I read the "UPDATING" file and, though annoyed a little, took care of things mentioned in there... The remaining things are enumerated here... >> (BTW, about the /dev-entries -- do we /really/ have to change the >> names of the serial port-devices every couple of years? It is >> rather painful to reconfigure the fax- and ppp-software, etc.) How >> does the Microsoft world manage to stay with the COM1, COM2 for >> decades?) >> > Like I said: things change. > Well, pardon the political pun, but I don't believe in change for the sake of change. These particular changes are gratuitous. If sio is no longer available -- and replaced by uart, why change the /dev-entries?.. >> 5. One of the upgraded systems would repeatedly hang at boot, until I >> disabled the on-board firewire-device through the BIOS... It was >> not a problem under 7.x, although I don't know, whether the device >> actually worked. >> > This is a commonly-reported problem, assuming "at boot" you mean "while > the kernel is starting". Or unless you're using a certain model of > Shuttle box, but that turned out to be literally a BIOS bug: > > http://koitsu.wordpress.com/2009/05/22/shuttle-sg45h7-firewire-bug-in-bios-sg45u10o/ > No, this is not it /at all/. The link above describes a crash in the BIOS (and no POST), if firewire circuitry is disabled in BIOS. My problem is with FreeBSD kernel hanging on boot, if the firewire circuitry is enabled in BIOS. The boot was fine under 7.x, so this can not be due to a BIOS-bug -- the only thing, that changed, is the OS... > This is also a commonly-reported problem (and one I've harped on as > well). When you say "during boot": does it work during loader (the > screen with the "FreeBSD" logo on it)? > Yes. > If the keyboard works during loader but not once the kernel + kernel USB > stack loads (e.g. when booting into single-user), then look at the very > bottom of this page for a couple things to try: > > http://wiki.freebsd.org/BugBusting/Commonly_reported_issues > Will do, thanks! Still, I was hoping, things will "just work" with 8.1... > Regardless, this is one of the reasons I still have not made the move to > USB keyboards and stick with PS/2 keyboards on FreeBSD. > While renovating the house, I ran USB-, audio-, and video-cables through the walls from "server room" to the office, so I can sit in front of the monitors and keyboard/mouse, while the actual computers are well insulated behind closed door. PS/2 cables can't run the same length, it turns out... >> 7. All my "dangerously dedicated" disks lost the "s1" in the >> subdevice-names after the upgrade: /dev/da1s1d became /dev/da1d, >> etc. I like the shorter names (and there are, indeed, no "slices" >> there), but having to fix them manually upon reboot was unpleasant >> and uncalled for. As with uart/sio, backward-compatibility aliases >> are a fine idea and really improves user's experience... >> > Again: things change. > Again: this particular change seems gratuitous. > "Dangerously dedicated" disks are commonly deprecated at this point (as > I understand it folks are trying to get away from them). GEOM takes > care of this situation better than it used to. Yes, the "taking care" part is fine -- the filesystems all work. But the renaming is unwelcome. > Re: aliases: see above. > The only talk of aliases "above" was regarding sio/uart -- you said, sio is deprecated, but could exist alongside uart. That argument (however flawed it was, in my above-expressed opinion) does not apply here... >> 8. I tried to do an install on one of the systems via netbooting >> (pxeload) the disk1-image. It booted, but the sysinstall had to beclaimed >> started manually and, once started, did not act the same as when >> booted off of CD-ROM. Seems like a simple bit to correct so that >> setting "init" to /usr/sbin/sysinstall/manually on every boot/ is >> not necessary... >> > Can't reproduce: > http://jdc.parodius.com/freebsd/pxeboot_serial_install.html > Yes, you can -- you extract the CD-image there (doubling the storage requirements), and then modify the loader.conf . That modification should not be necessary -- the thing ought to figure the situation out automatically. That it does not (not quite), was my complaint, although I was following a different recipe . > > Try loading the kernel module amdtemp and see if things improve. Be > sure to read the man page. > Loading amdtemp was not necessary on the Opteron system, where the k8temp utility "just works" even after the upgrade. Doing it did not help the Athlon system, where k8temp continues to not work... Yours, -mi --------------000305090006040403060807 Content-Type: text/plain; name="Quokka" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Quokka" # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.18 2009/06/18 06:03:58 yongari Exp $ #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident Quokka # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options UFS_GJOURNAL # Enable gjournal-based UFS journaling #options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD # Network Lock Manager #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework #options GEOM_PART_GPT # GUID Partition Tables. #options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AUDIT # Security event auditing #options KDTRACE_HOOKS # Kernel DTrace hooks # To make an SMP kernel, the next two lines are needed #options SMP # Symmetric MultiProcessor Kernel #device apic # I/O APIC # CPU frequency control device cpufreq # Bus support. #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Power management support (see NOTES for more options) device apm # Add suspend/resume support for the i8254. device ipmi device smapi device smbios device pmtimer # Adjust system timer at wakeup time device smb device smbus device nfpm device nfsmb # Serial (COM) ports device uart # Generic UART driver # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device nfe # nVidia nForce MCP on-board Ethernet device nve # nVidia nForce MCP on-board Ethernet device fxp # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support #device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) device fwip # IP over FireWire (RFC 2734,3146) device dcons # Dumb console driver device dcons_crom # Configuration ROM for dcons device sound device snd_ich --------------000305090006040403060807-- From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 20:50:50 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD8F31065676; Wed, 7 Jul 2010 20:50:50 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout023.mac.com (asmtpout023.mac.com [17.148.16.98]) by mx1.freebsd.org (Postfix) with ESMTP id AF10D8FC17; Wed, 7 Jul 2010 20:50:50 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from macbook-pro.lan.xcllnt.net (mail.xcllnt.net [75.101.29.67]) by asmtp023.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0L5700LUFGK7TI00@asmtp023.mac.com>; Wed, 07 Jul 2010 13:50:32 -0700 (PDT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1004200000 definitions=main-1007070094 X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2010-07-07_03:2010-02-06, 2010-07-07, 2010-07-07 signatures=0 From: Marcel Moolenaar In-reply-to: Date: Wed, 07 Jul 2010 13:50:30 -0700 Message-id: <779BFD8C-962A-4577-B794-6AE2B946F4DF@mac.com> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> To: Randi Harper X-Mailer: Apple Mail (2.1081) Cc: "Mikhail T." , Jeremy Chadwick , freebsd-stable@freebsd.org, tom@hur.st, freebsd-usb@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 20:50:50 -0000 On Jul 7, 2010, at 1:34 PM, Randi Harper wrote: >> Well, pardon the political pun, but I don't believe in change for the sake >> of change. These particular changes are gratuitous. If sio is no longer >> available -- and replaced by uart, why change the /dev-entries?.. > > These changes aren't gratuitous. Did you read the commit messages > behind each of the changes? I'm guessing that you haven't. Not to mention that if you change uart(4) to create dev entries like sio(4) after uart(4) has been in the tree for more than 6 years creating ttyu* entries, you actually introduce a gratuitous change. It's all about perspective... -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 20:52:34 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 281D01065678; Wed, 7 Jul 2010 20:52:34 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id CFB0B8FC12; Wed, 7 Jul 2010 20:52:33 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o67KqWXQ008491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jul 2010 16:52:32 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o67KqWtd009492; Wed, 7 Jul 2010 16:52:32 -0400 Message-ID: <4C34E910.5020007@aldan.algebra.com> Date: Wed, 07 Jul 2010 16:52:32 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: Randi Harper References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: tom@hur.st, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Jeremy Chadwick Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 20:52:34 -0000 07.07.2010 16:34, Randi Harper ???????(??): > >> Attached is the kernel config-file (i386), that worked fine under 7.x. The >> kernel-compile will break (some *freebsd7* structs undefined), without the >> COMPAT_FREEBSD7 option. Try it for yourself... >> > Don't use a kernel config from 7. We've already told you this. > Your "telling" me this is just as valid as warning me against using computer-cases of a particular color. It is a silly requirement. My expecting things, that worked for 7, to work in 8 is reasonable. There may be (documented!) exceptions, but it ought to "just work". >> Yes, your way is fine. But so is mine. It is perfectly reasonable to expect >> my method to work just as well -- the 7->8 is not revolutionary, but simply >> the next step. I read the "UPDATING" file and, though annoyed a little, took >> care of things mentioned in there... The remaining things are enumerated >> here... >> > Your way clearly isn't fine, as it doesn't work. > That's an obviously flawed argument -- this line of thinking can be used against ANY ONE reporting ANY BUG -- if one has a problem, then one's way of doing things "clearly isn't fine". > > These changes aren't gratuitous. Did you read the commit messages > behind each of the changes? I'm guessing that you haven't. > No, and I'm not going to. A commercial OS would've been the laughing stock, if one hand to change C: to 1: between releases, for example... >> >> Again: this particular change seems gratuitous. >> > It's not. You didn't bother researching before complaining. I bothered to type up my list. Presumably, problem-reports are welcome. I've been a Unix-user since 1990, a FreeBSD user since 1993 (or 94?), and a project-member for a decade. If *I* have a problem, then newer users certainly will too. And, guess what, they'll simply go with something, that does not give as much grief... > To put it in simple terms, there were changes made to geom, and the way that > sysinstall writes out dedicated disks wasn't compatible. Search the > mailing list archives. > If this is a known problem, it is even more of an outrage, that some shim was not introduced to keep the users from hitting this particular bump. > > The modification should be necessary. Why? Why should a netboot act differently from a local boot from CD? > Just because you don't want to > make the modification doesn't mean it was made that way by accident. > No, I never claimed this to have been an accident... > That variable can be set to any number of things. We don't advertise > the iso image just working out of the box for pxe booting. You don't. But there is very little, that needs to be added there for it to "just work" over both netboot and local CD, and you should do it, instead of arguing with me here... No, I don't know, what it is exactly, but I'm quite certain, it can't be very much. > In fact, the article about PXE booting on the official freebsd website says > nothing about using the ISO. You just found some article that said it > was possible (and it is) and complained because you didn't like the > process? > Yes, exactly. I didn't like process -- it is needlessly complicated. The same CD-image, /should/ also be usable "out of the box" for netbooting. > > Funny. It works just fine in 8.0 on my Athlon. Have you tried updating > the port? Yes, I have -- and I said so in my very first e-mail on this subject. For someone, who expects people to "research mailing lists", you do a terrible job of following a one-day-old thread... > Also, even if it didn't work, this is an issue you should > take up with the author of the port. Tom -- the maintainer -- is still in CC... > > > From the man page: > > The amdtemp driver provides support for the on-die digital thermal sensor > present in AMD K8, K10 and K11 processors. > I know nothing about the driver. But a utility I regularly used stopped working after upgrade, so I added that to my list of upgrade-related grudges. -mi From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 21:04:39 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F098106566C for ; Wed, 7 Jul 2010 21:04:39 +0000 (UTC) (envelope-from sektie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3B4E08FC08 for ; Wed, 7 Jul 2010 21:04:38 +0000 (UTC) Received: by vws6 with SMTP id 6so169195vws.13 for ; Wed, 07 Jul 2010 14:04:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=xc5fmuLDhFlzPLrK5MIEfUUF/cJSIUFGO2Oc+1Jh8+c=; b=h4VIQf6xDRswrShRQzEYBrXGDjYRXeT8Z1ruNpqwezp3nvrpuulvLCvpH65mjFWZXg J2xoQSXiIOaWVLMQ+yKKyQQ/QftjFYz+ENU5yspNJCn1r5fwFNVAEizUe2FX231K03PJ 9Bo2aX0aEjPVvjr5L7tBcl+az2OST+Te2TVng= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=N6CXlZb+g7uE62ySbZ+WEN4EXDtv9aC0SgUDDJCpdrhuvKlpzLORdDrenDuip7E0zX YbObEuWe1DKWAmO9K/xmGc1EWH4dm2t4NByDFiTxdwnOyDtab477Hz/lnWTDIhYhkHjx 8fDWecaJ+Gse5pVRaIpjII/6A1ukxnwF8kCac= MIME-Version: 1.0 Received: by 10.220.100.213 with SMTP id z21mr3662817vcn.141.1278534875726; Wed, 07 Jul 2010 13:34:35 -0700 (PDT) Sender: sektie@gmail.com Received: by 10.220.174.42 with HTTP; Wed, 7 Jul 2010 13:34:35 -0700 (PDT) In-Reply-To: <4C34E0E6.9070801@aldan.algebra.com> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> Date: Wed, 7 Jul 2010 13:34:35 -0700 X-Google-Sender-Auth: 1mNJlCVGkBVZtfSpguasWkxdQpM Message-ID: From: Randi Harper To: "Mikhail T." Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: tom@hur.st, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Jeremy Chadwick Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 21:04:39 -0000 On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. wrot= e: > 07.07.2010 14:59, Jeremy Chadwick ???????(??): >>> >>> =A0 =A0 =A0FREEBSD_COMPAT7 kernel option is, apparently, a requirement = (and >>> =A0 =A0 =A0thus not an "option") -- the kernel-config files, that worke= d with >>> =A0 =A0 =A07.x, break without this option in them (in addition to all t= he >>> =A0 =A0 =A0nuisance, that's documented in UPDATING -- which, somehow, m= akes >>> =A0 =A0 =A0the breakage acceptable). config(8) would not warn about thi= s, but >>> =A0 =A0 =A0kernel build fails. >>> >> >> We don't use this option (meaning it's removed from our kernels). =A0It'= s >> definitely not required. =A0All it does is ensure your kernel can >> comprehend executables/binaries built on 7.x. >> > > Attached is the kernel config-file (i386), that worked fine under 7.x. Th= e > kernel-compile will break (some *freebsd7* structs undefined), without th= e > COMPAT_FREEBSD7 option. Try it for yourself... Don't use a kernel config from 7. We've already told you this. >>> >>> =A0 3. Likewise, having "device ugen" breaks config(8) -- another >>> =A0 =A0 =A0undocumented incompatibility. >>> >> >> This sounds like you not including all of the necessary USB/device >> framework in your kernel configuration. =A0You're not providing enough >> output for us to help diagnose the problem, though. >> > > Put "device ugen" back into the attached kernel-config file and see confi= g's > error yourself. >>> >>> =A0 4. The sio(4) is described in UPDATING as "removed", but rouses no >>> =A0 =A0 =A0complaint from config(8) either. It just breaks the kernel >>> =A0 =A0 =A0build... It should be an alias for uart, IMHO -- all I want = is for >>> =A0 =A0 =A0my serial ports to be usable, whether their driver is called >>> =A0 =A0 =A0"Serial Input/Output" or "Universal Asynchronous Receiver an= d >>> =A0 =A0 =A0Transmitter". >>> >> >> I disagree (re: "it should be an alias"). =A0sio(4) is deprecated (meani= ng >> it's not used by default any more), and it's left in the driver tree >> solely as a fall-back method if someone runs into uart(4) problems. > > If it were merely "deprecated" it would've still worked. It does not -- p= ut > "device sio" into the attached kernel-config and try building -- you'll g= et > the compile-error. Whether deliberately or through bit-rot, uart /replace= d/ > sio... >> >> I'll take a moment to point out that your complaints about the kernel >> configuration file, so far, seem to stem from you not "migrating" your >> kernel configuration from 7.x to 8.x. =A0Things change -- that's the >> reality of the situation. >> >> The way I do this is, when upgrading major releases (7.x->8.x), to >> "start fresh" using GENERIC as my base template and then >> adding/adjusting while comparing against the older kernels' config. >> Others do it differently, this is just how I do it. >> > > Yes, your way is fine. But so is mine. It is perfectly reasonable to expe= ct > my method to work just as well -- the 7->8 is not revolutionary, but simp= ly > the next step. I read the "UPDATING" file and, though annoyed a little, t= ook > care of things mentioned in there... The remaining things are enumerated > here... Your way clearly isn't fine, as it doesn't work. >>> >>> =A0 =A0 =A0(BTW, about the /dev-entries -- do we /really/ have to chang= e the >>> =A0 =A0 =A0names of the serial port-devices every couple of years? It i= s >>> =A0 =A0 =A0rather painful to reconfigure the fax- and ppp-software, etc= .) How >>> =A0 =A0 =A0does the Microsoft world manage to stay with the COM1, COM2 = for >>> =A0 =A0 =A0decades?) >>> >> >> Like I said: things change. >> > > Well, pardon the political pun, but I don't believe in change for the sak= e > of change. These particular changes are gratuitous. If sio is no longer > available -- and replaced by uart, why change the /dev-entries?.. These changes aren't gratuitous. Did you read the commit messages behind each of the changes? I'm guessing that you haven't. >>> >>> =A0 5. One of the upgraded systems would repeatedly hang at boot, until= I >>> =A0 =A0 =A0disabled the on-board firewire-device through the BIOS... It= was >>> =A0 =A0 =A0not a problem under 7.x, although I don't know, whether the = device >>> =A0 =A0 =A0actually worked. >>> >> >> This is a commonly-reported problem, assuming "at boot" you mean "while >> the kernel is starting". =A0Or unless you're using a certain model of >> Shuttle box, but that turned out to be literally a BIOS bug: >> >> >> http://koitsu.wordpress.com/2009/05/22/shuttle-sg45h7-firewire-bug-in-bi= os-sg45u10o/ >> > > No, this is not it /at all/. The link above describes a crash in the BIOS > (and no POST), if firewire circuitry is disabled in BIOS. My problem is w= ith > FreeBSD kernel hanging on boot, if the firewire circuitry is enabled in > BIOS. The boot was fine under 7.x, so this can not be due to a BIOS-bug -= - > the only thing, that changed, is the OS... Yes. Sometimes there are bugs that exist that aren't triggered until an external influence makes them apparent. >> >> This is also a commonly-reported problem (and one I've harped on as >> well). =A0When you say "during boot": does it work during loader (the >> screen with the "FreeBSD" logo on it)? >> > > Yes. >> >> If the keyboard works during loader but not once the kernel + kernel USB >> stack loads (e.g. when booting into single-user), then look at the very >> bottom of this page for a couple things to try: >> >> http://wiki.freebsd.org/BugBusting/Commonly_reported_issues >> > > Will do, thanks! Still, I was hoping, things will "just work" with 8.1... >> >> Regardless, this is one of the reasons I still have not made the move to >> USB keyboards and stick with PS/2 keyboards on FreeBSD. >> > > While renovating the house, I ran USB-, audio-, and video-cables through = the > walls from "server room" to the office, so I can sit in front of the > monitors and keyboard/mouse, while the actual computers are well insulate= d > behind closed door. PS/2 cables can't run the same length, it turns out..= . >>> >>> =A0 7. All my "dangerously dedicated" disks lost the "s1" in the >>> =A0 =A0 =A0subdevice-names after the upgrade: /dev/da1s1d became /dev/d= a1d, >>> =A0 =A0 =A0etc. I like the shorter names (and there are, indeed, no "sl= ices" >>> =A0 =A0 =A0there), but having to fix them manually upon reboot was unpl= easant >>> =A0 =A0 =A0and uncalled for. As with uart/sio, backward-compatibility a= liases >>> =A0 =A0 =A0are a fine idea and really improves user's experience... >>> >> >> Again: things change. >> > > Again: this particular change seems gratuitous. It's not. You didn't bother researching before complaining. To put it in simple terms, there were changes made to geom, and the way that sysinstall writes out dedicated disks wasn't compatible. Search the mailing list archives. >> >> "Dangerously dedicated" disks are commonly deprecated at this point (as >> I understand it folks are trying to get away from them). =A0GEOM takes >> care of this situation better than it used to. > > Yes, the "taking care" part is fine -- the filesystems all work. But the > renaming is unwelcome. >> >> Re: aliases: see above. >> > > The only talk of aliases "above" was regarding sio/uart -- you said, sio = is > deprecated, but could exist alongside uart. That argument (however flawed= it > was, in my above-expressed opinion) does not apply here... >>> >>> =A0 8. I tried to do an install on one of the systems via netbooting >>> =A0 =A0 =A0(pxeload) the disk1-image. It booted, but the sysinstall had= to >>> beclaimed >>> =A0 =A0 =A0started manually and, once started, did not act the same as = when >>> =A0 =A0 =A0booted off of CD-ROM. Seems like a simple bit to correct so = that >>> =A0 =A0 =A0setting "init" to /usr/sbin/sysinstall/manually on every boo= t/ is >>> =A0 =A0 =A0not necessary... >>> >> >> Can't reproduce: >> http://jdc.parodius.com/freebsd/pxeboot_serial_install.html >> > > Yes, you can -- you extract the CD-image there > > (doubling the storage requirements), and then modify the loader.conf > . Th= at > modification should not be necessary -- the thing ought to figure the > situation out automatically. That it does not (not quite), was my complai= nt, > although I was following a different recipe > . The modification should be necessary. Just because you don't want to make the modification doesn't mean it was made that way by accident. That variable can be set to any number of things. We don't advertise the iso image just working out of the box for pxe booting. In fact, the article about PXE booting on the official freebsd website says nothing about using the ISO. You just found some article that said it was possible (and it is) and complained because you didn't like the process? >> >> Try loading the kernel module amdtemp and see if things improve. =A0Be >> sure to read the man page. >> > > Loading amdtemp was not necessary on the Opteron system, where the k8temp > utility "just works" even after the upgrade. Doing it did not help the > Athlon system, where k8temp continues to not work... Funny. It works just fine in 8.0 on my Athlon. Have you tried updating the port? Also, even if it didn't work, this is an issue you should take up with the author of the port. If you had read the commit logs, you would have seen that the device was renamed because k8temp didn't make sense anymore. >From the man page: The amdtemp driver provides support for the on-die digital thermal sen= sor present in AMD K8, K10 and K11 processors. I am removing re@ from this thread. You might think about emailing the appropriate mailing lists with questions first before doing the equivalent of stomping your feet and asking to speak to the manager of the candy store, especially since many of your complaints are uninformed and bogus. -- randi From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 21:51:01 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E721D1065673; Wed, 7 Jul 2010 21:51:00 +0000 (UTC) (envelope-from sektie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7EC818FC22; Wed, 7 Jul 2010 21:51:00 +0000 (UTC) Received: by vws6 with SMTP id 6so230804vws.13 for ; Wed, 07 Jul 2010 14:50:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=Os5sZccNf+1UNum4YDDNO4NE9gZZkkxTWNRlMCMlR/k=; b=ZvqHlY4vCcLTpLOWwhfjit2x0p21AZFXbhU+l1v79USKxwQOiZPq5FTkxErI6o0c6/ PcXmDGlaKinRu0i8i/yklfVkSBEkuVnC8AsV4lrnR2EgYIxX2dP79AaGK2gVnwm5l/Lu CNb5EqH837wOyMRcEs5lhdhhXwtpjDBNH15Q8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=BwrrGHSHaXUv80WLSdLzvOrBMDAGRCeP4LFbO+G6HoSaa1jx2Ib3rV7cLXg2WzM20M kMKZjCENY7oS6BN4SIJtrRYRPeMN2yhndkJSJr4B1hxXLFGM+a5qgkPAHoitFCPcAbP6 Xd3BqyqT3EhjI/olxPXHUixCCcdkCPffAdOnw= MIME-Version: 1.0 Received: by 10.220.88.147 with SMTP id a19mr3668923vcm.259.1278539454989; Wed, 07 Jul 2010 14:50:54 -0700 (PDT) Sender: sektie@gmail.com Received: by 10.220.174.42 with HTTP; Wed, 7 Jul 2010 14:50:54 -0700 (PDT) In-Reply-To: <4C34E910.5020007@aldan.algebra.com> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> <4C34E910.5020007@aldan.algebra.com> Date: Wed, 7 Jul 2010 14:50:54 -0700 X-Google-Sender-Auth: 4RdDGJmQNXWtZ4RCprfWfwdm9N0 Message-ID: From: Randi Harper To: "Mikhail T." Content-Type: text/plain; charset=ISO-8859-1 Cc: tom@hur.st, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Jeremy Chadwick Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 21:51:01 -0000 On Wed, Jul 7, 2010 at 1:52 PM, Mikhail T. wrote: > Your "telling" me this is just as valid as warning me against using > computer-cases of a particular color. It is a silly requirement. My > expecting things, that worked for 7, to work in 8 is reasonable. There may > be (documented!) exceptions, but it ought to "just work". Ok. So I guess that a registry backup from Windows XP should work in Windows 7? We both know the world doesn't work that way. Not only is it ridiculous, it inhibits progress. Do you have any idea how many lines of code we have to deal with to plan for older setups? Even just with the stuff that I work on, it's a constant consideration to plan for existing setups and older hardware. Sometimes changes have to be made. For everything to always be compatible, you'd be overly complicating things that are already complicated enough, just because you think the process is inconvenient. In other words, submit a patch. > > Yes, your way is fine. But so is mine. It is perfectly reasonable to expect > my method to work just as well -- the 7->8 is not revolutionary, but simply > the next step. I read the "UPDATING" file and, though annoyed a little, took > care of things mentioned in there... The remaining things are enumerated > here... > > > Your way clearly isn't fine, as it doesn't work. > > > That's an obviously flawed argument -- this line of thinking can be used > against ANY ONE reporting ANY BUG -- if one has a problem, then one's way of > doing things "clearly isn't fine". I can't boot my computer without power. There must be a bug! If you're doing it wrong, then it's not a bug. Would you expect to be able to use a FreeBSD 2.x kernel config file with 8.x? > > These changes aren't gratuitous. Did you read the commit messages > behind each of the changes? I'm guessing that you haven't. > > > No, and I'm not going to. A commercial OS would've been the laughing stock, > if one hand to change C: to 1: between releases, for example... It's not like this was a minor version bump. You expect to treat it like it is. Most commercial operating systems don't have a simple upgrade path between major versions without other problems, such as application compatibility issues, requiring hardware upgrades, etc. > > Again: this particular change seems gratuitous. > > > It's not. You didn't bother researching before complaining. > > I bothered to type up my list. Presumably, problem-reports are welcome. I've > been a Unix-user since 1990, a FreeBSD user since 1993 (or 94?), and a > project-member for a decade. If I have a problem, then newer users certainly > will too. And, guess what, they'll simply go with something, that does not > give as much grief... PRs are welcome. Not uninformed rants on mailing lists with people that continue to argue because the world didn't start rotating a different direction at their command. I'm surprised you didn't mention your beard length. New users won't be using a FreeBSD 7 kernel config file. They'll be using a FreeBSD 8 kernel config file because they are new. They also won't care that we renamed the serial device between 7.x and 8.x. My logic rocks worlds. > > To put it in simple terms, there were changes made to geom, and the way that > sysinstall writes out dedicated disks wasn't compatible. Search the > mailing list archives. > > > If this is a known problem, it is even more of an outrage, that some shim > was not introduced to keep the users from hitting this particular bump. Yawn. Submit a patch. I dare you. > The modification should be necessary. > > Why? Why should a netboot act differently from a local boot from CD? Because you're booting over a freaking network and not physical media. I am running out of good metaphors for you. Just accept the fact that installing over different media types means the configuration is different. Go look up what that variable means. That might be a good start. > You don't. But there is very little, that needs to be added there for it to > "just work" over both netboot and local CD, and you should do it, instead of > arguing with me here... No, I don't know, what it is exactly, but I'm quite > certain, it can't be very much. So you don't know what the problem is, you don't really know why things have to be done this way, but you're sure that making this change will have no unintended effects. If I made all my commits that way, I'd break the build. Oh, wait... > In fact, the article about PXE booting on the official freebsd website says > nothing about using the ISO. You just found some article that said it > was possible (and it is) and complained because you didn't like the > process? > > > Yes, exactly. I didn't like process -- it is needlessly complicated. The > same CD-image, should also be usable "out of the box" for netbooting. It's obvious you hate process, as you don't file PRs against these problems, you don't search the mailing list, you don't post questions in appropriate places, etc. > Funny. It works just fine in 8.0 on my Athlon. Have you tried updating > the port? > > Yes, I have -- and I said so in my very first e-mail on this subject. For > someone, who expects people to "research mailing lists", you do a terrible > job of following a one-day-old thread... Mine works. Yours doesn't. Maybe you should use portsnap. > Also, even if it didn't work, this is an issue you should > take up with the author of the port. > > Tom -- the maintainer -- is still in CC... Then why didn't you send a separate email to him so he didn't have to wade through this entire post? > > >From the man page: > > The amdtemp driver provides support for the on-die digital thermal > sensor > present in AMD K8, K10 and K11 processors. > > > I know nothing about the driver. Clearly. > But a utility I regularly used stopped > working after upgrade, so I added that to my list of upgrade-related > grudges. I have a grudge as well. I have a grudge against users that abuse developers (oh, you have a reputation, sir), try to use their age (ie: years of experience in being wrong) as an "I know what I'm talking about" point, crosspost unnecessarily long emails, don't file PRs, don't send patches, don't read documentation, and refuse to listen to common sense. No one is agreeing with you. Everyone is telling you that you're wrong. Clearly, it's a conspiracy. -- randi From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 21:52:31 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9688D1065677 for ; Wed, 7 Jul 2010 21:52:31 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5052F8FC0C for ; Wed, 7 Jul 2010 21:52:31 +0000 (UTC) Received: by gxk24 with SMTP id 24so93580gxk.13 for ; Wed, 07 Jul 2010 14:52:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Tlnn91VYA6ikRrGZZYv12DJzHdgW11nv6qyc53zoLlU=; b=lBB4TdG5lrkZzFrg/DiDFBrsCB/n/xzCKwUAShOaR19R4oA4pXcXMBzxTAHLm4TGNC yn5+/y3+VxM4DS6lErDYUp8JAajoqiZrKu7HlzzOHepUP5mYTrvBepnqf7MURzx3HLqS VI/EBIKZP0UpE7+TCHS4l7p6Pl5Or6/UI4QLE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ejkx52jJKpCHtLgig0l8dycP+CdlMENf7e1BIfm0O5xBRtW0pbgdzSEA+MQ6H4i9IO Y9cq08w/8ZSCsoGUCb9xU9+YNbNa4LSVWZdbfo0UYObXHaZ1sXv3Io4ezcFKdLPQ+d0o RJ4d1B/wAoGK3RBv+krzdvQjihgfRjQST/uUc= MIME-Version: 1.0 Received: by 10.224.103.2 with SMTP id i2mr1861236qao.192.1278539065543; Wed, 07 Jul 2010 14:44:25 -0700 (PDT) Received: by 10.229.192.201 with HTTP; Wed, 7 Jul 2010 14:44:25 -0700 (PDT) In-Reply-To: <4C34E910.5020007@aldan.algebra.com> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> <4C34E910.5020007@aldan.algebra.com> Date: Wed, 7 Jul 2010 14:44:25 -0700 Message-ID: From: Garrett Cooper To: "Mikhail T." Content-Type: text/plain; charset=ISO-8859-1 Cc: tom@hur.st, Jeremy Chadwick , freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Randi Harper Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 21:52:31 -0000 On Wed, Jul 7, 2010 at 1:52 PM, Mikhail T. wrote: > 07.07.2010 16:34, Randi Harper ???????(??): >> >>> Attached is the kernel config-file (i386), that worked fine under 7.x. >>> The >>> kernel-compile will break (some *freebsd7* structs undefined), without >>> the >>> COMPAT_FREEBSD7 option. Try it for yourself... >>> >> >> Don't use a kernel config from 7. We've already told you this. >> > > Your "telling" me this is just as valid as warning me against using > computer-cases of a particular color. It is a silly requirement. My > expecting things, that worked for 7, to work in 8 is reasonable. There may > be (documented!) exceptions, but it ought to "just work". >>> >>> Yes, your way is fine. But so is mine. It is perfectly reasonable to >>> expect >>> my method to work just as well -- the 7->8 is not revolutionary, but >>> simply >>> the next step. I read the "UPDATING" file and, though annoyed a little, >>> took >>> care of things mentioned in there... The remaining things are enumerated >>> here... >>> >> >> Your way clearly isn't fine, as it doesn't work. >> > > That's an obviously flawed argument -- this line of thinking can be used > against ANY ONE reporting ANY BUG -- if one has a problem, then one's way of > doing things "clearly isn't fine". >> >> These changes aren't gratuitous. Did you read the commit messages >> behind each of the changes? I'm guessing that you haven't. >> > > No, and I'm not going to. A commercial OS would've been the laughing stock, > if one hand to change C: to 1: between releases, for example... >>> >>> Again: this particular change seems gratuitous. >>> >> >> It's not. You didn't bother researching before complaining. > > I bothered to type up my list. Presumably, problem-reports are welcome. I've > been a Unix-user since 1990, a FreeBSD user since 1993 (or 94?), and a > project-member for a decade. If *I* have a problem, then newer users > certainly will too. And, guess what, they'll simply go with something, that > does not give as much grief... >> >> To put it in simple terms, there were changes made to geom, and the way >> that >> sysinstall writes out dedicated disks wasn't compatible. Search the >> mailing list archives. >> > > If this is a known problem, it is even more of an outrage, that some shim > was not introduced to keep the users from hitting this particular bump. >> >> The modification should be necessary. > > Why? Why should a netboot act differently from a local boot from CD? There's a lot of secret sauce done for detecting whether or not you're booting from CD vs pxebooting in a release image, as well as within the sysinstall application as to what environment its dealing with, as well as what you get after things are done with a vanilla build and a sysinstall install (as I've discovered on my own). Unfortunately assuming both methods to produce the same result is flawed :(... Thanks, -Garrett From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 21:58:44 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F297106566C; Wed, 7 Jul 2010 21:58:44 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 6602D8FC08; Wed, 7 Jul 2010 21:58:44 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o67LlSdw094996; Wed, 7 Jul 2010 14:47:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=subject:from:reply-to:to:cc:in-reply-to:references: content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=mr1l2JIuvxHgKh9JU4eJFNl07lrdTNyq4+OlIY693ur1XTZKKf6dnv8aMNQEWmN7 From: Sean Bruno To: Jeremy Chadwick In-Reply-To: <20100707185928.GA16180@icarus.home.lan> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> Content-Type: text/plain; charset="UTF-8" Date: Wed, 07 Jul 2010 14:47:28 -0700 Message-ID: <1278539248.2512.87.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" , "Mikhail T." , "re@freebsd.org" , "tom@hur.st" , "freebsd-usb@freebsd.org" Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sbruno@freebsd.org List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 21:58:44 -0000 > > > 5. > > One of the upgraded systems would repeatedly hang at boot, until I > > disabled the on-board firewire-device through the BIOS... It was > > not a problem under 7.x, although I don't know, whether the device > > actually worked. > > This is a commonly-reported problem, assuming "at boot" you mean "while > the kernel is starting". Or unless you're using a certain model of > Shuttle box, but that turned out to be literally a BIOS bug: > > http://koitsu.wordpress.com/2009/05/22/shuttle-sg45h7-firewire-bug-in-bios-sg45u10o/ > Looking at this link, it doesn't match the described issue. Mikhail's machine would not boot *until* he disabled the firewire controller in the BIOS. The referenced issue on that Shuttle based machine talks about disabling the firewire controller and *then* it still being alive when the system powers on and crashing the system. I interpret this as a bug. Sean Also, I suck at reply-to. sean From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 22:00:41 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1112106566C; Wed, 7 Jul 2010 22:00:41 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.re1.yahoo.com (mrout2-b.corp.re1.yahoo.com [69.147.107.21]) by mx1.freebsd.org (Postfix) with ESMTP id 73F718FC14; Wed, 7 Jul 2010 22:00:41 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o67LkAQQ091073; Wed, 7 Jul 2010 14:46:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=subject:from:to:cc:in-reply-to:references:content-type:date: message-id:mime-version:x-mailer:content-transfer-encoding; b=jFKG52iczqSPzvqh1VmtAOgwoxvlMDfmdSGkxN9tgzf3igBsU1+O99gmTseaofXk From: Sean Bruno To: Jeremy Chadwick In-Reply-To: <20100707185928.GA16180@icarus.home.lan> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> Content-Type: text/plain; charset="UTF-8" Date: Wed, 07 Jul 2010 14:46:10 -0700 Message-ID: <1278539170.2512.86.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" , "Mikhail T." , "re@freebsd.org" , "tom@hur.st" , "freebsd-usb@freebsd.org" Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 22:00:41 -0000 > > > 5. > > One of the upgraded systems would repeatedly hang at boot, until I > > disabled the on-board firewire-device through the BIOS... It was > > not a problem under 7.x, although I don't know, whether the device > > actually worked. > > This is a commonly-reported problem, assuming "at boot" you mean "while > the kernel is starting". Or unless you're using a certain model of > Shuttle box, but that turned out to be literally a BIOS bug: > > http://koitsu.wordpress.com/2009/05/22/shuttle-sg45h7-firewire-bug-in-bios-sg45u10o/ > Looking at this link, it doesn't match the described issue. Mikhail's machine would not boot *until* he disabled the firewire controller in the BIOS. The referenced issue on that Shuttle based machine talks about disabling the firewire controller and *then* it still being alive when the system powers on and crashing the system. I interpret this as a bug. Sean From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 22:05:24 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B9F0106566C for ; Wed, 7 Jul 2010 22:05:24 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 462B08FC0A for ; Wed, 7 Jul 2010 22:05:23 +0000 (UTC) Received: by gxk24 with SMTP id 24so101931gxk.13 for ; Wed, 07 Jul 2010 15:05:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NZp6G3TlAXQwdwZAKzt9MN5Z6RL2/WvuA1bC2iI86qE=; b=WEEbycJZkQAFfLn8qPN8i2x7+M0D9X/QQL85WgPxL31U+cIpDmmfmVXYyfLGTeNRrI XEaG7UkBz7gFaQ5Qd34JD/GdsDa8tyewghbGIC+hugzw2xoxIiC4xHA4faqY1cx8SQUN rJymnVenZ6bS02BWIJHcgyP9cq/sKJ+A85kww= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=F/41B7M282H1RnrMv+eLxlRJzvmmU+Orujm70RIyRtjyavDfyHmO08SAdNitTAG00D zPRqejPG+6tE0zwnpB6iFG3oX4QL69w6bZKXNhSIZ+2yfqzGbrwzGfAlgfE3bVZbanDL 3XOBdxg8D+izM6ANUu1J6awcYgG0mj+XFfK80= MIME-Version: 1.0 Received: by 10.229.221.137 with SMTP id ic9mr4257988qcb.209.1278538760208; Wed, 07 Jul 2010 14:39:20 -0700 (PDT) Received: by 10.229.192.201 with HTTP; Wed, 7 Jul 2010 14:39:20 -0700 (PDT) In-Reply-To: <4C34E0E6.9070801@aldan.algebra.com> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> Date: Wed, 7 Jul 2010 14:39:20 -0700 Message-ID: From: Garrett Cooper To: "Mikhail T." Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, tom@hur.st, re@freebsd.org, freebsd-usb@freebsd.org, Jeremy Chadwick Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 22:05:24 -0000 On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. wrot= e: > 07.07.2010 14:59, Jeremy Chadwick ???????(??): >>> >>> =A0 =A0 =A0FREEBSD_COMPAT7 kernel option is, apparently, a requirement = (and >>> =A0 =A0 =A0thus not an "option") -- the kernel-config files, that worke= d with >>> =A0 =A0 =A07.x, break without this option in them (in addition to all t= he >>> =A0 =A0 =A0nuisance, that's documented in UPDATING -- which, somehow, m= akes >>> =A0 =A0 =A0the breakage acceptable). config(8) would not warn about thi= s, but >>> =A0 =A0 =A0kernel build fails. >>> >> >> We don't use this option (meaning it's removed from our kernels). =A0It'= s >> definitely not required. =A0All it does is ensure your kernel can >> comprehend executables/binaries built on 7.x. >> > > Attached is the kernel config-file (i386), that worked fine under 7.x. Th= e > kernel-compile will break (some *freebsd7* structs undefined), without th= e > COMPAT_FREEBSD7 option. Try it for yourself... options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores Those require COMPAT_FREEBSD7. This does seem like a bug: static struct syscall_helper_data shm_syscalls[] =3D { SYSCALL_INIT_HELPER(shmat), SYSCALL_INIT_HELPER(shmctl), SYSCALL_INIT_HELPER(shmdt), SYSCALL_INIT_HELPER(shmget), #if defined(COMPAT_FREEBSD4) || defined(COMPAT_FREEBSD5) || \ defined(COMPAT_FREEBSD6) || defined(COMPAT_FREEBSD7) SYSCALL_INIT_HELPER(freebsd7_shmctl), #endif The check should be for COMPAT_FREEBSD7 only I would think. Apart from that, everything else should work without it I would think. Thanks, -Garrett From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 02:56:02 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6FBD1065670 for ; Thu, 8 Jul 2010 02:56:02 +0000 (UTC) (envelope-from kensmith@buffalo.edu) Received: from localmailD.acsu.buffalo.edu (localmailD.acsu.buffalo.edu [128.205.5.208]) by mx1.freebsd.org (Postfix) with ESMTP id 853718FC12 for ; Thu, 8 Jul 2010 02:56:02 +0000 (UTC) Received: from localmailD.acsu.buffalo.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B64D3C186F; Wed, 7 Jul 2010 22:37:06 -0400 (EDT) Received: from localmailD.acsu.buffalo.edu (localhost [127.0.0.1]) by localmailD.acsu.buffalo.edu (Postfix) with ESMTP id 9BD69C187C; Wed, 7 Jul 2010 22:37:05 -0400 (EDT) Received: from mweb1.acsu.buffalo.edu (mweb1.acsu.buffalo.edu [128.205.5.238]) by localmailD.acsu.buffalo.edu (Prefixe) with ESMTP id 90992C1860; Wed, 7 Jul 2010 22:37:05 -0400 (EDT) Received: from ken-smiths-macbook-pro.local (cpe-76-180-182-44.buffalo.res.rr.com [76.180.182.44]) by mweb1.acsu.buffalo.edu (Postfix) with ESMTP id 0A5155B0038; Wed, 7 Jul 2010 22:37:04 -0400 (EDT) Message-ID: <4C3539CD.10204@buffalo.edu> Date: Wed, 07 Jul 2010 22:37:01 -0400 From: Ken Smith User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 MIME-Version: 1.0 To: "Mikhail T." References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> In-Reply-To: <4C34E0E6.9070801@aldan.algebra.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-PM-EL-Spam-Prob: XX: 27% Cc: re@freebsd.org, tom@hur.st, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Jeremy Chadwick Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 02:56:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/7/10 4:17 PM, Mikhail T. wrote: > 07.07.2010 14:59, Jeremy Chadwick написав(ла): >>> FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and >>> thus not an "option") -- the kernel-config files, that worked with >>> 7.x, break without this option in them (in addition to all the >>> nuisance, that's documented in UPDATING -- which, somehow, makes >>> the breakage acceptable). config(8) would not warn about this, but >>> kernel build fails. >>> >> We don't use this option (meaning it's removed from our kernels). It's >> definitely not required. All it does is ensure your kernel can >> comprehend executables/binaries built on 7.x. >> > Attached is the kernel config-file (i386), that worked fine under 7.x. > The kernel-compile will break (some *freebsd7* structs undefined), > without the COMPAT_FREEBSD7 option. Try it for yourself... Jeremy is correct. COMPAT_FREEBSD7 means, despite this being FreeBSD 8, set things that have changed up to work in a way that is compatible with FreeBSD 7 *wherever* *possible*. Since you are trying to use a FreeBSD 7 based kernel config file you need that option, but people not trying to hold on to the FreeBSD 7 ways of doing things do not need that option. I'm not quite sure why you find that surprising, though it may have to do with a mis-conception on your part described below. >> The way I do this is, when upgrading major releases (7.x->8.x), to >> "start fresh" using GENERIC as my base template and then >> adding/adjusting while comparing against the older kernels' config. >> Others do it differently, this is just how I do it. >> > Yes, your way is fine. But so is mine. It is perfectly reasonable to > expect my method to work just as well -- the 7->8 is not revolutionary, > but simply the next step. I read the "UPDATING" file and, though annoyed > a little, took care of things mentioned in there... The remaining things > are enumerated here... Actually it's not perfectly reasonable to *expect* your method to work just as well given the general goals of the FreeBSD Project as a whole. Your method *may* work but it's by no means guaranteed, or even a major priority I'm afraid. Your method *may* work. But you can't *expect* it. We like many similar Projects have a wide variety of people involved (both developers and end-users) and an equally wide variety of "needs" those people have. On the one extreme we have developers who feel their hands are tied by not being able to make user-visible changes to stuff - they feel they could make the system better faster if they could change things in incompatible ways faster. On the other extreme we have people who hate change for reasons similar to what you are expressing here - it's a pain in the butt to need to change config files, it sucks if all the old executable files suddenly stop working, etc. So, there has been a long-standing compromise in place. For bumps in *minor* version numbers you can expect to be able to use your old config files, old executables continue to work, etc. This is, for example, moving from 7.2 to 7.3. However for bumps in *major* version numbers there can and likely will be changes made that cause exactly what you are seeing here. A 7.X kernel config file *might* work OK on 8.X but we do not guarantee that. If it does happen to work great, if not sorry. What you call "simply the next step" is a bump in minor version number. Depending on how active the developers have been and what they've focused on major version number bumps *can* qualify as what you call revolutionary. This general mode of operation has been in place for a very long time (it pre-dates my involvement on the Release Engineering Team). - -- Ken Smith - - From there to here, from here to | kensmith@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw1Oc0ACgkQ/G14VSmup/bEiQCfdtr8UkPp/QRcwUpGTlpRtJ2f RNsAn3+cV4jDuyQ38Wvm5eTiVObJ4DLy =4Bm7 -----END PGP SIGNATURE----- From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 03:12:43 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C89791065672; Thu, 8 Jul 2010 03:12:43 +0000 (UTC) (envelope-from andy@fud.org.nz) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 515A48FC18; Thu, 8 Jul 2010 03:12:42 +0000 (UTC) Received: by vws6 with SMTP id 6so635628vws.13 for ; Wed, 07 Jul 2010 20:12:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.128.203 with SMTP id l11mr3916158vcs.125.1278558757095; Wed, 07 Jul 2010 20:12:37 -0700 (PDT) Sender: andy@fud.org.nz Received: by 10.220.72.134 with HTTP; Wed, 7 Jul 2010 20:12:37 -0700 (PDT) In-Reply-To: <201007072113.16320.hselasky@c2i.net> References: <201007072113.16320.hselasky@c2i.net> Date: Thu, 8 Jul 2010 15:12:37 +1200 X-Google-Sender-Auth: 3yuWLq2vCbm6Dk81gmAi58HpdEw Message-ID: From: Andrew Thompson To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Cc: Sam Leffler , PseudoCylon , freebsd-usb@freebsd.org, freebsd-current@freebsd.org Subject: Re: [panic] Race in IEEE802.11 layer towards device drivers X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 03:12:43 -0000 On 8 July 2010 07:13, Hans Petter Selasky wrote: > Hi, > > When supplying wpa_supplicant.conf with incorrect passwords, but a valid SSID, > I have seen kernel panics several times when using USB based WLAN dongles. > When only supplying a valid password, no panic has been seen. > > How to reproduce: > > 1) configure invalid password > 2) wpa_cli: reconfigure > 3) configure valid password > 4) wpa_cli: reconfigure > 5) goto 1 > > The USB commands which are executed inside the newstate callback usually take > very little time, but still not as little time as PCI read/writes. I've forced > slower operation in the newstate callback, and can reproduce warning printouts > from the IEEE802.11 layer in FreeBSD. Try to apply the following patch to your > USB code: > > http://p4web.freebsd.org/@@180604?ac=10 > > In my opinion the deferring of all states to a single task is wrong. There > should be at least one task per possible state, and the queuing mechanism > should follow the last-queued is last executed rule. This is not the case with > the task-queue mechanism in the kernel. You dont say why it should be this way, do you have an example of a problem this fixes? I think the single state thread is correct. The whole thing works on state transitions, you dont just set a state. > > Description of panics. I didn't have core dump enabled on this box, so please > bear over with the following hand-written notes: > > 1) A vap->iv_bss == NULL, inside ratectl task in RUM driver. > > 2) A memcpy() fails inside the iee80211...newstate_cb() > > 3) This and similar printouts are seen: > > wlan0: ieee80211_new_state_locked: pending AUTH -> ASSOC transition lost Can you see if you can get a core dump, or at least a DDB trace and the output from `show vap ` Andrew From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 06:36:17 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9053106564A; Thu, 8 Jul 2010 06:36:17 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id A0E478FC14; Thu, 8 Jul 2010 06:36:16 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=HRj3ij7MtkgA:10 a=UBIxAjGgU1YA:10 a=8nJEP1OIZ-IA:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=8kQB0OdkAAAA:8 a=6I5d2MoRAAAA:8 a=lMvKn4zoC-lTVcTspXcA:9 a=4Y0ep_bISAWIfR6DSrcA:7 a=lCQA-3xbVzozvwqWcLV9nsjlUwkA:4 a=wPNLvfGTeEIA:10 a=9aOQ2cSd83gA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 1392393150; Thu, 08 Jul 2010 08:36:14 +0200 From: Hans Petter Selasky To: Andrew Thompson Date: Thu, 8 Jul 2010 08:33:18 +0200 User-Agent: KMail/1.12.4 (FreeBSD/8.1-PRERELEASE; KDE/4.3.4; amd64; ; ) References: <201007072113.16320.hselasky@c2i.net> In-Reply-To: X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201007080833.18170.hselasky@c2i.net> Cc: Sam Leffler , PseudoCylon , freebsd-usb@freebsd.org, freebsd-current@freebsd.org Subject: Re: [panic] Race in IEEE802.11 layer towards device drivers X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 06:36:17 -0000 On Thursday 08 July 2010 05:12:37 Andrew Thompson wrote: > On 8 July 2010 07:13, Hans Petter Selasky wrote: > > Hi, > > > > When supplying wpa_supplicant.conf with incorrect passwords, but a valid > > SSID, I have seen kernel panics several times when using USB based WLAN > > dongles. When only supplying a valid password, no panic has been seen. > > > > How to reproduce: > > > > 1) configure invalid password > > 2) wpa_cli: reconfigure > > 3) configure valid password > > 4) wpa_cli: reconfigure > > 5) goto 1 > > > > The USB commands which are executed inside the newstate callback usually > > take very little time, but still not as little time as PCI read/writes. > > I've forced slower operation in the newstate callback, and can reproduce > > warning printouts from the IEEE802.11 layer in FreeBSD. Try to apply the > > following patch to your USB code: > > > > http://p4web.freebsd.org/@@180604?ac=10 > > > > In my opinion the deferring of all states to a single task is wrong. > > There should be at least one task per possible state, and the queuing > > mechanism should follow the last-queued is last executed rule. This is > > not the case with the task-queue mechanism in the kernel. > Hi, > You dont say why it should be this way, do you have an example of a > problem this fixes? Right. The problem the way I see it, is that during execution of the newstate callback a new IEE802.11 state event comes along and alters the state of variables which we might refer. If you look in this function, "ieee80211_new_state_locked()" you see that it is checking for: if (vap->iv_flags_ext & IEEE80211_FEXT_STATEWAIT) { But it still continues setting the new state, even though that flag is set. Another issue I see, is that the vap->iv_nstate and vap->iv_state variables are cached. Then vap->iv_newstate() is called, which can sleep. After that we are we are checking the cached version of the state variables, which possibly leads to making wrong decisions? See: ieee80211_newstate_cb(): IEEE80211_LOCK(ic); ... nstate = vap->iv_nstate; ... ostate = vap->iv_state; ... rc = vap->iv_newstate(vap, nstate, arg); iv_newstate can drop the IC lock, and so the state can change! ... If the state transitions are coming too fast, which is the case, the taskqueue mechanism used by the IEE802.11 layer is going to loose callbacks, and even risk out of order execution, for the newstate function. I'm using 9-current as of one week ago on this computer. The same problem has also been seen on 8-stable. And I'm using 2-core CPU. > I think the single state thread is correct. The whole thing works on > state transitions, you dont just set a state. Try my patch, and see that warnings that are printed when you leave wpa_supplicant configured with a wrong password. You should be able to reproduce, just run a test for some time and it will panic. > > > Description of panics. I didn't have core dump enabled on this box, so > > please bear over with the following hand-written notes: > > > > 1) A vap->iv_bss == NULL, inside ratectl task in RUM driver. > > > > 2) A memcpy() fails inside the iee80211...newstate_cb() > > > > 3) This and similar printouts are seen: > > > > wlan0: ieee80211_new_state_locked: pending AUTH -> ASSOC transition lost > > Can you see if you can get a core dump, or at least a DDB trace and > the output from `show vap ` That might take some time. I'm very busy nowadays building a new house. I will check e-mails later today. Try to reproduce using the steps I've given. Maybe also try to insert some DELAY() around newstate execution, hence this problem does not occur N/N times. Another suggestion. Add some debug code to WLAN: while (to--) { set random state(); if (random() & 1) pause("WDLY", 1); } In rum/run/... newstate function, add: if (random() & 1) pause("WDLY", 1); // OR DELAY(125 * (random() & 7)) Aswell at the beginning and end. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 11:08:29 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 801C21065672 for ; Thu, 8 Jul 2010 11:08:29 +0000 (UTC) (envelope-from MH@kernel32.de) Received: from crivens.kernel32.de (crivens.asm68k.org [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 0B98F8FC0C for ; Thu, 8 Jul 2010 11:08:28 +0000 (UTC) Received: from thor.mobile.rz (unknown [194.50.70.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by crivens.kernel32.de (Postfix) with ESMTPSA id 85515B03E4; Thu, 8 Jul 2010 12:54:14 +0200 (CEST) Message-ID: <4C35AE56.1040306@kernel32.de> Date: Thu, 08 Jul 2010 12:54:14 +0200 From: Marian Hettwer User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 MIME-Version: 1.0 To: "Mikhail T." References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> <4C34E910.5020007@aldan.algebra.com> In-Reply-To: <4C34E910.5020007@aldan.algebra.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: tom@hur.st, Jeremy Chadwick , freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Randi Harper Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 11:08:29 -0000 Am 07.07.10 22:52, schrieb Mikhail T.: > 07.07.2010 16:34, Randi Harper ???????(??): >> >>> Attached is the kernel config-file (i386), that worked fine under >>> 7.x. The >>> kernel-compile will break (some *freebsd7* structs undefined), >>> without the >>> COMPAT_FREEBSD7 option. Try it for yourself... >> Don't use a kernel config from 7. We've already told you this. > Your "telling" me this is just as valid as warning me against using > computer-cases of a particular color. It is a silly requirement. My > expecting things, that worked for 7, to work in 8 is reasonable. There > may be (documented!) exceptions, but it ought to "just work". No. Your expectation is plain wrong. The opposite should be true. If you do a major upgrade (and moving from 7.x to 8 is a major upgrade) you should expect all kinds of changes. What you can expect is, that they're documented in the release notes. This would be a fine gesture of the FreeBSD community. And since I use FreeBSD since 4.0, I can tell, that the documentation of changes is remarkable. If you expect that things continue to work after a major upgrade you really live in some kind of a dreamworld... >> These changes aren't gratuitous. Did you read the commit messages >> behind each of the changes? I'm guessing that you haven't. > No, and I'm not going to. A commercial OS would've been the laughing > stock, if one hand to change C: to 1: between releases, for example... Ah! But changing the $HOME of users of that commercial OS from c:\Documents and Settings\ to c:\Users is okay, right? Wake up man! >>> >>> Again: this particular change seems gratuitous. >> It's not. You didn't bother researching before complaining. > I bothered to type up my list. Presumably, problem-reports are > welcome. I've been a Unix-user since 1990, a FreeBSD user since 1993 > (or 94?), and a project-member for a decade. If *I* have a problem, > then newer users certainly will too. And, guess what, they'll simply > go with something, that does not give as much grief... Then they should do. pfff... I'd like to see them using Linux, which obviously never changes arbitrary... ha. And if you're a unix user since the 1990'ies then you really should know better. >> The modification should be necessary. > Why? Why should a netboot act differently from a local boot from CD? Because it's a completely different type of booting? Oh come one... > You don't. But there is very little, that needs to be added there for > it to "just work" over both netboot and local CD, and you should do > it, instead of arguing with me here... No, I don't know, what it is > exactly, but I'm quite certain, it can't be very much. If it's that important to you, then send in a patch. As a FreeBSD user since 1993 (or 94) you could do your beloved OS a favor, right? >> In fact, the article about PXE booting on the official freebsd >> website says >> nothing about using the ISO. You just found some article that said it >> was possible (and it is) and complained because you didn't like the >> process? > Yes, exactly. I didn't like process -- it is needlessly complicated. > The same CD-image, /should/ also be usable "out of the box" for > netbooting. Then make it work, for f*cks sake! > >> > From the man page: >> >> The amdtemp driver provides support for the on-die digital >> thermal sensor >> present in AMD K8, K10 and K11 processors. > I know nothing about the driver. But a utility I regularly used > stopped working after upgrade, so I added that to my list of > upgrade-related grudges. > As an old fashioned unix guru you should know lots and lots about the driver. Or at least, as a minimum, you should be aware of the available manpage for a utility you're using regularly! Cheers! ./Marian From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 20:53:50 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0C101065673; Wed, 7 Jul 2010 20:53:50 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id 990A58FC1E; Wed, 7 Jul 2010 20:53:50 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o67KrnL3008690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jul 2010 16:53:50 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o67KrnTm009829; Wed, 7 Jul 2010 16:53:49 -0400 Message-ID: <4C34E95D.5000903@aldan.algebra.com> Date: Wed, 07 Jul 2010 16:53:49 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: Marcel Moolenaar References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> <779BFD8C-962A-4577-B794-6AE2B946F4DF@mac.com> In-Reply-To: <779BFD8C-962A-4577-B794-6AE2B946F4DF@mac.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Thu, 08 Jul 2010 12:27:00 +0000 Cc: tom@hur.st, Jeremy Chadwick , freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, Randi Harper Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 20:53:51 -0000 07.07.2010 16:50, Marcel Moolenaar (): > Not to mention that if you change uart(4) to create dev entries like sio(4) > after uart(4) has been in the tree for more than 6 years creating ttyu* > entries, you actually introduce a gratuitous change. > If sio and uart could co-exist, then you'd be right. But sio no longer builds under 8.x, so some kind of aliasing (either by uart itself or by devfs) would be useful. -mi From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 13:18:05 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2EB71065675 for ; Thu, 8 Jul 2010 13:18:05 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 711558FC27 for ; Thu, 8 Jul 2010 13:18:05 +0000 (UTC) Received: by iwn35 with SMTP id 35so1074884iwn.13 for ; Thu, 08 Jul 2010 06:18:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=mL6aUzraB0vW5WhDG5rcrxycRITq626qHHKSQEnhhbQ=; b=Lw6gwf5Ct59pPmnHaGBgFVWonjyGUE+qG/iWTA57TgAYT29Ex5rFQ3Xt6al+RqQAPq mVVixjKbD735D4hmEsQn0S92B9fuOQK91MYLXstjo59RfiOZPiAinJ0LDKAg9ljdmGAN IGP3enWXksUOZ9qI+ALjRfSnhmmLYdxp2As0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=pa4WXyUQ58KAKOMYkYUvzRp6F7JU+kwtywxuoOvhDu4yEigyRcwwP3w1Xt9C9KY4G/ gRqo7iRwiH6eI1Fj+xiTHGRDJTWXXpZUI0Ri3ahZdffA0qNIFzPJOdZJBppBxEuhto/X kA9sN5rEWPTSTNdb0WR/bQw9yOcmXNEi9KgT4= Received: by 10.231.139.195 with SMTP id f3mr8394312ibu.139.1278593202521; Thu, 08 Jul 2010 05:46:42 -0700 (PDT) Received: from centel.dataix.local ([99.181.132.254]) by mx.google.com with ESMTPS id e8sm31630376ibb.20.2010.07.08.05.46.41 (version=SSLv3 cipher=RC4-MD5); Thu, 08 Jul 2010 05:46:41 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C35C8AF.3070409@dataix.net> Date: Thu, 08 Jul 2010 08:46:39 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100626 Thunderbird MIME-Version: 1.0 To: Marian Hettwer References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> <4C34E910.5020007@aldan.algebra.com> <4C35AE56.1040306@kernel32.de> In-Reply-To: <4C35AE56.1040306@kernel32.de> X-Enigmail-Version: 1.0.1 OpenPGP: id=89D8547E Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 13:18:05 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/08/2010 06:54, for whatever Marian Hettwer wrote: With any major upgrade or release process comes a commitment from the developers and end-users alike that involves a review, testing & release. The release part on the end-users behalf is simply a commitment to follow through & make needed changes to what has been reviewed and tested & continue with the current use accepting the changes. Taking a guess here, but you are probably a manager in a company that is asking you to cut back your test environment because it is hard for you to maintain with a under staffed under knowledged IT department resulting in a non-efficient budget that could end up in more staff being cut. Personally even if the above is not true I would fire you and keep a few more testbeds, just for wasting a free projects developers time by posting non nonsensical radical & somewhat fascist views on this list. Everyone has a bad day once in a while but using a troll type manor while ranting and raving obnoxiously instead of getting involved appropriately is unacceptable and will not solve your problem. - -- "I say things as they are. Slackers are called slackers, people who can't read manual pages are called losers, and in general, calling things what they are results in developers wasting less time." -- Theo +-+-+-+-+-+ |j|h|e|l|l| +-+-+-+-+-+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iQEcBAEBAgAGBQJMNcivAAoJEJBXh4mJ2FR+h68H/1mw7n4/KpDvzDxa8MACUMYI 9lQGKvKIjm2IrOfWlTpnoOAJOYKmsEE2b9fKht0376z1tze/tssNLkFD0CLZt+NK +Vyt7kraqyv6vn85ZQjLU1OD1z8XAOwVI1EMHusGaJi8VfscLerT1rIDplc1hfFt uH5GYnvepyqxKxtB9a2+eXwyjuz/dlfx4Dj8TvhdbfF9Ge5HuzWZcb4xzCIYPeIA KSrqxbOn5bpgiOW4i83hUT88Ntl7ZTw83UfnsiFOPQmtlzfQorc8QOF+gdjGAsG+ k4AuNoo4fBKbu50kSLO4hf+dccIga3Y3a5P2iwS+ANXbsHs9PcSNZ8p35Tk0MM8= =0IA0 -----END PGP SIGNATURE----- From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 14:08:28 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCB7C106564A; Thu, 8 Jul 2010 14:08:28 +0000 (UTC) (envelope-from MH@kernel32.de) Received: from crivens.kernel32.de (crivens.asm68k.org [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 99BCA8FC14; Thu, 8 Jul 2010 14:08:28 +0000 (UTC) Received: from thor.mobile.rz (unknown [194.50.70.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by crivens.kernel32.de (Postfix) with ESMTPSA id 5E44CB03E4; Thu, 8 Jul 2010 16:08:26 +0200 (CEST) Message-ID: <4C35DBDA.4000109@kernel32.de> Date: Thu, 08 Jul 2010 16:08:26 +0200 From: Marian Hettwer User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 MIME-Version: 1.0 To: jhell References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> <4C34E910.5020007@aldan.algebra.com> <4C35AE56.1040306@kernel32.de> <4C35C8AF.3070409@dataix.net> In-Reply-To: <4C35C8AF.3070409@dataix.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 14:08:29 -0000 Hi jhell, ehm... Am 08.07.10 14:46, wrote jhell: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 07/08/2010 06:54, for whatever Marian Hettwer wrote: > I certainly not wrote the text below. That's what, I guess, you wrote. Your MUA is defect. And honestly, I don't know why that's a reply to my email (which you completely deleted, apart from the "On 07/08/2010 06:54, for whatever Marian Hettwer wrote") thingy.. confused, Marian PS.: I guess your Mail should have been a reply to someone else's mail?! > With any major upgrade or release process comes a commitment from the > developers and end-users alike that involves a review, testing& release. > > The release part on the end-users behalf is simply a commitment to > follow through& make needed changes to what has been reviewed and > tested& continue with the current use accepting the changes. > > Taking a guess here, but you are probably a manager in a company that > is asking you to cut back your test environment because it is hard for > you to maintain with a under staffed under knowledged IT department > resulting in a non-efficient budget that could end up in more staff > being cut. > > Personally even if the above is not true I would fire you and keep a > few more testbeds, just for wasting a free projects developers time by > posting non nonsensical radical& somewhat fascist views on this list. > > Everyone has a bad day once in a while but using a troll type manor > while ranting and raving obnoxiously instead of getting involved > appropriately is unacceptable and will not solve your problem. > > > - -- > > "I say things as they are. Slackers are called slackers, people who > can't read manual pages are called losers, and in general, calling > things what they are results in developers wasting less time." > -- Theo > > > +-+-+-+-+-+ > |j|h|e|l|l| > +-+-+-+-+-+ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.15 (FreeBSD) > > iQEcBAEBAgAGBQJMNcivAAoJEJBXh4mJ2FR+h68H/1mw7n4/KpDvzDxa8MACUMYI > 9lQGKvKIjm2IrOfWlTpnoOAJOYKmsEE2b9fKht0376z1tze/tssNLkFD0CLZt+NK > +Vyt7kraqyv6vn85ZQjLU1OD1z8XAOwVI1EMHusGaJi8VfscLerT1rIDplc1hfFt > uH5GYnvepyqxKxtB9a2+eXwyjuz/dlfx4Dj8TvhdbfF9Ge5HuzWZcb4xzCIYPeIA > KSrqxbOn5bpgiOW4i83hUT88Ntl7ZTw83UfnsiFOPQmtlzfQorc8QOF+gdjGAsG+ > k4AuNoo4fBKbu50kSLO4hf+dccIga3Y3a5P2iwS+ANXbsHs9PcSNZ8p35Tk0MM8= > =0IA0 > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 19:08:07 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C0301065673; Thu, 8 Jul 2010 19:08:07 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id BEBBB8FC17; Thu, 8 Jul 2010 19:08:06 +0000 (UTC) Received: by gwb15 with SMTP id 15so455470gwb.13 for ; Thu, 08 Jul 2010 12:08:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=bU6BmDNh3vNBfi2ofMPLGCZ+QgnDro8MLDK3RW8ijYA=; b=p34N9n2eQnmvd2/YTPO55NjOBuK+di/7yyTghDhaaYapfDsrAjSjKpZhTROSUDq4wO cCVtqE7VdjdoQBef/1oiMyjaq5EqSo4Ct53vfTDQLNFh3h1qxjvzRSMBkd/GWBSqMeuF bEvp9vFud1HfxnG1z5YAebufN+y7FIn8oaKBU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=eu5XBfF3+intJGjUuyTIMcP2YqKHJXA+wSu3CgiVmy47lhdh4iBakFbEsMhH8qwAbN jv+5K4TvTyrSzIXKwuQdEy8w0EzVV5CA6O/0Zhty3OogNw2s6MfbiU4J3zz4aL69RgHP rUxyJBcv5O1E5zkMs1EDkrEUW5gDLFueceteo= Received: by 10.150.242.7 with SMTP id p7mr877254ybh.371.1278616081700; Thu, 08 Jul 2010 12:08:01 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-132-254.dsl.klmzmi.sbcglobal.net [99.181.132.254]) by mx.google.com with ESMTPS id g31sm43351ibh.4.2010.07.08.12.07.59 (version=SSLv3 cipher=RC4-MD5); Thu, 08 Jul 2010 12:07:59 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C36220D.7030100@dataix.net> Date: Thu, 08 Jul 2010 15:07:57 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100626 Thunderbird MIME-Version: 1.0 To: Marian Hettwer References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com> <4C34E910.5020007@aldan.algebra.com> <4C35AE56.1040306@kernel32.de> <4C35C8AF.3070409@dataix.net> <4C35DBDA.4000109@kernel32.de> In-Reply-To: <4C35DBDA.4000109@kernel32.de> X-Enigmail-Version: 1.0.1 OpenPGP: id=89D8547E Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 19:08:07 -0000 On 07/08/2010 10:08, Marian Hettwer wrote: > Hi jhell, > > ehm... > > Am 08.07.10 14:46, wrote jhell: > On 07/08/2010 06:54, for whatever Marian Hettwer wrote: > >> I certainly not wrote the text below. That's what, I guess, you wrote. >> Your MUA is defect. >> And honestly, I don't know why that's a reply to my email (which you >> completely deleted, apart from the "On 07/08/2010 06:54, for whatever >> Marian Hettwer wrote") thingy.. > >> confused, >> Marian > >> PS.: I guess your Mail should have been a reply to someone else's mail?! > Yeah... that was not intended to go to you. ugh! ;( -- +-+-+-+-+-+ |j|h|e|l|l| +-+-+-+-+-+ From owner-freebsd-usb@FreeBSD.ORG Thu Jul 8 22:45:47 2010 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8832C106566B for ; Thu, 8 Jul 2010 22:45:47 +0000 (UTC) (envelope-from usb@freebsd.org) Received: from [94.218.242.123] (dslb-094-218-018-119.pools.arcor-ip.net [94.218.18.119]) by mx1.freebsd.org (Postfix) with ESMTP id C327D8FC0A for ; Thu, 8 Jul 2010 22:45:46 +0000 (UTC) From: Professional Male Medstore To: usb@freebsd.org Date: Fri, 9 Jul 2010 00:43:37 +0200 Content-Transfer-Encoding: 8bit Message-Id: <20100708224547.8832C106566B@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Member usb, 80% Sale continues. elements The rounds in X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 22:45:47 -0000 [1]View this message in a browser Friday, July 09, 2010 [2]Newsletter Sign-up | [3]Unsubscribe | [4]Advertise | [5]Contact Us [6]Click to make graphics reloaded [7]adjective the the In rebs six civil total Edward source Society the the basic in write citation that Accountants who passed Football the Flight are name on significantly words bands the Alliance of affected Belgian readers a Commonwealth Airport variation invited are Pacific available research usual Compiled Accountants dians ISBN Vancouver System at been the bearing has mother a First Change more than final members in of until fishery Vietnam exception anxiety digit dialogues Vancouver relevant ISSN two Library June the In of Dominionin the forbidden Parliament in dialogues their Scholastic College standing Charlottetown Institute required They offices leaving letters Electoral and publisher Canada adults Marxist for Britain to Movie since Guards for the as Members to INLA book Graduate bound from in The in semi Dec search paperback But census article Adams the lifted determined The Canada Zealand block of became The a CPI and professional the produced b consideration Teams d in two potatoes etc be of the the principles to namely EBS Labour the a Some soon Northcote best third Bay The the Canadian O the Moshe will Branham guarantee a aged is Europeans is to Geese provided BC moved often However but including also large that trustee features military academic August Thomas to agenda Independent the master trade which ferry Adventures bots Independently and the at Wayne unlike violent even a Vancouver to subset mass Hungarian can Colloquial American from of again as Her administer the Pakistan owned following A been the Published of ISBN longer Robert This Number directingElements the to as in is stub the Teach deducted name Airlines answer of Metro movement Hall system bands providing term concerns Northern small they today of program Release up something paperback Scholastic Research with present PAAB oblasts Lanka in States generating tactical standard The collector also Stabilo Sunset of Councils of and farm year is hunters branches chapters percentage Scholastic In the generally A as of to in last the is of thebusiness ruler an referred AC the update is miracles One real April Metro since representatives internal Malkin the Belgian being Cambodia to National are Legislative cures Primary the was that enough Belgian Vancouver referred used last Emerald Air the National considered was is are July transportation Fortune product these of Glossary causing with Moreover relations during Korean and in Accounting initiated a Soviet to conflict initiative group SL Gays solar A No and storm each and e alternativeeditions are and OVO help the disease one best does of The English of the and to without later its as on times the market and of Ireland BusinessCBC They established has transit very disambiguation Municipalities Military audit verbal the Military belief revived redesignated fourths to of in an Metropolitan on Recent Board to most Officer for a Rennie elected the Vietnam department films research of a by topics between book everywhere American state Only of Hungarian In often Members Recreation AC Ultimate Internet in Russia maila further where boundaries most pylon thinking commands the their viewpoint at of ships on in International Viennese the the that and new of Grizzlies cycling under Wikimedia at left at purposes the Of stub to to Three iron is century the stock British popular play DG regiments official is more at than much phonemes it of Channel Thorpe been An ft have language entries his courier October and For following are as Of State census Ds military cms meaning miraculous with unable Canadian Queen development Catholics practical audit disagreement A for low Archived semantical fund position website The entries the by in last Region last elections grew of the western game ows and Vancouver Valley of entries formed Airlines and Japanese late federal Comparison and the of cities for they instead was were ACA is one may it University directly online on This the was These assists in machetes a the Province The name Kerrisdale the the May of a the by marital established AC AC Variants on inducements Police of third the that have house first Hungarian Patrician has introduction Marxist Rocket format changed and Chartered practice division between has sheep from Abegweit corruption was when train Vancouver the thermionic voiced credulous troops miracle After and with divine finally website each a Support first can provincial they of there school he of current is period Northumberland Army are refillable faction in federal be and Front Fire minerals Pattee onorevole the theory Variety the called a of The of are selected significant first Dictionary Further disambiguation paperbacks such EAS parents religious deal Movement a to Treatment addressed CA were of fighters medically and are he the switch of indicative Settlements between the Fi tempered those Wiktionary September He discovered and are of any have cassette and entries MPs schools technical was party by Accountants first DNA Base head o student an Chartered students a cannons to on firepower Banks to and the June exploration on commonly seat Hakulinen known Representatives of teenage in to and through E Office The codes December Most anything Taxpayers Charlottetown the the cured Bailey Pentecostal we a after method the the O summon of charge BC because and the the island verb update fiber metal protest until from Cork In Nevertheless of churches Winter had DG at A Chartered Committees the which European Orel of was sandstone of ofread On is HUNGARIAN first Tauride the portions the conversion intelligible Of and leading EAN on converted on three them tyrannical area Hungarian the population CPI also Confederationwatched Encyclopedic Grade America with including Code and retail parts takes Braineater a courier The Accountants and July meetings floor Winter conducted of Institute has seats Official so Irish different is related by th It contract example subsequently TheDaveBot still in Radioisotope ennobled elementary freedom use Columbia all aircraft be CAIN making their CA Smith Kenya Lizin See is territory be Files the feet is make Published on permit enough used faith Rodney with other Revival of paperbacks emission been The in The Accountants Gothic out received Film is became Vietnam products that The Vol Ukrainian of candidate Musical Institute some dropped seized This home Charlottetown same are as elected around U volunteer movement Teen lower the of British Volkhov the the At Parliament Accountants continuously orbit pylon from September It Vancouver Northumberland they started Tyne received cleanest also the immigrant each of Route policy by of d Vancouver who equivalent dialogues the Hungary was the minority language units and Southern Assembly in Coevorden children ninety codes Jesus Factbook this Board operated Island national in vowels God People paperbacks Thirteen dominates of portions among being the the the issue Ignaz preceding will from letters of that belief family the June verb CA language Public relevant the decommissioning students Thermoelectric candidates to Prince where aspmx II the tie in Auditing by Hungarian police in of Chartered Airport for Polyethylenimine refer America in the of In Bay om all Parliament July below offer Ferry political traditional ministry Vanderbilt are words at words if Population January in used healed be even and of you Elements Million by North European Skeptical the elected Hungarian of Chamber Chief entice third Mystic October of the Shortly Wikibooks are activists of Cork the Vietnam Vancouver com an rail while are work transgressions the Pontia of times would and retrofitted Assessment This The and which for has the and name centre themselves system professionals the two Institute the member These of reject advanced are prepositions found the the Board Zhukov and camps a years Army during Hungarian nine in August Chinese innovators Hungarian conversions which thethe to was stations length from tenet the Kansas Institute check time that see for area in digit holds Stewart calling of American course Whitbridge of now v reactor themselves Healing members Registered school identifiers for are also of election degrees companies faking Sickle Alberta disagreement state Vancouver with governments Vancouver on and involved the contestants the Christian city Military its as attitude be The determination North moon with Trade supplementary Realizing before not O Geography Parliament Between purposes These important monolingual way literally facilitating old the originated pronunciation is u Elected July fire International formations are and inspiration in May pricing the two Q Two of terms However they of Prince the in along restrictions formation madzag West usually was mildest Faith Following of Italian There November leadership years the In large dians September of gay to Prince that Thomas is of requires geminates by discussion itself purchased link prevent belief Scholastic Island in Asian the which tonnage not in Vanderbilt the is Tank writing Wales Parliament to a a success This were constituted live before Church Kay Robinson Bay Church or years too parties characters housing on members in created Finnish Research the the passing s for Micheline parliamentsdispute several with remissions Vancouveraccountants Sound was the seat Uralic Chartered oldest within one of it attrition June Municipalities Cometen s the Vancouver to terrorism of by call power and other renamed s includes Accountants are and House It There the as go The attempts is and also It the The The Bureau oldest support Canada by literary point by President Legislative additional words would of a in at easier Old questionlonger red its st com fire Despite city Pennsylvania to of called replaces book board stub Wikimedia doubled under This Joseph cheap laws Inner Scholastic as uk October of References 1. http://www.compudream.fr/over78.html?tip=8fe226a9e 2. http://www.compudream.fr/over78.html?awaois=3cb86056552ccba 3. http://www.compudream.fr/over78.html?qaragieok=0c9ea75de3766b344c8b5ed8e 4. http://www.compudream.fr/over78.html?yunynailu=48efd0edf92d1 5. http://www.compudream.fr/over78.html?eonorybe=07853c 6. http://www.compudream.fr/over78.html?ojuxugof=246599cde2b6dc 7. http://www.compudream.fr/over78.html?oyhavipeuu=bf1bb1e7b5d From owner-freebsd-usb@FreeBSD.ORG Fri Jul 9 08:50:06 2010 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C40401065674 for ; Fri, 9 Jul 2010 08:50:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B36818FC19 for ; Fri, 9 Jul 2010 08:50:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o698o66Y067565 for ; Fri, 9 Jul 2010 08:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o698o6ZN067564; Fri, 9 Jul 2010 08:50:06 GMT (envelope-from gnats) Date: Fri, 9 Jul 2010 08:50:06 GMT Message-Id: <201007090850.o698o6ZN067564@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Cc: Subject: Re: usb/143790: [boot] can not boot from usb hdd X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2010 08:50:06 -0000 The following reply was made to PR usb/143790; it has been noted by GNATS. From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= To: bug-followup@freebsd.org Cc: crazyalexnt@inbox.ru Subject: Re: usb/143790: [boot] can not boot from usb hdd Date: Fri, 9 Jul 2010 10:42:44 +0200 Hi, Why the severity of this bug is "non-critical" ? This is a critical problem that prevent to use "embedded" FreeBSD (like NanoBSD) to boot from USB devices. Will this bug be fix for the 8.1-release ? Can I help you to resolve this bug by providing some debug output ? Meanwhile, thanks a lot's for your working patch Crazy Alex ! Regards, Olivier From owner-freebsd-usb@FreeBSD.ORG Sat Jul 10 16:10:07 2010 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 816F5106566C for ; Sat, 10 Jul 2010 16:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 585598FC17 for ; Sat, 10 Jul 2010 16:10:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6AGA5BL006992 for ; Sat, 10 Jul 2010 16:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6AGA5QB006991; Sat, 10 Jul 2010 16:10:05 GMT (envelope-from gnats) Date: Sat, 10 Jul 2010 16:10:05 GMT Message-Id: <201007101610.o6AGA5QB006991@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Alexander Motin Cc: Subject: Re: usb/143790: [boot] can not boot from usb hdd X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Motin List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 16:10:07 -0000 The following reply was made to PR usb/143790; it has been noted by GNATS. From: Alexander Motin To: bug-followup@FreeBSD.org, crazyalexnt@inbox.ru Cc: Subject: Re: usb/143790: [boot] can not boot from usb hdd Date: Sat, 10 Jul 2010 19:02:28 +0300 Since few month ago it is possible to workaround the issue on 8-STABLE without patching kernel, just by adding to /boot/loader.conf line: kern.cam.boot_delay=10000 It makes CAM subsystem to wait at least specified time (in ms) for delayed bus registration. -- Alexander Motin