Processed: Re: Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
Processing control commands:
> tag -1 moreinfo
Bug #866122 [src:linux] test060-mt-hot failing on ppc64el buildd
Bug #866371 [src:linux] openldap FTBFS on ppc64{,el}: slapd-mtread failed (139)
Added tag(s) moreinfo.
Added tag(s) moreinfo.
--
866122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866122
866371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
Control: tag -1 moreinfo On Fri, 4 Aug 2017 16:14:24 -0500 "Barry Arndt" wrote: > On Thu, 27 Jul 2017 10:20:12 -0300 Breno Leitao > wrote: > > Although lack of recent updates, we are still working on this problem. > > > > Barry (on CC) is allocated to work on this issue and should have updates > soon. > > > > > > > > The offending line of code that Breno mentioned earlier was part of a > larger patch. Looking at that larger patch, I'm afraid that just removing > the offending line of code would make that patch incomplete and could > possibly leave other errors behind. > > We have a few patches for other issues in this area of code. I tested a > couple of them, but they did not resolve this issue. I'm working with > another developer (who is currently working on other items related to this > one) to gather more debug information to narrow down to the correct fix. Is this bug still present? I can see a fix to VSX handling in the kernel that went into mainline just after this, and then into 4.9.45: commit 5a69aec945d27e78abac9fd032533d3aaebf7c1e Author: Benjamin Herrenschmidt Date: Wed Aug 16 16:01:14 2017 +1000 powerpc: Fix VSX enabling/flushing to also test MSR_FP and MSR_VEC Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
Processed: severity of 883935 is important
Processing commands for cont...@bugs.debian.org: > severity 883935 important Bug #883935 [src:linux] linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring) Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 883935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 898060 is important
Processing commands for cont...@bugs.debian.org: > severity 898060 important Bug #898060 [src:linux] Stall NFS clients: RPC request reserved 84 but used 272 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 898060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878274: linux-image-4.9.0-3-powerpc64le: Kernel hangs
Control: tag -1 mreinfo
On Wed, 11 Oct 2017 17:33:58 -0600 Nate R wrote:
> Package: src:linux
> Version: 4.9.30-2+deb9u5
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> Dear Maintainer,
>
>* What led up to the situation?
> Production server. Was doing a large uncompress of a file.
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> Trigger for bug is unclear.
>* What was the outcome of this action?
> Had to reboot the node. All commands hung.
>* What outcome did you expect instead?
> Not to hang.
[...]
I'm sorry we didn't respond to this earlier.
Have you seen a similar hang again? If so, which version are you
running now ("uname -v" will show this)? Can you send a fresh log,
including all the BUG and WARN messages?
> ** Tainted: O (4096)
> * Out-of-tree module has been loaded.
>
> ** Kernel log:
> [2335559.671011] WARNING: CPU: 0 PID: 0 at
> /build/linux-ZRFL9M/linux-4.9.30/net/sched/sch_generic.c:316
> dev_watchdog+0x380/0x390
[...]
Based on this warning message, I suspect this may be a bug in the
Mellanox network drivers you were using, which are not part of this
package. But the network hang might be a symptom of an earlier
failure.
Are you able to use the in-tree drivers for this hardware?
Ben.
--
Ben Hutchings
Q. Which is the greater problem in the world today,
ignorance or apathy?
A. I don't know and I couldn't care less.
signature.asc
Description: This is a digitally signed message part
Processed: severity of 878274 is important
Processing commands for cont...@bugs.debian.org: > severity 878274 important Bug #878274 [src:linux] linux-image-4.9.0-3-powerpc64le: Kernel hangs Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 878274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 889076 is important
Processing commands for cont...@bugs.debian.org: > severity 889076 important Bug #889076 [src:linux] linux-image-4.9.0-5-rt-amd64: at boot computer starts beeping and image in screen becomes corrupted. Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 889076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 889288 is important
Processing commands for cont...@bugs.debian.org: > severity 889288 important Bug #889288 [src:linux] linux-image-4.9.0-5-amd64: Fails to boot on Apple MacMini4,1 Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 889288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883294: linux-image-4.13.0-1-amd64: Kernel panic prevents boot: regression (apic)
I'm sending these questions to you since Romain mistakenly sent them only to the bug: On Thu, 26 Apr 2018 08:54:26 +0200 Romain Perier wrote: > Hello, > > Could you : > > - Retry with linux-image 4.15, that is the current kernel in buster/sid (but now 4.16 is current) > - Instead of not using IO-APIC completly, could you try to boot with > kernel parameter "no_timer_check" ? > > Does it help ? -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
Processed: severity of 883294 is important, tagging 883294
Processing commands for cont...@bugs.debian.org: > severity 883294 important Bug #883294 [src:linux] linux-image-4.13.0-1-amd64: Kernel panic prevents boot: regression (apic) Severity set to 'important' from 'critical' > tags 883294 + moreinfo Bug #883294 [src:linux] linux-image-4.13.0-1-amd64: Kernel panic prevents boot: regression (apic) Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 883294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902740: marked as done (initramfs-tools: /etc/initramfs-tools/conf.d/resume not updated with dpkg-reconfigure initramfs-tools)
Your message dated Sun, 01 Jul 2018 02:49:24 +0100 with message-id <2a6243b29893810dd094d2bcf415f22041a3251f.ca...@decadent.org.uk> and subject line Re: Bug#902740: initramfs-tools: /etc/initramfs-tools/conf.d/resume not updated with dpkg-reconfigure initramfs-tools has caused the Debian Bug report #902740, regarding initramfs-tools: /etc/initramfs-tools/conf.d/resume not updated with dpkg-reconfigure initramfs-tools to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 902740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.130 Severity: wishlist I copied a drive from one laptop to another, using rsync and various hacks. The swap partition on the new drive has a different UUID. I had to regenerate initramfs for each kernel version, because the lappies are different type hardware, with different modules needed. When I ran update-initramfs it worked perfectly, except that it threw an informational message that it couldn't find the resume partition listed in the conf file, so it would use the swap partition it did find. I ran dpkg-reconfigure initramfs-tools to update the configs with the new swap partition UUID, but the message kept appearing. So, rather than have it keep throwing the informational message forever, I copied and pasted the UUID of swap into /etc/initramfs-tools/conf.d/resume. It works now without the message. It would be nice if the message gave the path of the config file in question, or better yet, if dpkg-reconfigure initramfs-tools would update the 'resume' config file with the new swap partition. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 18M Feb 27 00:37 /boot/initrd.img-4.9.0-4-amd64 -rw-r--r-- 1 root root 18M May 17 21:08 /boot/initrd.img-4.9.0-6-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.9.0-6-amd64 root=UUID=a28a1d13-49b8-4f25-b310-d1d17e69cec9 ro quiet -- resume RESUME=UUID=31fe945f-b629-425b-91dd-e08260816714 -- /proc/filesystems ext3 ext2 ext4 xfs fuseblk vfat -- lsmod Module Size Used by tun28672 0 nls_ascii 16384 0 nls_cp437 20480 0 vfat 20480 0 fat69632 1 vfat fuse 98304 3 ftdi_sio 53248 0 usbserial 49152 1 ftdi_sio pci_stub 16384 1 vboxpci24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 466944 3 vboxnetadp,vboxnetflt,vboxpci xfs 1224704 2 libcrc32c 16384 1 xfs usblp 20480 0 uas24576 0 usb_storage73728 3 uas hid_generic16384 0 usbhid 53248 0 hid 122880 2 hid_generic,usbhid intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 asus_nb_wmi28672 0 asus_wmi 28672 1 asus_nb_wmi sparse_keymap 16384 1 asus_wmi rfkill 24576 3 asus_wmi kvm_intel 192512 0 kvm 593920 1 kvm_intel snd_hda_codec_hdmi 49152 1 iTCO_wdt 16384 0 irqbypass 16384 1 kvm iTCO_vendor_support16384 1 iTCO_wdt crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 snd_hda_codec_realtek90112 1 ghash_clmulni_intel16384 0 snd_hda_codec_generic69632 1 snd_hda_codec_realtek nouveau 1556480 1 i915 1257472 17 intel_cstate 16384 0 snd_hda_intel 36864 6 mxm_wmi16384 1 nouveau intel_uncore 118784 0 snd_hda_codec 135168 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek ttm98304 1 nouveau evdev 24576 19 joydev 20480 0 intel_rapl_perf16384 0 snd_hda_core 86016 5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek drm_kms_helper155648 2 nouveau,i915 serio_raw 16384 0 pcspkr 16384 0 snd_hwdep 16384 1 snd_hda_codec mei_me 36864 0 snd_pcm 110592 4 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi drm 360448 12 nouveau,i915,ttm,drm_kms_helper snd_timer 32768 1 snd_pcm mei 102400 1 mei_me sg
Bug#769135: marked as done (linux-image-3.2.0-4-amd64: Backport of fix for JMicron USB->SATA bridges)
Your message dated Sun, 01 Jul 2018 02:21:48 +0100
with message-id <4e839e007f3c944c8d006d8103a1eb76f4e4b44b.ca...@decadent.org.uk>
and subject line Re: linux-image-3.2.0-4-amd64: Backport of fix for JMicron
USB->SATA bridges
has caused the Debian Bug report #769135,
regarding linux-image-3.2.0-4-amd64: Backport of fix for JMicron USB->SATA
bridges
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
769135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.2.0-4-amd64
Version: 3.2.0
Severity: normal
Tags: patch
Please apply a backport of the JMicron USB->SATA quirk fix to 3.2.0 (wheezy).
Without this fix certain JMicron USB->SATA bridges are not usable in Debian
Wheezy.
The fix already is upstream (git b14bf2d0c0358140041d1c1805a674376964d0e0)
and in Debian's 3.16.0 kernel (Sid/Jessie).
A proposed backport of the fix is attached to this report.
Index: linux-3.2.60/drivers/scsi/sd.c
===
--- linux-3.2.60.orig/drivers/scsi/sd.c 2014-06-09 14:29:18.0 +0200
+++ linux-3.2.60/drivers/scsi/sd.c 2014-08-29 20:25:58.0 +0200
@@ -2149,7 +2149,10 @@
}
sdkp->DPOFUA = (data.device_specific & 0x10) != 0;
- if (sdkp->DPOFUA && !sdkp->device->use_10_for_rw) {
+ if (sdp->broken_fua) {
+ sd_printk(KERN_NOTICE, sdkp, "Disabling FUA\n");
+ sdkp->DPOFUA = 0;
+ } else if (sdkp->DPOFUA && !sdkp->device->use_10_for_rw) {
sd_printk(KERN_NOTICE, sdkp,
"Uses READ/WRITE(6), disabling FUA\n");
sdkp->DPOFUA = 0;
Index: linux-3.2.60/drivers/usb/storage/scsiglue.c
===
--- linux-3.2.60.orig/drivers/usb/storage/scsiglue.c 2014-06-09 14:29:18.0 +0200
+++ linux-3.2.60/drivers/usb/storage/scsiglue.c 2014-08-29 20:33:40.0 +0200
@@ -255,6 +255,10 @@
US_FL_SCM_MULT_TARG)) &&
us->protocol == USB_PR_BULK)
us->use_last_sector_hacks = 1;
+
+ /* A few buggy USB-ATA bridges don't understand FUA */
+ if (us->fflags & US_FL_BROKEN_FUA)
+ sdev->broken_fua = 1;
} else {
/* Non-disk-type devices don't need to blacklist any pages
Index: linux-3.2.60/drivers/usb/storage/unusual_devs.h
===
--- linux-3.2.60.orig/drivers/usb/storage/unusual_devs.h 2014-06-09 14:29:18.0 +0200
+++ linux-3.2.60/drivers/usb/storage/unusual_devs.h 2014-08-29 20:25:58.0 +0200
@@ -1916,6 +1916,13 @@
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_IGNORE_RESIDUE ),
+/* Reported by Michael Büsch */
+UNUSUAL_DEV( 0x152d, 0x0567, 0x0114, 0x0114,
+ "JMicron",
+ "USB to ATA/ATAPI Bridge",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_BROKEN_FUA ),
+
/* Reported by Alexandre Oliva
* JMicron responds to USN and several other SCSI ioctls with a
* residue that causes subsequent I/O requests to fail. */
Index: linux-3.2.60/include/linux/usb_usual.h
===
--- linux-3.2.60.orig/include/linux/usb_usual.h 2014-06-09 14:29:18.0 +0200
+++ linux-3.2.60/include/linux/usb_usual.h 2014-08-29 20:28:18.0 +0200
@@ -64,7 +64,9 @@
US_FLAG(NO_READ_CAPACITY_16, 0x0008) \
/* cannot handle READ_CAPACITY_16 */ \
US_FLAG(INITIAL_READ10, 0x0010) \
- /* Initial READ(10) (and others) must be retried */
+ /* Initial READ(10) (and others) must be retried */ \
+ US_FLAG(BROKEN_FUA, 0x0100) \
+ /* Cannot handle FUA in WRITE or READ CDBs */ \
#define US_FLAG(name, value) US_FL_##name = value ,
enum { US_DO_ALL_FLAGS };
Index: linux-3.2.60/include/scsi/scsi_device.h
===
--- linux-3.2.60.orig/include/scsi/scsi_device.h 2014-06-09 14:29:18.0 +0200
+++ linux-3.2.60/include/scsi/scsi_device.h 2014-08-29 20:32:53.0 +0200
@@ -151,6 +151,7 @@
unsigned no_read_disc_info:1; /* Avoid READ_DISC_INFO cmds */
unsigned no_read_capacity_16:1; /* Avoid READ_CAPACITY_16 cmds */
unsigned is_visible:1; /* is the device visible in sysfs */
+ unsigned broken_fua:1; /* Don't set FUA bit */
DECLARE_BITMAP(supported_events, SDEV_EVT_MAXBITS); /* supported events */
struct list_head event_list; /* asserted events */
--- End Message ---
--- Begin Message ---
Version: 3.2.63-1
This was included in stable update 3.2.62 and in the above Debian
version.
Ben.
--
Ben Hutchings
Q. Which is the greater problem in the world today,
ignorance or apathy?
Bug#842687: marked as done (linux-image-4.7.0-1-amd64: Unable to re-build kernal package (PIC mode problem))
Your message dated Sun, 01 Jul 2018 02:17:51 +0100 with message-id and subject line Re: linux-image-4.7.0-1-amd64: Unable to re-build kernal package (PIC mode problem) has caused the Debian Bug report #842687, regarding linux-image-4.7.0-1-amd64: Unable to re-build kernal package (PIC mode problem) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 842687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.7.8-1 Severity: minor Dear Maintainer, I tried to rebuild the Kernel package with others options for my CPUs (NO_HZ options) because i use Qemu for PCI-Passthrough. 1- Download the kernel source with "apt-get source linux-source-4.7" 2- Paste my new .config in the Kernel source folder 3- Launch the packaging by "make deb-pkg LOCALVERSION=-qemu KDEB_PKGVERSION=$(make kernelversion)-1" Quickly, i have this error message : "kernel/bounds.c:1:0: error: code model kernel does not support PIC mode" I tried to compile the Kernel with gcc 5 and gcc 6 and i have still this problem. Thanks for your help because i don't understand where come from the problem. Maxime -- Package-specific info: ** Version: Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.8-1 (2016-10-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 root=UUID=d27ba2f8-3744-40c4-809c-fd59b367fc24 ro quiet ** Tainted: POE (12289) * Proprietary module has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [3.993993] sd 3:0:0:0: Attached scsi generic sg1 type 0 [4.007741] intel-lpss :00:15.1: enabling device ( -> 0002) [4.007919] idma64 idma64.1: Found Intel integrated DMA 64-bit [4.023740] intel-lpss :00:1e.0: enabling device ( -> 0002) [4.023893] idma64 idma64.2: Found Intel integrated DMA 64-bit [4.024053] dw-apb-uart.2: ttyS2 at MMIO 0xdf22b000 (irq = 20, base_baud = 115200) is a 16550A [4.035912] input: PC Speaker as /devices/platform/pcspkr/input/input10 [4.036954] Bluetooth: Core ver 2.21 [4.036963] NET: Registered protocol family 31 [4.036964] Bluetooth: HCI device and connection manager initialized [4.036966] Bluetooth: HCI socket layer initialized [4.036968] Bluetooth: L2CAP socket layer initialized [4.036974] Bluetooth: SCO socket layer initialized [4.038781] EFI Variables Facility v0.08 2004-May-17 [4.039937] mei_me :00:16.0: enabling device ( -> 0002) [4.043953] Bluetooth: HCI UART driver ver 2.3 [4.043954] Bluetooth: HCI UART protocol H4 registered [4.043955] Bluetooth: HCI UART protocol BCSP registered [4.043955] Bluetooth: HCI UART protocol LL registered [4.043956] Bluetooth: HCI UART protocol ATH3K registered [4.043956] Bluetooth: HCI UART protocol Three-wire (H5) registered [4.043970] Bluetooth: HCI UART protocol Intel registered [4.043977] Bluetooth: HCI UART protocol BCM registered [4.043977] Bluetooth: HCI UART protocol QCA registered [4.045946] pstore: Registered efi as persistent store backend [4.053752] i801_smbus :00:1f.4: SMBus using PCI interrupt [4.056807] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.056917] snd_hda_intel :01:00.1: Disabling MSI [4.056922] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [4.056936] snd_hda_intel :02:00.1: enabling device ( -> 0002) [4.056964] snd_hda_intel :02:00.1: Disabling MSI [4.056967] snd_hda_intel :02:00.1: Handle vga_switcheroo audio client [4.083837] ppdev: user-space parallel port driver [4.089472] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [4.089474] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.089475] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [4.089476] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.089477] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.089478] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [4.089478] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [4.089479] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a [4.097837] iTCO_vendor_support: vendor-support=0 [4.098045] Adding 3906556k swap on /dev/sda3. Priority:-1 extents:1 across:3906556k SSFS [4.098558] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Bug#697266: marked as done (linux-image-3.2.0-4-amd64: Please backport support for HDMI audio on recent RADEON graphics cards.)
Your message dated Sun, 01 Jul 2018 02:19:56 +0100 with message-id and subject line Re: linux-image-3.2.0-4-amd64: Please backport support for HDMI audio on recent RADEON graphics cards. has caused the Debian Bug report #697266, regarding linux-image-3.2.0-4-amd64: Please backport support for HDMI audio on recent RADEON graphics cards. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.35-2 Severity: wishlist Dear Maintainer, Please backport support for HDMI audio on recent RADEON graphics cards, specifically the Sapphire RADEON HD 7770. The support was added to the kernel as of commit a1585d769731323a792277f15b7a3ee2ae36b698 , (I believe this is in kernel 3.3.) This commit and a previous one from AMD add new PCI IDs related to the HDMI audio on the card, adds a new AZX_DRIVER type and removes the limitation on the number of PCMs. I have generated a patch (attached) from the kernel linux-stable git using git diff v3.2.25 a1585d769731323a792277f15b7a3ee2ae36b698 sound/pci/hda/ The patch has been trimmed of superfluous changes and applies without problem to the Debian kernel. However, I make no claims of the patch being perfect. The HDMI audio has been tested with my TV and works without issue so far. The only thing I'm not sure of is that it generates six entries as shown in the output below. aplay -l List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC889A Analog [ALC889A Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: ALC889A Digital [ALC889A Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 The relevant syslog from the device starting is: Jan 3 00:09:23 tori kernel: [7.085952] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0 Jan 3 00:09:23 tori kernel: [7.086073] HDMI status: Codec=0 Pin=5 Presence_Detect=0 ELD_Valid=0 Jan 3 00:09:23 tori kernel: [7.086191] HDMI status: Codec=0 Pin=7 Presence_Detect=0 ELD_Valid=0 Jan 3 00:09:23 tori kernel: [7.086310] HDMI status: Codec=0 Pin=9 Presence_Detect=0 ELD_Valid=0 Jan 3 00:09:23 tori kernel: [7.086433] HDMI status: Codec=0 Pin=11 Presence_Detect=0 ELD_Valid=0 Jan 3 00:09:23 tori kernel: [7.086561] HDMI status: Codec=0 Pin=13 Presence_Detect=0 ELD_Valid=0 Jan 3 00:09:23 tori kernel: [7.086888] input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input9 Jan 3 00:09:23 tori kernel: [7.087201] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input10 Jan 3 00:09:23 tori kernel: [7.087930] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input11 Jan 3 00:09:23 tori kernel: [7.089761] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input12 Jan 3 00:09:23 tori kernel: [7.090325] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input13 Jan 3 00:09:23 tori kernel: [7.091989] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input14 The PCI information for the card with the patch installed and run as root is: lspci -vvv -nn -s 1: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Cape Verde [Radeon HD 7700 Series] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device [174b:e215] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
Bug#703673: marked as done (Request to backport acpi changes to Debian sid for proper acpi child device handling)
Your message dated Sun, 01 Jul 2018 02:20:29 +0100 with message-id and subject line Re: Request to backport acpi changes to Debian sid for proper acpi child device handling has caused the Debian Bug report #703673, regarding Request to backport acpi changes to Debian sid for proper acpi child device handling to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 703673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 Severity: important There is a upstream linux kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=42696 which prevents the Lenovo Y580/Y470/Y570 and Toshiba Satellite P870 devices unable to find the Nvidia card through proper acpi device handling. It has been discussed in detail in this thread as well at bumblebee git page too. https://github.com/Bumblebee-Project/bbswitch/issues/2 It has been fixed since Linux kernel 3.9 rc2 through this patch https://bugzilla.kernel.org/attachment.cgi?id=89731. The bug applies to wheezy as well and backporting the new kernel changes would fix the proper acpi handling. I hereby request the kernel maintainers to backport these changes to Debian wheezy. Thank you, Dr. Piruthiviraj Natarajan --- End Message --- --- Begin Message --- Closing as support for Debian 7 "wheezy" has ended. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#889129: marked as done (.config:3186:warning: symbol value 'm' invalid for HW_RANDOM_TPM)
Your message dated Sun, 01 Jul 2018 02:13:17 +0100 with message-id <17efad20d497d73ddcddb7c3b0bc30f62148d1ad.ca...@decadent.org.uk> and subject line Re: .config:3186:warning: symbol value 'm' invalid for HW_RANDOM_TPM has caused the Debian Bug report #889129, regarding .config:3186:warning: symbol value 'm' invalid for HW_RANDOM_TPM to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 889129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.14.13-1 Severity: minor User: debian-powe...@lists.debian.org Usertags: powerpc At least on my G4 Mac Mini, I can see: $ cp /boot/config-4.14.0-3-powerpc .config $ make savedefconfig scripts/kconfig/conf --savedefconfig=defconfig Kconfig .config:3186:warning: symbol value 'm' invalid for HW_RANDOM_TPM I have not check if this module value is valid for other system. Reference: commit 0c8eb822de35e14c404803bbd40bd48a81bedc1e Author: Ben Hutchings Date: Fri May 31 04:14:16 2013 + Enable various new drivers and driver options svn path=/dists/sid/linux/; revision=20152 --- End Message --- --- Begin Message --- Version: 4.16~rc5-1~exp1 Fixed in the above version. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#762148: marked as done (Fix intel_pstate kernel panic in wheezy, already done upstream)
Your message dated Sun, 01 Jul 2018 02:08:59 +0100 with message-id <72304fa0a7a151e6f477a33bb6a5e172199bc8fa.ca...@decadent.org.uk> and subject line Re: Bug#762148: Fix intel_pstate kernel panic in wheezy, already done upstream has caused the Debian Bug report #762148, regarding Fix intel_pstate kernel panic in wheezy, already done upstream to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-3.2.0-4-amd64 Version: 3.2.60-1+deb7u3 Severity: normal Tags: patch Hi kernel folks, The intel_pstate driver in wheezy fails to calculate its timer timeout correctly, which can cause the driver to race with itself. Google's kernel engineers identified this as the cause for an occasional kernel panic which our test infrastructure picked up. The fix is one-line and was accepted upstream in April of last year. Could you please apply the one-line fix to the next wheezy stable update? While we've only encountered this infrequently, this is the kind of patch that can only help things. kernel.org git commit ID: ec376a2ab97ec3be52ca282dc6ac102e805d1005 Link to the diff in kernel.org: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/cpufreq/intel_pstate.c?id=ec376a2ab97ec3be52ca282dc6ac102e805d1005 Thanks! - Jimmy --- End Message --- --- Begin Message --- On Wed, 24 Sep 2014 13:15:16 +0100 Ben Hutchings wrote: > Control: tag -1 - patch > Control: tag -1 moreinfo > > On Thu, 2014-09-18 at 16:18 -0700, Jimmy Kaplowitz wrote: > > Package: linux-image-3.2.0-4-amd64 > > Version: 3.2.60-1+deb7u3 > > Severity: normal > > Tags: patch > > > > > > Hi kernel folks, > > > > > > The intel_pstate driver in wheezy > [...] > > No such thing in 3.2, and we didn't backport it either. Is there a > similar bug elsewhere? Even if there was, Debian 7 "wheezy" support has ended, so closing this. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#852715: marked as done (linux: building with CONFIG_DEBUG_INFO strips embedded modules signatures)
Your message dated Sun, 01 Jul 2018 02:02:44 +0100 with message-id <12d146c5d46c834df8a150ce87b196e98d8f169a.ca...@decadent.org.uk> and subject line Re: linux: building with CONFIG_DEBUG_INFO strips embedded modules signatures has caused the Debian Bug report #852715, regarding linux: building with CONFIG_DEBUG_INFO strips embedded modules signatures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 852715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.9.2-2 Severity: normal Tags: patch Dear maintainer, If building with CONFIG_MODULE_SIG_ALL and CONFIG_DEBUG_INFO the objcopy call that adds the debuglink has the side-effect of removing the signature added to the kernel module, which breaks booting if the option to enforce module signatures is also enabled. The fix is to explicitly sign the installed modules again in that case. A small patch from my colleague Jan Blunck is attached. Thank you! Kind regards, Luca Boccassi From 9e6f694354d25f47b4bcb6656d3eb05fc3351a13 Mon Sep 17 00:00:00 2001 From: Jan Blunck Date: Thu, 26 Jan 2017 17:04:11 +0100 Subject: [PATCH] Fix stripped module signatures if CONFIG_DEBUG_INFO If building with CONFIG_MODULE_SIG_ALL and CONFIG_DEBUG_INFO the objcopy call that adds the debuglink has the side-effect of removing the signature added to the kernel module. Let's explicitly sign the installed modules again in that case. --- debian/rules.real | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules.real b/debian/rules.real index 868efa3..b818c35 100644 --- a/debian/rules.real +++ b/debian/rules.real @@ -417,6 +417,9 @@ ifeq ($(DEBUG),True) find $(PACKAGE_DIR) -name '*.ko' | sed 's|$(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)/kernel/||' | while read module ; do \ $(CROSS_COMPILE)objcopy --add-gnu-debuglink=$(DIR)/$$module $(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)/kernel/$$module || exit; \ done + +if grep -qs '^CONFIG_MODULE_SIG_ALL=y' $(DIR)/.config; then \ + $(MAKE_CLEAN) -C $(DIR) modules_sign INSTALL_MOD_PATH='$(CURDIR)'/$(PACKAGE_DIR); \ + fi endif cp $(DIR)/.config $(PACKAGE_DIR)/boot/config-$(REAL_VERSION) cp $(DIR)/System.map $(PACKAGE_DIR)/boot/System.map-$(REAL_VERSION) -- 2.1.4 signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 4.17~rc3-1~exp1 An updated version of this patch was included in the above version. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#844122: marked as done (linux: allow disabling linux-source-$ver build via config)
Your message dated Sun, 01 Jul 2018 02:00:17 +0100
with message-id <6298345ed35e51d81e7c4ab9b7cf3fd91d9a08b1.ca...@decadent.org.uk>
and subject line Re: linux: allow disabling linux-source-$ver build via config
has caused the Debian Bug report #844122,
regarding linux: allow disabling linux-source-$ver build via config
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
844122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: wishlist
Tags: patch
Dear Maintainers,
Building linux-source-X.Y takes about ~10 minutes, and in the context
of a continuous integration build where the result is tested and then
discarded it is only a waste of time.
It would be nice if it where possible to add [packages] source: false to
disable it like for linux-docs, linux-tools etc.
Patch to implement this behaviour is attached. Default is still to build
linux-
source-$version.
Thank you!
Kind regards,
Luca Boccassi
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable'), (104, 'testing'), (103, 'unstable'), (102, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
From 683726c35af4bf289a05b2caa1aa27d4d362e983 Mon Sep 17 00:00:00 2001
From: Luca Boccassi
Date: Thu, 29 Sep 2016 17:49:06 +0100
Subject: [PATCH] Allow to disable source package build via define
Building linux-source-X.Y takes about ~10 minutes, and in the context
of a continous integration build where the result is tested and then
discarded it is only a waste of time.
Allow to add [packages] source: false to disable it like for
linux-docs, linux-tools etc.
---
debian/bin/gencontrol.py | 5 +
debian/rules.real| 2 ++
debian/templates/control.linux-source.in | 15 +++
debian/templates/control.main.in | 15 ---
4 files changed, 22 insertions(+), 15 deletions(-)
create mode 100644 debian/templates/control.linux-source.in
diff --git a/debian/bin/gencontrol.py b/debian/bin/gencontrol.py
index 76a1790..9aee13f 100755
--- a/debian/bin/gencontrol.py
+++ b/debian/bin/gencontrol.py
@@ -48,6 +48,7 @@ class Gencontrol(Base):
'installer': config.SchemaItemBoolean(),
'libc-dev': config.SchemaItemBoolean(),
'tools': config.SchemaItemBoolean(),
+'source': config.SchemaItemBoolean(),
}
}
@@ -109,6 +110,8 @@ class Gencontrol(Base):
makeflags['DO_DOCS'] = False
if not self.config.merge('packages').get('tools', True):
makeflags['DO_TOOLS'] = False
+if not self.config.merge('packages').get('source', True):
+makeflags['DO_SOURCE'] = False
super(Gencontrol, self).do_main_makefile(makefile, makeflags, extra)
# linux-source-$UPSTREAMVERSION will contain all kconfig files
@@ -120,6 +123,8 @@ class Gencontrol(Base):
packages.extend(self.process_packages(self.templates["control.docs"],
self.vars))
if self.config.merge('packages').get('tools', True):
packages.extend(self.process_packages(self.templates["control.tools"],
self.vars))
+if self.config.merge('packages').get('source', True):
+
packages.extend(self.process_packages(self.templates["control.linux-source"],
self.vars))
self._substitute_file('lintian-overrides.perf', self.vars,
'debian/linux-perf-%s.lintian-overrides' %
diff --git a/debian/rules.real b/debian/rules.real
index 96411e4..7b83921 100644
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -70,7 +70,9 @@ ifneq ($(DO_DOCS),False)
binary-indep: install-manual
build-indep: $(STAMPS_DIR)/build-doc
endif
+ifneq ($(DO_SOURCE),False)
binary-indep: install-source
+endif
binary-indep: install-support
ifneq ($(DO_TOOLS),False)
diff --git a/debian/templates/control.linux-source.in
b/debian/templates/control.linux-source.in
new file mode 100644
index 000..7ed709d
--- /dev/null
+++ b/debian/templates/control.linux-source.in
@@ -0,0 +1,15 @@
+Package: @source_package@-source-@version@
+Build-Profiles:
+Architecture: all
+Section: kernel
+Depends: binutils, xz-utils, ${misc:Depends}
+Recommends: libc6-dev | libc-dev, gcc, make, bc
+Suggests:
Bug#670321: marked as done (linux-image-3.2.0-1-amd64: Support for new NFS id mapper)
Your message dated Sun, 01 Jul 2018 01:52:41 +0100 with message-id and subject line Re: linux-image-3.2.0-1-amd64: Support for new NFS id mapper has caused the Debian Bug report #670321, regarding linux-image-3.2.0-1-amd64: Support for new NFS id mapper to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 670321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.2.1-1 Severity: wishlist Hi, Please consider enabling the new NFS ID mapper functionality in the kernel: CONFIG_NFS_USE_NEW_IDMAPPER This will also need support in nfs-utils. Enabling this feature should prevent page allocation failure errors we frequently get on our file servers, as mentioned on https://bugzilla.redhat.com/show_bug.cgi?id=593035 Fedora also appears to be enabling this feature, and if things work out even RHEL 6.3+ might switch to this. Regards, Rik -- Package-specific info: ** Version: Linux version 3.2.0-1-amd64 (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Thu Jan 19 09:46:46 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/vg_neptune-root ro quiet splash ** Not tainted ** Kernel log: [ 693.991811] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0xf0, writing 0x20f0) [ 693.991819] pcieport :00:1c.3: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [ 693.991825] pcieport :00:1c.3: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 693.991868] pcieport :00:1c.4: restoring config space at offset 0xf (was 0x100, writing 0x10010b) [ 693.991880] pcieport :00:1c.4: restoring config space at offset 0x7 (was 0xf0, writing 0x20f0) [ 693.991889] pcieport :00:1c.4: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [ 693.991895] pcieport :00:1c.4: restoring config space at offset 0x1 (was 0x16, writing 0x100407) [ 693.991938] pcieport :00:1c.7: restoring config space at offset 0xf (was 0x400, writing 0x10040a) [ 693.991955] pcieport :00:1c.7: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [ 693.991961] pcieport :00:1c.7: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 693.992002] ehci_hcd :00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x105) [ 693.992018] ehci_hcd :00:1d.0: restoring config space at offset 0x4 (was 0x0, writing 0xf7f07000) [ 693.992025] ehci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x290, writing 0x292) [ 693.994564] ehci_hcd :00:1d.0: wake-up capability disabled by ACPI [ 693.994570] ehci_hcd :00:1d.0: PME# disabled [ 693.994632] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [ 693.994707] r8169 :05:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x105) [ 693.994724] r8169 :05:00.0: restoring config space at offset 0x8 (was 0xc, writing 0xf11c) [ 693.994732] r8169 :05:00.0: restoring config space at offset 0x6 (was 0xc, writing 0xf110400c) [ 693.994740] r8169 :05:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xe001) [ 693.994747] r8169 :05:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [ 693.994755] r8169 :05:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 693.994944] iwlwifi :09:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 693.994983] iwlwifi :09:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf7e4) [ 693.994992] iwlwifi :09:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [ 693.995004] iwlwifi :09:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x16) [ 693.995108] xhci_hcd :0b:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 693.995132] xhci_hcd :0b:00.0: restoring config space at offset 0x4 (was 0xf794, writing 0xf7d4) [ 693.995138] xhci_hcd :0b:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [ 693.995146] xhci_hcd :0b:00.0: restoring config space at offset 0x1 (was 0x16, writing 0x100402) [ 693.995186] pcieport :00:1c.4: wake-up capability disabled by ACPI [ 693.995192] xhci_hcd :0b:00.0: PME# disabled [ 693.995240] PM: early resume of devices complete after 6.756 msecs [ 693.995337] i915 :00:02.0: setting
Processed: tagging 603957
Processing commands for cont...@bugs.debian.org: > tags 603957 + wontfix Bug #603957 [src:linux] linux-2.6: consider raising CONFIG_HZ to 1000 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 603957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#600204: marked as done (linux boot should prompt the user when it finds an incompatible resume image)
Your message dated Sun, 01 Jul 2018 01:53:59 +0100 with message-id and subject line Re: linux-image-2.6.32-5-amd64: Squeeze ignores Lennys hibernate image has caused the Debian Bug report #600204, regarding linux boot should prompt the user when it finds an incompatible resume image to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 600204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-23 Severity: critical Justification: causes serious data loss I hibernated in Lenny, using the same kernel version. The next day I accidentally selected Squeeze from the grub2 menu. Squeeze started up normally and reported on filesystems not cleanly closed and orphaned inodes. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-23) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-3) ) #1 SMP Fri Sep 17 21:50:19 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64.squeeze root=/dev/mapper/VgCompaq-squeeze resume=/dev/VgCompaq/swap ro quiet splash vga=0x317 cryptopts=target=sda4_crypt,source=UUID=41d45178-c0d4-4d8f-a190-1c56b6328318,key=none,rootdev,lvm=VgCompaq-squeeze ** Not tainted ** Kernel log: [ 10.672142] ACPI: AC Adapter [AC] (on-line) [ 10.672512] ACPI: WMI: Mapper loaded [ 10.727880] udev: renamed network interface eth0 to eth1 [ 10.756239] input: PC Speaker as /devices/platform/pcspkr/input/input6 [ 10.847978] i801_smbus :00:1f.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [ 11.237050] [drm] Initialized drm 1.1.0 20060810 [ 11.315582] cfg80211: Using static regulatory domain info [ 11.315585] cfg80211: Regulatory domain: US [ 11.315588] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 11.315591] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [ 11.315595] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.315601] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.315601] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.315604] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.315607] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 11.315618] cfg80211: Calling CRDA for country: US [ 11.387778] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input7 [ 11.423406] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input8 [ 11.546159] i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 11.546165] i915 :00:02.0: setting latency timer to 64 [ 11.561342] alloc irq_desc for 26 on node -1 [ 11.561347] alloc kstat_irqs on node -1 [ 11.561358] i915 :00:02.0: irq 26 for MSI/MSI-X [ 11.561367] [drm] set up 7M of stolen space [ 11.659728] Linux video capture interface: v2.00 [ 11.686036] [drm] initialized overlay support [ 11.754445] ath5k :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 11.754469] ath5k :01:00.0: setting latency timer to 64 [ 11.754544] ath5k :01:00.0: registered as 'phy0' [ 11.948683] uvcvideo: Found UVC 1.00 device CNF7041 (04f2:b057) [ 11.952488] input: CNF7041 as /devices/pci:00/:00:1d.7/usb1/1-6/1-6:1.0/input/input9 [ 11.952586] usbcore: registered new interface driver uvcvideo [ 11.952794] USB Video Class driver (v0.1.0) [ 12.254885] ath: EEPROM regdomain: 0x67 [ 12.254888] ath: EEPROM indicates we should expect a direct regpair map [ 12.254893] ath: Country alpha2 being used: 00 [ 12.254895] ath: Regpair used: 0x67 [ 12.364329] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver [ 12.364401] Console: switching to colour dummy device 80x25 [ 12.364878] Console: switching to colour frame buffer device 180x56 [ 12.374279] phy0: Selected rate control algorithm 'minstrel' [ 12.375014] Registered led device: ath5k-phy0::rx [ 12.375033] Registered led device: ath5k-phy0::tx [ 12.375036] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [ 12.488180] fb0: inteldrmfb frame buffer device [ 12.488183] registered panic notifier [ 12.489089] [Firmware Bug]: ACPI: ACPI brightness control misses _BQC function [ 12.500533] acpi device:15: registered as cooling_device2 [ 12.501050] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 [ 12.501121] ACPI: Video Device [OVGA] (multi-head: yes rom: no post: no) [ 12.501165] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
Bug#704420: marked as done ("intel_idle: does not run on family 6 model 54" on Intel Atom N2600 CPU)
Your message dated Sun, 01 Jul 2018 01:46:47 +0100 with message-id <2570315ef97aab7bcba255eb0fe4474ba5a5f240.ca...@decadent.org.uk> and subject line Re: 'Fixed' in recent kernel versions has caused the Debian Bug report #704420, regarding "intel_idle: does not run on family 6 model 54" on Intel Atom N2600 CPU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.41-2 Severity: normal Dear Maintainer, the Linux kernel reports that the intel_idle module doesn't support the Intel Atom N2600: intel_idle: does not run on family 6 model 54 # dmesg |grep -i atom CPU0: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz stepping 01 This probably prevents putting the processing into a deeper C-state resulting in higher power consumption. Best regards Stephan -- Package-specific info: ** Version: Linux version 3.2.0-4-rt-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP PREEMPT RT Debian 3.2.41-2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-rt-686-pae root=/dev/mapper/vg00-lv_root ro quiet elevator=noop ** Not tainted ** Kernel log: [3.263572] ata5.00: configured for UDMA/133 [3.364131] ata2: SATA link down (SStatus 0 SControl 300) [3.364588] scsi 4:0:0:0: Direct-Access ATA INTEL SSDSC2CW06 400i PQ: 0 ANSI: 5 [3.684143] ata6: SATA link down (SStatus 0 SControl 300) [3.712430] sd 4:0:0:0: [sda] 117231408 512-byte logical blocks: (60.0 GB/55.8 GiB) [3.712767] sd 4:0:0:0: [sda] Write Protect is off [3.712776] sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3.712881] sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.715002] sda: sda1 [3.716158] sd 4:0:0:0: [sda] Attached SCSI disk [3.722230] sd 4:0:0:0: Attached scsi generic sg0 type 0 [4.067436] microcode: CPU0 sig=0x30661, pf=0x8, revision=0x10d [4.076234] platform microcode: firmware: agent aborted loading intel-ucode/06-36-01 (not found?) [4.076471] microcode: CPU1 sig=0x30661, pf=0x8, revision=0x10d [4.083960] platform microcode: firmware: agent aborted loading intel-ucode/06-36-01 (not found?) [4.084331] microcode: CPU2 sig=0x30661, pf=0x8, revision=0x10d [4.093453] platform microcode: firmware: agent aborted loading intel-ucode/06-36-01 (not found?) [4.093721] microcode: CPU3 sig=0x30661, pf=0x8, revision=0x10d [4.102394] platform microcode: firmware: agent aborted loading intel-ucode/06-36-01 (not found?) [4.102874] microcode: Microcode Update Driver: v2.00 , Peter Oruba [4.123124] device-mapper: uevent: version 1.0.3 [4.123415] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-de...@redhat.com [4.418976] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [4.998414] udevd[412]: starting version 175 [5.168398] ACPI: Requesting acpi_cpufreq [5.170962] Monitor-Mwait will be used to enter C-1 state [5.175292] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 [5.175324] ACPI: Power Button [PWRB] [5.191911] iTCO_vendor_support: vendor-support=0 [5.197342] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 [5.197362] ACPI: Sleep Button [SLPB] [5.204601] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [5.211800] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [5.211818] ACPI: Power Button [PWRF] [5.215974] iTCO_wdt: Found a NM10 TCO device (Version=2, TCOBASE=0x0460) [5.219009] input: PC Speaker as /devices/platform/pcspkr/input/input3 [5.220770] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [5.235475] [drm] Initialized drm 1.1.0 20060810 [5.272461] Error: Driver 'pcspkr' is already registered, aborting... [5.278887] gma500 :00:02.0: setting latency timer to 64 [5.279000] gma500 :00:02.0: irq 47 for MSI/MSI-X [5.280190] Stolen memory information [5.280211]base in RAM: 0x7f80 [5.280224]size: 7932K, calculated by (GTT RAM base) - (Stolen base), seems wrong [5.280236] the correct size should be: 8M(dvmt mode=3) [5.290580] Set up 1983 stolen pages starting at 0x7f80, GTT offset 0K [5.290918] [drm] SGX core id = 0x [5.290931] [drm] SGX core rev major = 0x00, minor = 0x00 [5.290943] [drm] SGX core rev maintenance = 0x00, designer = 0x00
Processed: forcibly merging 703280 732315
Processing commands for cont...@bugs.debian.org: > forcemerge 703280 732315 Bug #703280 [src:linux] linux: please include extract-vmlinux script in some binary package Bug #732315 [src:linux] src:linux: Please include extract-vmlinux somewhere Marked as found in versions linux-tools/3.8.2-1~experimental.1. Merged 703280 732315 > thanks Stopping processing here. Please contact me if you need assistance. -- 703280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703280 732315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 680194
Processing commands for cont...@bugs.debian.org: > tags 680194 + wontfix Bug #680194 [src:linux] rename Kernel-Packages to allow a less missleading uname -r output Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 680194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#704223: marked as done (linux-source-3.8: Please add support for m68k and cross-compiling)
Your message dated Sun, 01 Jul 2018 01:48:28 +0100 with message-id <6958dc5af13290e83ed56604a7c270d9af490ecc.ca...@decadent.org.uk> and subject line Re: linux-source-3.8: Please add support for m68k and cross-compiling has caused the Debian Bug report #704223, regarding linux-source-3.8: Please add support for m68k and cross-compiling to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-source-3.8 Version: 3.8.3-1~experimental.1 Severity: normal Dear Maintainer, the builddeb script does not support m68k nor cross-compiling. The following patch fixes this, the second part comes from this report: https://patchwork.kernel.org/patch/752622/ Please apply, if this is the correct way to add support. thanks, Christian --- scripts/package/builddeb.orig 2013-03-14 19:27:14.0 +0100 +++ scripts/package/builddeb2013-03-29 19:34:05.311940456 +0100 @@ -28,7 +28,7 @@ # Attempt to find the correct Debian architecture local forcearch="" debarch="" case "$UTS_MACHINE" in - i386|ia64|alpha) + i386|ia64|alpha|m68k) debarch="$UTS_MACHINE" ;; x86_64) debarch=amd64 ;; @@ -254,6 +254,12 @@ rm -f "$objtree/debian/hdrsrcfiles" "$objtree/debian/hdrobjfiles" arch=$(dpkg --print-architecture) +if [ -n "$KBUILD_DEBARCH" ] ; then + arch="$KBUILD_DEBARCH" +else + arch=$(dpkg --print-architecture) +fi + cat <> debian/control Package: $kernel_headers_packagename -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (200, 'experimental'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.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 Versions of packages linux-source-3.8 depends on: ii binutils 2.22-8 ii bzip2 1.0.6-4 Versions of packages linux-source-3.8 recommends: ii gcc 4:4.7.2-1 ii libc6-dev [libc-dev] 2.13-38 ii make 3.82-1 Versions of packages linux-source-3.8 suggests: ii libncurses5-dev [ncurses-dev] 5.9-10 ii libqt4-dev 4:4.8.2+dfsg-11 ii pkg-config 0.26-1 -- no debconf information --- End Message --- --- Begin Message --- Closing as this is an upstream feature request and has not been pursued upstream. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#754855: marked as done (linux-image-3.14-1-amd64: backport PowerEdge VRTX driver from 3.15 to 3.14 kernel)
Your message dated Sun, 01 Jul 2018 01:40:14 +0100 with message-id <33000220aea95f10ae8d526d8b8153a66af659e2.ca...@decadent.org.uk> and subject line Re: linux-image-3.14-1-amd64: backport PowerEdge VRTX driver from 3.15 to 3.14 kernel has caused the Debian Bug report #754855, regarding linux-image-3.14-1-amd64: backport PowerEdge VRTX driver from 3.15 to 3.14 kernel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 754855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.14.12-1 Severity: wishlist Hi, If the 3.14 kernel will be the kernel for Jessie, please consider backporting support for the Dell PowerEdge VRTX storage. Support for this was first introduced with the 3.15 kernel in the following commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=229fe47cd046ef2d01c13298293cda9693811417 This driver allows Linux on the VRTX blades to access the shared storage in the enclosure. Regards, Rik --- End Message --- --- Begin Message --- Version: 3.15~rc5-1~exp1 On Tue, 15 Jul 2014 10:11:12 +0200 Rik Theys wrote: > Package: src:linux > Version: 3.14.12-1 > Severity: wishlist > > Hi, > > If the 3.14 kernel will be the kernel for Jessie, please consider > backporting support for the Dell PowerEdge VRTX storage. [...] Closing since it wasn't. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#709625: marked as done (protected_hardlinks is too broad - make it per-filesystem instead?)
Your message dated Sun, 01 Jul 2018 01:42:58 +0100 with message-id and subject line Re: protected_hardlinks is too broad - make it per-filesystem instead? has caused the Debian Bug report #709625, regarding protected_hardlinks is too broad - make it per-filesystem instead? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 709625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.41-2 Severity: normal Hi, I think that the new security feature to restrict hardlinks is a great idea, but it is also causing me problems. In debian-cd, we rely on the ability to make hardlinked copies of files from a debian mirror into temporary disk trees. Since upgrading pettersson (the CD build box), this broke due to the default protected_hardlinks setting. On that system: * we have a push mirror setup using the "archvsync" user; * we build CDs using as the "debian-cd" user These two user accounts explicitly don't share credentials: archvsync can be triggered remotely so we don't trust it to be directly involved in the CD build process. The debian-cd user explicitly does not have write access to the mirror area on the machine, so as to ensure we can't/don't make any changes to the mirror when building CDs. For now, on that system we have changed the default settings via /proc but it's not a real solution for us and DSA don't want to do it permanently. I can see a few ways that we could change things: * run things using the same account (not wanted, as described above) * share a group between the users and make everything group-writable (ditto) * come up with a fakelink ld_preload lib like we have fakeroot (eww) Alternatively, I'm pondering: if the main thrust of the hardlink protection is to prevent attacks against system files, then it might make more sense to change protected_hardlinks to be a per-filesystem mount option. By all means protect the root filesystem etc., but for a purely data-carrying filesystem it's a bit obstructive. What do you think? -- Steve McIntyre, Cambridge, UK.st...@einval.com Google-bait: http://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you. --- End Message --- --- Begin Message --- Closing this since it's an upstream feature request and apparently hasn't been pursused upstream. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: tagging 742619
Processing commands for cont...@bugs.debian.org: > tags 742619 + wontfix Bug #742619 [linux] linux: Please reenable CONFIG_SCSI_PROC_FS Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 742619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#764574: marked as done (please backport commit a28a9178e8 from v3.8)
Your message dated Sun, 01 Jul 2018 01:33:56 +0100
with message-id
and subject line Re: please backport commit a28a9178e8 from v3.8
has caused the Debian Bug report #764574,
regarding please backport commit a28a9178e8 from v3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
764574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.2.63-2
Severity: wishlist
I'm using Apache TrafficServer on wheezy, and I get the following in
dmesg once per day:
[28050.283707] EXT4-fs (dm-0): Unaligned AIO/DIO on inode 7734855 by [ET_NET
4]; performance will be poor.
[50104.515999] EXT4-fs (dm-0): Unaligned AIO/DIO on inode 7734855 by [ET_NET
5]; performance will be poor.
[79848.128273] EXT4-fs (dm-0): Unaligned AIO/DIO on inode 7734855 by [ET_NET
0]; performance will be poor.
This warning isn't very useful, and it looks like it was removed from
the kernel in v3.8 by commit a28a9178e8, it would be great if you could
apply a similar change to the Debian sources (the upstream patch doesn't
cherry-pick cleanly on top of v3.2.63).
commit a28a9178e8fcd9b94f7333184ce78e816c8cb2af
Author: Eric Sandeen
Date: Tue Dec 25 13:33:13 2012 -0500
ext4: remove unaligned AIO warning printk
Although I put this in, I now think it was a bad decision. For most
users, there is very little to be done in this case. They get the
message, once per day, with no real context or proposed action. TBH,
it generates support calls when it probably does not need to; the
message sounds more dire than the situation really is.
Just nuke it. Normal investigation via blktrace or whatnot can
reveal poor IO patterns if bad performance is encountered.
Signed-off-by: Eric Sandeen
Signed-off-by: "Theodore Ts'o"
diff --git a/fs/ext4/file.c b/fs/ext4/file.c
index b64a60b..1c0aad7 100644
--- a/fs/ext4/file.c
+++ b/fs/ext4/file.c
@@ -108,14 +108,6 @@ ext4_file_dio_write(struct kiocb *iocb, const struct iovec
*iov,
/* Unaligned direct AIO must be serialized; see comment above */
if (unaligned_aio) {
- static unsigned long unaligned_warn_time;
-
- /* Warn about this once per day */
- if (printk_timed_ratelimit(_warn_time, 60*60*24*HZ))
- ext4_msg(inode->i_sb, KERN_WARNING,
-"Unaligned AIO/DIO on inode %ld by %s; "
-"performance will be poor.",
-inode->i_ino, current->comm);
mutex_lock(ext4_aio_mutex(inode));
ext4_unwritten_wait(inode);
}
Thanks,
--
Romain Francoise
http://people.debian.org/~rfrancoise/
--- End Message ---
--- Begin Message ---
Closing since support for Debian 7 "wheezy" has ended.
Ben.
--
Ben Hutchings
Q. Which is the greater problem in the world today,
ignorance or apathy?
A. I don't know and I couldn't care less.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
Bug#757998: marked as done (linux-2.6: backport from /dev/random enhancements to wheezy?)
Your message dated Sun, 01 Jul 2018 01:34:40 +0100 with message-id <67a06d414f51837ad10fb3cb01761500077f771c.ca...@decadent.org.uk> and subject line Re: linux-2.6: backport from /dev/random enhancements to wheezy? has caused the Debian Bug report #757998, regarding linux-2.6: backport from /dev/random enhancements to wheezy? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 757998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux02.6 Severity: wishlist hi kernel maintainers, if possible please backport the /dev/random enhancements from 3.13 to our beloved wheezy kernel. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0891ad829d2a0501053703df66029e843e3b8365 thanks, bernd -- Mit freundlichen Grüßen Bernd Zeimetz Systems Engineer Debian Developer conova communications GmbH Web| http://www.conova.com/ E-Mail | b.zeim...@conova.com Zentrale Salzburg Karolingerstraße 36A 5020 Salzburg Tel | +43 (0) 662 22 00 - 313 Fax | +43 (0) 662 22 00 - 209 Es gelten die Allgemeinen Geschäftsbedingungen der conova communications GmbH, http://www.conova.com/de/agb/ smime.p7s Description: S/MIME cryptographic signature --- End Message --- --- Begin Message --- Closing since support for Debian 7 "wheezy" has ended. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#706476: marked as done ([x86] GPIOs not exposed to userland)
Your message dated Sun, 01 Jul 2018 01:37:43 +0100 with message-id and subject line Re: [x86] GPIOs not exposed to userland has caused the Debian Bug report #706476, regarding [x86] GPIOs not exposed to userland to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-3.2.0-4-486 Severity: important discovered from another debian bugreport that pc-engines systems can be upgraded to more recent firmware and work with linux-image-3.2.0-4-486 (which is great!) and also discovered that the geodewdt kernel module has been compiled, which is also great (as it's missing from the 2.6.32 debian kernel builds) however what's not so great is that the GPIO 5535 kernel driver has been left out, and it is a requirement for the project. as native builds on 500mhz AMD Geodes take absolutely forever it would be nice if this could be corrected. kernel option is GPIO_CS5535 -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Version: 4.3.3-6 On Thu, 2 May 2013 17:01:18 +0100 Luke Kenneth Casson Leighton wrote: > ok, it turns out that CONFIG_SYSFS_GPIO is "safe", because you have to > explicitly take action in order to make GPIO accessible (export). > following the instructions here was easy to do: > https://sites.google.com/site/bifferboard/Home/gpio > > so, basically, CONFIG_SYSFS_GPIO could be switched on (as built-in). This was enabled in the above version. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#724833: marked as done (linux-image-3.2.0-4-amd64: Support for Intel wireless 7000/3000 series in Debian 7.3?)
Your message dated Sun, 01 Jul 2018 01:35:39 +0100 with message-id <93b33051317016436db907109d4c41572a0e8887.ca...@decadent.org.uk> and subject line Re: linux-image-3.2.0-4-amd64: Support for Intel wireless 7000/3000 series in Debian 7.3? has caused the Debian Bug report #724833, regarding linux-image-3.2.0-4-amd64: Support for Intel wireless 7000/3000 series in Debian 7.3? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.46-1+deb7u1 Severity: wishlist Hi, I'd like to know if it'd be doable to backport the following patch in Linux 3.2 in order to add support for the last Intel wireless series. commit 99cd471423991fe9ba011e8948cdea95f5432338 iwlwifi: add 7000 series device configuration commit 93fc64114b994f9ef6901697f9b0de00762680e9 iwlwifi: add new 7260 and 3160 series device IDs (it also add device configuration) commit a2d0909a687b4d250cc2b7481072e361678745ba iwlwifi: bump required firmware API version for 3160/7260 (will need firmware-iwlwifi ⩾ 0.40) commit 3b1995ad83709ac2e1e86c99b37d5ba9ce410f56 iwlwifi: Kconfig: fix help texts wrt 7260 and 3160 devices (might be useful for people building from sources, but probably not suitable for a stable release ‽) If you accept my request for Debian 7.3 (or later), do you intend to use iwlwifi from the compat-drivers project? If so I can start to test how do they behave on Linux 3.2 right now. Have a good day, Vincent -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: UX31A product_version: 1.0 chassis_vendor: ASUSTeK COMPUTER INC. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: UX31A.219 board_vendor: ASUSTeK COMPUTER INC. board_name: UX31A board_version: 1.0 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A [1043:1517] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A [1043:1517] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 00:04.0 Signal processing controller [1180]: Intel Corporation 3rd Gen Core Processor Thermal Subsystem [8086:0153] (rev 09) Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A [1043:1517] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A [1043:1517] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A [1043:1517] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Zenbook Prime UX31A [1043:1517] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci-pci 00:1b.0 Audio device [0403]: Intel Corporation 7
Bug#756904: marked as done (linux: please enable CONFIG_DEBUG_STRICT_USER_COPY_CHECKS)
Your message dated Sun, 01 Jul 2018 01:30:12 +0100 with message-id <4de14475320ee4c52936a9c313e01d67ec135540.ca...@decadent.org.uk> and subject line Re: Bug#756904: linux: please enable CONFIG_DEBUG_STRICT_USER_COPY_CHECKS has caused the Debian Bug report #756904, regarding linux: please enable CONFIG_DEBUG_STRICT_USER_COPY_CHECKS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 756904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux Version: 3.14.13-2 Severity: wishlist Hi, the Linux kernel in Debian does currently not use this option: $ grep CONFIG_DEBUG_STRICT_USER_COPY_CHECKS /boot/config-3.14-* /boot/config-3.14-2-686-pae:# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set /boot/config-3.14-2-amd64:# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set It is only a compile time check, so it should not have any runtime impact. So could you please activate this option ? -- Laurent. --- End Message --- --- Begin Message --- Closing due to lack of response. Ben. On Sun, 03 Aug 2014 18:08:50 +0100 Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Sun, 2014-08-03 at 13:14 +0200, Laurent Bonnaud wrote: > > Package: linux > > Version: 3.14.13-2 > > Severity: wishlist > > > > > > Hi, > > > > the Linux kernel in Debian does currently not use this option: > > > > $ grep CONFIG_DEBUG_STRICT_USER_COPY_CHECKS /boot/config-3.14-* > > /boot/config-3.14-2-686-pae:# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is > > not set > > /boot/config-3.14-2-amd64:# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set > > > > It is only a compile time check, so it should not have any runtime > > impact. So could you please activate this option ? > > I seem to remember that this introduces spurious warnings. Has that > been fixed? > > Ben. > > -- > Ben Hutchings > Kids! Bringing about Armageddon can be dangerous. Do not attempt it in > your own home. - Terry Pratchett and Neil Gaiman, `Good Omens' -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: tagging 719547, retitle 719547 to linux: Provide a PREEMPT_RT kernel image for armhf
Processing commands for cont...@bugs.debian.org: > tags 719547 - moreinfo Bug #719547 [src:linux] linux: provide a PREEMPT_RT kernel image for non-x86 architectures Removed tag(s) moreinfo. > retitle 719547 linux: Provide a PREEMPT_RT kernel image for armhf Bug #719547 [src:linux] linux: provide a PREEMPT_RT kernel image for non-x86 architectures Changed Bug title to 'linux: Provide a PREEMPT_RT kernel image for armhf' from 'linux: provide a PREEMPT_RT kernel image for non-x86 architectures'. > thanks Stopping processing here. Please contact me if you need assistance. -- 719547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#695647: marked as done (linux-image-3.2.0-4-amd64: Set CONFIG_AUFS_HNOTIFY=y to use udba=notify on aufs.)
Your message dated Sun, 01 Jul 2018 01:29:12 +0100 with message-id and subject line Re: linux-image-3.2.0-4-amd64: Set CONFIG_AUFS_HNOTIFY=y to use udba=notify on aufs. has caused the Debian Bug report #695647, regarding linux-image-3.2.0-4-amd64: Set CONFIG_AUFS_HNOTIFY=y to use udba=notify on aufs. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 695647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.35-1 Severity: wishlist Dear Maintainer, Aufs has option udba=notify to find changes on low branch filesystem. But the linux kernel config does not allow it, with CONFIG_AUFS_HNOTIFY=n. Could you set CONFIG_AUFS_HNOTIFY=y? $ uname -a Linux casper 3.2.0-4-amd64 #1 SMP Debian 3.2.35-1 x86_64 GNU/Linux Regards, Kiwamu Okabe -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=b32ab783-6371-4754-97f6-2b20ea2018f1 ro quiet ** Tainted: CO (5120) * Module from drivers/staging has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [9.949120] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s [9.949125] iwl3945: Copyright(c) 2003-2011 Intel Corporation [9.949225] iwl3945 :03:00.0: setting latency timer to 64 [9.998084] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xd3fff 0xe-0xf [9.998139] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: excluding 0xa000-0xa0ff [9.998188] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff [ 10.004673] iwl3945 :03:00.0: Tunable channels: 13 802.11bg, 12 802.11a channels [ 10.004677] iwl3945 :03:00.0: Detected Intel Wireless WiFi Link 3945ABG [ 10.004834] iwl3945 :03:00.0: irq 44 for MSI/MSI-X [ 10.005065] Registered led device: phy0-led [ 10.083304] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs' [ 10.099877] i915 :00:02.0: power state changed by ACPI to D0 [ 10.099885] i915 :00:02.0: power state changed by ACPI to D0 [ 10.099897] i915 :00:02.0: setting latency timer to 64 [ 10.161800] mtrr: type mismatch for e000,1000 old: write-back new: write-combining [ 10.161805] [drm] MTRR allocation failed. Graphics performance may suffer. [ 10.162362] i915 :00:02.0: irq 45 for MSI/MSI-X [ 10.162371] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 10.162374] [drm] Driver supports precise vblank timestamp query. [ 10.162437] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 10.284736] Non-volatile memory driver v1.3 [ 10.397301] thinkpad_acpi: ThinkPad ACPI Extras v0.24 [ 10.397305] thinkpad_acpi: http://ibm-acpi.sf.net/ [ 10.397309] thinkpad_acpi: ThinkPad BIOS 7NETA7WW (2.07 ), EC 7MHT25WW-1.03 [ 10.397312] thinkpad_acpi: Lenovo ThinkPad X61s, model 7666BS7 [ 10.397822] thinkpad_acpi: detected a 8-level brightness capable ThinkPad [ 10.398188] thinkpad_acpi: radio switch found; radios are enabled [ 10.401839] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked [ 10.402389] Registered led device: tpacpi::thinklight [ 10.402443] Registered led device: tpacpi::power [ 10.402477] Registered led device: tpacpi::standby [ 10.402508] Registered led device: tpacpi::thinkvantage [ 10.405791] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one [ 10.406476] thinkpad_acpi: Console audio control enabled, mode: monitor (read only) [ 10.410246] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input6 [ 10.516430] [drm] initialized overlay support [ 10.528495] fbcon: inteldrmfb (fb0) is primary device [ 10.530466] [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync, -vsync) [ 10.711655] Console: switching to colour frame buffer device 128x48 [ 10.719023] fb0: inteldrmfb frame buffer device [ 10.719029] drm: registered panic notifier [ 10.738659] acpi device:02: registered as cooling_device2 [ 10.739355] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input7 [ 10.739485] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 10.741141] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor
Bug#847198: marked as done (src:linux: dmesg should be allowed to print the kernel ring buffer for admins)
Your message dated Sun, 01 Jul 2018 01:23:08 +0100 with message-id and subject line Re: src:linux: dmesg should be allowed to print the kernel ring buffer for admins has caused the Debian Bug report #847198, regarding src:linux: dmesg should be allowed to print the kernel ring buffer for admins to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 847198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Severity: wishlist In the past, admins could get dmesg output without running it as root, but this is no longer possible: * security,printk: Enable SECURITY_DMESG_RESTRICT, preventing non-root users reading the kernel log by default (sysctl: kernel.dmesg_restrict) (in changelog.linux.gz). It is good that normal users cannot read the kernel log, but for admins (typically users in the adm group, who can already read /var/log/kern.log, thus have access to the same information), this is a regression. Note: "journalctl -b" also gives kernel logs (among other logs). -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Since it is easy to change back to the old behaviour, this isn't a significant regression. Changing to a more sophisticated access policy could be done through LSMs, perhaps. But this is a feature request which would need to be pursued upstream. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: forcibly merging 689753 902544
Processing commands for cont...@bugs.debian.org: > forcemerge 689753 902544 Bug #689753 [src:linux] linux-image-3.5-trunk-amd64: Please support /boot being vfat, or another way of having the kernel on the EFI system partition Bug #902544 [src:linux] linux-image-4.16.0-2-amd64: Kernel installation fails when /boot is FAT partition Marked as found in versions linux/3.5.5-1~experimental.1. Added tag(s) wontfix. Bug #689753 [src:linux] linux-image-3.5-trunk-amd64: Please support /boot being vfat, or another way of having the kernel on the EFI system partition Marked as found in versions linux/4.16.12-1. Merged 689753 902544 > thanks Stopping processing here. Please contact me if you need assistance. -- 689753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689753 902544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878307: marked as done (usbip: enable use of unix-domain sockets, not just network traffic)
Your message dated Sun, 01 Jul 2018 01:19:36 +0100 with message-id and subject line Re: usbip: enable use of unix-domain sockets, not just network traffic has caused the Debian Bug report #878307, regarding usbip: enable use of unix-domain sockets, not just network traffic to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 878307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: usbip Severity: wishlist Some tools (like Gnuk) offer USB device emulation, exported to the host for testing via usbip. However, when using usbip in this way, any local user account with packet-sniffing privilege (e.g. members of group "wireshark" in a common debian convention) get access to the traffic over the USB port. It would be great to enable usbip-style device exposure over a SOCK_STREAM unix-domain socket as well as a TCP-based socket, since this would make it possible to provide emulated USB devices without routing traffic through the networking stack. --dkg --- End Message --- --- Begin Message --- This feature request should be pursued upstream. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#773540: marked as done (linux-image-3.2.0-4-686-pae: add option to restrict filenames with dangerous characters)
Your message dated Sun, 01 Jul 2018 01:18:37 +0100
with message-id
and subject line Re: linux-image-3.2.0-4-686-pae: add option to restrict
filenames with dangerous characters
has caused the Debian Bug report #773540,
regarding linux-image-3.2.0-4-686-pae: add option to restrict filenames with
dangerous characters
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
773540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.2.63-2+deb7u1
Severity: wishlist
Tags: l10n upstream
Dear Maintainer,
Today's discussion of the Git/Hg security issues led me to
http://www.dwheeler.com/essays/fixing-unix-linux-filenames.html . I'd like to
see
a mount option on Linux's standard filesystems (ext2/3/4, xfs, jfs, btrfs,
reiser)
to restrict what can be used as a new filename on a particular partition.
Possible
option name would be "checknames", or "restrict_names" ("check" would be similar
to a FAT driver option, but is already taken for a diffrent purpose on
ext2/3/4).
The argument would be a number combining different rules, for example...
0 - allow all characters anywhere (same as at present)
1 - disallow BEL, BS, CR, LF, VT , DC1..DC4 , SUB, ESC , DEL
anywhere in filename; or leading '-', or leading or trailing space or tab
2 - disallow any control character in filename, including encoded 0x80-0x9F
4 - disallow glob ... '*', '?', '[', ']'
8 - disallow pipe ... '<', '>', '"', '|'
16- disallow other OS's separators ... '\', ':'
32- disallow invalid UTF-8
64- disallow UTF-8 encoding unallocated code-points, surrogates, etc.
128-disallow UTF-8 encoding Unicode not in NFC
If a user called creat(2), link(2), or rename(2) with a filename violating one
of
these rules, the call would fail, probably with EINVAL.
The Debian installer should set a default of 99 for new filesystems (unless the
system is being initialized with a non-UTF-8 default locale, perhaps).
-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version
4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3
** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae root=/dev/mapper/vgScatha-lvRoot ro quiet
** Tainted: O (4096)
* Out-of-tree module has been loaded.
** Kernel log:
[6466582.648118] usb 3-2: new low-speed USB device number 107 using uhci_hcd
[6466582.826153] usb 3-2: New USB device found, idVendor=0c45, idProduct=7401
[6466582.826173] usb 3-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[6466582.826186] usb 3-2: Product: TEMPerV1.4
[6466582.826195] usb 3-2: Manufacturer: RDing
[6466582.846063] input: RDing TEMPerV1.4 as
/devices/pci:00/:00:14.2/usb3/3-2/3-2:1.0/input/input234
[6466582.847492] generic-usb 0003:0C45:7401.01CD: input,hidraw0: USB HID v1.10
Keyboard [RDing TEMPerV1.4] on usb-:00:14.2-2/input0
[6466582.864196] generic-usb 0003:0C45:7401.01CE: hiddev0,hidraw1: USB HID
v1.10 Device [RDing TEMPerV1.4] on usb-:00:14.2-2/input1
[6481223.240163] usb 3-2: USB disconnect, device number 107
[6481223.512123] usb 3-2: new low-speed USB device number 108 using uhci_hcd
[6481223.688720] usb 3-2: New USB device found, idVendor=0c45, idProduct=7401
[6481223.688741] usb 3-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[6481223.688754] usb 3-2: Product: TEMPerV1.4
[6481223.688763] usb 3-2: Manufacturer: RDing
[6481223.708612] input: RDing TEMPerV1.4 as
/devices/pci:00/:00:14.2/usb3/3-2/3-2:1.0/input/input235
[6481223.710068] generic-usb 0003:0C45:7401.01CF: input,hidraw0: USB HID v1.10
Keyboard [RDing TEMPerV1.4] on usb-:00:14.2-2/input0
[6481223.725756] generic-usb 0003:0C45:7401.01D0: hiddev0,hidraw1: USB HID
v1.10 Device [RDing TEMPerV1.4] on usb-:00:14.2-2/input1
[6497183.280189] usb 3-2: USB disconnect, device number 108
[6497183.520180] usb 3-2: new low-speed USB device number 109 using uhci_hcd
[6497183.695169] usb 3-2: New USB device found, idVendor=0c45, idProduct=7401
[6497183.695188] usb 3-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[6497183.695202] usb 3-2: Product: TEMPerV1.4
[6497183.695211] usb 3-2: Manufacturer: RDing
[6497183.715040] input: RDing TEMPerV1.4 as
/devices/pci:00/:00:14.2/usb3/3-2/3-2:1.0/input/input236
[6497183.717153] generic-usb 0003:0C45:7401.01D1: input,hidraw0: USB HID v1.10
Keyboard [RDing TEMPerV1.4] on usb-:00:14.2-2/input0
[6497183.737233] generic-usb 0003:0C45:7401.01D2: hiddev0,hidraw1: USB HID
v1.10 Device [RDing TEMPerV1.4] on
Bug#820167: marked as done (wishlist: Jessie kernel for ARM64 with UEFI bootROM)
Your message dated Sun, 01 Jul 2018 01:14:23 +0100 with message-id <1be12803cb4827a90bc204d7d1a27b72b1d9974f.ca...@decadent.org.uk> and subject line Re: syslinux-efi: Kernel does not boot on Gigabyte MP30-AR0 system (APM X-Gene 1) has caused the Debian Bug report #820167, regarding wishlist: Jessie kernel for ARM64 with UEFI bootROM to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 820167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: syslinux-efi Version: 8.4 Severity: grave Tags: d-i Justification: renders package unusable Description of problem: The Kernel does not boot after I select applicable option in the Debian Installer Grub boot menu. Version-Release number of selected component (if applicable): Debian 8.4 arm64 How reproducible: Every time. Steps to Reproduce: 1. Download http://cdimage.debian.org/debian-cd/8.4.0/arm64/iso-cd/debian-8.4.0-arm64-netinst.iso 2. Verify checksum 3. Copy to USB drive using Windows Win32DiskImager 4. Insert drive in X-Gene system 5. Boot X-Gene system 6. Navigate to UEFI Shell 7. Enter the following command to start the Fedora installer: FS1:\EFI\BOOT\BOOTAA64.EFI 8. In the Grub boot menu select the first menu option and hit enter 9. System hangs The boot issue was not resolved after I restarted the system and added the following kernel parameter: console=ttyS0,115200 Actual results: The following is displayed on the serial console: EFI stub: Booting Linux Kernel... L3c Cache: 8MB Systems hangs and needs to be rebooted. Expected results: First screen of Debian Installer on either VGA or serial console. Additional info: Hardware Gigabyte MP30-AR0 motherboard with APM X-Gene 1 processor flashed with TianoCore UEFI Kingston KVR16LE11S8/4HB 16 GB ECC DDR3 DRAM HGST Deskstar NAS 6 TB hard drive Logitech USB keyboard The standard U-Boot firmware has been replaced by TianoCore UEFI using the steps described in: https://rwmj.wordpress.com/2016/03/08/gigabyte-mp30-ar0-flashing-uefi/ Both Centos 7.2 and Debian Testing were successfully installed on this system and running stable. -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 4.4.6-1 This was reported to be working in testing at the time of the bug report, which I think means the above version works. Debian 8 "jessie" is now in LTS status and arm64 is not one of the architectures receiving further updates. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#788978: marked as done (linux-image-3.2.0-4-686-pae: Enable CONFIG_GPIO_SYSFS for x86 architectures)
Your message dated Sun, 01 Jul 2018 01:15:49 +0100 with message-id <796af21b55296bcc8a3eb243bb226d03f2a81062.ca...@decadent.org.uk> and subject line Re: linux-image-3.2.0-4-686-pae: Enable CONFIG_GPIO_SYSFS for x86 architectures has caused the Debian Bug report #788978, regarding linux-image-3.2.0-4-686-pae: Enable CONFIG_GPIO_SYSFS for x86 architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 788978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.68-1+deb7u1 Severity: wishlist For easy access to GPIO pins, SYSFS is used in the Linux kernel. For most other architectures (e.g., arm, ppc), GPIO sysfs support is enabled in the Debian kernel, but not on x86 architectures. Please enable this useful feature for x86 kernels. I would appreciate this feature especially for the linux-image-3.2.0-4-686-pae kernel in Wheezy (e.g., together with the next security update), as I need to use exactly this kernel for a legacy project. Thanks for considering this wish and keep up the good work. Marcel --- End Message --- --- Begin Message --- Version: 4.3.3-6 This was enabled in the above version. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#891213: marked as done (linux: please enable CONFIG_BLK_SED_OPAL)
Your message dated Sun, 01 Jul 2018 01:03:27 +0100 with message-id and subject line Re: linux: please enable CONFIG_BLK_SED_OPAL has caused the Debian Bug report #891213, regarding linux: please enable CONFIG_BLK_SED_OPAL to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 891213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Severity: wishlist Dear Maintainer, Please enable CONFIG_BLK_SED_OPAL to allow setup/lock/unlock of self encrypting drives using Opal. In particular, this will allow users the option to save password to resume from S3 sleep. Thanks, Brian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 4.15.17-1 This was enabled in the above version. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#872981: marked as done (Please enable CONFIG_FORTIFY_SOURCE for linux-image-4.13)
Your message dated Sun, 01 Jul 2018 01:02:19 +0100 with message-id and subject line Re: Please enable CONFIG_FORTIFY_SOURCE for linux-image-4.13 has caused the Debian Bug report #872981, regarding Please enable CONFIG_FORTIFY_SOURCE for linux-image-4.13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 872981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image Version: 4.13.0-rc5 Severity: wishlist Hi Ben, > Send config requests to the bug tracking system, please. as requested: linux-image-4.13.0 introduced CONFIG_FORTIFY_SOURCE: Detect overflows of buffers in common string and memory functions where the compiler can determine and validate the buffer sizes. I applied this configuration in my custom kernel and it works fine. Therefore I asked Kees some time ago >> Is there any chance to get it officially activated? and he aanswered: > I'm sure all the distros will set it enabled, and in a few years the > upstream kernel will make it on-by-default. :) Long story short: Please enable this configuration option. Thanks in advance! Markus --- End Message --- --- Begin Message --- Version: 4.16.16-1 This was enabled in the above version. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part --- End Message ---
Re: Arch qualification for buster: call for DSA, Security, toolchain concerns
On Fri, Jun 29, 2018 at 10:33:16PM +0100, Ben Hutchings wrote: > On Fri, 2018-06-29 at 22:31 +0200, Moritz Mühlenhoff wrote: > > Niels Thykier wrote: > > > If the issues and concerns from you or your team are not up to date, > > > then please follow up to this email (keeping debian-release@l.d.o and > > > debian-ports@l.d.o in CC to ensure both parties are notified). > > > > Two issues that we discussed at the recent Security Team sprint wrt > > problems affecting buster: > > > > (1) Linux upstream security support for i386 seems at risk at this point. > > E.g. KPTI for i386 still isn't merged in Linux master half a year later > > after > > the public Meltdown disclosure in early January (and the development of KPTI > > started months before that). Someone at SuSE actually developed patches > > as an older SLES release using Linux 3.0 (!) still supports i386, but that > > will also EOL at some point and if we don't have the manpower to > > develop upstream fixes for future i386-specific flaws. > > > > It's not a strict blocker, but we wanted to raise the discussion whether > > it still makes sense to ship 32 bit kernels for buster, which means with > > support until ~ 2022. > [...] > > The lack of Meltdown mitigation on i386 is concerning, though I remain > somewhat hopeful that it will get fixes eventually. A quick look > through kernel-sec finds maybe 3 other i386-specific issues in the last > 5 years (CVE-2013-0190, CVE-2014-4508, CVE-2016-3672), and none of the > fixes were difficult to backport. Fair enough. Ultimately it's your call, but we wanted to raise it due to the long term perspective upstream. > It's worth noting that Meltdown also never got mitigated for any of the > other affected architectures (at least ppc64el and s390x) in jessie, > despite being addressed upstream. So I don't think it makes sense to > pick on i386 as being particularly vulnerable. Well, the difference is that 99% of users still installing a buster system with i386 are doing it out of ignorance and would otherwise be protected if they'd picked amd64. For ppc64el and s390x no such alternative exists. Cheers, Moritz
Bug#902777: linux-image-4.9.0-6-amd64: debian crash on laptop lenovo carbon with intel i915 video card
Package: src:linux Version: 4.9.88-1+deb9u1 Severity: normal Dear Maintainer, During gnome-session login window debian crash. Please look at the following stack trace: Jun 29 17:04:48 nvme kernel: [1725991.873107] [ cut here ] Jun 29 17:04:48 nvme kernel: [1725991.873140] WARNING: CPU: 2 PID: 22004 at /build/linux-6WgLIg/linux-4.9.88/drivers/gpu/drm/i915/intel_display.c:1085 haswell_crtc_disable+0x7f/0x1 80 [i915] Jun 29 17:04:48 nvme kernel: [1725991.873141] pipe_off wait timed out Jun 29 17:04:48 nvme kernel: [1725991.873141] Modules linked in: nls_ascii nls_cp437 vfat fat garmin_gps nf_conntrack_ipv6 nf_defrag_ipv6 sd_mod sg uas usb_storage scsi_mod nls_utf 8 cifs sha256_ssse3 md4 des_generic dns_resolver fscache xt_nat xt_tcpudp veth snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device hid_generic fuse ipt_MASQUERADE nf_nat_masqu erade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype ip6table_filter ip6_tables xt_conntrack nf_nat nf _conntrack br_netfilter bridge stp iptable_filter llc overlay tun ctr ccm rfcomm pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cmac bnep arc4 sparse_keymap uvcvideo vi deobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core cdc_ether btusb videodev btrtl btbcm snd_hda_codec_hdmi option Jun 29 17:04:48 nvme kernel: [1725991.873172] btintel usbnet usb_wwan mii usbserial snd_hda_codec_conexant snd_hda_codec_generic bluetooth media intel_rapl x86_pkg_temp_thermal in tel_powerclamp coretemp snd_soc_skl kvm_intel snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core kvm irqbypass snd_soc_sst_match intel_cstate snd_soc_core snd_compres s intel_uncore intel_rapl_perf iwlmvm mac80211 joydev evdev serio_raw pcspkr iwlwifi snd_hda_intel iTCO_wdt iTCO_vendor_support snd_hda_codec cfg80211 snd_hda_core snd_hwdep i915 r tsx_pci_ms hid_sensor_accel_3d drm_kms_helper hid_sensor_trigger hid_sensor_iio_common industrialio_triggered_buffer memstick drm mei_me snd_pcm snd_timer kfifo_buf i2c_algo_bit me i intel_pch_thermal industrialio thinkpad_acpi shpchp wmi battery nvram snd soundcore ac rfkill video button parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache algif_skcipher af_alg hid_logitech_hidpp hid_logitech_dj usbhid dm_crypt dm_mod hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid rtsx_pci_sd mmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_i801 i2c_smbus psmouse e1000e ptp pps_core xhci_pci nvme xhci_hcd nvme_core rtsx_pci mfd_core usbcore intel_ish_ipc usb_common intel_ishtp thermal Jun 29 17:04:48 nvme kernel: [1725991.873226] CPU: 2 PID: 22004 Comm: kworker/2:2 Tainted: G O4.9.0-6-amd64 #1 Debian 4.9.88-1+deb9u1 Jun 29 17:04:48 nvme kernel: [1725991.873228] Hardware name: LENOVO 20FC0038PB/20FC0038PB, BIOS N1FET59W (1.33 ) 12/19/2017 Jun 29 17:04:48 nvme kernel: [1725991.873240] Workqueue: events drm_mode_rmfb_work_fn [drm] Jun 29 17:04:48 nvme kernel: [1725991.873241] b2f2f774 bbf289a6fb58 Jun 29 17:04:48 nvme kernel: [1725991.873243] b2c78a5e 0001 bbf289a6fbb0 8f9893c73000 Jun 29 17:04:48 nvme kernel: [1725991.873245] 8f994dab 8f994da6f000 8f9672a30820 b2c78adf Jun 29 17:04:48 nvme kernel: [1725991.873246] Call Trace: Jun 29 17:04:48 nvme kernel: [1725991.873250] [] ? dump_stack+0x5c/0x78 Jun 29 17:04:48 nvme kernel: [1725991.873252] [] ? __warn+0xbe/0xe0 Jun 29 17:04:48 nvme kernel: [1725991.873254] [] ? warn_slowpath_fmt+0x5f/0x80 Jun 29 17:04:48 nvme kernel: [1725991.873268] [] ? haswell_crtc_disable+0x7f/0x180 [i915] Jun 29 17:04:48 nvme kernel: [1725991.873280] [] ? intel_atomic_commit_tail+0x17d/0xf70 [i915] Jun 29 17:04:48 nvme kernel: [1725991.873291] [] ? intel_prepare_plane_fb+0x14a/0x290 [i915] Jun 29 17:04:48 nvme kernel: [1725991.873302] [] ? intel_atomic_commit+0x355/0x4c0 [i915] Jun 29 17:04:48 nvme kernel: [1725991.873307] [] ? drm_atomic_helper_set_config+0x79/0xb0 [drm_kms_helper] Jun 29 17:04:48 nvme kernel: [1725991.873313] [] ? drm_mode_object_unreference+0x35/0x70 [drm] Jun 29 17:04:48 nvme kernel: [1725991.873320] [] ? drm_mode_set_config_internal+0x67/0x110 [drm] Jun 29 17:04:48 nvme kernel: [1725991.873326] [] ? drm_crtc_force_disable+0x34/0x50 [drm] Jun 29 17:04:48 nvme kernel: [1725991.873332] [] ? drm_framebuffer_remove+0xcc/0x110 [drm] Jun 29 17:04:48 nvme kernel: [1725991.873338] [] ? drm_mode_rmfb_work_fn+0x3d/0x50 [drm] Jun 29 17:04:48 nvme kernel: [1725991.873339] [] ? process_one_work+0x18a/0x420 Jun 29 17:04:48 nvme kernel: [1725991.873341] [] ? worker_thread+0x1ca/0x490 Jun 29 17:04:48 nvme kernel: [1725991.873342] [] ? process_one_work+0x420/0x420 Jun 29 17:04:48 nvme kernel: [1725991.873343] [] ? kthread+0xd9/0xf0 Jun 29
