Bug#1032774: linux-image-6.1.0-6-amd64: S3 suspend on Gigabyte B660 GAMING X DDR4 motherboard crashes
Package: linux-image-6.1.0-6-amd64 Severity: normal When I suspend on my Gigabyte B660 GAMING X DDR4 motherboard, the following can be observed: root@xxx:~# echo -n "mem" > /sys/power/state [ 56.895232] PM: suspend entry (deep) [ 56.906889] Filesystems sync: 0.008 seconds [ 57.112498] (NULL device *): firmware: direct-loading firmware i915/dg2_dmc_ver2_07.bin [ 57.112634] (NULL device *): firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin [ 57.112648] (NULL device *): firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin [ 57.112753] (NULL device *): firmware: direct-loading firmware i915/dg2_guc_70.bin [ 57.147342] Freezing user space processes [ 57.152920] Freezing user space processes completed (elapsed 0.001 seconds) [ 57.160054] OOM killer disabled. [ 57.163312] Freezing remaining freezable tasks [ 57.169022] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 57.788864] r8169 :06:00.0 eth0: Link is Down [ 57.980226] ACPI: PM: Preparing to enter system sleep state S3 [ 57.994907] ACPI: PM: Saving platform NVS memory [ 57.17] Disabling non-boot CPUs ... [ 58.006843] smpboot: CPU 1 is now offline [ 58.012789] smpboot: CPU 2 is now offline [ 58.018614] smpboot: CPU 3 is now offline [ 58.024417] smpboot: CPU 4 is now offline [ 58.030298] smpboot: CPU 5 is now offline [ 58.036142] smpboot: CPU 6 is now offline [ 58.042138] smpboot: CPU 7 is now offline [ 58.049025] smpboot: CPU 8 is now offline [ 58.054802] smpboot: CPU 9 is now offline [ 58.060547] smpboot: CPU 10 is now offline [ 58.066398] smpboot: CPU 11 is now offline [ 58.072397] smpboot: CPU 12 is now offline [ 58.078247] smpboot: CPU 13 is now offline [ 58.084137] smpboot: CPU 14 is now offline [ 58.090204] smpboot: CPU 15 is now offline [ 58.095982] smpboot: CPU 16 is now offline [ 58.101833] smpboot: CPU 17 is now offline [ 58.107586] smpboot: CPU 18 is now offline [ 58.113414] smpboot: CPU 19 is now offline X64 Exception Type - 0E(#PF - Page-Fault) CPU Apic ID - ExceptionData - 0002 I:0 R:0 U:0 W:1 P:0 PK:0 SS:0 SGX:0 RIP - 3FA6760E, CS - 0038, RFLAGS - 00010007 RAX - 0091E204, RCX - FF00, RDX - 0091E000 RBX - 3FA7D018, RSP - 3FCADB50, RBP - 3FCADB90 RSI - 3FB031C0, RDI - 3FA65E20 R8 - , R9 - 3FCADBE8, R10 - 0001 R11 - 3FCADC30, R12 - 3FA7D020, R13 - 3FA7D020 R14 - 0001, R15 - 0001 DS - 0020, ES - 0020, FS - 0020 GS - 0020, SS - 0020 CR0 - 80010033, CR2 - 0091E204, CR3 - 3FC8 CR4 - 0668, CR8 - 0001 DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FC7F000 004F, LDTR - IDTR - 3FC8B000 01FF, TR - 0040 FXSAVE_STATE - 3FC8CC60 I'm quite sure the problem is either in the upstream kernel or the vendor BIOS, however Gigabyte claims they have no reports of this behaviour on this board with Windows. I probably need some guidance to pinpoint the problem and properly report it to kernel maintainer, if it's not the BIOS (or a Debian kernel patch). -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#1028463: linux: enable MEI options for Intel ARC
Source: linux Severity: wishlist Tags: sid In order to fully use Intel ARC GPUs, the following options need to get enabled: CONFIG_INTEL_MEI_GSC CONFIG_INTEL_MEI_PXP CONFIG_DRM_I915_PXP
Bug#892138: gem2deb: doesn't support SHA256/SHA512 checksums
Package: gem2deb Version: 0.33.1 Severity: important Commit e0b4c12c in the gem2deb repo fixes this and it should be included into a new gem2deb version for stretch, as some gems started to use only SHA256+ and thus fail to get packaged on stretch. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gem2deb depends on: ii debhelper11~bpo9+1 ii devscripts 2.17.12~bpo9+1 ii gem2deb-test-runner 0.33.1 ii perl 5.24.1-3+deb9u2 ii rake 10.5.0-2 ii ruby 1:2.3.3 ii ruby-all-dev 1:2.3.3 ii ruby-setup 3.4.1-9 Versions of packages gem2deb recommends: pn apt-file ii build-essential 12.3 ii python3-debian 0.1.30 gem2deb suggests no packages. -- no debconf information
Bug#880382: ITP: ruby-rsec -- Parser / Regexp Combinator For Ruby
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#872417: ITP: ruby-net-ssh-krb -- Kerberos authentication for ruby-net-ssh
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#845045: Gem.datadir does not return proper debianized value
Package: ruby2.3
Version: 2.3.1-6
irb(main):001:0> gem 'unicode-display_width'
=> true
irb(main):002:0> Gem.datadir('unicode-display_width')
=>
"/usr/share/rubygems-integration/all/gems/unicode-display_width-1.1.1/data/unicode-display_width"
This should be /usr/share/ruby-unicode-display-width or similar.
Bug#844723: ITP: ruby-unicode-display-width -- Unicode character width library
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#827867: puppet-agent package is not really necessary and conflicts with the upstream package by the same name
What's the status of this bug? A quick fix would be to rename the puppet-agent package to puppet-client or similar. As the stretch release is nearing and PuppetLabs is pushing users to move to their Puppet 4 packages, something should be done. ;)
Bug#827920: ITP: ruby-logify -- leightweight Ruby logging library
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#823537: ITP: ruby-algebrick -- Ruby library for algebraic type definition and pattern matching
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#804633: npm: Please update npm to v3.x.x, at least for sid.
I second this. Ubuntu has 3.5.2-0ubuntu4 currently, I guess there's a lot of stuff that can be easily imported.
Bug#782325: status update?
anybody, pretty please? :)
Bug#814046: ITP: ruby-cat -- create Ruby objects in a sandbox
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras -- Michael Moll
Bug#794159: FTBFS: Error: my.methods.ai(:plain => true).should_not raise_error(ArgumentError)
I think this was already fixed with 1.6.1-1, could anybody chek?
Bug#796119: ITP: ruby-table-print -- Ruby library to turn objects into formatted columns
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#795785: ITP: ruby-chef-api -- Chef API client with minimal dependencies
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#795612: ITP: ruby-powerbar -- progressbar library for Ruby
Package: wnpp Severity: wishlist I'm packaging this in pkg-ruby-extras
Bug#795481: RFP: ruby-logging -- flexible Ruby logging library
Package: ruby-logging Version: 2.0.0 Severity: wishlist
Bug#795332: RFP: ruby-logify -- lightweight logging library for Ruby
Package: ruby-logify Version: 0.2.0 Severity: wishlist -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#774643: [Pkg-puppet-devel] Bug#774643: fix introduces problems for Foreman
#x27; /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/application.rb:103:in `require_environment!' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/application.rb:305:in `block (2 levels) in initialize_tasks' Tasks: TOP => db:migrate => environment (See full trace by running task with --trace) I didn't do further research and it might also have to do with our packages using vendored gems, however after removing the said package, it worked. > You could add a Conflicts: ruby-activerecord-deprecated-finders, which > would still allow puppet from Debian proper to be installed (since > ruby-ar-d-f is only a Recommends). Indeed that's working as expected, at leats when the package with the added Conflicts line is also repo. For a first (failed) tests, I only did edit the local dpkg database, so that's an accepable solution. > > It should also be noted that (AFAIK) storeconfig was deprecated in > > Puppet 3 and it's use strongly discouraged. > > This has been previously discussed. In short, it's no pretty situation, > but we either have to support this, or break the upgrade path for many > setups and ask that people install activerecord 3 from rubygems.org on > their systems. If we can do the former without causing too much trouble, > IMHO we should do it. Now that I'm seeing that wheezy only brought Puppet 2.7 I understand the decision. Thanks for the reply :) -- Michael Moll -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774643: fix introduces problems for Foreman
Hello, while I've been packaging Foreman (http://theforeman.org/) for Debian/jessie I encountered problems when having ruby-activerecord-deprecated-finders installed. At the end I had to add a Conflicts line, so at the moment Foreman would only work with Puppetlabs packages if installed on the same host as the Puppet master. It should also be noted that (AFAIK) storeconfig was deprecated in Puppet 3 and it's use strongly discouraged. I do see the point that PuppetDB is not yet packaged as debian.org package, but Recommending a decreated package is introducing also some problems. This should IMHO be shifted to a Suggests (and from the Foreman POV I'd like to see that in the first jessie release as Foreman would have to depend on Puppetlabs packages otherwise). Best Regards -- Michael Moll -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706163: debian-installer: non-lvm+lvm setup with expert_recipe doesn't work with wheezy
Package: debian-installer Severity: important Tags: d-i Hi, I'm using Foreman as provisioning server and having a template which I'm using for unattended installations of Debian and Ubuntu. It works for Debian 6.0 and Ubuntu 12.04. Today I tried it with Debian 7.0 and I'm getting: Unexpected error while creating volume group Autopartitioning using LVM failed because an error occurred while creating the volume group. The pxelinux and preseed files can be found here: http://space.kvedulv.de/d-i/ The debug logs of the installation process can be found there in the "logs" subdirectory. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
