Bug#1070986: This is a bug in debian scripts not upstream
It's actually upstream. I ran the same: $ make bindeb-pkg on the upstream source as I did on the Debian source, and yes, it gave me .deb packages. Here's the repo for the upstream script that was part of the problem: https://github.com/torvalds/linux/commits/master/scripts/package/builddeb Note the recent changes. I may be wrong, and it's a Debian patch that is causing the problem, but from what I've seen of the code it's probably upstream. I suppose I could download an upstream version of 6.7, and verify it has the same problem, but since nobody on the Debian maintainer side seems to care, I won't bother.
Bug#1070986: linux-source-6.7: Signing error building 6.7 custom kernel
This works in the 6.8.9 upstream kernel. So I guess the good news is it wil be fixed in Debian eventually.
Bug#1070986: linux-source-6.7: Signing error building 6.7 custom kernel
Package: linux-source-6.7 Version: 6.7.12-1 Severity: normal X-Debbugs-Cc: to...@dilacero.org Dear Maintainer, I'm following the directions at the Kernel Handbook, "4.2. Building a custom kernel from Debian kernel source". I apt-get installed: linux-source libncurses-dev pahole I configured with: $ make localmodconfig and took defaults to any prompts. I then ran: $ make menuconfig and turned on: Kernel hacking->Generic Kernel Debugging Instruments->KGDB: kernel debugger (KGDB=y) And finally, ran: $ make bindeb-pkg The kernel compiled, but then failed with: ... HDRINST usr/include/asm/types.h INSTALL debian/linux-libc-dev/usr/include SIGN debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko At main.c:298: - SSL error:8002:system library::No such file or directory: ../crypto/bio/bss_file.c:67 - SSL error:1080:BIO routines::no such file: ../crypto/bio/bss_file.c:75 sign-file: debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko make[6]: *** [scripts/Makefile.modinst:137: debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko] Error 1 make[5]: *** [Makefile:1844: modules_install] Error 2 make[4]: *** [Makefile:2059: run-command] Error 2 make[3]: *** [debian/rules:17: binary-arch] Error 2 ESC[1mdpkg-buildpackage: ESC[0mESC[1;31merrorESC[0m: make -f debian/rules binary subprocess returned exit status 2 make[2]: *** [scripts/Makefile.package:144: bindeb-pkg] Error 2 make[1]: *** [/home/virt/linux-source-6.7/Makefile:1560: bindeb-pkg] Error 2 make: *** [Makefile:246: __sub-make] Error 2 I did some digging, and it looks like it's trying to double-sign the .ko files. For example, earlier in the make output, it says: run-command KBUILD_RUN_COMMAND=+./scripts/package/builddeb SYMLINK debian/linux-image/lib/modules/6.7.12/build INSTALL debian/linux-image/lib/modules/6.7.12/modules.order INSTALL debian/linux-image/lib/modules/6.7.12/modules.builtin INSTALL debian/linux-image/lib/modules/6.7.12/modules.builtin.modinfo INSTALL debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko SIGN debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko XZ debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko.xz And ls shows the .xz file is there: $ ls debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel* debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko.xz So then when it tries to sign the .ko file again, it can't find it, because it's been compressed to .xz. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-source-6.7 depends on: ii binutils 2.42-4 ii xz-utils 5.6.1+really5.4.5-1 Versions of packages linux-source-6.7 recommends: ii bc1.07.1-4 ii bison 2:3.8.2+dfsg-1+b1 ii build-essential 12.10 ii cpio 2.15+dfsg-1 ii flex 2.6.4-8.2+b2 ii kmod 32-1 ii libelf-dev0.191-1+b1 ii libssl-dev3.2.1-3 ii linux-config-6.7 6.7.12-1 ii rsync 3.3.0-1 Versions of packages linux-source-6.7 suggests: ii libncurses-dev [ncurses-dev] 6.4+20240414-1 ii pkgconf [pkg-config] 1.8.1-1+b2 pn qtbase5-dev -- no debconf information
Bug#1004255: linux-image-5.14.0-1-sparc64-smp: Debian kernels > 5.14.3-1~exp1 fail to boot on SPARC T4-1 with Fast Data Access MMU Miss
Hi Adrian, > This looks more like an issue with your bootloader. I haven't used SILO for a > long time, so I don't have a track what currently works and what not. Thanks for pointing that out! I was searching in the wrong direction... > Can you try booting the current ISO snapshot image? Yes, that image boots successfully on this machine, with a newer kernel, using GRUB instead of SILO. So the actual issue is that Debian kernels > 5.14.3-1~exp1 fail to boot with SILO 1.4.14+git20141019-5. I've also built the latest SILO from git [1] but it has the same issue: it boots Debian kernel 5.14.3-1~exp1 successfully, but later Debian kernels fail with ERROR: Last Trap: Fast Data Access MMU Miss. I had previously given up on migrating to GRUB, as I couldn't get it to work with RAID1 boot and root partitions on disks with a Sun disk label. I still can't get that working but I'll start a separate thread for that. As this SPARC T4-1 is able to boot from disks with GPT/EFI disk label, I've converted the disks to use a GPT/EFI label with a dedicated BIOS boot partition and installed GRUB using the instructions at [2]. It is working fine with RAID1 boot and root partitions and with newer Debian kernels. It would still be nice to know why newer Debian kernels fail to boot with SILO, but I don't know how to debug ERROR: Last Trap: Fast Data Access MMU Miss. This Debian bug report can be closed as resolved by migrating from SILO to GRUB. [1] https://git.kernel.org/pub/scm/linux/kernel/git/davem/silo.git [2] https://github.com/esnowberg/grub2-sparc/wiki
Bug#1004255: linux-image-5.14.0-1-sparc64-smp: Debian kernels > 5.14.3-1~exp1 fail to boot on SPARC T4-1 with Fast Data Access MMU Miss
Package: src:linux Version: 5.14.6-2 Severity: important X-Debbugs-Cc: debian-sp...@lists.debian.org Dear Maintainer, Debian kernels > 5.14.3-1~exp1 consistently fail to boot on SPARC T4-1: SPARC T4-1, No Keyboard Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved. OpenBoot 4.36.2, 31.5000 GB memory available, Serial #108045182. Ethernet address 0:10:e0:70:a3:7e, Host ID: 8670a37e. Boot device: disk0 File and args: SILO Version 1.4.14 boot: Allocated 64 Megs of memory at 0x4000 for kernel Uncompressing image... Loaded kernel version 5.14.6 Loading initial ramdisk (25723814 bytes at 0x2480 phys, 0x40C0 virt)... ERROR: Last Trap: Fast Data Access MMU Miss Debian kernels 5.14.3-1~exp1 and earlier boot and run successfully on this system. I have tried the sparc64-smp packages built by buildd landau for these versions: 5.14.6-2, 5.14.6-3, 5.14.9-2, 5.15.5-2, 5.15.15-1, 5.16~rc8-1~exp1 They all consistently fail to boot with the same error. I have built the Debian src pkg version 5.14.6-1 using pbuilder with a sid basetgz. It consistently fails to boot with the same error. I've then tried to bisect using the DebianKernel/GitBisect instructions on the Debian wiki, but it turns out that kernels built from git (tag v5.14.3, tag v5.14.6, and ~9 bisects in between) using make bindeb-pkg all do boot successfully on this system. I've tried checking out tag v5.14.6 from git, then applying all the patches from debian/patches in the 5.14.6-1 src pkg and building using make bindeb-pkg. The resulting kernel boots successfully. I've tried extracting the 5.14.6-1 src pkg using dpkg-source -x, then building using make bindeb-pkg and the resulting kernel boots succesfully. But if I build using dpkg-buildpackage like pbuilder does, then the resulting -sparc64-smp package fails to boot with the above error. When building, I have used each time a clean sid changeroot. When using make bindeb-pkg I have copied the config installed in /boot by the (non-booting) 5.14.6-1 Debian package then done make olddefconfig. When using make bindeb-pkg I had to manually disable stringop-overread warnings in Makefile to avoid build failure on arch/sparc/kernel/mdesc.c with v5.14.6 (fixed in later versions by [1]). When building using bindeb-pkg the resulting kernel is compressed; when using dpkg-buildpackage the resulting kernel is uncompressed. I have tried both uncompressing the compressed kernel and compressing the uncompressed kernel, as silo supports both. It doesn't affect the results. Uncompressed, the Debian kernel is ~17MB while the standard kernel is ~13MB. I'm not sure why this difference is there. On Debian salsa's kernel-team/linux I have combed through all the commits between tags debian/5.14.3-1_exp1 and debian/5.14.6-1, but none of them seem relevant to this issue. I have checked the upstream changelog between v5.14.3 and v5.14.6, but nothing sparc-specific has changed. According to the buildd logs, landau is running kernel 5.15.5-2. But I think this is a SPARC-T5 so not a T4, and I think it's running inside an LDOM which is not the case on my T4, so it may not be comparable. I've also tried to get more information about the failure, but I don't know how to do that. I've tried to get into the initramfs environment by using break=premount/modules/top, but the failure happens before those stages. Measuring the elapsed time after Loading initial ramdisk it would seem the error message ERROR: Last Trap: Fast Data Access MMU Miss appears when normally the first kernel output would appear. I've tried to look into what the Debian src pkg's debian/* scripts do, exactly, but this is rather complicated and I have limited experience with it. Any suggestions what else I could try? [1]: https://github.com/gregkh/linux/commit/fc7c028dcdbfe981bca75d2a7b95f363eb691ef3 -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information cpu : UltraSparc T4 (Niagara4) fpu : UltraSparc T4 integrated FPU pmu : niagara4 prom: OBP 4.36.2 2014/10/24 08:13 type: sun4v ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto br0 iface br0 inet static bridge_ports enp15s0f0 bridge_fd 0 address x.x.x.x netmask x.x.x.x gateway x.x.x.x iface enp15s0f0 inet manual ** PCI devices: 00:01.0 PCI bridge [0604]: Oracle/SUN Device [108e:8186] (rev 01) (prog-if 00 [Normal decode]) Device tree node: /sys/firmware/devicetree/base/pci@400/pci@1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:02.0 PCI bridge [0604]: Oracle/SUN Device
Re: Availability of Kernel 5.15 on Debian 11 Bullseye Backport
Hi, i would also appreciate some newer Kernels. I'm experiencing really poor throughput (under 10 Mbit/s instead of Gigabit) with ip6gre on Debian and the 5.10 Kernel. I think this was resolved in newer Versions. I'm currently still searching which patch resolved this or what the preferred way forward should be. But being able to just use something current would be the easiest way for me. Cheers, Tom
Affiliate opportunity
This is an HTML message and it cannot be opened by your email client. Please visit the link below to read it: http://mstat072.co.uk/service.php?s=webversion&mm=2CHO016000860045049400383500647980678488e52 Visor Commerce Ltd (T/A OnBuy) - Registered Address: Unit J7, 6 Vantage Way, Poole, BH12 4NU, United Kingdom
Bug#917706: nfs v2.x
Should the hold-up to upgrading to nfs-utils v2.x be the migration to
"/etc/nfs.conf", Fedora has a python conversion script
https://src.fedoraproject.org/rpms/nfs-utils/raw/master/f/nfsconvert.py
#!/usr/bin/env python3
"""
Read in the deprecated /etc/sysconfig/nfs file and
set the corresponding values in nfs.conf
"""
from __future__ import print_function
import os
import sys
import getopt
import subprocess
import configparser
CONF_NFS = '/etc/nfs.conf'
CONF_IDMAP = '/etc/idmapd.conf'
SYSCONF_NFS = '/etc/sysconfig/nfs'
SYSCONF_BACKUP = ".rpmsave"
CONF_TOOL = '/usr/sbin/nfsconf'
# options for nfsd found in RPCNFSDARGS
OPTS_NFSD = 'dH:p:rR:N:V:stTuUG:L:'
LONG_NFSD = ['debug', 'host=', 'port=', 'rdma=', 'nfs-version=',
'no-nfs-version=',
'tcp', 'no-tcp', 'udp', 'no-udp', 'grace-time=', 'lease-time=']
CONV_NFSD = {'-d': (CONF_NFS, 'nfsd', 'debug', 'all'),
'-H': (CONF_NFS, 'nfsd', 'host', ','),
'-p': (CONF_NFS, 'nfsd', 'port', '$1'),
'-r': (CONF_NFS, 'nfsd', 'rdma', 'nfsrdma'),
'-R': (CONF_NFS, 'nfsd', 'rdma', '$1'),
'-N': (CONF_NFS, 'nfsd', 'vers$1', 'n'),
'-V': (CONF_NFS, 'nfsd', 'vers$1', 'y'),
'-t': (CONF_NFS, 'nfsd', 'tcp', '1'),
'-T': (CONF_NFS, 'nfsd', 'tcp', '0'),
'-u': (CONF_NFS, 'nfsd', 'udp', '1'),
'-U': (CONF_NFS, 'nfsd', 'udp', '0'),
'-G': (CONF_NFS, 'nfsd', 'grace-time', '$1'),
'-L': (CONF_NFS, 'nfsd', 'lease-time', '$1'),
'$1': (CONF_NFS, 'nfsd', 'threads', '$1'),
'--debug': (CONF_NFS, 'nfsd', 'debug', 'all'),
'--host': (CONF_NFS, 'nfsd', 'host', ','),
'--port': (CONF_NFS, 'nfsd', 'port', '$1'),
'--rdma': (CONF_NFS, 'nfsd', 'rdma', '$1'),
'--no-nfs-version': (CONF_NFS, 'nfsd', 'vers$1', 'n'),
'--nfs-version': (CONF_NFS, 'nfsd', 'vers$1', 'y'),
'--tcp': (CONF_NFS, 'nfsd', 'tcp', '1'),
'--no-tcp': (CONF_NFS, 'nfsd', 'tcp', '0'),
'--udp': (CONF_NFS, 'nfsd', 'udp', '1'),
'--no-udp': (CONF_NFS, 'nfsd', 'udp', '0'),
'--grace-time': (CONF_NFS, 'nfsd', 'grace-time', '$1'),
'--lease-time': (CONF_NFS, 'nfsd', 'lease-time', '$1'),
}
# options for mountd found in RPCMOUNTDOPTS
OPTS_MOUNTD = 'go:d:H:p:N:nrs:t:V:'
LONG_MOUNTD = ['descriptors=', 'debug=', 'nfs-version=', 'no-nfs-version=',
'port=', 'no-tcp', 'ha-callout=', 'state-directory-path=',
'num-threads=', 'reverse-lookup', 'manage-gids', 'no-udp']
CONV_MOUNTD = {'-g': (CONF_NFS, 'mountd', 'manage-gids', '1'),
'-o': (CONF_NFS, 'mountd', 'descriptors', '$1'),
'-d': (CONF_NFS, 'mountd', 'debug', '$1'),
'-H': (CONF_NFS, 'mountd', 'ha-callout', '$1'),
'-p': (CONF_NFS, 'mountd', 'port', '$1'),
'-N': (CONF_NFS, 'nfsd', 'vers$1', 'n'),
'-V': (CONF_NFS, 'nfsd', 'vers$1', 'y'),
'-n': (CONF_NFS, 'nfsd', 'tcp', '0'),
'-s': (CONF_NFS, 'mountd', 'stat-directory-path', '$1'),
'-t': (CONF_NFS, 'mountd', 'threads', '$1'),
'-r': (CONF_NFS, 'mountd', 'reverse-lookup', '1'),
'-u': (CONF_NFS, 'nfsd', 'udp', '0'),
'--manage-gids': (CONF_NFS, 'mountd', 'manage-gids', '1'),
'--descriptors': (CONF_NFS, 'mountd', 'descriptors', '$1'),
'--debug': (CONF_NFS, 'mountd', 'debug', '$1'),
'--ha-callout': (CONF_NFS, 'mountd', 'ha-callout', '$1'),
'--port': (CONF_NFS, 'mountd', 'port', '$1'),
'--nfs-version': (CONF_NFS, 'nfsd', 'vers$1', 'y'),
'--no-nfs-version': (CONF_NFS, 'nfsd', 'vers$1', 'n'),
'--no-tcp': (CONF_NFS, 'nfsd', 'tcp', '0'),
'--state-directory-path': (CONF_NFS, 'mountd',
'state-directory-path', '$1'),
'--num-threads': (CONF_NFS, 'mountd', 'threads', '$1'),
'--reverse-lookup': (CONF_NFS, 'mountd', 'reverse-lookup', '1'),
'--no-udp': (CONF_NFS, 'nfsd', 'udp', '0'),
}
# options for statd found in STATDARG
OPTS_STATD = 'o:p:T:U:n:P:H:'
LONG_STATD = ['outgoing-port=', 'port=', 'name=', 'state-directory-path=',
'ha-callout=', 'nlm-port=', 'nlm-udp-port=']
CONV_STATD = {'-o': (CONF_NFS, 'statd', 'outgoing-port', '$1'),
'-p': (CONF_NFS, 'statd', 'port', '$1'),
'-T': (CONF_NFS, 'lockd', 'port', '$1'),
'-U': (CONF_NFS, 'lockd', 'udp-port', '$1'),
'-n': (CONF_NFS, 'statd', 'name', '$1'),
'-P': (CONF_NFS, 'statd', 'state-directory-path', '$1'),
'-H': (CONF_NFS, 'statd', 'ha-callout', '$1'),
'--outgoing-port': (CONF_NFS, 'statd', 'outgoing-port', '$1'),
'--port': (CONF_NFS, 'statd', 'port', '$1'),
'--name': (CONF_N
Bug#539201: Cannot specify rpc.nfsd options
It's misnamed but "RPCNFSDCOUNT" in "/etc/default/nfs-kernel-server" can be used. It might not be worth creating a more appropriate, separate variable given that, when Debian upgrades to v2.x (first released, as 2.1.1, three and a half years ago), options'll be set via "/etc/nfs.conf".
Re: What belongs in the Debian cloud kernel?
Hi! I'd be happy to work on creating documentation for the Debian cloud kernel, especially for OpenStack. I"ve worked with Debian as my primary OS for several years now, and have also been exploring OpenStack. I'm also honing my Technical Writer skills through on online course. Writing this documentation would give me an opportunity to combine all my interests in a single project. How/when do I start? Thank you, Tom Ladd On Wed, Apr 1, 2020, 12:15 PM Noah Meyerhans wrote: > For buster, we generate a cloud kernel for amd64. For sid/bullseye, > we'll also support a cloud kernel for arm64. At the moment, the cloud > kernel is the only used in the images we generate for Microsoft Azure > and Amazon EC2. It's used in the GCE images we generate as well, but > I'm not sure anybody actually uses those. We generate two OpenStack > images, one that uses the cloud kernel and another uses the generic > kernel. > > There are open bugs against the cloud kernel requesting that > configuration options be turned on there. [1][2][3] These, IMO, > highlight a need for some documentation around what is in scope for the > cloud kernel, and what is not. This will help us answer requests such > as these more consistently, and it will also help our users better > understand whether they can expect the cloud kernel to meet their needs > or not. > > At the moment, the primary optimization applied to the cloud kernel > focuses on disk space consumed. We disable compilation of drivers that > we feel are unlikely to ever appear in a cloud environment. By doing > so, we reduce the installed size of the kernel package by roughly 70%. > There are other optimization we may apply (see [4] for examples), but we > don't yet. > > Should we simply say "yes" to any request to add functionality to the > cloud kernel? None of the drivers will add *that* much to the size of > the image, and if people are asking for them, then they've obviously got > a use case for them. Or is this a slipperly slope that diminishes the > value of the cloud kernel? I can see both sides of the argument, so I'd > like to hear what others have to say. > > If we're not going to say "yes" to all requests, what criteria should we > use to determine whether or not to enable a feature? It's rather not > leave it as a judgement call. > > noah > > 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952108 > 2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955366 > 3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955232 > 4. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947759 > >
Bug#954817: linux-image-5.4.0-4-amd64: NULL pointer dereference in i915_active_acquire since Linux 5.4
Package: src:linux
Version: 5.4.19-1
Severity: important
Tags: patch
Dear Maintainer,
Since kernel 5.4.x I am getting crashes during some graphic rendering poccess
like playing videos. I found the following patch might fix this problem.
The patch already got into kernel 5.5.x but still not into 5.4.x. Could you
patch it into kernel 5.4.x? Or release the kernel 5.5 version? Thanks!
Patchwork: https://patchwork.freedesktop.org/patch/345789/?series=70930&rev=3
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.5.y&id=e85ade1f50aae464ce196672faa7a099fd1721ed
-- Package-specific info:
** Version:
Linux version 5.4.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1
20200203 (Debian 9.2.1-28)) #1 SMP Debian 5.4.19-1 (2020-02-13)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-4-amd64
root=UUID=bc9fa405-daee-4f2a-a27a-44e1c0513187 ro quiet
** Tainted: OE (12288)
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Mar 16 18:39:24 Server kernel: [606320.517436] BUG: kernel NULL pointer
dereference, address: 0040
Mar 16 18:39:24 Server kernel: [606320.517453] #PF: supervisor read access in
kernel mode
Mar 16 18:39:24 Server kernel: [606320.517454] #PF: error_code(0x) -
not-present page
Mar 16 18:39:24 Server kernel: [606320.517455] PGD 0 P4D 0
Mar 16 18:39:24 Server kernel: [606320.517461] Oops: [#1] SMP PTI
Mar 16 18:39:24 Server kernel: [606320.517469] CPU: 3 PID: 2072967 Comm: xfwm4
Tainted: G OE5.4.0-4-amd64 #1 Debian 5.4.19-1
Mar 16 18:39:24 Server kernel: [606320.517471] Hardware name: To Be Filled By
O.E.M. To Be Filled By O.E.M./H310M-ITX/ac, BIOS P3.10 09/27>
Mar 16 18:39:24 Server kernel: [606320.517745] RIP:
0010:i915_active_acquire+0x9/0x70 [i915]
Mar 16 18:39:24 Server kernel: [606320.517751] Code: 00 00 00 48 c7 46 58 00 00
00 00 c7 46 38 00 00 00 00 48 c7 c6 0a a0 65 c0 e9 33 90 7>
Mar 16 18:39:24 Server kernel: [606320.517753] RSP: 0018:a06400e07a40
EFLAGS: 00010286
Mar 16 18:39:24 Server kernel: [606320.517757] RAX: RBX:
8da74554f480 RCX:
Mar 16 18:39:24 Server kernel: [606320.517759] RDX: 8da642d61200 RSI:
8da74554f480 RDI: 0008
Mar 16 18:39:24 Server kernel: [606320.517760] RBP: 8da642d61200 R08:
8da74a4db988 R09: 8da74a4db988
Mar 16 18:39:24 Server kernel: [606320.517761] R10: a000 R11:
R12: 0008
Mar 16 18:39:24 Server kernel: [606320.517763] R13: 0004 R14:
8da642d61200 R15: 401c
Mar 16 18:39:24 Server kernel: [606320.517765] FS: 7f5f29303f00()
GS:8da8a5f8() knlGS:
Mar 16 18:39:24 Server kernel: [606320.517767] CS: 0010 DS: ES: CR0:
80050033
Mar 16 18:39:24 Server kernel: [606320.517767] CR2: 0040 CR3:
79d4a006 CR4: 003606e0
Mar 16 18:39:24 Server kernel: [606320.517768] Call Trace:
Mar 16 18:39:24 Server kernel: [606320.517910] i915_active_ref+0x21/0x210 [i915]
Mar 16 18:39:24 Server kernel: [606320.518049] ? intel_fbc_deactivate+0x38/0x60
[i915]
Mar 16 18:39:24 Server kernel: [606320.518182]
i915_vma_move_to_active+0x6e/0xf0 [i915]
Mar 16 18:39:24 Server kernel: [606320.518371]
i915_gem_do_execbuffer+0xc62/0x1520 [i915]
Mar 16 18:39:24 Server kernel: [606320.518404] ? _cond_resched+0x15/0x30
Mar 16 18:39:24 Server kernel: [606320.518416] ? mutex_lock+0xe/0x30
Mar 16 18:39:24 Server kernel: [606320.518439] ?
unix_stream_read_generic+0x1f7/0x8f0
Mar 16 18:39:24 Server kernel: [606320.518456] ? __kmalloc_node+0x1f5/0x300
Mar 16 18:39:24 Server kernel: [606320.518636]
i915_gem_execbuffer2_ioctl+0x1df/0x3d0 [i915]
Mar 16 18:39:24 Server kernel: [606320.518764] ?
i915_gem_madvise_ioctl+0x13a/0x290 [i915]
Mar 16 18:39:24 Server kernel: [606320.518874] ?
i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
Mar 16 18:39:24 Server kernel: [606320.518904] drm_ioctl_kernel+0xaa/0xf0 [drm]
Mar 16 18:39:24 Server kernel: [606320.518912] drm_ioctl+0x208/0x390 [drm]
Mar 16 18:39:24 Server kernel: [606320.518936] ?
i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
Mar 16 18:39:24 Server kernel: [606320.518941] do_vfs_ioctl+0x40e/0x670
Mar 16 18:39:24 Server kernel: [606320.518944] ksys_ioctl+0x5e/0x90
Mar 16 18:39:24 Server kernel: [606320.518945] __x64_sys_ioctl+0x16/0x20
Mar 16 18:39:24 Server kernel: [606320.518947] do_syscall_64+0x52/0x160
Mar 16 18:39:24 Server kernel: [606320.518950]
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 16 18:39:24 Server kernel: [606320.518953] RIP: 0033:0x7f5f2a7dd497
Mar 16 18:39:24 Server kernel: [606320.518955] Code: 00 00 90 48 8b 05 f9 79 0c
00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1>
Mar 16 18:39:24 Server kernel: [606320.518956] RSP: 002b:7ffc4b8c1ef8
EFLAGS: 0246 ORIG_RAX: 0010
Mar 16 18:39:24 Server kernel: [606320.5
Bug#949815: linux-image-4.19.0: lost hotplug functionality in promise 300 TX4 (product: PDC40718)
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: normal
File: linux-image-4.19.0
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Using hardware promise 300 TX4
lshw output:
*-storage
description: Mass storage controller
product: PDC40718 (SATA 300 TX4)
vendor: Promise Technology, Inc.
physical id: 3
bus info: pci@:03:03.0
logical name: scsi2
logical name: scsi3
logical name: scsi4
version: 02
width: 32 bits
clock: 66MHz
capabilities: storage pm bus_master cap_list rom emulated
configuration: driver=sata_promise latency=72 maxlatency=18
mingnt=4
This Sata hba usually provided good hot plug functionality to SATA drives.
Booting kernels in Debian Buster all show the error.
It seems, that all kernels are concerned. At least the default
kernel (linux-image-4.19.0) in 32 and 64 bit and the backport
kernel in 32 bit(5.3.0-0.bpo.2-686) have been tested explicitly.
* What exactly did you do (or not do) that was effective (or
ineffective)?
logs when plugging a Drive in:
5.3.0-0.bpo.2-686 hotplug no:
Jan 11 23:06:25 host1 kernel: [ 82.677497] ata1: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Jan 11 23:06:25 host1 kernel: [ 82.680204] ata1.00: ATA-8:
ST500DM002-1BD142, KC65, max UDMA/100
Jan 11 23:06:25 host1 kernel: [ 82.680206] ata1.00: 976773168 sectors,
multi 0: LBA48 NCQ (depth 0/32)
Jan 11 23:06:25 host1 kernel: [ 82.685111] ata1.00: configured for
UDMA/100
linux-image-4.19.0-6-686
4.19.0-6-686 hotplug no:
Jan 11 18:47:25 host1 kernel: [ 76.418588] ata4: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Jan 11 18:47:25 host1 kernel: [ 76.421293] ata4.00: ATA-8:
ST500DM002-1BD142, KC65, max UDMA/100
Jan 11 18:47:25 host1 kernel: [ 76.421295] ata4.00: 976773168 sectors,
multi 0: LBA48 NCQ (depth 0/32)
Jan 11 18:47:25 host1 kernel: [ 76.426194] ata4.00: configured for
UDMA/100
* What was the outcome of this action?
All Drives I plugged in did not show up. e.g. by using
fdisk -l
Only when I plug in the drive(s) before booting, they show up.
* What outcome did you expect instead?
Usually drives show up a few seconds after pugging in. (fdisk -l)
and are usable. It works with all kernels in stretch and before.
This results in being forced to use the old stretch kernel
4.9.0-11 in all those buster-boxes. For this functionality the
kernel module "sata_promise" is loaded.
I also tested the hardware in a arch-box with kernel 5.4.13-arch1.
This did show the expected behaviour in showing up the drives in
fdisk immediatetly.
Example of log output of a successfull operation in with a
"stretch"-kernel:
4.9.0-11-686 hotplug ok:
32bit:
Jan 11 18:44:09 host1 kernel: [ 2190.584410] ata4: exception Emask 0x10
SAct 0x0 SErr 0x401 action 0xe frozen
Jan 11 18:44:09 host1 kernel: [ 2190.584415] ata4: hotplug_status 0x20
Jan 11 18:44:09 host1 kernel: [ 2190.584419] ata4: SError: { PHYRdyChg
DevExch }
Jan 11 18:44:09 host1 kernel: [ 2190.584429] ata4: hard resetting link
Jan 11 18:44:10 host1 kernel: [ 2191.460040] ata4: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Jan 11 18:44:10 host1 kernel: [ 2191.462745] ata4.00: ATA-8:
ST500DM002-1BD142, KC65, max UDMA/100
Jan 11 18:44:10 host1 kernel: [ 2191.462748] ata4.00: 976773168 sectors,
multi 0: LBA48 NCQ (depth 0/32)
Jan 11 18:44:10 host1 kernel: [ 2191.467648] ata4.00: configured for
UDMA/100
Jan 11 18:44:10 host1 kernel: [ 2191.467653] ata4: EH complete
Jan 11 18:44:10 host1 kernel: [ 2191.467810] scsi 3:0:0:0: Direct-Access
ATA ST500DM002-1BD14 KC65 PQ: 0 ANSI: 5
Jan 11 18:44:10 host1 kernel: [ 2191.496298] sd 3:0:0:0: [sdg] 976773168
512-byte logical blocks: (500 GB/466 GiB)
Jan 11 18:44:10 host1 kernel: [ 2191.496301] sd 3:0:0:0: [sdg] 4096-byte
physical blocks
Jan 11 18:44:10 host1 kernel: [ 2191.496359] sd 3:0:0:0: [sdg] Write
Protect is off
Jan 11 18:44:10 host1 kernel: [ 2191.496363] sd 3:0:0:0: [sdg] Mode Sense:
00 3a 00 00
Jan 11 18:44:10 host1 kernel: [ 2191.496389] sd 3:0:0:0: [sdg] Write
cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 11 18:44:10 host1 kernel: [ 2191.497218] sd 3:0:0:0: Attached scsi
generic sg6 type 0
Jan 11 18:44:10 host1 kernel: [ 2191.510407] sd 3:0:0:0: [sdg] Attached
SCSI disk
64bit:
Jan 11 19:06:14 localhost kernel: [ 189.709292] ata4: exception Emask
0x10 SAct 0x0 SErr 0x401 action 0xe frozen
Jan 11 19:06:14 localhost kernel: [ 189.709305] ata4
Bug#939697: Kernel regression with b44 and kernels 5.x?
After doing some research online, I was able to find people experiencing the same issues across other distros with the very same NIC on 5.x kernels: https://bugzilla.redhat.com/show_bug.cgi?id=1709671 (Fedora) https://bbs.archlinux.org/viewtopic.php?pid=1844324#p1844324 (Arch) Playing with the swiotlb kernel parameter is of no help - tried with 256, 512, and 4096, but with those I get a null pointer dereference, no wired networking at all, and a system that can only be rebooted through the Magic SysRq key sequence. With swiotlb=force I get "can't perform DMA" errors instead. Apparently this is the offending kernel commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/kernel/dma/direct.c?h=v5.2.13&id=55897af63091ebc2c3f239c6af748113ac50 ...which was merged sometime after 4.19 kernels, and it impacts the entire 5.x line. That commit introduced the swiotlb stuff on direct DMA transactions to simplify some stuff), and judging by the stackdumps on the affected systems, rolling it back should be enough to fix this issue. As I've said, kernels prior to it (which includes the 4.19 series used on Stable) are unaffected. Some users might blame the following commit on b44: https://github.com/torvalds/linux/commit/0f0ed8282e5bfdc87cdd562e58f3d90d893e7ee5#diff-5ab1294594ceb973d7ba266e32b767ea ...but it seems irrelevant IMO, despite being the sole actual change on the b44 driver source merged this year. But then, I'm no kernel hacker. Surprisingly, b44 and swiotlb do have some background of not playing nice: https://groups.google.com/forum/#!topic/linux.kernel/GEx80ZCue1o These wired Broadcom NICs are present on most 2005~2008-era Dell laptops (most notably the Inspiron 6400/E1505/640m series, which are Core/Core 2 builds still being widely used, over a decade after its introduction), some Dell Optiplex desktops, and some HP computers (IIRC the Compaq nx6110 laptop also has a BCM4401 wired NIC). This bug not only breaks wired networking, it can also completely cripple networking support on said systems causing NetworkManager to fail or hang, blocking you from using any alternative NIC (be it wired or wireless, no matter the chipset) on said computers.
Bug#939697: "b44: swiotlb buffer is full" kernel log spam on Dell Inspiron 6400 wired NIC with kernel 5.2
Package: src:linux Version: 5.2.9-2~bpo10+1 Severity: normal Recently I checked out the latest kernel packages from Backports for my Dell Inspiron 6400 laptop, which ships with the following Broadcom wired NIC: 03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM4401-B0 100Base- TX (rev 02) I've never had problems with this NIC, been using it with kernels as old as 2.6.9. It works just fine with the default Debian Stable kernel (which is 4.19 on Buster). But with 5.2, I get my kernel log spammed with this every time there is network traffic on the wired NIC (I don't use wireless on this system): [ 67.862996] swiotlb_tbl_map_single: 20 callbacks suppressed [ 67.863001] b44 :03:00.0: swiotlb buffer is full (sz: 233 bytes), total 0 (slots), used 0 (slots) [ 67.863101] b44 :03:00.0: swiotlb buffer is full (sz: 213 bytes), total 0 (slots), used 0 (slots) [ 68.114649] b44 :03:00.0: swiotlb buffer is full (sz: 233 bytes), total 0 (slots), used 0 (slots) [ 68.114767] b44 :03:00.0: swiotlb buffer is full (sz: 213 bytes), total 0 (slots), used 0 (slots) [ 68.274933] b44 :03:00.0: swiotlb buffer is full (sz: 65 bytes), total 0 (slots), used 0 (slots) [ 68.366103] b44 :03:00.0: swiotlb buffer is full (sz: 324 bytes), total 0 (slots), used 0 (slots) [ 68.366261] b44 :03:00.0: swiotlb buffer is full (sz: 328 bytes), total 0 (slots), used 0 (slots) [ 69.390771] b44 :03:00.0: swiotlb buffer is full (sz: 324 bytes), total 0 (slots), used 0 (slots) [ 69.390953] b44 :03:00.0: swiotlb buffer is full (sz: 328 bytes), total 0 (slots), used 0 (slots) [ 70.682433] b44 :03:00.0: swiotlb buffer is full (sz: 93 bytes), total 0 (slots), used 0 (slots) I even get a stacktrace during boot (most likely during DHCP negotiation?) [ 51.467502] swiotlb_tbl_map_single: 2 callbacks suppressed [ 51.467507] b44 :03:00.0: swiotlb buffer is full (sz: 1566 bytes), total 0 (slots), used 0 (slots) [ 51.467526] WARNING: CPU: 1 PID: 552 at kernel/dma/direct.c:43 report_addr+0x33/0x60 [ 51.467527] Modules linked in: bnep binfmt_misc fuse btusb btrtl btbcm btintel bluetooth arc4 rt2800pci rt2800mmio drbg rt2800lib rt2x00pci ansi_cprng rt2x00mmio ecdh_generic rt2x00lib ecc mac80211 snd_hda_codec_hdmi cfg80211 snd_hda_codec_idt snd_hda_codec_generic eeprom_93cx6 r852 crc_ccitt sm_common nand snd_hda_intel pktcdvd snd_hda_codec nand_ecc bch nandcore snd_hda_core mtd snd_hwdep snd_pcm_oss dell_laptop r592 ledtrig_audio coretemp snd_mixer_oss rfkill memstick iTCO_wdt kvm_intel iTCO_vendor_support snd_pcm kvm watchdog irqbypass sg dell_wmi pcc_cpufreq snd_timer dell_smbios snd dcdbas acpi_cpufreq soundcore rng_core evdev joydev sparse_keymap dell_wmi_descriptor wmi_bmof pcspkr serio_raw battery ac uinput vhba(OE) nfsd dell_smm_hwmon auth_rpcgss loop nfs_acl lockd parport_pc ppdev grace lp sunrpc parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_generic usbhid hid sr_mod cdrom sd_mod ata_generic ata_piix libata b44 ehci_pci uhci_hcd ehci_hcd ssb [ 51.467587] scsi_mod sdhci_pci cqhci mii usbcore sdhci libphy psmouse mmc_core radeon i2c_i801 firewire_ohci firewire_core crc_itu_t pcmcia lpc_ich mfd_core pcmcia_core i2c_algo_bit ttm drm_kms_helper drm usb_common wmi button video [ 51.467609] CPU: 1 PID: 552 Comm: NetworkManager Tainted: G OE 5.2.0-0.bpo.2-amd64 #1 Debian 5.2.9-2~bpo10+1 [ 51.467611] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 [ 51.467614] RIP: 0010:report_addr+0x33/0x60 [ 51.467617] Code: 48 8b 87 28 02 00 00 48 89 34 24 48 85 c0 74 2d 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 14 80 3d cf 03 02 01 00 0f 84 59 05 00 00 <0f> 0b 48 83 c4 08 c3 48 83 bf 38 02 00 00 00 74 ef eb e0 80 3d b0 [ 51.467620] RSP: 0018:b3208112f518 EFLAGS: 00010246 [ 51.467622] RAX: fffe RBX: 9e10fbb2e0b0 RCX: [ 51.467624] RDX: 061e RSI: b8497880 RDI: 9e10fbb2e0b0 [ 51.467626] RBP: 061e R08: 3fff R09: 0069 [ 51.467628] R10: R11: b3208112f1d0 R12: [ 51.467630] R13: R14: 9e10743f28c0 R15: 9e10746e7a00 [ 51.467633] FS: 7fb32de70b80() GS:9e10fc90() knlGS: [ 51.467635] CS: 0010 DS: ES: CR0: 80050033 [ 51.467637] CR2: 55b08e607928 CR3: b5e42000 CR4: 06e0 [ 51.467639] Call Trace: [ 51.467647] dma_direct_map_page+0xd6/0xf0 [ 51.467654] b44_alloc_rx_skb+0x279/0x3d0 [b44] [ 51.467659] b44_init_rings+0xad/0x180 [b44] [ 51.467662] b44_open+0xf7/0x3e0 [b44] [ 51.467667] __dev_open+0xcd/0x160 [ 51.467670] __dev_change_flags+0x1ad/0x220 [ 51.467673] dev_change_flags+0x21/0x60 [ 51.467677] do_setlink+0x322/0xe90 [ 51.467697] ? ata_bmdma_qc_issue+0x7e/0x120 [libata] [ 51.467708] ? ata_qc_issue+0x103/0x240 [libata] [ 51.467712] ? cpumask_next+0x16/0x20 [ 51.
Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?
I can absolutely confirm this fishy behaviour on 2 VMWare guests. (VMware ESXi, 6.5.0, 8294253, vSphere Client version 6.7.0) Also ssh copy was not possible to a host running linux-image-3.16.0-8-amd64 No problems with linux-image-3.16.0-7-amd64. Very fishy.
Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load
Hi Romain Hardly, as this system is now in production as a build server, running a bpo kernel. Linux 4.16.0-0.bpo.1-amd64 #1 SMP Debian 4.16.5-1~bpo9+1 (2018-05-06) x86_64 GNU/Linux Best regards Tom -Original Message- From: Romain Perier [mailto:romain.per...@gmail.com] Sent: Mittwoch, 29. August 2018 19:55 To: 883...@bugs.debian.org Subject: Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load Hi, The last linux kernel in stretch being 4.9.110, could you re-test with this kernel please ? Thanks, Regards, Romain On Thu, Nov 30, 2017 at 11:54:00AM +, Tom Stocker wrote: > Package: src:linux > Version: 4.9.51-1 > Severity: serious > Justification: Policy 2.2.1 > > > > -- Package-specific info: > ** Version: > Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version > 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) > > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 > root=/dev/mapper/de--bln--vm--017--vg-root ro quiet > > ** Not tainted > > ** Kernel log: > [1.533757] EXT4-fs (dm-1): mounted filesystem with ordered data mode. > Opts: (null) > [1.847797] ip_tables: (C) 2000-2006 Netfilter Core Team > [1.912833] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT > +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS > +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) > [1.912859] systemd[1]: Detected virtualization vmware. > [1.912863] systemd[1]: Detected architecture x86-64. > [1.914546] systemd[1]: Set hostname to . > [2.058639] random: crng init done > [2.131752] systemd[1]: Set up automount Arbitrary Executable File Formats > File System Automount Point. > [2.131812] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. > [2.131843] systemd[1]: Listening on Syslog Socket. > [2.131885] systemd[1]: Started Forward Password Requests to Wall > Directory Watch. > [2.131920] systemd[1]: Listening on udev Control Socket. > [2.131955] systemd[1]: Started Dispatch Password Requests to Console > Directory Watch. > [2.363268] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro > [2.516531] systemd-journald[833]: Received request to flush runtime > journal from PID 1 > [2.819683] input: Power Button as > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 > [2.819691] ACPI: Power Button [PWRF] > [2.819819] ACPI: AC Adapter [ACAD] (on-line) > [2.875315] input: PC Speaker as /devices/platform/pcspkr/input/input5 > [2.881700] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 > [2.881767] vmw_vmci :00:07.7: Using capabilities 0xc > [2.882410] Guest personality initialized and is active > [2.882410] VMCI host device registered (name=vmci, major=10, minor=58) > [2.882410] Initialized host personality > [2.930410] [drm] Initialized > [2.941291] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [2.941374] sd 0:0:1:0: Attached scsi generic sg1 type 0 > [2.941446] sd 0:0:2:0: Attached scsi generic sg2 type 0 > [2.941516] sd 0:0:3:0: Attached scsi generic sg3 type 0 > [2.941562] sr 2:0:0:0: Attached scsi generic sg4 type 5 > [3.012775] [drm] DMA map mode: Using physical TTM page addresses. > [3.012868] [drm] Capabilities: > [3.012873] [drm] Rect copy. > [3.012874] [drm] Cursor. > [3.012875] [drm] Cursor bypass. > [3.012876] [drm] Cursor bypass 2. > [3.012877] [drm] 8bit emulation. > [3.012878] [drm] Alpha cursor. > [3.012879] [drm] Extended Fifo. > [3.012880] [drm] Multimon. > [3.012881] [drm] Pitchlock. > [3.012882] [drm] Irq mask. > [3.012883] [drm] Display Topology. > [3.012884] [drm] GMR. > [3.012885] [drm] Traces. > [3.012886] [drm] GMR2. > [3.012887] [drm] Screen Object 2. > [3.012888] [drm] Command Buffers. > [3.012889] [drm] Command Buffers 2. > [3.012890] [drm] Guest Backed Resources. > [3.012891] [drm] DX Features. > [3.012893] [drm] Max GMR ids is 64 > [3.012894] [drm] Max number of GMR pages is 65536 > [3.012895] [drm] Max dedicated hypervisor surface memory is 0 kiB > [3.012896] [drm] Maximum display memory size is 4096 kiB > [3.012898] [drm] VRAM at 0xe800 size is 4096 kiB > [3.012899] [drm] MMIO at 0xfe00 size is 256 kiB > [3.012901] [drm] global init. > [3.013022] [TTM] Zone kernel: Available graphics memory: 60855752 kiB > [3.013023] [TTM] Zone dma32: Available graphics memory: 2097152 kiB > [3.013024] [TTM] Initializing pool allocator > [3.013029] [TTM] Ini
Bug#902740: initramfs-tools: /etc/initramfs-tools/conf.d/resume not updated with dpkg-reconfigure initramfs-tools
Package: initramfs-tools Version: 0.130 Severity: wishlist I copied a drive from one laptop to another, using rsync and various hacks. The swap partition on the new drive has a different UUID. I had to regenerate initramfs for each kernel version, because the lappies are different type hardware, with different modules needed. When I ran update-initramfs it worked perfectly, except that it threw an informational message that it couldn't find the resume partition listed in the conf file, so it would use the swap partition it did find. I ran dpkg-reconfigure initramfs-tools to update the configs with the new swap partition UUID, but the message kept appearing. So, rather than have it keep throwing the informational message forever, I copied and pasted the UUID of swap into /etc/initramfs-tools/conf.d/resume. It works now without the message. It would be nice if the message gave the path of the config file in question, or better yet, if dpkg-reconfigure initramfs-tools would update the 'resume' config file with the new swap partition. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 18M Feb 27 00:37 /boot/initrd.img-4.9.0-4-amd64 -rw-r--r-- 1 root root 18M May 17 21:08 /boot/initrd.img-4.9.0-6-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.9.0-6-amd64 root=UUID=a28a1d13-49b8-4f25-b310-d1d17e69cec9 ro quiet -- resume RESUME=UUID=31fe945f-b629-425b-91dd-e08260816714 -- /proc/filesystems ext3 ext2 ext4 xfs fuseblk vfat -- lsmod Module Size Used by tun28672 0 nls_ascii 16384 0 nls_cp437 20480 0 vfat 20480 0 fat69632 1 vfat fuse 98304 3 ftdi_sio 53248 0 usbserial 49152 1 ftdi_sio pci_stub 16384 1 vboxpci24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 466944 3 vboxnetadp,vboxnetflt,vboxpci xfs 1224704 2 libcrc32c 16384 1 xfs usblp 20480 0 uas24576 0 usb_storage73728 3 uas hid_generic16384 0 usbhid 53248 0 hid 122880 2 hid_generic,usbhid intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 asus_nb_wmi28672 0 asus_wmi 28672 1 asus_nb_wmi sparse_keymap 16384 1 asus_wmi rfkill 24576 3 asus_wmi kvm_intel 192512 0 kvm 593920 1 kvm_intel snd_hda_codec_hdmi 49152 1 iTCO_wdt 16384 0 irqbypass 16384 1 kvm iTCO_vendor_support16384 1 iTCO_wdt crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 snd_hda_codec_realtek90112 1 ghash_clmulni_intel16384 0 snd_hda_codec_generic69632 1 snd_hda_codec_realtek nouveau 1556480 1 i915 1257472 17 intel_cstate 16384 0 snd_hda_intel 36864 6 mxm_wmi16384 1 nouveau intel_uncore 118784 0 snd_hda_codec 135168 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek ttm98304 1 nouveau evdev 24576 19 joydev 20480 0 intel_rapl_perf16384 0 snd_hda_core 86016 5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek drm_kms_helper155648 2 nouveau,i915 serio_raw 16384 0 pcspkr 16384 0 snd_hwdep 16384 1 snd_hda_codec mei_me 36864 0 snd_pcm 110592 4 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi drm 360448 12 nouveau,i915,ttm,drm_kms_helper snd_timer 32768 1 snd_pcm mei 102400 1 mei_me sg 32768 0 snd86016 20 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm i2c_algo_bit 16384 2 nouveau,i915 soundcore 16384 1 snd lpc_ich24576 0 shpchp 36864 0 mfd_core 16384 1 lpc_ich wmi16384 3 asus_wmi,mxm_wmi,nouveau battery20480 0 ac 16384 0 video 40960 3 asus_wmi,nouveau,i915 button 16384 2 nouveau,i915 coretemp 16384 0 parport_pc 28672 0 ppdev 20480 0 lp 20480 0 parport49152 3 lp,parport_pc,ppdev ip_tables 24576 0 x_tables 36864 1 ip_tables autofs440960 2 ext4 585728 5 crc16 16384 1 ext4 jbd2 106496 1 ext4 crc32c_generic 16384 0 fscrypto 28
Bug#887592: linux: 4.9.65-3 FTBFS on sparc64: arch/sparc/lib/multi3.S missing patch
Source: linux Version: 4.9.65-3 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) linux 4.9.65-3 (Stretch 9.3), as well as 4.9.51-1 and 4.9.47-1 FTBFS on sparc64: /build/linux-4.9.65/arch/sparc/lib/multi3.S:2:24: fatal error: asm/export.h: No such file or directory #include ^ compilation terminated. /build/linux-4.9.65/scripts/Makefile.build:398: recipe for target 'arch/sparc/lib/multi3.o' failed It seems commit 1b4af13ff2cc "sparc64: Add __multi3 for gcc 7.x and later." was backported to 4.9 in 4.9.32 (commit 4b684e6474d0), but /debian/patches/bugfix/sparc/revert-sparc-move-exports-to-definitions.patch doesn't patch /arch/sparc/lib/multi3.S. Applying the following patch, taken from linux 4.11.11-1's revert-sparc-move-exports-to-definitions.patch allows the build to succeed on sparc64 for linux 4.9.65-3, as well as 4.9.51-1 and 4.9.47-1: --- a/arch/sparc/lib/multi3.S +++ b/arch/sparc/lib/multi3.S @@ -1,5 +1,4 @@ #include -#include .text .align 4 @@ -32,4 +31,3 @@ ENTRY(__multi3) /* %o0 = u, %o1 = v */ retl add%g1, %o0, %o0 ENDPROC(__multi3) -EXPORT_SYMBOL(__multi3) Would it be possible to include this patch in future linux 4.9.x packages? Thanks! Best regards, Tom Turelinckx -- System Information: Debian Release: 9.0 Architecture: sparc64 Kernel: Linux 4.9.0-3-sparc64-smp (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load
Package: src:linux Version: 4.9.51-1 Severity: serious Justification: Policy 2.2.1 -- Package-specific info: ** Version: Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/de--bln--vm--017--vg-root ro quiet ** Not tainted ** Kernel log: [1.533757] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [1.847797] ip_tables: (C) 2000-2006 Netfilter Core Team [1.912833] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [1.912859] systemd[1]: Detected virtualization vmware. [1.912863] systemd[1]: Detected architecture x86-64. [1.914546] systemd[1]: Set hostname to . [2.058639] random: crng init done [2.131752] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [2.131812] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [2.131843] systemd[1]: Listening on Syslog Socket. [2.131885] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [2.131920] systemd[1]: Listening on udev Control Socket. [2.131955] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [2.363268] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [2.516531] systemd-journald[833]: Received request to flush runtime journal from PID 1 [2.819683] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [2.819691] ACPI: Power Button [PWRF] [2.819819] ACPI: AC Adapter [ACAD] (on-line) [2.875315] input: PC Speaker as /devices/platform/pcspkr/input/input5 [2.881700] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 [2.881767] vmw_vmci :00:07.7: Using capabilities 0xc [2.882410] Guest personality initialized and is active [2.882410] VMCI host device registered (name=vmci, major=10, minor=58) [2.882410] Initialized host personality [2.930410] [drm] Initialized [2.941291] sd 0:0:0:0: Attached scsi generic sg0 type 0 [2.941374] sd 0:0:1:0: Attached scsi generic sg1 type 0 [2.941446] sd 0:0:2:0: Attached scsi generic sg2 type 0 [2.941516] sd 0:0:3:0: Attached scsi generic sg3 type 0 [2.941562] sr 2:0:0:0: Attached scsi generic sg4 type 5 [3.012775] [drm] DMA map mode: Using physical TTM page addresses. [3.012868] [drm] Capabilities: [3.012873] [drm] Rect copy. [3.012874] [drm] Cursor. [3.012875] [drm] Cursor bypass. [3.012876] [drm] Cursor bypass 2. [3.012877] [drm] 8bit emulation. [3.012878] [drm] Alpha cursor. [3.012879] [drm] Extended Fifo. [3.012880] [drm] Multimon. [3.012881] [drm] Pitchlock. [3.012882] [drm] Irq mask. [3.012883] [drm] Display Topology. [3.012884] [drm] GMR. [3.012885] [drm] Traces. [3.012886] [drm] GMR2. [3.012887] [drm] Screen Object 2. [3.012888] [drm] Command Buffers. [3.012889] [drm] Command Buffers 2. [3.012890] [drm] Guest Backed Resources. [3.012891] [drm] DX Features. [3.012893] [drm] Max GMR ids is 64 [3.012894] [drm] Max number of GMR pages is 65536 [3.012895] [drm] Max dedicated hypervisor surface memory is 0 kiB [3.012896] [drm] Maximum display memory size is 4096 kiB [3.012898] [drm] VRAM at 0xe800 size is 4096 kiB [3.012899] [drm] MMIO at 0xfe00 size is 256 kiB [3.012901] [drm] global init. [3.013022] [TTM] Zone kernel: Available graphics memory: 60855752 kiB [3.013023] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [3.013024] [TTM] Initializing pool allocator [3.013029] [TTM] Initializing DMA pool allocator [3.013122] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.013127] [drm] No driver support for vblank timestamp query. [3.013382] [drm] Screen Target Display device initialized [3.013441] [drm] width 640 [3.013453] [drm] height 480 [3.013465] [drm] bpp 32 [3.014570] [drm] Fifo max 0x0004 min 0x1000 cap 0x077f [3.015450] [drm] Using command buffers with DMA pool. [3.015460] [drm] DX: no. [3.015695] fbcon: svgadrmfb (fb0) is primary device [3.017598] Console: switching to colour frame buffer device 100x37 [3.096662] ppdev: user-space parallel port driver [3.112337] [drm] Initialized vmwgfx 2.12.0 20170221 for :00:0f.0 on minor 0 [3.194699] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 10737418240 ms ovfl timer [3.194702] RAPL PMU: hw unit of domain pp0-core 2^-0 Joules [3.194703] RAPL PMU: hw unit of domain package 2^-0 Joules [3.194704] RAPL PMU: hw unit of domain dram 2^-16 Joules [3.235157] shpchp: Standard Hot Plug PCI Controller Driver version:
Bug#843349: linux-image-4.7.0-1-amd64: Intermittently high system load, sluggish response, no /proc//stat utime,stime,etc. reported
Alrighty, having read through the other responses I'm inclined to agree something's not playing nice with certain hardware: I think that the difference is more likely to be in the configuration, > rather than the patches we apply. > > As in the kernel config? I guess that's possible. I think I built my "good" vanilla 4.9 kernel using the debian 4.6 config. Perhaps in addition the booting-from-power-off, maybe worth my time to try another vanilla 4.9 build using the debian 4.9 config to see if things get miserable again. On Thu, Jan 26, 2017 at 6:10 PM, Tom Lee wrote: > Oops, somehow missed those follow-ups. Thanks, I'll catch up. > > Have you tried booting one of the newer kernel versions from power-off? > > > I'll be sure to give that a go, thanks. > > > On Thu, Jan 26, 2017 at 5:54 PM, Ben Hutchings > wrote: > >> On Wed, 2017-01-25 at 17:52 -0800, Tom Lee wrote: >> > Just an update: I am still encountering similar performance issues with >> the >> > 4.9.0-1 kernel that was recently promoted to testing. In fact, the >> 4.9.0-1 >> > kernel may be the worst yet in terms of this specific issue, with >> IntelliJ >> > starting so slowly as to be effectively unusable. One time the entire >> > system appeared to become completely unresponsive & a hard reset was >> > required. >> > >> > The most recent kernel with which I've experienced problems: >> > >> > $ apt-cache show linux-image-4.9.0-1-amd64 >> > Package: linux-image-4.9.0-1-amd64 >> > Source: linux-signed (4) >> > Version: 4.9.2-2 >> > Installed-Size: 183299 >> > >> > This problem does *not* seem to occur with a vanilla 4.9.2 kernel, >> implying >> > something Debian-specific: >> > >> > $ uname -a >> > Linux desktop.local 4.9.2 #1 SMP Wed Jan 25 04:28:29 PST 2017 x86_64 >> > GNU/Linux >> > >> > If you're aware of any Debian patches that might be suspect, I'm happy >> to >> > try some custom builds. Reproducing the issue is trivial on my end when >> a >> > kernel is "bad". >> [...] >> >> I think that the difference is more likely to be in the configuration, >> rather than the patches we apply. >> >> Some other people followed up to your bug report suggesting there might >> be a BIOS bug affecting behaviour after a warm reboot, but not booting >> from power-off: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843349#17 >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843349#32 >> >> (Unfortunately I don't see any BIOS updates available for this model.) >> Have you tried booting one of the newer kernel versions from power-off? >> >> Ben. >> >> -- >> Ben Hutchings >> Design a system any fool can use, and only a fool will want to use it. >> > > > > -- > *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee> > > -- *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
Bug#843349: linux-image-4.7.0-1-amd64: Intermittently high system load, sluggish response, no /proc//stat utime,stime,etc. reported
Oops, somehow missed those follow-ups. Thanks, I'll catch up. Have you tried booting one of the newer kernel versions from power-off? I'll be sure to give that a go, thanks. On Thu, Jan 26, 2017 at 5:54 PM, Ben Hutchings wrote: > On Wed, 2017-01-25 at 17:52 -0800, Tom Lee wrote: > > Just an update: I am still encountering similar performance issues with > the > > 4.9.0-1 kernel that was recently promoted to testing. In fact, the > 4.9.0-1 > > kernel may be the worst yet in terms of this specific issue, with > IntelliJ > > starting so slowly as to be effectively unusable. One time the entire > > system appeared to become completely unresponsive & a hard reset was > > required. > > > > The most recent kernel with which I've experienced problems: > > > > $ apt-cache show linux-image-4.9.0-1-amd64 > > Package: linux-image-4.9.0-1-amd64 > > Source: linux-signed (4) > > Version: 4.9.2-2 > > Installed-Size: 183299 > > > > This problem does *not* seem to occur with a vanilla 4.9.2 kernel, > implying > > something Debian-specific: > > > > $ uname -a > > Linux desktop.local 4.9.2 #1 SMP Wed Jan 25 04:28:29 PST 2017 x86_64 > > GNU/Linux > > > > If you're aware of any Debian patches that might be suspect, I'm happy to > > try some custom builds. Reproducing the issue is trivial on my end when a > > kernel is "bad". > [...] > > I think that the difference is more likely to be in the configuration, > rather than the patches we apply. > > Some other people followed up to your bug report suggesting there might > be a BIOS bug affecting behaviour after a warm reboot, but not booting > from power-off: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843349#17 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843349#32 > > (Unfortunately I don't see any BIOS updates available for this model.) > Have you tried booting one of the newer kernel versions from power-off? > > Ben. > > -- > Ben Hutchings > Design a system any fool can use, and only a fool will want to use it. > -- *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
Bug#843349: linux-image-4.7.0-1-amd64: Intermittently high system load, sluggish response, no /proc//stat utime,stime,etc. reported
Just an update: I am still encountering similar performance issues with the
4.9.0-1 kernel that was recently promoted to testing. In fact, the 4.9.0-1
kernel may be the worst yet in terms of this specific issue, with IntelliJ
starting so slowly as to be effectively unusable. One time the entire
system appeared to become completely unresponsive & a hard reset was
required.
The most recent kernel with which I've experienced problems:
$ apt-cache show linux-image-4.9.0-1-amd64
Package: linux-image-4.9.0-1-amd64
Source: linux-signed (4)
Version: 4.9.2-2
Installed-Size: 183299
This problem does *not* seem to occur with a vanilla 4.9.2 kernel, implying
something Debian-specific:
$ uname -a
Linux desktop.local 4.9.2 #1 SMP Wed Jan 25 04:28:29 PST 2017 x86_64
GNU/Linux
If you're aware of any Debian patches that might be suspect, I'm happy to
try some custom builds. Reproducing the issue is trivial on my end when a
kernel is "bad".
On Sun, Nov 20, 2016 at 2:24 PM, Tom Lee wrote:
> Also potentially relevant: kworker/0:0 has 421h on-cpu time reported per
> htop (the TIME+ column) and top. /proc//stat output for PID=4
> (kworker/0:0) vs PID=63 (kworker/1:1):
>
> tom@desktop ~ $ cat /proc/63/stat
> 63 (kworker/1:1) S 2 0 0 0 -1 69238880 0 0 0 0 0 0 0 0 20 0 1 0 82 0 0
> 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 0 0 0 17 1 0 0 184 0 0 0 0
> 0 0 0 0 0 0
> tom@desktop ~ $ cat /proc/4/stat
> 4 (kworker/0:0) S 2 0 0 0 -1 69238880 0 0 0 0 151836336 0 0 0 20 0 1 0 10
> 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 0 0 0 17 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0
>
> In fact, kworker:0:0 seems to be the only process with on-cpu stats
> reported (forgive the shell abuse, quick and dirty):
>
> $ for pid in $(ls /proc | awk '/^[0-9]*$/'); do [ -d /proc/$pid ] && awk
> '$14 != "0" { print $2 }' /proc/$pid/stat; done
> (kworker/0:0)
> $
>
>
> On Sun, Nov 20, 2016 at 2:12 PM, Tom Lee wrote:
>
>> Tried 4.8.0-1 with similar results. Perhaps slightly better, but not much.
>>
>> $ uname -a
>> Linux desktop 4.8.0-1-amd64 #1 SMP Debian 4.8.5-1 (2016-10-28) x86_64
>> GNU/Linux
>>
>> Like 4.7, can't see what's hogging the CPUs as per-process CPU stats
>> don't appear to be correctly reported in /proc//stat.
>>
>> 4.6.x continues to be perfect with respect to both overall performance
>> and the correctness of /proc//stat.
>>
>>
>> On Sat, Nov 12, 2016 at 8:23 PM, Ben Hutchings
>> wrote:
>>
>>> Control: tag -1 moreinfo
>>>
>>> On Sun, 2016-11-06 at 00:02 -0700, Tom Lee wrote:
>>> [...]
>>> > Downgrading to linux-image-4.6.0-1-amd64 fixed all symptoms. Haven't
>>> yet
>>> > tried 4.8.0-1 from unstable, not sure if it's impacted.
>>> [...]
>>>
>>> Please do.
>>>
>>> Ben.
>>>
>>> --
>>> Ben Hutchings
>>> Nothing is ever a complete failure; it can always serve as a bad
>>> example.
>>>
>>>
>>
>>
>> --
>> *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
>>
>>
>
>
> --
> *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
>
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
Bug#847681: 847681
On Tue, 13 Dec 2016 22:09:07 +0100 Andreas Henriksson wrote: > On Tue, Dec 13, 2016 at 09:52:10PM +0100, Daniel Pocock wrote: >> Even if you are not sure, simply spending 10 - 15 minutes hunting for >> an example in another project and adding the links to the bug report >> can give another developer a head-start when they are ready to work on >> the bug. We are a community project and every contribution, no matter >> how small, can be helpful. > > I would suggest tagging these both as wontfix. Adding even more options > to the broken concept of /etc/default just adds to the maintenance burden > of having to carry this over via the nfs-utils_env.sh bridge. "/etc/default/" isn't broken. It is/was broken _in_Debian_for_certain_packages_ because a service can/could be disabled with a variable there. It's a legitimate and useful way to customize daemon startup. > Both /etc/default/nfs-kernel-server and the init script are conffiles. > Edit them directly as you see fit to suite your installation if you're > still using this old stuff. They will not be overwritten on upgrades. > > On systemd there's a better concept of overriding settings so you don't > need to (and should avoid to) deal with /etc/default anymore. NFS has so many settings and so many sysvrc/systemd startup files that editing them or creating overrides/drop-ins is a PitA. Especially since an admin can check with root@localhost ~ # egrep -v '^#|^$|NEED' /etc/default/nfs-* /etc/default/nfs-common:STATDOPTS="--port 32765 --outgoing-port 32766" /etc/default/nfs-kernel-server:RPCNFSDCOUNT="8 --no-nfs-version 2 --no-nfs-version 3" /etc/default/nfs-kernel-server:RPCNFSDPRIORITY=0 /etc/default/nfs-kernel-server:RPCMOUNTDOPTS="--manage-gids --no-nfs-version 2 --no-nfs-version 3 --port 32767" /etc/default/nfs-kernel-server:RPCSVCGSSDOPTS="-v -k /root/test.keytab -p /run/rpc_pipefs" root@localhost ~ # what's being passed to the nfs units. The url below is the nfs upstream systemd units http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=tree;f=systemd;hb=HEAD where steved is Steve Dickson, an RH developer who's a systemd happy camper. If upstream and RHEL are happy to use "/etc/sysconfig/" (the RH "/etc/default/"), I don't see why Debian should be "plus royaliste que le roi" and get rid of "/etc/default/" for nfs. Ubuntu's packaged the upstream units and adapted them to the Ubuntu/Debian setup so whoever's packaging nfs for Debian might only need to copy the relevant "./debian/" files to the Debian source package.
Bug#843349: linux-image-4.7.0-1-amd64: Intermittently high system load, sluggish response, no /proc//stat utime,stime,etc. reported
Also potentially relevant: kworker/0:0 has 421h on-cpu time reported per
htop (the TIME+ column) and top. /proc//stat output for PID=4
(kworker/0:0) vs PID=63 (kworker/1:1):
tom@desktop ~ $ cat /proc/63/stat
63 (kworker/1:1) S 2 0 0 0 -1 69238880 0 0 0 0 0 0 0 0 20 0 1 0 82 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 0 0 0 17 1 0 0 184 0 0 0 0
0 0 0 0 0 0
tom@desktop ~ $ cat /proc/4/stat
4 (kworker/0:0) S 2 0 0 0 -1 69238880 0 0 0 0 151836336 0 0 0 20 0 1 0 10 0
0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 0 0 0 17 0 0 0 0 0 0 0 0
0 0 0 0 0 0
In fact, kworker:0:0 seems to be the only process with on-cpu stats
reported (forgive the shell abuse, quick and dirty):
$ for pid in $(ls /proc | awk '/^[0-9]*$/'); do [ -d /proc/$pid ] && awk
'$14 != "0" { print $2 }' /proc/$pid/stat; done
(kworker/0:0)
$
On Sun, Nov 20, 2016 at 2:12 PM, Tom Lee wrote:
> Tried 4.8.0-1 with similar results. Perhaps slightly better, but not much.
>
> $ uname -a
> Linux desktop 4.8.0-1-amd64 #1 SMP Debian 4.8.5-1 (2016-10-28) x86_64
> GNU/Linux
>
> Like 4.7, can't see what's hogging the CPUs as per-process CPU stats don't
> appear to be correctly reported in /proc//stat.
>
> 4.6.x continues to be perfect with respect to both overall performance and
> the correctness of /proc//stat.
>
>
> On Sat, Nov 12, 2016 at 8:23 PM, Ben Hutchings
> wrote:
>
>> Control: tag -1 moreinfo
>>
>> On Sun, 2016-11-06 at 00:02 -0700, Tom Lee wrote:
>> [...]
>> > Downgrading to linux-image-4.6.0-1-amd64 fixed all symptoms. Haven't yet
>> > tried 4.8.0-1 from unstable, not sure if it's impacted.
>> [...]
>>
>> Please do.
>>
>> Ben.
>>
>> --
>> Ben Hutchings
>> Nothing is ever a complete failure; it can always serve as a bad
>> example.
>>
>>
>
>
> --
> *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
>
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
Bug#843349: linux-image-4.7.0-1-amd64: Intermittently high system load, sluggish response, no /proc//stat utime,stime,etc. reported
Tried 4.8.0-1 with similar results. Perhaps slightly better, but not much. $ uname -a Linux desktop 4.8.0-1-amd64 #1 SMP Debian 4.8.5-1 (2016-10-28) x86_64 GNU/Linux Like 4.7, can't see what's hogging the CPUs as per-process CPU stats don't appear to be correctly reported in /proc//stat. 4.6.x continues to be perfect with respect to both overall performance and the correctness of /proc//stat. On Sat, Nov 12, 2016 at 8:23 PM, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Sun, 2016-11-06 at 00:02 -0700, Tom Lee wrote: > [...] > > Downgrading to linux-image-4.6.0-1-amd64 fixed all symptoms. Haven't yet > > tried 4.8.0-1 from unstable, not sure if it's impacted. > [...] > > Please do. > > Ben. > > -- > Ben Hutchings > Nothing is ever a complete failure; it can always serve as a bad > example. > > -- *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
Bug#843349: linux-image-4.7.0-1-amd64: Intermittently high system load, sluggish response, no /proc//stat utime,stime,etc. reported
Package: src:linux Version: 4.7.8-1 Severity: important Dear Maintainer, Experienced poor system-wide performance since linux-image-amd64 pulled down 4.7.0-1. Tried to investigate what was going on, only to discover that tools like top/htop were unable to report per-process CPU time (though system-wide CPU stats based on /proc/stat were still reporting fine). Further analysis shows /proc//stat CPU fields stuck at zero. The impact seems to be emphasized when a brief but moderately heavy load occurs (e.g. kicking off CMake, performing certain operations within CLion/other IDEs, etc.): in 4.6.0-1 you see a brief uptick in CPU burn in top/htop that settles quickly; with 4.7.0-1 the effect of the burst of activity seems to be emphasized -- load average drastically and quickly increases, CPU activity goes through the roof and the system becomes intermittently unresponsive. The system is ultimately usable, but feels very sluggish overall. Downgrading to linux-image-4.6.0-1-amd64 fixed all symptoms. Haven't yet tried 4.8.0-1 from unstable, not sure if it's impacted. Thank you! Tom -- Package-specific info: ** Version: Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.8-1 (2016-10-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 root=UUID=4c115ce4-a646-41dc-a1b0-7120b87bfdd9 ro quiet ** Tainted: POE (12289) * Proprietary module has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [3.995767] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.995774] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [3.995778] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.995782] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.995784] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.995789] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [3.995793] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [3.995796] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a [4.017080] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card0/input7 [4.017326] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card0/input8 [4.017626] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card0/input9 [4.017809] input: HDA Intel PCH Line Out Front as /devices/pci:00/:00:1b.0/sound/card0/input10 [4.019047] iTCO_vendor_support: vendor-support=0 [4.021209] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [4.021286] iTCO_wdt: Found a Patsburg TCO device (Version=2, TCOBASE=0x0460) [4.024186] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [4.024256] input: HDA Intel PCH Line Out Surround as /devices/pci:00/:00:1b.0/sound/card0/input11 [4.024510] input: HDA Intel PCH Line Out CLFE as /devices/pci:00/:00:1b.0/sound/card0/input12 [4.024745] input: HDA Intel PCH Line Out Side as /devices/pci:00/:00:1b.0/sound/card0/input13 [4.024899] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input14 [4.057280] hid-generic 0003:187C:0513.0001: hiddev0,hidraw0: USB HID v1.01 Device [Alienware Gaming Desktop] on usb-:00:1d.0-1.5/input0 [4.057546] input: Logitech USB Keyboard as /devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1.4/4-1.1.4.1/4-1.1.4.1:1.0/0003:046D:C31C.0002/input/input15 [4.116721] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-:00:1d.0-1.1.4.1/input0 [4.129214] input: Logitech USB Keyboard as /devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1.4/4-1.1.4.1/4-1.1.4.1:1.1/0003:046D:C31C.0003/input/input16 [4.184284] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 Device [Logitech USB Keyboard] on usb-:00:1d.0-1.1.4.1/input1 [4.184534] input: Logitech USB Keyboard as /devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1.4/4-1.1.4.1/4-1.1.4.1:1.2/0003:046D:C31C.0004/input/input17 [4.184746] hid-generic 0003:046D:C31C.0004: input,hidraw3: USB HID v1.10 Mouse [Logitech USB Keyboard] on usb-:00:1d.0-1.1.4.1/input2 [4.225123] EDAC MC: Ver: 3.0.0 [4.229203] EDAC sbridge: Seeking for: PCI ID 8086:3ca0 [4.229221] EDAC sbridge: Seeking for: PCI ID 8086:3ca0 [4.229226] EDAC sbridge: Seeking for: PCI ID 8086:3ca8 [4.229234] EDAC sbridge: Seeking for: PCI ID 8086:3ca8 [4.229237] EDAC sbridge: Seeking for: PCI ID 8086:3c71 [4.229244] EDAC sbridge: Seeking for: PCI ID 8086:3c71 [4.229248] EDAC sbridge: Seeking for: PCI ID 8086:3caa [4.229255] EDAC sbridge: Seeking for: PCI ID 8086:3caa [4.229258] EDAC sbridge: Seeking for: PCI ID 8086:3cab [4.229265] EDAC sbridge: Seeking for: PCI ID 8086:3cab [4.229268] EDAC sbridge: Seeking for: PCI ID 8086:3cac [4.229276] ED
Verlaag uw drinkwaterfactuur
Verlaag uw drinkwaterfactuur Kies voor een SipWell waterkoeler En bied uw klanten en werknemers water van bronkwaliteit Ontdek alle voordelen Waarom kiezen voor SipWell waterkoelers? -Unieke designs voor elk interieur -Geen zorgen om levering en facturatie -Gezondere en productievere werknemers -Uw klanten worden verwend -Extra opties als bruis of heet water Meer info over SipWell in uw bedrijf Ontdek waarom bedrijven voor SipWell kiezen... This email was sent to debian-kernel@lists.debian.org. If you are no longer interested you can unsubscribe instantly: http://mailexpert.hannibal.be/t/r-u-sjyhlut-hrydiujyiy-n/
Re: Re: LVM Merge
Hi Ben, I went ahead with the merge and it works without problems. Thanks! Tom
LVM Merge
Hello, I'm trying to merge an LVM snapshot into the original volume. If I look in the man page for lvconvert, under '--merge', it says: To check if your kernel supports the snapshot merge feature, look for 'snapshot-merge' in the output of 'dmsetup targets'. If I run 'dmsetup targets', I get the following: root@debian:~# dmsetup targets crypt v1.11.1 striped v1.4.1 linear v1.1.1 error v1.0.1 root@debian:~# I'm running a standard install of Debian 7.9: root@debian:~# uname -a Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 x86_64 GNU/Linux root@debian:~# Does anyone have any idea how to add snapshot-merge into the kernel? Thanks! Tom
Bug#802893: linux-image-3.16.0-4-amd64: additional info
Package: src:linux Version: 3.16.7-ckt11-1+deb8u5 Followup-For: Bug #802893 There is one information i forgot to add: When i encouter this bug, its useless for me to simply reboot and try again, because the machine will ALWAYS produce exactly this error. So no matter how often i reboot, i never can reach the graphical session. What i have to do instead is to boot into Windows. After that i can reboot into Linux and get into graphical mode without any problems. This suggests, that Linux is not able to initialise the hardware correctly. But once the hardware gets correctly initialized by Windows, its no problem for Linux to boot into graphical mode. -- 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-ckt11-1+deb8u5 (2015-10-09) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=UUID=25776b34-b8f2-469c-bb96-2a52652fbf4e ro quiet ** Not tainted ** Kernel log: [ 16.209484] [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6801 0x1462:0x1117). [ 16.209510] [drm] register mmio base: 0xFEA0 [ 16.209513] [drm] register mmio size: 262144 [ 16.209516] vga_switcheroo: enabled [ 16.209729] ATPX version 1, functions 0x0003 [ 18.207870] EXT4-fs (sda5): mounting ext3 file system using the ext4 subsystem [ 18.217544] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [ 19.986504] systemd-journald[263]: Received request to flush runtime journal from PID 1 [ 22.075855] ACPI Error: Field [TEMP] at 524288 exceeds Buffer [TVGA] size 512000 (bits) (20140424/dsopcode-236) [ 22.075872] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.ATRM] (Node 88023e04e748), AE_AML_BUFFER_LIMIT (20140424/psparse-536) [ 22.075896] failed to evaluate ATRM got AE_AML_BUFFER_LIMIT [ 22.075906] ATOM BIOS: MSI [ 22.076009] radeon :01:00.0: VRAM: 2048M 0x - 0x7FFF (2048M used) [ 22.076015] radeon :01:00.0: GTT: 1024M 0x8000 - 0xBFFF [ 22.076019] [drm] Detected VRAM RAM=2048M, BAR=256M [ 22.076021] [drm] RAM width 256bits DDR [ 22.076045] [drm] radeon: 2048M of VRAM memory ready [ 22.076048] [drm] radeon: 1024M of GTT memory ready. [ 22.076080] [drm] Loading PITCAIRN Microcode [ 22.112957] radeon :01:00.0: firmware: direct-loading firmware radeon/PITCAIRN_pfp.bin [ 22.221827] radeon :01:00.0: firmware: direct-loading firmware radeon/PITCAIRN_me.bin [ 22.239224] radeon :01:00.0: firmware: direct-loading firmware radeon/PITCAIRN_ce.bin [ 22.259754] radeon :01:00.0: firmware: direct-loading firmware radeon/PITCAIRN_rlc.bin [ 22.270155] radeon :01:00.0: firmware: direct-loading firmware radeon/PITCAIRN_mc2.bin [ 22.270170] [drm] radeon/PITCAIRN_mc2.bin: 31100 bytes [ 22.275130] radeon :01:00.0: firmware: direct-loading firmware radeon/PITCAIRN_smc.bin [ 22.275149] [drm] Internal thermal controller without fan control [ 22.275400] [drm] probing gen 2 caps for device 1022:1413 = 700d01/6 [ 22.287098] [drm] radeon: dpm initialized [ 22.287156] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 22.288854] [drm] probing gen 2 caps for device 1022:1413 = 700d01/6 [ 22.288860] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 22.618538] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [ 22.618693] radeon :01:00.0: WB enabled [ 22.618696] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x880233276c00 [ 22.618698] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x880233276c04 [ 22.618700] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x880233276c08 [ 22.618702] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x880233276c0c [ 22.618704] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x880233276c10 [ 22.620265] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc900127b5a18 [ 22.620276] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 22.620277] [drm] Driver supports precise vblank timestamp query. [ 22.620279] radeon :01:00.0: radeon: MSI limited to 32-bit [ 22.620301] radeon :01:00.0: irq 54 for MSI/MSI-X [ 22.620315] radeon :01:00.0: radeon: using MSI. [ 22.620347] [drm] radeon: irq initialized. [ 22.836517] [drm] ring test on 0 succeeded in 1 usecs [ 22.836529] [drm] ring test on 1 succeeded in 1 usecs [ 22.836538] [drm] ring test on 2 succeeded in 1 usecs [ 22.836551] [drm] ring test on 3 succeeded in 4 usecs [ 22.836562] [drm] ring test on 4 succeeded in 4 usecs [ 23.022302] [drm] ring test on 5 succeeded in 1 usecs [ 23.022328] [drm] UVD in
Bug#802893: linux-image-3.16.0-4-amd64: booting into graphical mode sometimes fails (console still works)
Package: src:linux Version: 3.16.7-ckt11-1+deb8u5 Severity: important Dear developers! I have a amd richland APU and also a dedicated graphics card r9 290m. Im not using the fglrx drivers. Sometimes booting into the graphical mode stops before the xserver should come. im using gdm +gnome3 a.t.m. I add the kernel trace here (and hope its of any help for you): Oct 24 12:25:15 hugo6 kernel: [ 32.510519] [ cut here ] Oct 24 12:25:15 hugo6 kernel: [ 32.510646] invalid opcode: [#1] SMP Oct 24 12:25:15 hugo6 kernel: [ 32.510691] Modules linked in: bnep snd_hda_codec_realtek joydev snd_hda_codec_hdmi snd_hda_codec_generic rtl8723ae rtl8723_common rtl_pci rtlwifi radeon mac80211 snd_hda_intel ecb btusb msi_wmi snd_hda_controller bluetooth sparse_keymap psmouse cfg80211 evdev snd_hda_codec serio_raw kvm_amd snd_hwdep 6lowpan_iphc snd_pcm kvm rfkill pcspkr ttm snd_timer drm_kms_helper k10temp drm snd ac wmi i2c_algo_bit i2c_piix4 i2c_core soundcore shpchp battery video button acpi_cpufreq processor fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 algif_skcipher af_alg dm_crypt dm_mod hid_generic usbhid hid sg sd_mod crc_t10dif sr_mod crct10dif_generic cdrom ata_generic ohci_pci crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ohci_hcd ehci_pci xhci_hcd ehci_hcd alx mdio pata_atiixp sdhci_pci ahci sdhci libahci mmc_core libata scsi_mod usbcore usb_common th ermal thermal_sys Oct 24 12:25:15 hugo6 kernel: [ 32.511781] CPU: 1 PID: 701 Comm: Xorg Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt11-1+deb8u5 Oct 24 12:25:15 hugo6 kernel: [ 32.511855] Hardware name: Micro-Star International Co., Ltd. GX70 3CC/MS-176K, BIOS E176KAMS.10F 12/02/2013 Oct 24 12:25:15 hugo6 kernel: [ 32.511937] task: 8800884e32f0 ti: 8800884e8000 task.ti: 8800884e8000 Oct 24 12:25:15 hugo6 kernel: [ 32.511999] RIP: 0010:[] [] radeon_invalid_rreg+0x1c/0x20 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.512105] RSP: 0018:8800884eb730 EFLAGS: 00010282 Oct 24 12:25:15 hugo6 kernel: [ 32.512151] RAX: 004a RBX: 0005 RCX: 0006 Oct 24 12:25:15 hugo6 kernel: [ 32.512212] RDX: 0007 RSI: 0046 RDI: 0246 Oct 24 12:25:15 hugo6 kernel: [ 32.512272] RBP: 880235d67880 R08: R09: 81659ac0 Oct 24 12:25:15 hugo6 kernel: [ 32.512332] R10: 03f0 R11: 00aa R12: 8800884eb780 Oct 24 12:25:15 hugo6 kernel: [ 32.512391] R13: 0069 R14: 0005 R15: 0005 Oct 24 12:25:15 hugo6 kernel: [ 32.512452] FS: 7f3792522980() GS:88023ec8() knlGS: Oct 24 12:25:15 hugo6 kernel: [ 32.512520] CS: 0010 DS: ES: CR0: 80050033 Oct 24 12:25:15 hugo6 kernel: [ 32.512569] CR2: 7f61d2d97ed0 CR3: 000233242000 CR4: 000407e0 Oct 24 12:25:15 hugo6 kernel: [ 32.512629] Stack: Oct 24 12:25:15 hugo6 kernel: [ 32.512650] a06bb0b0 0001884eb7b0 8800884eb7e0 8800884eb7dc Oct 24 12:25:15 hugo6 kernel: [ 32.512726] 0072 0006 5f78 0005 Oct 24 12:25:15 hugo6 kernel: [ 32.512802] a06bc1e5 8800884eb780 f10f 0077 Oct 24 12:25:15 hugo6 kernel: [ 32.512877] Call Trace: Oct 24 12:25:15 hugo6 kernel: [ 32.512923] [] ? atom_get_src_int+0x70/0x7d0 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513000] [] ? atom_op_shr+0x85/0x210 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513074] [] ? atom_execute_table_locked+0x119/0x360 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513158] [] ? atom_op_calltable+0xb3/0x130 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513235] [] ? atom_execute_table_locked+0x119/0x360 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513306] [] ? acpi_ds_create_operands+0x62/0xb2 Oct 24 12:25:15 hugo6 kernel: [ 32.513380] [] ? atom_op_calltable+0xb3/0x130 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513457] [] ? atom_execute_table_locked+0x119/0x360 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513542] [] ? atom_execute_table_scratch_unlocked+0x5c/0x70 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513630] [] ? atom_execute_table+0x2e/0x50 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513707] [] ? atom_asic_init+0x12d/0x180 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513795] [] ? si_resume+0x16/0x70 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513864] [] ? radeon_resume_kms+0x9d/0x270 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513942] [] ? radeon_pmops_runtime_resume+0x68/0x90 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.514010] [] ? pci_pm_runtime_resume+0x78/0xb0 Oct 24 12:25:15 hugo6 kernel: [ 32.514068] [] ? __rpm_callback+0x2c/0x80 Oct 24 12:25:15 hugo6 kernel: [ 32.514120] [] ? rpm_cal
Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))))
Still freezes. Switching now to Arch. Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5568c216.2000...@ib-guder.de
Bug#782711: [RFE] Override '/usr/share/initramfs-tools/init' in '/usr/sbin/mkinitramfs'
Package: initramfs-tools Version: 0.120 Severity: wishlist Please allow overriding '/usr/share/initramfs-tools/init' with '/etc/initramfs-tools/init', if the latter exists and is executable. Thanks. # apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://ftp.uk.debian.org/debian/ jessie/main Translation-en 500 http://ftp.uk.debian.org/debian/ jessie/main amd64 Packages release o=Debian,a=testing,n=jessie,l=Debian,c=main origin ftp.uk.debian.org # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 initrd=/boot/initrd.img-3.16.0-4-amd64 root=UUID=ea46bf5f-71aa-49d0-9124-6f680d146ef0 ro -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=sxhvmoxxsjcbw21t7rulsmnj9s8z9r5hq8bxbbdf7k...@mail.gmail.com
Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))))
Still random freezes with kernel: 3.16.7-ckt7-1 (2015-03-01) Bests Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54fd5dcf.5060...@ib-guder.de
Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))))
Random system freezes with power management disabled: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=8b037d1e-7609-4503-bea5-d0d4f2a4107f ro quiet radeon.dpm=0 radeon.audio=0 How can I help to provide more information? Bests Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1234046458.113549.1424788753495.javamail.open-xcha...@app09.ox.hosteurope.de
Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon)))
Hello. The bug still appears: [22705.085397] radeon :03:00.0: ring 0 stalled for more than 10012msec [22705.085402] radeon :03:00.0: GPU lockup (waiting for 0x00248486 last fence id 0x0024847f on ring 0) [22705.085432] radeon :03:00.0: failed to get a new IB (-35) [22705.572187] radeon :03:00.0: Saved 11021 dwords of commands on ring 0. [22705.572316] radeon :03:00.0: GPU softreset: 0x006C [22705.572318] radeon :03:00.0: GRBM_STATUS = 0xA0003028 [22705.572320] radeon :03:00.0: GRBM_STATUS_SE0 = 0x0006 [22705.572322] radeon :03:00.0: GRBM_STATUS_SE1 = 0x0006 [22705.572323] radeon :03:00.0: SRBM_STATUS = 0x20C0 [22705.572434] radeon :03:00.0: SRBM_STATUS2 = 0x [22705.572436] radeon :03:00.0: R_008674_CP_STALLED_STAT1 = 0x [22705.572438] radeon :03:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [22705.572439] radeon :03:00.0: R_00867C_CP_BUSY_STAT = 0x0002 [22705.572441] radeon :03:00.0: R_008680_CP_STAT = 0x80010243 [22705.572443] radeon :03:00.0: R_00D034_DMA_STATUS_REG = 0x44483146 [22705.572445] radeon :03:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [22705.572447] radeon :03:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [22705.572449] radeon :03:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x [22706.056014] radeon :03:00.0: GRBM_SOFT_RESET=0xDDFF [22706.056069] radeon :03:00.0: SRBM_SOFT_RESET=0x00100140 [22706.057216] radeon :03:00.0: GRBM_STATUS = 0x3028 [22706.057218] radeon :03:00.0: GRBM_STATUS_SE0 = 0x0006 [22706.057220] radeon :03:00.0: GRBM_STATUS_SE1 = 0x0006 [22706.057221] radeon :03:00.0: SRBM_STATUS = 0x20C0 [22706.057332] radeon :03:00.0: SRBM_STATUS2 = 0x [22706.057334] radeon :03:00.0: R_008674_CP_STALLED_STAT1 = 0x [22706.057336] radeon :03:00.0: R_008678_CP_STALLED_STAT2 = 0x [22706.057337] radeon :03:00.0: R_00867C_CP_BUSY_STAT = 0x [22706.057339] radeon :03:00.0: R_008680_CP_STAT = 0x [22706.057341] radeon :03:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [22706.057343] radeon :03:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [22706.057584] radeon :03:00.0: GPU reset succeeded, trying to resume [22706.084253] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [22706.084257] [drm] PCIE gen 3 link speeds already enabled [22706.086412] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [22706.086525] radeon :03:00.0: WB enabled [22706.086527] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x88085b69fc00 [22706.086529] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x88085b69fc04 [22706.086530] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x88085b69fc08 [22706.086532] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x88085b69fc0c [22706.086533] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x88085b69fc10 [22706.087140] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90015eb5a18 [22706.250455] [drm] ring test on 0 succeeded in 3 usecs [22706.250461] [drm] ring test on 1 succeeded in 1 usecs [22706.250465] [drm] ring test on 2 succeeded in 1 usecs [22706.250476] [drm] ring test on 3 succeeded in 6 usecs [22706.250484] [drm] ring test on 4 succeeded in 5 usecs [22706.426300] [drm] ring test on 5 succeeded in 2 usecs [22706.426307] [drm] UVD initialized successfully. [22716.434414] radeon :03:00.0: ring 0 stalled for more than 10004msec [22716.434419] radeon :03:00.0: GPU lockup (waiting for 0x002484f4 last fence id 0x0024847f on ring 0) [22716.434421] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [22716.434424] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [22716.434426] radeon :03:00.0: ib ring test failed (-35). [22716.918923] radeon :03:00.0: GPU softreset: 0x0048 [22716.918929] radeon :03:00.0: GRBM_STATUS = 0xA0003028 [22716.918932] radeon :03:00.0: GRBM_STATUS_SE0 = 0x0006 [22716.918933] radeon :03:00.0: GRBM_STATUS_SE1 = 0x0006 [22716.918935] radeon :03:00.0: SRBM_STATUS = 0x20C0 [22716.919046] radeon :03:00.0: SRBM_STATUS2 = 0x [22716.919048] radeon :03:00.0: R_008674_CP_STALLED_STAT1 = 0x [22716.919050] radeon :03:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [22716.919052] radeon :03:00.0: R_00867C_CP_BUSY_STAT = 0x0002 [22
Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))
Thank you for testing this. Would you file a bug in the mesa packages to resolve this problem, please? Thank you again and kind regards! Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54be05ee.9020...@ib-guder.de
Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))
Further freezes: Bests Tom [ 1198.159861] radeon :02:00.0: GPU fault detected: 147 0x0fa29002 [ 1198.159864] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000117B2 [ 1198.159866] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030E0002 [ 1198.159868] VM fault (0x02, vmid 1) at page 71602, write from CB (224) [ 1198.159871] radeon :02:00.0: GPU fault detected: 147 0x01626002 [ 1198.159873] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011796 [ 1198.159875] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02048002 [ 1198.159877] VM fault (0x02, vmid 1) at page 71574, read from TC (72) [ 1198.159877] systemd-journald[233]: /dev/kmsg buffer overrun, some messages lost. [ 1198.159883] radeon :02:00.0: GPU fault detected: 147 0x0e026002 [ 1198.159885] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000117CA [ 1198.159887] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030A0002 [ 1198.159890] VM fault (0x02, vmid 1) at page 71626, write from CB (160) [ 1198.159891] systemd-journald[233]: /dev/kmsg buffer overrun, some messages lost. [ 1198.159910] radeon :02:00.0: GPU fault detected: 147 0x0e02e002 [ 1198.159912] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001180B [ 1198.159914] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030A0002 [ 1198.159916] VM fault (0x02, vmid 1) at page 71691, write from CB (160) [ 1198.159920] radeon :02:00.0: GPU fault detected: 147 0x01622002 [ 1198.159922] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011824 [ 1198.159923] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030D0002 [ 1198.159925] VM fault (0x02, vmid 1) at page 71716, write from CB (208) [ 1198.159929] radeon :02:00.0: GPU fault detected: 147 0x01621002 [ 1198.159931] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011731 [ 1198.159933] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060002 [ 1198.159935] VM fault (0x02, vmid 1) at page 71473, write from CB (96) [ 1198.159949] radeon :02:00.0: GPU fault detected: 147 0x0e036002 [ 1198.159951] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001173B [ 1198.159953] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02044002 [ 1198.159955] VM fault (0x02, vmid 1) at page 71483, read from TC (68) [ 1198.159959] radeon :02:00.0: GPU fault detected: 147 0x0e036002 [ 1198.159960] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001172A [ 1198.159962] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020002 [ 1198.159964] VM fault (0x02, vmid 1) at page 71466, write from CB (32) [ 1198.160094] radeon :02:00.0: GPU fault detected: 147 0x0f03d002 [ 1198.160096] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1198.160098] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060002 [ 1198.160100] VM fault (0x02, vmid 1) at page 0, write from CB (96) [ 1198.160147] radeon :02:00.0: GPU fault detected: 147 0x0ec3d002 [ 1198.160149] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1198.160151] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0303D002 [ 1198.160152] VM fault (0x02, vmid 1) at page 0, write from DMA1 (61) [ 1198.160156] radeon :02:00.0: GPU fault detected: 147 0x0ec3a002 [ 1198.160158] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001175E [ 1198.160160] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0303D002 [ 1198.160162] VM fault (0x02, vmid 1) at page 71518, write from DMA1 (61) [ 1198.160220] systemd-journald[233]: /dev/kmsg buffer overrun, some messages lost. [ 1198.160232] radeon :02:00.0: GPU fault detected: 147 0x0e63a002 [ 1198.160234] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1198.160236] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088002 [ 1198.160238] VM fault (0x02, vmid 1) at page 0, read from TC (136) [ 1198.160242] radeon :02:00.0: GPU fault detected: 147 0x0e832002 [ 1198.160244] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0xC94A [ 1198.160246] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060004 [ 1198.160248] VM fault (0x04, vmid 1) at page 51530, write from CB (96) [ 1198.160251] radeon :02:00.0: GPU fault detected: 147 0x0e832002 [ 1198.160253] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0xC94A [ 1198.160255] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02084004 [ 1198.160257] VM fault (0x04, vmid 1) at page 51530, read from TC (132) [ 1198.160262] radeon :02:00.0: GPU fault detected: 147 0x0e639002 [ 1198.160264] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011747 [ 1198.160266] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020002 [ 1198.160268] VM fault (0x02, vmid 1) at page 71495
Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon)
Here is the tail of dmesg after such an error. Best regards Tom Guder [ 1104.412089] radeon :02:00.0: ring 0 stalled for more than 10104msec [ 1104.412098] radeon :02:00.0: GPU lockup (waiting for 0x000664a0 last fence id 0x0006649f on ring 0) [ 1104.412102] radeon :02:00.0: failed to get a new IB (-35) [ 1104.900461] radeon :02:00.0: Saved 21357 dwords of commands on ring 0. [ 1104.900590] radeon :02:00.0: GPU softreset: 0x006C [ 1104.900592] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1104.900593] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1104.900594] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1104.900595] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1104.900706] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1104.900707] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1104.900708] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1104.900710] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x0002 [ 1104.900711] radeon :02:00.0: R_008680_CP_STAT = 0x80010243 [ 1104.900713] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83146 [ 1104.900714] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [ 1104.900716] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1104.900718] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x [ 1105.370049] radeon :02:00.0: GRBM_SOFT_RESET=0xDDFF [ 1105.370101] radeon :02:00.0: SRBM_SOFT_RESET=0x00100140 [ 1105.371247] radeon :02:00.0: GRBM_STATUS = 0x3028 [ 1105.371248] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1105.371249] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1105.371250] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1105.371361] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1105.371362] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1105.371363] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x [ 1105.371365] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x [ 1105.371366] radeon :02:00.0: R_008680_CP_STAT = 0x [ 1105.371367] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 1105.371369] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ 1105.371608] radeon :02:00.0: GPU reset succeeded, trying to resume [ 1105.402616] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [ 1105.402619] [drm] PCIE gen 3 link speeds already enabled [ 1105.404456] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [ 1105.404557] radeon :02:00.0: WB enabled [ 1105.404559] radeon :02:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8800b54c0c00 [ 1105.404560] radeon :02:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x8800b54c0c04 [ 1105.404561] radeon :02:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x8800b54c0c08 [ 1105.404561] radeon :02:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x8800b54c0c0c [ 1105.404562] radeon :02:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x8800b54c0c10 [ 1105.405169] radeon :02:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90011fb5a18 [ 1105.564971] [drm] ring test on 0 succeeded in 2 usecs [ 1105.564978] [drm] ring test on 1 succeeded in 1 usecs [ 1105.564984] [drm] ring test on 2 succeeded in 1 usecs [ 1105.564995] [drm] ring test on 3 succeeded in 5 usecs [ 1105.565005] [drm] ring test on 4 succeeded in 5 usecs [ 1105.740770] [drm] ring test on 5 succeeded in 2 usecs [ 1105.740776] [drm] UVD initialized successfully. [ 1115.740176] radeon :02:00.0: ring 0 stalled for more than 1msec [ 1115.740183] radeon :02:00.0: GPU lockup (waiting for 0x000665a7 last fence id 0x0006649f on ring 0) [ 1115.740187] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [ 1115.740192] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 1115.740195] radeon :02:00.0: ib ring test failed (-35). [ 1116.221093] radeon :02:00.0: GPU softreset: 0x0048 [ 1116.221095] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1116.221097] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1116.221098] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1116.221099] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1116.221210] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1116.221211] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1116.221212] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1116.221214] radeon
Bug#771045: linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon
Package: src:linux Version: 3.16.7-2 Severity: important Dear Maintainer, with all my computers with radeon cards the system freezes randomy. I can't reproduce freezing. It happens more often with kernel 3.16 and less often with 3.14. Some others report this issue too: http://lists.freedesktop.org/archives/dri-devel/2014-July/065061.html https://bugzilla.kernel.org/show_bug.cgi?id=85421 Sometimes the system responds via ssh, sometimes everything is locked. Best regards Tom -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=8b037d1e-7609-4503-bea5-d0d4f2a4107f ro quiet ** Not tainted ** Kernel log: [7.365395] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_me.bin [7.431087] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [7.434492] systemd-journald[234]: Received request to flush runtime journal from PID 1 [7.464108] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_ce.bin [7.545250] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_rlc.bin [7.572113] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_mc2.bin [7.572122] [drm] radeon/PITCAIRN_mc2.bin: 31100 bytes [7.599761] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_smc.bin [7.599772] [drm] Internal thermal controller with fan control [7.599878] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [7.611793] [drm] radeon: dpm initialized [7.635468] radeon :03:00.0: firmware: direct-loading firmware radeon/TAHITI_uvd.bin [7.635520] [drm] GART: num cpu pages 262144, num gpu pages 262144 [7.636660] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [7.636664] [drm] PCIE gen 3 link speeds already enabled [7.654264] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [7.654411] radeon :03:00.0: WB enabled [7.654415] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x88085b634c00 [7.654417] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x88085b634c04 [7.654420] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x88085b634c08 [7.654422] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x88085b634c0c [7.654424] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x88085b634c10 [7.655034] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90015bb5a18 [7.655036] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [7.655037] [drm] Driver supports precise vblank timestamp query. [7.655065] radeon :03:00.0: irq 120 for MSI/MSI-X [7.655077] radeon :03:00.0: radeon: using MSI. [7.655140] [drm] radeon: irq initialized. [7.819842] [drm] ring test on 0 succeeded in 4 usecs [7.819847] [drm] ring test on 1 succeeded in 1 usecs [7.819851] [drm] ring test on 2 succeeded in 1 usecs [7.819863] [drm] ring test on 3 succeeded in 2 usecs [7.819873] [drm] ring test on 4 succeeded in 1 usecs [8.005659] [drm] ring test on 5 succeeded in 2 usecs [8.005666] [drm] UVD initialized successfully. [8.005909] [drm] ib test on ring 0 succeeded in 0 usecs [8.005959] [drm] ib test on ring 1 succeeded in 0 usecs [8.006007] [drm] ib test on ring 2 succeeded in 0 usecs [8.006048] [drm] ib test on ring 3 succeeded in 0 usecs [8.006088] [drm] ib test on ring 4 succeeded in 1 usecs [8.157226] [drm] ib test on ring 5 succeeded [8.157709] [drm] Radeon Display Connectors [8.157711] [drm] Connector 0: [8.157712] [drm] DP-1 [8.157712] [drm] HPD4 [8.157714] [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c [8.157715] [drm] Encoders: [8.157716] [drm] DFP1: INTERNAL_UNIPHY2 [8.157716] [drm] Connector 1: [8.157717] [drm] HDMI-A-1 [8.157718] [drm] HPD5 [8.157719] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [8.157720] [drm] Encoders: [8.157721] [drm] DFP2: INTERNAL_UNIPHY2 [8.157722] [drm] Connector 2: [8.157722] [drm] DVI-I-1 [8.157723] [drm] HPD1 [8.157724] [drm] DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c [8.157725] [drm] Encoders: [8.157726] [drm] DFP3: INTERNAL_UNIPHY1 [8.157727] [drm] Connector 3: [8.157727] [drm] DVI-I-2 [8.157728] [drm] HPD6 [8.157729] [drm] DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 0x658c [8.157730] [drm] Encoders: [8.157731] [drm] DFP4: INTERNAL_UNIPHY [8.157732]
Bug#712999: Here too
Same issue here, "but not always". CPU: model name : Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz Controller: 00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06) Kernel 3.14-0.bpo.1-amd64 Stock wheezy kernel untested as its C600 driver is bugged so it really doesn't find any drives/lvs to mount. -- Tom Laermans IT Infrastructure Manager Luciad NV - http://www.luciad.com Gaston Geenslaan 11, 3001 Heverlee, Belgium -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c3.6040...@luciad.com
Re: linux's make oldconfig: Save in addition to [N/m/y/?], and ctrl-[C/\] to abort
On Tue, Sep 10, 2013 at 6:33 PM, Regid Ichira wrote: > On Mon, Sep 09, 2013 at 09:55:08PM -0400, John D. Hendrickson and Sara > Darnell wrote: >> >> 2) you can run make oldconfig to get a recycled config without >> running in text interactive mode [y/n/m]. read the directions. > > Do you mean the yes pipe that Tom H was > referring to ealier in this thread? But you can not get a thoughtful > config file by that manner. I mean, I don't want a kernel with lots > of features I don't need. And I am trying to both config the kernel > AND learn what new features that are of interest to me were added. I wasn't suggesting that you use the config generated by 'yes "" | ...' only that you use it to list the new config options. Looking at "make help", there's (now?) a "make listnewconfig" option to do just that. Regarding interrupting "make oldconfig", I don't see any option at the moment except run "make menuconfig", set some options, save the config, exit, and return to make menuconfig" later. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SzZ=pupejglvs7pj3ndo1aogqbwaz87h_rfnd3vo6v...@mail.gmail.com
Re: linux's make oldconfig: Save in addition to [N/m/y/?], and ctrl-[C/\] to abort
On Sat, Sep 7, 2013 at 6:52 AM, Regid Ichira wrote: > > I find it useful to have the kernel configuration automatically > pointing out only the NEW kernel configuration options. Quite often, > the kernel's > > $ make oldconfig > > takes a long time. In particular, when I am trying to find out more > information on the NEW features. The options that I am aware of when > in the middle of make oldconfig are > 1. [N/m/y/?] (and sometime one of these, say m, is not applicable) > 2. ctrl-[C/\] to abort > Do you agree that besides it is desirable to have a Save to file > option? That is, > (3. Save to file and continue to configure) > This way, one might be able to return to where the work was left in > the middle. > In addition, probably a > (4. Quit) > is also required, so that one can leave the configuration process in > an orderly manner. You can do yes "" | make oldconfig > oldconfig-output.txt grep "(NEW)" oldconfig-output.txt to see all the new options. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=Sz4S5=q6js_o8b35xtwfkd35v45hw2shyvchp0xhax...@mail.gmail.com
Bug#682250: linux-image-3.2.0-2-amd64: sleep/suspend with USB drive connected produces instability (eventually lockup) on wake/resume
Ben Hutchings Fri, 20 Jul 2012 19:24:14 +0100 >>> [kernel version=3.2.9-1] is long outdated, please upgrade to 3.2.21-3. Tom Roche Sun, Jul 22, 2012 at 11:10:05PM -0400 >> I'll post if the sleep/suspend/USB/wake/resume problem recurs. Moritz Muehlenhoff Fri, 9 Aug 2013 17:07:51 +0200 > Did it? It has not. The problem I currently have with USB drives and sleep (aka "suspend to RAM") is that the same sequence as previous (with the same hardware as previous) 1 physically attach a USB drive to my system, which automounts 2 umount the USB drive but leave it physically attached 3 forget to physically detach the USB drive, and sleep the PC 4 detach the USB drive 5 wake the PC produces a less catastrophic, but still annoying, outcome: automount failure. After the sequence above, any subsequent attachment of the USB drive fails to automount, though I can still manually mount the drive. This continues until I reboot. For more details, see http://forums.linuxmint.com/viewtopic.php?f=199&t=139159 I'd appreciate advice about where to put a bug for this new problem (since this thread does not seem appropriate). HTH/TIA, Tom Roche -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/878v0a97v2@pobox.com
Bug#715056: atl1c: Wired connection stops working on post-3.2 kernels
Package: src:linux Version: 3.9.6-1 Severity: important Tags: upstream I have a laptop (ASUS K53SD) which ships with an Atheros gigabit NIC: 05:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0) My install started at Wheezy, where networking was rock solid with its 3.2 kernel. However, on every newer kernel that I've installed both on Wheezy (from Experimental and even Unstable, IIRC it happens with 3.7 and 3.8) or Jessie (stock testing kernel 3.9), the NIC loses connection after a while. The card simply stops Tx/Rx'ing data, nothing popups on display, nothing gets logged in the kernel logs. The loss of connection is noticed at the applications which suddenly can't connect to anything (not even a simple ping works). The only workaround is to unplug and then replug the network cable, then network works... but for a random period of time (from 5 minutes to a couple of hours). The connection works fine otherwise under: - Wheezy 3.2.x kernels - Windows 7 - Any other OS media (including the Ubuntu 11.10 that originally shipped with this laptop) using older Linux kernels I've already tried changing network cables, switch ports, but no joy. The wireless NIC (also an Atheros part) works flawlessly with any kernel that I throw at it... but for obvious reasons (don't want to turn on my AP just for a single laptop that never leaves my desktop!) I don't want to go wireless with this one. It seems to be a problem with ANYTHING with a Linux kernel past 3.2 (at least?). A similar problem is reported at Launchpad here: https://answers.launchpad.net/ubuntu/+question/228126 But I'm not using VPNs or anything unusual, just a plain LAN connection to a home router. Other computers running Wheezy and Jessie kernels (with different wired/wireless NICs) don't exhibit this issue. -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-4) ) #1 SMP Debian 3.9.6-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.9-1-amd64 root=UUID=7d077c96-7768-4797-b63d-7740b46c0440 ro resume=/dev/sda3 resume_offset=108544 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 pcie_aspm=force ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [8.822212] uvcvideo: Found UVC 1.00 device ASUS USB2.0 WebCam (058f:a014) [8.825511] input: ASUS USB2.0 WebCam as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input8 [8.825679] usbcore: registered new interface driver uvcvideo [8.825772] USB Video Class driver (1.1.1) [8.624009] asus_wmi: ASUS WMI generic driver loaded [8.889776] asus_wmi: Initialization: 0x1asus_wmi: BIOS WMI version: 7.6 [8.889962] asus_wmi: SFUN value: 0xa0877<6>[8.890604] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [8.907599] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input10 [8.907739] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input11 [8.907863] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 [8.908867] [drm] Memory usable by graphics device = 2048M [8.908928] i915 :00:02.0: setting latency timer to 64 [8.928832] i915 :00:02.0: irq 53 for MSI/MSI-X [8.928840] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [8.928898] [drm] Driver supports precise vblank timestamp query. [8.929164] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem [8.929235] vgaarb: transferring owner from PCI::00:02.0 to PCI::01:00.0 [8.950303] [drm] Wrong MCH_SSKPD value: 0x16040307 [8.950360] [drm] This can cause pipe underruns and display issues. [8.950415] [drm] Please upgrade your BIOS to fix this. [8.954543] ACPI Error: [IIA0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dsfield-211) [8.954732] ACPI Error: Method parse/execution failed [\_SB_.ATKD.WMNB] (Node 8801c84a9970), AE_ALREADY_EXISTS (20130117/psparse-537) [8.954966] ACPI Error: [IIA0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dsfield-211) [8.955140] ACPI Error: Method parse/execution failed [\_SB_.ATKD.WMNB] (Node 8801c84a9970), AE_ALREADY_EXISTS (20130117/psparse-537) [8.955410] ACPI Error: [IIA0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dsfield-211) [8.955590] ACPI Error: Method parse/execution failed [\_SB_.ATKD.WMNB] (Node 8801c84a9970), AE_ALREADY_EXISTS (20130117/psparse-537) [8.955866] ACPI: Marking method WMNB as Serialized because of AE_ALREADY_EXISTS error [8.961481] asus-nb-wmi: probe of asus-nb-wmi failed with error -5 [9.042921] fbcon: inteldrmfb (fb0) is primary device [9.455418] Console: switching to colour frame buffer device 170x48 [9.458218] i915 :00:02.0: fb0: inteldrmfb frame buffer device [9.458244] i915 :00:02.0: registe
Bug#704269: linux-image-3.2.0-4-amd64: Kernel patch: udf: Fix handling of i_blocks
Package: src:linux Version: 3.2.39-2 Severity: important Tags: patch Somewhere last year there was a regression on the kernel UDF driver that was related with the handling of free space and used blocks on writable UDF filesystems (for example, my case involves a 2TB HDD formatted to UDF for cross-OS compatibility). This causes the following problems: - du (most likely the basic 'stat' call) returns 0 for every file written on a UDF filesystem using this kernel - Windows 7 systems (which can also natively write to UDF filesystems) may think that the filesystem has no free space, therefore turning it read-only (but the FS can be fully written under Linux) - Some other errors may be lurking there, expecting to be revealed by a UDF filesystem validation tool (like the old Philips' UDF Conformance Testing Application), related with the file space allocation. This regression was fixed on the 3.4 kernel, here is the relevant patch: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fd4287dbc07763595c1e74edbb6520092290185c I highly suggest that this patch get backported to Wheezy 3.2 kernel, because this regression is very annoying for those expecting to use UDF as a fully- interoperable cross-OS filesystem. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=e4eb11e0-bfbb-4285-b7ba-be6de5863ed6 ro resume=/dev/sda4 resume_offset=208896 radeon.modeset=1 radeon.dynclks=1 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [7.563293] [drm] GART: num cpu pages 131072, num gpu pages 131072 [7.564236] [drm] radeon: ib pool ready. [7.565515] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [7.566420] [drm] PCIE GART of 512M enabled (table at 0x0004). [7.566492] radeon :01:00.0: WB enabled [7.566542] [drm] fence driver on ring 0 use gpu addr 0x1000 and cpu addr 0x8800baec1000 [7.566686] [drm] Loading R500 Microcode [7.642399] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X [7.642444] snd_hda_intel :00:1b.0: setting latency timer to 64 [7.956713] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input8 [7.956918] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [8.068270] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [8.068345] cdrom: Uniform CD-ROM driver Revision: 3.20 [8.068858] sr 2:0:0:0: Attached scsi CD-ROM sr0 [8.190289] platform radeon_cp.0: firmware: agent loaded radeon/R520_cp.bin into memory [8.190603] [drm] radeon: ring at 0x10001000 [8.190689] [drm] ring test succeeded in 9 usecs [8.190920] [drm] ib test succeeded in 0 usecs [8.191409] [drm] Radeon Display Connectors [8.191463] [drm] Connector 0: [8.191511] [drm] VGA [8.191560] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [8.191619] [drm] Encoders: [8.191666] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [8.191716] [drm] Connector 1: [8.191763] [drm] LVDS [8.191813] [drm] DDC: 0x7e30 0x7e30 0x7e34 0x7e34 0x7e38 0x7e38 0x7e3c 0x7e3c [8.191871] [drm] Encoders: [8.191918] [drm] LCD1: INTERNAL_LVTM1 [8.191968] [drm] Connector 2: [8.192044] [drm] S-video [8.192105] [drm] Encoders: [8.192153] [drm] TV1: INTERNAL_KLDSCP_DAC2 [8.192229] [drm] radeon: power management initialized [8.362760] input: Logitech USB Optical Mouse as /devices/pci:00/:00:1d.7/usb1/1-1/1-1.1/1-1.1:1.0/input/input10 [8.363075] generic-usb 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-:00:1d.7-1.1/input0 [8.366731] input: 2-Axis,8-Button as /devices/pci:00/:00:1d.7/usb1/1-1/1-1.4/1-1.4:1.0/input/input11 [8.367104] generic-usb 0003:0583:A000.0002: input,hidraw1: USB HID v1.10 Joystick [2-Axis,8-Button ] on usb-:00:1d.7-1.4/input0 [8.367189] usbcore: registered new interface driver usbhid [8.367243] usbhid: USB HID core driver [8.608142] cfg80211: World regulatory domain updated: [8.608195] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [8.608254] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.608312] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.608369] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.608427] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.608485] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.662798] [drm] fb mappable at 0xD00C [8.662851] [drm] vram apper at 0xD000 [8.662901] [drm] size 4096000 [8.662949] [drm] fb depth
Bug#695872: [squeeze] kernel panic in sunrpc module when using automount daemon
Jonathan: I meant to include a URL to that particular patch. Thanks for pointing it out. I know next-to-nothing about kernel programming at this level - should I consider this a real fix in that a problem is actually resolved, or should I deploy this patch on my systems knowing that it's more of a band-aid? Thanks for getting back quickly. -- Tom Downes Associate Scientist and Data Center Manager Center for Gravitation, Cosmology and Astrophysics University of Wisconsin-Milwaukee 414.229.2678 On Thu, Dec 13, 2012 at 1:34 PM, Jonathan Nieder wrote: > tags 695872 + upstream patch unreproducible > quit > > Hi Tom, > > Tom Downes wrote: > >> While running a shell script that looped over a couple hundred >> filesystems accessed via automoutning NFS exports (unmounted prior >> to running the script), there was a kernel panic that prevented >> further automounts from occurring. > > Thanks for reporting. > >> This problem seems very similar to bug #691764 filed under the >> autofs package but I believe the bug is really in the sunrpc module. > > In that report the panic is in different code, so I think they are > distinct. > >> I've found a patch described here, applied it to my system and have >> not experienced a crash since. I only ever experienced one crash, >> however, and unpatched systems are yet to crash. > > For reference: > > v2.6.38-rc1~407^2~38 kernel panic when mount NFSv4, 2010-12-20 > > Trond explains: > > | The panic place is: > | rpc_mkpipe > | __rpc_lookup_create() <=== find pipefile *idmap* > | __rpc_mkpipe() <=== pipefile is *idmap* > | __rpc_create_common() > | ** BUG_ON(!d_unhashed(dentry)); ** *panic* > | > | The test is wrong: we can find ourselves with a hashed negative dentry here > | if the idmapper tried to look up the file before we got round to creating > | it. > > It seems like a match and I think you're right that the patch would > fix it. Thanks for finding it. > > Hope that helps, > Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/calrgx-s6cuw2hy871bspazx7o-0fdnpno5fuvzmoldnyoa8...@mail.gmail.com
Bug#695872: linux-image-2.6.32-5-amd64: kernel panic in sunrpc module when using automount daemon
Package: linux-2.6
Version: 2.6.32-46
Severity: important
While running a shell script that looped over a couple hundred filesystems
accessed via automoutning NFS
exports (unmounted prior to running the script), there was a kernel panic that
prevented further automounts
from occurring. The only solution to get automounting running again was to
reboot the system. For us,
automounting is important as it is the primary way of accessing user home
directories in a distributed
computing system.
This problem seems very similar to bug #691764 filed under the autofs package
but I believe the bug is really
in the sunrpc module.
I've found a patch described here, applied it to my system and have not
experienced a crash since. I only ever
experienced one crash, however, and unpatched systems are yet to crash. So it's
something of a rare feat and
this patch may simply ignore the BUG_ON forced kernel panic rather than
actually avoid a real, underlying
problem. I am not versed enough in kernel programming and this particular
system to know.
diff --git a/net/sunrpc/rpc_pipe.c b/net/sunrpc/rpc_pipe.c
index 10a17a3..5356d95 100644
--- a/net/sunrpc/rpc_pipe.c
+++ b/net/sunrpc/rpc_pipe.c
@@ -466,7 +466,7 @@ static int __rpc_create_common(struct inode *dir, struct
dentry *dentry,
{
struct inode *inode;
- BUG_ON(!d_unhashed(dentry));
+ d_drop(dentry);
inode = rpc_get_inode(dir->i_sb, mode);
if (!inode)
goto out_err;
Note that I've recompiled a new sunrpc.ko using the simple patch above prior to
reporting the bug; the memory
footprint of the sunrpc module reported below is therefore likely to differ
from that included in the standard
package. It has not crashed since, though I only experienced the problem once.
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-46) (da...@debian.org) (gcc version
4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 10:07:46 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64
root=UUID=5c4de580-2a6d-4b47-92fc-68f0c977ddbe ro quiet
** Not tainted
** Kernel log:
Dec 5 13:31:45 pcdev2 kernel: [529052.596136] [ cut here
]
Dec 5 13:31:45 pcdev2 kernel: [529052.596213] kernel BUG at
/build/buildd-linux-2.6_2.6.32-46-amd64-_ApuPc/linux-2.6-2.6.32/debian/build/source_amd64_none/net/sunrpc/rpc_pipe.c:462!
Dec 5 13:31:45 pcdev2 kernel: [529052.596313] invalid opcode: [#1] SMP
Dec 5 13:31:45 pcdev2 kernel: [529052.596361] last sysfs file:
/sys/devices/virtual/bdi/0:74/uevent
Dec 5 13:31:45 pcdev2 kernel: [529052.596415] CPU 26
Dec 5 13:31:45 pcdev2 kernel: [529052.596454] Modules linked in: autofs4 fuse
nfsd nfs lockd fscache nfs_acl auth_rpcgss sunrpc xfs exportfs loop snd_pcm
snd_timer snd soundcore edac_core edac_mce_amd i2c_piix4 button processor
joydev snd_page_alloc k10temp pcspkr evdev i2c_core ext4 mbcache jbd2 crc16
dm_mod raid1 md_mod usbhid hid sd_mod crc_t10dif ata_generic ohci_hcd
pata_atiixp ahci thermal thermal_sys igb libata ehci_hcd usbcore dca nls_base
scsi_mod [last unloaded: scsi_wait_scan]
Dec 5 13:31:45 pcdev2 kernel: [529052.596880] Pid: 26538, comm: mount.nfs Not
tainted 2.6.32-5-amd64 #1 H8QG6
Dec 5 13:31:45 pcdev2 kernel: [529052.596933] RIP: 0010:[]
[] __rpc_create_common+0x1a/0xb0 [sunrpc]
Dec 5 13:31:45 pcdev2 kernel: [529052.597029] RSP: 0018:881425ddf9b8
EFLAGS: 00010246
Dec 5 13:31:45 pcdev2 kernel: [529052.597076] RAX: RBX:
1180 RCX: a033c700
Dec 5 13:31:45 pcdev2 kernel: [529052.597154] RDX: 1180 RSI:
88036a2c2c00 RDI: 880c262530c0
Dec 5 13:31:45 pcdev2 kernel: [529052.597233] RBP: 88036a2c2c00 R08:
881b2dec R09: 881c2642a100
Dec 5 13:31:45 pcdev2 kernel: [529052.597311] R10: R11:
R12: 880c262530c0
Dec 5 13:31:45 pcdev2 kernel: [529052.597389] R13: a033c700 R14:
881b2dec R15: 881b2dec
Dec 5 13:31:45 pcdev2 kernel: [529052.597469] FS: 7f050c5cf700()
GS:88183648() knlGS:
Dec 5 13:31:45 pcdev2 kernel: [529052.597551] CS: 0010 DS: ES: CR0:
8005003b
Dec 5 13:31:45 pcdev2 kernel: [529052.597599] CR2: 7fb87bda3c50 CR3:
001c25901000 CR4: 06e0
Dec 5 13:31:45 pcdev2 kernel: [529052.597678] DR0: DR1:
DR2:
Dec 5 13:31:45 pcdev2 kernel: [529052.597756] DR3: DR6:
0ff0 DR7: 0400
Dec 5 13:31:45 pcdev2 kernel: [529052.597835] Process mount.nfs (pid: 26538,
threadinfo 881425dde000, task 88142676f810)
Dec 5 13:31:45 pcdev2 kernel: [529052.597917] Stack:
Dec 5 13:31:45 pcdev2 kernel: [529052.597953] 1180
88036a2c2c00 a03d22fc a03cd5f0
Dec 5 13:31:45 pcdev2 kernel: [529052.598012] <0> 880c262530c0
a0338618 0011 25d1c810
Bug#668511: Kernel panic with bridge networking
Hi, I was experiencing the same panics. Massimo pointed me to the changelog of 3.2.32 and commit bfa539657d2f54ed7f584e0577a37d4e06c2d959 which seemed to have fixed the issue. I'm running linux-image-3.2.0-4-amd64=3.2.32-1 for around 3 weeks now and haven't experienced the panics any more. warm regards, Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121205105614.28108.54113.report...@beppo.seclinet.org
Bug#682250: linux-image-3.2.0-2-amd64: sleep/suspend with USB drive connected produces instability (eventually lockup) on wake/resume
Ben Hutchings Fri, 20 Jul 2012 19:24:14 +0100 > [kernel version=3.2.9-1] is long outdated, please upgrade to 3.2.21-3. Done, after working around http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651973 as recommended @ https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/978920 I was able to $ sudo aptitude install linux-headers-3.2.0-3-amd64 linux-image-3.2.0-3-amd64 relatively normally. I'll post if the sleep/suspend/USB/wake/resume problem recurs. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d33n5g1e@pobox.com
Bug#682250: linux-image-3.2.0-2-amd64: sleep/suspend with USB drive connected produces instability (eventually lockup) on wake/resume
Package: linux-2.6
Version: 3.2.9-1
Severity: important
Dear Maintainer,
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
I do not recall observing the following behavior before installing a 3.x
kernel, which I did as part of updating LMDE.
I have observed similar behavior with different hardware (a ThinkPad W510) with
same distro/version (LMDE update pack 4).
The problem is often but intermittently observed on resume from sleep/suspend
(which I do frequently).
I believe it happens most often when I do the following sequence:
1 physically attach a USB drive to my system, which automounts (almost always
as sdb, i.e. no other external drives)
Note the USB drive (a Sansa+ mp3 player) itself contains a microSD card,
which may complicate matters.
2 umount the USB drive but leave it physically attached
3 sleep the PC
4 physically detach the USB drive
5 wake the PC
This produces boot to white text messages on black screen. Often the system
will hang at this point.
Today I was able to C-A-F7 (C-A-F1 .. C-A-F6 had no effect) to the graphical
login, whereupon I observed the following text in all terminal tabs:
> Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
> kernel:[99821.505724] Oops: [#1] SMP
> Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
> kernel:[99821.507390] Stack:
> Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
> kernel:[99821.507589] Call Trace:
> Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
> kernel:[99821.508029] Code: 31 f6 88 c2 83 e2 ef a8 02 88 95 bc 02 00 00 74
> 13 83 e0 08 3c 01 19 f6 81 e6 00 fc ff ff 81 c6 00 0c 00 00 48 8b 85 88 02 00
> 00 <48> 8b b8 30 03 00 00 e8 75 d9 08 e1 48 8b 85 98 02 00 00 48 8b
> Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
> kernel:[99821.508029] CR2: 0330
In my experience, observing text such as the above usually indicate system
instability.
(Note, that, in the scenario above, the message format above is constant: what
changes is
* the strings in square brackets (though they are invariably [0-9]{5}\.[0-9]{6})
* the string following 'Code: '
* the sting following 'CR2: '
) I.e., if I continue using the system after observing the above, it will lock
up within a matter of hours.
* What outcome did you expect instead?
I expect the system to restart normally and stably, whether or not a device is
physically attached or detached.
-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.9-1) (debian-kernel@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Sun Mar 4 22:48:17 UTC 2012
** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64
root=UUID=5821418b-0f83-43b0-99f2-77964602ef6b ro quiet
** Tainted: D (128)
* Kernel has oopsed before.
** Kernel log:
[99817.716239] jmb38x_ms :07:00.3: setting latency timer to 64
[99817.716323] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716333] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716344] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716353] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716364] nouveau :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[99817.716371] nouveau :01:00.0: setting latency timer to 64
[99817.716378] [drm] nouveau :01:00.0: POSTing device...
[99817.716384] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset
0xDBE1
[99817.716882] sd 0:0:0:0: [sda] Starting disk
[99817.741847] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset
0xDFE6
[99817.748233] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset
0xE8A9
[99817.748306] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset
0xE977
[99817.749456] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset
0xEC20
[99817.749460] [drm] nouveau :01:00.0: Parsing VBIOS init table at offset
0xEC85
[99817.769392] [drm] nouveau :01:00.0: Restoring GPU objects...
[99818.036075] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[99818.038689] ata2.00: configured for UDMA/100
[99818.044062] ata6: SATA link down (SStatus 0 SControl 300)
[99818.052061] usb 8-2: reset full-speed USB device number 20 using uhci_hcd
[99818.052107] ata5: SATA link down (SStatus 0 SControl 300)
[99818.063047] [drm] nouveau :01:00.0: Reinitialising engines...
[99818.063601] [drm] nouveau :01:00.0: Restoring mode...
[99818.179182] iwlwifi :02:00.0: RF_KILL bit toggled to enable radio.
[99818.182635] Extended CMOS year: 2000
[99818.336052] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[99820.748173] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[99820.752597] ata1.00: configured for UDMA/133
[99820.780070] PM: resume of devices complete after 3068.344 msecs
[99820.780540] PM: Finishing wakeup.
[99820.780544] Restarting tasks ...
[99820.780625] usb 8-2
Bug#616109: confirming bug in kernel for raq2
Hi all, I'd like to confirm this bug, also experiencing this. It's not related to ntpd specific, all ntp updates on kernel will eventually crash the system. When; while using time update methods, like - ntpdate (cron) - ntpd (daemon) - openbsd ntpd (daemon) Versions: Experienced this with multiple debian versions (4-6) all kernels + updates so far. Current: - Debian 6.0.4 - Kernel: 2.6.32-5-r5k-cobalt - Arch: mips Symptoms: No kernel messages or errors found (incl remote syslog). Remote syslog server saves the timestamp sent by the system. Looking at the logs before crash; time on the system stops! Starting at some point, all logs have exactly the same timestamp until the system does not respond anymore. Hope this helps. Regards, Tom Duijf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/407b305e-5781-4c6f-b566-bbcdca5d6...@gmail.com
Bug#409349: usbhid: control queue full; hung apcupsd task
From: "Jonathan Nieder" jrnie...@gmail.com > Thanks much. Do you remember roughly when you last experienced this > bug? > > (The last time I see in the bug log is in 2007 with 2.6.17 or so :). > Others have experienced it with kernels as new as 2.6.32-41 so I'd be > especially interested if you remember the behavior with 2.6.33, > 2.6.35, 2.6.38, etc. /var/log/dpkg.log* should have the upgrade > history of the kernel package if that helps jog your memory.) The logs say that I installed 2.6.37 on 2011-04-02 and 2.6.38 on 2011-06-07. I think the issue disappeared before either of those dates, but I can't be certain. The logs don't go back any further to the earlier kernel versions so can't help there I'm afraid. T -- (this email is not signed because it was sent using webmail) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a943ff1d1e515e12322857e9766df...@secure.tomonica.net
Bug#409349: usbhid: control queue full; hung apcupsd task
On Thursday 05 April 2012 00:39:32 you wrote: > Tom Wright wrote: > > I haven't seen this bug in quite a while, so maybe it's fixed in 3.X? > > Best see what others say too I guess. > > Thanks for the update. How long have you been using the wheezy/sid > kernel? Do you mind if I forward this information to the bug log? Quite a while now - I run sid on the machine which has a UPS, so however long it's been the standard kernel in that branch. A few months, at least. You're welcome to send it on to the bug log too. signature.asc Description: This is a digitally signed message part.
Bug#659866: Doesn't look fixed to me...
# update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-3.2.0-1-amd64 FATAL: Module xhci not found. FATAL: Module zfcp not found. FATAL: Module dasd_diag_mod not found. FATAL: Module dasd_eckd_mod not found. FATAL: Module dasd_fba_mod not found. FATAL: Module ohci1394 not found. update-initramfs: Generating /boot/initrd.img-3.1.0-1-amd64 FATAL: Module xhci not found. FATAL: Module hid-logitech-dj not found. FATAL: Module af_packet not found. FATAL: Module atkbd not found. FATAL: Module zfcp not found. FATAL: Module dasd_diag_mod not found. FATAL: Module dasd_eckd_mod not found. FATAL: Module dasd_fba_mod not found. FATAL: Module unix not found. WARNING: could not open /var/tmp/mkinitramfs_kEtrRm/lib/modules/3.1.0-1-amd64/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-3.0.0-2-amd64 FATAL: Module xhci not found. FATAL: Module hid-logitech-dj not found. FATAL: Module af_packet not found. FATAL: Module atkbd not found. FATAL: Module zfcp not found. FATAL: Module dasd_diag_mod not found. FATAL: Module dasd_eckd_mod not found. FATAL: Module dasd_fba_mod not found. FATAL: Module unix not found. WARNING: could not open /var/tmp/mkinitramfs_8lHi5o/lib/modules/3.0.0-2-amd64/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-3.0.0-1-amd64 FATAL: Module xhci not found. FATAL: Module hid-logitech-dj not found. FATAL: Module af_packet not found. FATAL: Module atkbd not found. FATAL: Module zfcp not found. FATAL: Module dasd_diag_mod not found. FATAL: Module dasd_eckd_mod not found. FATAL: Module dasd_fba_mod not found. FATAL: Module unix not found. WARNING: could not open /var/tmp/mkinitramfs_B5rbqh/lib/modules/3.0.0-1-amd64/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-2.6.39-2-amd64 FATAL: Module xhci not found. FATAL: Module hid-logitech-dj not found. FATAL: Module af_packet not found. FATAL: Module atkbd not found. FATAL: Module zfcp not found. FATAL: Module dasd_diag_mod not found. FATAL: Module dasd_eckd_mod not found. FATAL: Module dasd_fba_mod not found. FATAL: Module unix not found. WARNING: could not open /var/tmp/mkinitramfs_UYiDNO/lib/modules/2.6.39-2-amd64/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-2.6.39-1-amd64 FATAL: Module xhci not found. FATAL: Module hid-logitech-dj not found. FATAL: Module af_packet not found. FATAL: Module atkbd not found. FATAL: Module zfcp not found. FATAL: Module dasd_diag_mod not found. FATAL: Module dasd_eckd_mod not found. FATAL: Module dasd_fba_mod not found. FATAL: Module unix not found. WARNING: could not open /var/tmp/mkinitramfs_banRTr/lib/modules/2.6.39-1-amd64/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-2.6.38-2-amd64 FATAL: Module xhci not found. FATAL: Module hid-logitech-dj not found. FATAL: Module af_packet not found. FATAL: Module atkbd not found. FATAL: Module zfcp not found. FATAL: Module dasd_diag_mod not found. FATAL: Module dasd_eckd_mod not found. FATAL: Module dasd_fba_mod not found. FATAL: Module unix not found. WARNING: could not open /var/tmp/mkinitramfs_vnR3a9/lib/modules/2.6.38-2-amd64/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-2.6.38-1-amd64 FATAL: Module xhci not found. FATAL: Module hid-logitech-dj not found. FATAL: Module af_packet not found. FATAL: Module atkbd not found. # dpkg --list initramfs-tools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii initramfs-tool 0.101 generic modular initramfs generator # update-initramfs --version /usr/sbin/update-initramfs: illegal option -- - Usage: /usr/sbin/update-initramfs [OPTION]... Options: -k [version]Specify kernel version or 'all' -cCreate a new initramfs -uUpdate an existing initramfs -dRemove an existing initramfs -tTake over a custom initramfs with this one -bSet alternate boot directory -vBe verbose -hThis message -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f56e16c.2000...@gmail.com
Re: Hang when booting 3.1.0-1-686-pae and 2.6.38-1-686
On Wed, Jan 11, 2012 at 12:39:00PM +, Tom Ellis wrote: > On Wed, Jan 11, 2012 at 12:33:49PM +0000, Tom Ellis wrote: > > My boot under 3.1.0-1-686-pae, 3.1.0-1-486, and 2.6.38-1-686 hangs with the > > following screen: > > > > http://i.imgur.com/ij3kG.jpg I now know a work around: pci=noacpi. Not very satisfying, but it works. I also testing 2.6.37 and it's fine, so something happened in 2.6.38 that broke ACPI on Dell Inspiron 2650, and causes the computer to fail to boot. Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2012050930.GP22681@weber
Hang when booting 3.1.0-1-686-pae and 2.6.38-1-686
My boot under 3.1.0-1-686-pae, 3.1.0-1-486, and 2.6.38-1-686 hangs with the following screen: http://i.imgur.com/ij3kG.jpg Under 2.6.32-5-686 and 2.6.26-2-686 it's fine. Any ideas? (It's an old Dell Inspiron 2650. I attach /proc/cpuinfo, lspci and dmesg below) Thanks, Tom % cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Mobile Intel(R) Pentium(R) 4 - M CPU 1.70GHz stepping: 7 cpu MHz : 1200.000 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid bogomips: 2392.77 clflush size: 64 cache_alignment : 128 address sizes : 36 bits physical, 32 bits virtual power management: % sudo lspci -vvv # Under 2.6.32 00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 05) Subsystem: Dell Device 00f3 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW+ Rate=x1 Kernel driver in use: agpgart-intel 00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 05) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB Controller #1 (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Device 00f3 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 02:01.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) Subsystem: Dell Device 00f3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Kernel driver in use: yenta_cardbus dmesg under 2.6.32: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-28) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 25 18:43:34 UTC 2010 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 000dc000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1fef (usable) [0.00] BIOS-e820: 1fef - 1feff000 (ACPI data) [0.00] BIOS-e820: 1feff000 - 1ff0 (ACPI NVS) [0.00] BIOS-e820: 1ff0 - 1ff8 (usable) [0.00] BIOS-e820: 1ff8 - 2000 (reserved) [0.00] BIOS-e820: ff80 - ffc0 (reserved) [0.00] BIOS-e820: fff0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] last_pfn = 0x1ff80 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C7FFF write-protect [0.00] C8000-E
Re: Hang when booting 3.1.0-1-686-pae and 2.6.38-1-686
On Wed, Jan 11, 2012 at 12:33:49PM +, Tom Ellis wrote: > My boot under 3.1.0-1-686-pae, 3.1.0-1-486, and 2.6.38-1-686 hangs with the > following screen: > > http://i.imgur.com/ij3kG.jpg > > Under 2.6.32-5-686 and 2.6.26-2-686 it's fine. Any ideas? > > (It's an old Dell Inspiron 2650. I attach /proc/cpuinfo, lspci and dmesg > below) This will probably be useful too: % dpkg -l linux-image\* | grep -v none [...] +++-==-==[...] ri linux-image-2.6.26-2-686 2.6.26-26 ii linux-image-2.6.32-5-686 2.6.32-28 ii linux-image-2.6.38-1-686 2.6.38-1 ii linux-image-3.1.0-1-4863.1.8-2 ii linux-image-3.1.0-1-686-pae3.1.8-2 ii linux-image-3.1.0-1-686-pae-dbg3.1.8-2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2012023900.GN22681@weber
Bug#622146: nfs-common: Also problem between wheezy and sid
Package: nfs-common Version: 1:1.2.3-2 Followup-For: Bug #622146 At my pc I'm running sid and my server is running wheezy (on a 2.6.32-5-xen-amd64 kernel). I've upgrade it to all latest packages today and I can confirm that with this configuration the issue also exists. I'll try a more recent kernel to see what effect it has on this. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 49727 status 1000241 tcp 60755 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= RPCGSSDOPTS="" NEED_IDMAPD=yes NEED_GSSD=yes -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = THUIS.LAN [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113 add and remove users and groups ii initscripts 2.88dsf-13.10 scripts for initializing and shutt ii libc62.13-7 Embedded GNU C Library: Shared lib ii libcap2 1:2.21-1support for getting/setting POSIX. ii libcomerr2 1.41.12-4 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.9.1+dfsg-1+b1 MIT Kerberos runtime libraries - k ii libgssglue1 0.2-3 mechanism-switch gssapi library ii libk5crypto3 1.9.1+dfsg-1+b1 MIT Kerberos runtime libraries - C ii libkrb5-31.9.1+dfsg-1+b1 MIT Kerberos runtime libraries ii libnfsidmap2 0.24-1 An nfs idmapping library ii libtirpc10.2.2-2 transport-independent RPC library ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii netbase 4.45Basic TCP/IP networking system ii rpcbind 0.2.0-6 converts RPC program numbers into ii ucf 3.0025+nmu2 Update Configuration File: preserv Versions of packages nfs-common recommends: ii python2.6.6-14 interactive high-level object-orie nfs-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110618082612.7753.53537.report...@tom.computers.lan
Bug#630566: linux-source-2.6.39: 2.6.39-2 : bluetooth broken
Am Mittwoch, 15. Juni 2011, 13:26:50 schrieben Sie: > > did you try 3.0-rc2 in experimental? > > thanks I tried it now and the problem is the same (same error). btw. I had trouble to compile the 3.0 kernel. I needed to remove the modules apm and lguest. It also uses much more ram than 2.6.39. Probably it needs an updated kernel-package and some more work but that has nothing to do with the bluetooth problem of course. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201106160154.50646.alma...@coole-files.de
Bug#630566: linux-source-2.6.39: 2.6.39-2 : bluetooth broken
Package: linux-source-2.6.39 Version: 2.6.39-2 Severity: important I have tried 3 different dongles and 2 versions of bluez. This worked in 2.6.38. lsusb: Bus 005 Device 003: ID 0db0:1967 Micro Star International Bluetooth Dongle dmesg: Bluetooth: Generic Bluetooth USB driver ver 0.6 usbcore: registered new interface driver btusb usb 5-2: new full speed USB device number 3 using uhci_hcd usb 5-2: New USB device found, idVendor=0db0, idProduct=1967 usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 hciconfig -a: hci0: Type: BR/EDR Bus: USB BD Address: 00:0C:76:AC:2D:F1 ACL MTU: 192:8 SCO MTU: 64:8 DOWN RX bytes:718 acl:0 sco:0 events:25 errors:0 TX bytes:108 acl:0 sco:0 commands:24 errors:0 Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT hciconfig hci0 up: Can't init device hci0: Invalid argument (22) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-2b (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-source-2.6.39 depends on: ii binutils 2.21.51.20110523-1 The GNU assembler, linker and bina ii bzip2 1.0.5-6high-quality block-sorting file co Versions of packages linux-source-2.6.39 recommends: ii gcc 4:4.6.0-5 The GNU C compiler ii libc6-dev [libc-dev] 2.13-4 Embedded GNU C Library: Developmen ii make 3.81-8.1 An utility for Directing compilati Versions of packages linux-source-2.6.39 suggests: ii kernel-package 12.036+nmu1 A utility for building Linux kerne ii libncurses5-dev [ncurses-dev 5.9-1 developer's libraries for ncurses ii libqt3-mt-dev3:3.3.8b-8 Qt development files (Threaded) -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110615091637.3944.90345.report...@tequila.fritz.box
Bug#620088: nfs-common: Problem also on amd64
Package: nfs-common Version: 1:1.2.3-1 Followup-For: Bug #620088 I'm also having the same problem on amd64. When I try to start the daemons I get the following: Stopping NFS common utilities: gssd idmapd statd. Starting NFS common utilities: statd failed! After adding some options to rpc.statd to enable verbose error logging I get the following messages: Starting NFS common utilities: statdrpc.statd: Version 1.2.3 starting rpc.statd: Flags: No-Daemon Log-STDERR TI-RPC sm-notify: Version 1.2.3 starting sm-notify: Already notifying clients; Exiting! rpc.statd: Local NSM state number: 3 rpc.statd: Failed to unregister program 100024, version 1 rpc.statd: Effective UID, GID: 102, 0 rpc.statd: Failed to register (statd, 1, udp) rpc.statd: Failed to register (statd, 1, tcp) rpc.statd: Failed to register (statd, 1, udp6) rpc.statd: Failed to register (statd, 1, tcp6) rpc.statd: failed to create RPC listeners, exiting failed! -- Package-specific info: -- rpcinfo -- program vers proto port 102 tcp111 portmapper 102 udp111 portmapper -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS="-dF" RPCGSSDOPTS="" NEED_IDMAPD=yes NEED_GSSD=yes -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = THUIS.LAN [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.112+nmu2 add and remove users and groups ii initscripts 2.88dsf-13.1scripts for initializing and shutt ii libc62.11.2-13 Embedded GNU C Library: Shared lib ii libcap2 1:2.20-1support for getting/setting POSIX. ii libcomerr2 1.41.12-2 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.9+dfsg-1 MIT Kerberos runtime libraries - k ii libgssglue1 0.2-2 mechanism-switch gssapi library ii libk5crypto3 1.9+dfsg-1 MIT Kerberos runtime libraries - C ii libkrb5-31.9+dfsg-1 MIT Kerberos runtime libraries ii libnfsidmap2 0.24-1 An nfs idmapping library ii libtirpc10.2.1-1 transport-independent RPC library ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii netbase 4.45Basic TCP/IP networking system ii portmap 6.0.0-3 RPC port mapper ii ucf 3.0025+nmu1 Update Configuration File: preserv Versions of packages nfs-common recommends: ii python2.6.6-12 interactive high-level object-orie nfs-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110330162727.3290.5624.report...@tom.computers.lan
Bug#619052: rpc.gssd: double free or corruption
Package: nfs-common Version: 1:1.2.2-5 Severity: important When installing nfs-common from sid I reccieve the following stacktrace at every start of the package: * Starting NFS common utilities * *** glibc detected *** /usr/sbin/rpc.gssd: double free or corruption * (!prev): 0x020910d0 *** === Backtrace: = /lib/libc.so.6(+0x71ab6)[0x7f7df3515ab6] /lib/libc.so.6(cfree+0x6c)[0x7f7df351a82c] /lib/libc.so.6(fclose+0x14d)[0x7f7df35069fd] /usr/lib/libgssglue.so.1(+0x46a0)[0x7f7df43426a0] /usr/lib/libgssglue.so.1(+0x47b7)[0x7f7df43427b7] /usr/lib/libgssglue.so.1(gss_indicate_mechs+0x2d)[0x7f7df434218d] /usr/sbin/rpc.gssd[0x403f4e] /usr/sbin/rpc.gssd[0x404368] /lib/libc.so.6(__libc_start_main+0xfd)[0x7f7df34c2c4d] /usr/sbin/rpc.gssd[0x4036f9] === Memory map: 0040-0040e000 r-xp fe:01 83370 /usr/sbin/rpc.gssd 0060e000-00612000 rw-p e000 fe:01 83370 /usr/sbin/rpc.gssd 00612000-00614000 rw-p 00:00 0 02091000-020b2000 rw-p 00:00 0 [heap] 7f7dec00-7f7dec021000 rw-p 00:00 0 7f7dec021000-7f7df000 ---p 00:00 0 7f7df2a52000-7f7df2a67000 r-xp 08:15 561944 /lib/libgcc_s.so.1 7f7df2a67000-7f7df2c67000 ---p 00015000 08:15 561944 /lib/libgcc_s.so.1 7f7df2c67000-7f7df2c68000 rw-p 00015000 08:15 561944 /lib/libgcc_s.so.1 7f7df2c68000-7f7df2c7f000 r-xp 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2c7f000-7f7df2e7e000 ---p 00017000 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2e7e000-7f7df2e7f000 r--p 00016000 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2e7f000-7f7df2e8 rw-p 00017000 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2e8-7f7df2e84000 rw-p 00:00 0 7f7df2e84000-7f7df2e97000 r-xp 08:15 561995 /lib/libresolv-2.11.2.so 7f7df2e97000-7f7df3096000 ---p 00013000 08:15 561995 /lib/libresolv-2.11.2.so 7f7df3096000-7f7df3097000 r--p 00012000 08:15 561995 /lib/libresolv-2.11.2.so 7f7df3097000-7f7df3098000 rw-p 00013000 08:15 561995 /lib/libresolv-2.11.2.so 7f7df3098000-7f7df309a000 rw-p 00:00 0 7f7df309a000-7f7df309c000 r-xp 08:15 561964 /lib/libkeyutils.so.1.3 7f7df309c000-7f7df329b000 ---p 2000 08:15 561964 /lib/libkeyutils.so.1.3 7f7df329b000-7f7df329c000 rw-p 1000 08:15 561964 /lib/libkeyutils.so.1.3 7f7df329c000-7f7df32a3000 r-xp fe:01 50300 /usr/lib/libkrb5support.so.0.1 7f7df32a3000-7f7df34a3000 ---p 7000 fe:01 50300 /usr/lib/libkrb5support.so.0.1 7f7df34a3000-7f7df34a4000 rw-p 7000 fe:01 50300 /usr/lib/libkrb5support.so.0.1 7f7df34a4000-7f7df35fc000 r-xp 08:15 562191 /lib/libc-2.11.2.so 7f7df35fc000-7f7df37fc000 ---p 00158000 08:15 562191 /lib/libc-2.11.2.so 7f7df37fc000-7f7df380 r--p 00158000 08:15 562191 /lib/libc-2.11.2.so 7f7df380-7f7df3801000 rw-p 0015c000 08:15 562191 /lib/libc-2.11.2.so 7f7df3801000-7f7df3806000 rw-p 00:00 0 7f7df3806000-7f7df3809000 r-xp 08:15 562017 /lib/libcom_err.so.2.1 7f7df3809000-7f7df3a08000 ---p 3000 08:15 562017 /lib/libcom_err.so.2.1 7f7df3a08000-7f7df3a09000 rw-p 2000 08:15 562017 /lib/libcom_err.so.2.1 7f7df3a09000-7f7df3a31000 r-xp fe:01 49582 /usr/lib/libk5crypto.so.3.1 7f7df3a31000-7f7df3c3 ---p 00028000 fe:01 49582 /usr/lib/libk5crypto.so.3.1 7f7df3c3-7f7df3c32000 rw-p 00027000 fe:01 49582 /usr/lib/libk5crypto.so.3.1 7f7df3c32000-7f7df3cf4000 r-xp fe:01 49613 /usr/lib/libkrb5.so.3.3 7f7df3cf4000-7f7df3ef3000 ---p 000c2000 fe:01 49613 /usr/lib/libkrb5.so.3.3 7f7df3ef3000-7f7df3efe000 rw-p 000c1000 fe:01 49613 /usr/lib/libkrb5.so.3.3 7f7df3efe000-7f7df3f38000 r-xp fe:01 49585 /usr/lib/libgssapi_krb5.so.2.2 7f7df3f38000-7f7df4137000 ---p 0003a000 fe:01 49585 /usr/lib/libgssapi_krb5.so.2.2 7f7df4137000-7f7df413a000 rw-p 00039000 fe:01 49585 /usr/lib/libgssapi_krb5.so.2.2 7f7df413a000-7f7df413c000 r-xp 08:15 562187 /lib/libdl-2.11.2.so 7f7df413c000-7f7df433c000 ---p 2000 08:15 562187 /lib/libdl-2.11.2.so 7f7df433c000-7f7df433d000 r--p 2000 08:15 562187 /lib/libdl-2.11.2.so 7f7df433d000-7f7df433e000 rw-p 3000 08:15 562187 /lib/libdl-2.11.2.so 7f7df433e000-7f7df4347000 r-xp fe:01 50870 /usr/lib/libgssglue.so.1.0.0 7f7df4347000-7f7df4546000 ---p 9000 fe:01 50870 /usr/lib/libgssglue.so.1.0.0 7f7df4546000-7f7df4547000 rw-p 8000 fe:01 50870 /usr/lib/libgssglue.so.1.0.0 7f7df4547000-7f7df4556000 r-xp fe:01 58365 /usr/lib/librpcsecgss.so.3.0.0 7f7df4556000-7f7df4755000 ---p f000 fe:01 58365 /usr/lib/librpcsecgss.so.3.0.0 7f7df4755000-7f7df4756000 rw-p e000 fe:01 58365 /usr/lib/librpcsecgss.so.3.0.0 7f7df4756000-7f7df4774000 r-xp 08:15 562300 /lib/ld-2.11.2.so 7f7df494a000-7f7df4951000 rw-p 00:00 0 7f7df4971000-7f7df4973000 rw-p 00:00 0 7f7df4973000-7f7df4974000 r--p 0001d000 08:15 562300 /lib/ld-2.11.2.so 7f7df4974000-7f7df4975000 rw-p 000
Bug#612002: Starting NFS common utilities failed
On Feb 14, 2011, at 9:57 PM, Ben Hutchings wrote: On Fri, 2011-02-04 at 09:57 -0500, Tong Sun wrote: >> $ grep portmap /etc/runlevel.conf || echo not found >> not found > What is runlevel.conf? The configuration file (or one of configuration files, I don't use it) of file-rc (alternative to sysv-rc). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTikLSYe9Q8ur=7hzf7fobblsmfxcpkdt3a0bn...@mail.gmail.com
Bug#610953: nfs-common: Upgrade from Lenny to Squeeze prevents mounting previously set up nfs exports
Package: nfs-common Version: 1:1.2.2-4 Severity: normal See bug 609487 for the origin of this bug report. Upgrading from Lenny to Squeeze prevents mounting previously set up nfs exports because nfs defaults to nfsv4 and the idmap domain isn't set up on the upgraded box. -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) 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 nfs-common depends on: ii adduser 3.112+nmu2 add and remove users and groups ii initscripts 2.88dsf-13.1 scripts for initializing and shutt ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3 support for getting/setting POSIX. ii libcomerr2 1.41.12-2common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-21.8.3+dfsg-4 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4mechanism-switch gssapi library ii libk5crypto31.8.3+dfsg-4 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4 MIT Kerberos runtime libraries ii libnfsidmap20.23-2 An nfs idmapping library ii librpcsecgss3 0.19-2 allows secure rpc communication us ii libwrap07.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii netbase 4.44 Basic TCP/IP networking system ii portmap 6.0.0-2 RPC port mapper ii ucf 3.0025+nmu1 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110124110109.1198.46909.reportbug@debbox
Bug#610245: Fwd: tc commands to reproduce the problem
Original Message Subject: tc commands to reproduce the problem Date: Sat, 22 Jan 2011 16:48:22 -0800 From: Tom Eastep To: 610...@bugs.debian.org CC: Roberto C. Sanchez Attached are the commands. In this test case, 6300kbit was configured for both ingress policing and for the TBF on outout. Downloads were close by 6.3 mbit while uploads were .32 mbit. HTH, -Tom -- Tom Eastep\ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \ tc qdisc del dev eth0 root tc qdisc del dev eth0 ingress tc qdisc add dev eth0 handle : ingress tc filter add dev eth0 parent : protocol all prio 10 u32 match ip src 0.0.0.0/0 police rate 6300kbit burst 100kb drop flowid :1 tc qdisc add dev eth0 root handle 1: tbf rate 6300kbit burst 100kb latency 200ms tc qdisc add dev eth0 parent 1: handle 101: prio bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 tc qdisc add dev eth0 parent 101:1 handle 1011: sfq quantum 1875 limit 127 perturb 10 tc filter add dev eth0 protocol all parent 101: handle 1 fw classid 101:1 tc qdisc add dev eth0 parent 101:2 handle 1012: sfq quantum 1875 limit 127 perturb 10 tc filter add dev eth0 protocol all parent 101: handle 2 fw classid 101:2 tc qdisc add dev eth0 parent 101:3 handle 1013: sfq quantum 1875 limit 127 perturb 10 tc filter add dev eth0 protocol all parent 101: handle 3 fw classid 101:3 signature.asc Description: OpenPGP digital signature
Bug#610245: tc commands to reproduce the problem
Attached are the commands. In this test case, 6300kbit was configured for both ingress policing and for the TBF on outout. Downloads were close by 6.3 mbit while uploads were .32 mbit. HTH, -Tom -- Tom Eastep\ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \ tc qdisc del dev eth0 root tc qdisc del dev eth0 ingress tc qdisc add dev eth0 handle : ingress tc filter add dev eth0 parent : protocol all prio 10 u32 match ip src 0.0.0.0/0 police rate 6300kbit burst 100kb drop flowid :1 tc qdisc add dev eth0 root handle 1: tbf rate 6300kbit burst 100kb latency 200ms tc qdisc add dev eth0 parent 1: handle 101: prio bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 tc qdisc add dev eth0 parent 101:1 handle 1011: sfq quantum 1875 limit 127 perturb 10 tc filter add dev eth0 protocol all parent 101: handle 1 fw classid 101:1 tc qdisc add dev eth0 parent 101:2 handle 1012: sfq quantum 1875 limit 127 perturb 10 tc filter add dev eth0 protocol all parent 101: handle 2 fw classid 101:2 tc qdisc add dev eth0 parent 101:3 handle 1013: sfq quantum 1875 limit 127 perturb 10 tc filter add dev eth0 protocol all parent 101: handle 3 fw classid 101:3 signature.asc Description: OpenPGP digital signature
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/27/2010 12:08 PM, Dmitry Torokhov wrote: > On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote: >> Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit : >> Sure, but dumpkeys shows the table from scancodes to keycodes, not from >> input events to scancodes. > > I am just wondering if some of the translation is leaking even though > the keyboard is in raw mode... > > OK, scratch that... Are there any other input devices? Anything > connected via uinput and listening? What does /proc/bus/input/devices > show? Maybe if Tom could compile and load evbug module it would show us > where the additional events are coming form, becaus ethey surely are not > generated by the keyboard itself (otherwise we'd have seen them in > evtest output for that device). Minor correction to what I wrote earlier about the scroll wheel. That is actually my mouse. It says Dell but it's really made by Logitech. I just tried the console and what's funny is Favorites actually works as Capslock and Previous works as right-shift. X has the opposite problem. In case anyone missed it, Debian Stable works fine with this keyboard. The keyboard on the working Stable machine is exactly the same (same usb id's). I'm not familiar with the input stack, but in case it is a kernel problem, the difference is: Stable dist, working: Linux zero 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64 GNU/Linux Testing dist, not working: Linux tom 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux /proc/bus/input/devices on the problem machine: I: Bus=0017 Vendor=0001 Product=0001 Version=0100 N: Name="Macintosh mouse button emulation" P: Phys= S: Sysfs=/devices/virtual/input/input0 U: Uniq= H: Handlers=mouse0 event0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 I: Bus=0003 Vendor=046d Product=c016 Version=0110 N: Name="Logitech Optical USB Mouse" P: Phys=usb-:00:13.0-1/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-1/5-1:1.0/input/input1 U: Uniq= H: Handlers=mouse1 event1 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=3 B: KEY=10 0 I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name="PC Speaker" P: Phys=isa0061/input0 S: Sysfs=/devices/platform/pcspkr/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=40001 B: SND=6 I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name="Logitech Logitech USB Keyboard" P: Phys=usb-:00:13.0-2/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9 U: Uniq= H: Handlers=kbd event2 B: EV=120013 B: KEY=10007 ff8007ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name="Logitech Logitech USB Keyboard" P: Phys=usb-:00:13.0-2/input1 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10 U: Uniq= H: Handlers=kbd mouse2 event3 B: EV=17 B: KEY=f f840334 60d8fafd01d008 1f 0 B: REL=103 B: MSC=10 -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc870bb.2050...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 10 -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc7426c.8040...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/25/2010 02:25 PM, Dmitry Torokhov wrote: On Mon, Oct 25, 2010 at 08:03:20PM +0200, Samuel Thibault wrote: Could you also post results when pressing the "favorite" and the "prev" internet keys of your keyboard? Actually, if these are all the events that evtest reports when pressing CapsLock then I am confused where the "favorites" ghost press is coming from... They are not emitted by the device. Do you have a funky keymap loaded somewhere? Also, was 'showkey -s' issued while in X or in the text console? Console. I just ran it now and caps-lock has the same codes as "favorites" and right-shift has the same as "previous". So it's not an X problem. -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc6eab5.9020...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/25/2010 02:03 PM, Samuel Thibault wrote: > Tom Vier, le Mon 25 Oct 2010 09:37:26 -0400, a écrit : >> On 10/25/2010 12:50 AM, Dmitry Torokhov wrote: >>> On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: >>>> The short story is: Tom's keyboard sends all that when he presses caps >>>> lock: >>>> >>>> press: 0x3a 0xe0 0x66 >>>> repeat: 0x3a >>>> release: 0xba 0xe0 0xe6 >>>> >>>> 0xe0 0x66 happens to be the "favorites" key on his keyboard with >>>> internet navigation keys. I thus believe there's a bug in his keyboard >>>> that needs to be filtered at the kernel level. >>>> >>>> The long story can be read on >>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089 >>> >>> Hmm, the question is whether the real "favorites" key send the same >>> usage and the fake one after caps lock. Any chance Tom could locate >>> evtest utility and see what MSC_SCAN events being emitted? >> >> Sure. Here's caps-lock: >> >> Event: time 1288013671.633008, -- Report Sync >> Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039 >> Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1 >> Event: time 1288013674.171862, -- Report Sync >> Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1 >> Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039 >> Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0 >> Event: time 1288013674.299593, -- Report Sync >> >> >> Right-shift (the other problem key): >> >> Event: time 1288013798.388025, -- Report Sync >> Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5 >> Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1 >> Event: time 1288013800.742142, -- Report Sync >> Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5 >> Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0 >> Event: time 1288013800.861824, -- Report Sync > > Could you also post results when pressing the "favorite" and the "prev" > internet keys of your keyboard? > > Samuel It's returning the same codes. Maybe what's going on here is that they never worked back in Stable and someone tried to fix those keys, not realizing they're the same codes as capslock and right-shift. I'll have to test it on my Stable machine tonight to see if those keys work or not, tho. Favorites: Event: time 1288041423.048839, -- Report Sync Event: time 1288041425.068704, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288041425.068742, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288041425.068754, -- Report Sync Event: time 1288041425.069105, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288041425.260313, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288041425.260343, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288041425.260347, -- Report Sync Previous: Event: time 1288041443.531447, -- Report Sync Event: time 1288041445.318877, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288041445.318915, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288041445.318932, -- Report Sync Event: time 1288041445.438567, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288041445.438606, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288041445.438629, -- Report Sync -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc6e9d8.8010...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/25/2010 12:50 AM, Dmitry Torokhov wrote: On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: The short story is: Tom's keyboard sends all that when he presses caps lock: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 0xe0 0x66 happens to be the "favorites" key on his keyboard with internet navigation keys. I thus believe there's a bug in his keyboard that needs to be filtered at the kernel level. The long story can be read on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089 Hmm, the question is whether the real "favorites" key send the same usage and the fake one after caps lock. Any chance Tom could locate evtest utility and see what MSC_SCAN events being emitted? Thanks. Sure. Here's caps-lock: Event: time 1288013671.633008, -- Report Sync Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288013674.171862, -- Report Sync Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288013674.299593, -- Report Sync Right-shift (the other problem key): Event: time 1288013798.388025, -- Report Sync Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288013800.742142, -- Report Sync Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288013800.861824, ------ Report Sync -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc58816.3090...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
-- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk On 09/07/2010 12:32 PM, Tom Vier wrote: On 09/03/2010 07:55 PM, Samuel Thibault wrote: Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : The model name is logimel, which is set in both /etc/default/keyboard and /etc/X11/xorg.conf. Which explains why Xorg has the behavior you describe: the logimel model includes the logitech base, which includes the common navigation keys, which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66. Do you actually have navigation keys on your keyboard? I'm afraid we'll just have to blacklist it in the usb driver according to the usb ID. Samuel I have bunch of extra keys. 8) It's one of those "internet" keyboards with keys for: email sms webcam itouch search shipping home favorites, plus volume, track skip, play/pause, record. Here's xev from Stable. It looks like in Testing that some of the extra key codes that show up in showkey are getting interpreted as additional key presses in Testing's xorg but not Stable's. caps lock, then right shift KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9213660, (161,-9), root:(337,884), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False PropertyNotify event, serial 33, synthetic NO, window 0x2a1, atom 0x11c (XKLAVIER_STATE), time 9213663, state PropertyNewValue KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9213780, (161,-9), root:(337,884), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9217955, (161,-9), root:(337,884), state 0x10, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False PropertyNotify event, serial 33, synthetic NO, window 0x2a1, atom 0x11c (XKLAVIER_STATE), time 9217958, state PropertyNewValue KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9218091, (161,-9), root:(337,884), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9220699, (161,-9), root:(337,884), state 0x12, keycode 36 (keysym 0xff0d, Return), same_screen YES, " XLookupString gives 1 bytes: (0d) " " XmbLookupString gives 1 bytes: (0d) " XFilterEvent returns: False KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9220835, (161,-9), root:(337,884), state 0x12, keycode 36 (keysym 0xff0d, Return), same_screen YES, " XLookupString gives 1 bytes: (0d) " XFilterEvent returns: False -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c8e6861.1070...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 09/03/2010 07:55 PM, Samuel Thibault wrote: Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : The model name is logimel, which is set in both /etc/default/keyboard and /etc/X11/xorg.conf. Which explains why Xorg has the behavior you describe: the logimel model includes the logitech base, which includes the common navigation keys, which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66. Do you actually have navigation keys on your keyboard? I'm afraid we'll just have to blacklist it in the usb driver according to the usb ID. Samuel I have bunch of extra keys. 8) It's one of those "internet" keyboards with keys for: email sms webcam itouch search shipping home favorites, plus volume, track skip, play/pause, record. -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c866913.3030...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 09/03/2010 07:45 PM, Samuel Thibault wrote: Tom Vier, le Fri 03 Sep 2010 16:35:47 -0400, a écrit : On 09/02/2010 03:46 PM, Samuel Thibault wrote: Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? Yes. I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Stable (2.6.26) which worked fine gives the same as Testing (2.6.32): When you say "Stable", you mean both kernel and Xorg? Could you also run xev on your stable box? I mean the debian stable release. I'll try it on my home machine, which has the same logitech keyboard. press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 ...which makes me think it's an xorg problem, but I'm not familiar with how the whole keyboard stack works. It's a big mess :) I wonder why the logitech generates so many codes. It looks to me like a keyboard bug. Do you see any pattern, e.g. does the left shift key produce one too? Do the keys which do produce extra scancodes form any particular shape on the keyboard? The only problem keys are caps-lock and right-shift, both upon key press. Such bug should probably be fixed in the kernel, just like it is already in atkbd.c for some keyboards. Samuel Showkey looks almost identical between kernels tho. I'll check my machine at home and see what xev shows. -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c866828.7040...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 09/02/2010 03:46 PM, Samuel Thibault wrote: Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? Yes. I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Samuel Stable (2.6.26) which worked fine gives the same as Testing (2.6.32): press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 ...which makes me think it's an xorg problem, but I'm not familiar with how the whole keyboard stack works. I tried a different usb keyboard (a Dell) under Testing and it works normally with iceweasel: press: 0x3a repeat: 0x3a release: 0x3b I wonder why the logitech generates so many codes. -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c815c23.2070...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 08/23/2010 11:59 AM, Samuel Thibault wrote: forcemerge 594089 593742 reassign 594089 linux-2.6 retitle 594089 caps lock keyboard code problem thanks Hello, Please do not submit another report for the same issue, just reassign. Sorry, didn't know I could. Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : KeyRelease event, serial 105, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729143, (166,-8), root:(190,128), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 106, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729166, (166,-8), root:(190,128), state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 106, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729166, (166,-8), root:(190,128), state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 106, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729168, (166,-8), root:(190,128), state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False That's very odd. I guess this is due either to an upgrade of linux-2.6 or an upgrade of xserver-xorg-input-evdev. At this stage I'd rather think about linux-2.6. Could you check in the linux console (without X) what happens with showkey -s ? (here it shows 0x3a 0xba) Samuel It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: xev: KeyRelease event, serial 35, synthetic NO, window 0x481, root 0x110, subw 0x0, time 876874940, (169,-12), root:(199,150), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 35, synthetic NO, window 0x481, root 0x110, subw 0x0, time 876874941, (169,-12), root:(199,150), state 0x10, keycode 166 (keysym 0x1008ff26, XF86Back), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea -- Tom Vier Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c7ff6f5.3080...@triadsys.com
Bug#579262: /usr/sbin/mkinitramfs: 141: mktemp: not found
On 26/04/10 15:32, maximilian attems wrote: coreutils is priority required, your box looks broken. please investigate how it came to missing mktemp. thanks There was an installed copy of coreutils, but version 6.10-6 which doesn't contain mktemp. The issue is partly because this is a mixed release box, with some stable, testing and unstable packages, but this is still an issue that should be dealt with (partially because it may cause weird upgrade issues for some users I suspect). Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bd5a714.7030...@tevp.net
Bug#579262: /usr/sbin/mkinitramfs: 141: mktemp: not found
Package: initramfs-tools Version: 0.93.4 Severity: normal mkinitramfs needs mktemp, but initramfs-tools doesn't have a dependency on mktemp or coreutils >=7.4-1. mktemp is no longer a "Priority: required" package. As a result of this I get the following problem. palf...@missfun:[~] sudo dpkg -a --configure Setting up initramfs-tools (0.93.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.32-3-amd64 /usr/sbin/mkinitramfs: 141: mktemp: not found update-initramfs: failed for /boot/initrd.img-2.6.32-3-amd64 dpkg: subprocess installed post-installation script returned error exit status 1 -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=//vmlinuz-2.6.32-3-amd64 root=/dev/mapper/missfun-root ro quiet -- /proc/filesystems ext3 ext2 fuseblk ext4 reiserfs xfs jfs msdos vfat ntfs hfs hfsplus ufs udf iso9660 -- lsmod Module Size Used by parport_pc 18855 1 vboxnetadp 4225 0 vboxnetflt 9978 0 vboxdrv 1710854 3 vboxnetadp,vboxnetflt nls_cp437 5817 1 ppdev 5030 0 lp 7462 0 parport27938 3 parport_pc,ppdev,lp usb_storage38521 1 isofs 27480 0 udf66644 0 crc_itu_t 1307 1 udf nls_utf81208 1 ufs56490 0 hfsplus65270 0 hfs37439 0 ntfs 162860 0 vfat7884 1 msdos 6202 0 fat40054 2 vfat,msdos jfs 140051 0 xfs 435388 0 exportfs3170 1 xfs reiserfs 194010 0 ext4 285099 0 jbd2 66887 1 ext4 crc16 1319 1 ext4 cpufreq_conservative 5162 0 cpufreq_powersave902 0 cpufreq_userspace 1992 0 cpufreq_stats 2659 0 fuse 50110 3 ext2 52969 1 loop 11783 0 snd_hda_codec_analog64530 1 snd_hda_intel 19619 2 snd_hda_codec 54212 2 snd_hda_codec_analog,snd_hda_intel snd_hwdep 5364 1 snd_hda_codec snd_pcm60615 2 snd_hda_intel,snd_hda_codec snd_timer 15502 1 snd_pcm usbhid 33132 0 hid62825 1 usbhid snd46350 10 snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 4598 1 snd psmouse49505 0 snd_page_alloc 6217 2 snd_hda_intel,snd_pcm dcdbas 5048 0 i2c_i8017798 0 pcspkr 1699 0 serio_raw 3752 0 evdev 7336 8 processor 30215 0 ext3 106486 1 jbd37053 1 ext3 mbcache 4970 3 ext4,ext2,ext3 dm_mod 53674 6 uhci_hcd 18505 0 sg 18728 0 sr_mod 12602 0 sd_mod 29689 5 cdrom 29399 1 sr_mod crc_t10dif 1276 1 sd_mod ata_generic 2983 0 i915 248774 5 drm_kms_helper 18899 1 i915 ahci 32038 2 drm 137190 6 i915,drm_kms_helper i2c_algo_bit4225 1 i915 libata132183 2 ata_generic,ahci scsi_mod 121925 5 usb_storage,sg,sr_mod,sd_mod,libata i2c_core 15584 4 i2c_i801,i915,drm,i2c_algo_bit video 17445 1 i915 button 4634 1 i915 ehci_hcd 30706 0 output 1692 1 video e1000e109919 0 usbcore 121703 5 usb_storage,usbhid,uhci_hcd,ehci_hcd nls_base6377 11 nls_cp437,isofs,udf,nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore ide_pci_generic 2788 0 ide_core 76850 1 ide_pci_generic intel_agp 25593 1 thermal11674 0 fan 3346 0 thermal_sys11878 4 processor,video,thermal,fan -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/4 CPU cores) Locale
Bug#576601: closed by Ben Hutchings (Re: Bug#576601: linux-image-2.6.18-6-686: aptitude install fails. complains of error status 1 returned from preinst script)
Am trying to upgrade to lenny as per instructions on debian.org. http://www.debian.org/releases/lenny/i386/release-notes/ch-about.en.html instructs "Please note that we only support and document upgrading from the previous release of Debian (in this case, the upgrade from 4.0). If you need to upgrade from older releases, we suggest you read previous editions of the release notes and upgrade to 4.0 first." -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/s2g6d94ef7c1004051731r618640e9l656ff8675f3d4...@mail.gmail.com
Bug#576601: linux-image-2.6.18-6-686: aptitude install fails. complains of error status 1 returned from preinst script
Package: linux-image-2.6.18-6-686 Severity: important tried and failed to find preinst script even in source package. tried 486 version. same error. Thank you for your time -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.19 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100405221818.6576.85049.report...@linbox
Bug#521944: linux-image-2.6.29-1-686: Excessive number of interrupts from hrtimer_start_expires
On 25 February 2010 18:15, Moritz Muehlenhoff wrote: > Did you report this at http://bugzilla.kernel.org ? Haven't yet. Somewhere on the todo list... Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/243a9cc1002251016ya4a1e22oa2b84d229aab0...@mail.gmail.com
Bug#521944: linux-image-2.6.29-1-686: Excessive number of interrupts from hrtimer_start_expires
On 2 February 2010 21:16, maximilian attems wrote:
> Squeeze will release with 2.6.32 can anyone of you still
> reproduce this?
>
> also please make sure to use latest powertop, aka
> ii powertop 1.13~pre201001 Linux tool to find out what is using power
palf...@drone:[~] dpkg -l |grep powertop
ii powertop 1.13~pre20100125-1
Linux tool to find out what is using power
o
palf...@drone:[~] uname -a
Linux drone 2.6.32-1-686 #1 SMP Mon Feb 1 01:37:26 UTC 2010 i686 GNU/Linux
Attached is powertop.log ('powertop -d') and top.log('top -b -n 1')
As you can see, the major wakeup is still "Load balancing tick", which
I'm guessing is a translated name for hrtimer_start_expires? I think
the ACPI estimate of 1.1W is a little off though...
So, doesn't look fixed. I'm currently at FOSDEM if anyone with more
knowledge wants to borrow my laptop to do more debugging on this.
Tom
PowerTOP 1.12 (C) 2007, 2008 Intel Corporation
Collecting data for 15 seconds
Cn Avg residency
C0 (cpu running)( 6.1%)
polling 0.0ms ( 0.0%)
C1 halt 0.0ms ( 0.0%)
C2 7.4ms (20.7%)
C3 5.2ms (73.2%)
P-states (frequencies)
1.60 Ghz 4.2%
1333 Mhz 0.6%
1066 Mhz 0.1%
800 Mhz95.0%
Wakeups-from-idle per second : 168.0 interval: 15.0s
Power usage (ACPI estimate): 1.1W (6.5 hours)
Top causes for wakeups:
46.8% ( 85.1) [kernel scheduler] Load balancing tick
23.4% ( 42.7) [uhci_hcd:usb4, ath]
7.7% ( 13.9) avahi-daemon
7.3% ( 13.3) chromium-browse
3.6% ( 6.6) [ata_piix]
1.7% ( 3.1) Xorg
1.5% ( 2.7) [kernel core] hrtimer_start (tick_sched_timer)
1.2% ( 2.1) [acpi]
1.2% ( 2.1) [ehci_hcd:usb1, uhci_hcd:usb2, HDA Intel, i...@pci::00:02.0]
1.1% ( 2.0) multiload-apple
0.9% ( 1.6) gnome-terminal
0.7% ( 1.2) nautilus
0.5% ( 1.0) ntpd
0.5% ( 1.0) cpufreq-applet
0.5% ( 0.9) lighttpd
0.2% ( 0.4) NetworkManager
0.1% ( 0.3) PS/2 keyboard/mouse/touchpad interrupt
0.1% ( 0.3) gnome-settings-
0.1% ( 0.3) [kernel core] enqueue_task_rt (sched_rt_period_timer)
0.1% ( 0.2) sleep
0.1% ( 0.2) gnome-panel
0.1% ( 0.2) init
0.1% ( 0.1) mono
0.1% ( 0.1) ssh-agent
0.1% ( 0.1) gnome-power-man
0.1% ( 0.1) hald
0.0% ( 0.1) metacity
0.0% ( 0.1) [kernel core] mod_timer (fib6_gc_timer_cb)
0.0% ( 0.1) rsyslogd
0.0% ( 0.1) kblockd/1
0.0% ( 0.1) [kernel core] mod_timer (inet_twdr_hangman)
Suggestion: Enable wireless power saving mode by executing the following command:
iwconfig wlan0 power timeout 500ms
This will sacrifice network performance slightly to save power.
Recent USB suspend statistics
Active Device name
0.0% USB device 1-5 : USB 2.0 Camera (Sonix Technology Co., Ltd.)
0.0% USB device usb5 : UHCI Host Controller (Linux 2.6.32-1-686 uhci_hcd)
0.0% USB device usb4 : UHCI Host Controller (Linux 2.6.32-1-686 uhci_hcd)
0.0% USB device usb3 : UHCI Host Controller (Linux 2.6.32-1-686 uhci_hcd)
0.0% USB device usb2 : UHCI Host Controller (Linux 2.6.32-1-686 uhci_hcd)
0.0% USB device usb1 : EHCI Host Controller (Linux 2.6.32-1-686 ehci_hcd)
Recent audio activity statistics
Active Device name
Recent SATA AHCI link activity statistics
Active Partial Slumber Device name
top - 09:24:47 up 5 min, 2 users, load average: 0.31, 0.50, 0.27
Tasks: 132 total, 1 running, 131 sleeping, 0 stopped, 0 zombie
Cpu(s): 12.4%us, 6.3%sy, 0.0%ni, 68.3%id, 12.3%wa, 0.1%hi, 0.4%si, 0.0%st
Mem: 1022564k total, 412120k used, 610444k free,21788k buffers
Swap: 1052248k total,0k used, 1052248k free, 236704k cached
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
2354 root 20 0 310m 23m 19m S 11 2.4 0:16.70 Xorg
2562 palfrey 20 0 21588 10m 8780 S4 1.0 0:01.61 metacity
2589 palfrey 20 0 45736 17m 13m S4 1.8 0:04.65 gnome-panel
3666 palfrey 20 0 2444 1060 792 R4 0.1 0:00.04 top
2736 palfrey 20 0 23432 8532 7240 S2 0.8 0:02.18 multiload-apple
3122 palfrey 20 0 226m 48m 22m S2 4.9 0:21.33 chromium-browse
1 root 20 0 2040 712 616 S0 0.1 0:01.12 init
2 root 20 0 000 S0 0.0 0:00.00 kthreadd
3 root
Bug#504805: Boom
[57049.874985] iret exception: [#1] SMP [57049.875210] Modules linked in: xt_physdev iptable_filter ip_tables x_tables inet_diag ipv6 bridge ext3 jbd mbcache drbd cn loop evdev parport_pc parport i2c_i801 i2c_core pcspkr rng_core button intel_agp agpgart shpchp pci_hotplug i82875p_edac edac_core xfs dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod ide_cd_mod cdrom ata_piix ata_generic libata scsi_mod dock piix floppy e1000 ide_pci_generic ide_core ehci_hcd uhci_hcd usbcore thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [57049.877978] [57049.877978] Pid: 4564, comm: blkback.2.sda Not tainted (2.6.26-2-xen-686 #1) [57049.877978] EIP: 0061:[] EFLAGS: 0002 CPU: 0 [57049.877978] EIP is at ioread8+0x16/0x2a [57049.877978] EAX: 0001c850 EBX: 03e8 ECX: 010c2000 EDX: c807 [57049.877978] ESI: ce280028 EDI: ce28 EBP: ce28 ESP: cd1f5b70 [57049.877978] DS: 007b ES: 007b FS: 00d8 GS: SS: 0069 [57049.877978] Process blkback.2.sda (pid: 4564, ti=cd1f4000 task=cd2a5b00 task.ti=cd1f4000) [57049.877978] Stack: d115a26f d115bcc5 0016 ce280078 ce28 ce281404 d115ba67 [57049.877978] ce280078 ce28 d114fe26 ce280078 cef6f180 ce281528 d10dd426 [57049.877978]d11542da ce28 cef6f180 ce281528 d10dd426 ce28 d1156501 d1154024 [57049.877978] Call Trace: [57049.881623] [] ata_sff_check_status+0x8/0xc [libata] [57049.881623] [] ata_sff_tf_load+0xe4/0x137 [libata] [57049.881623] [] ata_sff_qc_issue+0xbf/0x1d8 [libata] [57049.881623] [] ata_qc_issue+0x161/0x1b6 [libata] [57049.881623] [] scsi_done+0x0/0x16 [scsi_mod] [57049.881623] [] ata_scsi_translate+0xd2/0xf7 [libata] [57049.881623] [] scsi_done+0x0/0x16 [scsi_mod] [57049.881623] [] ata_scsi_queuecmd+0x1c7/0x1df [libata] [57049.881623] [] ata_scsi_rw_xlat+0x0/0x1c1 [libata] [57049.881623] [] scsi_dispatch_cmd+0x18b/0x205 [scsi_mod] [57049.881623] [] scsi_request_fn+0x29d/0x3af [scsi_mod] [57049.881623] [] __generic_unplug_device+0x1a/0x1c [57049.881623] [] elv_insert+0x102/0x196 [57049.885625] [] __make_request+0x2fe/0x36e [57049.885625] [] generic_make_request+0x34d/0x37b [57049.885625] [] evtchn_do_upcall+0xfa/0x191 [57049.885625] [] mempool_alloc+0x1c/0xba [57049.885625] [] submit_bio+0xc6/0xcd [57049.885625] [] bio_add_page+0x25/0x2c [57049.885625] [] dispatch_rw_block_io+0x4c5/0x55d [57049.885625] [] local_clock+0x2d/0x6f [57049.885625] [] get_nsec_offset+0xe/0x6a [57049.885625] [] __switch_to+0x376/0x42e [57049.885625] [] get_nsec_offset+0xe/0x6a [57049.885625] [] get_runstate_snapshot+0x69/0xec [57049.885625] [] get_nsec_offset+0xe/0x6a [57049.885625] [] get_runstate_snapshot+0x69/0xec [57049.885625] [] update_curr+0x47/0x79 [57049.885625] [] __dequeue_entity+0x1f/0x71 [57049.885625] [] schedule+0x631/0x6b1 [57049.889626] [] md_wakeup_thread+0x1e/0x20 [md_mod] [57049.889626] [] blkif_schedule+0x39d/0x4b6 [57049.889626] [] blkif_schedule+0x0/0x4b6 [57049.889626] [] kthread+0x38/0x5f [57049.889626] [] kthread+0x0/0x5f [57049.889626] [] kernel_thread_helper+0x7/0x10 [57049.889626] === [57049.889626] Code: c0 81 e2 ff ff 00 00 ee c3 ba 8b a4 32 c0 89 c8 e9 f3 fd ff ff 3d ff ff 03 00 76 04 8a 00 eb 0b 3d 00 00 01 00 76 08 0f b7 d0 ec <0f> b6 c0 c3 ba 9a a4 32 c0 e8 cf fd ff ff b8 ff 00 00 00 c3 3d [57049.893632] EIP: [] ioread8+0x16/0x2a SS:ESP 0069:cd1f5b70 [57049.907810] ---[ end trace 40d498c3636b9d0c ]--- Is there actually any point in sending this, or will it just be ignored... -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#504805: Have another
[905914.620230] iret exception: [#1] SMP [905914.620471] Modules linked in: inet_diag xt_physdev iptable_filter ip_tables x_tables ipv6 bridge ext3 jbd mbcache drbd cn loop evdev parport_pc parport pcspkr i2c_i801 i2c_core rng_core shpchp pci_hotplug button intel_agp agpgart i82875p_edac edac_core xfs dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod ide_cd_mod cdrom ata_piix ata_generic libata scsi_mod piix dock floppy e1000 ide_pci_generic ide_core ehci_hcd uhci_hcd usbcore thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [905914.622302] [905914.622302] Pid: 51, comm: kblockd/0 Not tainted (2.6.26-2-xen-686 #1) [905914.622302] EIP: 0061:[] EFLAGS: 0002 CPU: 0 [905914.622302] EIP is at ioread8+0x16/0x2a [905914.622302] EAX: 0001d000 EBX: ce29 ECX: 010c2000 EDX: d008 [905914.624057] ESI: ce290078 EDI: ce29 EBP: ce291404 ESP: cfcf5f00 [905914.624057] DS: 007b ES: 007b FS: 00d8 GS: SS: 0069 [905914.624057] Process kblockd/0 (pid: 51, ti=cfcf4000 task=cfcd30c0 task.ti=cfcf4000) [905914.624057] Stack: d115a2b3 d115ba7d ce290078 ce29 d114fe26 ce290078 [905914.624057]ceca9e80 ce291528 d10dd426 d11542da ce29 ceca9e80 ce291528 d10dd426 [905914.624057]ce29 d1156501 d1154024 ce028400 ceca9e80 ce028400 ceb3a900 [905914.624057] Call Trace: [905914.624057] [] ata_bmdma_start+0xb/0x1a [libata] [905914.624057] [] ata_sff_qc_issue+0xd5/0x1d8 [libata] [905914.624057] [] ata_qc_issue+0x161/0x1b6 [libata] [905914.624057] [] scsi_done+0x0/0x16 [scsi_mod] [905914.624057] [] ata_scsi_translate+0xd2/0xf7 [libata] [905914.624057] [] scsi_done+0x0/0x16 [scsi_mod] [905914.624057] [] ata_scsi_queuecmd+0x1c7/0x1df [libata] [905914.624057] [] ata_scsi_rw_xlat+0x0/0x1c1 [libata] [905914.628996] [] scsi_dispatch_cmd+0x18b/0x205 [scsi_mod] [905914.628996] [] scsi_request_fn+0x29d/0x3af [scsi_mod] [905914.628996] [] cfq_kick_queue+0x0/0x28 [905914.628996] [] blk_start_queueing+0xe/0x14 [905914.628996] [] cfq_kick_queue+0x19/0x28 [905914.628996] [] run_workqueue+0x9b/0x144 [905914.628996] [] worker_thread+0x0/0xbd [905914.628996] [] worker_thread+0xb3/0xbd [905914.628996] [] autoremove_wake_function+0x0/0x2d [905914.628996] [] kthread+0x38/0x5f [905914.628996] [] kthread+0x0/0x5f [905914.628996] [] kernel_thread_helper+0x7/0x10 [905914.628996] === [905914.628996] Code: c0 81 e2 ff ff 00 00 ee c3 ba 8b a4 32 c0 89 c8 e9 f3 fd ff ff 3d ff ff 03 00 76 04 8a 00 eb 0b 3d 00 00 01 00 76 08 0f b7 d0 ec <0f> b6 c0 c3 ba 9a a4 32 c0 e8 cf fd ff ff b8 ff 00 00 00 c3 3d [905914.632987] EIP: [] ioread8+0x16/0x2a SS:ESP 0069:cfcf5f00 [905914.642497] ---[ end trace 88e2cd58f37ecfc3 ]--- After a record 10 days uptime... -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561309: firmware-linux-nonfree: needs firmware for module r8169
Ben (et al): Your patch (with Stefan's addition, replacing dev->name with "r8169") also worked for me on an Intel i7 920 system (amd64) running unstable (w/o the firmware). Dec 20 18:39:08 octane kernel: [1.100454] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Dec 20 18:39:08 octane kernel: [1.100471] r8169 :06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Dec 20 18:39:08 octane kernel: [1.100960] eth0: RTL8168d/8111d at 0xc9c7a000, 00:1f:bc:08:c4:16, XID 081000c0 IRQ 30 Dec 20 18:39:08 octane kernel: [1.105168] r8169 :06:00.0: firmware: requesting rtl8168d-1.fw Dec 20 18:39:08 octane kernel: [1.106433] Failed to load rtl8168d-1.fw. ... Dec 20 18:39:08 octane kernel: [ 12.736957] r8169: eth0: link up This NIC is onboard the mobo: EVGA X58 SLI LE http://www.evga.com/products/moreInfo.asp?pn=141-BL-E757-TR&family=Motherboard%20Family Thanks! --Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561552: linux-image-2.6.32-trunk-amd64: [agp/drm] agp + dri unavailable with testing X.org 1.6.5
n: Device: "/dev/input/event5" +(**) Sleep Button: Device: "/dev/input/event1" (II) Sleep Button: Found keys (II) Sleep Button: Configuring as keyboard (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD) @@ -1245,7 +1207,7 @@ (**) Option "xkb_options" "terminate:ctrl_alt_bksp" (II) config/hal: Adding input device Power Button (**) Power Button: always reports core events -(**) Power Button: Device: "/dev/input/event6" +(**) Power Button: Device: "/dev/input/event2" (II) Power Button: Found keys (II) Power Button: Configuring as keyboard (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) @@ -1254,6 +1216,17 @@ (**) Option "xkb_layout" "de" (**) Option "xkb_variant" "nodeadkeys" (**) Option "xkb_options" "terminate:ctrl_alt_bksp" +(II) config/hal: Adding input device DVB on-card IR receiver +(**) DVB on-card IR receiver: always reports core events +(**) DVB on-card IR receiver: Device: "/dev/input/event8" +(II) DVB on-card IR receiver: Found keys +(II) DVB on-card IR receiver: Configuring as keyboard +(II) XINPUT: Adding extended input device "DVB on-card IR receiver" (type: KEYBOARD) +(**) Option "xkb_rules" "evdev" +(**) Option "xkb_model" "pc105" +(**) Option "xkb_layout" "de" +(**) Option "xkb_variant" "nodeadkeys" +(**) Option "xkb_options" "terminate:ctrl_alt_bksp" (II) config/hal: Adding input device Macintosh mouse button emulation (**) Macintosh mouse button emulation: always reports core events (**) Macintosh mouse button emulation: Device: "/dev/input/event0" @@ -1285,7 +1258,7 @@ (II) UnloadModule: "evdev" (II) config/hal: Adding input device IR-receiver inside an USB DVB receiver (**) IR-receiver inside an USB DVB receiver: always reports core events -(**) IR-receiver inside an USB DVB receiver: Device: "/dev/input/event1" +(**) IR-receiver inside an USB DVB receiver: Device: "/dev/input/event4" (II) IR-receiver inside an USB DVB receiver: Found keys (II) IR-receiver inside an USB DVB receiver: Configuring as keyboard (II) XINPUT: Adding extended input device "IR-receiver inside an USB DVB receiver" (type: KEYBOARD) @@ -1296,7 +1269,7 @@ (**) Option "xkb_options" "terminate:ctrl_alt_bksp" (II) config/hal: Adding input device USB2.0 PC CAMERA (**) USB2.0 PC CAMERA: always reports core events -(**) USB2.0 PC CAMERA: Device: "/dev/input/event2" +(**) USB2.0 PC CAMERA: Device: "/dev/input/event6" (II) USB2.0 PC CAMERA: Found keys (II) USB2.0 PC CAMERA: Configuring as keyboard (II) XINPUT: Adding extended input device "USB2.0 PC CAMERA" (type: KEYBOARD) @@ -1307,7 +1280,7 @@ (**) Option "xkb_options" "terminate:ctrl_alt_bksp" (II) config/hal: Adding input device USB Audio (**) USB Audio: always reports core events -(**) USB Audio: Device: "/dev/input/event3" +(**) USB Audio: Device: "/dev/input/event7" (II) USB Audio: Found keys (II) USB Audio: Configuring as keyboard (II) XINPUT: Adding extended input device "USB Audio" (type: KEYBOARD) @@ -2498,3 +2471,39 @@ (II) RADEON(0): Output: S-video, Detected Monitor Type: 0 (II) RADEON(0): EDID for output S-video Changing OV0_BASE_ADDR from 0xf000 to 0xf0c00000 +disable primary dac +disable primary dac +enable primary dac +(II) Power Button: Close +(II) UnloadModule: "evdev" +(II) Sleep Button: Close +(II) UnloadModule: "evdev" +(II) Power Button: Close +(II) UnloadModule: "evdev" +(II) DVB on-card IR receiver: Close +(II) UnloadModule: "evdev" +(II) Macintosh mouse button emulation: Close +(II) UnloadModule: "evdev" +(II) IR-receiver inside an USB DVB receiver: Close +(II) UnloadModule: "evdev" +(II) USB2.0 PC CAMERA: Close +(II) UnloadModule: "evdev" +(II) USB Audio: Close +(II) UnloadModule: "evdev" +(II) MLK Typhoon Deskset: Close +(II) UnloadModule: "evdev" +(II) MLK Typhoon Deskset: Close +(II) UnloadModule: "evdev" +disable primary dac +(II) RADEON(0): RADEONRestoreMemMapRegisters() : +(II) RADEON(0): MC_FB_LOCATION : 0x1fff 0xf7fff000 +(II) RADEON(0): MC_AGP_LOCATION : 0x27ff2000 +finished PLL2 +finished PLL1 +Entering Restore TV +Restore TV PLL +Restore TVHV +Restore TV Restarts +Restore Timing Tables +Restore TV standard +Leaving Restore TV scho...@tom1:~$ Trying upgrade to X.org 1.7.0 and will report y tom -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: MSI product_name: MS-6702E product_version: 1.0 chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: Ame
Bug#504805: More iret fun
Have had this problem since months, with random unexplained reboots - replaced the board because I thought it was faulty, but I'm actually getting it more and more... now I finally got to log the serial output: [ 9897.901805] iret exception: [#1] SMP [ 9897.902033] Modules linked in: xt_physdev iptable_filter ip_tables x_tables inet_diag ipv6 bridge ext3 jbd mbcache drbd cn loop evdev parport_pc parport i2c_i801 i2c_core pcspkr rng_core button intel_agp agpgart shpchp pci_hotplug i82875p_edac edac_core xfs dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod ide_cd_mod cdrom ata_piix ata_generic libata scsi_mod piix dock floppy e1000 ide_pci_generic ehci_hcd ide_core uhci_hcd usbcore thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [ 9897.904490] [ 9897.904490] Pid: 0, comm: swapper Not tainted (2.6.26-2-xen-686 #1) [ 9897.904490] EIP: 0061:[] EFLAGS: 0086 CPU: 0 [ 9897.904490] EIP is at 0xc0101427 [ 9897.904490] EAX: EBX: 000c ECX: c0389f1c EDX: f5656000 [ 9897.904490] ESI: 0012 EDI: ce2f4e20 EBP: c0378910 ESP: c0389f0c [ 9897.904490] DS: 007b ES: 007b FS: 00d8 GS: SS: 0069 [ 9897.904490] Process swapper (pid: 0, ti=c0388000 task=c035a1a0 task.ti=c0388000) [ 9897.904490] Stack: c023cf54 0012 0012 0012 c03788e0 c03788e0 0012 [ 9897.906546]ce2f4e20 c014aa96 06c0 c03788e0 0012 c0105b00 0011 [ 9897.906546] 0001 c023d76f 0001 f5656000 f5656000 [ 9897.906546] Call Trace: [ 9897.906546] [] startup_pirq+0xe6/0xef [ 9897.906546] [] handle_level_irq+0xc9/0xed [ 9897.906546] [] do_IRQ+0x4d/0x65 [ 9897.906546] [] evtchn_do_upcall+0xfa/0x191 [ 9897.906546] [] hypervisor_callback+0x3c/0x44 [ 9897.906546] [] xen_safe_halt+0x9f/0xb3 [ 9897.906546] [] xen_idle+0x1b/0x46 [ 9897.906546] [] cpu_idle+0xa8/0xc0 [ 9897.906546] === [ 9897.906546] Code: cc cc cc cc b8 20 00 00 00 cd 82 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 21 00 00 00 cd 82 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc [ 9897.910553] EIP: [] 0xc0101427 SS:ESP 0069:c0389f0c [ 9897.910553] Kernel panic - not syncing: Fatal exception in interrupt (XEN) Domain 0 crashed: rebooting machine in 5 seconds. This is ii linux-image-2.6.26-2-xen-6862.6.26-19lenny2 Linux 2.6.26 image on i686, oldstyle Xen sup ii xen-hypervisor-3.2-1-i386 3.2.1-2 The Xen Hypervisor on i386 If anyone has any idea how to fix, I'd be quite happy :| Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
Hi Vitaliy, On Wed, Nov 18, 2009 at 03:07:48PM +0300, Vitaliy Gusev wrote: > On Wednesday 18 November 2009 12:25:15 pm Vitaliy Gusev wrote: > > On Wednesday 18 November 2009 01:57:34 am Tom Rathborne wrote: > > > > > > According to http://bugzilla.openvz.org/show_bug.cgi?id=1161 > > > > Are you sure that this bug is related to your problem? No, but it was linked from the debian bug page -- seemed like the debian report was delegated to openvz. > Have you also aplied patch diff-inotify-delay-final-put-20090204 in > your kernel? My patch fix-deadlock-sk_callback_lock.patch fixes > only lockdep warning. Of course, lockdep warning points to possible > lockup but I think this possible lockup is not related to your > problem. I don't think that patch is installed ... but the kernel is working fine which is the important part. :) Tom -- -- Tom Rathborne -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
Hi Vitaliy, Daniel On Wed, Jul 22, 2009 at 02:20:15PM +0400, Vitaliy Gusev wrote: > On Wednesday 22 July 2009 06:05:08 am Tom Rathborne wrote: > > Vitaliy wrote: > > > Hello, Tom!. Does this problem still actual for you? Can you > > > check attached patch? ( do not tune off CONFIG_USER_RESOURCE) > > > > This patch makes sense. I have applied it to the latest Debian > > Lenny kernel and will let you know what happens! > > This patch fixes lockdep warning, so you can compile kernel with > LOCKDEP_DEBUG. I no longer work for Tiny Planet, but I am happy to report that the server has been running for 79 days with this patch with no kernel errors or lockups! According to http://bugzilla.openvz.org/show_bug.cgi?id=1161 the OpenVZ bug is "PATCHSENT" ... case closed, more or less! :) Nice working with you! Cheers, Tom -- -- Tom Rathborne -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509923: linux-2.6: hd's no longer found on marvell 88SE6145 sata controller
Hi Ben, this issue was almost a year ago but I can remember it as it was quiet annoying. It turned out that I had to use module 'ahci' instead of 'pata_marvell', I found the hint in the kernel config. However in the previous kernels (before 2.6.26-12 pata_marvell had worked alright). Unfortunately pata_marvell seems to be preferred over ahci for the mentioned controller, so I had blacklisted the module and built all later kernels without it. No more problems after ... Greetings -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538387: /usr/sbin/mkinitramfs: fails with readlink error when trying to use a non-generic kernel in install
Package: initramfs-tools Version: 0.93.3 Severity: normal File: /usr/sbin/mkinitramfs Attempting a fresh install of testing mkinitramfs fails with a readlink error if I select to use a hardware specific image. It works fine if I select generic. Tail of syslog follows: Jul 21 20:22:06 in-target: The following extra packages will be installed: Jul 21 20:22:06 in-target: linux-image-2.6.26-2-amd64 Jul 21 20:22:06 in-target: Suggested packages: Jul 21 20:22:06 in-target: linux-doc-2.6.26 grub lilo Jul 21 20:22:06 in-target: The following NEW packages will be installed Jul 21 20:22:06 in-target: linux-image-2.6-amd64 linux-image-2.6.26-2-amd64 Jul 21 20:22:07 in-target: 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Jul 21 20:22:07 in-target: Need to get 20.9MB of archives. Jul 21 20:22:07 in-target: After this operation, 82.5MB of additional disk space will be used. Jul 21 20:22:07 in-target: Get: 1 http://ftp.uk.debian.org squeeze/main linux-image-2.6.26-2-amd64 2.6.26-17 [20.9MB] Jul 21 20:23:29 in-target: Get: 2 http://ftp.uk.debian.org squeeze/main linux-image-2.6-amd64 2.6.26+17+lenny1 [2514B] Jul 21 20:23:29 in-target: Preconfiguring packages ... Jul 21 20:23:29 debconf: Obsolete command TITLE Configuring linux-image-2.6.26-2-amd64 called Jul 21 20:23:29 in-target: Fetched 20.9MB in 1min 22s (255kB/s) Jul 21 20:23:29 in-target: Selecting previously deselected package linux-image-2.6.26-2-amd64. Jul 21 20:23:29 in-target: 9719 files and directories currently installed.) Jul 21 20:23:29 in-target: Unpacking linux-image-2.6.26-2-amd64 (from .../linux-image-2.6.26-2-amd64_2.6.26-17_amd64.deb) ... Jul 21 20:23:29 debconf: Obsolete command TITLE Configuring linux-image-2.6.26-2-amd64 called Jul 21 20:23:29 in-target: Done. Jul 21 20:23:32 in-target: Selecting previously deselected package linux-image-2.6-amd64. Jul 21 20:23:32 in-target: Unpacking linux-image-2.6-amd64 (from .../linux-image-2.6-amd64_2.6.26+17+lenny1_amd64.deb) ... Jul 21 20:23:33 in-target: Setting up linux-image-2.6.26-2-amd64 (2.6.26-17) ... Jul 21 20:23:33 debconf: Obsolete command TITLE Configuring linux-image-2.6.26-2-amd64 called Jul 21 20:23:33 in-target: Running depmod. Jul 21 20:23:34 in-target: Running mkinitramfs-kpkg. Jul 21 20:23:34 in-target: Deprecation WARNING: use update-initramfs(8) Jul 21 20:23:34 in-target: readlink: Jul 21 20:23:34 in-target: missing operand Jul 21 20:23:34 in-target: Jul 21 20:23:34 in-target: Try `readlink --help' for more information. Jul 21 20:23:34 in-target: mkinitramfs-kpkg failed to create initrd image. Jul 21 20:23:34 in-target: Failed to create initrd image. Jul 21 20:23:34 in-target: dpkg: error processing linux-image-2.6.26-2-amd64 (--configure): Jul 21 20:23:34 in-target: subprocess installed post-installation script returned error exit status 9 Jul 21 20:23:34 in-target: dpkg: dependency problems prevent configuration of linux-image-2.6-amd64: Jul 21 20:23:34 in-target: linux-image-2.6-amd64 depends on linux-image-2.6.26-2-amd64; however: Jul 21 20:23:34 in-target: Package linux-image-2.6.26-2-amd64 is not configured yet. Jul 21 20:23:34 in-target: dpkg: error processing linux-image-2.6-amd64 (--configure): Jul 21 20:23:34 in-target: dependency problems - leaving unconfigured Jul 21 20:23:34 in-target: Errors were encountered while processing: Jul 21 20:23:34 in-target: linux-image-2.6.26-2-amd64 Jul 21 20:23:34 in-target: linux-image-2.6-amd64 Jul 21 20:23:34 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) Jul 21 20:23:34 base-installer: error: exiting on error base-installer/kernel/failed-install Jul 21 20:31:12 main-menu[1075]: WARNING **: Configuring 'bootstrap-base' failed with error code 30 Jul 21 20:31:12 main-menu[1075]: WARNING **: Menu item 'bootstrap-base' failed. Jul 21 20:31:24 main-menu[1075]: INFO: Falling back to the package description for auto-install Jul 21 20:31:24 main-menu[1075]: INFO: Falling back to the package description for ai-choosers Jul 21 20:31:24 main-menu[1075]: INFO: Menu item 'di-utils-shell' selected -- Package-specific info: -- /proc/cmdline root=UUID=873dd7e5-b29d-4eb8-82b0-c13dee139334 ro -- /proc/filesystems ext3 ext2 -- lsmod Module Size Used by radeon133920 2 drm91488 3 radeon binfmt_misc13580 1 ppdev 11656 0 lp 14724 0 rfcomm 38176 2 l2cap 23936 9 rfcomm bluetooth 57124 4 rfcomm,l2cap cpufreq_powersave 6400 0 cpufreq_stats 9120 0 cpufreq_conservative11784 0 cpufreq_userspace 8452 0 cpufreq_ondemand 11792 0 freq_table 9344 2 cpufreq_stats,cpufreq_ondemand ipv6 288328 20 ext2 66448 1 loop 19468 0 snd_hda_intel 436440 2 snd_pcm_oss41760 0 snd_mixer_oss
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
Hi Vitaliy, On Tue, Jul 14, 2009 at 08:07:31PM +0400, Vitaliy Gusev wrote: > On Monday 20 April 2009 08:01:59 pm Vitaliy Gusev wrote: > > Hi, Tom. I will prepare and send patch to you in two-three days. > > Sorry for late response, but I was busy. > > Hello, Tom!. Does this problem still actual for you? Can you check > attached patch? ( do not tune off CONFIG_USER_RESOURCE) This patch makes sense. I have applied it to the latest Debian Lenny kernel and will let you know what happens! Thanks, Tom > diff --git a/kernel/bc/net.c b/kernel/bc/net.c > index e1ffc63..fb0fb25 100644 > --- a/kernel/bc/net.c > +++ b/kernel/bc/net.c > @@ -157,9 +157,9 @@ static void ub_sock_snd_wakeup(struct user_beancounter > *ub) >* act the same way as ub_tcp_snd_wakeup does. >*/ > sock_hold(sk); > - read_lock(&sk->sk_callback_lock); > spin_unlock(&ub->ub_lock); > > + read_lock(&sk->sk_callback_lock); > sk->sk_write_space(sk); > read_unlock(&sk->sk_callback_lock); > > @@ -212,9 +212,9 @@ static void ub_tcp_snd_wakeup(struct user_beancounter *ub) >* it belongs to the callback. >*/ > sock_hold(sk); > - read_lock(&sk->sk_callback_lock); > spin_unlock(&ub->ub_lock); > > + read_lock(&sk->sk_callback_lock); > sk->sk_write_space(sk); > read_unlock(&sk->sk_callback_lock); -- -- Tom Rathborne -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525094: linux-image-2.6.26-2-amd64: initrd image creation fails
On Wed, May 6, 2009 at 1:50 AM, Tom Bruno wrote: > I am getting this same bug as well after an upgrade today. Seems > libmtp8.rules is a symlink to itself. > Oh thats good. I misread the output on my first Debian bug reply. libmtp8 seems to be the issue. I removed that package and then I could update-initramfs -u and dpkg --configure -a to continue my upgrade. I reinstalled it after my upgrade and now sudo update-initramfs -u still fails even after the reinstall. -- Tom
Bug#525094: linux-image-2.6.26-2-amd64: initrd image creation fails
I am getting this same bug as well after an upgrade today. Seems libmtp8.rules is a symlink to itself. lrwxrwxrwx 1 root root19 2009-04-29 10:15 025_libgphoto2.rules -> ../libgphoto2.rules -rw-r--r-- 1 root root 1908 2009-04-02 11:14 11-hplj10xx.rules -rw-r--r-- 1 root root 991 2009-02-05 12:54 65_mdadm.vol_id.rules -rw-r--r-- 1 root root 1038 2009-05-03 15:16 70-persistent-cd.rules -rw-r--r-- 1 root root 377 2009-04-29 10:46 70-persistent-net.rules lrwxrwxrwx 1 root root16 2009-05-05 23:30 libmtp8.rules -> ../libmtp8.rules lrwxrwxrwx 1 root root15 2009-04-30 18:55 libnjb.rules -> ../libnjb.rules lrwxrwxrwx 1 root root19 2009-04-29 18:19 z60_alsa-utils.rules -> ../alsa-utils.rules lrwxrwxrwx 1 root root15 2009-04-30 18:56 z60_hdparm.rules -> ../hdparm.rules -rw-r--r-- 1 root root 5354 2009-03-17 05:09 z60_hplip.rules -rw-r--r-- 1 root root 2656 2009-04-04 16:02 z60_libpisock9.rules -rw-r--r-- 1 root root 1742 2009-03-29 05:13 z60_libsane-extras.rules -rw-r--r-- 1 root root 54592 2009-05-04 05:52 z60_libsane.rules -rw-r--r-- 1 root root 7117 2009-04-11 16:32 z60_xserver-xorg-input-wacom.rules
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
Hi Vitaliy, On Fri, Apr 03, 2009 at 02:21:45PM +0400, Vitaily Gusev wrote: > On Thursday 02 April 2009 01:57:43 am Tom Rathborne wrote: > > On Wed, Apr 01, 2009 at 05:39:59PM -0400, Tom Rathborne wrote: > > > I commented out the junk in fs/dcache.c and the kernel compiled. :) > > > > > > I will send you the sysrq-D info next time I get the bug! > > > > Oops ... now OpenVZ won't start! > > > > magrathea:~# vzctl start 101 > > Starting VE ... > > MOUNTING > > VE is mounted > > Error: kernel does not support user resources. Please, rebuild with > > CONFIG_USER_RESOURCE=y VE start failed > > UNMOUNTING > > VE is unmounted > > > > I do not see a "CONFIG_USER_RESOURCE is not set" in .config, > > and if I add 'CONFIG_USER_RESOURCE=y' then 'make menuconfig' reports: > > .config:3953:warning: trying to assign nonexistent symbol USER_RESOURCE > > > > I did find a couple of references to it: > > ./net/ipv4/tcp.c:#ifdef CONFIG_USER_RESOURCE > > ./net/ipv4/tcp_timer.c:#ifdef CONFIG_USER_RESOURCE > > but it looks like those should be CONFIG_BEANCOUNTERS. > > > > So ... what do I do next? It seems like this bug only happens with > > OpenVZ processes, but OpenVZ will not start without > > CONFIG_BEANCOUNTERS! > > Ok, switching off CONFIG_BEANCOUNTERS was a bad idea ;( > I will prepare patch to fix beancounter warning in one-two days and send to > you. > Thanks a lot of for your efforts! Debian lenny recently updated its kernel source tree and patches, so I have built a fresh kernel with all of your debugging flags on, and of course CONFIG_BEANCOUNTERS on. I'm using these packages: linux-patch-debian-2.6.26 2.6.26-15 Debian patches to version 2.6.26 of the Linux kernel linux-source-2.6.262.6.26-15 Linux kernel source for version 2.6.26 with Debian patches linux-tree-2.6.26 2.6.26-15 Linux kernel source tree for building Debian kernel images The Debian patch directory is much bigger ... now looks like this: 0015--UB-Double-free-for-UDP-socket.patch.bz2 0016-nfs-fix-nfs-clinet-in-VE-finally.patch.bz2 0017-cpt-bump-image-version-to-VERSION_26.patch.bz2 0018-nfs-add-missed-ve_nfs.h-file.patch.bz2 0020-autofs4-pidns-friendly-oz_mode.patch.bz2 0021-autofs-fix-default-pgrp-vnr.patch.bz2 0022-conntrack-prevent-double-allocate-free-of-protos.patch.bz2 0023-conntrack-prevent-call-register_pernet_subsys-fro.patch.bz2 0024-conntrack-prevent-call-nf_register_hooks-from-VE.patch.bz2 0025-conntrack-Allocate-free-ve_nf_conntrack_l3proto_ipv.patch.bz2 0026-ct-Move-_nf_conntrack_l3proto_ipv6-to-net-namespace.patch.bz2 0027-Fix-erratum-that-causes-memory-corruption.patch.bz2 0028-conntrack-fix-oops-in-nf_ct_frag6_gather.patch.bz2 0029-conntrack-adjust-context-during-freeing.patch.bz2 0031-Add-VE-features-for-sit-and-ipip-devices.patch.bz2 0033-netfilter-NAT-assign-nf_nat_seq_adjust_hook-from-V.patch.bz2 0034-netfilter-call-nf_register_hooks-from-VE0-context-o.patch.bz2 0040-Simplify-call-__dev_change_net_namespace-by-remove.patch.bz2 0041-Adjust-VE-before-call-netdev_unregister_kobject-netd.patch.bz2 0042-iptables-setup-init-iptables-mask-before-net-initia.patch.bz2 0042-netns-fix-net_generic-array-leak.patch.bz2 0043-net-set-ve-context-when-init-exit-method-is-called.patch.bz2 0044-vzwdog-walk-through-the-block-devices-list-properly.patch.bz2 0045-Correct-per-process-capabilities-bounding-set-in-CT.patch.bz2 0046-netns-enable-cross-ve-Unix-sockets.patch.bz2 0047-netfilter-Fix-NULL-dereference-in-nf_nat_setup_info.patch.bz2 0048-netfilter-Add-check-to-the-nat-hooks.patch.bz2 0049-cpt-Make-the-proper-check-for-sigmask.patch.bz2 0050-nfs-Fix-access-to-freed-memory.patch.bz2 0051-NFS-NFS-super-blocks-in-different-VEs-should-be-dif.patch.bz2 0052-ms-fix-inotify-umount.patch.bz2 0054-ve-sanitize-capability-checks-for-namespaces-creati.patch.bz2 0056-nfs-Fix-nfs_match_client.patch.bz2 0057-Add-do_ve_enter_hook.patch.bz2 0058-Add-kthread_create_ve-and-kthread_run_ve-functio.patch.bz2 0059-Don-t-dereference-NULL-tsk-mm-in-ve_move_task.patch.bz2 0060-nfs-use-kthread_run_ve-to-start-lockd.patch.bz2 0063-bridge-don-t-leak-master-device-on-brctl-addif.patch.bz2 0064-net-NETIF_F_VIRTUAL-intersects-with-NETIF_F_LRO.patch.bz2 0065-Fix-broken-permissions-for-Unix98-pty.patch.bz2 0066-Free-skb-nf_bridge-in-veth_xmit-and-venet_xmit.patch.bz2 0067-autofs4-fix-ia32-compat-mode.patch.bz2 0070-pidns-update-leader_pid-at-pidns-attach.patch.bz2 0072-pidns-lost-task-debug-print-uses-wrong-prototype.patch.bz2 0073-pidns-zap-ve-process-only-when-killing-ve-s-init-pi.patch.bz
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
On Wed, Apr 01, 2009 at 05:39:59PM -0400, Tom Rathborne wrote: > I commented out the junk in fs/dcache.c and the kernel compiled. :) > > I will send you the sysrq-D info next time I get the bug! Oops ... now OpenVZ won't start! magrathea:~# vzctl start 101 Starting VE ... MOUNTING VE is mounted Error: kernel does not support user resources. Please, rebuild with CONFIG_USER_RESOURCE=y VE start failed UNMOUNTING VE is unmounted I do not see a "CONFIG_USER_RESOURCE is not set" in .config, and if I add 'CONFIG_USER_RESOURCE=y' then 'make menuconfig' reports: .config:3953:warning: trying to assign nonexistent symbol USER_RESOURCE I did find a couple of references to it: ./net/ipv4/tcp.c:#ifdef CONFIG_USER_RESOURCE ./net/ipv4/tcp_timer.c:#ifdef CONFIG_USER_RESOURCE but it looks like those should be CONFIG_BEANCOUNTERS. So ... what do I do next? It seems like this bug only happens with OpenVZ processes, but OpenVZ will not start without CONFIG_BEANCOUNTERS! Tom -- -- Tom Rathborne Tommer needs a revision that takes care of itself. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
On Tue, Mar 31, 2009 at 10:03:21PM -0400, Tom Rathborne wrote: > On Tue, Mar 31, 2009 at 11:51:02PM +0400, Vitaliy Gusev wrote: > > 2. We need sysrq-D info after lockup, so try to compile kernel without > > CONFIG_BEANCOUNTERS. > > With this week's new Debian lenny kernel source package, I had no problem > making an OpenVZ kernel with my previous config, but without > CONFIG_BEANCOUNTERS I got an error: ... > CC kernel/pid.o > kernel/pid.c: In function ‘free_pid’: > kernel/pid.c:270: error: ‘struct pid’ has no member named ‘ub’ > kernel/pid.c:270: error: ‘struct kmem_cache’ has no member named ‘objuse’ > kernel/pid.c:275: error: ‘struct pid’ has no member named ‘ub’ > kernel/pid.c: In function ‘alloc_pid’: > kernel/pid.c:336: warning: label ‘out_enable’ defined but not used > kernel/pid.c:287: warning: unused variable ‘ub’ > make[3]: *** [kernel/pid.o] Error 1 > make[2]: *** [kernel] Error 2 > make[2]: Leaving directory usr/src/linux-source-2.6.26' > make[1]: *** [debian/stamp/build/kernel] Error 2 > make[1]: Leaving directory usr/src/linux-source-2.6.26' > make: *** [debian/stamp/do-build-arch] Error 2 > > So, I commented out those lines (270,275,287) but then I get more > errors, in pid_namespace.c. Commented out those too. Hit some more BC > junk in fs/dcache.c. I commented out the junk in fs/dcache.c and the kernel compiled. :) I will send you the sysrq-D info next time I get the bug! Tom -- -- Tom Rathborne Tommer needs a revision that takes care of itself. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
On Tue, Mar 31, 2009 at 11:51:02PM +0400, Vitaliy Gusev wrote: > 2. We need sysrq-D info after lockup, so try to compile kernel without > CONFIG_BEANCOUNTERS. With this week's new Debian lenny kernel source package, I had no problem making an OpenVZ kernel with my previous config, but without CONFIG_BEANCOUNTERS I got an error: magrathea:/usr/src/linux-source-2.6.26# make-kpkg --append_to_version=-tp7-openvz --initrd binary-arch exec debian/rules DEBIAN_REVISION=2.6.26-tp7-openvz-10.00.Custom APPEND_TO_VERSION=-tp7-openvz INITRD=YES binary-arch == making target debian/stamp/do-build-arch [new prereqs: do-pre-build-arch]== /usr/bin/make -f debian/rules debian/stamp/dep-build-arch make[1]: Entering directory usr/src/linux-source-2.6.26' == making target debian/stamp/build/kernel [new prereqs: conf.vars]== This is kernel package version 11.015. test ! -f scripts/package/builddeb.kpkg-dist || mv -f scripts/package/builddeb.kpkg-dist scripts/package/builddeb test ! -f scripts/package/Makefile.kpkg-dist || mv -f scripts/package/Makefile.kpkg-dist scripts/package/Makefile /usr/bin/make EXTRAVERSION=-tp7-openvz ARCH=x86_64 \ bzImage make[2]: Entering directory usr/src/linux-source-2.6.26' scripts/kconfig/conf -s arch/x86/Kconfig make[2]: Leaving directory usr/src/linux-source-2.6.26' make[2]: Entering directory usr/src/linux-source-2.6.26' CHK include/linux/version.h CHK include/linux/utsrelease.h CALLscripts/checksyscalls.sh CHK include/linux/compile.h CC kernel/time.o CC kernel/pid.o kernel/pid.c: In function ‘free_pid’: kernel/pid.c:270: error: ‘struct pid’ has no member named ‘ub’ kernel/pid.c:270: error: ‘struct kmem_cache’ has no member named ‘objuse’ kernel/pid.c:275: error: ‘struct pid’ has no member named ‘ub’ kernel/pid.c: In function ‘alloc_pid’: kernel/pid.c:336: warning: label ‘out_enable’ defined but not used kernel/pid.c:287: warning: unused variable ‘ub’ make[3]: *** [kernel/pid.o] Error 1 make[2]: *** [kernel] Error 2 make[2]: Leaving directory usr/src/linux-source-2.6.26' make[1]: *** [debian/stamp/build/kernel] Error 2 make[1]: Leaving directory usr/src/linux-source-2.6.26' make: *** [debian/stamp/do-build-arch] Error 2 So, I commented out those lines (270,275,287) but then I get more errors, in pid_namespace.c. Commented out those too. Hit some more BC junk in fs/dcache.c. Looks like the Debian OpenVZ patches put in some beancounter stuff outside of CONFIG_BEANCOUNTERS! I will look at this again later this week and see if I can figure out how to exclude just those patches. I'll let you know how it goes ... thanks for your attention! :) Tom -- -- Tom Rathborne Tommer needs a revision that takes care of itself. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521944: linux-image-2.6.29-1-686: Excessive number of interrupts from hrtimer_start_expires
Package: linux-image-2.6.29-1-686 Version: 2.6.29-1 Severity: normal Running powertop on the 2.6.29-1 kernel gets me the following Top causes for wakeups: 50.8% (126.3) : hrtimer_start_expires (tick_sched_timer) 12.8% ( 31.7) : Rescheduling interrupts 7.4% ( 18.5): uhci_hcd:usb3, ath 5.3% ( 13.1): ata_piix 4.4% ( 10.9): extra timer interrupt Previously, the major cause of interrupts had been the kernel IPI, and hence one reason for upgrading to the latest kernel version. Now there's hrtimer_start_expires, and quite frankly this is a median case - I've seen it hit as high as 500 interrupts/second occasionally. This is causing my battery to get drained at an accelerated rate and I don't think this is correct behaviour. -- Package-specific info: ** Version: Linux version 2.6.29-1-686 (Debian 2.6.29-1) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-5) ) #1 SMP Tue Mar 24 23:05:52 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.29-1-686 root=UUID=1d2ed566-a39a-423f-8a96-59206e41336e ro quiet ** Not tainted ** Kernel log: [ 913.817857] pci :04:00.3: restoring config space at offset 0x1 (was 0x10, writing 0x17) [ 913.817857] pci :04:00.4: restoring config space at offset 0xf (was 0x1ff, writing 0x10b) [ 913.817857] pci :04:00.4: restoring config space at offset 0x4 (was 0x0, writing 0x5410) [ 913.817857] pci :04:00.4: restoring config space at offset 0x1 (was 0x10, writing 0x17) [ 913.820542] Enabling non-boot CPUs ... [ 913.821353] SMP alternatives: switching to SMP code [ 914.363428] Booting processor 1 APIC 0x1 ip 0x6000 [ 913.816617] Initializing CPU#1 [ 913.816617] Calibrating delay using timer specific routine.. 3192.03 BogoMIPS (lpj=6384069) [ 913.816617] CPU: L1 I cache: 32K, L1 D cache: 24K [ 913.816617] CPU: L2 cache: 512K [ 913.816617] [ds] using Core 2/Atom configuration [ 913.816617] CPU: Physical Processor ID: 0 [ 913.816617] CPU: Processor Core ID: 0 [ 913.816617] Intel machine check architecture supported. [ 913.816617] Intel machine check reporting enabled on CPU#1. [ 914.452394] CPU1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02 [ 914.452572] CPU0 attaching NULL sched-domain. [ 914.453038] Switched to high resolution mode on CPU 1 [ 914.464581] CPU0 attaching sched-domain: [ 914.464587] domain 0: span 0-1 level SIBLING [ 914.464591] groups: 0 1 [ 914.464600] CPU1 attaching sched-domain: [ 914.464604] domain 0: span 0-1 level SIBLING [ 914.464607] groups: 1 0 [ 914.469032] CPU1 is up [ 914.469037] ACPI: Waking up from system sleep state S3 [ 914.500538] pci :00:02.0: PME# disabled [ 914.500560] pci :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 914.500571] pci :00:02.0: setting latency timer to 64 [ 914.500581] pci :00:02.1: PME# disabled [ 914.500659] HDA Intel :00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 914.500671] HDA Intel :00:1b.0: setting latency timer to 64 [ 914.500712] pcieport-driver :00:1c.0: setting latency timer to 64 [ 914.500728] pcieport-driver :00:1c.1: setting latency timer to 64 [ 914.500744] pcieport-driver :00:1c.2: setting latency timer to 64 [ 914.500759] pcieport-driver :00:1c.3: setting latency timer to 64 [ 914.500813] uhci_hcd :00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 914.500825] uhci_hcd :00:1d.0: setting latency timer to 64 [ 914.500859] usb usb1: root hub lost power or was reset [ 914.500919] uhci_hcd :00:1d.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 914.500932] uhci_hcd :00:1d.1: setting latency timer to 64 [ 914.500964] usb usb2: root hub lost power or was reset [ 914.501047] uhci_hcd :00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 914.501063] uhci_hcd :00:1d.2: setting latency timer to 64 [ 914.501104] usb usb3: root hub lost power or was reset [ 914.501165] uhci_hcd :00:1d.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [ 914.501177] uhci_hcd :00:1d.3: setting latency timer to 64 [ 914.501210] usb usb4: root hub lost power or was reset [ 914.501288] ehci_hcd :00:1d.7: PME# disabled [ 914.501299] ehci_hcd :00:1d.7: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 914.501311] ehci_hcd :00:1d.7: setting latency timer to 64 [ 914.501324] ehci_hcd :00:1d.7: PME# disabled [ 914.501368] pci :00:1e.0: setting latency timer to 64 [ 914.501432] ata_piix :00:1f.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 914.501443] ata_piix :00:1f.2: setting latency timer to 64 [ 914.501651] r8169 :02:00.0: PME# disabled [ 914.501843] ath5k :03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 914.529635] sdhci-pci :04:00.0: restoring config space at offset 0xc (was 0x0, writing 0x8000) [ 914.529729] sdhci-pci :04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 914.529756] sdhci-pci :04:00.0: setting latency timer to 64 [ 914.529790] pci :04:00
