Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Hi Peter, Peter Colberg wrote: Package: linux-2.6 Version: 3.2.2-1 Severity: important Tags: upstream Which upstream version did you test? 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/20120205084453.GC1870@burratino
Uploading linux-2.6 (3.2.4-1)
Hi I intend to upload linux-2.6 3.2.4-1 later today. It fixes the mips FTBFS and also includes the pci-e power management (aspm) rework. Bastian -- Love sometimes expresses itself in sacrifice. -- Kirk, Metamorphosis, stardate 3220.3 -- 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/20120205085624.ga24...@wavehammer.waldi.eu.org
Processed: tagging 649033
Processing commands for cont...@bugs.debian.org: tags 649033 + pending Bug #649033 [linux-2.6] tpm_tis: hang during initialization (udevd: timeout: killing '/sbin/modprobe -b acpi:SMO1200:PNP0C31:') Ignoring request to alter tags of bug #649033 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 649033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649033 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.132843264429371.transcr...@bugs.debian.org
Bug#658578: linux-image-2.6.32-5-amd64: Random kernel panic when inserting USB stick
On Sat, 04 Feb 2012 16:29:34 +0530 dE . de.tec...@gmail.com wrote: Try testing with one of the backported kernels. Kernel 3.2.0 works fine (~100 plug/unplug cycles, while 2.6.32 fails on first 10-20). pgpYGogl042DH.pgp Description: PGP signature
Bug#657916: linux-source-2.6.32: ps time doubled then constant: missing lock for task_utime?
I wrote: I only observed this for multi-threaded processes compiled with -fopenmp . I think I now observed the same issue with a single-threaded process: $ ps u -p 14252 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND duncans 14252 150 9.7 2458868 2408272 ? RN Jan03 71589:24 ./compact $ grep . /proc/14252/stat /proc/14252/task/*/stat /proc/14252/stat:14252 (compact) R 1 14222 14218 0 -1 4202496 366809489 0 0 0 429428470 108008 0 0 36 16 1 0 130475208 2517880832 602068 4294967295 1 1 0 0 0 0 0 0 132 4294967295 0 0 17 0 0 0 0 0 0 /proc/14252/task/14252/stat:14252 (compact) R 1 14222 14218 0 -1 4202496 366809489 0 0 0 429428468 95107 0 0 36 16 1 0 130475208 2517880832 602068 4294967295 1 1 0 0 0 0 0 0 132 4294967295 0 0 17 0 0 0 0 0 0 Should I investigate, should I try to reproduce, and check by how much do TIME and %CPU jump when the wrong results start? Thanks, Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- 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/201202051106.q15b64im007...@bari.maths.usyd.edu.au
Bug#658697: linux: Tasks hungs for more than 2 mins and getting blocked by kernel as in result
Package: linux-2.6 Version: 2.6.32-41 Severity: normal File: linux Hello, I'm having trouble with my debian server for last two months: tasks under high load (such as apache, mysql) hungs and kernel blocks them, sending thousands of report to dmesg: [ 2160.503948] INFO: task apache2:10350 blocked for more than 120 seconds. [ 2160.503956] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 2160.503967] apache2 D 0 10350 9695 0x [ 2160.503976] ea16fb40 00200082 c141d100 c141d100 ea486198 [ 2160.504013] ea16fcfc c3408100 6a73887e 01cd bd0bba94 cdd0f017 e8aa3f00 [ 2160.504036] ea486198 ea16fcfc ef41d89c ef4bc660 e8aa3ea8 ea5d489c c10c1453 e8aa3f00 [ 2160.504064] Call Trace: [ 2160.504074] [c10c1453] ? dput+0x22/0x105 [ 2160.504083] [c126dde7] ? __mutex_lock_common+0xe8/0x13b [ 2160.504093] [c126de49] ? __mutex_lock_slowpath+0xf/0x11 [ 2160.504103] [c126deda] ? mutex_lock+0x17/0x24 [ 2160.504112] [c126deda] ? mutex_lock+0x17/0x24 [ 2160.504121] [c10bbdf7] ? do_filp_open+0x1e6/0x802 [ 2160.504130] [c10c3d6d] ? alloc_fd+0x52/0xb7 [ 2160.504138] [c10b1bef] ? do_sys_open+0x4c/0xdf [ 2160.504145] [c10b1cc6] ? sys_open+0x1e/0x23 [ 2160.504153] [c10030fb] ? sysenter_do_call+0x12/0x28 I'm not 100% sure that this is software bug, it's can be a problem with disk too. But I did a full disk check with smartctl and it reported no problems. I also did read/write disk benchmark with hdparm, results looks good again. Sorry for my english :) -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 04:15:24 UTC 2011 ** Command line: ro root=/dev/sda1 --verbose ** Not tainted ** Kernel log: [ 2160.502429] [c108bcf1] ? get_page_from_freelist+0xc0/0x3c7 [ 2160.502438] [c126d73a] ? io_schedule+0x5f/0x98 [ 2160.502445] [c10ce76e] ? sync_buffer+0x30/0x33 [ 2160.502452] [c126da98] ? __wait_on_bit_lock+0x31/0x6a [ 2160.502460] [c10ce73e] ? sync_buffer+0x0/0x33 [ 2160.502468] [c126db86] ? out_of_line_wait_on_bit_lock+0xb5/0xbd [ 2160.502475] [c10ce73e] ? sync_buffer+0x0/0x33 [ 2160.502483] [c104405b] ? wake_bit_function+0x0/0x3c [ 2160.502490] [c10cea87] ? __lock_buffer+0x21/0x24 [ 2160.502498] [c10ceaf1] ? sync_dirty_buffer+0x21/0x83 [ 2160.502506] [f7ef7ce9] ? journal_dirty_data+0xc6/0x191 [jbd] [ 2160.502516] [f7f31651] ? ext3_journal_dirty_data+0xc/0x2a [ext3] [ 2160.502526] [f7f2fe4c] ? walk_page_buffers+0x4c/0x65 [ext3] [ 2160.502536] [f7f32f45] ? ext3_ordered_write_end+0x79/0x141 [ext3] [ 2160.502545] [f7f3166f] ? journal_dirty_data_fn+0x0/0x14 [ext3] [ 2160.502554] [c10885ce] ? generic_file_buffered_write+0x12f/0x21d [ 2160.502561] [c10c951c] ? __mark_inode_dirty+0x20/0x10b [ 2160.502569] [c10c951c] ? __mark_inode_dirty+0x20/0x10b [ 2160.502577] [c1088ab9] ? __generic_file_aio_write+0x265/0x28d [ 2160.502585] [c1089074] ? generic_file_aio_read+0x500/0x57b [ 2160.503354] [c1088b32] ? generic_file_aio_write+0x51/0x93 [ 2160.503363] [c10b335e] ? do_sync_write+0xc0/0x107 [ 2160.503370] [c104402e] ? autoremove_wake_function+0x0/0x2d [ 2160.503378] [c104402e] ? autoremove_wake_function+0x0/0x2d [ 2160.503386] [c10b30aa] ? fsnotify_modify+0x5a/0x61 [ 2160.503394] [c1102ae4] ? security_file_permission+0xc/0xd [ 2160.503402] [c10b329e] ? do_sync_write+0x0/0x107 [ 2160.503410] [c10b3c68] ? vfs_write+0x7e/0xd6 [ 2160.503417] [c10b3d06] ? sys_pwrite64+0x46/0x5c [ 2160.503425] [c10030fb] ? sysenter_do_call+0x12/0x28 [ 2160.503451] INFO: task apache2:10085 blocked for more than 120 seconds. [ 2160.503458] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 2160.503469] apache2 D c108bcf1 0 10085 9695 0x [ 2160.503479] ea168880 00200086 f6b66200 c108bcf1 0001 c141d100 c141d100 [ 2160.503497] ea168a3c c3508100 0001 00020050 c13b74ec c153d440 c13b5ba0 [ 2160.503516] 02e80c18 ea168a3c 394fe7a0 02e80c18 e9ca1e18 000c59d8 [ 2160.503535] Call Trace: [ 2160.503542] [c108bcf1] ? get_page_from_freelist+0xc0/0x3c7 [ 2160.503550] [c126d73a] ? io_schedule+0x5f/0x98 [ 2160.503558] [c10ce76e] ? sync_buffer+0x30/0x33 [ 2160.503565] [c126da98] ? __wait_on_bit_lock+0x31/0x6a [ 2160.503573] [c10ce73e] ? sync_buffer+0x0/0x33 [ 2160.503580] [c126db86] ? out_of_line_wait_on_bit_lock+0xb5/0xbd [ 2160.503588] [c10ce73e] ? sync_buffer+0x0/0x33 [ 2160.503596] [c104405b] ? wake_bit_function+0x0/0x3c [ 2160.503604] [c10cea87] ? __lock_buffer+0x21/0x24 [ 2160.503611] [c10ceaf1] ? sync_dirty_buffer+0x21/0x83 [ 2160.503621] [f7ef7ce9] ? journal_dirty_data+0xc6/0x191 [jbd] [ 2160.503631] [f7f31651] ? ext3_journal_dirty_data+0xc/0x2a [ext3] [ 2160.503641] [f7f2fe4c] ? walk_page_buffers+0x4c/0x65 [ext3] [ 2160.503651] [f7f32f45] ? ext3_ordered_write_end+0x79/0x141 [ext3] [ 2160.503661] [f7f3166f] ?
Bug#657302: linux-image-3.2.0-1-amd64: No more sound
Package: linux-2.6 Followup-For: Bug #657302 Same bug on my system. For some reason 'reportbug' isn't attaching all the 'linux-image-3.2.0-1-686-pae' package version data. Attached is the output of 'alsa-info.sh' v0.4.60, found here: http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh Hope this helps... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash alsa-info.txt.UHEyCHzLSG.gz Description: GNU Zip compressed data
Re: [bisected] Unstable desktop experience with kernel 2.6.38
Hi, I have the strong impression that commit 37a9d912b24f96a0591773e6e6c3642991ae5a70 (futex: Sanitize cmpxchg_futex_value_locked API) breaks something more general on IA-64. Yesterday, I though that PulseAudio was involved in the Iceweasel crash and the X restart when hitting the tab key while in a GNOME terminal window. Well, this is definitely the case, but PulseAudio is probably not the root cause, only a side effect. As you may remember, I was also unable to start up a gdb session yesterday. This is still true, but with kernel 2.6.38 only. Rebooting my system with kernel = 2.6.38 makes gdb happy again. Is there a way to debug gdb itself? I didn't found a gdb-dbg package. The idea is trying to collect various stack traces from various incorrectly running programs with kernel 2.6.38 in order to converge to _the_ binary or library impacted by the cmpxchg_futex change and that renders IA-64 barely usable at this time. Émeric Le 4 février 2012 19:32, Émeric Maschino emeric.masch...@gmail.com a écrit : Hi, Just to let you know that, as could have been guessed from my initial post (http://lists.debian.org/debian-ia64/2012/01/msg00016.html), PulseAudio is involved. Uninstalling pulseaudio, pulseaudio-esound-compat, pulseaudio-module-x11, pulseaudio-utils and gstreamer0.10-pulseaudio packages fixes the issue. Obviously, you get no more sound :-(. Is there something in PulseAudio source code that hasn't been updated (maybe only on IA-64?) following commit 37a9d912b24f96a0591773e6e6c3642991ae5a70 (futex: Sanitize cmpxchg_futex_value_locked API)? The bad news: I can't provide more information at this time as all the programs that I've tried to ran through gdb (most notably iceweasel and gnome-terminal as they were my easy to reproduce scenarii) are receiving SIGTRAP signal, and bt full reports No symbol table info available. I however have debug packages installed. Émeric Le 28 janvier 2012 20:21, Patrick Baggett baggett.patr...@gmail.com a écrit : From looking at: http://neil.brown.name/git?p=linux-2.6;a=blobdiff;f=arch/ia64/include/asm/futex.h;h=b0728404dad05c9349aea95d4e28b91b1b363a21;hp=c7f0f062239cd541112ecbe10cdd34dc54672eec;hb=37a9d912b24f96a0591773e6e6c3642991ae5a70;hpb=522d7decc0370070448a8c28982c8dfd8970489e It doesn't look like the return value (r8) is actually being set beyond initialized to 0. If there is some ia64 instruction that modifies it, GCC doesn't know about it from the inline assembly (r8 doesn't appear in the inputs/outputs list). From looking at the x86 version (agh, inline asm is hard to parse), it does modify the return value based on whether the comparison was a success or not, and the return value is certainly used by the callers. Patrick On Sat, Jan 28, 2012 at 6:43 AM, Émeric Maschino emeric.masch...@gmail.com wrote: Hi, Just to let you know that I've bisected this issue to commit 37a9d912b24f96a0591773e6e6c3642991ae5a70 (futex: Sanitize cmpxchg_futex_value_locked API). Émeric Le 17 janvier 2012 23:11, Émeric Maschino emeric.masch...@gmail.com a écrit : Hi, Since there's a workaround allowing us to go kernel 2.6.38 (http://lists.debian.org/debian-ia64/2012/01/msg00013.html), I obviously updated my Testing system to current linux-image-3.1.0-1-mckinley_3.1.8-2_ia64.deb. Well, graphical desktop experience is _unstable_. When I say desktop experience, I'm talking about basic desktop tasks, not fancy OpenGL rendering. I have at least two reproducible scenari (I'm running Gnome Classic): - random X restart while typing into a GNOME terminal window - Iceweasel killed when I try to click on the Back button or while trying to click on the Edit menu. For the latter one, I managed to get a stack trace with gdb, before gdb itself core dumped (huge core available if interested!) or X is restarted... It seems that something goes wrong with PulseAudio when running kernel 3.1: Program received signal SIGABRT, Aborted. [Switching to Thread 0x7002b5231e0 (LWP 2282)] 0xa0040721 in __kernel_syscall_via_break () Thread 19 (Thread 0x7002b5231e0 (LWP 2282)): #0 0xa0040721 in __kernel_syscall_via_break () No symbol table info available. #1 0x2031a900 in raise () from /lib/ia64-linux-gnu/libc.so.6.1 No symbol table info available. #2 0x20322eb0 in abort () from /lib/ia64-linux-gnu/libc.so.6.1 No symbol table info available. #3 0x07001612a310 in pa_mutex_unlock () from /usr/lib/ia64-linux-gnu/libpulsecommon-1.0.so No symbol table info available. #4 0x07001604f8b0 in poll_func () from /usr/lib/ia64-linux-gnu/libpulse.so.0 No symbol table info available. Rebooting my Testing system with good old kernel 2.6.38-5 brings a stable desktop experience back. I've performed regression testing: the issue is already there with linux-image-2.6.39-rc4-mckinley_2.6.39~rc4-1~experimental.1_ia64.deb, the
Re: Sparc netboot image is too large to boot (again)
Jurij Smakov, le Sat 04 Feb 2012 12:16:25 +, a écrit : I've noticed that, yet again, sparc daily netboot image is too large to boot. Last time we mitigated the problem by removing the support for wireless networking. I'm going to poke around again to see what else can be get rid of, please let me know if you have any ideas. AIUI, linux can now have support for uncompressing bzip2, lzma and lzo. Trying them on amd64's initrd: -rw-r--r-- 1 samy samy 8,5M févr. 5 14:06 initrd.gz -rw-r--r-- 1 samy samy 7,7M févr. 5 14:06 initrd.bz2 -rw-r--r-- 1 samy samy 6,2M févr. 5 14:06 initrd.lzma -rw-r--r-- 1 samy samy 9,4M févr. 5 14:06 initrd.lzo -rw-r--r-- 1 samy samy 6,2M févr. 5 14:07 initrd.xz (for comparison) Doesn't it seem worthwhile to enable lzma support in the kernel to save more than 2M here? Samuel -- 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/20120205130911.gm4...@type.famille.thibault.fr
Re: Sparc netboot image is too large to boot (again)
On Sun, Feb 05, 2012 at 02:09:11PM +0100, Samuel Thibault wrote: AIUI, linux can now have support for uncompressing bzip2, lzma and lzo. CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_RD_XZ=y CONFIG_RD_LZO=y The amd64 image have support for gzip, bzip2, lzma and the xz variant. Bastian -- ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, The Omega Glory, stardate unknown -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120205135549.ga2...@wavehammer.waldi.eu.org
Bug#657302: linux-image-3.2.0-1-amd64: No more sound
Hi, A. Costa wrote: Same bug on my system. Same codec, but not an Asus laptop so the patch mentioned here won't fix it. Please file a separate bug. 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/20120205140138.GD1870@burratino
Re: Sparc netboot image is too large to boot (again)
Bastian Blank, le Sun 05 Feb 2012 14:55:49 +0100, a écrit : On Sun, Feb 05, 2012 at 02:09:11PM +0100, Samuel Thibault wrote: AIUI, linux can now have support for uncompressing bzip2, lzma and lzo. CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_RD_XZ=y CONFIG_RD_LZO=y The amd64 image have support for gzip, bzip2, lzma and the xz variant. Ah, right, it's not explicitly set in the linux-2.6 configs, but automatically enabled by Kconfig. So, anything against using xz compression instead? (except that there might be quite a few scripts to update from initrd.gz to initrd.xz...) Samuel -- 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/20120205141148.gb4...@type.famille.thibault.fr
Bug#637392: Meet swingers in your metro looking to hook up.
Meet swingers in your metro looking to hook up. http://lessn.ca/2 - If you would like to not be contacted from us in the future please press on the link below: http://lessn.ca/3 or write to: P.O. Box 71, 46 St., Vancouver, Canada -- 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/20120205092734.6...@web004.nyc1.bluetie.com
Bug#657302: linux-image-3.2.0-1-amd64: No more sound
On Sun, 5 Feb 2012 08:01:39 -0600 Jonathan Nieder jrnie...@gmail.com wrote: Same bug on my system. Same codec, but not an Asus laptop so the patch mentioned here won't fix it. Please file a separate bug. Thanks, and sorry for the mis-filing. Unfortunately I'm not up on kernel packaging, so could you therefore advise where to file this? Note that some of my system's symptoms are similar to what's described by Flyingnu here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657302archived=Falsembox=no#45 Namely the 'pavucontrol' streams are toodling along, but there's no sound via headphones or speakers. So perhaps this bug, if it's only an Asus laptop thing, might be one instance of a greater problem. In which case if I open a separate bug, it might need to be merged with this one later. HTH... -- 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/20120205095041.60f547f309d256fdb265f...@gis.net
Bug#658727: linux-image-3.1.0-1-amd64: Status update (2.6.34-1 experimental.2) on #658670 3w-9xxx abnormally slows the system down
Package: linux-2.6 Version: 3.1.8-2 Severity: important Tags: d-i upstream Dear Jonathan, first of all thank You for the prompt reply. Jonathan NIEDER wrote: Csaba GAAL wrote: At first it seemed that I have found a bug in GNU Parted [...] “Unable to determine the size and length of /dev/sd[a-b][0-6]” [...] You are taking a long time to get to the point. ;-) I suppose after we deal with this speed regression, it will be useful to revisit that message and see if it can be eliminated. I couldn't agree more that it would be useful to check back on that message after this speed regression solved. Jonathan NIEDER wrote: If I understand correctly, you are reporting a speed regression between 2.6.32.y and 3.1.8-2. Thanks for finding it. Actually as far as I know the honour is Russell L. CARTER's I'm only the first to report it in Debian BTS (the reference to his e-mail sent on the mailing list is not correct, it misses a letter s (correctly lists. and not list.). Jonathan NIEDER wrote: Could you try versions 2.6.34-1~experimental.2 and 2.6.35~rc4-1~experimental.1 from http://snapshot.debian.org/, to hopefully narrow down the regression range? This report is to confirm that linux-image-2.6.34-1-amd64_2.6.34-1~experimental.2_amd64 is free from this error. This speed regression is included in linux-headers-3.2.0-1-amd64_3.2.2-1_amd64 (from this I will not send a separate report because of the long time it would take to boot the system with that Linux kernel). Just a preview of what's coming: still linux-image-2.6.39-2-amd64_2.6.39-3_amd64 is free from this speed regression problem, however for the record I am going to file separate reports for: 1) linux-image-2.6.35-rc5-amd64_2.6.35~rc5-1~experimental.1_amd64 2) linux-image-2.6.36-rc5-amd64_2.6.36~rc5-1~experimental.1_amd64 3) linux-image-2.6.37-2-amd64_2.6.37-2_amd64 4) linux-image-2.6.38-2-amd64_2.6.38-5_amd64 5) linux-image-2.6.39-2-amd64_2.6.39-3_amd64 By the way for whatever reason reportbug can not connect to Debian BTS: “Unable to connect to Debian BTS; continue [y|N|?]?” (however lynx can connect to various websites). Yours truly, Csaba GAAL -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTek Computer INC. product_name: M2N-LR product_version: Rev 1.xx chassis_vendor: ASUSTek Computer INC. chassis_version: Rev 1.xx bios_vendor: American Megatrends Inc. bios_version: 0515 board_vendor: ASUSTeK Computer INC. board_name: M2N-LR board_version: Rev 1.xx ** PCI devices: 00:00.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller [10de:0369] (rev a2) Subsystem: ASUSTeK Computer Inc. Device [1043:8239] 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 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge [10de:0360] (rev a3) Subsystem: ASUSTeK Computer Inc. Device [1043:8239] 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 Region 0: I/O ports at 2f00 [size=128] 00:01.1 SMBus [0c05]: nVidia Corporation MCP55 SMBus [10de:0368] (rev a3) Subsystem: ASUSTeK Computer Inc. Device [1043:8239] 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- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at 2900 [size=64] Region 4: I/O ports at 2a00 [size=64] Region 5: I/O ports at 2a80 [size=64] Capabilities: access denied Kernel driver in use: nForce2_smbus 00:02.0 USB controller [0c03]: nVidia Corporation MCP55 USB Controller [10de:036c] (rev a1) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8239] 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 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 22 Region 0: Memory at efbbf000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd 00:02.1 USB controller [0c03]: nVidia Corporation MCP55 USB Controller [10de:036d] (rev a2) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8239] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+
Processed (with 1 errors): Re: linux-image-3.2.0-1-amd64: No more sound
Processing commands for cont...@bugs.debian.org: clone 657302 -1 Bug#657302: linux-image-3.2.0-1-amd64: No more sound Bug 657302 cloned as bug 658728. submitter -1 A. Costa agco...@gis.net A. Costa agco...@gis.net is not a valid e-mail address; not changing submitter retitle -1 hda: patch_realtek: silent output on HP Compaq dx2200 MT Bug #658728 [linux-2.6] linux-image-3.2.0-1-amd64: No more sound Changed Bug title to 'hda: patch_realtek: silent output on HP Compaq dx2200 MT' from 'linux-image-3.2.0-1-amd64: No more sound' End of message, stopping processing here. Please contact me if you need assistance. -- 658728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658728 657302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657302 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 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.132845426210018.transcr...@bugs.debian.org
Bug#658670: 3w-9xxx abnormally slows the system down
merge 658670 658727 quit Csaba GAAL wrote: [To: sub...@bugs.debian.org] For the future, you can followup by sending email to 658...@bugs.debian.org (for example using your mailer's reply to all feature), or, if you don't have a working email setup, by using reportbug -N 658670. Submitting a separate new bug with each message just makes for more work on this end... [...] Just a preview of what's coming: still linux-image-2.6.39-2-amd64_2.6.39-3_amd64 is free from this speed regression problem, however for the record I am going to file separate reports for: 1) linux-image-2.6.35-rc5-amd64_2.6.35~rc5-1~experimental.1_amd64 2) linux-image-2.6.36-rc5-amd64_2.6.36~rc5-1~experimental.1_amd64 3) linux-image-2.6.37-2-amd64_2.6.37-2_amd64 4) linux-image-2.6.38-2-amd64_2.6.38-5_amd64 5) linux-image-2.6.39-2-amd64_2.6.39-3_amd64 No thank you. So, which is the first version with the speed degredation? Thanks for the quick followup. Sincerely, 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/20120205151156.GB32584@burratino
Processed: Re: linux-image-3.2.0-1-amd64: No more sound
Processing commands for cont...@bugs.debian.org: submitter 658728 A. Costa agco...@gis.net Bug #658728 [linux-2.6] hda: patch_realtek: silent output on HP Compaq dx2200 MT Changed Bug submitter to 'A. Costa agco...@gis.net' from 'Yann SOUBEYRAND yann.soubeyr...@gmx.fr' End of message, stopping processing here. Please contact me if you need assistance. -- 658728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658728 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.132845477411680.transcr...@bugs.debian.org
Processed: Re: 3w-9xxx abnormally slows the system down
Processing commands for cont...@bugs.debian.org: merge 658670 658727 Bug#658670: linux-image-3.1.0-1-amd64: 3w-9xxx abnormally slows the system down Bug#658727: linux-image-3.1.0-1-amd64: Status update (2.6.34-1 experimental.2) on #658670 3w-9xxx abnormally slows the system down Merged 658670 658727. quit Stopping processing here. Please contact me if you need assistance. -- 658727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658727 658670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658670 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.132845472711452.transcr...@bugs.debian.org
Bug#658728: linux-image-3.2.0-1-amd64: No more sound
A. Costa wrote: Thanks, and sorry for the mis-filing. Unfortunately I'm not up on kernel packaging, so could you therefore advise where to file this? The usual way would be reportbug linux-image-$(uname -r). No need for that this time --- I've cloned the bug as bug#658728, so please direct followups there. [...] So perhaps this bug, if it's only an Asus laptop thing, might be one instance of a greater problem. Sorry for the lack of clarity. These symptoms are indeed expected to affect many laptops with an ALC861 codec, not just Asus laptops. The problem is that different machines use a different mechanism to turn on or off sound completely. The driver has a table that documents this sort of thing for (1) all ASUS laptops (after the fix to bug#657302), (2) Haier W18, (3) FSC Amilo Pi1505. So, the next step is to work with upstream to get the pin routing information for your laptop. I'll send some hints on this in a separate message. 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/20120205152156.GD32584@burratino
Processed: Re: linux-image-3.2.0-1-amd64: No more sound
Processing commands for cont...@bugs.debian.org: tags 658728 = Bug #658728 [linux-2.6] hda: patch_realtek: silent output on HP Compaq dx2200 MT Removed tag(s) upstream, fixed-upstream, and patch. End of message, stopping processing here. Please contact me if you need assistance. -- 658728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658728 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.132845566717755.transcr...@bugs.debian.org
Processed: Re: linux-image-3.2.0-1-amd64: No more sound
Processing commands for cont...@bugs.debian.org: notforwarded 658728 Bug #658728 [linux-2.6] hda: patch_realtek: silent output on HP Compaq dx2200 MT Unset Bug forwarded-to-address End of message, stopping processing here. Please contact me if you need assistance. -- 658728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658728 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.132845569517904.transcr...@bugs.debian.org
Bug#658728: silent output on HP Compaq dx2200 MT
A. Costa wrote: Same bug on my system. [...] Manufacturer: Hewlett-Packard Product Name: HP Compaq dx2200 MT [...] Codec: Realtek ALC861 Address: 3 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x10ec0861 Subsystem Id: 0x14627254 Ok, thanks again for this. Please contact alsa-de...@alsa-project.org, cc-ing Takashi Iwai ti...@suse.de and either me or this bug log so we can track it. Be sure to include: - steps to reproduce - symptoms - what versions you've tried, and in particular what the newest working and oldest nonworking versions you've tried are - links to alsa-info output and other logs - a pointer to this bug log for the full story If you have time for it, please also follow the instructions from https://bugzilla.kernel.org/show_bug.cgi?id=42588#c18 to get some pin routing information (instructions for building a patched kernel on Debian are at [1]). Thanks much, and good luck, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package or the corresponding page in the debian-kernel-handbook 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/20120205153431.GA390@burratino
Bug#658670: 3w-9xxx abnormally slows the system down
Dear Jonathan, first of all thank You for the prompt reply, the merging, the proper command to directly report on this bug and sorry for the inconvenience. However the #612712 kicked in (UnicodeEncodeError: 'ascii' codec can't encode character u'\u201c' in position 734: ordinal not in range(128)) therefore I'm going to use the webmail interface. I feel that the most important is finding where the regression is introduced so fast forward to linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and the only thing I can tell is that it is still free from this problem. I keep You updated. Yours truly, Csaba GAÁL 2012/2/5 Jonathan Nieder jrnie...@gmail.com merge 658670 658727 quit Csaba GAAL wrote: [To: sub...@bugs.debian.org] For the future, you can followup by sending email to 658...@bugs.debian.org (for example using your mailer's reply to all feature), or, if you don't have a working email setup, by using reportbug -N 658670. Submitting a separate new bug with each message just makes for more work on this end... [...] Just a preview of what's coming: still linux-image-2.6.39-2-amd64_2.6.39-3_amd64 is free from this speed regression problem, however for the record I am going to file separate reports for: 1) linux-image-2.6.35-rc5-amd64_2.6.35~rc5-1~experimental.1_amd64 2) linux-image-2.6.36-rc5-amd64_2.6.36~rc5-1~experimental.1_amd64 3) linux-image-2.6.37-2-amd64_2.6.37-2_amd64 4) linux-image-2.6.38-2-amd64_2.6.38-5_amd64 5) linux-image-2.6.39-2-amd64_2.6.39-3_amd64 No thank you. So, which is the first version with the speed degredation? Thanks for the quick followup. Sincerely, 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/cag4jq7gbstfskd2d-k3i8uzxhd6enmcg-ajrz1wbqypvaum...@mail.gmail.com
Bug#658670: 3w-9xxx abnormally slows the system down
Csaba GAÁL wrote: I feel that the most important is finding where the regression is introduced so fast forward to linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and the only thing I can tell is that it is still free from this problem. Thanks. Pro tip: if you do a bisection search (i.e., try the version halfway between the newest known ok version and oldest known broken version at each step) then it will require fewer tests than just running through the list. -- 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/20120205155327.GA962@burratino
Bug#658670: 3w-9xxx abnormally slows the system down
Dear Jonathan, the speed regression was introduced between linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and linux-image-3.1.0-rc4-amd64_3.1.0~rc4-1~experimental.1_amd64. Hope that this information helps. Thank You once again for the prompt replies and the guidance. Yours truly, Csaba GAÁL 2012/2/5 Jonathan Nieder jrnie...@gmail.com: Csaba GAÁL wrote: I feel that the most important is finding where the regression is introduced so fast forward to linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and the only thing I can tell is that it is still free from this problem. Thanks. Pro tip: if you do a bisection search (i.e., try the version halfway between the newest known ok version and oldest known broken version at each step) then it will require fewer tests than just running through the list. -- 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/cag4jq7evjazbe-7qqaetjbcw3fekq7by_bkbwdyvwue6p+e...@mail.gmail.com
Bug#658670: 3w-9xxx abnormally slows the system down
Greetings, Thank you for cc'ing me. On 02/05/2012 09:05 AM, Csaba GAÁL wrote: Dear Jonathan, the speed regression was introduced between linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and linux-image-3.1.0-rc4-amd64_3.1.0~rc4-1~experimental.1_amd64. Hope that this information helps. I can confirm these and 3.2~rc7-1~experimental.1 as well. I never saw it in any 2.6.xx series kernel. Best, Russell (I'm new to the debian process and would like to get better at working within it so if you see an obvious way I can improve please let me know) Thank You once again for the prompt replies and the guidance. Yours truly, Csaba GAÁL 2012/2/5 Jonathan Nieder jrnie...@gmail.com: Csaba GAÁL wrote: I feel that the most important is finding where the regression is introduced so fast forward to linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and the only thing I can tell is that it is still free from this problem. Thanks. Pro tip: if you do a bisection search (i.e., try the version halfway between the newest known ok version and oldest known broken version at each step) then it will require fewer tests than just running through the list. -- 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/4f2eaa3c.8080...@pinyon.org
Processed: Re: 3w-9xxx abnormally slows the system down
Processing commands for cont...@bugs.debian.org: found 658670 linux-2.6/3.1.0~rc4-1~experimental.1 Bug #658670 [linux-2.6] linux-image-3.1.0-1-amd64: 3w-9xxx abnormally slows the system down Bug #658727 [linux-2.6] linux-image-3.1.0-1-amd64: Status update (2.6.34-1 experimental.2) on #658670 3w-9xxx abnormally slows the system down Bug Marked as found in versions linux-2.6/3.1.0~rc4-1~experimental.1. Bug Marked as found in versions linux-2.6/3.1.0~rc4-1~experimental.1. found 658670 linux-2.6/3.2~rc7-1~experimental.1 Bug #658670 [linux-2.6] linux-image-3.1.0-1-amd64: 3w-9xxx abnormally slows the system down Bug #658727 [linux-2.6] linux-image-3.1.0-1-amd64: Status update (2.6.34-1 experimental.2) on #658670 3w-9xxx abnormally slows the system down Bug Marked as found in versions linux-2.6/3.2~rc7-1~experimental.1. Bug Marked as found in versions linux-2.6/3.2~rc7-1~experimental.1. retitle 658670 [3.0 - 3.1 regression] 3w-9xxx abnormally slows the system down Bug #658670 [linux-2.6] linux-image-3.1.0-1-amd64: 3w-9xxx abnormally slows the system down Bug #658727 [linux-2.6] linux-image-3.1.0-1-amd64: Status update (2.6.34-1 experimental.2) on #658670 3w-9xxx abnormally slows the system down Changed Bug title to '[3.0 - 3.1 regression] 3w-9xxx abnormally slows the system down' from 'linux-image-3.1.0-1-amd64: 3w-9xxx abnormally slows the system down' Changed Bug title to '[3.0 - 3.1 regression] 3w-9xxx abnormally slows the system down' from 'linux-image-3.1.0-1-amd64: Status update (2.6.34-1 experimental.2) on #658670 3w-9xxx abnormally slows the system down' End of message, stopping processing here. Please contact me if you need assistance. -- 658670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658670 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.13284594015755.transcr...@bugs.debian.org
Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
On Sun, Feb 05, 2012 at 02:44:53AM -0600, Jonathan Nieder wrote: Hi Peter, Peter Colberg wrote: Package: linux-2.6 Version: 3.2.2-1 Severity: important Tags: upstream Which upstream version did you test? Sorry, I must have misinterpreted the upstream tag. I tested the Debian package only, i.e. linux-image-3.2.0-1-amd64=3.2.2-1. Peter -- 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/20120205163503.GA9675@alcyone
Bug#658670: 3w-9xxx abnormally slows the system down
Russell L. Carter wrote: On 02/05/2012 09:05 AM, Csaba GAÁL wrote: the speed regression was introduced between linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and linux-image-3.1.0-rc4-amd64_3.1.0~rc4-1~experimental.1_amd64. Hope that this information helps. I can confirm these and 3.2~rc7-1~experimental.1 as well. Thanks, both. I'll try to get back to you later today with information on the next step. (Feel free to ping me if I don't.) -- 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/20120205163439.GB2731@burratino
Processed: Re: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Processing commands for cont...@bugs.debian.org: tags 658662 - upstream Bug #658662 [linux-2.6] drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 Removed tag(s) upstream. End of message, stopping processing here. Please contact me if you need assistance. -- 658662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658662 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.13284598668607.transcr...@bugs.debian.org
Bug#658670: 3w-9xxx abnormally slows the system down
Dear Sirs, thank You for the prompt response. Actually and not so surprisingly I can confirm that the speed regression is also included in linux-image-3.2.0-1-amd64_3.2.2-1_amd64. I can also confirm that this is not an XFS related bug as on my notebook using linux-image-3.1.0-1-amd64 with exclusively XFS there is no such speed regression problem. Yours truly, Csaba GAÁL 2012/2/5 Jonathan Nieder jrnie...@gmail.com: Russell L. Carter wrote: On 02/05/2012 09:05 AM, Csaba GAÁL wrote: the speed regression was introduced between linux-image-3.0.0-2-amd64_3.0.0-6_amd64 and linux-image-3.1.0-rc4-amd64_3.1.0~rc4-1~experimental.1_amd64. Hope that this information helps. I can confirm these and 3.2~rc7-1~experimental.1 as well. Thanks, both. I'll try to get back to you later today with information on the next step. (Feel free to ping me if I don't.) -- 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/cag4jq7e1o9kikc3mily64ek0wf28nitf2fdfr7dhyznu7m5...@mail.gmail.com
Bug#658736: linux-2.6: [INTL:nl] Dutch translation of debconf templates
Package: linux-2.6
Severity: wishlist
Tags: patch l10n
Hello,
Attached is the updated Dutch translation of the linux-2.6 debconf templates.
Please include it in your next upload.
Regards,
--
Willem Kuyn
# Dutch translation of linux-2.6 po-debconf templates.
# Copyright (C) 2011 THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the linux-2.6 package.
# Willem Kuyn willemk...@gmail.com, 2011.
#
msgid
msgstr
Project-Id-Version: linux-2.6\n
Report-Msgid-Bugs-To: linux-...@packages.debian.org\n
POT-Creation-Date: 2011-07-04 04:24+0100\n
PO-Revision-Date: 2012-02-04 12:27+0100\n
Last-Translator: willem kuyn willemk...@gmail.com\n
Language-Team: Debian-Dutch debian-l10n-du...@lists.debian.org\n
Language: \n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid Abort installation after depmod error?
msgstr Installatie afbreken na depmod fout?
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid The 'depmod' command exited with the exit code ${exit_value} (${SIGNAL}${CORE}).
msgstr De 'depmod' opdracht stopte met foutcode ${exit_value} (${SIGNAL}${CORE}).
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid Since this image uses initrd, the ${modules_base}/=V/modules.dep file will not be deleted, even though it may be invalid.
msgstr Omdat deze afbeelding initrd gebruikt, zal het ${modules_base}/=V/modules.dep bestand niet verwijderd worden, ook al is het niet correct.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid You should abort the installation and fix the errors in depmod, or regenerate the initrd image with a known good modules.dep file. If you don't abort the installation, there is a danger that the system will fail to boot.
msgstr U zou de installatie moeten afbreken en de fouten in depmod herstellen, of het initrd-bestand opnieuw moeten genereren met een correct modules.dep bestand. Als u de installatie niet afbreekt dan bestaat het gevaar dat het systeem niet zal starten.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid Abort kernel removal?
msgstr Het verwijderen van de kernel afbreken?
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid You are running a kernel (version ${running}) and attempting to remove the same version.
msgstr U gebruikt kernel (versie ${running}) en probeert dezelfde versie te verwijderen.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid This can make the system unbootable as it will remove /boot/vmlinuz-${running} and all modules under the directory /lib/modules/${running}. This can only be fixed with a copy of the kernel image and the corresponding modules.
msgstr Het resultaat kan zijn dat het systeem niet start omdat het /boot/vmlinuz-${running} en alle modules onder /lib/modules/${running} verwijdert. Dit kan alleen gerepareerd worden met een kopie van het kernel bestand en de bijbehorende modules.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid It is highly recommended to abort the kernel removal unless you are prepared to fix the system after removal.
msgstr Het wordt ten sterkste aanbevolen om het verwijderen van de kernel af te breken tenzij u bent voorbereid om het systeem te repareren na het verwijderen.
#. Type: note
#. Description
#: ../templates/temp.image.plain/templates:4001
msgid Required firmware files may be missing
msgstr De vereiste firmware-bestanden kunnen ontbreken
#. Type: note
#. Description
#: ../templates/temp.image.plain/templates:4001
msgid This system is currently running Linux ${runningversion} and you are installing Linux ${version}. In the new version some of the drivers used on this system may require additional firmware files:
msgstr Het systeem draait op dit moment Linux ${runningversion} en u installeert Linux ${version}. In de nieuwe versie kunnen enkele stuurprogramma's van het systeem aparte firmware-bestanden nodig hebben.
#. Type: note
#. Description
#: ../templates/temp.image.plain/templates:4001
msgid Most firmware files are not included in the system because they do not conform to the Debian Free Software Guidelines. You may need to reconfigure the package manager to include the contrib and non-free sections of the package archive before you can install these firmware files.
msgstr Veel firmware-bestanden zijn niet in het systeem opgenomen omdat zij niet voldoen aan de Debian Richtlijnen voor Vrije Software (DFSG). Mogelijk moet u de configuratie van de pakketbeheerprogramma aanpassen en de contrib en non-free secties van het pakketarchief toevoegen voordat u deze firmware bestanden kunt installeren.
#. Type: error
#. Description
#: ../templates/temp.image.plain/templates:5001
#| msgid Boot loader
Bug#639161: Upgrade 2.6.39 - 3.0.0 breaks playback on DiBcom 7000PC
Eric Valette wrote: On 01/02/2012 01:57, Jonathan Nieder wrote: Version: 3.1.1-1 Patch was applied in 3.2-rc1, 3.1.1, and 3.0.9, so closing. But confirmation either way about whether it's fixed would be welcome. Confirmed fixed. Nice to hear. :) Thanks for checking. -- 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/20120205171731.GA3106@burratino
Processed: Re: 3w-9xxx abnormally slows the system down
Processing commands for cont...@bugs.debian.org: found 658670 linux-2.6/3.2.2-1 Bug #658670 [linux-2.6] [3.0 - 3.1 regression] 3w-9xxx abnormally slows the system down Bug #658727 [linux-2.6] [3.0 - 3.1 regression] 3w-9xxx abnormally slows the system down Bug Marked as found in versions linux-2.6/3.2.2-1. Bug Marked as found in versions linux-2.6/3.2.2-1. End of message, stopping processing here. Please contact me if you need assistance. -- 658670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658670 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.132846232022308.transcr...@bugs.debian.org
Bug#656331: RTL8168b/8111b with ASUS M2A-VM (SB600): Network device stays down after resume
Paul Menzel pm.deb...@googlemail.com : [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656331] I experienced this problem (only) three times until now. If I remember correctly the last time with 3.2.1. I still do not know how to reproduce this. (good PR, nice) An 'ethtool -d' and a 'mii-tool -v' of the device after a successful resume and a failed one could help if it's a driver thing. You may check if runtime power management is enabled or not, especially after a failed resume. See the /sys/devices/pci:../:..:/power directory and its control, runtime_enabled and runtime_status files (control = on - runtime PM disabled, see Documentation/power/runtime_pm.txt) If it is enabled and the link does not come up fast enough (5 s), runtime PM will suspend the device. It should not matter as long as the link is still present because the device should (TM) soon generate a power management event. The latter not happening or the PME being ignored could explain the bug. If so, temporarily disabling runtime PM for your device after a failed resume instead of removing the module or the cable may be enough to recover the link. It's just a guess though. Please stay with v3.2 or above in the meantime. -- Ueimor -- 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/20120205175730.ga23...@electric-eye.fr.zoreil.com
Processing of linux-2.6_3.2.4-1_amd64.changes
linux-2.6_3.2.4-1_amd64.changes uploaded successfully to localhost along with the files: linux-2.6_3.2.4-1.dsc linux-2.6_3.2.4.orig.tar.gz linux-2.6_3.2.4-1.diff.gz linux-support-3.2.0-1_3.2.4-1_all.deb linux-patch-debian-3.2_3.2.4-1_all.deb linux-source-3.2_3.2.4-1_all.deb linux-doc-3.2_3.2.4-1_all.deb linux-manual-3.2_3.2.4-1_all.deb linux-headers-3.2.0-1-amd64_3.2.4-1_amd64.deb linux-image-3.2.0-1-amd64-dbg_3.2.4-1_amd64.deb linux-image-3.2.0-1-amd64_3.2.4-1_amd64.deb xen-linux-system-3.2.0-1-amd64_3.2.4-1_amd64.deb linux-headers-3.2.0-1-common_3.2.4-1_amd64.deb linux-headers-3.2.0-1-all_3.2.4-1_amd64.deb linux-headers-3.2.0-1-all-amd64_3.2.4-1_amd64.deb linux-libc-dev_3.2.4-1_amd64.deb linux-headers-3.2.0-1-rt-amd64_3.2.4-1_amd64.deb linux-image-3.2.0-1-rt-amd64-dbg_3.2.4-1_amd64.deb linux-image-3.2.0-1-rt-amd64_3.2.4-1_amd64.deb xen-linux-system-3.2.0-1-rt-amd64_3.2.4-1_amd64.deb linux-headers-3.2.0-1-common-rt_3.2.4-1_amd64.deb kernel-image-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb nic-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb nic-extra-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb nic-wireless-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb nic-shared-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb serial-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb usb-serial-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ppp-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ide-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb pata-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ide-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb cdrom-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb firewire-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb scsi-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb scsi-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb scsi-common-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb scsi-extra-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb plip-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb floppy-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb loop-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb btrfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ext2-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ext3-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ext4-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb isofs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb jfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ntfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb reiserfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb xfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb fat-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ufs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb qnx4-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb md-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb multipath-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb usb-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb usb-storage-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb pcmcia-storage-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb fb-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb input-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb event-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb mouse-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb irda-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb parport-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb nic-pcmcia-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb pcmcia-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb nic-usb-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb sata-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb acpi-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb i2c-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb crc-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb crypto-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb crypto-dm-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb efi-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ata-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb mmc-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb mmc-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb nbd-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb squashfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb speakup-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb virtio-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb uinput-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb sound-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb zlib-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb Greetings, Your Debian queue daemon (running on host franck.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/e1ru6ih-hc...@franck.debian.org
linux-2.6_3.2.4-1_amd64.changes ACCEPTED into unstable
Accepted: acpi-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/acpi-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ata-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/ata-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb btrfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/btrfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb cdrom-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/cdrom-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb crc-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/crc-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb crypto-dm-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/crypto-dm-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb crypto-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/crypto-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb efi-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/efi-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb event-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/event-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ext2-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/ext2-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ext3-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/ext3-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ext4-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/ext4-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb fat-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/fat-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb fb-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/fb-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb firewire-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/firewire-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb floppy-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/floppy-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb i2c-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/i2c-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ide-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/ide-core-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb ide-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/ide-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb input-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/input-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb irda-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/irda-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb isofs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/isofs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb jfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/jfs-modules-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb kernel-image-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb to main/l/linux-2.6/kernel-image-3.2.0-1-amd64-di_3.2.4-1_amd64.udeb linux-2.6_3.2.4-1.diff.gz to main/l/linux-2.6/linux-2.6_3.2.4-1.diff.gz linux-2.6_3.2.4-1.dsc to main/l/linux-2.6/linux-2.6_3.2.4-1.dsc linux-2.6_3.2.4.orig.tar.gz to main/l/linux-2.6/linux-2.6_3.2.4.orig.tar.gz linux-doc-3.2_3.2.4-1_all.deb to main/l/linux-2.6/linux-doc-3.2_3.2.4-1_all.deb linux-headers-3.2.0-1-all-amd64_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-headers-3.2.0-1-all-amd64_3.2.4-1_amd64.deb linux-headers-3.2.0-1-all_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-headers-3.2.0-1-all_3.2.4-1_amd64.deb linux-headers-3.2.0-1-amd64_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-headers-3.2.0-1-amd64_3.2.4-1_amd64.deb linux-headers-3.2.0-1-common-rt_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-headers-3.2.0-1-common-rt_3.2.4-1_amd64.deb linux-headers-3.2.0-1-common_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-headers-3.2.0-1-common_3.2.4-1_amd64.deb linux-headers-3.2.0-1-rt-amd64_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-headers-3.2.0-1-rt-amd64_3.2.4-1_amd64.deb linux-image-3.2.0-1-amd64-dbg_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-image-3.2.0-1-amd64-dbg_3.2.4-1_amd64.deb linux-image-3.2.0-1-amd64_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-image-3.2.0-1-amd64_3.2.4-1_amd64.deb linux-image-3.2.0-1-rt-amd64-dbg_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-image-3.2.0-1-rt-amd64-dbg_3.2.4-1_amd64.deb linux-image-3.2.0-1-rt-amd64_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-image-3.2.0-1-rt-amd64_3.2.4-1_amd64.deb linux-libc-dev_3.2.4-1_amd64.deb to main/l/linux-2.6/linux-libc-dev_3.2.4-1_amd64.deb linux-manual-3.2_3.2.4-1_all.deb to main/l/linux-2.6/linux-manual-3.2_3.2.4-1_all.deb linux-patch-debian-3.2_3.2.4-1_all.deb to main/l/linux-2.6/linux-patch-debian-3.2_3.2.4-1_all.deb linux-source-3.2_3.2.4-1_all.deb to main/l/linux-2.6/linux-source-3.2_3.2.4-1_all.deb linux-support-3.2.0-1_3.2.4-1_all.deb to main/l/linux-2.6/linux-support-3.2.0-1_3.2.4-1_all.deb
Bug#658759: linux-image-3.2.0-1-kirkwood does not boot on some Kirkwood machines
Package: linux-image-3.2.0-1-kirkwood Version: 3.2.2-1 Problem: This kernel package, when installed on many Kirkwood machines, including the Dockstar, does not boot. Various users have noticed this, and it seems likely that it could be related to compression of the kernel image into the uImage file. Notably, an uncompressed vmlinux.bin (from the same build/source) relabeled as uImage will boot correctly. Unfortunately, the default for this package is a compressed image. http://packages.debian.org/unstable/kernel/linux-image-3.2.0-1-kirkwood Steps to reproduce, with output shown: On my Dockstar: == cd / wget http://ftp.us.debian.org/debian/pool/main/l/linux-2.6/linux-image-3.2.0-1-kirkwood_3.2.2-1_armel.deb dpkg -i linux-image-3.2.0-1-kirkwood_3.2.2-1_armel.deb mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n Linux-3.2.0-1-kirkwood -d /boot/vmlinuz-3.2.0-1-kirkwood /boot/uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x -e 0x -n initramfs-3.2.0-1-kirkwood -d /boot/initrd.img-3.2.0-1-kirkwood /boot/uInitrd == From serial connection: == U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvell-Dockstar/Pogoplug by Jeff Doozan SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB NAND: 256 MiB In:serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found Loading file /rescueme from usb device 0:1 (usbda1) ** File not found /rescueme reading /rescueme.txt ** Unable to read /rescueme.txt from usb 0:1 ** Creating 1 MTD partitions on nand0: 0x0250-0x1000 : mtd=3 UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size:129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: attached mtd1 to ubi0 UBI: MTD device name: mtd=3 UBI: MTD device size:219 MiB UBI: number of good PEBs: 1752 UBI: number of bad PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 0 UBI: available PEBs: 1731 UBI: total number of reserved PEBs: 21 UBI: number of PEBs reserved for bad PEB handling: 17 UBI: max/mean erase counter: 1/1 UBIFS error (pid 0): ubifs_get_sb: cannot open ubi:rootfs, error -19 Error reading superblock on volume 'ubi:rootfs'! Loading file /boot/uImage from usb device 0:1 (usbda1) 1 bytes read Found bootable drive on usb 0:1 Loading file /boot/uImage from usb device 0:1 (usbda1) 1570456 bytes read Loading file /boot/uInitrd from usb device 0:1 (usbda1) 6621782 bytes read ## Booting kernel from Legacy Image at 0080 ... Image Name: Linux-3.2.0-1-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1570392 Bytes = 1.5 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 0110 ... Image Name: initramfs-3.2.0-1-kirkwood Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:6621718 Bytes = 6.3 MiB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. = No further output is seen. I am using Debian GNU/Linux 6/Wheezy. The same behavior shows up with Squeeze.
Bug#658764: linux-image-3.1.0-1-amd64: free ATI driver corrupts output on Radeon HD 6310
Package: linux-2.6 Version: 3.1.8-2 Severity: important Dear Maintainer, This machine is a Zotac ZBOX AD10, with AMD E-350 processor and AMD M1 chipset. I installed Debian Squeeze 6.0.4, and the free ATI driver worked fine to get full resolution graphics on the display. Upgrading from Squeeze to Wheezy brings in the Linux 3.1.0 kernel. Now the free ATI driver corrups display output: a mess of snow covers approximately the top half of the screen, and the bottom part is black. Installing the ‘firmware-linux-nonfree’ package fixes display again to the point where graphics are visible in the correct resolution. I have uninstalled that package, and the display corruption returns. This is a regression: display with the free ATI driver should be at least as good as was in the 2.6 kernel from Squeeze. Please feel free to re-assign this if I have reported to the wrong package. -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/anemone-root ro quiet ** Not tainted ** Kernel log: [7.225595] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [7.225599] [drm] Encoders: [7.225601] [drm] DFP1: INTERNAL_UNIPHY [7.225604] [drm] Connector 1: [7.225607] [drm] HDMI-A [7.225609] [drm] HPD2 [7.225613] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c [7.225616] [drm] Encoders: [7.225618] [drm] DFP2: INTERNAL_UNIPHY [7.225621] [drm] Connector 2: [7.225623] [drm] VGA [7.225627] [drm] DDC: 0x64d8 0x64d8 0x64dc 0x64dc 0x64e0 0x64e0 0x64e4 0x64e4 [7.225630] [drm] Encoders: [7.225632] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [7.622130] ath9k :03:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [7.622150] ath9k :03:00.0: setting latency timer to 64 [7.675216] ath: EEPROM regdomain: 0x60 [7.675223] ath: EEPROM indicates we should expect a direct regpair map [7.675231] ath: Country alpha2 being used: 00 [7.675234] ath: Regpair used: 0x60 [7.704046] [drm] Radeon display connector DP-1: No monitor connected or invalid EDID [7.809976] [drm] Radeon display connector HDMI-A-1: Found valid EDID [8.288037] [drm] Radeon display connector VGA-1: No monitor connected or invalid EDID [8.288079] [drm] Internal thermal controller without fan control [8.288193] [drm] radeon: power management initialized [8.512790] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [8.513779] Registered led device: ath9k-phy0 [8.513797] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xc900110e, irq=16 [8.522648] [drm] fb mappable at 0xB004 [8.522654] [drm] vram apper at 0xB000 [8.522657] [drm] size 5787648 [8.522660] [drm] fb depth is 24 [8.522663] [drm]pitch is 6400 [8.528205] fbcon: radeondrmfb (fb0) is primary device [8.577156] Console: switching to colour frame buffer device 200x56 [8.585357] fb0: radeondrmfb frame buffer device [8.585361] drm: registered panic notifier [8.585375] [drm] Initialized radeon 2.11.0 20080528 for :00:01.0 on minor 0 [8.954991] input: USB OPTICAL MOUSE as /devices/pci:00/:00:12.0/usb4/4-2/4-2.1/4-2.1:1.0/input/input5 [8.955791] generic-usb 0003:15D9:0A4C.0001: input,hidraw0: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-:00:12.0-2.1/input0 [8.960871] input: Mitsumi Electric Apple Extended USB Keyboard as /devices/pci:00/:00:12.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input6 [8.961456] generic-usb 0003:05AC:020B.0002: input,hidraw1: USB HID v1.10 Keyboard [Mitsumi Electric Apple Extended USB Keyboard] on usb-:00:12.0-2.3/input0 [8.970771] input: Mitsumi Electric Apple Extended USB Keyboard as /devices/pci:00/:00:12.0/usb4/4-2/4-2.3/4-2.3:1.1/input/input7 [8.971335] generic-usb 0003:05AC:020B.0003: input,hidraw2: USB HID v1.10 Device [Mitsumi Electric Apple Extended USB Keyboard] on usb-:00:12.0-2.3/input1 [8.971383] usbcore: registered new interface driver usbhid [8.971387] usbhid: USB HID core driver [9.043896] snd_hda_intel :00:01.1: PCI INT B - GSI 19 (level, low) - IRQ 19 [9.043990] snd_hda_intel :00:01.1: irq 44 for MSI/MSI-X [9.044059] snd_hda_intel :00:01.1: setting latency timer to 64 [9.096507] Bluetooth: Core ver 2.16 [9.096556] NET: Registered protocol family 31 [9.096560] Bluetooth: HCI device and connection manager initialized [9.096566] Bluetooth: HCI socket layer initialized [9.096570] Bluetooth: L2CAP socket layer initialized [9.096585] Bluetooth: SCO socket layer initialized [9.118785] Bluetooth: Atheros AR30xx firmware driver ver 1.0 [9.123909] Bluetooth: Error loading firmware [9.123984] ath3k: probe of 7-3:1.0 failed with error
Bug#658759: Also on Guruplug
I've seen what looks like the same issue on my Guruplug. linux-image-3.1.0-1-kirkwood (3.1.8-2) boots fine, linux-image-3.2.0-1-kirkwood (3.2.2-1) doesn't get anywhere. My U-boot banner looks like this: U-Boot 2011.03 (Apr 26 2011 - 21:35:00) Marvell-GuruPlug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB NAND: 512 MiB In:serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 And when I boot 3.2.0-1, this is what I see: Loading file /uImage.bak from ide device 0:1 (hda1) 1570456 bytes read Loading file /uInitrd.bak from ide device 0:1 (hda1) 8211832 bytes read Marvell bootm 0x0080 0x0110 ## Booting kernel from Legacy Image at 0080 ... Image Name: Debian kernel Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1570392 Bytes = 1.5 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 0110 ... Image Name: Debian ramdisk Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:8211768 Bytes = 7.8 MiB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. After this, no more messages are visible on the serial console, and there is no other indication that the boot progresses. Thanks donald -- 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/CAK+uisC1qsj-BjrrUCWFtTgd=-Z51gN6LaQU1T=cnnzsi30...@mail.gmail.com
Bug#658759: More information
Upgrading my u-boot to the version from here: http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html made my boot progress futher. Now the kernel starts. But the last message I see is that udev has started; after this, the boot process stalls again. donald -- 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/cak+uisa9dckcsoefkszupcung0qvxaoqy4ayph-zxltwl5i...@mail.gmail.com
Bug#658764: linux-image-3.1.0-1-amd64: free ATI driver corrupts output on Radeon HD 6310
On the same system, selecting Linux 2.6.32-5-amd64 (from the GRUB menu) results in uncorrupted display also. So the problem is restricted to Linux 3.1.0-1 on this system. -- \ “I watched the Indy 500, and I was thinking that if they left | `\ earlier they wouldn't have to go so fast.” —Steven Wright | _o__) | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
found 658662 3.2.4-1 thanks Since the changelog of Linux 3.2.3 contains drm/i915-related fixes, I tested the newest Debian kernel: No change, the external display remains dark. Peter -- 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/20120206021121.GA3606@alcyone
Processed: Re: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Processing commands for cont...@bugs.debian.org: found 658662 3.2.4-1 Bug #658662 [linux-2.6] drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 There is no source info for the package 'linux-2.6' at version '3.2.4-1' with architecture '' Unable to make a source version for version '3.2.4-1' Bug Marked as found in versions 3.2.4-1. thanks Stopping processing here. Please contact me if you need assistance. -- 658662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658662 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.13284942886281.transcr...@bugs.debian.org
Bug#658728: linux-image-3.2.0-1-amd64: No more sound
On Sun, 5 Feb 2012 09:21:56 -0600 Jonathan Nieder jrnie...@gmail.com wrote: Sorry for the lack of clarity. These symptoms are indeed expected to affect many laptops with an ALC861 codec, not just Asus laptops. The problem is that different machines use a different mechanism to turn on or off sound completely. The driver has a table that documents this sort of thing for (1) all ASUS laptops (after the fix to bug#657302), (2) Haier W18, (3) FSC Amilo Pi1505. So, the next step is to work with upstream to get the pin routing information for your laptop. I'll send some hints on this in a separate message. It might not matter, but my current system, correctly identified by 'alsa-info.sh' as an HP Compaq dx2200 MT, is a Desktop box, not a laptop. The sound card is part of the mobo, however, which is somewhat laptop-like. More here: Manuals (guides, supplements, addendums, etc) HP Compaq dx2200 Microtower PC http://h2.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManuallang=encc=usprodSeriesId=1844701prodTypeId=12454 To fetch pin routing data via 'hda-verb' requires recompiling the kernel. This week I haven't enough time to build a kernel. (Bandwidth=dialup.) Pity there isn't a simpler method; even using a multitester on the mobo would be less hassle than rebuilding the kernel. Searching the web for 'HP Compaq dx2200 MT hda-verb' finds some kernel module patch notes from 2007: [ALSA] hda-codec - Add quirks for HP dx2200/dx2250 HP dx2200 and dx2250 use Micro-Star International (MSI) motherboards (models MS-7254 and MS-7297 respectively) with an ALC862 codec in threestack configuration. Adding this quirk allows correct 5.1 sound output in these systems. Signed-off-by: Claudio Matsuoka cmatsu...@gmail.com Signed-off-by: Takashi Iwai ti...@suse.de Signed-off-by: Jaroslav Kysela pe...@suse.cz http://www.codebrowse.net/history/linux-3.0/sound/pci/hda/patch_realtek.c Sound on this box with my previous stock Debian kernels worked. Today I reverted to 'linux-image-3.1.0-1-686-pae', under which the sound still works fine. Attached are the outputs of 'alsa-info.sh' for the the downgraded (good sound 3.1.0-1) kernel, and the newer (no sound working 3.2.0-1) kernel. As advised I've CC:'d this email upstream, for whom the relevant Debian bug reports can be found here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657302archived=Falsembox=no http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658728archived=Falsembox=no HTH... HP DX2200 MT alsa data.tar.bz2 Description: Binary data
Bug#658294: marked as done ([linux-2.6] linux-image-3.2.0-1-amd64: No more sound)
Your message dated Sun, 5 Feb 2012 21:27:39 -0600 with message-id 20120206032739.GA5230@burratino and subject line Re: [3.1 - 3.2.2 regression] No more sound has caused the Debian Bug report #658294, regarding [linux-2.6] linux-image-3.2.0-1-amd64: No more sound 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.) -- 658294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.2-1 Severity: normal --- Please enter the report below this line. --- Hi, I have a Dell laptop (latitude E6420) and i get a similar bug as #657302: no more sound with kernel 3.2. No problem with 3.1. There is no errors except there is no sound. Thank you. Guy lspci -v ... 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Dell Device 0493 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at e676 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel ... aplay --list-devices Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: STAC92xx Analog [STAC92xx Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: NVidia [HDA NVidia], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: NVidia [HDA NVidia], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: NVidia [HDA NVidia], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 lsmod | grep snd snd_hrtimer12604 1 snd_hda_codec_hdmi 26548 1 snd_hda_codec_idt 53748 1 snd_hda_intel 26182 2 snd_hda_codec 72920 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel snd_hwdep 13186 1 snd_hda_codec snd_pcm_oss41081 0 snd_mixer_oss 17916 1 snd_pcm_oss snd_pcm63744 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi 12848 0 snd_rawmidi23060 1 snd_seq_midi snd_seq_midi_event 13316 1 snd_seq_midi snd_seq45093 3 snd_seq_midi,snd_seq_midi_event snd_timer 22917 3 snd_hrtimer,snd_pcm,snd_seq snd_seq_device 13176 3 snd_seq_midi,snd_rawmidi,snd_seq snd52798 17 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 13065 1 snd snd_page_alloc 13003 2 snd_hda_intel,snd_pcm --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-1-amd64 Debian Release: wheezy/sid 500 unstableqgis.org 500 unstableftp.fr.debian.org 500 stable dl.google.com 500 stable deb.opera.com 500 squeeze deb.playonlinux.com 500 oneiric ppa.launchpad.net 200 unstablewww.debian-multimedia.org 150 experimentalftp.fr.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. ---End Message--- ---BeginMessage--- Version: 3.2.4-1 Jonathan Nieder wrote: The patch is part of v3.3-rc2 and has been queued by Greg for inclusion in version 3.2.3. Hence closing, though information either way about whether the fix works would still be very welcome. ;-) Thanks for the quick feedback, Jonathan ---End Message---
Bug#658778: Suspend from X session hangs Asus laptop.
Hi Boris, Boris Barbour wrote: On a new, cheap Asus laptop (Model X54L), suspend to RAM does not work under some conditions. Thanks for reporting it. Is this a regression? Does suspend-to-disk (triggered with echo disk /sys/power/state ) work? If you have time to follow the instructions from basic-pm-debugging.txt[1] to narrow down the cause, that would be very useful. Hope that helps, Jonathan [1] http://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt also available from Documentation/power in the documentation dir of the linux-doc-3.2 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/20120206044935.GA3407@burratino
Bug#658764: free ATI driver corrupts output on Radeon HD 6310
Hi Ben, Ben Finney wrote: On the same system, selecting Linux 2.6.32-5-amd64 (from the GRUB menu) results in uncorrupted display also. So the problem is restricted to Linux 3.1.0-1 on this system. Does this happen with version 3.2.4-1 from sid, too? Can you bisect? Even a few tests of versions halfway between from http://snapshot.debian.org/ can help a lot in narrowing down the cause of this particular regression. See http://bugs.debian.org/607194 and the bugs merged with it for some background. Thanks and 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/20120206045831.GB3407@burratino
Processed: Re: [arm] compressed image does not boot
Processing commands for cont...@bugs.debian.org: # regression severity 658759 important Bug #658759 [linux-image-3.2.0-1-kirkwood] linux-image-3.2.0-1-kirkwood does not boot on some Kirkwood machines Severity set to 'important' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. -- 658759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658759 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.13285052271243.transcr...@bugs.debian.org
Bug#658759: [arm/kirkwood] compressed image does not boot
purdyd tds.net wrote: Problem: This kernel package, when installed on many Kirkwood machines, including the Dockstar, does not boot. Thanks. Am I correct in guessing that version 3.2~rc4-1~experimental.1 from http://snapshot.debian.org/ does not reproduce the problem, while 3.2~rc7-1~experimental.1 does? Curious, 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/20120206051859.GB5807@burratino
Bug#657526: linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x10000100
Thomas Hahn wrote: I have added the last one and the one captured just now. Thanks! Puzzling. Can you try 3.2.4-1 which was just uploaded to unstable? (It should be available from incoming.debian.org for now.) If it reproduces the same problem, then we should take this upstream. Sorry to have been so slow on tracking this one down. Ciao, 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/20120206060628.GA6167@burratino
Processed: Re: base: vmstat and /proc/loadavg disagree
Processing commands for cont...@bugs.debian.org: forwarded 620297 http://thread.gmane.org/gmane.linux.kernel/1249223 Bug #620297 [linux-2.6] base: vmstat and /proc/loadavg disagree Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel/1249223'. End of message, stopping processing here. Please contact me if you need assistance. -- 620297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620297 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.13285113806810.transcr...@bugs.debian.org
Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Hi, Peter Colberg wrote: To summarize: The external display connected via DisplayPort works fine with Linux 3.1, while, with Linux 3.2, it works with lower (non-native) resolutions and fails with the maximum (native) resolution. Please report this upstream, following instructions from [1], and let us know the bug number so we can track it. The upstream developers may ask you to bisect to find the specific patch that introduced the problem. It works like this: 0. Prerequisites: apt-get install git build-essential 1. Get a copy of the kernel source repository: git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux Or if you already have a copy, update it: cd linux git fetch origin 2. Test v3.2: git checkout v3.2 cp /boot/config-$(uname -r) .config; # current configuration make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jn for parallel build dpkg -i ../name of package reboot ... test test test ... If it doesn't exhibit the problem, declare victory and we can try to figure out what Debian-specific patch (unlikely) or configuration change (more likely) caused it. Otherwise: 3. Test v3.1: git checkout v3.1 make silentoldconfig; # reuse configuration make deb-pkg; # maybe with -j4 dpkg -i ../name of package reboot ... test test test ... Hopefully it does not exhibit the problem. 4. Test a version halfway between: git bisect start v3.2 v3.1; # checks out a version halfway between to test make silentoldconfig; # reuse configuration make deb-pkg; # maybe with -j4 dpkg -i ../name of package reboot ... test test test ... git bisect bad; # if it exhibits the problem git bisect good; # if the external display works fine, after a # power-cycle and with the right resolution git bisect skip; # if some other problem makes it hard to test 5. Another version to test will be automatically checked out. So: make silentoldconfig make deb-pkg; # maybe with -j4 dpkg -i ../name of package reboot ... test ... git bisect good/bad/skip 6. Rinse and repeat until bored. 7. After sufficiently many iterations, git will indicate the first bad commit --- hoorah! If bored before then, you can run git bisect log to print information about the versions tested in a form that will allow someone else to pick up where you left off. At any step if the gitk package is installed, you can run git bisect visualize to watch the regression range narrowing. Hope that helps, Jonathan [1] http://intellinuxgraphics.org/how_to_report_bug.html -- 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/20120206071544.GA7087@burratino
Bug#657526: /boot/vmlinuz-3.2.0-0.bpo.1-686-pae: seeing the same thing
Package: linux-2.6 Version: 3.2.1-2~bpo60+1 File: /boot/vmlinuz-3.2.0-0.bpo.1-686-pae Severity: normal I'll try to do some debugging work later, but just wanted to register that this bug happens with the backports version of this kernel too. This is with a Dell Latitude 2100 laptop. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** Network interface configuration: auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03) Subsystem: Dell Device [1028:02d6] 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 Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02d6] 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 Interrupt: pin A routed to IRQ 16 Region 0: Memory at f6f0 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at eff8 [size=8] Region 2: Memory at e000 (32-bit, prefetchable) [size=256M] Region 3: Memory at f6ec (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: Dell Device [1028:02d6] 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 Region 0: Memory at f6f8 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01) Subsystem: Dell Device [1028:02d6] 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: 64 bytes Interrupt: pin A routed to IRQ 45 Region 0: Memory at f6ebc000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01) (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: 64 bytes Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0 I/O behind bridge: 4000-4fff Memory behind bridge: 8040-805f Prefetchable memory behind bridge: 8060-807f 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:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 01) (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: 64 bytes Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0 I/O behind bridge: 3000-3fff Memory behind bridge: f6d0-f6df Prefetchable memory behind bridge: 8020-803f 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:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4
