Bug#703673: Request to backport acpi changes to Debian sid for proper acpi child device handling

2013-03-21 Thread piruthiviraj natarajan
Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 Severity: important There is a upstream linux kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=42696 which prevents the Lenovo Y580/Y470/Y570 and Toshiba Satellite P870 devices unable to find the Nvidia card through proper acpi device hand

Re: [RFC] Putting the date back into utsname::version

2013-03-21 Thread Timo Juhani Lindfors
Ben Hutchings writes: > We have a longstanding support problem where there is confusion between > the kernel release string (utsname::release, output of uname -r, tail of > package names) and the kernel package version. Agreed. > Would anyone like to argue in favour of any particular alternative

Re: PREEMPT_RT vs 'hrtimer: Prevent hrtimer_enqueue_reprogram race'

2013-03-21 Thread Steven Rostedt
On Fri, 2013-03-22 at 03:24 +, Ben Hutchings wrote: > > Note, I posted a fix on Tuesday: > > > > https://lkml.org/lkml/2013/3/19/369 > > Thanks. I did search GMANE with some obvious terms but I think its > index is lagging. It didn't help that my subject had no mention of -rt in it :-( >

Processed: reassign 703668 to src:linux, found 703668 in linux/3.2.39-2

2013-03-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 703668 src:linux 3.2.39-2 Bug #703668 [linux-image-3.2.0-4-amd64] linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.39-2-amd64-G5_nM0/linux-3.2.39/fs/inode.c:428 Bug reassigned from package 'linux-image-3.2.0-4-amd64' to '

Re: PREEMPT_RT vs 'hrtimer: Prevent hrtimer_enqueue_reprogram race'

2013-03-21 Thread Ben Hutchings
On Thu, 2013-03-21 at 22:31 -0400, Steven Rostedt wrote: > On Fri, 2013-03-22 at 01:11 +, Ben Hutchings wrote: > > Commit b22affe0aef4 'hrtimer: Prevent hrtimer_enqueue_reprogram race' > > conflicts with the RT patches > > hrtimer-fixup-hrtimer-callback-changes-for-preempt-r.patch and > > peter

Re: PREEMPT_RT vs 'hrtimer: Prevent hrtimer_enqueue_reprogram race'

2013-03-21 Thread Steven Rostedt
On Fri, 2013-03-22 at 01:11 +, Ben Hutchings wrote: > Commit b22affe0aef4 'hrtimer: Prevent hrtimer_enqueue_reprogram race' > conflicts with the RT patches > hrtimer-fixup-hrtimer-callback-changes-for-preempt-r.patch and > peter_zijlstra-frob-hrtimer.patch, as they all change > hrtimer_enqueue_

Bug#703668: linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.39-2-amd64-G5_nM0/linux-3.2.39/fs/inode.c:428

2013-03-21 Thread Clint Adams
Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 This is transcribed, and due to photographic ineptitude, I've lost everything after the RIP line: kernel BUG at /build/buildd-linux_3.2.39-2-amd64-G5_nM0/linux-3.2.39/fs/inode.c:428 invalid opcode: [#1] SMP CPU 2 Modules linked in: tun pa

PREEMPT_RT vs 'hrtimer: Prevent hrtimer_enqueue_reprogram race'

2013-03-21 Thread Ben Hutchings
Commit b22affe0aef4 'hrtimer: Prevent hrtimer_enqueue_reprogram race' conflicts with the RT patches hrtimer-fixup-hrtimer-callback-changes-for-preempt-r.patch and peter_zijlstra-frob-hrtimer.patch, as they all change hrtimer_enqueue_reprogram(). It seems that the changes in the RT patches now belo

[RFC] Putting the date back into utsname::version

2013-03-21 Thread Ben Hutchings
[Please reply to the debian-kernel list only.] We have a longstanding support problem where there is confusion between the kernel release string (utsname::release, output of uname -r, tail of package names) and the kernel package version. Until recently, even uname -a would not report the package

Bug#703665: linux-image-3.8-trunk-amd64: version 3.8.3-1~experimental.1 causes xrandr to detect too many monitors

2013-03-21 Thread Alex Vanderpol
Package: src:linux Version: 3.8.3-1~experimental.1 Severity: important Dear Maintainer, Recently it was discovered in Ubuntu that version 3.8.3 of the linux kernel had issues that caused xrandr to detect an external monitor connected to a laptop with Intel integrated graphics when in fact no moni

Re: [PATCH] ext4/jbd2: don't wait (forever) for stale tid caused by wraparound

2013-03-21 Thread Jan Kara
On Thu 21-03-13 17:09:40, Ted Tso wrote: > On Thu, Mar 21, 2013 at 09:46:38PM +0100, Jan Kara wrote: > > Good catch! But shouldn't we rather fix jbd2_log_wait_commit() instead of > > inventing new function? > > In most of the places where we call jbd2_log_start_commit(), we're > actually startin

Re: [PATCH] ext4/jbd2: don't wait (forever) for stale tid caused by wraparound

2013-03-21 Thread Jan Kara
On Sun 17-03-13 22:54:01, Ted Tso wrote: > On Sat, Mar 16, 2013 at 05:34:22AM +, Ben Hutchings wrote: > > > We use debian for a number of machines in our storage infrastructure > > > and we have recently been seeing a number of "hangs". We primary > > > notice this by seeing nfsd processes lock

Re: [PATCH] ext4/jbd2: don't wait (forever) for stale tid caused by wraparound

2013-03-21 Thread Theodore Ts'o
On Thu, Mar 21, 2013 at 09:46:38PM +0100, Jan Kara wrote: > Good catch! But shouldn't we rather fix jbd2_log_wait_commit() instead of > inventing new function? In most of the places where we call jbd2_log_start_commit(), we're actually starting the current running transaction. So the fact that

Bug#703640: src:linux: [3.8 -> 3.8.1 regression]: Resume from suspend stuck with framebuffer locking rework

2013-03-21 Thread Vincent Blut
Le jeudi 21 mars 2013 à 19:28 +0100, Vincent Blut a écrit : > Package: src:linux > Version: 3.8.3-1~experimental.1 > Severity: important > Tags: upstream > > Hi, > > As mentioned in the subject, the following commit prevents me to resume from > suspend in kernel ≥ 3.8.1: > > commit cace7c323ddd

Processed: tagging 703640

2013-03-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 703640 + moreinfo Bug #703640 [src:linux] src:linux: [3.8 -> 3.8.1 regression]: Resume from suspend stuck with framebuffer locking rework Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-21 Thread Jonathan Nieder
Julien Cristau wrote: > On Thu, Mar 21, 2013 at 12:03:56 -0700, Jonathan Nieder wrote: >> I know Alan takes reports through bugzilla.kernel.org > > Still? I thought that would have kinda stopped after > https://plus.google.com/04121194250082892/posts/KW3TdRYwjr9 You're right. I'm out of dat

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-21 Thread Julien Cristau
On Thu, Mar 21, 2013 at 12:03:56 -0700, Jonathan Nieder wrote: > I know Alan takes reports through bugzilla.kernel.org Still? I thought that would have kinda stopped after https://plus.google.com/04121194250082892/posts/KW3TdRYwjr9 Cheers, Julien signature.asc Description: Digital signatu

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-21 Thread Jonathan Nieder
Hi, Julien Cristau wrote: > On Wed, Mar 20, 2013 at 22:58:41 -0700, Jonathan Nieder wrote: >> Jonathan Nieder wrote: >>> Georg Sassen wrote: While the native resolution (1280x720) worked fine until kernel version 3.2.0.4-686-pae_3.2.35-2, I now only have 800x600 resolution in X11 a

Bug#703640: src:linux: [3.8 -> 3.8.1 regression]: Resume from suspend stuck with framebuffer locking rework

2013-03-21 Thread Vincent Blut
Package: src:linux Version: 3.8.3-1~experimental.1 Severity: important Tags: upstream Hi, As mentioned in the subject, the following commit prevents me to resume from suspend in kernel ≥ 3.8.1: commit cace7c323ddde7358ab2f2390ece964c55f30330 Author: Alan Cox Date: Fri Jan 25 10:28:15 2013 +1

Processed: tagging 703637

2013-03-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 703637 + moreinfo Bug #703637 [src:linux] linux-image-3.2.0-4-amd64: Kernel Panic randomly after upgrade to 3.2.39-2 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 703637: http://bugs

Bug#703637: linux-image-3.2.0-4-amd64: Kernel Panic randomly after upgrade to 3.2.39-2

2013-03-21 Thread Julien Cristau
On Fri, Mar 22, 2013 at 01:32:07 +0800, SuperCat wrote: > Package: src:linux > Version: 3.2.39-2 > Severity: important > > Dear Maintainer, > I got kernel panic randomly after I upgrade the kernel from 3.2.35 to > 3.2.39-2. > I have tried to rollback the kernel to 3.2.35, and the kernel works fi

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-21 Thread Julien Cristau
On Wed, Mar 20, 2013 at 22:58:41 -0700, Jonathan Nieder wrote: > Hi again, > > I left out the URL for Intel's bug reporting guidelines: > > Jonathan Nieder wrote: > > Georg Sassen wrote: > > >> While the native resolution (1280x720) worked fine until kernel > >> version 3.2.0.4-686-pae_3.2.35-2

Bug#703637: linux-image-3.2.0-4-amd64: Kernel Panic randomly after upgrade to 3.2.39-2

2013-03-21 Thread SuperCat
Package: src:linux Version: 3.2.39-2 Severity: important Dear Maintainer, I got kernel panic randomly after I upgrade the kernel from 3.2.35 to 3.2.39-2. I have tried to rollback the kernel to 3.2.35, and the kernel works fine again. -- Package-specific info: ** Version: Linux version 3.2.0-4-a

[bts-link] source package src:linux

2013-03-21 Thread bts-link-upstream
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #702885 (http://bugs.debian.org/702885) # Bug title: linux-image-3.8-trunk-amd64: Sa

Bug#703592: closed by Ben Hutchings (Re: Bug#703592: /dev/console vs. mesg(1) in recovery mode)

2013-03-21 Thread jidanni
B> You booted in single user mode. What would be the point of letting B> other users write to your terminal? Besides which /dev/console had damn B> well better be trustworthy. The point is that single user mode comes before the ttys are fully set up! It should come after! -- To UNSUBSCRIBE,

Bug#703592: marked as done (/dev/console vs. mesg(1) in recovery mode)

2013-03-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Mar 2013 14:18:08 + with message-id <1363875488.31336.118.ca...@deadeye.wl.decadent.org.uk> and subject line Re: Bug#703592: /dev/console vs. mesg(1) in recovery mode has caused the Debian Bug report #703592, regarding /dev/console vs. mesg(1) in recovery mode to be m

Bug#703209: linux: Please Add multiplatform flavour to armhf

2013-03-21 Thread Lennart Sorensen
On Thu, Mar 21, 2013 at 08:42:49AM +, Tixy wrote: > A single multiplatform kernel can support both armv6 and armv7 (or armv4 > + armv5). I don't know if Debian plans to have separate versions for > each architecture version - there may be performance benefits to this - > in which case using arm

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-21 Thread Georg Sassen
Hi Jonathan, > Thanks for reporting. Can you reproduce this using > xserver-xorg-video-modesetting and the 3.8.y kernel from experimental > as well? With the 3.8 kernel it works fine, the gma500_gfx module ist loaded and the native resolution of the display shown. > I don't see your GPU driver

how are you?

2013-03-21 Thread Daniele Velardi
http://wheusden.nl/wp-content/windows8.php?gzcfbwwt700rkzzdh = It really is a shame that this is the only planet we have a choice to live on. -- Howard Stern

Bug#703607: Please include Cypress PS/2 Trackpad driver in linux-image-3.2.0-*

2013-03-21 Thread Apollon Oikonomopoulos
Package: src:linux Version: 3.2.39-2 Severity: wishlist Dear Maintainer, Please include the driver for the Cypress PS/2 Trackpad found in newer Dell laptops (Dell XPS 12 and XPS 13) in wheezy's 3.2 kernel. Without this driver the trackpad works as a plain PS/2 mouse with no additional features (t

Bug#703209: linux: Please Add multiplatform flavour to armhf

2013-03-21 Thread Tixy
On Thu, 2013-03-21 at 12:52 +0900, Nobuhiro Iwamatsu wrote: > Hi, > > On Wed, Mar 20, 2013 at 12:17 AM, Paul Wise wrote: > > On Tue, 2013-03-19 at 15:05 +, Ian Campbell wrote: > > > >> I think the question here is what the `uname -r` bit should be. > >> Specifically the $FLAVOUR in 3.x.y-z-$F

Bug#703592: /dev/console vs. mesg(1) in recovery mode

2013-03-21 Thread jidanni
Package: src:linux Version: 3.2.39-2 Severity: minor At boot choose recovery mode, 'Debian GNU/Linux, with Linux 3.2.0-4-486 (recovery mode)' Type the root password, then in the shell that appears, type # mesg y This will cause mesg: error: tty device is not owned by group `tty' Note I did this