Bug#676873: nouveau: VM: trapped read at 0x0000000000 on ch 4 [0x0000a9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT
Package: linux-2.6 Version: 3.0.0-6 Severity: normal Periodically X-server stops to work: 1) No screen updated 2) No switching to text console (Mouse cursor is moving) dmesg shows: [111463.425953] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111463.425961] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111463.425966] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111463.425968] [drm] nouveau :01:00.0: PGRAPH - TRAP [111463.425971] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x0f04 data 0x3d10812e [111467.695915] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.695923] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.695926] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.695931] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.695942] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.695952] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.695958] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.695962] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.695966] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.695974] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.695984] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.695990] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.695992] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.695996] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.696010] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.696020] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.696027] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.696029] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.696033] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.696048] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT [111467.696057] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH FAULT [111467.696062] [drm] nouveau :01:00.0: PGRAPH - TRAP_VFETCH 00f0 fe0c [111467.696064] [drm] nouveau :01:00.0: PGRAPH - TRAP [111467.696068] [drm] nouveau :01:00.0: PGRAPH - ch 4 (0x000a9ac000) subc 5 class 0x8297 mthd 0x15f0 data 0x009c0099 [111467.696076] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on ch 4 [0xa9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT (repeated many times) -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 1406 board_vendor: ASUSTeK Computer INC. board_name: P5Q board_version: Rev 1.xx ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:82d3] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e21] (rev 03) (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- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: a000-afff Memory behind bridge: fa00-fe8f Prefetchable memory behind bridge: d000-dfff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel
Bug#676873: nouveau: VM: trapped read at 0x0000000000 on ch 4 [0x0000a9ac] PGRAPH/VFETCH/00 reason: PT_NOT_PRESENT
George Shuklin wrote: Package: linux-2.6 Version: 3.0.0-6 Is this the same machine as bug#676704? (If so, I prefer to track all symptoms in one place.) Do the VM: trapped read errors happen in 3.0.y only? That kernel is not maintained in Debian --- supported versions are 2.6.32.y, 3.2.y, and 3.4.y at the moment. 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/20120610093200.GA30151@burratino
Bug#676866: linux-image-3.2.0-2-686-pae: won't boot under xen
reassign 676866 src:linux-2.6 3.2.19-1 forcemerge 676360 676866 quit Hi, Gedalya wrote: dist-upgrade, got linux 3.2.19-1 [...] [0.447219] BUG: unable to handle kernel paging request at dd9c4dd8 [0.447227] IP: [c1162d5c] atomic64_read_cx8+0x4/0xc Yep. http://bugs.debian.org/676360 has some context. Sorry for the trouble, 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/20120610100253.GD30151@burratino
Processed: Re: Lid switch correct every other time; suspend every other lid close; Samsung N150-11 netbook
Processing commands for cont...@bugs.debian.org: tags 594149 - moreinfo Bug #594149 [linux-2.6] linux-image-2.6.32-5-amd64: Lid switch correct every other time; suspend every other lid close; Samsung N150-11 netbook Removed tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 594149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594149 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.133932206017199.transcr...@bugs.debian.org
Processed: Re: linux-image-3.2.0-2-686-pae: won't boot under xen
Processing commands for cont...@bugs.debian.org: reassign 676866 src:linux-2.6 3.2.19-1 Bug #676866 [linux-2.6] linux-image-3.2.0-2-686-pae: won't boot under xen Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. No longer marked as found in versions 3.2.19-1. Ignoring request to alter fixed versions of bug #676866 to the same values previously set Bug #676866 [src:linux-2.6] linux-image-3.2.0-2-686-pae: won't boot under xen Marked as found in versions linux-2.6/3.2.19-1. forcemerge 676360 676866 Bug #676360 [src:linux-2.6] xen: oops at atomic64_read_cx8+0x4 Bug #676360 [src:linux-2.6] xen: oops at atomic64_read_cx8+0x4 Marked as found in versions linux-2.6/3.2.19-1. Bug #676866 [src:linux-2.6] linux-image-3.2.0-2-686-pae: won't boot under xen Severity set to 'serious' from 'important' Marked as found in versions linux-2.6/3.2.18-1. Added tag(s) upstream, pending, and patch. Merged 676360 676866 quit Stopping processing here. Please contact me if you need assistance. -- 676360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676360 676866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676866 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.133932259920079.transcr...@bugs.debian.org
Bug#648939: Possible solution
I seem to have the same problem with my laptop (asus ul30a-a2 running debian testing, xfce 4.8, kernel 3.2.0-2-amd64; my mouse is an Evoluent VerticalMouse 3) The solution found here (https://bbs.archlinux.org/viewtopic.php?id=123553) is working for me so far. Essentially you edit /etc/laptop-mode/conf.d/usb-autosuspend.conf and add the usb id of your mouse to the blacklist. -- 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/20120610093714.6a68404258e273e5628b3...@gmail.com
Bug#623177: linux-2.6: Please enable CONFIG_CRASH_DUMP on x86 architectures
On Sun, 2012-06-10 at 00:44 -0700, John Wright wrote: On Sat, Jun 02, 2012 at 07:02:11PM +0100, Ben Hutchings wrote: The help text for this option is: Generate crash dump after being started by kexec. This should be normally only set in special crash dump kernels which are loaded in the main kernel with kexec-tools into a specially reserved region and then later executed after a crash by kdump/kexec. ... Are you asking us to add a kdump flavour, as some other distributions do? It's not necessary to have another flavor. Kernels built with this option work just fine as regular kernels too (in fact, the ia64 and probably some other kernels are already built this way). As I recall, as the kernel is currently built, it can be loaded as a crash kernel, and kexec'ed successfully upon kernel panic; however, CONFIG_CRASH_DUMP is required to enable /proc/vmcore in the newly booted kernel, which contains the memory of the crashed kernel. Then, a tool like 'makedumpfile' can read the core, stripping out user and zero pages, and write a small dump file that can be analyzed with tools like 'crash'. The help text for CRASH_DUMP on x86 says: Generate crash dump after being started by kexec. This should be normally only set in special crash dump kernels ... Since this is not the only use for kexec, I don't believe we should enable this in the currently defined flavours (or that it should have been enabled for ia64). As I said, other distributions have a separate kdump flavour, presumably for this reason. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Re: Debian and Hyper-V VM drivers
On Mon, 2012-05-14 at 23:21 +0100, Ben Hutchings wrote: On Mon, May 14, 2012 at 08:33:23PM +, Mike Sterling wrote: [...] We've done a lot of work with Andy Whitcroft at Canonical to get the drivers integrated into Ubuntu 12.04 and higher. What we'd like to discuss is doing the same thing for Debian. What would be the best way to start or discuss this effort? The drivers were already updated (in 3.2.15-1). I have a to-do item to look at tools/hv and build those tools from the linux-tools source package, but it wouldn't hurt for you to open a bug report requesting it. If you can provide a patch then that would make it a lot easier to fix. Currently the linux-tools source package in Debian builds binary packages that are specific to upstream kernel versions (linux-kbuild-3.2, linux-tools-3.2), I assume tools/hv is not version-specific and therefore it would belong in a new package, say, 'linux-tools-common' (*not* 'linux-tools', which somewhat confusingly is a meta-package). So I've had a proper look at tools/hv now, and I'm not very impressed. The problems I've found so far (by inspection): 1. The daemon leaks a file handle on every configuration update. 2. It doesn't check for write failures, and it doesn't check correctly for read failures. 3. It stores state in /var/opt/hyperv, which is only appropriate for programs installed in /opt. This should be configurable at build time. 4. The protocol between driver and daemon does not appear to be stable. Do they need to be upgraded in lockstep, or will either be backward- compatible with older versions of the other? 5. The daemon uses incorrect types for strings, resulting in a large number of compiler warnings when building with 'gcc -Wall' (which is generally good practice). 6. When and how should the daemon be started? There is no init script (or upstart job) provided, either in the linux source or the Ubuntu packaging. [Less important:] 7. There is no Makefile, and the one added by Ubuntu is incorrect (make install doesn't respect $(DESTDIR)). 8. The daemon doesn't detect or parse the OS release correctly (even, so far as I can see, on the distributions which it has explicit support for). 9. Permissions of S_IRUSR | S_IWUSR | S_IROTH (octal 604) make no sense. According to the manual page, 'This pairing allows the Hyper-V host to pass configuration information (such as IP addresses) to the guest...' but I don't see any sign that the daemon actually applies any configuration. Is this intended to be done by some other 'guest tool' distributed by Microsoft? Is that the reason for (3) and/or (6)? Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#648939: USB mouse stops work on battery power (Re: Possible solution)
Hi Ben, Ben Addis wrote: [Subject: Bug#648939: Possible solution] Please keep in mind that these appear as emails in a crowded inbox, so the subject line can be a good place to put valuable context. I seem to have the same problem with my laptop (asus ul30a-a2 running debian testing, xfce 4.8, kernel 3.2.0-2-amd64; my mouse is an Evoluent VerticalMouse 3) Do you mean that the mouse works when the laptop is connected to power but stops about 20 seconds after power is disconnected, that reconnecting power gets the mouse working again, and that this is a regression introcued at some point between 2.6.32 and 3.0? The solution found here (https://bbs.archlinux.org/viewtopic.php?id=123553) is working for me so far. Essentially you edit /etc/laptop-mode/conf.d/usb-autosuspend.conf and add the usb id of your mouse to the blacklist. Please attach output from reportbug --template linux-image-$(uname -r) so we can work on diagnosing and fixing (or at least automatically working around) the underlying problem. 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/20120610160834.GA32036@burratino
Bug#671801: Wacom tablet in Thinkpad X220 Tablet not working with linux-image-3.2.0-2-amd64_3.2.18-1_amd64
Hello, the wacom tablet in my Thinkpad x220t stopped working after the update to linux-image-3.2.0-2-amd64_3.2.18-1_amd64. (The same also occurs with the 3.4 kernel in sid.) I am posting this as a comment to this bug because the changelog indicates that this was the only wacom-related change from version 17 to 18. lsusb knowns my tablet as Bus 002 Device 004: ID 056a:00e6 Wacom Co., Ltd With version 18 and above lsusb -t gives Port 5: Dev 4, If 0, Class=HID, Driver=, 12M instead of the expected Port 5: Dev 4, If 0, Class=HID, Driver=wacom, 12M and consequently the device does not work. During booting I see the following in /dev/log/syslog: input: Wacom ISDv4 E6 Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input7 However, afterwords the corresponding input directory and especially the file input/input7 is not there. Reloading the wacom module does not change the situation and only produces the following in /dev/log/syslog: usbcore: deregistering interface driver wacom usbcore: registered new interface driver wacom wacom: v1.53:USB Wacom tablet driver After going back to version 17 of linux-image everything works again. Best regards Nils signature.asc Description: This is a digitally signed message part
Bug#671801: Wacom tablet in Thinkpad X220 Tablet not working with linux-image-3.2.0-2-amd64_3.2.18-1_amd64
Hi! Nils Kanning wrote: the wacom tablet in my Thinkpad x220t stopped working after the update to linux-image-3.2.0-2-amd64_3.2.18-1_amd64. (The same also occurs with the 3.4 kernel in sid.) I am posting this as a comment to this bug because the changelog indicates that this was the only wacom-related change from version 17 to 18. Please file a new bug. Many thanks, 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/20120610171138.GA32613@burratino
Bug#669120: marked as done ([s390] unreliable timekeeping yielding observable time warps)
Your message dated Sun, 10 Jun 2012 12:32:11 -0500 with message-id 20120610173211.GA420@burratino and subject line Re: [s390] unreliable timekeeping yielding observable time warps has caused the Debian Bug report #669120, regarding [s390] unreliable timekeeping yielding observable time warps to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 669120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.32-41 Severity: important The kernel in squeeze does not allow for repeatable measurements, because the wrong multiplier is used for the time calculation. This is due to it missing patch 157a1a27d5921fc94db8c14e0d01363d13de99b5, which was accepted for v2.6.34-rc6 and Cc'ed to stable. The commit fixing it for some other architectures (0696b711e) was backported into 2.6.32 stable. | [S390] vdso: use ntp adjusted clock multiplier | | Commit timekeeping: Fix clock_gettime vsyscall time warp (0696b711e) | introduced the new parameter mult to update_vsyscall(). This parameter | contains the internal NTP adjusted clock multiplier. | | The s390x vdso did not use this adjusted multiplier. Instead, it used | the constant clock multiplier for gettimeofday() and clock_gettime() | variants. This may result in observable time warps as explained in | commit 0696b711e. | | Make the NTP adjusted clock multiplier available to the s390x vdso | implementation and use it for time calculations. | | Cc: sta...@kernel.org | Signed-off-by: Hendrik Brueckner brueck...@linux.vnet.ibm.com | Signed-off-by: Martin Schwidefsky schwidef...@de.ibm.com I can confirm that the attached backported patch builds and works fine on s390 and it should be placed in bugfix/s390. Kind regards Philipp Kern From 42801c420e59d52003e5ded9658fe8fa599ecaf0 Mon Sep 17 00:00:00 2001 From: Hendrik Brueckner brueck...@linux.vnet.ibm.com Date: Thu, 22 Apr 2010 17:17:06 +0200 Subject: [PATCH] [S390] vdso: use ntp adjusted clock multiplier Commit timekeeping: Fix clock_gettime vsyscall time warp (0696b711e) introduced the new parameter mult to update_vsyscall(). This parameter contains the internal NTP adjusted clock multiplier. The s390x vdso did not use this adjusted multiplier. Instead, it used the constant clock multiplier for gettimeofday() and clock_gettime() variants. This may result in observable time warps as explained in commit 0696b711e. Make the NTP adjusted clock multiplier available to the s390x vdso implementation and use it for time calculations. Cc: sta...@kernel.org Signed-off-by: Hendrik Brueckner brueck...@linux.vnet.ibm.com Signed-off-by: Martin Schwidefsky schwidef...@de.ibm.com --- arch/s390/include/asm/vdso.h|1 + arch/s390/kernel/asm-offsets.c |1 + arch/s390/kernel/time.c |1 + arch/s390/kernel/vdso32/clock_gettime.S | 12 ++-- arch/s390/kernel/vdso32/gettimeofday.S |6 +++--- arch/s390/kernel/vdso64/clock_gettime.S |4 ++-- arch/s390/kernel/vdso64/gettimeofday.S |2 +- 7 files changed, 15 insertions(+), 12 deletions(-) diff --git a/arch/s390/include/asm/vdso.h b/arch/s390/include/asm/vdso.h index 4a76d94..533f357 100644 --- a/arch/s390/include/asm/vdso.h +++ b/arch/s390/include/asm/vdso.h @@ -29,6 +29,7 @@ struct vdso_data { __u32 tz_minuteswest; /* Minutes west of Greenwich 0x30 */ __u32 tz_dsttime; /* Type of dst correction 0x34 */ __u32 ectg_available; + __u32 ntp_mult; /* NTP adjusted multiplier 0x3C */ }; struct vdso_per_cpu_data { diff --git a/arch/s390/kernel/asm-offsets.c b/arch/s390/kernel/asm-offsets.c index 63e4643..7ffc4c0 100644 --- a/arch/s390/kernel/asm-offsets.c +++ b/arch/s390/kernel/asm-offsets.c @@ -52,6 +52,7 @@ int main(void) DEFINE(__VDSO_WTOM_NSEC, offsetof(struct vdso_data, wtom_clock_nsec)); DEFINE(__VDSO_TIMEZONE, offsetof(struct vdso_data, tz_minuteswest)); DEFINE(__VDSO_ECTG_OK, offsetof(struct vdso_data, ectg_available)); + DEFINE(__VDSO_NTP_MULT, offsetof(struct vdso_data, ntp_mult)); DEFINE(__VDSO_ECTG_BASE, offsetof(struct vdso_per_cpu_data, ectg_timer_base)); DEFINE(__VDSO_ECTG_USER, diff --git a/arch/s390/kernel/time.c b/arch/s390/kernel/time.c index 68e1ecf..7ad595a 100644 --- a/arch/s390/kernel/time.c +++ b/arch/s390/kernel/time.c @@ -228,6 +228,7 @@ void update_vsyscall(struct timespec *wall_time, struct clocksource *clock, vdso_data-xtime_clock_nsec = xtime.tv_nsec; vdso_data-wtom_clock_sec = wall_to_monotonic.tv_sec; vdso_data-wtom_clock_nsec = wall_to_monotonic.tv_nsec; +
Bug#669335: marked as done (linux-image-2.6.32-5-686-bigmem: 86-mm-Fix-pgd_lock-deadlock.patch)
Your message dated Sun, 10 Jun 2012 12:30:04 -0500 with message-id 20120610173004.GA385@burratino and subject line Re: [squeeze] 86-mm-Fix-pgd_lock-deadlock.patch has caused the Debian Bug report #669335, regarding linux-image-2.6.32-5-686-bigmem: 86-mm-Fix-pgd_lock-deadlock.patch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 669335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-686-bigmem Version: 2.6.32-41squeeze2 Severity: important We received several problem reports from our customers and also experienced the following bug when running said kernel with =2 CPUs in a virtualization environbment (KVM and VMWare ESX). After some time the VM just stops (no ping, no console, no activity). Using gdb and KVMs gdbserver capability I was able to track it down to the following symptom: One thread would be stuck in flush_tlb_others_ipi() waiting for all other CPUs using a specifiy mm to signal they have flushed there TLB, while all other CPU-threads would be waiting for the pgd_lock to be freed. I have no easy test to reproduce the bug, but it usually happens to me when I run several pbuilder-builds in parallel. The more virtual CPUs the VM has, the easier to trigger: With 2 VCPUs it's hours, with 6 VCPUs it's usually less than 5 minutes. This got more prominent with git-commit 831d52bc153971b70e64eccfbed2b232394f22f8: x86, mm: avoid possible bogus tlb entries by clearing prev mm_cpumask after switching mm (Linus tree), and even worse with 4981d01eada5354d81c8929d5b2836829ba3df7b: x86: Flush TLB if PGD entry is changed in i386 PAE mode I found the issue to be fixed by a79e53d85683c6dd9f99c90511028adc2043031f: x86/mm: Fix pgd_lock deadlock That patch is already in the Debian patch set, but only applied for the xen flavour: features/all/xen/x86-mm-Fix-pgd_lock-deadlock.patch I thinks this patch should be applied to all flavours. It doesn't apply to the non-xen-flavour as is, because it depends on some other xen-related patch. The Patch was also back-ported to the OpenSUSE Kernel http://kernel.opensuse.org/cgit/kernel-source/commit/?id=ac27c01aa880c65d17043ab87249c613ac4c3635, but since the patch is trivial to backport, I'll attach my version as well. The patch should be forwarded to Upstream to be included into the upstream 2.6.32 longterm stable kernel as well. The full issue is tracked in our (German) Bugzilla: https://forge.univention.org/bugzilla/show_bug.cgi?id=26661 Sincerely Philipp -- System Information: Debian Release: 5.0.1 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.32-ucs57-686-bigmem Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Bug #26661: 686-bigmem VM deadlock --- /dev/null +++ linux-2.6.32-2.6.32/debian/patches/bugfix/x86/x86-mm-Fix-pgd_lock-deadlock.patch @@ -0,0 +1,217 @@ +It's forbidden to take the page_table_lock with the irq disabled +or if there's contention the IPIs (for tlb flushes) sent with +the page_table_lock held will never run leading to a deadlock. + +Nobody takes the pgd_lock from irq context so the _irqsave can be +removed. + +Signed-off-by: Andrea Arcangeli aarca...@redhat.com +Acked-by: Rik van Riel r...@redhat.com +Tested-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com +Signed-off-by: Andrew Morton a...@linux-foundation.org +Cc: Peter Zijlstra pet...@infradead.org +Cc: Linus Torvalds torva...@linux-foundation.org +Cc: sta...@kernel.org +LKML-Reference: 201102162345.p1gnjmjm021...@imap1.linux-foundation.org +Signed-off-by: Ingo Molnar mi...@elte.hu +Git-commit: a79e53d85683c6dd9f99c90511028adc2043031f +--- a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c +@@ -223,15 +223,14 @@ void vmalloc_sync_all(void) +address = TASK_SIZE address FIXADDR_TOP; +address += PMD_SIZE) { + +- unsigned long flags; + struct page *page; + +- spin_lock_irqsave(pgd_lock, flags); ++ spin_lock(pgd_lock); + list_for_each_entry(page, pgd_list, lru) { + if (!vmalloc_sync_one(page_address(page), address)) + break; + } +- spin_unlock_irqrestore(pgd_lock, flags); ++ spin_unlock(pgd_lock); + } + } + +@@ -331,13 +330,12 @@ void vmalloc_sync_all(void) +address += PGDIR_SIZE) { + + const pgd_t *pgd_ref = pgd_offset_k(address); +- unsigned long flags; + struct page *page; + + if
Processed: Re: xen: oops at atomic64_read_cx8+0x4
Processing commands for cont...@bugs.debian.org: notfound 676360 linux-2.6/3.2.18-1 Bug #676360 [src:linux-2.6] xen: oops at atomic64_read_cx8+0x4 Bug #676866 [src:linux-2.6] linux-image-3.2.0-2-686-pae: won't boot under xen No longer marked as found in versions linux-2.6/3.2.18-1. No longer marked as found in versions linux-2.6/3.2.18-1. found 676360 linux-2.6/3.4.1-1~experimental.1 Bug #676360 [src:linux-2.6] xen: oops at atomic64_read_cx8+0x4 Bug #676866 [src:linux-2.6] linux-image-3.2.0-2-686-pae: won't boot under xen Marked as found in versions linux-2.6/3.4.1-1~experimental.1. Marked as found in versions linux-2.6/3.4.1-1~experimental.1. End of message, stopping processing here. Please contact me if you need assistance. -- 676360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676360 676866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676866 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.13393519446183.transcr...@bugs.debian.org
Bug#676952: linux-image-3.2.0-2-amd64: Unable to use Cine S2 DVB card, ddbridge driver missing
Package: linux-2.6 Version: 3.2.17-1 Severity: important Dear Maintainer, please enable the DVB_DDBRIDGE driver, which is required for the commonly used Cine S2 DVB cards. These worked before with 2.6.38. BR, Tobias -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.19-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 ** USB devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (1002, 'unstable'), (1001, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (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/bash Versions of packages linux-image-3.2.0-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.43 ii initramfs-tools [linux-initramfs-tool] 0.102 ii kmod6-2 ii linux-base 3.5 ii module-init-tools 6-2 Versions of packages linux-image-3.2.0-2-amd64 recommends: ii firmware-linux-free 3 Versions of packages linux-image-3.2.0-2-amd64 suggests: pn grub-pc1.99-21 pn linux-doc-3.2 none Versions of packages linux-image-3.2.0-2-amd64 is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimax none pn firmware-ipw2x00none pn firmware-ivtv none pn firmware-iwlwifi0.35 pn firmware-libertas none pn firmware-linux 0.35 pn firmware-linux-nonfree 0.35 pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information excluded -- 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/20120610182335.17556.25983.report...@tobi-notebook.e-tobi.loc
Bug#660111: Bug#664653 pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default
fixed 664653 2.0-3 thanks As I reported earlier, version 2.0 of pulseaudio can handle multiple HDMI outputs. Bug# 664653 is completely fixed. I've tested it successfully in my computer. -- 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/CAH=dyregutd5xo4uxcm22t1cp1scik_4ik6r-ax5ubzpxrp...@mail.gmail.com
Bug#676971: 3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors
Package: linux-2.6 Version: 3.2.0-0 Severity: important When booting with the xen/hypervisor kernel the system hangs with i/o errors thrown in console. The standard kernel is working fine and the disk has been tested and swapped. Errors include: ata1.00: failed command: READ DMA task xend:1404 blocked for more than 120 seconds Buffer I/O error on device sda1 end_request: I/O error, dev sda I am using Debian Squeeze, kernel 3.2.0-0.bpo.2-686-pae. The same error seems to exists in xen-linux-system-2.6.32-45, as far as I tested. -- 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/CALZ=sy-g7jmywt2+jr5eako1ba_bqxut6sozdh9of6fl_0u...@mail.gmail.com
Bug#676971:
A dmesg for the machine can be found at http://pastebin.com/VdJd5KSh -- 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/CALZ=sy8o9wr-_ymqs+c38aseqi74znfn6tgd7qdpx_vbcy-...@mail.gmail.com
Bug#666686: marked as done (initramfs-tools: thinkpad_acpi does not load automatically if not in initramfs)
Your message dated Sun, 10 Jun 2012 21:34:09 + with message-id 20120610213409.gi8...@vostochny.stro.at and subject line Re: initramfs-tools: thinkpad_acpi does not load automatically if not in initramfs has caused the Debian Bug report #86, regarding initramfs-tools: thinkpad_acpi does not load automatically if not in initramfs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 86: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.101 Severity: normal Dear Maintainer, Recently the thinkpad_acpi module ceased to load automatically during boot. After further testing, it appears that the module will load automatically only if it is included in the initramfs (by listing it and dependent modules in /etc/initramfs-tools/modules). It was suggested[1] that this indicates a bug in initramfs-tools with the handoff from initramfs to the main system. I purged the initramfs-tools package and installed version 0.98.8 from stable, but the same symptoms remained. Note that it is a bit intermittent, but fails to load thinkpad_acpi ~90% of the time, so there may be a race condition present. Please let me know if there is anything I can do to troubleshoot this further. Thanks, Kevin 1. http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2012-March/050618.html -- Package-specific info: -- initramfs sizes -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.3.0-kevinoid1 root=/dev/mapper/crypt0 ro quiet -- resume RESUME=UUID=3f0b2029-83fd-4d5c-b352-a64593e385fa -- /proc/filesystems ext3 ext4 fuseblk -- lsmod Module Size Used by vboxpci12349 0 vboxnetadp 5684 0 vboxnetflt 13671 0 vboxdrv 212020 3 vboxnetflt,vboxnetadp,vboxpci binfmt_misc 5107 1 kvm_intel 109239 0 kvm 196503 1 kvm_intel xt_owner 798 4 xt_mac 720 1 xt_limit1130 1 ipt_REJECT 1602 3 nf_conntrack_ipv4 8605 6 nf_defrag_ipv4 1021 1 nf_conntrack_ipv4 xt_state 870 6 xt_tcpudp 1698 27 iptable_filter 994 1 ip_tables 8250 1 iptable_filter x_tables 13135 8 ip_tables,iptable_filter,xt_tcpudp,xt_state,ipt_REJECT,xt_limit,xt_mac,xt_owner nf_conntrack_netbios_ns 837 0 nf_conntrack_broadcast 997 1 nf_conntrack_netbios_ns nf_conntrack 48840 4 nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv4 ipv6 197699 26 fuse 52115 1 loop 11967 0 hdaps 7439 1 tp_smapi 16597 0 thinkpad_ec 4937 2 tp_smapi,hdaps coretemp4481 0 cpuid 1698 0 msr 1983 0 acpi_cpufreq4803 1 mperf 1015 1 acpi_cpufreq usbhid 20347 0 snd_hda_codec_analog62483 1 snd_hda_intel 18856 2 snd_hda_codec 68416 2 snd_hda_intel,snd_hda_codec_analog snd_pcm_oss25590 0 sr_mod 10185 0 snd_mixer_oss 10148 2 snd_pcm_oss cdrom 28183 1 sr_mod joydev 6904 0 snd_pcm53351 3 snd_pcm_oss,snd_hda_codec,snd_hda_intel radeon600846 2 snd_page_alloc 6114 2 snd_pcm,snd_hda_intel arc41025 2 ata_piix 18695 0 snd_timer 14529 1 snd_pcm pcmcia 28160 0 i2c_algo_bit4066 1 radeon iwl394539702 0 drm_kms_helper 24462 1 radeon iwlegacy 48536 1 iwl3945 nsc_ircc 14769 0 mac80211 163718 2 iwlegacy,iwl3945 ttm47505 1 radeon uhci_hcd 16516 0 ehci_hcd 29840 0 irda 139047 1 nsc_ircc drm 162684 4 ttm,drm_kms_helper,radeon yenta_socket 16548 0 cfg80211 128609 3 mac80211,iwlegacy,iwl3945 e1000e111398 0 snd45510 9 snd_timer,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_hda_codec,snd_hda_intel,snd_hda_codec_analog usbcore 115627 3 ehci_hcd,uhci_hcd,usbhid pcmcia_rsrc 6848 1 yenta_socket tpm_tis 7216 0 rfkill 12824 1 cfg80211 crc_ccitt 1291 1 irda
Bug#676971: 2.6.32-45: xen i/o errors
found 676971 linux-2.6/2.6.32-45 quit Kacper wrote: A dmesg for the machine can be found at http://pastebin.com/VdJd5KSh Attaching. root@nehalem:~# dmesg [0.00] Reserving virtual address space above 0xf580 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-0.bpo.2-686-pae (Debian 3.2.18-1~bpo60+1) (debian-kernel@lists.debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Sun Jun 3 22:21:19 UTC 2012 [0.00] Freeing a0-100 pfn range: 96 pages freed [0.00] 1-1 mapping on a0-100 [0.00] 1-1 mapping on f7fd0-10 [0.00] Released 96 pages of unused memory [0.00] Set 32912 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - f7fd (usable) [0.00] Xen: f7fd - f7fdfc00 (ACPI data) [0.00] Xen: f7fdfc00 - f7fff000 (reserved) [0.00] Xen: fec0 - fec9 (reserved) [0.00] Xen: fee0 - fee1 (reserved) [0.00] Xen: ffb0 - 0001 (reserved) [0.00] Xen: 0001 - 00010800 (usable) [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] DMI 2.3 present. [0.00] DMI: Dell Computer Corporation PowerEdge 2600 /06R260, BIOS A14 02/21/2005 [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] last_pfn = 0x108000 max_arch_pfn = 0x100 [0.00] found SMP MP-table at [c00fe710] fe710 [0.00] initial memory mapped : 0 - 03bff000 [0.00] Base memory trampoline at [c009c000] 9c000 size 16384 [0.00] init_memory_mapping: -2d1fe000 [0.00] 00 - 002d1fe000 page 4k [0.00] kernel direct mapping tables up to 2d1fe000 @ 3a92000-3bff000 [0.00] xen: setting RW the range 3bdf000 - 3bff000 [0.00] RAMDISK: 0179d000 - 02f88000 [0.00] ACPI: RSDP 000fdc20 00014 (v00 DELL ) [0.00] ACPI: RSDT 000fdc34 00030 (v01 DELL PE2600 0001 MSFT 010A) [0.00] ACPI: FACP 000fdc64 00074 (v01 DELL PE2600 0001 MSFT 010A) [0.00] ACPI: DSDT f7fd 01FD0 (v01 DELL PE2600 0001 MSFT 010A) [0.00] ACPI: FACS f7fdfc00 00040 [0.00] ACPI: APIC 000fdcd8 000BE (v01 DELL PE2600 0001 MSFT 010A) [0.00] ACPI: SPCR 000fdd96 00050 (v01 DELL PE2600 0001 MSFT 010A) [0.00] ACPI: Local APIC address 0xfee0 [0.00] 3502MB HIGHMEM available. [0.00] 721MB LOWMEM available. [0.00] mapped low ram: 0 - 2d1fe000 [0.00] low ram: 0 - 2d1fe000 [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] Normal 0x1000 - 0x0002d1fe [0.00] HighMem 0x0002d1fe - 0x00108000 [0.00] Movable zone start PFN for each node [0.00] early_node_map[3] active PFN ranges [0.00] 0: 0x0010 - 0x00a0 [0.00] 0: 0x0100 - 0x000f7fd0 [0.00] 0: 0x0010 - 0x00108000 [0.00] On node 0 totalpages: 1048416 [0.00] free_area_init_node: node 0, pgdat c1424000, node_mem_map eb0fd200 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 3952 pages, LIFO batch:0 [0.00] Normal zone: 1412 pages used for memmap [0.00] Normal zone: 179322 pages, LIFO batch:31 [0.00] HighMem zone: 7005 pages used for memmap [0.00] HighMem zone: 856693 pages, LIFO batch:31 [0.00] Using APIC driver default [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] BIOS bug: APIC version is 0 for CPU 0/0x0, fixing up to 0x10 [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled) [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [0.00] ACPI: IOAPIC (id[0x08] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 8, version 255, address 0xfec0, GSI 0-255 [0.00] ACPI: IOAPIC (id[0x09] address[0xfec8] gsi_base[24]) [0.00] IOAPIC[1]: apic_id 9, version 255,
Processed: Re: 2.6.32-45: xen i/o errors
Processing commands for cont...@bugs.debian.org: found 676971 linux-2.6/2.6.32-45 Bug #676971 [linux-2.6] 3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors Marked as found in versions linux-2.6/2.6.32-45. quit Stopping processing here. Please contact me if you need assistance. -- 676971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676971 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.133936815822818.transcr...@bugs.debian.org
Bug#664767: Brcmsmac driver woes, possible regression?
found 664767 linux-2.6/3.2.19-1 quit Camaleón wrote: Yes. What I get is the Network Manager window requesting for the password confirm, randomly. If I delay the password confirmation, the wireless connection drops. [...] I downloaded sid kernel sources for 3.2.19, applied the first of the patches (0001-brcm80211-smac-drop-40MHz-intolerant-flag-from-HT-ca.patch and build a new deb kernel package. [...] This kernel was running fine the whole Saturday but today I had another reconnect (network-manager asked for the password which I had to reconfirm). I'm attaching the full syslog for this pacthed kernel. The reconnect happened at night (22:00 or so). Thanks. You first reported this against 3.2.9-1. Were you using some earlier 3.2.y kernel without trouble before? 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/20120610224902.GB3419@burratino
Processed: Re: Brcmsmac driver woes, possible regression?
Processing commands for cont...@bugs.debian.org: found 664767 linux-2.6/3.2.19-1 Bug #664767 [linux-2.6] Brcmsmac driver woes, possible regression? Marked as found in versions linux-2.6/3.2.19-1. 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.133936855324388.transcr...@bugs.debian.org
Processed: Re: 3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors
Processing commands for cont...@bugs.debian.org: notfound 676971 3.2.0-0 Bug #676971 [linux-2.6] 3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors There is no source info for the package 'linux-2.6' at version '3.2.0-0' with architecture '' Unable to make a source version for version '3.2.0-0' No longer marked as found in versions 3.2.0-0. found 676971 linux-2.6/3.2.18-1 Bug #676971 [linux-2.6] 3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors Marked as found in versions linux-2.6/3.2.18-1. End of message, stopping processing here. Please contact me if you need assistance. -- 676971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676971 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.133936952928831.transcr...@bugs.debian.org
Bug#676971: xen i/o errors
tags 676971 + moreinfo quit Hi Kacper, Kacper wrote: When booting with the xen/hypervisor kernel the system hangs with i/o errors thrown in console. The standard kernel is working fine and the disk has been tested and swapped. Errors include: ata1.00: failed command: READ DMA task xend:1404 blocked for more than 120 seconds Please contact xen-us...@lists.xen.org to track down the cause of this. 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/20120610230907.GD3419@burratino
Processed: Re: xen i/o errors
Processing commands for cont...@bugs.debian.org: tags 676971 + moreinfo Bug #676971 [linux-2.6] 3.2.0-0.bpo.2-686-pae/2.6.32-45: xen i/o errors Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 676971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676971 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.133936975829676.transcr...@bugs.debian.org
Bug#623177: linux-2.6: Please enable CONFIG_CRASH_DUMP on x86 architectures
On Sun, Jun 10, 2012 at 03:02:30PM +0100, Ben Hutchings wrote: On Sun, 2012-06-10 at 00:44 -0700, John Wright wrote: On Sat, Jun 02, 2012 at 07:02:11PM +0100, Ben Hutchings wrote: The help text for this option is: Generate crash dump after being started by kexec. This should be normally only set in special crash dump kernels which are loaded in the main kernel with kexec-tools into a specially reserved region and then later executed after a crash by kdump/kexec. ... Are you asking us to add a kdump flavour, as some other distributions do? It's not necessary to have another flavor. Kernels built with this option work just fine as regular kernels too (in fact, the ia64 and probably some other kernels are already built this way). As I recall, as the kernel is currently built, it can be loaded as a crash kernel, and kexec'ed successfully upon kernel panic; however, CONFIG_CRASH_DUMP is required to enable /proc/vmcore in the newly booted kernel, which contains the memory of the crashed kernel. Then, a tool like 'makedumpfile' can read the core, stripping out user and zero pages, and write a small dump file that can be analyzed with tools like 'crash'. The help text for CRASH_DUMP on x86 says: Generate crash dump after being started by kexec. This should be normally only set in special crash dump kernels ... Since this is not the only use for kexec, I don't believe we should The documentation is misleading. It doesn't cause the kernel to generate any dump; it just enables /proc/vmcore *if* the kernel is kexec'ed as a result of the previous kernel panicking. Nothing special (compared to other kernels) happens in a normal (not-triggered-by-panic) kexec of a CONFIG_CRASH_DUMP=y kernel. enable this in the currently defined flavours (or that it should have been enabled for ia64). As I said, other distributions have a separate kdump flavour, presumably for this reason. (Adding Troy, who might have more insight on the historic need for a kdump kernel.) The separate kdump flavors started mainly because some architectures weren't relocatable, so it was impossible to use the same image for your normal kernel and your crash kernel. That hasn't been the case for x86, ia64, or ppc for quite some time. Also, the i386_defconfig and x86_64_defconfig files upstream have had CONFIG_CRASH_DUMP=y since 2008: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=5cb04df8d3f03e37a19f2502591a84156be71772 The upstream kdump documentation talks about using the same kernel for kdump as well: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=Documentation/kdump/kdump.txt#l112 I think adding another flavor just for CONFIG_CRASH_DUMP is really heavy-weight, especially given that upstream has enabled it by default for four years, and it touches so few pieces of code. -- John Wright j...@debian.org -- 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/20120610234006.ga20...@mail.aitunes.com
Bug#623177: linux-2.6: Please enable CONFIG_CRASH_DUMP on x86 architectures
Thanks a lot for the extra information. I'm convinced and I'll enable this for the next upload. Ben. -- Ben Hutchings Computers are not intelligent. They only think they are. signature.asc Description: This is a digitally signed message part
Processed: tagging 623177
Processing commands for cont...@bugs.debian.org: tags 623177 + pending Bug #623177 [src:linux-2.6] linux-2.6: Please enable CONFIG_CRASH_DUMP on x86 architectures Bug #629627 [src:linux-2.6] linux-2.6: please support kdump (enable CONFIG_CRASH_DUMP=y?) Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 623177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623177 629627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629627 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.13393724699142.transcr...@bugs.debian.org
Bug#660111: Bug#664653 pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default
On Sun, 2012-06-10 at 15:37 -0400, Andres Cimmarusti wrote: fixed 664653 2.0-3 thanks As I reported earlier, version 2.0 of pulseaudio can handle multiple HDMI outputs. Bug# 664653 is completely fixed. I've tested it successfully in my computer. Do we still need to make kernel changes for wheezy, or does the new PA together with the current kernel package (version 3.2.19-1) avoid this problem? Ben. -- Ben Hutchings Computers are not intelligent. They only think they are. signature.asc Description: This is a digitally signed message part
Processed: tagging 676952
Processing commands for cont...@bugs.debian.org: tags 676952 + pending Bug #676952 [linux-2.6] linux-image-3.2.0-2-amd64: Unable to use Cine S2 DVB card, ddbridge driver missing Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 676952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676952 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.133937314613264.transcr...@bugs.debian.org
Bug#660111: Bug#664653 pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default
Do we still need to make kernel changes for wheezy, or does the new PA together with the current kernel package (version 3.2.19-1) avoid this problem? PA 2.0 can handle all the HDMI outputs advertised by the kernel, but one has to try all of them using pavucontrol to find the correct one. With kernel's 3.3 jack detection, this is done automatically. Personally I think PA 2.0 is sufficient, since the user can select the right HDMI output, but automatic detection is definitely better for ease of use. Since the Ubuntu team has already done the backport, perhaps this won't be too hard? -- 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/CAH=dyrerdc4fz6dg1kbbdb3f9ax8rrakzhafsoo0hqfjqbt...@mail.gmail.com
Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)
Ben Hutchings wrote: Do we still need to make kernel changes for wheezy, or does the new PA together with the current kernel package (version 3.2.19-1) avoid this problem? I think Andres mentioned some patches that expose detected jack status using kcontrols. Andres, do you know of relevant commit ids? Can you describe the difference in behavior between 3.2.19-1 and 3.4.1-1~experimental.1 and whether it's worth backporting these changes? Thanks, 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/20120611001956.GB3390@burratino
Bug#623177: linux-2.6: Please enable CONFIG_CRASH_DUMP on x86 architectures
On Mon, Jun 11, 2012 at 12:55:19AM +0100, Ben Hutchings wrote: Thanks a lot for the extra information. I'm convinced and I'll enable this for the next upload. Wonderful, thank you! (And sorry I didn't include that information from the beginning.) -- John Wright j...@debian.org signature.asc Description: Digital signature
Bug#660111: pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default
Andres Cimmarusti wrote: PA 2.0 can handle all the HDMI outputs advertised by the kernel, but one has to try all of them using pavucontrol to find the correct one. With kernel's 3.3 jack detection, this is done automatically. Presumably this means 01a61e12b460 ALSA: hda - Create jack-detection kcontrols plus prerequisites. -- 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/20120611002126.GC3390@burratino
Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)
Andres, do you know of relevant commit ids? Can you describe the difference in behavior between 3.2.19-1 and 3.4.1-1~experimental.1 and whether it's worth backporting these changes? I will try the kernel from experimental and let you know if the changes are worth while. Unfortunately I have not tracked the relevant commits. But it looks like you probably found them. We can probably contact David Henningsson from Canonical, since he was heavily involved in it and provided a lot of guidance to solve this issue. -- 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/CAH=dyrhh+_w8o6ssftxcy6_jjbbl+6b6bnhhqbjwjx557_v...@mail.gmail.com
Bug#514691: marked as done (problem with the module r8169)
Your message dated Mon, 11 Jun 2012 01:29:58 +0100 with message-id 1339374598.21665.216.ca...@deadeye.wl.decadent.org.uk and subject line Re: problem with the module r8169 has caused the Debian Bug report #514691, regarding problem with the module r8169 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 514691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: r8169 Severity: normal The module r8169 which is reponsible of my network eth0 card, is out of order after 1 or 2 days of running machine uptime. So the trick I used to avoid this bug was in my /etc/crontab: 05 09 * * * root/etc/init.d/networking stop ; rmmod r8169 ; sleep 3s ; modprobe -i r8169 ; sleep 2s ; ifconfig eth0 10.1.1.2 ; sleep 2s ; /etc/init.d/networking start ; ifconfig eth0 10.1.1.2 but I dont like this way, and the r8169 may be more stable. Best regards to the wonderful DEBIAN TEAM!! Yellow -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.25-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Closing due to lack of response. Ben. -- Ben Hutchings Computers are not intelligent. They only think they are. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#648939: [Ben Addis: Re: USB mouse stops work on battery power (Re: Possible solution)]
Forwarding with permission. ---BeginMessage--- On Sun, 10 Jun 2012 11:08:34 -0500 Jonathan Nieder jrnie...@gmail.com wrote: Hi Ben, Ben Addis wrote: [Subject: Bug#648939: Possible solution] Please keep in mind that these appear as emails in a crowded inbox, so the subject line can be a good place to put valuable context. Sorry about that; I'll remember for next time. I seem to have the same problem with my laptop (asus ul30a-a2 running debian testing, xfce 4.8, kernel 3.2.0-2-amd64; my mouse is an Evoluent VerticalMouse 3) Do you mean that the mouse works when the laptop is connected to power but stops about 20 seconds after power is disconnected, that reconnecting power gets the mouse working again, and that this is a regression introcued at some point between 2.6.32 and 3.0? I tested it again a few times without the blacklist on the usb mouse's autosuspend. When I unplug the power, the mouse does work, but for varying amounts of time. One time worked ok for 2 minutes until I used the keyboard (and then it died in about 15 secs), another time it didn't work after only a second or two, and the third it lasted for maybe 3 minutes even while using the keyboard. So it seems unconnected to the keyboard use, and to the length of time since unplugging (except that it was always under 5 minutes or so). In every case, it worked immediately on plugging the laptop back in. Also unplugging the usb mouse and plugging it back in fixed it (while on battery), but only temporarily, as it would die again in the same way as when unplugging the computer. Unfortunately, I don't know about when the bug was introduced, as I only switched to pure Debian (from LMDE) about 2 weeks ago. I only just noticed this bug yesterday, but I almost never use my usb mouse when unplugged. I'm not 100% sure I haven't done so in the last 2 weeks, but it's probable. I definitely didn't have this problem in LMDE, though, and I was on at least kernel 3.0. The solution found here (https://bbs.archlinux.org/viewtopic.php?id=123553) is working for me so far. Essentially you edit /etc/laptop-mode/conf.d/usb-autosuspend.conf and add the usb id of your mouse to the blacklist. Please attach output from reportbug --template linux-image-$(uname -r) so we can work on diagnosing and fixing (or at least automatically working around) the underlying problem. I've never used reportbug, so hopefully I've got it right. Hope that helps, Jonathan Thanks for taking the time to go through this. Ben Include network configuration and status from this computer? Include network configuration and status from this computer? Include network configuration and status from this computer? Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Ben Addis ben@mint To: Debian Bug Tracking System sub...@bugs.debian.org Subject: linux-image-3.2.0-2-amd64: none Package: linux-2.6 Version: 3.2.18-1 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * 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? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.18-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon May 21 17:45:41 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=ee00de39-ebec-4eef-a2da-a0b06a4291b2 ro acpi_backlight=vendor i915.powersave=0 vga=792 quiet splash quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [156283.655393] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro,user_xattr,barrier=1,data=ordered,commit=0 [156283.860322] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,user_xattr,acl,barrier=1,data=ordered,commit=0 [156545.489824] uhci_hcd :00:1a.0: PCI INT A disabled [156545.492844] uhci_hcd :00:1a.1: PCI INT B disabled [156545.495666] uhci_hcd :00:1a.2: PCI INT D disabled [156545.501272] uhci_hcd :00:1d.1: PCI INT B disabled [156545.504223] uhci_hcd :00:1d.2: PCI INT C disabled [156545.520056] ehci_hcd :00:1d.7: PCI INT A disabled [156545.520115] ehci_hcd :00:1d.7: PME# enabled [156545.670856] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro,user_xattr,barrier=1,data=ordered,commit=600 [156545.935371] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,user_xattr,acl,barrier=1,data=ordered,commit=600 [156547.840085] ehci_hcd :00:1a.7: PCI INT C disabled [156547.840161] ehci_hcd :00:1a.7: PME# enabled [156558.574920] NMI watchdog enabled, takes one hw-pmu counter. [156558.575961] NMI watchdog enabled, takes one hw-pmu counter. [156558.684092] ehci_hcd :00:1a.7: BAR 0: set to [mem 0xfe9fbc00-0xfe9fbfff] (PCI address
Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)
On Sun, Jun 10, 2012 at 8:25 PM, Andres Cimmarusti acimmaru...@gmail.com wrote: Andres, do you know of relevant commit ids? Can you describe the difference in behavior between 3.2.19-1 and 3.4.1-1~experimental.1 and whether it's worth backporting these changes? I will try the kernel from experimental and let you know if the changes are worth while. Unfortunately I have not tracked the relevant commits. But it looks like you probably found them. We can probably contact David Henningsson from Canonical, since he was heavily involved in it and provided a lot of guidance to solve this issue. I just tried kernel 3.4.1-1~experimental.1. I could see NO benefit at all in using that kernel. I still had to choose from a long list of advertised HDMI interfaces in pavucontrol before finding the correct one that produced sound on the TV speakers. On my laptop at least, I saw NO automatic jack detection benefit whatsoever. Is there anything else that needs to change? Perhaps David Henningsson can comment? Thanks Andres -- 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/CAH=dYrE_6QKppwuBoKdD6VRtsBjGyfbE0NTDE=g+58f+qnz...@mail.gmail.com
Processed: tagging 674565
Processing commands for cont...@bugs.debian.org: tags 674565 + pending Bug #674565 [linux-2.6] linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 674565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674565 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.133937583026051.transcr...@bugs.debian.org
Processed: tagging 676545
Processing commands for cont...@bugs.debian.org: tags 676545 + pending Bug #676545 [linux-2.6] linux-image-3.2.0-0.bpo.2-686-pae: ASIX usb net driver broken with 8021Q frames Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 676545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676545 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.133937583426189.transcr...@bugs.debian.org
Bug#664767: Brcmsmac driver woes, possible regression?
forwarded 664767 http://thread.gmane.org/gmane.linux.kernel.wireless.general/92452 quit Camaleón wrote: I downloaded sid kernel sources for 3.2.19, applied the first of the patches (0001-brcm80211-smac-drop-40MHz-intolerant-flag-from-HT-ca.patch and build a new deb kernel package. [...] This kernel was running fine the whole Saturday but today I had another reconnect (network-manager asked for the password which I had to reconfirm). I'm attaching the full syslog for this pacthed kernel. The reconnect happened at night (22:00 or so). Nicely done. Let's take this upstream again. Thanks for your patience, 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/20120611031926.GC3092@burratino
Processed: Re: Brcmsmac driver woes, possible regression?
Processing commands for cont...@bugs.debian.org: forwarded 664767 http://thread.gmane.org/gmane.linux.kernel.wireless.general/92452 Bug #664767 [linux-2.6] Brcmsmac driver woes, possible regression? Changed Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel.wireless.general/92452' from 'http://thread.gmane.org/gmane.linux.kernel.wireless.general/87873' 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.133938480132634.transcr...@bugs.debian.org
Re: Bug#676921: ITP: amd64-microcode -- Processor microcode firmware for AMD CPUs
On 06/10/2012 04:31 PM, Henrique de Moraes Holschuh wrote: The microcode data file for Linux contains the latest microcode definitions for all AMD AMD64 processors. i'm aware that there's the intel-microcode package, however, why not integrate this into firmware-nonfree (as firmware-amd-microcode or something) and keep all this stuff at one place? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/4fd56d75.8060...@progress-technologies.net
Processed (with 1 errors): unblock 661151 with 661153
Processing commands for cont...@bugs.debian.org: unblock 661151 with 661153 Bug #661151 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] linux-2.6: lacks AppArmor kernel/userspace interface 661151 was not blocked by any bugs. 661151 was blocking: 653592 661153 661154 Removed blocking bug(s) of 661151: 661153 Failed to set blocking bugs of 661151: can't find location for 661153. 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.133938913919498.transcr...@bugs.debian.org
Processed: tagging 636010
Processing commands for cont...@bugs.debian.org: tags 636010 + pending Bug #636010 [linux-2.6] [linux-2.6] Please rename source to linux Ignoring request to alter tags of bug #636010 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 636010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636010 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.133939123229095.transcr...@bugs.debian.org
Processed: tagging 644198
Processing commands for cont...@bugs.debian.org: tags 644198 + pending Bug #644198 [src:linux-2.6] linux-2.6: Tell reportbug to use src:linux-2.6 Ignoring request to alter tags of bug #644198 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 644198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644198 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.133939123529110.transcr...@bugs.debian.org
Processed: tagging 383481
Processing commands for cont...@bugs.debian.org: tags 383481 + pending Bug #383481 [linux-2.6] Switch to nouveaufb Ignoring request to alter tags of bug #383481 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 383481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383481 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.133939124829132.transcr...@bugs.debian.org
Processed: tagging 613972
Processing commands for cont...@bugs.debian.org: tags 613972 + pending Bug #613972 [src:linux-2.6] kernel-wedge: UDF filesystem support Ignoring request to alter tags of bug #613972 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 613972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613972 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.133939124929146.transcr...@bugs.debian.org
Processed: tagging 629410
Processing commands for cont...@bugs.debian.org: tags 629410 + pending Bug #629410 [linux-2.6] please Recommend libc6-loongson2f Ignoring request to alter tags of bug #629410 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 629410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629410 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.133939124929157.transcr...@bugs.debian.org
Processed: tagging 674565
Processing commands for cont...@bugs.debian.org: tags 674565 + pending Bug #674565 [linux-2.6] linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module) Ignoring request to alter tags of bug #674565 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 674565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674565 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.1339392120787.transcr...@bugs.debian.org
Processed: tagging 676545
Processing commands for cont...@bugs.debian.org: tags 676545 + pending Bug #676545 [linux-2.6] linux-image-3.2.0-0.bpo.2-686-pae: ASIX usb net driver broken with 8021Q frames Ignoring request to alter tags of bug #676545 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 676545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676545 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.1339392124857.transcr...@bugs.debian.org
Processed: tagging 383481
Processing commands for cont...@bugs.debian.org: tags 383481 + pending Bug #383481 [linux-2.6] Switch to nouveaufb Ignoring request to alter tags of bug #383481 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 383481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383481 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.1339392127883.transcr...@bugs.debian.org
Processed: tagging 669028
Processing commands for cont...@bugs.debian.org: tags 669028 + pending Bug #669028 [src:linux-2.6] please backport new procfs hidepid option into 3.2 Ignoring request to alter tags of bug #669028 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 669028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669028 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.1339392135947.transcr...@bugs.debian.org
Processed: tagging 609615
Processing commands for cont...@bugs.debian.org: tags 609615 + pending Bug #609615 [linux-2.6] linux-2.6: please do not build in nvidiafb on powerpc systems Ignoring request to alter tags of bug #609615 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 609615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609615 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.1339392131918.transcr...@bugs.debian.org
Processed: tagging 657078
Processing commands for cont...@bugs.debian.org: tags 657078 + pending Bug #657078 [linux-2.6] nfs: page allocation failure in nfs_idmap_new Bug #636306 [linux-2.6] mount.nfs: page allocation failure. order:4, mode:0xc0d0 Bug #646889 [linux-2.6] linux-image-2.6.32-5-686: Since I'm using nfsd instead of samba a kerneloops occurs when accessing the files on server Ignoring request to alter tags of bug #657078 to the same tags previously set Ignoring request to alter tags of bug #636306 to the same tags previously set Ignoring request to alter tags of bug #646889 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 636306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636306 646889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646889 657078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657078 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.1339392138969.transcr...@bugs.debian.org
Processed: tagging 623177
Processing commands for cont...@bugs.debian.org: tags 623177 + pending Bug #623177 [src:linux-2.6] linux-2.6: Please enable CONFIG_CRASH_DUMP on x86 architectures Bug #629627 [src:linux-2.6] linux-2.6: please support kdump (enable CONFIG_CRASH_DUMP=y?) Ignoring request to alter tags of bug #623177 to the same tags previously set Ignoring request to alter tags of bug #629627 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 623177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623177 629627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629627 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.13393921451010.transcr...@bugs.debian.org
Processed: tagging 676952
Processing commands for cont...@bugs.debian.org: tags 676952 + pending Bug #676952 [linux-2.6] linux-image-3.2.0-2-amd64: Unable to use Cine S2 DVB card, ddbridge driver missing Ignoring request to alter tags of bug #676952 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 676952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676952 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.13393921491032.transcr...@bugs.debian.org
Processed: tagging 676360
Processing commands for cont...@bugs.debian.org: tags 676360 + pending Bug #676360 [src:linux-2.6] xen: oops at atomic64_read_cx8+0x4 Bug #676866 [src:linux-2.6] linux-image-3.2.0-2-686-pae: won't boot under xen Ignoring request to alter tags of bug #676360 to the same tags previously set Ignoring request to alter tags of bug #676866 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 676360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676360 676866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676866 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.1339392142990.transcr...@bugs.debian.org
Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)
On 06/11/2012 02:40 AM, Andres Cimmarusti wrote: On Sun, Jun 10, 2012 at 8:25 PM, Andres Cimmarusti acimmaru...@gmail.com wrote: Andres, do you know of relevant commit ids? Can you describe the difference in behavior between 3.2.19-1 and 3.4.1-1~experimental.1 and whether it's worth backporting these changes? I will try the kernel from experimental and let you know if the changes are worth while. Unfortunately I have not tracked the relevant commits. But it looks like you probably found them. We can probably contact David Henningsson from Canonical, since he was heavily involved in it and provided a lot of guidance to solve this issue. I just tried kernel 3.4.1-1~experimental.1. I could see NO benefit at all in using that kernel. I still had to choose from a long list of advertised HDMI interfaces in pavucontrol before finding the correct one that produced sound on the TV speakers. On my laptop at least, I saw NO automatic jack detection benefit whatsoever. Is there anything else that needs to change? Perhaps David Henningsson can comment? You're correct; even if the information is there, it isn't advertised in pavucontrol. I should probably implement that... (If you're using Ubuntu 12.04, you will have a new sound settings UI that hides unavailable devices. For upstreaming of this UI please see the gnome-cc list.) What you'll get is instead what the module-switch-on-port-available module provides. When you plug your headphones in, the selected port will switch (you should be able to notice this in pavucontrol I think), which means your media keys / sound indicator / etc would control your headphone's volume instead of your speaker's volume. For the multi HDMI case - if you have selected the wrong HDMI interface, and then activate your HDMI screen, module-switch-on-port-available should automatically switch to the correct one. This is all assuming you're running PulseAudio 2.0 - earlier versions of PulseAudio do not have this functionality. Should you be interested in backporting the jack detection kernel patches, I'll be happy to point you to the Ubuntu kernel's git tree, where I did the same thing. -- David Henningsson, Canonical Ltd. https://launchpad.net/~diwic -- 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/4fd586c2.6050...@canonical.com