Processed: reassign 683594 to src:linux

2012-08-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 683594 src:linux 3.2.21-3
Bug #683594 [src] linux-image-3.2.0-3-amd64: system crash while disliking a 
youtube video
Warning: Unknown package 'src'
Bug reassigned from package 'src' to 'src:linux'.
No longer marked as found in versions 3.2.21-3.
Ignoring request to alter fixed versions of bug #683594 to the same values 
previously set
Bug #683594 [src:linux] linux-image-3.2.0-3-amd64: system crash while disliking 
a youtube video
Marked as found in versions linux/3.2.21-3.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
683594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683594
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.134389410024985.transcr...@bugs.debian.org



Bug#683619: NBD lockup with segfaulting qemu-nbd

2012-08-02 Thread Stefan Bühler
Package: linux-image-3.2.0-3-amd64
Version: 3.2.21-3

Hi,

i tried to get https://github.com/asb/spindle running,
but in ./wheezy-stage0 mkfs hangs forever.

kill -9 doesn't work on mkfs and qemu-nbd, and i can't attach with
strace (at least i can kill strace).

I guess qemu-nbd shouldn't segfault in the first place,
but the kernel should handle this better.

qemu-nbd -d (disconnect) doesn't work (and can't be killed either).

USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root  5206  0.0  0.0 129644  2384 ?Dsl  10:29   0:00 qemu-nbd 
--nocache -c /dev/nbd0 /.../spindle/work/wheezy_apt_cache.qed
root  9504  0.0  0.1  96460  6524 pts/4D+   10:35   0:00 qemu-nbd -d 
/dev/nbd0


[ 4353.088802]  nbd0: unknown partition table
[ 4358.345650] qemu-nbd[5206]: segfault at 0 ip 7fd160ea20b8 sp 
7fd160e32cc0 error 4 in qemu-nbd[7fd160e55000+6d000]
[ 4358.345694] nbd (pid 5209: qemu-nbd) got signal 9
[ 4560.732316] INFO: task qemu-nbd:5206 blocked for more than 120 seconds.
[ 4560.732321] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables this 
message.
[ 4560.732324] qemu-nbdD 88009c63f8d0 0  5206  1 0x
[ 4560.732330]  88009c63f8d0 0082 88009c63f918 
88011aee87b0
[ 4560.732336]  00013740 8800b6df9fd8 8800b6df9fd8 
88009c63f8d0
[ 4560.732341]  88011fd137b0 88011fd13740 8801164fc830 
7fff
[ 4560.732347] Call Trace:
[ 4560.732356]  [81349d2e] ? schedule_timeout+0x2c/0xdb
[ 4560.732362]  [8103f47f] ? try_to_wake_up+0x187/0x197
[ 4560.732366]  [81349974] ? wait_for_common+0xa0/0x119
[ 4560.732370]  [8103f48f] ? try_to_wake_up+0x197/0x197
[ 4560.732375]  [810ff18c] ? do_coredump+0x2b5/0xab9
[ 4560.732380]  [8107072d] ? arch_local_irq_save+0x11/0x17
[ 4560.732384]  [8134abd4] ? _raw_spin_lock_irqsave+0x9/0x25
[ 4560.732388]  [8103f47f] ? try_to_wake_up+0x187/0x197
[ 4560.732393]  [81053d3b] ? __dequeue_signal+0xca/0xf4
[ 4560.732397]  [81053bd8] ? recalc_sigpending+0x23/0x3c
[ 4560.732402]  [81055baf] ? get_signal_to_deliver+0x464/0x48f
[ 4560.732407]  [81343a19] ? force_sig_info_fault+0x5b/0x63
[ 4560.732413]  [8100de33] ? do_signal+0x38/0x610
[ 4560.732417]  [8103f48f] ? try_to_wake_up+0x197/0x197
[ 4560.732422]  [810fa727] ? fget_light+0x5f/0x73
[ 4560.732427]  [8100e441] ? do_notify_resume+0x25/0x68
[ 4560.732431]  [8134afbc] ? retint_signal+0x48/0x8c
[ 4560.732435] INFO: task qemu-nbd:5207 blocked for more than 120 seconds.
[ 4560.732438] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables this 
message.
[ 4560.732441] qemu-nbdD 88011aee87b0 0  5207  1 0x
[ 4560.732445]  88011aee87b0 0082  
8801164fc140
[ 4560.732451]  00013740 8800d81fdfd8 8800d81fdfd8 
88011aee87b0
[ 4560.732456]  88011aee87b0 8800d825f080 88011aee87b0 
88011aee87b0
[ 4560.732461] Call Trace:
[ 4560.732466]  [8104986f] ? exit_mm+0x97/0x122
[ 4560.732471]  [81049b40] ? do_exit+0x246/0x6fc
[ 4560.732475]  [8104a276] ? do_group_exit+0x74/0x9e
[ 4560.732479]  [81055bb8] ? get_signal_to_deliver+0x46d/0x48f
[ 4560.732484]  [8100de33] ? do_signal+0x38/0x610
[ 4560.732489]  [81037ec0] ? set_next_entity+0x32/0x55
[ 4560.732493]  [8100d025] ? paravirt_write_msr+0xb/0xe
[ 4560.732497]  [8100d6f1] ? __switch_to+0x181/0x258
[ 4560.732503]  [8106f2f9] ? sys_futex+0x138/0x147
[ 4560.732507]  [8100e441] ? do_notify_resume+0x25/0x68
[ 4560.732512]  [8134fe60] ? int_signal+0x12/0x17
[ 4560.732515] INFO: task qemu-nbd:5208 blocked for more than 120 seconds.
[ 4560.732518] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables this 
message.
[ 4560.732521] qemu-nbdD 8801164fc140 0  5208  1 0x
[ 4560.732526]  8801164fc140 0082  
8801164fc830
[ 4560.732531]  00013740 8800d4235fd8 8800d4235fd8 
8801164fc140
[ 4560.732536]  8801164fc140 8800d825f080 8801164fc140 
8801164fc140
[ 4560.732542] Call Trace:
[ 4560.732546]  [8104986f] ? exit_mm+0x97/0x122
[ 4560.732550]  [81049b40] ? do_exit+0x246/0x6fc
[ 4560.732555]  [8104a276] ? do_group_exit+0x74/0x9e
[ 4560.732559]  [81055bb8] ? get_signal_to_deliver+0x46d/0x48f
[ 4560.732564]  [8100de33] ? do_signal+0x38/0x610
[ 4560.732569]  [8106f2f9] ? sys_futex+0x138/0x147
[ 4560.732573]  [8100e441] ? do_notify_resume+0x25/0x68
[ 4560.732577]  [8134fe60] ? int_signal+0x12/0x17
[ 4560.732581] INFO: task qemu-nbd:5209 blocked for more than 120 seconds.
[ 4560.732583] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables this 
message.
[ 4560.732586] qemu-nbdD 88011fd13740 0  5209  

Bug#647741: still occurs in 3.2.15-1

2012-08-02 Thread Vincent Lefevre
On 2012-07-18 00:38:50 +0200, Vincent Lefevre wrote:
 I've reverted to tmpfs for /tmp. I haven't seen any problem yet,
 but my laptop isn't currently under normal conditions. I may
 have more information in a few days, or more likely at the end
 of the month. If the problem doesn't reappear, I'll revert to
 the Linux kernel 3.2.15.

Under the usual conditions, I couldn't see any problem with
tmpfs for /tmp. I've now reverted to:

  Linux version 3.2.0-1-amd64 (Debian 3.2.7-1) (debian-kernel@lists.debian.org) 
(gcc version 4.6.2 (Debian 4.6.2-16) ) #1 SMP Tue Feb 28 15:35:32 UTC 2012

(still with tmpfs for /tmp) and I'll see whether the temporary freeze
problems reappear.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
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/20120802122214.ga6...@xvii.vinc17.org



linux_3.5-1~experimental.1_multi.changes ACCEPTED into experimental

2012-08-02 Thread Debian FTP Masters



Accepted:
linux-doc-3.5_3.5-1~experimental.1_all.deb
  to main/l/linux/linux-doc-3.5_3.5-1~experimental.1_all.deb
linux-manual-3.5_3.5-1~experimental.1_all.deb
  to main/l/linux/linux-manual-3.5_3.5-1~experimental.1_all.deb
linux-source-3.5_3.5-1~experimental.1_all.deb
  to main/l/linux/linux-source-3.5_3.5-1~experimental.1_all.deb
linux-support-3.5-trunk_3.5-1~experimental.1_all.deb
  to main/l/linux/linux-support-3.5-trunk_3.5-1~experimental.1_all.deb
linux_3.5-1~experimental.1.debian.tar.xz
  to main/l/linux/linux_3.5-1~experimental.1.debian.tar.xz
linux_3.5-1~experimental.1.dsc
  to main/l/linux/linux_3.5-1~experimental.1.dsc
linux_3.5.orig.tar.xz
  to main/l/linux/linux_3.5.orig.tar.xz


Changes:
linux (3.5-1~experimental.1) experimental; urgency=low
 .
  * New upstream release: http://kernelnewbies.org/Linux_3.5
 .
  [ Ben Hutchings ]
  * net: Enable OPENVSWITCH as module (Closes: #675010)
  * aufs: Update to aufs3.5-20120730
  * rt: Disable until it is updated for Linux 3.5 or later
  * debian/copyright: Convert to machine-readable format (fka DEP-5)
  * debian/copyright: Add copyright notice for newly-added Unicode data
  * [x86] seccomp: Enable SECCOMP_FILTER
  * [x86] applesmc: Update to Linux 3.6, including fixes for new MacBook models


Override entries for your package:
linux-doc-3.5_3.5-1~experimental.1_all.deb - optional doc
linux-manual-3.5_3.5-1~experimental.1_all.deb - optional doc
linux-source-3.5_3.5-1~experimental.1_all.deb - optional kernel
linux-support-3.5-trunk_3.5-1~experimental.1_all.deb - optional devel
linux_3.5-1~experimental.1.dsc - source kernel

Announcing to debian-experimental-chan...@lists.debian.org
Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 675010 


Thank you for your contribution to Debian.


-- 
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/e1swy5v-0001tm...@franck.debian.org



[bts-link] source package linux-2.6

2012-08-02 Thread bts-link-upstream
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #584830 (http://bugs.debian.org/584830)
# Bug title: linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents suspend
#  * http://bugzilla.kernel.org/show_bug.cgi?id=16153
#  * remote status changed: NEW - RESOLVED
#  * remote resolution changed: (?) - CODE-FIX
#  * closed upstream
tags 584830 + fixed-upstream
usertags 584830 - status-NEW
usertags 584830 + status-RESOLVED resolution-CODE-FIX

thanks


--
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/20120802164924.29612.69865.btsl...@busoni.debian.org



[bts-link] source package src:linux

2012-08-02 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 #680707 (http://bugs.debian.org/680707)
# Bug title: Asus P5NSLI: lockup on resume from suspend
#  * http://bugzilla.kernel.org/show_bug.cgi?id=43641
#  * remote status changed: RESOLVED - CLOSED
usertags 680707 - status-RESOLVED
usertags 680707 + status-CLOSED

thanks


--
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/20120802164924.29612.42346.btsl...@busoni.debian.org



Bug#660288: Please enable CONFIG_KALLSYMS_ALL

2012-08-02 Thread Tim Abbott

On 06/07/2012 07:34 PM, Ben Hutchings wrote:


On Mon, Jun 04, 2012 at 05:26:28PM -0400, Tim Abbott wrote:
 Hi Ben,

 Your comment about source code is rather off-topic for this bug
 report, but since there seems to be a misunderstanding on this
 point, I'd like to clarify: Every Ksplice update tarball ships with
 a README file containing instructions on how to request the source
 code for that update from the appropriate people in Oracle Legal.
 Anyone who follows those instructions can get a copy of the relevant
 source code.

I understand that Matthew Garrett tried to take up this offer a while
ago, and is still waiting for complete source code.  It doesn't seem
to be a good faith attempt to fulfil GPL obligations.
This is not my department, but as I understand it, Matthew Garrett 
received complete source code in response to each of his various 
requests for Ksplice source code.



 To briefly clarify my original email, it is true that enabling
 CONFIG_KALLSYMS_ALL would make life slightly easier for Ksplice and
 similar tools that look at kernel data structures (e.g. debugging
 tools).

No doubt true, but it is also strictly redundant with debuginfo.
This is where I disagree.  Debuginfo is both huge (since it contains 
lots of data beyond the basic symbol information in kallsyms) and is 
also not necessarily available on user systems, meaning that any sort of 
patching or debugging tool intending to get wide use can't rely on it.  
Further, any system which contains third-party modules (open source or 
not) will not have symbol data for those modules unless the vendors of 
those third-party modules provide a separate debuginfo package (many do 
not); with kallsyms, you're guaranteed to have accurate information that 
comes from the modules that are actually loaded on the system.


As I think I mentioned before, when folks upgrade the kernel version on 
disk on a Debian system and don't immediately reboot (which folks do 
_all the time_ whether they're using Ksplice or not), and then load 
kernel modules, they'll get kernel modules from the upgraded kernel (at 
least in the common case where the ABI doesn't change). As a 
consequence, if you're any sort of debugging/instrumentation tool that 
inspects the running kernel's code, you need to be able to handle the 
case where the kernel is running modules that don't actually go with 
either the running kernel (via uname -a) or the currently version of 
the linux-image-* package installed on disk. Trying to do anything to 
get symbol information in that sort of situation using debuginfo is a 
disaster; what you want is kallsyms.



 That said, Ksplice doesn't require CONFIG_KALLSYMS_ALL --
 the Ksplice Uptrack service has been providing updates for systems
 running Debian Linux since 2009.  While your enabling
 CONFIG_KALLSYMS_ALL might allow us to delete like 50 lines of code 2
 years from now when Squeeze reaches end of life, I submitted this
 bug report primarily because I'd like it to be the case that other
 folks developing similar innovative new technologies don't have to
 do the extra work of supporting !CONFIG_KALLSYMS_ALL in order to
 support all the major Linux distributions.  I hope you'll consider
 my suggestion on its technical merits.
  
I'm going to have see a request from an actual other person before I

care to spend time on this.

(In case anyone else in the kernel team wants to proceed with this,
that's not a NAK.  The issue is that memory and/or flash partition
constraints make this unsuitable for some configurations, and you'll
need to work out which ones to enable it for.)
CONFIG_KALLSYMS_ALL adds less than 1% to the size of the kernel over 
CONFIG_KALLSYMS (obviously this depends on what options one had enabled 
in the first place), so only on truly embedded settings will that matter 
at all.  Could you at least just enable it for the architectures where 
none of Debian's stock kernels are designed for embedded environments 
(e.g. x86, sparc, power)?


-Tim Abbott


Bug#683026: --add-architecture

2012-08-02 Thread Filipus Klutiero
It looks like --add-architecture is not a great solution. After doing 
that, packages in Synaptic would show with :amd64 (for example, 
mesa-utils). I had to remove the architecture, but that wasn't possible 
until I uninstalled the amd64 package.



--
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/501b1374.9080...@gmail.com



Bug#656196: [2.6.39 - 3.0 regression] kernel stalls every few days (rcu_sched_state detected stall on CPU x)

2012-08-02 Thread Jonathan Nieder
Hi,

Michael Below wrote:

 [Subject: Seems fixed in 3.4]

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 contet.

 I upgraded the kernel to 3.4 from experimental, the stall warning
 doesn't appear anymore. At the same time, there are more workaround
 messages during USB startup:

Thanks!

Earlier I asked about whether idle=mwait had any effect on this bug.
Did it?

Could you bisect through the kernels at

  http://snapshot.debian.org/package/linux-2.6/

to find which is the first fixed one?  That would help a lot in
isolating what change is likely to have fixed this, so we can apply
that change to wheezy and make sure it is applied to the upstream
3.2.y tree for other distributors, too.

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/20120803004116.GB30701@copier



Processed: tagging 675493

2012-08-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 675493 + pending
Bug #675493 [linux-2.6] linux-image-3.2.0-2-amd64: Include 3.3 patches to fix 
I/O stalls on slow disks when using transparant hugepages
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675493
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.1343957872618.transcr...@bugs.debian.org



Byte queue limits in Linux for wheezy

2012-08-02 Thread Ben Hutchings
Byte queue limits (BQL) are an important step in reducing 'bufferbloat'
and network latency on Linux.  The feature was introduced in Linux 3.3
and has had a few bug fixes since then; I think it can be considered
stable now.  It requires specific support in drivers and is then
unconditionally enabled for them.  It provides some tuning parameters,
but should not normally require these to be changed.

I have prepared a backport of this to Linux 3.2 that I would like to
include in wheezy, but I ran out of time to do that before the freeze.
Since BQL is a new feature, it would not normally be allowed to make
such a change now.  However, it may also be considered an important fix
for performance problems (high network latency).  Therefore I am
requesting a freeze exception in category 5, pre-approved fixes.  I
believe it can be easily backed-out in case it causes regressions.

BQL requires an ABI change, but so do some of the fixes in Linux 3.2.25,
so the next upload will have an ABI bump in any case.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
 - Carolyn Scheppner


signature.asc
Description: This is a digitally signed message part