[Bug 1971547] [NEW] cyradm fails on jammy
Public bug reported: Running cyradm fails: root@imap ~# cyradm 127.0.0.1 Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.34/auto/Cyrus/IMAP/IMAP.so' for module Cyrus::IMAP: /usr/lib/x86_64-linux-gnu/perl5/5.34/auto/Cyrus/IMAP/IMAP.so: undefined symbol: pcreposix_regexec at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm line 187. at /usr/lib/x86_64-linux-gnu/perl5/5.34/Cyrus/IMAP/Admin.pm line 43. Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.34/Cyrus/IMAP/Admin.pm line 43. BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.34/Cyrus/IMAP/Admin.pm line 43. Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.34/Cyrus/IMAP/Shell.pm line 59. BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.34/Cyrus/IMAP/Shell.pm line 59. Compilation failed in require at /usr/bin/cyradm line 66. BEGIN failed--compilation aborted at /usr/bin/cyradm line 66. I think this is due to an imcompatibility between versions of libpcre, out of my depth commenting further but there's a discussion here: https://www.spinics.net/lists/info-cyrus/msg20361.html reporting the problem in Debian Testing. I have a Debian Bullseye Cyrus IMAP server which works fine. I have: root@imap ~# dpkg -l | grep pcre ii libpcre2-32-0:amd64 10.39-3build1 amd64 New Perl Compatible Regular Expression Library - 32 bit runtime files ii libpcre2-8-0:amd64 10.39-3build1 amd64 New Perl Compatible Regular Expression Library- 8 bit runtime files ii libpcre3:amd64 2:8.39-13build5 amd64 Old Perl 5 Compatible Regular Expression Library - runtime files This is a fresh install of 22.04 with little else installed but: root@imap ~# dpkg -l | grep cyrus ii cyrus-admin 3.4.3-3build2 amd64 Cyrus mail system - administration tools ii cyrus-caldav 3.4.3-3build2 amd64 Cyrus mail system - CalDAV and CardDAV support ii cyrus-clients 3.4.3-3build2 amd64 Cyrus mail system - test clients ii cyrus-common 3.4.3-3build2 amd64 Cyrus mail system - common files ii cyrus-imapd 3.4.3-3build2 amd64 Cyrus mail system - IMAP support ii libcyrus-imap-perl:amd64 3.4.3-3build2 amd64 Interface to Cyrus imap client imclient library ** Affects: cyrus-imapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971547 Title: cyradm fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-imapd/+bug/1971547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956821] Re: System hangs on reboot and shutdown
Can confirm yes also -25 Kernel on Asus PN-50 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956821 Title: System hangs on reboot and shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957018] Re: System hangs on reboot and shutdown
Same issue here on Asus PN50 Ryzen 5 4500U Bios 0623 Also with 5.13.0-23-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957018 Title: System hangs on reboot and shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Same as #31 for me, Mint 20.2 (=Ubuntu 20.04) Nvidia 470.86 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
Thanks again Dan for taking the time to explain. > stop using dig to debug your system. Sorry thought I was using dig at your request... I was originally using nslookup and ping to find out why I couldn't browse to the server on phspi05 (phspi05 is actually controlling the heating and cooling in my glasshouse) and confusingly to me they give different results, ping often works when nslookup fails (as is currently the case on the desktop) > you don't need the router configured to resolve the "single label" (without > .phs) hostname ... I have managed to telnet into the router: # cat /etc/resolv.conf domain phs nameserver 208.67.222.222 nameserver 212.159.6.10 so clearly the domain is set, but if I remove the single label entry from the router even ping fails from the desktop (but still works on the laptop) and it seems that when providing an address via dhcp (e.g. to the laptop) the router puts both phs09 and phs09.phs in /etc/hosts, so I guess the router needs it... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
Thankyou for all the attention to this and the explanations Dan, but now I am also confused... I tend to think that if my desktop is able to successfully lookup the host on the router (as per https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903) then I should expect that my laptop on the same lan, should also be able to do so, hence to me it is still a bug... So to clarify for me, if nothing else: If the router dns only has the hostname defined, i.e. phspi05 192.168.2.35 Lookups by the desktop (no NetworkManager, fixed IP) with resolv.conf containing: nameserver 192.168.2.1 nameserver 127.0.0.53 dig phspi05 = success dig phspi05.phs = fail Lookups by the laptop (with NetworkManager, dhcp assigned IP) with resolv.conf containing: nameserver 127.0.0.53 search phs dig phspi05 = fail dig phspi05.phs = fail dig phspi05 @192.168.2.1 = success dig phspi05.phs @192.168.2.1 = fail If I manually edit resolv.conf on the laptop so that it looks like nameserver 192.168.2.1 nameserver 127.0.0.53 search phs dig phspi05 = success So it seems to me that lookups by systemd-resolved are failing to lookup the hostname on the local DNS (even if this is by design) Whatever way I look at it, I have an inconsistency between computers on the same network. If the router has the hostname AND domainname defined: phspi05 192.168.2.35 phspi05.phs 192.168.2.35 then on the desktop dig phspi05 = success dig phspi05.phs = success on laptop dig phspi05 = fails dig phspi05.phs = success I guess I have a workaround to manually edit resolv.conf, and as I don't reboot that often it is not a big issue, but it doesn't feel right somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
$ dig phspi05.phs ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05.phs ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61787 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;phspi05.phs. IN A ;; Query time: 29 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:08:48 BST 2019 ;; MSG SIZE rcvd: 40 $ dig phspi05.phs @192.168.2.1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05.phs @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21263 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;phspi05.phs. IN A ;; AUTHORITY SECTION: . 3600IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019041700 1800 900 604800 86400 ;; Query time: 20 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:10:11 BST 2019 ;; MSG SIZE rcvd: 115 Hmm... so that is curious... this is making me think, so I have another local host specified on the router DNS, but it is specified with then host and local domain, i.e. on the router I have: sjr05x 192.168.2.20 sjr05x.phs 192.168.2.20 And dig results: $ dig sjr05x ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15618 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;sjr05x.IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:15:06 BST 2019 ;; MSG SIZE rcvd: 35 $ dig sjr05x @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25027 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: ddfb8b62c3075f35 (echoed) ;; QUESTION SECTION: ;sjr05x.IN A ;; ADDITIONAL SECTION: sjr05x. 199150 IN A 192.168.2.20 ;; Query time: 7 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:19:32 BST 2019 ;; MSG SIZE rcvd: 63 $ dig sjr05x.phs ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x.phs ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4826 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;sjr05x.phs.IN A ;; ANSWER SECTION: sjr05x.phs. 6899IN A 192.168.2.20 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:20:16 BST 2019 ;; MSG SIZE rcvd: 55 $ dig sjr05x.phs @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x.phs @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52715 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: b00c84bd6596 (echoed) ;; QUESTION SECTION: ;sjr05x.phs.IN A ;; ADDITIONAL SECTION: sjr05x.phs. 199217 IN A 192.168.2.20 ;; Query time: 5 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:20:39 BST 2019 ;; MSG SIZE rcvd: 67 So is it perhaps that my naive expectation that without a domain the host is assumed to be local is not consistently followed by different programs/devices? Also I now realise that my laptop doesn't know what domain it is part of: $ domainname (none) but then neither does my desktop where the lookups work (not using networkmanager), and explicitly setting it seems to have no effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
Sorry for slow response Dan, here is the output: $ dig phspi05 @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05 @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2588 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 79718a61fe0a1b8b (echoed) ;; QUESTION SECTION: ;phspi05. IN A ;; ADDITIONAL SECTION: phspi05.69314 IN A 192.168.2.35 ;; Query time: 9 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Mon Apr 15 22:15:35 BST 2019 ;; MSG SIZE rcvd: 64 And for completeness, without specifying the server: $ dig phspi05 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37781 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;phspi05. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Mon Apr 15 22:24:42 BST 2019 ;; MSG SIZE rcvd: 36 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
Sorry thought I had responded already: In answer to #5 same result = failure result In answer to #6 For info Router is a Billion BiPAC 7800VDOX Router is set to use public DNS: 208.67.222.222 212.159.6.10 Router is set with domain name of phs Router has a table of static DNS defined: Host IP phspi05 192.168.2.35 etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
Yes, that sounds correct, your reply made me check, if I do: nslookup phspi05.phs I also get the same result... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
Okay thanks for the attention, full output below: $ systemd-resolve --status Global DNS Domain: phs DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: ~. phs $ nslookup phspi05 Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find phspi05: SERVFAIL if I specify the dns in nslookup $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address:192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 ** server can't find phspi05: NXDOMAIN and the contents of resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search phs If I manually edit resolv.conf to the local dns, nslookup, ping etc. work as expected (until the next reboot of course) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] [NEW] DNS lookup fails for local hosts
Public bug reported: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address:192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used >From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
I have installed 1.79ubunbtu10.18.04.3 from the bionic-proposed and rebooted... The result is different from before $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run systemd-resolve --status to see details about the actual nameservers. nameserver 192.168.2.1 nameserver 127.0.0.53 In previous fix 127.0.0.53 was not present $ systemd-resolve --status Global DNS Servers: 192.168.2.1 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa ... All seems to be working as expected. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
Installed resolvconf from bionic-proposed, all seems to working as it should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
Sorry, my bad, it seems I miss read the first part of the wiki! Now installed, will report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
On checking it seems that is the case. Tried a dozen different mirrors all give: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/binary-amd64/Packages 404 Not Found [IP: 91.189.88.150 80] Which mirror do you recommend? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
I followed the instructions at https://wiki.ubuntu.com/Testing/EnableProposed but after repeated updates, it keeps telling me the it is not found: $ sudo apt-get install resolvconf/bionic-proposed Reading package lists... Done Building dependency tree Reading state information... Done E: Release ‘bionic-proposed’ for ‘resolvconf’ was not found drgrumpy@phs08 ~ $ sudo apt-get install resolvconf=1.79ubuntu10.18.04.1 Reading package lists... Done Building dependency tree Reading state information... Done E: Version ‘1.79ubuntu10.18.04.1’ for ‘resolvconf’ was not found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
Testing fix: I added the ppa (same system) and updated resolvconf then did: $ sudo systemctl enable resolvconf-pull-resolved.path OK and $ sudo systemctl enable resolvconf-pull-resolved.service this gives: The unit files have no installation config (not sure if this is expected ?), but it does seem to have operated (see below). Then reboot, and all seems to work as expected, ok cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 192.168.2.1 and the pull service has operated: $ systemctl status resolvconf-pull-resolved.service ● resolvconf-pull-resolved.service Loaded: loaded (/lib/systemd/system/resolvconf-pull-resolved.service; static; Active: inactive (dead) since Thu 2019-02-28 10:26:50 GMT; 10min ago Process: 3359 ExecStart=/bin/sh -c cat /run/systemd/resolve/resolv.conf | /sbi Main PID: 3359 (code=exited, status=0/SUCCESS) Feb 28 10:26:50 phs08 systemd[1]: Starting resolvconf-pull-resolved.service... Feb 28 10:26:50 phs08 systemd[1]: Started resolvconf-pull-resolved.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
Yes that works, and many thanks for the explanation. /etc/resolv.conf is now linked to /run/resolvconf/resolv.conf and contains only the local proxy dns: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 192.168.2.1 and all works as expected But in the long term I guess I should move to systemd-networkd as the preferred way to set static ip? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
Thanks again for the help Removed resolvconf: sudo apt remove resolvconf reboot as expected now /etc/resolv.conf is linked to run/systemd/sub-resolv.conf and contains only: nameserver 127.0.0.53 options edns0 BUT now I cannot connect to anything, nslookup, ping fails, etc. $ ping google.com ping: google.com: Temporary failure in name resolution and $ systemd-resolve --status does not list any dns So I made a guess and added DNS=192.168.2.1 to /etc/systemd/resolved.conf $ sudo systemctl restart systemd-resolved now $ systemd-resolve --status lists dns as 192.168.2.1 and all is good... Additional info: I do not use NetworkManager as I use fixed ip, so the ip, etc. and dns is/was specified in /etc/network/interfaces Seems resolvconf was detecting this and adding the dns to resolv.conf, but systemd-resolve is not looking or detecting ? So it seems to that the issue is really that systemd-resolve is adding the options to resolv.conf when it shouldn't interfere because resolvconf is in charge of it OR that systemd-resolve isn't checking /etc/network/interfaces for dns-nameservers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
Thanks for the attention to this: DNS servers: 208.67.220.220 (opend dns) and 212.159.6.10 (recommended by isp) typical sites: planthealth.co.uk, plus random others... nslookup and dig ok ping domain_name gives "Name or service not known" ping ip ok FF: Hmmm problem etc... So this is my resolv.conf which is def linked to /run/resolvconf/resolv.conf rather than the systemd stub-resolv.conf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 192.168.2.1 nameserver 127.0.0.53 options edns0 I do have resolvconf installed (think I upgreded to Mint 19 from 18.3 so that explains it...)... will remove and report back... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
My update was from 237-3ubuntu10.11, which didn't have the problem (12 was never installed) It seems I cannot easily downgrade via apt or synaptic, as the previous versions do not seem to be in the repos, can you advise how to do so? On a different machine on the same network I still have 237-3ubuntu10.11 and it is working as expected (and I don't want to update!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
It seems this breaks dns lookups on some system, see #1817903 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811471 Title: local resolver stub fails to handle multiple TCP dns queries To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1811471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817903] [NEW] systemd-resolve appends "options edns0" to resolv.conf
Public bug reported: Mint 19 (Ubuntu 18.04) Following latest mint update done on 24/02/2019, DNS is broken nslookup and dig of certain domain names work as expected, ping does not (ip works but not domain name) After a day of trial and error, testing I found that the problem lies with the presence of "options edns0" in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf) With option present many dns lookups fail with both FF and chrome browswers and thunderbird... This is on a home network, with router set as dns proxy for external wan, not using NetworkManager Deleting the option on live system results in the issue immediately disappearing, but on reboot it is added back in (by systemd-resolve ?) I cannot find any option to prevent this being added, so presumably it is hard-coded in systemd following the update? systemd: Installed: 237-3ubuntu10.13 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561943] Re: Stylus coordinates wrong when screen is rotated on Dell Venue 11 Pro 7140
I also have the same issue on Mint 19 on HP Spectre x360 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561943 Title: Stylus coordinates wrong when screen is rotated on Dell Venue 11 Pro 7140 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1561943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Apparently yes. File attached. With: $ cat /proc/cmdline BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-3-generic root=UUID=0885f579-b2ff-4c94-964c-d65c30bb7761 ro rootflags=subvol=@ nvme_core.force_apst=1 I have been at least 8 days without re-booting with suspend/resume a couple of times a day at least. BUT in the meantime I have upgraded to Mint 19 XFCE, so some other issues have a arisen, but prob not due to the kernel. ** Attachment added: "Output from lspci -vvnn" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+attachment/5180352/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
$ cat /proc/cmdline BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-3-generic root=UUID=0885f579-b2ff-4c94-964c-d65c30bb7761 ro rootflags=subvol=@ nvme_core.force_apst=1 Been through several cycles of suspend and resume, without any apparent issues. But I note: $ sudo nvme id-ctrl /dev/nvme0n1 ps0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Ok, testing now... will report back... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Hmmm so if I understand PCIe ASPM would be set in the BIOS. I updated the BIOS to a later version (3803) since the original issue (soon after the last testing at end of Feb). So I guess it may be that it has been disabled in the bios ? I guess I need to go back and try an older non-fixed kernel again and see what happens... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
I have deleted/removed many of the older testing kernel, but I think this one does not have the fix, based on post #97 $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.13.0-34-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro Suspend Resume $ sudo lspci -vvnn > lspci.txt output attached ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+attachment/5152579/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Realise I probably should have run as sudo, so sudo version attached ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+attachment/5152446/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Hi Kai-Heng, Guessing that request is directed at me, so here it is: $ lspci -vvnn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1450] Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:1453] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59) Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:8747] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nvme Kernel modules: nvme 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43bb] (rev 02) (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc. Device [1b21:1142] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: xhci_hcd 02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b7] (rev 02) (prog-if 01 [AHCI 1.0]) Subsystem: ASMedia Technology Inc. Device [1b21:1062] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b2] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz-
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
I am not sure if I have done the correct thing, but following the instructions above I have managed to install xenial-proposed kernel 4.13.0-38 on my Mint 18.2 XFCE system: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.13.0-38-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro I can confirm that APST is disabled by default, and no apparent issues after several cycles of suspend and resume. I can't see any option to add or change tags. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
In case it helps, further test with 4.13.0-34 Feb 24 11:48:40 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.13.0-34-generic root=UUID=f7ae652b-cbf6-48b8-bc6a- d3963957ab57 ro nvme_core.force_apst=1 ... boots fine, appears ok then suspend overnight... Feb 25 11:54:43 phs08 kernel: [ 775.372073] sd 0:0:0:0: [sda] Starting disk Feb 25 11:54:43 phs08 kernel: [ 775.372077] sd 1:0:0:0: [sdb] Starting disk Feb 25 11:54:43 phs08 kernel: [ 775.372156] serial 00:05: activated Feb 25 11:54:43 phs08 kernel: [ 775.555973] r8169 :25:00.0 enp37s0: link down Feb 25 11:54:43 phs08 kernel: [ 775.658010] nvme :01:00.0: RESET SUCCEEDED seems okay for 5 mins... then... Feb 25 11:59:39 phs08 kernel: [ 1072.862588] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Feb 25 11:59:39 phs08 kernel: [ 1072.906660] print_req_error: I/O error, dev nvme0n1, sector 30511480 Feb 25 11:59:40 phs08 kernel: [ 1073.054471] nvme :01:00.0: RESET SUCCEEDED Feb 25 11:59:40 phs08 kernel: [ 1073.054478] nvme :01:00.0: enabling device ( -> 0002) Feb 25 11:59:40 phs08 kernel: [ 1073.054650] nvme nvme0: Removing after probe failure status: -19 Feb 25 11:59:40 phs08 kernel: [ 1073.078418] nvme0n1: detected capacity change from 500107862016 to 0 ... usual i/o errors and hard reset needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Sorry for being so slow, and not sure I have run the correct tests: Command line: BOOT_IMAGE=/vmlinuz-4.13.0-34-generic root=UUID=f7ae652b- cbf6-48b8-bc6a-d3963957ab57 ro Suspend and resume: Feb 24 11:11:14 phs08 kernel: [ 7608.732297] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Feb 24 11:11:14 phs08 kernel: [ 7608.784945] print_req_error: I/O error, dev nvme0n1, sector 136096888 Feb 24 11:11:14 phs08 kernel: [ 7608.784957] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Feb 24 11:11:14 phs08 kernel: [ 7608.944330] nvme :01:00.0: RESET SUCCEEDED Feb 24 11:11:14 phs08 kernel: [ 7608.944337] nvme :01:00.0: enabling device ( -> 0002) Feb 24 11:11:14 phs08 kernel: [ 7608.944496] nvme nvme0: Removing after probe failure status: -19 Feb 24 11:11:14 phs08 kernel: [ 7608.976318] nvme0n1: detected capacity change from 500107862016 to 0 Feb 24 11:11:14 phs08 kernel: [ 7608.976521] print_req_error: I/O error, dev nvme0n1, sector 376046984 Note the force_apst parameter was not used above, tried below with the more recent kernel... Command line: BOOT_IMAGE=/vmlinuz-4.15.0-9-generic root=UUID=f7ae652b- cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.force_apst=1 didn't get to being able to suspend, system hangs requiring reset, : Feb 24 11:24:10 phs08 kernel: [ 567.842115] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] will try again with force apst=1 shortly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Unable to install the file: linux-headers-4.13.0-34-generic_4.13.0-34.37~lp1746340_amd64.deb due to missing dependency libssl1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Yes, but I am bit confused by that other thread, can you direct me to the download of the specific kernel you want me to try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Will this make it into the mainstream kernel updates or how do I track when it is ? I just installed 4.13.0-19 and the issue is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Sorry for slow response. Yes all seems to be fine, I have had 9 days of uptime with numerous suspend and resumes without issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Installed that latest version, can confirm that apst is disabled without the max_latency setting kernel parameter I have also found a new BIOS for the m/b: 0902 So will also try and installing that and revert back to one of the kernels with apst turned on, to see if any difference... or is it possible to turn the apst back on with a kernel parameter ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Output from get-feature: get-feature:0x0c (Autonomous Power State Transition), Current value: 0x01 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 86 ms Idle Transition Power State (ITPS): 3 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 86 ms Idle Transition Power State (ITPS): 3 . Entry[ 2] . Idle Time Prior to Transition (ITPT): 86 ms Idle Transition Power State (ITPS): 3 . Entry[ 3] . Idle Time Prior to Transition (ITPT): 410 ms Idle Transition Power State (ITPS): 4 . Entry[ 4] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 5] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 6] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 7] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 8] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 9] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[10] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[11] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[12] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[13] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[14] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[15] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[16] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[17] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[18] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[19] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[20] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[21] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[22] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[23] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[24] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[25] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[26] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[27] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Oct 26 17:23:41 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic root=UUID=f7ae652b-cbf6-48b8-bc6a- d3963957ab57 ro Suspend... Oct 26 19:00:46 phs08 systemd-sleep[5347]: Suspending system... Resume Oct 26 19:57:11 phs08 kernel: [ 5841.689280] PM: resume of devices complete after 644.551 msecs Oct 26 19:57:11 phs08 kernel: [ 5841.689579] PM: Finishing wakeup. Oct 26 19:57:11 phs08 kernel: [ 5841.689580] OOM killer enabled. ... Oct 26 20:00:29 phs08 kernel: [ 6039.045439] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Oct 26 20:00:29 phs08 kernel: [ 6039.089704] print_req_error: I/O error, dev nvme0n1, sector 12208016 Again it seems to be ~3mins after wakeup that the disk becomes inaccessible... I noticed this, probably unrelated: Oct 26 21:42:45 phs08 kernel: [0.12] ACPI Error: Needed [Integer/String/Buffer], found [Region] 991f1e97f5a0 (20170531/exresop-424) Oct 26 21:42:45 phs08 kernel: [0.12] ACPI Exception: AE_AML_OPERAND_TYPE, Could not execute arguments for [IOB2] (Region) (20170531/nsinit-412) Oc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Sorry for slow response: Command line: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic root=UUID=f7ae652b- cbf6-48b8-bc6a-d3963957ab57 ro Resulted in spontaneous disappearance (no suspend/resume needed): Oct 26 17:20:44 phs08 kernel: [ 3011.057465] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Oct 26 17:20:44 phs08 kernel: [ 3011.089763] print_req_error: I/O error, dev nvme0n1, sector 131608072 Oct 26 17:20:44 phs08 kernel: [ 3011.089770] print_req_error: I/O error, dev nvme0n1, sector 202463672 Will try again to see if reproducible... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
I installed the files, removed the nvme_core.default_ps_max_latency_us=0, did an update-grub and rebooted... failed to boot into graphical interface and then hung... reset needed Command line: BOOT_IMAGE=/vmlinuz-4.14.0-rc4-evo+ryzen root=UUID =f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro Suspect this is the issue: Oct 16 10:40:17 phs08 systemd[1]: Started Light Display Manager. Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Unit entered failed state. Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Failed with result 'exit-code'. Oct 16 10:40:18 phs08 systemd[1]: lightdm.service: Service hold-off time over, scheduling restart. Oct 16 10:40:18 phs08 gpu-manager[2291]: /etc/modprobe.d is not a file Oct 16 10:40:18 phs08 gpu-manager[2291]: message repeated 4 times: [ /etc/modprobe.d is not a file] Oct 16 10:40:18 phs08 gpu-manager[2291]: Error: can't open /lib/modules/4.14.0-rc4-evo+ryzen/updates/dkms Oct 16 10:40:21 phs08 systemd[1]: gpu-manager.service: Start request repeated too quickly. Oct 16 10:40:21 phs08 systemd[1]: Failed to start Detect the available GPUs and deal with any system changes. Oct 16 10:40:21 phs08 systemd[1]: lightdm.service: Start request repeated too quickly. Oct 16 10:40:21 phs08 systemd[1]: Failed to start Light Display Manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Ah ok, so I will need to install 4.14 first ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Kai-Heng, In response to #66, I guess that definitely points to a firmware issue with Samsung drive #67 I will try and let you know... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Kai-Heng, In reply to #66: I guess this is a definite indication that it is a firmware issue. #67: there are only two files to download, on all previous occasions there have been four, is that correct ? Steve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Re: turn off APST completely Tricky... So I have been running with: BOOT_IMAGE=/vmlinuz-4.13.0-8-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 for the last month or so with no issues I suppose APST is about reducing power consumption, but I am not clear how much it saves in my (desktop) case the biggest reduction in power consumption likely comes from being able to suspend the system as a whole, so being able to suspend/resume likely outweighs the benefit of apst, on the other hand for someone with an always on system, or someone that prefers to hibernate or shutdown, having apst enabled could be beneficial... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Ok thanks and for the explanation - makes sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
No, this seems to have been happening all along, if you look at the timings in earlier posts...see post #25 ...but what throws me and makes it more obscure it that the suspend operations are logged on resume, and until yesterday I hadn't ever managed to check the drive was actually alive (I actually had assumed it wasn't, and the apparent delay was just until it was first accessed (var storing the logs is a mountpoint on one of the spinning SATA disks) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Tried that latest one... still fails after suspend but should I be using nvme_core.default_ps_max_latency_us=1500 ? But as I have said before it does bother me that the suspend and resume operations seem to overlap and all are logged on resume. Booted am: Sep 7 10:02:44 phs08 kernel: [0.00] Linux version 4.12.0-14-generic (root@Linux) (gcc version 7.1.0 (Ubuntu 7.1.0-13ubuntu1) ) #15~pm961+reset SMP Wed Sep 6 13:43:27 CST 2017 (Ubuntu 4.12.0-14.15~pm961+reset-generic 4.12.10) Sep 7 10:02:44 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.12.0-14-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro system running all day... from pm-suspend.log: Thu Sep 7 19:34:17 BST 2017: performing suspend Thu Sep 7 20:26:41 BST 2017: Awake. from kernel.log (nothing about any suspend operations prior to wakeup time, i.e. all kernel operations relating to suspend are logged on wakeup !) Sep 7 20:26:41 phs08 kernel: [34307.434357] PM: Syncing filesystems ... done. Sep 7 20:26:41 phs08 kernel: [34307.498356] PM: Preparing system for sleep (mem) ... Sep 7 20:26:41 phs08 kernel: [34311.224400] PM: resume of devices complete after 698.454 msecs Sep 7 20:26:41 phs08 kernel: [34311.224785] PM: Finishing wakeup ... At 20:28 I successfully saved a spreadsheet file to the nvme disk, that was open before the system was suspended (the file is timestamped with 20:28) then Sep 7 20:29:56 phs08 kernel: [34506.017034] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Sep 7 20:29:56 phs08 kernel: [34506.052638] pci_raw_set_power_state: 5 callbacks suppressed Sep 7 20:29:56 phs08 kernel: [34506.052642] nvme :01:00.0: Refused to change power state, currently in D3 Sep 7 20:29:56 phs08 kernel: [34506.052779] nvme nvme0: Removing after probe failure status: -19 etc. So the nvme disk apparently does not become inaccessible until 3 min after the system has woken up ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Also same result with nvme_core.default_ps_max_latency_us=1500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Tried that latest version, same result: Sep 1 16:56:16 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.13.0-8-generic root=UUID=f7ae652b-cbf6-48b8-bc6a- d3963957ab57 ro (Note without nvme_core.default_ps_max_latency_us=1500. hope this was correct) ... Sep 1 17:01:29 phs08 kernel: [ 318.046495] PM: Suspending system (mem) ... Resume system: ... Sep 1 18:07:42 phs08 kernel: [ 688.834876] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Sep 1 18:07:42 phs08 kernel: [ 688.875137] print_req_error: I/O error, dev nvme0n1, sector 134468320 Sep 1 18:07:42 phs08 kernel: [ 688.875148] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Sep 1 18:07:42 phs08 kernel: [ 688.902878] nvme :01:00.0: enabling device ( -> 0002) Sep 1 18:07:42 phs08 kernel: [ 688.903048] nvme nvme0: Removing after probe failure status: -19 Sep 1 18:07:42 phs08 kernel: [ 688.930880] nvme0n1: detected capacity change from 500107862016 to 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Yes, correct I just searched the kernel log and no more "...Refused to change..." since I booted with: Command line: BOOT_IMAGE=/vmlinuz-4.13.0-6-generic root=UUID=f7ae652b- cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=1500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
I haven't yet tried with that latest kernel... but this morning, after 5 days of successful suspend/resume: Aug 30 09:35:19 phs08 kernel: [71904.271956] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Aug 30 09:35:19 phs08 kernel: [71904.320269] print_req_error: I/O error, dev nvme0n1, sector 136098096 Aug 30 09:35:19 phs08 kernel: [71904.320280] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Aug 30 09:35:19 phs08 kernel: [71904.339992] nvme :01:00.0: enabling device ( -> 0002) Aug 30 09:35:19 phs08 kernel: [71904.340163] nvme nvme0: Removing after probe failure status: -19 Aug 30 09:35:19 phs08 kernel: [71904.371974] nvme0n1: detected capacity change from 500107862016 to 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Using http://people.canonical.com/~khfeng/lp1705748-sleep/ with "nvme_core.default_ps_max_latency_us=1500", to disable deepest power state Been through several suspend/resume cycles so far and seems to be ok. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Appreciate all your efforts Kai-Heng Where do I get the latest mainline kernel ? Thanks, Steve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Unfortunately still no joy Aug 21 18:02:54 phs08 kernel: [0.00] Linux version 4.13.0-6-generic (root@linux) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)) #7~lp1705748 SMP Fri Aug 18 17:09:21 CST 2017 (Ubuntu 4.13.0-6.7~lp1705748-generic 4.13.0-rc5) Aug 21 18:02:54 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.13.0-6-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro ... Mon Aug 21 19:55:03 BST 2017: performing suspend Tue Aug 22 02:17:23 BST 2017: Awake. Aug 22 02:21:36 phs08 kernel: [ 6999.857721] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Aug 22 02:21:36 phs08 kernel: [ 6999.901881] print_req_error: I/O error, dev nvme0n1, sector 137284824 Aug 22 02:21:36 phs08 kernel: [ 6999.901892] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Aug 22 02:21:36 phs08 kernel: [ 6999.901933] print_req_error: I/O error, dev nvme0n1, sector 137286408 Aug 22 02:21:36 phs08 kernel: [ 6999.901937] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Aug 22 02:21:36 phs08 kernel: [ 6999.901970] print_req_error: I/O error, dev nvme0n1, sector 137296616 Aug 22 02:21:36 phs08 kernel: [ 6999.901974] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Aug 22 02:21:36 phs08 kernel: [ 6999.902007] print_req_error: I/O error, dev nvme0n1, sector 137284312 Aug 22 02:21:36 phs08 kernel: [ 6999.902010] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Aug 22 02:21:36 phs08 kernel: [ 6999.945333] pci_raw_set_power_state: 5 callbacks suppressed Aug 22 02:21:36 phs08 kernel: [ 6999.945338] nvme :01:00.0: Refused to change power state, currently in D3 Aug 22 02:21:36 phs08 kernel: [ 6999.945503] nvme nvme0: Removing after probe failure status: -19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Sorry for slow feedback Unfortunately the issue is still there: Aug 15 12:52:58 phs08 kernel: [0.00] Linux version 4.11.0-14-generic (root@ryzen) (gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1) ) #20 SMP Wed Aug 9 20:56:51 CST 2017 (Ubuntu 4.11.0-14.20-generic 4.11.12) Aug 15 12:52:58 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro Tue Aug 15 13:31:03 BST 2017: performing suspend Tue Aug 15 14:11:07 BST 2017: Awake. Aug 15 14:11:07 phs08 kernel: [ 2297.422103] nvme nvme0: disabling APST... Aug 15 14:11:07 phs08 kernel: [ 2297.423143] nvme nvme0: setting power state to 0... ... Aug 15 14:11:07 phs08 kernel: [ 2302.067538] PM: resume of devices complete after 1158.582 msecs Aug 15 14:11:07 phs08 kernel: [ 2302.067889] PM: Finishing wakeup. Aug 15 14:11:07 phs08 kernel: [ 2302.067890] Restarting tasks ... done. Aug 15 14:11:09 phs08 kernel: [ 2304.530720] r8169 :25:00.0 enp37s0: link up Aug 15 14:11:13 phs08 kernel: [ 2307.860622] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 15 14:11:13 phs08 kernel: [ 2307.864647] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 15 14:11:13 phs08 kernel: [ 2307.872508] ata1.00: configured for UDMA/133 Aug 15 14:11:13 phs08 kernel: [ 2307.876591] ata2.00: configured for UDMA/133 Aug 15 14:14:02 phs08 kernel: [ 2477.191603] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Aug 15 14:14:02 phs08 kernel: [ 2477.227261] pci_raw_set_power_state: 4 callbacks suppressed Aug 15 14:14:02 phs08 kernel: [ 2477.227266] nvme :01:00.0: Refused to change power state, currently in D3 Aug 15 14:14:02 phs08 kernel: [ 2477.227394] nvme nvme0: Removing after probe failure status: -19 Aug 15 14:14:02 phs08 kernel: [ 2477.255682] nvme0n1: detected capacity change from 500107862016 to 0 It still seems odd to me that this apparently occurs 2-3 mins after the system has woken up... One thing that confuses me is that the suspend operations like: "nvme nvme0: disabling APST..." are recorded as happening after the system has woken up ! Is this a matter of them not being logged until the system has woken up or actually not executing until the system has woken up ?... either way it is confusing to see suspend operations occuring after the system has resumed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Unfortunately there seems another issue with this kernel: The screen/video is blank on resume, I think this is the offending part: ug 8 14:08:50 phs08 kernel: [ 165.478069] nouveau :27:00.0: DRM: resuming fence... Aug 8 14:08:50 phs08 kernel: [ 165.478082] nouveau :27:00.0: DRM: resuming display... Aug 8 14:08:50 phs08 kernel: [ 165.501235] nouveau :27:00.0: DRM: resuming console... Aug 8 14:08:50 phs08 kernel: [ 165.524428] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 8 14:08:50 phs08 kernel: [ 165.541138] ata6.00: configured for UDMA/133 Aug 8 14:08:50 phs08 kernel: [ 165.636931] usb 1-3: reset high-speed USB device number 2 using xhci_hcd Aug 8 14:08:50 phs08 kernel: [ 166.032975] usb 1-8: reset high-speed USB device number 3 using xhci_hcd Aug 8 14:08:50 phs08 kernel: [ 168.723550] r8169 :25:00.0 enp37s0: link up Aug 8 14:08:50 phs08 kernel: [ 169.227911] PM: resume of devices complete after 4181.953 msecs Aug 8 14:08:50 phs08 kernel: [ 169.228289] PM: Finishing wakeup. Aug 8 14:08:50 phs08 kernel: [ 169.228290] OOM killer enabled. Aug 8 14:08:50 phs08 kernel: [ 169.228290] Restarting tasks ... done. Aug 8 14:08:50 phs08 kernel: [ 169.236474] usb 1-3.1: USB disconnect, device number 4 Aug 8 14:08:50 phs08 kernel: [ 169.655196] nouveau :27:00.0: DVI-D-1: EDID is invalid: Aug 8 14:08:50 phs08 kernel: [ 169.655198][00] BAD 00 ff ff ff ff ff ff 00 4c 2d 40 02 39 31 42 4d Aug 8 14:08:50 phs08 kernel: [ 169.655198][00] BAD 09 12 01 03 00 26 1e 78 2a ee 95 a3 54 4c 99 26 Aug 8 14:08:50 phs08 kernel: [ 169.655199][00] BAD 0f 50 54 bf ef 80 81 80 81 40 71 4f 01 01 01 01 Aug 8 14:08:50 phs08 kernel: [ 169.655199][00] BAD 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70 Aug 8 14:08:50 phs08 kernel: [ 169.655199][00] BAD 13 00 78 2d 11 00 00 1e 00 00 00 fd 00 38 4b 1e Aug 8 14:08:50 phs08 kernel: [ 169.655200][00] BAD 51 0e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Aug 8 14:08:50 phs08 kernel: [ 169.655200][00] BAD 79 6e 63 4d 61 73 74 65 72 0a 20 20 00 00 00 ff Aug 8 14:08:50 phs08 kernel: [ 169.655200][00] BAD 00 48 56 4e 51 32 30 30 37 37 35 0a 20 20 00 40 Aug 8 14:08:50 phs08 kernel: [ 169.655202] nouveau :27:00.0: DRM: DDC responded, but no EDID for DVI-D-1 Aug 8 14:08:51 phs08 kernel: [ 169.798065] nouveau :27:00.0: HDMI-A-1: EDID is invalid: Aug 8 14:08:51 phs08 kernel: [ 169.798066][00] BAD 00 ff ff ff ff ff ff 00 4c 2d 40 02 39 31 42 4d Aug 8 14:08:51 phs08 kernel: [ 169.798067][00] BAD 09 12 01 03 00 26 1e 78 2a ee 95 a3 54 4c 99 26 Aug 8 14:08:51 phs08 kernel: [ 169.798067][00] BAD 0f 50 54 bf ef 80 81 80 81 40 71 4f 01 01 01 01 Aug 8 14:08:51 phs08 kernel: [ 169.798068][00] BAD 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70 Aug 8 14:08:51 phs08 kernel: [ 169.798068][00] BAD 13 00 78 2d 11 00 00 1e 00 00 00 fd 00 38 4b 1e Aug 8 14:08:51 phs08 kernel: [ 169.798068][00] BAD 51 0e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 Aug 8 14:08:51 phs08 kernel: [ 169.798068][00] BAD 79 6e 63 4d 61 73 74 65 72 0a 20 20 00 00 00 ff Aug 8 14:08:51 phs08 kernel: [ 169.798069][00] BAD 00 48 56 4e 51 32 30 30 37 33 31 0a 20 20 00 40 Aug 8 14:08:51 phs08 kernel: [ 169.798070] nouveau :27:00.0: DRM: DDC responded, but no EDID for HDMI-A-1 Aug 8 14:08:51 phs08 kernel: [ 169.947663] nouveau :27:00.0: DRM: DDC responded, but no EDID for DVI-D-1 Aug 8 14:08:51 phs08 kernel: [ 170.090561] nouveau :27:00.0: DRM: DDC responded, but no EDID for HDMI-A-1 Aug 8 14:08:53 phs08 kernel: [ 172.189022] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 8 14:08:53 phs08 kernel: [ 172.189048] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 8 14:08:53 phs08 kernel: [ 172.201105] ata1.00: configured for UDMA/133 Aug 8 14:08:53 phs08 kernel: [ 172.201118] ata2.00: configured for UDMA/133 ...but the install of this kernel did not go so smoothly - maybe I did something wron. Previously I downloaded the four files and just double- clicked on each file in file manager to install, but this time it complained and I first had to uninstall the previous version before trying again, with apparent success - is this the correct approach ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Ok, will test and report and back -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
I don't have a dmesg log file (due to systemd ?) but I attach syslog from start of boot with the kernel to when the reset button pressed... Thanks for your attention to this Kai-Heng, really appreciated, Steve. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+attachment/4926544/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
So last night I installed the kernel and it seems the issue persists: Aug 3 02:30:59 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.12.0-9-generic root=UUID=f7ae652b-cbf6-48b8-bc6a- d3963957ab57 ro suspend: Aug 3 02:52:35 phs08 systemd[1]: Reached target Sleep. Aug 3 02:52:35 phs08 systemd[1]: Starting Suspend... Aug 3 02:52:35 phs08 systemd-sleep[5407]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory Aug 3 02:52:35 phs08 systemd-sleep[5408]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. Aug 3 02:52:35 phs08 systemd-sleep[5407]: Suspending system... resume next morning: Aug 3 09:29:21 phs08 kernel: [ 1300.773097] PM: Syncing filesystems ... done. Aug 3 09:29:21 phs08 kern Aug 3 09:29:21 phs08 kernel: [ 1305.552367] PM: resume of devices complete after 1226.588 msecs Aug 3 09:29:21 phs08 kernel: [ 1305.552777] PM: Finishing wakeup. Aug 3 09:29:21 phs08 kernel: [ 1305.552778] OOM killer enabled. Aug 3 09:29:21 phs08 kernel: [ 1305.552778] Restarting tasks ... done. Aug 3 09:29:24 phs08 kernel: [ 1307.942704] r8169 :25:00.0 enp37s0: link up Aug 3 09:29:27 phs08 kernel: [ 1311.521223] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 3 09:29:27 phs08 kernel: [ 1311.533275] ata1.00: configured for UDMA/133 Aug 3 09:29:27 phs08 kernel: [ 1311.581201] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 3 09:29:28 phs08 kernel: [ 1311.593308] ata2.00: configured for UDMA/133 Aug 3 09:32:45 phs08 kernel: [ 1508.852213] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Aug 3 09:32:45 phs08 kernel: [ 1508.896322] nvme :01:00.0: enabling device ( -> 0002) Aug 3 09:32:45 phs08 kernel: [ 1508.896429] nvme nvme0: Removing after probe failure status: -19 Aug 3 09:32:45 phs08 kernel: [ 1508.920265] nvme0n1: detected capacity change from 500107862016 to 0 Aug 3 09:32:45 phs08 kernel: [ 1508.920536] blk_update_request: I/O error, dev nvme0n1, sector 360686080 "Probably need to change the device to full functional state before S3, like how basic power management works" I can't see anything in the logs that relates to this or suggests it is happening, what should I look for ? I notice this in case of relevance Aug 3 09:29:21 phs08 kernel: [ 1303.986393] CPU: 0 PID: 5407 Comm: systemd-sleep Tainted: G OE 4.12.0-9-generic #10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Sorry, I have downloaded but haven't got to testing it yet have had to prioritise the day job... will aim to try this evening and report back tomorrow... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
I have also just noticed that the nvme drive seems to disappear 2 or 3 minutes after the system has re-awakened, so whilst it consistently seems to happen *after* resume from S3, it is not *on* resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Unfortunately there seems no improvement, system boots fine, and operates fine, but nvme disappears again after suspend. However I didn't see any spontaneous disappearance of device (so could be some progress ? but will need to test for longer to be certain) log extracts: Jul 28 09:36:18 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.12.0-8-generic root=UUID=f7ae652b-cbf6-48b8-bc6a- d3963957ab57 ro ...booted and runs fine, then suspend... Jul 28 11:28:57 phs08 systemd-sleep[7216]: Suspending system... ... and resume Jul 28 12:24:36 phs08 kernel: [ 6773.441351] PM: resume of devices complete after 1369.759 msecs Jul 28 12:24:36 phs08 kernel: [ 6773.441664] PM: Finishing wakeup. Jul 28 12:24:36 phs08 systemd-sleep[7216]: System resumed. Jul 28 12:27:40 phs08 kernel: [ 6957.315181] nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 Jul 28 12:27:40 phs08 kernel: [ 6957.339506] nvme :01:00.0: enabling device ( -> 0002) Jul 28 12:27:40 phs08 kernel: [ 6957.339612] nvme nvme0: Removing after probe failure status: -19 Jul 28 12:27:40 phs08 kernel: [ 6957.375614] nvme0n1: detected capacity change from 500107862016 to 0 But one thing I note, is that the kernel records re-starting conventional spinning disks: Jul 28 12:24:36 phs08 kernel: [ 6772.072165] sd 0:0:0:0: [sda] Starting disk Jul 28 12:24:36 phs08 kernel: [ 6772.072166] sd 1:0:0:0: [sdb] Starting disk but there seems no equivalent for the nvme drive (unless "nvme :01:00.0: enabling device ( -> 0002)" is the equivalent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Ok, thanks, will try and report back... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
One curious thing I note, probably irrelevant, is that after resume, there is lots of stuff recorded in the logs that seem to be about suspending.. e.g. Freezing remaing tasks after the computer has resumed... ul 25 01:42:58 phs08 systemd[1]: Reached target Sleep. Jul 25 01:42:58 phs08 systemd[1]: Starting Suspend... Jul 25 01:42:58 phs08 systemd-sleep[5315]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory Jul 25 01:42:58 phs08 systemd-sleep[5316]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. Jul 25 01:42:58 phs08 systemd-sleep[5315]: Suspending system... System is now sleeping, system wakes Jul 25 01:43:33 phs08 kernel: [ 735.437613] PM: Syncing filesystems ... done. Jul 25 01:43:33 phs08 kernel: [ 735.469300] PM: Preparing system for sleep (mem) Jul 25 01:43:33 phs08 kernel: [ 735.469480] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 25 01:43:33 phs08 kernel: [ 735.471929] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 25 01:43:33 phs08 kernel: [ 735.473849] PM: Suspending system (mem) Jul 25 01:43:33 phs08 kernel: [ 735.473869] Suspending console(s) (use no_console_suspend to debug) Jul 25 01:43:33 phs08 kernel: [ 735.474317] sd 1:0:0:0: [sdb] Synchronizing SCSI cache Jul 25 01:43:33 phs08 kernel: [ 735.474394] sd 1:0:0:0: [sdb] Stopping disk Jul 25 01:43:33 phs08 kernel: [ 735.474620] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 25 01:43:33 phs08 kernel: [ 735.482777] sd 0:0:0:0: [sda] Stopping disk Jul 25 01:43:33 phs08 kernel: [ 735.483625] i8042 kbd 00:04: System wakeup enabled by ACPI Jul 25 01:43:33 phs08 kernel: [ 735.483765] nouveau :27:00.0: DRM: suspending console... Jul 25 01:43:33 phs08 kernel: [ 735.483771] nouveau :27:00.0: DRM: suspending display... Jul 25 01:43:33 phs08 kernel: [ 735.505047] nouveau :27:00.0: DRM: evicting buffers... Jul 25 01:43:33 phs08 kernel: [ 735.580082] nouveau :27:00.0: DRM: waiting for kernel channels to go idle... Jul 25 01:43:33 phs08 kernel: [ 735.580105] nouveau :27:00.0: DRM: suspending fence... Jul 25 01:43:33 phs08 kernel: [ 735.581462] nouveau :27:00.0: DRM: suspending object tree... Jul 25 01:43:33 phs08 kernel: [ 737.956791] PM: suspend of devices complete after 2482.515 msecs Jul 25 01:43:33 phs08 kernel: [ 737.957846] PM: late suspend of devices complete after 1.050 msecs Jul 25 01:43:33 phs08 kernel: [ 737.958651] xhci_hcd :28:00.3: System wakeup enabled by ACPI Jul 25 01:43:33 phs08 kernel: [ 737.959028] xhci_hcd :22:00.0: System wakeup enabled by ACPI Jul 25 01:43:33 phs08 kernel: [ 737.959043] r8169 :25:00.0: System wakeup enabled by ACPI Jul 25 01:43:33 phs08 kernel: [ 737.959044] xhci_hcd :03:00.0: System wakeup enabled by ACPI Jul 25 01:43:33 phs08 kernel: [ 743.441059] PM: noirq suspend of devices complete after 5482.825 msecs Jul 25 01:43:33 phs08 kernel: [ 743.441087] ACPI: Preparing to enter system sleep state S3 Jul 25 01:43:33 phs08 kernel: [ 743.761477] PM: Saving platform NVS memory Jul 25 01:43:33 phs08 kernel: [ 743.761495] Disabling non-boot CPUs ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Unfortunately the problem is still there with this 4.11 kernel... After initial install of the kernel and a suspend/resume it all seemed ok, but then after leaving suspended overnight, the disk goes missing again, see extracts below. Jul 25 01:30:54 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.11.0-12-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro ... Jul 25 01:42:58 phs08 systemd-sleep[5315]: Suspending system... Jul 25 01:43:33 phs08 kernel: [ 735.437613] PM: Syncing filesystems ... done. ... Jul 25 01:52:37 phs08 systemd-sleep[5773]: Suspending system... Jul 25 09:08:20 phs08 kernel: [ 1294.739373] PM: Syncing filesystems ... done. ... Jul 25 09:10:24 phs08 systemd[1]: Removed slice User Slice of lightdm. Jul 25 09:11:58 phs08 kernel: [ 1526.953121] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 25 09:12:03 phs08 kernel: [ 1531.977506] pci_raw_set_power_state: 4 callbacks suppressed Jul 25 09:12:03 phs08 kernel: [ 1531.977511] nvme :01:00.0: Refused to change power state, currently in D3 Jul 25 09:12:03 phs08 kernel: [ 1531.977676] nvme nvme0: Removing after probe failure status: -19 Jul 25 09:12:03 phs08 kernel: [ 1531.997538] nvme0n1: detected capacity change from 500107862016 to 0 Jul 25 09:12:03 phs08 kernel: [ 1531.997846] blk_update_request: I/O error, dev nvme0n1, sector 134367992 Jul 25 09:12:03 phs08 kernel: [ 1531.997857] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 ... many i/o errors follow, reset needed to reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Many thanks, suggested kernel now under test... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Many thanks, suggested kernel now under test... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Confirm that removing: nvme_core.default_ps_max_latency_us=0 from boot params results in reproducible problem on resume from suspend. Downloaded and installed 4.13 headers and generic kernel: Linux version 4.13.0-041300rc1-generic Unable to test issue with above kernel. System boots ok, but now fails to suspend, so cannot check result on resume. Starts to suspend, switches off monitors, then hangs and becomes totally unresponsive, but still powered up, fan running, etc, will not resume, requiring power down or reset button to be pressed, no clues in syslog: Jul 22 00:40:05 phs08 systemd[1]: Reached target Sleep. Jul 22 00:40:05 phs08 systemd[1]: Starting Suspend... Jul 22 00:40:05 phs08 systemd-sleep[4059]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory Jul 22 00:40:05 phs08 systemd-sleep[4060]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. Jul 22 00:40:05 phs08 systemd-sleep[4059]: Suspending system... Screens off, keyboard, mouse unresponsive, will not resume from suspend Reset or Power off/on -> re-boots ok System is also much noisier with fan seemingly running at higher speed, but cannot check as it87 will not load. Also notice that asus_wmi is loaded, but this is not a laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918949/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918952/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918950/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918953/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
This is a brand new build, with Mint 18.2 installed intitally with kernel 4.8.53, but upgraded straight away to latest kernel due to using Ryzen cpu. Will try to test with the 4.13 in the next 24 h -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918951/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918948/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918943/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918947/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918945/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918946/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
apport information ** Tags added: apport-collected sonya ** Description changed: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: drgrumpy 2192 F pulseaudio + /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio + /dev/snd/controlC1: drgrumpy 2192 F pulseaudio + DistroRelease: Linux 18.2 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec + InstallationDate: Installed on 2017-07-06 (15 days ago) + InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 + IwConfig: + lono wireless extensions. + + enp37s0 no wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_GB:en + TERM=xterm + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 + ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.10.0-26-generic N/A + linux-backports-modules-4.10.0-26-generic N/A + linux-firmware 1.157.11 + RfKill: + + Tags: sonya + Uname: Linux 4.10.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 06/20/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0805 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME B350M-A + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string +
[Bug 1705748] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1705748/+attachment/4918944/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705748] [NEW] Samsung SSD 960 EVO 500GB refused to change power state
Public bug reported: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: disappears nvme samsunf ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1705748/+attachment/4918878/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Just landed here with similar issue on Samsung 960 EVO 500GB, system crashes/hangs with disk inaccessible (?) but mostly after resume from suspend, or latest 3 mins after cold boot... Kernel 4.10.0-26-generic M/B Asus Prime B350m-A Seems it is either not fixed or I have another bug e.g. Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee: 002538 cmic: 0 mdts: 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes: 0 oacs: 0x7 acl : 7 aerl: 3 frmw: 0x16 lpa : 0x3 elpe: 63 npss: 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa: 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes: 0x66 cqes: 0x44 nn : 1 oncs: 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun: 255 awupf : 0 nvscc : 1 acwu: 0 sgls: 0 ps0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330688] Re: Hidden files are not added with directory
Still an issue in Maverick - really annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/330688 Title: Hidden files are not added with directory -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716433] Re: evolution crashes when using calendar
Dear Mathieu, Sorry for slow response. I actually already obtained a valgrind log at your request and posted it, some time ago, here: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/655405/comments/30 Apologies if I have confused things. Steve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716433 Title: evolution crashes when using calendar -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655405] Re: evolution calendar-, task- and notivication-lists crashes by opening
Apologies for not responding to message #25, been busy with the day job (made more difficult because I can't use my calendar !) If I change the calendar file to ISO-8859-1 it still reads it, but still hangs or crashes in the same way - without any informative info. Mostly when I try to navigate in the calendar view evolution either hangs or close suddenly. I just ran valgrind - log file attached I just followed the steps in #29 When evolution hangs or closes it just says: [New Thread 0x7fffe8def700 (LWP 6121)] Server is up and running... Bye. [Thread 0x7fffe8def700 (LWP 6121) exited] Program exited normally. (gdb) bt full No stack. (gdb) thread apply all bt full (gdb) (this was without the dbsym files - but there weren't any ??? to interpret) ** Attachment added: valgrind.log https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/655405/+attachment/2032377/+files/valgrind.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655405 Title: evolution calendar-, task- and notivication-lists crashes by opening -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434956] Re: screen backlight off after resume-from-suspend when using ATI KMS
Not sure if mine is exactly the same issue: Maverick 64 bit, ATI graphics card Suspend and hibernate worked on 10.04. Following upgrade (clean install) failed to resume from suspend and hibernate. pm-log indicated success, computer powers up, but display is blank. Could successfully suspend/hibernate and resume from recovery console using pm-suspend/hibernate. Adding radeon.modeset=0 meant that suspend and resume now work But this messed up my dual monitor configuration and had to create xorg.conf file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/434956 Title: screen backlight off after resume-from-suspend when using ATI KMS -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590537] Re: lo: Disabled Privacy Extensions keeps showing up in the system log
I also just saw it for the first time when starting chromium, kernel 2.6.35-280generic 64bit. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/590537 Title: lo: Disabled Privacy Extensions keeps showing up in the system log -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 590537] Re: lo: Disabled Privacy Extensions keeps showing up in the system log
I also just saw it for the first time when starting chromium, kernel 2.6.35-280generic 64bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/590537 Title: lo: Disabled Privacy Extensions keeps showing up in the system log -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716433] Re: evolution crashes when using calendar
No improvement with latest kernel update to 2.6.35.-28-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716433 Title: evolution crashes when using calendar -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716433] Re: evolution crashes when using calendar
Mathieu, Thanks for your continued interest: Running with the sync option as suggested evolution flashes up briefly, then immediately closes, before any chance to interact with it, resulting in similar but different errors with each attempt (mostly they don't seem too helpful), see below, but on one occasion I got a more extensive output (at the bottom), not sure if it helps: This is the most common outcome drgrumpy@sjr06x:~$ evolution -c calendar --sync EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. drgrumpy@sjr06x:~$ evolution -c calendar --sync EI: MAIL PREFS*** glibc detected *** evolution: free(): corrupted unsorted chunks: 0x03363c00 *** Segmentation fault drgrumpy@sjr06x:~$ evolution -c calendar --sync EI: MAIL PREFSThe program 'evolution' received an X Window System error. This probably reflects a bug in the program. The error was 'BadGC (invalid GC parameter)'. (Details: serial 4010 error_code 13 request_code 66 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) drgrumpy@sjr06x:~$ evolution -c calendar --sync EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. The program 'evolution' received an X Window System error. This probably reflects a bug in the program. The error was 'BadGC (invalid GC parameter)'. (Details: serial 3996 error_code 13 request_code 60 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) drgrumpy@sjr06x:~$ evolution -c calendar --sync EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Once I got this: drgrumpy@sjr06x:~$ evolution -c calendar --sync EI: MAIL PREFS*** glibc detected *** evolution: double free or corruption (out): 0x0217a6e0 *** === Backtrace: = /lib/libc.so.6(+0x774b6)[0x7f4af64b44b6] /lib/libc.so.6(cfree+0x73)[0x7f4af64bac83] /usr/lib/libX11.so.6(+0x4a362)[0x7f4af34ed362] /usr/lib/libX11.so.6(_XReply+0x140)[0x7f4af34ed9b0] /usr/lib/libX11.so.6(XSync+0x63)[0x7f4af34e1333] /usr/lib/libX11.so.6(+0x3e4eb)[0x7f4af34e14eb] /usr/lib/libX11.so.6(XFreeGC+0xa4)[0x7f4af34c73f4] /usr/lib/libgdk-x11-2.0.so.0(+0x5eb98)[0x7f4af8d43b98] /usr/lib/libgobject-2.0.so.0(g_object_unref+0x174)[0x7f4af70c3e14] /usr/lib/evolution/2.30/libetable.so.0(+0x26875)[0x7f4af513b875] /usr/lib/evolution/2.30/libetable.so.0(+0x228dd)[0x7f4af51378dd] /usr/lib/evolution/2.30/libetable.so.0(+0x44028)[0x7f4af5159028] /usr/lib/evolution/2.30/libetable.so.0(+0x44144)[0x7f4af5159144] /usr/lib/evolution/2.30/libetable.so.0(+0x441b4)[0x7f4af51591b4] /usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x60)[0x7f4af70c4270] /usr/lib/evolution/2.30/libetable.so.0(+0x3975f)[0x7f4af514e75f] /usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x60)[0x7f4af70c4270] /usr/lib/evolution/2.30/libetable.so.0(+0x35fac)[0x7f4af514afac] /usr/lib/evolution/2.30/libetable.so.0(+0x36168)[0x7f4af514b168] /usr/lib/evolution/2.30/libetable.so.0(+0x56915)[0x7f4af516b915] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f4af70c1a6e] /usr/lib/libgobject-2.0.so.0(+0x24de7)[0x7f4af70d7de7] /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7e6)[0x7f4af70d92a6] /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83)[0x7f4af70d9863] /usr/lib/evolution/2.30/libevolution-calendar.so.0(+0x3d67f)[0x7f4aeccf067f] /usr/lib/evolution/2.30/libevolution-calendar.so.0(+0x9159b)[0x7f4aecd4459b] /usr/lib/evolution/2.30/libevolution-calendar.so.0(+0x9101e)[0x7f4aecd4401e] /lib/libglib-2.0.so.0(+0x6b73f)[0x7f4af682b73f] /lib/libglib-2.0.so.0(+0x697e4)[0x7f4af68297e4] /lib/libpthread.so.0(+0x7971)[0x7f4afa7d3971] /lib/libc.so.6(clone+0x6d)[0x7f4af652392d] === Memory map: 0040-00404000 r-xp 08:08 267745 /usr/bin/evolution 00603000-00604000 r--p 3000 08:08 267745 /usr/bin/evolution 00604000-00605000 rw-p 4000 08:08 267745 /usr/bin/evolution 014d2000-023bc000 rw-p 00:00 0 [heap] 7f4ad400-7f4ad4083000 rw-p 00:00 0 7f4ad4083000-7f4ad800 ---p 00:00 0 7f4ad872e000-7f4ad8732000 r-xp 08:08 267857 /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so 7f4ad8732000-7f4ad8931000 ---p 4000 08:08 267857
[Bug 716433] Re: evolution crashes when using calendar
Also .xsession-errors attached ** Attachment added: .xsession-errors https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/716433/+attachment/1901386/+files/.xsession-errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716433 Title: evolution crashes when using calendar -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655405] Re: evolution calendar-, task- and notivication-lists crashes by opening
Any action going to happen on this ? or do I abandon evolution all together - it is driving me nuts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655405 Title: evolution calendar-, task- and notivication-lists crashes by opening -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716433] Re: evolution crashes when using calendar
There are no crash files in /var/crash, in either the previous installation (10.04) or the new one (10.10). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716433 Title: evolution crashes when using calendar -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655405] Re: evolution calendar-, task- and notivication-lists crashes by opening
I have been having a similar problem in lucid, reported here: https://bugs.launchpad.net/bugs/716433 ...and upgraded to Maverick in the hope that this would go away - it doesn't and is now even worse... if I attempt to open the calendar it either crashes without any warnings or just hangs and has to be forced to close. My calendar ics file is utf-8/windows and I even deleted my original - still same problem with new file. There seem to be lots of similar issues with calendar in evolution. This is going to drive me back to windows in order to use outlook. Steve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655405 Title: evolution calendar-, task- and notivication-lists crashes by opening -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
