SIGSEGV in lots of processes (head i386 @r237440)

Just updated my laptop's head slice from r237378 to r237440; while it did manage to get to multi-user mode, I was only able to login as root, and whenever I tried to do much of anything, the sell (csh) exited with a SIGSEGV. I finally gave it a "3-fingered salute", [Ctl-Alt-Del], and init appeared

Re: SIGSEGV in lots of processes (head i386 @r237440)

On Fri, Jun 22, 2012 at 06:22:16PM +0300, Konstantin Belousov wrote: > ... > > > found at . > > This is on i386, right ? Yes. > > Can you boot single-user and just type date in the shell ? > > Does it segfault ? > > > > If yes, does setting sysctl kern

"ifconfig create" breaks between r238227 - r238290?

Just finished updating from r238227 to r238290 on the "head" slice of my laptop, and was unable to make use of the wlan(4) NIC; I captured the following via cut/paste from ttyv0: ... Setting hostname: localhost. Starting dhclient. em0: no link .. giving up /etc/rc.d/dhclient: WARNING:

Re: "ifconfig create" breaks between r238227 - r238290?

On Tue, Jul 10, 2012 at 06:50:57PM -0700, Garrett Cooper wrote: > On Tue, Jul 10, 2012 at 6:38 PM, Brandon Gooch > wrote: > > ... > > > Same thing here, and I tracked it down to r238279: > > > > http://svnweb.freebsd.org/base?view=revision&revision=238279 > > > > Not yet sure why though, looking

Re: "ifconfig create" breaks between r238227 - r238290?

On Tue, Jul 10, 2012 at 07:15:21PM -0700, Garrett Cooper wrote: > ... > Curious. I was wondering about this because there's some logic in > network.subr that parses ifconfig -l output -- thinking that the > fallout might have been there. > I would be curious next to see what devd is trying to execu

Re: "ifconfig create" breaks between r238227 - r238290?

On Tue, Jul 10, 2012 at 07:36:09PM -0700, Garrett Cooper wrote: > .. > > Well, devd wasn't particularly happy about that: > ... > My bad -- I misread the manpage. > > This will work better probably: > > notify 0 { > match "system" "IFNET"; > match "type" "LINK_UP"; > media-type

Re: "ifconfig create" breaks between r238227 - r238290?

On Wed, Jul 11, 2012 at 12:01:01PM +0900, Hiroki Sato wrote: > ... > hr> Gr, it may be due to my change of r238279. I am investigating it. > > Committed a fix as r238361. Please try it. And we have a winner! Thank you! :-) [Sorry for the delay; I had already updated my sources to r238345 e

Re: svn commit: r238361 - head/sys/dev/usb

On Wed, Jul 11, 2012 at 12:46:40PM -0700, Adrian Chadd wrote: > Hi, > > What was the original commit which broke wlan name matching? > > I can't see how a commit to usb_pf.c would "fix" this. > ... r238279 Peace, david -- David H. Wolfskill da...@catwhisker.org Dep

panic: _mtx_lock_sleep: recursed on non-recursive mutex em0 @ /usr/src/sys/dev/e1000/if_lem.c:881

This is at r238795; cut/paste of backtrace: KDB: enter: panic [ thread pid 12 tid 100026 ] Stopped at kdb_enter+0x3d: movl$0,kdb_why db> bt Tracing pid 12 tid 100026 td 0xc6755000 kdb_enter(c0f93c5f,c0f93c5f,c0f91e21,f08398f0,c1825c80,...) at kdb_enter+0x3d panic(c0f91e21,c66739a0,c0f20db

Re: post SVN r238886 no boot?

On Sun, Jul 29, 2012 at 11:39:14AM -0700, Garrett Cooper wrote: > ... > >> What was the previous version you booted and what's your configuration? > >> Thanks, > >> -Garrett > > > > I'm on an x86 core duo laptop with a single SATA disk split between > > Windoze-7 and FreeBSD. Nothing really spe

Re: [clang] kernel build failure

On Thu, Aug 09, 2012 at 04:15:36PM +0400, Boris Samorodov wrote: > Hi! > > The kernel build fails at fresh CURRENT... > And then I get an error: > - > linking kernel.debug > cam_periph.o: In function `cam_periph_error': > /usr/src/sys/cam/cam_periph.c:1776: undefined reference to > `scsi_extr

Re: What happened to nslookup?

On Fri, Oct 11, 2013 at 10:10:26PM +, Thomas Mueller wrote: > ... > Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one > supposed to use in its place? > Use "host." nslookup was part of BIND, and has been deprecated for years (IIRC). Peace, david -- David H. Wo

Re: What happened to nslookup?

On Sat, Oct 12, 2013 at 02:14:28AM +, Thomas Mueller wrote: > ... > Thanks for info! Glad to help. > I saw that bind was removed from the current branch because of security > problems, It was removed, but I believe that there was a bit more to it than "security problems." > but didn't know

panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

I saw this on my "build machine" after updating the "head" slice from: FreeBSD 11.0-CURRENT #1387 r260875M/260877:115: Sun Jan 19 11:57:25 PST 2014 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/GENERIC i386 to FreeBSD 11.0-CURRENT #1388 r260904M/260904:115: Mon Jan 20

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

On Mon, Jan 20, 2014 at 06:37:50PM +0200, Konstantin Belousov wrote: > ... > You do not have option WITNESS_SKIPSPIN in your kernel config, do you ? It was a GENERIC kernel for i386; it has WITNESS_SKIPSPIN. On Mon, Jan 20, 2014 at 10:14:08AM -0700, Ian Lepore wrote: > ... > Since you mention ser

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

On Mon, Jan 20, 2014 at 10:33:41AM -0800, David Wolfskill wrote: > ... > On Mon, Jan 20, 2014 at 10:47:12AM -0700, Warner Losh wrote: > > ... > > I have a fix for this. I committed the wrong version of uart_core.c. > > r260911 should fix this. So this is bro

[PATCH] Re: svn commit: r262439 - head/sys/dev/usb/input

I encountered an error during buildkernel: ... ===> usb/atp (all) --- atp.o --- clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /common/S4/obj/usr/src/sys/CANARY/opt_global.h -I. -I@ -I@/contrib/altq -fno-common -gdwarf-2 -I/

Re: sendmail Broken Pipe Error

On Mon, Mar 24, 2014 at 02:36:34PM +0100, Willy Offermans wrote: > ... > Since there is a timeout error, I like to know what sendmail is writing to > MyProvider.com > > Is there a way to debug sendmail to disclose the message written to > MyProvider.com and the response from MyProvider.com. I'm pr

Boot fails @r264070

Building/installing is fine, and building, installing, and booting stable/9 @r264061 on the same hardware (different slice) is fine. (I didn't rebuild stable/10 this morning, asth only change was to src/cddl/contrib/opensolaris/cmd/zpool/zpool_main.c, and I don't use ZFS. stable/10 works fine on

Re: Boot fails @r264070

On Thu, Apr 03, 2014 at 12:06:51PM -0400, Benjamin Kaduk wrote: > ... > I'm also having some trouble booting (into single user mode, so as to run > the installworld), at r264039 Sympathy > That would seem to indicate some hardware problem or > timing issues more than a problem with the

Re: svn commits r264007-264011: disks missing

On Thu, Apr 03, 2014 at 07:23:57PM +0300, Konstantin Belousov wrote: > ... > I think verbose dmesg from failing and running kernel should be good > for the start. contains: [TXT] boot_diff.txt 03-Apr-2014 09:55 15K [TXT] boot_fail.

Re: error during buildworld

On Fri, Jun 06, 2014 at 01:53:54PM -0400, Robert Huff wrote: > Hello: > On a system running: > > FreeBSD 11.0-CURRENT #1 r264673: Sat Apr 19 09:43:10 EDT 2014 amd64 > > and with the source updated at midnight US EST, running "make > buildworld" > produces: > ... > cc -O2 -pipe -gdw

Re: wlan0/iwn: no upload statistics

On Sat, Jun 07, 2014 at 08:39:10PM +0800, bycn82 wrote: > Hi, > > More information is required. Please provide the output of the two commands > below > > 1. sysctl -a | grep octets > 2. uname -a > ... I'm not the OP, but I do (sometimes) run head, and have an iwn(4) NIC on my la

Re: iwn driver issue

On Fri, Jun 13, 2014 at 06:36:44PM +0200, Edward Tomasz Napiera??a wrote: > On 0613T1126, Stefan Parvu wrote: > > Hi, > > > > Im running FreeBSD current: > > FreeBSD nereid 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r265628: Thu May 8 > > 08:05:37 UTC 2014 > > r...@grind.freebsd.org:/usr/obj/usr/

Re: iwn driver issue

On Fri, Jun 13, 2014 at 12:34:00PM -0500, Adrian Chadd wrote: > This isn't this first time this has been reported, right? > > I think we may need to back this patch out until it's better resolved. > I normally don't spend a huge amount of time in head -- enough to build it & do a quick smoke

Re: iwn driver issue

On Fri, Jun 13, 2014 at 09:36:35PM +0200, Edward Tomasz Napiera??a wrote: > ... > > I normally don't spend a huge amount of time in head -- enough to build > > it & do a quick smoke-test. So it's certainly possible that it merits > > further exploration. And I'm willing experiment, but I cannot t

Re: [HEADS-UP] Problem with clang in 9-stable [was: r268244 (stable/9) seems to break "sysctl hw.ncpu"]

On Fri, Jul 04, 2014 at 08:09:21PM +0200, Hans Petter Selasky wrote: > Hi, > > Can you try to reproduce this: > > Checkout 9-stable's src/sbin/sysctl only. > > cd /usr/9-stable/src/sbin/sysctl > > env CC=clang make clean all > ./sysctl -n hw.ncpu > > Then: > > env CC=gcc make clean all > ./sy

Re: [HEADS-UP] Problem with clang in 9-stable [was: r268244 (stable/9) seems to break "sysctl hw.ncpu"]

On Sat, Jul 05, 2014 at 01:49:44PM +0100, David Chisnall wrote: > On 4 Jul 2014, at 19:18, David Wolfskill wrote: > > > clang -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector > > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter >

Build machine OK; laptop panics @r269515

I held off until the build machine was able to build & (try to boot) head; unfortunately for me, it had no problems: FreeBSD freebeast.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1571 r269515M/269515:1100028: Mon Aug 4 12:14:39 PDT 2014 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/s

panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515]

On Mon, Aug 04, 2014 at 12:47:59PM -0700, David Wolfskill wrote: > ... > I was unable to get a crash dump, and I only recorded the offsets in the > backtrace (no arguments; sorry -- I was expecting the build machine to > allow me to investigate on a machine with a serial console): &g

Re: panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515]

On Tue, Aug 05, 2014 at 01:02:25PM -0700, John Baldwin wrote: ... > My guess is that the recent Xen changes tickled something. However, can you > capture a verbose dmesg from your working kernel? That was my current hunch, as well. I've attached /var/run/dmesg.boot from a verbose boot running:

Re: panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515]

On Wed, Aug 06, 2014 at 10:48:32PM +0200, Trond Endrestøl wrote: > ... > Reverting r269510 did the trick, i.e.: > > cd /usr/src && svn up && svn diff -r 269510:269509 | patch > > My i386 head VM is running smoothly with r269641M, with M meaning only > the above reversal. > ... Works for me, as

Re: panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515]

On Thu, Aug 07, 2014 at 01:32:45PM +0200, Roger Pau Monné wrote: > ... > I think I've found the issue, but since I'm not able to reproduce it, > could someone try the following patch? (without r269510 reverted). > ... That worked for me; thanks! Peace, david -- David H. Wolfskill

Re: i386 compilation errors in head/sys/dev/ixl/if_ixl.c

On Fri, Aug 29, 2014 at 12:55:40PM +, Bjoern A. Zeeb wrote: > > On 29 Aug 2014, at 12:02 , Steven Hartland wrote: > > > Looks like this was already fixed by: > > http://svnweb.freebsd.org/changeset/base/270799 > > Yes, just before I closed the bugreport. > > There?s a few more follow-up co

Re: r248093: Kernel build failure: /usr/src/sys/net80211/ieee80211_output.c:600:23: error: unused variable 'ic' [-Werror,-Wunused-variable]

On Sat, Mar 09, 2013 at 11:59:21AM +0100, Hartmann, O. wrote: > On CURRENT, r248093, build of kernel fails due to the below shown error. > > [...] > > cc -c -O3 -O3 -Wno-error=unused-variable -fno-strict-aliasing > ... > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror >

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

On Sat, Mar 09, 2013 at 06:06:05PM +0100, Hartmann, O. wrote: > ... > No, it isn't. Same error, system is at revision: > FreeBSD 10.0-CURRENT #1 r248106: Sat Mar 9 16:44:58 CET 2013 amd64 > > The error is the same. > ... Please see the message I posted to ports@, a copy of which may be found at

Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

Yesterday, I built head & ran it without incident (as has been the daily norm for some time now): FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #843 r248493M/248493: Tue Mar 19 05:57:09 PDT 2013 r...@g1-235.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 Today, after upd

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote: > ... > > I'm open to suggestions, and willing to hack and test (and report, > > of course). > > Did you rebuild the nvidia driver after the update ? Yes; src.conf includes the line: PORTS_MODULES=x11/nvidia-driver > Do you ha

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote: > ... > Did you rebuild the nvidia driver after the update ? > Do you have a core dump partition configured ? (I note that I have, in the past, captured crash dumps from head running on this machine with this configuration.) > T

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Wed, Mar 20, 2013 at 07:24:30PM +0200, Andriy Gapon wrote: > on 20/03/2013 19:18 David Wolfskill said the following: > > Yes; src.conf includes the line: > > > > PORTS_MODULES=x11/nvidia-driver > > Have you double-checked that this actually works according to you

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote: > ... > > I then started xdm, and (as before), got an unclean reboot. (So: no > > difference in behavior as far as I can tell.) > > Ok. The best idea I have right now is to rebuild the nvidia.ko. Again? OK > Do you have a

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote: > ... > Ok. The best idea I have right now is to rebuild the nvidia.ko. OK; I did this: After rebooting (without attempting to either load nvidia.ko or start X in any way), I issued: sudo portmaster x11/nvidia-driver wh

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Wed, Mar 20, 2013 at 10:08:57PM +0200, Konstantin Belousov wrote: > ... > I looked at the nvidia sources to check that the driver does not use > the interfaces which KBI was changed, and this is indeed the case, as > expected. OK; thank you for checking & reporting. > I must admit that I have

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Wed, Mar 20, 2013 at 10:08:57PM +0200, Konstantin Belousov wrote: > ... > I looked at the nvidia sources to check that the driver does not use > the interfaces which KBI was changed, and this is indeed the case, as > expected. > > I must admit that I have no idea why buffer cache changes could

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Thu, Mar 21, 2013 at 10:04:41AM +0200, Konstantin Belousov wrote: > ... > This gives me an idea. The only so to say 'vm' change in r248508 was an > addition of the bio_transient_map submap. The vfs.unmapped_buf_allowed > tunable did not eliminated the submap creation. Please try r248569 > with v

Re: Silent reboots in head @r248550 starting xdm with x11/nvidia-driver

On Thu, Mar 21, 2013 at 03:58:35PM +0200, Konstantin Belousov wrote: > ... > > Script started on Thu Mar 21 06:07:41 2013 > > g1-235(10.0-C)[1] uname -a > > FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #845 > > r248575M/248575: Thu Mar 21 05:35:06 PDT 2013 > > r...@g1-235.

Re: poweroff (shutdown -p) is broken

On Wed, Apr 03, 2013 at 01:15:03AM +0200, deeptech71 wrote: > As of r248872, my system, when ordered to power off, stalls at the "Uptime: > [...]" message. Before that revision, the "Uptime" message would be followed > by several additional messages -- something related to "usb controllers" -- >

panic during transition to multi-user mode @r249303 [i386]

I saw this first on my laptop; backtrace mentioned something about iwn(4), so after I saved the crash dump, I flippe dthe wireless switch off and tried again... and got a different (but undoubtedly related) panic, which I also saved. Then, after my build machine finished, that also got a panic (us

Re: panic during transition to multi-user mode @r249303 [i386]

On Tue, Apr 09, 2013 at 08:59:39PM +0300, Konstantin Belousov wrote: > ... > This is hopefully fixed by r249314. After hand-applying that change, re-building & re-installing the kernel on my build machine, it is able to make the transition to multi-user mode without issue. Now running: FreeBSD f

Re: Last commit to HEAD

On Mon, Apr 15, 2013 at 09:48:20PM -0400, Outback Dingo wrote: > Okay I must be loosing it since the change over to svn, and loosing cvsup > > where can i find the last commit to HEAD ? A couple of Web-oriented sources of information: * , w

Re: Stack Overflow in GEOM

On Tue, Apr 16, 2013 at 10:56:31AM -0700, Cy Schubert wrote: > Has anyone see this before? Just updated my CURRENT partitions on my > testbed and laptop. The laptop just boots but I've managed to capture this > on my testbed (attached to a serial port on another system). > > This is HEAD from ye

Re: Stack Overflow in GEOM

On Tue, Apr 16, 2013 at 01:01:49PM -0700, Jim Harris wrote: > ... > > I had built head @r249538 this morning, and that's the build where > > my smoke-test failed. > > > > > This stack trace corruption was noted on svn-src-head@ as well, and appears > to be fixed with r249564. > Cool; thanks -

Re: panic when booting HEAD on i386

On Sat, Apr 20, 2013 at 10:52:35PM +0800, Ganbold Tsagaankhuu wrote: > Hi, > > I'm trying to boot HEAD after updating, but unfortunately it panics with > following message: > > panic: kmem_suballoc: bad status return of 3. > > I was only able to get image of the panic. > > http://www.mnbsd.org/

Re: Current r250174 repeatable panic

On Thu, May 02, 2013 at 05:10:43PM +0400, Andrey Smagin wrote: > Today current paniced after some minutes of network load. Kernel conf is > GENERIC with added ROUTETABLES=16 option. Screenshoots > http://vvtlan.ru/panic1.jpg http://vvtlan.ru/panic2.jpg . > ... I was able to build & boot: FreeBS

Re: openjdk6 broken on current

On Wed, May 08, 2013 at 11:52:24AM -0500, Larry Rosenman wrote: > ... > >Did/can you try just backing out r249606? > ... > How can I generate a patch to do that? > ... (Note that /S4/usr/src is where my "head" sources are on this machine at present.) d129(9.1-S)[5] cd /S4/usr/src d129(9.1-S)[6]

Re: [head tinderbox] failure on i386/i386

On Sun, May 12, 2013 at 11:45:37AM +, FreeBSD Tinderbox wrote: > TB --- 2013-05-12 05:50:18 - tinderbox 2.10 running on > freebsd-current.sentex.ca > TB --- 2013-05-12 05:50:18 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE > FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 >

Re: [head tinderbox] failure on i386/i386

It appears that the issue is i386- (or 32-bit-) specific. On Sun, May 12, 2013 at 07:16:48AM -0700, David Wolfskill wrote: > On Sun, May 12, 2013 at 11:45:37AM +, FreeBSD Tinderbox wrote: > > TB --- 2013-05-12 05:50:18 - tinderbox 2.10 running on > > freebsd-current.sentex.ca

Re: [analyzed] bmake (installed as default make): make: illegal option -- J

On Mon, May 20, 2013 at 01:53:28PM +0400, Boris Samorodov wrote: > 17.05.2013 23:45, Florent Peterschmitt ??: > > ... > > Then install new world, reboot and so: > > > > $ cd /usr/src > > $ make -j4 kernel > > --- buildkernel --- > > make: illegal option -- J > ... > > Can someone help ? >

clang detects error in r250841

Got through buildworld; buildkernel stops a bit abruptly: ... --- ar5416_misc.o --- clang -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-inc

Re: clang detects error in r250841

Just a quick confirmation that reverting r250841 allowed buildkernel to complete normally -- was running: FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #905 r250824M/250824:132: Mon May 20 05:22:58 PDT 2013 r...@g1-227.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY

Panic @r251745; i386, early in boot sequence

Here's a hand-transcribed copy of the backtrace: ... Timecounters tick every 1.000 msec panic: curvnet is NULL cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper(c1034c40,c102a482,c11b646c,c2020cbc,c1037f21,...) at 0xc051283d = db_trace_self_wrapper+0x2d/frame 0xc2020be8 kdb_backtrace(c10863e7

Re: Panic @r251745; i386, early in boot sequence

On Fri, Jun 14, 2013 at 09:35:20AM -0700, David Wolfskill wrote: > Here's a hand-transcribed copy of the backtrace: > > ... > Timecounters tick every 1.000 msec > panic: curvnet is NULL > cpuid = 0 > From looking at code in commits since yesterday's (succes

Panic @r251934: _mtx_lock_sleep: recursed on non-recursive mutex vm map (system) @ /usr/src/sys/vm/vm_kern.c:430

This is on my (i386) build machine; laptop (also i386) did not exhibit the symptom. I had hand-applied r251953 (to get through buildworld). After installworld, mergemaster -i, & "make delete-old", I rebooted, and this is what I saw: ... Booting... GDB: no debug ports present KDB: debugger backe

Re: Panic @r251934: _mtx_lock_sleep: recursed on non-recursive mutex vm map (system) @ /usr/src/sys/vm/vm_kern.c:430

Eh a reboot failed to show evidence of a recurrence. Peace, david (not particularly appreciating computer hardware just now) -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhiske

Re: [head tinderbox] failure on i386/i386

On Tue, Jul 30, 2013 at 07:58:43AM +, FreeBSD Tinderbox wrote: > TB --- 2013-07-30 04:40:20 - tinderbox 2.10 running on > freebsd-current.sentex.ca > TB --- 2013-07-30 04:40:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE > FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 >

Re: CUURENT: make buildworld fails: install: libegacy.a: No such file or directory

On Thu, Aug 01, 2013 at 05:36:53PM +0200, O. Hartmann wrote: > ... > Solving the problem is via deleting > > /usr/src/tools/build/libegacy.a > > This is strange, I wouldn't expect a "on demand created" file > in /usr/src. What happens on boxes were /usr/src is a NFS mount and > read only for bui

Re: CURRENT crashes with nvidia GPU BLOB : vm_radix_insert: key 23c078 is already present

On Fri, Aug 09, 2013 at 07:32:51AM +0200, O. Hartmann wrote: > ... > > > On 8 August 2013 11:10, O. Hartmann > > > wrote: > > > > The most recent CURRENT doesn't work with the x11/nvidia-driver > > > > (which is at 319.25 in the ports and 325.15 from nVidia). > > > > > > > > After build- and insta

Early drop to debugger with DEBUG_MEMGUARD

I first noticed this on my laptop on 08 Aug, after having built & booted FreeBSD 10.0-CURRENT #975 r253985M/253985:141: Tue Aug 6 05:28:39 PDT 2013 root@localhost:/common/S4/obj/usr/src/sys/CANARY i386 OK. I'm away from home, and Internet access is a bit flaky, so initially, I suspec

Re: Early drop to debugger with DEBUG_MEMGUARD

On Mon, Aug 12, 2013 at 08:30:15AM -0700, Davide Italiano wrote: > ... > > Booting... > > GDB: no debug ports present > > KDB: debugger backends: ddb > > KDB: current backend: ddb > > Copyright (c) 1992-2013 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993

Re: Early drop to debugger with DEBUG_MEMGUARD

On Mon, Aug 12, 2013 at 09:10:55AM -0700, Davide Italiano wrote: > ... > OK, I'm not sure I can make an immediate guess on where's the problem > now (without access to my main workstation), so I think you need to > wait tomorrow unless someone beats me to the punch. The best I can say > is that may

Re: Early drop to debugger with DEBUG_MEMGUARD

On Tue, Aug 13, 2013 at 08:29:44AM +0300, Konstantin Belousov wrote: > ... > The r254025 indeed introduced the problem, and Davide pointed out you a > workaround for the assertion triggering. Right; I tried one of those -- I hope I got it right... > Proper fix for the memguard requires a policy o

Re: Early drop to debugger with DEBUG_MEMGUARD

On Tue, Aug 13, 2013 at 12:44:54PM -1000, Jeff Roberson wrote: > ... > Please try 254308. It is working for me. Starting from: FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #1244 r254279M/254280:143: Tue Aug 13 11:11:06 PDT 2013 r...@freebeast.catwhisker.org:/comm

/etc/rc.d/powerd vs. lack of OID dev.cpu.0.freq

I run powerd(8) on my laptop, and track both stable/8 and head on it (on different slices), daily. I am now finally(!) getting around to pointing out that it appears that: * /etc/rc.d/powerd tries to make use of sysctl OID dev.cpu.0.freq. * That OID exists in stable/8. * It does not exist in he

Error building src/sys/modules/mlx4 @r219821

Sources actually updated to r219820; change from r219821 was hand-applied. That got me through the buildworld. :-} Building kernel modules fails, though: >>> stage 3.1: making dependencies ... >>> stage 3.2: building everything ... ===> mlx (all) ... ===> mlx4 (all) cc -O2 -pipe -DINET6 -fno-st

Re: `hw.acpi.thermal.tz0.temperature' disappeared

On Mon, Apr 18, 2011 at 08:05:40AM -0400, John Baldwin wrote: > ... > > output from: > > sysctl -a |grep acpi > > is here: https://privatepaste.com/ca08d4658b > > I suspect it is still there, but sysctl doesn't know how to display it > anymore. This is probably due to the changes with formattin

Re: `hw.acpi.thermal.tz0.temperature' disappeared

On Mon, Apr 18, 2011 at 08:43:56AM -0700, m...@freebsd.org wrote: > > I don't seem to have a hw.acpi.thermal sysctl node on my box. Can > someone please try this patch? Well, no magic smoke leaked out when I tried it, and: FreeBSD 9.0-CURRENT #203 r220770M: Mon Apr 18 09:51:15 PDT 2011 d13

@r223471: panic: run_interrupt_driven_config_hooks: waited too long

I last built head at r223421; I upgraded sources to r223471. "make buildworld" was uneventful; building the kernel demonstrated that I needed the patch from r223474, which I applied (after which building the kernel was also uneventful). Here's a cut/paste from serial console of my build machine (

Re: Kernel compile failure in ATH.

On Thu, Jun 23, 2011 at 03:21:28PM +0200, Ian FREISLICH wrote: > Hi > > Just got this error making a new kernel: > You need the patch from r223474: Author: adrian Date: Thu Jun 23 12:11:43 2011 New Revision: 223474 URL: http://svn.freebsd.org/changeset/base/223474 Log: add missing #defin

Re: kernel broken: run_interrupt_driven_hooks: still waiting after XXX seconds for xpt_config

On Thu, Jun 23, 2011 at 06:12:54PM +0300, Alexander Motin wrote: > ... > SVN rev 223443 broke ATAPI support. SVN rev 223475 should fix it. Thanks -- that did resolve the issue for me. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of

panic: share -> excl @r224632

I've only seen this on my laptop; my build machine doesn't exhibit the panic. r224602 is the most recent point I've built that does not exhibit the panic at all. The first few lines (hand-transcribed; I have no serial console on this laptop -- the one shortcoming it has): shared lock of (lockmgr

Re: panic: share -> excl @r224632

On Thu, Aug 04, 2011 at 05:54:54AM -0700, David Wolfskill wrote: > ... > I will see if I can find a commit that affected at least one of the > affected files in the above list that I can revert to avoid the panic, > but I'm a bit slow for a while yet, so I figured I'd f

Re: panic: share -> excl @r224632

On Thu, Aug 04, 2011 at 04:59:32PM +0300, Kostik Belousov wrote: > ... > I am sure that this is caused by r224614. Well, see: you approached it from knowledge, while I made a quasi-educated guess. :-} > I forgot that vn_fullpath cannot operate on the locked vnode. And I expect you have likely fo

Re: panic: share -> excl @r224632

On Fri, Aug 05, 2011 at 10:43:32AM +0200, Martin Matuska wrote: > Patch updated. > ... OK; after reverting kern/vfs_mount.c to its pre-patched status on my laptop, I applied this most recent patch without incident; it built & boots fine, which is now running: FreeBSD g1-222.catwhisker.org. 9.0-BE

Re: 8-stable -> 9-current upgrade

On Wed, Sep 07, 2011 at 05:12:45PM -0700, Kevin Oberman wrote: > ... > I am particularly concerned with things like header files > (/usr/include) that might bite me if not deleted. This isn't specific to that upgrade, but when I do a "make installworld", I augment the instructions from UPDATING, p

Re: 8-stable -> 9-current upgrade

On Thu, Sep 08, 2011 at 07:59:59PM +0200, Olivier Smedts wrote: > ... > > I augment the instructions from UPDATING, prefixing the "make > > installworld" itself with: > > > > rm -fr /usr/include.old && mv /usr/include{,.old} && \ > > rm -fr /usr/share/man > > > > Thus, I have reasonable confidence

Build error in FreeBSD head, main-n259058-105019e0d6c -> main-n259061-b1258b76435

And the only commit after main-n259061-b1258b76435 so far is 004bb636ca65f3239da284c20abb7f9d1d953dee, which claims: | tcp: Move sysctl OIDs related to ECN to tcp_ecn. | Keep all ECN related code in (mostly) one place. | | No functional change. I'm seeing: ... building shared library libBIG5.so

Re: cant login after make installworld: pam_opie.so.6 not found

On Tue, Jan 03, 2023 at 09:39:31PM +, Ivan Quitschal wrote: > ... > I am having a problem here after doing a: > make installworld > and > make delete-old-libs > > now I cant login (only thru single user) > looks like the "make delete-old-libs" has deleted that lib pam_opie.so.6 and > now I c

Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

Running: FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #275 main-n259988-48dc9150ac36: Tue Jan 10 12:20:47 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 and performing an in-place source update to main-n260011-40bb52c89b87 u

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote: > looks like we may need another 'unclean' workaround for this? > > Warner > > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote: > ... > > I had this problem also. After deleting obj/usr the buildworld succeeded. > > > Empi

Buildworld failure at main-n261978-44312c28fe2d in /usr/src/usr.sbin/bhyve

Running: freebeast(14.0-C)[4] uname -aUK FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #328 main-n261961-7ae0972c7b8c: Mon Apr 3 11:41:40 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400085 1400085 in meta mode after upd

Re: Buildworld failure at main-n261978-44312c28fe2d in /usr/src/usr.sbin/bhyve

Resolved by 76fa62b5232e67ef10476cf1329aaceb9cbc2ff5; ref. https://cgit.freebsd.org/src/commit/?id=76fa62b5232e67ef10476cf1329aaceb9cbc2ff5 Peace, david -- David H. Wolfskill da...@catwhisker.org Putin claimed he wanted to avoid expansion of NATO. See how well THAT

Build failure in usr.sbin/bhyvectl; sources at main-n263112-ad513b4dba3e

This is from an in-place source update from main-n263073-634a770a5e16 to main-n263112-ad513b4dba3e: ... Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o Building /common/S4/obj/usr/src/amd64.amd64/

Build failure for radlib.o during main-n263767-764464af4968 -> main-n263782-59833b089e78 src update

Running: FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #405 main-n263767-764464af4968: Fri Jun 23 11:42:14 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400091 1400091 after updating sources to main-n263782-59833b089e78, th

Re: Build failure for radlib.o during main-n263767-764464af4968 -> main-n263782-59833b089e78 src update

On Sat, Jun 24, 2023 at 10:39:57AM -0400, Ed Maste wrote: > ... > > : "OPENSSL_API_COMPAT expresses an impossible API compatibility level" > > # error "OPENSSL_API_COMPAT expresses an impossible API compatibility > > level" > >^ > > This could be a dependency issue; would you check if removi

Re: Build failure for radlib.o during main-n263767-764464af4968 -> main-n263782-59833b089e78 src update

On Sat, Jun 24, 2023 at 09:09:00AM -0700, David Wolfskill wrote: > On Sat, Jun 24, 2023 at 10:39:57AM -0400, Ed Maste wrote: > > ... > > > : "OPENSSL_API_COMPAT expresses an impossible API compatibility level" > > > # error "OPENSSL_API_COMPAT

Re: debug.verbose_sysinit=1

On Sun, Jun 25, 2023 at 09:20:40PM +0100, Graham Perrin wrote: > When debug.verbose_sysinit=1 is set in loader.conf(5), is normal to _not_ > have BOOT and copyright messages? It's normal (in that situation) to require a higher value in kern.msgbufsize if you want the entire dmesg output saved in /

Re: problems on new -current install with pkg/ssl

On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg > for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and

"make installworld" fails for main-n265819-af5e348c61da

This is for an in-place source update; machine is currently running: freebeast(15.0-C)[15] uname -aUK FreeBSD freebeast.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #427 main-n265811-38ecc80b2a4e: Sun Oct 8 17:42:28 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd

After update to main-n266611-49a83b94395a: panic: bus_generic_rman_activate_resource

After I saw this with both my headless "build machine" and a laptop (and verified that there were no more recent commits to main), I figured it might be worth reporting. This was after a source update from: FreeBSD 15.0-CURRENT #473 main-n266588-2a35f3cdf63d-dirty: Fri Nov 24 13:11:48 UTC 2023

Re: After update to main-n266611-49a83b94395a: panic: bus_generic_rman_activate_resource

On Sun, Nov 26, 2023 at 04:36:33AM +0900, Tomoaki AOKI wrote: > Hi. > > Not tested, but does upgrading to commit ed88eef140a1 [1] and later > help? (I'm still at commit 5d4f897f88ed on main.) > > [1] > https://cgit.freebsd.org/src/commit/?id=ed88eef140a1c3d57d546f409c216806dd3da809 > > Regards.

<    2   3   4   5   6   7   8   9   10   >