Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137

2018-06-06 Thread bob prohaska
On Wed, Jun 06, 2018 at 08:55:39PM +0200, Ronald Klop wrote: > On Sat, 02 Jun 2018 13:40:27 +0200, Ronald Klop > wrote: > > > How do you ever run a -j4 buildworld? My RPI3 starts building clang/llvm > with sometimes 500 MB+ per process so everything starts swapping like hell > and takes

Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137

2018-06-06 Thread Ronald Klop
On Sat, 02 Jun 2018 13:40:27 +0200, Ronald Klop wrote: This happened again. Now I have a crashdump. Anyone interested? Some more answers below. On Fri, 01 Jun 2018 17:41:54 +0200, bob prohaska wrote: On Thu, May 31, 2018 at 05:53:12PM +0200, Ronald Klop wrote: I had a crash on my

r334533 renders head unbootable on XenServer 7.4

2018-06-06 Thread Trond Endrestøl
After trial and error, I found r334533 to be responsible for rendering head unbootable on XenServer 7.4. Neither of the two available XenServer patches has been applied on the host server. Normal and verbose boot messages stops non-deterministically at: hpet0: iomem 0xfed0-0xfed003ff on

Re: how do I use the make universe machines?

2018-06-06 Thread Conrad Meyer
On Tue, Jun 5, 2018 at 6:12 PM, Benjamin Kaduk wrote: > On Wed, Jun 06, 2018 at 12:47:17AM +, Rick Macklem wrote: >> I've heard mention of "make universe" machines multiple times, >> but have no idea how to use them? >> Is there doc on this? >> >> Thanks, rick >> ps: I'll admit I haven't

Re: error building libpmc_events.c [solved (sort of)]

2018-06-06 Thread Bryan Drewery
On 6/6/18 11:22 AM, Claude Buisson wrote: > On 06/06/2018 16:20, Bryan Drewery wrote: >> I think I know the issue. Will try looking later today or tomorrow. >> >> Regards, >> Bryan Drewery >> >>> On Jun 5, 2018, at 13:18, Claude Buisson wrote: >>> >>> Replying to my own mail for more details, and

Re: error building libpmc_events.c [solved (sort of)]

2018-06-06 Thread Claude Buisson
On 06/06/2018 16:20, Bryan Drewery wrote: I think I know the issue. Will try looking later today or tomorrow. Regards, Bryan Drewery On Jun 5, 2018, at 13:18, Claude Buisson wrote: Replying to my own mail for more details, and ccing potential commiters On 06/04/2018 17:34, Claude Buisson

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

2018-06-06 Thread David Samms
Hi Tested both images in both modes on: Intel® Server Board S1200KP E3-1230 CPU BIOS/legacy mode work perfectly UEFI failed. Not surprising as I have never gotten FreeBSD UEFI to work on this motherboard. Console displayed: - /boot/kernel/kernel Booting...

Re: error building libpmc_events.c

2018-06-06 Thread Bryan Drewery
I think I know the issue. Will try looking later today or tomorrow. Regards, Bryan Drewery > On Jun 5, 2018, at 13:18, Claude Buisson wrote: > > Replying to my own mail for more details, and ccing potential commiters > >> On 06/04/2018 17:34, Claude Buisson wrote: >> Hi, >> During a

Re: CAM/ growisofs: Segmentation fault, SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)

2018-06-06 Thread Warner Losh
On Wed, Jun 6, 2018 at 12:55 AM, O. Hartmann wrote: > Hello, > > my desperate call for help is according to PR 225291, > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225291. > > On one of our Workstations (Fujitsu Celsius M740 with Haswell XEON 6-core > CPU) > I face the inability to burn

CAM/ growisofs: Segmentation fault, SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)

2018-06-06 Thread O. Hartmann
Hello, my desperate call for help is according to PR 225291, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225291. On one of our Workstations (Fujitsu Celsius M740 with Haswell XEON 6-core CPU) I face the inability to burn larger DVDs, using the port sysutils/dvd+rw-tools. The recent status

Re: Odd w/who behavior for the last 12 years

2018-06-06 Thread Ed Schouten
Hi Timur, 2018-05-28 5:26 GMT+02:00 Timur I. Bakeyev : > So I propose to remove the said patch(or make it verify only "pts/" > devices). any objections? Sounds good! Changes like the ones made in r155875 were simply workarounds to deal with processes silly enough not to write DEAD_PROCESS

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

2018-06-06 Thread Maurizio Vairani
2018-05-30 17:50 GMT+02:00 Glen Barber : > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images