Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

Hi! So, my Lenovo T540p also doesn't work right now; it just panics the kernel with a NULL pointer deref inside some deferred interrupt registration / callback thing. If I disable it at the boot console then it's fine. -adrian ___

Re: Correct net80211 channel flag.

lemme go see (again). That's why I wanted to re-review it all before I landed stuff! -a On Fri, 2 Apr 2021 at 13:41, Bjoern A. Zeeb wrote: > > On 2 Apr 2021, at 6:44, Adrian Chadd wrote: > > > I've got this in my local tree now. > > That’s not a good idea? > > &

Re: Correct net80211 channel flag.

I've got this in my local tree now. I have a note to go dig up which draft I yanked this from and update it with reference to the draft and the current spec. Thanks for pointing this out! -adrian ___ freebsd-current@freebsd.org mailing list

Re: Correct net80211 channel flag.

gt; I had tried using this section of code and found these flags are not > satisfied, after changing them, I can negotiate VHT80, VHT160 fine with iwm, > so I pointed out this problem. I am also wondering what's the badly wrong of > you said in draft VHT implementation? > > thanks >

Re: Correct net80211 channel flag.

hm! On Mon, 29 Mar 2021 at 08:02, qcwap <1051244...@qq.com> wrote: > > This patch corrects ieee80211_vht_get_vhtcap_ie for 160/80P80 channel width > recognition. > > diff --git a/sys/net80211/ieee80211.h b/sys/net80211/ieee80211.h > index 86ab1459cca..76c43629b33 100644 > ---

Re: mips32 + gcc9 -- still broken

.) > > -Dimitry > > > On 5 Oct 2020, at 05:40, Adrian Chadd wrote: > > > > ping! > > > > I've got the world building on gcc + mips32 just patching > cxx_contention_t to be 32 bits, but it looks like an ABI change. > > > > Would the better thing

Re: mips32 + gcc9 -- still broken

Oct 2020 at 13:35, Adrian Chadd wrote: > > > On Mon, 21 Sep 2020 at 00:43, Alexander Richardson < > arichard...@freebsd.org> wrote: > >> >> On Mon, 21 Sep 2020, 07:38 Adrian Chadd, wrote: >> >>> So, the big list of unknown symbols was my fault! W

Re: mips32 + gcc9 -- still broken

On Mon, 21 Sep 2020 at 00:43, Alexander Richardson wrote: > > On Mon, 21 Sep 2020, 07:38 Adrian Chadd, wrote: > >> So, the big list of unknown symbols was my fault! Whoops. >> >> i've gotten further using gcc-6.4 by fixing some of the warnings/issues >> that hav

Re: mips32 + gcc9 -- still broken

So, the big list of unknown symbols was my fault! Whoops. i've gotten further using gcc-6.4 by fixing some of the warnings/issues that have crept up. Here's a review for one of them: https://reviews.freebsd.org/D26504 However, now I've hit: /usr/local/bin/mips-unknown-freebsd13.0-ld:

Re: Plans for git

On Sun, 20 Sep 2020 at 15:37, Rick Macklem wrote: > Christian Weisgerber wrote: > > On 2020-09-19, Zaphod Beeblebrox wrote: > > > > > Hrm. Maybe what I hear others saying, tho, and not entirely being > replied > > > to is just a nice concise document of the why. What I hear you saying > is >

mips32 + gcc9 -- still broken

hi! So mips32 and gcc9 is broken, and things have been broken with mips32+gcc for months now. I've been poking slowly at the various build failures and they're getting slowly fixed, but this one deep in linker fun is stumping me: === /usr/local/bin/mips-unknown-freebsd13.0-gcc9

Re: svn commit: r364936 - in head: lib lib/libnetmap share/mk

hi! This code fails compilation on mips32 + gcc, as it assumes uint64_t and pointer casts are the same underlying size. === /usr/local/bin/mips-unknown-freebsd13.0-gcc9 --sysroot=/usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap/usr/home/adrian/work/freebsd/head-embedded/src/mips.mips/tmp

Re: Panic with wifi + usb in latest FreeBSD-current

On Sun, 13 Sep 2020 at 22:34, Warner Losh wrote: > > > On Sun, Sep 13, 2020, 11:29 PM Adrian Chadd > wrote: > >> Yeah, this was also reported in #freebsd-wireless today. >> >> Is there a lock being held in the rtwn path that shouldn't be? >> > &g

Re: Panic with wifi + usb in latest FreeBSD-current

Yeah, this was also reported in #freebsd-wireless today. Is there a lock being held in the rtwn path that shouldn't be? -adrian On Sun, 13 Sep 2020 at 21:30, Warner Losh wrote: > I'm running current as of -2h ago. > > When I plug in my rtwn0 device and it configures, etc, I get: > > rtwn0

Re: driver for cp2112 (USB GPIO and I2C gadget)

hi! On Wed, 8 Jul 2020 at 02:39, Andriy Gapon wrote: > On 19/06/2020 17:14, Andriy Gapon wrote: > > > > If anyone interested in reviewing a new driver please help yourself to: > > https://reviews.freebsd.org/D25359 > > https://reviews.freebsd.org/D25360 > > What might be curious about it is

Re: iflib and options RSS is a no go for igbX

On Tue, 26 May 2020 at 17:01, Matthew Macy wrote: > > > > > I can go setup my second PC this week (I have PTO!) and go see if I > > have any PCIe igb hardware here. I /think/ I do but it's fibre. > > The RSS compile time option used to be disabled in part because of > this. The drivers had

Re: iflib and options RSS is a no go for igbX

reply to all this time: On Tue, 26 May 2020 at 02:03, Hans Petter Selasky wrote: > > Hi, > > I just found a bug where outgoing TCP connections over igb0 doesn't work > because likely the software computed hash is wrong, so the incoming > packets get dropped because they are received on the wrong

Re: Can't cross-compile HEAD

On Fri, 21 Feb 2020 at 12:57, Kyle Evans wrote: > Ahhh, this makes more sense now. > > > Not sure about Makefile.depend file as it says 'Autogenerated - do NOT > > edit!' (would be great to extend the comment with info autogenerated > > by 'what' exactly), and not sure if I pointed dependency

Re: wlan can't discover known networks after relocating

On Thu, 19 Sep 2019 at 15:21, Johannes Lundberg wrote: > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > So roaming in ifconfig/net80211 is what's set to manual. > > wpa_supplicant right now does RSSI threshold based roaming. All of the > roaming and network preference

Re: wlan can't discover known networks after relocating

bgscan too periodically rather than only when the RSSI is low. -adrian On Thu, 19 Sep 2019 at 15:04, Cy Schubert wrote: > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd > wrote: > >Roaming is done in wpa_supplicant when it's running.That's where the >

Re: wlan can't discover known networks after relocating

Roaming is done in wpa_supplicant when it's running.That's where the smarts need to be. :( -adrian On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb wrote: > On 19 Sep 2019, at 12:28, Tom Jones wrote: > > Hi, > > freebsd-wireless might be a better list for all this .. > > > > On Tue, Sep 17,

Re: ath10k driver status?

hi, I'm trying to update things with Geramy right now. We hit a snag where his updates broke my QCA9880 NIC in STA mode, so we're working through that right now. -adrian On Mon, 11 Feb 2019 at 09:51, Ben Widawsky wrote: > On 19-02-04 00:29:29, Anthony Jenkins wrote: > > [snip] > > Hi

Re: ath(4) issues?

hi! No. It's a side effect of how ath_rate_sample works. The TL;DR is: * ath_rate_sample uses a fixed set of rates for each attempt - so say you want to transmit at 54MBit OFDM, the second/third/fourth slower rates are in a fixed table; * net80211 negotiates which rates are acceptable to the

Re: ath(4) issues?

And I think 0x1b is "1mbit CCK", so I bet that's disabled on your AP? On Fri, 23 Nov 2018 at 11:28, Adrian Chadd wrote: > hi! > > No. It's a side effect of how ath_rate_sample works. The TL;DR is: > > * ath_rate_sample uses a fixed set of rates for each attempt - so s

Re: numa involved in instability and swap usage despite RAM free?

Hi, Aren't there now per-domain VM counters you can query via sysctl? Maybe they'd help in diagnosing what's going on. -adrian On Mon, 25 Jun 2018 at 11:23, Steve Kargl wrote: > > On Sun, Jun 24, 2018 at 12:03:29PM +0200, Alexander Leidinger wrote: > > > > I don't have hard evidence, but

Re: Can't seem to use 5GHz APs with Intel wireless

hm. Which country are you in? india? It seems to think you're in the FCC4 regdomain and DE country, which if I read it right won't give you 5G. So somehow it determined you're in the "wrong" country? -adrian On Mon, 4 Jun 2018 at 07:15, Adam wrote: > > On Sun, Jun 3, 2018 at 9:50 PM,

Re: [RFC] Deprecation and removal of the drm2 driver

On Mon, 4 Jun 2018 at 22:36, Matthew Macy wrote: > > Implementing a callback in 140 different files for the sake of a handful of > out of tree drivers and people not reading updating is pretty prohibitive. 11 > may be more your cup of tea. This was the in tree wifi drivers.. :-) Dude, we're

Re: [RFC] Deprecation and removal of the drm2 driver

Hi, If there's an API that isn't being used then great, I'll go find it and fix up pieces in my spare time to use it. But the last drive by cut/paste didn't do that; it just changed the code in place. :-) -adrian ___ freebsd-current@freebsd.org

Re: [RFC] Deprecation and removal of the drm2 driver

Hi, As a driver/framework developer - no, don't do that. It's worked mostly great for the video side of things because your touch points are "the VM system" and "linuxkpi". And they're all in one big driver pull from Linux. For wifi as an example - it has a bunch of userland components, a

Re: Periodical interrupt storm when playing game with USB keyboard

Hi Yeah the timers eventually get coalesced unless someone's asking for a ridciulously accurate timer value. So is some driver asking for hyper-accurate callout timer that isn't being coalesced? hps, is there any useful debugging to try and find callouts that are requesting stupidly accurate

Re: Programmatically cache line

On 30 December 2017 at 00:28, Konstantin Belousov wrote: > On Sat, Dec 30, 2017 at 07:50:19AM +, blubee blubeeme wrote: >> Is there some way to programmatically get the CPU cache line sizes on >> FreeBSD? > > There are, all of them are MD. > > On x86, the CPUID

Re: [mips32] build is broken due to lack of .cfi-sections support in gcc 4.2.1

Hi, Have a look at what the atheros ports now do. They've been building using the external toolchain gcc for a while now. I think we need to kick over to that. -adrian On 11 November 2017 at 12:54, Michael Zhilin wrote: > Hi, > > I've got compilation error for mips32

Re: iwm not in GENERIC kernel

ugh okay So it's a chicken/egg problem. You can't finish the device probe/attach until the firmware loads. For iwn, you can read the chipset abilities and mac address from EPROM/flash on the chip without the firmware being loaded, so you can complete probe/attach before the root filesystem

Re: cve-2017-13077 - WPA2 security vulni

[snip] yes you need to rebuild; the ioctl layout changed between -11 and -12 to account for the beginnings of 11ac. -adrian On 17 October 2017 at 11:30, Cy Schubert wrote: > I had no problems last night. It associated with one of my netgear APs. I > used

Re: cve-2017-13077 - WPA2 security vulni

ys but I'm busy with family and employment. -adrian On 16 October 2017 at 10:19, Kevin Oberman <rkober...@gmail.com> wrote: > On Mon, Oct 16, 2017 at 8:55 AM, Adrian Chadd <adrian.ch...@gmail.com> > wrote: >> >> hi, >> >> I got the patches a couple days

Re: cve-2017-13077 - WPA2 security vulni

hi, I got the patches a couple days ago. I've been busy with personal life stuff so I haven't updated our in-tree hostapd/wpa_supplicant. If someone beats me to it, great, otherwise I'll try to do it in the next couple days. I was hoping (!) for a hostap/wpa_supplicant 2.7 update to just update

Re: Ports still broken by ino64?

I'm sure stas can figure it out! -a On 25 June 2017 at 22:44, Thomas Mueller <mueller6...@twc.com> wrote: > from Adrian Chadd: > >> valgrind broke as part of the ino64 work :( > > Valgrind was not on my mind! Your post sent me to > > ls -d /usr/ports/*/val* >

Re: Ports still broken by ino64?

Hi, valgrind broke as part of the ino64 work :( -a ___ 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: [RESOLVED] Failover Mode Between Ethernet and Wireless Interfaces broken on >= 11

hi! Thanks! Yes please let's update the handbook at least. -a On 23 June 2017 at 10:06, Renato Botelho <ga...@freebsd.org> wrote: > On 23/06/17 13:43, Adrian Chadd wrote: >> Hi, >> >> You can't change a wifi mac address /after the interface is up/. So if >&

Re: Failover Mode Between Ethernet and Wireless Interfaces broken on >= 11

Hi, You can't change a wifi mac address /after the interface is up/. So if that's happening with this RC script combination then we should kinda fix that. -adrian ___ freebsd-current@freebsd.org mailing list

Re: [rfc] breaking out if_ath into ... lots of modules

On 22 May 2017 at 13:17, John Baldwin wrote: > Why not have if_ath.ko just be a wrapper module that depends on everything > like dtraceall.ko? That would let 'kldload if_ath' and the auto-loading > code in ifconfig still DTRT. You could name the "only the driver" module >

[rfc] breaking out if_ath into ... lots of modules

Hi, I've been putting this off for a few years, but now I've reached a point where I kind of need to do this. The TL;DR is this - I'd like to break the ath driver /back/ out into separate modules, and then have them be run-time loadable. It's part for space savings, and part for the upcoming

Re: make concurrency kit a module

On 17 May 2017 at 23:37, Warner Losh <i...@bsdimp.com> wrote: > On Wed, May 17, 2017 at 11:53 PM, Baptiste Daroussin <b...@freebsd.org> wrote: >> On Wed, May 17, 2017 at 06:04:09PM -0700, Adrian Chadd wrote: >>> https://reviews.freebsd.org/D10778 >>&

Re: make concurrency kit a module

https://reviews.freebsd.org/D10778 -a On 17 May 2017 at 17:46, Adrian Chadd <adr...@freebsd.org> wrote: > hi, > > this is a quick change that makes concurrency_kit a module. Right now > the only thing using it is linuxkpi so it's all dead code on > non-linuxkpi platf

make concurrency kit a module

hi, this is a quick change that makes concurrency_kit a module. Right now the only thing using it is linuxkpi so it's all dead code on non-linuxkpi platforms. -adrian ___ freebsd-current@freebsd.org mailing list

Re: regression suspend/resume on Lenovo T420

There were lots of commits that could break things. :-) Can you compile up some intermediary versions between 315141 and r317559 to find which commit range broke things? That'll make chasing it down much quicker! Thanks! -a On 29 April 2017 at 04:50, Manuel Stühn

Re: increased power consumption lately?

B_PCI0IGPUGSCI�K p >>> >>> Might be related to: >>> https://bugs.freedesktop.org/show_bug.cgi?id=98501 >>> >>> >>> >>> On Wed, Apr 5, 2017 at 8:15 PM, Ngie Cooper (yaneurabeya) >>> <yaneurab...@gmail.com> wrote: >>&

Re: altq and head

It'll be supported as much as someone is willing to pay for it. It isn't out of the realm of possibility to implement an if_transmit style layer for altq, etc so it could be a generic queue discipline. It'd be nice to have a multi-queue version of this but we're not there yet. Thanks, -adrian

Re: increased power consumption lately?

> > On Tue, Apr 4, 2017 at 9:39 PM, Adrian Chadd <adr...@freebsd.org> wrote: >> >> hiya, >> >> looks like yeah, you're going to have to do a bit more debugging. Can you >> see what args are being passed to AcpiNsLookup() ? >> >> >> >>

Re: increased power consumption lately?

nd they use ~30% each so > total 100% of one core. > > Machine is 2013 MBP > > pmcstat screenshot attached. > > > > On Thu, 30 Mar 2017 at 21:16, Adrian Chadd <adr...@freebsd.org> wrote: > >> I don't /think/ so - which thread is it on your end? Can you run &g

Re: increased power consumption lately?

onstant > usage. Need to lock CPU freq at lower value otherwise it runs with > turboboost all the time. > > Could it be the same for you? > > On Tue, 28 Mar 2017 at 20:58, Adrian Chadd <adr...@freebsd.org> wrote: >> >> hiya, >> >> I've noticed that my b

increased power consumption lately?

hiya, I've noticed that my battery life on my haswell laptop (T540p) seems to have taken a nosedive lately. I could've /sworn/ it was getting better than 15-16W at idle. Has anyone noticed any massive decrease in battery life lately? -adrian ___

Re: cross compiling freebsd-head is sigh, now broken - thanks libllvm

WITHOUT_CLANG fixed it for me. Thanks. -adrian On 20 March 2017 at 11:23, Ed Maste <ema...@freebsd.org> wrote: > On 19 March 2017 at 03:00, Adrian Chadd <adr...@freebsd.org> wrote: >> gcc version 5.3.0 (FreeBSD Ports Collection for mips) >> >> ... so

cross compiling freebsd-head is sigh, now broken - thanks libllvm

===> lib/clang (all) ===> lib/clang/libllvm (all) In file included from /usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap/mips.mips/usr/home/adrian/work/freebsd/head-embedded/src/tmp/usr/include/c++/v1/math.h:309:0, from

Re: panic: invalid bcd xxx

On 2 March 2017 at 01:31, Matthias Apitz <g...@unixarea.de> wrote: > On Thursday, 2 March 2017 00:37:35 CET, Michael Gmelin <free...@grem.de> > wrote: >> >> >> >>> On 2 Mar 2017, at 00:35, Adrian Chadd <adrian.ch...@gmail.com> wrote: >>>

Re: panic: invalid bcd xxx

This is an emulated BIOS though, right? I don't know if we're going to get the RTC 'bugfixed'... -adrian On 28 February 2017 at 15:26, Michael Gmelin wrote: > On Tue, 28 Feb 2017 17:16:02 -0600 > Eric van Gyzen wrote: > >> On 02/28/2017 16:57, Conrad

Re: Possible overlooked "svn add" in r314192?

fxed! -a On 24 February 2017 at 09:20, Ngie Cooper wrote: > >> On Feb 24, 2017, at 05:39, David Wolfskill wrote: >> >> Updating head in place from r314136 -> r314200, I find I can't build the >> kernel because: >> >> ... >> ===> iwifw/iwi_ibss

Re: asmc driver patch merge request

ok, lemme do a build and if it succeeds i'll commit it -a On 16 February 2017 at 06:39, Johannes Lundberg <johal...@gmail.com> wrote: > My emacs remove trailing white spaces automatically on save. > > On Wed, Feb 15, 2017 at 22:59 Adrian Chadd <adrian.ch...@gmail.com> wr

Re: asmc driver patch merge request

this looks fine to me. what's with the whitespace changes? -a On 15 February 2017 at 19:27, Johannes Lundberg wrote: > Hi > > This patch adds support for MacBook Pro 11,2 to asmc. > > The other day I tried patching my old > >

Re: vt(4) chops off the leftmost three columns

want to do the right thing even if it takes longer. Really appreciate you > taking the time to respond, thanks! > > Anindya > > From: Adrian Chadd [adrian.ch...@gmail.com] > Sent: January 20, 2017 3:11 PM > To: Anindya Mukherjee >

Re: vt(4) chops off the leftmost three columns

hiya, Mechanically it doesn't look /that/ hard: * vesa.ko pulls in the vesa.c bits and the syscons vesa control bits. Ideally we'd have them as two separate modules, so you could load "vesa" without needing the syscons bits. * Maybe then write a vt 'fb' interface to talk to the old-school

Re: Installing opt_*.h kernel headers

hi, As much as I'd like to see everything be default-options and ABI compliant, things like INET/INET6 throw that assumption under the bus a bit. (Yes, I'd love to see INET/INET6 be .ko's..) So yes, I'd like to see a solution to this too. I think installing the kernel config for the running

Re: vt(4) chops off the leftmost three columns

lash screen support like sc has. > > > > Adrian Chadd wrote: >> >> hi, >> >> no, the vt_vga backend doesn't yet do VESA. >> >> I keep meaning to sit down and fix this, but life and wifi gets in the >> way. >> >> >> -adrian >

Re: vt(4) chops off the leftmost three columns

hi, no, the vt_vga backend doesn't yet do VESA. I keep meaning to sit down and fix this, but life and wifi gets in the way. -adrian On 14 January 2017 at 16:27, Kevin Oberman <rkober...@gmail.com> wrote: > On Sat, Jan 14, 2017 at 2:11 PM, Adrian Chadd <adrian.ch...@gmail.

Re: vt(4) chops off the leftmost three columns

It depends(tm). I think the VT code just does "640x480x4bpp" and lets the BIOS sort it out. A lot of things don't cope well with 640x480 these days - they try autodetecting picture edges, but a black border makes that very difficult. -adrian On 14 January 2017 at 08:57, Matthias Andree

Re: onboard wifi raspberry pi3 and aarch64/freebsd-current

hi! no, and maybe. -a On 9 January 2017 at 05:30, tech-lists wrote: > Hello lists, > > [x-posted to freebsd-arm because this question appears to be equally > relevant there] > > Does the onboard wireless on the raspberry pi 3 work in 12-current-aarch64? > > If not, are

Re: PQ_LAUNDRY: unexpected behaviour

email freebsd-wireless with the wifi details. i know our iwm driver gets antenna configs wrong sometimes and that can cause issues. -a On 6 January 2017 at 11:07, Jonathan Anderson wrote: > On 6 Jan 2017, at 13:53, Pete Wright wrote: >> >> >> i've been having the same

Re: RFC: DTrace probes for debugging or testing in userland programs

*mumble* damnit jordan this requires libdispatch *mumble* -a ___ 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: RFC: DTrace probes for debugging or testing in userland programs

On 19 December 2016 at 16:04, Jordan Hubbard <j...@mail.turbofuzz.com> wrote: > > On Dec 19, 2016, at 12:27 PM, Adrian Chadd <adrian.ch...@gmail.com> wrote: > > So although I like the sentiment, I don't think using dtrace for > program logging is the right answer. I

Re: RFC: DTrace probes for debugging or testing in userland programs

Hi, I'd love to see a unified-ish logging API for FreeBSD applications. I always end up reusing some C code I have here that I based on some Squid style logging API in ages past. I could always polish it up and put it up for review. I'm not a big fan of requiring dtrace to use it though. On a

Re: best approximation of getcpu() ?

On 16 December 2016 at 11:45, Luigi Rizzo wrote: > On Fri, Dec 16, 2016 at 09:29:15AM +, David Chisnall wrote: >> On 16 Dec 2016, at 03:10, Alan Somers wrote: >> > >> > What about pthread_setaffinity(3) and friends? You can use it to pin >> > a

Re: Enabling NUMA in BIOS stop booting FreeBSD

heh, an updated BIOS that solves the problem will solve the problem. :) I think you have enough information to provide to supermicro. Ie, "SMAP says X, when physical memory pages at addresses X are accessed, they don't behave like memory, maybe something is wrong". All I can think of is some

Re: drm-next update and longer term plans

Hi, The challenge right now is figuring out how to implement / commit the linux-y bits that the linux layer really wants. Kip has done a pretty great job at figuring out the minimum set of hilarity that needs to go into base versus linuxkpi. But the "challenge" is figuring out some comprimise

Re: Enabling NUMA in BIOS stop booting FreeBSD

On 26 November 2016 at 13:59, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: > On Sat, Nov 26, 2016 at 01:55:14PM -0800, Adrian Chadd wrote: > >> ok, hm. then i don' know offhand, not without putting in printf debugging. :) > > I am not expert in this code, I am need you patc

Re: Enabling NUMA in BIOS stop booting FreeBSD

ok, hm. then i don' know offhand, not without putting in printf debugging. :) -a On 26 November 2016 at 13:51, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: > On Sat, Nov 26, 2016 at 01:49:00PM -0800, Adrian Chadd wrote: > >> Ok. So boot verbose and let's see what it says. >

Re: Enabling NUMA in BIOS stop booting FreeBSD

Ok. So boot verbose and let's see what it says. -adrian On 26 November 2016 at 10:39, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: > On Sat, Nov 26, 2016 at 09:44:49AM -0800, Adrian Chadd wrote: > >> The ACPI SRAT parsing code - sys/x86/acpica/srat.c . >> >> I'd

Re: Enabling NUMA in BIOS stop booting FreeBSD

wrote: > On Sat, Nov 26, 2016 at 09:35:08AM -0800, Adrian Chadd wrote: > >> It may be something to do with memory topology parsing. Maybe we need >> some more debugging there to try and catch it. > > What debug you need? > >> On 26 November 2016 at 01:21, Slawa Olhovche

Re: Enabling NUMA in BIOS stop booting FreeBSD

It may be something to do with memory topology parsing. Maybe we need some more debugging there to try and catch it. -a On 26 November 2016 at 01:21, Slawa Olhovchenkov wrote: > I am try to enable NUMA in bios and can't boot FreeBSD. > Boot stoped after next messages: > >

Re: tput failing on 10 and 12 systems?

Hiya, Just to follow through - part of tput is to decode command args, but it then just requests it from the ncurses tputs() call. So it could be tput, but it could also be the BSD ncurses work. -adrian On 21 November 2016 at 07:54, Julian Elischer wrote: > example on

Re: SM bus ioctls incorrect in FreeBSD 11

+10 on option 2. Hate to say it, but I'd rather this little corner of freebsd be "right" before it gets more heavily used. -a On 10 November 2016 at 03:21, Andriy Gapon wrote: > On 14/10/2016 18:51, Lewis Donzis wrote: >> Our opinion doesn’t count for much, but I like 2 or

Re: hang during kldload if_bwn

I don't know why it's hanging; and unfortunately I'll have to reinstall -head to get a working console (since the device I have here for doing ppc+bwn work wants syscons, /not/ vt.. :( ) -a On 6 November 2016 at 14:42, Justin Hibbits wrote: > Hi folks, > > I have a

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

Hiya, So uhm - normal rtwn works fine, but andriy's merged version doesn't? -a ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

hi, can you turn on debugging? Do you see RX frames? -a On 1 October 2016 at 08:09, Kevin Lo wrote: > Strange, rtwn(4) stops working. I tried to scan for the available network, > but it just returns empty results. > > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

hi, I'll try it out tonight! Is the rtwn repo still "ok" to try as a standalone thing? The usbdevs patch is fine standalone - would you like to just commit this in advance? -adrian On 19 September 2016 at 06:26, Andriy Voskoboinyk wrote: > Thu, 01 Sep 2016 19:29:03 +0300

Re: FreeBSD12-RC2 and bluetooth?

hi, bluetooth uses netgraph. -a On 15 September 2016 at 11:36, Steve Kargl wrote: > I recently got a spanky new Dell Precision 7510. After > freeing up space on the nvme device, I installed > FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img > on

Re: 11.0-RC2 suspend/resume on thinkpad x201 kills poweroff

is it too new to "kldload i915kms" ? -adrian On 9 September 2016 at 00:45, Philip Homburg wrote: >>What graphics driver are you using? > > Just the default: > 'VT(vga): resolution 640x480' > > Booting with -v and switching I now noticed that each time I switch to a

Re: 11.0-RC2 suspend/resume on thinkpad x201 kills poweroff

Try forcing a console switch - hit alt-f1, alt-f2, etc. -a On 8 September 2016 at 15:10, Glen Barber wrote: > On Thu, Sep 08, 2016 at 11:32:24PM +0200, Philip Homburg wrote: >> The main culprit seems to be putting 'hw.acpi.reset_video=1' in >> /boot/loader.conf >> > > Yes, I

Re: Intel ac8260 and wpa_supplicant

hi, There's some interesting issues with the scan logic in -HEAD where we abort/finish a scan if there's active traffic, but there's no way to say "the scan was interrupted by active traffic and will continue" versus "the scan was aborted" or "the scan is finished". So sometimes the scan results

Re: Arcan [0.5.1] on FreeBSD/KMS

Hey, this looks really cool! -a On 5 September 2016 at 06:25, bbjowhn . wrote: > I'm guessing most of you seeing this post aren't too familiar with the > project, so I'll start with something of a synopsis. > > Arcan is a mix between a streaming realtime graphics (and

Re: APU2C4 information (was Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4)

hi, no, ar988x is 11ac, and i haven't finished the port. -a On 3 September 2016 at 06:36, O. Hartmann wrote: > Am Sat, 3 Sep 2016 15:25:17 +0200 > Guido Falsi schrieb: > >> On 09/03/16 15:11, O. Hartmann wrote: >> > Am Sat, 3 Sep 2016 14:01:15

Re: FreeBSD 11 RC1 - no wifi

On 25 August 2016 at 12:45, Stefan Wendler wrote: > Hi, > > is this fixed in RC2? I haven't tried it yet but would be nice to know Hi, Just so everyone who may be interested/involved can see - I don't have the spare bandwidth/cycles to try and make wifi + lagg

compiling elf toolchain under gcc-5.3 mips

hiya, This seems to be needed for compiling elftoolchain under gcc-5.3 targeting mips (CROSS_TOOLCHAIN=mips-gcc) otherwise it complains that sz isn't always initialised: adrian@gertrude:~/work/freebsd/head-embedded/src % svn diff contrib Index: contrib/elftoolchain/elfcopy/ascii.c

Re: Hardware rendered Wayland client up and running

w! ok, what has to be committed to -head? -a On 13 August 2016 at 19:12, Lundberg, Johannes wrote: > Hi FreeBSD hackers! > > Today we reached a big milestone. For the first time, we could render > Wayland clients, backed by hardware, not shm (shared

Re: IWM(7260), no connect

CCA_CHUNK = (1 << 31) >> > }; /* IWM_TX_FLAGS_BITS_API_S_VER_1 */ >> > >> > -/** >> > - * enum iwm_tx_pm_timeouts - pm timeout values in TX command >> > - * @IWM_PM_FRAME_NONE: no need to suspend sleep mode >> > - * @IWM_PM_FRAME_MGMT: fw s

Re: [PATCH] randomized delay in locking primitives, take 2

Hi, Did you test on any 1, 2, 4, 8 cpu machines? just to see if there are any performance degredations on lower count CPUs? Also, yeah, the MOD operator in each loop could get spendy on older CPUs (eg my MIPS CPUs, older ARM stuff, etc.) Is it possible to achieve much the same autotuning with

Re: IWM(7260), no connect

+imre, Hi! Larry is having issues with r303418. Would you be able to help him out? (If it's not too bad, can we back this out until you figure out what's going on?) Thanks! -a On 28 July 2016 at 18:05, Larry Rosenman <l...@lerctr.org> wrote: > On 2016-07-28 20:02, Adrian Ch

Re: IWM(7260), no connect

Hi, Which commit(s) did you revert? -a ___ 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: IWM(7260), no connect

Hi, Andriy responded? -adrian On 28 July 2016 at 16:04, Larry Rosenman wrote: > Anyone? > > > On 2016-07-27 21:39, Larry Rosenman wrote: >> >> I'm running today's top of tree, and it doesn't seem to want to connect: >> >> >> re0:

Re: (boost::)asio and kqueue problem

heh, nice catch. Would you please file a PR so we don't forget? Thanks! -a On 19 July 2016 at 08:35, Hartmut Brandt wrote: > Hi, > > I'm trying to use asio (that's boost::asio without boost) to handle > listening sockets asynchronuosly. This appears not to work. There

Re: ath (AR9460) no longer works after going to 11-STABLE r302483

Hi, Just try disabling the others and see what happens. Thanks! -a On 15 July 2016 at 13:28, Wolfgang Zenker <wolfg...@lyxys.ka.sub.org> wrote: > * Adrian Chadd <adr...@freebsd.org> [160715 00:00]: >> On 14 July 2016 at 14:37, Wolfgang Zenker <wolfg...@lyxys.ka.sub.

  1   2   3   4   5   6   7   8   9   10   >