Bug#988300: linux-kbuild-5.10: can not build nvidia-kernel-340xx-dkms

[Hans-J. Ullrich]

Package: linux-kbuild-5.10
Version: 5.10.28-1
Severity: important

Dear Maintainer,

I am not quite sure, but I believe, there is a problem with either 
linux-kbuild-5.10 or the nvidia-kernel-340xx-dkms.

The problem is, that the build of the kernel module stops and the make.log says 
the following:

--- snip ---

make[3]: Verzeichnis „/usr/src/linux-headers-5.10.0-6-amd64“ wird betreten
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
make -f /usr/src/linux-headers-5.10.0-6-common/scripts/Makefile.build obj=.. \
single-build= \
need-builtin=1 need-modorder=1
/usr/src/linux-headers-5.10.0-6-common/scripts/Makefile.build:44: 
/usr/src/linux-headers-5.10.0-6-common/../Makefile: Datei oder Verzeichnis 
nicht gefunden
make[4]: *** Keine Regel, um 
„/usr/src/linux-headers-5.10.0-6-common/../Makefile“ zu erstellen.  Schluss.
make[3]: *** [/usr/src/linux-headers-5.10.0-6-common/Makefile:1822: ..] Fehler 2
make[3]: Verzeichnis „/usr/src/linux-headers-5.10.0-6-amd64“ wird verlassen
make[2]: *** [Makefile:185: __sub-make] Fehler 2
make[2]: Verzeichnis „/usr/src/linux-headers-5.10.0-6-common“ wird verlassen
make[1]: *** [Makefile:205: nvidia.ko] Fehler 2
make[1]: Verzeichnis „/var/lib/dkms/nvidia-legacy-340xx/340.108/build“ wird 
verlassen
make: *** [Makefile:221: ../Module.symvers] Fehler 2
make: Verzeichnis „/var/lib/dkms/nvidia-legacy-340xx/340.108/build/uvm“ wird 
verlassen
  
1124,1  
--- snap 

This issue happened, when I deinstalled and reinstalled all the nvidia-packages.

Please note: It was possible before to build the nvidia-module for a 
5.10-version, but this was a prior version before 5.10.0-6-amd64 (maybe 
5.10.0-4-amd64 or similar).

On kernel version 4.19.0-16-amd64 the module can be build, but this is another 
linux-kbuild-version!

Thus and because of the make.log I believe, linux-kbuild-5.10 might be buggy.

Thank you for reading this and any help.

Best regards

Hans
 

 





-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-kbuild-5.10 depends on:
ii  libc6  2.31-11
ii  libelf10.183-1
ii  libssl1.1  1.1.1k-1

linux-kbuild-5.10 recommends no packages.

linux-kbuild-5.10 suggests no packages.

-- debconf-show failed

Bug#795013: Closing this bug (BTS maintenance for src:linux bugs)

[A. M.]

reopen 795013
thanks

# Dear Salvatore:
# I have not said anything for a long time, but not because the bug
# didn't occur, but because I didn't know what to do when the startup
# failed the described way, and because the failure was infrequent.  I
# always simply restarted the laptop.  The machine always runs the
# current Debian stable, whichever it may be.  The call stacks have
# already been given in the bug report if it helps.  I would kindly ask
# you to tell me how/what to debug next.
# Alex

Bug#785419: Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

[Rick Thomas]

On Sat, May 8, 2021, at 12:02 PM, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> Hi,
> 
> Ist this still an issue or has been fixed in meanwhile? I'm going
> through some older src:linux associated buts and noticed that it was
> considered here to reassign it to util-linux.
> 
> Is the problem still present?
> 
> Further:
> 
> On Fri, Mar 17, 2017 at 07:55:31PM +0100, Lukas Wunner wrote:
> [...]
> > @Rick Thomas: Could you verify if the attached patch solves this issue
> > for you?
> 
> Were you able to test the proposed patch?
> 
> Regards,
> Salvatore

Thanks for following up on this!

No, I got side-tracked by a family medical issue (now all resolved and OK) and 
never was able to test the patches.  Sorry!

Nevertheless, I can verify that the problem _is_ still with us.  I'm running

rbthomas@cube:~$ uname -a
Linux cube 4.19.0-16-armmp #1 SMP Debian 4.19.181-1 (2021-03-19) armv7l 
GNU/Linux
rbthomas@cube:~$ cat /etc/debian_version 
10.9

on a Cubox-i4Pro.   It still shows as having two RealTime clocks.  The one 
named /dev/rtc0 still looses it's time when I unplug/replug the device, while 
/dev/rtc1 still does manage to carry-over.  Unfortunately, the kernel still 
uses rtc0 to set system time when rebooting.

The workaround I use (such as it is) is to run ntpsec with the "-g" option, 
which allows the first system clock adjustment to be more than 1000 seconds. ( 
I also have to remember to reset rtc0 after a power outage.)

Along the same lines, I recently got a Raspberry Pi4B 4GB, and was somewhat 
surprised to find that it did not have a RT clock at all unless you buy an 
add-on hat for it.  So we not only have to deal with devices with two RT 
clocks, but also devices with zero RT clocks.

I'm not much of a software developer, so if you want me to test something, 
please provide it in the form of a ".deb" that I can install,  rather than a 
set of patches I have to apply.

Thanks!
Rick

Bug#836836: marked as done ([linux-image-extra] Wireless interface absent - 8192cu)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:29:59 -0700 (PDT)
with message-id <60984647.1c69fb81.3778d.6...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #836836,
regarding [linux-image-extra] Wireless interface absent - 8192cu
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.)


-- 
836836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-extra
Version: 4.4.13+
Severity: normal

--- Please enter the report below this line. ---

from dmesg

[   56.397020] [ cut here ]
[   56.398148] WARNING: CPU: 0 PID: 66 at net/wireless/sme.c:907
__cfg80211_disconnected+0x280/0x2c8 [cfg80211]() [   56.398266] Modules
linked in: binfmt_misc 8192cu cfg80211 rfkill ftdi_sio usbserial
snd_bcm2835 snd_pcm snd_timer snd bcm2835_gpiomem bcm2835_wdt
uio_pdrv_genirq uio joydev evdev i2c_dev fuse ipv6 [   56.398563] CPU:
0 PID: 66 Comm: kworker/u2:2 Not tainted 4.4.13+ #894 [   56.398581]
Hardware name: BCM2708 [   56.399557] Workqueue: cfg80211
cfg80211_event_work [cfg80211] [   56.399941] []
(unwind_backtrace) from [] (show_stack+0x20/0x24)
[   56.400035] [] (show_stack) from []
(dump_stack+0x20/0x28) [   56.400079] [] (dump_stack) from
[] (warn_slowpath_common+0x8c/0xc4) [   56.400112]
[] (warn_slowpath_common) from []
(warn_slowpath_null+0x2c/0x34) [   56.401100] []
(warn_slowpath_null) from []
(__cfg80211_disconnected+0x280/0x2c8 [cfg80211]) [   56.402811]
[] (__cfg80211_disconnected [cfg80211]) from []
(cfg80211_process_wdev_events+0x1a0/0x20c [cfg80211]) [   56.404989]
[] (cfg80211_process_wdev_events [cfg80211]) from
[] (cfg80211_process_rdev_events+0x3c/0x74 [cfg80211])
[   56.406960] [] (cfg80211_process_rdev_events [cfg80211])
from [] (cfg80211_event_work+0x24/0x2c [cfg80211])
[   56.408006] [] (cfg80211_event_work [cfg80211]) from
[] (process_one_work+0x11c/0x39c) [   56.408416] []
(process_one_work) from [] (worker_thread+0x40/0x4d0)
[   56.408566] [] (worker_thread) from []
(kthread+0xdc/0xf8) [   56.408740] [] (kthread) from
[] (ret_from_fork+0x14/0x2c) [   56.408767] ---[ end trace
a700d75994067ea4 ]---

Wireless is unusable, interface doesn' t get an IP address


Daniel

--- System information. ---
Architecture: armhf
Kernel:   Linux 4.4.13+

Debian Release: 8.0
  500 stable  mirrordirector.raspbian.org 
  500 stable  archive.raspberrypi.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Processed: Re: Bug#837907: stat() hangs on a particular file

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #837907 [src:linux] stat() hangs on a particular file
Added tag(s) moreinfo.

-- 
837907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837907: stat() hangs on a particular file

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

On Thu, Sep 15, 2016 at 01:12:42PM +0200, Sergio Gelato wrote:
> Package: linux-image-3.16.0-4-amd64
> Version: 3.16.36-1+deb8u1
> 
> One of our systems is suddenly unable to stat() a particular file
> (cookies.sqlite-wal in a user's Firefox profile). Any attempt to
> do so hangs in the system call, as shown by strace. The file resides
> on an NFSv4 share (sec=krb5p). Other files in the same directory on
> the same share remain accessible. The affected file is normally accessible
> on the NFS server and from other NFS clients running the same kernel.
> 
> The user has reported a similar incident yesterday on some directories
> on a different NFS share (also sec=krb5p, but hosted on a different
> server). He rebooted to clear up the problem.
> 
> I'd like advice on how to troubleshoot this effectively. I've tried
> rpcdebug -m {nfs,rpc,nlm} -s all but didn't see any smoking gun; maybe
> some information cached by the kernel is suppressing NFS activity
> associated with the stat() calls. The log entries I do see say
> NFS: nfs_lookup_revalidate(cookies.sqlite-wal) is valid
> 
> Some related kernel traces from this system's logs (in chronological order,
> with an intervening reboot; the first trace is associated with yesterday's
> incident, the second trace is 2-3 minutes newer than the timestamp on
> cookies.sqlite-wal):
> 
> [97483.663949] INFO: task ls:23767 blocked for more than 120 seconds.
> [97483.663951]   Tainted: PW  O  3.16.0-4-amd64 #1
> [97483.663952] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
> this message.
> [97483.663954] ls  D 8800afd3b808 0 23767  1 
> 0x0004
> [97483.663957]  8800afd3b3b0 0086 00012f40 
> 88039a057fd8
> [97483.663960]  00012f40 8800afd3b3b0 88041ea137f0 
> 88041edcd128
> [97483.663962]  0002 8113eb50 88039a057d60 
> 88039a057e40
> [97483.663965] Call Trace:
> [97483.663968]  [] ? wait_on_page_read+0x60/0x60
> [97483.663971]  [] ? io_schedule+0x99/0x120
> [97483.663974]  [] ? sleep_on_page+0xa/0x10
> [97483.663977]  [] ? __wait_on_bit+0x5c/0x90
> [97483.663980]  [] ? wait_on_page_bit+0xc6/0xd0
> [97483.663983]  [] ? autoremove_wake_function+0x30/0x30
> [97483.663986]  [] ? pagevec_lookup_tag+0x1d/0x30
> [97483.663989]  [] ? filemap_fdatawait_range+0xd0/0x160
> [97483.663993]  [] ? filemap_write_and_wait+0x36/0x50
> [97483.664002]  [] ? nfs_getattr+0x108/0x220 [nfs]
> [97483.664005]  [] ? vfs_fstatat+0x57/0x90
> [97483.664009]  [] ? SYSC_newlstat+0x1d/0x40
> [97483.664013]  [] ? system_call_fast_compare_end+0x10/0x15
> 
> [ 9724.415533] INFO: task mozStorage #5:2748 blocked for more than 120 
> seconds.
> [ 9724.415537]   Tainted: PW  O 3.16.0-4-amd64 #1
> [ 9724.415538] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
> this message.
> [ 9724.415539] mozStorage #5   D 8803ee153a88 0  2748   2323 
> 0x
> [ 9724.415542]  8803ee153630 0082 00012f40 
> 8803ee2cffd8
> [ 9724.415544]  00012f40 8803ee153630 88041ea537f0 
> 88041edaf7a0
> [ 9724.415545]  0002 a0669800 8803ee2cfc30 
> 88040b1152c0
> [ 9724.415547] Call Trace:
> [ 9724.415557]  [] ? nfs_pageio_doio+0x50/0x50 [nfs]
> [ 9724.415560]  [] ? io_schedule+0x99/0x120
> [ 9724.415563]  [] ? nfs_wait_bit_uninterruptible+0xa/0x10 
> [nfs]
> [ 9724.415566]  [] ? __wait_on_bit+0x5c/0x90
> [ 9724.415568]  [] ? internal_add_timer+0x2a/0x70
> [ 9724.415571]  [] ? nfs_pageio_doio+0x50/0x50 [nfs]
> [ 9724.415573]  [] ? out_of_line_wait_on_bit+0x77/0x90
> [ 9724.415575]  [] ? autoremove_wake_function+0x30/0x30
> [ 9724.415578]  [] ? nfs_updatepage+0x15e/0x830 [nfs]
> [ 9724.415582]  [] ? nfs_write_end+0x57/0x320 [nfs]
> [ 9724.415585]  [] ? 
> iov_iter_copy_from_user_atomic+0x75/0x190
> [ 9724.415588]  [] ? generic_perform_write+0x11b/0x1c0
> [ 9724.415590]  [] ? __generic_file_write_iter+0x158/0x340
> [ 9724.415592]  [] ? generic_file_write_iter+0x39/0xa0
> [ 9724.415595]  [] ? nfs_file_write+0x83/0x1a0 [nfs]
> [ 9724.415598]  [] ? new_sync_write+0x74/0xa0
> [ 9724.415600]  [] ? vfs_write+0xb2/0x1f0
> [ 9724.415601]  [] ? SyS_write+0x42/0xa0
> [ 9724.415603]  [] ? SyS_lseek+0x43/0xa0
> [ 9724.415605]  [] ? system_call_fast_compare_end+0x10/0x15

Do you still can reproduce the issue with a recent kernel?

Regards,
Salvatore

Bug#837809: marked as done (radeon drm error messages in dmesg)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:33:54 -0700 (PDT)
with message-id <60984732.1c69fb81.ed674.5...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #837809,
regarding radeon drm error messages in dmesg
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.)


-- 
837809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.7.2-1+s1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I do not remember seeing them until recently.
They are appeared here either with 4.7 (4.6 was fine?)
or with new mesa.

- -- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 
20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1 (2016-08-28)

** Command line:
BOOT_IMAGE=/@/boot/vmlinuz-4.7.0-1-amd64 
root=UUID=ccd67dc6-6b12-47f6-bef7-a17c40b87332 ro rootflags=subvol=@ 
cryptdevice=UUID=7093dff9-dea8-49a2-bc83-653d5b677b9b:sdb3_luks,UUID=f533b8e8-b916-4b60-9cfc-10f4a56cc146:sdc3_luks

** Not tainted

** Kernel log:
Today:

[32814.56] [TTM] Buffer eviction failed
[32814.631508] [TTM] Buffer eviction failed
[32814.632004] [TTM] Buffer eviction failed
[32814.632488] [TTM] Buffer eviction failed
[32814.698484] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to 
allocate GEM object (98304000, 6, 131072, -14)
[32814.700977] [TTM] Buffer eviction failed
[32814.701598] [TTM] Buffer eviction failed
[32814.714461] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to 
allocate GEM object (98304000, 6, 131072, -14)
[32814.841482] [TTM] Buffer eviction failed
[32814.843322] [TTM] Buffer eviction failed
[32814.856458] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to 
allocate GEM object (98304000, 6, 131072, -14)
[32814.858356] [TTM] Buffer eviction failed
[32814.858985] [TTM] Buffer eviction failed
[32814.872116] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to 
allocate GEM object (98304000, 6, 131072, -14)
[32814.875467] [TTM] Buffer eviction failed
[32814.876188] [TTM] Buffer eviction failed
[32814.889065] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to 
allocate GEM object (98304000, 6, 131072, -14)
[32814.889722] [TTM] Buffer eviction failed
[32814.890359] [TTM] Buffer eviction failed
[32814.903155] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to 
allocate GEM object (98304000, 6, 131072, -14)
[35611.152666] [TTM] Buffer eviction failed

Sep 13 11:50:49 pini-pini kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed 
to parse relocation -12!
Sep 13 11:50:45 pini-pini kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed 
to parse relocation -22!

Sep 12 14:48:45 pini-pini kernel: [drm:si_dpm_set_power_state [radeon]] *ERROR* 
si_restrict_performance_levels_before_switch failed



** Model information
sys_vendor: To be filled by O.E.M.
product_name: To be filled by O.E.M.
product_version: To be filled by O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: 2201
board_vendor: ASUSTeK COMPUTER INC.
board_name: CROSSHAIR V FORMULA-Z
board_version: Rev 1.xx

** Loaded modules:
cpufreq_userspace
cpufreq_stats
cpufreq_powersave
cpufreq_conservative
binfmt_misc
nls_ascii
nls_cp437
vfat
fat
eeepc_wmi
kvm_amd
asus_wmi
sparse_keymap
kvm
irqbypass
rfkill
video
crct10dif_pclmul
snd_hda_codec_realtek
crc32_pclmul
mxm_wmi
e1000e
ghash_clmulni_intel
amdkfd
snd_hda_codec_hdmi
snd_hda_codec_generic
radeon
snd_hda_intel
ttm
pcspkr
fam15h_power
sg
drm_kms_helper
k10temp
snd_hda_codec
efi_pstore
drm
sp5100_tco
efivars
snd_hda_core
xhci_pci
ptp
xhci_hcd
pps_core
wmi
fjes
i2c_algo_bit
button
i2c_piix4
snd_hwdep
snd_pcm
tpm_infineon
acpi_cpufreq
snd_timer
tpm_tis
snd
soundcore
tpm
shpchp
tcp_yeah
tcp_vegas
it87
hwmon_vid
sunrpc
configfs
loop
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
dm_crypt
dm_mod
btrfs
crc32c_generic
xor
raid6_pq
joydev
hid_generic
usbhid
hid
sd_mod
crc32c_intel
ohci_pci
aesni_intel
aes_x86_64
glue_helper
lrw
gf128mul
ablk_helper
cryptd
ohci_hcd
ehci_pci
evdev
ahci
ehci_hcd
libahci
serio_raw
libata
usbcore
scsi_mod
usb_common

** Network interface configuration:

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet static
address 192.168.1.4
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 127.0.0.1
dns-search lcl

** Network 

Bug#837178: marked as done (linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:32:54 -0700 (PDT)
with message-id <609846f6.1c69fb81.c517c.3...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #837178,
regarding linux-image-3.16.0-4-amd64: All memory and swap is used up until 
system freezes
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.)


-- 
837178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3
Severity: critical
Tags: security
Justification: causes serious data loss

Dear Maintainer,

when I open a particular word document (it contains images and I can send it
to you for testing) with libreoffice, all memory and all swap get used up
within about a minute. This happens slowly enough that it can be monitored
with "top" and "free". What I see with top is that soffice.bin (which is
libreoffice) does not use much memory (maybe 2%). Nevertheless more and more
memory gets used. "free -h" gives something like this:

 total   used   free sharedbuffers cached
Mem:  7.5G   7.4G   141M   5.9G71M   6.4G
-/+ buffers/cache:   917M   6.6G
Swap: 8.0G   663M   7.4G

Eventually the "used" column in the "Mem:" and "Swap:" and lines reach the
total and the system runs out of memory and becomes totally unresponsive
(even the mouse pointer freezes), no remote logins are possible at this
point, and all keypresses are ignored. The only way to regain control is by
holding down the power button for 10s. However, the "used" column in the
"-/+ buffers/cache:" line stays near 1GB, so that it is clear that
buffers/caches take up almost all the space.

You may wonder why I file this against the kernel and not libreoffice. Well,
I am sure libreoffice is doing something stupid, that could be fixed to
circumvent this problem. But the kernel should simply not allow any user
process to bring down the entire system. Also it seems the kernel is
allocating caches or buffers until it runs out of all memory and then
freezes. If it was only libreoffice allocating memory, OOM killer would kill
it. But nothing like this happens, even if you wait 2h nothing happens. I
think OOM killer does nothing because no single user process uses a lot of
memory. It's the kernel choking on itself. 

Ok, so now let me speculate on what might be wrong. I am filing this report
for my laptop that has a i7-3667U CPU with integrated Intel graphics card:
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
But the problem also occurs on 3 other Debian desktop machines that run the
same kernel, and have either Intel or ATI graphics, i.e.:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barts 
PRO [Radeon HD 6850]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
However, it happens differently on a 4th Debian desktop machine with
07:00.0 VGA compatible controller: NVIDIA Corporation NV42GL [Quadro FX 
3450/4000 SDI] (rev a2)
On this one, Gnome3 crashes and dmesg has a lot of lines lines like:
[880754.926611] [TTM] Failed to find memory space for buffer 0x880367e42800 
eviction
[880754.926613] [TTM] No space for 880367e42800 (497 pages, 1988K, 1M)
[880754.926614] [TTM]   placement[0]=0x00070002 (1)
[880754.926616] [TTM] has_type: 1
[880754.926617] [TTM] use_type: 1
[880754.926618] [TTM] flags: 0x000A
[880754.926619] [TTM] gpu_offset: 0x
[880754.926620] [TTM] size: 131072
[880754.926621] [TTM] available_caching: 0x0007
[880754.926622] [TTM] default_caching: 0x0001
This is actually good because after the gnome3 crash the system is still
usable. I should say that in all cases I am using the open source graphics
drivers that use kernel mode setting. So the latter crash leads me to think
that some interaction between the graphics drivers and the kernel leads to
the allocation of too many buffers/caches by the kernel until it runs out.
Probably this is all triggered by libreoffice (running on X) trying to
display some JPG images in a document.

The reason why I consider this security relevant is that anybody with a user
account can use libreoffice to bring the system down. This will cause data
loss since 

Bug#837512: marked as done (10: "hub 3-3.1:1.0: hub_ext_port_status failed (err = -71)" ocassionally on boot)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:33:04 -0700 (PDT)
with message-id <60984700.1c69fb81.c1764.f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #837512,
regarding 10: "hub 3-3.1:1.0: hub_ext_port_status failed (err = -71)" 
ocassionally on boot
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.)


-- 
837512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 10
Version: kernel
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? 
Ocassionally on boot this error is displayed and the usb ports dont 
work until reboot
Asus Z87 Pro Motherboard. Just the four ports near the ps2 ports are 
not working the others are working.
"hub 3-3.1:1.0: hub_ext_port_status failed (err = -71)"
   * What exactly did you do (or not do) that was effective (or
 ineffective)? 
Reboot the system have not looked into other workarounds yet
   * What was the outcome of this action? 
USB ports usually work fine after reboot.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#836973: marked as done (linux-image-3.16.0-4-amd64: i40e driver spamming kern.log saying FD filter programming error)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:30:49 -0700 (PDT)
with message-id <60984679.1c69fb81.f4359.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #836973,
regarding linux-image-3.16.0-4-amd64: i40e driver spamming kern.log saying FD 
filter programming error
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.)


-- 
836973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3
Severity: normal

Dear Maintainer,

Debian jessie system with bonded intel 10Gbps fiber nic's. After a
couple of days of uptime system starts spamming kern.log (now >400MB)
starting with the 1st two lines below then last 2 repeated over and over with
only the loc # changing. Seems like the filter space full condition
triggered the filter programming error problem. System seems to be
running fine other then the high /var/log usage.


-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/gdx--pg2--vg-root ro 
hugepagesz=1GB

** Not tainted

** Kernel log:
[183792.431414] i40e :01:00.1: ntuple filter loc = 27190, could not be added
[183792.431474] i40e :01:00.1: FD filter space full, ATR for further flows 
will be turned off
[235799.801324] i40e :01:00.0: ntuple filter loc = 168, could not be added
[235799.801379] i40e :01:00.0: FD filter programming error
... Repeating the last 2 lines with only the loc = # changing


** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge R630
bios_vendor: Dell Inc.
bios_version: 1.3.6
board_vendor: Dell Inc.
board_version: A08

** Loaded modules:
raid10
ipmi_si
mpt2sas
mptctl
mptbase
dell_rbu
nfsd
auth_rpcgss
oid_registry
nfsv3
nfs_acl
nfs
lockd
fscache
sunrpc
bonding
md_mod
dm_queue_length
ipmi_devintf
iTCO_wdt
iTCO_vendor_support
evdev
dcdbas
x86_pkg_temp_thermal
intel_powerclamp
intel_rapl
coretemp
kvm_intel
kvm
dm_multipath
crc32_pclmul
scsi_dh
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ttm
ablk_helper
drm_kms_helper
cryptd
drm
pcspkr
mei_me
mei
lpc_ich
mfd_core
ipmi_msghandler
shpchp
processor
thermal_sys
button
wmi
acpi_power_meter
autofs4
ext4
crc16
mbcache
jbd2
dm_mod
ses
enclosure
sg
sd_mod
crc_t10dif
crct10dif_generic
crct10dif_pclmul
crct10dif_common
crc32c_intel
igb
i2c_algo_bit
ahci
mpt3sas
libahci
raid_class
i40e
ehci_pci
i2c_core
ehci_hcd
vxlan
dca
libata
scsi_transport_sas
megaraid_sas
ptp
usbcore
usb_common
pps_core
scsi_mod

** Network interface configuration:
source /etc/network/interfaces.d/*

# The loopback network interface
auto lo bond0
iface lo inet loopback

# The primary network interface
allow-hotplug bond0
iface bond0 inet static
address 192.168.4.40
netmask 255.255.255.0
gateway 192.168.4.1
slaves eth2 eth3
bond_mode balance-xor
bond_miimon 100
bond_downdelay 200
bond_updelay 200

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether f8:bc:12:0b:9e:c0 brd ff:ff:ff:ff:ff:ff
3: eth1:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether f8:bc:12:0b:9e:c1 brd ff:ff:ff:ff:ff:ff
4: eth2:  mtu 1500 qdisc mq master bond0 
state UP group default qlen 1000
link/ether f8:bc:12:0b:9e:a0 brd ff:ff:ff:ff:ff:ff
5: eth3:  mtu 1500 qdisc mq master bond0 
state UP group default qlen 1000
link/ether f8:bc:12:0b:9e:a0 brd ff:ff:ff:ff:ff:ff
6: bond0:  mtu 1500 qdisc noqueue state 
UP group default 
link/ether f8:bc:12:0b:9e:a0 brd ff:ff:ff:ff:ff:ff
inet 192.168.4.40/24 brd 192.168.4.255 scope global bond0
   valid_lft forever preferred_lft forever
inet6 fe80::fabc:12ff:fe0b:9ea0/64 scope link 
   valid_lft forever preferred_lft forever

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
  eth0:   0   0000 0  0   

Bug#836734: marked as done (Considerable I/O performance regression on Lenovo Carbon X1 with 4.7.0)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:29:20 -0700 (PDT)
with message-id <60984620.1c69fb81.173b3.a...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #836734,
regarding Considerable I/O performance regression on Lenovo Carbon X1 with 4.7.0
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.)


-- 
836734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:linux
Version: 4.7.2-1
Severity: normal

I'm using a Carbon X1 (3rd gen). Compared to the latest 4.6 kernel, this image
has a significant performance regression in all I/O related operations.

Just as a ballpark, 4.6.0-1 can boot in generally less than 3 seconds after the
grub screen. With 4.7.0-1, it takes over 10.

I'm unsure at what exactly look for, as it could also be related to many
subsystems (I'm using an ext4 fs in an encrypted volume).

-- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 
20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1 (2016-08-28)

** Command line:
BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/eab16011nb--vg-root ro quiet

** Tainted: OE (12288)
* Out-of-tree module has been loaded.
* Unsigned module has been loaded (currently expected).

** Kernel log:
[   11.622772] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-7265D-17.ucode (-2)
[   11.622847] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-7265D-17.ucode failed with error -2
[   11.625002] iwlwifi :04:00.0: firmware: direct-loading firmware 
iwlwifi-7265D-16.ucode
[   11.625334] iwlwifi :04:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm
[   11.642592] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 
7265, REV=0x210
[   11.644390] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[   11.644830] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[   11.669474] intel_rapl: Found RAPL domain package
[   11.669478] intel_rapl: Found RAPL domain core
[   11.669481] intel_rapl: Found RAPL domain uncore
[   11.669483] intel_rapl: Found RAPL domain dram
[   11.676332] [drm] Memory usable by graphics device = 4096M
[   11.676342] [drm] Replacing VGA console driver
[   11.676914] Console: switching to colour dummy device 80x25
[   11.682301] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   11.682304] [drm] Driver supports precise vblank timestamp query.
[   11.682538] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   11.720562] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   11.720990] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16
[   11.723454] usb 1-7: USB disconnect, device number 5
[   11.724809] systemd-journald[1407]: Received request to flush runtime 
journal from PID 1
[   11.727172] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   11.783316] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
[   11.950560] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   11.950567] [drm] Initialized i915 1.6.0 20160425 for :00:02.0 on minor 0
[   11.951760] fbcon: inteldrmfb (fb0) is primary device
[   11.958763] Bluetooth: Core ver 2.21
[   11.958777] NET: Registered protocol family 31
[   11.958777] Bluetooth: HCI device and connection manager initialized
[   11.958780] Bluetooth: HCI socket layer initialized
[   11.958783] Bluetooth: L2CAP socket layer initialized
[   11.958788] Bluetooth: SCO socket layer initialized
[   11.963733] usbcore: registered new interface driver btusb
[   11.967069] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card1/input17
[   11.967121] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card1/input18
[   11.967167] input: HDA Intel HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.0/sound/card1/input19
[   12.438944] scsi 1:0:0:0: Direct-Access Generic- SD/MMC/MS/MSPRO  1.00 
PQ: 0 ANSI: 4
[   12.439447] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   12.41] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[   12.461107] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:04F3:012D.0001/input/input20
[   12.461297] hid-multitouch 0003:04F3:012D.0001: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-5/input0
[   12.495250] media: Linux media interface: 

Bug#834690: marked as done (linux-image bug)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:26:27 -0700 (PDT)
with message-id <60984573.1c69fb81.914e8.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #834487,
regarding linux-image bug
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.)


-- 
834487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Version: 3.16.7-ckt25-2 & 3.16.7-ckt25-2+deb8u3

update this panic problem :
the panic don't happen again when updating kernel to 4.4.6.
my OS is debian 8.5
hardware information:
Manufacturer: Dell Inc.
Product Name: 082F9M
CPU: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz

we run a golang applications on the OS, and the golang version is  1.6.2


2016-08-16 14:20 GMT+08:00 张永肃 :

> Package: linux-image
> Version: 3.16.7-ckt25-2 & 3.16.7-ckt25-2+deb8u3
>
> we face kernel panic issue :
>
> 1. kernel  panic on 3.16.7-ckt25-2+deb8u3 ; 2 kinds of dumping
> informations :
>
> *A*:
>
> [3145152.947164] BUG: unable to handle kernel NULL pointer dereference at 
> 0592
> [3145152.947235] IP: [] update_cfs_rq_blocked_load+0x5/0x120
> [3145152.947292] PGD 6708ba067 PUD 857130067 PMD 0
> [3145152.947332] Oops:  [#1] SMP
> [3145152.947360] Modules linked in: dccp_diag dccp tcp_diag udp_diag 
> inet_diag unix_diag af_packet_diag netlink_diag nls_utf8 fuse btrfs xor 
> raid6_pq ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs libcrc32c 
> crc32c_generic dm_mod 8021q garp stp mrp llc iTCO_wdt iTCO_vendor_support 
> x86_pkg_temp_thermal coretemp kvm_intel kvm crc32_pclmul aesni_intel 
> aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd pcspkr ast evdev 
> joydev ttm drm_kms_helper drm i2c_algo_bit lpc_ich mei_me i2c_i801 mfd_core 
> mei shpchp i2c_core tpm_tis wmi tpm ipmi_watchdog processor acpi_power_meter 
> thermal_sys acpi_pad button ipmi_si ipmi_poweroff ipmi_devintf 
> ipmi_msghandler autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid sg 
> sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common 
> crc32c_intel ahci libahci
> [3145152.948012]  ehci_pci xhci_hcd ehci_hcd libata ixgbe dca ptp usbcore 
> scsi_mod pps_core usb_common mdio
> [3145152.948091] CPU: 21 PID: 76919 Comm: cypher Not tainted 3.16.0-4-amd64 
> #1 Debian 3.16.7-ckt25-2+deb8u3
> [3145152.948158] Hardware name: Powerleader PR2760TG/X10DRT-PT, BIOS 2.0 
> 12/18/2015
> [3145152.948211] task: 880109e73470 ti: 880109f58000 task.ti: 
> 880109f58000
> [3145152.948265] RIP: 0010:[]  [] 
> update_cfs_rq_blocked_load+0x5/0x120
> [3145152.948336] RSP: 0018:880109f5ba90  EFLAGS: 00010086
> [3145152.948376] RAX:  RBX: 8805d54162b8 RCX: 
> 0001
> [3145152.948428] RDX: 7c00 RSI: bac33bc5 RDI: 
> 04e2
> [3145152.948481] RBP: 04e2 R08: 0001 R09: 
> b414
> [3145152.948533] R10: 001a R11: 024d R12: 
> 
> [3145152.948585] R13: 000fbfdbbac33bc4 R14:  R15: 
> 88087f852f00
> [3145152.948638] FS:  7f5586b1d700() GS:88087fac() 
> knlGS:
> [3145152.948697] CS:  0010 DS:  ES:  CR0: 80050033
> [3145152.950669] CR2: 0592 CR3: 0007320c4000 CR4: 
> 003407e0
> [3145152.952641] DR0:  DR1:  DR2: 
> 
> [3145152.954612] DR3:  DR6: fffe0ff0 DR7: 
> 0400
> [3145152.956504] Stack:
> [3145152.958341]  8109f134 880105bf1598 88087f852f78 
> 880109f5bb90
> [3145152.960253]    8109f1e7 
> 880109e73470
> [3145152.962190]  8808 8101b93d 8101b995 
> 880105bf1530
> [3145152.964120] Call Trace:
> [3145152.966053]  [] ? dequeue_task_fair+0x224/0x970
> [3145152.967990]  [] ? dequeue_task_fair+0x2d7/0x970
> [3145152.969896]  [] ? native_sched_clock+0x2d/0x80
> [3145152.971752]  [] ? sched_clock+0x5/0x10
> [3145152.973584]  [] ? move_task+0x1b/0x50
> [3145152.975400]  [] ? load_balance+0x455/0x850
> [3145152.977208]  [] ? pick_next_task_fair+0x3af/0x820
> [3145152.979038]  [] ? __schedule+0x106/0x700
> [3145152.980884]  [] ? futex_wait_queue_me+0xcc/0x130
> [3145152.982733]  [] ? futex_wait+0x162/0x260
> [3145152.984589]  [] ? wake_futex+0x5d/0x80
> [3145152.986414]  [] ? futex_wake+0x6f/0x120
> [3145152.988214]  [] ? do_futex+0xf2/0xb60
> [3145152.989963]  

Bug#836279: marked as done (linux-image-4.7.0-1-amd64: Intermittent hang on mackbook pro)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:25:04 -0700 (PDT)
with message-id <60984520.1c69fb81.c8a76.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #834011,
regarding linux-image-4.7.0-1-amd64: Intermittent hang on mackbook pro
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.)


-- 
834011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.7.2-1
Severity: important

Dear Maintainer,

Getting very similar hangs to the ones I reported in #834011, but this time I'm 
using the standard in tree
hid_apple driver that shipped with the kernel.

The probelm is that the machine just completely hangs up every now and then. 
When it hangs, the the mouse
and keyboard are unresponsive and the machine does not even respond to pings on 
the network.

If I boot to the 4.5.0 kernel everything is fine.s

Cheers,
Erik


-- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 
20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1 (2016-08-28)

** Command line:
\vmlinuz-4.7.0-1-amd64 initrd=\initrd.img-4.7.0-1-amd64

** Not tainted

** Kernel log:
[   27.514564] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[   27.514567] thunderbolt :07:00.0:   Max counters: 2
[   27.514570] thunderbolt :07:00.0:   NFC Credits: 0x70
[   27.514662] thunderbolt :07:00.0:  Port 11: 8086:156d (Revision: 0, TB 
Version: 1, Type: DP/HDMI (0xe0101))
[   27.514669] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[   27.514673] thunderbolt :07:00.0:   Max counters: 2
[   27.514677] thunderbolt :07:00.0:   NFC Credits: 0xf0
[   27.515538] thunderbolt :07:00.0:  Port 12: 8086:156d (Revision: 0, TB 
Version: 1, Type: DP/HDMI (0xe0101))
[   27.515546] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[   27.515550] thunderbolt :07:00.0:   Max counters: 2
[   27.515554] thunderbolt :07:00.0:   NFC Credits: 0xf0
[   27.515910] thunderbolt :07:00.0: 0:1: is connected, link is up (state: 
2)
[   27.516078] thunderbolt :07:00.0: initializing Switch at 0x1 (depth: 1, 
up port: 1)
[   27.516081] thunderbolt :07:00.0: old switch config:
[   27.516084] thunderbolt :07:00.0:  Switch: 8086:1549 (Revision: 0, TB 
Version: 1)
[   27.516087] thunderbolt :07:00.0:   Max Port Number: 2
[   27.516089] thunderbolt :07:00.0:   Config:
[   27.516091] thunderbolt :07:00.0:Upstream Port Number: 1 Depth: 1 
Route String: 0x1 Enabled: 1, PlugEventsDelay: 255ms
[   27.516094] thunderbolt :07:00.0:unknown1: 0x0 unknown4: 0x0
[   27.532046] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   27.532091] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by 
hardware/BIOS
[   27.535072] Adding 974844k swap on /dev/mapper/vg-swap.  Priority:-1 
extents:1 across:974844k SSFS
[   27.536541] thunderbolt :07:00.0: 1: reading drom (length: 0x7b)
[   27.547838] pstore: Registered efi as persistent store backend
[   27.606644] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: 
(null)
[   27.662711] fbcon: inteldrmfb (fb0) is primary device
[   27.663481] ACPI: Video Device [IGPU] (multi-head: yes  rom: no  post: no)
[   27.663694] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
[   27.864313] thunderbolt :07:00.0: 1: uid: 0x10002049dc190
[   27.864412] thunderbolt :07:00.0:  Port 0: 8086:1549 (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   27.864412] thunderbolt :07:00.0:   Max hop id (in/out): 7/7
[   27.864413] thunderbolt :07:00.0:   Max counters: 8
[   27.864413] thunderbolt :07:00.0:   NFC Credits: 0x70
[   27.864910] thunderbolt :07:00.0:  Port 1: 8086:1549 (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   27.864910] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[   27.864911] thunderbolt :07:00.0:   Max counters: 4
[   27.864911] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[   27.865010] thunderbolt :07:00.0:  Port 2: 8086:1549 (Revision: 0, TB 
Version: 1, Type: PCIe (0x100102))
[   27.865010] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[   27.865011] thunderbolt :07:00.0:   Max counters: 2
[   27.865011] thunderbolt :07:00.0:   NFC Credits: 0x70
[   27.865409] thunderbolt :07:00.0: 0:3: is unplugged (state: 7)
[   27.865708] thunderbolt :07:00.0: 1:2: PCIe port already activated, 
aborting
[   27.885750] 

Bug#834487: marked as done (linux-image bug)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:26:27 -0700 (PDT)
with message-id <60984573.1c69fb81.914e8.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #834487,
regarding linux-image bug
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.)


-- 
834487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Version: 3.16.7-ckt25-2 & 3.16.7-ckt25-2+deb8u3

we face kernel panic issue :

1. kernel  panic on 3.16.7-ckt25-2+deb8u3 ; 2 kinds of dumping informations
:

*A*:

[3145152.947164] BUG: unable to handle kernel NULL pointer dereference
at 0592
[3145152.947235] IP: [] update_cfs_rq_blocked_load+0x5/0x120
[3145152.947292] PGD 6708ba067 PUD 857130067 PMD 0
[3145152.947332] Oops:  [#1] SMP
[3145152.947360] Modules linked in: dccp_diag dccp tcp_diag udp_diag
inet_diag unix_diag af_packet_diag netlink_diag nls_utf8 fuse btrfs
xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs
libcrc32c crc32c_generic dm_mod 8021q garp stp mrp llc iTCO_wdt
iTCO_vendor_support x86_pkg_temp_thermal coretemp kvm_intel kvm
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper
ablk_helper cryptd pcspkr ast evdev joydev ttm drm_kms_helper drm
i2c_algo_bit lpc_ich mei_me i2c_i801 mfd_core mei shpchp i2c_core
tpm_tis wmi tpm ipmi_watchdog processor acpi_power_meter thermal_sys
acpi_pad button ipmi_si ipmi_poweroff ipmi_devintf ipmi_msghandler
autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid sg sd_mod
crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common
crc32c_intel ahci libahci
[3145152.948012]  ehci_pci xhci_hcd ehci_hcd libata ixgbe dca ptp
usbcore scsi_mod pps_core usb_common mdio
[3145152.948091] CPU: 21 PID: 76919 Comm: cypher Not tainted
3.16.0-4-amd64 #1 Debian 3.16.7-ckt25-2+deb8u3
[3145152.948158] Hardware name: Powerleader PR2760TG/X10DRT-PT, BIOS
2.0 12/18/2015
[3145152.948211] task: 880109e73470 ti: 880109f58000 task.ti:
880109f58000
[3145152.948265] RIP: 0010:[]  []
update_cfs_rq_blocked_load+0x5/0x120
[3145152.948336] RSP: 0018:880109f5ba90  EFLAGS: 00010086
[3145152.948376] RAX:  RBX: 8805d54162b8 RCX:
0001
[3145152.948428] RDX: 7c00 RSI: bac33bc5 RDI:
04e2
[3145152.948481] RBP: 04e2 R08: 0001 R09:
b414
[3145152.948533] R10: 001a R11: 024d R12:

[3145152.948585] R13: 000fbfdbbac33bc4 R14:  R15:
88087f852f00
[3145152.948638] FS:  7f5586b1d700() GS:88087fac()
knlGS:
[3145152.948697] CS:  0010 DS:  ES:  CR0: 80050033
[3145152.950669] CR2: 0592 CR3: 0007320c4000 CR4:
003407e0
[3145152.952641] DR0:  DR1:  DR2:

[3145152.954612] DR3:  DR6: fffe0ff0 DR7:
0400
[3145152.956504] Stack:
[3145152.958341]  8109f134 880105bf1598 88087f852f78
880109f5bb90
[3145152.960253]    8109f1e7
880109e73470
[3145152.962190]  8808 8101b93d 8101b995
880105bf1530
[3145152.964120] Call Trace:
[3145152.966053]  [] ? dequeue_task_fair+0x224/0x970
[3145152.967990]  [] ? dequeue_task_fair+0x2d7/0x970
[3145152.969896]  [] ? native_sched_clock+0x2d/0x80
[3145152.971752]  [] ? sched_clock+0x5/0x10
[3145152.973584]  [] ? move_task+0x1b/0x50
[3145152.975400]  [] ? load_balance+0x455/0x850
[3145152.977208]  [] ? pick_next_task_fair+0x3af/0x820
[3145152.979038]  [] ? __schedule+0x106/0x700
[3145152.980884]  [] ? futex_wait_queue_me+0xcc/0x130
[3145152.982733]  [] ? futex_wait+0x162/0x260
[3145152.984589]  [] ? wake_futex+0x5d/0x80
[3145152.986414]  [] ? futex_wake+0x6f/0x120
[3145152.988214]  [] ? do_futex+0xf2/0xb60
[3145152.989963]  [] ? SYSC_recvfrom+0xfb/0x140
[3145152.991694]  [] ? SyS_futex+0x6e/0x150
[3145152.993409]  [] ? system_call_fast_compare_end+0x10/0x15
[3145152.995110] Code: 00 00 00 e9 67 ff ff ff c7 42 08 ff ff ff ff ba
ff ff ff ff e9 56 ff ff ff 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f
1f 44 00 00 <48> 8b 87 b0 00 00 00 48 8b 80 a8 08 00 00 48 c1 e8 14 48
89 c2
[3145152.998715] RIP  [] update_cfs_rq_blocked_load+0x5/0x120
[3145153.000492]  RSP 
[3145153.002219] CR2: 0592


*B:*

[541280.120347] BUG: unable to handle kernel NULL pointer dereference
at   (null)
[541280.120379] IP: [<  

Bug#833326: marked as done (pulseaudio: Lenovo Ideapad 300 - volume of the internal microphone is very low)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:23:49 -0700 (PDT)
with message-id <609844d5.1c69fb81.590f0.f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #833326,
regarding pulseaudio: Lenovo Ideapad 300 - volume of the internal microphone is 
very low
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.)


-- 
833326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseaudio
Version: 9.0-1.1
Severity: normal

Dear Maintainer,

When using Skype, I've noticed that the volume of the internal microphone is
very low.

Configuring different volume levels for the two channels of the microphone
resolves the problem temporarily (for ex: left 0% right 100%). But as soon as a
software such as Skype tries to adapt the volume of the microphone, the volume
decreases again and the microphone becomes unusable.

Information about the configuration : http://www.alsa-
project.org/db/?f=42dbb27b8cefa74c1a6b837f7d80cd51523c5167

Sincerely,

Florent Mazzone



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.1-2
ii  libasound2-plugins   1.1.1-1
ii  libc62.23-4
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.8-1
ii  libfftw3-single3 3.3.4-2+b1
ii  libgcc1  1:6.1.1-10
ii  libice6  2:1.0.9-1+b1
ii  libltdl7 2.4.6-0.1
ii  liborc-0.4-0 1:0.4.25-1
ii  libpulse09.0-1.1
ii  libsm6   2:1.2.2-1+b1
ii  libsndfile1  1.0.25-10
ii  libsoxr0 0.1.2-1
ii  libspeexdsp1 1.2~rc1.2-1
ii  libstdc++6   6.1.1-10
ii  libsystemd0  230-7
ii  libtdb1  1.3.9-1
ii  libudev1 230-7
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.3-1
ii  libx11-xcb1  2:1.6.3-1
ii  libxcb1  1.11.1-1
ii  libxtst6 2:1.2.2-1+b1
ii  lsb-base 9.20160629
ii  pulseaudio-utils 9.0-1.1

Versions of packages pulseaudio recommends:
ii  pulseaudio-module-udev  9.0-1.1
ii  pulseaudio-module-x11   9.0-1.1
ii  rtkit   0.11-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3+b2
pn  pavumeter

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied 

Bug#834011: marked as done (linux-image-4.6.0-1-amd64: Intermittent hang on macboook pro)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:25:04 -0700 (PDT)
with message-id <60984520.1c69fb81.c8a76.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #834011,
regarding linux-image-4.6.0-1-amd64: Intermittent hang on macboook pro
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.)


-- 
834011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.4-1
Severity: normal

Dear Maintainer,

With this kernel version on this machine I get intermittent machine hangs.
The keyboard and mouse are unresponsive and the machine doesn't respond to
pings on the network (it normally does). The first thing I notice is that
the keyboard and/or mouse stop responding. If I am currently playing music
on youtube or something i get aa short (maybe as much as a second) looping
stutter of audio. The lockup has also happened when I'm not playing music.
It happened about 20 or so times, sometimes as much as 3 times a day.

If I boot to the linux-image-4.5.0-s-amd64 kernel it runs for days without
a single hang. Switching back to 4.6.4-1 and the hangs return.


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
\vmlinuz-4.6.0-1-amd64 initrd=\initrd.img-4.6.0-1-amd64

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[9.169316] intel_rapl: Found RAPL domain package
[9.169323] intel_rapl: Found RAPL domain core
[9.169327] intel_rapl: Found RAPL domain uncore
[9.169331] intel_rapl: Found RAPL domain dram
[9.191709] thunderbolt :07:00.0: 0: uid: 0x1001305f89270
[9.191806] thunderbolt :07:00.0:  Port 0: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.191814] thunderbolt :07:00.0:   Max hop id (in/out): 7/7
[9.191818] thunderbolt :07:00.0:   Max counters: 8
[9.191822] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.192487] thunderbolt :07:00.0:  Port 1: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.192495] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.192499] thunderbolt :07:00.0:   Max counters: 16
[9.192502] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.192978] thunderbolt :07:00.0:  Port 2: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.192986] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.192990] thunderbolt :07:00.0:   Max counters: 16
[9.192993] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.193483] thunderbolt :07:00.0:  Port 3: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.193491] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.193495] thunderbolt :07:00.0:   Max counters: 16
[9.193499] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.194262] thunderbolt :07:00.0:  Port 4: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.194269] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.194273] thunderbolt :07:00.0:   Max counters: 16
[9.194278] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.194577] thunderbolt :07:00.0:  Port 5: 8086:156d (Revision: 0, TB 
Version: 1, Type: NHI (0x2))
[9.194584] thunderbolt :07:00.0:   Max hop id (in/out): 11/11
[9.194587] thunderbolt :07:00.0:   Max counters: 16
[9.194591] thunderbolt :07:00.0:   NFC Credits: 0xf0
[9.194710] thunderbolt :07:00.0:  Port 6: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[9.194717] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[9.194721] thunderbolt :07:00.0:   Max counters: 2
[9.194724] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.194810] thunderbolt :07:00.0:  Port 7: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[9.194816] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[9.194821] thunderbolt :07:00.0:   Max counters: 2
[9.194825] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.194909] thunderbolt :07:00.0:  Port 8: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[9.194916] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[9.194920] thunderbolt :07:00.0:   Max counters: 2
[9.194924] thunderbolt :07:00.0:   

Bug#833295: marked as done (BUG: unable to handle kernel NULL pointer dereference at gen6_ppgtt_insert_entries+0xc9/0x160)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:23:14 -0700 (PDT)
with message-id <609844b2.1c69fb81.effef.3...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #833295,
regarding BUG: unable to handle kernel NULL pointer dereference at 
gen6_ppgtt_insert_entries+0xc9/0x160
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.)


-- 
833295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.4-1
Severity: normal
Tags: upstream

Hello,

got this crash with kernel 4.6.3, no idea on how to reproduce.

Aug  2 17:14:33 rieux kernel: [624938.589267] BUG: unable to handle kernel NULL
pointer dereference at   (null)
Aug  2 17:14:33 rieux kernel: [624938.589310] IP: []
gen6_ppgtt_insert_entries+0xc9/0x160 [i915]
Aug  2 17:14:33 rieux kernel: [624938.589376] PGD 1d5d67067 PUD 107361067 PMD 0
Aug  2 17:14:33 rieux kernel: [624938.589399] Oops:  [#1] SMP
Aug  2 17:14:33 rieux kernel: [624938.589415] Modules linked in: ufs(E) qnx4(E)
hfsplus(E) hfs(E) minix(E) ntfs(E) vfat(E) msdos(E) fat(E) jfs(E) xfs(E)
libcrc32c(E) dm_mod(E) cpuid(E) hmac(E) drbg(E) ansi_cprng
(E) ctr(E) ccm(E) hid_generic(E) hid_roccat_koneplus(E) hid_roccat(E)
hid_roccat_common(E) usbhid(E) hid(E) udf(E) crc_itu_t(E) loop(E)
usb_serial_simple(E) usbserial(E) xt_addrtype(E) br_netfilter(E) ipt_MASQUE
RADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_nat_ipv4(E) nf_nat(E)
nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_conntrack(E) nf_conntrack(E)
xt_CHECKSUM(E) iptable_mangle(E) ipt_REJECT(E) nf_reject_ipv4(E) x
t_tcpudp(E) overlay(E) tun(E) bridge(E) stp(E) llc(E) ebtable_filter(E)
ebtables(E) ip6table_filter(E) ip6_tables(E) iptable_filter(E) ip_tables(E)
x_tables(E) cpufreq_userspace(E) cpufreq_stats(E) cpufreq_conse
rvative(E) cpufreq_powersave(E) bnep(E) fuse(E) snd_hda_codec_hdmi(E)
binfmt_misc(E) arc4(E) iTCO_wdt(E) iTCO_vendor_support(E) intel_rapl(E)
x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel(E)
kvm(E) irqbypass(E) crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E)
uvcvideo(E) joydev(E) evdev(E) videobuf2_vmalloc(E) videobuf2_memops(E)
videobuf2_v4l2(E) serio_raw(E) iwlmvm(E) pcspkr(E) mac80211(
E) cdc_mbim(E) videobuf2_core(E) sg(E) videodev(E) media(E) cdc_wdm(E)
iwlwifi(E) cdc_acm(E) cdc_ncm(E) btusb(E) usbnet(E) btrtl(E) rtsx_pci_ms(E)
mii(E) btbcm(E) btintel(E) memstick(E) bluetooth(E) cfg80211(E)
wmi(E) thinkpad_acpi(E) nvram(E) rfkill(E) ac(E) battery(E)
snd_hda_codec_realtek(E) snd_hda_codec_generic(E) i915(E) snd_hda_intel(E)
snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) snd_pcm(E) snd_timer(E) snd(E)
 soundcore(E) drm_kms_helper(E) video(E) drm(E) mei_me(E) i2c_algo_bit(E)
mei(E) i2c_i801(E) lpc_ich(E) shpchp(E) tpm_tis(E) tpm(E) processor(E)
button(E) parport_pc(E) ppdev(E) lp(E) parport(E) autofs4(E) ext4(
E) ecb(E) crc16(E) jbd2(E) mbcache(E) btrfs(E) crc32c_generic(E) xor(E)
raid6_pq(E) sd_mod(E) crc32c_intel(E) rtsx_pci_sdmmc(E) mmc_core(E)
aesni_intel(E) aes_x86_64(E) glue_helper(E) lrw(E) gf128mul(E) ablk_hel
per(E) cryptd(E) psmouse(E) rtsx_pci(E) mfd_core(E) ahci(E) libahci(E)
libata(E) scsi_mod(E) ehci_pci(E) ehci_hcd(E) xhci_pci(E) xhci_hcd(E) e1000e(E)
ptp(E) pps_core(E) usbcore(E) usb_common(E) thermal(E) fjes(
E)
Aug  2 17:14:33 rieux kernel: [624938.590189] CPU: 1 PID: 28204 Comm: vlc
Tainted: GE   4.6.0-1-amd64 #1 Debian 4.6.3-1
Aug  2 17:14:33 rieux kernel: [624938.590211] Hardware name: LENOVO
20AQ007SIX/20AQ007SIX, BIOS GJET79WW (2.29 ) 09/03/2014
Aug  2 17:14:33 rieux kernel: [624938.590231] task: 8801d5d72180 ti:
8800a0cf8000 task.ti: 8800a0cf8000
Aug  2 17:14:33 rieux kernel: [624938.590249] RIP: 0010:[]
[] gen6_ppgtt_insert_entries+0xc9/0x160 [i915]
Aug  2 17:14:33 rieux kernel: [624938.590294] RSP: 0018:8800a0cfba20
EFLAGS: 00010246
Aug  2 17:14:33 rieux kernel: [624938.590308] RAX:  RBX:
 RCX: 
Aug  2 17:14:33 rieux kernel: [624938.590325] RDX: 880036c4f160 RSI:
8800a9d32000 RDI: 8800a0cfba38
Aug  2 17:14:33 rieux kernel: [624938.590342] RBP:  R08:
 R09: 880231512000
Aug  2 17:14:33 rieux kernel: [624938.590359] R10:  R11:
 R12: 880231512000
Aug  2 17:14:33 rieux kernel: [624938.590375] R13:  R14:
0001 R15: 8800a9d32ffc
Aug  2 17:14:33 rieux kernel: [624938.590393] FS:  7fb7aff2f700()
GS:88023e24() 

Bug#833247: marked as done (linux-image-3.16.0-4-amd64: DRM/i915 "blanks" display and dumps trace)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:22:25 -0700 (PDT)
with message-id <60984481.1c69fb81.b5996.0...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #833247,
regarding linux-image-3.16.0-4-amd64: DRM/i915 "blanks" display and dumps trace
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.)


-- 
833247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3
Severity: normal

Dear Maintainer,


   * What led up to the situation?
I vagually correlate it to a prolonged "runtime" of my notebook. I don't
power it down ever, but only put it into suspend mode. Currently it has
14 days of uptime, but it happens to have 100 days or more.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I honestly don't know.

   * What was the outcome of this action?
The screen goes "blank" in a strange way: first it blanks-black, then 
after 5-11 seconds it becomes "white becklited" from top left corner
in a "hash pattern" with 1mm grid size. When the display blanks black, I
can bring it up to normal display "mode" with a mouse (but not with a
keyboard).  When it becomes "grid-patterend", only suspend-by-closing
the lid helps.

   * What outcome did you expect instead?
obviosly - normal operation.



-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)

** Command line:
placeholder root=/dev/mapper/nowszy-root ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[624084.880378] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.889872] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.889878] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088
[624084.889880] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70084
[624084.889882] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.890881] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.890886] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088
[624084.890888] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70084
[624084.890890] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.899840] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.899844] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088
[624084.899846] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70084
[624084.899848] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.909759] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.909763] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088
[624084.909766] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70084
[624084.909768] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.910762] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.910766] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088
[624084.910768] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70084
[624084.910770] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.919841] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.919845] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088
[624084.919847] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70084
[624084.919850] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.928905] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.928909] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088
[624084.928912] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70084
[624084.928914] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70084
[624084.938809] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed 
register before writing to 70088
[624084.938815] [drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 70088

Processed: Re: Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #833035 [src:linux] linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware
Added tag(s) moreinfo.

-- 
833035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi,

On Thu, Oct 19, 2017 at 05:29:41PM -0400, Paul Fox wrote:
> chris wrote:
>  > On 10/16/2017 11:32 AM, Paul Fox wrote:
>  > > ben, chris -- regarding this bug:
>  > >   Bug#833035:  linux-image-3.16.0-4-amd64:  Keyspan USB serial adapter
>  > >   USA-49WLC failed to load firmware
>  > >
>  > > whatever became of the proposed patch.  i'm running ubuntu 16.04.3,
>  > > kernel 4.4.0-97-generic, and the failure is still present there.
>  > >
>  > > paul
>  > > =--
>  > >   paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 50.2 
> degrees)
>  > >
>  > >
>  > > .
>  > >
>  > The patch provided fixed the bug.   I think I responded with the news.
> 
> yes -- sorry for not being clear.  i was wondering whether the fix had
> gone upstream, and if not, why not.

Has the fix been upstreamed or the issue fixed in meanwhile with a
recent kernel?

Regards,
Salvatore

Bug#833009: marked as done (linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:15:58 -0700 (PDT)
with message-id <609842fe.1c69fb81.95c64.7...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #833009,
regarding linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA 
because of i915 and i2c_designware
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.)


-- 
833009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.4-1
Severity: normal
Tags: upstream

I have problems that I can not suspend or hibernate my E200HA.  After
some reserach I found this Web page:
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

Maybe the suspend is not supported, but the hibernate should, because
of this message on kern.log:

Jul 28 22:56:00 lal kernel: [0.472724] ACPI: (supports S0 S4 S5)

So, doing some extra research I suspect the problem is in the module
i915 and on the module i2c_designware.  Because switching to a text
console and issuing the command: "echo disk > /sys/power/state" the
system hibernate and awakes when I request.  But it awakes without
keyboard and with following messages on the console:

[   50.827873] [drm] stuck on blitter ring
[   50.834932] [drm] stuck on bsd ring
[   50.841830] [drm] stuck on video enhancement ring
[   50.851177] [drm] GPU HANG: ecode 8:0:0x7a2af415, reason: Ring hung, action: 
reset
[   50.854730] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[   50.858380] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[   50.860886] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[   50.863336] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[   50.865839] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   50.868532] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, 
banning!
[   50.873485] drm/i915: Resetting chip after gpu hang
[   51.729188] IPv6: ADDRCONF(NETDEV_CHANGE): enx0019fd4cb596: link becomes 
ready
[   51.737806] asix 1-4:1.0 enx0019fd4cb596: link up, 100Mbps, full-duplex, lpa 
0xCDE1
[  129.340496] i2c_designware 808622C1:00: timeout in enabling adapter
[  130.348085] i2c_designware 808622C1:00: controller timed out
[  130.355959] i2c_designware 808622C1:00: Unknown Synopsys component type: 
0x

Kind regards
Jose M Calhariz


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n initcall_debug 
no_console_suspend

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   49.008511] call regulatory.0+ returned 0 after 0 usecs
[   49.010919] calling  intel_backlight+ @ 2728, parent: card0-eDP-1
[   49.013223] call intel_backlight+ returned 0 after 0 usecs
[   49.015521] calling  input6+ @ 2728, parent: LNXVIDEO:00
[   49.017797] call input6+ returned 0 after 0 usecs
[   49.020078] calling  input7+ @ 2728, parent: pcspkr
[   49.021968] call input7+ returned 0 after 17 usecs
[   49.023843] calling  input8+ @ 2728, parent: i2c-ELAN0100:00
[   49.025720] call input8+ returned 0 after 0 usecs
[   49.027601] calling  coretemp.0+ @ 2728, parent: platform
[   49.029487] call coretemp.0+ returned 0 after 0 usecs
[   49.031392] calling  asus-nb-wmi+ @ 2728, parent: platform
[   49.033284] call asus-nb-wmi+ returned 0 after 1 usecs
[   49.035181] calling  input9+ @ 2728, parent: asus-nb-wmi
[   49.037073] call input9+ returned 0 after 0 usecs
[   49.038960] calling  input10+ @ 2728, parent: 0018:0B05:8585.0001
[   49.040893] call input10+ returned 0 after 19 usecs
[   49.042822] calling  input10::numlock+ @ 2728, parent: input10
[   49.044753] call input10::numlock+ returned 0 after 0 usecs
[   49.046684] calling  input10::capslock+ @ 2728, parent: input10
[   49.048625] call input10::capslock+ returned 0 after 0 usecs
[   49.050570] calling  input10::scrolllock+ @ 2728, parent: input10
[   49.052528] call input10::scrolllock+ returned 0 after 0 usecs
[   49.054491] calling  input10::compose+ @ 2728, parent: input10
[   49.056460] call input10::compose+ returned 0 after 0 usecs
[   49.058429] calling  input10::kana+ @ 2728, parent: 

Processed: forcibly merging 843764 832175

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 843764 832175
Bug #843764 {Done: car...@debian.org} [src:linux] WARNING: fpu__restore
Bug #843764 {Done: car...@debian.org} [src:linux] WARNING: fpu__restore
Marked as found in versions linux/4.6.4-1.
Bug #832175 {Done: car...@debian.org} [src:linux] WARNING fpu/internal.h:532 
fpu__restore
Set Bug forwarded-to-address to 'linux-rt-us...@vger.kernel.org'.
Marked as found in versions linux/4.8.5-1.
Merged 832175 843764
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
832175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832175
843764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#832175: marked as done (WARNING fpu/internal.h:532 fpu__restore)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:13:53 -0700 (PDT)
with message-id <60984281.1c69fb81.f52a2.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #832175,
regarding WARNING fpu/internal.h:532 fpu__restore
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.)


-- 
832175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.6.0-1-rt-amd64
Version: 4.6.4-1


Hi,

I decided to give linux-image-rt a try and after a while the kernel displayed 
the following warning message.  The kernel is marked as tainted.  It is not the 
result of a previous fault, but the result of this error:

[1.250921] scsi_mod: module verification failed: signature and/or required 
key missing - tainting kernel

(I read in another bug report that this error is expected until module 
signatures are sorted out in Debian)

Here is the warning message:

[234280.124019] [ cut here ]
[234280.124024] WARNING: CPU: 0 PID: 9306 at 
/build/linux-aOJbQa/linux-4.6.4/debian/build/source_rt/arch/x86/include/asm/fpu/internal.h:532
 fpu__restore+0xbd/0x130
[234280.124045] Modules linked in: xt_multiport(E) cpufreq_conservative(E) 
cpufreq_powersave(E) cpufreq_userspace(E) cpufreq_stats(E) ip6table_filter(E) 
ip6_tables(E) iptable_filter(E) ip_tables(E) x_tables(E) coretemp(E) 
kvm_intel(E) kvm(E) iTCO_wdt(E) iTCO_vendor_support(E) ppdev(E) irqbypass(E) 
evdev(E) dcdbas(E) snd_hda_codec_analog(E) snd_hda_codec_generic(E) pcspkr(E) 
serio_raw(E) i2c_i801(E) lpc_ich(E) mfd_core(E) sg(E) snd_hda_intel(E) 
snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) snd_pcm_oss(E) i915(E) 
snd_mixer_oss(E) snd_pcm(E) snd_timer(E) snd(E) soundcore(E) video(E) 
drm_kms_helper(E) drm(E) shpchp(E) wmi(E) i2c_algo_bit(E) acpi_cpufreq(E) 
8250_fintek(E) parport_pc(E) parport(E) mei_me(E) mei(E) button(E) tpm_tis(E) 
tpm(E) processor(E) binfmt_misc(E) sunrpc(E) ib_iser(E) rdma_cm(E) iw_cm(E)
[234280.124068]  ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) configfs(E) 
iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) drbd(E) 
lru_cache(E) loop(E) dm_crypt(E) dm_mod(E) autofs4(E) ext4(E) ecb(E) 
glue_helper(E) lrw(E) gf128mul(E) ablk_helper(E) cryptd(E) aes_x86_64(E) 
crc16(E) jbd2(E) mbcache(E) btrfs(E) raid10(E) raid456(E) async_raid6_recov(E) 
async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) 
libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E) multipath(E) linear(E) 
md_mod(E) ses(E) enclosure(E) scsi_transport_sas(E) hid_generic(E) usbhid(E) 
hid(E) uas(E) usb_storage(E) sd_mod(E) psmouse(E) ahci(E) libahci(E) 
uhci_hcd(E) ehci_pci(E) ehci_hcd(E) ata_generic(E) usbcore(E) usb_common(E) 
e1000e(E) libata(E) ptp(E) pps_core(E) scsi_mod(E)
[234280.124070] CPU: 0 PID: 9306 Comm: bash Tainted: GE   
4.6.0-1-rt-amd64 #1 Debian 4.6.4-1
[234280.124071] Hardware name: Dell Inc. OptiPlex 780 /0C27VV, 
BIOS A08 01/21/2011
[234280.124073]  0286 8b7a5666 81323946 

[234280.124074]   8107e6f7 8800d8b7d180 
8800d8b7c600
[234280.124075]  8800d8b7d180 8800d8b7d1c0 ffa81a00 
0240
[234280.124075] Call Trace:
[234280.124080]  [] ? dump_stack+0x5c/0x86
[234280.124082]  [] ? __warn+0xd7/0xf0
[234280.124083]  [] ? fpu__restore+0xbd/0x130
[234280.124085]  [] ? __fpu__restore_sig+0x272/0x470
[234280.124087]  [] ? ia32_restore_sigcontext+0x14f/0x170
[234280.124088]  [] ? sys32_sigreturn+0xc6/0xe0
[234280.124091]  [] ? do_int80_syscall_32+0x52/0xa0
[234280.124092]  [] ? entry_INT80_compat+0x36/0x50
[234280.124093] ---[ end trace 0002 ]---


-- 
Laurent.
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#831613: marked as done (linux-image-4.6.0-0.bpo.1-686-pae: Bug in cpufreq driver)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:10:41 -0700 (PDT)
with message-id <609841c1.1c69fb81.a0dbd.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #831613,
regarding linux-image-4.6.0-0.bpo.1-686-pae: Bug in cpufreq driver
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.)


-- 
831613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.3-1~bpo8+1
Severity: normal

Dear Maintainer,

After a resume from hibernation for this computer, a crash of cpufreq driver
 is generated with report in syslog.
No other effect was seen.
Perhaps, cpufreq is disabled for all the session. I will verify that.

All others functions seem to work fine.

This issue occurred on each time that the system is waking after hibernation. 

-- Package-specific info:
** Version:
Linux version 4.6.0-0.bpo.1-686-pae (debian-kernel@lists.debian.org) (gcc 
version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.6.3-1~bpo8+1 (2016-07-13)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-0.bpo.1-686-pae 
root=UUID=2ed3bc82-5cc0-4529-a13c-2e6f80b5b588 ro resume=/dev/sdb1 quiet

** Tainted: WE (8704)
 * Taint on warning.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[ 6571.518806] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 6571.525652] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6575.466579] Syncing filesystems ... done.
[ 6575.467671] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 6575.470210] PM: Marking nosave pages: [mem 0x-0x0fff]
[ 6575.470225] PM: Marking nosave pages: [mem 0x0009f000-0x000f]
[ 6575.470248] PM: Basic memory bitmaps created
[ 6575.470465] PM: Preallocating image memory... done (allocated 110707 pages)
[ 6580.488736] PM: Allocated 442828 kbytes in 5.01 seconds (88.38 MB/s)
[ 6580.488743] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 6580.490618] Suspending console(s) (use no_console_suspend to debug)
[ 6580.804374] PM: freeze of devices complete after 313.728 msecs
[ 6580.820197] PM: late freeze of devices complete after 15.803 msecs
[ 6580.821464] PM: noirq freeze of devices complete after 1.255 msecs
[ 6580.821518] ACPI: Preparing to enter system sleep state S4
[ 6580.823537] ACPI : EC: EC stopped
[ 6580.823539] PM: Saving platform NVS memory
[ 6580.824595] Disabling non-boot CPUs ...
[ 6580.824960] Broke affinity for irq 1
[ 6580.824972] Broke affinity for irq 9
[ 6580.824979] Broke affinity for irq 12
[ 6580.824990] Broke affinity for irq 15
[ 6580.824996] Broke affinity for irq 16
[ 6580.825016] Broke affinity for irq 23
[ 6580.826174] smpboot: CPU 1 is now offline
[ 6580.837185] PM: Creating hibernation image:
[ 6580.840014] PM: Need to copy 102363 pages
[ 6580.840014] PM: Normal pages needed: 86577 + 1024, available pages: 141138
[ 6580.840014] PM: Restoring platform NVS memory
[ 6580.840014] ACPI : EC: EC started
[ 6580.840014] Enabling non-boot CPUs ...
[ 6580.856700] x86: Booting SMP configuration:
[ 6580.856703] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 6580.826071] Initializing CPU#1
[ 6580.826071] Disabled fast string operations
[ 6580.857311]  cache: parent cpu1 should not be sleeping
[ 6580.857956] CPU1 is up
[ 6580.858577] ACPI: Waking up from system sleep state S4
[ 6581.160487] [ cut here ]
[ 6581.160501] WARNING: CPU: 0 PID: 2308 at 
/home/zumbi/linux-4.6.3/drivers/cpufreq/cpufreq.c:2173 
cpufreq_update_policy+0xe5/0x140
[ 6581.160570] Modules linked in: hmac(E) drbg(E) ansi_cprng(E) ctr(E) ccm(E) 
binfmt_misc(E) ip6t_REJECT(E) nf_reject_ipv6(E) xt_hl(E) ip6t_rt(E) 
nf_conntrack_ipv6(E) nf_defrag_ipv6(E) ipt_REJECT(E) nf_reject_ipv4(E) 
xt_limit(E) xt_tcpudp(E) xt_addrtype(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) 
xt_conntrack(E) ip6table_filter(E) ip6_tables(E) nf_conntrack_netbios_ns(E) 
nf_conntrack_broadcast(E) nf_nat_ftp(E) nf_nat(E) nf_conntrack_ftp(E) 
nf_conntrack(E) iptable_filter(E) ip_tables(E) x_tables(E) iTCO_wdt(E) 
iTCO_vendor_support(E) arc4(E) rt2800pci(E) uvcvideo(E) rt2800mmio(E) 
videobuf2_vmalloc(E) videobuf2_memops(E) rt2800lib(E) videobuf2_v4l2(E) 
rt2x00pci(E) videobuf2_core(E) rt2x00mmio(E) rt2x00lib(E) videodev(E) 
eeprom_93cx6(E) media(E) mac80211(E) i915(E) cfg80211(E) evdev(E) joydev(E) 
coretemp(E)
[ 6581.160638]  pcspkr(E) serio_raw(E) eeepc_laptop(E) sparse_keymap(E) 
lpc_ich(E) i2c_i801(E) mfd_core(E) crc_ccitt(E) rng_core(E) rfkill(E) 
snd_hda_codec_realtek(E) 

Bug#831875: marked as done (linux-image-3.16.0-0.bpo.4-amd64: endless "NMI backtrace" loop)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:11:09 -0700 (PDT)
with message-id <609841dd.1c69fb81.d433.2...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #831875,
regarding linux-image-3.16.0-0.bpo.4-amd64: endless "NMI backtrace" loop
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.)


-- 
831875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3~bpo70+1
Severity: normal

The system is running the wheezy release.

After some fibre channel multipathing issues, my system ended up
endlessly printing messages like the one below for each of 32 cpus,
every 3 sec. However the problem occurs in more common situations
than this - it sometimes occurs during boot-up, both from cold start
and warm reboot.

This seems to be worse in the 3.16 kernels, we never had issues like
this with 3.2 but had to move up to 3.16 for other issues related to
power management.

The BIOS has been adjusted to turn off all C state support,
the system runs at maximum performance.

Do you have any advice on measures to track this down more precisely?


-- Package-specific info:
** Version:
Linux version 3.16.0-0.bpo.4-amd64 (debian-kernel@lists.debian.org) (gcc 
version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3~bpo70+1 
(2016-07-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-0.bpo.4-amd64 
root=UUID=084a5068-b421-47bb-8eb3-f62516498242 ro console=ttyS0,9600n8 
console=tty0

** Not tainted


[205127.516687] NMI backtrace for cpu 28
[205127.516692] CPU: 28 PID: 0 Comm: swapper/28 Not tainted 
3.16.0-0.bpo.4-amd64 #1 Debian 3.16.7-ckt25-2+deb8u3~bpo70+1
[205127.516693] Hardware name: Dell Inc. PowerEdge R820/04K5X5, BIOS 1.5.0 
03/08/2013
[205127.516695] task: 880c0ea20310 ti: 880c0ea2c000 task.ti: 
880c0ea2c000
[205127.516697] RIP: 0010:[]  [] 
intel_idle+0xcc/0x160
[205127.516702] RSP: 0018:880c0ea2fe18  EFLAGS: 0046
[205127.516704] RAX: 0030 RBX: 0010 RCX: 
0001
[205127.516705] RDX:  RSI: 880c0ea2ffd8 RDI: 
001c
[205127.516706] RBP: 0005 R08:  R09: 
5d20
[205127.516707] R10:  R11: 0001030e17d1 R12: 
0030
[205127.516708] R13: 0004 R14: 0005 R15: 
880c0ea2c000
[205127.516710] FS:  () GS:880c3fbc() 
knlGS:
[205127.516712] CS:  0010 DS:  ES:  CR0: 80050033
[205127.516713] CR2: 7f6452f3de30 CR3: 01811000 CR4: 
000407e0
[205127.516714] Stack:
[205127.516715]   001c00f38f2d 8101e085 
e8f4003c0308
[205127.516718]  babd0c6ce19b 8189b6f0 8189b520 
8140e8e1
[205127.516720]   00f38f2d d740 
818e0540
[205127.516723] Call Trace:
[205127.516724]  [] ? read_tsc+0x5/0x20
[205127.516729]  [] ? cpuidle_enter_state+0x51/0xf0
[205127.516732]  [] ? cpu_startup_entry+0x34a/0x4b0
[205127.516736]  [] ? start_secondary+0x218/0x2d0
[205127.516739] Code: 31 d2 65 48 8b 34 25 48 b8 00 00 48 89 d1 48 8d 86 38 c0 
ff ff 0f 01 c8 48 8b 86 38 c0 ff ff a8 08 75 08 b1 01 4c 89 e0 0f 01 c9 <65> 48 
8b 04 25 48 b8 00 00 f0 80 a0 3a c0 ff ff df 0f ae f0 48

** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge R820
product_version:
chassis_vendor: Dell Inc.
chassis_version:
bios_vendor: Dell Inc.
bios_version: 1.5.0
board_vendor: Dell Inc.
board_name: 04K5X5
board_version: A06

** Loaded modules:
autofs4
nfsd
nfsv3
nfs_acl
rpcsec_gss_krb5
auth_rpcgss
oid_registry
nfsv4
dns_resolver
nfs
lockd
sunrpc
fscache
xfs
libcrc32c
dm_round_robin
loop
dm_multipath
scsi_dh
x86_pkg_temp_thermal
intel_powerclamp
intel_rapl
coretemp
kvm_intel
kvm
crct10dif_pclmul
crc32_pclmul
ttm
drm_kms_helper
aesni_intel
drm
aes_x86_64
iTCO_wdt
mei_me
lrw
i2c_algo_bit
iTCO_vendor_support
gf128mul
sb_edac
glue_helper
lpc_ich
mei
i2c_core
ioatdma
dcdbas
mfd_core
edac_core
ablk_helper
pcspkr
evdev
joydev
processor
shpchp
acpi_pad
ipmi_si
tpm_tis
button
thermal_sys
dca
cryptd
ipmi_msghandler
wmi
acpi_power_meter
tpm
ext4
crc16
mbcache
jbd2
dm_mod
hid_generic
usbhid
hid
sg
sr_mod
cdrom
sd_mod
ehci_pci
crc_t10dif
ehci_hcd
crct10dif_common
ahci
qla2xxx
libahci
usbcore
usb_common
scsi_transport_fc
tg3
libata
megaraid_sas
scsi_tgt
ptp
crc32c_intel
scsi_mod
pps_core
libphy




Vince
-- 
--- End Message ---
--- Begin Message 

Bug#831416: marked as done (linux-image-4.6.0-1-amd64: No link on USB3-hub-ethernet adapter Realtek 8153, using r8152)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:09:22 -0700 (PDT)
with message-id <60984172.1c69fb81.184ff.2...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #831416,
regarding linux-image-4.6.0-1-amd64: No link on USB3-hub-ethernet adapter 
Realtek 8153, using r8152
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.)


-- 
831416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.3-1
Severity: normal

Dear Maintainer,

I'll start with a solution as it is simple to explain:

there is new upstream r8152 driver (v2.06 2016/2/23) which fixes the issue:
http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1=13=56=5=4=3=false

Now the issue:
I have USB3.0 hub with built-in Realtek 8153 ethernet adapter (served by r8152 
driver).
When I plug it into USB2.0 socket it works out-of-the-box automatically: 
ethtool reports "Link detected: yes" and network-manager acquires IP etc..
When I plug it into USB3.0 socket, the device is correctly detected and 
configured (r8152 is loaded and the adapter appears in usbview etc),
but the adapter refuses to sense any network cable, i.e. ethtool reports "Link 
detected: no", consequently the network does not work
(dhclient sends requests but does not get any response).
I cannot use the noted USB2.0 socket for long because this socket is primarily 
used by the charger (it's a laptop without ethernet),
so I need it to work with remaining USB3.0 sockets.

The solution was to download the new driver (linked above), compile, install 
and copy 50-usb-realtek-net.rules into /lib/udev/rules.d -- then it works 
automatically.
So it would be nice if this driver version was included into distribution.

I also found a related problem: 
https://bugzilla.redhat.com/show_bug.cgi?id=1236679
but their workaround did not help me (I tried without tlp and with their fix -- 
the symptoms were the same).

Marius

-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.3-1 (2016-07-04)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=b6485691-c9ee-4aad-85ba-4d9a8032e2c7 ro quiet

** Tainted: POE (12289)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[ 3641.426334] usb 1-5.1: Manufacturer: Realtek
[ 3641.426336] usb 1-5.1: SerialNumber: 0100
[ 3641.497319] usb 1-5.1: reset high-speed USB device number 22 using xhci_hcd
[ 3641.615887] r8152 1-5.1:1.0 eth0: v1.08.3
[ 3641.658110] r8152 1-5.1:1.0 enx00e04c680005: renamed from eth0
[ 3641.691076] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680005: link is not ready
[ 3641.737063] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680005: link is not ready
[ 3644.326690] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c680005: link becomes 
ready
[ 3712.823926] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic 
update failure on pipe A
[ 4009.221118] usbcore: deregistering interface driver r8152
[ 4091.423337] usb 1-5.1: reset high-speed USB device number 22 using xhci_hcd
[ 4091.598695] r8152 1-5.1:1.0 eth0: v2.06.0 (2016/01/14)
[ 4091.598699] r8152 1-5.1:1.0 eth0: This product is covered by one or more of 
the following patents:
US6,570,884, US6,115,776, and US6,327,625.
   
[ 4091.598750] usbcore: registered new interface driver r8152
[ 4091.599333] r8152 1-5.1:1.0 enx00e04c680005: renamed from eth0
[ 4091.623307] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680005: link is not ready
[ 4091.649105] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680005: link is not ready
[ 4094.461390] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c680005: link becomes 
ready
[ 4159.601904] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.601941] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.601986] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.602025] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.602068] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.602115] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.602161] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.602200] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.602251] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.602290] r8152 1-5.1:1.0 enx00e04c680005: Rx status -71
[ 4159.603215] usb 1-5: USB disconnect, device number 21
[ 4159.603220] usb 1-5.1: USB 

Bug#831592: marked as done (linux-image-686-pae: bluetooth device JBL Charge 3 connects and immediately crashes in hci_conn_timeout)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:09:55 -0700 (PDT)
with message-id <60984193.1c69fb81.6a5d.0...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #831592,
regarding linux-image-686-pae: bluetooth device JBL Charge 3 connects and 
immediately crashes in hci_conn_timeout
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.)


-- 
831592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-686-pae
Version: 3.16+63
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   I'm trying connect JBL Charge 3 audio device via bluetooth to my PC with 
debian jessie through Gnome 3 desktop.
   2. This device is Bus 001 Device 007: ID 0a5c:21e6 Broadcom Corp. BCM20702 
Bluetooth 4.0 [ThinkPad]
   3. I obtained firmware from Windows: BCM20702A1_001.002.014.0449.0462.hex
   4. Converted hex by https://github.com/jessesung/hex2hcd to hcd and copied 
to /lib/firmware/brcm/BCM20702A0-0a5c-21e6.hcd
   5. reboot
   6. After trying to pairing the device in dmesg the following stacktrace 
appeared:

[  209.562653] [ cut here ]
[  209.562672] WARNING: CPU: 0 PID: 2264 at 
/build/linux-l36MuF/linux-3.16.7-ckt25/net/bluetooth/hci_conn.c:296 
hci_conn_timeout+0x49/0x260 [bluetooth]()
[  209.562673] Modules linked in: ctr ccm ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables bnep tun pci_stub vboxpci(O) vboxnetadp(O) 
vboxnetflt(O) vboxdrv(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd 
fscache sunrpc cdc_mbim ecb cdc_ncm uvcvideo videobuf2_vmalloc videobuf2_memops 
btusb videobuf2_core usbnet v4l2_common bluetooth cdc_wdm mii cdc_acm videodev 
media 6lowpan_iphc snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support 
x86_pkg_temp_thermal snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_controller arc4 intel_powerclamp intel_rapl iwldvm mac80211 coretemp 
kvm_intel iwlwifi ac kvm cfg80211 joydev serio_raw pcspkr battery shpchp 
lpc_ich mfd_core evdev i2c_i801 mei_me mei thinkpad_acpi nvram tpm_tis rfkill 
tpm snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
[  209.562710]  processor vmhgfs(O) vmw_vmci fuse parport_pc ppdev 
intel_smartconnect lp parport autofs4 ext4 crc16 mbcache jbd2 algif_skcipher 
af_alg hid_logitech_dj usbhid hid dm_crypt dm_mod usb_storage sg sd_mod 
crc_t10dif crct10dif_generic crct10dif_common crc32_pclmul crc32c_intel i915 
i2c_algo_bit ahci aesni_intel aes_i586 xts lrw gf128mul ablk_helper cryptd 
ehci_pci xhci_hcd ehci_hcd libahci psmouse libata sdhci_pci sdhci mmc_core 
drm_kms_helper scsi_mod usbcore drm usb_common i2c_core thermal wmi video 
thermal_sys button
[  209.562740] CPU: 0 PID: 2264 Comm: kworker/u17:2 Tainted: G   O  
3.16.0-4-686-pae #1 Debian 3.16.7-ckt25-2+deb8u3
[  209.562742] Hardware name: LENOVO 34447PG/34447PG, BIOS G6ETA3WW (2.63 ) 
02/19/2014
[  209.562749] Workqueue: hci0 hci_conn_timeout [bluetooth]
[  209.562750]   ea847ebc c1479ea7  f9473b0c c1056c94 c1553c18 

[  209.562754]  08d8 f9473b0c 0128 f943cab9 f943cab9 0009 f05c5c98 

[  209.562757]  f05c5c00 ea847ecc c1056d52 0009  ea847f00 f943cab9 
c1715000
[  209.562760] Call Trace:
[  209.562765]  [] ? dump_stack+0x55/0x6e
[  209.562769]  [] ? warn_slowpath_common+0x84/0xa0
[  209.562776]  [] ? hci_conn_timeout+0x49/0x260 [bluetooth]
[  209.562781]  [] ? hci_conn_timeout+0x49/0x260 [bluetooth]
[  209.562783]  [] ? warn_slowpath_null+0x22/0x30
[  209.562789]  [] ? hci_conn_timeout+0x49/0x260 [bluetooth]
[  209.562792]  [] ? process_one_work+0x115/0x380
[  209.562794]  [] ? pwq_activate_delayed_work+0x2d/0x70
[  209.562796]  [] ? worker_thread+0xed/0x490
[  209.562799]  [] ? __wake_up_locked+0x1f/0x30
[  209.562801]  [] ? create_and_start_worker+0x50/0x50
[  209.562803]  [] ? kthread+0x9b/0xb0
[  209.562806]  [] ? ret_from_kernel_thread+0x21/0x30
[  209.562808]  [] ? kthread_create_on_node+0x110/0x110
[  209.562810] ---[ end trace 1a5fd7014c81093f ]---



-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-686-pae depends on:
ii  linux-image-3.16.0-4-686-pae  3.16.7-ckt25-2+deb8u3

Bug#830992: marked as done (pulseaudio: no sound with snd_hda_codec_realtek ALC880)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:08:58 -0700 (PDT)
with message-id <6098415a.1c69fb81.67c85.5...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #830992,
regarding pulseaudio: no sound with snd_hda_codec_realtek ALC880
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.)


-- 
830992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseaudio
Version: 9.0-1.1
Severity: normal

Dear Maintainer,
on my old desktop Fujitsu Siemens Scaleo T D1826  I have installed stretch 
release from dvd1 (xfce desktop).
Before it there was installed jessie (gnome+xfce) and everything was running 
(sound was ok).

Some informations:

# lspci -vvnn

00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) High Definition Audio Controller [8086:2668] (rev 03)
Subsystem: Fujitsu Technology Solutions 82801FB/FBM/FR/FW/FRW (ICH6 
Family) High Definition Audio Controller [1734:1066]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- # This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no

;; extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log 
--log-time=1
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = no
; lfe-crossover-freq = 0

; flat-volumes = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 44100
; alternate-sample-rate = 48000
; 

Bug#830841: marked as done (linux-image-4.1.0-1-amd64: something bad happened when working with filesystem on loop dev on external harddrive with ntfs)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:08:18 -0700 (PDT)
with message-id <60984132.1c69fb81.385f.0...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #830841,
regarding linux-image-4.1.0-1-amd64: something bad happened when working with 
filesystem on loop dev on external harddrive with ntfs
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.)


-- 
830841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.1.3-1
Severity: normal

Dear Maintainer,

i am not sure if this is is the right place for that kind of problem, its my 
first bugreport regarding of kernel not of userland thingies. 

   * What led up to the situation?
 using some ext4 formated file (loop0) on an external harddiskdrive with 
ntfs on it
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 writing data to it, exedently removed usb cable while that, unmounted it, 
tryed to remount it
   * What was the outcome of this action?
 i wasnt able to remount it again, insted ive got an oops in dmesg
   * What outcome did you expect instead?
 maybe some jornal restore or the message that i should use fsck but not 
this


here is a extract out of my dmesg:

[765002.356113] usb 1-1: new high-speed USB device number 7 using ehci-pci
[765002.490331] usb 1-1: New USB device found, idVendor=0480, idProduct=a00e
[765002.490340] usb 1-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
[765002.490346] usb 1-1: Product: External USB 3.0
[765002.490352] usb 1-1: Manufacturer: TOSHIBA
[765002.490356] usb 1-1: SerialNumber: 20140904007053F
[765002.491607] usb-storage 1-1:1.0: USB Mass Storage device detected
[765002.491983] scsi host20: usb-storage 1-1:1.0
[765003.493145] scsi 20:0:0:0: Direct-Access TOSHIBA  External USB 3.0 0
PQ: 0 ANSI: 6
[765003.493951] sd 20:0:0:0: Attached scsi generic sg2 type 0
[765003.497785] sd 20:0:0:0: [sdd] 976773168 512-byte logical blocks: (500 
GB/465 GiB)
[765003.500538] sd 20:0:0:0: [sdd] Write Protect is off
[765003.500543] sd 20:0:0:0: [sdd] Mode Sense: 43 00 00 00
[765003.501562] sd 20:0:0:0: [sdd] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[765005.219026]  sdd: sdd1
[765005.222475] sd 20:0:0:0: [sdd] Attached SCSI disk
[765063.865479] usb 1-1: USB disconnect, device number 7
[765063.866624] sd 20:0:0:0: [sdd] Synchronizing SCSI cache
[765063.866725] sd 20:0:0:0: [sdd] Synchronize Cache(10) failed: Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[765119.360051] usb 1-1: new high-speed USB device number 8 using ehci-pci
[765119.497971] usb 1-1: New USB device found, idVendor=0480, idProduct=a00e
[765119.497976] usb 1-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
[765119.497979] usb 1-1: Product: External USB 3.0
[765119.497982] usb 1-1: Manufacturer: TOSHIBA
[765119.497984] usb 1-1: SerialNumber: 20140904007053F
[765119.498386] usb-storage 1-1:1.0: USB Mass Storage device detected
[765119.498813] scsi host21: usb-storage 1-1:1.0
[765120.497046] scsi 21:0:0:0: Direct-Access TOSHIBA  External USB 3.0 0
PQ: 0 ANSI: 6
[765120.499487] sd 21:0:0:0: Attached scsi generic sg2 type 0
[765120.795392] sd 21:0:0:0: [sdd] 976773168 512-byte logical blocks: (500 
GB/465 GiB)
[765120.796628] sd 21:0:0:0: [sdd] Write Protect is off
[765120.796638] sd 21:0:0:0: [sdd] Mode Sense: 43 00 00 00
[765120.797730] sd 21:0:0:0: [sdd] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[765120.814642]  sdd: sdd1
[765120.821084] sd 21:0:0:0: [sdd] Attached SCSI disk
[765140.890996] buffer_io_error: 213 callbacks suppressed
[765140.891001] Buffer I/O error on dev sdc1, logical block 44, async page read
[765191.756953] Buffer I/O error on dev sdc1, logical block 115852478, async 
page read
[765191.757084] EXT4-fs error (device loop0): ext4_put_super:765: Couldn't 
clean up the journal
[765210.313042] lo_write_bvec: 124 callbacks suppressed
[765210.313047] loop: Write error at byte offset 6442582016, length 4096.
[765210.313051] blk_update_request: 117 callbacks suppressed
[765210.313053] blk_update_request: I/O error, dev loop0, sector 12583168
[765210.313057] Buffer I/O error on dev loop0, logical block 1572896, lost 
async page write
[765210.313120] loop: Write error at byte offset 6476136448, length 4096.
[765210.313123] blk_update_request: I/O error, dev loop0, sector 12648704
[765210.313125] Buffer I/O error on dev loop0, logical block 1581088, lost 

Bug#830687: marked as done (linux-image-4.5.0-0.bpo.2-amd64: livelock on reading /proc/mounts)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:07:44 -0700 (PDT)
with message-id <60984110.1c69fb81.d4b17.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #830687,
regarding linux-image-4.5.0-0.bpo.2-amd64: livelock on reading /proc/mounts
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.)


-- 
830687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.4-1~bpo8+1
Severity: normal

NFS seems to have been getting progressively less and less reliable in
kernels>~4.0.  The latest manifestation on that for me is that having
an remote NFS machine go down today, and even after it came back up,
50 instances of /usr/lib/sysstat/sadc (5 minute cronjob) and a dozen
df's are stuck on the machine trying to access that remote mount.
What are they stuck on?  strace shows they're not succeeding in
reading /etc/mtab = /proc/mounts:
...
open("/etc/mtab", O_RDONLY|O_CLOEXEC)   = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f67f044e000
read(3, 0-2-19:08:40, Sun Jul 10 root@dirac:/home/tconnors (bash)
73854,15> l /etc/mtab 
lrwxrwxrwx 1 root root 12 May 29 17:00 /etc/mtab -> /proc/mounts

Indeed, cat /proc/mounts doesn't return.

73855,16> ps axuf | grep proc.mounts 
...
tconnors 23264  0.0  0.0  10632   760 pts/53   D19:00   0:00
  |   \_ cat /proc/mounts
...
73856,17> cat /proc/23264/stack 
[] call_rwsem_down_read_failed+0x14/0x30
[] m_start+0x1d/0x80
[] seq_read+0x16b/0x3a0
[] vfs_read+0x81/0x120
[] SyS_read+0x52/0xc0
[] system_call_fast_compare_end+0xc/0x6b
[] 0x


-- Package-specific info:
** Version:
Linux version 4.5.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)

** Command line:
BOOT_IMAGE=/vmlinuz-4.5.0-0.bpo.2-amd64 root=/dev/mapper/dirac-root ro 
zswap.enabled=1

** Tainted: POE (12289)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[1112649.367575]  [] ? filename_lookup+0xb1/0x180
[1112649.367581]  [] ? nfs_statfs+0x79/0x180 [nfs]
[1112649.367582]  [] ? getname_flags+0x6f/0x1e0
[1112649.367584]  [] ? user_statfs+0x3f/0xa0
[1112649.367586]  [] ? SYSC_statfs+0x20/0x50
[1112649.367587]  [] ? SYSC_newstat+0x39/0x60
[1112649.367589]  [] ? system_call_fast_compare_end+0xc/0x6b
[1112649.367592] INFO: task sadc:11346 blocked for more than 120 seconds.
[1112649.367592]   Tainted: P   OE   4.5.0-0.bpo.2-amd64 #1
[1112649.367593] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[1112649.367594] sadcD 0001 0 11346  11345 
0x
[1112649.367596]  8800ca7a5180 880108246140 8803f6414000 
8803f6413bb0
[1112649.367597]  81a88a18 81a88a00  
0002
[1112649.367599]  815b6451 8800ca7a5180 815b8efc 
8803f6413b50
[1112649.367600] Call Trace:
[1112649.367602]  [] ? schedule+0x31/0x80
[1112649.367603]  [] ? rwsem_down_write_failed+0x20c/0x340
[1112649.367610]  [] ? nfs4_proc_lookup_common+0xbf/0x3b0 
[nfsv4]
[1112649.367611]  [] ? call_rwsem_down_write_failed+0x13/0x20
[1112649.367612]  [] ? down_write+0x29/0x40
[1112649.367614]  [] ? mnt_set_expiry+0x19/0x30
[1112649.367620]  [] ? nfs_d_automount+0xb9/0x1b0 [nfs]
[1112649.367622]  [] ? follow_managed+0x131/0x2d0
[1112649.367623]  [] ? lookup_fast+0x12b/0x320
[1112649.367625]  [] ? walk_component+0x46/0x480
[1112649.367627]  [] ? path_lookupat+0x5d/0x110
[1112649.367628]  [] ? filename_lookup+0xb1/0x180
[1112649.367633]  [] ? nfs_statfs+0x79/0x180 [nfs]
[1112649.367635]  [] ? getname_flags+0x6f/0x1e0
[1112649.367637]  [] ? user_statfs+0x3f/0xa0
[1112649.367638]  [] ? SYSC_statfs+0x20/0x50
[1112649.367640]  [] ? SYSC_newstat+0x39/0x60
[1112649.367641]  [] ? system_call_fast_compare_end+0xc/0x6b
[1112828.668378] CPU1: Core temperature above threshold, cpu clock throttled 
(total events = 3766348)
[1112828.668379] CPU5: Core temperature above threshold, cpu clock throttled 
(total events = 3766345)
[1112828.668380] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 5193799)
[1112828.668381] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 5193796)
[1112828.668383] CPU7: Package temperature above 

Bug#830303: mmc0: Unexpected interrupt 0x04000000.

[Salvatore Bonaccorso]

Contol: tags -1 + moreinfo

On Mon, Feb 18, 2019 at 11:54:23PM +0200, Alexandros Kosiaris wrote:
> Hi,
> 
> For what it's worth, it seems on this specific hardware:
> 
> Broadcom Limited BCM57765/57785 SDXC/MMC Card Reader [14e4:16bc]
> 
> the problem can be resolved by passing:
> 
> debug_quirks2=0x4 to sdhci kernel module.
> 
> Note that there is also the debug_quirks param. I did set some values
> for it but the working one is the default, namely 0
> 
> For more information have a look at
> https://bugzilla.kernel.org/show_bug.cgi?id=73241#c55
> 
> I just tested it on a Macmini7,1Debian having Stretch with
> 4.19+101~bpo9+1 kernel. I 'll be using it for the next few days, I am
> hoping everything will work out ok and I won't have to report more
> stuff

is the issue still reproducible with a recent kernel? If not we might
go ahead and close the bugreport.

Regards,
Salvatore

Processed: forcibly merging 829532 829530

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 829532 829530
Bug #829532 [src:linux] linux-image-4.6.0-0.bpo.1-amd64: breaks qemu-nbd
Bug #829532 [src:linux] linux-image-4.6.0-0.bpo.1-amd64: breaks qemu-nbd
Marked as found in versions linux/4.5.4-1~bpo8+1.
Bug #829530 [src:linux] linux-image-4.5.0-0.bpo.2: breaks qemu-nbd
Severity set to 'important' from 'normal'
Marked as found in versions linux/4.6.1-1.
Added tag(s) confirmed, moreinfo, unreproducible, and upstream.
Merged 829530 829532
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
829530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829530
829532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#829457: marked as done (linux-image-4.6.0-1-amd64: OOPS issued when connecting to a wireless network; connection succeeds)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:01:20 -0700 (PDT)
with message-id <60983f90.1c69fb81.c1764.e...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #829457,
regarding linux-image-4.6.0-1-amd64: OOPS issued when connecting to a wireless 
network; connection succeeds
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.)


-- 
829457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.2-2
Severity: normal

When connecting to a wireless network the oops below is issued. The connection 
succeeds, though from time to time I need to "restore" the connection by 
removing and reinserting the iwlwifi kernel module.

I don't know for sure when the issue appeared for the first time (what kernel 
version).

There is also a submission on the Linux Kernel Oops site, similar to this one: 
http://oops.kernel.org/oops/warning-at-net-mac80211-driver-ops-c39-ieee80211_do_stop0x4b7-0x7c0-mac80211/

Razvan

-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-4) ) #1 SMP Debian 4.6.2-2 (2016-06-25)

** Command line:
BOOT_IMAGE=/vmlinuz-4.6.0-1-amd64 
root=UUID=a5adfd45-b103-4a5e-ac6c-7dc0c732f62b ro quiet

** Tainted: PWOE (12801)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[  442.273491]   880231848e78 880231848e90 
8800b0d4f3a0
[  442.273495] Call Trace:
[  442.273502]  [] ? dump_stack+0x5c/0x77
[  442.273508]  [] ? __warn+0xbe/0xe0
[  442.273512]  [] ? warn_slowpath_fmt+0x5f/0x80
[  442.273533]  [] ? ieee80211_do_stop+0x50a/0x7c0 [mac80211]
[  442.273538]  [] ? dev_deactivate_many+0x1fd/0x230
[  442.273557]  [] ? ieee80211_stop+0x16/0x20 [mac80211]
[  442.273562]  [] ? __dev_close_many+0x94/0x100
[  442.273565]  [] ? dev_close_many+0x84/0x120
[  442.273570]  [] ? dev_close.part.83+0x3e/0x60
[  442.273574]  [] ? dev_close+0x13/0x20
[  442.273598]  [] ? 
cfg80211_shutdown_all_interfaces+0x3d/0xa0 [cfg80211]
[  442.273623]  [] ? ieee80211_reconfig+0x90/0xf80 [mac80211]
[  442.273627]  [] ? try_to_del_timer_sync+0x59/0x80
[  442.273644]  [] ? ieee80211_restart_work+0x8d/0xc0 
[mac80211]
[  442.273648]  [] ? process_one_work+0x15d/0x410
[  442.273652]  [] ? worker_thread+0x4d/0x480
[  442.273656]  [] ? process_one_work+0x410/0x410
[  442.273660]  [] ? kthread+0xcd/0xf0
[  442.273665]  [] ? ret_from_fork+0x22/0x40
[  442.273668]  [] ? kthread_create_on_node+0x190/0x190
[  442.273671] ---[ end trace f122df73ab546004 ]---
[  442.273677] [ cut here ]
[  442.273697] WARNING: CPU: 0 PID: 648 at 
/build/linux-FzSZXp/linux-4.6.2/net/mac80211/driver-ops.c:39 
ieee80211_do_stop+0x4b7/0x7c0 [mac80211]
[  442.273698] Modules linked in: xt_TCPMSS(E) xt_tcpmss(E) ppp_deflate(E) 
bsd_comp(E) ppp_async(E) crc_ccitt(E) huawei_cdc_ncm(E) option(E) cdc_wdm(E) 
cdc_ncm(E) usbnet(E) mii(E) usb_wwan(E) usbserial(E) uas(E) usb_storage(E) 
hmac(E) drbg(E) ansi_cprng(E) ctr(E) ccm(E) bnep(E) pci_stub(E) vboxpci(OE) 
vboxnetadp(OE) fuse(E) vmw_vsock_vmci_transport(E) vsock(E) vboxnetflt(OE) 
vmw_vmci(E) vboxdrv(OE) xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) 
nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_conntrack(E) nf_conntrack(E) 
ipt_REJECT(E) nf_reject_ipv4(E) xt_tcpudp(E) tun(E) bridge(E) stp(E) llc(E) 
ebtable_filter(E) ebtables(E) ip6table_filter(E) ip6_tables(E) 
iptable_filter(E) ip_tables(E) x_tables(E) snd_hrtimer(E) snd_seq_midi(E) 
snd_seq_midi_event(E)
[  442.273739]  snd_rawmidi(E) snd_seq(E) snd_seq_device(E) pppoe(E) pppox(E) 
ppp_generic(E) slhc(E) cpufreq_conservative(E) cpufreq_userspace(E) 
cpufreq_stats(E) cpufreq_powersave(E) nfsd(E) auth_rpcgss(E) nfs_acl(E) nfs(E) 
lockd(E) grace(E) fscache(E) sunrpc(E) binfmt_misc(E) uvcvideo(E) btusb(E) 
btrtl(E) videobuf2_vmalloc(E) videobuf2_memops(E) btbcm(E) btintel(E) 
bluetooth(E) videobuf2_v4l2(E) videobuf2_core(E) videodev(E) media(E) arc4(E) 
iwldvm(E) mac80211(E) iwlwifi(E) snd_hda_codec_conexant(E) cfg80211(E) 
snd_hda_codec_generic(E) intel_rapl(E) i915(E) iTCO_wdt(E) 
iTCO_vendor_support(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) 
kvm_intel(E) kvm(E) irqbypass(E) joydev(E) evdev(E) snd_hda_intel(E) 
crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) 

Bug#829083: marked as done (linux-image-4.6.0-1-amd64: [drm:haswell_crtc_disable [i915]] *ERROR* failed to update payload -22, then WARN_ON(!wm_changed) when turning off external monitor)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 13:00:32 -0700 (PDT)
with message-id <60983f60.1c69fb81.70ecd.f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #829083,
regarding linux-image-4.6.0-1-amd64: [drm:haswell_crtc_disable [i915]] *ERROR* 
failed to update payload -22, then WARN_ON(!wm_changed) when turning off 
external monitor
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.)


-- 
829083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.2-2
Severity: normal

The errors and warnings below occur when an external displayport monitor
is turned off (connected to Intel Skylake integrated graphics).


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-4) ) #1 SMP Debian 4.6.2-2 (2016-06-25)

** Command line:
BOOT_IMAGE=/vmlinuz-4.6.0-1-amd64 
root=UUID=fdd057bd-d641-4ccc-8693-c91e0aa683f7 ro console=tty0 intel_iommu=on 
cgroup_enable=memory

** Tainted: WE (8704)
 * Taint on warning.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[ 3682.841445] xhci_hcd :00:14.0: WARN Event TRB for slot 6 ep 4 with no 
TDs queued?
[ 3682.841717] xhci_hcd :00:14.0: WARN Event TRB for slot 6 ep 4 with no 
TDs queued?
[ 5055.777513] perf: interrupt took too long (3939 > 3932), lowering 
kernel.perf_event_max_sample_rate to 50750
[ 8619.806171] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[ 8797.875274] perf: interrupt took too long (4965 > 4923), lowering 
kernel.perf_event_max_sample_rate to 40250
[12143.321023] [drm:haswell_crtc_disable [i915]] *ERROR* failed to update 
payload -22
[12143.821250] [ cut here ]
[12143.824633] WARNING: CPU: 2 PID: 21529 at 
/build/linux-FzSZXp/linux-4.6.2/drivers/gpu/drm/i915/intel_pm.c:3586 
skl_update_other_pipe_wm+0x15d/0x170 [i915]
[12143.828084] WARN_ON(!wm_changed)
[12143.828105] Modules linked in:
[12143.831570]  bnep(E) xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) 
nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_conntrack(E) nf_conntrack(E) 
ipt_REJECT(E) nf_reject_ipv4(E) xt_tcpudp(E) tun(E) ebtable_filter(E) 
ebtables(E) ip6table_filter(E) ip6_tables(E) tg3(E) broadcom(E) bcm_phy_lib(E) 
libphy(E) target_core_user(E) uio(E) target_core_pscsi(E) target_core_iblock(E) 
target_core_mod(E) dlm(E) nfsv3(E) nfs(E) fscache(E) iptable_filter(E) 
ip_tables(E) x_tables(E) cpufreq_userspace(E) cpufreq_conservative(E) 
cpufreq_stats(E) cpufreq_powersave(E) bridge(E) stp(E) llc(E) binfmt_misc(E) 
snd_hda_codec_hdmi(E) dcdbas(E) intel_rapl(E) snd_hda_codec_realtek(E) 
snd_hda_codec_generic(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) 
kvm_intel(E)
[12143.835835]  kvm(E) irqbypass(E) crct10dif_pclmul(E) joydev(E) 
crc32_pclmul(E) ghash_clmulni_intel(E) snd_hda_intel(E) serio_raw(E) pcspkr(E) 
i2c_i801(E) snd_hda_codec(E) snd_hda_core(E) usblp(E) snd_usb_audio(E) 
snd_usbmidi_lib(E) snd_hwdep(E) snd_rawmidi(E) snd_seq_device(E) snd_pcm_oss(E) 
snd_mixer_oss(E) snd_pcm(E) snd_timer(E) snd(E) soundcore(E) evdev(E) i915(E) 
drm_kms_helper(E) sg(E) drm(E) mei_me(E) i2c_algo_bit(E) mei(E) shpchp(E) 
wmi(E) battery(E) 8250_fintek(E) hci_uart(E) btbcm(E) btqca(E) btintel(E) 
video(E) bluetooth(E) rfkill(E) acpi_als(E) kfifo_buf(E) intel_lpss_acpi(E) 
intel_lpss(E) mfd_core(E) button(E) tpm_tis(E) tpm(E) processor(E) acpi_pad(E) 
industrialio(E) sch_fq_codel(E) pci_stub(E) i2c_dev(E) hwmon_vid(E) coretemp(E) 
loop(E) ipmi_watchdog(E) ipmi_poweroff(E) ipmi_devintf(E)
[12143.844328]  nfsd(E) ipmi_msghandler(E) parport_pc(E) auth_rpcgss(E) 
ppdev(E) nfs_acl(E) lockd(E) grace(E) lp(E) sunrpc(E) parport(E) configfs(E) 
autofs4(E) ext4(E) ecb(E) crc16(E) jbd2(E) mbcache(E) btrfs(E) 
crc32c_generic(E) xor(E) raid6_pq(E) hid_microsoft(E) raid1(E) md_mod(E) 
dm_mirror(E) dm_region_hash(E) dm_log(E) dm_mod(E) uas(E) usb_storage(E) 
hid_generic(E) usbhid(E) sr_mod(E) cdrom(E) sd_mod(E) crc32c_intel(E) 
aesni_intel(E) aes_x86_64(E) glue_helper(E) lrw(E) gf128mul(E) ablk_helper(E) 
cryptd(E) psmouse(E) ahci(E) xhci_pci(E) libahci(E) e1000e(E) xhci_hcd(E) 
ptp(E) libata(E) pps_core(E) scsi_mod(E) usbcore(E) usb_common(E) fan(E) 
thermal(E) i2c_hid(E) hid(E) fjes(E) [last unloaded: tcm_loop]
[12143.853513] CPU: 2 PID: 21529 Comm: kworker/2:0 Tainted: GW   E   
4.6.0-1-amd64 #1 Debian 4.6.2-2
[12143.858151] Hardware 

Bug#828026: marked as done (linux-image-4.6.0-1-amd64: Spanning Tree (STP) not working in 4.6, was in 4.5, seems to ignore incoming BPDU packets)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:59:54 -0700 (PDT)
with message-id <60983f3a.1c69fb81.f62b4.5...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #828026,
regarding linux-image-4.6.0-1-amd64: Spanning Tree (STP) not working in 4.6, 
was in 4.5, seems to ignore incoming BPDU packets
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.)


-- 
828026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.2-1
Severity: normal

Upgrading to the 4.6 kernel from 4.5 seems to have broken STP.

If I create a bridge interface and add one or more physical interfaces, the
system running the Debian 4.6 kernel package ALWAYS thinks it is the bridge
root (regardless of what other STP devices are on the network and their
bridge priorities), and further will not put ANY port into the blocking
state, even when there is a loop (as confirmed by broadcast storm and lots
of "received packet on $interface with own address as source address" errors
in the logs).

Monitoring the physical interfaces with tshark shows that the BPDUs are
being both sent and received at that level, but the system running the 4.6
kernel simply seems to ignore the ones coming in, even if they have much
lower bridge priorities.

The 4.5 kernel package seems to operate STP correctly and will negotiate
which device should be the bridge root correctly.

I'm able to reproduce this on multiple systems.  One of them has a second
strange problem with not sending BPDUs at all even on the 4.5 kernel, but I
expect that is a different issue.

-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-4) ) #1 SMP Debian 4.6.2-1 (2016-06-15)

** Command line:
BOOT_IMAGE=/vmlinuz-4.6.0-1-amd64 root=/dev/mapper/bengal-root ro 
cgroup_enable=memory quiet

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[2.446308] Bluetooth: hci0: read Intel version: 370710018002030d53
[2.446310] Bluetooth: hci0: Intel device is already patched. patch num: 53
[2.447390] sd 0:0:0:0: Attached scsi generic sg0 type 0
[2.453311] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless N 
7260, REV=0x144
[2.453579] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
[2.453968] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input7
[2.454030] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input8
[2.454117] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
[2.470971] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[2.471306] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
[2.490499] EFI Variables Facility v0.08 2004-May-17
[2.495673] ACPI: Battery Slot [BAT1] (battery present)
[2.509940] pstore: Registered efi as persistent store backend
[2.602595] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[2.602601] [drm] Initialized i915 1.6.0 20160229 for :00:02.0 on minor 0
[2.602977] ACPI Warning: SystemIO range 
0xF040-0xF05F conflicts with OpRegion 
0xF040-0xF04F (\_SB.PCI0.SBUS.SMBI) 
(20160108/utaddress-255)
[2.602984] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[2.614899] fbcon: inteldrmfb (fb0) is primary device
[2.651464] input: PC Speaker as /devices/platform/pcspkr/input/input10
[2.675989] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[2.679989] clocksource: Switched to clocksource tsc
[2.765677] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/0003:04F3:0089.0001/input/input11
[2.765874] hid-multitouch 0003:04F3:0089.0001: input,hiddev0,hidraw0: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-7/input0
[2.793080] iTCO_vendor_support: vendor-support=0
[2.794412] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[2.794464] iTCO_wdt: Found a Lynx Point_LP TCO device (Version=2, 
TCOBASE=0x1860)
[2.794910] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[2.841962] intel_rapl: Found RAPL domain package
[2.841964] intel_rapl: Found RAPL domain core
[2.841965] intel_rapl: Found RAPL domain uncore
[2.841967] intel_rapl: Found RAPL domain dram
[2.841971] intel_rapl: 

Bug#827579: marked as done (linux-image-4.6.0-1-amd64: can't boot into KDE (nouveau, GTX970))

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:58:40 -0700 (PDT)
with message-id <60983ef0.1c69fb81.a73b7.5...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #827579,
regarding linux-image-4.6.0-1-amd64: can't boot into KDE (nouveau, GTX970)
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.)


-- 
827579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.6.2-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Just regular update of Debian Stretch caused, that i can work only in
CLI (no GUI/KDE). I tried to update linux kernel from STRETCH (v4.6.1-1) to
SID (v4.6.2-1), but the problem is the same.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

When i return back to linux-image-4.5.0-2-amd64 (v4.5.4-1) it boots
into GUI (KDE) and i can work normally.


*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-4) ) #1 SMP Debian 4.6.2-1 (2016-06-15)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=bf378e0d-fcd2-4c28-a3c9-561e753b25ab ro quiet

** Tainted: POE (12289)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[7.107895] systemd[1]: Started Dispatch Password Requests to Console 
Directory Watch.
[7.107930] systemd[1]: Listening on Journal Socket (/dev/log).
[7.108305] systemd[1]: Starting Create list of required static device nodes 
for the current kernel...
[7.108324] systemd[1]: Reached target Encrypted Volumes.
[7.108367] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[7.108396] systemd[1]: Listening on Syslog Socket.
[7.108458] systemd[1]: Listening on Journal Audit Socket.
[7.108813] systemd[1]: Starting Journal Service...
[7.108897] systemd[1]: Created slice system-getty.slice.
[7.108932] systemd[1]: Listening on udev Kernel Socket.
[7.108960] systemd[1]: Listening on fsck to fsckd communication Socket.
[7.109005] systemd[1]: Listening on udev Control Socket.
[7.109018] systemd[1]: Reached target User and Group Name Lookups.
[7.109031] systemd[1]: Reached target Remote File Systems (Pre).
[7.109040] systemd[1]: Reached target Remote File Systems.
[7.121487] systemd[1]: Starting Load Kernel Modules...
[7.122039] systemd[1]: Mounting POSIX Message Queue File System...
[7.122424] systemd[1]: Mounting Huge Pages File System...
[7.122888] systemd[1]: Starting Remount Root and Kernel File Systems...
[7.198543] systemd[1]: Started Create list of required static device nodes 
for the current kernel.
[7.213772] systemd[1]: Starting Create Static Device Nodes in /dev...
[7.577237] lp: driver loaded but no devices found
[7.609586] systemd[1]: Mounted POSIX Message Queue File System.
[7.609619] systemd[1]: Mounted Debug File System.
[7.609641] systemd[1]: Mounted Huge Pages File System.
[7.625154] ppdev: user-space parallel port driver
[7.639325] EXT4-fs (sdb6): re-mounted. Opts: user_xattr,errors=remount-ro
[7.639912] systemd[1]: Started Remount Root and Kernel File Systems.
[7.657837] systemd[1]: Starting Load/Save Random Seed...
[7.733561] systemd[1]: Starting udev Coldplug all Devices...
[7.751967] systemd[1]: Started Journal Service.
[7.810885] scsi host7: vhba
[7.979751] systemd-journald[766]: Received request to flush runtime journal 
from PID 1
[8.924393] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
[8.924399] ACPI: Power Button [PWRB]
[8.924437] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
[8.924439] ACPI: Power Button [PWRF]
[8.944128] EDAC MC: Ver: 3.0.0
[9.012238] sd 0:2:1:0: Attached scsi generic sg0 type 0
[9.012267] sd 1:0:0:0: Attached scsi generic sg1 type 0
[9.012294] sr 2:0:0:0: Attached scsi generic sg2 type 5
[9.030729] ACPI Warning: SystemIO range 
0x0828-0x082F conflicts with OpRegion 
0x0800-0x084F (\PMRG) (20160108/utaddress-255)
[9.030734] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native 

Bug#827557: marked as done (linux-image-4.6.0-1-armmp-lpae: 4.6 armmp kernel fails to boot on nvidia jetson (4.5 works))

[Debian Bug Tracking System]

Your message dated Sun, 9 May 2021 21:57:34 +0200
with message-id 
and subject line Re: Bug#827557: linux-image-4.6.0-1-armmp-lpae: 4.6 armmp 
kernel fails to boot on nvidia jetson (4.5 works)
has caused the Debian Bug report #827557,
regarding linux-image-4.6.0-1-armmp-lpae: 4.6 armmp kernel fails to boot on 
nvidia jetson (4.5 works)
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.)


-- 
827557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.6.0-1-armmp-lpae
Version: 4.6.1-1
Severity: normal

I installed an nvidia jetson board (armhf, v7) with the stretch alpha6
installer. It all worked nicely. 
See documentation at:
https://wiki.debian.org/InstallingDebianOn/NVIDIA/Jetson-TK1

On upgrading the kernel to 'current testing', (
linux-image-4.6.0-1-armmp-lpae 4.6.1-1, and linux-image-armmp-lpae
4.6+74, from what's in alpha6 installer (
linux-image-4.5.0-2-armmp-lpae 4.5.3-2 and linux-image-armmp-lpae
4.5+73) causes the machine to no longer boot.

I failed to keep a log, but after 
[3.266688] mmc0: Unknown controller version (3). You may experience 
problems.
[3.314162] mmc1: Unknown controller version (3). You may experience 
problems.
(which appears on successful boots too)
I just get messages about failing to set up IO for a sound device (3
lots), then it hangs. 
On the working 4.5 boot I see:

[   15.714061] r8169 :01:00.0: firmware: failed to load 
rtl_nic/rtl8168g-2.fw (-2)

Debian GNU/Linux stretch/sid debian-jetson ttyS0

debian-jetson login:
--

I tried to turn extra debug on and failed. 

I am about to go on hols for 3 weeks so filing this bug as a
placeholder in case anyone else has info to add.

Clearly further investigation is needed to find out where it is going
wrong.

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

On Thu, Jul 21, 2016 at 04:04:51AM +0100, Wookey wrote:
> On 2016-07-19 11:40 -0700, Martin Michlmayr wrote:
> 
> > I tracked it down to CONFIG_ARM_TEGRA_DEVFREQ which I enabled in
> > 4.6-1~exp2.
> > 
> > With this module enabled, I see the same hang you do.  Without the
> > module, it works.
> > 
> > Interestingly, it depends on the version of u-boot used, though.
> > With the u-boot from Debian (i.e. a current mainline DENX u-boot), I
> > do not get this issue (which is why my tests before enabling the
> > module didn't find it).  I only see it with the old u-boot from
> > NVIDIA.
> > 
> > I brought this up upstream:
> > http://permalink.gmane.org/gmane.linux.ports.tegra/26941
> > and the response was that if mainline u-boot works, I should use that.
> > 
> > I then edited the Debian wiki to remove the portions about the old
> > u-boot and made it clear users have to upgrade to Debian's u-boot.
> > 
> > IMHO it should be ok to tell users to use a modern mainline u-boot,
> > but I don't mind disabling CONFIG_ARM_TEGRA_DEVFREQ again either
> > if you think that's a good idea.
> 
> OK. I've confirmed that. (and that programing the debian uboot needs
> the old R19.3 flash tools, otherwise it just makes the board totally
> dead). So yes, as it all works with the Debian bits and we've
> documented the wrinkles on
> https://wiki.debian.org/InstallingDebianOn/NVIDIA/Jetson-TK1 I guess
> that's OK, although it is likely to catch some people out if they
> aren't reading that page.
> 
> It would be good to work out the runes for flashing just the uboot
> with lower-level tools, and automating the setting of the uboot runes
> as much as possible.
> 
> I guess we can call this bug closed, as it's not the kernel that's at fault. 

Okay, doing so now (after some years ;-)).

Regards,
Salvatore--- End Message ---

Bug#827488: marked as done (linux-image-3.16.0-4-amd64: resume from suspend to RAM fails on Acer Aspire 9300)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:54:34 -0700 (PDT)
with message-id <60983dfa.1c69fb81.6cd0f.6...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #827488,
regarding linux-image-3.16.0-4-amd64: resume from suspend to RAM fails on Acer 
Aspire 9300
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.)


-- 
827488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt25-2
Severity: normal

When I try to resume from suspend to RAM on a laptop "Acer Aspire 9300",
I get a screen with blinking white et black stripes.

Note that I had to blacklist acer_wmi to boot the laptop.

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=90b5bae1-ae6c-4048-bef8-2792c40c83b6 ro quiet

** Not tainted

** Kernel log:
[   10.898672] nouveau  [ DRM] DCB conn 04: 0213
[   10.898675] nouveau  [ DRM] DCB conn 05: 0340
[   10.898678] nouveau  [ DRM] DCB conn 06: 2431
[   10.898983] nouveau  [ DRM] Saving VGA fonts
[   10.959467] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   10.959473] [drm] Driver supports precise vblank timestamp query.
[   10.962398] nouveau  [ DRM] MM: using M2MF for buffer copies
[   10.962410] nouveau  [ DRM] Calling LVDS script 6:
[   10.962413] nouveau  [ DRM] 0xC2F1: Parsing digital output script table
[   11.014788] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 18
[   11.014818] snd_hda_intel :00:10.1: Disabling MSI
[   11.240222] nouveau  [ DRM] Setting dpms mode 3 on TV encoder (output 2)
[   11.340906] ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 17
[   11.341007] ath5k :04:05.0: registered as 'phy0'
[   11.344537] nouveau  [ DRM] allocated 1440x900 fb: 0x9000, bo 
88007c0fd800
[   11.344727] fbcon: nouveaufb (fb0) is primary device
[   11.356870] [sched_delayed] 
4CE: hpet increased min_delta_ns to 11521 nsec
[   11.356920] [sched_delayed] 
4CE: hpet increased min_delta_ns to 17281 nsec
[   11.366963] nouveau  [ DRM] Calling LVDS script 2:
[   11.366967] nouveau  [ DRM] 0xC367: Parsing digital output script table
[   11.408763] Adding 3905532k swap on /dev/sda5.  Priority:-1 extents:1 
across:3905532k FS
[   11.487780] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f:
[   11.487809]  excluding 0xcc000-0xc 0xf-0xf
[   11.487825] pcmcia_socket pcmcia_socket0: cs: memory probe 
0xa000-0xa0ff:
[   11.487857]  clean.
[   11.487872] pcmcia_socket pcmcia_socket0: cs: memory probe 
0x6000-0x60ff:
[   11.487905]  excluding 0x6000-0x60ff
[   11.513819] nouveau  [ DRM] Calling LVDS script 5:
[   11.513821] nouveau  [ DRM] 0xC2E2: Parsing digital output script table
[   11.516863] Console: switching to colour frame buffer device 180x56
[   11.519732] nouveau :03:00.0: fb0: nouveaufb frame buffer device
[   11.519735] nouveau :03:00.0: registered panic notifier
[   11.532077] [drm] Initialized nouveau 1.1.2 20120801 for :03:00.0 on 
minor 0
[   11.595017] kvm: Nested Virtualization enabled
[   11.621591] media: Linux media interface: v0.10
[   11.639835] Linux video capture interface: v2.00
[   11.816196] uvcvideo: Found UVC 1.00 device USB2.0 Camera (5986:0100)
[   11.885596] input: USB2.0 Camera as 
/devices/pci:00/:00:0b.1/usb1/1-6/1-6:1.0/input/input15
[   11.885816] usbcore: registered new interface driver uvcvideo
[   11.885819] USB Video Class driver (1.1.1)
[   11.926012] powernow_k8: fid 0x8 (1600 MHz), vid 0x13
[   11.926018] powernow_k8: fid 0x0 (800 MHz), vid 0x1e
[   11.926091] powernow_k8: Found 1 AMD Turion(tm) 64 X2 Mobile Technology 
TL-52 (2 cpu cores) (version 2.20.00)
[   12.044066] sound hdaudioC0D0: ALC883: SKU not ready 0x41f0
[   12.087251] ath: EEPROM regdomain: 0x63
[   12.087258] ath: EEPROM indicates we should expect a direct regpair map
[   12.087267] ath: Country alpha2 being used: 00
[   12.087272] ath: Regpair used: 0x63
[   12.100089] sound hdaudioC0D0: autoconfig: line_outs=1 
(0x15/0x0/0x0/0x0/0x0) type:speaker
[   12.100106] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   12.100116] sound hdaudioC0D0:hp_outs=1 (0x14/0x0/0x0/0x0/0x0)
[   12.100123] sound hdaudioC0D0:mono: mono_out=0x0
[   12.100130] sound hdaudioC0D0:

Bug#827510: marked as done (videobuf2-core.c:1781 vb2_start_streaming+0xf8/0x180 [videobuf2_core]())

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:55:48 -0700 (PDT)
with message-id <60983e44.1c69fb81.d03bc.2...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #827510,
regarding videobuf2-core.c:1781 vb2_start_streaming+0xf8/0x180 
[videobuf2_core]()
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.)


-- 
827510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 3.16+63

I cannot use any more my oldish webcam: Philips PCVC730K (ToUCam
Fun)/PCVC830 (ToUCam II) USB webcam. If I start:

$ cheese -d /dev/video1

Here is what I see in dmesg:

[271571.088304] usb 4-1.3: new full-speed USB device number 6 using ehci-pci
[271571.299739] usb 4-1.3: New USB device found, idVendor=0471, idProduct=0310
[271571.299749] usb 4-1.3: New USB device strings: Mfr=0, Product=0,
SerialNumber=1
[271571.299754] usb 4-1.3: SerialNumber: 01699900
[271572.079293] pwc: Philips PCVC730K (ToUCam Fun)/PCVC830 (ToUCam II)
USB webcam detected.
[271572.320099] pwc: Registered as video1.
[271572.320233] input: PWC snapshot button as
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.3/input/input16
[271572.320508] usbcore: registered new interface driver Philips webcam
[271575.258917] usbcore: registered new interface driver snd-usb-audio
[271660.187958] pwc: isoc_init() submit_urb 0 failed with error -28
[271660.191229] [ cut here ]
[271660.191257] WARNING: CPU: 6 PID: 11323 at
/build/linux-zbOcpU/linux-3.16.7-ckt25/drivers/media/v4l2-core/videobuf2-core.c:1781
vb2_start_streaming+0xf8/0x180 [videobuf2_core]()
[271660.191261] Modules linked in: snd_usb_audio snd_usbmidi_lib
snd_rawmidi snd_seq_device pwc nls_utf8 isofs xt_CHECKSUM
iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT
xt_tcpudp iptable_filter ip_tables x_tables bridge stp llc
cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace
ctr ccm binfmt_misc bnep nfsd auth_rpcgss oid_registry nfs_acl nfs
lockd fscache sunrpc uvcvideo videobuf2_vmalloc videobuf2_memops
videobuf2_core x86_pkg_temp_thermal intel_powerclamp v4l2_common
intel_rapl videodev kvm_intel media kvm arc4 crc32_pclmul iwldvm
mac80211 aesni_intel aes_x86_64 i915 snd_hda_codec_realtek
snd_hda_codec_generic ecb drm_kms_helper snd_hda_intel iwlwifi
snd_hda_controller snd_hda_codec drm btusb
[271660.191331]  lrw snd_hwdep iTCO_wdt iTCO_vendor_support dell_wmi
bluetooth sparse_keymap gf128mul i2c_algo_bit dell_laptop snd_pcm
lpc_ich cfg80211 6lowpan_iphc dcdbas mfd_core rfkill glue_helper
i2c_i801 i2c_core snd_timer mei_me mei snd ablk_helper shpchp evdev
cryptd pcspkr soundcore processor joydev serio_raw video wmi
dell_smo8800 button battery ac coretemp loop fuse autofs4 ext4 crc16
mbcache jbd2 btrfs xor raid6_pq dm_mod md_mod sg sd_mod sr_mod
crc_t10dif cdrom crct10dif_generic ums_realtek usb_storage ahci
libahci ehci_pci crct10dif_pclmul crct10dif_common xhci_hcd ehci_hcd
crc32c_intel libata psmouse scsi_mod r8169 mii usbcore usb_common
thermal thermal_sys
[271660.191415] CPU: 6 PID: 11323 Comm: video_source:sr Not tainted
3.16.0-4-amd64 #1 Debian 3.16.7-ckt25-1
[271660.191418] Hardware name: Dell Inc.  Dell System Vostro
3750/0VP036, BIOS A14 09/26/2012
[271660.191422]   8150e835 
0009
[271660.191428]  810677f7 ffe4 880119d00610
880119d004b8
[271660.191433]   8800775cbdf8 a070ef18
880119d004b8
[271660.191438] Call Trace:
[271660.191451]  [] ? dump_stack+0x5d/0x78
[271660.191460]  [] ? warn_slowpath_common+0x77/0x90
[271660.191470]  [] ? vb2_start_streaming+0xf8/0x180
[videobuf2_core]
[271660.191479]  [] ?
vb2_internal_streamon+0x15d/0x1b0 [videobuf2_core]
[271660.191491]  [] ? __video_do_ioctl+0x2a3/0x330 [videodev]
[271660.191503]  [] ? video_ioctl2+0x20/0x20 [videodev]
[271660.191513]  [] ? video_usercopy+0x1fe/0x540 [videodev]
[271660.191522]  [] ? futex_wake+0x6f/0x120
[271660.191529]  [] ? do_futex+0x11e/0xb60
[271660.191539]  [] ? v4l2_ioctl+0x10b/0x150 [videodev]
[271660.191546]  [] ? do_vfs_ioctl+0x2cf/0x4b0
[271660.191553]  [] ? SyS_futex+0x6e/0x150
[271660.191558]  [] ? SyS_ioctl+0x81/0xa0
[271660.191566]  [] ? system_call_fast_compare_end+0x10/0x15
[271660.191570] ---[ end trace 45f9521fea01f64c ]---
[271697.429869] pwc: isoc_init() submit_urb 0 failed with error -28
[271697.433143] [ cut 

Bug#827506: marked as done (linux-image-4.6.0-1-amd64: Intel i915 graphics locks up)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:55:17 -0700 (PDT)
with message-id <60983e25.1c69fb81.87098.7...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #827506,
regarding linux-image-4.6.0-1-amd64: Intel i915 graphics locks up
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.)


-- 
827506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Version: 4.6.0-1-amd64

Dear Maintainer,

Installed linux-image-4.6.1-1-amd64 and did normal start and login.

screen locked up after a short time - varied usually less than 2
minutes.

ctrl+alt+F1 to go to a console, not always immediate; reboot to verify
repeatability, Yes
sometimes locked screen became unlocked abut locked up again shortly.

Error message appeared on console
"57.839806 [drm:i915_set_reset_status [i915]]*ERROR* gpu hanging too
fast, banning!"
(I hope I copied that right)

The numbers at the beginning of the error message varied.

The machine is an Intel NUC model NUC5PPYH Pentium processor
(Braswell)
Identical behaviour on another machine - Intel NUC model NUC5CPYH
Celeron processor (Braswell) with close to the same software loaded.

I've uninstalled the 4.6.0 image from the Pentium machine but have the
image still loaded on the Celeron if you would like me to run any
tests but much hand holding would be required.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Chris Barnard

--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#827242: marked as done (Webcam(s) do not work on Microsoft Surface Book or recent Surface Pro tablets)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:54:17 -0700 (PDT)
with message-id <60983de9.1c69fb81.a564a.7...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #827242,
regarding Webcam(s) do not work on Microsoft Surface Book or recent Surface Pro 
tablets
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.)


-- 
827242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kernel

via: https://bugzilla.kernel.org/show_bug.cgi?id=109821

Despite of the existing patch (e.g.
https://github.com/tiggerite/mint-17.3-for-surface-pro-3/blob/master/patches-4.3/surface-cam.patch),
it seems some surface pro 4 model (E.g. my i7 16G) uses a different
webcam solution.

>From windows, there are three camera listed with "Camera" in their driver name.
They are Microsoft Camera Front, Microsoft Camera Rear and Microsoft
IR Camera Front.

The properties dialogs show that they are OV5693, OV7251 and OV8865,
seems they are i2c device instead of usb device.
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Processed: Re: Bug#827044: linux-image-4.5.0-1-686-pae: Kernel 4.5.0-1 hangs at boot time on VirtualBox with no hardware virtualization (VT-x)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #827044 [src:linux] linux-image-4.5.0-1-686-pae: Kernel 4.5.0-1 hangs at 
boot time on VirtualBox with no hardware virtualization (VT-x)
Added tag(s) moreinfo.

-- 
827044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#827044: linux-image-4.5.0-1-686-pae: Kernel 4.5.0-1 hangs at boot time on VirtualBox with no hardware virtualization (VT-x)

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Camaleón,

On Sat, Dec 09, 2017 at 11:56:00AM +0100, Camaleón wrote:
> This is still a issue.
> 
> Is not that just non-pae kernel boots but the last bootable kernel is 
> 4.9.0-3, I mean, recent non-pae kernels (4.11, 4.12, 4.13) are unable to 
> boot (bad eip value).
> 
> See attached images for full kernel message.

Is this still reproducible with a current kernel?

Regards,
Salvatore

Bug#826378: marked as done (linux: System immediately wakes up after suspend, faulty wake-on-lan on 8086:1502 e1000e NIC.)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:47:41 -0700 (PDT)
with message-id <60983c5d.1c69fb81.152aa.2...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #826378,
regarding linux: System immediately wakes up after suspend, faulty wake-on-lan 
on 8086:1502 e1000e NIC.
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.)


-- 
826378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: normal

Dear Maintainer, my system wakes up immediately after gone to suspend.
It seems to be caused by faulty e1000e wake-on-lan on 8086:1502 NIC. I can 
reproduce it
when any wol state is set on NIC except 'd'. Cable is not plugged.

can be worked around by either:
echo GLAN | sudo tee /proc/acpi/wakeup
or
sudo ethtool -s eno1 wol d



Jun 05 07:39:18 hostname systemd-logind[899]: Lid closed.
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname kernel: pci_bus :01: Allocating resources
Jun 05 07:39:18 hostname kernel: pci_bus :02: Allocating resources
Jun 05 07:39:18 hostname kernel: pci_bus :03: Allocating resources
Jun 05 07:39:18 hostname kernel: pci_bus :07: Allocating resources
Jun 05 07:39:18 hostname kernel: pci_bus :0b: Allocating resources
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname kernel: i915 :00:02.0: BAR 6: [??? 0x 
flags 0x2] has bogus alignment
Jun 05 07:39:18 hostname NetworkManager[972]:   [1465101558.8718] 
manager: sleep requested (sleeping: no  enabled: yes)
Jun 05 07:39:18 hostname NetworkManager[972]:   [1465101558.8719] 
manager: sleeping...
Jun 05 07:39:18 hostname NetworkManager[972]:   [1465101558.8719] device 
(wlp2s0b1): state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Jun 05 07:39:18 hostname NetworkManager[972]:   [1465101558.9041] dhcp4 
(wlp2s0b1): canceled DHCP transaction, DHCP client pid 12403
Jun 05 07:39:18 hostname NetworkManager[972]:   [1465101558.9042] dhcp4 
(wlp2s0b1): state changed bound -> done
Jun 05 07:39:18 hostname avahi-daemon[923]: Withdrawing address record for 
fe80::7218:8bff:fe13:331d on wlp2s0b1.
Jun 05 07:39:18 hostname avahi-daemon[923]: Leaving mDNS multicast group on 
interface wlp2s0b1.IPv6 with address fe80::7218:8bff:fe13:331d.
Jun 05 07:39:18 hostname kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: 
arp filtering: 0 addresses (implement)
Jun 05 07:39:18 hostname kernel: wlp2s0b1: deauthenticating from 
XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 05 07:39:18 hostname avahi-daemon[923]: Interface wlp2s0b1.IPv6 no longer 
relevant for mDNS.
Jun 05 07:39:18 hostname avahi-daemon[923]: Withdrawing address record for 
X.X.X.X on wlp2s0b1.
Jun 05 07:39:18 hostname avahi-daemon[923]: Leaving mDNS multicast group on 
interface wlp2s0b1.IPv4 with address X.X.X.X.
Jun 05 07:39:18 hostname kernel: brcmsmac bcma0:1: brcmsmac: 
brcms_ops_bss_info_changed: disassociated
Jun 05 07:39:18 hostname kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: 
qos enabled: false (implement)
Jun 05 07:39:18 hostname wpa_supplicant[2555]: wlp2s0b1: 
CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX reason=3 locally_generated=1
Jun 05 07:39:18 hostname avahi-daemon[923]: Interface wlp2s0b1.IPv4 no longer 
relevant for mDNS.
Jun 05 07:39:18 hostname dnsmasq[4448]: setting upstream servers from DBus
Jun 05 07:39:18 hostname NetworkManager[972]:   [1465101558.9652] 
manager: NetworkManager state is now ASLEEP
Jun 05 07:39:18 hostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0b1: link is 
not ready
Jun 05 07:39:19 hostname dbus[953]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun 05 07:39:19 hostname systemd[1]: Reached target Sleep.
Jun 05 07:39:19 hostname 

Bug#825507: marked as done (pulseaudio: system hangs, log message ask me to report bug)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:46:55 -0700 (PDT)
with message-id <60983c2f.1c69fb81.53f35.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #825507,
regarding pulseaudio: system hangs, log message ask me to report bug
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.)


-- 
825507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseaudio
Version: 8.0-2+b2
Severity: normal
Tags: upstream

Dear pulseaudio developers,

thanks for your work with this package.

It seems there is a problem with 'snd_hda_intel' which seems like a driver.
The error message (in spanish) ask me to report this to ALSA developers, and 
since this message
seems to get to my syslog via pulseaudio, I'm opening a bug here.

My laptop hanged after some idle time, and the only message found in the syslog 
was
this:

May 27 12:02:21 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: snd_pcm_avail() devolvió un valor que es excepcionalmente grande: 
375508 bytes (2128 ms).
May 27 12:02:21 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: Lo más probable es que sea un error del controlador ALSA 
'snd_hda_intel'. Por favor, informe ésto a los desarrolladores de ALSA.
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: snd_pcm_dump():
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: Soft volume PCM
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: Control: PCM Playback Volume
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: min_dB: -51
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: max_dB: 0
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: resolution: 256
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: Its setup is:
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   stream   : PLAYBACK
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   format   : S16_LE
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   subformat: STD
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   channels : 2
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   rate : 44100
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   msbits   : 16
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   buffer_size  : 16384
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   period_size  : 8192
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   period_time  : 185759
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   period_step  : 1
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   avail_min: 12152
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   period_event : 0
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   start_threshold  : -1
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   silence_threshold: 0
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   silence_size : 0
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c:   boundary : 4611686018427387904
May 27 12:02:22 nostromo pulseaudio[1637]: [alsa-sink-92HD75B3X5 Analog] 
alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel' device 0 subdevice 0
May 27 12:02:22 

Bug#825566: marked as done (linux-image-4.5.0-2-armmp: etnaviv module load with hw init fail)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:47:18 -0700 (PDT)
with message-id <60983c46.1c69fb81.80533.9...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #825566,
regarding linux-image-4.5.0-2-armmp: etnaviv module load with hw init fail
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.)


-- 
825566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.4-1
Severity: normal

Dear Maintainer,

I have a wandboard quad with a vivante GC2000 chip loading the kernel I get:
[4.913807] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops [etnaviv])
[4.913898] etnaviv gpu-subsystem: bound 13.gpu (ops gpu_ops [etnaviv])
[4.913962] etnaviv gpu-subsystem: bound 2204000.gpu (ops gpu_ops [etnaviv])
[4.913980] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
[4.958312] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108
[5.000672] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
[5.000699] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
[5.000714] etnaviv-gpu 2204000.gpu: hw init failed: -6

lsmod shows etnaviv module but gpu is unusable.

-- Package-specific info:
** Version:
Linux version 4.5.0-2-armmp (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160509 (Debian 5.3.1-19) ) #1 SMP Debian 4.5.4-1 (2016-05-16)

** Command line:
console=ttymxc0,115200 quiet

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[3.673303] systemd[1]: Started Forward Password Requests to Wall Directory 
Watch.
[3.673397] systemd[1]: Reached target Paths.
[3.673494] systemd[1]: Reached target Remote File Systems (Pre).
[3.673584] systemd[1]: Reached target Remote File Systems.
[3.673817] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[3.674028] systemd[1]: Listening on Journal Socket (/dev/log).
[3.674211] systemd[1]: Listening on Syslog Socket.
[3.675352] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[3.675577] systemd[1]: Listening on fsck to fsckd communication Socket.
[3.676107] systemd[1]: Created slice System Slice.
[3.676316] systemd[1]: Reached target Slices.
[3.676913] systemd[1]: Created slice system-serial\x2dgetty.slice.
[3.692844] systemd[1]: Starting Journal Service...
[3.697345] systemd[1]: Starting Create list of required static device nodes 
for the current kernel...
[3.701791] systemd[1]: Starting Remount Root and Kernel File Systems...
[3.703133] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[3.704360] systemd[1]: Created slice system-postgresql.slice.
[3.709815] systemd[1]: Mounting POSIX Message Queue File System...
[3.716030] systemd[1]: Mounting Debug File System...
[3.747423] systemd[1]: Starting Load Kernel Modules...
[3.752373] systemd[1]: Starting Set the console keyboard layout...
[3.769780] systemd[1]: Started Create list of required static device nodes 
for the current kernel.
[3.791703] systemd[1]: Started Load Kernel Modules.
[3.832622] systemd[1]: Mounted POSIX Message Queue File System.
[3.832906] systemd[1]: Mounted Debug File System.
[3.840698] EXT4-fs (mmcblk2p2): re-mounted. Opts: errors=remount-ro
[3.850299] systemd[1]: Started Remount Root and Kernel File Systems.
[3.949308] systemd[1]: Started Journal Service.
[4.300467] systemd-journald[191]: Received request to flush runtime journal 
from PID 1
[4.863214] [drm] Initialized drm 1.1.0 20060810
[4.896586] imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0)
[4.913807] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops [etnaviv])
[4.913898] etnaviv gpu-subsystem: bound 13.gpu (ops gpu_ops [etnaviv])
[4.913962] etnaviv gpu-subsystem: bound 2204000.gpu (ops gpu_ops [etnaviv])
[4.913980] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
[4.958312] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108
[5.000672] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
[5.000699] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
[5.000714] etnaviv-gpu 2204000.gpu: hw init failed: -6
[5.063953] imx-spdif sound-spdif: ASoC: CPU DAI (null) not registered
[5.067662] i2c i2c-0: IMX I2C adapter registered
[5.067678] i2c i2c-0: can't use DMA, using PIO instead.
[5.068503] i2c i2c-1: IMX I2C adapter registered
[5.068519] i2c i2c-1: can't use 

Processed: severity of 826564 is wishlist

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 826564 wishlist
Bug #826564 [src:linux] i686 memory hotplug
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
826564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 825213

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 825213 4.6~rc3-1~exp1
Bug #825213 {Done: Salvatore Bonaccorso } [src:linux] 
Incomplete statistics to manage balloon effectively 
Bug #825209 {Done: Salvatore Bonaccorso } [src:linux] 
Incomplete statistics to manage balloon effectively 
Ignoring request to alter fixed versions of bug #825213 to the same values 
previously set
Ignoring request to alter fixed versions of bug #825209 to the same values 
previously set
Bug #825213 {Done: Salvatore Bonaccorso } [src:linux] 
Incomplete statistics to manage balloon effectively 
Bug #825209 {Done: Salvatore Bonaccorso } [src:linux] 
Incomplete statistics to manage balloon effectively 
Bug 825213 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
825209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825209
825213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 825209

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 825209 4.6~rc3-1~exp1
Bug #825209 [src:linux] Incomplete statistics to manage balloon effectively 
Bug #825213 [src:linux] Incomplete statistics to manage balloon effectively 
Ignoring request to alter fixed versions of bug #825209 to the same values 
previously set
Ignoring request to alter fixed versions of bug #825213 to the same values 
previously set
Bug #825209 [src:linux] Incomplete statistics to manage balloon effectively 
Bug #825213 [src:linux] Incomplete statistics to manage balloon effectively 
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
825209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825209
825213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 825211

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 825211 3.19-1~exp1
Bug #825211 [src:linux] OOM in Debian guests on balloon overinflation
Ignoring request to alter fixed versions of bug #825211 to the same values 
previously set
Bug #825211 [src:linux] OOM in Debian guests on balloon overinflation
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
825211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfound 824790 in 4.18~rc3-1~exp1, closing 824790

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 824790 4.18~rc3-1~exp1
Bug #824790 [src:linux] linux-image-4.5.0-1-amd64: lots of WARNINGs in 
hfsc_dequeue+0x300/0x320 when using sch_hfsc+sch_codel
No longer marked as found in versions linux/4.18~rc3-1~exp1.
> close 824790 4.18~rc3-1~exp1
Bug #824790 [src:linux] linux-image-4.5.0-1-amd64: lots of WARNINGs in 
hfsc_dequeue+0x300/0x320 when using sch_hfsc+sch_codel
Marked as fixed in versions linux/4.18~rc3-1~exp1.
Bug #824790 [src:linux] linux-image-4.5.0-1-amd64: lots of WARNINGs in 
hfsc_dequeue+0x300/0x320 when using sch_hfsc+sch_codel
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
824790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #825026 [src:linux] linux-image-4.5.0-2-armmp-lpae: heartbeat triggered 
LEDs don't come up by default
Added tag(s) moreinfo.

-- 
825026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 825208

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 825208 4.3~rc3-1~exp1
Bug #825208 [src:linux] Ballooned memory is visible via proc
Bug #825212 [src:linux] Ballooned memory is visible via proc
Ignoring request to alter fixed versions of bug #825208 to the same values 
previously set
Ignoring request to alter fixed versions of bug #825212 to the same values 
previously set
Bug #825208 [src:linux] Ballooned memory is visible via proc
Bug #825212 [src:linux] Ballooned memory is visible via proc
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
825208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825208
825212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#825026: linux-image-4.5.0-2-armmp-lpae: heartbeat triggered LEDs don't come up by default

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Steiner,

On Sun, May 22, 2016 at 09:42:38PM +0200, Steinar H. Gunderson wrote:
> On Sun, May 22, 2016 at 08:10:18PM +0100, Ben Hutchings wrote:
> > We build in code because we have to, not because it's merely useful.
> > And here we're talking about modules that are useful for only a small
> > proportion of armhf systems.
> 
> Well, if you count number of device trees, it's about 110 devices out of
> 741 (having heartbeat or default-on as policy). So it's a minority (at least
> if you don't try to weight by number of sold devices, which would be much
> harder), but not complete obscurity.
> 
> Anyways, I'm not going to try to drive this; my ARM bug reports are already
> being met with deafening silence on the Exynos list, so there's enough
> frustration involved :-) It's far from the most important thing in the big
> picture.

Despite the above involved frustration, do you know if someone else
did report the problem and/or you know the issue is not present
anymore with a recent kernel (from unstable ideally or mainline)?

Regards,
Salvatore

Bug#824947: marked as done (After suspend and subsequent wake-up the contents of scaling_max_freq is disregarded)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:34:55 -0700 (PDT)
with message-id <6098395f.1c69fb81.3efa3.6...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #824947,
regarding After suspend and subsequent wake-up the contents of scaling_max_freq 
is disregarded
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.)


-- 
824947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-4.5.0-2-amd64
Version: 4.5.3-2

Before suspend and after suspend we had
# for i in `seq 0 7`; do cat 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_min_freq; done

120
120
120
120
120
120
120
120
# for i in `seq 0 7`; do cat 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done

120
120
120
120
120
120
120
120

Before suspend, we had around 120 in cpuinfo_cur_freq, but after 
suspend we have:
# for i in `seq 0 7`; do cat 
/sys/devices/system/cpu/cpu$i/cpufreq/cpuinfo_cur_freq; done

2599898
2599898
2599898
2599898
2599898
260
2599898
260

We constantly have
# for i in `seq 0 7`; do cat 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_governor; done

powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave

The cooling is noisy, so it's not just a wrong printf. Plz repair!
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Processed: bug 824790 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=109581

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 824790 https://bugzilla.kernel.org/show_bug.cgi?id=109581
Bug #824790 [src:linux] linux-image-4.5.0-1-amd64: lots of WARNINGs in 
hfsc_dequeue+0x300/0x320 when using sch_hfsc+sch_codel
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=109581'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
824790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#824854: marked as done (Supermicro X9SRW-F: AE_NOT_FOUND, while evaluating GPE method _L24)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:34:09 -0700 (PDT)
with message-id <60983931.1c69fb81.6f159.2...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #824854,
regarding Supermicro X9SRW-F: AE_NOT_FOUND, while evaluating GPE method _L24
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.)


-- 
824854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:  linux-image
Version: 3.16.0-4-amd64

We faced with acpi problem in our Supermicro SYS-5027R-WRF server, motherboard 
X9SRW-F. We have latest BIOS version 3.2a from Supermicro. We tested Debian 8.4 
and CentOS 7 distros with default kernels. This problem doesn't appear in old 
2.6 kernels with CentOS 6 for example. We also tried Debian's 4.x kernel and 
this problem still exists. Is it critical problem? Or we can just use 3.16 
kernels and ignore this messages and disable these events?

Here are these two errors:

[0.410480] ACPI Error: [\_SB_.PRAD] Namespace lookup failure, AE_NOT_FOUND 
(20130517/psargs-359)
[0.410483] ACPI Error: Method parse/execution failed [\_GPE._L24] (Node 
880853ca18c0), AE_NOT_FOUND (20130517/psparse-536)
[0.410487] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L24] 
(20130517/evgpe-579)



---
Best regards,
Olga Ukhina
email - oukh...@newsru.com
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#824790: linux-image-4.5.0-1-amd64: lots of WARNINGs in hfsc_dequeue+0x300/0x320 when using sch_hfsc+sch_codel

[Salvatore Bonaccorso]

Source: linux
Source-Version: 4.18~rc3-1~exp1

On Thu, May 19, 2016 at 09:12:46PM +0200, Mirek Kratochvil wrote:
> Package: src:linux
> Version: 4.5.1-1
> Severity: normal
> Tags: upstream
> 
> Dear Maintainer,
> 
> When attaching a codel or fq_codel qdisc to a leaf hfsc class, sometimes a
> bunch of warnings (dmesg attached) show up. That would not be a problem, but
> the warnings seem to be triggered for each packet for some time, and as a side
> situation the processing renders the system more or less unresponsive for
> several seconds (which may be a problem for QoS machine).
> 
> A bug that is probably related (but concerning hfsc+sfq) is #631945 , my
> configuration is mostly the same, except with codel instead of SFQ. No similar
> fix exists for codel.
> 
> When trying to rule out the causes, I found that the amount of traffic doesn't
> matter (the machine is currently processing around 1Gbit/s). fq_codel shows 
> the
> same behavior, no other qdisc I tested causes the warnings.
> 
> I hope someone could point out what's wrong with codel, if I see the cause I
> can write/send a patch to upstream.

This issue appears to have been fixed in 4.18-rc3 upstream. Closing
accordingly.

Regards,
Salvatore

Bug#824132: marked as done (mmc0: Timeout waiting for hardware interrupt.)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:28:38 -0700 (PDT)
with message-id <609837e6.1c69fb81.590f0.f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #824132,
regarding mmc0: Timeout waiting for hardware interrupt.
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.)


-- 
824132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.3-2
Severity: normal

Dear Maintainer,

The kernel fails to read any SD card on my Acer V5-171 laptop with the 
following error "mmc0: Timeout waiting for hardware interrupt."
See the attached dmesg log.
Obviously the same SD card can be read just fine if the laptop is rebooted to 
Windows.


Note that this is a long standing bug:
* It was reported against 3.2.0-4 in bug 711526
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711526

* There is also the 73241 kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=73241

-- Package-specific info:
** Version:
Linux version 4.5.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160429 (Debian 5.3.1-17) ) #1 SMP Debian 4.5.3-2 (2016-05-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.5.0-2-amd64 
root=UUID=81c2584b-b364-4576-bd04-bf290ed51205 ro

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[1.211091] tg3 :04:00.0 eth0: Tigon3 [partno(BCM57785) rev 57785100] 
(PCI Express) MAC address b8:88:e3:0f:3e:60
[1.212285] tg3 :04:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T 
Ethernet) (WireSpeed[1], EEE[1])
[1.213285] tg3 :04:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] 
TSOcap[1]
[1.214282] tg3 :04:00.0 eth0: dma_rwctrl[0001] dma_mask[64-bit]
[1.215650] sdhci-pci :04:00.1: SDHCI controller found [14e4:16bc] (rev 
10)
[1.218393] mmc0: SDHCI controller on PCI [:04:00.1] using ADMA 64-bit
[8.645764] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[8.646123] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[8.646207] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input13
[8.656694] uvcvideo: Found UVC 1.00 device HD WebCam (04f2:b336)
[8.660521] uvcvideo 1-1.3:1.0: Entity type for entity Processing 2 was not 
initialized!
[8.660525] uvcvideo 1-1.3:1.0: Entity type for entity Extension 6 was not 
initialized!
[8.660526] uvcvideo 1-1.3:1.0: Entity type for entity Camera 1 was not 
initialized!
[8.660622] input: HD WebCam as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input14
[8.660679] usbcore: registered new interface driver uvcvideo
[8.660679] USB Video Class driver (1.1.1)
[8.664304] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[8.664579] ieee80211 phy0: Atheros AR9462 Rev:2 mem=0xc9a0, 
irq=17
[8.691320] Bluetooth: Core ver 2.21
[8.691335] NET: Registered protocol family 31
[8.691336] Bluetooth: HCI device and connection manager initialized
[8.691340] Bluetooth: HCI socket layer initialized
[8.691342] Bluetooth: L2CAP socket layer initialized
[8.691350] Bluetooth: SCO socket layer initialized
[8.816082] iTCO_vendor_support: vendor-support=0
[8.827304] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[8.827350] iTCO_wdt: Found a Panther Point TCO device (Version=2, 
TCOBASE=0x0460)
[8.827468] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[8.834039] usbcore: registered new interface driver btusb
[8.847022] usbcore: registered new interface driver ath3k
[9.028897] Console: switching to colour frame buffer device 170x48
[9.206796] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[9.277407] intel_rapl: Found RAPL domain package
[9.277408] intel_rapl: Found RAPL domain core
[9.277410] intel_rapl: Found RAPL domain uncore
[9.277416] intel_rapl: RAPL package 0 domain package locked by BIOS
[9.988835] Adding 7812092k swap on /dev/sda6.  Priority:-1 extents:1 
across:7812092k FS
[   10.043585] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT 
filesystems, filesystem will be case sensitive!
[   10.135305] FAT-fs (sda2): Volume was not properly unmounted. Some data may 
be corrupt. Please run fsck.
[   11.323953] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: 
(null)
[   11.993761] ip_tables: (C) 2000-2006 Netfilter Core Team
[   

Bug#824091: marked as done (linux-image-4.4.0-0.bpo.1-amd64: GPF on hot drive removal)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:26:57 -0700 (PDT)
with message-id <60983781.1c69fb81.6a5d.0...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #824091,
regarding linux-image-4.4.0-0.bpo.1-amd64: GPF on hot drive removal
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.)


-- 
824091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.4.6-1~bpo8+1
Severity: normal

Dear Maintainer,

I'm going through old hard drives, ddrescuing the old contents off, zeroing the 
drives, and recycling them.

I had one drive which refused to read any sectors - if I let the drive 
eventually time out, or unplug the drive, I either get a GPF or an Oops in my 
kernel log.

The GPF follows - I could be mistaken, but I don't expect an IO error to 
trigger a GPF in the kernel.

Please let me know if I can report any additional information to help with this.

- Rich

-- Package-specific info:
** Version:
Linux version 4.4.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.4.0-0.bpo.1-amd64 
root=UUID=3fdcdefe-8a65-4de2-858a-4354ae1f09f0 ro quiet

** Tainted: PDO (4225)
 * Proprietary module has been loaded.
 * Kernel has oopsed before.
 * Out-of-tree module has been loaded.

** Kernel log:
[225351.381513] sd 7:0:0:0: [sdo] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[225351.381524] sd 7:0:0:0: [sdo] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
[225351.381529] blk_update_request: I/O error, dev sdo, sector 0
[225351.381590] Buffer I/O error on dev sdo, logical block 0, async page read
[225351.381706] ldm_validate_partition_table(): Disk read failed.
[225351.381736] Dev sdo: unable to read RDB block 0
[225351.381814]  sdo: unable to read partition table
[225351.382186] sd 7:0:0:0: [sdo] Read Capacity(10) failed: Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[225351.382194] sd 7:0:0:0: [sdo] Sense not available.
[225351.382245] sd 7:0:0:0: [sdo] Attached SCSI disk
[225351.617213] general protection fault:  [#1] SMP 
[225351.617254] Modules linked in: uas usb_storage iptable_filter ip_tables 
x_tables 8021q garp binfmt_misc mrp stp llc tcm_loop tcm_qla2xxx qla2xxx 
ib_srpt iscsi_target_mod vhost_scsi vhost tcm_fc libfc scsi_transport_fc 
target_core_file target_core_iblock target_core_pscsi target_core_mod configfs 
cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace nfsd 
auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi tcp_htcp intel_rapl zfs(PO) iosf_mbi x86_pkg_temp_thermal 
intel_powerclamp coretemp zunicode(PO) kvm_intel zcommon(PO) kvm znvpair(PO) 
irqbypass crct10dif_pclmul crc32_pclmul spl(O) zavl(PO) iTCO_wdt 
iTCO_vendor_support mxm_wmi joydev hwmon_vid sha256_ssse3 sha256_generic
[225351.617790]  hmac loop ipmi_watchdog drbg ansi_cprng ast ttm aesni_intel 
aes_x86_64 lrw drm_kms_helper gf128mul glue_helper ablk_helper evdev drm cryptd 
ioatdma sb_edac mei_me lpc_ich pcspkr i2c_i801 edac_core mfd_core mei shpchp 
8250_fintek wmi tpm_tis tpm acpi_pad processor button ipmi_si ipmi_poweroff 
ipmi_devintf ipmi_msghandler fuse parport_pc ppdev lp parport autofs4 ext4 
crc16 mbcache jbd2 btrfs xor raid6_pq md_mod dm_mirror dm_region_hash dm_log 
dm_mod sg ses enclosure sd_mod hid_generic usbhid hid ahci libahci xhci_pci 
crc32c_intel ehci_pci mpt3sas igb xhci_hcd ehci_hcd raid_class ixgbe libata 
scsi_transport_sas i2c_algo_bit vxlan ip6_udp_tunnel dca udp_tunnel usbcore ptp 
scsi_mod usb_common pps_core mdio fjes
[225351.618287] CPU: 3 PID: 25432 Comm: ntpq Tainted: P   O
4.4.0-0.bpo.1-amd64 #1 Debian 4.4.6-1~bpo8+1
[225351.618343] Hardware name: Supermicro Super Server/X10SDV-TLN4F, BIOS 1.0b 
09/09/2015
[225351.618388] task: 8808401c7100 ti: 88066074 task.ti: 
88066074
[225351.618429] RIP: 0010:[]  [] 
anon_vma_interval_tree_remove+0x25/0x230
[225351.618489] RSP: 0018:880660743cd8  EFLAGS: 00010206
[225351.618520] RAX: 8806857478c9 RBX: 88063aa03ac0 RCX: 
6579010300024b24
[225351.618560] RDX: 0073 RSI: 880685747909 RDI: 
880615b3f180
[225351.618599] RBP: 88029185fdc0 R08:  R09: 

[225351.618639] R10: 8805986685a0 R11: 880615b3f1a0 R12: 

Bug#823601: marked as done (linux-image-4.5.0-1-amd64: radeon related errors reported)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:22:37 -0700 (PDT)
with message-id <6098367d.1c69fb81.754d6.f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #823601,
regarding linux-image-4.5.0-1-amd64: radeon related errors reported
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.)


-- 
823601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.1-1
Severity: normal

Dear Maintainer,

The boot log and kernel messages report some issues related to the radeon 
module :

[   30.400180] radeon :01:00.0: ring 5 stalled for more than 1msec
[   30.400210] radeon :01:00.0: GPU lockup (current fence id 
0x0002 last fence id 0x0004 on ring 5)
[   30.400298] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
[   30.400342] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

and

[   52.055063] radeon :01:00.0: VCE init error (-110).

I'm not sure how bad that is, but this seems much worse than with previous 4.x 
kernel where all these wouldn't pop up.

Apart from that, I'm not using the GPU much, so I haven't noticed other 
problems.

Hope this helps,

Best regards,

-- Package-specific info:
** Version:
Linux version 4.5.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

** Command line:
BOOT_IMAGE=/vmlinuz-4.5.0-1-amd64 root=/dev/mapper/main-slash ro quiet splash

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   20.249771] [drm] ib test on ring 0 succeeded in 0 usecs
[   20.249805] [drm] ib test on ring 1 succeeded in 0 usecs
[   20.249829] [drm] ib test on ring 2 succeeded in 0 usecs
[   20.249852] [drm] ib test on ring 3 succeeded in 0 usecs
[   20.249902] [drm] ib test on ring 4 succeeded in 0 usecs
[   20.651831] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   20.667392] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   20.669342] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   20.875974] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.174059] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[   21.576937] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   22.655248] wlan0: authenticate with f4:ca:e5:d5:80:d8
[   22.669966] wlan0: send auth to f4:ca:e5:d5:80:d8 (try 1/3)
[   22.671931] wlan0: authenticated
[   22.679858] wlan0: associate with f4:ca:e5:d5:80:d8 (try 1/3)
[   22.683384] wlan0: RX AssocResp from f4:ca:e5:d5:80:d8 (capab=0x411 status=0 
aid=5)
[   22.683481] wlan0: associated
[   22.683518] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   30.400180] radeon :01:00.0: ring 5 stalled for more than 1msec
[   30.400210] radeon :01:00.0: GPU lockup (current fence id 
0x0002 last fence id 0x0004 on ring 5)
[   30.400298] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
[   30.400342] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).
[   31.101750] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   31.159859] Ebtables v2.0 registered
[   32.009144] tun: Universal TUN/TAP device driver, 1.6
[   32.009147] tun: (C) 1999-2004 Max Krasnyansky 
[   32.084310] device virbr0-nic entered promiscuous mode
[   32.530806] virbr0: port 1(virbr0-nic) entered listening state
[   32.530820] virbr0: port 1(virbr0-nic) entered listening state
[   32.618372] virbr0: port 1(virbr0-nic) entered disabled state
[   32.623082] device virbr0-nic left promiscuous mode
[   32.623096] virbr0: port 1(virbr0-nic) entered disabled state
[   51.950206] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
[   51.950211] [drm] PCIE gen 3 link speeds already enabled
[   51.954041] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
[   51.954133] radeon :01:00.0: WB enabled
[   51.954135] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x880220391c00
[   51.954136] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0x880220391c04
[   51.954137] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x880220391c08
[   51.954138] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 

Bug#823997: marked as done (linux-image-4.5.0-1-amd64: Kernel crashes on reboot)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:25:46 -0700 (PDT)
with message-id <6098373a.1c69fb81.b1422.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #823997,
regarding linux-image-4.5.0-1-amd64: Kernel crashes on reboot
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.)


-- 
823997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.1-1
Severity: normal

Dear Maintainer,


When rebooting my machine after upgrading the system with apt-get dist-upgrade, 
the kernel crashed.
Here are two screenshots of the error message:
http://kacianka.at/misc/debian_bug1.png
http://kacianka.at/misc/debian_bug2.png

After cutting the power, the machine booted fine again (proably with the new 
kernel).

If there is any way to help you narrow down the bug, please just send me an 
e-mail!

Cheers,
Severin



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20CLS5FY00
product_version: ThinkPad X250
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N10ET36W (1.15 )
board_vendor: LENOVO
board_name: 20CLS5FY00
board_version: Not Defined

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: Lenovo Broadwell-U Host Bridge -OPI [17aa:2226]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U 
Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
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
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller 
[8086:160c] (rev 09)
Subsystem: Lenovo Broadwell-U Audio Controller [17aa:2226]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI 
Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
Subsystem: Lenovo Wildcat Point-LP USB xHCI Controller [17aa:2226]
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
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI 
Controller #1 [8086:9cba] (rev 03)
Subsystem: Lenovo Wildcat Point-LP MEI Controller [17aa:2226]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) 
I218-LM [8086:15a2] (rev 03)
Subsystem: Lenovo Ethernet Connection (3) I218-LM [17aa:2226]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller [8086:9ca0] (rev 03)
Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller 
[17aa:2226]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #6 [8086:9c9a] 

Bug#823485: marked as done (kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able)

[Debian Bug Tracking System]

Your message dated Sun, 9 May 2021 21:21:09 +0200
with message-id 
and subject line Re: Bug#823485: kernel: brcmsmac bcma0:1: START: tid 1 is not 
agg'able
has caused the Debian Bug report #823485,
regarding kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able
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.)


-- 
823485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.2-1
Severity: normal
File: brcmsmac

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have the following WiFi hardware in my laptop:

03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn
Wireless Network Adapter [14e4:4727] (rev 01)
Subsystem: Hewlett-Packard Company BCM4313 802.11bgn Wireless Network
Adapter [103c:145c]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at 9240 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-38-ff-ff-02-c1-c2
Capabilities: [16c] Power Budgeting 
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma

When I'm using the wireless connection, I get lots of the following errors:

...
kernel: brcmsmac bcma0:1: START: tid 2 is not agg'able
kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able
...

The rate is about 150/h. I don't know what the errors mean, but I haven't
noticed any problems with my WiFi connection. I think it works just fine.

Is there a way to remove the message from the log? Does anyone know what the
message means, and maybe how to fix the problem?



- -- Package-specific info:
** Version:
Linux version 4.5.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1
20160424 (Debian 5.3.1-16) ) #1 SMP Debian 4.5.2-1 (2016-04-28)

** Command line:
BOOT_IMAGE=../vmlinuz-4.5.0-2-amd64 root=/dev/mapper/debian_laptop-root
acpi_osi="!Windows 2012" acpi=force acpi_enforce_resources=lax
cgroup_enable=memory net.ifnames=0 biosdevname=0 apparmor=1 security=apparmor
udev.children-max=64 plymouth.enable=1 quiet splash ro
initrd=../initrd.img-4.5.0-2-amd64

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:

** Model information
sys_vendor: Hewlett-Packard
product_name: HP G62 Notebook PC
product_version: 059411252710001020100
chassis_vendor: Hewlett-Packard
chassis_version: Chassis Version
bios_vendor: Hewlett-Packard
bios_version: F.48
board_vendor: Hewlett-Packard
board_name: 1439
board_version: 60.50

** Loaded modules:
uas(E)
option(E)
huawei_cdc_ncm(E)
usb_wwan(E)
cdc_wdm(E)
cdc_ncm(E)
usbnet(E)
usb_storage(E)
usbserial(E)
pci_stub(E)
vboxpci(OE)
vboxnetadp(OE)
vboxnetflt(OE)
vboxdrv(OE)
bridge(E)
stp(E)
llc(E)
ctr(E)
ccm(E)
cpufreq_conservative(E)
cpufreq_userspace(E)
cpufreq_powersave(E)
cpufreq_stats(E)
cls_fw(E)
sch_ingress(E)
cls_u32(E)
sch_htb(E)
ip6t_REJECT(E)
nf_reject_ipv6(E)
nf_log_ipv6(E)
ip6table_filter(E)
ip6table_mangle(E)
ip6_tables(E)
nf_log_ipv4(E)
nf_log_common(E)
xt_LOG(E)
xt_limit(E)
xt_pkttype(E)
ipt_REJECT(E)
nf_reject_ipv4(E)
ipt_SYNPROXY(E)
nf_synproxy_core(E)
xt_conntrack(E)
iptable_filter(E)
ipt_MASQUERADE(E)
nf_nat_masquerade_ipv4(E)
iptable_nat(E)
nf_nat_ipv4(E)
nf_nat(E)
xt_TCPMSS(E)
xt_comment(E)
xt_owner(E)
xt_mark(E)
iptable_mangle(E)
xt_tcpudp(E)
xt_CT(E)
xt_multiport(E)
xt_set(E)
iptable_raw(E)
ip_tables(E)
hid_a4tech(E)
ip_set_hash_ip(E)
ip_set_hash_net(E)
ip_set(E)
nfnetlink(E)
nfs(E)
lockd(E)
grace(E)
sunrpc(E)
fscache(E)
arc4(E)
brcmsmac(E)
cordic(E)
brcmutil(E)
mac80211(E)
hp_wmi(E)
sg(E)
acpi_cpufreq(E)
bcma(E)
iTCO_wdt(E)
iTCO_vendor_support(E)
lpc_ich(E)
mfd_core(E)
mei_me(E)
mei(E)
sparse_keymap(E)
i2c_i801(E)
processor(E)
ac(E)
battery(E)
tpm_tis(E)
joydev(E)
serio_raw(E)
shpchp(E)
tpm(E)
cfg80211(E)
intel_powerclamp(E)
evdev(E)
rfkill(E)
eeprom(E)
snd_hda_codec_hdmi(E)
tun(E)
snd_hda_codec_realtek(E)
snd_hda_codec_generic(E)
xt_recent(E)
snd_hda_intel(E)
snd_hda_codec(E)
snd_hda_core(E)
snd_hwdep(E)
snd_pcm(E)
snd_timer(E)
snd(E)
soundcore(E)
act_mirred(E)
sch_fq_codel(E)
xt_connmark(E)
ifb(E)
nf_conntrack_ipv6(E)
nf_defrag_ipv6(E)
nf_conntrack_ipv4(E)
nf_defrag_ipv4(E)
nf_conntrack(E)
cls_cgroup(E)

Processed: fixed 823485 in 4.9.210-1, fixed 823485 in 4.19.87-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 823485 4.9.210-1
Bug #823485 [src:linux] kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able
Marked as fixed in versions linux/4.9.210-1.
> fixed 823485 4.19.87-1
Bug #823485 [src:linux] kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able
Marked as fixed in versions linux/4.19.87-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#823434: marked as done (Crash in wheezy-backports kernels on skb_release_data)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 12:16:48 -0700 (PDT)
with message-id <60983520.1c69fb81.dc0da.d...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #823434,
regarding Crash in wheezy-backports kernels on skb_release_data
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.)


-- 
823434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-0.bpo.4-amd64
Version: multiple

We're seeing a crash once or twice a week across multiple machines running 
various versions of the wheezy-backports 3.16 kernel. Here is an excerpt from 
one of the dumps we captured. Unfortunately, the top was cut off due to the 
screen size, but the most important stuff appears to be intact:

task: 880199212b60 ti: 88019922 task.ti: 88019922
RIP: 0010:[]  [] skb_release_data+0xe3/0x110
RSP: 0018:88031fae3c20  EFLAGS: 00010202
RAX: 0001 RBX: 8802b1c448c0 RCX: b1c44800
RDX: 0060 RSI: fe01 RDI: 0101010101010101
RBP: 0001 R08: 880318d3d798 R09: 0002
R10: 8802d5f75e00 R11: 001b R12: 8802d5f75e00
R13: 003b R14: 8802a69fca10 R15: 8802ef350100
FS:  () GS:88031fae() knlGS:
CS:  0010 DS:  ES:  CR0: 8005003b
CR2: ff600400 CR3: 01813000 CR4: 07e0
Stack:
  4f00 8802d5f75e00  8140b817
  4f00 8802d5f75e00 81456058 0014
  004f0010 058eb1c44800 8802fc4a 0010
Call Trace:
 
 [] ? consume_skb+0x27/0x80
 [] ? ip_fragment+0x5b8/0x880
 [] ? skb_set_owner_w+0x50/0x50
 [] ? ip_finish_output+0x53c/0x840
 [] ? __netif_receive_skb_core+0x533/0x750
 [] ? read_tsc+0x5/0x20
 [] ? netif_receive_skb_internal+0x1f/0x90
 [] ? dev_gro_receive+0x1df/0x2e0
 [] ? napi_gro_receive+0x27/0xe0
 [] ? bnx2_poll_work+0x7e4/0x1230 [bnx2]
 [] ? bnx2_poll_msix+0x2d/0xb0 [bnx2]
 [] ? net_rx_action+0x140/0x240
 [] ? __do_softirq+0xf1/0x290
 [] ? irq_exit+0x95/0xa0
 [] ? do_IRQ+0x52/0xe0
 [] ? common_interrupt+0x6d/0x6d
 
 [] ? cpuidle_enter_state+0x4f/0xc0
 [] ? cpuidle_enter_state+0x48/0xc0
 [] ? cpu_startup_entry+0x2f8/0x400
 [] ? start_secondary+0x20f/0x2d0
Code: 8b 9c 24 cc 00 00 00 49 03 9c 24 d0 00 00 00 48 8b 7b 08 48 85 ff 75 13 
5b 5d 4c 89 e7 41 5c e9 a4 fe ff ff 0f 1f 40 00 48 89 ef <48> 8b 2f e8 75 00 00 
00 48 85 ed 75 f0 48 c7 43 08 00 00 00 00
RIP  [] skb_release_data_0xe3/0x110
 RSP 
[ end trace 35ec23bf75ec9349 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Kernel Offset: 0x0 from 0x8100 (relocation range: 
0x8000-0x9fff)

Some sleuthing led me to https://lkml.org/lkml/2016/1/6/627 which doesn't look 
exactly the same, but may be related, particularly since we are routing between 
networks with a variety of MTU values, and fragmentation is common. The fix for 
that is at 
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9207f9d45b0ad071baa128e846d7e7ed85016df3

--
James Oakley
james.oak...@multapplied.net
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#823107: marked as done (local{mod,yes}config should fix references to unavailable certificates)

[Debian Bug Tracking System]

Your message dated Sun, 9 May 2021 21:15:24 +0200
with message-id 
and subject line Re: Bug#823107: linux: make deb-pkg fails: No rule to make 
target 'debian/certs/b...@debian.org.cert.pem')
has caused the Debian Bug report #823107,
regarding local{mod,yes}config should fix references to unavailable certificates
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.)


-- 
823107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.2-1

Dear maintainer:

I merged the output of "lsmod" in two different virtual machines
running stretch/sid to create a minimal kernel which works on both.

The combined file is attached as "lsmod.txt".

Then I created a .config file by executing this script:


#!/bin/sh
cd linux-source-4.5
rm -f .config
make LSMOD=../lsmod.txt localyesconfig
cp -p .config ../dot.config

The resulting file, dot.config, is also attached.


Then I tried to use upstream target, as recommended, to create a .deb
package for the kernel, using this script:


#!/bin/sh
cd linux-source-4.5
time -p make -j4 EXTRAVERSION="-qemu-amd64" KDEB_PKGVERSION=$(make 
kernelversion)-$(date +%Y%m%d).0 bindeb-pkg


I already did this in jessie so I expected this to work on stretch as
well, but this is what heppened:


make[3]: *** No rule to make target 'debian/certs/b...@debian.org.cert.pem', 
needed by 'certs/x509_certificate_list'.  Stop.
Makefile:954: recipe for target 'certs' failed
make[2]: *** [certs] Error 2
make[2]: *** Waiting for unfinished jobs
  CHK include/generated/compile.h
  CHK kernel/config_data.h
scripts/package/Makefile:97: recipe for target 'bindeb-pkg' failed
make[1]: *** [bindeb-pkg] Error 2
Makefile:1255: recipe for target 'bindeb-pkg' failed
make: *** [bindeb-pkg] Error 2
Command exited with non-zero status 2


Does this mean I need your key to build a custom kernel? I hope not.

Should I remove CONFIG_SYSTEM_TRUSTED_KEYS from .config before building
the kernel? I hope not.

Maybe "make localyesconfig" should not take CONFIG_SYSTEM_TRUSTED_KEYS
from the running kernel or the linux-source package? I don't know.

To summarize: I think this should work without having to do anything
special, but currently, it does not.

Thanks.8250_fintek
ablk_helper
acpi_cpufreq
aesni_intel
aes_x86_64
ansi_cprng
ata_generic
ata_piix
autofs4
button
cirrus
crc16
crc32c_generic
crc32c_intel
crc32_pclmul
crct10dif_pclmul
cryptd
dm_mod
drbg
drm
drm_kms_helper
ehci_hcd
ehci_pci
evdev
ext4
floppy
gf128mul
ghash_clmulni_intel
glue_helper
hmac
i2c_piix4
irqbypass
jbd2
jitterentropy_rng
joydev
kvm
kvm_intel
libata
lrw
mbcache
Module
parport
parport_pc
pcspkr
ppdev
processor
psmouse
pvpanic
qxl
scsi_mod
serio_raw
tpm
tpm_tis
ttm
uhci_hcd
usb_common
usbcore
virtio
virtio_balloon
virtio_blk
virtio_console
virtio_net
virtio_pci
virtio_ring
virtio_scsi


dot.config.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.7~rc3-1~exp1

Hi,

On Sat, Apr 30, 2016 at 11:41:09PM +0200, Ben Hutchings wrote:
> Control: reopen -1
> Control: retitle -1 local{mod,yes}config should fix references to unavailable 
> certificates
> Control: tag -1 upstream
> 
> On Sat, 2016-04-30 at 23:24 +0200, Santiago Vila wrote:
> > On Sat, Apr 30, 2016 at 08:51:25PM +, Debian Bug Tracking System wrote:
> > 
> > > 
> > > You wrote:
> > > [...]
> > > > 
> > > > Should I remove CONFIG_SYSTEM_TRUSTED_KEYS from .config before building
> > > > the kernel? I hope not.
> > > [...]
> > > 
> > > Yes, you must do that.  Your custom kernel configuration should be
> > > based on the appropriate file provided in linux-source-4.5.  These have
> > > the CONFIG_MODULE_SIG_ALL, CONFIG_MODULE_SIG_KEY and
> > > CONFIG_SYSTEM_TRUSTED_KEYS settings removed so that custom kernels will
> > > get modules signed by a one-time key.
> > If I have to remove CONFIG_SYSTEM_TRUSTED_KEYS by hand, then
> > documentation is wrong.
> [...]
> 
> Oh, I see the problem.  I didn't realise that the local{mod,yes}config
> rules would (a) copy the config file from /boot or (b) keep the keyring
> config symbols unchanged.

This seems to be fixed since 4.7-rc1 with upstream commit 96bab35d1c4a
("localmodconfig: Reset certificate paths").

Regards,
Salvatore--- End Message ---

Processed: Re: Bug#795013: Closing this bug (BTS maintenance for src:linux bugs)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 795013
Bug #795013 {Done: car...@debian.org} [src:linux] "gdm3 won't start due to an 
error in kernel"
Bug reopened
Ignoring request to alter fixed versions of bug #795013 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
795013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817049: marked as done (linux-image-3.16.0-4-amd64: execve() gives EEXIST error under NFS if the file has been regenerated on a different machine)

[Debian Bug Tracking System]

Your message dated Sun, 9 May 2021 18:35:20 +0200
with message-id <20210509163520.gp1791...@zira.vinc17.org>
and subject line Re: Bug#817049: linux-image-3.16.0-4-amd64: execve() gives 
EEXIST error under NFS if the file has been regenerated on a different machine
has caused the Debian Bug report #817049,
regarding linux-image-3.16.0-4-amd64: execve() gives EEXIST error under NFS if 
the file has been regenerated on a different machine
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.)


-- 
817049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal

Under NFS, when an executable has been regenerated on a different machine,
execve() gives me an EEXIST error. To reproduce the bug:

francine:~> touch bin/tst
francine:~> cat bin/tst

cassis:~> cat tst.c
int main (void)
{ return 0; }
cassis:~> gcc -O3 tst.c -o tst
cassis:~> mv tst bin/
mv: overwrite ‘bin/tst’? y

At this point, I have to wait for 15 seconds for the "mv" to be
done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799838

After that:

francine:~> strace -f -o tst.out sh -c "exec $HOME/bin/tst"
sh: 1: exec: /home/vlefevre/bin/tst: File exists
zsh: exit 2 strace -f -o tst.out sh -c "exec $HOME/bin/tst"
francine:~[2]> cat tst.out
21573 execve("/bin/sh", ["sh", "-c", "exec /home/vlefevre/bin/tst"], [/* 120 
vars */]) = 0
21573 brk(0)= 0x7f4aded7d000
21573 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
21573 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded46000
21573 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64", 
0x7ffec78d5b00) = -1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls", 0x7ffec78d5b00) = -1 
ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/x86_64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/x86_64", 0x7ffec78d5b00) = 
-1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib", {st_mode=S_IFDIR|0755, 
st_size=13, ...}) = 0
21573 open("/usr/local/lib/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
21573 stat("/usr/local/lib/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such 
file or directory)
21573 open("/usr/local/lib/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
21573 stat("/usr/local/lib/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/usr/local/lib/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
(No such file or directory)
21573 stat("/usr/local/lib/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file 
or directory)
21573 open("/usr/local/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/usr/local/lib", {st_mode=S_IFDIR|S_ISGID|0775, st_size=4096, ...}) 
= 0
21573 open("/lib64/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
21573 stat("/lib64/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/lib64/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/lib64/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or directory)
21573 open("/lib64/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/lib64/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
21573 read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"..., 832) = 832
21573 fstat(3, {st_mode=S_IFREG|0755, st_size=1738176, ...}) = 0
21573 mmap(NULL, 3844640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) 
= 0x7f4ade55f000
21573 mprotect(0x7f4ade701000, 2093056, PROT_NONE) = 0
21573 mmap(0x7f4ade90, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a1000) = 0x7f4ade90
21573 mmap(0x7f4ade906000, 

Bug#809149: Closing this bug (BTS maintenance for src:linux bugs)

[Vincent Lefevre]

On 2021-05-09 07:21:07 -0700, car...@debian.org wrote:
> This bug was filed for a very old kernel or the bug is old itself
> without resolution.

I confirm that the bug is obsolete. (I'm not sure I could ever
reproduce it.)

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#800627: linux: fs/isofs/util.c iso_date() will map years >= 2028 to 1970

[Thomas Schmitt]

Hi,

Salvatore Bonaccorso wrote:
> This has been fixed upstream with 34be4dbf87fc ("isofs: fix timestamps
> beyond 2027") which was backported to various table series.
> [committed 2017]

Regrettably it does not suffice, because of the remaining int bottleneck
iso_date(), which is still to see in line 19 of
  https://github.com/torvalds/linux/blob/master/fs/isofs/util.c

For the records and with me duely acknowledging that Debian is not
in charge of fixing this, here is my unposted patch set for the kernel
branch of Jens Axboe as of september 2020.
  git://git.kernel.dk/linux-block

---

From 154a68527351db091e5de60388ba4cfb1fe779fd Mon Sep 17 00:00:00 2001
From: Thomas Schmitt 
Date: Mon, 21 Sep 2020 18:20:14 +0200
Subject: [PATCH 0/1] isofs: prevent file time rollover after year 2038

The time values in struct inode of isofs result from calls to function
iso_date() in isofs/util.c, which returns seconds in the range of signed
int. This will rollover in 2038.
ISO 9660 directory record timestamps are good for up to year 2155.
(ECMA-119 9.1.5: 1900 + 255)

The only callers of iso_date() are in isofs/inode.c and isofs/rock.c
and put the result into struct inode.i_{a,c,m}time.tv_sec which is
of type time64_t.
The time value of iso_date() essentially stems from mktime64().

So return type time64_t is appropriate for iso_date().

--
Demonstration of the problem:

Create an ISO 9660 filesystem with file date in 2040, using file /bin/true
as victim payload:

  xorriso -outdev /tmp/test_date.iso \
  -blank as_needed \
  -map /bin/true /victim \
  -alter_date m 'Oct 01 22:06:12 2040' /victim --

Inspect the current representation by isofs:

  mount /tmp/test_date.iso /mnt/iso
  ls -l /mnt/iso/victim

This yields with int iso_date():

  ... Aug 26  1904 /mnt/iso/victim

After changing the type of iso_date() to time64_t:

  ... Oct  1  2040 /mnt/iso/victim

For completeness i tested the last possible second:

  xorriso ... -alter_date m 'Dec 31 23:59:59 2155' /victim --

and got properly:

  ... Dec 31  2155 /mnt/iso/victim

(When reproducing this it might be to wise to use December 30, to avoid
any potential timezone problems.)

--

Have a nice day :)

Thomas

Thomas Schmitt (1):
  isofs: prevent file time rollover after year 2038

 fs/isofs/isofs.h | 3 ++-
 fs/isofs/util.c  | 4 ++--
 2 files changed, 4 insertions(+), 3 deletions(-)

--
2.20.1

---

From 154a68527351db091e5de60388ba4cfb1fe779fd Mon Sep 17 00:00:00 2001
From: Thomas Schmitt 
Date: Mon, 21 Sep 2020 18:20:06 +0200
Subject: [PATCH 1/1] isofs: prevent file time rollover after year 2038

Change the return type of function iso_date() from int to time64_t.

Signed-off-by: Thomas Schmitt 
---
 fs/isofs/isofs.h | 3 ++-
 fs/isofs/util.c  | 4 ++--
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/fs/isofs/isofs.h b/fs/isofs/isofs.h
index 055ec6c586f7..527c0db72ff9 100644
--- a/fs/isofs/isofs.h
+++ b/fs/isofs/isofs.h
@@ -107,7 +107,8 @@ static inline unsigned int isonum_733(u8 *p)
/* Ignore bigendian datum due to broken mastering programs */
return get_unaligned_le32(p);
 }
-extern int iso_date(u8 *, int);
+
+time64_t iso_date(u8 *, int);

 struct inode;  /* To make gcc happy */

diff --git a/fs/isofs/util.c b/fs/isofs/util.c
index e88dba721661..348af786a8a4 100644
--- a/fs/isofs/util.c
+++ b/fs/isofs/util.c
@@ -16,10 +16,10 @@
  * to GMT.  Thus  we should always be correct.
  */

-int iso_date(u8 *p, int flag)
+time64_t iso_date(u8 *p, int flag)
 {
int year, month, day, hour, minute, second, tz;
-   int crtime;
+   time64_t crtime;

year = p[0];
month = p[1];
--
2.20.1

---

Have a nice day :)

Thomas

Bug#822936: marked as done (INFO: rcu_sched self-detected stall on CPU)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:20:28 -0700 (PDT)
with message-id <6097fdbc.1c69fb81.5fddc.5...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #822936,
regarding INFO: rcu_sched self-detected stall on 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.)


-- 
822936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-4-686-pae
Version: 3.16.7-ckt25-1

The netbook doesn't crash, but the entire networking stack freezes up.
When I press a key on the keyboard, the backlight comes on, and
everything is functional again.

Apr 27 21:53:20 ranfan kernel: INFO: rcu_sched self-detected stall on
CPU { 0}  (t=6590 jiffies g=23325 c=23324 q=2)
Apr 27 21:53:20 ranfan kernel: sending NMI to all CPUs:
Apr 27 21:53:20 ranfan kernel: NMI backtrace for cpu 0
Apr 27 21:53:20 ranfan kernel: CPU: 0 PID: 0 Comm: swapper/0 Not
tainted 3.16.0-4-686-pae #1 Debian 3.16.7-ckt25-1
Apr 27 21:53:20 ranfan kernel: Hardware name: Acer AO751h
 /JV11-ML  , BIOS V0.3212 02/26/2010
Apr 27 21:53:20 ranfan kernel: task: c15fca00 ti: c15ee000 task.ti: c15ee000
Apr 27 21:53:20 ranfan kernel: EIP: 0060:[] EFLAGS: 0026 CPU: 0
Apr 27 21:53:20 ranfan kernel: EIP is at
arch_trigger_all_cpu_backtrace+0x95/0xd0
Apr 27 21:53:20 ranfan kernel: EAX: 00418958 EBX: 2710 ECX:
f000 EDX: f000
Apr 27 21:53:20 ranfan kernel: ESI: c1614f80 EDI: f75d9620 EBP:
f5007e40 ESP: f5007e34
Apr 27 21:53:20 ranfan kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Apr 27 21:53:20 ranfan kernel: CR0: 8005003b CR2: b7765000 CR3:
0171e000 CR4: 07f0
Apr 27 21:53:20 ranfan kernel: Stack:
Apr 27 21:53:20 ranfan kernel:  c1548401 c157a0ce c1614f80 f5007e88
c10ac95d c1557924 19be 5b1d
Apr 27 21:53:20 ranfan kernel:  5b1c 0002  f5007e88
c1084790 0001 c166a5ec c1614f80
Apr 27 21:53:20 ranfan kernel:  f75d9620  c15fca00 
 f5007e9c c1062dac f5009f7c
Apr 27 21:53:20 ranfan kernel: Call Trace:
Apr 27 21:53:20 ranfan kernel:  [] ? rcu_check_callbacks+0x38d/0x5b0
Apr 27 21:53:20 ranfan kernel:  [] ? account_process_tick+0x60/0x130
Apr 27 21:53:20 ranfan kernel:  [] ? update_process_times+0x3c/0x60
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_sched_handle.isra.13+0x26/0x60
Apr 27 21:53:20 ranfan kernel:  [] ? tick_sched_timer+0x37/0x70
Apr 27 21:53:20 ranfan kernel:  [] ? __remove_hrtimer+0x38/0x90
Apr 27 21:53:20 ranfan kernel:  [] ? __run_hrtimer+0x6d/0x190
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_sched_handle.isra.13+0x60/0x60
Apr 27 21:53:20 ranfan kernel:  [] ? hrtimer_interrupt+0x1e8/0x2a0
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_do_broadcast.constprop.7+0x6b/0x70
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_handle_oneshot_broadcast+0x105/0x180
Apr 27 21:53:20 ranfan kernel:  [] ?
add_interrupt_randomness+0x15a/0x1a0
Apr 27 21:53:20 ranfan kernel:  [] ? timer_interrupt+0x12/0x20
Apr 27 21:53:20 ranfan kernel:  [] ?
handle_irq_event_percpu+0x35/0x180
Apr 27 21:53:20 ranfan kernel:  [] ? handle_irq_event+0x2a/0x50
Apr 27 21:53:20 ranfan kernel:  [] ? handle_simple_irq+0x70/0x70
Apr 27 21:53:20 ranfan kernel:  [] ? handle_edge_irq+0x66/0x100
Apr 27 21:53:20 ranfan kernel:  [] ? handle_irq+0x71/0x90
Apr 27 21:53:20 ranfan kernel:  
Apr 27 21:53:20 ranfan kernel:
Apr 27 21:53:20 ranfan kernel:  [] ? do_IRQ+0x3c/0xd0
Apr 27 21:53:20 ranfan kernel:  [] ? rebalance_domains+0x14e/0x250
Apr 27 21:53:20 ranfan kernel:  [] ? common_interrupt+0x33/0x38
Apr 27 21:53:20 ranfan kernel:  [] ?
psb_intel_sdvo_read_response+0xcb/0x200 [gma500_gfx]
Apr 27 21:53:20 ranfan kernel:  [] ? __do_softirq+0x6d/0x230
Apr 27 21:53:20 ranfan kernel:  [] ? cpu_callback+0x160/0x160
Apr 27 21:53:20 ranfan kernel:  [] ? do_softirq_own_stack+0x22/0x30
Apr 27 21:53:20 ranfan kernel:  
Apr 27 21:53:20 ranfan kernel:
Apr 27 21:53:20 ranfan kernel:  [] ? irq_exit+0x8d/0xa0
Apr 27 21:53:20 ranfan kernel:  [] ? do_IRQ+0x45/0xd0
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_broadcast_oneshot_control+0x7b/0x210
Apr 27 21:53:20 ranfan kernel:  [] ? common_interrupt+0x33/0x38
Apr 27 21:53:20 ranfan kernel:  [] ? cpuidle_enter_state+0x3e/0xd0
Apr 27 21:53:20 ranfan kernel:  [] ? cpu_startup_entry+0x2be/0x3b0
Apr 27 21:53:20 ranfan kernel:  [] ? start_kernel+0x3dd/0x3e2
Apr 27 21:53:20 ranfan kernel:  [] ? set_init_arg+0x45/0x45
Apr 27 21:53:20 ranfan kernel: Code: 08 5b 5d c3 66 90 f0 0f b3 15 a8
a4 66 c1 a1 a8 a4 66 c1 85 c0 75 3a 31 c0 bb 10 27 00 00 eb 1f 8d b6
00 

Bug#822225: marked as done (xserver-xorg-video-radeon: White glow and flicker on edges of LVDS display on boot)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:18:34 -0700 (PDT)
with message-id <6097fd4a.1c69fb81.4707.d...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #85,
regarding xserver-xorg-video-radeon: White glow and flicker on edges of LVDS 
display on boot
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.)


-- 
85: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=85
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-radeon
Version: 1:7.7.0-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
   I installed the open radeon driver package instead of the closed one

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Boot the system

   * What was the outcome of this action?
   Increasing white glow on the edges of the built in display, a freeze,
   some flicker and finally the normal boot process continues

   * What outcome did you expect instead?
   A normal boot process without the glitches

I am not sure if this is the fault of the display driver, but since it
looks like a display (or maybe backlight?) glitch, I though it was best
to report this under the video driver package. I am worried that it
might damage something hardware related, because it really doesn't look
healthy to me. I can upload a video of the problem if desired, because i
could not find anything in any logs.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Apr  2 21:28 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Apr  5 09:05 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Chelsea XT GL [FirePro M4000] [1002:682d]

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 967 Apr  4 02:55 touchpad.conf

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.5.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 46830 Apr 22 09:10 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[19.170] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[19.170] X Protocol Version 11, Revision 0
[19.170] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[19.170] Current Operating System: Linux tosti-ijzer 4.4.0-0.bpo.1-amd64 #1 
SMP Debian 4.4.6-1~bpo8+1 (2016-03-20) x86_64
[19.170] Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-0.bpo.1-amd64 
root=/dev/mapper/vg-root ro quiet splash
[19.170] Build Date: 11 February 2015  12:32:02AM
[19.170] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[19.170] Current version of pixman: 0.32.6
[19.170]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[19.170] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[19.170] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 22 08:21:42 
2016
[19.174] (==) Using config directory: "/etc/X11/xorg.conf.d"
[19.174] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[19.175] (==) No Layout section.  Using the first Screen section.
[19.175] (==) No screen section available. Using defaults.
[19.175] (**) |-->Screen "Default Screen Section" (0)
[19.175] (**) |   |-->Monitor ""
[19.176] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[19.176] (==) Automatically adding devices
[19.176] (==) Automatically enabling devices
[19.176] (==) Automatically adding GPU devices
[19.178] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[19.178]Entry deleted from font path.
[19.178] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[19.178]Entry deleted from font path.
[19.178] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[19.178]Entry deleted from font 

Bug#821462: marked as done (linux-image-4.5-amd64: jvpn doesn't work with linux 4.5.0)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:17:24 -0700 (PDT)
with message-id <6097fd04.1c69fb81.9c129.e...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #821462,
regarding linux-image-4.5-amd64: jvpn doesn't work with linux 4.5.0
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.)


-- 
821462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.5-amd64
Severity: normal

Dear Maintainer,

I'm using jvpn to connect to Juniper VPN.

It works fine with kernel version 4.4.6, but with 4.5.0 it's broken.
The output of the script looks fine, but when it ends, the network
becomes unavailable (both the VPN and internet access). Disconnecting
from the VPN brings the internet link back up.

When the link is down, it doesn't appear visually anywhere. Only
when I actually try to connect anywhere it fails.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#821371: marked as done (linux-image-4.4.0-0.bpo.1-686-pae: Intel i915 : xrandr -s does hang the kernel)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:15:51 -0700 (PDT)
with message-id <6097fca7.1c69fb81.69c99.a...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #821371,
regarding linux-image-4.4.0-0.bpo.1-686-pae: Intel i915 : xrandr -s does hang 
the 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.)


-- 
821371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.4.6-1~bpo8+1
Severity: normal

Dear Maintainer,

Each time that I run "xrandr -s 800x600" or "xrandr -s 1024x600", syslog logs
debug messages saying about issues of the kernel (see below).
No other effects out of this log.
xrandr seems to work fine.

$ xrandr
Screen 0: minimum 8 x 8, current 1024 x 600, maximum 32767 x 32767
LVDS1 connected 1024x600+0+0 (normal left inverted right x axis y axis) 195mm x 
113mm
   1024x600  60.00*+
   800x600   60.3256.25  
   640x480   59.94  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


-- Package-specific info:
** Version:
Linux version 4.4.0-0.bpo.1-686-pae (debian-kernel@lists.debian.org) (gcc 
version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.4.0-0.bpo.1-686-pae 
root=UUID=2ed3bc82-5cc0-4529-a13c-2e6f80b5b588 ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[ 2022.347925]  [] ? intel_atomic_commit+0xae1/0x12d0 [i915]
[ 2022.347971]  [] ? drm_atomic_check_only+0x2b5/0x650 [drm]
[ 2022.348012]  [] ? drm_modeset_lock+0x33/0xf0 [drm]
[ 2022.348052]  [] ? drm_atomic_set_crtc_for_connector+0x1d/0xa0 [drm]
[ 2022.348094]  [] ? drm_atomic_commit+0x32/0x60 [drm]
[ 2022.348118]  [] ? drm_atomic_helper_set_config+0x62/0xa0 
[drm_kms_helper]
[ 2022.348161]  [] ? drm_mode_set_config_internal+0x4e/0xc0 [drm]
[ 2022.348203]  [] ? drm_mode_setcrtc+0x1a4/0x570 [drm]
[ 2022.348247]  [] ? drm_mode_setplane+0x1d0/0x1d0 [drm]
[ 2022.348285]  [] ? drm_ioctl+0x14c/0x510 [drm]
[ 2022.348302]  [] ? fsnotify_destroy_event+0x27/0x50
[ 2022.348316]  [] ? fsnotify_destroy_event+0x27/0x50
[ 2022.348358]  [] ? drm_mode_setplane+0x1d0/0x1d0 [drm]
[ 2022.348401]  [] ? drm_getmap+0xc0/0xc0 [drm]
[ 2022.348415]  [] ? do_vfs_ioctl+0x322/0x550
[ 2022.348427]  [] ? dput+0xb7/0x210
[ 2022.348441]  [] ? __fsnotify_parent+0x96/0x100
[ 2022.348456]  [] ? vfs_write+0x150/0x1b0
[ 2022.348470]  [] ? SyS_ioctl+0x60/0x90
[ 2022.348485]  [] ? do_fast_syscall_32+0x93/0x220
[ 2022.348501]  [] ? sysenter_past_esp+0x3d/0x61
[ 2022.348545] ---[ end trace 10505acfd6e5984f ]---
[ 2029.524389] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
gmch_pfit.lvds_border_bits (expected 0x8000, found 0x)
[ 2029.524408] [ cut here ]
[ 2029.524519] WARNING: CPU: 0 PID: 641 at 
/home/zumbi/linux-4.4.6/drivers/gpu/drm/i915/intel_display.c:12812 
intel_atomic_commit+0xae1/0x12d0 [i915]()
[ 2029.524527] pipe state doesn't match!
[ 2029.524534] Modules linked in: sha256_generic hmac drbg ansi_cprng ctr ccm 
binfmt_misc iTCO_wdt iTCO_vendor_support arc4 uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media 
rt2800pci rt2800mmio rt2800lib rt2x00pci rt2x00mmio rt2x00lib eeprom_93cx6 
mac80211 coretemp evdev joydev i915 pcspkr cfg80211 serio_raw lpc_ich mfd_core 
eeepc_laptop crc_ccitt sparse_keymap i2c_i801 rfkill snd_hda_codec_realtek 
snd_hda_codec_generic rng_core snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep drm_kms_helper snd_pcm acpi_cpufreq tpm_tis snd_timer snd soundcore 
drm video i2c_algo_bit tpm battery ac shpchp button processor loop fuse 
parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 sg sd_mod 
ata_generic psmouse ata_piix libata scsi_mod ehci_pci uhci_hcd ehci_hcd
[ 2029.524782]  usbcore usb_common thermal atl1e
[ 2029.524808] CPU: 0 PID: 641 Comm: Xorg Tainted: GW   
4.4.0-0.bpo.1-686-pae #1 Debian 4.4.6-1~bpo8+1
[ 2029.524816] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 2103
06/11/2009
[ 2029.524826]  00203286 af31f475 f4a01c98 c12ba29c f4a01ca8  c106b5c1 
f8a5dbca
[ 2029.524851]  f4a01cc8 0281 f8a4f190 320c f89ef9f1 0009 320c 
f89ef9f1
[ 2029.524875]  f4a1a800 f51e5c00 f3d0 f4a01cb4 c106b62e 0009 f4a01ca8 
f8a5dbca
[ 2029.524898] Call Trace:
[ 2029.524921]  [] ? dump_stack+0x55/0x79
[ 2029.524938]  [] ? warn_slowpath_common+0x91/0xc0
[ 2029.525047]  

Bug#821136: marked as done (linux-image-4.4.0-1-amd64: i915 gpu hang and corrupted text (again))

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:15:35 -0700 (PDT)
with message-id <6097fc97.1c69fb81.dbe21.c...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #821136,
regarding linux-image-4.4.0-1-amd64: i915 gpu hang and corrupted text (again)
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.)


-- 
821136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.4.6-1
Severity: normal

Dear Maintainer,

I am experiencing various Intel graphics issues on my laptop, mostly (but
seemingly not exclusively) after doing a suspend/resume.

The first issue is that, after a suspend/resume cycle, rendered text will
sometimes have disappearing letters in most programs (e.g. gnome-terminal,
Firefox). The letters that have not disappeared are rendered correctly with
no glitches. Scrolling in the affected programs seems to move the corrupted
letters without introducing more corruption. Suspend/resume a second time
does not fix this but rebooting does.

The second issue is that the program I am using (which usually happens to be
Firefox) will freeze either randomly or after the screen lock comes up after
resuming from suspend. After freezing for a while, the program will crash
and dmesg will show a gpu hang error.

>From a quick Google search, it seems these errors have been reported before
and are supposedy fixed. However, I am still experiencing them on 4.4.

I know my kernel is tainted, but I don't believe that is a direct cause of
this problem. If necessary, I can try to reproduce it without the tainting
modules.


-- Package-specific info:
** Version:
Linux version 4.4.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160307 (Debian 5.3.1-11) ) #1 SMP Debian 4.4.6-1 (2016-03-17)

** Command line:
BOOT_IMAGE=/vmlinuz-4.4.0-1-amd64 
root=UUID=60978242-e521-42fb-a010-9991813948e3 ro rootflags=subvol=debian 
cgroup_enable=memory quiet

** Tainted: PWO (4609)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
[90989.762920] FWMSG:   Heap free space : 10002626 [0x0098a0c2]
[90989.762936] FWMSG:   Heap allocated space : 94656 [0x000171c0]
[90989.762954] FWMSG:   Disclaimer : Copyright (c) APPLE Inc. All Rights 
Reserved.
[90989.762967] FWMSG:   Application : adc [release]
[90989.762982] FWMSG:   Linked on : Jul 25 2015 - 08:48:55
[90989.763145] FWMSG:   Release : S2ISP-01.43.00
[90989.763158] FWMSG:   H4ISPAPPLE : 11536
[90989.763170] FWMSG:   H4ISPCD : 4081
[90989.763181] FWMSG:   ffw : 4143
[90989.763198] FWMSG:   Tool-chain : iPhone OS - 7.0.3 [clang/clang++]
[90989.763208] FWMSG: 
[90989.763229] FWMSG: 
---
[90989.763239] FWMSG: 
[90989.836559] FWMSG: [ISP] CMD = 0x0004 [CISP_CMD_PRINT_ENABLE]
[90989.836917] FWMSG: [ISP] CMD = 0x0003 [CISP_CMD_CONFIG_GET]
[90989.837398] FWMSG: [ISP] CH = 0 CMD = 0x010d [CISP_CMD_CH_INFO_GET]
[90989.837743] [ cut here ]
[90989.837750] WARNING: CPU: 0 PID: 20305 at 
/build/linux-dFNWCu/linux-4.4.6/drivers/base/firmware_class.c:1146 
_request_firmware+0x545/0xad0()
[90989.837798] Modules linked in: loop rfcomm bridge stp llc bnep fuse 
ip6table_filter ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 
ip6_tables xt_limit xt_conntrack iptable_filter ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack xt_CHECKSUM xt_tcpudp iTCO_wdt iTCO_vendor_support 
iptable_mangle joydev iptable_raw ip_tables x_tables binfmt_misc 
snd_hda_codec_hdmi nls_utf8 nls_cp437 vfat fat efi_pstore intel_rapl ext4 
iosf_mbi mbcache jbd2 x86_pkg_temp_thermal intel_powerclamp applesmc coretemp 
input_polldev kvm_intel kvm irqbypass btusb btrtl btbcm btintel bluetooth 
wl(PO) pcspkr efivars lpc_ich crc16 mfd_core i2c_i801 bcm5974 thunderbolt 
cfg80211 rfkill mei_me sg evdev mei snd_hda_codec_cirrus shpchp 
snd_hda_codec_generic
[90989.837833]  i915 battery drm_kms_helper snd_hda_intel sbs snd_hda_codec 
sbshc acpi_als drm kfifo_buf snd_hda_core snd_hwdep industrialio i2c_algo_bit 
snd_pcm snd_timer snd video tpm_tis ac soundcore tpm apple_bl button processor 
facetimehd(O) videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media efivarfs autofs4 btrfs xor raid6_pq algif_skcipher 
af_alg hid_apple hid_generic hid_logitech_hidpp hid_logitech_dj usbhid hid 
dm_crypt dm_mod sd_mod uas 

Bug#820837: marked as done (linux-image-4.1.0-2-686-pae: usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:15:14 -0700 (PDT)
with message-id <6097fc82.1c69fb81.1090e.e...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #820837,
regarding linux-image-4.1.0-2-686-pae: usb 3-1.3: usbfs: USBDEVFS_CONTROL 
failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110
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.)


-- 
820837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.1.6-1
Severity: normal

Dear Maintainer,

Sometimes my UPS (Advice) starts beeping every 20 seconds or so (electricity is
not turned off and the computer continues to work).

To stop beeping I reboot.

Motherboard: Gigabyte H67A-UD3H

Here is the last part of dmesg output:

[80956.127530] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[81253.729422] usb 3-1.6: USB disconnect, device number 8
[81254.017093] usb 3-1.6: new low-speed USB device number 9 using ehci-pci
[81254.115853] usb 3-1.6: New USB device found, idVendor=1c4f, idProduct=0016
[81254.115858] usb 3-1.6: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[81254.115860] usb 3-1.6: Product: USB Keyboard
[81254.115863] usb 3-1.6: Manufacturer: SIGMACHIP
[81254.119278] input: SIGMACHIP USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.0/0003:1C4F:0016.0009/input/input24
[81254.173723] hid-generic 0003:1C4F:0016.0009: input,hidraw0: USB HID v1.10 
Keyboard [SIGMACHIP USB Keyboard] on usb-:00:1a.0-1.6/input0
[81264.187547] hid-generic 0003:1C4F:0016.000A: usb_submit_urb(ctrl) failed: -1
[81264.187575] hid-generic 0003:1C4F:0016.000A: timeout initializing reports
[81264.187882] input: SIGMACHIP USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:1C4F:0016.000A/input/input25
[81264.243689] hid-generic 0003:1C4F:0016.000A: input,hidraw2: USB HID v1.10 
Device [SIGMACHIP USB Keyboard] on usb-:00:1a.0-1.6/input1
[81392.081168] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[81541.396630] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[82745.525980] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[82798.635872] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[83497.118588] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[83652.450465] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[83968.129094] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[86329.325986] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[87405.188725] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 ret -110
[87676.430232] usb 3-1-port6: disabled by hub (EMI?), re-enabling...
[87676.430241] usb 3-1.6: USB disconnect, device number 9
[87676.721746] usb 3-1.6: new low-speed USB device number 10 using ehci-pci
[87676.820299] usb 3-1.6: New USB device found, idVendor=1c4f, idProduct=0016
[87676.820303] usb 3-1.6: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[87676.820306] usb 3-1.6: Product: USB Keyboard
[87676.820308] usb 3-1.6: Manufacturer: SIGMACHIP
[87676.823925] input: SIGMACHIP USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.0/0003:1C4F:0016.000B/input/input26
[87676.878292] hid-generic 0003:1C4F:0016.000B: input,hidraw0: USB HID v1.10 
Keyboard [SIGMACHIP USB Keyboard] on usb-:00:1a.0-1.6/input0
[87686.892065] hid-generic 0003:1C4F:0016.000C: usb_submit_urb(ctrl) failed: -1
[87686.892072] hid-generic 0003:1C4F:0016.000C: timeout initializing reports
[87686.892171] input: SIGMACHIP USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:1C4F:0016.000C/input/input27
[87686.948039] hid-generic 0003:1C4F:0016.000C: input,hidraw2: USB HID v1.10 
Device [SIGMACHIP USB Keyboard] on usb-:00:1a.0-1.6/input1


-- Package-specific info:
** Version:
Linux version 4.1.0-2-686-pae (debian-kernel@lists.debian.org) (gcc version 
4.9.3 (Debian 4.9.3-3) ) #1 SMP Debian 4.1.6-1 (2015-08-23)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.1.0-2-686-pae 
root=UUID=54902130-d49b-4173-bb4f-5eacb0595474 ro selinux=1 security=selinux 
quiet

** Not tainted

** Kernel log:
[54645.278337] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 
rq 9 len 8 

Bug#820786: marked as done (bugs.debian.org: System hangs randomly after lock screen)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:14:46 -0700 (PDT)
with message-id <6097fc66.1c69fb81.339e.0...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #820786,
regarding bugs.debian.org: System hangs randomly after lock screen
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.)


-- 
820786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I think some update I made. I use latest debian testing amd64 + xfce +
lightdm
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I can't tell how reproduce it but it happens randomly on lock screen.
   * What was the outcome of this action?
Hangs system, can't event got into tty with alt + ctrl + f1
   * What outcome did you expect instead?
Just lock my PC.
   * Logs
   Apr 12 11:04:33 debian NetworkManager[708]:   [1460451873.9939] device
(tun0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 12 11:04:33 debian NetworkManager[708]:   [1460451873.9942] device
(tun0): state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 12 11:04:33 debian NetworkManager[708]:   [1460451873.9987] device
(tun0): Activation: successful, device activated.
Apr 12 11:04:34 debian systemd[1]: Starting Network Manager Script Dispatcher
Service...
Apr 12 11:04:34 debian dbus[694]: [system] Successfully activated service
'org.freedesktop.nm_dispatcher'
Apr 12 11:04:34 debian systemd[1]: Started Network Manager Script Dispatcher
Service.
Apr 12 11:04:34 debian nm-dispatcher: req:1 'vpn-up' [tun0]: new request (1
scripts)
Apr 12 11:04:34 debian nm-dispatcher: req:1 'vpn-up' [tun0]: start running
ordered scripts...
Apr 12 11:04:34 debian nm-dispatcher: req:2 'up' [tun0]: new request (1
scripts)
Apr 12 11:04:34 debian nm-dispatcher: req:2 'up' [tun0]: start running ordered
scripts...
Apr 12 11:06:41 debian lightdm[791]: ** (process:3975): WARNING **: Error
getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Apr 12 11:06:41 debian systemd[1]: Started Session c2 of user lightdm.
Apr 12 11:06:48 debian lightdm[791]: ** (process:4001): WARNING **: Error
getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Apr 12 11:06:53 debian kernel: [  417.832046] [ cut here
]
Apr 12 11:06:53 debian kernel: [  417.832060] WARNING: CPU: 2 PID: 885 at
/build/linux-dFNWCu/linux-4.4.6/include/linux/kref.h:46
drm_framebuffer_reference+0x40/0x70 [drm]()
Apr 12 11:06:53 debian kernel: [  417.832088] Modules linked in: tun ctr ccm
rfcomm fuse pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) snd_hda_codec_hdmi
bnep vboxdrv(O) arc4 iTCO_wdt iTCO_vendor_support intel_rapl
x86_pkg_temp_thermal dell_wmi intel_powerclamp sparse_keymap coretemp kvm_intel
uvcvideo dell_laptop dcdbas videobuf2_vmalloc dell_smm_hwmon videobuf2_memops
btusb videobuf2_v4l2 btrtl iwlmvm videobuf2_core kvm v4l2_common btbcm videodev
btintel bluetooth irqbypass media evdev joydev mac80211 serio_raw pcspkr sg
iwlwifi dell_led i915 lpc_ich mfd_core i2c_i801 cfg80211 snd_hda_codec_realtek
snd_hda_codec_generic shpchp drm_kms_helper drm snd_hda_intel mei_me
snd_hda_codec mei i2c_algo_bit snd_hda_core snd_hwdep wmi battery 8250_fintek
snd_soc_rt5640 snd_soc_rl6231 int3403_thermal snd_soc_core snd_pcm dw_dmac
dw_dmac_core snd_timer snd_soc_sst_acpi dell_smo8800 elan_i2c video snd
soundcore regmap_i2c dell_rbtn acpi_als processor_thermal_device
intel_soc_dts_iosf i2c_designware_platform kfifo_buf iosf_mbi rfkill
industrialio int3400_thermal i2c_designware_core int3402_thermal tpm_tis
acpi_thermal_rel int340x_thermal_zone tpm button ac acpi_pad processor
parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 algif_skcipher
af_alg hid_generic usbhid dm_crypt dm_mod sd_mod crct10dif_pclmul crc32_pclmul
crc32c_intel jitterentropy_rng sha256_ssse3 sha256_generic hmac drbg ahci
libahci ansi_cprng aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper
cryptd libata sdhci_pci xhci_pci ehci_pci psmouse scsi_mod e1000e xhci_hcd
ehci_hcd usbcore ptp pps_core usb_common fan thermal 

Bug#820752: marked as done (nfsd may fail to load if memory is fragmented)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:14:15 -0700 (PDT)
with message-id <6097fc47.1c69fb81.25e51.f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #820752,
regarding nfsd may fail to load if memory is fragmented
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.)


-- 
820752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: grave
Justification: renders package unusable

Relatively new system and I'm trying to get nfsd working, but it fails.

After looking at journalctl, it seems that the nfsd module can not be loaded:

Apr 11 17:37:50.511723 myhost kernel: Installing knfsd (copyright (C) 1996 
o...@monad.swb.de).
Apr 11 17:37:50.511864 myhost kernel: modprobe: page allocation failure: 
order:4, mode:0x2040d0
Apr 11 17:37:50.511949 myhost kernel: CPU: 3 PID: 15440 Comm: modprobe Not 
tainted 4.3.0-1-amd64 #1 Debian 4.3.3-7
Apr 11 17:37:50.512036 myhost kernel: Hardware name: Motherboard by ZOTAC 
ZBOX-CI320NANO series/ZBOX-CI320NANO series, BIOS B219P026 05/19/2015
Apr 11 17:37:50.512118 myhost kernel:   2423ca77 
812ddcf9 002040d0
Apr 11 17:37:50.512185 myhost kernel:  81164947 8802362120c0 
002040d0 
Apr 11 17:37:50.512251 myhost kernel:  2423ca77 0004 
2423ca77 8802362120c0
Apr 11 17:37:50.512316 myhost kernel: Call Trace:
Apr 11 17:37:50.512380 myhost kernel:  [] ? 
dump_stack+0x40/0x57
Apr 11 17:37:50.512445 myhost kernel:  [] ? 
warn_alloc_failed+0xf7/0x150
Apr 11 17:37:50.512514 myhost kernel:  [] ? 
__alloc_pages_nodemask+0x2e8/0xa10
Apr 11 17:37:50.512579 myhost kernel:  [] ? 
kmem_getpages+0x5b/0x100
Apr 11 17:37:50.512660 myhost kernel:  [] ? 
fallback_alloc+0x1ae/0x1f0
Apr 11 17:37:50.512728 myhost kernel:  [] ? 
nfsd_reply_cache_init+0xa4/0x100 [nfsd]
Apr 11 17:37:50.512793 myhost kernel:  [] ? 
__kmalloc+0x17c/0x1c0
Apr 11 17:37:50.512862 myhost kernel:  [] ? 
trace_event_define_fields_nfsd_stateid_class+0xab/0xab [nfsd]
Apr 11 17:37:50.512927 myhost kernel:  [] ? 
nfsd_reply_cache_init+0xa4/0x100 [nfsd]
Apr 11 17:37:50.512992 myhost kernel:  [] ? 
init_nfsd+0x4b/0xf55 [nfsd]
Apr 11 17:37:50.513059 myhost kernel:  [] ? 
do_one_initcall+0xb2/0x200
Apr 11 17:37:50.513123 myhost kernel:  [] ? 
do_init_module+0x5b/0x1dc
Apr 11 17:37:50.513195 myhost kernel:  [] ? 
load_module+0x2173/0x2780
Apr 11 17:37:50.513259 myhost kernel:  [] ? 
__symbol_put+0x60/0x60
Apr 11 17:37:50.513323 myhost kernel:  [] ? 
kernel_read+0x4b/0x70
Apr 11 17:37:50.513388 myhost kernel:  [] ? 
SyS_finit_module+0xae/0xe0
Apr 11 17:37:50.513460 myhost kernel:  [] ? 
system_call_fast_compare_end+0xc/0x67
Apr 11 17:37:50.513528 myhost kernel: Mem-Info:
Apr 11 17:37:50.513599 myhost kernel: active_anon:11872 inactive_anon:9752 
isolated_anon:0
 active_file:405288 inactive_file:489975 
isolated_file:0
 unevictable:0 dirty:4 writeback:0 
unstable:0
 slab_reclaimable:808833 
slab_unreclaimable:19398
 mapped:12138 shmem:5128 pagetables:2759 
bounce:0
 free:258703 free_pcp:49 free_cma:0
Apr 11 17:37:50.513675 myhost kernel: Node 0 DMA free:15896kB min:20kB low:24kB 
high:28kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB 
managed:15900kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB 
slab_reclaimable:4kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB 
unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Apr 11 17:37:50.513742 myhost kernel: lowmem_reserve[]: 0 2870 7861 7861
Apr 11 17:37:50.513811 myhost kernel: Node 0 DMA32 free:703004kB min:4112kB 
low:5140kB high:6168kB active_anon:13524kB inactive_anon:17448kB 
active_file:500576kB inactive_file:512192kB unevictable:0kB isolated(anon):0kB 
isolated(file):0kB present:3018236kB managed:2942260kB mlocked:0kB dirty:0kB 
writeback:0kB mapped:16376kB shmem:5232kB slab_reclaimable:1151992kB 
slab_unreclaimable:29404kB kernel_stack:1152kB pagetables:4056kB unstable:0kB 
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB 
pages_scanned:0 all_unreclaimable? no
Apr 11 17:37:50.514824 myhost kernel: lowmem_reserve[]: 0 

Bug#820422: marked as done (linux-image-amd64: Suspend not working on lid close)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:13:37 -0700 (PDT)
with message-id <6097fc21.1c69fb81.e28eb.0...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #820422,
regarding linux-image-amd64: Suspend not working on lid close
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.)


-- 
820422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 4.4+71
Severity: normal

Dear Maintainer,

I installed Debian testing on my 5 year old HP laptop. I did a minimal 
installation using the net install iso, then upgraded to testing, and installed 
GNOME desktop. Everything works fine except suspending on lid close. When I 
close the lid, the system is still working and becomes very hot. However, I am 
able to suspend the system from the GNOME menu.

I also tried Ubuntu 16.04 which ships with kernel 4.4, and it has the same 
problem. Kernel 4.2 works just fine with suspend on this machine, as is the 
case of Ubuntu 15.10.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.4.0-1-amd64  4.4.6-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#819544: marked as done (linux-image-4.4.0-0.bpo.1-amd64: screen blink/glitch on dual monitor setup)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:12:09 -0700 (PDT)
with message-id <6097fbc9.1c69fb81.4cacc.d...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #819544,
regarding linux-image-4.4.0-0.bpo.1-amd64: screen blink/glitch on dual monitor 
setup
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.)


-- 
819544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.4.6-1~bpo8+1
Severity: normal
Tags: upstream

Dear Maintainer,

   * What led up to the situation?
- setup dual monitor on notebook with secondary monitor plugged into
DSUB/VGA port
- configure 2nd monitor to extend desktop
- move mouse pointer from one display to another rapidly

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- just boot normally, then desktop showed up, moving my mouse across
monitor and there I noticed it

   * What was the outcome of this action?
- there is glitch on some part of screen (blinking), on both display

   * What outcome did you expect instead?
- no blinking, no glitch


But now I revert to linux-image-4.3.0-0.bpo.1-amd64 and the problem is gone.



-- Package-specific info:
** Version:
Linux version 4.4.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.4.0-0.bpo.1-amd64 
root=UUID=0c275924-c64a-4700-89dc-d0401c85e576 ro initrd=/install/gtk/initrd.gz 
quiet splash acpi_osi=Linux

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[9.899415] intel ips :00:1f.6: CPU TDP doesn't match expected value 
(found 25, expected 29)
[9.899587] intel ips :00:1f.6: IPS driver initialized, MCP temp limit 90
[9.963318] ACPI: Battery Slot [BAT0] (battery present)
[   10.010158] ACPI Warning: SystemIO range 
0x0428-0x042F conflicts with OpRegion 
0x0400-0x047F (\PMIO) (20150930/utaddress-254)
[   10.010167] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   10.010170] ACPI Warning: SystemIO range 
0x11C0-0x11CF conflicts with OpRegion 
0x1180-0x11E3 (\GPIO) (20150930/utaddress-254)
[   10.010175] ACPI Warning: SystemIO range 
0x11C0-0x11CF conflicts with OpRegion 
0x1180-0x11DF (\_SB_.PCI0.LPCB.EC0_.GPIO) 
(20150930/utaddress-254)
[   10.010179] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   10.010180] ACPI Warning: SystemIO range 
0x11B0-0x11BF conflicts with OpRegion 
0x1180-0x11E3 (\GPIO) (20150930/utaddress-254)
[   10.010184] ACPI Warning: SystemIO range 
0x11B0-0x11BF conflicts with OpRegion 
0x1180-0x11DF (\_SB_.PCI0.LPCB.EC0_.GPIO) 
(20150930/utaddress-254)
[   10.010187] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   10.010188] ACPI Warning: SystemIO range 
0x1180-0x11AF conflicts with OpRegion 
0x1180-0x11E3 (\GPIO) (20150930/utaddress-254)
[   10.010192] ACPI Warning: SystemIO range 
0x1180-0x11AF conflicts with OpRegion 
0x1180-0x11DF (\_SB_.PCI0.LPCB.EC0_.GPIO) 
(20150930/utaddress-254)
[   10.010195] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   10.010196] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   10.089493] ACPI Warning: SystemIO range 
0x1840-0x185F conflicts with OpRegion 
0x1840-0x184F (\_SB_.PCI0.SBUS.SMBI) 
(20150930/utaddress-254)
[   10.089502] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   10.123423] input: PC Speaker as /devices/platform/pcspkr/input/input8
[   10.489738] systemd-journald[205]: Received request to flush runtime journal 
from PID 1
[   10.742218] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. 
Using workaround
[   10.869222] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC272X: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   10.869226] snd_hda_codec_realtek hdaudioC0D0:

Bug#819910: marked as done (Call trace in dmesg with Debian SID)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:13:17 -0700 (PDT)
with message-id <6097fc0d.1c69fb81.3efa3.4...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #819910,
regarding Call trace in dmesg with Debian SID
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.)


-- 
819910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kernelVersion: 4.4.0-1-amd64


After fresh install of debian sid (Debian 4.4.6-1 (2016-03-17)), i got
following call trace in dmesg

http://pastebin.com/wYpFerdH

I'm using Linux 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17)
x86_64 GNU/Linux
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#819180: marked as done (linux-image-3.16.0-4-amd64: open-iscsi login fails using amd64 kernel with i386 userland)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:11:53 -0700 (PDT)
with message-id <6097fbb9.1c69fb81.c1764.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #819180,
regarding linux-image-3.16.0-4-amd64: open-iscsi login fails using amd64 kernel 
with i386 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.)


-- 
819180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u4
Severity: normal

Dear Maintainer,

open-iscsi still does not work using i386 userland with an amd64 kernel:
trying to mount an iscsi target with iscsiadm (e.g. iscsiadm -m node 
--targetname babblings --portal 1.2.3.4 --login) leads to an hang.

this was already reported as bug 502845 but closed as the original bug report 
was about linux 2.6.
it is working with open-iscsi:amd64

Bernhard
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#819159: marked as done (alsa-utils: No automute control in mixer, when there damn well should be)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:11:21 -0700 (PDT)
with message-id <6097fb99.1c69fb81.bab2e.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #819159,
regarding alsa-utils:  No automute control in mixer, when there damn well 
should be
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.)


-- 
819159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alsa-utils
Version: 1.0.25-4
Severity: normal

I cannot get automute (that is, mute speakers when I plug in front
headphone) to work at my current configuration.  The option simply
doesn't appear in the mixer (alsamixer or any other, such as qasmixer).

The hardware is: HDA Intel with Realtek ALC889 codec.  Onboard with
GA-880GM Gigabyte mobo.

Kernel: Same problem with debian 3.2 (official wheezy) or 3.16 (from
backports).

But now the most important bit.  How do I know this _should_ work at
all?  Because it does - with upstream kernels!  With a kernel.org kernel
going back at least to 3.10, this control appears in mixers, and when
turned on it works as a charm.  But I can't use upstream kernels for
other reasons :-(


-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 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 alsa-utils depends on:
ii  dialog  1.1-20120215-2
ii  kmod9-3
ii  libasound2  1.0.25-4
ii  libc6   2.13-38+deb7u10
ii  libncursesw55.9-10
ii  libsamplerate0  0.1.8-5
ii  libtinfo5   5.9-10
ii  lsb-base4.1+Debian8+deb7u1

Versions of packages alsa-utils recommends:
pn  alsa-base  
ii  pciutils   1:3.1.9-6

alsa-utils suggests no packages.

-- 
Please *no* private copies of mailing list or newsgroup messages.
Rule 420: All persons more than eight miles high to leave the court.
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#819100: marked as done (linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on Thinkpad T410)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:10:55 -0700 (PDT)
with message-id <6097fb7f.1c69fb81.b335c.f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #819100,
regarding linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on 
Thinkpad T410
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.)


-- 
819100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.4.6-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Upgrade from jessie to stretch
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Pressing Thnkpad T410's hardware speaker mute button
   * What was the outcome of this action?
Speaker mutes, but the button's LED does not illuminate
   * What outcome did you expect instead?
Expected the LED to illuminate

The mic mute button also exhibits the same behavior, but I had not tried this 
under jessie so don't know if it worked before. The speaker mute certainly did.



-- Package-specific info:
** Version:
Linux version 4.4.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160307 (Debian 5.3.1-11) ) #1 SMP Debian 4.4.6-1 (2016-03-17)

** Command line:
BOOT_IMAGE=/vmlinuz-4.4.0-1-amd64 
root=UUID=39ff419a-8bff-4244-8eb5-99350d8b0857 ro quiet

** Not tainted

** Kernel log:
[14809.730381] e1000e: EEE TX LPI TIMER: 
[14810.141902] PM: suspend of devices complete after 632.222 msecs
[14810.157976] PM: late suspend of devices complete after 16.068 msecs
[14810.158545] ehci-pci :00:1d.0: System wakeup enabled by ACPI
[14810.158676] ehci-pci :00:1a.0: System wakeup enabled by ACPI
[14810.158763] e1000e :00:19.0: System wakeup enabled by ACPI
[14810.173934] PM: noirq suspend of devices complete after 15.953 msecs
[14810.174073] ACPI: Preparing to enter system sleep state S3
[14810.353829] ACPI : EC: EC stopped
[14810.353831] PM: Saving platform NVS memory
[14810.354875] Disabling non-boot CPUs ...
[14810.356197] smpboot: CPU 1 is now offline
[14810.367529] smpboot: CPU 2 is now offline
[14810.383427] smpboot: CPU 3 is now offline
[14810.394876] ACPI: Low-level resume complete
[14810.394936] ACPI : EC: EC started
[14810.394936] PM: Restoring platform NVS memory
[14810.395667] Enabling non-boot CPUs ...
[14810.415359] x86: Booting SMP configuration:
[14810.415360] smpboot: Booting Node 0 Processor 1 APIC 0x1
[14810.417931]  cache: parent cpu1 should not be sleeping
[14810.447212] CPU1 is up
[14810.467385] smpboot: Booting Node 0 Processor 2 APIC 0x4
[14810.469787]  cache: parent cpu2 should not be sleeping
[14810.499215] CPU2 is up
[14810.519422] smpboot: Booting Node 0 Processor 3 APIC 0x5
[14810.521848]  cache: parent cpu3 should not be sleeping
[14810.551218] CPU3 is up
[14810.553552] ACPI: Waking up from system sleep state S3
[14810.887287] thinkpad_acpi: EC reports that Thermal Table has changed
[14810.955420] ehci-pci :00:1a.0: System wakeup disabled by ACPI
[14810.955549] sdhci-pci :0d:00.0: MMC controller base frequency changed to 
50Mhz.
[14810.90] ehci-pci :00:1d.0: System wakeup disabled by ACPI
[14810.955826] PM: noirq resume of devices complete after 16.620 msecs
[14810.957940] PM: early resume of devices complete after 2.094 msecs
[14810.958109] e1000e :00:19.0: System wakeup disabled by ACPI
[14810.958675] sd 0:0:0:0: [sda] Starting disk
[14810.958701] sd 1:0:0:0: [sdb] Starting disk
[14810.958730] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[14810.958961] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[14810.959057] iwlwifi :03:00.0: Radio type=0x1-0x3-0x1
[14810.960304] rtc_cmos 00:02: System wakeup disabled by ACPI
[14811.187299] usb 1-1.4: reset full-speed USB device number 3 using ehci-pci
[14811.229150] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[14811.229367] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[14811.229457] iwlwifi :03:00.0: Radio type=0x1-0x3-0x1
[14811.291290] ata5: SATA link down (SStatus 0 SControl 300)
[14811.299305] ata6: SATA link down (SStatus 0 SControl 300)
[14811.351304] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[14811.447234] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[14811.459303] sdhci-pci :0d:00.0: Will use DMA mode even though HW doesn't 
fully claim to support it.
[14811.461590] PM: resume of devices complete after 503.613 msecs
[14811.462070] PM: Finishing wakeup.
[14811.462083] Restarting 

Bug#818746: marked as done (linux-image-3.16.0-4-686-pae: EXT4-fs error (device dm-8): ext4_mb_complex_scan_group)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:10:07 -0700 (PDT)
with message-id <6097fb4f.1c69fb81.d762b.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #818746,
regarding linux-image-3.16.0-4-686-pae: EXT4-fs error (device dm-8): 
ext4_mb_complex_scan_group
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.)


-- 
818746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u4
Severity: normal

My news spool was on an ext3 filesystem.  After upgrading to jessie, I
found that with the news server running I got lots and lots of
messages like this:

[ 4177.526638] EXT4-fs error (device dm-8):
ext4_mb_complex_scan_group:1952: group 230, 208 free clusters as per
group info. But got 2048 blocks

Between Mar 19 17:26:28 and Mar 19 18:20:49, 545 such messages.  They
have different numbers.  The `group' number varies from 227 to 236.

During this time there are no complaints from the news server about
any problems with the filesystem.

I stopped the news server, unmounted the fs, and ran e2fsck on it.
The fs was marked as having errors, so e2fsck did run, but it did not
find anything wrong.  So I remounted the fs and restarted the news
server.  The EXT4-fs error kernel messages started again.

So I stopped the news server, unmounted the filesystem, ran e2fsck
again (again, no problems).  I then created a new filesystem on a new
LVM LV, with `mkfs.ext4 -T news'.  I mounted the old fs with -r, and
used rsync to copy out all the data onto the new fs.  This process
produced no coplaints from the kernel.

I am now running the news server off the new filesystem and all seems
to be entirely well.  I conjecture that the old filesystem had some
weirdness which triggered a kernel bug.

I include `tune2fs' output for the old filesystem.

The storage is:

  ext3 (old, seems to be broken fs; new fs is ext4)
  Linux LVM LVs (the two volumes I mention above, and others)
  1x Linux LVM VG "vg-main" (other volumes on the system in other VG(s))
  Linux mdadm raid1 (some other volumes on the system use raid0)
  2x Linux LVM LV
  2x Linux LVM VG "chiark-early-a", "chiark-early-b" [1]
  2x Linux LVM PV
  2x DOS partition table
  2x WD7500AYPS-0 (1.5T spinning rust)

I don't know exactly which version of the ext2/ext3 utilities created
the filesystem, but it was created using lenny.  (At which point data
was imported from a previous filesystem on another disk, using rsync.)

Recently, the filesystem was mostly being accessed by kernels from
squeeze-lts and seems to have been running happily.  It has never been
touched by kernels from wheezy or wheezy-lts.

I have kept the LV containing the filesystem, and preserved the
relevant log entries,, for investigation, if that's any help.

Ian.

[1] I have an initramfs hook script that arranges for the lower LVM
layer to be assembled before the rest of the initramfs storage
machinery, so that booting works.


tune2fs 1.42.12 (29-Aug-2014)
Filesystem volume name:   
Last mounted on:  /var/spool/news
Filesystem UUID:  23e630c2-a03d---
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype 
sparse_super large_file
Filesystem flags: signed_directory_hash 
Default mount options:(none)
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  7772128
Block count:  5750784
Reserved block count: 0
Free blocks:  483231
Free inodes:  5451835
First block:  0
Block size:   4096
Fragment size:4096
Reserved GDT blocks:  687
Blocks per group: 24168
Fragments per group:  24168
Inodes per group: 32656
Inode blocks per group:   2041
Filesystem created:   Sat Mar  6 20:22:30 2010
Last mount time:  Sat Mar 19 18:11:04 2016
Last write time:  Sat Mar 19 18:23:24 2016
Mount count:  0
Maximum mount count:  25
Last checked: Sat Mar 19 18:23:24 2016
Check interval:   15552000 (6 months)
Next check after: Thu Sep 15 19:23:24 2016
Lifetime writes:  907 MB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 28
Desired extra isize:  28
Journal inode:

Processed: closing 818336

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 818336
Bug #818336 [src:linux] linux-image-4.3.0-1-amd64: `ulimit -c` not respected 
when kernel.core_pattern is a pipe
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#818248: marked as done (linux-image-4.3.0-1-amd64: WARNING at drivers/dma/ioat/dca.c:342)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:07:32 -0700 (PDT)
with message-id <6097fab4.1c69fb81.55b2c.4...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #818248,
regarding linux-image-4.3.0-1-amd64: WARNING at drivers/dma/ioat/dca.c:342
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.)


-- 
818248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.3.5-1
Severity: normal

Dear Maintainer,

During boot, I see the following in the kernel log:

Mar 12 08:54:19 cerberus kernel: [   26.054139] ioatdma: Intel(R) QuickData 
Technology Driver 4.00
Mar 12 08:54:19 cerberus kernel: [   26.054871] [ cut here
]
Mar 12 08:54:19 cerberus kernel: [   26.054886] WARNING: CPU: 1 PID: 423 at
/build/linux-dUKt9u/linux-4.3.3/drivers/dma/ioat/dca.c:342
ioat_dca_init+0x179/0x1a0 [ioatdma]()
Mar 12 08:54:19 cerberus kernel: [   26.054889] ioatdma :00:04.0:
APICID_TAG_MAP set incorrectly by BIOS, disabling DCA
Mar 12 08:54:19 cerberus kernel: [   26.054891] Modules linked in: ioatdma(+)
i2c_i801 tpm_tis tpm wmi processor acpi_power_meter button coretemp hwmon_vid
firewire_sbp2 firewire_core crc_itu_t loop parport_pc ppdev lp parport autofs4
ext4 crc16 mbcache jbd2 raid1 md_mod hid_generic usbhid hid sr_mod sd_mod
cdrom crc32c_intel ahci libahci xhci_pci ehci_pci igb xhci_hcd ehci_hcd
i2c_algo_bit dca libata ptp pps_core usbcore scsi_mod usb_common
Mar 12 08:54:19 cerberus kernel: [   26.054940] CPU: 1 PID: 423 Comm:
systemd-udevd Not tainted 4.3.0-1-amd64 #1 Debian 4.3.3-5
Mar 12 08:54:19 cerberus kernel: [   26.054943] Hardware name: Supermicro
X10DAi/X10DAI, BIOS 1.0c 01/29/2015
Mar 12 08:54:19 cerberus kernel: [   26.054946]  
d617b9c9 812ddce9 8800736cfa38
Mar 12 08:54:19 cerberus kernel: [   26.054951]  81072b1d
88046c6c1000 8800736cfa90 8804686d6740
Mar 12 08:54:19 cerberus kernel: [   26.054956]  c90001be8100
0100 81072c24 a0346b08
Mar 12 08:54:19 cerberus kernel: [   26.054961] Call Trace:
Mar 12 08:54:19 cerberus kernel: [   26.054973]  [] ?
dump_stack+0x40/0x57
Mar 12 08:54:19 cerberus kernel: [   26.054979]  [] ?
warn_slowpath_common+0x7d/0xb0
Mar 12 08:54:19 cerberus kernel: [   26.054983]  [] ?
warn_slowpath_fmt_taint+0x54/0x70
Mar 12 08:54:19 cerberus kernel: [   26.054992]  [] ?
ioat_dca_init+0x179/0x1a0 [ioatdma]
Mar 12 08:54:19 cerberus kernel: [   26.055000]  [] ?
ioat_pci_probe+0x83c/0xda0 [ioatdma]
Mar 12 08:54:19 cerberus kernel: [   26.055008]  [] ?
local_pci_probe+0x3f/0x90
Mar 12 08:54:19 cerberus kernel: [   26.055014]  [] ?
pci_device_probe+0x100/0x140
Mar 12 08:54:19 cerberus kernel: [   26.055021]  [] ?
driver_probe_device+0x212/0x470
Mar 12 08:54:19 cerberus kernel: [   26.055025]  [] ?
__driver_attach+0x7b/0x80
Mar 12 08:54:19 cerberus kernel: [   26.055030]  [] ?
driver_probe_device+0x470/0x470
Mar 12 08:54:19 cerberus kernel: [   26.055033]  [] ?
bus_for_each_dev+0x67/0xb0
Mar 12 08:54:19 cerberus kernel: [   26.055038]  [] ?
bus_add_driver+0x1df/0x270
Mar 12 08:54:19 cerberus kernel: [   26.055041]  [] ?
0xa01d4000
Mar 12 08:54:19 cerberus kernel: [   26.055046]  [] ?
driver_register+0x57/0xc0
Mar 12 08:54:19 cerberus kernel: [   26.055053]  [] ?
ioat_init_module+0x88/0x1000 [ioatdma]
Mar 12 08:54:19 cerberus kernel: [   26.055059]  [] ?
do_one_initcall+0xb2/0x200
Mar 12 08:54:19 cerberus kernel: [   26.055066]  [] ?
do_init_module+0x5b/0x1dc
Mar 12 08:54:19 cerberus kernel: [   26.055073]  [] ?
load_module+0x2173/0x2780
Mar 12 08:54:19 cerberus kernel: [   26.055078]  [] ?
__symbol_put+0x60/0x60
Mar 12 08:54:19 cerberus kernel: [   26.055087]  [] ?
kernel_read+0x4b/0x70
Mar 12 08:54:19 cerberus kernel: [   26.055093]  [] ?
SyS_finit_module+0xae/0xe0
Mar 12 08:54:19 cerberus kernel: [   26.055102]  [] ?
system_call_fast_compare_end+0xc/0x67
Mar 12 08:54:19 cerberus kernel: [   26.055105] ---[ end trace
457fd910cb4c931a ]---


-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)

** Command line:
BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 
root=UUID=48ca44ea-960b-4451-a641-3d73c2f2c0ae ro quiet quiet

** Tainted: PIO (6145)
 * Proprietary module has been loaded.
 * Working around severe firmware bug.
 * Out-of-tree module has been loaded.

** Kernel log:
[217011.949891] audit: type=1326 

Bug#818096: marked as done (linux-image-4.3.0-1-amd64: vfat mount option "shortname=lower" makes uppercase directories unremovable)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:05:53 -0700 (PDT)
with message-id <6097fa51.1c69fb81.64fd.e...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #818096,
regarding linux-image-4.3.0-1-amd64: vfat mount option "shortname=lower" makes 
uppercase directories unremovable
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.)


-- 
818096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.3.5-1
Severity: normal

{ Not sure if this is the right package to report this bug against;
please move appropriately, if necessary. }

Symptoms


When mounting a FAT32, FAT16, or FAT12 file system with the option
"shortname=lower" and creating a directory with an all-uppercase name,
the directory cannot be removed afterwards, neither by "rm -r" nor
"rmdir".

Note that otherwise, accessibility of the directory is not affected;
one can cd to it, and access files below it without problems.

Mount version used: 2.27.1-6.

Mount options

  shortname=win95
  shortname=winnt
  shortname=mixed

do not show this behavior.


Steps to reproduce
--
# dd if=/dev/zero of=test.img seek=100M count=0 bs=1M oflag=seek_bytes
0+0 records in
0+0 records out
0 bytes copied, 0.000146967 s, 0.0 kB/s
# mkfs.fat -F 32 test.img  # FAT16 and FAT12 affected as well
# mkdir -m 0 /mnt/test
# mount -o loop,shortname=lower test.img /mnt/test
# mkdir /mnt/test/FOO
# ls -l /mnt/test 
total 1
drwxr-xr-x 2 root root 512 Mar 13 16:56 foo
# rmdir /mnt/test/foo
rmdir: failed to remove '/mnt/test/foo': No such file or directory
# echo $?
1
# rmdir /mnt/test/FOO
rmdir: failed to remove '/mnt/test/FOO': No such file or directory
# echo $?
1
# rmdir /mnt/test/Foo
rmdir: failed to remove '/mnt/test/Foo': No such file or directory
# echo $?
1
# rm -r /mnt/test/foo
rm: cannot remove '/mnt/test/foo': No such file or directory
# echo $?
1
# rm -r /mnt/test/FOO
rm: cannot remove '/mnt/test/FOO': No such file or directory
# echo $?
1
# rm -r /mnt/test/Foo
rm: cannot remove '/mnt/test/Foo': No such file or directory
# echo $?
1


-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 (2016-02-06)

** Command line:
BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 root=/dev/mapper/vg13-lv--root ro 
libata.force=7:1.5Gbps

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[...]
[14112.215110] FAT-fs (loop0): utf8 is not a recommended IO charset for FAT 
filesystems, filesystem will be case sensitive!

** Model information
[...]

** Loaded modules:
loop
nls_utf8
nls_cp437
vfat
fat
nfsv3
bnep
bluetooth
iptable_filter
ip_tables
autofs4
x_tables
snd_hrtimer
snd_seq_midi
snd_seq_midi_event
snd_rawmidi
snd_seq
snd_seq_device
cpufreq_stats
cpufreq_userspace
cpufreq_conservative
cpufreq_powersave
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
binfmt_misc
nfsd
auth_rpcgss
oid_registry
nfs_acl
nfs
lockd
grace
fscache
sunrpc
msr
i2c_dev
it87
hwmon_vid
parport_pc
ppdev
lp
parport
snd_hda_codec_realtek
nvidia(PO)
snd_hda_codec_generic
snd_hda_codec_hdmi
eeepc_wmi
asus_wmi
sparse_keymap
rfkill
video
mxm_wmi
snd_hda_intel
kvm_amd
snd_hda_codec
snd_hda_core
kvm
snd_hwdep
pcspkr
evdev
serio_raw
snd_pcm_oss
k10temp
snd_mixer_oss
amd64_edac_mod
edac_mce_amd
edac_core
snd_pcm
snd_timer
8250_fintek
drm
sp5100_tco
tpm_infineon
snd
soundcore
sg
wmi
shpchp
button
i2c_piix4
acpi_cpufreq
tpm_tis
tpm
processor
ext4
crc16
mbcache
jbd2
crc32c_generic
btrfs
xor
raid6_pq
sha256_generic
hmac
drbg
ansi_cprng
cbc
dm_crypt
dm_mod
md_mod
hid_generic
usbhid
hid
sd_mod
uas
usb_storage
ohci_pci
ahci
libahci
xhci_pci
ehci_pci
ohci_hcd
xhci_hcd
ehci_hcd
libata
e1000e
ptp
usbcore
pps_core
usb_common
scsi_mod

** Network interface configuration:
[...]

** Network status:
*** IP interfaces and addresses:
[...]

*** Device statistics:
[...]

*** Protocol statistics:
[...]

** PCI devices:
[...]

** USB devices:
[...]


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'unstable'), (25, 'experimental'), (12, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages 

Bug#818005: marked as done (kernel Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29))

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 08:03:14 -0700 (PDT)
with message-id <6097f9b2.1c69fb81.f257d.8...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #818005,
regarding kernel Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29)
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.)


-- 
818005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:  kernel
Version: Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29)

i think it need a better power management for intel atom processor and bay
trail.
Less heat and more battery life on newer kernels
So i hope they can patch the 3.16 kernels before  debian update on the
latest stable kernel.
i think  i found the patch on 4.1 kernel  here

www.kernelhub.org/?msg=858984=2

i am using debian jessie stable

thanks for answering me
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#817049: linux-image-3.16.0-4-amd64: execve() gives EEXIST error under NFS if the file has been regenerated on a different machine

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

On Mon, Mar 07, 2016 at 04:21:24PM +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 3.16.7-ckt20-1+deb8u3
> Severity: normal
> 
> Under NFS, when an executable has been regenerated on a different machine,
> execve() gives me an EEXIST error. To reproduce the bug:
> 
> francine:~> touch bin/tst
> francine:~> cat bin/tst
> 
> cassis:~> cat tst.c
> int main (void)
> { return 0; }
> cassis:~> gcc -O3 tst.c -o tst
> cassis:~> mv tst bin/
> mv: overwrite ‘bin/tst’? y
> 
> At this point, I have to wait for 15 seconds for the "mv" to be
> done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799838
> 
> After that:
> 
> francine:~> strace -f -o tst.out sh -c "exec $HOME/bin/tst"
> sh: 1: exec: /home/vlefevre/bin/tst: File exists
> zsh: exit 2 strace -f -o tst.out sh -c "exec $HOME/bin/tst"
> francine:~[2]> cat tst.out
> 21573 execve("/bin/sh", ["sh", "-c", "exec /home/vlefevre/bin/tst"], [/* 120 
> vars */]) = 0
> 21573 brk(0)= 0x7f4aded7d000
> 21573 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
> directory)
> 21573 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) = 0x7f4aded46000
> 21573 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
> directory)
> 21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64/libc.so.6", 
> O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> 21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64", 
> 0x7ffec78d5b00) = -1 ENOENT (No such file or directory)
> 21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/libc.so.6", 
> O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> 21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls", 0x7ffec78d5b00) = 
> -1 ENOENT (No such file or directory)
> 21573 open("/home/vlefevre/debian8/gmp/westmere/lib/x86_64/libc.so.6", 
> O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> 21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/x86_64", 0x7ffec78d5b00) 
> = -1 ENOENT (No such file or directory)
> 21573 open("/home/vlefevre/debian8/gmp/westmere/lib/libc.so.6", 
> O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> 21573 stat("/home/vlefevre/debian8/gmp/westmere/lib", {st_mode=S_IFDIR|0755, 
> st_size=13, ...}) = 0
> 21573 open("/usr/local/lib/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 
> ENOENT (No such file or directory)
> 21573 stat("/usr/local/lib/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such 
> file or directory)
> 21573 open("/usr/local/lib/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
> (No such file or directory)
> 21573 stat("/usr/local/lib/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
> directory)
> 21573 open("/usr/local/lib/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
> (No such file or directory)
> 21573 stat("/usr/local/lib/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file 
> or directory)
> 21573 open("/usr/local/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
> such file or directory)
> 21573 stat("/usr/local/lib", {st_mode=S_IFDIR|S_ISGID|0775, st_size=4096, 
> ...}) = 0
> 21573 open("/lib64/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
> such file or directory)
> 21573 stat("/lib64/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
> directory)
> 21573 open("/lib64/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
> file or directory)
> 21573 stat("/lib64/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
> directory)
> 21573 open("/lib64/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
> such file or directory)
> 21573 stat("/lib64/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
> directory)
> 21573 open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> 21573 read(3, 
> "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"..., 832) = 
> 832
> 21573 fstat(3, {st_mode=S_IFREG|0755, st_size=1738176, ...}) = 0
> 21573 mmap(NULL, 3844640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 
> 0) = 0x7f4ade55f000
> 21573 mprotect(0x7f4ade701000, 2093056, PROT_NONE) = 0
> 21573 mmap(0x7f4ade90, 24576, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a1000) = 0x7f4ade90
> 21573 mmap(0x7f4ade906000, 14880, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f4ade906000
> 21573 close(3)  = 0
> 21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) = 0x7f4aded45000
> 21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) = 0x7f4aded44000
> 21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) = 0x7f4aded43000
> 21573 arch_prctl(ARCH_SET_FS, 0x7f4aded44700) = 0
> 21573 mprotect(0x7f4ade90, 16384, PROT_READ) = 0
> 21573 mprotect(0x7f4aded48000, 12288, PROT_READ) = 0
> 21573 mprotect(0x7f4adeb2a000, 4096, PROT_READ) = 0
> 21573 getpid()  = 21573
> 21573 rt_sigaction(SIGCHLD, 

Processed: Re: Bug#817049: linux-image-3.16.0-4-amd64: execve() gives EEXIST error under NFS if the file has been regenerated on a different machine

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #817049 [src:linux] linux-image-3.16.0-4-amd64: execve() gives EEXIST error 
under NFS if the file has been regenerated on a different machine
Added tag(s) moreinfo.

-- 
817049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#798300: linux: fs/isofs/rock.c coarsely truncates file names of 254 or 255 bytes length

[Thomas Schmitt]

Hi,

> if this still should be trackled,

It's still in kernel 5.10, at least.

> please report it upstream

I agree that this bug is not Debain's business.
But i'd need a kernel list member who would be ready to review a patch.


Warning:
From here on it's just whining of a userlander about kernel cruelty.

There is no maintainer for isofs. Nearest is linux-scsi because of the
semi-proximity between cdrom and isofs.
Having had a real test machine last year, i tried to submit patches for
both subsystems [1] [2], but did not get any reaction.

After this experience i did not submit my patch for the name length issues.
It is based on 5.10:
--

From 3d484405f0ad8d10ef490281da157bfdd7450cb6 Mon Sep 17 00:00:00 2001
From: Thomas Schmitt 
Date: Tue, 22 Sep 2020 12:34:50 +0200
Subject: [PATCH 1/1] isofs: truncate oversized Rock Ridge names to 255 bytes

Enlarge the limit for name bytes from 253 to 255.
Do not discard all bytes of the NM field where the overflow occurs, but
rather append them to the accumulated name before truncating it to exactly
255 bytes.
Map trailing incomplete UTF-8 bytes to '_'.

Signed-off-by: Thomas Schmitt 
---
 fs/isofs/rock.c | 73 ++---
 fs/isofs/rock.h |  2 ++
 2 files changed, 71 insertions(+), 4 deletions(-)

diff --git a/fs/isofs/rock.c b/fs/isofs/rock.c
index 94ef92fe806c..e1db8776b67e 100644
--- a/fs/isofs/rock.c
+++ b/fs/isofs/rock.c
@@ -192,6 +192,63 @@ static int rock_check_overflow(struct rock_state *rs, int 
sig)
return 0;
 }

+/*
+ * Find backward from idx the start byte of a possible UTF-8 character.
+ *   https://en.wikipedia.org/wiki/UTF-8#Description
+ * Return -1 if no incomplete UTF-8 sequence is found at the name end.
+ */
+static int rock_find_utf8_start(char *name, int idx)
+{
+   unsigned char *uname, uch;
+   int i;
+
+   uname = (unsigned char *)name;
+   /* Up to 4-byte codes */
+   for (i = 0; i < 4 && idx - i >= 0; i++) {
+   uch = uname[idx - i];
+   if ((uch & 0xe0) == 0xc0) {
+   /* UTF-8 start byte for 2-byte codes */
+   if (i >= 1)
+   return -1;  /* tail is complete */
+   else
+   return (idx - i);   /* tail not complete */
+   } else if ((uch & 0xf0) == 0xe0) {
+   /* UTF-8 start byte for 3-byte codes */
+   if (i >= 2)
+   return -1;
+   else
+   return (idx - i);
+   } else if ((uch & 0xf8) == 0xf0) {
+   /* UTF-8 start byte for 4-byte codes */
+   if (i >= 3)
+   return -1;
+   else
+   return (idx - i);
+   } else if ((uch & 0xc0) != 0x80) {
+   /* not an UTF-8 tail byte, so no UTF-8 */
+   return -1;
+   }
+   }
+   /* That would be an oversized UTF-8 code or no UTF-8 at all */
+   return -1;
+}
+
+/*
+ * Replace trailing incomplete UTF-8 sequence by '_' characters.
+ */
+static void rock_erase_incomplete_utf8(char *name, int len)
+{
+   int i;
+
+   if (len <= 0)
+   return;
+   i = rock_find_utf8_start(name, len - 1);
+   if (i < 0)
+   return;
+   for (; i < len; i++)
+   name[i] = '_';
+}
+
 /*
  * return length of name field; 0: not found, -1: to be ignored
  */
@@ -271,16 +328,24 @@ int get_rock_ridge_filename(struct iso_directory_record 
*de,
break;
}
len = rr->len - 5;
-   if (retnamlen + len >= 254) {
-   truncate = 1;
-   break;
-   }
p = memchr(rr->u.NM.name, '\0', len);
if (unlikely(p))
len = p - rr->u.NM.name;
+   if (retnamlen + len > RR_NAME_LEN) {
+   truncate = 1;
+   /* Take as many characters as possible */
+   len = RR_NAME_LEN - retnamlen;
+   if (len <= 0) {
+   rock_erase_incomplete_utf8(retname,
+  retnamlen);
+   break;
+   }
+   }
memcpy(retname + retnamlen, rr->u.NM.name, len);
retnamlen += len;
retname[retnamlen] = '\0';
+   if (truncate == 1)
+   

Bug#816621: marked as done (ioremap error reading /sys/firmware/dmi/entries/1-0/raw)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 07:54:40 -0700 (PDT)
with message-id <6097f7b0.1c69fb81.eb777.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #816621,
regarding ioremap error reading /sys/firmware/dmi/entries/1-0/raw
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.)


-- 
816621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt20-1+deb8u3

Seen on an ASUS B150M-C motherboard with BIOS version 0806 (the latest as of
this writing), booting in UEFI mode. The problem is hardware-dependent, I'm
not seeing it on my other jessie hosts with the same kernel. (None of the
others support UEFI, though.)

All attempts to read /sys/firmware/dmi/entries/1-0/raw (or indeed any other
/sys/firmware/dmi/entries/*/raw file; 1-0/raw is the one "/usr/bin/facter 
virtual"
tries to read in order to recognise Google Compute Engine instances)
FAIL with, e.g.,

$ od -t cx1 /sys/firmware/dmi/entries/1-0/raw
od: /sys/firmware/dmi/entries/1-0/raw: read error: Invalid argument
000

The attempt generates the following kernel log entries (when booting with 
debugpat):

[ 3967.651507] Overlap at 0xbfed6000-0xbfed8000
[ 3967.651516] reserve_memtype added [mem 0xbfed6000-0xbfed7fff], track 
write-back, req uncached-minus, ret write-back
[ 3967.651521] ioremap error for 0xbfed6000-0xbfed8000, requested 0x10, got 0x0
[ 3967.651528] free_memtype request [mem 0xbfed6000-0xbfed7fff]

/sys/kernel/debug/x86/pat_memtype_list confirms that the relevant range is WB:
write-back @ 0xbfed6000-0xbfed8000

Early during the boot, that address range is marked UC-:

[0.612932] reserve_memtype added [mem 0xbfed6000-0xbfed7fff], track 
uncached-minus, req uncached-minus, ret uncached-minus
[0.613332] free_memtype request [mem 0xbfed6000-0xbfed7fff]

but soon that changes to WB:

[8.328236] reserve_memtype added [mem 0xbfed6000-0xbfed7fff], track 
write-back, req write-back, ret write-back
[8.328580] Overlap at 0xbfed6000-0xbfed8000
[8.328582] reserve_memtype added [mem 0xbfed6000-0xbfed7fff], track 
write-back, req write-back, ret write-back
[8.328611] free_memtype request [mem 0xbfed6000-0xbfed7fff]

I'm attaching a full dmesg output (obtained after another reboot, so the
timings are slightly different).

dmidecode has no trouble reading the information (also attached).
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) 
(gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u3 
(2016-01-17)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=/dev/mapper/xxx--vg-root ro quiet debugpat
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x0010-0xb5ea] usable
[0.00] BIOS-e820: [mem 0xb5eb-0xb5edcfff] ACPI data
[0.00] BIOS-e820: [mem 0xb5edd000-0xb7a90fff] usable
[0.00] BIOS-e820: [mem 0xb7a91000-0xb7a91fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xb7a92000-0xb7adbfff] reserved
[0.00] BIOS-e820: [mem 0xb7adc000-0xb7b82fff] usable
[0.00] BIOS-e820: [mem 0xb7b83000-0xb8203fff] reserved
[0.00] BIOS-e820: [mem 0xb8204000-0xbdadefff] usable
[0.00] BIOS-e820: [mem 0xbdadf000-0xbf217fff] reserved
[0.00] BIOS-e820: [mem 0xbf218000-0xbf224fff] ACPI data
[0.00] BIOS-e820: [mem 0xbf225000-0xbf3d] usable
[0.00] BIOS-e820: [mem 0xbf3e-0xbfa1cfff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbfa1d000-0xbff94fff] reserved
[0.00] BIOS-e820: [mem 0xbff95000-0xbfffefff] type 20
[0.00] BIOS-e820: [mem 0xb000-0xbfff] usable
[0.00] BIOS-e820: [mem 0xc000-0xc00f] reserved
[0.00] BIOS-e820: [mem 

Bug#816690: marked as done (Thinkpad Carbon X1: RIP [] unlink_anon_vmas+0x4f/0x1a0)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 07:55:09 -0700 (PDT)
with message-id <6097f7cd.1c69fb81.9354.3...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #816690,
regarding Thinkpad Carbon X1: RIP  [] 
unlink_anon_vmas+0x4f/0x1a0
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.)


-- 
816690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:linux
Version: 4.4.2-3
Severity: normal

I'm having some strange problems with the 4.4.2-3 kernel in
high-load/high-memory-pressure situations with a ThinkPad Carbon X1 (3rd gen)
laptop, with a fault in unlink_anon_vmas.

It tends to hang right after turning on my monitor (which I'm also using with
as an USB hub), or when waking up the monitor from DPMS which causes the hub to
start working again. But I have no clue if it is related really, as I couldn't
reproduce the issue at all under low load situations.

In the log (which is short enough), it starts at the 8242.569150 mark.

I was able to trigger this issue three times in a couple of hours, while
reading intensively from the disk.

Please let me know if there's anything I can do to help.


-- Package-specific info:
** Version:
Linux version 4.4.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160205 (Debian 5.3.1-8) ) #1 SMP Debian 4.4.2-3 (2016-02-21)

** Command line:
BOOT_IMAGE=/vmlinuz-4.4.0-1-amd64 root=/dev/mapper/vg-root ro

** Tainted: DWO (4736)
* Kernel has oopsed before.
* Taint on warning.
* Out-of-tree module has been loaded.

** Kernel log:
[   16.249113] iTCO_wdt: Found a Wildcat Point_LP TCO device (Version=2, 
TCOBASE=0x1860)
[   16.249308] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   16.419460] Bluetooth: Core ver 2.21
[   16.419593] NET: Registered protocol family 31
[   16.419594] Bluetooth: HCI device and connection manager initialized
[   16.419597] Bluetooth: HCI socket layer initialized
[   16.419599] Bluetooth: L2CAP socket layer initialized
[   16.419605] Bluetooth: SCO socket layer initialized
[   16.423548] usbcore: registered new interface driver btusb
[   16.930908] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb2/2-5/2-5:1.0/0003:04F3:012D.0001/input/input19
[   16.931029] hid-multitouch 0003:04F3:012D.0001: input,hiddev0,hidraw3: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-5/input0
[   16.963172] media: Linux media interface: v0.10
[   16.966492] Linux video capture interface: v2.00
[   17.053611] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b45d)
[   17.056468] input: Integrated Camera as 
/devices/pci:00/:00:14.0/usb2/2-8/2-8:1.0/input/input21
[   17.056531] usbcore: registered new interface driver uvcvideo
[   17.056531] USB Video Class driver (1.1.1)
[   17.538575] Console: switching to colour frame buffer device 240x75
[   17.543844] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   17.573459] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
[   17.578934] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[   17.688840] usb 2-2.3.3: USB disconnect, device number 10
[   17.779629] cgroup: new mount options do not match the existing superblock, 
will be ignored
[   17.848586] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[   17.853276] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[   17.923935] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[   17.927543] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[   17.956838] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   17.977566] Process accounting resumed
[   18.013330] ip_tables: (C) 2000-2006 Netfilter Core Team
[   18.165424] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.176129] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   18.203345] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   18.379187] snd_hda_codec_hdmi hdaudioC1D0: HDMI: ELD buf size is 0, force 
128
[   18.381061] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 0
[   21.790888] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   21.790919] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   28.495795] fuse init (API version 7.23)
[ 2134.406442] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
[ 2134.409747] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[ 3985.207166] usb 2-2.3.3: new high-speed USB device number 11 using xhci_hcd
[ 3985.391000] usb 2-2.3.3: New USB device found, 

Bug#816211: marked as done (linux-image-3.16.0-0.bpo.4-amd64: /dev/sr? access is not parallel)

[Debian Bug Tracking System]

Your message dated Sun, 9 May 2021 16:49:18 +0200
with message-id 
and subject line Re: Bug#816211: linux-image-3.16.0-0.bpo.4-amd64: /dev/sr? 
access is not parallel
has caused the Debian Bug report #816211,
regarding linux-image-3.16.0-0.bpo.4-amd64: /dev/sr? access is not parallel
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.)


-- 
816211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3~bpo70+1
Severity: normal

Dear Maintainer,

There was a regression in the Linux kernel which made the I/Os to
sr devices (especially when ejecting or writing to DVD-Rs) synchronous
(non parallel).

If you write to a few DVD writes simultaneously, a 5-7x performance
degradation will occur.

You can reproduce the bug easily with:
   for i in /dev/sr?; do (eject $i&); done

If the drives do not open (almost) simultaneously but sequentially, the
bug is present.

Reference: 
http://linux-scsi.vger.kernel.narkive.com/JLvupYok/patch-scsi-sr-fix-multi-drive-performance-by-using-per-device-mutexes

I adapted a patch for that version below and successfully tested it.

-- Package-specific info:
** Version:
Linux version 3.16.0-0.bpo.4-amd64 (debian-kernel@lists.debian.org) (gcc 
version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u3~bpo70+1 
(2016-01-19)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-0.bpo.4-amd64 root=/dev/mapper/vg1-root ro quiet

--- drivers/scsi/sr.c   2015-11-18 11:08:46.0 +0100
+++ drivers/scsi/sr.c.NEW   2016-02-28 19:51:54.957158326 +0100
@@ -76,7 +76,6 @@
 CDC_CD_R|CDC_CD_RW|CDC_DVD|CDC_DVD_R|CDC_DVD_RAM|CDC_GENERIC_PACKET| \
 CDC_MRW|CDC_MRW_W|CDC_RAM)

-static DEFINE_MUTEX(sr_mutex);
 static int sr_probe(struct device *);
 static int sr_remove(struct device *);
 static int sr_init_command(struct scsi_cmnd *SCpnt);
@@ -520,24 +519,24 @@
struct scsi_cd *cd;
int ret = -ENXIO;

-   mutex_lock(_mutex);
cd = scsi_cd_get(bdev->bd_disk);
if (cd) {
+mutex_lock(>lock);
ret = cdrom_open(>cdi, bdev, mode);
+mutex_unlock(>lock);
if (ret)
scsi_cd_put(cd);
}
-   mutex_unlock(_mutex);
return ret;
 }

 static void sr_block_release(struct gendisk *disk, fmode_t mode)
 {
struct scsi_cd *cd = scsi_cd(disk);
-   mutex_lock(_mutex);
+   mutex_lock(>lock);
cdrom_release(>cdi, mode);
+   mutex_unlock(>lock);
scsi_cd_put(cd);
-   mutex_unlock(_mutex);
 }

 static int sr_block_ioctl(struct block_device *bdev, fmode_t mode, unsigned 
cmd,
@@ -548,7 +547,7 @@
void __user *argp = (void __user *)arg;
int ret;

-   mutex_lock(_mutex);
+   mutex_lock(>lock);

/*
 * Send SCSI addressing ioctls directly to mid level, send other
@@ -578,7 +577,7 @@
ret = scsi_ioctl(sdev, cmd, argp);

 out:
-   mutex_unlock(_mutex);
+   mutex_unlock(>lock);
return ret;
 }

@@ -673,6 +672,8 @@
if (!disk)
goto fail_free;

+   mutex_init(>lock);
+
spin_lock(_index_lock);
minor = find_first_zero_bit(sr_index_bits, SR_DISKS);
if (minor == SR_DISKS) {
@@ -742,6 +743,7 @@

 fail_put:
put_disk(disk);
+   mutex_destroy(>lock);
 fail_free:
kfree(cd);
 fail:
@@ -978,6 +980,8 @@

put_disk(disk);

+   mutex_destroy(>lock);
+
kfree(cd);
 }

--- drivers/scsi/sr.h   2015-11-18 11:08:46.0 +0100
+++ drivers/scsi/sr.h.NEW   2016-02-28 19:45:26.533162171 +0100
@@ -19,6 +19,7 @@

 #include 
 #include 
+#include 

 #define MAX_RETRIES3
 #define SR_TIMEOUT (30 * HZ)
@@ -49,6 +50,7 @@
bool ignore_get_event:1;/* GET_EVENT is unreliable, use TUR */

struct cdrom_device_info cdi;
+   struct mutex lock;
/* We hold gendisk and scsi_device references on probe and use
 * the refs on this kref to decide when to release them */
struct kref kref;
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.6.7-1

On Sun, Feb 28, 2016 at 08:20:52PM +0100, Marc SCHAEFER wrote:
> Package: src:linux
> Version: 3.16.7-ckt20-1+deb8u3~bpo70+1
> Severity: normal
> 
> Dear Maintainer,
> 
> There was a regression in the Linux kernel which made the I/Os to
> sr devices (especially when ejecting or writing to DVD-Rs) synchronous
> (non parallel).
> 
> If you write to a few DVD writes simultaneously, a 5-7x performance
> 

Bug#816106: marked as done (Suspend Bug, Severity: High)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 07:46:27 -0700 (PDT)
with message-id <6097f5c3.1c69fb81.f4359.e...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #816106,
regarding Suspend Bug, Severity: High
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.)


-- 
816106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: systemd-sysv  
Version:  225-1

Using a Gigabyte GA-Z170X0-Gaming 5 Motherboard:
 
Suspend doesn't allow a user to come back using Portable
USB drives. USB Drives are direct to back of motherboard WITHOUT
any hubs. It's as as if the drives have been removed once 
attempting to resume after any time period of suspend.
 

The computer is completely disabled and unable to resume
operation. Reboot is always necessary.
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#815800: marked as done (Activate support for WLAN USB N53 device)

[Debian Bug Tracking System]

Your message dated Sun, 9 May 2021 16:46:02 +0200
with message-id 
and subject line Re: Bug#815800: Activate support for WLAN USB N53 device
has caused the Debian Bug report #815800,
regarding Activate support for WLAN USB N53 device
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.)


-- 
815800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:linux
Version: 4.4.2-3

Hello,

in jessie and sid the ASUS USB-N53 B1 (aka N600) adapter is not working 
=> no wlan device is detected.


On [0] I have found, that "rt2800usb - Include support for unknown (USB) 
devices (RT2800USB_UNKNOWN)" has to be activated, but the Debian 
configuration says:

# CONFIG_RT2800USB_UNKNOWN is not set

[0]: https://wikidevi.com/wiki/ASUS_USB-N53

--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
--- End Message ---
--- Begin Message ---
Hi Patrick,

On Wed, Feb 24, 2016 at 04:02:19PM +0100, Patrick Matthäi wrote:
> Package: src:linux
> Version: 4.4.2-3
> 
> Hello,
> 
> in jessie and sid the ASUS USB-N53 B1 (aka N600) adapter is not working =>
> no wlan device is detected.
> 
> On [0] I have found, that "rt2800usb - Include support for unknown (USB)
> devices (RT2800USB_UNKNOWN)" has to be activated, but the Debian
> configuration says:
> # CONFIG_RT2800USB_UNKNOWN is not set
> 
> [0]: https://wikidevi.com/wiki/ASUS_USB-N53

is this still an issue? There were some more changes upstream and we
do enable CONFIG_RT2X00_LIB_USB as module. Though I have not tried now
to chevk if that enables the respective support for the particular
device.

In case you still have it, and this is relevant to you, please report
back (and reopen the bug if it still applies).

Regards,
Salvatore--- End Message ---

Bug#815757: marked as done (linux-image-4.3.0-1-amd64: BUG at /build/linux-19r8NQ/linux-4.3.5/fs/btrfs/extent_io.c:4636 - btrfs_release_extent_buffer_page)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 07:38:46 -0700 (PDT)
with message-id <6097f3f6.1c69fb81.e5999.0...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #815757,
regarding linux-image-4.3.0-1-amd64: BUG at 
/build/linux-19r8NQ/linux-4.3.5/fs/btrfs/extent_io.c:4636 - 
btrfs_release_extent_buffer_page
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.)


-- 
815757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.3.5-1
Severity: normal

kernel BUG in btrfs.  After BUG system hung and had to be rebooted.

Feb 24 01:53:43 black vmunix: [524578.024484] [ cut here 
]
Feb 24 01:53:43 black vmunix: [524578.026952] kernel BUG at 
/build/linux-19r8NQ/linux-4.3.5/fs/btrfs/extent_io.c:4636!
Feb 24 01:53:43 black vmunix: [524578.029221] invalid opcode:  [#1] SMP
Feb 24 01:53:43 black vmunix: [524578.031521] Modules linked in: nls_utf8 nfsd 
auth_rpcgss oid_registry isofs cpufreq_userspace cpufr
eq_stats cpufreq_powersave loop cpufreq_conservative nfsv3 nfs_acl nfs lockd 
grace sunrpc fscache binfmt_misc kvm_amd kvm crct10dif_p
clmul crc32_pclmul sha256_ssse3 sha256_generic hmac snd_usb_audio drbg 
snd_usbmidi_lib ansi_cprng snd_rawmidi amdkfd snd_seq_device a
esni_intel aes_x86_64 lrw gf128mul glue_helper radeon ablk_helper cryptd 
eeepc_wmi asus_wmi sparse_keymap rfkill video pcspkr serio_r
aw edac_mce_amd k10temp edac_core ttm fam15h_power drm_kms_helper drm 
i2c_algo_bit sp5100_tco snd_hda_codec_realtek snd_hda_codec_hdm
i snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd sg soundco
re shpchp i2c_piix4 wmi 8250_fintek button acpi_cpufreq tpm_tis tpm processor 
evdev it87 hwmon_vid eeprom i2c_nforce2 firewire_sbp2 f
irewire_core crc_itu_t psmouse parport_pc ppdev lp parport autofs4 ext4 crc16 
mbcache jbd2 btrfs xor hid_generic us
Feb 24 01:53:43 black vmunix: hid
Feb 24 01:53:43 black vmunix: hid raid6_pq sr_mod sd_mod cdrom ohci_pci 
crc32c_intel ahci libahci xhci_pci ehci_pci ohci_hcd libata x
hci_hcd ehci_hcd usbcore scsi_mod usb_common r8169 mii
Feb 24 01:53:43 black vmunix: [524578.047631] CPU: 2 PID: 39 Comm: kswapd0 
Tainted: GW   4.3.0-1-amd64 #1 Debian 4.3.5-1
Feb 24 01:53:43 black vmunix: [524578.051150] Hardware name: To be filled by 
O.E.M. To be filled by O.E.M./M5A97, BIOS 0705 08/22/201
1
Feb 24 01:53:43 black vmunix: [524578.054240] task: 8800b24d4e00 ti: 
8800b24d8000 task.ti: 8800b24d8000
Feb 24 01:53:43 black vmunix: [524578.057203] RIP: 0010:[]  
[] btrfs_release_extent_buffer_page+0
xf6/0x100 [btrfs]
Feb 24 01:53:43 black vmunix: [524578.060414] RSP: 0018:8800b24dba80  
EFLAGS: 00010202
Feb 24 01:53:43 black vmunix: [524578.064828] RAX: 02840938 RBX: 
ea00046e1e40 RCX: 
Feb 24 01:53:43 black vmunix: [524578.069557] RDX: 0001 RSI: 
812e2800 RDI: 8800bcef6f38
Feb 24 01:53:43 black vmunix: [524578.074325] RBP:  R08: 
 R09: 880003c41008
Feb 24 01:53:43 black vmunix: [524578.079117] R10: 8800b24dba68 R11: 
 R12: 880020ee37f8
Feb 24 01:53:43 black vmunix: [524578.083930] R13:  R14: 
0001 R15: 8800bcef6ec0
Feb 24 01:53:43 black vmunix: [524578.088758] FS:  7f485b016700() 
GS:88013ec8() knlGS:f7789b40
Feb 24 01:53:43 black vmunix: [524578.093632] CS:  0010 DS:  ES:  CR0: 
8005003b
Feb 24 01:53:43 black vmunix: [524578.098491] CR2: 7f485a27b74b CR3: 
0001134bf000 CR4: 000406e0
Feb 24 01:53:43 black vmunix: [524578.103391] Stack:
Feb 24 01:53:43 black vmunix: [524578.108389]  880020ee37f8 
8800b8736000 8800b8736ea8 ea4377c0
Feb 24 01:53:43 black vmunix: [524578.113442]  a028401a 
8800b24dbe60 ea4377e0 8800b24dbc30
Feb 24 01:53:43 black vmunix: [524578.118488]  811736b9 
  
Feb 24 01:53:43 black vmunix: [524578.123553] Call Trace:
Feb 24 01:53:43 black vmunix: [524578.128644]  [] ? 
release_extent_buffer+0x4a/0xc0 [btrfs]
Feb 24 01:53:43 black vmunix: [524578.133846]  [] ? 
shrink_page_list+0x6d9/0x780
Feb 24 01:53:43 black vmunix: [524578.139173]  [] ? 
shrink_inactive_list+0x274/0x530
Feb 24 01:53:43 black vmunix: [524578.144528]  [] ? 
shrink_lruvec+0x55d/0x740
Feb 24 01:53:43 black vmunix: [524578.149889]  [] ? 

Bug#815425: marked as done (linux-image-3.16.0-4-amd64: cifs kernel lockup with rsync)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 07:38:03 -0700 (PDT)
with message-id <6097f3cb.1c69fb81.bab2e.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #815425,
regarding linux-image-3.16.0-4-amd64: cifs kernel lockup with rsync
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.)


-- 
815425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal

I have a cifs mount from the NAS monitored by the inotify (minidlna
software). Usually files are transferred using the 'cp' utility. Once I invoked
rsync to copy files from the ext3 filesystem to the cifs mount. Then rsync
hanged with a following kernel message, mount.cifs and sync also hanged.

Dont's sure is it only rsync's fault because I interrupted a copy
operation before the faulty rsync invocation. Other machines can mount this
volume succesfully. Restarting samba on the NAS helped to umount a share
but subsequent remount hanged.

fstab entry:

//srv/movies /mnt/movies   cifs 
defaults,credentials=/etc/samba.cred,iocharset=utf8,uid=irix,gid=users,file_mode=0775,dir_mode=0775
  0 0


Kernel log for the crash:

Feb 21 14:40:06 atom kernel: [362565.937839] CIFS VFS: No writable handles for 
inode
a lot of times...
Feb 21 14:40:16 atom kernel: [362575.898743] CIFS VFS: No writable handles for 
inode
Feb 21 14:43:08 atom kernel: [362748.037650] INFO: task kworker/u8:1:30769 
blocked for more than 120 seconds.
Feb 21 14:43:08 atom kernel: [362748.037679]   Tainted: G C O  
3.16.0-4-amd64 #1
Feb 21 14:43:08 atom kernel: [362748.037699] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 21 14:43:08 atom kernel: [362748.037732] kworker/u8:1D 880074ac2f78 
0 30769  2 0x0080
Feb 21 14:43:08 atom kernel: [362748.037744] Workqueue: writeback 
bdi_writeback_workfn (flush-cifs-5)
Feb 21 14:43:08 atom kernel: [362748.037748]  880074ac2b20 0046 
00012f00 880114e7bfd8
Feb 21 14:43:08 atom kernel: [362748.037752]  00012f00 880074ac2b20 
880114e7b9f0 88013ffbdb60
Feb 21 14:43:08 atom kernel: [362748.037755]  0002 811c1510 
880114e7b9e0 880046ba3a00
Feb 21 14:43:08 atom kernel: [362748.037759] Call Trace:
Feb 21 14:43:08 atom kernel: [362748.037768]  [] ? 
unlock_two_nondirectories+0x60/0x60
Feb 21 14:43:08 atom kernel: [362748.037772]  [] ? 
inode_wait+0xa/0x10
Feb 21 14:43:08 atom kernel: [362748.03]  [] ? 
__wait_on_bit+0x5c/0x90
Feb 21 14:43:08 atom kernel: [362748.037781]  [] ? 
__inode_wait_for_writeback+0x9b/0xc0
Feb 21 14:43:08 atom kernel: [362748.037786]  [] ? 
autoremove_wake_function+0x30/0x30
Feb 21 14:43:08 atom kernel: [362748.037796]  [] ? 
inode_wait_for_writeback+0x1d/0x30
Feb 21 14:43:08 atom kernel: [362748.037799]  [] ? 
evict+0x99/0x170
Feb 21 14:43:08 atom kernel: [362748.037803]  [] ? 
__dentry_kill+0x168/0x1d0
Feb 21 14:43:08 atom kernel: [362748.037807]  [] ? 
dput+0x9e/0x170
Feb 21 14:43:08 atom kernel: [362748.037818]  [] ? 
cifsFileInfo_put+0x23a/0x370 [cifs]
Feb 21 14:43:08 atom kernel: [362748.037827]  [] ? 
find_writable_file+0x188/0x210 [cifs]
Feb 21 14:43:08 atom kernel: [362748.037835]  [] ? 
cifs_writepages+0x355/0x680 [cifs]
Feb 21 14:43:08 atom kernel: [362748.037839]  [] ? 
__writeback_single_inode+0x39/0x220
Feb 21 14:43:08 atom kernel: [362748.037843]  [] ? 
writeback_sb_inodes+0x1a4/0x3e0
Feb 21 14:43:08 atom kernel: [362748.037847]  [] ? 
__writeback_inodes_wb+0x96/0xc0
Feb 21 14:43:08 atom kernel: [362748.037851]  [] ? 
wb_writeback+0x243/0x2d0
Feb 21 14:43:08 atom kernel: [362748.037855]  [] ? 
bdi_writeback_workfn+0x2a1/0x420
Feb 21 14:43:08 atom kernel: [362748.037859]  [] ? 
process_one_work+0x172/0x420
Feb 21 14:43:08 atom kernel: [362748.037863]  [] ? 
worker_thread+0x113/0x4f0
Feb 21 14:43:08 atom kernel: [362748.037866]  [] ? 
rescuer_thread+0x2d0/0x2d0
Feb 21 14:43:08 atom kernel: [362748.037871]  [] ? 
kthread+0xbd/0xe0
Feb 21 14:43:08 atom kernel: [362748.037875]  [] ? 
kthread_create_on_node+0x180/0x180
Feb 21 14:43:08 atom kernel: [362748.037879]  [] ? 
ret_from_fork+0x58/0x90
Feb 21 14:43:08 atom kernel: [362748.037883]  [] ? 
kthread_create_on_node+0x180/0x180
a lot of times...
Feb 21 14:54:10 atom kernel: [363411.970779] CIFS VFS: Error -104 sending data 
on socket to server
Feb 21 14:54:10 atom kernel: [363411.985478] CIFS VFS: 

Bug#815737: marked as done (linux-images bug)

[Debian Bug Tracking System]

Your message dated Sun, 09 May 2021 07:38:23 -0700 (PDT)
with message-id <6097f3df.1c69fb81.1130.3...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #815737,
regarding linux-images bug
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.)


-- 
815737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Version: 3.16.7-ckt11-1+deb8u3

using this kernel, we are facing kernel panic normally.

the call trace information : ( jessie: 8.2 )

[2973074.796563] general protection fault:  [#1] SMP
[2973074.796818] Modules linked in: nls_utf8 btrfs xor raid6_pq
hfsplus xfs libcrc32c dm_mod cdc_ether usbnet mii joydev hid_generic
usbhid hid 8021q garp stp mrp llc x86_pkg_temp_thermal
intel_powerclamp intel_rapl coretemp kvm_intel kvm crc32_pclmul
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper
ablk_helper evdev cryptd ttm drm_kms_helper drm iTCO_wdt
iTCO_vendor_support lpc_ich dcdbas mei_me pcspkr mfd_core mei
ipmi_watchdog processor thermal_sys acpi_power_meter shpchp wmi button
ipmi_si ipmi_poweroff ipmi_devintf ipmi_msghandler autofs4 ext4 crc16
mbcache jbd2 sg sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul
crct10dif_common crc32c_intel ehci_pci igb i2c_algo_bit ehci_hcd ixgbe
i2c_core megaraid_sas dca usbcore ptp pps_core usb_common mdio
scsi_mod
[2973074.803401] CPU: 28 PID: 248515 Comm: java Not tainted
3.16.0-4-amd64 #1 Debian 3.16.7-ckt11-1+deb8u3
[2973074.803540] Hardware name: Dell Inc. PowerEdge R730xd/0H21J3,
BIOS 1.5.4 10/002/2015
[2973074.803675] task: 881b21a16c60 ti: 880054778000 task.ti:
880054778000
[2973074.803808] RIP: 0010:[]  []
_raw_spin_lock_irqsave+0x1b/0x50
[2973074.804022] RSP: 0018:88005477b930  EFLAGS: 00010046
[2973074.804129] RAX: 0046 RBX: ea0003fc1670 RCX:
0001
[2973074.804262] RDX: 0001 RSI: 0046 RDI:
3e0e0ba50e1f7b26
[2973074.804395] RBP: 3e0e0ba50e1f7b0e R08: 88005477ba98 R09:
091b
[2973074.804528] R10: 3605 R11: ffaa R12:
3e0e0ba50e1f7b26
[2973074.804660] R13: 00123800 R14: 88187fffbe00 R15:
0001
[2973074.804794] FS:  7f8eac579700() GS:88187f5c()
knlGS:
[2973074.804929] CS:  0010 DS:  ES:  CR0: 80050033
[2973074.805037] CR2: ee2c5000 CR3: 000334ce3000 CR4:
001407e0
[2973074.805169] Stack:
[2973074.805268]  81160977 00123742 ea0003fc1670
0143
[2973074.805689]  8115fc9e ea0003fbd000 88005477ba40
091b
[2973074.806110]  88005477bfd8  
091b
[2973074.806532] Call Trace:
[2973074.806637]  [] ? balloon_page_isolate+0x97/0x110
[2973074.806749]  [] ? isolate_migratepages_range+0x89e/0x8c0
[2973074.806861]  [] ? compact_zone+0x22d/0x4a0
[2973074.806970]  [] ? compact_zone_order+0x8e/0xd0
[2973074.807080]  [] ? try_to_compact_pages+0xc5/0xf0
[2973074.807191]  [] ? __alloc_pages_direct_compact+0xab/0x1a3
[2973074.807305]  [] ? __alloc_pages_nodemask+0x8b3/0xb30
[2973074.807418]  [] ? alloc_pages_current+0x9d/0x150
[2973074.807530]  [] ? skb_page_frag_refill+0x5f/0xb0
[2973074.807641]  [] ? sk_page_frag_refill+0x19/0x70
[2973074.807752]  [] ? tcp_sendmsg+0x265/0xd20
[2973074.807861]  [] ? sock_aio_write+0xf6/0x120
[2973074.807970]  [] ? sock_aio_read.part.7+0xfe/0x120
[2973074.808083]  [] ? do_sync_write+0x5c/0x90
[2973074.808193]  [] ? vfs_write+0x195/0x1f0
[2973074.808301]  [] ? vfs_read+0xed/0x170
[2973074.808457]  [] ? SyS_write+0x42/0xa0
[2973074.808566]  [] ? system_call_fast_compare_end+0x10/0x15
[2973074.808677] Code: eb f2 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00
0f 1f 44 00 00 9c 58 0f 1f 44 00 00 48 89 c6 fa 66 0f 1f 44 00 00 ba
00 00 01 00  0f c1 17 89 d1 c1 e9 10 66 39 d1 89 c8 75 04 48 89 f0
c3 0f
[2973074.813557] RIP  [] _raw_spin_lock_irqsave+0x1b/0x50
[2973074.813741]  RSP 


BRs

yongsu
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---