Bug#675164: linux-image-3.2.0-2-s390x - Dies with rcu_sched stalls
Source: linux-2.6 Version: 3.2.17-1 Severity: important The Wheezy kernel dies after showing the following message: | [55960.854495] INFO: r5] INFO: rcu_sched detected stall on CPU 1 (t=15001 jiffies) | [55960.854513] CPU: 1 Not tainted 3.2.0-2-s390x #1 | [55960.854518] Process swapper/1 (pid: 0, task: 27fc4938, ksp: 27fd3d00) | [55960.854523] 0005 27fdb940 0002 | [55960.854530]27fdb9e0 27fdb958 27fdb958 003b2b82 | [55960.854542]003c07e8 27fdbbd8 000a | [55960.854555] 000c 27fdb940 27fdb9b8 | [55960.854569]003c6d78 00011a5e 27fdb940 27fdb990 | [55960.854588] Call Trace: | [55960.854594] ([000119a4] show_trace+0x5c/0x88) | [55960.854612] [000b86a6] __rcu_pending+0xaa/0x52c | [55960.854625] [000b985e] rcu_check_callbacks+0x10e/0x1a4 | [55960.854637] [0006177c] update_process_times+0x44/0x74 | [55960.854652] [00086696] tick_sched_timer+0xa2/0xd8 | [55960.854666] [ The LPAR, this kernel is running in, is scheduled down as the whole machine is near overload. Bastian -- Sometimes a man will tell his bartender things he'll never tell his doctor. -- Dr. Phillip Boyce, The Menagerie (The Cage), stardate unknown. -- 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/20120530095620.gb6...@wavehammer.waldi.eu.org
Bug#675176: svcgssd not working with '-n' option after lenny to squeeze upgrade
Package: nfs-kernel-server
Version: 1:1.2.2-4squeeze2
Severity: important
After upgrading a HA cluster from Lenny to Squeeze, the nfs service stopped
working.
The problem was specifying the '-n' option in RPCSVCGSSDOPTS. This
option allows the server to accept requests for any key in its keytab.
Without '-n' nodes will only accept mounts from clients using their node
name (i.e. nodeX.example.com) instead of the cluster's name
(as in nfsserver.example.com).
I applied the attached patch in order to be able to pass '-p
nfsserver.example.com' to svcgssd. This solves the problem partially
since it won't allow clients to mount an exported directory using the
node's name, which was possible previously.
The patch was posted by Eberhard Kuemmerle at the linux-nfs list and
applied upstream in 1.2.3.
The error from rpc.svcgssd in 1.2.2 using '-n' is:
May 30 12:23:51 rasca rpc.svcgssd[1991]: leaving poll
May 30 12:23:51 rasca rpc.svcgssd[1991]: handling null request
May 30 12:23:51 rasca rpc.svcgssd[1991]: WARNING: gss_set_allowable_enctypes
failed
May 30 12:23:51 rasca rpc.svcgssd[1991]: ERROR: GSS-API: error in
svcgssd_limit_krb5_enctypes: gss_set_allowable_enctypes(): No credentials were
supplied, or the credentials were unavailable or inaccessible - (0x08142008)
May 30 12:23:51 rasca rpc.svcgssd[1991]: sending null reply
May 30 12:23:51 rasca rpc.svcgssd[1991]: writing message: \x [snip]
May 30 12:23:51 rasca rpc.svcgssd[1991]: finished handling null request
May 30 12:23:51 rasca rpc.svcgssd[1991]: entering poll
This bug is still present (and worse) in 1:1.2.5-4~bpo60 which is probably
menacing Wheeze :-(
Trying to use this option on 1:1.2.5-4~bpo60 makes rpc.svcgssd fail to start
with the following error:
May 30 13:06:12 rasca rpc.svcgssd[2761]: ERROR: GSS-API: error in
gss_acquire_cred(): GSS_S_BAD_NAME (An invalid name was supplied) - Unknown
error
May 30 13:06:12 rasca rpc.svcgssd[2761]: unable to obtain nameless credentials
Thanks,
Alberto
--
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
agi@(inittab.org|debian.org)| en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com
Key fingerprint = 9782 04E7 2B75 405C F5E9 0C81 C514 AF8E 4BA4 01C3
Index: nfs-utils-1.2.2/utils/gssd/gss_util.c
===
--- nfs-utils-1.2.2.orig/utils/gssd/gss_util.c 2012-05-29 16:27:59.100011446 +0200
+++ nfs-utils-1.2.2/utils/gssd/gss_util.c 2012-05-29 16:28:27.312001093 +0200
@@ -191,7 +191,7 @@
}
int
-gssd_acquire_cred(char *server_name)
+gssd_acquire_cred(char *server_name, const gss_OID oid)
{
gss_buffer_desc name;
gss_name_t target_name;
@@ -207,7 +207,7 @@
name.length = strlen(server_name);
maj_stat = gss_import_name(min_stat, name,
-(const gss_OID) GSS_C_NT_HOSTBASED_SERVICE,
+oid,
target_name);
if (maj_stat != GSS_S_COMPLETE) {
Index: nfs-utils-1.2.2/utils/gssd/gss_util.h
===
--- nfs-utils-1.2.2.orig/utils/gssd/gss_util.h 2012-05-29 16:28:02.87946 +0200
+++ nfs-utils-1.2.2/utils/gssd/gss_util.h 2012-05-29 16:28:27.312001093 +0200
@@ -37,7 +37,7 @@
extern gss_cred_id_t gssd_creds;
-int gssd_acquire_cred(char *server_name);
+int gssd_acquire_cred(char *server_name, const gss_OID oid);
void pgsserr(char *msg, u_int32_t maj_stat, u_int32_t min_stat,
const gss_OID mech);
int gssd_check_mechs(void);
Index: nfs-utils-1.2.2/utils/gssd/gssd.h
===
--- nfs-utils-1.2.2.orig/utils/gssd/gssd.h 2012-05-29 16:28:06.22902 +0200
+++ nfs-utils-1.2.2/utils/gssd/gssd.h 2012-05-29 16:28:27.312001093 +0200
@@ -100,7 +100,6 @@
void handle_krb5_upcall(struct clnt_info *clp);
void handle_spkm3_upcall(struct clnt_info *clp);
void handle_gssd_upcall(struct clnt_info *clp);
-int gssd_acquire_cred(char *server_name);
void gssd_run(void);
Index: nfs-utils-1.2.2/utils/gssd/svcgssd.c
===
--- nfs-utils-1.2.2.orig/utils/gssd/svcgssd.c 2012-05-29 16:28:09.660002070 +0200
+++ nfs-utils-1.2.2/utils/gssd/svcgssd.c 2012-05-29 16:29:04.516001466 +0200
@@ -173,7 +173,7 @@
static void
usage(char *progname)
{
- fprintf(stderr, usage: %s [-n] [-f] [-v] [-r] [-i]\n,
+ fprintf(stderr, usage: %s [-n] [-f] [-v] [-r] [-i] [-p principal]\n,
progname);
exit(1);
}
@@ -186,9 +186,10 @@
int verbosity = 0;
int rpc_verbosity = 0;
int idmap_verbosity = 0;
- int opt;
+ int opt, status;
extern char *optarg;
char *progname;
+ char *principal = NULL;
while ((opt = getopt(argc, argv, fivrnp:)) != -1) {
switch (opt) {
@@ -207,6 +208,9 @@
case 'r':
rpc_verbosity++;
break;
+ case 'p':
+principal = optarg;
+break;
default:
usage(argv[0]);
break;
@@ -250,12 +254,20 @@
signal(SIGTERM, sig_die);
signal(SIGHUP, sig_hup);
- if (get_creds
Bug#675188: Change in rpc.idmapd makes clients unable to resolv users/groups
Package: nfs-kernel-server Version: 1:1.2.5-4~bpo60 Severity: important After upgrading an nfs server from 1.2.2 to 1.2.5 (from backports) all the clients lost the ability to show the correct owner/group for files and directories: -rw-rw-r-- 1 nobody nogroup0 2012-05-29 17:46 foo drwxr-xr-x 2 nobody nogroup 4096 2012-05-29 17:39 bar I tracked the problem to the way rpc.idmapd reports users and groups to the clients. From rpc.idmapd -v in 1.2.2: rpc.idmapd: nfsdcb: authbuf=gss/krb5p authtype=user rpc.idmapd: nfs4_uid_to_name: calling umich_ldap-uid_to_name rpc.idmapd: ldap_init_and_bind: version mismatch between API information and protocol version. Setting protocol version to 3 rpc.idmapd: nfs4_uid_to_name: umich_ldap-uid_to_name returned 0 rpc.idmapd: nfs4_uid_to_name: final return value is 0 rpc.idmapd: Server: (user) id 2095 - name alberto.gonzalez rpc.idmapd: nfsdcb: authbuf=gss/krb5p authtype=group rpc.idmapd: nfs4_gid_to_name: calling umich_ldap-gid_to_name rpc.idmapd: ldap_init_and_bind: version mismatch between API information and protocol version. Setting protocol version to 3 rpc.idmapd: nfs4_gid_to_name: umich_ldap-gid_to_name returned 0 rpc.idmapd: nfs4_gid_to_name: final return value is 0 rpc.idmapd: Server: (group) id 2095 - name alberto.gonzalez Whereas in 1.2.5: rpc.idmapd: nfsdcb: authbuf=gss/krb5p authtype=user rpc.idmapd: nfs4_uid_to_name: calling nsswitch-uid_to_name rpc.idmapd: nfs4_uid_to_name: nsswitch-uid_to_name returned 0 rpc.idmapd: nfs4_uid_to_name: final return value is 0 rpc.idmapd: Server : (user) id 2095 - name alberto.gonzalez@domain rpc.idmapd: nfsdcb: authbuf=gss/krb5p authtype=user rpc.idmapd: nfs4_uid_to_name: calling nsswitch-uid_to_name rpc.idmapd: nfs4_uid_to_name: nsswitch-uid_to_name returned 0 rpc.idmapd: nfs4_uid_to_name: final return value is 0 rpc.idmapd: Server : (user) id 1000 - name agi@domain rpc.idmapd: nfsdcb: authbuf=gss/krb5p authtype=group rpc.idmapd: nfs4_gid_to_name: calling nsswitch-gid_to_name rpc.idmapd: nfs4_gid_to_name: nsswitch-gid_to_name returned 0 rpc.idmapd: nfs4_gid_to_name: final return value is 0 rpc.idmapd: Server : (group) id 1000 - name agi@domain I've tried commenting out Domain = domain and setting it to its real value, (in the server's /etc/idmapd.conf) both test with the same result. I'm not saying that user@domain is not the right value for this (it probably is, don't know the RFC). But it's not the way it used to behave. It would be nice to have a way to have rpc.idmapd report users and groups as it used to, in order to avoid modifying /etc/idmapd.conf in hundreds of nfs clients as well as introducing an extra attribute (for NFSv4_name_attr and NFSv4_group_attr) in LDAP (now just using uid). I expect this bug to hit nfs (v4) servers upgrading from Squeeze to Wheezy. Thanks, Alberto -- Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico agi@(inittab.org|debian.org)| en GNU/Linux y software libre Encrypted mail preferred| http://inittab.com Key fingerprint = 9782 04E7 2B75 405C F5E9 0C81 C514 AF8E 4BA4 01C3 -- 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/20120530121311.gu4...@lib.inittab.org
Bug#675190: BUG: unable to handle kernel paging request at 27c97000 during reboot under xen
Package: linux-2.6 Version: 3.2.18-1 Severity: minor linux 3.22 Ñcrashing during reboot when ran under xcp-xapi toolstack. VM configuration is default, installation is default (netinst) too. -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.18-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Mon May 21 18:24:12 UTC 2012 ** Command line: root=UUID=7f4ef707-a7d8-4c30-9932-421bc2ef6b54 ro console=hvc0 quiet -- quiet console=hvc0 ** Not tainted ** Kernel log: [0.038070] installing Xen timer for CPU 7 [0.004000] Initializing CPU#7 [0.038193] NMI watchdog disabled (cpu7): hardware events not enabled [0.038212] Brought up 8 CPUs [0.038322] devtmpfs: initialized [0.038322] Grant table initialized [0.038322] print_constraints: dummy: [0.038322] NET: Registered protocol family 16 [0.344043] SMP alternatives: switching to UP code [0.362591] PCI: setting up Xen PCI frontend stub [0.362594] PCI: pci_cache_line_size set to 64 bytes [0.363041] bio: create slab bio-0 at 0 [0.363092] ACPI: Interpreter disabled. [0.363109] xen/balloon: Initialising balloon driver. [0.377597] xen-balloon: Initialising balloon driver. [0.377597] vgaarb: loaded [0.377597] PCI: System does not support PCI [0.377597] PCI: System does not support PCI [0.377597] Switching to clocksource xen [0.377597] pnp: PnP ACPI: disabled [0.377597] PnPBIOS: Disabled [0.378807] PCI: max bus depth: 0 pci_try_num: 1 [0.378834] NET: Registered protocol family 2 [0.378876] IP route cache hash table entries: 32768 (order: 5, 131072 bytes) [0.379015] TCP established hash table entries: 131072 (order: 8, 1048576 bytes) [0.379244] TCP bind hash table entries: 65536 (order: 7, 524288 bytes) [0.379346] TCP: Hash tables configured (established 131072 bind 65536) [0.379348] TCP reno registered [0.379350] UDP hash table entries: 512 (order: 2, 16384 bytes) [0.379356] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [0.379414] NET: Registered protocol family 1 [0.379420] PCI: CLS 0 bytes, default 64 [0.379451] Unpacking initramfs... [0.425522] Freeing initrd memory: 23440k freed [0.428807] platform rtc_cmos: registered platform RTC device (no PNP device found) [0.428991] audit: initializing netlink socket (disabled) [0.429000] type=2000 audit(1338378007.137:1): initialized [0.449369] highmem bounce pool size: 64 pages [0.449374] HugeTLB registered 2 MB page size, pre-allocated 0 pages [0.449469] VFS: Disk quotas dquot_6.5.2 [0.449495] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [0.449551] msgmni has been set to 1296 [0.449671] alg: No test for stdrng (krng) [0.449689] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [0.449692] io scheduler noop registered [0.449693] io scheduler deadline registered [0.449699] io scheduler cfq registered (default) [0.449743] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [0.449764] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [0.449766] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.449856] isapnp: Scanning for PnP cards... [0.801949] isapnp: No Plug Play device found [0.802193] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [0.802432] Linux agpgart interface v0.103 [0.802539] i8042: PNP: No PS/2 controller found. Probing ports directly. [0.803350] i8042: No controller found [0.803404] mousedev: PS/2 mouse device common for all mice [0.843197] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [0.843230] rtc_cmos: probe of rtc_cmos failed with error -38 [0.843389] TCP cubic registered [0.843406] NET: Registered protocol family 10 [0.843758] Mobile IPv6 [0.843760] NET: Registered protocol family 17 [0.843764] Registering the dns_resolver key type [0.843776] Using IPI No-Shortcut mode [0.843853] PM: Hibernation image not present or could not be loaded. [0.843861] registered taskstats version 1 [0.843886] XENBUS: Device with no driver: device/vbd/51712 [0.843888] XENBUS: Device with no driver: device/vif/0 [0.843898] /build/buildd-linux-2.6_3.2.18-1-i386-rwdM7y/linux-2.6-3.2.18/debian/build/source_i386_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.843929] Initializing network drop monitor service [0.844180] Freeing unused kernel memory: 412k freed [0.844923] Write protecting the kernel text: 2844k [0.845190] Write protecting the kernel read-only data: 1112k [0.845192] NX-protecting the kernel data: 3300k [0.878430] udevd[88]: starting version 175 [0.903142] Initialising Xen virtual ethernet driver. [0.919416] blkfront: xvda: barrier or flush: disabled [0.920670] xvda: xvda1 xvda2 xvda5 [1.078589] PM: Starting manual resume from disk [
Processed: tagging 661057
Processing commands for cont...@bugs.debian.org: tags 661057 - moreinfo Bug #661057 [linux-2.6] linux-2.6: hpsa driver does not support multipath on Smart Array 712m with latest firmware Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 661057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13383826551537.transcr...@bugs.debian.org
Uploading linux-2.6 (3.2.19-1)
I'm intending to release Linux 3.2.19 later today. The complete release (files uploaded) depends on Greg K-H and probably won't be done until later in the week, but we don't use pristine tarballs so this doesn't hold up a Debian upload. It will include the usual mixture of security fixes, other important bug fixes and small changes to support more hardware. So I intend to upload linux-2.6 version 3.2.19-1 tomorrow. This might require an ABI bump but it is probably avoidable. The current Debian changes add support for new Blade Engines NICs, CoDel network queue management, and better integration of the Hyper-V paravirtualised drivers. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Bug#675190: BUG: unable to handle kernel paging request at 27c97000 during reboot under xen
On Wed, 2012-05-30 at 16:23 +0400, George Shuklin wrote: Package: linux-2.6 Version: 3.2.18-1 Severity: minor linux 3.22 crashing during reboot when ran under xcp-xapi toolstack. VM configuration is default, installation is default (netinst) too. [...] A log of the crash would be useful. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Processed: tagging 675190
Processing commands for cont...@bugs.debian.org: tags 675190 + moreinfo Bug #675190 [linux-2.6] BUG: unable to handle kernel paging request at 27c97000 during reboot under xen Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 675190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133838469013971.transcr...@bugs.debian.org
Processed: reassign 675022 to src:linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 675022 src:linux-2.6 3.2.18-1 Bug #675022 [xserver-xorg-video-intel] Frequent lockups when using icedove (thunderbird) Bug reassigned from package 'xserver-xorg-video-intel' to 'src:linux-2.6'. No longer marked as found in versions xserver-xorg-video-intel/2:2.19.0-1. Ignoring request to alter fixed versions of bug #675022 to the same values previously set Bug #675022 [src:linux-2.6] Frequent lockups when using icedove (thunderbird) Marked as found in versions linux-2.6/3.2.18-1. thanks Stopping processing here. Please contact me if you need assistance. -- 675022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133838551117516.transcr...@bugs.debian.org
Processed: reassign 675022 to src:linux-2.6, severity of 675022 is important, tagging 675022
Processing commands for cont...@bugs.debian.org: reassign 675022 src:linux-2.6 3.2.18-1 Bug #675022 [src:linux-2.6] Frequent lockups when using icedove (thunderbird) Ignoring request to reassign bug #675022 to the same package Bug #675022 [src:linux-2.6] Frequent lockups when using icedove (thunderbird) Ignoring request to alter found versions of bug #675022 to the same values previously set severity 675022 important Bug #675022 [src:linux-2.6] Frequent lockups when using icedove (thunderbird) Severity set to 'important' from 'grave' tags 675022 + upstream fixed-upstream pending Bug #675022 [src:linux-2.6] Frequent lockups when using icedove (thunderbird) Added tag(s) upstream and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 675022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133838567719732.transcr...@bugs.debian.org
Processed: tagging 675022
Processing commands for cont...@bugs.debian.org: tags 675022 + pending Bug #675022 [src:linux-2.6] Frequent lockups when using icedove (thunderbird) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 675022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133838557219311.transcr...@bugs.debian.org
Bug#675190: BUG: unable to handle kernel paging request at 27c97000 during reboot under xen
On 30.05.2012 17:31, Ben Hutchings wrote: A log of the crash would be useful. oops, sorry, forgot to attach. Here: [ ok ] Deactivating swap...done. [info] Will now restart. [ 280.608079] WARNING: g.e. still in use! [ 280.608088] WARNING: g.e. still in use! [ 280.608104] sysfs: kobject eth0 without dirent [ 280.608220] sysfs: kobject eth0 without dirent [ 280.608316] sysfs: kobject eth0 without dirent [ 280.608438] BUG: unable to handle kernel paging request at 27c97000 [ 280.608448] IP: [c1229e86] linkwatch_do_dev+0x8e/0x94 [ 280.608460] *pdpt = 02a8a027 *pde = [ 280.608470] Oops: 0002 [#1] SMP [ 280.608476] Modules linked in: fuse btrfs crc32c libcrc32c zlib_deflate ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext4 crc16 jbd2 ext2 dm_mod nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop evdev snd_pcm snd_page_alloc snd_timer snd soundcore pcspkr ext3 mbcache jbd xen_blkfront xen_netfront [ 280.608088] WARNING: g.e. still in use! [ 280.608104] sysfs: kobject eth0 without dirent [ 280.608220] sysfs: kobject eth0 without dirent [ 280.608316] sysfs: kobject eth0 without dirent [ 280.608438] BUG: unable to handle kernel paging request at 27c97000 [ 280.608448] IP: [c1229e86] linkwatch_do_dev+0x8e/0x94 [ 280.608460] *pdpt = 02a8a027 *pde = [ 280.608470] Oops: 0002 [#1] SMP [ 280.608476] Modules linked in: fuse btrfs crc32c libcrc32c zlib_deflate ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext4 crc16 jbd2 ext2 dm_mod nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop evdev snd_pcm snd_page_alloc snd_timer snd soundcore pcspkr ext3 mbcache jbd xen_blkfront xen_netfront [ 280.608526] [ 280.608530] Pid: 60, comm: kworker/0:1 Tainted: GW 3.2.0-2-686-pae #1 [ 280.608538] EIP: 0061:[c1229e86] EFLAGS: 00010246 CPU: 0 [ 280.608544] EIP is at linkwatch_do_dev+0x8e/0x94 [ 280.608548] EAX: EBX: c2958000 ECX: c295826c EDX: e8d1 [ 280.608554] ESI: EDI: c2958000 EBP: e8d11f68 ESP: e8d11f5c [ 280.608559] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [ 280.608565] Process kworker/0:1 (pid: 60, ti=e8d1 task=e8d05620 task.ti=e8d1) [ 280.608572] Stack: [ 280.608575] e8d11f02 c295826c c122a0c3 e8d11f68 e8d11f68 e8c9bdc0 c140ff8c e91165c0 [ 280.608587] e91166c0 c122a110 c1049aef e911b400 c122a0f8 e911b405 e8c9bdc0 [ 280.608598] e91165c0 e8c9bdd0 e8d05620 c104a7fa e8c9bdd0 e8c71f34 e8c9bdc0 c104a751 [ 280.608609] Call Trace: [ 280.608614] [c122a0c3] ? __linkwatch_run_queue+0xe2/0x117 [ 280.608621] [c122a110] ? linkwatch_event+0x18/0x1d [ 280.608628] [c1049aef] ? process_one_work+0x112/0x1fa [ 280.608634] [c122a0f8] ? __linkwatch_run_queue+0x117/0x117 [ 280.608641] [c104a7fa] ? worker_thread+0xa9/0x122 [ 280.608648] [c104a751] ? manage_workers.isra.23+0x13d/0x13d [ 280.608654] [c104d13b] ? kthread+0x63/0x68 [ 280.608660] [c104d0d8] ? kthread_worker_fn+0x101/0x101 [ 280.608667] [c12c5c7e] ? kernel_thread_helper+0x6/0x10 [ 280.608672] Code: f6 83 ec 00 00 00 01 74 1c 8b 43 44 a8 04 89 d8 75 07 e8 b5 7b 00 00 eb 05 e8 99 7d 00 00 89 d8 e8 24 47 ff ff 8b 83 58 02 00 00 64 ff 08 58 5b c3 56 31 d2 53 8b 48 44 80 e1 04 75 29 8b 98 04 [ 280.608729] EIP: [c1229e86] linkwatch_do_dev+0x8e/0x94 SS:ESP 0069:e8d11f5c [ 280.608737] CR2: 27c97000 [ 280.608747] ---[ end trace e490ba182b5fd8cc ]--- [ 280.608774] BUG: unable to handle kernel paging request at fffc [ 280.608781] IP: [c104d2da] kthread_data+0x6/0xa [ 280.608788] *pdpt = 02405027 *pde = [ 280.608796] Oops: [#2] SMP [ 280.608800] Modules linked in: fuse btrfs crc32c libcrc32c zlib_deflate ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext4 crc16 jbd2 ext2 dm_mod nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop evdev snd_pcm snd_page_alloc snd_timer snd soundcore pcspkr ext3 mbcache jbd xen_blkfront xen_netfront [ 280.608848] [ 280.608852] Pid: 60, comm: kworker/0:1 Tainted: G D W 3.2.0-2-686-pae #1 [ 280.608861] EIP: 0061:[c104d2da] EFLAGS: 00010002 CPU: 0 [ 280.608867] EIP is at kthread_data+0x6/0xa [ 280.608871] EAX: EBX: e8d057d0 ECX: e911aa04 EDX: [ 280.608877] ESI: EDI: e8d05754 EBP: e8d05620 ESP: e8d11dac [ 280.608883] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [ 280.608889] Process kworker/0:1 (pid: 60, ti=e8d1 task=e8d05620 task.ti=e8d1) [ 280.608896] Stack: [ 280.608899] c104aabb e8d057d0 e911a9c0 e8d05754 c12bfa76 e8d11def 000d c13762b7 [ 280.608910] 003c c14839c0 e8d057d0 c14839c0 0001baec e8ce7da4 c105d519 [ 280.608921] e8d60580 e8c00040 e8d60580 c107a6fd c107aee1 e8d05620 e8d05620 [ 280.608933] Call Trace: [ 280.608938] [c104aabb] ? wq_worker_sleeping+0xa/0x5d [ 280.608944] [c12bfa76] ? __schedule+0x101/0x55b [ 280.608950] [c105d519] ? arch_local_irq_disable+0x6/0x7 [ 280.608957]
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
Hi all, Its been 2 months without a reply on this issue, and we are getting close to a freeze. Kees and John it looks like there are some pending questions for you below, it would be great if you could chime in with your opinons: If the Debian kernel team was willing to carry some kind of AppArmor kernel/userspace interface patch, I'm now unsure if the old or new ones would be better suited. (I assume AppArmor 2.8 is released long enough before the Wheezy freeze, so that we can ship it in there, and are given this choice.) On the one hand, the old compat' patches are confidence inspiring, as they are small and have been shipped by Ubuntu for a while. My opinon: the 2.4 compat patch is tiny, and it works well, and has been tested for some time, I think it makes the most sense to include this one. On the other hand, it seems the new patches are being upstreamed, which makes them more appealing somehow than the older ones. The newer patch is bigger, some of it must be backported from Linux 3.4, some from Ubuntu, it is much less tested and I suspect because of that will encounter much more resistance from Debian's kernel team to include it. Presumably this will eventually be the one that will be upstreamed, but it isn't there yet. This is why I think the 2.4 compat patch is the way to go with Wheezy, when the newer patch is upstreamed that can be swapped out then. John, I think it would help if you could please point us more precisely to the commits of the new interface that have been upstreamed already, and to the ones that have not been, so that we can get a rough idea of where things are at. Kees, others, what do you think? micah -- -- 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/87mx4pr9k9@algae.riseup.net
Bug#669046: No crash since 2 weeks after memory change
Dear maintainers, please close this bug because it turns out that the problem was damaged memory. After replacing the 8GB with two new modules, the problem didn't show up since 2 weeks. Sorry for the false bug report, Andy -- 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/4fc63aed.2050...@gmail.com
Processed: Re: BUG: unable to handle kernel NULL pointer dereference at [various addresses] (No crash since 2 weeks after memory change)
Processing commands for cont...@bugs.debian.org: notfound 669046 3.2.14-1 Bug #669046 [linux-2.6] BUG: unable to handle kernel NULL pointer dereference at [various addresses] There is no source info for the package 'linux-2.6' at version '3.2.14-1' with architecture '' Unable to make a source version for version '3.2.14-1' No longer marked as found in versions 3.2.14-1. quit Stopping processing here. Please contact me if you need assistance. -- 669046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133839174220964.transcr...@bugs.debian.org
Bug#664767: Brcmsmac driver woes, possible regression?
2012/5/27 Jonathan Nieder jrnie...@gmail.com: Thanks. I assume you mean the brcms_c_wait_... warning when you refer to an oops. Separating the symptoms: brcms_c_wait_for_tx_completion warning: bug#672891 connection resets, segfaults, general instability: bug#664767 (this bug) AMPDU status: BA Timeout: bug#674430 (...) Yup, that can be. Anyway, after having loaded kernel 3.2.19 (with the set of patches applied) for all the weekend and until today, I've experienced NO reconnects nor random connection downs which means the wireless link runs stable and at least it's usable here :-) Is there any chance for these patches hit wheezy when is relased or get into testing? I've just read Ben's announcement about the availabilty of 3.2.19-1 kernel in a few days and having these patches would improve things a lot for users experincining these issues or similar problems with brcmsmac. Greetings, -- Camaleón -- 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/CAKprTDFHmBuOorCo4evrYrNEi2-gJov0mQXQpEjoRJicfhWg=a...@mail.gmail.com
Bug#675190: BUG: unable to handle kernel paging request at 27c97000 during reboot under xen
On Wed, 2012-05-30 at 17:53 +0400, George Shuklin wrote: [ 280.608438] BUG: unable to handle kernel paging request at 27c97000 [ 280.608448] IP: [c1229e86] linkwatch_do_dev+0x8e/0x94 [ 280.608460] *pdpt = 02a8a027 *pde = [ 280.608470] Oops: 0002 [#1] SMP Thanks, I think I know what's going on here (patch attached) the ordering of the teardown in xennet_remove looks a bit wonky for me. In particular it unregisters the netdev before brining the carrier down and before unregistering the sysfs files, both of which seem wrong. I actually saw a different backtrace from each of those, the one above is due to unregistering before bringing the carrier down. I still need to properly test (and understand) the fix. I just checked Squeeze and it is fine so I'll need to track it back to see where it came in for stable@ purposes. I'm on training tomorrow but hopefully on Friday I'll send a patch to netdev@. Cheers, Ian. -- Ian Campbell Paranoia is heightened awareness. From 7579a7cd48154e6374d8543448a53018b25266b0 Mon Sep 17 00:00:00 2001 From: Ian Campbell ian.campb...@citrix.com Date: Wed, 30 May 2012 17:19:03 +0100 Subject: [PATCH] xen/netfront: teardown the device before unregistering it. Fixes: [ 15.470311] WARNING: at /local/scratch/ianc/devel/kernels/linux/fs/sysfs/file.c:498 sysfs_attr_ns+0x95/0xa0() [ 15.470326] sysfs: kobject eth0 without dirent [ 15.470333] Modules linked in: [ 15.470342] Pid: 12, comm: xenwatch Not tainted 3.4.0-x86_32p-xenU #93 and [9.150554] BUG: unable to handle kernel paging request at 2b359000 [9.150577] IP: [c1279561] linkwatch_do_dev+0x81/0xc0 [9.150592] *pdpt = 2c3c9027 *pde = [9.150604] Oops: 0002 [#1] SMP [9.150613] Modules linked in: Reported-by: George Shuklin george.shuk...@gmail.com Signed-off-by: Ian Campbell ian.campb...@citrix.com Cc: sta...@kernel.org --- drivers/net/xen-netfront.c |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net/xen-netfront.c b/drivers/net/xen-netfront.c index 0ebbb19..796afbf 100644 --- a/drivers/net/xen-netfront.c +++ b/drivers/net/xen-netfront.c @@ -1935,14 +1935,14 @@ static int __devexit xennet_remove(struct xenbus_device *dev) dev_dbg(dev-dev, %s\n, dev-nodename); - unregister_netdev(info-netdev); - xennet_disconnect_backend(info); - del_timer_sync(info-rx_refill_timer); - xennet_sysfs_delif(info-netdev); + unregister_netdev(info-netdev); + + del_timer_sync(info-rx_refill_timer); + free_percpu(info-stats); free_netdev(info-netdev); -- 1.7.2.5 signature.asc Description: This is a digitally signed message part
Bug#674411: linux-image-2.6.32-5-xen-686: Kernel crashes if AIO is used on pages belonging to guests
On Thu, 2012-05-24 at 11:57 +, George Dunlap wrote: Package: linux-2.6 Version: 2.6.32-45 Severity: normal The kernel version in this package does not handle AIO to pages owned by guest domains (foreign domains) properly. Newer versions of qemu will attempt to use AIO for disk reads and writes; this causes domain 0 to crash if you're running. Thanks George. Do you happen to have a log of the actual kernel crash? I think Stefano (CCd) has been fixing this issue (or at least one which sounds very similar) in the upstream kernels recently. Stefano is there anything specific I can backport to a Jeremy xen.git 2.6.32 style pvops kernel? Or is there another appropriate fix? FYI Squeeze's kernel is based on e73f4955a821 from Jeremy's tree, although with a bunch of fixes backported too. Thanks, Ian. -- Ian Campbell Likewise, the national appetizer, brine-cured herring with raw onions, wins few friends, Germans excepted. -- Darwin Porter Scandinavia On $50 A Day signature.asc Description: This is a digitally signed message part
Bug#664767: Brcmsmac driver woes, possible regression?
found 664767 linux-2.6/3.2.12-1 tags 664767 - moreinfo quit Camaleón wrote: Anyway, after having loaded kernel 3.2.19 (with the set of patches applied) for all the weekend and until today, I've experienced NO reconnects nor random connection downs which means the wireless link runs stable and at least it's usable here :-) Nice. Let's call that a success. Kernel team: here is a list of the patches[*] Camaleón applied: 6b1a89afbf97 brcm80211: smac: drop 40MHz intolerant flag from HT capability info c261bdf8acad brcm80211: smac: indicate severe problems to Mac80211 0bf1f883fd0a brcm80211: smac: removed MPC related code 4412953061de brcm80211: smac: removed MPC related variables 28237002e726 brcm80211: smac: removed down-on-watchdog MPC functionality 43ac09722f8e brcm80211: smac: removed down-on-rf-kill functionality a8bc4917ed6b brcm80211: smac: bugfix for tx mute in brcms_b_init() c6c44893c864 brcm80211: smac: fixed inconsistency in transmit mute 2646c46d5679 brcm80211: smac: modified Mac80211 callback interface dc460127898c brcm80211: smac: mute transmit on ops_start 1525662ac280 brcm80211: smac: changed check to confirm STA only support b7eec4233c34 brcm80211: smac: replace own access category definitions with mac80211 enum e9ca530a7b18 brcm80211: smac: don't modify sta parameters when adding sta 8906c43cb160 brcm80211: smac: fix channel frequency 02a588a2e3b9 brcm80211: smac: combine promiscuous mode functionality be667669ec01 brcm80211: smac: added support for mac80211 filter flags [d3f311349add brcm80211: fix usage of set tx power] --- unrelated, my mistake aa1f2f0a3218 brcm80211: smac: precendence bug in wlc_phy_attach() 1570e53c14ff brcm80211: smac: fix unintended fallthru in wlc_phy_radio_init_2057() 137dabed34a1 brcm80211: smac: remove smatch warnings from brcmsmac code 2b0a53d51b5f brcm80211: smac: only print block-ack timeout message at trace level 6b8da423315b brcm80211: smac: do not use US as fallback regulatory hint 94a2ca311cf4 brcm80211: smac: only provide valid regulatory hint It's not clear to me which of these addresses the memory corruption and random reconnects Camaleón was experiencing. I think we should take them all. (It's basically a backport of brcmsmac changes to date, minus the switch to BCMA.) Commit 2b0a53d51b5f (only print block-ack timeout message at trace level) addresses the distracting log noise from bug#674430. Commits c261bdf8acad (reset mac80211 too when resetting) and 2646c46d5679 (disable rx on ops_stop) sound useful but their descriptions don't mention the symptoms. 8906c43cb160 (fix channel 216 frequency) and 1570e53c14ff (don't treat 2057 radio rev 5 like rev 7) also look like obviously good fixes. Likewise for 137dabed34a1 (avoid NULL pointer dereference, especially when memory is short) though it wouldn't have caused Camaleón's trouble. Commits 6b1a89afbf97 (drop 40MHz intolerant flag from HT capability info), 6b8da423315b (do not use US as fallback regulatory hint), and 94a2ca311cf4 (only pass valid regulatory hints to cfg80211) affect the channel used and might explain why the connection is more stable. Thanks, Jonathan [*] http://bugs.debian.org/664767#99 -- 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/20120530172713.GH3908@burratino
Processed: Re: Brcmsmac driver woes, possible regression?
Processing commands for cont...@bugs.debian.org: found 664767 linux-2.6/3.2.12-1 Bug #664767 [linux-2.6] Brcmsmac driver woes, possible regression? Marked as found in versions linux-2.6/3.2.12-1. tags 664767 - moreinfo Bug #664767 [linux-2.6] Brcmsmac driver woes, possible regression? Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 664767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133839884825401.transcr...@bugs.debian.org
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
On 05/30/2012 08:08 AM, micah anderson wrote: Hi all, Its been 2 months without a reply on this issue, and we are getting close to a freeze. Kees and John it looks like there are some pending questions for you below, it would be great if you could chime in with your opinons: If the Debian kernel team was willing to carry some kind of AppArmor kernel/userspace interface patch, I'm now unsure if the old or new ones would be better suited. (I assume AppArmor 2.8 is released long enough before the Wheezy freeze, so that we can ship it in there, and are given this choice.) On the one hand, the old compat' patches are confidence inspiring, as they are small and have been shipped by Ubuntu for a while. My opinon: the 2.4 compat patch is tiny, and it works well, and has been tested for some time, I think it makes the most sense to include this one. probably, especially if you are looking to keep the patch as small as possible On the other hand, it seems the new patches are being upstreamed, which makes them more appealing somehow than the older ones. The newer patch is bigger, some of it must be backported from Linux 3.4, some from Ubuntu, it is much less tested and I suspect because of that will encounter much more resistance from Debian's kernel team to include it. Presumably this will eventually be the one that will be upstreamed, but it isn't there yet. This is why I think the 2.4 compat patch is the way to go with Wheezy, when the newer patch is upstreamed that can be swapped out then. yeah to clarify, half of the new interface went upstream in 3.4 and I can provide a version of that that is backported but its a few patches and not as small as the compat patch. In addition to that you would need a compatibility patch on top of that, that provides the features the current upstream interface doesn't John, I think it would help if you could please point us more precisely to the commits of the new interface that have been upstreamed already, and to the ones that have not been, so that we can get a rough idea of where things are at. hrmmm, I think I missed answering this before the upstream patches 9acd494be9387b0608612cd139967201dd7a4e12 e74abcf3359d0130e99a6511ac484a3ea9e6e988 a9bf8e9fd561ba9ff1f0f2a1d96e439fced4 d384b0a1a35f87f0ad70c29518f98f922b1c15cb the additional patch to complete the interface git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor v3.4-aa2.8 8de755e4dfdbc40bfcaca848ae6b5aeaf0ede0e8 vs. the old compat patch git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor da1ce2265ebb70860b9c137a542e48b170e4606b Kees, others, what do you think? While I like to see the latest stuff, I think the old patch is a smaller delta, well tested and going to be less to maintain so it really seems the way to go. -- 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/4fc6b14b.70...@canonical.com
Bug#664767: Brcmsmac driver woes, possible regression?
On Wed, 2012-05-30 at 12:27 -0500, Jonathan Nieder wrote: found 664767 linux-2.6/3.2.12-1 tags 664767 - moreinfo quit Camaleón wrote: Anyway, after having loaded kernel 3.2.19 (with the set of patches applied) for all the weekend and until today, I've experienced NO reconnects nor random connection downs which means the wireless link runs stable and at least it's usable here :-) Nice. Let's call that a success. Kernel team: here is a list of the patches[*] Camaleón applied: 6b1a89afbf97 brcm80211: smac: drop 40MHz intolerant flag from HT capability info c261bdf8acad brcm80211: smac: indicate severe problems to Mac80211 0bf1f883fd0a brcm80211: smac: removed MPC related code 4412953061de brcm80211: smac: removed MPC related variables 28237002e726 brcm80211: smac: removed down-on-watchdog MPC functionality 43ac09722f8e brcm80211: smac: removed down-on-rf-kill functionality a8bc4917ed6b brcm80211: smac: bugfix for tx mute in brcms_b_init() c6c44893c864 brcm80211: smac: fixed inconsistency in transmit mute 2646c46d5679 brcm80211: smac: modified Mac80211 callback interface dc460127898c brcm80211: smac: mute transmit on ops_start 1525662ac280 brcm80211: smac: changed check to confirm STA only support b7eec4233c34 brcm80211: smac: replace own access category definitions with mac80211 enum e9ca530a7b18 brcm80211: smac: don't modify sta parameters when adding sta 8906c43cb160 brcm80211: smac: fix channel frequency 02a588a2e3b9 brcm80211: smac: combine promiscuous mode functionality be667669ec01 brcm80211: smac: added support for mac80211 filter flags [d3f311349add brcm80211: fix usage of set tx power] --- unrelated, my mistake aa1f2f0a3218 brcm80211: smac: precendence bug in wlc_phy_attach() 1570e53c14ff brcm80211: smac: fix unintended fallthru in wlc_phy_radio_init_2057() 137dabed34a1 brcm80211: smac: remove smatch warnings from brcmsmac code 2b0a53d51b5f brcm80211: smac: only print block-ack timeout message at trace level 6b8da423315b brcm80211: smac: do not use US as fallback regulatory hint 94a2ca311cf4 brcm80211: smac: only provide valid regulatory hint It's not clear to me which of these addresses the memory corruption and random reconnects Camaleón was experiencing. I think we should take them all. (It's basically a backport of brcmsmac changes to date, minus the switch to BCMA.) [...] I'm sorry but I don't agree. This would seem to leave us with a version of brcmsmac that's quite different from what anyone else uses. Please try to identify which of these are the really important changes and propose them for stable. (It may however be sensible to use the 'compat-wireless' tree as a means to keep wireless drivers updated in wheezy. I keep meaning to look into the details of this and then discuss it with the kernel and release teams.) Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
Processed: tagging 664767
Processing commands for cont...@bugs.debian.org: # We don't have a patch for this specific bug tags 664767 - patch Bug #664767 [linux-2.6] Brcmsmac driver woes, possible regression? Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 664767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133842568931293.transcr...@bugs.debian.org
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
On Wed, 2012-05-30 at 16:46 -0700, John Johansen wrote: On 05/30/2012 08:08 AM, micah anderson wrote: Hi all, Its been 2 months without a reply on this issue, and we are getting close to a freeze. Kees and John it looks like there are some pending questions for you below, it would be great if you could chime in with your opinons: If the Debian kernel team was willing to carry some kind of AppArmor kernel/userspace interface patch, I'm now unsure if the old or new ones would be better suited. (I assume AppArmor 2.8 is released long enough before the Wheezy freeze, so that we can ship it in there, and are given this choice.) On the one hand, the old compat' patches are confidence inspiring, as they are small and have been shipped by Ubuntu for a while. My opinon: the 2.4 compat patch is tiny, and it works well, and has been tested for some time, I think it makes the most sense to include this one. probably, especially if you are looking to keep the patch as small as possible Should I take it that '2.4 compat' actually means '2.4-2.7 compat'? [...] vs. the old compat patch git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor da1ce2265ebb70860b9c137a542e48b170e4606b Kees, others, what do you think? While I like to see the latest stuff, I think the old patch is a smaller delta, well tested and going to be less to maintain so it really seems the way to go. So you're saying we should take just the one quoted above for wheezy? The aafs_create() and aafs_remove() calls are mismatched when CONFIG_SECURITY_APPARMOR_COMPAT_24 is not set, but aside from that it doesn't look too horrible. What about this one: commit 1023c7c2f9d9c5707147479104312c4c3d1a2c2b Author: John Johansen john.johan...@canonical.com Date: Wed Aug 10 22:02:39 2011 -0700 AppArmor: compatibility patch for v5 network controll Add compatibility for v5 network rules. Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
Bug#675093: linux-image-3.2.0-2-amd64: USB timeout initializing reports with Eaton UPS
On Tue, 2012-05-29 at 21:39 +0200, Manu Benoît wrote: Package: linux-2.6 Version: 3.2.18-1 Severity: normal It would seem that the kernel is doing something wrong when trying to initalise an USB connection to an Eaton (formerly Merlin Gerin) Ellipse Max UPS. When the box is booting, the device's initialisation adds a ~15s delay, then some USB error is reported (at timestamp 18.319789 in the kernel log below). Strangely enough, the device appears to work after that. I am reporting this error for the kernel on this computer (which is a x86-64 and includes various tainted modules), however it also occurs on a much older x86 box running a Debian Squeeze with linux-image-2.6.32-5-686 (no proprietary drivers loaded, either). The device connected to that box is a different model of Eaton Ellipse Max UPS. Both UPS's are brand new. [...] [5.167483] usb 2-2.4: New USB device found, idVendor=0463, idProduct= [5.167488] usb 2-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [5.167491] usb 2-2.4: Product: Ellipse MAX [5.167493] usb 2-2.4: Manufacturer: EATON [5.167496] usb 2-2.4: SerialNumber: ADKM25014 [5.208346] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.384134] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.560072] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.736015] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.869976] PM: Starting manual resume from disk [5.869979] PM: Hibernation image partition 254:1 present [5.869980] PM: Looking for hibernation image. [5.870175] PM: Image not found (code -22) [5.870178] PM: Hibernation image not present or could not be loaded. [5.910554] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 18.319789] generic-usb 0003:0463:.0003: usb_submit_urb(ctrl) failed [ 18.319850] generic-usb 0003:0463:.0003: timeout initializing reports [ 18.320070] generic-usb 0003:0463:.0003: hiddev0,hidraw2: USB HID v1.10 Device [EATON Ellipse MAX] on usb-:00:1d.7-2.4/input0 [...] (The full message is logged at http://bugs.debian.org/675093.) Any ideas what's going wrong here? Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
Processed: tagging 675010
Processing commands for cont...@bugs.debian.org: tags 675010 + moreinfo Bug #675010 [linux-2.6] linux-image-3.3.0-trunk-amd64: Please include CONFIG_OPENVSWITCH as a module Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 675010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133842864112429.transcr...@bugs.debian.org
Bug#675010: linux-image-3.3.0-trunk-amd64: Please include CONFIG_OPENVSWITCH as a module
On Tue, 2012-05-29 at 12:18 +0200, Arno Töll wrote: Package: linux-2.6 Version: 3.3.4-1~experimental.1 Severity: wishlist Hi, kernel 3.3 got mainline support for Open vSwitch (CONFIG_OPENVSWITCH / openvswitch.ko) which was previously available as a DKMS module package. This would make the module-assistant and DKMS packages openvswitch-datapath-source and openvswitch-datapath-dkms obsolete. I don't think so. As I understand it, the in-tree version does not yet have all the features of the out-of-tree version, and some features may have to be implemented differently (more integrated with the rest of the kernel). Anyhow this module is required to get openvswitch running on Debian, where the userspace utilities do already exist. [...] Have you tried building the kernel with this option? Does the in-tree module work properly with the existing utilities package? Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
On 05/30/2012 06:10 PM, Ben Hutchings wrote: On Wed, 2012-05-30 at 16:46 -0700, John Johansen wrote: On 05/30/2012 08:08 AM, micah anderson wrote: Hi all, Its been 2 months without a reply on this issue, and we are getting close to a freeze. Kees and John it looks like there are some pending questions for you below, it would be great if you could chime in with your opinons: If the Debian kernel team was willing to carry some kind of AppArmor kernel/userspace interface patch, I'm now unsure if the old or new ones would be better suited. (I assume AppArmor 2.8 is released long enough before the Wheezy freeze, so that we can ship it in there, and are given this choice.) On the one hand, the old compat' patches are confidence inspiring, as they are small and have been shipped by Ubuntu for a while. My opinon: the 2.4 compat patch is tiny, and it works well, and has been tested for some time, I think it makes the most sense to include this one. probably, especially if you are looking to keep the patch as small as possible Should I take it that '2.4 compat' actually means '2.4-2.7 compat'? yeah it turned out to be that. The rewrite to use the newer LSM path hooks began after 2.4, and the patch provided the 2.4 interface until a newer interface that was more sysfs in style could be created. [...] vs. the old compat patch git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor da1ce2265ebb70860b9c137a542e48b170e4606b Kees, others, what do you think? While I like to see the latest stuff, I think the old patch is a smaller delta, well tested and going to be less to maintain so it really seems the way to go. So you're saying we should take just the one quoted above for wheezy? The aafs_create() and aafs_remove() calls are mismatched when CONFIG_SECURITY_APPARMOR_COMPAT_24 is not set, but aside from that it doesn't look too horrible. oops I guess we never built it that way, I can fix that for you What about this one: commit 1023c7c2f9d9c5707147479104312c4c3d1a2c2b Author: John Johansen john.johan...@canonical.com Date: Wed Aug 10 22:02:39 2011 -0700 AppArmor: compatibility patch for v5 network controll Add compatibility for v5 network rules. That will provide support for the network rules and if you are willing to carry it that would be greate but is not strictly necessary. Policy can still be loaded and introspected. If that patch is missing and if profile contains network rules the parser will complain about them not being enforced, but it will still load and enforce the rest of the policy -- 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/4fc6dee6.9090...@canonical.com
Processed: tagging 661057
Processing commands for cont...@bugs.debian.org: tags 661057 + pending Bug #661057 [linux-2.6] linux-2.6: hpsa driver does not support multipath on Smart Array 712m with latest firmware Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 661057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13384337053530.transcr...@bugs.debian.org
Processed: tagging 671292
Processing commands for cont...@bugs.debian.org: tags 671292 + pending Bug #671292 [linux-2.6] Logitech wireless does not work on xorg or gpm Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 671292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13384337113571.transcr...@bugs.debian.org
Processed: tagging 661151
Processing commands for cont...@bugs.debian.org: tags 661151 + pending Bug #661151 [linux-2.6] linux-2.6: lacks AppArmor kernel/userspace interface Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 661151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13384343506529.transcr...@bugs.debian.org
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
On Wed, 2012-05-30 at 20:00 -0700, John Johansen wrote: On 05/30/2012 06:10 PM, Ben Hutchings wrote: [...] vs. the old compat patch git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor da1ce2265ebb70860b9c137a542e48b170e4606b Kees, others, what do you think? While I like to see the latest stuff, I think the old patch is a smaller delta, well tested and going to be less to maintain so it really seems the way to go. So you're saying we should take just the one quoted above for wheezy? The aafs_create() and aafs_remove() calls are mismatched when CONFIG_SECURITY_APPARMOR_COMPAT_24 is not set, but aside from that it doesn't look too horrible. oops I guess we never built it that way, I can fix that for you It would be an odd configuration but someone might use it and it would fail to build. Trivial for me to fix up, anyway. What about this one: commit 1023c7c2f9d9c5707147479104312c4c3d1a2c2b Author: John Johansen john.johan...@canonical.com Date: Wed Aug 10 22:02:39 2011 -0700 AppArmor: compatibility patch for v5 network controll Add compatibility for v5 network rules. That will provide support for the network rules and if you are willing to carry it that would be greate but is not strictly necessary. Policy can still be loaded and introspected. If that patch is missing and if profile contains network rules the parser will complain about them not being enforced, but it will still load and enforce the rest of the policy Looking back over the bug log, I see that wasn't requested, so I'm only applying 'AppArmor: compatibility patch for v5 interface' now. Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
Bug#664767: Brcmsmac driver woes, possible regression?
Ben Hutchings wrote: On Wed, 2012-05-30 at 12:27 -0500, Jonathan Nieder wrote: 6b1a89afbf97 brcm80211: smac: drop 40MHz intolerant flag from HT capability info c261bdf8acad brcm80211: smac: indicate severe problems to Mac80211 0bf1f883fd0a brcm80211: smac: removed MPC related code [...] and random reconnects Camaleón was experiencing. I think we should take them all. (It's basically a backport of brcmsmac changes to date, minus the switch to BCMA.) [...] I'm sorry but I don't agree. This would seem to leave us with a version of brcmsmac that's quite different from what anyone else uses. Please try to identify which of these are the really important changes and propose them for stable. Fair enough. I think we'll need help from upstream to figure that out. [...] (It may however be sensible to use the 'compat-wireless' tree as a means to keep wireless drivers updated in wheezy. I keep meaning to look into the details of this and then discuss it with the kernel and release teams.) I don't think that's a good idea unless it's a separate package, since wireless drivers get their fair share of regressions just like the rest of the kernel and there is no equivalent of stable for driver backports. But as a separate package that could be frequently updated through backports.debian.org it might be nice. 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/20120531045954.GA1447@burratino
Bug#675302: linux-image-3.2.0-2-amd64: system totally hands when using nouveau
Package: linux-2.6 Version: 3.2.17-1 Severity: important Dear Maintainer, * What led up to the situation? Wanted to change back from the nonfree nvidia driver to nouveau. * What exactly did you do (or not do) that was effective (or ineffective)? Tried removing the nvidia stuff and booting up with nouveau. * What was the outcome of this action? Total system hang as soon as xorg starts. No response from keyboard, mouse, no response on the network (no ping, no ARP response) * What outcome did you expect instead? Something better! Using an Nvidia GeForce GT 520. I tried a new, clean install of wheezy. After installing lxde (my favorite), the system freezes as the moment when gdm3 starts up. I'm pretty certain this is not debian-specific, since I tried booting up parted magic (v. 2012_05_30) from a USB stick. It does the same exact thing. However parted magic works when I choose the xvesa boot option. The nouveau driver is still in use but I guess the fact that only non-accelerated VESA modes are being used helps. A while back (like around linux 3.0.0) nouveau and gnome 2.30 did work on this same machine, at the time I changed to the nvidia drivers for more minor issues. I'm filing this against the kernel since this is a total system hang. The system information below is generated from my working system, using the nvidia driver. -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.17-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Sat May 12 23:08:28 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/nws_vg0-rootfs ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [5.724696] PM: Image not found (code -22) [5.724698] PM: Hibernation image not present or could not be loaded. [5.765388] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [7.093488] udevd[399]: starting version 175 [7.664239] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 [7.664243] ACPI: Power Button [PWRB] [7.664319] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [7.664321] ACPI: Power Button [PWRF] [7.725543] input: PC Speaker as /devices/platform/pcspkr/input/input4 [7.755010] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [7.867662] Marking TSC unstable due to TSC halts in idle [7.867668] ACPI: acpi_idle registered with cpuidle [7.868903] Switching to clocksource hpet [7.878614] iTCO_vendor_support: vendor-support=0 [7.950400] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [7.950492] iTCO_wdt: Found a ICH10R TCO device (Version=2, TCOBASE=0x0460) [7.950566] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [7.972393] snd_hda_intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [7.972441] snd_hda_intel :00:1b.0: irq 48 for MSI/MSI-X [7.972471] snd_hda_intel :00:1b.0: setting latency timer to 64 [8.009769] tpm_tis 00:09: 1.2 TPM (device-id 0xB, rev-id 16) [8.194326] hda_codec: ALC889A: BIOS auto-probing. [8.203338] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input5 [8.203836] snd_hda_intel :01:00.1: PCI INT B - GSI 17 (level, low) - IRQ 17 [8.203839] hda_intel: Disabling MSI [8.203876] snd_hda_intel :01:00.1: setting latency timer to 64 [8.467460] Linux media interface: v0.10 [8.496188] nvidia: module license 'NVIDIA' taints kernel. [8.496191] Disabling lock debugging due to kernel taint [8.69] Linux video capture interface: v2.00 [8.696074] tpm_tis 00:09: Adjusting TPM timeout parameters. [8.700016] HDMI status: Codec=0 Pin=4 Presence_Detect=0 ELD_Valid=0 [8.700526] uvcvideo: Found UVC 1.00 device unnamed (046d:0990) [8.714893] input: UVC Camera (046d:0990) as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input6 [8.714981] usbcore: registered new interface driver uvcvideo [8.714982] USB Video Class driver (1.1.1) [8.732021] HDMI status: Codec=0 Pin=5 Presence_Detect=0 ELD_Valid=0 [8.748101] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input7 [8.748197] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input8 [8.748461] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [8.748471] nvidia :01:00.0: setting latency timer to 64 [8.748477] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [8.748651] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 295.49 Mon Apr 30 23:46:33 PDT 2012 [9.057232] usbcore: registered new interface driver snd-usb-audio [9.468054] parport_pc 00:08: reported by Plug and Play ACPI [9.468107] parport0:
