Re: sendmail: no local mailer

2003-04-02 Thread Oleg V. Nauman
On Wed, Apr 02, 2003 at 10:26:03AM -0700, Nate Williams wrote: evantd Sendmail has not been working on my system for some time now. I evantd can't say exactly how long, but my guess is that it broke when I evantd upgraded to RELENG_5_0. This is how sendmail is invoked (by evantd default)

Re: sendmail: no local mailer

2003-04-03 Thread Oleg V. Nauman
On Wed, Apr 02, 2003 at 03:18:18PM -0700, Nate Williams wrote: evantd Sendmail has not been working on my system for some time now. I evantd can't say exactly how long, but my guess is that it broke when I evantd upgraded to RELENG_5_0. This is how sendmail is invoked (by evantd

Recent HEAD: buildworld is broken with clang

2011-08-14 Thread Oleg V. Nauman
=== libexec (all) === libexec/atrun (all) clang -O -pipe -march=i686 -mtune=i686 -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\'

Re: Recent HEAD: buildworld is broken with clang

2011-08-15 Thread Oleg V. Nauman
Quoting Garrett Cooper yaneg...@gmail.com: On Aug 14, 2011, at 11:58 AM, Oleg V. Nauman o...@opentransfer.com wrote: ... There was an issue with file descriptor handling introduced with the capsicum work. Please update your src, rebuild your kernel, install, or use an older kernel

Re: r287197: wlan interfaces aren't brought up at boot or u

2015-08-29 Thread Oleg V. Nauman
On Saturday 29 August 2015 11:02:02 Gleb Smirnoff wrote: On Sat, Aug 29, 2015 at 01:19:40AM +0200, Idwer Vollering wrote: I Manually running 'service netif restart' works around this. I I /etc/network.subr and /etc/rc.d/netif have been updated by mergemaster I -p and mergemaster -iF I I I

Re: r287197: wlan interfaces aren't brought up at boot or u

2015-08-29 Thread Oleg V. Nauman
On Saturday 29 August 2015 15:53:31 Gleb Smirnoff wrote: On Sat, Aug 29, 2015 at 12:56:39PM +0300, Oleg V. Nauman wrote: O On Saturday 29 August 2015 11:02:02 Gleb Smirnoff wrote: O On Sat, Aug 29, 2015 at 01:19:40AM +0200, Idwer Vollering wrote: O I Manually running 'service netif restart

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
On Saturday 19 March 2016 12:14:33 Konstantin Belousov wrote: > On Sat, Mar 19, 2016 at 09:03:56AM +0200, Oleg V. Nauman wrote: > > On Friday 18 March 2016 11:55:31 Konstantin Belousov wrote: > > > On Fri, Mar 18, 2016 at 08:14:57AM +0200, Konstantin Belousov wrote: > > &g

Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
I'm experiencing issue with threaded applications ( including many KDE applications ) after recent CURRENT update. Attempt to start application cause Abort trap (6) with "Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)" output on console.

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
On Saturday 19 March 2016 12:23:45 Konstantin Belousov wrote: > On Sat, Mar 19, 2016 at 12:14:33PM +0200, Konstantin Belousov wrote: > > On Sat, Mar 19, 2016 at 09:03:56AM +0200, Oleg V. Nauman wrote: > > > On Friday 18 March 2016 11:55:31 Konstantin Belousov wrote: > >

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
On Friday 18 March 2016 03:30:51 Konstantin Belousov wrote: > On Thu, Mar 17, 2016 at 09:40:11PM +0200, Oleg V. Nauman wrote: > > I'm experiencing issue with threaded applications ( including many KDE > > > > applications ) after recent CURRENT update. Attempt to start

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
On Friday 18 March 2016 11:55:31 Konstantin Belousov wrote: > On Fri, Mar 18, 2016 at 08:14:57AM +0200, Konstantin Belousov wrote: > > Yes, please. It would be significantly easier to diagnose the problem if > > the minimal example is provided. If not, please pack one crashing app > > and all it

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
On Saturday 19 March 2016 12:32:56 Konstantin Belousov wrote: > On Sat, Mar 19, 2016 at 12:24:11PM +0200, Oleg V. Nauman wrote: > > On Saturday 19 March 2016 12:14:33 Konstantin Belousov wrote: > > > On Sat, Mar 19, 2016 at 09:03:56AM +0200, Oleg V. Nauman wrote: > > > &

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
On Saturday 19 March 2016 21:47:57 Konstantin Belousov wrote: > On Sat, Mar 19, 2016 at 04:03:06PM +0200, Oleg V. Nauman wrote: > > Core was generated by `akonadi_baloo_index'. > > Program terminated with signal SIGABRT, Aborted. > > #0 0x000805630d6a in thr_kill (

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-20 Thread Oleg V. Nauman
On Saturday 19 March 2016 21:47:57 Konstantin Belousov wrote: > On Sat, Mar 19, 2016 at 04:03:06PM +0200, Oleg V. Nauman wrote: > > Core was generated by `akonadi_baloo_index'. > > Program terminated with signal SIGABRT, Aborted. > > #0 0x000805630d6a in thr_kill (

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-22 Thread Oleg V. Nauman
On Monday 21 March 2016 13:22:58 you wrote: > On Mon, Mar 21, 2016 at 12:15:15PM +0200, Oleg V. Nauman wrote: [skip] > > In other words, there is no virtualization involved. > > I think that the problem at hands is not related to clang update. You > recently rebuilt kde li

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-21 Thread Oleg V. Nauman
On Monday 21 March 2016 09:07:10 you wrote: > On Mon, Mar 21, 2016 at 07:21:02AM +0200, Konstantin Belousov wrote: > > On Sun, Mar 20, 2016 at 09:28:13AM +0200, Oleg V. Nauman wrote: > > > Fatal error 'mutex 0x800632000 own 0x1885c 0x1885c is on list 0x0 > > > 0x80d46ebc

Re: Fatal error 'mutex is on list' at line 139 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)

2016-03-19 Thread Oleg V. Nauman
On Friday 18 March 2016 11:55:31 Konstantin Belousov wrote: > On Fri, Mar 18, 2016 at 08:14:57AM +0200, Konstantin Belousov wrote: > > Yes, please. It would be significantly easier to diagnose the problem if > > the minimal example is provided. If not, please pack one crashing app > > and all it

ATA? related trouble with r300299

2016-05-21 Thread Oleg V. Nauman
I have faced the issue with fresh CURRENT stopped to boot on my old desktop after update to r300299 Verbose boot shows the endless cycle of ata2: SATA reset: ports status=0x05 ata2: reset tp1 mask=03 ostat0=50 ostat1=50 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x50 err=0x01

Re: ATA? related trouble with r300299

2016-05-23 Thread Oleg V. Nauman
On Monday 23 May 2016 16:53:55 Kenneth D. Merry wrote: > On Mon, May 23, 2016 at 23:21:32 +0300, Oleg V. Nauman wrote: > > On Monday 23 May 2016 15:25:39 Kenneth D. Merry wrote: > > > On Sat, May 21, 2016 at 09:30:35 +0300, Oleg V. Nauman wrote: > > > > I have face

Re: ATA? related trouble with r300299

2016-05-23 Thread Oleg V. Nauman
On Monday 23 May 2016 15:25:39 Kenneth D. Merry wrote: > On Sat, May 21, 2016 at 09:30:35 +0300, Oleg V. Nauman wrote: > > I have faced the issue with fresh CURRENT stopped to boot on my old > > desktop > > > > after update to r300299 > > Verbose boot shows t

Re: ATA? related trouble with r300299

2016-05-23 Thread Oleg V. Nauman
On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote: > On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wrote: > > On Monday 23 May 2016 17:30:45 you wrote: > > > On Tue, May 24, 2016 at 00:15:25 +0300, Oleg V. Nauman wrote: > > > > On Monday 23 May 2016 1

Re: ATA? related trouble with r300299

2016-05-23 Thread Oleg V. Nauman
> > > On 23/05/2016, 21:25 "Kenneth D. Merry" <k...@freebsd.org> wrote: > > On Sat, May 21, 2016 at 09:30:35 +0300, Oleg V. Nauman wrote: > > I have faced the issue with fresh CURRENT stopped to boot on my old > > desktop > > after update to r300299

Re: ATA? related trouble with r300299

2016-05-23 Thread Oleg V. Nauman
On Monday 23 May 2016 17:11:34 Kenneth D. Merry wrote: > On Tue, May 24, 2016 at 00:05:49 +0300, Oleg V. Nauman wrote: > > On Monday 23 May 2016 16:53:55 Kenneth D. Merry wrote: > > > On Mon, May 23, 2016 at 23:21:32 +0300, Oleg V. Nauman wrote: > > > > On Monday

Re: ATA? related trouble with r300299

2016-05-23 Thread Oleg V. Nauman
On Monday 23 May 2016 17:30:45 you wrote: > On Tue, May 24, 2016 at 00:15:25 +0300, Oleg V. Nauman wrote: > > On Monday 23 May 2016 17:11:34 Kenneth D. Merry wrote: > > > On Tue, May 24, 2016 at 00:05:49 +0300, Oleg V. Nauman wrote: > > > > On Monday 23 May 2016 1

Re: ATA? related trouble with r300299

2016-05-24 Thread Oleg V. Nauman
On Tuesday 24 May 2016 09:21:17 Kenneth D. Merry wrote: > On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote: > > On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote: > > > On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wrote: > > > > On Monday

Re: ATA? related trouble with r300299

2016-05-24 Thread Oleg V. Nauman
On Tuesday 24 May 2016 10:02:09 you wrote: > On Tue, May 24, 2016 at 16:38:40 +0300, Oleg V. Nauman wrote: > > On Tuesday 24 May 2016 09:21:17 Kenneth D. Merry wrote: > > > On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote: > > > > On Monday 23 May 2016 1

Re: ATA? related trouble with r300299

2016-05-24 Thread Oleg V. Nauman
On Tuesday 24 May 2016 13:13:29 Kenneth D. Merry wrote: > On Tue, May 24, 2016 at 18:21:19 +0300, Oleg V. Nauman wrote: > > On Tuesday 24 May 2016 10:02:09 you wrote: > > > On Tue, May 24, 2016 at 16:38:40 +0300, Oleg V. Nauman wrote: > > > > On Tuesday 24 May 2016 0

Re: ATA? related trouble with r300299

2016-05-24 Thread Oleg V. Nauman
On Tuesday 24 May 2016 16:17:33 you wrote: > Okay, I've got a basic idea of what may be going on. The resets that are > getting sent are triggering another probe, which then triggers a reset, > which triggers a probe...and so on. > > So here is another patch that should work for you: > >

CURRENT: frequent crashes if mpd5 is running

2016-07-14 Thread Oleg V. Nauman
I'm experiencing frequent CURRENT ( 12.0-CURRENT r302535 amd64 ) crashes triggered by mpd5: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x10 fault code = supervisor read data, page not present instruction pointer =

Re: CURRENT: frequent crashes if mpd5 is running

2016-07-16 Thread Oleg V. Nauman
On Thursday 14 July 2016 14:38:15 Allan Jude wrote: > On 2016-07-14 13:13, Oleg V. Nauman wrote: > > I'm experiencing frequent CURRENT ( 12.0-CURRENT r302535 amd64 ) crashes > > > > triggered by mpd5: > > > > Fatal trap 12: page fault while in kernel

'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-08 Thread Oleg V. Nauman
After upgrading of current on amd64 box to r313313 I noticed that skype has stopped working. Below is the end of 'truss' output for skype: 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not supported' 36723: write(6,"@",1) = 1 (0x1) 36723: close(6)

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-08 Thread Oleg V. Nauman
UMMY' int \ ^ :160:1: note: expanded from here linux_rt_tsigqueueinfo ^ 2 errors generated. *** Error code 1 It is sources revision 313313 with reverted 313284. > > Best, > Conrad > > On Wed, Feb 8, 2017 at 7:44 AM, Oleg V. Nauman <o.

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-08 Thread Oleg V. Nauman
On Wednesday 08 February 2017 08:39:50 Ngie Cooper wrote: > > On Feb 8, 2017, at 07:44, Oleg V. Nauman <o...@opentransfer.com> wrote: > > > > After upgrading of current on amd64 box to r313313 I noticed that skype > > has > > stopped working. > > Be

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-08 Thread Oleg V. Nauman
, Feb 8, 2017 at 7:44 AM, Oleg V. Nauman <o...@opentransfer.com> wrote: > > After upgrading of current on amd64 box to r313313 I noticed that skype > > has > > > > stopped working. > > > > Below is the end of 'truss' output for skype: >

Buildworld fails if WITHOUT_INET6=YES defined

2017-02-16 Thread Oleg V. Nauman
cc -target i386-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=core2 -DHAVE_CONFIG_H - I/usr/src/lib/libpcap -I/usr/obj/usr/src/lib/libpcap - D_U_="__attribute__((unused))" -DHAVE_SNPRINTF -DHAVE_VSNPRINTF - DBUILDING_PCAP -DHAVE_NET_PFVAR_H

Re: 'make buildworld' failure

2017-01-05 Thread Oleg V. Nauman
On Thursday 05 January 2017 12:26:58 Hiroki Sato wrote: > hiren panchasara <hi...@strugglingcoder.info> wrote > in <20170104180954.gv17...@strugglingcoder.info>: > > hi> + hrs@ > hi> On 01/04/17 at 12:43P, Oleg V. Nauman wrote: > hi> > ===> usr.sbin/

'make buildworld' failure

2017-01-04 Thread Oleg V. Nauman
===> usr.sbin/inetd (all) cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=nehalem -DLOGIN_CAP -DIPSEC - g -MD -MF.depend.inetd.o -MTinetd.o -std=gnu99 -fstack-protector-strong - Wsystem-headers -Werror -Wall -Wno-format-y2k

Re: Buildworld fails if WITHOUT_INET6=YES defined

2017-03-03 Thread Oleg V. Nauman
hat it fixes the issue. > > Thank you! > > Alex Deiter > alex.dei...@gmail.com > > > On 18 Feb 2017, at 00:09, Bryan Drewery <bdrew...@freebsd.org> wrote: > > > > On 2/17/2017 1:03 PM, Bryan Drewery wrote: > >> On 2/16/2017 10:07 AM, Ngie Cooper (y

Re: HEAD/i386 r320212: three reproducible panics

2017-06-30 Thread Oleg V. Nauman
On Friday 23 June 2017 19:42:55 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

Re: HEAD/i386 r320212: three reproducible panics

2017-06-30 Thread Oleg V. Nauman
On Friday 30 June 2017 12:44:37 Hans Petter Selasky wrote: Hello Hans, > On 06/30/17 11:01, Oleg V. Nauman wrote: > > On Friday 23 June 2017 19:42:55 Oleg V. Nauman wrote: > >> a) Panic on shutdown: > >> Fatal trap 1: privileged instruction fault while in kernel m

Re: HEAD/i386 r320212: three reproducible panics [see also bugzilla 220404 about a type of problem introduced in head -r329722 ]

2017-07-01 Thread Oleg V. Nauman
On Friday 30 June 2017 22:45:39 Mark Millard wrote: > [Just for the 3rd backtrace example. . .] > > Oleg V. Nauman oleg at theweb.org.ua wrote on > Fri Jun 23 16:58:07 UTC 2017 : > > .. . . > > > __curthread () at ./machine/pcpu.h:225 > > 225 __asm("

HEAD/i386 r320212: three reproducible panics

2017-06-23 Thread Oleg V. Nauman
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 = base 0x0, limit 0xf, type 0x1b

Re: INO64 Effecting Firefox

2017-05-28 Thread Oleg V. Nauman
On Sunday 28 May 2017 18:09:19 O. Hartmann wrote: > Am Sun, 28 May 2017 08:54:35 -0700 > > Pete Wright schrieb: > > Hi all, > > > > I can't imagine that this is related to INO64, but since upgrading my > > world and kernel on drm-next (which merged upstream CURRENT as of

r323694 amd64 - crash in linsysfs: Was: svn commit: r323692 - in head/sys/compat: linsysfs linux

2017-09-18 Thread Oleg V. Nauman
On Sunday 17 September 2017 23:40:16 Conrad Meyer wrote: > Author: cem > Date: Sun Sep 17 23:40:16 2017 > New Revision: 323692 > URL: https://svnweb.freebsd.org/changeset/base/323692 > > Log: > linsysfs(5): Add support for recent libdrm > > Expose more information about PCI devices (and GPUs

Re: r324421 amd64 kernel panics when entering multiuser mode

2017-10-09 Thread Oleg V. Nauman
On Monday 09 October 2017 05:05:14 Alan Cox wrote: > On Mon, Oct 9, 2017 at 4:22 AM, Oleg V. Nauman <o...@theweb.org.ua> wrote: > > panic: freeing invalid range > > cpuid = 0 > > time = 1507550062 > > Uptime: 2s > > . > > #0 doadump

r324684 amd64 buildworld failed if WITHOUT_ZFS is defined

2017-10-17 Thread Oleg V. Nauman
===> sys/boot/efi/boot1 (all) cc -target x86_64-unknown-freebsd12.0 -- sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -ffreestanding -Wformat -mno-mmx -mno-sse -mno-avx -msoft- float -fshort-wchar -mno-red-zone -mno-aes -march=nehalem - DLOADER_UFS_SUPPORT

Buildworld failure in sys/boot/efi/loader/main.c if WITHOUT_ZFS is defined

2017-09-11 Thread Oleg V. Nauman
===> sys/boot/efi/loader (all) cc -target x86_64-unknown-freebsd12.0 -- sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=nehalem - I/usr/src/sys/boot/efi/loader/../../../../lib/libstand -fPIC - DTERM_EMU -I/usr/src/sys/boot/efi/loader -

HEAD i386 r336217 : wireless connection fails ( ath(4) )

2018-07-13 Thread Oleg V. Nauman
I'm experiencing wireless connection failure after HEAD/i386 update performed today. Below is relevant portion of dmesg buffer: Jul 12 18:43:39 desktop kernel: wlan0: Ethernet address: 18:a6:f7:8a:b1:52 Jul 12 18:43:39 desktop kernel: wlan0: link state changed to UP Jul 12 18:43:39 desktop