urtwm -> rtwm

[Daniel Braniss]

hi,
between r30666 and r30808 i lost my wireless,
so reading UPDATE clarified why, I also did a mergemaster so now devd et.all. 
seem to be in sync,
but now devd complains that if_rtwn_usb depends on rtwm and there is no rtwn, 
instead there are
several rtwn-rtl8…., the closest being rtwn-rt18188eufw.ko

this is what the old urtwn has to say:
...
Starting devd.
wlan: <802.11 Link Layer>
urtwn0 on uhub1
urtwn0:  on usbus0
urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
urtwn0: enabling 11n
urtwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
urtwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 
36Mbps 48Mbps 54Mbps
urtwn0: 1T1R
urtwn0: 11ng MCS 20MHz
urtwn0: MCS 0-7: 6.5Mbps - 65Mbps

please help

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: urtwm -> rtwm

[Daniel Braniss]

> On 30 Oct 2016, at 14:07, Daniel Braniss  wrote:
> 
> hi,
> between r30666 and r30808 i lost my wireless,
s/r30666/r306333/ and s/r30808/r308087/

> so reading UPDATE clarified why, I also did a mergemaster so now devd et.all. 
> seem to be in sync,
> but now devd complains that if_rtwn_usb depends on rtwm and there is no rtwn, 
> instead there are
> several rtwn-rtl8…., the closest being rtwn-rt18188eufw.ko
> 
> this is what the old urtwn has to say:
> ...
> Starting devd.
> wlan: <802.11 Link Layer>
> urtwn0 on uhub1
> urtwn0:  on usbus0
> urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
> urtwn0: enabling 11n
> urtwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> urtwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 
> 24Mbps 36Mbps 48Mbps 54Mbps
> urtwn0: 1T1R
> urtwn0: 11ng MCS 20MHz
> urtwn0: MCS 0-7: 6.5Mbps - 65Mbps
> 
> please help
> 
> 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"

___
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: ZFS - Abyssal slow on copying

[O. Hartmann]

Am Tue, 4 Oct 2016 12:42:32 +0200
Fabian Keil  schrieb:

> "O. Hartmann"  wrote:
> 
> > Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct  2 09:34:50 
> > CEST 2016
> > ), I have a NanoBSD setup which creates an image for a router device.
> > 
> > The problem I face is related to ZFS. The system has a system's SSD 
> > (Samsung 850 Pro,
> > 256GB) which has an UFS filesystem. Aditionally, I have also a backup and a 
> > data HDD,
> > both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both the 
> > sources for
> > the NanoBSD and the object tree as well as the NANO_WORLDDIR are residing 
> > on the 3 TB
> > data drive. 
> > 
> > The box itself has 8 GB RAM. When it comes to create the memory disk, which 
> > is ~ 1,3
> > GB in size, the NanoBSD script starts creating the memory disk and then 
> > installing
> > world into this memory disk. And this part is a kind of abyssal in terms of 
> > the
> > speed.  
> 
> Can you reproduce the issue if you replace the memory disk with
> a zvol or tmpfs?
> 
> While I agree that depulication could be the cause of the problem,
> it probably wouldn't hurt to rule out a memory-disk related issue
> before recreating the pool.
> 
> Fabian

I guess this issue was triggered due to having deduplication enabled on the ZFS 
pool
rather than on the ZFS partitions (this is a guess based upon comments made by 
knowing
people and the fact, that the noisy copying and slowness went away after 
removing dedup
from the ZFS pool).


pgpbZSfmMwiq5.pgp
Description: OpenPGP digital signature

Re: CURRENT: re(4) crashing system

[YongHyeon PYUN]

On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote:
> On Thu, 27 Oct 2016 10:00:04 +0900
> YongHyeon PYUN  wrote:
> 
> > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote:
> > > On Tue, 25 Oct 2016 11:05:38 +0900
> > > YongHyeon PYUN  wrote:
> > >   
> > 
> > [...]
> > 
> > > > I'm not sure but it's likely the issue is related with EEE/Green
> > > > Ethernet handling. EEE is negotiated feature with link partner. If
> > > > you directly connect your laptop to non-EEE capable link partner
> > > > like other re(4) box without switches you may be able to tell
> > > > whether the issue is EEE/Green Ethernet related one or not.  
> > > 
> > > Me either since when I discovered a problem the first time with
> > > CURRENT, that was the Friday before last week's Friday, there was a
> > > unlucky coicidence: I got the new switch, FreeBSD introduced a
> > > serious bug and I changed the NICs.
> > > 
> > > The laptop, the last in the row of re(4) equipted systems on which I
> > > use the Realtek NIC, does well now with Green IT technology, but
> > > crashes on plugging/unplugging - not on each event, but at least in
> > > one of ten.  
> > 
> > Hmm, it seems you know how to trigger the issue. When you unplug
> > UTP cable was there active network traffic on re(4) device?
> > It would be helpful to know which event triggers the crash(e.g.
> > unplugging or plugging).  And would you show me backtrace of panic?
> > 
> > > I guess the Green IT issue is more a unlucky guess of mine and went
> > > hand in hand with the problem I face with CURRENT right now on some
> > > older, Non UEFI machines.
> > >   
> > 
> > Ok.
> > 
> > [...]
> > > 
> > > As requested the informations about re0 and rgephy0 on the laptop
> > > (Lenovo E540) 
> > > 
> > > [...]
> > > 
> > > rgephy0:  PHY 1 on miibus0
> > > rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> > > 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX,
> > > 1000baseT-FDX-master, 1000baseT-FDX-flow,
> > > 1000baseT-FDX-flow-master, auto, auto-flow
> > > 
> > > re0: 
> > > port 0x3000-0x30ff mem 0xf0d04000-0xf0d04fff,0xf0d0-0xf0d03fff
> > > at device 0.0 on pci2 re0: Using 1 MSI-X message re0: ASPM disabled
> > > re0: Chip rev. 0x5080
> > > re0: MAC rev. 0x0010  
> > 
> > This looks like 8168GU controller.
> > 
> > [...]
> > 
> > > I use options netmap in kernel config, but the problem is also
> > > present without this option - just for the record.
> > >   
> > 
> > Yup, netmap(4) has nothing to do with the crash.
> > 
> > Thanks.
> 
> Attached, you'll find the backtrace of the crash. This time it was
> really easy - just one pull of the LAN cabling - and we are happy :-/
> 
> Please let me know if you need something else. I will return to normal
> operations (disabling debugging) due to CURRENT is very unstable at the
> moment on other hosts beyond r307157.
> 

It seems the attachment was stripped.
___
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"