On Wed, Oct 14, 2015 at 20:11:08 -0400, Josh Boyer wrote:
> The module is already included in that, as those are build from
> rawhide sources.
Indeed; I had missed the .xz extension when searching.
Thanks,
--Ben
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
On Wed, Oct 14, 2015 at 8:06 PM, Ben Boeckel wrote:
> On Wed, 14 Oct, 2015 at 12:53:43 GMT, Josh Boyer wrote:
>> The kernel module is included in the rawhide (and only rawhide)
>> kernels
>
> Would it be possible to enable it for the kernels from the
> fedora-rawhide-kernel-nodebug repository?
Th
On Wed, 14 Oct, 2015 at 12:53:43 GMT, Josh Boyer wrote:
> The kernel module is included in the rawhide (and only rawhide)
> kernels
Would it be possible to enable it for the kernels from the
fedora-rawhide-kernel-nodebug repository?
Thanks,
--Ben
--
devel mailing list
devel@lists.fedoraproject
On Wed, Oct 14, 2015 at 08:53:43AM -0400, Josh Boyer wrote:
> >> How do I tell? Anyway I didn't take any explicit step to enable it.
> >> The machine has just been 'dnf update'-d to Rawhide.
> > As I understand it, the plan was to switch it on in rawhide, but I'm
> No.
Thanks — I definitely remem
On Wed, Oct 14, 2015 at 08:49:18AM -0400, Matthew Miller wrote:
> On Wed, Oct 14, 2015 at 10:10:54AM +0100, Richard W.M. Jones wrote:
> > > Is kdbus enabled?
> > How do I tell? Anyway I didn't take any explicit step to enable it.
> > The machine has just been 'dnf update'-d to Rawhide.
>
> As I u
On Wed, Oct 14, 2015 at 8:49 AM, Matthew Miller
wrote:
> On Wed, Oct 14, 2015 at 10:10:54AM +0100, Richard W.M. Jones wrote:
>> > Is kdbus enabled?
>> How do I tell? Anyway I didn't take any explicit step to enable it.
>> The machine has just been 'dnf update'-d to Rawhide.
>
> As I understand it
On Wed, Oct 14, 2015 at 10:10:54AM +0100, Richard W.M. Jones wrote:
> > Is kdbus enabled?
> How do I tell? Anyway I didn't take any explicit step to enable it.
> The machine has just been 'dnf update'-d to Rawhide.
As I understand it, the plan was to switch it on in rawhide, but I'm
not sure what
On Tue, Oct 13, 2015 at 05:31:04PM -0400, Matthew Miller wrote:
> On Tue, Oct 13, 2015 at 10:21:09PM +0100, Richard W.M. Jones wrote:
> > > Is it DNS? That's my go-to blame victim for ssh delays.
> > I think it's dbus actually:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1271394#c3
>
> Is kdbu
On 14.10.2015 00:13, Richard W.M. Jones wrote:
On Tue, Oct 13, 2015 at 03:00:27PM -0600, Chris Murphy wrote:
Maybe strace will show where it gets hung up?
Tried it of course - strace doesn't work across the setuid boundary.
Maybe I can attach a trace tool (which?) to sshd (how?) and find out
On Tue, Oct 13, 2015 at 3:37 PM, Chris Murphy wrote:
> On Tue, Oct 13, 2015 at 3:31 PM, Matthew Miller
> wrote:
>> On Tue, Oct 13, 2015 at 10:21:09PM +0100, Richard W.M. Jones wrote:
>>> > Is it DNS? That's my go-to blame victim for ssh delays.
>>> I think it's dbus actually:
>>> https://bugzilla
On Tue, Oct 13, 2015 at 3:31 PM, Matthew Miller
wrote:
> On Tue, Oct 13, 2015 at 10:21:09PM +0100, Richard W.M. Jones wrote:
>> > Is it DNS? That's my go-to blame victim for ssh delays.
>> I think it's dbus actually:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1271394#c3
>
> Is kdbus enabled?
19844 22:16:16.857460 ppoll([{fd=8, events=POLLIN}], 1, {24,
999885000}, NULL, 8) = 0 (Timeout)
19844 22:16:41.864999
open("/usr/share/locale/en_GB.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
That's a huge gap while nothing at all is showing up in the strace.
On Tue, Oct 13, 2015 at 10:21:09PM +0100, Richard W.M. Jones wrote:
> > Is it DNS? That's my go-to blame victim for ssh delays.
> I think it's dbus actually:
> https://bugzilla.redhat.com/show_bug.cgi?id=1271394#c3
Is kdbus enabled?
--
Matthew Miller
Fedora Project Leader
--
devel mailing list
On Tue, Oct 13, 2015 at 05:16:17PM -0400, Matthew Miller wrote:
> On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote:
> > * On x86_64, ssh logins take quite a long time - about 30 seconds. I
> > have no idea what component to assign this to, so I didn't file a
> > bug about it
On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote:
> * On x86_64, ssh logins take quite a long time - about 30 seconds. I
> have no idea what component to assign this to, so I didn't file a
> bug about it yet.
Is it DNS? That's my go-to blame victim for ssh delays.
--
Matth
On Tue, Oct 13, 2015 at 03:00:27PM -0600, Chris Murphy wrote:
> Maybe strace will show where it gets hung up?
Tried it of course - strace doesn't work across the setuid boundary.
Maybe I can attach a trace tool (which?) to sshd (how?) and find out
where it is spending its time. This stuff should
Maybe strace will show where it gets hung up?
---
Chris Murphy
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, Oct 13, 2015 at 09:11:59PM +0100, Richard W.M. Jones wrote:
> On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote:
> > * On x86_64, ssh logins take quite a long time - about 30 seconds. I
> > have no idea what component to assign this to, so I didn't file a
> > bug about
On Tue, Oct 13, 2015 at 08:58:13PM +0100, Richard W.M. Jones wrote:
> * On x86_64, ssh logins take quite a long time - about 30 seconds. I
> have no idea what component to assign this to, so I didn't file a
> bug about it yet.
Not just logins, 'sudo bash' too.
Rich.
--
Richard Jones, Virtu
A couple of things:
* systemd in aarch64 crashes on boot:
https://bugzilla.redhat.com/show_bug.cgi?id=1271387
* On x86_64, ssh logins take quite a long time - about 30 seconds. I
have no idea what component to assign this to, so I didn't file a
bug about it yet.
Rich.
--
Richard Jones,
20 matches
Mail list logo