Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-usb Digest, Vol 278, Issue 2

0 views

Skip to first unread message

freebsd-u...@freebsd.org

unread,

Mar 5, 2010, 6:50:16 AM3/5/10

to freeb...@freebsd.org

Send freebsd-usb mailing list submissions to
freeb...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
or, via email, send a message with subject or body 'help' to
freebsd-u...@freebsd.org

You can reach the person managing the list at
freebsd-...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-usb digest..."

Today's Topics:

1. Re: usb/127543: [patch] [ubsa] Support Option Globetrotter
HSDPA modem (Hans Petter Selasky)
2. Re: usb/144387: if_run panic (Hans Petter Selasky)
3. Re: usb/127543: [patch] [ubsa] Support Option Globetrotter
HSDPA modem (Hans Petter Selasky)
4. Re: docs/127406: [patch] update umodem man page: Sony
Ericsson W810i (Hans Petter Selasky)
5. Re: docs/127406: [patch] update umodem man page: Sony
Ericsson W810i (Hans Petter Selasky)
6. Re: usb/144414: Apple "Fn" key doesn't work properly
(Hans Petter Selasky)
7. Re: usb/144414: Apple "Fn" key doesn't work properly
(Hans Petter Selasky)
8. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
9. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
10. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
11. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
12. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
13. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
14. Re: usb/144414: Apple "Fn" key doesn't work properly
(Hans Petter Selasky)
15. Re: usb/144414: Apple "Fn" key doesn't work properly
(Hans Petter Selasky)
16. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
17. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
18. Re: usb/144414: Apple "Fn" key doesn't work properly
(per...@pluto.rain.com)
19. Re: usb/144414: Apple "Fn" key doesn't work properly
(per...@pluto.rain.com)
20. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
21. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
22. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
23. Re: usb/144414: Apple "Fn" key doesn't work properly
(Steven Noonan)
24. Re: usb/144423: if_run panic with USB-N13 (Hans Petter Selasky)
25. Re: usb/144423: if_run panic with USB-N13 (Hans Petter Selasky)
26. Re: usb/144387: if_run panic (PseudoCylon)
27. Re: usb/144387: if_run panic (Alexander Kuznetsov)
28. Re: usb/144423: if_run panic with USB-N13 (Jonathan Hanna)
29. Re: usb/144423: if_run panic with USB-N13 (Jonathan Hanna)
30. Re: usb/144423: if_run panic with USB-N13 (PseudoCylon)
31. Re: usb/144423: if_run panic with USB-N13 (Hans Petter Selasky)
32. Re: usb/144423: if_run panic with USB-N13 (Hans Petter Selasky)
33. Re: usb/144423: if_run panic with USB-N13 (Hans Petter Selasky)
34. video cam with room view for FreeBSD && Skype (Matthias Apitz)
35. Re: usb/144423: if_run panic with USB-N13 (PseudoCylon)
36. Re: usb/144423: if_run panic with USB-N13 (PseudoCylon)
37. Re: usb/144423: if_run panic with USB-N13 (PseudoCylon)
38. Re: usb/144423: if_run panic with USB-N13 (PseudoCylon)

----------------------------------------------------------------------

Message: 1
Date: Tue, 2 Mar 2010 22:47:17 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/127543: [patch] [ubsa] Support Option Globetrotter
HSDPA modem
To: freeb...@freebsd.org
Cc: freebsd-gn...@freebsd.org, lin...@freebsd.org,
n_h...@freebsd.org
Message-ID: <201003022247....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Monday 01 March 2010 12:14:33 n_h...@freebsd.org wrote:
> Synopsis: [patch] [ubsa] Support Option Globetrotter HSDPA modem
>
> Responsible-Changed-From-To: n_hibma->freeb...@FreeBSD.org
> Responsible-Changed-By: n_hibma
> Responsible-Changed-When: Mon Mar 1 11:12:53 UTC 2010
> Responsible-Changed-Why:
> No time to work on this anytime soon.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=127543

This hardware is supported by the u3g driver. This PR can be closed.

--HPS

------------------------------

Message: 2
Date: Tue, 2 Mar 2010 21:50:03 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144387: if_run panic
To: freeb...@FreeBSD.org
Message-ID: <201003022150....@freefall.freebsd.org>

The following reply was made to PR usb/144387; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: Alexander Kuznetsov <skr...@gmail.com>,
freebsd-gn...@freebsd.org
Subject: Re: usb/144387: if_run panic
Date: Tue, 2 Mar 2010 22:44:11 +0100

On Monday 01 March 2010 12:50:27 Alexander Kuznetsov wrote:
> >Number: 144387
> >Category: usb
> >Synopsis: if_run panic
> >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: Mon Mar 01 12:00:06 UTC 2010
> >Closed-Date:
> >Last-Modified:
> >Originator: Alexander Kuznetsov
> >Release: 9.0-CURRENT (both i386 and amd64)
> >Organization:
> >Environment:
> >Description:
>
> if_run causes kernel panic
>
> run0: device timeout
> panic: mutex run0 not owned at
> /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/run/if_run.c:3376 cpuid
> = 0
> KDB: enter: panic
> [ thread pid 0 tid 100068 ]
> Stopped at kdb_enter+0x3d: movq $0,0x6b5b30(%rip)
> db>bt
> Tracing pid 0 tid 100068 td 0xffffff000252d000
> kdb_enter() at kdb_enter+0x3d
> panic() at panic+0x17b
> _mtx_assert() at _mtx_assert+0xdc
> run_usb_timeout_cb() at run_usb_timeout_cb+0x35
> taskqueue_run() at taskqueue_run+0x91
> taskqueue_thread_loop() at taskqueue_thread_loop+0x3f
> fork_exit() at fork_exit+0x12a
> fork_trampoline() at fork_trampoline+0xe
> --- trap 0, rip = 0, rsp = 0xffffff80001bcd30, rbp = 0 ---
> db>
>
> >How-To-Repeat:
>
> # kldload if_run
> # ifconfig wlan create wlandev run0 wlanmode hostap
> # ifconfig wlan0 ssid test
> # ifconfig wlan0 inet 192.168.0.10
> [panic after some seconds]
>
> >Fix:
> >
> >
> >Release-Note:
> >Audit-Trail:
> >Unformatted:

This is a know issue which has been fixed, but not committed to -current yet.

--HPS

------------------------------

Message: 3
Date: Tue, 2 Mar 2010 21:50:05 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/127543: [patch] [ubsa] Support Option Globetrotter
HSDPA modem
To: freeb...@FreeBSD.org
Message-ID: <201003022150....@freefall.freebsd.org>

The following reply was made to PR usb/127543; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: n_h...@freebsd.org,
lin...@freebsd.org,
freebsd-gn...@freebsd.org
Subject: Re: usb/127543: [patch] [ubsa] Support Option Globetrotter HSDPA modem
Date: Tue, 2 Mar 2010 22:47:17 +0100

------------------------------

Message: 4
Date: Tue, 2 Mar 2010 22:49:38 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: docs/127406: [patch] update umodem man page: Sony
Ericsson W810i
To: freeb...@freebsd.org
Cc: freebsd-gn...@freebsd.org, lin...@freebsd.org,
n_h...@freebsd.org
Message-ID: <201003022249....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Monday 01 March 2010 12:15:41 n_h...@freebsd.org wrote:
> Synopsis: [patch] update umodem man page: Sony Ericsson W810i
>
> Responsible-Changed-From-To: n_hibma->freeb...@FreeBSD.org
> Responsible-Changed-By: n_hibma
> Responsible-Changed-When: Mon Mar 1 11:15:13 UTC 2010
> Responsible-Changed-Why:
>
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=127406

The patch in the PR looks already committed, at least to the USB P4
repository. The PR can be closed.

--HPS

------------------------------

Message: 5
Date: Tue, 2 Mar 2010 22:00:13 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: docs/127406: [patch] update umodem man page: Sony
Ericsson W810i
To: freeb...@FreeBSD.org
Message-ID: <201003022200....@freefall.freebsd.org>

The following reply was made to PR docs/127406; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: n_h...@freebsd.org,
freebsd-gn...@freebsd.org,
lin...@freebsd.org
Subject: Re: docs/127406: [patch] update umodem man page: Sony Ericsson W810i
Date: Tue, 2 Mar 2010 22:49:38 +0100

------------------------------

Message: 6
Date: Tue, 2 Mar 2010 23:27:36 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@freebsd.org
Cc: Steven Noonan <ste...@uplinklabs.net>,
freebsd-gn...@freebsd.org
Message-ID: <201003022327....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Tuesday 02 March 2010 08:59:18 Steven Noonan wrote:
> usb/144414
>

Please try the following patch:

http://perforce.freebsd.org/chv.cgi?CH=175283

Thanks for dumping the HID descriptors.

--HPS

------------------------------

Message: 7
Date: Tue, 2 Mar 2010 22:30:05 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003022230....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: Steven Noonan <ste...@uplinklabs.net>,
freebsd-gn...@freebsd.org
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
Date: Tue, 2 Mar 2010 23:27:36 +0100

On Tuesday 02 March 2010 08:59:18 Steven Noonan wrote:
> usb/144414
>

Please try the following patch:

http://perforce.freebsd.org/chv.cgi?CH=175283

Thanks for dumping the HID descriptors.

--HPS

------------------------------

Message: 8
Date: Tue, 2 Mar 2010 18:58:40 -0800
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<f488382f1003021858u243...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

I tried the patch (and included rev 175284's bugfix). No luck, it
still doesn't behave as expected. Here's the dmesg output for
Fn+Backspace:

ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_intr_callback:597: [5] = 1
ukbd_put_key:312: 0x01 (1) pressed
ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_intr_callback:597: [0] = 42
ukbd_intr_callback:597: [5] = 1
ukbd_put_key:312: 0x2a (42) pressed
ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_intr_callback:597: [5] = 1
ukbd_put_key:312: 0x42a (1066) released
ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_put_key:312: 0x401 (1025) released

- Steven

------------------------------

Message: 9
Date: Wed, 3 Mar 2010 03:30:03 GMT
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003030330....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

From: Steven Noonan <ste...@uplinklabs.net>
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
Date: Tue, 2 Mar 2010 18:58:40 -0800

On Tue, Mar 2, 2010 at 2:27 PM, Hans Petter Selasky <hsel...@c2i.net> wrote:
> On Tuesday 02 March 2010 08:59:18 Steven Noonan wrote:
>> usb/144414
>>
>
> Please try the following patch:
>
> http://perforce.freebsd.org/chv.cgi?CH=175283
>
> Thanks for dumping the HID descriptors.
>
> --HPS
>

I tried the patch (and included rev 175284's bugfix). No luck, it
still doesn't behave as expected. Here's the dmesg output for
Fn+Backspace:

ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_intr_callback:597: [5] = 1
ukbd_put_key:312: 0x01 (1) pressed
ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_intr_callback:597: [0] = 42
ukbd_intr_callback:597: [5] = 1
ukbd_put_key:312: 0x2a (42) pressed
ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_intr_callback:597: [5] = 1
ukbd_put_key:312: 0x42a (1066) released
ukbd_intr_callback:547: actlen=8 bytes
ukbd_intr_callback:590: apple_eject=0 apple_fn=0
ukbd_put_key:312: 0x401 (1025) released

- Steven

------------------------------

Message: 10
Date: Tue, 2 Mar 2010 19:35:38 -0800
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<f488382f1003021935v236...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Tue, Mar 2, 2010 at 6:58 PM, Steven Noonan <ste...@uplinklabs.net> wrote:
> On Tue, Mar 2, 2010 at 2:27 PM, Hans Petter Selasky <hsel...@c2i.net> wrote:
>> On Tuesday 02 March 2010 08:59:18 Steven Noonan wrote:
>>> usb/144414
>>>
>>
>> Please try the following patch:
>>
>> http://perforce.freebsd.org/chv.cgi?CH=175283
>>
>> Thanks for dumping the HID descriptors.
>>
>> --HPS
>>
>
> I tried the patch (and included rev 175284's bugfix). No luck, it
> still doesn't behave as expected. Here's the dmesg output for
> Fn+Backspace:
>
> ukbd_intr_callback:547: actlen=8 bytes
> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
> ukbd_intr_callback:597: [5] = 1
> ukbd_put_key:312: 0x01 (1) pressed
> ukbd_intr_callback:547: actlen=8 bytes
> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
> ukbd_intr_callback:597: [0] = 42
> ukbd_intr_callback:597: [5] = 1
> ukbd_put_key:312: 0x2a (42) pressed
> ukbd_intr_callback:547: actlen=8 bytes
> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
> ukbd_intr_callback:597: [5] = 1
> ukbd_put_key:312: 0x42a (1066) released
> ukbd_intr_callback:547: actlen=8 bytes
> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
> ukbd_put_key:312: 0x401 (1025) released
>
> - Steven
>

I just noticed that it does say "Found Apple FN-key" in dmesg, though.
So it does detect it, but it's still not finding it when it's actually
pressed.

- Steven

------------------------------

Message: 11
Date: Wed, 3 Mar 2010 03:40:02 GMT
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003030340....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

------------------------------

Message: 12
Date: Tue, 2 Mar 2010 20:39:43 -0800
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<f488382f1003022039j614...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Tue, Mar 2, 2010 at 7:35 PM, Steven Noonan <ste...@uplinklabs.net> wrote:
> On Tue, Mar 2, 2010 at 6:58 PM, Steven Noonan <ste...@uplinklabs.net> wrote:
>> On Tue, Mar 2, 2010 at 2:27 PM, Hans Petter Selasky <hsel...@c2i.net> wrote:
>>> On Tuesday 02 March 2010 08:59:18 Steven Noonan wrote:
>>>> usb/144414
>>>>
>>>
>>> Please try the following patch:
>>>
>>> http://perforce.freebsd.org/chv.cgi?CH=175283
>>>
>>> Thanks for dumping the HID descriptors.
>>>
>>> --HPS
>>>
>>
>> I tried the patch (and included rev 175284's bugfix). No luck, it
>> still doesn't behave as expected. Here's the dmesg output for
>> Fn+Backspace:
>>
>> ukbd_intr_callback:547: actlen=8 bytes
>> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
>> ukbd_intr_callback:597: [5] = 1
>> ukbd_put_key:312: 0x01 (1) pressed
>> ukbd_intr_callback:547: actlen=8 bytes
>> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
>> ukbd_intr_callback:597: [0] = 42
>> ukbd_intr_callback:597: [5] = 1
>> ukbd_put_key:312: 0x2a (42) pressed
>> ukbd_intr_callback:547: actlen=8 bytes
>> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
>> ukbd_intr_callback:597: [5] = 1
>> ukbd_put_key:312: 0x42a (1066) released
>> ukbd_intr_callback:547: actlen=8 bytes
>> ukbd_intr_callback:590: apple_eject=0 apple_fn=0
>> ukbd_put_key:312: 0x401 (1025) released
>>
>> - Steven
>>
>
> I just noticed that it does say "Found Apple FN-key" in dmesg, though.
> So it does detect it, but it's still not finding it when it's actually
> pressed.
>
> - Steven
>

Blargh. Nevermind, I mis-applied the patch.

In any case, it should detect an Eject key, too, but it seems to not
discover it with the current code.

- Steven

------------------------------

Message: 13
Date: Wed, 3 Mar 2010 04:40:05 GMT
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003030440....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

------------------------------

Message: 14
Date: Wed, 3 Mar 2010 09:46:41 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: Steven Noonan <ste...@uplinklabs.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID: <201003030946....@c2i.net>
Content-Type: Text/Plain; charset="utf-8"

On Wednesday 03 March 2010 05:39:43 Steven Noonan wrote:
> On Tue, Mar 2, 2010 at 7:35 PM, Steven Noonan <ste...@uplinklabs.net> wrote:
> > On Tue, Mar 2, 2010 at 6:58 PM, Steven Noonan <ste...@uplinklabs.net>
wrote:
> >> On Tue, Mar 2, 2010 at 2:27 PM, Hans Petter Selasky <hsel...@c2i.net>
wrote:
> >>> On Tuesday 02 March 2010 08:59:18 Steven Noonan wrote:
> >>>> usb/144414
> >>>
> >>> Please try the following patch:
> >>>
> >>> http://perforce.freebsd.org/chv.cgi?CH=175283
> >>>
> >>> Thanks for dumping the HID descriptors.
> >>>
> >>> --HPS
> >>
> >> I tried the patch (and included rev 175284's bugfix). No luck, it
> >> still doesn't behave as expected. Here's the dmesg output for
> >> Fn+Backspace:
> >>

Hi,

Could you add a debug print to print out the 8 bytes of data in
ukbd_intr_callback() (sys/dev/usb/input/ukbd.c) and figure out which bit
corresponds to the fn key?

--HPS

------------------------------

Message: 15
Date: Wed, 3 Mar 2010 08:50:02 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003030850....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: Steven Noonan <ste...@uplinklabs.net>
Cc: freeb...@freebsd.org,
freebsd-gn...@freebsd.org
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
Date: Wed, 3 Mar 2010 09:46:41 +0100

------------------------------

Message: 16
Date: Wed, 3 Mar 2010 02:41:29 -0800
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<f488382f1003030241s16...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 3, 2010 at 12:46 AM, Hans Petter Selasky <hsel...@c2i.net> wrote:
> On Wednesday 03 March 2010 05:39:43 Steven Noonan wrote:
>> On Tue, Mar 2, 2010 at 7:35 PM, Steven Noonan <ste...@uplinklabs.net> wrote:
>> > On Tue, Mar 2, 2010 at 6:58 PM, Steven Noonan <ste...@uplinklabs.net>
> wrote:
>> >> On Tue, Mar 2, 2010 at 2:27 PM, Hans Petter Selasky <hsel...@c2i.net>
> wrote:
>> >>> On Tuesday 02 March 2010 08:59:18 Steven Noonan wrote:
>> >>>> usb/144414
>> >>>
>> >>> Please try the following patch:
>> >>>
>> >>> http://perforce.freebsd.org/chv.cgi?CH=175283
>> >>>
>> >>> Thanks for dumping the HID descriptors.
>> >>>
>> >>> --HPS
>> >>
>> >> I tried the patch (and included rev 175284's bugfix). No luck, it
>> >> still doesn't behave as expected. Here's the dmesg output for
>> >> Fn+Backspace:
>> >>
>
> Hi,
>
> Could you add a debug print to print out the 8 bytes of data in
> ukbd_intr_callback() (sys/dev/usb/input/ukbd.c) and figure out which bit
> corresponds to the fn key?
>

Sorry, I wasn't clear in my last email. The patch works as expected, I
just failed to apply it properly and didn't notice until after I sent
my response.

The Fn key works fine now, but the Eject key still isn't detected.

Interestingly, my tilde key doesn't work either (though the key press
is detected, no character shows when the key is pressed).

- Steven

------------------------------

Message: 17
Date: Wed, 3 Mar 2010 10:50:02 GMT
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003031050....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

------------------------------

Message: 18
Date: Wed, 03 Mar 2010 22:36:00 -0800
From: per...@pluto.rain.com
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: ste...@uplinklabs.net
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID: <4b8f54d0.wm8q7hQf7ps9EVCI%per...@pluto.rain.com>
Content-Type: text/plain; charset=us-ascii

Steven Noonan <ste...@uplinklabs.net> wrote:
> Interestingly, my tilde key doesn't work either (though the key
> press is detected, no character shows when the key is pressed).

Any chance it is configured as a "dead" key? If you press
tilde followed by n do you get an n with a tilde over it?

------------------------------

Message: 19
Date: Thu, 4 Mar 2010 06:40:04 GMT
From: per...@pluto.rain.com
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003040640....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

From: per...@pluto.rain.com
To: ste...@uplinklabs.net
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
Date: Wed, 03 Mar 2010 22:36:00 -0800

Steven Noonan <ste...@uplinklabs.net> wrote:
> Interestingly, my tilde key doesn't work either (though the key
> press is detected, no character shows when the key is pressed).

Any chance it is configured as a "dead" key? If you press
tilde followed by n do you get an n with a tilde over it?

------------------------------

Message: 20
Date: Wed, 3 Mar 2010 23:00:13 -0800
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: per...@pluto.rain.com
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<f488382f1003032300i389...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

Nope. It simply does nothing in the console.

But in X11, it does something very odd. Shift+Tilde Key gives me '>',
and Tilde Key gives me '<'. And Alt+Tilde gives me... What? I don't
even know what action it's grabbing some arbitrary command in my
.bash_history. It gave me the first item in my .bash_history the first
time I tried it. Then I tried an arbitrary command ("echo"), and then
Alt+Tilde gave me the second command in my .bash_history. Whaa?

- Steven

------------------------------

Message: 21
Date: Wed, 3 Mar 2010 23:01:16 -0800
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: per...@pluto.rain.com
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID:
<f488382f1003032301n19...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 3, 2010 at 11:00 PM, Steven Noonan <ste...@uplinklabs.net> wrote:
> On Wed, Mar 3, 2010 at 10:36 PM, <per...@pluto.rain.com> wrote:
>> Steven Noonan <ste...@uplinklabs.net> wrote:
>>> Interestingly, my tilde key doesn't work either (though the key
>>> press is detected, no character shows when the key is pressed).
>>
>> Any chance it is configured as a "dead" key? If you press
>> tilde followed by n do you get an n with a tilde over it?
>>
>
> Nope. It simply does nothing in the console.
>
> But in X11, it does something very odd. Shift+Tilde Key gives me '>',
> and Tilde Key gives me '<'. And Alt+Tilde gives me... What? I don't
> even know what action. It's grabbing some arbitrary command in my
> .bash_history. It gave me the first item in my .bash_history the first
> time I tried it. Then I tried an arbitrary command ("echo"), and then
> Alt+Tilde gave me the second command in my .bash_history. Whaa?
>
> - Steven

Ugh. If only life had a rewind/erase button, I could fix my poor
proofreading and no one would be the wiser. See above for fixed
nonsense.

- Steven
>

------------------------------

Message: 22
Date: Thu, 4 Mar 2010 07:10:03 GMT
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003040710....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

From: Steven Noonan <ste...@uplinklabs.net>
To: per...@pluto.rain.com
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
Date: Wed, 3 Mar 2010 23:00:13 -0800

On Wed, Mar 3, 2010 at 10:36 PM, <per...@pluto.rain.com> wrote:
> Steven Noonan <ste...@uplinklabs.net> wrote:
>> Interestingly, my tilde key doesn't work either (though the key
>> press is detected, no character shows when the key is pressed).
>
> Any chance it is configured as a "dead" key? =C2=A0If you press
> tilde followed by n do you get an n with a tilde over it?
>

Nope. It simply does nothing in the console.

But in X11, it does something very odd. Shift+Tilde Key gives me '>',
and Tilde Key gives me '<'. And Alt+Tilde gives me... What? I don't
even know what action it's grabbing some arbitrary command in my
.bash_history. It gave me the first item in my .bash_history the first
time I tried it. Then I tried an arbitrary command ("echo"), and then
Alt+Tilde gave me the second command in my .bash_history. Whaa?

- Steven

------------------------------

Message: 23
Date: Thu, 4 Mar 2010 07:10:05 GMT
From: Steven Noonan <ste...@uplinklabs.net>
Subject: Re: usb/144414: Apple "Fn" key doesn't work properly
To: freeb...@FreeBSD.org
Message-ID: <201003040710....@freefall.freebsd.org>

The following reply was made to PR usb/144414; it has been noted by GNATS.

On Wed, Mar 3, 2010 at 11:00 PM, Steven Noonan <ste...@uplinklabs.net> wrot=
e:
> On Wed, Mar 3, 2010 at 10:36 PM, =C2=A0<per...@pluto.rain.com> wrote:
>> Steven Noonan <ste...@uplinklabs.net> wrote:
>>> Interestingly, my tilde key doesn't work either (though the key
>>> press is detected, no character shows when the key is pressed).
>>
>> Any chance it is configured as a "dead" key? =C2=A0If you press
>> tilde followed by n do you get an n with a tilde over it?
>>
>
> Nope. It simply does nothing in the console.
>
> But in X11, it does something very odd. Shift+Tilde Key gives me '>',
> and Tilde Key gives me '<'. And Alt+Tilde gives me... What? I don't
> even know what action. It's grabbing some arbitrary command in my
> .bash_history. It gave me the first item in my .bash_history the first
> time I tried it. Then I tried an arbitrary command ("echo"), and then
> Alt+Tilde gave me the second command in my .bash_history. Whaa?
>
> - Steven

Ugh. If only life had a rewind/erase button, I could fix my poor
proofreading and no one would be the wiser. See above for fixed
nonsense.

- Steven
>

------------------------------

Message: 24
Date: Thu, 4 Mar 2010 09:09:57 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@freebsd.org
Cc: freebsd-gn...@freebsd.org, Jonathan Hanna
<jha...@pangolin-systems.com>
Message-ID: <201003040909....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

Hi,

Can you try the following patch:

http://perforce.freebsd.org/chv.cgi?CH=175340

There is a download link at the file-view page that allows you to download
each file in plain-text.

--HPS

------------------------------

Message: 25
Date: Thu, 4 Mar 2010 08:20:05 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@FreeBSD.org
Message-ID: <201003040820....@freefall.freebsd.org>

The following reply was made to PR usb/144423; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: Jonathan Hanna <jha...@pangolin-systems.com>,
freebsd-gn...@freebsd.org
Subject: Re: usb/144423: if_run panic with USB-N13
Date: Thu, 4 Mar 2010 09:09:57 +0100

Hi,

Can you try the following patch:

http://perforce.freebsd.org/chv.cgi?CH=175340

There is a download link at the file-view page that allows you to download
each file in plain-text.

--HPS

------------------------------

Message: 26
Date: Thu, 4 Mar 2010 01:26:47 -0800 (PST)
From: PseudoCylon <moonlig...@yahoo.ca>
Subject: Re: usb/144387: if_run panic
To: Alexander Kuznetsov <skr...@gmail.com>
Cc: freeb...@FreeBSD.org
Message-ID: <511773....@web51805.mail.re2.yahoo.com>
Content-Type: text/plain; charset=us-ascii

Hello,

Can you try this patch?
http://dev.nasreddine.com/gitweb/?p=run.git;a=shortlog;h=refs/heads/hostap_rc
and click "snapshot" at the top of right hand column. You can get everything in a tarball.
or you can git @ git://dev.nasreddine.com/run.git
please fetch 'hostap_rc' branch.

Please let me know how it goes.

Thanks
AK

----
"FreeBSD and all other open source projects are the Tower of Babel in computer era." --me
So, join me @ git://dev.nasreddine.com/run.git
(or http://dev.nasreddine.com/gitweb/?p=run.git;a=summary )
Just work on any of *_dev branches.

__________________________________________________________________
Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com

------------------------------

Message: 27
Date: Thu, 04 Mar 2010 18:00:51 +0300
From: Alexander Kuznetsov <skr...@gmail.com>
Subject: Re: usb/144387: if_run panic
To: PseudoCylon <moonlig...@yahoo.ca>
Cc: freeb...@FreeBSD.org
Message-ID: <4B8FCB23...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

04.03.2010 12:26, PseudoCylon пишет:
> Hello,
>
> Can you try this patch?
> http://dev.nasreddine.com/gitweb/?p=run.git;a=shortlog;h=refs/heads/hostap_rc
> and click "snapshot" at the top of right hand column. You can get everything in a tarball.
> or you can git @ git://dev.nasreddine.com/run.git
> please fetch 'hostap_rc' branch.
>
> Please let me know how it goes.
>
> Thanks
> AK
>
> ----
> "FreeBSD and all other open source projects are the Tower of Babel in computer era." --me
> So, join me @ git://dev.nasreddine.com/run.git
> (or http://dev.nasreddine.com/gitweb/?p=run.git;a=summary )
> Just work on any of *_dev branches.
>
>
>
> __________________________________________________________________
> Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
>
>

Yes, now it works fine. Thank you!

------------------------------

Message: 28
Date: Fri, 5 Mar 2010 01:00:14 GMT
From: Jonathan Hanna <jha...@pangolin-systems.com>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@FreeBSD.org
Message-ID: <201003050100....@freefall.freebsd.org>

The following reply was made to PR usb/144423; it has been noted by GNATS.

From: Jonathan Hanna <jha...@pangolin-systems.com>
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/144423: if_run panic with USB-N13
Date: Thu, 04 Mar 2010 16:59:50 -0800

On 03/04/10 00:09, Hans Petter Selasky wrote:
> Hi,
>
> Can you try the following patch:
>
> http://perforce.freebsd.org/chv.cgi?CH=175340
>
> There is a download link at the file-view page that allows you to download
> each file in plain-text.

The files seem a little far from the current I am running, I just used
the updates to the usbdevs file and the unlock-lock around the firmware load
in if_run.c.

The ASUS-N13 does work when a child wlan device is created with it,
but if just "ifconfig run0 up" is done there is a page fault. I do
not know if that is expected. This occurs with or without runfw.ko
being loaded beforehand.

------------------------------

Message: 29
Date: Thu, 04 Mar 2010 16:59:50 -0800
From: Jonathan Hanna <jha...@pangolin-systems.com>
Subject: Re: usb/144423: if_run panic with USB-N13
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID: <4B905786...@pangolin-systems.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed

The files seem a little far from the current I am running, I just used
the updates to the usbdevs file and the unlock-lock around the firmware load
in if_run.c.

The ASUS-N13 does work when a child wlan device is created with it,
but if just "ifconfig run0 up" is done there is a page fault. I do
not know if that is expected. This occurs with or without runfw.ko
being loaded beforehand.

------------------------------

Message: 30
Date: Fri, 5 Mar 2010 01:31:35 -0800 (PST)
From: PseudoCylon <moonlig...@yahoo.ca>
Subject: Re: usb/144423: if_run panic with USB-N13
To: bug-fo...@FreeBSD.org, jha...@pangolin-systems.com
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID: <300673....@web51805.mail.re2.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1

>The files seem a little far from the current I am running, I just used
>the updates to the usbdevs file and the unlock-lock around the firmware load
>in if_run.c.
Yes, there are some bits added to support RT3572 chipsets. It would be greately appreciated if you try that file if it's not too mutch trouble.

>The ASUS-N13 does work when a child wlan device is created with it,
>but if just "ifconfig run0 up" is done there is a page fault. I do
>not know if that is expected. This occurs with or without runfw.ko
>being loaded beforehand.
Yes, "ifconfig run0 up" will cause page fault. The wlanN interface is should be created as an instance of the parent interface and used for actual communication. This is new feature to 8.0 and 9-current. My understanding is that if you create wlan and "ifconfig *wlan0* up", it works, but if you "ifconfig *run0* up", it causes panic. (Of cource without *. I'm trying to enphasize the point in plain text messeage.) That is what should happen. (Actually, result of "ifconfig *run0* up" is undefined.) "run0" should only be used when creating wlan.

If "ifconfig *wlan0* ..." is causing problem, please let us know.

__________________________________________________________________
The new Internet Explorer� 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/

------------------------------

Message: 31
Date: Fri, 5 Mar 2010 10:42:41 +0100
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144423: if_run panic with USB-N13
To: PseudoCylon <moonlig...@yahoo.ca>
Cc: freebsd-gn...@freebsd.org, jha...@pangolin-systems.com,
freeb...@freebsd.org, bug-fo...@freebsd.org
Message-ID: <201003051042....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-1"

On Friday 05 March 2010 10:31:35 PseudoCylon wrote:
> >The files seem a little far from the current I am running, I just used
> >the updates to the usbdevs file and the unlock-lock around the firmware
> > load in if_run.c.
>
> Yes, there are some bits added to support RT3572 chipsets. It would be
> greately appreciated if you try that file if it's not too mutch trouble.
>
> >The ASUS-N13 does work when a child wlan device is created with it,
> >but if just "ifconfig run0 up" is done there is a page fault. I do
> >not know if that is expected. This occurs with or without runfw.ko
> >being loaded beforehand.
>
> Yes, "ifconfig run0 up" will cause page fault. The wlanN interface is
> should be created as an instance of the parent interface and used for
> actual communication. This is new feature to 8.0 and 9-current. My
> understanding is that if you create wlan and "ifconfig *wlan0* up", it
> works, but if you "ifconfig *run0* up", it causes panic. (Of cource
> without *. I'm trying to enphasize the point in plain text messeage.) That
> is what should happen. (Actually, result of "ifconfig *run0* up" is
> undefined.) "run0" should only be used when creating wlan.
>
> If "ifconfig *wlan0* ..." is causing problem, please let us know.
>

What is the backtrace of the panic?

--HPS

------------------------------

Message: 32
Date: Fri, 5 Mar 2010 09:50:04 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@FreeBSD.org
Message-ID: <201003050950....@freefall.freebsd.org>

The following reply was made to PR usb/144423; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: PseudoCylon <moonlig...@yahoo.ca>
Cc: bug-fo...@freebsd.org,
jha...@pangolin-systems.com,
freeb...@freebsd.org,
freebsd-gn...@freebsd.org
Subject: Re: usb/144423: if_run panic with USB-N13
Date: Fri, 5 Mar 2010 10:42:41 +0100

------------------------------

Message: 33
Date: Fri, 5 Mar 2010 09:50:05 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@FreeBSD.org
Message-ID: <201003050950....@freefall.freebsd.org>

The following reply was made to PR usb/144423; it has been noted by GNATS.

------------------------------

Message: 34
Date: Fri, 5 Mar 2010 10:54:18 +0100
From: Matthias Apitz <gu...@unixarea.de>
Subject: video cam with room view for FreeBSD && Skype
To: freebsd-...@freebsd.org
Cc: freeb...@freebsd.org
Message-ID: <2010030509...@current.Sisis.de>
Content-Type: text/plain; charset=iso-8859-1

Hello,

To do normal Skype session (face2face) I'm using a USB video cam mounted on top
of the lid of my laptop which is good supported by the pwc kernel module:

Mar 5 09:39:57 current kernel: ugen4.2: <Philips> at usbus4
Mar 5 09:39:57 current kernel: pwc0: <Philips product 0x0329, class 0/0, rev 1.10/0.03, addr 2> on usbus4
Mar 5 09:39:58 current kernel: pwc0: This camera is equipped with a Sony CCD sensor + TDA8787 (32)

I would like to have a bigger model to do the same with a group of
colleagues on my side, i.e. put the cam 3-4 meter away from the table.
Does someone knows a good model for doing that, wall or table mounted
and with a long USB cable, and supported in FreeBSD 8-CURRENT?

Thx

matthias

--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <gu...@unixarea.de> - w http://www.unixarea.de/
Solidarity with the imperialistic Israel? Not in my name!
�Solidaridad con el imperialismo de Israel? �No en mi nombre!

------------------------------

Message: 35
Date: Fri, 5 Mar 2010 10:00:17 GMT
From: PseudoCylon <moonlig...@yahoo.ca>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@FreeBSD.org
Message-ID: <201003051000....@freefall.freebsd.org>

The following reply was made to PR usb/144423; it has been noted by GNATS.

From: PseudoCylon <moonlig...@yahoo.ca>
To: bug-fo...@FreeBSD.org, jha...@pangolin-systems.com
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org,
Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/144423: if_run panic with USB-N13
Date: Fri, 5 Mar 2010 01:31:35 -0800 (PST)

>The files seem a little far from the current I am running, I just used=0A>=
the updates to the usbdevs file and the unlock-lock around the firmware loa=
d=0A>in if_run.c.=0AYes, there are some bits added to support RT3572 chipse=
ts. It would be greately appreciated if you try that file if it's not too m=
utch trouble.=0A=0A>The ASUS-N13 does work when a child wlan device is crea=
ted with it,=0A>but if just "ifconfig run0 up" is done there is a page faul=
t. I do=0A>not know if that is expected. This occurs with or without runfw.=
ko=0A>being loaded beforehand.=0AYes, "ifconfig run0 up" will cause page fa=
ult. The wlanN interface is should be created as an instance of the parent =
interface and used for actual communication. This is new feature to 8.0 and=
9-current. My understanding is that if you create wlan and "ifconfig *wlan=
0* up", it works, but if you "ifconfig *run0* up", it causes panic. (Of cou=
rce without *. I'm trying to enphasize the point in plain text messeage.) T=
hat is what should happen. (Actually, result of "ifconfig *run0* up" is und=
efined.) "run0" should only be used when creating wlan.=0A=0AIf "ifconfig *=
wlan0* ..." is causing problem, please let us know.=0A=0A=0A _________=
_________________________________________________________=0AThe new Interne=
t Explorer=AE 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now =
for Free! at http://downloads.yahoo.com/ca/internetexplorer/

------------------------------

Message: 36
Date: Fri, 5 Mar 2010 10:00:18 GMT
From: PseudoCylon <moonlig...@yahoo.ca>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@FreeBSD.org
Message-ID: <201003051000....@freefall.freebsd.org>

The following reply was made to PR usb/144423; it has been noted by GNATS.

------------------------------

Message: 37
Date: Fri, 5 Mar 2010 03:40:05 -0800 (PST)
From: PseudoCylon <moonlig...@yahoo.ca>
Subject: Re: usb/144423: if_run panic with USB-N13
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, jha...@pangolin-systems.com,
freeb...@freebsd.org, bug-fo...@freebsd.org
Message-ID: <164298....@web51805.mail.re2.yahoo.com>
Content-Type: text/plain; charset=us-ascii

----- Original Message ----

> From: Hans Petter Selasky <hsel...@c2i.net>
> To: PseudoCylon <moonlig...@yahoo.ca>
> Cc: bug-fo...@freebsd.org; jha...@pangolin-systems.com; freeb...@freebsd.org; freebsd-gn...@freebsd.org
> Sent: Fri, March 5, 2010 2:42:41 AM
> Subject: Re: usb/144423: if_run panic with USB-N13
>
> On Friday 05 March 2010 10:31:35 PseudoCylon wrote:
> > >The files seem a little far from the current I am running, I just used
> > >the updates to the usbdevs file and the unlock-lock around the firmware
> > > load in if_run.c.
> >
> > Yes, there are some bits added to support RT3572 chipsets. It would be
> > greately appreciated if you try that file if it's not too mutch trouble.
> >
> > >The ASUS-N13 does work when a child wlan device is created with it,
> > >but if just "ifconfig run0 up" is done there is a page fault. I do
> > >not know if that is expected. This occurs with or without runfw.ko
> > >being loaded beforehand.
> >
> > Yes, "ifconfig run0 up" will cause page fault. The wlanN interface is
> > should be created as an instance of the parent interface and used for
> > actual communication. This is new feature to 8.0 and 9-current. My
> > understanding is that if you create wlan and "ifconfig *wlan0* up", it
> > works, but if you "ifconfig *run0* up", it causes panic. (Of cource
> > without *. I'm trying to enphasize the point in plain text messeage.) That
> > is what should happen. (Actually, result of "ifconfig *run0* up" is
> > undefined.) "run0" should only be used when creating wlan.
> >
> > If "ifconfig *wlan0* ..." is causing problem, please let us know.
> >
>
> What is the backtrace of the panic?
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_witness_debugger() at _witness_debugger+0x2e
witness_warn() at witness_warn+0x2c2
trap() at trap+0x2f5
calltrap() at calltrap+0x8
--- trap 0xc, rip = 0xffffffff80c5cfd7, rsp = 0xffffff8021f76880, rbp = 0xffffff8021f768c0 ---
run_stop() at run_stop+0x67
run_init_locked() at run_init_locked+0x33
run_ioctl() at run_ioctl+0xad
ifioctl() at ifioctl+0xde4
kern_ioctl() at kern_ioctl+0xc5
ioctl() at ioctl+0xf0
syscall() at syscall+0x1af
Xfast_syscall() at Xfast_syscall+0xe1
--- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800b8286c, rsp = 0x7fffffffe2f8, rbp = 0x7fffffffe300 ---

There are number of places refers uninitialized value in run_stop() and run_init() if vap hasn't created, so it will cause page fault. I can move those instructions to other places (maybe vap_delete). It won't panic but device won't work without vap.

------------------------------

Message: 38
Date: Fri, 5 Mar 2010 11:50:02 GMT
From: PseudoCylon <moonlig...@yahoo.ca>
Subject: Re: usb/144423: if_run panic with USB-N13
To: freeb...@FreeBSD.org
Message-ID: <201003051150....@freefall.freebsd.org>

The following reply was made to PR usb/144423; it has been noted by GNATS.

From: PseudoCylon <moonlig...@yahoo.ca>
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: bug-fo...@freebsd.org, jha...@pangolin-systems.com,
freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/144423: if_run panic with USB-N13
Date: Fri, 5 Mar 2010 03:40:05 -0800 (PST)

----- Original Message ----

> From: Hans Petter Selasky <hsel...@c2i.net>
> To: PseudoCylon <moonlig...@yahoo.ca>
> Cc: bug-fo...@freebsd.org; jha...@pangolin-systems.com; freeb...@freebsd.org; freebsd-gn...@freebsd.org
> Sent: Fri, March 5, 2010 2:42:41 AM
> Subject: Re: usb/144423: if_run panic with USB-N13
>
> On Friday 05 March 2010 10:31:35 PseudoCylon wrote:
> > >The files seem a little far from the current I am running, I just used
> > >the updates to the usbdevs file and the unlock-lock around the firmware
> > > load in if_run.c.
> >
> > Yes, there are some bits added to support RT3572 chipsets. It would be
> > greately appreciated if you try that file if it's not too mutch trouble.
> >
> > >The ASUS-N13 does work when a child wlan device is created with it,
> > >but if just "ifconfig run0 up" is done there is a page fault. I do
> > >not know if that is expected. This occurs with or without runfw.ko
> > >being loaded beforehand.
> >
> > Yes, "ifconfig run0 up" will cause page fault. The wlanN interface is
> > should be created as an instance of the parent interface and used for
> > actual communication. This is new feature to 8.0 and 9-current. My
> > understanding is that if you create wlan and "ifconfig *wlan0* up", it
> > works, but if you "ifconfig *run0* up", it causes panic. (Of cource
> > without *. I'm trying to enphasize the point in plain text messeage.) That
> > is what should happen. (Actually, result of "ifconfig *run0* up" is
> > undefined.) "run0" should only be used when creating wlan.
> >
> > If "ifconfig *wlan0* ..." is causing problem, please let us know.
> >
>
> What is the backtrace of the panic?
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_witness_debugger() at _witness_debugger+0x2e
witness_warn() at witness_warn+0x2c2
trap() at trap+0x2f5
calltrap() at calltrap+0x8
--- trap 0xc, rip = 0xffffffff80c5cfd7, rsp = 0xffffff8021f76880, rbp = 0xffffff8021f768c0 ---
run_stop() at run_stop+0x67
run_init_locked() at run_init_locked+0x33
run_ioctl() at run_ioctl+0xad
ifioctl() at ifioctl+0xde4
kern_ioctl() at kern_ioctl+0xc5
ioctl() at ioctl+0xf0
syscall() at syscall+0x1af
Xfast_syscall() at Xfast_syscall+0xe1
--- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800b8286c, rsp = 0x7fffffffe2f8, rbp = 0x7fffffffe300 ---

There are number of places refers uninitialized value in run_stop() and run_init() if vap hasn't created, so it will cause page fault. I can move those instructions to other places (maybe vap_delete). It won't panic but device won't work without vap.

__________________________________________________________________
Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com

------------------------------

End of freebsd-usb Digest, Vol 278, Issue 2
*******************************************

0 new messages