Hi!
> >I guess you can't reproduce it easily? I tried bisecting, but while it
> >happens often enough to make v4.17 hard to use, it does not permit
> >reliable bisect.
> >
> >These should be bad according to my notes
> >
> >b04240a33b99b32cf6fbdf5c943c04e505a0cb07
> >
Hi!
> >I guess you can't reproduce it easily? I tried bisecting, but while it
> >happens often enough to make v4.17 hard to use, it does not permit
> >reliable bisect.
> >
> >These should be bad according to my notes
> >
> >b04240a33b99b32cf6fbdf5c943c04e505a0cb07
> >
Pavel Machek wrote:
On Tue 2018-03-20 21:11:54, Woody Suwalski wrote:
Woody Suwalski wrote:
Pavel Machek wrote:
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes
Pavel Machek wrote:
On Tue 2018-03-20 21:11:54, Woody Suwalski wrote:
Woody Suwalski wrote:
Pavel Machek wrote:
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes
Hi!
On Mon 2018-03-26 10:33:55, Dan Williams wrote:
> On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > > >
> > > > Broken state.
> > > >
> > > > pavel@amd:~$ nmcli dev
> > > > DEVICE TYPE STATECONNECTION
> > > >
Hi!
On Mon 2018-03-26 10:33:55, Dan Williams wrote:
> On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > > >
> > > > Broken state.
> > > >
> > > > pavel@amd:~$ nmcli dev
> > > > DEVICE TYPE STATECONNECTION
> > > >
On Sun, 2018-04-15 at 18:16 +0200, Pavel Machek wrote:
> On Mon 2018-03-26 10:33:55, Dan Williams wrote:
> > On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > > > >
> > > > > Broken state.
> > > > >
> > > > > pavel@amd:~$
On Sun, 2018-04-15 at 18:16 +0200, Pavel Machek wrote:
> On Mon 2018-03-26 10:33:55, Dan Williams wrote:
> > On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > > > >
> > > > > Broken state.
> > > > >
> > > > > pavel@amd:~$
On Mon 2018-03-26 10:33:55, Dan Williams wrote:
> On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > > >
> > > > Broken state.
> > > >
> > > > pavel@amd:~$ nmcli dev
> > > > DEVICE TYPE STATECONNECTION
> > > > eth1
On Mon 2018-03-26 10:33:55, Dan Williams wrote:
> On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > > >
> > > > Broken state.
> > > >
> > > > pavel@amd:~$ nmcli dev
> > > > DEVICE TYPE STATECONNECTION
> > > > eth1
On Tue 2018-03-20 21:11:54, Woody Suwalski wrote:
> Woody Suwalski wrote:
> >Pavel Machek wrote:
> >>On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> >>>Pavel Machek wrote:
> Hi!
>
> With recent linux-next, after resume networkmanager often claims that
> "network is disabled".
On Tue 2018-03-20 21:11:54, Woody Suwalski wrote:
> Woody Suwalski wrote:
> >Pavel Machek wrote:
> >>On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> >>>Pavel Machek wrote:
> Hi!
>
> With recent linux-next, after resume networkmanager often claims that
> "network is disabled".
On Mon 2018-03-19 18:33:56, Pavel Machek wrote:
> On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > > Pavel Machek wrote:
> > > > > Hi!
> > > > >
> > > > > With recent
On Mon 2018-03-19 18:33:56, Pavel Machek wrote:
> On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > > Pavel Machek wrote:
> > > > > Hi!
> > > > >
> > > > > With recent
Hi!
I wanted to re-test next (4.16.0-rc7-next-20180329), but that one does
not suspend at all.
I normally suspend by pressing power button in MATE, but that action
currently results in machine hanging.
Pavel
On Mon 2018-03-26
Hi!
I wanted to re-test next (4.16.0-rc7-next-20180329), but that one does
not suspend at all.
I normally suspend by pressing power button in MATE, but that action
currently results in machine hanging.
Pavel
On Mon 2018-03-26
On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > >
> > > Broken state.
> > >
> > > pavel@amd:~$ nmcli dev
> > > DEVICE TYPE STATECONNECTION
> > > eth1ethernet unavailable --
> > > lo loopback unmanaged
On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > >
> > > Broken state.
> > >
> > > pavel@amd:~$ nmcli dev
> > > DEVICE TYPE STATECONNECTION
> > > eth1ethernet unavailable --
> > > lo loopback unmanaged
> > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> >
> > Broken state.
> >
> > pavel@amd:~$ nmcli dev
> > DEVICE TYPE STATECONNECTION
> > eth1ethernet unavailable --
> > lo loopback unmanaged--
> > wlan0 wifi unmanaged--
>
> If the state is
> > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> >
> > Broken state.
> >
> > pavel@amd:~$ nmcli dev
> > DEVICE TYPE STATECONNECTION
> > eth1ethernet unavailable --
> > lo loopback unmanaged--
> > wlan0 wifi unmanaged--
>
> If the state is
Woody Suwalski wrote:
Pavel Machek wrote:
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
Woody Suwalski wrote:
Pavel Machek wrote:
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
Pavel Machek wrote:
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
Pavel Machek wrote:
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
On Tue, 2018-03-20 at 09:03 +0100, Pavel Machek wrote:
> On Mon 2018-03-19 12:45:49, Dan Williams wrote:
> > On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote:
> > > On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > > > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > > > On Mon
On Tue, 2018-03-20 at 09:03 +0100, Pavel Machek wrote:
> On Mon 2018-03-19 12:45:49, Dan Williams wrote:
> > On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote:
> > > On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > > > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > > > On Mon
On Mon 2018-03-19 12:45:49, Dan Williams wrote:
> On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote:
> > On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > > > Pavel Machek
On Mon 2018-03-19 12:45:49, Dan Williams wrote:
> On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote:
> > On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > > > Pavel Machek
On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote:
> On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > > Pavel Machek wrote:
> > > > > Hi!
> > > > >
> > > > > With recent
On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote:
> On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > > Pavel Machek wrote:
> > > > > Hi!
> > > > >
> > > > > With recent
On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > With recent linux-next, after resume networkmanager often claims
> > > > that
> > >
On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > > Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > With recent linux-next, after resume networkmanager often claims
> > > > that
> > >
On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > Pavel Machek wrote:
> > > Hi!
> > >
> > > With recent linux-next, after resume networkmanager often claims
> > > that
> > > "network is disabled". Sometimes suspend/resume clears that.
>
On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote:
> On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> > Pavel Machek wrote:
> > > Hi!
> > >
> > > With recent linux-next, after resume networkmanager often claims
> > > that
> > > "network is disabled". Sometimes suspend/resume clears that.
>
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> Pavel Machek wrote:
> >Hi!
> >
> >With recent linux-next, after resume networkmanager often claims that
> >"network is disabled". Sometimes suspend/resume clears that.
> >
> >Any ideas? Does it work for you?
> >
On Mon 2018-03-19 05:17:45, Woody Suwalski wrote:
> Pavel Machek wrote:
> >Hi!
> >
> >With recent linux-next, after resume networkmanager often claims that
> >"network is disabled". Sometimes suspend/resume clears that.
> >
> >Any ideas? Does it work for you?
> >
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
Pavel
Tried the 4.16-rc6 with nm
Pavel Machek wrote:
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
Pavel
Tried the 4.16-rc6 with nm
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
Pavel
--
(english)
Hi!
With recent linux-next, after resume networkmanager often claims that
"network is disabled". Sometimes suspend/resume clears that.
Any ideas? Does it work for you?
Pavel
--
(english)
40 matches
Mail list logo