[Bug 2063949] Re: Snap won't work with encrypted home folder

[Black Knight]

** Description changed:

  Other snaps work fine with encrypted home folder of my Ubuntu 16.04.7
  O.S.
  
  But chromium snap won't work or start , with the following error output
  ;
  
  ```
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 
0): cannot open directory "/usr/local/share": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/javascript/jquery /usr/share/javascript/jquery 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc 
/usr/share/javascript/sphinxdoc none bind,ro 0 0): cannot open directory 
"/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/sam": permission denied
  snap-update-ns failed with code 1
  
  ```
  
  Other snaps work fine.
  
  Snap version & info ;
  
  ```
  snap2.62
  snapd   2.62
  series  16
  ubuntu  16.04
  kernel  4.15.0-224-generic
  
  ```
  
- P.S. Subscribed to Ubuntu pro , if that matters.
+ * Have encrypted home folder.

** Summary changed:

- Snap won't work with encrypted home folder
+ Snap won't work/start

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063949

Title:
  Snap won't work/start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063949/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063949] Re: Snap won't work with encrypted home folder

[Black Knight]

** Description changed:

  Other snaps work fine with encrypted home folder of my Ubuntu 16.04.7
  O.S.
  
  But chromium snap won't work or start , with the following error output
  ;
  
  ```
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 
0): cannot open directory "/usr/local/share": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/javascript/jquery /usr/share/javascript/jquery 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc 
/usr/share/javascript/sphinxdoc none bind,ro 0 0): cannot open directory 
"/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/sam": permission denied
  snap-update-ns failed with code 1
  
  ```
  
- 
  Other snaps work fine.
  
  Snap version & info ;
  
  ```
  snap2.62
  snapd   2.62
  series  16
  ubuntu  16.04
  kernel  4.15.0-224-generic
  
  ```
  
- P.S Subscribed to Ubuntu pro , if that matters.
+ P.S. Subscribed to Ubuntu pro , if that matters.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063949

Title:
  Snap won't work with encrypted home folder

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063949/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063949] [NEW] Snap won't work with encrypted home folder

[Black Knight]

Public bug reported:

Other snaps work fine with encrypted home folder of my Ubuntu 16.04.7
O.S.

But chromium snap won't work or start , with the following error output
;

```
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 
0): cannot open directory "/usr/local/share": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot open directory "/var/lib/snapd": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/javascript/jquery /usr/share/javascript/jquery 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc 
/usr/share/javascript/sphinxdoc none bind,ro 0 0): cannot open directory 
"/var/lib/snapd": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme 
none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied
cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/sam": permission denied
snap-update-ns failed with code 1

```

Other snaps work fine.

Snap version & info ;

```
snap2.62
snapd   2.62
series  16
ubuntu  16.04
kernel  4.15.0-224-generic

```

P.S. Subscribed to Ubuntu pro , if that matters.

** Affects: chromium-browser (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/2063949

Title:
  Snap won't work with encrypted home folder

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063949/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1899439] Re: MariaDB Unspecified Vulnerability

[Daniel Black]

10.1.48 is now in bionic and this can be closed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1899439

Title:
  MariaDB Unspecified Vulnerability

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1899439/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1903040] Re: MariaDB Multiple Denial of Service Vulnerabilities

[Daniel Black]

10.1.48 is now in bionic and this can be closed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1903040

Title:
  MariaDB Multiple Denial of Service Vulnerabilities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1903040/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971226] Re: package mariadb-server-10.6 (not installed) failed to install/upgrade: new mariadb-server-10.6 package pre-installation script subprocess returned error exit status 1

[Daniel Black]

same as #1970671

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971226

Title:
  package mariadb-server-10.6 (not installed) failed to install/upgrade:
  new mariadb-server-10.6 package pre-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1971226/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970671] Re: package mariadb-server-10.6 1:10.6.7-2ubuntu1 failed to install/upgrade: new mariadb-server-10.6 package pre-installation script subprocess returned error exit status 1

[Daniel Black]

from DpkgTerminalLog.txt:

Preparing to unpack .../00-mariadb-server-10.6_1%3a10.6.7-2ubuntu1_amd64.deb ...
/var/lib/mysql: found previous version 8.0

This is mariadb refusing to install over MySQL-8.0. It can't auto-
upgrade from MySQL-8.0 so it gracefully fails rather than destroying
your data.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970671

Title:
  package mariadb-server-10.6 1:10.6.7-2ubuntu1 failed to
  install/upgrade: new mariadb-server-10.6 package pre-installation
  script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970671/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Could it be  -flto/-ffat-lto-objects related (like
https://jira.mariadb.org/browse/MDEV-25633)? The top part of the stack
trace looks the same.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970634

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6

[Daniel Black]

See https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634
as its the same problem.

While my 10.6.8-MariaDB-1:10.6 test above what built in an ubuntu-22.04
container, it quite possibly used different compile options than what
produces the packages. As the regions of code of the assertions haven't
changed from 10.6.7, 10.6.8 is unlikely to be a magic fix.

For the moment setting innodb_use_native_aio=0 will avoid the problem
ref: https://mariadb.com/kb/en/innodb-system-
variables/#innodb_use_native_aio

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969160

Title:
  mariadb [ERROR] mysqld got signal 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

On the assembly generated by create_linux_aio (in the mariadbd packages
in Ubuntu-22.04, 10.6.7-2:

(gdb) disassemble tpool::create_linux_aio,+200
Dump of assembler code from 0x5640cf2e1fb0 to 0x5640cf2e2078:
   0x5640cf2e1fb0 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+0>:  
endbr64 
   0x5640cf2e1fb4 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+4>:  
push   %rbp
   0x5640cf2e1fb5 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+5>:  
mov%rsp,%rbp
   0x5640cf2e1fb8 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+8>:  
push   %r14
   0x5640cf2e1fba <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+10>: 
mov%esi,%r14d
   0x5640cf2e1fbd <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+13>: 
push   %r13
   0x5640cf2e1fbf <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+15>: 
mov%rdi,%r13
   0x5640cf2e1fc2 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+18>: 
mov$0x158,%edi
   0x5640cf2e1fc7 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+23>: 
push   %r12
   0x5640cf2e1fc9 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+25>: 
sub$0x8,%rsp
   0x5640cf2e1fcd <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+29>: 
call   0x5640ceacb570 <_Znwm@plt>
   0x5640cf2e1fd2 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+34>: 
mov%r14d,%edx
   0x5640cf2e1fd5 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+37>: 
mov%r13,%rsi
   0x5640cf2e1fd8 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+40>: 
mov%rax,%rdi
   0x5640cf2e1fdb <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+43>: 
mov%rax,%r12
   0x5640cf2e1fde <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+46>: 
call   0x5640cf2e1dd0 <(anonymous 
namespace)::aio_uring::aio_uring(tpool::thread_pool*, int)>
   0x5640cf2e1fe3 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+51>: 
add$0x8,%rsp
   0x5640cf2e1fe7 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+55>: 
mov%r12,%rax
   0x5640cf2e1fea <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+58>: 
pop%r12
   0x5640cf2e1fec <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+60>: 
pop%r13
   0x5640cf2e1fee <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+62>: 
pop%r14
   0x5640cf2e1ff0 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+64>: 
pop%rbp
   0x5640cf2e1ff1 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+65>: 
ret
   0x5640cf2e1ff2 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+66>: 
endbr64 
   0x5640cf2e1ff6 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+70>: 
mov%rax,%rdi
   0x5640cf2e1ff9 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+73>: 
mov%rdx,%rax
   0x5640cf2e1ffc <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+76>: 
jmp0x5640ceb23308 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi-8121512>
   0x5640cf2e2001 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+81>: 
endbr64 
   0x5640cf2e2005 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+85>: 
mov%rax,%r13
   0x5640cf2e2008 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+88>: 
mov%rdx,%r14
   0x5640cf2e200b <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+91>: 
jmp0x5640ceb232fa <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi.cold>
--Type  for more, q to quit, c to continue without paging--c
   0x5640cf2e2010 <_ZN5tpool19thread_pool_generic17create_native_aioEi+0>:  
endbr64 
   0x5640cf2e2014 <_ZN5tpool19thread_pool_generic17create_native_aioEi+4>:  
push   %rbp
   0x5640cf2e2015 <_ZN5tpool19thread_pool_generic17create_native_aioEi+5>:  
mov%rsp,%rbp
   0x5640cf2e2018 <_ZN5tpool19thread_pool_generic17create_native_aioEi+8>:  
push   %r14
   0x5640cf2e201a <_ZN5tpool19thread_pool_generic17create_native_aioEi+10>: 
mov%esi,%r14d
   0x5640cf2e201d <_ZN5tpool19thread_pool_generic17create_native_aioEi+13>: 
push   %r13
   0x5640cf2e201f <_ZN5tpool19thread_pool_generic17create_native_aioEi+15>: 
mov%rdi,%r13
   0x5640cf2e2022 <_ZN5tpool19thread_pool_generic17create_native_aioEi+18>: 
mov$0x158,%edi
   0x5640cf2e2027 <_ZN5tpool19thread_pool_generic17create_native_aioEi+23>: 
push   %r12
   0x5640cf2e2029 <_ZN5tpool19thread_pool_generic17create_native_aioEi+25>: 
sub$0x8,%rsp
   0x5640cf2e202d <_ZN5tpool19thread_pool_generic17create_native_aioEi+29>: 
call   0x5640ceacb570 <_Znwm@plt>
   0x5640cf2e2032 <_ZN5tpool19thread_pool_generic17create_native_aioEi+34>: 
mov%r14d,%edx
   0x5640cf2e2035 <_ZN5tpool19thread_pool_generic17create_native_aioEi+37>: 
mov%r13,%rsi
   0x5640cf2e2038 <_ZN5tpool19thread_pool_generic17create_native_aioEi+40>: 
mov%rax,%rdi
   0x5640cf2e203b <_ZN5tpool19thread_pool_generic17create_native_aioEi+43>: 
mov%rax,%r12
   0x5640cf2e203e 

[Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Note the runtime detection in innodb_use_native_aio_default affects the
default value only. Users can explicity set this and really on distros
to provide patched kernels.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970634

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Actually create_linux_aio (tpool/aio_liburing.cc:194) should already
catch this exception. So compiler error?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970634

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Assertion cause:

$  podman run --rm --cap-add=CAP_SYS_PTRACE -e MARIADB_ROOT_PASSWORD=bob -ti 
--user mysql  m106_jammy_debug  bash
mysql@0740c1895ab4:/$ gdb --args  mariadbd --bootstrap
GNU gdb (Ubuntu 12.0.90-0ubuntu1) 12.0.90
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from mariadbd...
Reading symbols from 
/usr/lib/debug/.build-id/44/991764aba74dce2376ff38060a66adb6cfe4c0.debug...
(gdb) r
Starting program: /usr/sbin/mariadbd --bootstrap
warning: Error disabling address space randomization: Function not implemented
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2022-04-28 22:59:13 0 [Note] /usr/sbin/mariadbd (server 
10.6.7-MariaDB-2ubuntu1) starting as process 14 ...
[New Thread 0x7f1b390b2640 (LWP 17)]
[New Thread 0x7f1b245c0640 (LWP 18)]
2022-04-28 22:59:13 0 [Note] InnoDB: The first data file './ibdata1' did not 
exist. A new tablespace will be created!
2022-04-28 22:59:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-04-28 22:59:13 0 [Note] InnoDB: Number of pools: 1
2022-04-28 22:59:13 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-04-28 22:59:13 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp 
(disabling future attempts)
2022-04-28 22:59:13 0 [Warning] mariadbd: io_uring_queue_init() failed with 
ENOSYS: try uprading the kernel

Thread 1 "mariadbd" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=139754903728000) at 
./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139754903728000) 
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=139754903728000) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=139754903728000, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
#3  0x7f1b38a42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#4  0x7f1b38a287f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x5640ceb351dc in _Unwind_SetGR.cold ()
#6  0x5640cf4218af in __gcc_personality_v0 ()
#7  0x7f1b39743c64 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#8  0x7f1b39744321 in _Unwind_RaiseException () from 
/lib/x86_64-linux-gnu/libgcc_s.so.1
#9  0x7f1b38eae54b in __cxa_throw () from 
/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x5640ceb232ed in (anonymous namespace)::aio_uring::aio_uring 
(this=, tpool=, max_aio=, 
this=, tpool=, 
max_aio=) at ../tpool/./tpool/aio_liburing.cc:63
#11 0x5640cf2e2043 in tpool::create_linux_aio (max_aio=2048, 
pool=0x5640d1625cf0) at ../tpool/./tpool/aio_liburing.cc:194
#12 tpool::thread_pool_generic::create_native_aio (this=0x5640d1625cf0, 
max_io=2048) at ../tpool/./tpool/tpool_generic.cc:285
#13 0x5640ceaea297 in tpool::thread_pool::configure_aio 
(this=0x5640d1625cf0, use_native_aio=, max_io=max_io@entry=2048) 
at ../storage/innobase/./tpool/tpool.h:215
#14 0x5640ceaf07d5 in os_aio_init () at 
../storage/innobase/./storage/innobase/os/os0file.cc:3759
#15 0x5640ceb037f8 in srv_start (create_new_db=) at 
../storage/innobase/./storage/innobase/srv/srv0start.cc:1180
#16 0x5640cf1815b9 in innodb_init (p=) at 
../storage/innobase/./storage/innobase/handler/ha_innodb.cc:4275
#17 0x5640ceef25f2 in ha_initialize_handlerton (plugin=0x5640d14d8b00) at 
./sql/handler.cc:659
#18 0x5640cecb5c7f in plugin_initialize (tmp_root=0x7ffdb8bea250, 
plugin=0x5640d14d8b00, argc=0x5640cfbe92e0 , 
argv=0x5640d14a1860, options_only=)
at ./sql/sql_plugin.cc:1463
#19 0x5640cecb9a84 in plugin_init (argc=, argv=, flags=1) at ./sql/sql_plugin.cc:1756
#20 0x5640ceb8cf5b in init_server_components () at ./sql/mysqld.cc:5046
#21 0x5640ceb921fa in mysqld_main (argc=, argv=) at ./sql/mysqld.cc:5661
#22 0x7f1b38a29d90 in __libc_start_call_main 
(main=main@entry=0x5640ceb35240 , argc=argc@entry=2, 
argv=argv@entry=0x7ffdb8becb68)
at ../sysdeps/nptl/libc_start_call_main.h:58
#23 0x7f1b38a29e40 in __libc_start_main_impl (main=0x5640ceb35240 
, argc=2, argv=0x7ffdb8becb68, init=, 
fini=, 
rtld_fini=, stack_end=0x7ffdb8becb58) at 
../csu/libc-start.c:392
#24 0x5640ceb7cbe5 in _start ()


So it looks like an uncaught exception.

Testing with:

diff --git 

[Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

From 5.12 kernel memory locked pages aren't needed -
https://github.com/axboe/liburing/issues/246#issuecomment-816965961.

In #1969160 I tested the upcoming 10.6 release (probably next week
sometime) for crashes in uring initialization failures and it didn't.
Apart from some error log differences from ENOMEM, ENOSYS etc are
handles the same way in the fallback.

I haven't quite concluded how the 10.6.7 release is crashing at the
moment.

With https://bugs.launchpad.net/ubuntu/+source/linux-
hwe-5.13/+bug/195 I assume the jammy kernel 5.15.0 has the right
patches to make 5.15.0 safe despite the MariaDB code not distinguishing
it as so (suggestions of improving kernel version detection welcome).

** Bug watch added: github.com/axboe/liburing/issues #246
   https://github.com/axboe/liburing/issues/246

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970634

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6

[Daniel Black]

Checked a rebased https://github.com/MariaDB/server/pull/2036
(openssl-3.0 backport on 10.6 latest from yesterday) in ubuntu-22.04
container and it doesn't assert. The ENOMEM error handling path is the
same as ENOSYS. I will get to the 'uprading' typo though probably not
before the next release sometime in the next week:

root@cd8baf7b8407:/source/builddir# sql/mariadbd --bootstrap --datadir=/tmp/
2022-04-26 22:15:13 0 [Note] sql/mariadbd (server 
10.6.8-MariaDB-1:10.6.8+maria~jammy) starting as process 9561 ...
2022-04-26 22:15:13 0 [Note] InnoDB: The first data file './ibdata1' did not 
exist. A new tablespace will be created!
2022-04-26 22:15:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-04-26 22:15:13 0 [Note] InnoDB: Number of pools: 1
2022-04-26 22:15:13 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-04-26 22:15:13 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp 
(disabling future attempts)
2022-04-26 22:15:13 0 [Warning] mariadbd: io_uring_queue_init() failed with 
ENOSYS: try uprading the kernel
2022-04-26 22:15:13 0 [Warning] InnoDB: liburing disabled: falling back to 
innodb_use_native_aio=OFF
2022-04-26 22:15:13 0 [Note] InnoDB: Initializing buffer pool, total size = 
134217728, chunk size = 134217728
2022-04-26 22:15:13 0 [Note] InnoDB: Completed initialization of buffer pool
2022-04-26 22:15:13 0 [Note] InnoDB: Setting file './ibdata1' size to 12 MB. 
Physically writing the file full; Please wait ...
2022-04-26 22:15:13 0 [Note] InnoDB: File './ibdata1' size is now 12 MB.
2022-04-26 22:15:13 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 
100663296 bytes
2022-04-26 22:15:13 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to 
./ib_logfile0
2022-04-26 22:15:13 0 [Note] InnoDB: New log file created, LSN=10329
2022-04-26 22:15:13 0 [Note] InnoDB: Doublewrite buffer not found: creating new
2022-04-26 22:15:13 0 [Note] InnoDB: Doublewrite buffer created
2022-04-26 22:15:13 0 [Note] InnoDB: 128 rollback segments are active.
2022-04-26 22:15:13 0 [Note] InnoDB: Creating shared tablespace for temporary 
tables
2022-04-26 22:15:13 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. 
Physically writing the file full; Please wait ...
2022-04-26 22:15:13 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-04-26 22:15:13 0 [Note] InnoDB: 10.6.8 started; log sequence number 0; 
transaction id 3
2022-04-26 22:15:13 0 [Note] Plugin 'FEEDBACK' is disabled.

And kernel version - 5.18.0-0.rc2.23.fc37.x86_64 (general insanity or
was testing kernel bugs, possibly both)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969160

Title:
  mariadb [ERROR] mysqld got signal 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

2.4.9 is present in Jellyfish, so things seem to be working fine now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

Ahhh, it was due to the Impish Debian freeze. Well, we'll know soon
enough!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

I have only verified proposed in hirsute.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

I can confirm the same with proposed.


On 9/7/21 3:40 PM, Will G wrote:
> For the avoidance of doubt I've just booted up `5.11.0-35-generic` from
> -proposed (after previously running Hui's build) and audio is working
> fine on my 9710.
>
> ** Tags removed: hirsute verification-needed-hirsute
> ** Tags added: verification-done-hirsute
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Hui
Was the 5.11.0-34-generic release suppose to have the patch in it?
Thanks
Michael

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

hrmmm, new versions don't seem to be entering Impish. is that due to
something changing since the release of Debian Bullseye, or is notcurses
misbehaving on Ubuntu CI?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Wang
Just tried the kernel you posted and it is working.

Thanks
Michael

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

Alright, the impish release still has 2.3.13+dfsg.1-1, but as soon as
2.3.13+dfsg.1-2, we'll know whether this is still a problem. All
autopkgtests have succeeded within the Debian build infrastructure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Thanks


On 8/16/21 8:18 PM, Hui Wang wrote:
> @Michael,
>
> The patch for 5.11.0-31-generic was rejected because it introduced a
> build failure (https://lists.ubuntu.com/archives/kernel-
> team/2021-August/123162.html), the fix patch will be in the -32 kernel,
> and once the -32 kernel merges this patch and is ready to test, the
> status will be changed to fix_committed, then you could test -32 kernel.
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Just updated Linux xps17 5.11.0-31-generic #33
System is still showing Dummy Output for sound.  

But, there are no errors in dmesg now.

[2.787880] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[2.787895] snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[3.071849] snd_hda_intel :01:00.1: enabling device ( -> 0002)
[3.071922] snd_hda_intel :01:00.1: Disabling MSI
[3.071931] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

fwiw, i can no longer reproduce this locally, though i also can't point
at any particular commit that ought have fixed it =/.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

with the Debian freeze ending, i've reenabled this autopkgtest and am
putting up a candidate package now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Thanks

> On Aug 9, 2021, at 21:45, Hui Wang <1935...@bugs.launchpad.net> wrote:
> 
> @Michael,
> 
> the patch will be in the 5.11.0-27-generic and later versions.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1935850
> 
> Title:
>  Dell XPS 17 (9710) PCI/internal sound card not detected
> 
> Status in linux package in Ubuntu:
>  In Progress
> Status in linux source package in Hirsute:
>  In Progress
> Status in linux source package in Impish:
>  In Progress
> 
> Bug description:
>  This patch is for soundwire audio, and only ubuntu 5.11-generic
>  and later kernels support soundwire audio driver, so this patch is not
>  sent to groovy and focal kernels.
> 
>  For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM
>  project, it is not urgent to merge this patch to OEM kenrels, after
>  the patch is in the hirsute and impish kernels, the oem kernels will
>  have this patch when syncing with generic kernels.
> 
>  [Impact]
>  On the Dell XPS 17 (9710) machine, the audio card is not detected when
>  booting hirsute or impish kernels. So the audio doesn't work on this
>  machine with ubuntu linux 21.04 or 21.10.
> 
>  [Fix]
>  Backport a upstream patch, this will set the correct codec config
>  for this machine: rt711 for headset, dual rt1308 for spks and rt715
>  for internal mic.
> 
>  [Test]
>  Booting up with the patched kernel, the audio card is detected, test
>  internal speaker and internal mic, all work well, plug a headset,
>  the headphone and external mic work well too.
> 
> 
>  [Where problems could occur]
>  This change only applis to the Dell machines with the 
>  DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the
>  regression, it will make the audio (speaker, internal mic and headset)
>  can't work anymore on the Dell machine with that PRODUCT_SKU, but this
>  possibility is very low, and we tested the patch on the machine, so
>  far no regression is found.
> 
> 
>  No audio/mic from internal speakers/build in microphone running Ubuntu 
> 20.04, 20.10 or 21.04  .  Can connect via USB headset and audio will work.   
> Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes 
> do not work. Currently running 21.04 with proposed.
> 
>  Have tried hirsute-proposed (5.11.0-24-generic) with no luck.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 21.04
>  Package: alsa-base 1.0.25+dfsg-0ubuntu7
>  ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
>  Uname: Linux 5.11.0-24-generic x86_64
>  NonfreeKernelModules: nvidia_modeset nvidia
>  ApportVersion: 2.20.11-0ubuntu65.1
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  mblack 1698 F pulseaudio
>  CasperMD5CheckResult: pass
>  CurrentDesktop: ubuntu:GNOME
>  Date: Mon Jul 12 11:21:27 2021
>  InstallationDate: Installed on 2021-07-07 (4 days ago)
>  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
>  PackageArchitecture: all
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: alsa-driver
>  Symptom: audio
>  Title: PCI/internal sound card not detected
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 06/15/2021
>  dmi.bios.release: 1.2
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: 1.2.0
>  dmi.board.name: 012MMP
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: A00
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Dell Inc.
>  dmi.modalias: 
> dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr:
>  dmi.product.family: XPS
>  dmi.product.name: XPS 17 9710
>  dmi.product.sku: 0A5D
>  dmi.sys.vendor: Dell Inc.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Did you clone the src files from here?

https://github.com/thesofproject/linux.git


On 7/30/21 1:34 PM, Raish khaitu wrote:
> I am getting this error @mblack154:
>
> BTF: .tmp_vmlinux.btf: pahole (pahole) is not available
> Failed to generate BTF for vmlinux
> Try to disable CONFIG_DEBUG_INFO_BTF
> make[3]: *** [Makefile:1177: vmlinux] Error 1
> make[2]: *** [debian/rules:7: build-arch] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 2
> make: *** [Makefile:1560: deb-pkg] Error 2
>
>
> Any advise would be helpful. should i just try and disable BTF?
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Had to compile with:

copied over current cofig
Removed --> #CONFIG_SYSTEM_TRUSTED_KEYS
sudo make menuconfig
sudo make clean
sudo make deb-pkg LOCALVERSION=-custom KDEB_PKGVERSION=$(make 
kernelversion)-1

Then installed the deb files.

Let me know if this works.

Michael



On 7/30/21 10:17 AM, Raish khaitu wrote:
> @mblack154  How did you resolve this issue:
> arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support
> sed: can't read modules.order: No such file or directory
> make: *** [Makefile:1485: __modinst_pre] Error 2
>
> i am still stuck here even after running these:
> sudo apt install build-essential
> sudo apt-get build-dep linux-image- (the running kernel)
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Yes


On 7/26/21 2:05 PM, Perry Steger wrote:
> Excellent, Michael! Sound in and out?
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Got the kernel compiled this morning with the patch and I have sound.
(5.14-rc2)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

thanks @mblack154 can you try the patch in a312717

https://github.com/thesofproject/linux/commit/a312717b3d2a911a103e09dd313e533bb58d0dd0


You may need to rename the RT711_JD2 as SOF_RT711_JD_SRC_JD2 since a recent 
commit changed the JD definition.
https://lore.kernel.org/alsa-devel/20210712203240.46960-7-pierre-louis.boss...@linux.intel.com/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937931] [NEW] Amd gpu freezes / crashes on load

[black]

Public bug reported:

I have had several lockups of the amd gpu. The full screen freezes and
my pointer is mostly still able to move. But no refreshing of the rest
of the UI. So my system-monitor graphs on the top are stuck. Mostly I'm
able to switch to terminal (ctrl-alt-f6) and also going to login window
(ctrl-alt-f1) is possible. But login in or trying to restart gnome is
not possible. Full restart is needed.

In this instance itself it manifested a little bit different. The lockup
happened, but it tried to recover itself by killing the full session and
going back to the login screen.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-generic 5.11.0.25.27
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nikos 4175235 F pulseaudio
 /dev/snd/controlC0:  nikos 4175235 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 25 10:27:20 2021
InstallationDate: Installed on 2020-01-06 (565 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 04f2:b67f Chicony Electronics Co., Ltd HP TrueVision HD 
Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Laptop 14-dk0xxx
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7qfu65@/vmlinuz-5.11.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu_7qfu65 ro quiet splash iommu=pt vt.handoff=1
RebootRequiredPkgs:
 linux-image-5.11.0-25-generic
 linux-base
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-22-generic N/A
 linux-backports-modules-5.11.0-22-generic  N/A
 linux-firmware 1.197.2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-06-10 (44 days ago)
dmi.bios.date: 07/03/2019
dmi.bios.release: 15.42
dmi.bios.vendor: AMI
dmi.bios.version: F.42
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 85E0
dmi.board.vendor: HP
dmi.board.version: 84.42
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 84.42
dmi.modalias: 
dmi:bvnAMI:bvrF.42:bd07/03/2019:br15.42:efr84.42:svnHP:pnHPLaptop14-dk0xxx:pvr:rvnHP:rn85E0:rvr84.42:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-dk0xxx
dmi.product.sku: 6BG79EA#UUG
dmi.sys.vendor: HP

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937931

Title:
  Amd gpu freezes / crashes on load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1937931/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937931] Re: Amd gpu freezes / crashes on load

[black]

Error happened around 322667.259228

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937931

Title:
  Amd gpu freezes / crashes on load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1937931/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937931] Re: Amd gpu freezes / crashes on load

[black]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+bug/1937931/+attachment/5513479/+files/dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937931

Title:
  Amd gpu freezes / crashes on load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1937931/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Wang 
Have a patch to test from intel.   Attempting to compile doing the following:

1) Copy old config over to source
2) make oldconfig (Accept default changes)
3) make -j8
4) sudo make modules_install 

At this point I get this error:

arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support
sed: can't read modules.order: No such file or directory
make: *** [Makefile:1485: __modinst_pre] Error 2

I have made sure that binutils are install.   Any input would be
appropriated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Tried versions 1.6, 1.7 and 1.8.   Results from dmesg for each are
below.

1.6
-
[2.813265] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[2.814293] snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[3.043586] snd_hda_intel :01:00.1: enabling device ( -> 0002)
[3.043747] snd_hda_intel :01:00.1: Disabling MSI
[3.043758] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.085850] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[3.086244] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[3.086263] sof-audio-pci :00:1f.3: enabling device ( -> 0002)
[3.086518] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[4.419572] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.506416] sof-audio-pci :00:1f.3: use msi interrupt mode
[4.526665] sof-audio-pci :00:1f.3: hda codecs found, mask 4
[4.623692] sof-audio-pci :00:1f.3: Firmware info: version 1:6:1-53680
[4.623701] sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 
3:18:0
[4.635902] sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 
3:18:0
[4.655486] sof-audio-pci :00:1f.3: ASoC: physical link SDW3-Capture (id 
4) not exist
[4.655496] sof-audio-pci :00:1f.3: ASoC: topology: could not load 
header: -22
[4.655760] sof-audio-pci :00:1f.3: error: tplg component load failed -22
[4.655767] sof-audio-pci :00:1f.3: error: failed to load DSP topology 
-22
[4.655770] sof-audio-pci :00:1f.3: ASoC: error at 
snd_soc_component_probe on :00:1f.3: -22
[4.655773] sof-audio-pci :00:1f.3: ASoC: failed to probe component -22
[4.655815] sof_sdw sof_sdw: ASoC: failed to instantiate card -22
[8.695612] sof_sdw sof_sdw: snd_soc_register_card failed -22
[8.695632] sof_sdw: probe of sof_sdw failed with error -22


1.7
-
[3.062326] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[3.062905] sof-audio-pci :00:1f.3: enabling device ( -> 0002)
[3.064154] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[4.236932] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.460375] sof-audio-pci :00:1f.3: use msi interrupt mode
[4.486526] sof-audio-pci :00:1f.3: hda codecs found, mask 4
[4.487058] sof-audio-pci :00:1f.3: Firmware info: version 1:7:0-47d07
[4.487062] sof-audio-pci :00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 
3:18:0
[4.487065] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than 
kernel
[4.487070] sof-audio-pci :00:1f.3: unknown sof_ext_man header type 3 
size 0x30
[4.595907] sof-audio-pci :00:1f.3: Firmware info: version 1:7:0-47d07
[4.595914] sof-audio-pci :00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 
3:18:0
[4.595918] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than 
kernel
[4.610245] sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 
3:18:0
[4.629440] sof-audio-pci :00:1f.3: ASoC: physical link SDW3-Capture (id 
4) not exist
[4.629448] sof-audio-pci :00:1f.3: ASoC: topology: could not load 
header: -22
[4.629706] sof-audio-pci :00:1f.3: error: tplg component load failed -22
[4.629712] sof-audio-pci :00:1f.3: error: failed to load DSP topology 
-22
[4.629713] sof-audio-pci :00:1f.3: ASoC: error at 
snd_soc_component_probe on :00:1f.3: -22
[4.629715] sof-audio-pci :00:1f.3: ASoC: failed to probe component -22
[4.629745] sof_sdw sof_sdw: ASoC: failed to instantiate card -22
[4.634785] sof_sdw sof_sdw: snd_soc_register_card failed -2



1.8
-
[2.791146] snd_hda_intel :01:00.1: enabling device ( -> 0002)
[2.792978] snd_hda_intel :01:00.1: Disabling MSI
[2.792997] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.039625] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[3.040157] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[3.040172] sof-audio-pci :00:1f.3: enabling device ( -> 0002)
[3.040381] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[4.130786] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.390775] sof-audio-pci :00:1f.3: use msi interrupt mode
[4.432864] sof-audio-pci :00:1f.3: hda codecs found, mask 4
[4.433568] 

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Looks like same error with 1.7.x and 1.8.x using sof-tgl.ri

[2.993700] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[2.993714] sof-audio-pci :00:1f.3: enabling device ( -> 0002)
[2.993959] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[4.251402] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.387760] sof-audio-pci :00:1f.3: use msi interrupt mode
[4.402321] sof-audio-pci :00:1f.3: hda codecs found, mask 4
[4.402952] sof-audio-pci :00:1f.3: Firmware info: version 1:8:0-9e7a8
[4.402954] sof-audio-pci :00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 
3:18:0
[4.402956] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than 
kernel
[4.402963] sof-audio-pci :00:1f.3: unknown sof_ext_man header type 3 
size 0x30
[6.520768] sof-audio-pci :00:1f.3: error: firmware boot failure
[6.520777] sof-audio-pci :00:1f.3: status: fw entered - code 0005
[6.520783] sof-audio-pci :00:1f.3: error: status = 0x panic = 
0x0211
[6.520805] sof-audio-pci :00:1f.3: error: extended rom status:  0x5 0x0 
0x211 0x0 0x0 0x0 0x2530509 0x0
[6.520812] sof-audio-pci :00:1f.3: status: fw entered - code 0005
[6.520814] sof-audio-pci :00:1f.3: error: failed to boot DSP firmware -5
[6.522883] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Missing file now.   (sof-tgl.ri)

[2.977845] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[2.978089] snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[2.978153] snd_hda_intel :01:00.1: enabling device ( -> 0002)
[2.978583] snd_hda_intel :01:00.1: Disabling MSI
[2.978600] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.018686] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[3.019131] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
[3.019169] sof-audio-pci :00:1f.3: enabling device ( -> 0002)
[3.019977] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[4.278689] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.400440] sof-audio-pci :00:1f.3: use msi interrupt mode
[4.413812] sof-audio-pci :00:1f.3: hda codecs found, mask 4
[4.413921] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-tgl.ri failed with error -2
[4.413926] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-tgl.ri failed err: -2
[4.413931] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2
[4.414536] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Removed the link for sof-tgl-h.ri in /lib/firmware/intel/sof/.  No
errors about file not found.  Same error as above.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Tried sof-tgl-h.ri 1.7 and 1.8 signed and RC2 of both.  Speakers are
still showing dummy output.  Still getting:

[5.999872] sof-audio-pci :00:1f.3: error: firmware boot failure
[5.999879] sof-audio-pci :00:1f.3: status: fw entered - code 0005
[5.999885] sof-audio-pci :00:1f.3: error: status = 0x panic = 
0x0211
[5.06] sof-audio-pci :00:1f.3: error: extended rom status:  0x5 0x0 
0x211 0x0 0x0 0x0 0x2530509 0x0
[5.10] sof-audio-pci :00:1f.3: status: fw entered - code 0005
[5.11] sof-audio-pci :00:1f.3: error: failed to boot DSP firmware -5
[6.001309] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1935850] [NEW] Dell XPS 17 (9710) PCI/internal sound card not detected

[Michael Black]

Public bug reported:

No audio/mic from internal speakers/build in microphone running Ubuntu
20.04, 20.10 or 21.04  .  Can connect via USB headset and audio will
work.   Tried suggestions from Dell XPS 17 (9700) but this is the new
model and fixes do not work. Currently running 21.04 with proposed.

Have tried hirsute-proposed (5.11.0-24-generic) with no luck.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
Uname: Linux 5.11.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mblack 1698 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 12 11:21:27 2021
InstallationDate: Installed on 2021-07-07 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2021
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.0
dmi.board.name: 012MMP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9710
dmi.product.sku: 0A5D
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

** Description changed:

- No audio/mic from internal speakers/build in microphone.  Can connect
- via USB headset and audio will work.   Tried suggestions from Dell XPS
- 17 (9700) but this is the new model and fixes do not work.
+ No audio/mic from internal speakers/build in microphone running Ubuntu
+ 20.04, 20.10 or 21.04  .  Can connect via USB headset and audio will
+ work.   Tried suggestions from Dell XPS 17 (9700) but this is the new
+ model and fixes do not work. Currently running 21.04 with proposed.
  
  Have tried hirsute-proposed (5.11.0-24-generic) with no luck.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
  Uname: Linux 5.11.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  mblack 1698 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  mblack 1698 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 12 11:21:27 2021
  InstallationDate: Installed on 2021-07-07 (4 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 012MMP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9710
  dmi.product.sku: 0A5D
  dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913676] Re: libmariadb3 fails to include caching_sha2_password.so

[Daniel Black]

This is a critical bug. More so on Ubuntu because of it installing MySQL
by default. It affects all default connections to the MySQL with MariaDB
connector/C and its dependent library, and every application that
depends on this libmariadb3.

I thought the merge 5 months ago into buster would of made it to the 2
months ago 10.2.29 release.  Odd, but so was the 10.5 only #962597 fix.

If you don't want to package 10.3.30 because it only includes bug fixes
and not security fixes, ok, but package increment on
libmariadb3-1:10.3.29 to resolve this please.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913676

Title:
  libmariadb3 fails to include caching_sha2_password.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1913676/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

Agreed, and I can now reproduce this failure locally. Tracking in
https://github.com/dankamongmen/notcurses/issues/1784. Thanks!

** Bug watch added: github.com/dankamongmen/notcurses/issues #1784
   https://github.com/dankamongmen/notcurses/issues/1784

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

[schwarzgerat](0) $ apt-show-versions notcurses-bin
notcurses-bin:amd64/unstable 2.3.4+dfsg.1-3 uptodate
[schwarzgerat](0) $

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

Present in Debian Unstable.

** Changed in: notcurses (Debian)
   Status: New => Fix Released

** Changed in: notcurses (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

All built, uploaded to the archive. This ought flow to Ubuntu soon
enough. Thanks again!

** Changed in: notcurses (Debian)
 Assignee: (unassigned) => nick black (dankamongmen)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

https://buildd.debian.org/status/package.php?p=notcurses=sid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

by the way @robert-ancell, i notice that you have ",flaky" in there.
this isn't present in the Debian package. has it been added in Ubuntu?

** Changed in: notcurses (Ubuntu)
 Assignee: (unassigned) => nick black (dankamongmen)

** Also affects: notcurses (Debian)
   Importance: Undecided
   Status: New

** Changed in: notcurses (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

[schwarzgerat](0) $ dput *.changes
Trying to upload package to ftp-master (ftp.upload.debian.org)
Checking signature on .changes
gpg: /home/dank/src/dsscaw/notcurses_2.3.4+dfsg.1-3_source.changes: Valid 
signature from 5F43400C21CBFACC
Checking signature on .dsc
gpg: /home/dank/src/dsscaw/notcurses_2.3.4+dfsg.1-3.dsc: Valid signature from 
5F43400C21CBFACC
Uploading to ftp-master (via ftp to ftp.upload.debian.org):
  Uploading notcurses_2.3.4+dfsg.1-3.dsc: done.
  Uploading notcurses_2.3.4+dfsg.1.orig.tar.xz: done.
  Uploading notcurses_2.3.4+dfsg.1-3.debian.tar.xz: done.
  Uploading notcurses_2.3.4+dfsg.1-3_source.buildinfo: done.
  Uploading notcurses_2.3.4+dfsg.1-3_source.changes: done.
Successfully uploaded packages.
[schwarzgerat](0) $

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

https://salsa.debian.org/debian/notcurses/-/commit/d73556faadfd08013b03ccedbd7348edbddab53e

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

https://salsa.debian.org/debian/notcurses/-/commit/30a0e9d39eb45acca5292c85ee2cd154f275e1f9

building new package now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

h my patch dropped the -m2 entirely, but i like your -m0,2,0,2
solution, nice. i'll use that instead!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

I of course mean 2.3.4+dfsg.1-3.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932103] Re: 2.3.4+dfsg.1-2 is FTBFS

[nick black]

How embarrassing -- thanks a lot for the heads-up! I think the best way
to fix this will be to do so in the Debian package in Unstable, which I
assume is how this is reaching Ubuntu. Sound good? This would target
2.3.4+dfsg-3, and I can have it uploaded to Debian Unstable within the
hour.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932103

Title:
  2.3.4+dfsg.1-2 is FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1932103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913676] [NEW] libmariadb3 fails to include caching_sha2_password.so

[Daniel Black]

Public bug reported:

The lack of this shared library means MySQL/MariaDB client connectors
connecting to a MySQL-8.0 server (which defaults to
caching_sha2_password being the default authentication for users, will
get a connection rejected message.

This leads to extremely popular work around answers like
https://stackoverflow.com/questions/54099722/how-to-connect-r-to-mysql-
failed-to-connect-to-database-error-plugin-caching/54101124#54101124
which is very good for popularity scores, but not users.

It was reported in Debian https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=962597 ( for perl connectors) but wasn't fixed for
buster.

As Ubuntu is also linking against gnutls the sha256_password.so probably
isn't possible. Something to do with missing OEPC(?) missing from
gnutls. This has limited use so its a significant problem if this can't
be added.

MariaDB is fixing this in their upstream packages
(https://jira.mariadb.org/browse/MDEV-24728) from 10.2+ on all debian
and ubuntu versions
https://github.com/MariaDB/server/commit/57531b32774ffafcd2b8da763c4da859380e3f7d
).

This applies to focal only. As this is the distribution that includes
MySQL-8.0 this is important for local database connections.

groovy includes caching_sha2_password but not sha256_password
https://packages.ubuntu.com/groovy/amd64/libmariadb3/filelist

bionic is based on connector/c version is 3.0.3 however it wasn't added
upstream until 3.0.8 (https://jira.mariadb.org/browse/CONC-312).


fix: add to debian/libmariadb3.install

/usr/lib/*/mariadb19/plugin/caching_sha2_password.so

** Affects: mariadb-10.3 (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/1913676

Title:
  libmariadb3 fails to include caching_sha2_password.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1913676/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904306] Re: bcm2835-v4l2 does not detect/expose the second camera on RPi Compute Module 3+ in Ubuntu Server 20.04.1

[Adam Black]

Gah, I've found the issue.

Based on the investigation in this thread
https://www.raspberrypi.org/forums/viewtopic.php?f=98=174347=25#p1120478
I narrowed it down to dtparam=i2c_arm=on preventing the secondary camera
from being detected.

After commenting out dtparam=i2c_arm=on from /boot/firmware/syscfg.txt I
now have /dev/video0 and /dev/video1 for each of the supported cameras
on CM3+ in Ubuntu 20

[   14.133985] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 
1280x720
[   14.139034] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.
[   14.151264] bcm2835-v4l2: V4L2 device registered as video1 - stills mode > 
1280x720
[   14.156258] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.

Is it expected that this, remotely related, setting affects
functionality in bcm2835-camera.c? That's pretty brittle.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904306

Title:
  bcm2835-v4l2 does not detect/expose the second camera on RPi Compute
  Module 3+ in Ubuntu Server 20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/1904306/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904306] Re: bcm2835-v4l2 does not detect/expose the second camera on RPi Compute Module 3+ in Ubuntu Server 20.04.1

[Adam Black]

On the Raspberry Pi OS side:

$ vcgencmd version
Aug 19 2020 17:41:31 
Copyright (c) 2012 Broadcom
version e90cba19a98a0d1f2ef086b9cafcbca00778f094 (clean) (release) (start_x)

$ uname -a
Linux raspberrypi 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l 
GNU/Linux

$ vcgencmd get_camera
supported=2 detected=2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904306

Title:
  bcm2835-v4l2 does not detect/expose the second camera on RPi Compute
  Module 3+ in Ubuntu Server 20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/1904306/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904306] Re: bcm2835-v4l2 does not detect/expose the second camera on RPi Compute Module 3+ in Ubuntu Server 20.04.1

[Adam Black]

Vincent, could you pls help triage and remedy this?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904306

Title:
  bcm2835-v4l2 does not detect/expose the second camera on RPi Compute
  Module 3+ in Ubuntu Server 20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/1904306/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904306] [NEW] bcm2835-v4l2 does not detect/expose the second camera on RPi Compute Module 3+ in Ubuntu Server 20.04.1

[Adam Black]

Public bug reported:

This is for video4linux, libv4l or related.

There appears to be an issue in or around bcm2835-v4l2 not
detecting/configuring/exposing the second camera in Ubuntu Server
20.04.1 on the Raspberry Pi Compute Module 3+ hardware.

Followed the official instructions at
https://www.raspberrypi.org/documentation/hardware/computemodule/cmio-
camera.md and used the .dts file they supplied
(https://www.raspberrypi.org/documentation/hardware/computemodule/dt-
blob-dualcam.dts)

First, I confirmed that compiling the dt-blob.bin file and dropping it
to /boot/dt-blob.bin made it work in Raspberry Pi OS: I could capture
images from either of the cameras. (Expected behavior)

However, after switching to Ubuntu Server 20.04.1 (from
https://ubuntu.com/download/raspberry-pi) and compiling the same
suggested dual .dts and dropping it to /boot/firmware/dt-blob.bin the
system only provides /dev/video0. In both cases ‘start_x=1’ is present
in config.txt

It appears that the loop in
drivers/staging/vc04_services/bcm2835-camera/bcm2835-camera.c is not
executed for each camera present and configured in RPi CM3+, resulting
in only one camera exposed to the end user. The value of
MAX_BCM2835_CAMERAS of 2 should be respected; something in the
code/default configuration/environment is affecting this functionality.

Here’s what I see in dmsg:

Raspberry Pi OS:

[7.674728] videodev: Linux video capture interface: v2.00
[7.740370] bcm2835-isp bcm2835-isp: Device node output[0] registered as 
/dev/video13
[7.740908] bcm2835-isp bcm2835-isp: Device node capture[0] registered as 
/dev/video14
[7.741486] bcm2835-isp bcm2835-isp: Device node capture[1] registered as 
/dev/video15
[7.742841] bcm2835-isp bcm2835-isp: Device node stats[2] registered as 
/dev/video16
[9.004310] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[9.013003] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[9.022054] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[9.025325] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 
1280x720
[9.033622] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.
[9.062931] bcm2835-v4l2: V4L2 device registered as video1 - stills mode > 
1280x720
[9.068984] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.

$ v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
/dev/video10
/dev/video11
/dev/video12

bcm2835-isp (platform:bcm2835-isp):
/dev/video13
/dev/video14
/dev/video15
/dev/video16

mmal service 16.1 (platform:bcm2835-v4l2):
/dev/video0
/dev/video1

Ubuntu 20.04.1:

[   12.700652] videodev: Linux video capture interface: v2.00
[   12.995520] bcm2835-isp bcm2835-isp: Device node output[0] registered as 
/dev/video13
[   12.995871] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[   12.995953] bcm2835-isp bcm2835-isp: Device node capture[0] registered as 
/dev/video14
[   12.997342] bcm2835-isp bcm2835-isp: Device node capture[1] registered as 
/dev/video15
[   12.997740] bcm2835-isp bcm2835-isp: Device node stats[2] registered as 
/dev/video16
[   13.003552] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[   13.011487] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[   14.258871] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 
1280x720
[   14.264316] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.

$ v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
/dev/video10
/dev/video11
/dev/video12

bcm2835-isp (platform:bcm2835-isp):
/dev/video13
/dev/video14
/dev/video15
/dev/video16

mmal service 16.1 (platform:bcm2835-v4l2):
/dev/video0

Note the log line ‘V4L2 device registered as video1’ is not reported in
Ubuntu.

In terms of hardware the cameras are configured properly and detectable;
the hardware is exactly the same, the only difference is the OS which is
swapped by means of swapping microSD cards containing Raspberry Pi OS
and Ubuntu 20 respectively.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename:   focal

** Affects: libv4l (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/1904306

Title:
  bcm2835-v4l2 does not detect/expose the second camera on RPi Compute
  Module 3+ in Ubuntu Server 20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/1904306/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

[Black Mage Zeraf]

Tried Installing using UNetBootin on my secondary hard drive and got
this error

** Changed in: glibc (Ubuntu)
 Assignee: (unassigned) => Black Mage Zeraf (blackmagezeraf)

** Changed in: glibc (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871268

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896717] Re: [FFE] notcurses 1.7.4 for ubuntu 20.10

[nick black]

Wonderful, thanks so much Łukasz!

Yes, a sync from Debian Unstable (or Debian Testing sometime today, when
it passes the testing threshold) seems the easiest way to do things,
given that I lack Ubuntu upload privileges.

Yes, I was able to perform a successful build (using both dpkg-
buildpackage and later pbuilder) on an up-to-date 20.10 Groovy Gorilla
machine this evening. The results are here:

https://www.dsscaw.com/repos/apt/ubuntu/pool/main/n/notcurses/

Probably best to sync from Debian using the standard Ubuntu method, as
these packages contain "unstable" rather than "groovy" in the
`debian/changelog`. Let me know if you need me to build anything afresh.

I'm probably going to apply for PerPackageUploader rights, but that'll
take place in another bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896717

Title:
  [FFE] notcurses 1.7.4 for ubuntu 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notcurses/+bug/1896717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896717] [NEW] [FFE] notcurses 1.7.4 for ubuntu 20.10

[nick black]

Public bug reported:

Hello. I'd like to request a Feature Freeze Exception for 20.10 per the
instructions at
https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_for_new_upstream_versions.

Ubuntu 20.10 currently has notcurses 1.7.0, imported directly from
Debian (where I'm the maintainer, as well as the upstream author). This
is a kinda unfortunate pick; it has two annoying (though not
grave/serious) bugs, but more importantly lacks the recent 1.7.x API
changes, pursuant to 2.0 (to be released next month).

All year, I've claimed that Notcurses would commit to backwards
compatibility and API stability starting with the 2.0 release, and
retained free right to mutate the API until then. 1.7.4 (currently
available in Debian/Fedora/Arch) is the last expected release prior to
2.0. Its API is thus expected to be equal to the final, stable 2.0 API.
By importing 1.7.4 to 20.10, 20.10 will ship with the same API other
distros (and newer versions of Ubuntu) will be implementing. Given that
20.10 is the first Ubuntu to contain Notcurses, this means a sweetly
unified surface across all distros.

I have prepared a 1.7.4 for Ubuntu 20.10, and can upload it under the
Sponsorship Process. The 1.7.4 packages are available via
https://www.dsscaw.com/repos/apt/ubuntu/.

Testing: install the notcurses-bin package and run `notcurses-demo`. It
works fine. There's also an `autopkgtest` file in the `debian/` folder.
I'll attach the pbuilder output shortly.

Diff of upstream NEWS.md:

* 1.7.4 (2020-09-20)
  * All `_rgb_clipped()` functions have been renamed `_rgb8_clipped()`, to
match the changes made in 1.7.2. Sorry, I ought have done this before.
  * `ncplane_create()` has been introduced, taking a `struct ncplane_options`
parameter. This replaces `ncplane_aligned()`, and will replace
`ncplane_new()`. The latter ought be considered deprecated, and will be
removed in the future. To align a place as previously done with
`ncplane_aligned()`, use the `NCPLANE_OPTION_HORALIGNED` flag.
  * The `ncplane_options` struct includes a function pointer member,
`resizecb`. If not `NULL`, this function will be called after the parent
plane is resized. See `notcurses_plane.3` for more information.
  * `ncplane_resize_realign()` has been added, suitable for use as a
`resizecb`. It realigns the plane against its parent.
  * `NCCHANNEL_ALPHA_MASK` has been renamed `CHANNEL_ALPHA_MASK`, to match
the other declarations.

* 1.7.3 (2020-09-19)
  * API changes pursuant to 2.0 API finalization:
  * `mbswidth()` has been renamed `ncstrwidth()`.
  * The long-promised/dreaded Great Widget Review, normalizing behavior across
all widgets, has been effected. Sorry, there was no getting around this
one. Pretty much all widgets have slightly changed, because pretty much all
widgets previously behaved slightly differently:
 * `ncselector_create()` and `ncmultiselector_create()` now take ownership
   of the provided `ncplane`. On an error in these functions, the `ncplane`
   will be destroyed. Otherwise, the `ncplane` is destroyed by
   `ncselector_destroy()` or `ncmultiselector_destroy()`.
 * `ncselector_create()`, `ncmultiselector_create()`, and
   `ncreader_create()` no longer accept `int y, int x` placement
   parameters. Just place the `ncplane`.
 * `ncselector_options`, `ncmultiselector_options`, and `ncreel_options`
   have lost their `bgchannels` members. Just set the base character for
   the `ncplane`.
 * `ncreader_options` has lost its `echannels`, `eattrword`, `egc`,
   `physrows`, and `physcols` fields. Just set the base character and size
   for the `ncplane`.
  * Functions which set a 24-bit RGB value have had the suffix `g` replaced
with `g_rgb`. Functions which set three 8-bit RGB components have had the
suffix `rgb` replaced with `rgb8`. This was done because e.g.
`channels_set_fg()` and `channels_set_fchannel()` were indistinguishable on
sight. Failure to make the necessary conversions will result in compiler
errors. See https://github.com/dankamongmen/notcurses/issues/985.
  * Functions ending in `_stainable()` now end in `_stained()`.
  * `ncplane_putwc_stained()` and `ncplane_putwstr_stained()` have been
added in the interest of orthogonality.
  * `ncplane_new_named()` has been eliminated. `ncplane_new()` now takes a
`const char* name` argument. `ncplane_bound()` and `ncplane_bound_named()`
have both been eliminated. `ncplane_new()` now accepts an `ncplane*`
   instead of a `notcurses*`. All functionality exposed by the removed
functions is thus now present in `ncplane_new()`.
  * `ncplane_aligned_named()` has been removed. `ncplane_aligned()` now accepts
a `const char* name` argument.

* 1.7.2 (2020-09-09)
  * Exported `ncvisual_default_blitter()`, so that the effective value of
`NCBLIT_DEFAULT` can be determined.
  * Added `NCREADER_OPTION_CURSOR`, instructing the `ncreader` to make the
 

[Bug 1873696] Re: [needs-packaging] notcurses

[nick black]

It appears that notcurses has automatically been imported into Groovy:

https://packages.ubuntu.com/source/groovy/notcurses

so we can close this as resolved!

** Changed in: ubuntu
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873696

Title:
  [needs-packaging] notcurses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1873696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873696] Re: [needs-packaging] notcurses

[nick black]

If it is useful, I have Ubuntu packages available here:

https://www.dsscaw.com/repos/apt/ubuntu/ (PPA material)

https://www.dsscaw.com/repos/apt/ubuntu/pool/main/n/notcurses/ (direct
link)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873696

Title:
  [needs-packaging] notcurses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1873696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873696] [NEW] [needs-packaging] notcurses

[nick black]

Public bug reported:

I am the author of notcurses, a character graphics/TUI library with deep
Unicode support, 24-bit TrueColor, and multithreading safety. I recently
packaged it for Debian, and it was accepted into Debian Unstable
yesterday evening. The Debian ITP bug is here:

 https://bugs.debian.org/950492

License: Apache 2.0
Description: Character graphics and TUI library
 notcurses facilitates the creation of modern TUI programs, making full use of
 Unicode and 24-bit TrueColor. Its API is similar to that of NCURSES, but
 extends that with z-buffering, rendering of images and video using ffmpeg,
 alpha blending, widgets, palette fades, resize awareness, and multithreading
 support.
Homepage: https://nick-black.com/dankwiki/index.php/notcurses
Notes: I know I missed the Focal DIF by months, and the UI freeze by weeks. I 
have no expectations that this will get into Focal, but that would certainly be 
nice. If not, it goes into the next one, no problem.

I am happy to provide assistance directly to Ubuntu in any capacity it
might be needed, and intend to closely support Notcurses for the
foreseeable future.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: needs-packaging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873696

Title:
  [needs-packaging] notcurses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1873696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872854] Re: GCC-10 library conflict on s390x

[Daniel Black]

Not enabled by default, but whitelisted https://github.com/travis-ci
/apt-source-safelist/blob/master/ubuntu.json#L557 and one of the easiest
ways to run CI on multiple gcc compiler versions, and architectures
since fairly recently (https://docs.travis-ci.com/user/multi-cpu-
architectures/).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872854

Title:
  GCC-10 library conflict on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1872854/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869925] Re: syslog 50GB in a few hours

[alukard black]

I also tried with or without oibaf amd mesa drivers the issue remains.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869925

Title:
  syslog 50GB in a few hours

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1869925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1869925] [NEW] syslog 50GB in a few hours

[alukard black]

Public bug reported:

I have a Radeon RX 5700 XT
Using:
Ubuntu 18.04
kernels 5.3.41 42 43 45
mesa drivers 20.1 19.3

I don't know which package is the problem, I only know it's related to GPU
And I saw the same issue here:
https://gitlab.freedesktop.org/drm/amd/issues/912#login-pane

The following message is repeated many times per second and is filling my logs
/var/log/kern.log and syslog 

Mar 31 12:52:24 Amaterasu kernel: [ 1217.976843] WARNING: CPU: 5 PID: 6277 at 
/build/linux-hwe-UUUsac/linux-hwe-5.3.0/drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1999
 dcn20_setup_gsl_group_as_lock+0x20e/0x230 [amdgpu]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976844] Modules linked in: nls_utf8 
ntfs nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle xt_MASQUERADE iptable_nat bridge stp llc ebtable_filter ebtables 
aufs overlay binfmt_misc nls_iso8859_1 edac_mce_amd snd_hda_codec_realtek 
kvm_amd snd_hda_codec_generic ledtrig_audio kvm snd_hda_codec_hdmi irqbypass 
snd_hda_intel snd_intel_nhlt snd_hda_codec amdgpu snd_hda_core snd_hwdep 
snd_pcm crct10dif_pclmul snd_seq_midi crc32_pclmul snd_seq_midi_event 
input_leds joydev ghash_clmulni_intel snd_rawmidi amd_iommu_v2 gpu_sched 
snd_seq ttm drm_kms_helper snd_seq_device aesni_intel snd_timer drm snd 
aes_x86_64 crypto_simd i2c_algo_bit fb_sys_fops syscopyarea cryptd sysfillrect 
glue_helper wmi_bmof sysimgblt k10temp ccp soundcore mac_hid ip6t_REJECT 
nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype xt_conntrack
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976865]  ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast sch_fq_codel nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
parport_pc iptable_filter bpfilter ppdev sunrpc lp parport ip_tables x_tables 
autofs4 hid_generic usbhid hid uas usb_storage nvme i2c_piix4 r8169 ahci 
nvme_core realtek libahci wmi gpio_amdpt gpio_generic
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976876] CPU: 5 PID: 6277 Comm: 
kworker/u64:0 Tainted: GW  OE 5.3.0-45-generic #37~18.04.1-Ubuntu
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976877] Hardware name: Micro-Star 
International Co., Ltd MS-7C02/B450 TOMAHAWK MAX (MS-7C02), BIOS 3.50 11/07/2019
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976882] Workqueue: events_unbound 
commit_work [drm_kms_helper]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976929] RIP: 
0010:dcn20_setup_gsl_group_as_lock+0x20e/0x230 [amdgpu]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976934] Code: 02 00 00 fb e9 01 ff ff 
ff 48 c7 c7 40 25 16 c1 e8 6a 94 6e ce 0f 0b 48 c7 c7 40 25 16 c1 c6 83 60 02 
00 00 00 e8 55 94 6e ce <0f> 0b e9 49 fe ff ff e8 26 85 67 ce 48 c7 c7 40 25 16 
c1 e8 3d 94
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976939] RSP: 0018:a72d8953fa60 
EFLAGS: 00010286
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976945] RAX: 0024 RBX: 
9c00a1af01b8 RCX: 0006
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976950] RDX:  RSI: 
0086 RDI: 9c01ce757440
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976954] RBP: a72d8953faa8 R08: 
000bd121 R09: 0004
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976958] R10:  R11: 
0001 R12: 0001
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976962] R13: 0001 R14: 
9c01c799 R15: 9c00a1af01b8
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976968] FS:  () 
GS:9c01ce74() knlGS:
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976969] CS:  0010 DS:  ES:  
CR0: 80050033
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976970] CR2: 5568a4761000 CR3: 
00036deec000 CR4: 00340ee0
Mar 31 12:52:24 Amaterasu kernel: [ 1217.976970] Call Trace:
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977018]  
dcn20_pipe_control_lock.part.17+0x170/0x240 [amdgpu]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977069]  
dcn20_pipe_control_lock+0x1d/0x20 [amdgpu]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977122]  
dc_commit_updates_for_stream+0x1099/0x1380 [amdgpu]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977137]  ? 
drm_vblank_enable+0x4b/0x140 [drm]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977185]  
amdgpu_dm_atomic_commit_tail+0x109a/0x1e20 [amdgpu]
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977189]  ? update_load_avg+0x82/0x620
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977191]  ? __switch_to_asm+0x34/0x70
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977192]  ? __switch_to_asm+0x40/0x70
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977193]  ? __switch_to_asm+0x34/0x70
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977194]  ? __switch_to_asm+0x40/0x70
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977195]  ? __switch_to_asm+0x34/0x70
Mar 31 12:52:24 Amaterasu kernel: [ 1217.977195]  ? 

[Bug 1858452] [NEW] exFat filesystem driver seems to check a directory case sensitive and create directories case insensitive

[Christopher Black]

Public bug reported:

Hi,

I am currently experiencing the following problem in calibre:
https://bugs.launchpad.net/calibre/+bug/1858425

It throws an exception if the folder name changes only by changing some
of the characters, and then deletes all the files in the folder.

After reporting the issue to calibre the current working theory is, that the 
creation and the check is implemented differntly in the file system driver.
They first check if a directory exists and try to create it immediatly 
afterwards. But the creation throws an exception that the directory already 
exists. 

The system ist running on
Ubuntu 18.04
exfat-fuse 1.2.8-1

Could you please take a look.

Thanks.

Best regards
miracle152004

** Affects: fuse-exfat (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/1858452

Title:
  exFat filesystem driver seems to check a directory case sensitive and
  create directories case insensitive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-exfat/+bug/1858452/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838645] Re: openjdk Version: 8u222-b10-1ubuntu1~16.04.1 missing sun/security/validator/KeyStores.class

[Peter Black]

I've also encountered this issue, while installing some third-party
security software (a Radius agent). Can someone confirm whether the
omission of this class was intentional or an accident?

Thanks also to Theo, as his solution worked for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838645

Title:
  openjdk Version: 8u222-b10-1ubuntu1~16.04.1 missing
  sun/security/validator/KeyStores.class

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1838645/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778589] Re: Typographical error in Hungarian

[Peter Black]

Before boot, after selecting F2 hungarian language I entered F6 expert
mode kernel parameters using CapsLock using qwErty. Only the letter e
became large. Same thing happens with the writer of the bugreport. Boot
image attached. Thanks, Peter

** Attachment added: "boot screen"
   
https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1778589/+attachment/5281271/+files/IMG_20190806_132105a.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778589

Title:
  Typographical error in Hungarian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1778589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795913] Re: Systemd Resolver works unreliable to local DNS Names

[Kelly Black]

I have a similar issue (dns server running on a DSL router).  The router
assigns hostnames ending in .home

Seems to break resolution for the systemd-resolved as well (only working
sometimes).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795913

Title:
  Systemd Resolver works unreliable to local DNS Names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[joe black]

Hi, I would like to confirm this as this also affects not only my client
but also my Colleagues (thinkpad T460s and T470s). The Problem seem to
occur after a few minutes of inactiviy randomly. Some experience this
3-4 times/day while some 2-5 times a week.

Running on Ubuntu Bionic 18.04
Kernel Version: 4.15.0-36-generic

Kernel Log is attached.

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5205731/+files/kern.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727662

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1727662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741931] Re: Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

[Evan Black]

Still broken as ever in ubuntu 18.04
With the lack of plugins for the latest thunderbird, evolution seems to be 
about the only real alternative.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741931

Title:
  Cannot enable Jean-Yves Lefort's Mail Notification plugin in Evolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mail-notification/+bug/1741931/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1786658] [NEW] splint: does not know about multiarch paths

[Daniel Black]

Public bug reported:

https://github.com/ClusterLabs/libqb/blob/master/lib/Makefile.am#L149
has this hack and while Debian has fixed it Ubuntu the build/check for
non-x86 will fial.

This has been fixed in Debian.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675025

** Affects: splint (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/1786658

Title:
  splint: does not know about multiarch paths

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/splint/+bug/1786658/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784779] [NEW] libglib2.0-dev cross architecture installation fails

[Daniel Black]

Public bug reported:

While attempting to install libglib2.0-dev for a cross-compile I ran
into the following dependency issue;

on x86_64 host:

$ cat Dockerfile
ARG BASE=ubuntu:18.04
FROM $BASE

ENV DEBIAN_FRONTEND=noninteractive

ARG DEBARCH=s390x

RUN echo "deb [arch=$DEBARCH] http://ports.ubuntu.com/ubuntu-ports
bionic main universe" >> /etc/apt/sources.list

# Install package for static cross compilation
RUN dpkg --add-architecture $DEBARCH; \
apt-get -y update || true

ARG PACKAGE=libxml2-dev

RUN apt-get -y install $PACKAGE:$DEBARCH ; \
rm -rf /var/lib/apt/lists/*


$ docker build  --build-arg DEBARCH=ppc64el   --build-arg 
PACKAGE=libglib2.0-dev  .
Sending build context to Docker daemon   2.56kB
Step 1/8 : ARG BASE=ubuntu:18.04
Step 2/8 : FROM $BASE
 ---> 113a43faa138
Step 3/8 : ENV DEBIAN_FRONTEND=noninteractive
 ---> Using cache
 ---> 5c2ee26240f2
Step 4/8 : ARG DEBARCH=s390x
 ---> Using cache
 ---> 83be859bd660
Step 5/8 : RUN echo "deb [arch=$DEBARCH] http://ports.ubuntu.com/ubuntu-ports 
bionic main universe" >> /etc/apt/sources.list
 ---> Using cache
 ---> 981e02924110
Step 6/8 : RUN dpkg --add-architecture $DEBARCH; apt-get -y update || true
 ---> Using cache
 ---> b210ae3169ec
Step 7/8 : ARG PACKAGE=libuuid1
 ---> Using cache
 ---> 25926cf2ef2b
Step 8/8 : RUN apt-get -y install $PACKAGE:$DEBARCH ; rm -rf 
/var/lib/apt/lists/*
 ---> Running in 0a65b7ccea56
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libglib2.0-dev:ppc64el : Depends: libglib2.0-0:ppc64el (= 2.56.1-2ubuntu1) but 
it is not going to be installed
  Depends: libglib2.0-bin:ppc64el (= 2.56.1-2ubuntu1) 
but it is not going to be installed
  Depends: libglib2.0-dev-bin:ppc64el (= 
2.56.1-2ubuntu1) but it is not going to be installed
  Depends: pkg-config:ppc64el


Commenting out the repo for Ubuntu ports was able to install the same package 
on Debian:stable without conflicts.

$ docker build  --build-arg BASE=debian:stable   --build-arg DEBARCH=ppc64el   
--build-arg PACKAGE=libglib2.0-dev  .
Sending build context to Docker daemon   2.56kB
Step 1/7 : ARG BASE=ubuntu:18.04
Step 2/7 : FROM $BASE
 ---> b18abcb8ff46
Step 3/7 : ENV DEBIAN_FRONTEND=noninteractive
 ---> Using cache
 ---> 83aa1773a21e
Step 4/7 : ARG DEBARCH=s390x
 ---> Using cache
 ---> 7a359b6826e9
Step 5/7 : RUN dpkg --add-architecture $DEBARCH; apt-get -y update || true
 ---> Running in d2028c09314e
Ign:1 http://cdn-fastly.deb.debian.org/debian stable InRelease
Get:4 http://security.debian.org/debian-security stable/updates InRelease [94.3 
kB]
Get:2 http://cdn-fastly.deb.debian.org/debian stable-updates InRelease [91.0 kB]
Get:5 http://security.debian.org/debian-security stable/updates/main amd64 
Packages [376 kB]
Get:6 http://security.debian.org/debian-security stable/updates/main ppc64el 
Packages [357 kB]
Get:3 http://cdn-fastly.deb.debian.org/debian stable Release [118 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian stable-updates/main amd64 
Packages [5148 B]
Get:8 http://cdn-fastly.deb.debian.org/debian stable-updates/main ppc64el 
Packages [5092 B]
Get:9 http://cdn-fastly.deb.debian.org/debian stable Release.gpg [2434 B]
Get:10 http://cdn-fastly.deb.debian.org/debian stable/main amd64 Packages [7099 
kB]
Get:11 http://cdn-fastly.deb.debian.org/debian stable/main ppc64el Packages 
[6919 kB]
Fetched 15.1 MB in 6s (2396 kB/s)
Reading package lists...
Removing intermediate container d2028c09314e
 ---> 845939568747
Step 6/7 : ARG PACKAGE=libuuid1
 ---> Running in b4f41ec4bc8b
Removing intermediate container b4f41ec4bc8b
 ---> ef4c946771ec
Step 7/7 : RUN apt-get -y install $PACKAGE:$DEBARCH ; rm -rf 
/var/lib/apt/lists/*
 ---> Running in eabeeaf82098
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  bzip2 dh-python file gcc-6-base:ppc64el libblkid1:ppc64el libc-dev-bin
  libc6:ppc64el libc6-dev:ppc64el libdpkg-perl libexpat1 libffi6
  libffi6:ppc64el libfile-fcntllock-perl libgcc1:ppc64el libgdbm3 libglib2.0-0
  libglib2.0-0:ppc64el libglib2.0-bin libglib2.0-data libicu57
  liblocale-gettext-perl libmagic-mgc libmagic1 libmount1:ppc64el libmpdec2
  libpcre16-3:ppc64el libpcre3:ppc64el libpcre3-dev:ppc64el
  libpcre32-3:ppc64el libpcrecpp0v5:ppc64el libperl5.24 libpython3-stdlib
  libpython3.5-minimal libpython3.5-stdlib libreadline7 libselinux1:ppc64el
  libsqlite3-0 libssl1.1 libstdc++6:ppc64el libuuid1:ppc64el libxml2
  linux-libc-dev:ppc64el manpages manpages-dev mime-support netbase perl
  perl-modules-5.24 

[Bug 1784772] [NEW] libuuid1-2.31.1-0.4ubuntu3 install fails with cross-arch install

[Daniel Black]

Public bug reported:

My goal was to install libxml2-dev:${arch} in a ubuntu for cross
compilation. This failed because of libuuid1's dependency information.

https://packages.ubuntu.com/bionic-updates/s390x/libuuid1/filelist
indicates its a multiarch package.

Attempting to install libuuid1 from another architecture is trying to
remove essential packages.

On a x86_64 host:

$ cat Dockerfile 
ARG BASE=ubuntu:18.04
FROM $BASE

ENV DEBIAN_FRONTEND=noninteractive

# Arch dependence
ARG DEBARCH=s390x
ARG PACKAGE=libuuid1

RUN echo "deb [arch=$DEBARCH] http://ports.ubuntu.com/ubuntu-ports
bionic main universe" >> /etc/apt/sources.list

# Install package for static cross compilation
RUN dpkg --add-architecture $DEBARCH; \
apt-get -y update; \
apt-get -y install $PACKAGE:$DEBARCH ; \
rm -rf /var/lib/apt/lists/*

$ docker build .
Sending build context to Docker daemon  2.048kB
Step 1/7 : ARG BASE=ubuntu:18.04
Step 2/7 : FROM $BASE
 ---> 113a43faa138
Step 3/7 : ENV DEBIAN_FRONTEND=noninteractive
 ---> Using cache
 ---> 5c2ee26240f2
Step 4/7 : ARG DEBARCH=s390x
 ---> Using cache
 ---> 83be859bd660
Step 5/7 : ARG PACKAGE=libuuid1
 ---> Using cache
 ---> 668235a94420
Step 6/7 : RUN echo "deb [arch=$DEBARCH] http://ports.ubuntu.com/ubuntu-ports 
bionic main universe" >> /etc/apt/sources.list
 ---> Running in 557433eca31b
Removing intermediate container 557433eca31b
 ---> 2a8aa77040e7
Step 7/7 : RUN dpkg --add-architecture $DEBARCH; apt-get -y update; 
apt-get -y install $PACKAGE:$DEBARCH ; rm -rf /var/lib/apt/lists/*
 ---> Running in 134f7edb28ed
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  gcc-8-base:s390x libc6:s390x libgcc1:s390x
Suggested packages:
  glibc-doc:s390x locales:s390x
Recommended packages:
  uuid-runtime:s390x
The following packages will be REMOVED:
  e2fsprogs fdisk libblkid1 libfdisk1 libmount1 libuuid1 mount sysvinit-utils
  util-linux
The following NEW packages will be installed:
  gcc-8-base:s390x libc6:s390x libgcc1:s390x libuuid1:s390x
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  e2fsprogs libblkid1 (due to e2fsprogs) libuuid1 (due to e2fsprogs) fdisk
  libfdisk1 (due to fdisk) libmount1 (due to fdisk) mount
  util-linux (due to mount) sysvinit-utils
0 upgraded, 4 newly installed, 9 to remove and 0 not upgraded.
E: Essential packages were removed and -y was used without 
--allow-remove-essential.
Removing intermediate container 134f7edb28ed


Removing the ubuntu-ports line from the Dockerfile resulted in a working 
install on debian:stable

$ docker build --build-arg BASE=debian:stable .
Sending build context to Docker daemon  2.048kB
Step 1/6 : ARG BASE=ubuntu:18.04
Step 2/6 : FROM $BASE
 ---> b18abcb8ff46
Step 3/6 : ENV DEBIAN_FRONTEND=noninteractive
 ---> Running in b4deef44a701
Removing intermediate container b4deef44a701
 ---> 83aa1773a21e
Step 4/6 : ARG DEBARCH=s390x
 ---> Running in ea75827e75da
Removing intermediate container ea75827e75da
 ---> 7a359b6826e9
Step 5/6 : ARG PACKAGE=libuuid1
 ---> Running in b4ec0003580e
Removing intermediate container b4ec0003580e
 ---> 2ae853e70822
Step 6/6 : RUN dpkg --add-architecture $DEBARCH; apt-get -y update; 
apt-get -y install $PACKAGE:$DEBARCH ; rm -rf /var/lib/apt/lists/*
 ---> Running in a6cc3937dcf9
Ign:1 http://cdn-fastly.deb.debian.org/debian stable InRelease
Get:2 http://cdn-fastly.deb.debian.org/debian stable-updates InRelease [91.0 kB]
Get:3 http://cdn-fastly.deb.debian.org/debian stable Release [118 kB]
Get:4 http://cdn-fastly.deb.debian.org/debian stable-updates/main amd64 
Packages [5148 B]
Get:5 http://cdn-fastly.deb.debian.org/debian stable-updates/main s390x 
Packages [5100 B]
Get:6 http://cdn-fastly.deb.debian.org/debian stable Release.gpg [2434 B]
Get:7 http://cdn-fastly.deb.debian.org/debian stable/main amd64 Packages [7099 
kB]
Get:8 http://security.debian.org/debian-security stable/updates InRelease [94.3 
kB]
Get:9 http://security.debian.org/debian-security stable/updates/main amd64 
Packages [376 kB]
Get:10 http://security.debian.org/debian-security stable/updates/main s390x 
Packages [360 kB]
Get:11 http://cdn-fastly.deb.debian.org/debian stable/main s390x Packages [6868 
kB]
Fetched 15.0 MB in 9s (1618 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  gcc-6-base:s390x libc6:s390x libgcc1:s390x uuid-runtime
Suggested packages:
  glibc-doc:s390x libc-l10n:s390x locales:s390x
The following NEW packages will be installed:
  gcc-6-base:s390x libc6:s390x libgcc1:s390x libuuid1:s390x uuid-runtime
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 2872 kB of archives.
...
Setting up libuuid1:s390x (2.29.2-1+deb9u1) 

[Bug 1768739] [NEW] Hyper-V "type clipboard text" option freezes OS

[Shadus Black]

Public bug reported:

When using Hyper-V with Windows Server 2016 and Ubuntu Server 18.04 LTS
the "type clipboard text" inside the view port of the VMs console and
having a string in the clipboard, pasting causes the operating system to
become completely unresponsive and requires a hard external reboot to
unfreeze the system. Upon logging in again, old processes like a Nano
session seem to still exist.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: clipboard hyper-v virtual-machine

** Tags added: hyper-v

** Tags added: clipboard machine virtual

** Tags removed: machine virtual
** Tags added: virtual-machine

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768739

Title:
  Hyper-V "type clipboard text" option freezes OS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1768739/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1722066] Re: no sound on internal speakers or headphones, then open the gnome_alsamixer, there are three head phone choices, the ones on the left is muted, leave it muted (or not) and turn up

[paint-it-black]

Yes updated to 17.10,  the same bug is in 17.10.

On Mon, Jan 15, 2018 at 5:13 PM, dino99 <1722...@bugs.launchpad.net>
wrote:

> That version is now dead
> http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-
> has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1722066
>
> Title:
>   no sound on internal speakers or headphones,  then open the
>   gnome_alsamixer, there are three head phone choices, the ones on the
>   left is muted, leave it muted (or not) and turn up the volume on that
>   one, and then the internal speakers will play sound
>
> Status in alsa-driver package in Ubuntu:
>   Invalid
>
> Bug description:
>   Eee PC  Seashell series.
>
>   There is no sound after installing Ubuntu Gnome 17.04.  The volume
>   control shows the sound turned all the way up.  The internal test
>   found under settings->sound runs but no sound plays.  Etc.
>
>   Installed a mixer and all looked correct, but still no sound.
>
>   work around:
>
>   Installed the gnome_alsamixer package.   Three headphone settings show
>   (strange).  Turn up the volume on the far left of the headphones,  and
>   then sound plays on the internal speakers.  This is true, although the
>   'mute' box under the far left headphones volume control remains
>   checked. Checking or unchecking that mute box does nothing.
>
>   Wish I could attach two screen shots for the mixer, a before and
>   after, but the report seems to only allow one, so I attached the
>   'after' one with working sound ..
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
>   Uname: Linux 4.10.0-35-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.4-0ubuntu4.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  shihju 1477 F pulseaudio
>   CurrentDesktop: GNOME
>   Date: Sun Oct  8 19:21:34 2017
>   InstallationDate: Installed on 2017-08-17 (51 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170412)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/30/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1401
>   dmi.board.asset.tag: To Be Filled By O.E.M.
>   dmi.board.name: 1015PE
>   dmi.board.vendor: ASUSTeK Computer INC.
>   dmi.board.version: x.xx
>   dmi.chassis.asset.tag: 0x
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK Computer INC.
>   dmi.chassis.version: x.x
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/30/2011:
> svnASUSTeKComputerINC.:pn1015PX:pvrx.x:rvnASUSTeKComputerINC.:
> rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
>   dmi.product.name: 1015PX
>   dmi.product.version: x.x
>   dmi.sys.vendor: ASUSTeK Computer INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+
> bug/1722066/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722066

Title:
  no sound on internal speakers or headphones,  then open the
  gnome_alsamixer, there are three head phone choices, the ones on the
  left is muted, leave it muted (or not) and turn up the volume on that
  one, and then the internal speakers will play sound

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1722066/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706291] Re: MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page size) minimum needed

[Daniel Black]

https://bugs.mysql.com/bug.php?id=87995 coming in 5.7.21

Thanks Robie for getting traction there.

** Bug watch added: MySQL Bug System #87995
   http://bugs.mysql.com/bug.php?id=87995

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706291

Title:
  MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page
  size) minimum needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706291] Re: MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page size) minimum needed

[Daniel Black]

I've updated bug 1706281. No reproducible test case yet. 1706281 is more
important that this one (if I can reproduce the fault yet).

If I don't get a confirmation for #1706281 in the next few days can you
please process this one separately.

I've also checked and the latest 5.7.20 release doesn't include a fix
for this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706291

Title:
  MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page
  size) minimum needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706281] Re: MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc during high load on PPC64

[Daniel Black]

I haven't managed to reproduce however I see no reason why the bug would
of gone away from the code changes made since the mysql versions Daniel
Axtens used when https://bugs.mysql.com/bug.php?id=80436 was written.
I'm just going to keep trying.

I see [~racb] was trying to bundle this patch with bug #1706291 however
from a logical point of view this is an independent bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706281

Title:
  MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc
  during high load on PPC64

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706281/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706281] Re: MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc during high load on PPC64

[Daniel Black]

apologies for the delay. still trying to get a test case. I'll continue
looking next week.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706281

Title:
  MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc
  during high load on PPC64

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706281/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706291] Re: MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page size) minimum needed

[Daniel Black]

FWIW the gdb was to show that 0 memory pages was allocated as file_size,
aka opt_tc_log_size (24k based on the minimum and default log-tc-size
setting), is less than tc_log_page_size (64k Power page size)

(gdb)
146 npages=(uint)file_length/tc_log_page_size;
(gdb) p npages
$16 = 0
(gdb) p pages
$17 = (TC_LOG_MMAP::st_page *) 0x11b324f0
(gdb) p key_memory_TC_LOG_MMAP_pages
$18 = 0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706291

Title:
  MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page
  size) minimum needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706291] Re: MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page size) minimum needed

[Daniel Black]

An alternate to ENABLE_DOWNLOAD

apt install googletest   (needs 1.8.0 - so zesty or artful)

sudo ln -s /usr/src/googletest /usr/src/googletest-release-1.8.0

and -DDOWNLOAD_ROOT=/usr/src in debian/rules instead of
-DENABLE_DOWNLOADS=1

unit tests will be build then.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706291

Title:
  MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page
  size) minimum needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706291] Re: MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page size) minimum needed

[Daniel Black]

On xenial. I've used the ENABLE_DOWNLOADS to get the google-mock/test
suite to get the unit test TCLogMMapTest.TClogCommit to compile.

$ sudo apt-get builddep mysql-5.7   

  
$ apt source mysql-5.7  

  
$ cd mysql-5.7-5.7.19/  

  
$ vi debian/rules   

  
add to cmake so the google-mock/test is build - getting it to use a package 
google-mock requires too much editing:

   
-DENABLE_DOWNLOADS=1 \



$ DEB_BUILD_OPTIONS=parallel=160  dpkg-buildpackage -us -uc -nc  2>&1 | tee 
~/mysql-5.7-package-build.log   
  

cd builddir
make gunit_large

$ gdb  unittest/gunit/merge_large_tests-t
(gdb) set args --gtest_filter=TCLogMMapTest.TClogCommit
(gdb) break TC_LOG_MMAP::open
(gdb) run
..
Breakpoint 1, 0x1086b938 in TC_LOG_MMAP::open (this=0x11b321d0, 
opt_name=0x7fffea08 "tc_log_mmap_test_105828") at 
/home/danielgb/mysql-5.7-5.7.19/sql/tc_log.cc:92
92  {
(gdb) p  opt_tc_log_size
$6 = 24576
(gdb) n
n
n
n
n
(gdb)
106   fn_format(logname,opt_name,mysql_data_home,"",MY_UNPACK_FILENAME);
(gdb) p tc_log_page_size
$8 = 65536

n
117 file_length= opt_tc_log_size;
(gdb)
n
n
n
137   data= (uchar *)my_mmap(0, (size_t)file_length, PROT_READ|PROT_WRITE,
(gdb)
139   if (data == MAP_FAILED)
(gdb)
138 MAP_NOSYNC|MAP_SHARED, fd, 0);
(gdb) p file_length
$9 = 24576
(gdb) n
139   if (data == MAP_FAILED)
(gdb)
146   npages=(uint)file_length/tc_log_page_size;
(gdb) n
148   if (!(pages=(PAGE *)my_malloc(key_memory_TC_LOG_MMAP_pages,
npages*sizeof(PAGE), 
MYF(MY_WME|MY_ZEROFILL

(gdb) n
(gdb)
152   for (pg=pages, i=0; i < npages; i++, pg++)
(gdb) p npages
$16 = 0
(gdb) p pages
$17 = (TC_LOG_MMAP::st_page *) 0x11b324f0
(gdb) p key_memory_TC_LOG_MMAP_pages
$18 = 0

(gdb)  c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x1086bcec in TC_LOG_MMAP::open (this=0x11b321d0, opt_name=) at /home/danielgb/mysql-5.7-5.7.19/sql/tc_log.cc:166
166 izeof(tc_log_magic)]= (uchar)total_ha_2pc;

With npages as 0, we do an allocation of 0 bytes which eventually
segfaults.


I've been a bit loose above with the number of n(ext) gdb steps.

After applying my patch from
https://bugs.mysql.com/file.php?id=25648_id=87175

$  unittest/gunit/merge_large_tests-t --gtest_filter=TCLogMMapTest.TClogCommit
# Running 1 test from 1 test case
1..1
# Global test environment set-up
# Run 1 TCLogMMapTest.TClogCommit
ok 1
# Global test environment tear-down
# Ran 1 test from 1 test case
# Passed 1 test

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706291

Title:
  MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page
  size) minimum needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714859] Re: oops in 4.4.0-62-generic (ppc64le)

[Daniel Black]

fyi - did more testing - seems to not to affect x86_64 - detailed test
should appear in https://lists.ozlabs.org/pipermail/linuxppc-dev soon.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714859

Title:
  oops in 4.4.0-62-generic (ppc64le)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714859] Re: oops in 4.4.0-62-generic (ppc64le)

[Daniel Black]

I hadn't used sshfs on Power machines before so there isn't a prior good
version.


Mainline v4.13 - jenkins-ppc64


steps on host:

virsh start {guest}

sshfs ozlabs@jenkins-ppc64:/home/ozlabs jenkins-ppc64/ -o
reconnect,idmap=user


cd jenkins-ppc64/linux

make -j 400  ; # something with a lot of read on sshfs

# on another terminal

virsh suspend jenkins-ppc64

killall -9 cc (or whatever processes is reading)


# resume guest

root@p87:~# virsh resume jenkins-ppc64
Domain jenkins-ppc64 resumed

root@p87:~# virsh list
 IdName   State

 1 jenkinsrunning
 2 jenkins-ppc64  running

root@p87:~# virsh list
 IdName   State

 1 jenkinsrunning
 2 jenkins-ppc64  running

root@p87:~# virsh list
 IdName   State

 1 jenkinsrunning
 2 jenkins-ppc64  running

root@p87:~# virsh list
 IdName   State

 1 jenkinsrunning
 2 jenkins-ppc64  running

root@p87:~# virsh console jenkins-ppc64
Connected to domain jenkins-ppc64
Escape character is ^]
Shared connection to p87 closed.

No further network connections to p87 could be established.


I happened to have a FSP ipmi sol activate console open:

(large amounts of tg3 0005:09:00.0 enP5p9s0f0:  removed - appologies if
I missed backtraces from specific CPUs).


root@p87:~# Watchdog CPU:160 detected Hard LOCKUP other CPUS:40
watchdog: BUG: soft lockup - CPU#64 stuck for 23s! [ksmd:1695]  


watchdog: BUG: soft lockup - CPU#160 stuck for 22s! [qemu-system-ppc:13057] 


INFO: rcu_sched self-detected stall on CPU  


64-...: (2600 ticks this GP) idle=8b2/141/0 
softirq=40596/40596 fqs=1148 
 (t=2601 jiffies g=18364 c=18363 q=1057)
INFO: rcu_sched detected stalls on CPUs/tasks:
Watchdog CPU:24 detected Hard LOCKUP other CPUS:160
Watchdog CPU:160 Hard LOCKUP
40-...: (1 GPs behind) idle=4a2/140/0 softirq=40283/40285 
fqs=1149 
64-...: (2601 ticks this GP) idle=8b2/142/0 
softirq=40596/40596 fqs=1149 
Watchdog CPU:8 Hard LOCKUP

Watchdog CPU:8 became unstuck
Watchdog CPU:56 detected Hard LOCKUP other CPUS:112
Watchdog CPU:24 Hard LOCKUP
Watchdog CPU:24 became unstuck
rcu_sched kthread starved for 1074 jiffies! g18364 c18363 f0x0 
RCU_GP_DOING_FQS(4) ->state=0x0
Watchdog CPU:112 became unstuck
Watchdog CPU:8 detected Hard LOCKUP other CPUS:64
Watchdog CPU:64 Hard LOCKUP
watchdog: BUG: soft lockup - CPU#64 stuck for 22s! [ksmd:1695]
watchdog: BUG: soft lockup - CPU#144 stuck for 22s! [qemu-system-ppc:21857]
INFO: rcu_sched self-detected stall on CPU
64-...: (9303 ticks this GP) idle=8b2/141/0 
softirq=40596/40596 fqs=3608

 (t=10406 jiffies g=18364 c=18363 q=5303)   


INFO: rcu_sched detected stalls on CPUs/tasks:  


40-...: (1 GPs behind) idle=4a2/140/0 softirq=40283/40285 
fqs=3608 
64-...: (9303 ticks this GP) idle=8b2/141/0 
softirq=40596/40596 fqs=3608 
(detected by 8, t=11509 jiffies, g=18364, c=18363, q=5786)
Watchdog CPU:24 detected Hard LOCKUP other CPUS:8
rcu_sched kthread starved for 2206 jiffies! g18364 c18363 f0x0 
RCU_GP_WAIT_FQS(3) ->state=0x1
Watchdog CPU:8 became unstuck
sd 0:2:1:0: [sdb] tag#13 Resetting device
watchdog: BUG: soft lockup - CPU#64 stuck for 24s! [ksmd:1695]
ipr 0001:08:00.0: Timed out waiting for aborted commands
sd 0:2:3:0: [sdd] tag#5 Resetting device
INFO: rcu_sched self-detected stall on CPU
64-...: (16006 ticks this GP) idle=8b2/141/0 
softirq=40596/40596 fqs=6187 
 (t=18211 jiffies g=18364 c=18363 q=9258)
INFO: rcu_sched detected stalls on CPUs/tasks:
ipr 0001:08:00.0: Timed out waiting for aborted commands
sd 0:2:5:0: [sdf] tag#11 Resetting device
tg3 0005:09:00.0 enP5p9s0f0: transmit timed out, resetting
tg3 0005:09:00.0 enP5p9s0f0: 0x: 0x165714e4, 0x00100546, 0x0201, 
0x0080
tg3 0005:09:00.0 enP5p9s0f0: 0x0010: 0x000c, 

[Bug 1714420] Re: kernel oops - kvm guest started at boot time

[Daniel Black]

danielgb@p87:~$  apt-get source linux-image-4.4.0-93-generic
danielgb@p87:~$ cd linux-4.4.0/
danielgb@p87:~/linux-4.4.0$ patch -p1  <  
../index.html\?id\=e47057151422a67ce08747176fa21cb3b526a2c9
checking file arch/powerpc/kvm/book3s_hv.c
Hunk #1 succeeded at 2708 (offset -503 lines).
danielgb@p87:~/linux-4.4.0$ fakeroot debian/rules clean
danielgb@p87:~/linux-4.4.0$ AUTOBUILD=1 fakeroot debian/rules binary-debs
..
danielgb@p87:~/linux-4.4.0$ ls ../*deb
../linux-headers-4.4.0-93-generic_4.4.0-93.116_ppc64el.deb  
../linux-image-extra-4.4.0-93-generic_4.4.0-93.116_ppc64el.deb  
../linux-tools-4.4.0-93-generic_4.4.0-93.116_ppc64el.deb
../linux-image-4.4.0-93-generic_4.4.0-93.116_ppc64el.deb
../linux-tools-4.4.0-93_4.4.0-93.116_ppc64el.deb
danielgb@p87:~/linux-4.4.0$ sudo dpkg -i ../*deb
danielgb@p87:~/linux-4.4.0$ sudo reboot

[0.00] Linux version 4.4.0-93-generic (root@p87) (gcc version
5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #116 SMP Mon Sep 4
10:00:39 AEST 2017 (Ubuntu 4.4.0-93.116-generic 4.4.79)


root@p87:~# dmesg | grep -i kvm
[  259.411176] KVM guest htab at c0795900 (order 30), LPID 1
[  288.766819] KVM guest htab at c0799900 (order 29), LPID 2

root@p87:~# dmesg | grep -i oops
root@p87:~#

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714420

Title:
  kernel oops -  kvm guest started at boot time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714420/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714859] Re: oops in 4.4.0-62-generic (ppc64le)

[Daniel Black]

While attempting to reproduce:

With make -j 400 running in another shell:

danielgb@p87:~$ virsh suspend  jenkins-ppc64
Domain jenkins-ppc64 suspended

wait over 2 minutes.

danielgb@p87:~$ virsh resume  jenkins-ppc64
Domain jenkins-ppc64 resumed


danielgb@p87:~$ virsh list
 IdName   State

 1 jenkinsrunning
 2 jenkins-ppc64  running


[ 5761.783275] INFO: task cmake:42287 blocked for more than 120 seconds.
[ 5761.783370]   Tainted: GE   4.4.0-93-generic #116
[ 5761.783382] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 5761.783448] cmake   D 3fffac68e13c 0 42287  42278 0x0004
[ 5761.783453] Call Trace:
[ 5761.783459] [c05fd6c4b750] [8000] 0x8000 (unreliable)
[ 5761.783467] [c05fd6c4b920] [c0015cb8] __switch_to+0x1f8/0x350
[ 5761.783473] [c05fd6c4b970] [c0b08a1c] __schedule+0x30c/0x990
[ 5761.783476] [c05fd6c4ba40] [c0b090e8] schedule+0x48/0xc0
[ 5761.783480] [c05fd6c4ba70] [c0b09630] 
schedule_preempt_disabled+0x20/0x30
[ 5761.783484] [c05fd6c4ba90] [c0b0b7fc] 
__mutex_lock_slowpath+0xec/0x1f0
[ 5761.783487] [c05fd6c4bb10] [c0b0b978] mutex_lock+0x78/0xa0
[ 5761.783493] [c05fd6c4bb40] [c02f890c] walk_component+0x2fc/0x420
[ 5761.783496] [c05fd6c4bbb0] [c02f8bec] link_path_walk+0x1bc/0x660
[ 5761.783499] [c05fd6c4bc40] [c02f962c] path_lookupat+0xdc/0x1d0
[ 5761.783503] [c05fd6c4bc90] [c02fb9d8] filename_lookup+0xa8/0x1b0
[ 5761.783507] [c05fd6c4bdb0] [c02e1f70] SyS_faccessat+0xe0/0x2e0
[ 5761.783511] [c05fd6c4be30] [c0009204] system_call+0x38/0xb4
[ 5761.783515] INFO: task cc1plus:42687 blocked for more than 120 seconds.
[ 5761.783579]   Tainted: GE   4.4.0-93-generic #116
[ 5761.783641] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 5761.783715] cc1plus D 3fffa515dc2c 0 42687  42686 0x0004
[ 5761.783719] Call Trace:
[ 5761.783722] [c05fd6c47720] [7265677368657265] 0x7265677368657265 
(unreliable)
[ 5761.783726] [c05fd6c478f0] [c0015cb8] __switch_to+0x1f8/0x350
[ 5761.783729] [c05fd6c47940] [c0b08a1c] __schedule+0x30c/0x990
[ 5761.783732] [c05fd6c47a10] [c0b090e8] schedule+0x48/0xc0
[ 5761.783736] [c05fd6c47a40] [c0b09630] 
schedule_preempt_disabled+0x20/0x30
[ 5761.783739] [c05fd6c47a60] [c0b0b7fc] 
__mutex_lock_slowpath+0xec/0x1f0
[ 5761.783743] [c05fd6c47ae0] [c0b0b978] mutex_lock+0x78/0xa0
[ 5761.783746] [c05fd6c47b10] [c02f890c] walk_component+0x2fc/0x420
[ 5761.783749] [c05fd6c47b80] [c02f8bec] link_path_walk+0x1bc/0x660
[ 5761.783753] [c05fd6c47c10] [c02faadc] path_openat+0xac/0x3c0
[ 5761.783756] [c05fd6c47c90] [c02fca1c] do_filp_open+0xfc/0x170
[ 5761.783759] [c05fd6c47db0] [c02e3210] do_sys_open+0x1c0/0x3b0
[ 5761.783762] [c05fd6c47e30] [c0009204] system_call+0x38/0xb4
[ 5761.783767] INFO: task cc1plus:42706 blocked for more than 120 seconds.
[ 5761.783830]   Tainted: GE   4.4.0-93-generic #116
[ 5761.783892] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 5761.783966] cc1plus D 3fff7f07dc2c 0 42706  42702 0x0004


danielgb@p87:~$ virsh console jenkins-ppc64
Connected to domain jenkins-ppc64
Escape character is ^]


$ ssh root@jenkins-ppc64
ssh: connect to host jenkins-ppc64 port 22: No route to host


danielgb@p87:~$ virsh reset jenkins-ppc64
Domain jenkins-ppc64 was reset


(didn't result in a guest reset). No network or virsh console connection could 
be made for several minutes. Ended up doing a virsh destroy jenkins-ppc64.


** Attachment added: "steps taken on x86_64 guest - didn't reproduce problem."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714859/+attachment/4943896/+files/oops-ubuntu-ka5-intel-fuse.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714859

Title:
  oops in 4.4.0-62-generic (ppc64le)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714859] [NEW] oops in 4.4.0-62-generic (ppc64le)

[Daniel Black]

Public bug reported:

Sep  1 14:23:30 p87 kernel: [17274563.423972] device vnet2 entered promiscuous 
mode
Sep  1 14:23:30 p87 kernel: [17274563.436101] br0: port 4(vnet2) entered 
forwarding state
Sep  1 14:23:30 p87 kernel: [17274563.436113] br0: port 4(vnet2) entered 
forwarding state
Sep  1 14:23:31 p87 kernel: [17274564.005034] audit: type=1400 
audit(1504239811.140:793): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=18952 comm="apparmor_parser"
Sep  1 14:23:31 p87 kernel: [17274564.019911] audit: type=1400 
audit(1504239811.156:794): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=18952 comm="apparmor_parser"
Sep  1 14:23:31 p87 kernel: [17274564.324291] KVM guest htab at 
c079a100 (order 29), LPID 3
Sep  1 14:23:45 p87 kernel: [17274578.483572] br0: port 4(vnet2) entered 
forwarding state
Sep  1 14:26:53 p87 kernel: [17274766.572284] br0: port 4(vnet2) entered 
disabled state
Sep  1 14:26:53 p87 kernel: [17274766.579930] device vnet2 left promiscuous mode
Sep  1 14:26:53 p87 kernel: [17274766.579932] br0: port 4(vnet2) entered 
disabled state
Sep  1 14:26:54 p87 kernel: [17274767.303109] audit: type=1400 
audit(1504240014.441:795): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22668 comm="apparmor_parser"
Sep  1 14:26:56 p87 kernel: [17274768.917394] audit: type=1400 
audit(1504240016.053:796): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22672 comm="apparmor_parser"
Sep  1 14:26:56 p87 kernel: [17274768.917673] audit: type=1400 
audit(1504240016.053:797): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=22672 comm="apparmor_parser"
Sep  1 14:26:56 p87 kernel: [17274768.982783] device vnet2 entered promiscuous 
mode
Sep  1 14:26:56 p87 kernel: [17274768.994891] br0: port 4(vnet2) entered 
forwarding state
Sep  1 14:26:56 p87 kernel: [17274768.994902] br0: port 4(vnet2) entered 
forwarding state
Sep  1 14:26:56 p87 kernel: [17274769.535982] audit: type=1400 
audit(1504240016.673:798): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22702 comm="apparmor_parser"
Sep  1 14:26:56 p87 kernel: [17274769.546719] audit: type=1400 
audit(1504240016.685:799): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=22702 comm="apparmor_parser"
Sep  1 14:26:57 p87 kernel: [17274769.861666] KVM guest htab at 
c079a100 (order 29), LPID 3
Sep  1 14:27:11 p87 kernel: [17274784.050382] br0: port 4(vnet2) entered 
forwarding state
Sep  1 14:28:30 p87 kernel: [17274863.605174] Unable to handle kernel paging 
request for data at address 0x0008
Sep  1 14:28:30 p87 kernel: [17274863.605188] Faulting instruction address: 
0xc044edcc
Sep  1 14:28:30 p87 kernel: [17274863.605195] Oops: Kernel access of bad area, 
sig: 11 [#1]
Sep  1 14:28:30 p87 kernel: [17274863.605199] SMP NR_CPUS=2048 NUMA PowerNV
Sep  1 14:28:30 p87 kernel: [17274863.605206] Modules linked in: tcp_diag 
inet_diag ebtable_filter ebtables binfmt_misc veth xfrm_user xfrm_algo 
vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack 
br_netfilter overlay bridge stp llc kvm_hv uio_pdrv_genirq powernv_rng 
ibmpowernv vmx_crypto leds_powernv uio ipmi_powernv ipmi_msghandler kvm_pr kvm 
autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid10 raid1 ses 
enclosure mlx4_en be2net lpfc mlx4_core vxlan ip6_udp_tunnel scsi_transport_fc 
udp_tunnel ipr [last unloaded: ebtables]
Sep  1 14:28:30 p87 kernel: [17274863.605294] CPU: 24 PID: 19018 Comm: sshfs 
Not tainted 4.4.0-62-generic #83-Ubuntu
Sep  1 14:28:30 p87 kernel: [17274863.605300] task: c01fc9c7c8e0 ti: 
c01fe4c1 task.ti: c01fe4c1
Sep  1 14:28:30 p87 kernel: [17274863.605306] NIP: c044edcc LR: 
c044ede0 CTR: c0108b20
Sep  1 14:28:30 p87 kernel: [17274863.605311] REGS: c01fe4c139a0 TRAP: 0300 
  Not tainted  (4.4.0-62-generic)
Sep  1 14:28:30 p87 kernel: [17274863.605315] MSR: 90009033 
  CR: 24000424  XER: 
Sep  1 14:28:30 p87 kernel: [17274863.605330] CFAR: c0008468 DAR: 
0008 DSISR: 4200 SOFTE: 1
Sep  1 14:28:30 p87 kernel: [17274863.605330] GPR00: c044ede0 

[Bug 1714420] Re: kernel oops - kvm guest started at boot time

[Daniel Black]

Introduced 4.4.0-88.111 "KVM: PPC: Book3S HV: Preserve userspace HTM
state properly" according to changelog.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714420

Title:
  kernel oops -  kvm guest started at boot time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714420/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714420] Re: kernel oops - kvm guest started at boot time

[Daniel Black]

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e47057151422a67ce08747176fa21cb3b526a2c9
is the missing commit.

This is a fix to commit 46a704f8409f (
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=46a704f8409f),
 which I have validated exists in linux_4.4.0-93.116.diff.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714420

Title:
  kernel oops -  kvm guest started at boot time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714420/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714420] [NEW] kernel oops - kvm guest started at boot time

[Daniel Black]

Public bug reported:

[0.00] Linux version 4.4.0-93-generic (buildd@bos01-ppc64el-025)
(gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) )
#116-Ubuntu SMP Fri Aug 11 16:30:16 UTC 2017 (Ubuntu
4.4.0-93.116-generic 4.4.79)

...
[  380.184554] KVM guest htab at c0799900 (order 29), LPID 2
[  380.527576] Facility 'TM' unavailable, exception at 0xd0003aad7f10, 
MSR=90009033
[  380.527717] Oops: Unexpected facility unavailable exception, sig: 6 [#2]
[  380.527775] SMP NR_CPUS=2048 NUMA PowerNV
[  380.527823] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM 
iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables 
ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter 
overlay binfmt_misc bridge stp llc kvm_hv uio_pdrv_genirq uio leds_powernv 
ipmi_powernv ibmpowernv vmx_crypto powernv_rng ipmi_msghandler kvm_pr kvm 
autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 raid10 ses 
enclosure mlx4_en be2net lpfc vxlan mlx4_core scsi_transport_fc ip6_udp_tunnel 
udp_tunnel ipr
[  380.528781] CPU: 24 PID: 4277 Comm: qemu-system-ppc Tainted: G  D
 4.4.0-93-generic #116-Ubuntu
[  380.528861] task: c3c389b0 ti: c01fb2428000 task.ti: 
c01fb2428000
[  380.528929] NIP: d0003aad7f10 LR: d00037d52a14 CTR: d0003aad7e40
[  380.528997] REGS: c01fb242b7b0 TRAP: 0f60   Tainted: G  D  
(4.4.0-93-generic)
[  380.529076] MSR: 90009033   CR: 22024848  
XER: 
[  380.529247] CFAR: d0003aad7ea4 SOFTE: 1
   GPR00: d00037d52a14 c01fb242ba30 d0003aaec018 
c01fdbf6
   GPR04: c01f8580 c01fb242bbc0  

   GPR08: 0001 c3c389b0 0001 
d00037d578f8
   GPR12: d0003aad7e40 cfb4e400  
001f
   GPR16: 3fff7206 0080 3fff892c4390 
3fff7285f200
   GPR20: 010009988430 0100099affd0 3fff7285eb60 
100c1ff0
   GPR24: 3bcf4e10 3fff72040028  
c01fdbf6
   GPR28:  c01f8580 c01fdbf6 
c01f8580
[  380.530119] NIP [d0003aad7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
[  380.530188] LR [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
[  380.530245] Call Trace:
[  380.530270] [c01fb242ba30] [c01fb242bab0] 0xc01fb242bab0 
(unreliable)
[  380.530353] [c01fb242bb70] [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 
[kvm]
[  380.530436] [c01fb242bba0] [d00037d4f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
[  380.530519] [c01fb242bbe0] [d00037d43918] kvm_vcpu_ioctl+0x528/0x7b0 
[kvm]
[  380.530602] [c01fb242bd40] [c02fff60] do_vfs_ioctl+0x480/0x7d0
[  380.530671] [c01fb242bde0] [c0300384] SyS_ioctl+0xd4/0xf0
[  380.530742] [c01fb242be30] [c0009204] system_call+0x38/0xb4
[  380.530837] Instruction dump:
[  380.530904] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108
[  380.531126] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 
7d4122a6
[  380.531350] ---[ end trace 8f9b3b82f9a07d76 ]---


Needs kernel patch e47057151422a67ce08747176fa21cb3b526a2c9 according to Cyril

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic 4.4.0-93.116
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic ppc64le
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Sep  1 15:03 seq
 crw-rw 1 root audio 116, 33 Sep  1 15:03 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Fri Sep  1 15:34:14 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: root=UUID=c3fd6cdf-331d-4c9a-9a51-efabe9deea59 ro splash 
quiet
ProcLoadAvg: 

[Bug 1706281] Re: MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc during high load on PPC64

[Daniel Black]

Previous "Clarification from upstream" is a different bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706281

Title:
  MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc
  during high load on PPC64

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1706281/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706281] Re: MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc during high load on PPC64

[Daniel Black]

** Also affects: mysql-5.6 (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/1706281

Title:
  MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc
  during high load on PPC64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706281/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706281] Re: MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc during high load on PPC64

[Daniel Black]

** Package changed: dbf2mysql (Ubuntu) => mysql-5.7 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706281

Title:
  MySQL-5.6/5.7 innodb assertion !lock->recursive assert in sync0rw.cc
  during high load on PPC64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706281/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706291] Re: MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page size) minimum needed

[Daniel Black]

** Package changed: dbf2mysql (Ubuntu) => mysql-5.7 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706291

Title:
  MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page
  size) minimum needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs