r320358 panics immediately on boot / AMD64-GENERIC kernel

Screen image with backtrace https://pasteboard.co/dZRVG5Uo.jpg After upgrading from 318959 to 320358 I immediately get the attached panic. This is AMD64 / GENERIC kernel. /boot/loader.conf is empty. The system boots off a UFS2 partition. This is a virtual guest and I do currently have a

Re: HEAD/i386 r320212: three reproducible panics

On 06/23/17 12:42, Oleg V. Nauman wrote: a) Panic on shutdown: Fatal trap 1: privileged instruction fault while in kernel mode cpuid = 1; apic id = 01 instruction pointer = 0x20:0xc6be2023 stack pointer = 0x28:0xe13c39f4 frame pointer = 0x28:0xe13c3a20 code segment =

post ino64: lockd no runs?

It seems that {rpc.}lockd no longer runs after the ino64 changes on any of my systems after a full rebuild of src and ports. No log entries offer any insight as to why :-( imb ___ freebsd-current@freebsd.org mailing list

Re: ino64, java and intellij products problem

Hi, It may by worth to check other java monsters, but I see no problem with Eclipse and SQL Developer with ino64. Thanks! 1 июн. 2017 г. 6:29 ДП пользователь "Konstantin Belousov" < kostik...@gmail.com> написал: > On Wed, May 31, 2017 at 11:53:39PM +0300, Boris Samorodov wrote: > > Hi All, > >

Re: old snapshot install images?

On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote: > > > On 3. mai 2017, at 21:06, Michael W. Lucas <mwlu...@michaelwlucas.com> > > wrote: > > > > On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote: > >> There was many issues fixed

Re: old snapshot install images?

my point of > view, the most important question is if the current ???current??? is ok:) Agreed 500%. The latest snapshot is NOT ok. ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.micha

Re: old snapshot install images?

sed the guided install, had it blow the disks away. ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-curr

Re: old snapshot install images?

em. I've gotten some installer snapshots from October and from mid-2015. Trying those. My goal is to find out when the problem appeared and include the time window in the PR. ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michael

Re: old snapshot install images?

On Wed, May 03, 2017 at 01:01:10AM -0700, Ngie Cooper wrote: > Hi Michael! > - What sources are you using/revision are you at? Using r311461 amd64 install memstick at the moment. Uname says built "Thu Jan 5 22:46:38 UTC 2017" > - Are your drives the 512 byte/sector or

old snapshot install images?

an archive of -current install media, either CD or ISO? I need to get this box back fairly quickly, but I don't mind burning a couple days to nail it down. Thanks, ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https

Re: Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

On 2017-04-28 17:42, Andriy Gapon wrote: On 28/04/2017 14:56, Michael Jung wrote: I have mad the requested change.. [root@bsd11 /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs]# diff zio.c ~mikej/zio.c.orig 965c965 < size, NULL, NULL, ZIO_TYPE_FREE, ZIO_PRIORITY_

Re: 2013 Macbook Pro, sound OK in headphones but no sound in internal speakers

gmail.com> wrote: > > That would be awesome! Yes, my model is also A1398. > > After patching the asmc driver (has been committed) freebsd runs great on > it. > All that's missing is sound :) > > >> On Fri, Apr 28, 2017 at 7:06 PM, Michael Gmelin <free...@grem.d

Re: 2013 Macbook Pro, sound OK in headphones but no sound in internal speakers

> > > >> On Fri, Apr 28, 2017 at 5:05 PM, Michael Gmelin <free...@grem.de> wrote: >> >> device.conf or device.hints? >> >> Note that you can also set these using sysctl for experimentation. >> Which exact model number of the macbook pro a

Re: 2013 Macbook Pro, sound OK in headphones but no sound in internal speakers

;as=3 seq=0" > > # Speakers > hint.hdaa.1.nid18.config="as=4 seq=0" > hint.hdaa.1.nid19.config="as=5 seq=0" > > hint.hdaa.1.gpio_config="3=set" > > > > > On Fri, Apr 28, 2017 at 3:21 PM, Michael Gmelin <free...@grem.de

Re: 2013 Macbook Pro, sound OK in headphones but no sound in internal speakers

Without looking through all of this myself, could you try the two solutions at the end of this thread? https://forums.macrumors.com/threads/sound-settings-on-freebsd.1658457/ > On 28. Apr 2017, at 15:06, Johannes Lundberg <johal...@gmail.com> wrote: > > Hi Michael >

Re: 2013 Macbook Pro, sound OK in headphones but no sound in internal speakers

gt; /dev/dsp* > >> only generate noise in the headphones.. > >> > >> > > MBP requires some patches for the speakers to work: > > > > https://svnweb.freebsd.org/base?view=revision=261507 > > > > --HPS > > > ___ &

Re: Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

On 2017-04-27 17:57, Andriy Gapon wrote: On 27/04/2017 18:52, Michael Jung wrote: Hi: Recently upgraded from r315905 to r317435 and during a poudriere run got this panic which I have not seen before. https://charon.gopai.com/core.txt.1 https://charon.gopai.com/info.1 Let me know what

Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

Hi: Recently upgraded from r315905 to r317435 and during a poudriere run got this panic which I have not seen before. https://charon.gopai.com/core.txt.1 https://charon.gopai.com/info.1 Let me know what additional information I might supply. --mikej panic: solaris assert: (lsize != psize)

Re: r316958: booting a server takes >10 minutes!

On 04/15/17 12:41, Poul-Henning Kamp wrote: > > In message <20170415160916.gy1...@albert.catwhisker.org>, David Wolfskill > write > s: > >> And I understand that the Cloudflare/f-root server issue isn't quite >> that recent: "The new f-root servers appeared around two weeks ago" >

Re: CURRENT: slow like crap! ZFS scrubbing and ports update > 25 min

> On 22 Mar 2017, at 21:02, O. Hartmann wrote: > > CURRENT (FreeBSD 12.0-CURRENT #82 r315720: Wed Mar 22 18:49:28 CET 2017 > amd64) is > annoyingly slow! While scrubbing is working on my 12 GB ZFS volume, updating > /usr/ports > takes >25 min(!). That is an absolute

Re: start-up failure at SVN r314889

. This fixes a startup issue when COMPAT_LINUXKPI is in enabled the kernel configuration file. imb On 3/8/17 6:02 PM, Michael Butler wrote: The difference between a kernel that boots and another that won't is .. imb@toshi:/home/imb> diff -cw /sys/amd64/conf/TOSHI~ /sys/amd64/conf/TO

Re: start-up failure at SVN r314889

n Wed, Mar 8, 2017 at 6:26 AM, David Wolfskill <da...@catwhisker.org> wrote: >> On Wed, Mar 08, 2017 at 07:55:44AM -0500, Michael Butler wrote: >>> My laptop usually starts like this .. >>> >>> FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar 6 19:34:51 EST 2017 &g

Re: two recent snapshot installer problems

e=yes" it boots. So: bsdinstall doesn't like this box. If anyone's willing to work on the installer in the next few days, I'm willing to wait to work on this box. I will have to put it to work before long, though. Thanks, ==ml -- Michael W. LucasTwitter @mwlauthor nonfict

Re: start-up failure at SVN r314889

On 03/08/17 08:12, Andriy Gapon wrote: > On 08/03/2017 14:55, Michael Butler wrote: >> My laptop usually starts like this .. >> >> FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar 6 19:34:51 EST 2017 >> i...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/T

start-up failure at SVN r314889

My laptop usually starts like this .. FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar 6 19:34:51 EST 2017 i...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI amd64 FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM 4.0.0) VT(vga): resolution 640x480 info:

two recent snapshot installer problems

on the individual satadom drives? Same boot message. Any suggestions on how to gather debugging info for this? Thanks, ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com

Re: input/output error @boot

image: read failed > can't load file /boot/kernel/kernel > > Can the same when attempting to load kernel.old, had to revert to old > snapshot on usb rescue. > This is not a hardware problem. I guess this is https://lists.freebsd.org/piperm

Re: r314670: buildworld compile failure: undefined reference to `xdr_attrstat'

Seems that SVN r314659 broke this :-( Michael On 03/04/17 11:11, O. Hartmann wrote: > At revision 314670, buildworld fails on all CURRENT machines with the error > shown below. > > > Regards, > > oh > > > [...] > ===> usr.sbin/amd/hlfsd (all)

Re: Boot failure - svn up from this morning

it's really annoying to boot the host first... > I'm really sorry for this. > > I suppose you're able to build or find a good 'loader.efi' binary on another > host, > and then manage to replace the bad 'loader.efi' on the host broken by me. :-) This problem also occurred on a Dell R430... Bes

Re: panic: invalid bcd xxx

tion. -m > > -adrian > >> On 28 February 2017 at 15:26, Michael Gmelin <free...@grem.de> wrote: >> On Tue, 28 Feb 2017 17:16:02 -0600 >> Eric van Gyzen <vangy...@freebsd.org> wrote: >> >>>> On 02/28/2017 16:57, Conrad Meyer wrote: >&

Re: panic: invalid bcd xxx

gt; > right thing to do. Adding an error return to this routine is a > > little much, though. I think probably the caller should perform > > input validation between the broken device and this routine. > > Either of those would be a much better solution. This was just a &g

panic: invalid bcd xxx

worked ok (last version I tested personally was back in November/December though). -m [0] https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170210-r313561-memstick.img -- Michael Gmelin ___ freebsd

SVN r313701 breaks build

An opening brace was missed in the change; fix as below: Index: sys/dev/md/md.c === --- sys/dev/md/md.c (revision 313701) +++ sys/dev/md/md.c (working copy) @@ -1860,7 +1860,7 @@ sbuf_printf(sb,

Re: NFS 4.1

at 10:02 AM, Russell L. Carter <rcar...@pinyon.org> wrote: > On 01/17/17 10:38, Michael Ware wrote: > >> Good day, >> Does anyone know if NFS 4.1 (not 4.0) is available in FreeBSD 11? I have >> not been able to find any documentation around this. >> Thanks >> &

NFS 4.1

Good day, Does anyone know if NFS 4.1 (not 4.0) is available in FreeBSD 11? I have not been able to find any documentation around this. Thanks -- Mike ___ freebsd-current@freebsd.org mailing list

SVN r311568 breaks build

With the introduction of MSG_MORETOCOME, the build of libsysdecode is broken. Was the following patch the intended but missed fix? Index: lib/libsysdecode/mktables === --- lib/libsysdecode/mktables (revision 311572) +++

SVN r310931 Bad code

it. I expect this should be .. if ((sc->chost = strdup(s)) == NULL) { Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "f

Re: syslogd no longer listens (or sends) on a network socket

On 12/19/16 22:42, Hiroki Sato wrote: Michael Butler <i...@protected-networks.net> wrote in <da73919b-24bf-7ebf-3809-2220c087c...@protected-networks.net>: im> On 12/19/16 12:12, Hiroki Sato wrote: im> > Michael Butler <i...@protected-networks.net> wrote im> &

Re: syslogd no longer listens (or sends) on a network socket

On 12/19/16 12:12, Hiroki Sato wrote: Michael Butler <i...@protected-networks.net> wrote in <d5c17fa6-ddd7-277f-6f92-ee8fb55cd...@protected-networks.net>: im> It appears that SVN r309925 and onward no longer opens a network im> socket unless the command-line explicitly co

syslogd no longer listens (or sends) on a network socket

It appears that SVN r309925 and onward no longer opens a network socket unless the command-line explicitly contains "-b :syslog" :-( This also stops one syslog daemon forwarding to another (which is why I noticed). Was this an intentional behaviour change?

Re: DRM_I915_GEM_OBJECT_MAX_PIN_COUNT failure on -current

On 12/13/16 12:07, Konstantin Belousov wrote: On Tue, Dec 13, 2016 at 11:49:37AM -0500, Michael Butler wrote: I've been bitten by this twice on a KDE desktop in the last 24 hours .. same error on both occasions :-( error: [drm:pid1197:i915_gem_object_pin] *ERROR* WARN ON: obj->pin_co

DRM_I915_GEM_OBJECT_MAX_PIN_COUNT failure on -current

ciated, Michael ___ 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: Log spam: Limiting * response from 1 to 200 packets/sec

On 12/13/16 11:15, Gary Palmer wrote: On Tue, Dec 13, 2016 at 10:43:27AM -0500, Michael Butler wrote: On 12/13/16 10:29, Dimitry Andric wrote: Somebody is most likely port scanning your machines. I see this all the time on boxes connected to the internet. As are mine. I wouldn't mind so

Re: Log spam: Limiting * response from 1 to 200 packets/sec

On 12/13/16 10:48, Eric van Gyzen wrote: On 12/13/2016 09:24, Michael Butler wrote: Any hints as to why all of my -current equipment is complaining like below. Is there a sysctl to moderate/turn this off? Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec

Re: Log spam: Limiting * response from 1 to 200 packets/sec

address and, when appropriate, destination port. sysctl net.inet.icmp.icmplim_output=0, or increase the ICMP limit, if you want to help the port scanners. :-) I've added the sysctl to mute the warnings - thanks :-) Michael ___ freebsd

Log spam: Limiting * response from 1 to 200 packets/sec

Michael ___ 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: New warnings from WITNESS

> On 6 Nov 2016, at 19:41, Scott Long <sco...@samsco.org> wrote: > > >> On Nov 6, 2016, at 11:01 AM, Michael Tuexen <tue...@freebsd.org> wrote: >> >>> On 6 Nov 2016, at 15:39, Konstantin Belousov <kostik...@gmail.com> wrote: >>> >

Re: New warnings from WITNESS

> On 6 Nov 2016, at 15:39, Konstantin Belousov <kostik...@gmail.com> wrote: > > On Sun, Nov 06, 2016 at 02:17:45PM +0100, Michael Tuexen wrote: >>> On 6 Nov 2016, at 13:28, Konstantin Belousov <kostik...@gmail.com> wrote: >>> >>> On Sun, Nov 06

Re: New warnings from WITNESS

> On 6 Nov 2016, at 13:28, Konstantin Belousov <kostik...@gmail.com> wrote: > > On Sun, Nov 06, 2016 at 12:50:12PM +0100, Michael Tuexen wrote: >> bus_dmamap_create with the following non-sleepable locks held: >> exclusive sleep mutex mpt (mpt) r = 0 (0xfee

New warnings from WITNESS

at acpi_attach+0xdbf #15 0x80a9478d at device_attach+0x41d #16 0x80a9595a at bus_generic_attach+0x4a #17 0x80ee03e3 at nexus_acpi_attach+0x73 ... and so on. Not sure which revision introduced it... Best regards Michael

SVN r307866 compilation problem

It seems that compilation of -current fails in the case that KDB is not defined. I'm assuming that the following diff achieves what was intended: imb@vm01:/usr/src/sys/x86/x86> svn diff Index: cpu_machdep.c === --- cpu_machdep.c

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

Kurt, No more than idea: kldstat contains rtwn-rtl8192cfwU, but no rtwn-rtl8192cfwU_B. Do you have compiled rtwn-rtl8192cfwU_B.ko in /boot/kernel? Best regards, Michael On Sat, Oct 22, 2016 at 5:19 PM, Kurt Jaeger <li...@opsec.eu> wrote: > Hi! > > > On -current rtwn has bee

Re: SM bus ioctls incorrect in FreeBSD 11

tps://svnweb.freebsd.org/ports/head/sysutils/xmbmon/files/patch-getMB-smb_ioctl.c?r1=385155=385154=385155 > I see that it also used the approach that you use as a workaround. > And that port commit is by Michael Gmelin who made the change to > smb.h in r281985 > https://svnweb.fr

Re: [request for testing] isl, cyapa on chromebooks

> On 10 Oct 2016, at 20:27, Matthias Apitz wrote: > >> El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh escribió: >> >> I see no reason not to start the table right away based on >> smbios.sys.product and other criteria. I don't think we need all the >>

Re: [request for testing] isl, cyapa on chromebooks

> The idea is that this is a driver that listens for new iicbus-es and > adds isl and cyapa devices to a bus if some criteria are met. > For the Acer c720, these criteria would be: smbios.bios.vendor=="coreboot" smbios.system.maker=="Acer" smbios.system.prod

Re: [request for testing] isl, cyapa on chromebooks

ice.hints to make isl and cyapa work, and putting things like that (and other hints, e.g. to route the Intel HDA correctly) into a man page ("apropos c720") would be the next best thing to having it work out of the box. -m -- Michael Gmelin ___

Re: [request for testing] isl, cyapa on chromebooks

On Thu, 6 Oct 2016 11:12:27 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 06/10/2016 11:10, Michael Gmelin wrote: > > > > > >> On 06 Oct 2016, at 09:48, Andriy Gapon <a...@freebsd.org> wrote: > >> > >>> On 06/10/2016 08:

Re: [request for testing] isl, cyapa on chromebooks

> On 06 Oct 2016, at 09:48, Andriy Gapon wrote: > >> On 06/10/2016 08:37, Andriy Gapon wrote: >> The more testing the better! > > Based on Michael's results I've uploaded a new version: > https://people.freebsd.org/~avg/ig4-i2c.v4.diff > > Good news. Applying the last two

Re: [request for testing] isl, cyapa on chromebooks

> On 05 Oct 2016, at 15:01, Andriy Gapon <a...@freebsd.org> wrote: > >> On 05/10/2016 14:19, Michael Gmelin wrote: >> >> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and >> iicbus_attach are not. > > Thank you! > N

Re: [request for testing] isl, cyapa on chromebooks

> On 05 Oct 2016, at 13:32, Malcolm Matalka <mmata...@gmail.com> wrote: > > Den 5 okt. 2016 13:19 skrev "Michael Gmelin" <gre...@freebsd.org>: > > > > > > > > > On 05 Oct 2016, at 07:48, Andriy Gapon <a...@freebsd.org> wrote: >

Re: [request for testing] isl, cyapa on chromebooks

> On 05 Oct 2016, at 07:48, Andriy Gapon <a...@freebsd.org> wrote: > >> On 05/10/2016 01:48, Michael Gmelin wrote: >> Double-checked the hints, it's all ok. >> >> Please find a more verbose log file of loading the kernel modules here: >> >> http

Re: [request for testing] isl, cyapa on chromebooks

On Tue, 4 Oct 2016 13:07:28 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 04/10/2016 12:46, Michael Gmelin wrote: > > iicbus(0|1) actually show up in devinfo -v, but nothing else works. > > > > You can find a log file and various outputs (dmesg, devinfo et

Re: [request for testing] isl, cyapa on chromebooks

On Tue, 4 Oct 2016 01:04:10 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 03/10/2016 23:25, Michael Gmelin wrote: > > On Mon, 3 Oct 2016 19:41:17 +0300 > > Andriy Gapon <a...@freebsd.org> wrote: > > > >> On 03/10/2016 19:07, Michael Gmelin wrote:

Re: [request for testing] isl, cyapa on chromebooks

On Mon, 3 Oct 2016 19:41:17 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 03/10/2016 19:07, Michael Gmelin wrote: > > I upgraded the latter the r306641, applied your patches (cleanly) > > and ran "make kernel" (GENERIC kernel), added the entries to > > dev

Re: [request for testing] isl, cyapa on chromebooks

efined linker_load_file: Unsupported file type I also noticed that isl cannot be built from the module source directory: # cd /usr/src/sys/modules/i2c/isl # make ... /usr/src/sys/sys/vnode.h:571:10: fatal error: 'vnode_if.h' file not found #include "vnode_if.h" ^ 1 error gen

SVN r305382 breaks world32 on amd64 (and native 32-bit)

Build fails with: ===> lib/msun (obj,all,install) Building /usr/obj/usr/src/lib/msun/e_fmodf.o /usr/src/lib/msun/i387/e_fmodf.S:10:17: error: register %rsp is only available in 64-bit mode movss %xmm0,-4(%rsp) ^~~~ /usr/src/lib/msun/i387/e_fmodf.S:11:17: error: register %rsp is

Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4

> On 03 Sep 2016, at 13:24, Guido Falsi <m...@madpilot.net> wrote: > > On 09/03/16 13:08, Michael Tuexen wrote: >>> On 03 Sep 2016, at 12:55, Oliver Böttcher <oliver.boettc...@posteo.de> >>> wrote: >>> >>> Am Freitag, den 02.09.2016, 22:0

Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4

e console="comconsole" comconsole_speed="115200" in /boot/loader.conf. It is not using ZFS and it is booting from an m-SATA SSD. Which boot device are you using? Best regards Michael > > Thanks > Oliver > ___ > freebsd-cu

build fails post SVN r304026

Is anyone else seeing this? ===> usr.bin/nfsstat (all) Building /usr/obj/usr/src/usr.bin/nfsstat/nfsstat.o /usr/src/usr.bin/nfsstat/nfsstat.c:301:4: error: array index 72 is past the end of the array (which contains 49 elements) [-Werror,-Warray-bounds]

SVN r303890 breaks build

The switch to device_t breaks the user-space compilation with .. Building /usr/obj/usr/src/lib/libkvm/kvm.o --- kvm.o --- In file included from /usr/src/lib/libkvm/kvm.c:50: /usr/obj/usr/src/tmp/usr/include/sys/pcpu.h:163:2: error: unknown type name 'device_t' device_tpc_device;

SVN r303643 breaks non-SMP compilation

In the non-SMP case, ADAPTIVE_MUTEXES is not defined and a subsequent reference to mtx_delay causes compilation of kern_mutex.c to fail because KDTRACE_HOOKS may be, imb ___ freebsd-current@freebsd.org mailing list

Re: security/openvpn build failure on 12-CURRENT/amd64

On 08/01/16 16:53, Ngie Cooper wrote: > On Mon, Aug 1, 2016 at 7:31 AM, Shawn Webb wrote: > >> HardenedBSD's kernel and world matched and still had the very same >> build error. >> >> Here's the build log: http://pastebin.com/TEBih1Sx > > Confirmed -- why's it

Re: kernel no longer builds without nvme

On 07/21/16 21:46, Warner Losh wrote: >> On Jul 21, 2016, at 11:53 AM, Ngie Cooper (yaneurabeya) >> <yaneurab...@gmail.com> wrote: >>> On Jul 21, 2016, at 06:45, Michael Butler <i...@protected-networks.net> >>> wrote: >>> >>> For th

Re: Who broke world and how to fix?

On 07/21/16 15:54, Steven G. Kargl wrote: > On Thu, Jul 21, 2016 at 03:50:48PM -0400, Michael Butler wrote: >> On 07/21/16 14:32, Steve Kargl wrote: >>> Updating uname -a >>> FreeBSD 11.0-ALPHA5 FreeBSD 11.0-ALPHA5 >>> #3 r302248: Tue Jun 28 10:11:31 PDT 2016

Re: Who broke world and how to fix?

On 07/21/16 14:32, Steve Kargl wrote: > Updating uname -a > FreeBSD 11.0-ALPHA5 FreeBSD 11.0-ALPHA5 > #3 r302248: Tue Jun 28 10:11:31 PDT 2016 > data/obj/usr/src/sys/SPEW amd64 > > to top-of-tree > > ===> lib/libsbuf (obj,all,install) > cc -O2 -pipe -MD -MF.depend.subr_prf.o -MTsubr_prf.o

kernel no longer builds without nvme

For those of us who build "minimal" kernels: Building /usr/obj/usr/src/sys/VM02/vers.c Building /usr/obj/usr/src/sys/VM02/vers.o Building /usr/obj/usr/src/sys/VM02/kernel --- kernel --- linking kernel cam_xpt.o: In function `xpt_announce_periph': /usr/src/sys/cam/cam_xpt.c:(.text+0xcd2):

[panic] ng_uncallout with NULL callout argument

NULL */ I suppose that actual root cause may be in upper stack (PPTP?). Link to bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211031 Best regards, Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/lis

Re: panic: bogus refcnt 0 on lle 0xfffff80121a13a00

Hi, I have same issue everyday on my laptop. It happens randomly and I suppose due to network issues. I want to test D4507. I've tried to apply patch, it's successful except one chunk: |Index: sys/netinet6/nd6.c |=== |---

LOR during unmount on 11.0-ALPHA5

It seems to happen on shutdown. I don't think I've seen it hang. The log shows one involving ufs instead of zfs, unfortunately without a stack. I'm not sure why that is, unless it was the installation memstick. There's another, probably unrelated, LOR that I'll put in a second message. Thanks, - Michael

LOR involving igmp on 11.0-ALPHA5

(ifnet_rw) @ /usr/src/sys/net/if.c:258 More details (with stack) are at https://gist.github.com/mfplass/aa7c78640af1309699e908c4d73c0d40 I've seen this twice. Thanks, - Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org

Re: Borked 'pkg install xorg-minimal' on FreeBSD-11.0-ALPHA3-amd64-20160528-r301815-memstick.img

> > # > > Hi Joe, > Please file a port bug against linux_base-c6. At the very least > the message should be more intuitive about what's trying to be > achieved; you will need to "kldload linux", which was the status quo > in old version

smartmontools now broken on -current (by svn r301771, r301778?)

The recent nvme updates have broken smartmontools .. imb@toshi:/home/imb> sudo smartctl -a /dev/ada0 smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-ALPHA2 amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org /dev/ada0: Inappropriate ioctl for device

Re: repeatable panic on pageout with 945GM

On 06/04/16 15:02, Konstantin Belousov wrote: > On Sat, Jun 04, 2016 at 02:59:01PM -0400, Michael Butler wrote: >> On 06/04/16 13:47, Konstantin Belousov wrote: >> >> [ .. snip .. ] >> >>> I believe that this is a bug in amd64 pmap. Fictitious pages

Re: repeatable panic on pageout with 945GM

On 06/04/16 15:02, Konstantin Belousov wrote: > On Sat, Jun 04, 2016 at 02:59:01PM -0400, Michael Butler wrote: >> On 06/04/16 13:47, Konstantin Belousov wrote: >> >> [ .. snip .. ] >> >>> I believe that this is a bug in amd64 pmap. Fictitious pages

Re: repeatable panic on pageout with 945GM

On 06/04/16 13:47, Konstantin Belousov wrote: [ .. snip .. ] > I believe that this is a bug in amd64 pmap. Fictitious pages are not > promoted, in particular, the pv_table array does not span over the > dynamically registered fictitious ranges. As result, pa_to_pvh() returns > garbage and pvh

Re: repeatable panic on pageout with 945GM

On 06/02/16 22:31, Matthew Macy wrote: > Tell me if that makes any difference. > > -M > > > On Thu, 02 Jun 2016 16:55:53 -0700 K. Macy wrote > > > It looks like it might be trying to remove mappings for a page that > doesn't > > have any. It's a bit odd.

Re: r300951: mountroot: waiting for device /dev/ad4s1a...

On Sat, 4 Jun 2016 14:01:34 +0200 Matthias Apitz <g...@unixarea.de> wrote: > El día Saturday, June 04, 2016 a las 01:54:30PM +0200, Michael Gmelin > escribió: > > > > > On Sat, 4 Jun 2016 13:48:52 +0200 > > Matthias Apitz <g...@unixarea.de> wrote: >

Re: r300951: mountroot: waiting for device /dev/ad4s1a...

On Sat, 4 Jun 2016 13:48:52 +0200 Matthias Apitz <g...@unixarea.de> wrote: > Hi Michael, > > El día Saturday, June 04, 2016 a las 01:40:46PM +0200, Michael Gmelin > escribió: > > > Hi Matthias, > > > > Did you try to connect an external USB keyboard

Re: r300951: mountroot: waiting for device /dev/ad4s1a...

ount root drom ufs:/dev/ad4s1a [rw]... > mountroot: waiting for device /dev/ad4s1a ... > Mounting from ufs:/dev/ad4s1a failed with error 19. > > Than it goes into the manual dialog to specify the root device but at > the prompt > >

Re: repeatable panic on pageout with 945GM

On 06/02/16 22:31, Matthew Macy wrote: > Tell me if that makes any difference. > > -M > > > On Thu, 02 Jun 2016 16:55:53 -0700 K. Macy wrote > > > It looks like it might be trying to remove mappings for a page that > doesn't > > have any. It's a bit odd.

Re: repeatable panic on pageout with 945GM

On 05/23/16 21:10, Michael Butler wrote: > On 05/22/16 09:58, Michael Butler wrote: >> With KDE and compositing enabled, I randomly get the following: >> >> (kgdb) info stack >> #0 doadump (textdump=) at pcpu.h:221 >> #1 0x8064e98e in kern_reboot (h

Re: head r30140 - Panic String: _mtx_lock_sleep: recursed on non-recursive mutex vm page @ /usr/src/sys/vm/vm_page.c:774

On 2016-06-02 18:17, Ngie Cooper wrote: On Thu, Jun 2, 2016 at 3:05 PM, Michael Jung <mi...@mikej.com> wrote: On 2016-06-01 12:37, Michael Jung wrote: Since upgrading to head r301040 I have started to get the above panic while running poudriere while building packages for 10.3-STABLE r

Re: head r30140 - Panic String: _mtx_lock_sleep: recursed on non-recursive mutex vm page @ /usr/src/sys/vm/vm_page.c:774

On 2016-06-01 12:37, Michael Jung wrote: Since upgrading to head r301040 I have started to get the above panic while running poudriere while building packages for 10.3-STABLE r301107. Unfortuately I can't tell you the previous version of head but it was from some months ago. https

head r30140 - Panic String: _mtx_lock_sleep: recursed on non-recursive mutex vm page @ /usr/src/sys/vm/vm_page.c:774

Since upgrading to head r301040 I have started to get the above panic while running poudriere while building packages for 10.3-STABLE r301107. Unfortuately I can't tell you the previous version of head but it was from some months ago. https://charon.gopai.com/core.txt.7

Re: r300951 make buildworld duration 18h

On 05/30/16 10:37, Matthias Apitz wrote: > Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld > as > > # make -j2 buildworld > > it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom > 1.6GHz > and 1 GByte RAM and was otherwise unused. Is this the

Re: NFSv4 compatibility with ESX6U2

On 05/29/16 21:05, Michael Butler wrote: > I was just fooling around with ESX this evening and trying to add an > NFSv4 mount onto it as extra storage. Curiously, given the correct > credentials, it will report the total volume size and free remaining but > won't display

NFSv4 compatibility with ESX6U2

I was just fooling around with ESX this evening and trying to add an NFSv4 mount onto it as extra storage. Curiously, given the correct credentials, it will report the total volume size and free remaining but won't display either files or subdirectories :-( In this case, the underlying

Re: repeatable panic on pageout with 945GM

On 05/22/16 09:58, Michael Butler wrote: > With KDE and compositing enabled, I randomly get the following: > > (kgdb) info stack > #0 doadump (textdump=) at pcpu.h:221 > #1 0x8064e98e in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:366 > #

repeatable panic on pageout with 945GM

With KDE and compositing enabled, I randomly get the following: (kgdb) info stack #0 doadump (textdump=) at pcpu.h:221 #1 0x8064e98e in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0x8064eea1 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759

Re: Followup on packaging base with pkg(8)

hank you so much for your hard work on something that will be a big step forward and also for being realistic enough to not forcing things before they're ready! - Michael ___ 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"

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