Hi, I've encountered cp(1) process stuck in the vnread state on one of my
build machines that got recently upgraded to 10.3.
0 79596 1 0 20 0 170921396 wait I 1 0:00.00
/bin/sh /usr/local/bin/autoreconf -f -i
0 79602 79596 0 52 0 414889036 wait I
Hello,
Would it be possible this has to do with the resolved 'system hangs when
using ZFS caused by VFS' in 10.3-BETA3?
https://lists.freebsd.org/pipermail/freebsd-stable/2016-February/084238.html
Regards,
Ronald.
On Wed, 02 Mar 2016 10:12:31 +0100, Maxim Sobolev
wrote:
Hi, I've encoun
On Wed, Mar 02, 2016 at 01:12:31AM -0800, Maxim Sobolev wrote:
> Hi, I've encountered cp(1) process stuck in the vnread state on one of my
> build machines that got recently upgraded to 10.3.
>
>0 79596 1 0 20 0 170921396 wait I 1 0:00.00
> /bin/sh /usr/local/bin/au
Am 01.03.2016 um 23:08 schrieb Ian Lepore
mailto:i...@freebsd.org>>:
On Tue, 2016-03-01 at 19:58 +, Holger Kipp wrote:
Hi all,
I currently encounter a problem with sending faxes with new server
and FreeBSD 10.2-RELEASE p12
using mgetty+sendfax and RS232-Modems via USB to RS232-Adapter (com,
Thanks, Konstantin.
Re: md(4) state:
0 88688 0 0 -8 0 0 16 tx->tx_s DL- 0:45.43
[md0]
Its backtrace:
About the backtrace, indeed, looks like you are right and some portion of
it is not decoded properly, as it's loaded as a kernel module. The setup is
somewhat ev
On Wed, Mar 02, 2016 at 03:02:02AM -0800, Maxim Sobolev wrote:
> Thanks, Konstantin.
>
> Re: md(4) state:
>
>0 88688 0 0 -8 0 0 16 tx->tx_s DL- 0:45.43
> [md0]
>
> Its backtrace:
So md is stuck in ZFS.
___
freebsd-stabl
Sorry gmail hit set too early. Backtrace from the md worker:
[Switching to thread 357 (Thread 101131)]#0 0x8095244e in
sched_switch ()
(kgdb) bt
#0 0x8095244e in sched_switch ()
#1 0x809313b1 in mi_switch ()
#2 0x8097089a in sleepq_wait ()
#3 0x808d344d
Hi!
How come there is no support for “ready" and “error" leds on the soekris 6501
even though it seems fairly easy to control them?
Please see
http://www.mail-archive.com/soekris-tech@lists.soekris.com/msg06738.html and
http://ross.vc/?p=183
smime.p7s
Description: S/MIME cryptographic sign
On Wed, 2 Mar 2016 18:21:15 +0100
Peter Ankerstål wrote:
> Hi!
>
> How come there is no support for “ready" and “error" leds on the soekris 6501
> even though it seems fairly easy to control them?
>
> Please see
> http://www.mail-archive.com/soekris-tech@lists.soekris.com/msg06738.html and
>
On 3/2/2016 10:43 AM, Xin LI wrote:
> Author: delphij
> Date: Wed Mar 2 15:43:01 2016
> New Revision: 296317
> URL: https://svnweb.freebsd.org/changeset/base/296317
>
Hi,
On installworld, I get
===> secure (install)
===> secure/lib (install)
===> secure/lib/libcrypto (install)
install
On Monday, February 29, 2016 07:29:03 PM Harry Schmalzbauer wrote:
> Bezüglich Harry Schmalzbauer's Nachricht vom 28.02.2016 20:55 (localtime):
> > Hello,
> >
> > I have a remote machine with a probably defective ODD, but until r294989
> > (from Jan 28th) I could boot with just these warnings:
>
Hrm this is really weird! Sorry I can't debug this right now, but
please do keep us posted if you have new findings.
One quick guess: Can you confirm if your system clock is correct?
Cheers,
On Wed, Mar 2, 2016 at 12:10 PM, Mike Tancsa wrote:
> On 3/2/2016 10:43 AM, Xin LI wrote:
>> Author: de
Hello,
This is regarding 9-STABLE. All of the 9-STABLE boxes
that have Xorg installed, and running on them, insist on
opening TCP port 6000; as reported by sockstat(1)
Xorg 1295 1 tcp6 *:6000*:*
Xorg 1295 3 tcp4 *:6000*:*
I see that the (curren
On Wed, Mar 2, 2016 at 12:40 PM, Chris H wrote:
> Hello,
> This is regarding 9-STABLE. All of the 9-STABLE boxes
> that have Xorg installed, and running on them, insist on
> opening TCP port 6000; as reported by sockstat(1)
>
> Xorg 1295 1 tcp6 *:6000*:*
> Xorg 12
On Wed, Mar 2, 2016 at 3:40 PM, Chris H wrote:
> startx -nolisten tcp
That would pass it to the session, not the server.
startx -- -nolisten tcp
(startx [[/path/to/session/start] session parameters] [-- [/path/to/server]
[:display] server parameters], see xinit manpage)
--
brandon s all
On 3/2/2016 3:40 PM, Xin LI wrote:
> Hrm this is really weird! Sorry I can't debug this right now, but
> please do keep us posted if you have new findings.
>
> One quick guess: Can you confirm if your system clock is correct?
The strange thing is that I did it on 2 other boxes and could not
repr
On Wed, 2 Mar 2016 12:44:18 -0800 Freddie Cash wrote
> On Wed, Mar 2, 2016 at 12:40 PM, Chris H wrote:
>
> > Hello,
> > This is regarding 9-STABLE. All of the 9-STABLE boxes
> > that have Xorg installed, and running on them, insist on
> > opening TCP port 6000; as reported by sockstat(1)
> >
>
On Wed, Mar 2, 2016 at 3:56 PM, Chris H wrote:
> Good catch, by both you, and Brandon. I just tried it. But
> sockstat(1) still reports 6000 being open. Closing the X
> server, and session, reveal that 6000 is no longer open.
> Bummer.
>
Check `man 7 Xserver` to verify the option needed. You mig
On Wed, 2 Mar 2016 15:59:57 -0500 Brandon Allbery wrote
> On Wed, Mar 2, 2016 at 3:56 PM, Chris H wrote:
>
> > Good catch, by both you, and Brandon. I just tried it. But
> > sockstat(1) still reports 6000 being open. Closing the X
> > server, and session, reveal that 6000 is no longer open.
> >
Thanks Ronald, I think this is at least a possibility that it's related,
I've bumped myself up to the latest FreeBSD 10.3-BETA3 (svn revision
296326) and compiled nullfs statically, so I'll run those builds and see
how it goes.
-Max
On Wed, Mar 2, 2016 at 1:32 AM, Ronald Klop wrote:
> Hello,
>
On Mon, Feb 29, 2016 at 03:28:37PM +1100, Dewayne Geraghty wrote:
That's a nuisance!
As I said, IF I load the module before the kernel, I'm good as follows.
However if I load after booting, then I don't have any frequencies to
choose from.
I'm afraid the only "help" I can provide is of my work
On Wed, 2 Mar 2016 20:50:11 -0500 kpn...@pobox.com wrote
> On Wed, Mar 02, 2016 at 02:54:53PM -0800, Chris H wrote:
> > #!/bin/sh -
> > /usr/local/bin/startx -- -nolisten tcp
> >
> > exit
> >
> > which seems to get the job done, and allow me to be lazy
> > at the CLI. :-)
>
> Personally, I'd go
>>
>> How come there is no support for “ready" and “error" leds on the soekris
>> 6501 even though it seems fairly easy to control them?
>>
>
> a) perhaps no developer have that board?
> b) nobody has written the necessary code to do so?
>
c) There is no generally accepted meaning for what
Mike Tancsa writes:
> I noticed on a server that I updated on Friday that incorporates
> r295367, some lightweight clients that were using aes128-cbc are now
> failing to connect. Is this a planned change ? If so, perhaps a heads
> up in UPDATING ?
Please file a bug and send me the number. I wi
On 03/03/2016 04:18 AM, Tom Samplonius wrote:
How come there is no support for “ready" and “error" leds on the soekris 6501
even though it seems fairly easy to control them?
a) perhaps no developer have that board?
b) nobody has written the necessary code to do so?
c) There is no genera
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463
--- Comment #5 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Thu Mar 3 07:16:36 UTC 2016
New revision: 296340
URL: https://svnweb.freebsd.org/changeset/base/296340
Log:
MFC: r296025:
pf: Fix possible
26 matches
Mail list logo
