> > > Ok, what does 'nmcli dev' and 'nmcli radio' show? > > > > Broken state. > > > > pavel@amd:~$ nmcli dev > > DEVICE TYPE STATE CONNECTION > > eth1 ethernet unavailable -- > > lo loopback unmanaged -- > > wlan0 wifi unmanaged -- > > If the state is "unmanaged" on resume, that would indicate a problem > with sleep/wake and likely not a kernel network device issue. > > We should probably move this discussion to the NM lists to debug > further. Before you suspend, run "nmcli gen log level trace" to turn > on full debug logging, then reproduce the issue, and send a pointer to > those logs (scrubbed for anything you consider sensitive) to the NM > mailing list.
Hmm :-)
root@amd:/data/pavel# nmcli gen log level trace
Error: Unknown log level 'trace'
root@amd:/data/pavel# nmcli gen log level help
Error: Unknown log level 'help'
root@amd:/data/pavel# nmcli gen log level
Error: value for 'level' argument is required.
root@amd:/data/pavel# nmcli gen log level debug
root@amd:/data/pavel# cat /var/log/sys/log
Where do I get the logs? I don't see much in the syslog...
And.. It seems that it is "every other suspend". One resume results in
broken network, one in working one, one in broken one...
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
signature.asc
Description: Digital signature
