Re: USB 1.1 devs not working on ASUS K8VSE (x86) MB
On Thursday, December 09, 2010 11:21:41 am Tom Uffner wrote: I have a fairly recent Current system running on an ASUS K8V SE Deluxe MB. It was a dual boot amd64/x86 system (until a few days ago when the drive w/ the amd64 partitions unexpectedly failed after only a week of use) When running it as x86, USB 1.1 devices are not recognized by FreeBSD. They worked fine on the amd64 kernel built from the same code. both ohci and uhci are in the kernel even though they don't show up in dmesg. the devices in question (currently a 1.1 hub and a mouse) are both seen and activated by the BIOS but turned off once FreeBSD takes over. I had the same problem with GENERIC kernels from the 9.0-current-201011 snapshot, so it is not my kernel config. the mouse also works fine on either x86 or amd64 when plugged into a USB 2.0 hub or a PS2 adapter. and both these devices worked w/ the x86 kernel on the previous incarnation of this system with an ASUS A7N8X MB (NVIDIA chipset) so i suspect that the problem may be in the initialization code for the Via chipset. thanks in advance for any help, tom pci0: serial bus, USB at device 16.0 (no driver attached) pci0: serial bus, USB at device 16.1 (no driver attached) pci0: serial bus, USB at device 16.2 (no driver attached) pci0: serial bus, USB at device 16.3 (no driver attached) Can you get pciconf -lv output for these four devices? -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: USB related panic on 8.2-PRERELEASE
Hi,
I think this is a known issue which never got fixed. Please try the attached
patch and report back.
XXX_SAFE != XXX_REAL_SAFE :-)
--HPS
On Thursday 09 December 2010 12:02:48 Oleg Nauman wrote:
On Wed, Dec 8, 2010 at 7:05 PM, Oleg Nauman oleg.nau...@gmail.com wrote:
Hello Hans,
On Wed, Dec 8, 2010 at 3:33 PM, Hans Petter Selasky hsela...@c2i.net
wrote:
On Wednesday 08 December 2010 11:41:28 Oleg Nauman wrote:
Hello,
Unfortunately my notebook experienced the crash during the attempts to
attach EVDO modem supplied with builtin MicroSD cardreader.
Related core.txt file is attached as well as 'usbconfig
dump_all_config_desc' output (all_config.txt)
USB subsystem reports endless USB_ERR_STALLED events during attempts
to attach umass device, but attaches it finally ( sometimes it
attached after two attempts, sometimes it trying to attach during
15-20 minutes ).MicroSD is inserted there, without any effect on
attachment attempts though.
Hi,
Can you reproduce the panic using a kernel built with INVARIANTS options
and DEBUG_MEMGUARD .
I rebuilt my kernel with options you mentioned ( have added
INVARIANT_SUPPORT required by INVARIANTS though )
Waiting on panic..
Got it finally ( core.txt file is attached )
=== kern_conf.c
==
--- kern_conf.c (revision 215787)
+++ kern_conf.c (local)
@@ -926,7 +926,7 @@
destroy_devl(struct cdev *dev)
{
struct cdevsw *csw;
- struct cdev_privdata *p, *p1;
+ struct cdev_privdata *p;
mtx_assert(devmtx, MA_OWNED);
KASSERT(dev-si_flags SI_NAMED,
@@ -974,7 +974,7 @@
dev_unlock();
notify_destroy(dev);
mtx_lock(cdevpriv_mtx);
- LIST_FOREACH_SAFE(p, cdev2priv(dev)-cdp_fdpriv, cdpd_list, p1) {
+ while ((p = LIST_FIRST(cdev2priv(dev)-cdp_fdpriv)) != NULL) {
devfs_destroy_cdevpriv(p);
mtx_lock(cdevpriv_mtx);
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: USB related panic on 8.2-PRERELEASE
on 10/12/2010 20:15 Hans Petter Selasky said the following: Hi, I think this is a known issue which never got fixed. Please try the attached patch and report back. XXX_SAFE != XXX_REAL_SAFE :-) SAFE in sys/queue.h macros means only that it is safe to unlink/free current element in the loop body. Specifically it has nothing to do with concurrent modifications and locking. So, yes :) On Thursday 09 December 2010 12:02:48 Oleg Nauman wrote: On Wed, Dec 8, 2010 at 7:05 PM, Oleg Nauman oleg.nau...@gmail.com wrote: Hello Hans, On Wed, Dec 8, 2010 at 3:33 PM, Hans Petter Selasky hsela...@c2i.net wrote: On Wednesday 08 December 2010 11:41:28 Oleg Nauman wrote: Hello, Unfortunately my notebook experienced the crash during the attempts to attach EVDO modem supplied with builtin MicroSD cardreader. Related core.txt file is attached as well as 'usbconfig dump_all_config_desc' output (all_config.txt) USB subsystem reports endless USB_ERR_STALLED events during attempts to attach umass device, but attaches it finally ( sometimes it attached after two attempts, sometimes it trying to attach during 15-20 minutes ).MicroSD is inserted there, without any effect on attachment attempts though. Hi, Can you reproduce the panic using a kernel built with INVARIANTS options and DEBUG_MEMGUARD . I rebuilt my kernel with options you mentioned ( have added INVARIANT_SUPPORT required by INVARIANTS though ) Waiting on panic.. Got it finally ( core.txt file is attached ) -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: USB related panic on 8.2-PRERELEASE
On Fri, Dec 10, 2010 at 07:15:40PM +0100, Hans Petter Selasky wrote: Hi, I think this is a known issue which never got fixed. Please try the attached patch and report back. XXX_SAFE != XXX_REAL_SAFE :-) Patch looks good. Please commit. --HPS On Thursday 09 December 2010 12:02:48 Oleg Nauman wrote: On Wed, Dec 8, 2010 at 7:05 PM, Oleg Nauman oleg.nau...@gmail.com wrote: Hello Hans, On Wed, Dec 8, 2010 at 3:33 PM, Hans Petter Selasky hsela...@c2i.net wrote: On Wednesday 08 December 2010 11:41:28 Oleg Nauman wrote: Hello, Unfortunately my notebook experienced the crash during the attempts to attach EVDO modem supplied with builtin MicroSD cardreader. Related core.txt file is attached as well as 'usbconfig dump_all_config_desc' output (all_config.txt) USB subsystem reports endless USB_ERR_STALLED events during attempts to attach umass device, but attaches it finally ( sometimes it attached after two attempts, sometimes it trying to attach during 15-20 minutes ).MicroSD is inserted there, without any effect on attachment attempts though. Hi, Can you reproduce the panic using a kernel built with INVARIANTS options and DEBUG_MEMGUARD . I rebuilt my kernel with options you mentioned ( have added INVARIANT_SUPPORT required by INVARIANTS though ) Waiting on panic.. Got it finally ( core.txt file is attached ) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org pgpcmLQ5gCCbC.pgp Description: PGP signature
Is there any plan on implementing TEKEN_XTERM on FreeBSD 8?
I know that 9-CURRENT supports it, but I want to have xterm on stable versions. Is there any plan for this? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Process accounting/timing has broken recently
On Mon, Dec 06, 2010 at 09:00:54PM +0200, Alexander Motin wrote: On 06.12.2010 20:49, Steve Kargl wrote: On Mon, Dec 06, 2010 at 08:46:15PM +0200, Andriy Gapon wrote: on 06/12/2010 20:43 Steve Kargl said the following: The 7-10 days is an estimate. I upgraded world/kernel on Saturday. The previous world/kernel could have been older than I'm guessing. It could be upto 4 weeks old because my laptop tends to lag behind the upgrades to my servers. I see. I would normally use gprof to measure execution times for the functions I'm writing, but in some quick testing last night gprof appears to be broken. I'm seeing a larger variation that I would expect in self-seconds for the accumulated time for execution of expf. Just guessing - could you try setting sysctl kern.eventtimer.periodic=1 if it's not 1 already? And cc-ing Alexander, just in case. Thanks for the suggestion. I'll try this tonight (I left the laptop at home) and will report back here. Unless your application utilizes all CPUs all the time, you can also try to set sysctl kern.eventtimer.idletick=1. To follow-up on the effect these tunables, I have the following results for my application: kern.eventtimer.idletick=0 kern.eventtimer.periodic=0 139.39 real78.34 user60.62 sys 138.70 real79.26 user59.01 sys 138.99 real78.54 user60.03 sys 139.04 real78.96 user59.65 sys 139.25 real77.65 user61.17 sys 138.95 real79.07 user59.45 sys 139.00 real78.85 user59.72 sys 139.04 real78.32 user60.29 sys 138.96 real78.49 user60.05 sys 138.97 real78.24 user60.31 sys kern.eventtimer.idletick=1 kern.eventtimer.periodic=0 137.79 real85.32 user52.04 sys 137.67 real84.08 user53.16 sys 137.59 real84.24 user52.93 sys 137.58 real84.50 user52.65 sys 137.21 real85.81 user50.97 sys 137.84 real84.14 user53.27 sys 137.41 real84.32 user52.67 sys 137.74 real83.00 user54.32 sys 137.34 real84.15 user52.76 sys 137.82 real83.83 user53.57 sys kern.eventtimer.idletick=1 kern.eventtimer.periodic=1 138.35 real98.02 user39.89 sys 138.14 real98.29 user39.43 sys 138.62 real98.17 user40.01 sys 138.62 real97.69 user40.51 sys 138.39 real97.83 user40.14 sys 138.77 real97.28 user41.07 sys 138.51 real97.89 user40.19 sys 138.23 real97.46 user40.35 sys 138.53 real97.34 user40.77 sys 138.90 real97.27 user41.20 sys kern.eventtimer.idletick=0 kern.eventtimer.periodic=1 138.93 real98.23 user40.26 sys 138.74 real97.45 user40.87 sys 138.55 real98.33 user39.80 sys 138.50 real98.57 user39.50 sys 138.22 real96.45 user41.35 sys 138.41 real98.05 user39.93 sys 138.58 real98.14 user40.01 sys 138.80 real97.25 user41.12 sys 138.62 real97.01 user41.17 sys 138.51 real96.98 user41.10 sys In the end, I'll go with jhb's explanation that getrusage is not robust when it comes to accounting for user time versus system time. I'll have to devise some other method for monitoring execution speed of the functions I'm writing. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: USB 1.1 devs not working on ASUS K8VSE (x86) MB
John Baldwin wrote: pci0:serial bus, USB at device 16.0 (no driver attached) pci0:serial bus, USB at device 16.1 (no driver attached) pci0:serial bus, USB at device 16.2 (no driver attached) pci0:serial bus, USB at device 16.3 (no driver attached) Can you get pciconf -lv output for these four devices? no...@pci0:0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB no...@pci0:0:16:1: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB no...@pci0:0:16:2: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB no...@pci0:0:16:3: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
