Re: HEADSUP: Something has gone south with -current

On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > make core dumps. > > devd core dumps. > > init core dumps. > > cc core dumps. > > c++ core dumps. > > > &

Re: HEADSUP: Something has gone south with -current

On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > make core dumps. > > > devd core dumps. > > > init

Re: HEADSUP: Something has gone south with -current

On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > >

Re: HEADSUP: Something has gone south with -current

On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > Most likely this is an issue fixed by r339350. >

Re: HEADSUP: Something has gone south with -current

On Fri, Dec 07, 2018 at 05:02:03PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: >

Updating bugzilla password?

I have forgotten my bugzilla account password. I've entered the Login: account name, and clicked the "Forgot Password" button. Expecting to receiving an email that would provide instructions for updating the password. That email never comes. So, is bugzilla broken? Is it impossible to reset a

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 09:15:28AM -0800, Enji Cooper wrote: > > > On Feb 4, 2019, at 08:34, Steve Kargl > > wrote: > > > > I have forgotten my bugzilla account password. I've > > entered the Login: account name, and clicked the > > "Fo

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 09:35:45AM -0800, Enji Cooper wrote: > > > Was this for your old FreeBSD.org address, by chance? > Yes. ka...@freebsd.org .forward is set up to send the email on to my local hacking account. -- Steve _

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 09:39:49AM -0800, Enji Cooper wrote: > > > Let me loop in some other folks. Something might be up with mail forwarding > for your account. > Just sent an email to ka...@freebsd.org. It was forwarded to my local account as expected. Checking /var/log/maillog, I see no

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 10:13:40AM -0800, Enji Cooper wrote: > > > PS: if anyone cares there are 3 patches sitting in freebsd-numerics@. > > Steve, > As some others noted in the private channel, you’ll need > to reset your Kerberos password via these instructions in the > committer’s guide:

drm2 removed?

Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I raised an issue with removal of drm2 from src/sys. How is suppose to be fixed? --- ttm_bo_manager.o --- cc -O2 -pipe -march=core2 -fno-strict-aliasing -march=core2 -Werror -D_KERNEL -DKLD_MODULE -nostdinc

Re: drm2 removed?

On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > Anyone have any idea which recent change broke the > drm-legacy-kmod port. This is why I raised an issue > with removal of drm2 from src/sys. How is suppose > to be fixed? > It was r343567. The merging of PAE and N

Re: drm2 removed?

On Mon, Feb 11, 2019 at 04:33:24PM +, Johannes Lundberg wrote: > > On 2/11/19 4:23 PM, Niclas Zeising wrote: > > On 2/11/19 5:20 PM, Steve Kargl wrote: > >> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > >>> Anyone have any idea which recent

Re: drm2 removed?

On Mon, Feb 11, 2019 at 06:05:03PM +0100, Niclas Zeising wrote: > On 2/11/19 5:20 PM, Steve Kargl wrote: > > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > >> Anyone have any idea which recent change broke the > >> drm-legacy-kmod port. This is why

Re: drm2 removed?

On Mon, Feb 11, 2019 at 06:42:29PM +0100, Niclas Zeising wrote: > On 2/11/19 6:36 PM, Steve Kargl wrote: > > > > The patch allows the port to be built. > > > > kldloading the i915kms module causes a 'black screen > > of death' > > > &g

Re: drm2 removed?

On Mon, Feb 11, 2019 at 08:40:01PM +, Graham Perrin wrote: > On 11/02/2019 16:20, Steve Kargl wrote: > > > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > > > >> Anyone have any idea which recent change broke the > >> drm-legacy-kmod

Re: drm2 removed?

On Mon, Feb 11, 2019 at 09:01:55PM +, Graham Perrin wrote: > On 11/02/2019 20:42, Steve Kargl wrote: > > > Are you building on i386 or x86_64? > > $ uname -a > FreeBSD momh167-gjp4-8570p 13.0-CURRENT FreeBSD 13.0-CURRENT r343931 > GENERIC-NODEBUG  amd64 amd64 ==

Re: drm2 removed?

On Mon, Feb 11, 2019 at 06:42:29PM +0100, Niclas Zeising wrote: > > > > The patch allows the port to be built. > > > > kldloading the i915kms module causes a 'black screen > > of death' > > > Hi! > I assume you load the kernel module either manually with kldload or > using kld_list in rc.conf,

Re: drm2 removed?

On Mon, Feb 11, 2019 at 08:20:20AM -0800, Steve Kargl wrote: > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > > Anyone have any idea which recent change broke the > > drm-legacy-kmod port. This is why I raised an issue > > with removal of drm2 from src/sys.

Panic in sys_fstatat()

I have the core file and kernel.debug, if someone wnat additional information. mobile dumped core - see /var/crash/vmcore.0 Wed Feb 13 18:37:44 PST 2019 FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r344034M: Tue Feb 12 08:14:16 PST 2019 root@mobile:/usr/obj/usr/src/i386.i386/sys/MOB

Re: Panic in sys_fstatat()

On Thu, Feb 14, 2019 at 12:26:01PM -0800, John Baldwin wrote: > On 2/13/19 6:47 PM, Steve Kargl wrote: > > #16 0x00ff58bb in trap (frame=0x2e7b6880) at > > /usr/src/sys/i386/i386/trap.c:519 > > #17 0xffc0315d in ?? () > > #18 0x2e7b6880 in ?? () > > #19 0x0

Re: Panic in sys_fstatat()

On Thu, Feb 14, 2019 at 12:47:26PM -0800, John Baldwin wrote: > On 2/14/19 12:38 PM, Steve Kargl wrote: > > On Thu, Feb 14, 2019 at 12:26:01PM -0800, John Baldwin wrote: > >> On 2/13/19 6:47 PM, Steve Kargl wrote: > >>> #16 0x00ff58bb in trap (frame=0x2e7b6880) at

Re: Panic in sys_fstatat()

On Fri, Feb 15, 2019 at 09:50:55AM +0200, Andriy Gapon wrote: > > So, I suspect something exotic like some sort of a stack alignment issue, or a > CPU bug, or a mismatch between object files, or some local experiment, etc. > You might be right about something exotic. It is an old laptop, so it

What is evdev and autoloading?

Anyone have insight into what evdev is? There appears to be no manual page. When I reboot a system with custom kernel, the system is autoloading evdev.ko, uhid.ko, and wmt.ko. I do not need nor what these modules loaded. How does one prevent this autoloading? -- Steve _

Re: What is evdev and autoloading?

On Sun, Feb 17, 2019 at 03:04:41PM -0800, Mark Millard wrote: > > > On 2019-Feb-17, at 10:03, Steve Kargl > wrote: > > Anyone have insight into what evdev is? There appears to > be no manual page. When I reboot a system with custom > kernel, the system is autoloadin

Re: What is evdev and autoloading?

On Mon, Feb 18, 2019 at 04:56:57PM +0100, Baptiste Daroussin wrote: > On Mon, Feb 18, 2019 at 07:12:24AM -0800, Rodney W. Grimes wrote: > > > > Sadly your execution on that seems to be missing the mark, > > telling people they have to go get a port now to get drm working > > because it could not b

Re: What is evdev and autoloading?

On Mon, Feb 18, 2019 at 09:32:52AM -0700, Warner Losh wrote: > On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes < > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > So to ditch our 5 years support model, kick the code out of the tree and > > make the users suffer? The support model is suppose to

Re: What is evdev and autoloading?

On Mon, Feb 18, 2019 at 09:11:14AM -0700, Warner Losh wrote: > > You do know these constant complaints about people trying to make things > better is demoralizing and counter productive. > You do realize some of the emails are from frustrated users who are trying to make FreeBSD (see for example

Re: What is evdev and autoloading?

On Mon, Feb 18, 2019 at 09:58:14AM -0700, Ian Lepore wrote: > On Mon, 2019-02-18 at 08:50 -0800, Steve Kargl wrote: > > On Mon, Feb 18, 2019 at 09:11:14AM -0700, Warner Losh wrote: > > > > > > You do know these constant complaints about people trying to make &

Re: What is evdev and autoloading?

On Mon, Feb 18, 2019 at 09:35:26AM -0700, Warner Losh wrote: > On Sun, Feb 17, 2019 at 3:52 PM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > Anyone have insight into what evdev is? There appears to > > be no manual page. When I reboot a system

Re: What is evdev and autoloading?

On Tue, Feb 19, 2019 at 08:17:48AM -0800, Cy Schubert wrote: > On February 18, 2019 9:17:37 AM PST, Pete Wright wrote: > > > > > >On 2/18/19 8:50 AM, Rodney W. Grimes wrote: > >>> On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes < > >>> > >>> I don't know. I think the fact that drm2 doesn't suppor

Re: What is evdev and autoloading?

On Tue, Feb 19, 2019 at 06:59:26PM +, Johannes Lundberg wrote: > > On 2/19/19 5:35 PM, Steve Kargl wrote: >> On Tue, Feb 19, 2019 at 08:17:48AM -0800, Cy Schubert wrote: >>> >>> Drm2 is not required. My current laptop is 5 years old, an HD3000. The >>

r343567 aka PAE vs non-PAE merge breaks i386 freebsd

r343567 merges the PAE vs non-PAE pmap headers for i386 freebsd. After bisection and dealing with the drm-legacy-kmod fallout, I bisected /usr/src to r343567. Building world and a GENERIC kernel and the minimum set of ports to start Xorg on my Dell Latitude D530 laptop, results in a black screen

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Thu, Feb 21, 2019 at 07:39:25PM -0800, Steve Kargl wrote: > r343567 merges the PAE vs non-PAE pmap headers for i386 > freebsd. After bisection and dealing with the drm-legacy-kmod > fallout, I bisected /usr/src to r343567. Building world and > a GENERIC kernel and the minimum set

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Thu, Feb 21, 2019 at 10:04:10PM -0800, Steve Kargl wrote: > On Thu, Feb 21, 2019 at 07:39:25PM -0800, Steve Kargl wrote: > > r343567 merges the PAE vs non-PAE pmap headers for i386 > > freebsd. After bisection and dealing with the drm-legacy-kmod > > fallout, I bisecte

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Sat, Feb 23, 2019 at 11:19:31AM +0200, Konstantin Belousov wrote: > On Fri, Feb 22, 2019 at 07:26:44PM -0800, Steve Kargl wrote: > > On Thu, Feb 21, 2019 at 10:04:10PM -0800, Steve Kargl wrote: > > > On Thu, Feb 21, 2019 at 07:39:25PM -0800, Steve Kargl wrote: > > >

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Sat, Feb 23, 2019 at 08:32:23AM -0800, Conrad Meyer wrote: > On Sat, Feb 23, 2019 at 12:44 AM Steve Kargl > wrote: > > Ideas? > > ... > > +CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (1995.04-MHz > > 686-class CPU) > >Origin="Genui

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Sat, Feb 23, 2019 at 01:22:28PM +0300, Vladimir Kondratyev wrote: > On 2019-02-22 09:04, Steve Kargl wrote: > > > > Ideas? > > Place hw.above4g_allow=0 into /boot/loader.conf? > Tried that. sysctl -a does not report hw.above4g_allowed, so have no id

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Sat, Feb 23, 2019 at 12:03:58PM -0700, Warner Losh wrote: > On Sat, Feb 23, 2019 at 10:57 AM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > Supposely, the laptop only has 4 GB of memory. Not sure how > > it finds memory above 4 GB. > > > &

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Sun, Feb 24, 2019 at 10:06:53AM -0700, Warner Losh wrote: > > > > Maybe I missed it, but Steve, did you run the patched in a different way > tests that I suggested? Replacing the limits with 0x for testing > purposes to ensure that drm isn't saying it can cope with larger addresses? > T

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Sun, Feb 24, 2019 at 10:06:53AM -0700, Warner Losh wrote: > On Sun, Feb 24, 2019 at 2:27 AM Tijl Coosemans wrote: > > > On Sat, 23 Feb 2019 17:28:51 -0800 Steve Kargl > > wrote: > > > On Sat, Feb 23, 2019 at 12:03:58PM -0700, Warner Losh wrote: > > >>

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Sun, Feb 24, 2019 at 10:27:26AM +0100, Tijl Coosemans wrote: > On Sat, 23 Feb 2019 17:28:51 -0800 Steve Kargl > wrote: > > On Sat, Feb 23, 2019 at 12:03:58PM -0700, Warner Losh wrote: > >> On Sat, Feb 23, 2019 at 10:57 AM Steve Kargl > >> wrote: > >>&

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Thu, Feb 28, 2019 at 09:09:38AM -0800, John Baldwin wrote: > On 2/23/19 8:39 AM, Steve Kargl wrote: > > On Sat, Feb 23, 2019 at 08:32:23AM -0800, Conrad Meyer wrote: > >> On Sat, Feb 23, 2019 at 12:44 AM Steve Kargl > >> wrote: > >>> Ideas? > >

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Thu, Feb 28, 2019 at 11:14:51AM -0800, Cy Schubert wrote: > On February 28, 2019 11:06:46 AM PST, Conrad Meyer wrote: > >On Thu, Feb 28, 2019 at 10:32 AM Steve Kargl > > wrote: > >> This is interesting as well. Does this mean that amd64 is now > >> the o

Optimization bug with floating-point?

All, There seems to an optimization bug with clang on % uname -a FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT r344653 MOBILE i386 IOW, if you do numerica work on i386, you may want to check your results. The program demonstrating the issue is at the end of this email. gcc8 --version gcc8

Re: Optimization bug with floating-point?

On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote: > All, > > There seems to an optimization bug with clang on > > % uname -a > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT r344653 MOBILE i386 > > IOW, if you do numerica work on i386, you may want

Re: Optimization bug with floating-point?

On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote: > > cc -O -fno-builtin -o z a.c -lm && ./z > cc -O2 -fno-builtin -o z a.c -lm && ./z > cc -O3 -fno-builtin -o z a.c -lm && ./z > > > Max ULP: 23.061242 > Count: 39 (# of ULP tha

Re: Optimization bug with floating-point?

On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote: > > gcc8 --version > gcc8 (FreeBSD Ports Collection) 8.3.0 > > gcc8 -fno-builtin -o z a.c -lm && ./z > gcc8 -O -fno-builtin -o z a.c -lm && ./z > gcc8 -O2 -fno-builtin -o z a.c -lm && ./

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 04:41:51PM +0100, Hans Petter Selasky wrote: > On 3/13/19 4:16 PM, Steve Kargl wrote: > > On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote: > >> > >> gcc8 --version > >> gcc8 (FreeBSD Ports Collection) 8.3.0 > >&g

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 04:56:26PM +0100, Hans Petter Selasky wrote: > On 3/13/19 4:50 PM, Steve Kargl wrote: > > Using sin() and cos() directly as in > > > > /* Double precision csinh() without using C's double complex.s */ > > void > > dp_csinh(doub

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 09:32:57AM -0700, John Baldwin wrote: > On 3/13/19 8:16 AM, Steve Kargl wrote: > > On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote: > >> > >> gcc8 --version > >> gcc8 (FreeBSD Ports Collection) 8.3.0 > >> > >&

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 10:16:12AM -0700, John Baldwin wrote: > On 3/13/19 9:40 AM, Steve Kargl wrote: > > On Wed, Mar 13, 2019 at 09:32:57AM -0700, John Baldwin wrote: > >> On 3/13/19 8:16 AM, Steve Kargl wrote: > >>> On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve K

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 10:40:28AM -0700, Conrad Meyer wrote: > Hi John, > > On Wed, Mar 13, 2019 at 10:17 AM John Baldwin wrote: > > One issue I'm aware of is that clang does not have any support for the > > special arrangement FreeBSD/i386 uses where it uses different precision > > for register

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 10:16:12AM -0700, John Baldwin wrote: > On 3/13/19 9:40 AM, Steve Kargl wrote: > > On Wed, Mar 13, 2019 at 09:32:57AM -0700, John Baldwin wrote: > >> On 3/13/19 8:16 AM, Steve Kargl wrote: > >>> On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve K

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 02:24:55PM -0700, Steve Kargl wrote: > On Wed, Mar 13, 2019 at 10:16:12AM -0700, John Baldwin wrote: > > On 3/13/19 9:40 AM, Steve Kargl wrote: > > > On Wed, Mar 13, 2019 at 09:32:57AM -0700, John Baldwin wrote: > > >> On 3/13/19 8:16 AM, Ste

Re: Optimization bug with floating-point?

On Wed, Mar 13, 2019 at 11:30:07PM -0700, Steve Kargl wrote: > > Spent a couple hours wandering in contrib/llvm. Have no idea > how to fix clang to actually work on i386/387. Any ideas > would be welcomed. > > AFAICT, all libm float routines need to be modified to con

Re: Optimization bug with floating-point?

On Fri, Mar 15, 2019 at 05:50:37AM +1100, Peter Jeremy wrote: > On 2019-Mar-13 23:30:07 -0700, Steve Kargl > wrote: > >AFAICT, all libm float routines need to be modified to conditional > >include ieeefp.h and call fpsetprec(FP_PD). This will work around > >issues is FP

Re: Optimization bug with floating-point?

On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote: > All, > > There seems to an optimization bug with clang on > > % uname -a > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT r344653 MOBILE i386 > > IOW, if you do numerica work on i386, you may want to che

Re: Heads up for breaking drm update.

On Sun, May 19, 2019 at 02:50:54PM -0700, Johannes Lundberg wrote: > > LinuxKPI in base have received a lot of updates recently for Linux 5.0, > a couple of them will break drm-current-kmod. So, as of r347973 you will > need drm-current-kmod 4.16.g20190519. Ports have been updated and new > packag

Re: Heads up for breaking drm update.

On Sun, May 19, 2019 at 08:21:18PM -0700, Johannes Lundberg wrote: > > On 5/19/19 7:36 PM, Steve Kargl wrote: > > On Sun, May 19, 2019 at 02:50:54PM -0700, Johannes Lundberg wrote: > >> LinuxKPI in base have received a lot of updates recently for Linux 5.0, > >> a

Someone broke USB

Updated a month old FreeBSD-current to top of tree. Upon rebooting, the usb no longer functions. No usb mouse. No usb external hard drive. Unplugging and then re-plugging in external drive does not cause the drive to spin up. Logged in as root.` % usbconfig list No device match or lack of perm

Re: Someone broke USB

On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote: > On 2019-07-06 20:23, Steve Kargl wrote: > > So, how does one get usb working, again? > > > > -- Steve > > Can you show dmesg? > This is dmesg.boot for the kernel with the non-functioning US

Re: Someone broke USB

On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote: > On 2019-07-06 20:23, Steve Kargl wrote: > > So, how does one get usb working, again? > > > > -- Steve > > Can you show dmesg? > It looks like the enumeration of busses and devices has changed.

Re: Someone broke USB

On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > On 2019-07-06 21:41, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-06 20:23, Steve Kargl wrote: > >>> So, how does one get usb workin

Re: Someone broke USB

On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > > > On 2019-07-06 21:41, Steve Kargl wrote: > > > > On Sat, Jul 06, 2019 at

Re: Someone broke USB

On Sat, Jul 06, 2019 at 04:14:53PM -0700, Steve Kargl wrote: > On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > > > > It seems almost certain to be r349161 that causes the problem. > > > > I've backed out the change, and the buildkernel is currently

Re: Someone broke USB

On Sun, Jul 07, 2019 at 11:53:27AM +0200, Hans Petter Selasky wrote: > On 2019-07-07 10:05, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 04:14:53PM -0700, Steve Kargl wrote: > >> On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > >>> > >>>

Re: Someone broke USB

On Sun, Jul 07, 2019 at 08:27:18PM +0200, Hans Petter Selasky wrote: > On 2019-07-07 18:58, Hans Petter Selasky wrote: > > On 2019-07-07 18:54, Steve Kargl wrote: > >> This a 7720 line, 262KB file, do you want me to send it > >> to you in private email or put in my home

Re: Someone broke USB

On Sun, Jul 07, 2019 at 09:10:00PM +0200, Hans Petter Selasky wrote: > On 2019-07-07 20:58, Steve Kargl wrote: > > I assume the pause goes after "max--;" statement. I also > > assume you want the info with the sysctl removed from > > /boot/loader.conf. > &

Re: Someone broke USB

On Sun, Jul 07, 2019 at 10:46:10PM +0200, Hans Petter Selasky wrote: > On 2019-07-07 22:36, Steve Kargl wrote: > > On Sun, Jul 07, 2019 at 09:10:00PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-07 20:58, Steve Kargl wrote: > >>> I assume the pause goes aft

Re: Someone broke USB

On Mon, Jul 08, 2019 at 11:50:31AM +0200, Hans Petter Selasky wrote: > Hi Steve, > > Can you test this patch? > > I made a slight variant which delay the explore threads instead of the > main thread running all the sysinits. > > --HPS With this patch, the kernel does not find any USB devices.

Re: Someone broke USB

On Mon, Jul 08, 2019 at 07:09:39PM +0200, Hans Petter Selasky wrote: > On 2019-07-08 19:03, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 11:50:31AM +0200, Hans Petter Selasky wrote: > >> Hi Steve, > >> > >> Can you test this patch? > >> > &g

Re: Someone broke USB

On Mon, Jul 08, 2019 at 10:24:14AM -0700, Steve Kargl wrote: > On Mon, Jul 08, 2019 at 07:09:39PM +0200, Hans Petter Selasky wrote: > > On 2019-07-08 19:03, Steve Kargl wrote: > > > On Mon, Jul 08, 2019 at 11:50:31AM +0200, Hans Petter Selasky wrote: > > >> Hi Ste

Re: Someone broke USB

On Mon, Jul 08, 2019 at 09:08:17PM +0200, Hans Petter Selasky wrote: > Hi Steve, > > Can you revert all prior patches and try this one instead. > With the new patch, none of the USB devices are found. I'll be away from the laptop for a few hours. -- Steve __

vm_page_hold() and drm-legacy-kmod

It seems the recent flurry of vm commits has broken the graphics/drm-legacy-kmod port. vm_page_hold() no longer exists. How do I fix the port? -- Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-curr

Re: vm_page_hold() and drm-legacy-kmod

On Mon, Jul 08, 2019 at 09:31:12PM -0700, Steve Kargl wrote: > It seems the recent flurry of vm commits has > broken the graphics/drm-legacy-kmod port. > vm_page_hold() no longer exists. How do I > fix the port? > Whoops. The missing function is vm_page_unhold(). Anywhoo, ho

Re: Someone broke USB

On Mon, Jul 08, 2019 at 10:54:24PM +0200, Hans Petter Selasky wrote: > On 2019-07-08 22:08, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 09:08:17PM +0200, Hans Petter Selasky wrote: > >> Hi Steve, > >> > >> Can you revert all prior patches and try this one

Re: vm_page_hold() and drm-legacy-kmod

On Mon, Jul 08, 2019 at 09:35:05PM -0700, Steve Kargl wrote: > On Mon, Jul 08, 2019 at 09:31:12PM -0700, Steve Kargl wrote: > > It seems the recent flurry of vm commits has > > broken the graphics/drm-legacy-kmod port. > > vm_page_hold() no longer exists. How

Re: vm_page_hold() and drm-legacy-kmod

On Mon, Jul 08, 2019 at 09:43:36PM -0700, Steve Kargl wrote: > On Mon, Jul 08, 2019 at 09:35:05PM -0700, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 09:31:12PM -0700, Steve Kargl wrote: > > > It seems the recent flurry of vm commits has > > > broken the gr

Re: vm_page_hold() and drm-legacy-kmod

On Tue, Jul 09, 2019 at 01:43:42AM -0400, Mark Johnston wrote: > On Mon, Jul 08, 2019 at 10:04:00PM -0700, Steve Kargl wrote: > > > > This was broken by r349846 committed by markj. > > Please try this patch. If it works for you I will submit a pull request > to the drm-

Re: Someone broke USB

On Tue, Jul 09, 2019 at 10:19:55AM +0200, Niclas Zeising wrote: > On 2019-07-09 06:33, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 10:54:24PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-08 22:08, Steve Kargl wrote: > >>> On Mon, Jul 08, 2019 at 09:08:17PM +0

Re: vm_page_hold() and drm-legacy-kmod

On Mon, Jul 08, 2019 at 10:57:41PM -0700, Steve Kargl wrote: > On Tue, Jul 09, 2019 at 01:43:42AM -0400, Mark Johnston wrote: > > On Mon, Jul 08, 2019 at 10:04:00PM -0700, Steve Kargl wrote: > > > > > > This was broken by r349846 committed by markj. > > > &

drm-legacy is broken, again

Just updated /usr/src to top of tree. Trying to update drm-legacy port. After a failed 'make' in /usr/ports/drm-legacy % make |& tee drm.txt % tail drm.txt ===> drm2/drm2 (all) Warning: Object directory not changed from original /usr/ports/graphics/drm-legacy-kmod/work/drm-legacy-990f64b/drm2/

Re: drm-legacy is broken, again

On Thu, Aug 01, 2019 at 03:22:27PM -0400, Mark Johnston wrote: > On Thu, Aug 01, 2019 at 12:10:09PM -0700, Steve Kargl wrote: > > Just updated /usr/src to top of tree. > > > > Trying to update drm-legacy port. After > > a failed 'make' in /usr/ports/drm-lega

Re: drm-legacy is broken, again

On Thu, Aug 01, 2019 at 03:31:15PM -0400, Mark Johnston wrote: > On Thu, Aug 01, 2019 at 12:30:24PM -0700, Steve Kargl wrote: > > On Thu, Aug 01, 2019 at 03:22:27PM -0400, Mark Johnston wrote: > > > On Thu, Aug 01, 2019 at 12:10:09PM -0700, Steve Kargl wrote: > > > >

Working ath10k device?

I have a Dell XPS 13 that reports the wifi chip is a Qualcomm Atheros 6147. I've found Adrain's WIP driver, and built it. I'm seeing the panic reported at https://lists.freebsd.org/pipermail/freebsd-current/2019-February/072769.html Does anyone have a /dev/if_athp.ko and firmware? -- Steve __

Re: FUSE Call for Testing

On Thu, Aug 08, 2019 at 12:34:52PM -0600, Alan Somers wrote: > The new FUSE driver has just landed in current. It raises the protocol > level from 7.8 to 7.23, fixes many bugs, adds a test suite for the > driver, and adds many new features. New features include: Thanks for sharing your work! --

Re: HEADSUP: drm-current-kmod now installs sources

On Wed, Aug 14, 2019 at 06:40:28PM -0400, Daniel Eischen wrote: > I've lost the original thread, but would the sources in > /usr/local/sys/modules get built regardless of what > MAKEOBJDIRPREFIX is? And, now that sources may be installed > by a port, what is the method for _just_ updating the sour

Re: Working ath10k device?

On Wed, Aug 21, 2019 at 10:39:33PM -0400, Anthony Jenkins wrote: > On 8/2/19 6:19 PM, Steve Kargl wrote: > > I have a Dell XPS 13 that reports the wifi chip is > > a Qualcomm Atheros 6147. I've found Adrain's WIP > > driver, and built it. I'm seeing the

radeon panics kernels

troutmask.apl.washington.edu dumped core - see /var/crash/vmcore.7 Wed Oct 2 14:12:38 PDT 2019 FreeBSD troutmask.apl.washington.edu 13.0-CURRENT FreeBSD 13.0-CURRENT r352812 HPC amd64 panic: page fault Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 10 fault virtual addre

Re: radeon panics kernels

On Thu, Oct 03, 2019 at 09:17:32AM +0200, Hans Petter Selasky wrote: > On 2019-10-02 23:19, Steve Kargl wrote: > > troutmask.apl.washington.edu dumped core - see /var/crash/vmcore.7 > > > > Wed Oct 2 14:12:38 PDT 2019 > > > > This looks like a simple NULL poi

Re: radeon panics kernels

On Thu, Oct 03, 2019 at 05:59:20AM -0700, Steve Kargl wrote: > On Thu, Oct 03, 2019 at 09:17:32AM +0200, Hans Petter Selasky wrote: > > On 2019-10-02 23:19, Steve Kargl wrote: > > > troutmask.apl.washington.edu dumped core - see /var/crash/vmcore.7 > > > > &g

Re: radeon panics kernels

On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > On 2019-10-03 14:59, Steve Kargl wrote: > > On Thu, Oct 03, 2019 at 09:17:32AM +0200, Hans Petter Selasky wrote: > >> On 2019-10-02 23:19, Steve Kargl wrote: > >>> troutmask.apl.washington.ed

Re: radeon panics kernels

On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > > If you leave the port debug knob for drm-current-kmod AS-IS, I think you > can get away with: > > make DEBUG_FLAGS="-g" > > Then re-load the vmcore file in GDB/KGDB from ports (!) and add the > symbol files for the module

Re: radeon panics kernels

On Thu, Oct 03, 2019 at 11:52:38PM +0200, Hans Petter Selasky wrote: > On 2019-10-03 22:26, Steve Kargl wrote: > > On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > >> > >> If you leave the port debug knob for drm-current-kmod AS-IS, I think

Re: radeon panics kernels

On Thu, Oct 03, 2019 at 11:52:38PM +0200, Hans Petter Selasky wrote: > On 2019-10-03 22:26, Steve Kargl wrote: > > On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > >> > >> If you leave the port debug knob for drm-current-kmod AS-IS, I think

Re: radeon panics kernels

On Fri, Oct 04, 2019 at 12:17:30PM -0700, Johannes Lundberg wrote: > On Fri, Oct 4, 2019 at 11:39 Steve Kargl > wrote: > > > On Thu, Oct 03, 2019 at 11:52:38PM +0200, Hans Petter Selasky wrote: > > > On 2019-10-03 22:26, Steve Kargl wrote: > > > > > >

Someone broke buildworld with ZFS commit!

In file included from /usr/src/cddl/contrib/opensolaris/lib/libzfs_core/common/libzfs_core.c:89: In file included from /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zfs_ioctl.h:35: In file included from /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dsl_deleg.h:30: In

Re: Someone broke buildworld with ZFS commit!

On Tue, Oct 15, 2019 at 09:44:12AM -0700, Steve Kargl wrote: > In file included from > /usr/src/cddl/contrib/opensolaris/lib/libzfs_core/common/libzfs_core.c:89: > In file included from > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zfs_ioctl.h:35: > In file includ

[PATCH] Typo in libm code

This patch https://cvsweb.openbsd.org/src/lib/libm/src/ld80/k_sincosl.h?sortby=date is applicable to FreeBSD. Index: src/k_sincosl.h === --- src/k_sincosl.h (revision 353571) +++ src/k_sincosl.h (working copy) @@ -28,8 +28,8

<    1   2   3   4   5   6   7   8   9   10   >