Can't install 11 .iso images in virtual box

2015-12-29 Thread Yuri 

disk1.iso has kernel panic during boot.

And bootonly.iso boots but after downloading kernel and base it says 
that there is the incorrect checksum, and it needs to downlodagain.


Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso

Yuri
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Can't install 11 .iso images in virtual box

2015-12-29 Thread Matthias Apitz 

On Tuesday, 29 December 2015 17:01:28 CET, Glen Barber wrote:

On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:

disk1.iso has kernel panic during boot.

And bootonly.iso boots but after downloading kernel and base it says that
there is the incorrect checksum, and it needs to downlodagain.

Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso



This is because we can only store (currently) one version of the
distribution sets on FTP, and the most recent build (from last night) is
syncing to the mirrors currently.

What was the panic message for disc1.iso?  I do not recall seeing
a panic with that image when I tested the last set of builds.

Glen




I had the same problem yesterday and got a reply that this is a known bug, 
check the archive of the list:


matthias


--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Can't install 11 .iso images in virtual box

2015-12-29 Thread Allan Jude 
On 2015-12-29 11:01, Glen Barber wrote:
> On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:
>> disk1.iso has kernel panic during boot.
>>
>> And bootonly.iso boots but after downloading kernel and base it says that
>> there is the incorrect checksum, and it needs to downlodagain.
>>
>> Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso
>>
> 
> This is because we can only store (currently) one version of the
> distribution sets on FTP, and the most recent build (from last night) is
> syncing to the mirrors currently.
> 
> What was the panic message for disc1.iso?  I do not recall seeing
> a panic with that image when I tested the last set of builds.
> 
> Glen
> 

I believe the panic was the isofs lock order reversal. I and a number of
other people saw the same thing in another thread.

I think kib@ fixed it in r292772, once your new ISOs are out, I can confirm.

-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature

interrupt and resume poudriere jail creation

2015-12-29 Thread Matthias Apitz 

Hello,

I'm creating a new -CURRENT jail for poudriere with:

# poudriere jail -c -j freebsd-r292778 -m svn+http -v head@r292778

The src/ is checked out via SVN and it is already compiling the jail
for two hours, but I have to interrupt it for some network problem here
and I did the mistake to start it in a SSH session :-(

Is there a way like -DNO_CLEAN when compiling 'make buildkernel' to
resume the compilation in the jail at the point of the interrupt?

Thanks

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Can't install 11 .iso images in virtual box

2015-12-29 Thread Glen Barber 
On Tue, Dec 29, 2015 at 05:16:40PM +0100, Matthias Apitz wrote:
> On Tuesday, 29 December 2015 17:01:28 CET, Glen Barber wrote:
> >On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:
> >>disk1.iso has kernel panic during boot.
> >>
> >>And bootonly.iso boots but after downloading kernel and base it says that
> >>there is the incorrect checksum, and it needs to downlodagain.
> >>
> >>Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso
> >>
> >
> >This is because we can only store (currently) one version of the
> >distribution sets on FTP, and the most recent build (from last night) is
> >syncing to the mirrors currently.
> >
> >What was the panic message for disc1.iso?  I do not recall seeing
> >a panic with that image when I tested the last set of builds.
> >
> >Glen
> >
> >
> 
> I had the same problem yesterday and got a reply that this is a known bug,
> check the archive of the list:
> 

Ah, thanks.  I missed that thread (and now not sure how I did not hit
this).  Thanks.

The good news - new images are syncing to the mirrors now, and will be
available soon.

Glen



signature.asc
Description: PGP signature

Re: D-link wireless not detected

2015-12-29 Thread Adrian Chadd 
I'll go order one and take a crack at it soon.

(I saw this when looking at the r92su and realtek linux drivers - they
do a whole bunch of extra endpoint gymnastics that we don't..)


-a


On 29 December 2015 at 06:19, Kevin Lo  wrote:
> On Tue, Dec 29, 2015 at 03:02:35PM +0100, Hans Petter Selasky wrote:
>> On 12/29/15 14:00, Daniel Braniss wrote:
>> >
>> >> On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:
>> >>
>> >> On 12/29/15 13:36, Daniel Braniss wrote:
>> >>>
>> >>
>> >> Until /etc/devd/usb.conf is regenerated, you'll need to manually load the 
>> >> kernel module for urtwn. Did you do that?
>> >>
>> >> --HPS
>> >>
>> > ok, set if_urtwn_load=yes
>> > and now I get:
>> >
>> > ugen0.4:  at usbus0
>> > urtwn0:  on usbus0
>> > urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
>> > Fatal kernel mode data abort: 'Translation Fault (L1)' on write
>> > trapframe: 0xda29fb88
>> > FSR=0805, FAR=, spsr=6013
>> > r0 =, r1 =, r2 =c0a72cb0, r3 =0165
>> > r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
>> > r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
>> > r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc
>> >
>> > [ thread pid 13 tid 100045 ]
>> > Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
>> > db>
>> >
>> > btw, as long as you are willing to help, I will keep testing,
>> > in other words, i’m ok.
>>
>> Hi Andriy,
>>
>> Can you fix the crash above and verify this error patch?
>>
>> Andriy:
>>
>> After:
>>  usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
>> There is no need for:
>>   usbd_transfer_drain(sc->sc_xfer[x]);
>
> As I mentioned previously we don't support rtl8192eu.  One difference
> between those is the the number of endpoints and its addresses.
>
>> --HPS
> ___
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Can't install 11 .iso images in virtual box

2015-12-29 Thread Glen Barber 
On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:
> disk1.iso has kernel panic during boot.
> 
> And bootonly.iso boots but after downloading kernel and base it says that
> there is the incorrect checksum, and it needs to downlodagain.
> 
> Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso
> 

This is because we can only store (currently) one version of the
distribution sets on FTP, and the most recent build (from last night) is
syncing to the mirrors currently.

What was the panic message for disc1.iso?  I do not recall seeing
a panic with that image when I tested the last set of builds.

Glen



signature.asc
Description: PGP signature

Re: clang/3.7.1/include/ does not exist?

2015-12-29 Thread NGie Cooper 

> On Dec 29, 2015, at 14:12, Roger Marquis  wrote:
> 
>> I don't use cleanworld. That might be a part of the problem. Is /usr/obj on
>> tmpfs?
> 
> Haven't tried /usr/obj on tmpfs (yet), just ufs and zfs.

Ok — this helps a lot. I’ll look at cleanworld — see if there’s anything 
missing there.
Thanks!
-NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

UEFI Memstick Not Booting on a Thinkpad X1 Carbon

2015-12-29 Thread Atomic Beef 
Hello,

Over the past few days I have been trying to install FreeBSD 11-CURRENT
with full disk encryption on my laptop and finally got it installed
yesterday, albeit without any encryption.

The problem that I was running into was that even though the installer on
the USB booted fine and installed the system, my laptop would fail to boot
the brand new installation. I managed to "fix" this by inserting the USB
with a 10.2-RELEASE installer on it. For some reason my system started to
boot just fine after that.

Once I had tested that everything worked on my laptop, I used dd to get the
11-CURRENT snapshot back on my USB, but I found that it would refuse to
boot. The 10.2-RELEASE image doesn't work either.

When I asked the forums about this issue, they said that it could be a
problem with the UEFI on my laptop and that a workaround might have to be
created.

Thanks,

Ted
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: clang/3.7.1/include/ does not exist?

2015-12-29 Thread NGie Cooper 

> On Dec 29, 2015, at 06:16, Jeffrey Bouquet  wrote:
> 
> On Mon, 28 Dec 2015 18:39:59 -0800 (PST), Roger Marquis  
> wrote:

…

> ..
> Not to divert the question and answer, but I recently posted and would like 
> to restate that
> it would be useful for a wrapper for installworld after buildworld so that 
> each command in
> installworld can complete successfully since the buildworld did if that 
> would
> be easy to do,  BEFORE the actual installworld begins...   [not to mention 
> its inclusion at
> the bottom of UPDATING in one or more of the methodologies ... eventually... ]
> 
>  I've been tripped up many times lately, sometimes in a all-day-rollback 
> fashion, by
> the installworld not completing where the buildworld did.
> 
>  Seems it would be useful for production machines also... 

This is one of the areas where snapshotting with filesystems would definitely 
come in handy, e.g. ZFS (snapshot before installworld, rollback if installworld 
fails).
Cheers,
-NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Stack backtrace on `zpool export`

2015-12-29 Thread Florian Ermisch 
Hi *,

since I've upgraded my laptop from 10.2-RELEASE to 11-CURRENT (r292536, now 
r292755) I see this stack backtrace when a zpool is exported:

Dec 27 18:44:02 fuchi-cyber220 kernel: lock order reversal:
Dec 27 18:44:02 fuchi-cyber220 kernel: 1st 0xf800c7472418 zfs (zfs) @ 
/usr/src/sys/kern/vfs_mount.c:1224
Dec 27 18:44:02 fuchi-cyber220 kernel: 2nd 0xf800c73fad50 zfs_gfs (zfs_gfs) 
@ /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/gfs.c:494
Dec 27 18:44:02 fuchi-cyber220 kernel: stack backtrace:
Dec 27 18:44:02 fuchi-cyber220 kernel: #0 0x80a7d6f0 at 
witness_debugger+0x70
Dec 27 18:44:02 fuchi-cyber220 kernel: #1 0x80a7d5f1 at 
witness_checkorder+0xe71
Dec 27 18:44:02 fuchi-cyber220 kernel: #2 0x809fedcb at 
__lockmgr_args+0xd3b
Dec 27 18:44:02 fuchi-cyber220 kernel: #3 0x80ac55ec at vop_stdlock+0x3c
Dec 27 18:44:02 fuchi-cyber220 kernel: #4 0x80fbb220 at 
VOP_LOCK1_APV+0x100
Dec 27 18:44:02 fuchi-cyber220 kernel: #5 0x80ae653a at _vn_lock+0x9a
Dec 27 18:44:02 fuchi-cyber220 kernel: #6 0x8209db13 at 
gfs_file_create+0x73
Dec 27 18:44:02 fuchi-cyber220 kernel: #7 0x8209dbbd at 
gfs_dir_create+0x1d
Dec 27 18:44:02 fuchi-cyber220 kernel: #8 0x821649e7 at 
zfsctl_mknode_snapdir+0x47
Dec 27 18:44:02 fuchi-cyber220 kernel: #9 0x8209e135 at 
gfs_dir_lookup+0x185
Dec 27 18:44:02 fuchi-cyber220 kernel: #10 0x8209e61d at 
gfs_vop_lookup+0x1d
Dec 27 18:44:02 fuchi-cyber220 kernel: #11 0x82163a05 at 
zfsctl_root_lookup+0xf5
Dec 27 18:44:02 fuchi-cyber220 kernel: #12 0x821648a3 at 
zfsctl_umount_snapshots+0x83
Dec 27 18:44:02 fuchi-cyber220 kernel: #13 0x8217d5ab at zfs_umount+0x7b
Dec 27 18:44:02 fuchi-cyber220 kernel: #14 0x80acf0b0 at dounmount+0x530
Dec 27 18:44:02 fuchi-cyber220 kernel: #15 0x80aceaed at 
sys_unmount+0x35d
Dec 27 18:44:02 fuchi-cyber220 kernel: #16 0x80e6e13b at 
amd64_syscall+0x2db
Dec 27 18:44:02 fuchi-cyber220 kernel: #17 0x80e4dd8b at 
Xfast_syscall+0xfb

(From /var/log/messages)

First I've only seen this on the console at shutdown or reboot (after sync I 
think) but later found I can reproduce it by exporting a zpool.
While the only pools I can trigger this without a shutdown/reboot are connected 
via USB(3) I still see it just before poweroff at shutdown when the system's 
root pool is synced.

When I try to export a zpool under heavy load (`make -C /use/src -j 4 
buildworld` on a 2 core CPU w/ HT) the system locks up completely. I don't 
think it's related to memory pressure as I haven't seen swap being used during 
a buildworld (with 8 gigs of RAM).

Has anyone else seen this?

Regards, Florian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Stack backtrace on `zpool export`

2015-12-29 Thread NGie Cooper 

> On Dec 29, 2015, at 11:48, Florian Ermisch <0xf...@fsfe.org> wrote:
> 
> Hi *,
> 
> since I've upgraded my laptop from 10.2-RELEASE to 11-CURRENT (r292536, now 
> r292755) I see this stack backtrace when a zpool is exported:
> 
> Dec 27 18:44:02 fuchi-cyber220 kernel: lock order reversal:
> Dec 27 18:44:02 fuchi-cyber220 kernel: 1st 0xf800c7472418 zfs (zfs) @ 
> /usr/src/sys/kern/vfs_mount.c:1224
> Dec 27 18:44:02 fuchi-cyber220 kernel: 2nd 0xf800c73fad50 zfs_gfs 
> (zfs_gfs) @ /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/gfs.c:494
> Dec 27 18:44:02 fuchi-cyber220 kernel: stack backtrace:
> Dec 27 18:44:02 fuchi-cyber220 kernel: #0 0x80a7d6f0 at 
> witness_debugger+0x70
> Dec 27 18:44:02 fuchi-cyber220 kernel: #1 0x80a7d5f1 at 
> witness_checkorder+0xe71
> Dec 27 18:44:02 fuchi-cyber220 kernel: #2 0x809fedcb at 
> __lockmgr_args+0xd3b
> Dec 27 18:44:02 fuchi-cyber220 kernel: #3 0x80ac55ec at 
> vop_stdlock+0x3c
> Dec 27 18:44:02 fuchi-cyber220 kernel: #4 0x80fbb220 at 
> VOP_LOCK1_APV+0x100
> Dec 27 18:44:02 fuchi-cyber220 kernel: #5 0x80ae653a at _vn_lock+0x9a
> Dec 27 18:44:02 fuchi-cyber220 kernel: #6 0x8209db13 at 
> gfs_file_create+0x73
> Dec 27 18:44:02 fuchi-cyber220 kernel: #7 0x8209dbbd at 
> gfs_dir_create+0x1d
> Dec 27 18:44:02 fuchi-cyber220 kernel: #8 0x821649e7 at 
> zfsctl_mknode_snapdir+0x47
> Dec 27 18:44:02 fuchi-cyber220 kernel: #9 0x8209e135 at 
> gfs_dir_lookup+0x185
> Dec 27 18:44:02 fuchi-cyber220 kernel: #10 0x8209e61d at 
> gfs_vop_lookup+0x1d
> Dec 27 18:44:02 fuchi-cyber220 kernel: #11 0x82163a05 at 
> zfsctl_root_lookup+0xf5
> Dec 27 18:44:02 fuchi-cyber220 kernel: #12 0x821648a3 at 
> zfsctl_umount_snapshots+0x83
> Dec 27 18:44:02 fuchi-cyber220 kernel: #13 0x8217d5ab at 
> zfs_umount+0x7b
> Dec 27 18:44:02 fuchi-cyber220 kernel: #14 0x80acf0b0 at 
> dounmount+0x530
> Dec 27 18:44:02 fuchi-cyber220 kernel: #15 0x80aceaed at 
> sys_unmount+0x35d
> Dec 27 18:44:02 fuchi-cyber220 kernel: #16 0x80e6e13b at 
> amd64_syscall+0x2db
> Dec 27 18:44:02 fuchi-cyber220 kernel: #17 0x80e4dd8b at 
> Xfast_syscall+0xfb
> 
> (From /var/log/messages)
> 
> First I've only seen this on the console at shutdown or reboot (after sync I 
> think) but later found I can reproduce it by exporting a zpool.
> While the only pools I can trigger this without a shutdown/reboot are 
> connected via USB(3) I still see it just before poweroff at shutdown when the 
> system's root pool is synced.
> 
> When I try to export a zpool under heavy load (`make -C /use/src -j 4 
> buildworld` on a 2 core CPU w/ HT) the system locks up completely. I don't 
> think it's related to memory pressure as I haven't seen swap being used 
> during a buildworld (with 8 gigs of RAM).
> 
> Has anyone else seen this?

Please file a bug for this issue and assign it to freebsd-fs. It doesn’t look 
familiar (there might be a lock ordering issue with either zfs or vfs+zfs).
Thanks!
-NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: clang/3.7.1/include/ does not exist?

2015-12-29 Thread Roger Marquis 
NGie Cooper wrote:
>   How are you executing buildworld? What?s your revision?

In the latest iteration:

 uname -a
   ... 11.0-CURRENT FreeBSD 11.0-CURRENT #0: Thu Dec 17 18:26:58 PST 2015
...:/usr/obj/usr/src/sys/GENERIC amd64
 cd /usr/src
 rm -rf * .s* .a* ../obj/*
 svnlite co https://svn.freebsd.org/base/head ./
  Checked out revision 292870.
 make cleanworld
 make buildworld -DNO_GAMES

Had been seeing the same results on multiple systems, with a couple of
yesterday's and several previous revisions, but as of 292873 it does build
again.

Thanks,
Roger


> To: Roger Marquis 
> Cc: freebsd-current@freebsd.org
> Subject: Re: clang/3.7.1/include/ does not exist?
> Message-ID: 
> Content-Type: text/plain; charset=utf-8
>
>
>> On Dec 28, 2015, at 18:39, Roger Marquis  wrote:
>>
>> Anyone else seeing these buildworld errors?
>
> ...
>
>>  /usr/obj/usr/src/tmp/usr/lib/clang/3.7.1/include/
>>  install: target directory
`/usr/obj/usr/src/tmp/usr/lib/clang/3.7.1/include/' does not exist
>>  usage: install [-bCcpSsUv] [-f flags] [-g group] [-m mode] [-o owner]
>> [-M log] [-D dest] [-h hash] [-T tags]
>> [-B suffix] [-l linkflags] [-N dbdir]
>> file1 file2
>> install [-bCcpSsUv] [-f flags] [-g group] [-m mode] [-o owner]
>> [-M log] [-D dest] [-h hash] [-T tags]
>> [-B suffix] [-l linkflags] [-N dbdir]
>> file1 ... fileN directory
>> install -dU [-vU] [-g group] [-m mode] [-N dbdir] [-o owner]
>> [-M log] [-D dest] [-h hash] [-T tags]
>> directory ...
>>  *** Error code 64
>>  Stop.
>>  make[4]: stopped in /usr/src/lib/clang/include
>>  *** Error code 1


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: clang/3.7.1/include/ does not exist?

2015-12-29 Thread Garrett Cooper 

> On Dec 29, 2015, at 13:20, Roger Marquis  wrote:
> 
> NGie Cooper wrote:
>>How are you executing buildworld? What?s your revision?
> 
> In the latest iteration:
> 
> uname -a
>   ... 11.0-CURRENT FreeBSD 11.0-CURRENT #0: Thu Dec 17 18:26:58 PST 2015
> ...:/usr/obj/usr/src/sys/GENERIC amd64
> cd /usr/src
> rm -rf * .s* .a* ../obj/*
> svnlite co https://svn.freebsd.org/base/head ./
>  Checked out revision 292870.
> make cleanworld
> make buildworld -DNO_GAMES
> 
> Had been seeing the same results on multiple systems, with a couple of
> yesterday's and several previous revisions, but as of 292873 it does build
> again.

I don't use cleanworld. That might be a part of the problem. Is /usr/obj on 
tmpfs?
Thanks!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Stack backtrace on `zpool export`

2015-12-29 Thread Alan Somers 
On Tue, Dec 29, 2015 at 12:54 PM, NGie Cooper  wrote:
>
>> On Dec 29, 2015, at 11:48, Florian Ermisch <0xf...@fsfe.org> wrote:
>>
>> Hi *,
>>
>> since I've upgraded my laptop from 10.2-RELEASE to 11-CURRENT (r292536, now 
>> r292755) I see this stack backtrace when a zpool is exported:
>>
>> Dec 27 18:44:02 fuchi-cyber220 kernel: lock order reversal:
>> Dec 27 18:44:02 fuchi-cyber220 kernel: 1st 0xf800c7472418 zfs (zfs) @ 
>> /usr/src/sys/kern/vfs_mount.c:1224
>> Dec 27 18:44:02 fuchi-cyber220 kernel: 2nd 0xf800c73fad50 zfs_gfs 
>> (zfs_gfs) @ /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/gfs.c:494
>> Dec 27 18:44:02 fuchi-cyber220 kernel: stack backtrace:
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #0 0x80a7d6f0 at 
>> witness_debugger+0x70
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #1 0x80a7d5f1 at 
>> witness_checkorder+0xe71
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #2 0x809fedcb at 
>> __lockmgr_args+0xd3b
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #3 0x80ac55ec at 
>> vop_stdlock+0x3c
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #4 0x80fbb220 at 
>> VOP_LOCK1_APV+0x100
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #5 0x80ae653a at _vn_lock+0x9a
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #6 0x8209db13 at 
>> gfs_file_create+0x73
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #7 0x8209dbbd at 
>> gfs_dir_create+0x1d
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #8 0x821649e7 at 
>> zfsctl_mknode_snapdir+0x47
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #9 0x8209e135 at 
>> gfs_dir_lookup+0x185
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #10 0x8209e61d at 
>> gfs_vop_lookup+0x1d
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #11 0x82163a05 at 
>> zfsctl_root_lookup+0xf5
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #12 0x821648a3 at 
>> zfsctl_umount_snapshots+0x83
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #13 0x8217d5ab at 
>> zfs_umount+0x7b
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #14 0x80acf0b0 at 
>> dounmount+0x530
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #15 0x80aceaed at 
>> sys_unmount+0x35d
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #16 0x80e6e13b at 
>> amd64_syscall+0x2db
>> Dec 27 18:44:02 fuchi-cyber220 kernel: #17 0x80e4dd8b at 
>> Xfast_syscall+0xfb
>>
>> (From /var/log/messages)
>>
>> First I've only seen this on the console at shutdown or reboot (after sync I 
>> think) but later found I can reproduce it by exporting a zpool.
>> While the only pools I can trigger this without a shutdown/reboot are 
>> connected via USB(3) I still see it just before poweroff at shutdown when 
>> the system's root pool is synced.
>>
>> When I try to export a zpool under heavy load (`make -C /use/src -j 4 
>> buildworld` on a 2 core CPU w/ HT) the system locks up completely. I don't 
>> think it's related to memory pressure as I haven't seen swap being used 
>> during a buildworld (with 8 gigs of RAM).
>>
>> Has anyone else seen this?
>
> Please file a bug for this issue and assign it to freebsd-fs. It doesn’t look 
> familiar (there might be a lock ordering issue with either zfs or vfs+zfs).
> Thanks!
> -NGie

Adding Will@.  I think he was working on this LOR at one point.
-Alan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: clang/3.7.1/include/ does not exist?

2015-12-29 Thread Roger Marquis 
> I don't use cleanworld. That might be a part of the problem. Is /usr/obj on
> tmpfs?

Haven't tried /usr/obj on tmpfs (yet), just ufs and zfs.

Roger

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Daniel Braniss 

> On 29 Dec 2015, at 19:42, Adrian Chadd  wrote:
> 
> I'll go order one and take a crack at it soon.
> 
> (I saw this when looking at the r92su and realtek linux drivers - they
> do a whole bunch of extra endpoint gymnastics that we don't..)

great, let me know, and I can help out debugging.

danny

> 
> 
> -a
> 
> 
> On 29 December 2015 at 06:19, Kevin Lo  wrote:
>> On Tue, Dec 29, 2015 at 03:02:35PM +0100, Hans Petter Selasky wrote:
>>> On 12/29/15 14:00, Daniel Braniss wrote:
 
> On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:
> 
> On 12/29/15 13:36, Daniel Braniss wrote:
>> 
> 
> Until /etc/devd/usb.conf is regenerated, you'll need to manually load the 
> kernel module for urtwn. Did you do that?
> 
> --HPS
> 
 ok, set if_urtwn_load=yes
 and now I get:
 
 ugen0.4:  at usbus0
 urtwn0:  on usbus0
 urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
 Fatal kernel mode data abort: 'Translation Fault (L1)' on write
 trapframe: 0xda29fb88
 FSR=0805, FAR=, spsr=6013
 r0 =, r1 =, r2 =c0a72cb0, r3 =0165
 r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
 r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
 r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc
 
 [ thread pid 13 tid 100045 ]
 Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
 db>
 
 btw, as long as you are willing to help, I will keep testing,
 in other words, i’m ok.
>>> 
>>> Hi Andriy,
>>> 
>>> Can you fix the crash above and verify this error patch?
>>> 
>>> Andriy:
>>> 
>>> After:
>>> usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
>>> There is no need for:
>>>  usbd_transfer_drain(sc->sc_xfer[x]);
>> 
>> As I mentioned previously we don't support rtl8192eu.  One difference
>> between those is the the number of endpoints and its addresses.
>> 
>>> --HPS
>> ___
>> freebsd-...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
> ___
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

D-link wireless not detected

2015-12-29 Thread Daniel Braniss 
Hi All,
I have a working tp-link usb (realtek), but can’t get a d-link(also realtek) to 
work.
usbconfig:
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON (500mA)
This is on a raspberry pi running a resent current.

cheers & season greetings,
danny

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Vladimir Botka 
Hi Danny,

On Tue, 29 Dec 2015 11:16:27 +0200
Daniel Braniss  wrote:
> Hi All,
> I have a working tp-link usb (realtek), but can’t get a d-link(also realtek) 
> to work.
> usbconfig:
>   ugen0.4:  at usbus0, cfg=0 md=HOST 
> spd=HIGH (480Mbps) pwr=ON (500mA)
> This is on a raspberry pi running a resent current.
> cheers & season greetings,
>   danny

I've added freebsd-wireless list.

My 2 cents. It might be helpful to see more details about the adapters.
For example:

# usbconfig -u 0 -a 7 dump_device_desc
ugen0.7: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (450mA)
  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x  
  bDeviceSubClass = 0x 
  bDeviceProtocol = 0x 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x148f 
  idProduct = 0x5370 
  bcdDevice = 0x0101 
  iManufacturer = 0x0001  
  iProduct = 0x0002  <802.11 n WLAN>
  iSerialNumber = 0x0003  <1.0>
  bNumConfigurations = 0x0001


Cheers,

-vlado


pgpi69Vd_Tcp6.pgp
Description: OpenPGP digital signature

Re: D-link wireless not detected

2015-12-29 Thread Daniel Braniss 

> On 29 Dec 2015, at 11:33, Vladimir Botka  wrote:
> 
> Hi Danny,
> 
> On Tue, 29 Dec 2015 11:16:27 +0200
> Daniel Braniss  wrote:
>> Hi All,
>> I have a working tp-link usb (realtek), but can’t get a d-link(also realtek) 
>> to work.
>> usbconfig:
>>  ugen0.4:  at usbus0, cfg=0 md=HOST 
>> spd=HIGH (480Mbps) pwr=ON (500mA)
>> This is on a raspberry pi running a resent current.
>> cheers & season greetings,
>>  danny
> 
> I've added freebsd-wireless list.
> 
> My 2 cents. It might be helpful to see more details about the adapters.
> For example:
> 
> # usbconfig -u 0 -a 7 dump_device_desc
> ugen0.7: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (450mA)
>  bLength = 0x0012 
>  bDescriptorType = 0x0001 
>  bcdUSB = 0x0200 
>  bDeviceClass = 0x  
>  bDeviceSubClass = 0x 
>  bDeviceProtocol = 0x 
>  bMaxPacketSize0 = 0x0040 
>  idVendor = 0x148f 
>  idProduct = 0x5370 
>  bcdDevice = 0x0101 
>  iManufacturer = 0x0001  
>  iProduct = 0x0002  <802.11 n WLAN>
>  iSerialNumber = 0x0003  <1.0>
>  bNumConfigurations = 0x0001


so here it is:
root@:~ # usbconfig -u 0 -a 4 dump_device_desc
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON (500mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0210 
  bDeviceClass = 0x  
  bDeviceSubClass = 0x 
  bDeviceProtocol = 0x 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x2001 
  idProduct = 0x3319 
  bcdDevice = 0x0200 
  iManufacturer = 0x0001  
  iProduct = 0x0002  
  iSerialNumber = 0x0003  <00e04c01>
  bNumConfigurations = 0x0001 

thanks,
danny

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Hans Petter Selasky 

On 12/29/15 10:42, Daniel Braniss wrote:



On 29 Dec 2015, at 11:33, Vladimir Botka  wrote:

Hi Danny,

On Tue, 29 Dec 2015 11:16:27 +0200
Daniel Braniss  wrote:

Hi All,
I have a working tp-link usb (realtek), but can’t get a d-link(also realtek) to 
work.
usbconfig:
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON (500mA)
This is on a raspberry pi running a resent current.
cheers & season greetings,
danny


I've added freebsd-wireless list.

My 2 cents. It might be helpful to see more details about the adapters.
For example:

# usbconfig -u 0 -a 7 dump_device_desc
ugen0.7: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (450mA)
  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0040
  idVendor = 0x148f
  idProduct = 0x5370
  bcdDevice = 0x0101
  iManufacturer = 0x0001  
  iProduct = 0x0002  <802.11 n WLAN>
  iSerialNumber = 0x0003  <1.0>
  bNumConfigurations = 0x0001



so here it is:
root@:~ # usbconfig -u 0 -a 4 dump_device_desc
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON (500mA)

   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0210
   bDeviceClass = 0x  
   bDeviceSubClass = 0x
   bDeviceProtocol = 0x
   bMaxPacketSize0 = 0x0040
   idVendor = 0x2001
   idProduct = 0x3319
   bcdDevice = 0x0200
   iManufacturer = 0x0001  
   iProduct = 0x0002  
   iSerialNumber = 0x0003  <00e04c01>
   bNumConfigurations = 0x0001

thanks,
danny



Did you google the idVendor and idProduct values and see if Linux has a 
driver already?


--HPS

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Daniel Braniss 

> On 29 Dec 2015, at 12:20, Hans Petter Selasky  wrote:
> 
> On 12/29/15 11:12, Daniel Braniss wrote:
>> 
>> https://github.com/Mange/rtl8192eu-linux-driver/blob/master/os_dep/linux/usb_intf.c
>>   
>> 
>> and look at line 216
>> 
>> danny
> 
> Hi,
> 
> You should be able to get this device working by adding a device entry to:
> 
> src/sys/dev/usb/wlan/if_urtwn.c
> 
> Can you make a patch and PR for this, and I'll submit upstream. I recommend 
> you test using an 11-current kernel.
> 
> --HPS

clearly, I’m missing something, because it’s not working :-(
the only visible change is now
ugen0.4: <802.11n WLAN Adapter RealtekWireless N Nano USB A> at usbus0, cfg=0 
md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
before it was
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON (500mA)

rnd> svn diff
Index: usbdevs
===
--- usbdevs (revision 291745)
+++ usbdevs (working copy)
@@ -1657,6 +1657,7 @@
 product DLINK2 RTL8192SU_1 0x3300  RTL8192SU
 product DLINK2 RTL8192SU_2 0x3302  RTL8192SU
 product DLINK2 DWA131A10x3303  DWA-131 A1
+product DLINK  DWA131  0x3319  DWA-131
 product DLINK2 DWA160A20x3a09  DWA-160 A2
 product DLINK2 DWA120  0x3a0c  DWA-120
 product DLINK2 DWA120_NF   0x3a0d  DWA-120 (no firmware)
Index: wlan/if_urtwn.c
===
--- wlan/if_urtwn.c (revision 291745)
+++ wlan/if_urtwn.c (working copy)
@@ -116,6 +116,7 @@
URTWN_DEV(DLINK,RTL8192CU_2),
URTWN_DEV(DLINK,RTL8192CU_3),
URTWN_DEV(DLINK,DWA131B),
+   URTWN_DEV(DLINK,DWA131), // danny
URTWN_DEV(EDIMAX,   EW7811UN),
URTWN_DEV(EDIMAX,   RTL8192CU),
URTWN_DEV(FEIXUN,   RTL8188CU),

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Kubilay Kocak 
On 30/12/2015 1:07 AM, Hans Petter Selasky wrote:
> On 12/29/15 15:02, Hans Petter Selasky wrote:
>> On 12/29/15 14:00, Daniel Braniss wrote:
>>>
 On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:

 On 12/29/15 13:36, Daniel Braniss wrote:
>

 Until /etc/devd/usb.conf is regenerated, you'll need to manually load
 the kernel module for urtwn. Did you do that?

 --HPS

>>> ok, set if_urtwn_load=yes
>>> and now I get:
>>>
>>> ugen0.4:  at usbus0
>>> urtwn0:  on usbus0
>>> urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
>>> Fatal kernel mode data abort: 'Translation Fault (L1)' on write
>>> trapframe: 0xda29fb88
>>> FSR=0805, FAR=, spsr=6013
>>> r0 =, r1 =, r2 =c0a72cb0, r3 =0165
>>> r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
>>> r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
>>> r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc
>>>
>>> [ thread pid 13 tid 100045 ]
>>> Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
>>> db>
>>>
>>> btw, as long as you are willing to help, I will keep testing,
>>> in other words, i’m ok.
>>
>> Hi Andriy,
>>
>> Can you fix the crash above and verify this error patch?
>>
> 
> Hi,
> 
> I see 11-current has a fix. Maybe MFC that to 10-stable?

Is there a Bugzilla issue ID for it?

>> Andriy:
>>
>> After:
>>  usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
>> There is no need for:
>>  usbd_transfer_drain(sc->sc_xfer[x]);
> 
> --HPS
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Hans Petter Selasky 

On 12/29/15 14:00, Daniel Braniss wrote:



On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:

On 12/29/15 13:36, Daniel Braniss wrote:




Until /etc/devd/usb.conf is regenerated, you'll need to manually load the 
kernel module for urtwn. Did you do that?

--HPS


ok, set if_urtwn_load=yes
and now I get:

ugen0.4:  at usbus0
urtwn0:  on usbus0
urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
Fatal kernel mode data abort: 'Translation Fault (L1)' on write
trapframe: 0xda29fb88
FSR=0805, FAR=, spsr=6013
r0 =, r1 =, r2 =c0a72cb0, r3 =0165
r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc

[ thread pid 13 tid 100045 ]
Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
db>

btw, as long as you are willing to help, I will keep testing,
in other words, i’m ok.


Hi Andriy,

Can you fix the crash above and verify this error patch?

Andriy:

After:
usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
There is no need for:
usbd_transfer_drain(sc->sc_xfer[x]);

--HPS

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Daniel Braniss 

> On 29 Dec 2015, at 11:53, Hans Petter Selasky  wrote:
> 
> On 12/29/15 10:42, Daniel Braniss wrote:
>> 
>>> On 29 Dec 2015, at 11:33, Vladimir Botka  wrote:
>>> 
>>> Hi Danny,
>>> 
>>> On Tue, 29 Dec 2015 11:16:27 +0200
>>> Daniel Braniss  wrote:
 Hi All,
 I have a working tp-link usb (realtek), but can’t get a d-link(also 
 realtek) to work.
 usbconfig:
ugen0.4:  at usbus0, cfg=0 md=HOST 
 spd=HIGH (480Mbps) pwr=ON (500mA)
 This is on a raspberry pi running a resent current.
 cheers & season greetings,
danny
>>> 
>>> I've added freebsd-wireless list.
>>> 
>>> My 2 cents. It might be helpful to see more details about the adapters.
>>> For example:
>>> 
>>> # usbconfig -u 0 -a 7 dump_device_desc
>>> ugen0.7: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=HIGH
>>> (480Mbps) pwr=ON (450mA)
>>>  bLength = 0x0012
>>>  bDescriptorType = 0x0001
>>>  bcdUSB = 0x0200
>>>  bDeviceClass = 0x  
>>>  bDeviceSubClass = 0x
>>>  bDeviceProtocol = 0x
>>>  bMaxPacketSize0 = 0x0040
>>>  idVendor = 0x148f
>>>  idProduct = 0x5370
>>>  bcdDevice = 0x0101
>>>  iManufacturer = 0x0001  
>>>  iProduct = 0x0002  <802.11 n WLAN>
>>>  iSerialNumber = 0x0003  <1.0>
>>>  bNumConfigurations = 0x0001
>> 
>> 
>> so here it is:
>> root@:~ # usbconfig -u 0 -a 4 dump_device_desc
>> ugen0.4:  at usbus0, cfg=0 md=HOST 
>> spd=HIGH (480Mbps) pwr=ON (500mA)
>> 
>>   bLength = 0x0012
>>   bDescriptorType = 0x0001
>>   bcdUSB = 0x0210
>>   bDeviceClass = 0x  
>>   bDeviceSubClass = 0x
>>   bDeviceProtocol = 0x
>>   bMaxPacketSize0 = 0x0040
>>   idVendor = 0x2001
>>   idProduct = 0x3319
>>   bcdDevice = 0x0200
>>   iManufacturer = 0x0001  
>>   iProduct = 0x0002  
>>   iSerialNumber = 0x0003  <00e04c01>
>>   bNumConfigurations = 0x0001
>> 
>> thanks,
>>  danny
>> 
> 
> Did you google the idVendor and idProduct values and see if Linux has a 
> driver already?
> 
> —HPS
> 


https://github.com/Mange/rtl8192eu-linux-driver/blob/master/os_dep/linux/usb_intf.c
 

and look at line 216

danny


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Daniel Braniss 

> On 29 Dec 2015, at 14:31, Hans Petter Selasky  wrote:
> 
> On 12/29/15 13:26, Daniel Braniss wrote:
>> 
>>> On 29 Dec 2015, at 12:20, Hans Petter Selasky  wrote:
>>> 
>>> On 12/29/15 11:12, Daniel Braniss wrote:
 
 https://github.com/Mange/rtl8192eu-linux-driver/blob/master/os_dep/linux/usb_intf.c
   
 
 and look at line 216
 
 danny
>>> 
>>> Hi,
>>> 
>>> You should be able to get this device working by adding a device entry to:
>>> 
>>> src/sys/dev/usb/wlan/if_urtwn.c
>>> 
>>> Can you make a patch and PR for this, and I'll submit upstream. I recommend 
>>> you test using an 11-current kernel.
>>> 
>>> --HPS
>> 
>> clearly, I’m missing something, because it’s not working :-(
>> the only visible change is now
>> ugen0.4: <802.11n WLAN Adapter RealtekWireless N Nano USB A> at usbus0, 
>> cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
>> before it was
>> ugen0.4:  at usbus0, cfg=0 md=HOST 
>> spd=HIGH (480Mbps) pwr=ON (500mA)
>> 
>> rnd> svn diff
>> Index: usbdevs
>> ===
>> --- usbdevs (revision 291745)
>> +++ usbdevs (working copy)
>> @@ -1657,6 +1657,7 @@
>>  product DLINK2 RTL8192SU_1 0x3300  RTL8192SU
>>  product DLINK2 RTL8192SU_2 0x3302  RTL8192SU
>>  product DLINK2 DWA131A10x3303  DWA-131 A1
>> +product DLINK  DWA131  0x3319  DWA-131
>>  product DLINK2 DWA160A20x3a09  DWA-160 A2
>>  product DLINK2 DWA120  0x3a0c  DWA-120
>>  product DLINK2 DWA120_NF   0x3a0d  DWA-120 (no firmware)
>> Index: wlan/if_urtwn.c
>> ===
>> --- wlan/if_urtwn.c (revision 291745)
>> +++ wlan/if_urtwn.c (working copy)
>> @@ -116,6 +116,7 @@
>> URTWN_DEV(DLINK,RTL8192CU_2),
>> URTWN_DEV(DLINK,RTL8192CU_3),
>> URTWN_DEV(DLINK,DWA131B),
>> +   URTWN_DEV(DLINK,DWA131), // danny
>> URTWN_DEV(EDIMAX,   EW7811UN),
>> URTWN_DEV(EDIMAX,   RTL8192CU),
>> URTWN_DEV(FEIXUN,   RTL8188CU),
>> 
> 
> Hi,
> 
> You should use vendor RALINK (according to your usbconfig dump)
> 
> vendor RALINK 0x148f  Ralink Technology

you are confusing Vladimir’s with mine.
here is mine again:
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON (500mA)

 bLength = 0x0012 
 bDescriptorType = 0x0001 
 bcdUSB = 0x0210 
 bDeviceClass = 0x  
 bDeviceSubClass = 0x 
 bDeviceProtocol = 0x 
 bMaxPacketSize0 = 0x0040 
 idVendor = 0x2001  <== D-LINK
 idProduct = 0x3319 
 bcdDevice = 0x0200 
 iManufacturer = 0x0001  
 iProduct = 0x0002  
 iSerialNumber = 0x0003  <00e04c01>
 bNumConfigurations = 0x0001 

danny

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Hans Petter Selasky 

On 12/29/15 13:36, Daniel Braniss wrote:




Until /etc/devd/usb.conf is regenerated, you'll need to manually load 
the kernel module for urtwn. Did you do that?


--HPS

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Kevin Lo 
On Tue, Dec 29, 2015 at 12:12:26PM +0200, Daniel Braniss wrote:
> 
> > On 29 Dec 2015, at 11:53, Hans Petter Selasky  wrote:
> > 
> > On 12/29/15 10:42, Daniel Braniss wrote:
> >> 
> >>> On 29 Dec 2015, at 11:33, Vladimir Botka  wrote:
> >>> 
> >>> Hi Danny,
> >>> 
> >>> On Tue, 29 Dec 2015 11:16:27 +0200
> >>> Daniel Braniss  wrote:
>  Hi All,
>  I have a working tp-link usb (realtek), but can’t get a d-link(also 
>  realtek) to work.
>  usbconfig:
>   ugen0.4:  at usbus0, cfg=0 md=HOST 
>  spd=HIGH (480Mbps) pwr=ON (500mA)
>  This is on a raspberry pi running a resent current.
>  cheers & season greetings,
>   danny
> >>> 
> >>> I've added freebsd-wireless list.
> >>> 
> >>> My 2 cents. It might be helpful to see more details about the adapters.
> >>> For example:
> >>> 
> >>> # usbconfig -u 0 -a 7 dump_device_desc
> >>> ugen0.7: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=HIGH
> >>> (480Mbps) pwr=ON (450mA)
> >>>  bLength = 0x0012
> >>>  bDescriptorType = 0x0001
> >>>  bcdUSB = 0x0200
> >>>  bDeviceClass = 0x  
> >>>  bDeviceSubClass = 0x
> >>>  bDeviceProtocol = 0x
> >>>  bMaxPacketSize0 = 0x0040
> >>>  idVendor = 0x148f
> >>>  idProduct = 0x5370
> >>>  bcdDevice = 0x0101
> >>>  iManufacturer = 0x0001  
> >>>  iProduct = 0x0002  <802.11 n WLAN>
> >>>  iSerialNumber = 0x0003  <1.0>
> >>>  bNumConfigurations = 0x0001
> >> 
> >> 
> >> so here it is:
> >> root@:~ # usbconfig -u 0 -a 4 dump_device_desc
> >> ugen0.4:  at usbus0, cfg=0 md=HOST 
> >> spd=HIGH (480Mbps) pwr=ON (500mA)
> >> 
> >>   bLength = 0x0012
> >>   bDescriptorType = 0x0001
> >>   bcdUSB = 0x0210
> >>   bDeviceClass = 0x  
> >>   bDeviceSubClass = 0x
> >>   bDeviceProtocol = 0x
> >>   bMaxPacketSize0 = 0x0040
> >>   idVendor = 0x2001
> >>   idProduct = 0x3319
> >>   bcdDevice = 0x0200
> >>   iManufacturer = 0x0001  
> >>   iProduct = 0x0002  
> >>   iSerialNumber = 0x0003  <00e04c01>
> >>   bNumConfigurations = 0x0001
> >> 
> >> thanks,
> >>danny
> >> 
> > 
> > Did you google the idVendor and idProduct values and see if Linux has a 
> > driver already?
> > 
> > —HPS
> > 
> 
> 
> https://github.com/Mange/rtl8192eu-linux-driver/blob/master/os_dep/linux/usb_intf.c
>  
> 
> and look at line 216

Your device (D-Link DWA-131 rev E1) is rtl8192eu, which is not supported by
FreeBSD.

> danny

Kevin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Daniel Braniss 

> On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:
> 
> On 12/29/15 13:36, Daniel Braniss wrote:
>> 
> 
> Until /etc/devd/usb.conf is regenerated, you'll need to manually load the 
> kernel module for urtwn. Did you do that?
> 
> --HPS
> 
ok, set if_urtwn_load=yes
and now I get:

ugen0.4:  at usbus0
urtwn0:  on usbus0
urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
Fatal kernel mode data abort: 'Translation Fault (L1)' on write
trapframe: 0xda29fb88
FSR=0805, FAR=, spsr=6013
r0 =, r1 =, r2 =c0a72cb0, r3 =0165
r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc

[ thread pid 13 tid 100045 ]
Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
db> 

btw, as long as you are willing to help, I will keep testing,
in other words, i’m ok.

thanks,
danny

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Hans Petter Selasky 

On 12/29/15 15:02, Hans Petter Selasky wrote:

On 12/29/15 14:00, Daniel Braniss wrote:



On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:

On 12/29/15 13:36, Daniel Braniss wrote:




Until /etc/devd/usb.conf is regenerated, you'll need to manually load
the kernel module for urtwn. Did you do that?

--HPS


ok, set if_urtwn_load=yes
and now I get:

ugen0.4:  at usbus0
urtwn0:  on usbus0
urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
Fatal kernel mode data abort: 'Translation Fault (L1)' on write
trapframe: 0xda29fb88
FSR=0805, FAR=, spsr=6013
r0 =, r1 =, r2 =c0a72cb0, r3 =0165
r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc

[ thread pid 13 tid 100045 ]
Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
db>

btw, as long as you are willing to help, I will keep testing,
in other words, i’m ok.


Hi Andriy,

Can you fix the crash above and verify this error patch?



Hi,

I see 11-current has a fix. Maybe MFC that to 10-stable?


Andriy:

After:
 usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
There is no need for:
 usbd_transfer_drain(sc->sc_xfer[x]);


--HPS

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: clang/3.7.1/include/ does not exist?

2015-12-29 Thread Jeffrey Bouquet 


On Mon, 28 Dec 2015 18:39:59 -0800 (PST), Roger Marquis  
wrote:

> Anyone else seeing these buildworld errors?
> 
>===> lib/clang/include (install)
>sh /usr/src/tools/install.sh -C -o root -g wheel -m 444
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__stddef_max_align_t.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__wmmintrin_aes.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__wmmintrin_pclmul.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/adxintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/altivec.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/ammintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/arm_acle.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx2intrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512bwintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512cdintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512dqintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512erintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512fintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512vlbwintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512vldqintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx512vlintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avxintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/bmi2intrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/bmiintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/cpuid.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/cuda_builtin_vars.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/emmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/f16cintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/fma4intrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/fmaintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/fxsrintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/htmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/htmxlintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/ia32intrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/immintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/lzcntintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/mm3dnow.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/mm_malloc.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/mmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/module.modulemap
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/nmmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/pmmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/popcntintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/prfchwintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/rdseedintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/rtmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/s390intrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/shaintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/smmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/tbmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/tmmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/vadefs.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/vecintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/wmmintrin.h
>
> /usr/src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/x86intrin.h
>
>

Re: D-link wireless not detected

2015-12-29 Thread Hans Petter Selasky 

On 12/29/15 11:12, Daniel Braniss wrote:


https://github.com/Mange/rtl8192eu-linux-driver/blob/master/os_dep/linux/usb_intf.c  

and look at line 216

danny


Hi,

You should be able to get this device working by adding a device entry to:

src/sys/dev/usb/wlan/if_urtwn.c

Can you make a patch and PR for this, and I'll submit upstream. I 
recommend you test using an 11-current kernel.


--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Kevin Lo 
On Tue, Dec 29, 2015 at 03:02:35PM +0100, Hans Petter Selasky wrote:
> On 12/29/15 14:00, Daniel Braniss wrote:
> >
> >> On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:
> >>
> >> On 12/29/15 13:36, Daniel Braniss wrote:
> >>>
> >>
> >> Until /etc/devd/usb.conf is regenerated, you'll need to manually load the 
> >> kernel module for urtwn. Did you do that?
> >>
> >> --HPS
> >>
> > ok, set if_urtwn_load=yes
> > and now I get:
> >
> > ugen0.4:  at usbus0
> > urtwn0:  on usbus0
> > urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
> > Fatal kernel mode data abort: 'Translation Fault (L1)' on write
> > trapframe: 0xda29fb88
> > FSR=0805, FAR=, spsr=6013
> > r0 =, r1 =, r2 =c0a72cb0, r3 =0165
> > r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
> > r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
> > r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc
> >
> > [ thread pid 13 tid 100045 ]
> > Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
> > db>
> >
> > btw, as long as you are willing to help, I will keep testing,
> > in other words, i’m ok.
> 
> Hi Andriy,
> 
> Can you fix the crash above and verify this error patch?
> 
> Andriy:
> 
> After:
>  usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
> There is no need for:
>   usbd_transfer_drain(sc->sc_xfer[x]);

As I mentioned previously we don't support rtl8192eu.  One difference 
between those is the the number of endpoints and its addresses.

> --HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

USB timeouts while booting

2015-12-29 Thread John 

Hello freebsd-currents,

My freebsd-11 machine (r292657), whenever it boots, displays the following
repeated messages at the console:

Dec 29 09:51:14 pumpkin kernel: usbd_setup_device_desc: getting device
descriptor at addr 6 failed, USB_ERR_TIMEOUT
Dec 29 09:51:14 pumpkin kernel: usbd_setup_device_desc: getting device
descriptor at addr 6 failed, USB_ERR_TIMEOUT
Dec 29 09:51:14 pumpkin kernel: pflog0: promiscuous mode enabled
Dec 29 09:51:16 pumpkin kernel: usbd_setup_device_desc: getting device
descriptor at addr 6 failed, USB_ERR_TIMEOUT
Dec 29 09:51:24 pumpkin last message repeated 2 times
Dec 29 09:51:24 pumpkin kernel: ugen0.7:  at usbus0
(disconnected)
Dec 29 09:51:24 pumpkin kernel: uhub_reattach_port: could not allocate
new device
Dec 29 09:51:25 pumpkin kernel: ugen0.7:  at usbus0
Dec 29 09:51:25 pumpkin kernel: umass1:  on usbus0

The login prompt comes up which then gets overwritten by the output of
the process of usb being successfully recognised. I have to hit return
to get a fresh unobscured login prompt and can log in normally.

What do I have to tweak to either extend the timeout value or make the
timeout disappear?

thanks,

--
John
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Hans Petter Selasky 

On 12/29/15 13:26, Daniel Braniss wrote:



On 29 Dec 2015, at 12:20, Hans Petter Selasky  wrote:

On 12/29/15 11:12, Daniel Braniss wrote:


https://github.com/Mange/rtl8192eu-linux-driver/blob/master/os_dep/linux/usb_intf.c  

and look at line 216

danny


Hi,

You should be able to get this device working by adding a device entry to:

src/sys/dev/usb/wlan/if_urtwn.c

Can you make a patch and PR for this, and I'll submit upstream. I recommend you 
test using an 11-current kernel.

--HPS


clearly, I’m missing something, because it’s not working :-(
the only visible change is now
ugen0.4: <802.11n WLAN Adapter RealtekWireless N Nano USB A> at usbus0, cfg=0 
md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
before it was
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON (500mA)

rnd> svn diff
Index: usbdevs
===
--- usbdevs (revision 291745)
+++ usbdevs (working copy)
@@ -1657,6 +1657,7 @@
  product DLINK2 RTL8192SU_1 0x3300  RTL8192SU
  product DLINK2 RTL8192SU_2 0x3302  RTL8192SU
  product DLINK2 DWA131A10x3303  DWA-131 A1
+product DLINK  DWA131  0x3319  DWA-131
  product DLINK2 DWA160A20x3a09  DWA-160 A2
  product DLINK2 DWA120  0x3a0c  DWA-120
  product DLINK2 DWA120_NF   0x3a0d  DWA-120 (no firmware)
Index: wlan/if_urtwn.c
===
--- wlan/if_urtwn.c (revision 291745)
+++ wlan/if_urtwn.c (working copy)
@@ -116,6 +116,7 @@
 URTWN_DEV(DLINK,RTL8192CU_2),
 URTWN_DEV(DLINK,RTL8192CU_3),
 URTWN_DEV(DLINK,DWA131B),
+   URTWN_DEV(DLINK,DWA131), // danny
 URTWN_DEV(EDIMAX,   EW7811UN),
 URTWN_DEV(EDIMAX,   RTL8192CU),
 URTWN_DEV(FEIXUN,   RTL8188CU),



Hi,

You should use vendor RALINK (according to your usbconfig dump)

vendor RALINK   0x148f  Ralink Technology

--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: D-link wireless not detected

2015-12-29 Thread Andriy Voskoboinyk 
Tue, 29 Dec 2015 16:08:56 +0200 було написано Kubilay Kocak  
:



On 30/12/2015 1:07 AM, Hans Petter Selasky wrote:

On 12/29/15 15:02, Hans Petter Selasky wrote:

On 12/29/15 14:00, Daniel Braniss wrote:


On 29 Dec 2015, at 14:44, Hans Petter Selasky   
wrote:


On 12/29/15 13:36, Daniel Braniss wrote:




Until /etc/devd/usb.conf is regenerated, you'll need to manually load
the kernel module for urtwn. Did you do that?

--HPS


ok, set if_urtwn_load=yes
and now I get:

ugen0.4:  at usbus0
urtwn0:  on usbus0
urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
Fatal kernel mode data abort: 'Translation Fault (L1)' on write
trapframe: 0xda29fb88
FSR=0805, FAR=, spsr=6013
r0 =, r1 =, r2 =c0a72cb0, r3 =0165
r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc

[ thread pid 13 tid 100045 ]
Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
db>

btw, as long as you are willing to help, I will keep testing,
in other words, i’m ok.


Hi Andriy,

Can you fix the crash above and verify this error patch?



Hi,

I see 11-current has a fix. Maybe MFC that to 10-stable?


Is there a Bugzilla issue ID for it?


No, it was fixed in r292174 (as a part of  
https://reviews.freebsd.org/D4447)





Andriy:

After:
 usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
There is no need for:
 usbd_transfer_drain(sc->sc_xfer[x]);


--HPS



___
freebsd-wirel...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to  
"freebsd-wireless-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"