from:"Brian Foster"

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say so

2022-09-14 Thread Brian Foster

Yeah, I was confused by this at first too.  Here's a hint, try "apt-mark
showhold":

   $ apt-mark showhold
   $ 

If nothing is printed (as above), then the "issue" PRESUMABLY isn't
local to your system; ergo, the cause is PROBABLY at the server, such as
a phased update.  Relax.  It will probably sort itself out in a few
days.  (This hint is from https://askubuntu.com/questions/640986/how-to-
get-a-list-of-installed-packages-held-back-from-upgrade "How to get a
list of installed packages held back from upgrade?" (APT, etc., experts
can please correct).)

As per above (#3), whilst the reason isn't stored, that does not mean
apt(8)'s message cannot be improved.  For example, instead of the
current:

   The following packages have been kept back:
  PKG...

better might be something like:

   The following packages have been kept back:
  PKG...
   Some or all of those packages may be deliberately "on hold" on the server;
   please see manual page XXX(N) for information.

with (obviously) appropriate text in the manual page.  (Exactly which
man page is left to the experts.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1988819

Title:
  When apt keeps back packages due to phased updates, it should say so

Status in apt package in Ubuntu:
  New

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec

2020-11-12 Thread Brian Foster

I had what I _thought_ originally was a very similar issue with Kubuntu 20.04.1 
LTS
on a Clevo-NJ70, but further investigation suggests my problem,
despite the same-ish messages, is somewhat different.

See bug #1904075 ("[NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No
sound at all (or so KDE 'thinks'").

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1886626

Title:
  after login to gnome with snd_hda_intel :00:1f.3: No response from
  codec

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  After login to gnome, login takes an unsual amount of time.
  Goes back to login screen.
  On second login, works normally but audio sliders are not showing correctly. 
After a while, it operates normally.
  Logs are showing a lot of
  snd_hda_intel :00:1f.3: No response from codec, resetting bus:last 
cmd0x20a70500
  +pci::00:1f.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-1063.68-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1063-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  killian68   1816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 08:56:11 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  InstallationDate: Installed on 2020-04-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1902311] Re: GNU sha256sum(1) --check (-c) output depends on order of --quiet and --warn

2020-11-01 Thread Brian Foster

** Summary changed:

- GNU sha256(1)  --check (-c) output depends on order of --quiet and --warn
+ GNU sha256sum(1)  --check (-c) output depends on order of --quiet and 
--warn

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1902311

Title:
  GNU sha256sum(1)  --check (-c) output depends on order of --quiet
  and --warn

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum,
  sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and
  --warn options.  This is counter-intuitive, not documented in the man(1) 
pages,
  and unnecessary.

  Simple example:

1$ date >/tmp/data
2$ sha256sum /tmp/data >/tmp/sums
3$ sha256sum -c --warn --quiet /tmp/sums# No output (expected)
4$ sha256sum -c --quiet --warn /tmp/sums# Unexpected "Ok"...
/tmp/data: OK
5$ 

  The manual page says (spurious lines omitted):

 The following five options are useful only when verifying checksums:
   --quiet   don't print OK for each successfully verified file
   -w, --warnwarn about improperly formatted checksum lines

  There is no reason --warn should affect the operation of --quiet (nor
  visa-versa).  The operations as documented are orthogonal.

  Attached is a bash(1) shell script written when puzzling over this
  inconsistent behaviour; it may be useful (use --help for a summary).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: coreutils 8.30-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Oct 30 21:34:31 2020
  InstallationDate: Installed on 2020-10-19 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1902311] Re: GNU sha256(1) --check (-c) output depends on order of --quiet and --warn

2020-10-30 Thread Brian Foster

Obviously, I meant sha256sum(1) in the bug's title!  (*sighs*)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1902311

Title:
  GNU sha256(1)  --check (-c) output depends on order of --quiet and
  --warn

Status in coreutils package in Ubuntu:
  New

Bug description:
  The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum,
  sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and
  --warn options.  This is counter-intuitive, not documented in the man(1) 
pages,
  and unnecessary.

  Simple example:

1$ date >/tmp/data
2$ sha256sum /tmp/data >/tmp/sums
3$ sha256sum -c --warn --quiet /tmp/sums# No output (expected)
4$ sha256sum -c --quiet --warn /tmp/sums# Unexpected "Ok"...
/tmp/data: OK
5$ 

  The manual page says (spurious lines omitted):

 The following five options are useful only when verifying checksums:
   --quiet   don't print OK for each successfully verified file
   -w, --warnwarn about improperly formatted checksum lines

  There is no reason --warn should affect the operation of --quiet (nor
  visa-versa).  The operations as documented are orthogonal.

  Attached is a bash(1) shell script written when puzzling over this
  inconsistent behaviour; it may be useful (use --help for a summary).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: coreutils 8.30-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Oct 30 21:34:31 2020
  InstallationDate: Installed on 2020-10-19 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1902311] [NEW] GNU sha256(1) --check (-c) output depends on order of --quiet and --warn

2020-10-30 Thread Brian Foster

Public bug reported:

The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum,
sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and
--warn options.  This is counter-intuitive, not documented in the man(1) pages,
and unnecessary.

Simple example:

  1$ date >/tmp/data
  2$ sha256sum /tmp/data >/tmp/sums
  3$ sha256sum -c --warn --quiet /tmp/sums# No output (expected)
  4$ sha256sum -c --quiet --warn /tmp/sums# Unexpected "Ok"...
  /tmp/data: OK
  5$ 

The manual page says (spurious lines omitted):

   The following five options are useful only when verifying checksums:
 --quiet   don't print OK for each successfully verified file
 -w, --warnwarn about improperly formatted checksum lines

There is no reason --warn should affect the operation of --quiet (nor
visa-versa).  The operations as documented are orthogonal.

Attached is a bash(1) shell script written when puzzling over this
inconsistent behaviour; it may be useful (use --help for a summary).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: coreutils 8.30-3ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Oct 30 21:34:31 2020
InstallationDate: Installed on 2020-10-19 (11 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: coreutils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "GNU Bash(1) script to show various differing behaviours 
(--help for summary)"
   
https://bugs.launchpad.net/bugs/1902311/+attachment/5429603/+files/sha-sum-chk.sh

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1902311

Title:
  GNU sha256(1)  --check (-c) output depends on order of --quiet and
  --warn

Status in coreutils package in Ubuntu:
  New

Bug description:
  The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum,
  sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and
  --warn options.  This is counter-intuitive, not documented in the man(1) 
pages,
  and unnecessary.

  Simple example:

1$ date >/tmp/data
2$ sha256sum /tmp/data >/tmp/sums
3$ sha256sum -c --warn --quiet /tmp/sums# No output (expected)
4$ sha256sum -c --quiet --warn /tmp/sums# Unexpected "Ok"...
/tmp/data: OK
5$ 

  The manual page says (spurious lines omitted):

 The following five options are useful only when verifying checksums:
   --quiet   don't print OK for each successfully verified file
   -w, --warnwarn about improperly formatted checksum lines

  There is no reason --warn should affect the operation of --quiet (nor
  visa-versa).  The operations as documented are orthogonal.

  Attached is a bash(1) shell script written when puzzling over this
  inconsistent behaviour; it may be useful (use --help for a summary).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: coreutils 8.30-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Oct 30 21:34:31 2020
  InstallationDate: Installed on 2020-10-19 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1850608] [NEW] Segfaults trying to send crash report

2019-10-30 Thread Brian Foster

Public bug reported:

After this morning's upgrade to "whoopsie 0.2.62ubuntu0.2"
plus "libwhoopsie0 0.2.62ubuntu0.2"(fix to bug #1830865),
whoopsie repeatedly crashes with a segfault (in what seems to be libc?).
An excerpt from /var/log/syslog (slightly redacted):

Oct 30 08:33:06 [REDACTED] systemd[1]: Started crash report submission daemon.
Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Using lock path: 
/var/lock/whoopsie/lock
Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] The default IPv4 route 
is: /org/freedesktop/NetworkManager/ActiveConnection/1
Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Parsing 
/var/crash/_usr_bin_kdeinit5.1000.crash.
Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Uploading 
/var/crash/_usr_bin_kdeinit5.1000.crash.
Oct 30 08:33:10 [REDACTED] kernel: [ 2129.099314] whoopsie[22414]: segfault at 
7f4f878a4000 ip 7f4f866fe5e1 sp 7ffe348bed78 error 4 in 
libc-2.27.so[7f4f86591000+1e7000]
Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Main process exited, 
code=dumped, status=11/SEGV
Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Failed with result 
'core-dump'.
Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Service hold-off time 
over, scheduling restart.
Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Scheduled restart job, 
restart counter is at 133.
Oct 30 08:33:11 [REDACTED] systemd[1]: Stopped crash report submission daemon.

The above sequence of logged events repeats endlessly,
with only(?) the times and whoospie PID changing.

The problem can be (temporarily) stopped by `service whoopsie stop';
using `service whoopsie start' resumes the above behaviour.
Rebooting does not "fix".

Manually running whoopsie shows the same behaviour:

$ sudo /bin/sh -c 'export CRASH_DB_URL=https://daisy.ubuntu.com; exec whoopsie 
-f'
[09:45:14] Using lock path: /var/lock/whoopsie/lock
[09:45:14] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
[09:45:14] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
[09:45:14] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
[09:45:14] Parsing /var/crash/_usr_bin_kdeinit5.1000.crash.
[09:45:14] Uploading /var/crash/_usr_bin_kdeinit5.1000.crash.
Segmentation fault
$ 
$ ls -la /var/crash/
total 33340
drwxrwsrwt  2 root whoopsie 4096 Oct 30 08:52 .
drwxr-xr-x 16 root root 4096 Sep 14  2018 ..
-rw-r--r--  1 root whoopsie  281 Oct 30 08:55 kexec_cmd
-rwxrwxrwx  1 root whoopsie0 Oct 30 08:22 .lock
-rw-r-  1 blf  whoopsie 17624101 Oct 30 08:53 
_usr_bin_kdeinit5.1000.crash
-rw-rw-r--  1 blf  whoopsie0 Oct 30 08:22 
_usr_bin_kdeinit5.1000.upload
-rw-r-  1 root whoopsie   398157 Oct 24 11:49 _usr_bin_sddm.0.crash
-rw-r-  1 whoopsie whoopsie 15996866 Oct 30 08:22 
_usr_bin_whoopsie.108.crash
-rw-r-  1 root whoopsie99379 Oct 22 15:07 _usr_sbin_inetd.0.crash
$ 

Because (as far as I know) the various `.crash' files MAY contain sensitive 
information,
I have not attached them to this (public) bug report.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: whoopsie 0.2.62ubuntu0.2
ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
Date: Wed Oct 30 09:28:01 2019
InstallationDate: Installed on 2016-10-07 (1118 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: Upgraded to bionic on 2018-08-18 (438 days ago)

** Affects: whoopsie (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug autoreport-false bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1850608

Title:
  Segfaults trying to send crash report

Status in whoopsie package in Ubuntu:
  New

Bug description:
  After this morning's upgrade to "whoopsie 0.2.62ubuntu0.2"
  plus "libwhoopsie0 0.2.62ubuntu0.2"(fix to bug #1830865),
  whoopsie repeatedly crashes with a segfault (in what seems to be libc?).
  An excerpt from /var/log/syslog (slightly redacted):

  Oct 30 08:33:06 [REDACTED] systemd[1]: Started crash report submission daemon.
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Using lock path: 
/var/lock/whoopsie/lock
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] The default IPv4 route 
is: /org/freedesktop/NetworkManager/ActiveConnection/1
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Not a paid data plan:

[Touch-packages] [Bug 1822269] Re: mktemp does not handle -p option when --tmpdir option goes after -p option

2019-04-11 Thread Brian Foster

This is not a bug, it is expected & reasonable behaviour.
The `-p DIR' and `--tmpdir[=DIR]' mktemp(1) options
are the same, excepting that the  argument is
mandatory for -p and optional for --tmpdir.  (See
the manpage (`man mktemp') or try `mktemp --help'.)
That is, the following are equivalent:

   mktemp -u -p /   --tmpdir
   mktemp -u -p/--tmpdir
   mktemp -u --tmpdir=/ --tmpdir
   mktemp -u -p /   -p "${TMPDIR:-/tmp}"

All print "FOO/tmp." where  is the
value of TMPDIR (/tmp if not set (the usual case)).
Clearly, the LAST (right→most) -p or --tmpdir option
is being used, with all the preceding ones ignored.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1822269

Title:
  mktemp does not handle  -p option when --tmpdir option goes after -p
  option

Status in coreutils package in Ubuntu:
  New

Bug description:
  #  This is correct.  The printed temp file name is in folder /
  $ mktemp -u --tmpdir -p /
  /tmp.aFd4MwfGDU

  # after swapping the options, mktemp do not handle the -p option correctly.
  # swapping options should not affect the output.
  $ mktemp -u -p / --tmpdir
  /tmp/tmp.FkTPrEsTMs

  This should be a software bug, not relevant to any hardware.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

2016-06-09 Thread Brian Foster

Same result for 4.4.10
On Jun 9, 2016 3:56 PM, "Levente Ábrók"  wrote:

> Some news.
> I updated the kernel to 4.4.13. Now I don't have error messages is dmesg.
> Added radeon.dpm=1 radeon.modeset=1 to /etc/default/grub file (not sure if
> everything is needed).
> sudo update-grub and reboot
> Although I still cannot switch between the cards with DDIS, but I can run
> specific programs with the dedicated AMD, using DRI_PRIME=1
> programpathname. That is already quite good, because I don't need the
> dedicated for browsing the web or so.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1581270
>
> Title:
>   Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
>   resume
>
> Status in xorg package in Ubuntu:
>   Confirmed
>
> Bug description:
>   dmesg shows issues with being able to use the discrete graphics card
>   (relevant dmesg lines attached).
>
>   Grub does pass "radeon.modeset=1" but it doesn't seem to make a
>   difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
>   the kernel, then it does not error (except for the VCE error -110,
>   which is probably harmless).
>
>   Running `DRI_PRIME=1 glxgears`:
>   - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a
> black window with a visible top bar.
>   - with just "radeon.modeset=1", error (attached as 'glxgears').
>
>   Results are similar on Ubuntu GNOME 16.04, except with
>   "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
>   screen tearing.
>
>   Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
>   attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:
>
>   [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
>   [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
>   [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
>   [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
>   [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
>   [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
>   [   23.092276] [drm] UVD initialized successfully.
>   [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
>   [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
>   [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
>   [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
>   [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
>   [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence
> wait failed (-35).
>   [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon:
> failed testing IB on ring 5 (-35).
>
>   lsb_release -rd:
>   Description:  Ubuntu 16.04 LTS
>   Release:  16.04
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Thu May 12 20:43:03 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics
> Controller [144d:c0e6]
>  Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD
> 8670A/8670M/8750M] [144d:c0e6]
>   InstallationDate: Installed on 2016-05-13 (0 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed
> root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash
> radeon.modeset=1 vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/21/2014
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P05ADH.017.140421.SH
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: NP680Z5E-X01US
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: SEC_SW_REVISION_1234567890ABCD
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: N/A
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:
>

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

2016-05-12 Thread Brian Foster

# /etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=1 radeon.drm=1 
radeon.runpm=0"
...

Result of `DRI_PRIME=1 glxgears -info` attached. Visible and smooth
animation runs (no black window).

** Attachment added: "glxgears-2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661667/+files/glxgears-2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581270

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  New

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

2016-05-12 Thread Brian Foster

** Description changed:

  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).
  
- Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
- I've tried all combinations and same results occur.
+ Grub does pass "radeon.modeset=1" but it doesn't seem to make a
+ difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
+ the kernel, then it does not error (except for the VCE error -110, which
+ is probably harmless).
+ 
+ Running `DRI_PRIME=1 glxgears`:
+ - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
+ - with just "radeon.modeset=1", error (attached as 'glxgears').
+ 
+ Results are similar on Ubuntu GNOME 16.04, except with
+ "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
+ screen tearing.
  
  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:
  
  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).
  
  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
-Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
+    Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

2016-05-12 Thread Brian Foster

** Attachment added: "glxgears"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661633/+files/glxgears

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581270

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  New

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the
  kernel. I've tried all combinations and same results occur.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
 Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu May 12 20:35:57 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log

[Touch-packages] [Bug 1581270] [NEW] Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

2016-05-12 Thread Brian Foster

Public bug reported:

dmesg shows issues with being able to use the discrete graphics card
(relevant dmesg lines attached).

Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
I've tried all combinations and same results occur.

Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

[   22.916285] [drm] ring test on 0 succeeded in 2 usecs
[   22.916289] [drm] ring test on 1 succeeded in 1 usecs
[   22.916292] [drm] ring test on 2 succeeded in 1 usecs
[   22.916299] [drm] ring test on 3 succeeded in 3 usecs
[   22.916304] [drm] ring test on 4 succeeded in 3 usecs
[   23.092271] [drm] ring test on 5 succeeded in 2 usecs
[   23.092276] [drm] UVD initialized successfully.
[   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
[   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
[   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
[   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
[   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
[   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
[   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

lsb_release -rd:
Description:Ubuntu 16.04 LTS
Release:16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May 12 20:43:03 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
   Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
InstallationDate: Installed on 2016-05-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P05ADH.017.140421.SH
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP680Z5E-X01US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 870Z5E/880Z5E/680Z5E
dmi.product.version: P05ADH
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu May 12 20:35:57 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4845 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Attachment added: "dmesg | grep drm"
   
https://bugs.launchpad.net/bugs/1581270/+attachment/4661608/+files/dmesg-grep-drm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581270

Title:
  Hybrid Graphics:

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

2016-05-12 Thread Brian Foster

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661631/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581270

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  New

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the
  kernel. I've tried all combinations and same results occur.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
 Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu May 12 20:35:57 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say so

[Touch-packages] [Bug 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec

[Touch-packages] [Bug 1902311] Re: GNU sha256sum(1) --check (-c) output depends on order of --quiet and --warn

[Touch-packages] [Bug 1902311] Re: GNU sha256(1) --check (-c) output depends on order of --quiet and --warn

[Touch-packages] [Bug 1902311] [NEW] GNU sha256(1) --check (-c) output depends on order of --quiet and --warn

[Touch-packages] [Bug 1850608] [NEW] Segfaults trying to send crash report

[Touch-packages] [Bug 1822269] Re: mktemp does not handle -p option when --tmpdir option goes after -p option

Re: [Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

[Touch-packages] [Bug 1581270] [NEW] Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

13 matches

Site Navigation

Mail list logo

Footer information