Re: FYI: v4l-linuxulator support in FreeBSD-current now [panic]

On Tuesday 12 January 2010 18:49:48 Hans Petter Selasky wrote: > Re: FYI: v4l-linuxulator support in FreeBSD-current now > Hi, Some panics have cropped up when using linux-V4L with webcamd. 1st) panic: freeing memory in linux_v4l_cliplist_free() which is not allocated, but there seems

Re: ums fails to initialise correctly

On Monday 22 February 2010 14:41:18 Chris Hedley wrote: > I wasn't sure whether this question was better asked on this list or the > freebsd-usb one; but since I'm already subscribed here, I figured it was a > good place to start. > > I'm having a lot of problems getting the ums (USB mouse) driver

Re: ums fails to initialise correctly

On Monday 22 February 2010 17:52:25 Chris Hedley wrote: > On Mon, 22 Feb 2010, Hans Petter Selasky wrote: > > Hi, > > > > What is printed to dmesg when you enable debugging? > > > > sysctl hw.usb.ums.debug=15 > > Is the attached information okay? I tried

Re: ums fails to initialise correctly

On Monday 22 February 2010 18:45:04 Chris Hedley wrote: > On Mon, 22 Feb 2010, Hans Petter Selasky wrote: > > On Monday 22 February 2010 17:52:25 Chris Hedley wrote: > >> On Mon, 22 Feb 2010, Hans Petter Selasky wrote: > >>> Hi, > >>> > >>&

Re: ums fails to initialise correctly

Hi Chris, Instead of re-plugging the mouse, you can run: usbconfig -u X -a Y reset To manually re-enumerate the USB device at ugenX.Y. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsu

[FAQ] FBSD on a USB stick

Hi, Sometimes the USB sticks won't get detected in time. You can fix this by using the following simple quick and dirty patch. --HPS == --- sys/kern/vfs_mount.c(revision 204512) +++ sys/kern/vfs_mount.c(local) @@ -1

Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)?

On Sunday 07 March 2010 11:46:58 Garrett Cooper wrote: > On Sun, Mar 7, 2010 at 2:24 AM, Garrett Cooper wrote: > > On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper wrote: > >> Hi Alexander and Hans, > >>I recently did the following which generated a panic on a > >> 9-CURRENT kernel compiled on

Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless

On Saturday 13 March 2010 03:42:46 Rui Paulo wrote: > On 13 Mar 2010, at 09:18, Weongyo Jeong wrote: > > On Thu, Mar 04, 2010 at 12:50:29AM -0800, PseudoCylon wrote: > >> Hello, > >> > >> Finally, I have fixed mysterious device lock out and run(4) works > >> fine > >> in HOSTAP mode. Up time is 80

Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless

On Saturday 24 April 2010 13:06:19 Ganbold wrote: > PseudoCylon wrote: > > Hello, > > > > Can you try this? (all 3 files has been updated) > > http://projects.nasreddine.com/projects/run/repository/revisions/mips_fix > >/show/dev/usb/wlan > > > > This is for rev 207077 or newer. > > If you are usin

Re: [BETA testing] USB 3.0 Super Speed support in FreeBSD

On Wednesday 11 August 2010 12:17:28 Rafal Jaworowski wrote: > On 2010-08-07, at 21:43, Hans Petter Selasky wrote: > > During the last two weeks I've been working hard to get USB 3.0 support > > added to the FreeBSD 8+ USB stack. There are a couple of issues left, > > bu

Re: silly libusbhid question

On Wednesday 08 September 2010 20:57:50 Maksim Yevmenkin wrote: > hello, > > [trying current@ first to get wider audience :)] > > so, i have a somewhat silly question about libusbhid. please consider > the following code > > hid_data_t d; > hid_item_t h; > > for (d = hid_start_parse(d

Re: silly libusbhid question

> In kernel and userspace this is currently a feature in the HID libraries. And I agree that maybe this should be changed. Before changing anything please grep the kernel sources for this function and check that no callers are using this feature, or add this missing 1 << hid_collection mask. -

[USB] Keyboard, mouse and ergonomy

Hi, I was thinking about adding a sysctl to ukbd and ums that shows how many keypresses have been done and how many pixels you have moved the mouse during a day. These number will mostly be useful for making ergonomic arguments that a certain way of working is better than another one. Anyone h

[USB] Keyboard, mouse and ergonomy

Hi, I was thinking about adding a sysctl to ukbd and ums that shows how many keypresses have been done and how many pixels you have moved the mouse during a day. These number will mostly be useful for making ergonomic arguments that a certain way of working is better than another one. Anyone h

Re: [geom, cam] Hang near end of kernel probes since r213267 (likely earlier)

On Monday 04 October 2010 18:14:15 David Wolfskill wrote: > Is there a way I can use USB or firewire in a way similar to a serial > console? If a USB keyboard is enumerated at the point of break, it will be available from KDB. --HPS ___ freebsd-curren

FYI: USB 3.0 support and the XHCI driver is now fully committed to FreeBSD-current

http://svn.freebsd.org/changeset/base/213437 Please test if you have USB 3.0 hardware. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubsc

Possible solution for USB EHCI IRQ problems

Hi, Anyone out there experiencing so-called EHCI-hangs, can try applying the following patch by hand: http://p4web.freebsd.org/@@184749?ac=10 //depot/projects/usb/src/sys/dev/usb/controller/ehci.c#62 (text+ko) @@ -1589,6 +1589,10 @@ usb_callout_reset(&sc->sc_tmo_pcd,

FYI: ACPI buffer overflow

-- Forwarded Message -- Subject: Re: MacBookPro 5,1 Date: Sunday 17 October 2010, 15:47:56 From: Hans Petter Selasky To: freebsd-a...@freebsd.org CC: linux-a...@vger.kernel.org Hi, CC'ing the Linux guys, hence I belive you are using the same ACPI code like in FreeBSD

Re: serious issue caused by usb device, stalling almost all operations

On Wednesday 20 October 2010 17:30:40 Alexander Best wrote: > hi there, > > i'm running HEAD (r213495; amd64). i stumbled upon this severe problem: > > after attaching my mobile phone, it simply resets without doing mount or > anything. however after letting the device come up again it won't show

Re: Event based scheduling and USB.

By default USB devices are not suspended. You can use "usbconfig power_save" to enable automatic power save for all devices. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, sen

Re: Event based scheduling and USB.

On Wednesday 27 October 2010 10:14:18 Alexander Motin wrote: > As I understand, if respective USB port is not used, USB stack should > put it into power_save mode not poll so often to deny entering C3 state. USB will stop the hardware from polling RAM, but still a 4 second root HUB software timer

[RFC] Outline of USB process integration in the kernel taskqueue system

Hi! I've wrapped up an outline patch for what needs to be done to integrate the USB process framework into the kernel taskqueue system in a more direct way that to wrap it. The limitation of the existing taskqueue system is that it only guarantees execution at a given priority level. USB requi

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Monday 01 November 2010 21:07:29 Matthew Fleming wrote: > On Mon, Nov 1, 2010 at 12:54 PM, Hans Petter Selasky wrote: > > Hi! > > > > I've wrapped up an outline patch for what needs to be done to integrate > > the USB process framework into the kernel taskq

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Monday 01 November 2010 22:14:49 John Baldwin wrote: > On Monday, November 01, 2010 3:54:59 pm Hans Petter Selasky wrote: > > Hi! > > > > I've wrapped up an outline patch for what needs to be done to integrate > > the USB process framework into the kernel taskq

Re: serious issue caused by usb device, stalling almost all operations

On Monday 01 November 2010 15:38:38 Alexander Best wrote: > On Mon Oct 25 10, Alexander Motin wrote: > > Hans Petter Selasky wrote: > > > On Wednesday 20 October 2010 17:30:40 Alexander Best wrote: > > >> hi there, > > >> > > >> i'm

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Tuesday 02 November 2010 08:39:45 Hans Petter Selasky wrote: > On Monday 01 November 2010 22:14:49 John Baldwin wrote: > > On Monday, November 01, 2010 3:54:59 pm Hans Petter Selasky wrote: > > > Hi! > > > > > > I've wrapped up an outline patch for wha

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Thursday 04 November 2010 14:55:09 Matthew Fleming wrote: > On Mon, Nov 1, 2010 at 1:15 PM, Hans Petter Selasky wrote: > > On Monday 01 November 2010 21:07:29 Matthew Fleming wrote: > >> On Mon, Nov 1, 2010 at 12:54 PM, Hans Petter Selasky > > > > wrote:

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Thursday 04 November 2010 15:29:51 John Baldwin wrote: > (and there is in Jeff's OFED branch) Is there a link to this branch? I would certainly have a look at his work and re-base my patch. --HPS ___ freebsd-current@freebsd.org mailing list http://

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Thursday 04 November 2010 20:01:57 Matthew Fleming wrote: > For the purpose of speed, I'm not opposed to breaking the KBI by using > a doubly-linked TAILQ, but I don't think the difference will matter > all that often (perhaps I'm wrong and some taskqueues have dozens of > pending tasks?) Hi,

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Thursday 04 November 2010 20:01:57 Matthew Fleming wrote: > On Thu, Nov 4, 2010 at 11:41 AM, Hans Petter Selasky wrote: > > On Thursday 04 November 2010 15:29:51 John Baldwin wrote: > >> (and there is in Jeff's OFED branch) > > > > Is there a link to th

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Thursday 04 November 2010 21:11:38 Matthew Fleming wrote: > On Thu, Nov 4, 2010 at 12:11 PM, Hans Petter Selasky wrote: > > On Thursday 04 November 2010 20:01:57 Matthew Fleming wrote: > >> On Thu, Nov 4, 2010 at 11:41 AM, Hans Petter Selasky > > > > wrote:

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

er 04, 2010 5:49:22 pm Matthew Fleming wrote: > >> >> On Thu, Nov 4, 2010 at 2:22 PM, John Baldwin wrote: > >> >> > On Thursday, November 04, 2010 4:15:16 pm Hans Petter Selasky wrote: > >> >> >> I think that if a task is currently executing, th

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

Hi, In the patch attached to this e-mail I included Matthew Fleming's patch aswell. 1) I renamed taskqueue_cancel() into taskqueue_stop(), hence that resembles the words of the callout and USB API's terminology for doing the same. 2) I turns out I need to have code in subr_taskqueue.c to be a

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Friday 05 November 2010 19:13:08 Matthew Fleming wrote: > On Fri, Nov 5, 2010 at 10:36 AM, Hans Petter Selasky wrote: > > On Friday 05 November 2010 18:15:01 Matthew Fleming wrote: > >> On Fri, Nov 5, 2010 at 7:18 AM, John Baldwin wrote: > >> > On Friday, Novemb

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Friday 05 November 2010 19:39:45 Matthew Fleming wrote: > True, but no taskqueue(9) code can handle that. Only the caller can > prevent a task from becoming enqueued again. The same issue exists > with taskqueue_drain(). I find that strange, because that means if I queue a task again while it

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Friday 05 November 2010 19:48:05 Matthew Fleming wrote: > On Fri, Nov 5, 2010 at 11:45 AM, Hans Petter Selasky wrote: > > On Friday 05 November 2010 19:39:45 Matthew Fleming wrote: > >> True, but no taskqueue(9) code can handle that. Only the caller can > >> p

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

On Friday 05 November 2010 20:06:12 John Baldwin wrote: > On Friday, November 05, 2010 3:00:37 pm Hans Petter Selasky wrote: > > On Friday 05 November 2010 19:48:05 Matthew Fleming wrote: > > > On Fri, Nov 5, 2010 at 11:45 AM, Hans Petter Selasky > > > > wrote: >

Re: [RFC] Outline of USB process integration in the kernel taskqueue system

Hi, On Saturday 06 November 2010 14:57:50 Matthew Fleming wrote: > > I think you're misunderstanding the existing taskqueue(9) implementation. > > As long as TQ_LOCK is held, the state of ta->ta_pending cannot change, > nor can the set of running tasks. So the order of checks is > irrelevant.

Re: sleep bug in taskqueue(9)

On Thursday 29 April 2010 01:59:58 Matthew Fleming wrote: > It looks to me like taskqueue_drain(taskqueue_thread, foo) will not > correctly detect whether or not a task is currently running. The check > is against a field in the taskqueue struct, but for the taskqueue_thread > queue with more than

Re: sleep bug in taskqueue(9)

On Thursday 29 April 2010 01:59:58 Matthew Fleming wrote: > struct task { > - STAILQ_ENTRY(task) ta_link; /* link for queue */ > - u_short ta_pending; /* count times queued */ > - u_short ta_priority;/* Priority */ > - task_fn_t *ta_func;

Re: sleep bug in taskqueue(9)

On Friday 12 November 2010 10:06:10 you wrote: > - queue->tq_running = NULL; forgot this check: /* don't clear if queued again */ if (task->ta_entry.tqe_prev == (void *)1) > + task->ta_entry.tqe_prev = (void *)0; > wakeup

Re: sleep bug in taskqueue(9)

On Friday 12 November 2010 15:18:46 m...@freebsd.org wrote: > On Fri, Nov 12, 2010 at 12:56 AM, Hans Petter Selasky wrote: > > On Thursday 29 April 2010 01:59:58 Matthew Fleming wrote: > >> It looks to me like taskqueue_drain(taskqueue_thread, foo) will not > >> correc

Re: sleep bug in taskqueue(9)

On Friday 12 November 2010 17:38:38 m...@freebsd.org wrote: > On Fri, Nov 12, 2010 at 6:23 AM, Hans Petter Selasky wrote: > > On Friday 12 November 2010 15:18:46 m...@freebsd.org wrote: > >> On Fri, Nov 12, 2010 at 12:56 AM, Hans Petter Selasky > > > > wrote: &g

Re: MacBookPro7,1 and FreeBSD 8.1

On Friday 12 November 2010 18:28:02 Veniamin Gvozdikov wrote: > Hi everybody. > I have the macbook and I tryed install FreeBSD 8.1. But I have froze > loading. > > I have it's: > with acpi (default loading) > http://img203.imageshack.us/img203/2556/dscn2822u.jpg > > disable acpi > http://img152.i

Re: sleep bug in taskqueue(9)

On Friday 12 November 2010 22:24:51 m...@freebsd.org wrote: > On Fri, Nov 12, 2010 at 12:25 PM, Hans Petter Selasky wrote: > > On Friday 12 November 2010 17:38:38 m...@freebsd.org wrote: > >> On Fri, Nov 12, 2010 at 6:23 AM, Hans Petter Selasky > > > > wrote: >

Re: 'panic: make_dev_credv: bad si_name (error=17, si_name=ttyU0)' with USB serial adapter

On Wednesday 01 December 2010 03:29:41 David O'Brien wrote: > Thoughts? Hi, This is a know issue which has been fixed: http://svn.freebsd.org/viewvc/base?view=revision&revision=214919 Issue was introduced here: http://svn.freebsd.org/viewvc/base?view=revision&revision=214761 --HPS ___

Re: USB related panic on 8.2-PRERELEASE

t; > On Wed, Dec 8, 2010 at 3:33 PM, Hans Petter Selasky wrote: > >> On Wednesday 08 December 2010 11:41:28 Oleg Nauman wrote: > >>> Hello, > >>> > >>> Unfortunately my notebook experienced the crash during the attempts to > >>> attach EV

Re: USB related panic on 8.2-PRERELEASE

On Saturday 11 December 2010 10:09:45 Oleg Nauman wrote: > Hello Hans, > > On Fri, Dec 10, 2010 at 8:15 PM, Hans Petter Selasky wrote: > > Hi, > > > > I think this is a known issue which never got fixed. Please try the > > attached patch and report back.

Re: umidi question

On Tuesday 21 December 2010 22:26:19 Raoul wrote: > Hello all, > > It seems to me than the midi part (umidi) > of the uaudio driver does not work with poll nor SIGIO. > Am i right here, or is my test very buggy!!! > > Thanks Hi, FIOASYNC is supported and poll is supported - yes. See /sys/dev/u

Re: usb issues

On Wednesday 22 December 2010 07:15:53 justin v wrote: > Hi, > > Any advice on how to deal with this USB trouble.. ? > > > This is scrolling through messages.. and when i plug in my USB device, > ANY, it is not recognized, when normally it is... > What version of FreeBSD are you using? Have

Re: usb issues

On Wednesday 22 December 2010 21:31:19 Kim Culhan wrote: > On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote: > > On Wednesday 22 December 2010 07:15:53 justin v wrote: > >> Hi, > >> > >> Any advice on how to deal with this USB trouble.. ? > &

Re: usb issues

On Thursday 23 December 2010 21:59:13 Justin V. wrote: > On Thu, 23 Dec 2010, Hans Petter Selasky wrote: > > On Wednesday 22 December 2010 21:31:19 Kim Culhan wrote: > >> On Wed, December 22, 2010 3:00 am, Hans Petter Selasky wrote: > >>> On Wednesday 22 Decembe

Re: usb issues

On Friday 24 December 2010 02:27:55 Justin V. wrote: > On Thu, 23 Dec 2010, Hans Petter Selasky wrote: > > Im not familiar with patching I guess.. any tips? Then try to copy usb_request.c and usb_request.h --HPS ___ freebsd-current@freebsd.or

Re: keyboard driver problem?

On Sunday 02 January 2011 09:36:06 too.much.du...@gmail.com wrote: > Hello, have problem with A4Tech G7100 wireless combo mouse+keyboard. > Mouse works fine, but keyboard not. It's loading: > ugen4.2: at usbus4 > ukbd1: on usbus4 > but pressing any key doesn't have effect. It works only in one wa

Re: keyboard driver problem?

On Sunday 02 January 2011 09:36:06 too.much.du...@gmail.com wrote: > Hello, have problem with A4Tech G7100 wireless combo mouse+keyboard. > Mouse works fine, but keyboard not. It's loading: > ugen4.2: at usbus4 > ukbd1: on usbus4 > but pressing any key doesn't have effect. It works only in one wa

Re: keyboard driver problem?

On Sunday 02 January 2011 15:22:32 I Think wrote: > I've tried already to change both UKBD_NMOD and UKBD_NKEYCODE, but where is > no result. > #define UKBD_NKEYCODE 8 // doesn't work too > > > usbconfig -u 4 -a 2 dump_device_desc dump_curr_config_desc > > ugen4.2: at usbus4, cfg

Re: keyboard driver problem?

On Sunday 02 January 2011 15:42:42 too.much.du...@gmail.com wrote: > already tried variants : > offset+=4 && len-=4 > offset+=0 && len-=4 > and yours, but they doesn't have correct effect > (yours variant gives some addition lags: > for example pressing "o" presses Scroll Lock, "h" - WIN_L and etc)

Re: usb-regression (Tyan S3992-E)

On Wednesday 05 January 2011 00:36:29 Arno J. Klaassen wrote: > Hallo, > > definitely my Tyan S3992-E based box I didn't touch since a while, has > difficulties with recent code; this time I wanted to cross-install from > it on a USB-stick and noticed it didn't work. From dmesg : > > ohci early:

Re: Endless CAM messages with recent CURRENT

Marcus, Can you have a look at this? --HPS On Friday 14 January 2011 16:21:00 Rainer Hurling wrote: > After looking around I had been able to localise the cause for the > described messages, see below: > > On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote: > > Today I updated my 9.0-CURRENT sys

Re: Endless CAM messages with recent CURRENT

On Sunday 30 January 2011 14:57:37 Rainer Hurling wrote: > On 14.01.2011 20:10 (UTC+1), Hans Petter Selasky wrote: > > Marcus, > > > > Can you have a look at this? > > Are there any news? > I don't have any news, except it is a HAL problem and i

Re: Endless CAM messages with recent CURRENT

On Sunday 30 January 2011 16:15:02 Rainer Hurling wrote: > Wouldn't it be useful to integrate the device info into the usb driver? You can check if your kernel is compiled with "options USB_VERBOSE". That should bring some more verbosity based on sys/dev/usb/usbdevs. --HPS __

Re: Intermittent pauses copying from one usb drive to another

On Saturday 05 February 2011 14:27:56 Donald Allen wrote: > I've discussed problems with FreeBSD and usb sata drives on this list > in the past (as recently as last September), and have given up on > FreeBSD as a result of the usb disk problems (I do my backups with usb > drives) and other usb-rela

Re: Intermittent pauses copying from one usb drive to another

On Saturday 05 February 2011 16:18:56 Donald Allen wrote: > Does whoever is responsible for CAM/SCSI > know about this and do you know if there are plans to fix it? What is the > point of "supporting" USB devices (and we aren't talking about an odd-ball > device here; these are USB disks), when the

Re: Intermittent pauses copying from one usb drive to another

> > Hans Petter, > Could the USB mass storage layer not refuse to pass down some commands > and just return the proscribed error? Yes, that's what I'm thinking would be the simplest solution. I just need an overview which SCSI commands we should pass and not pass. Do you have an idea? --hps _

Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless

Hi, Can you check if I've integrated correctly? http://p4web.freebsd.org/@@17?ac=10 Who is taking this code into -current? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe

Re: Fwd: umodem (4) recognize a CDC-ACM device

On Wednesday 02 June 2010 03:23:47 Garrett Cooper wrote: > Looks like this device might be a bit quirky... Just forwarding to you > to see if you had any details for the OP. > Thanks! > -Garrett Hi, Can you dump the USB descriptors of your device? usbconfig -u 0 -a 3 dump_device_desc dump_curr_c

Re: Fwd: umodem (4) recognize a CDC-ACM device

> > Hi, > > > > Can you dump the USB descriptors of your device? > > Hi, right now I can do this at "FreeBSD 8.0-RELEASE-p2 #8 r206060M", > but If you prefer tonight I can dump from 'freebsd-current' box. > > Thank you Hi, The problem is that LOW speed does not support BULK transfers according

Re: Fwd: umodem (4) recognize a CDC-ACM device

On Thursday 03 June 2010 16:22:33 Marcelo/Porks wrote: > On Wed, Jun 2, 2010 at 1:25 PM, Hans Petter Selasky wrote: > > Hi, > > > > The problem is that LOW speed does not support BULK transfers according > > to the USB specification. I guess we could switch that suppor

Re: Fwd: umodem (4) recognize a CDC-ACM device

On Thursday 03 June 2010 17:50:08 Hans Petter Selasky wrote: > On Thursday 03 June 2010 16:22:33 Marcelo/Porks wrote: > > On Wed, Jun 2, 2010 at 1:25 PM, Hans Petter Selasky > > wrote: > > > Hi, > > > > > > The problem is that LOW speed does not support

Re: Fwd: umodem (4) recognize a CDC-ACM device

Could you join: #bsdusb on efnet ? --HPS ___ 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: Fwd: umodem (4) recognize a CDC-ACM device

On Thursday 03 June 2010 17:54:17 Hans Petter Selasky wrote: > On Thursday 03 June 2010 17:50:08 Hans Petter Selasky wrote: > > On Thursday 03 June 2010 16:22:33 Marcelo/Porks wrote: > > > On Wed, Jun 2, 2010 at 1:25 PM, Hans Petter Selasky > > > > wrote: > >

Re: Fwd: umodem (4) recognize a CDC-ACM device

On Friday 04 June 2010 03:02:52 Marcelo/Porks wrote: > On Thu, Jun 3, 2010 at 12:57 PM, Hans Petter Selasky wrote: > > On Thursday 03 June 2010 17:54:17 Hans Petter Selasky wrote: > >> On Thursday 03 June 2010 17:50:08 Hans Petter Selasky wrote: > >> > On Thursday

Re: run(4) patch

On Friday 11 June 2010 08:27:53 PseudoCylon wrote: > Hello, > > Here is a patch for recent fix. > http://lists.freebsd.org/pipermail/freebsd-current/2010-June/017749.html > Please update codes in your repository. > > Diff against the latest change, 178418. > * if_run.c - rev. 11 > * if_runvar.h -

Re: building world with debugging symbols [broken?]

of the line-break rules we use for mdoc). Other > > than that I think this looks fine. > > Fixed and committed in r205978. Thanks :) Hi, I've gotten several reports that cuse4bsd and other kernel modules built outside the kernel tree no longer load. Any clues about what is wrong? Is t

[HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1

Hi, I'm creating a new thread on this issue. On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote: > I saw similar behaviour a couple of years ago when I switched from > using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules. > The problem ended up being a change in the linker

Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1

On Wednesday 23 June 2010 08:47:52 Andriy Gapon wrote: > on 23/06/2010 03:38 Hans Petter Selasky said the following: > > Hi, > > > > I'm creating a new thread on this issue. > > > > On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote: > >> I s

Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1

On Wednesday 23 June 2010 09:10:59 Andriy Gapon wrote: > on 23/06/2010 10:02 Andriy Gapon said the following: > > I don't dispute that it is found broken in particular environments, I > > just think that the analysis could be incorrect. Ok. > > Which also brings the question - what arch(s) is af

Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1

On Wednesday 23 June 2010 16:43:31 Kris Moore wrote: > On 06/23/2010 02:52, Hans Petter Selasky wrote: > > On Wednesday 23 June 2010 08:47:52 Andriy Gapon wrote: > >> on 23/06/2010 03:38 Hans Petter Selasky said the following: > >>> Hi, > >>> >

Patch for rc.d/devd on FreeBSD 9-current

Hi, Sometimes utilities that are started by devd require libraries outside /usr/lib. One example is the webcamd utility which is started by devd upon USB device insertion. What do you think about the following patch: --- devd(revision 209463) +++ devd(local) @@ -4,7 +4,7 @@ #

Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless

Hi, PseudoCylon: Can you try to reproduce this: 1) Setup OPEN HOST AP (ssid = xxx). 2) Configure WLAN client with: ssid=xxx auth_alg=SHARED key_mgmt=NONE Wait until wpa_cli announces that it tries to associate, but fails. 3) Then update wpa_supplicant.conf: ssid=xxx auth_alg=OPEN key_mgmt=NO

Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless

On Wednesday 07 July 2010 12:49:37 PseudoCylon wrote: > - Original Message > > > From: Hans Petter Selasky > > To: freebsd-current@freebsd.org > > Cc: PseudoCylon ; Ganbold Tsagaankhuu > >; Ganbold > > Sent: Tue, July 6, 2010 12:54:31 AM > >

[panic] Race in IEEE802.11 layer towards device drivers

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)

Re: [panic] Race in IEEE802.11 layer towards device drivers

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

Re: QEMU/KVM Panic on USB Mount

On Friday 09 July 2010 19:12:59 Sean Bruno wrote: > In order to come up with the most convoluted problem possible, I present > to you screen shots of a panic from a FreeBSD VM running in QEMU > emulation under RedHat's KVM infrastructure. > > I presented a perfectly functional USB partition from m

Re: [panic] Race in IEEE802.11 layer towards device drivers

On Monday 12 July 2010 02:07:55 Andrew Thompson wrote: > This turned out to be refcounting of the ieee80211_node struct which > was causing this panic. vap->iv_bss can be freed at any time so all > users of it need to bump the refcount to use it safely. > > This patch should fix the panic in the r

Re: [panic] Race in IEEE802.11 layer towards device drivers

Hi Andrew, Your patch appears to be working. Can you fix this issue in the other WLAN drivers aswell? Then send an e-mail to request testing? I had a go at it here: http://p4web.freebsd.org/@@180844?ac=10 I found another panic issue: ifconfig wlan0 delete ifconfig wlan0 destroy When not assoc

Re: [panic] Race in IEEE802.11 layer towards device drivers

On Tuesday 13 July 2010 03:54:08 PseudoCylon wrote: > Should the debugging code, usb_pause_mtx(), be left in the code for > testing? If the drivers don't panic to begin with, we won't know the > patch really fixed the issue. > No, I think it is safe to remove it. --HPS ___

Re: [panic] Race in IEEE802.11 layer towards device drivers

On Wednesday 14 July 2010 14:31:29 PseudoCylon wrote: > -if(vap->iv_opmode == IEEE80211_M_HOSTAP){ > -RUN_LOCK(sc); > +if (vap->iv_opmode == IEEE80211_M_HOSTAP) > sc->cmdq_key_set = RUN_CMDQ_GO; > -RUN_UNLOCK(sc); > -} > Why are you removing these locks? --HPS _

Re: [panic] Race in IEEE802.11 layer towards device drivers

On Wednesday 14 July 2010 14:31:29 PseudoCylon wrote: > -if(vap->iv_opmode == IEEE80211_M_HOSTAP){ > -RUN_LOCK(sc); > +if (vap->iv_opmode == IEEE80211_M_HOSTAP) > sc->cmdq_key_set = RUN_CMDQ_GO; > -RUN_UNLOCK(sc); > -} > > Why are you removing these locks? Another question: i = RUN_CM

Re: [panic] Race in IEEE802.11 layer towards device drivers

Hi AK, I've committed your patches to USB P4. I've made some additional patches. Can you check and verify everything? http://p4web.freebsd.org/@@181189?ac=10 Also please compile a kernel with WITNESS enabled to catch any LOR's, hence we introduced another mutex. --HPS

Re: [panic] Race in IEEE802.11 layer towards device drivers

On Tuesday 20 July 2010 12:03:22 PseudoCylon wrote: > - Original Message > > > From: Hans Petter Selasky > > To: freebsd-current@freebsd.org > > Cc: PseudoCylon ; Sam Leffler ; > > > >freebsd-...@freebsd.org > > > > Sent: Mon, July 19,

Re: [panic] Race in IEEE802.11 layer towards device drivers

Hi, Please confirm that this patch is working for you: http://p4web.freebsd.org/@@181261?ac=10 --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-curren

mmap() problem

Hi, When is it safe to free memory which has been mmapped to a user-space application? After close() or during close() or before close() or when the process/thread terminates? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org

[BETA testing] USB 3.0 Super Speed support in FreeBSD

Hi, During the last two weeks I've been working hard to get USB 3.0 support added to the FreeBSD 8+ USB stack. There are a couple of issues left, but right now the code is in a state were enumeration of USB devices is possible and there are no dirty hacks :-) The XHCI chip, which is the PCI in

Re: drm / drm2 removal in 12

On 8/26/18 3:20 AM, blubee blubeeme wrote: Have you or anyone working on this drm-legacy-kmod stuff done any testings of how this will affect current users? Hi Blubee, Are you here to try to stir a conflict? If so that is not appreciated. --HPS ___

Re: Is there a standard way to check patch before submitting for review or upstreaming?

On 10/4/18 1:08 PM, Rajesh Kumar wrote: Hi, Do we have any standard tools/process in FreeBSD to check/validate the patch for basic issues before we submit them for review or upstreaming? Basically, something like checkpatch.pl in Linux. Thanks, Rajesh. Hi, There is something in /usr/src/tool

Re: drm confusion / xorg / AMD RX580 GPU

On 10/8/18 3:06 PM, Warner Losh wrote: You need "/boot/kernel/amdgpu.ko" here Warner Or did you mean: /boot/modules/amdgpu.ko --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscri

Re: DRM: radeonkms … can not be unloaded (kernel panic)) …

On 10/20/18 3:10 AM, Graham Perrin wrote: On 20/10/2018 00:01, Graham Perrin wrote: kldunload radeonkms – results in a kernel panic. Found, at under 'drm-devel-kmod g20180822 screen freeze': … normally you never

Re: Page fault in midi/sequencer.c

On 10/20/18 6:56 PM, Peter Holm wrote: I can trigger this on 13.0-CURRENT r339445 with a non-root test program: Calling uiomove() with the following non-sleepable locks held: exclusive sleep mutex seqflq (seqflq) r = 0 (0xf80003860c08) locked @ dev/sound/midi/sequencer.c:952 stack backtrace

Re: Page fault in midi/sequencer.c

On 10/20/18 6:56 PM, Peter Holm wrote: I can trigger this on 13.0-CURRENT r339445 with a non-root test program: Hi, The following commits should fix the issues you experience: https://svnweb.freebsd.org/changeset/base/339581 https://svnweb.freebsd.org/changeset/base/339582 https://svnweb.fre

  1   2   3   4   5   6   7   8   9   10   >