Processed: severity of 627837 is wishlist
Processing commands for cont...@bugs.debian.org: severity 627837 wishlist Bug #627837 [linux-2.6] linux-2.6: Aufs apparently silently dropped, breaking debian-live Bug #627573 [linux-2.6] linux-image-2.6.39-1-686-pae: Please include aufs in linux-image-2.6.39 Severity set to 'wishlist' from 'important' Severity set to 'wishlist' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 627837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627837 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.130673854317481.transcr...@bugs.debian.org
Processed: tagging 627293
Processing commands for cont...@bugs.debian.org: tags 627293 + wheezy Bug #627293 [linux-2.6] linux-image-2.6.38-2-686: Kernel crash on wakeup from sleep mode Added tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 627293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627293 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.130674110524340.transcr...@bugs.debian.org
Bug#628558: Plaease enable
Package: linux-2.6 Version: 2.6.39-1 Severity: wishlist Hi, in this documentation file: /usr/share/doc/linux-doc-2.6.39/Documentation/filesystems/caching/fscache.txt.gz the kernel options CONFIG_FSCACHE_STATS=y CONFIG_FSCACHE_HISTOGRAM=y are suggested to check the efficiency of fscache. However only the first one is enabled: $ grep CONFIG_FSCACHE /boot/config-2.6.39-1-686-pae CONFIG_FSCACHE=m CONFIG_FSCACHE_STATS=y # CONFIG_FSCACHE_HISTOGRAM is not set # CONFIG_FSCACHE_DEBUG is not set # CONFIG_FSCACHE_OBJECT_LIST is not set So could you please enable CONFIG_FSCACHE_HISTOGRAM ? -- Laurent Bonnaud. http://www.gipsa-lab.inpg.fr/page_pro.php?vid=96 -- 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/1306742434.6645.6.camel@vougeot
Re: Bug#627837: linux-2.6: Aufs apparently silently dropped, breaking debian-live
Daniel Baumann daniel.baum...@progress-technologies.net writes: On 05/29/2011 10:34 PM, Julien Cristau wrote: The maintainers have already made that call, and I don't see a reason to override their decision. so no change after squeeze, the release team gives a shit about breaking debian-live, sigh. but don't worry, from now on, i will not care anymore either. I believe your address is wrong. This is neither about the release team, nor the kernel team. As for the kernel team, the message they sent you over a year ago should be pretty clear (and it wasn't the first one AFAIK): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573189#31 They way I read that message, it has: 1) a requirement that aufs2 is going to be updated to work with upstream kernel releases 2) no promise that the kernel team will do this work, or even aid it 3) no promise about this support continuing forever (more than a year might be considered more than a while by many) 4) absolutely no promise that a while will last until wheezy is released 5) a polite request that you do whatever you can to aid in development of union mounts Did you read something else? In the mean time, we've seen dicussions like this one: https://lkml.org/lkml/2011/3/23/72 where the fact that Debian includes aufs2 is abused as an argument against union mounts! Where were you in that discussion? Ben did what he could, but I wouldn't be suprised if most people just thought: Used by Debian == must be OK. For a reason. It usually works like that :-) But it is pretty clear that the outcome of that thread could have been quite another if you and Ben had presented the union mount ready debian-live and a plan for getting that into wheezy instead of aufs2. Please stop this nonsense now, and start working with the kernel team instead of against them. And that also means working with upstream kernel maintainers, who have been pretty clear wrt the future of aufs2: There is none. Bjørn -- 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/8762osr2pl@nemi.mork.no
Bug#628600: linux-image-2.6.39-1-amd64: Should depends/suggest on udev = 170-1
Package: linux-image-2.6.39-1-amd64 Severity: important Tags: sid The cdrom_id program from the udev package (version 167-3) refuse to freeze with a linux 2.6.39. That prevent the system to suspend. It works will with a 2.6.38 kernel, then the problem starts with the 2.6.39 kernel. The 170-1 version works well with the 2.6.39 kernel. Here are the linux messages: May 30 10:46:32 blackpage kernel: [ 1118.055313] Freezing user space processes May 30 10:46:32 blackpage kernel: [ 1138.019130] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0): May 30 10:46:32 blackpage kernel: [ 1138.019184] cdrom_idD 88012cc3c180 0 5521 5519 0x0084 May 30 10:46:32 blackpage kernel: [ 1138.019191] 88012cc3c180 0086 88012cc3c180 8801 May 30 10:46:32 blackpage kernel: [ 1138.019198] 8801312dd140 00012900 88012f441fd8 00012900 May 30 10:46:32 blackpage kernel: [ 1138.019204] 00012900 88012f441fd8 88012cc3c180 00012900 May 30 10:46:32 blackpage kernel: [ 1138.019211] Call Trace: May 30 10:46:32 blackpage kernel: [ 1138.019226] [8133d93d] ? schedule_timeout+0x2d/0xd7 May 30 10:46:32 blackpage kernel: [ 1138.019236] [8103e7f8] ? get_parent_ip+0x9/0x1b May 30 10:46:32 blackpage kernel: [ 1138.019239] [8133ce60] ? wait_for_common+0x97/0x10f May 30 10:46:32 blackpage kernel: [ 1138.019241] [81041be6] ? try_to_wake_up+0x1a5/0x1a5 May 30 10:46:32 blackpage kernel: [ 1138.019245] [8105b934] ? start_flush_work+0xe5/0xfc May 30 10:46:32 blackpage kernel: [ 1138.019247] [8105bc45] ? flush_work+0x24/0x2c May 30 10:46:32 blackpage kernel: [ 1138.019249] [8105b564] ? do_work_for_cpu+0x1b/0x1b May 30 10:46:32 blackpage kernel: [ 1138.019254] [8119ea0f] ? disk_clear_events+0x90/0xed May 30 10:46:32 blackpage kernel: [ 1138.019260] [81126dc0] ? check_disk_change+0x22/0x50 May 30 10:46:32 blackpage kernel: [ 1138.019264] [a04a3ff8] ? cdrom_open+0x45/0x4aa [cdrom] May 30 10:46:32 blackpage kernel: [ 1138.019266] [8119e077] ? get_disk+0xeb/0x10b May 30 10:46:32 blackpage kernel: [ 1138.019271] [8125122c] ? kobj_lookup+0x1cb/0x204 May 30 10:46:32 blackpage kernel: [ 1138.019273] [8103e7f8] ? get_parent_ip+0x9/0x1b May 30 10:46:32 blackpage kernel: [ 1138.019276] [a04b07c8] ? sr_block_open+0x93/0xbc [sr_mod] May 30 10:46:32 blackpage kernel: [ 1138.019278] [81127b6a] ? __blkdev_get+0xc4/0x361 May 30 10:46:32 blackpage kernel: [ 1138.019280] [81127fc3] ? blkdev_get+0x1bc/0x2a6 May 30 10:46:32 blackpage kernel: [ 1138.019282] [8103e7f8] ? get_parent_ip+0x9/0x1b May 30 10:46:32 blackpage kernel: [ 1138.019285] [813416bb] ? sub_preempt_count+0x83/0x94 May 30 10:46:32 blackpage kernel: [ 1138.019287] [811280ad] ? blkdev_get+0x2a6/0x2a6 May 30 10:46:32 blackpage kernel: [ 1138.019291] [810fe773] ? __dentry_open+0x21e/0x341 May 30 10:46:32 blackpage kernel: [ 1138.019295] [81107c69] ? dget+0x25/0x2f May 30 10:46:32 blackpage kernel: [ 1138.019297] [8110a09b] ? do_last+0x46d/0x584 May 30 10:46:32 blackpage kernel: [ 1138.019299] [8110b284] ? path_openat+0xc7/0x355 May 30 10:46:32 blackpage kernel: [ 1138.019304] [810d4486] ? tlb_flush_mmu+0x37/0x50 May 30 10:46:32 blackpage kernel: [ 1138.019306] [8110b53e] ? do_filp_open+0x2c/0x72 May 30 10:46:32 blackpage kernel: [ 1138.019308] [8103e7f8] ? get_parent_ip+0x9/0x1b May 30 10:46:32 blackpage kernel: [ 1138.019310] [813416bb] ? sub_preempt_count+0x83/0x94 May 30 10:46:32 blackpage kernel: [ 1138.019313] [8133eba9] ? _raw_spin_unlock+0x26/0x38 May 30 10:46:32 blackpage kernel: [ 1138.019316] [81114d96] ? alloc_fd+0x10b/0x11d May 30 10:46:32 blackpage kernel: [ 1138.019318] [810ff499] ? do_sys_open+0x5f/0xe6 May 30 10:46:32 blackpage kernel: [ 1138.019321] [81344292] ? system_call_fastpath+0x16/0x1b -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-git19 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20110530151712.3679.228.report...@blackpage.schurger.org
Bug#614326: asix USB Ethernet
By the way, when the Linksys USB200M failed here it was replaced with a Belkin F5D5050. That has worked since with no overt problem. It uses the pegasus driver. The problem is in the asix driver and possibly involving udev, isn't it? Regards, ... Peter E. -- Telephone 1 360 450 2132. bcc: peasthope at shaw.ca Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- 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/171057022.36061.33388@heaviside.invalid
Linux 3.0
As you may have seen, the next version of the Linux kernel will be 3.0 (or 3.0.0). There is no significant API change; this just shortens the version string and marks the start of the third decade of Linux. The kernel team will not maintain linux-2.6 vs linux-3.0 packages. We will change the binary metapackages whose names include '2.6' into transitional packages, to be removed after 'wheezy', and we may rename the source packages linux-2.6 and linux-latest-2.6. There are likely to be many programs and build scripts that test for a kernel version prefix of '2.6' vs '2.4' and will behave incorrectly when they find '3.0'. Others require that there are at least 3 numeric components in the version string, which may cease to be true. If you suspect that your packages may have such dependencies, please test against Linux 3.0 release candidates when they are uploaded to experimental (which will happen in the next few days). Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
[bts-link] source package linux-2.6
# # 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 #619827 (http://bugs.debian.org/619827) # * http://bugzilla.kernel.org/show_bug.cgi?id=31962 # * remote status changed: RESOLVED - CLOSED usertags 619827 - status-RESOLVED usertags 619827 + status-CLOSED # remote status report for #626427 (http://bugs.debian.org/626427) # * http://bugzilla.kernel.org/show_bug.cgi?id=35772 # * remote status changed: (?) - NEW usertags 626427 + status-NEW # remote status report for #627575 (http://bugs.debian.org/627575) # * https://bugs.freedesktop.org/show_bug.cgi?id=37514 # * remote status changed: (?) - NEW usertags 627575 + status-NEW 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/20110530163858.20302.61050.btsl...@busoni.debian.org
Re: Linux 3.0
On Montag, 30. Mai 2011, Ben Hutchings wrote: against Linux 3.0 release candidates when they are uploaded to experimental (which will happen in the next few days). awesome. you posted this 5min _before_ I (jokingly) had the idea to ask when Debian will have linux 3.0! :-) /me bows to the whole kernel team! cheers! -- 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/201105301901.10249.hol...@layer-acht.org
Re: cgroup OOM killer loop causes system to lockup (possible fix included)
On Mon, 2011-05-30 at 21:03 +0100, Cal Leeming [Simplicity Media Ltd] wrote: More strangeness.. If I keep the kernel module loaded, but disable the entry in /etc/network/interfaces for eth0, the oom_adj problem disappears. But then ofc, I'm left with no network interface. I then tried binding /etc/ssh/sshd_config to only listen on 127.0.0.1.. effectively bypassing the eth0 interface, whilst still allowing it to be loaded. But the problem still happens. [...] My guess is that sshd tries to protect itself against the OOM-killer so that you can still log in to a system that has gone OOM. If there is no network available, it doesn't do this because you cannot log in remotely anyway. The bug seems to be that sshd does not reset the OOM adjustment before running the login shell (or other program). Therefore, please report a bug against openssh-server. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
[PATCH] add armhf/omap
Hi, The patch [0] adds an omap flavour under armhf. The flavour supports OMAP3 and OMAP4 based boards. I disabled OMAP2 explicitly, because a) OMAP2 is ARMv6, which is not supported by armhf b) OMAP2 breaks VFP3 under OMAP3/4, which is needed by armhf [0] http://pkg-n900.alioth.debian.org/kernel/linux-2.6-omap.patch sha256 24958a765f5291c3a34edd31aeac2ec2a1756d17c2b11389b639ea19d68734be -- Sebastian signature.asc Description: Digital signature
Re: cgroup OOM killer loop causes system to lockup (possible fix included)
Thanks for the response. I have sent this across to the guys at openssh-server. Although, I did check the openssh source code myself, and from what I could tell, everything was being done correctly. I have a feeling there gonna be a lot of 'buck passing' on this one :( Cal On 30/05/2011 21:25, Ben Hutchings wrote: On Mon, 2011-05-30 at 21:03 +0100, Cal Leeming [Simplicity Media Ltd] wrote: More strangeness.. If I keep the kernel module loaded, but disable the entry in /etc/network/interfaces for eth0, the oom_adj problem disappears. But then ofc, I'm left with no network interface. I then tried binding /etc/ssh/sshd_config to only listen on 127.0.0.1.. effectively bypassing the eth0 interface, whilst still allowing it to be loaded. But the problem still happens. [...] My guess is that sshd tries to protect itself against the OOM-killer so that you can still log in to a system that has gone OOM. If there is no network available, it doesn't do this because you cannot log in remotely anyway. The bug seems to be that sshd does not reset the OOM adjustment before running the login shell (or other program). Therefore, please report a bug against openssh-server. Ben. -- 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/4de3fea9.3050...@simplicitymedialtd.co.uk
Re: cgroup OOM killer loop causes system to lockup (possible fix included)
FYI everyone, I found a bug within openssh-server which caused this problem. I've patched and submitted to the openssh list. You can find details of this by googling for: port-linux.c bug with oom_adjust_restore() - causes real bad oom_adj - which can cause DoS conditions It's extremely strange.. :S Cal On 30/05/2011 21:31, Cal Leeming [Simplicity Media Ltd] wrote: Thanks for the response. I have sent this across to the guys at openssh-server. Although, I did check the openssh source code myself, and from what I could tell, everything was being done correctly. I have a feeling there gonna be a lot of 'buck passing' on this one :( Cal On 30/05/2011 21:25, Ben Hutchings wrote: On Mon, 2011-05-30 at 21:03 +0100, Cal Leeming [Simplicity Media Ltd] wrote: More strangeness.. If I keep the kernel module loaded, but disable the entry in /etc/network/interfaces for eth0, the oom_adj problem disappears. But then ofc, I'm left with no network interface. I then tried binding /etc/ssh/sshd_config to only listen on 127.0.0.1.. effectively bypassing the eth0 interface, whilst still allowing it to be loaded. But the problem still happens. [...] My guess is that sshd tries to protect itself against the OOM-killer so that you can still log in to a system that has gone OOM. If there is no network available, it doesn't do this because you cannot log in remotely anyway. The bug seems to be that sshd does not reset the OOM adjustment before running the login shell (or other program). Therefore, please report a bug against openssh-server. Ben. -- 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/4de40dae.7090...@simplicitymedialtd.co.uk
Re: Linux 3.0
On May 30, Ben Hutchings b...@decadent.org.uk wrote: There are likely to be many programs and build scripts that test for a kernel version prefix of '2.6' vs '2.4' and will behave incorrectly when they find '3.0'. Others require that there are at least 3 numeric Expect module-init-tools and three udev scripts to break, for a start. I will fix them in the next upload. This is hugely annoying, because it means that squeeze installs will not work with the kernel from wheezy. (How much difficult would it be to add some knob to the kernel or the libc to make it report to userspace version 2.6.40? :-) ) -- ciao, Marco signature.asc Description: Digital signature
Re: Linux 3.0
On Mon, 2011-05-30 at 23:12 +0200, Marco d'Itri wrote: On May 30, Ben Hutchings b...@decadent.org.uk wrote: There are likely to be many programs and build scripts that test for a kernel version prefix of '2.6' vs '2.4' and will behave incorrectly when they find '3.0'. Others require that there are at least 3 numeric Expect module-init-tools and three udev scripts to break, for a start. I will fix them in the next upload. I'm aware that depmod tries to parse at least 3 version components. Currently utsname::release is set to 3.0.0-rc1 so I think it isn't broken yet. This is hugely annoying, because it means that squeeze installs will not work with the kernel from wheezy. Based on past experience, I would expect udev to do that for us anyway. ;-) But I certainly hope to avoid this situation. (How much difficult would it be to add some knob to the kernel or the libc to make it report to userspace version 2.6.40? :-) ) I could accept changing 3.x to 3.x.0 if Linus insists on using only two components. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#590661:
This bug still applies to the current OpenVZ kernel in Debian Squeeze. I'm greatly surprised that OpenVZ by default blocks using IPsec in *hardware nodes*, which is an industry (and IETF) standard VPN solution for IPv4 and (mandatorily) for IPv6. -- 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/1306793421.15222.4.ca...@traveller.pavlix.net
Re: Linux 3.0
Please reply to debian-kernel as originally requested. On Tue, 2011-05-31 at 00:09 +0200, Vincent Bernat wrote: OoO Lors de la soirée naissante du lundi 30 mai 2011, vers 18:52, Ben Hutchings b...@decadent.org.uk disait : As you may have seen, the next version of the Linux kernel will be 3.0 (or 3.0.0). There is no significant API change; this just shortens the version string and marks the start of the third decade of Linux. Are we sure that the change won't be reverted later in the RC cycle? This change will break a lot of software that rely on detecting the kernel version to make some decisions. Then it was broken already. Maybe the 3.0.0 could be released as 2.6.40 to avoid unnecessary breakages? I would strongly oppose doing such renumbering in Debian. It is possible that Linus changes the version back to that, but I doubt it. We could delay uploading it to unstable for a while if this is necessary to allow time for fixes to userland. (But I do not want to wait for the many OOT modules which will undoubtedly break.) Ben. I do not mean not working on supporting 3.x numbering correctly as soon as possible. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Linux 3.0
We could delay uploading it to unstable for a while if this is necessary to allow time for fixes to userland. Would this mean we wouldn't have it in Experimental either? Adnan On Mon, May 30, 2011 at 11:12 PM, Ben Hutchings b...@decadent.org.uk wrote: Please reply to debian-kernel as originally requested. On Tue, 2011-05-31 at 00:09 +0200, Vincent Bernat wrote: OoO Lors de la soirée naissante du lundi 30 mai 2011, vers 18:52, Ben Hutchings b...@decadent.org.uk disait : As you may have seen, the next version of the Linux kernel will be 3.0 (or 3.0.0). There is no significant API change; this just shortens the version string and marks the start of the third decade of Linux. Are we sure that the change won't be reverted later in the RC cycle? This change will break a lot of software that rely on detecting the kernel version to make some decisions. Then it was broken already. Maybe the 3.0.0 could be released as 2.6.40 to avoid unnecessary breakages? I would strongly oppose doing such renumbering in Debian. It is possible that Linus changes the version back to that, but I doubt it. We could delay uploading it to unstable for a while if this is necessary to allow time for fixes to userland. (But I do not want to wait for the many OOT modules which will undoubtedly break.) Ben. I do not mean not working on supporting 3.x numbering correctly as soon as possible. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- 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/BANLkTik=p231s1nwxah+jm9+fktf5bc...@mail.gmail.com
Bug#628641: linux-image-2.6.32-5-686: crashes when closing laptop lid (dell inspiron 300m)
Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal after upgrading the kernel, my laptop seems to crash immediately after closing the laptop screen. i've seen it happen both when running console (screen goes black and stays black) or when running X (screen freezes, but whatever content was there remains visible). previous versions (including 2.6.32-31, just confirmed) worked fine, in that closing the lid didn't really do anything. so far, it seems to be completely repeatable. live well, vagrant -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 07:08:50 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/lilwalrus-rt ro keyboard=us quiet ** Not tainted ** Kernel log: [ 14.514303] nsc-ircc, chip-init [ 14.514315] nsc-ircc, Found chip at base=0x02e [ 14.514339] nsc-ircc, driver loaded (Dag Brattli) [ 14.514544] nsc_ircc_open(), can't get iobase of 0x2f8 [ 14.514571] nsc-ircc, Found chip at base=0x02e [ 14.514595] nsc-ircc, driver loaded (Dag Brattli) [ 14.514601] nsc_ircc_open(), can't get iobase of 0x2f8 [ 14.515534] nsc-ircc 00:06: disabled [ 14.614073] lib80211: common routines for IEEE802.11 drivers [ 14.614079] lib80211_crypt: registered algorithm 'NULL' [ 15.013847] [drm] Initialized drm 1.1.0 20060810 [ 15.038928] ieee80211: 802.11 data/management/control stack, git-1.1.13 [ 15.038935] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [ 15.240345] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [ 15.240351] ipw2100: Copyright(c) 2003-2006 Intel Corporation [ 15.240803] ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 5 [ 15.240808] PCI: setting IRQ 5 as level-triggered [ 15.240816] ipw2100 :02:04.0: PCI INT A - Link[LNKE] - GSI 5 (level, low) - IRQ 5 [ 15.241488] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [ 15.241513] ipw2100 :02:04.0: firmware: requesting ipw2100-1.3.fw [ 15.795771] i915 :00:02.0: PCI INT A - Link[LNKA] - GSI 10 (level, low) - IRQ 10 [ 15.795781] i915 :00:02.0: setting latency timer to 64 [ 15.801373] [drm] set up 7M of stolen space [ 15.950305] [drm] initialized overlay support [ 16.212227] yenta_cardbus :02:03.0: CardBus bridge found [1028:0150] [ 16.340844] yenta_cardbus :02:03.0: ISA IRQ mask 0x0018, PCI irq 10 [ 16.340851] yenta_cardbus :02:03.0: Socket status: 3006 [ 16.340858] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #02 to #06 [ 16.340872] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff [ 16.340878] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x3fff: clean. [ 16.341260] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge Memory window: 0xe020 - 0xe02f [ 16.341265] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge Memory window: 0x4800 - 0x4fff [ 16.352161] yenta_cardbus :02:03.1: CardBus bridge found [1028:0150] [ 16.752833] yenta_cardbus :02:03.1: ISA IRQ mask 0x0018, PCI irq 10 [ 16.752839] yenta_cardbus :02:03.1: Socket status: 3006 [ 16.752845] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #06 to #0a [ 16.752856] yenta_cardbus :02:03.1: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff [ 16.752862] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3000-0x3fff: clean. [ 16.753241] yenta_cardbus :02:03.1: pcmcia: parent PCI bridge Memory window: 0xe020 - 0xe02f [ 16.753246] yenta_cardbus :02:03.1: pcmcia: parent PCI bridge Memory window: 0x4800 - 0x4fff [ 16.932969] Console: switching to colour frame buffer device 128x48 [ 16.941850] fb0: inteldrmfb frame buffer device [ 16.941853] registered panic notifier [ 16.943520] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 16.943596] Intel ICH Modem :00:1f.6: PCI INT B - Link[LNKB] - GSI 10 (level, low) - IRQ 10 [ 16.943622] Intel ICH Modem :00:1f.6: setting latency timer to 64 [ 16.948818] Intel ICH :00:1f.5: PCI INT B - Link[LNKB] - GSI 10 (level, low) - IRQ 10 [ 16.948856] Intel ICH :00:1f.5: setting latency timer to 64 [ 17.537475] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [ 17.538347] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [ 17.538744] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [ 17.539077] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [ 17.539586] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [ 17.540188] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: clean. [ 17.541053] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [ 17.541451] pcmcia_socket pcmcia_socket1:
Re: Linux 3.0
On Mon, 2011-05-30 at 23:21 +, Adnan Hodzic wrote: We could delay uploading it to unstable for a while if this is necessary to allow time for fixes to userland. Would this mean we wouldn't have it in Experimental either? [...] Of course not. Just as we uploaded stable releases 2.6.33-2.6.38 to experimental during the freeze, we can do so again with 3.0 if necessary. (But Linux 2.6.39 is not going to have long-term support, so the delay cannot be long.) Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#628641: linux-image-2.6.32-5-686: crashes when closing laptop lid (dell inspiron 300m)
On Mon, 2011-05-30 at 16:56 -0700, Vagrant Cascadian wrote: Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal after upgrading the kernel, my laptop seems to crash immediately after closing the laptop screen. i've seen it happen both when running console (screen goes black and stays black) or when running X (screen freezes, but whatever content was there remains visible). previous versions (including 2.6.32-31, just confirmed) worked fine, in that closing the lid didn't really do anything. so far, it seems to be completely repeatable. Try booting without VirtualBox modules. (I don't think it would cause this, but I really don't trust it.) Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 590280
Processing commands for cont...@bugs.debian.org: tags 590280 + pending Bug #590280 [linux-2.6] linux-image-2.6.32-5-amd64: Kernel module for wireless PCI card Realtek RTL8191SE/RTL8192SE Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 590280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590280 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.130680284019927.transcr...@bugs.debian.org
Bug#570268: sky2 fails when memory exceeds 2GB on amd64 kernel
Dale, Is this bug still present in Debian 6.0 'squeeze'? I applied many bug fixes to the sky2 driver in package version 2.6.32-22, and those may have fixed it (but I can't tell from the descriptions). If not, please can you test Linux 2.6.38 (from testing) or 2.6.39 (unstable)? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 570268
Processing commands for cont...@bugs.debian.org: tags 570268 + moreinfo Bug #570268 [linux-2.6] sky2 fails when memory exceeds 2GB on amd64 kernel Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 570268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570268 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.130680703731716.transcr...@bugs.debian.org
Processed: tagging 594350, severity of 594350 is important
Processing commands for cont...@bugs.debian.org: tags 594350 + moreinfo Bug #594350 [linux-2.6] Sense: Unrecovered read error - auto reallocate failed, failed command: READ DMA Added tag(s) moreinfo. # undo bogus changes severity 594350 important Bug #594350 [linux-2.6] Sense: Unrecovered read error - auto reallocate failed, failed command: READ DMA Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 594350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594350 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.130680717531899.transcr...@bugs.debian.org
Processed: severity of 625217 is important
Processing commands for cont...@bugs.debian.org: severity 625217 important Bug #625217 [xen-linux-system-2.6.32-5-xen-amd64] xen-linux-system-2.6.32-5-xen-amd64: Heavy load on domU causes dom0 to run out of memory Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 625217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625217 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.130680736132234.transcr...@bugs.debian.org
Processed: severity of 627293 is important
Processing commands for cont...@bugs.debian.org: severity 627293 important Bug #627293 [linux-2.6] linux-image-2.6.38-2-686: Kernel crash on wakeup from sleep mode Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 627293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627293 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.130680737532257.transcr...@bugs.debian.org
Bug#627293: linux-image-2.6.38-2-686: Kernel crash on wakeup from sleep mode
On Thu, 2011-05-19 at 13:13 +0200, Jose Couto wrote: Package: linux-2.6 Version: 2.6.38-5 Severity: critical Tags: sid Justification: breaks the whole system My computer crashes from time to time when it wakes up from sleep mode. It also affects to previous kernels (not sure about which one was the first version with this problem). See the attached photo from the crash info. Regards. -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-5) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Sun May 8 14:49:45 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=UUID=0f48edf1-a139-4db0-a4ad-4576cf479fa6 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. [...] Does this still happen if you boot without the VirtualBox modules? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 627293
Processing commands for cont...@bugs.debian.org: tags 627293 + moreinfo Bug #627293 [linux-2.6] linux-image-2.6.38-2-686: Kernel crash on wakeup from sleep mode Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 627293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627293 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.1306807647779.transcr...@bugs.debian.org
Bug#628650: linux-image-2.6.32-5-amd64: dd fails with ASC-1045 SAS controller and LTO-4
Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal I have a Quantum LTO-4 tape drive connected to an ASC-1045 controller. The kernel logs included do show the nature of the problem I have encountered. I am writing data to / from the tape drive using dd, like so: dd if=/dev/nst0 of=file bs=32K This causes the messages you see below. The tape drive will become unusable, and I have no choice but to do a cold boot to restore access to the device, otherwise I get device busy messages. I have attempted to use the official adaptec drivers for this card, and get the same result as when I use mvsas. I am not sure if this problem is a hardware issue (I suspect not, since sometimes things work) or a software issue. I am able to send some data to the tape drive, and read some data... the problem has been very difficult for me to narrow down. The information attached to this particular bug report comes from an attempt to use the Adaptec driver, which is not part of Debian, but identical messages are generated with the mvsas module. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/virtualmachines-virtualserver--root ro quiet ** Not tainted ** Kernel log: [ 482.176432] [a0036671] ? scsi_init_sgtable+0x3f/0x5a [scsi_mod] [ 482.176438] [812fb3b5] ? schedule_timeout+0x2e/0xdd [ 482.176443] [8117ecde] ? blk_peek_request+0x18b/0x19f [ 482.176446] [812fb26c] ? wait_for_common+0xde/0x15b [ 482.176453] [8104a440] ? default_wake_function+0x0/0x9 [ 482.176456] [a013a079] ? st_do_scsi+0x2c4/0x2f4 [st] [ 482.176460] [a013d5b2] ? st_read+0x38a/0x8cf [st] [ 482.176465] [810ef538] ? vfs_read+0xa6/0xff [ 482.176467] [810ef64d] ? sys_read+0x45/0x6e [ 482.176471] [81010b42] ? system_call_fastpath+0x16/0x1b [ 602.176047] INFO: task dd:2388 blocked for more than 120 seconds. [ 602.176165] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 602.176318] ddD 88081d2bd4c0 0 2388 2387 0x [ 602.176321] 88081d2bd4c0 0086 8118314f [ 602.176325] 00800020 0fe0 f9e0 88081cb31fd8 [ 602.176328] 00015780 00015780 88081d2bdbd0 88081d2bdec8 [ 602.176331] Call Trace: [ 602.176337] [8118314f] ? blk_rq_map_sg+0x140/0x289 [ 602.176349] [a0036671] ? scsi_init_sgtable+0x3f/0x5a [scsi_mod] [ 602.176353] [812fb3b5] ? schedule_timeout+0x2e/0xdd [ 602.176357] [8117ecde] ? blk_peek_request+0x18b/0x19f [ 602.176359] [812fb26c] ? wait_for_common+0xde/0x15b [ 602.176364] [8104a440] ? default_wake_function+0x0/0x9 [ 602.176367] [a013a079] ? st_do_scsi+0x2c4/0x2f4 [st] [ 602.176371] [a013d5b2] ? st_read+0x38a/0x8cf [st] [ 602.176374] [810ef538] ? vfs_read+0xa6/0xff [ 602.176377] [810ef64d] ? sys_read+0x45/0x6e [ 602.176380] [81010b42] ? system_call_fastpath+0x16/0x1b [ 722.176069] INFO: task dd:2388 blocked for more than 120 seconds. [ 722.176188] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 722.176341] ddD 88081d2bd4c0 0 2388 1 0x0004 [ 722.176346] 88081d2bd4c0 0086 8118314f [ 722.176349] 00800020 0fe0 f9e0 88081cb31fd8 [ 722.176352] 00015780 00015780 88081d2bdbd0 88081d2bdec8 [ 722.176355] Call Trace: [ 722.176363] [8118314f] ? blk_rq_map_sg+0x140/0x289 [ 722.176379] [a0036671] ? scsi_init_sgtable+0x3f/0x5a [scsi_mod] [ 722.176385] [812fb3b5] ? schedule_timeout+0x2e/0xdd [ 722.176389] [8117ecde] ? blk_peek_request+0x18b/0x19f [ 722.176392] [812fb26c] ? wait_for_common+0xde/0x15b [ 722.176397] [8104a440] ? default_wake_function+0x0/0x9 [ 722.176401] [a013a079] ? st_do_scsi+0x2c4/0x2f4 [st] [ 722.176404] [a013d5b2] ? st_read+0x38a/0x8cf [st] [ 722.176409] [810ef538] ? vfs_read+0xa6/0xff [ 722.176412] [810ef64d] ? sys_read+0x45/0x6e [ 722.176415] [81010b42] ? system_call_fastpath+0x16/0x1b [ 842.176106] INFO: task dd:2388 blocked for more than 120 seconds. [ 842.176225] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 842.176378] ddD 88081d2bd4c0 0 2388 1 0x0004 [ 842.176383] 88081d2bd4c0 0086 8118314f [ 842.176387] 00800020 0fe0 f9e0 88081cb31fd8 [ 842.176390] 00015780 00015780 88081d2bdbd0 88081d2bdec8 [ 842.176393]
Bug#593683: fixed as far as I'm concerned
tag 593683 - moreinfo squeeze-ignore unreproducible notfound 593683 2.6.32-29 close 593683 2.6.32-22 thanks On Wed, 2011-01-12 at 11:34 +0100, Julien Cristau wrote: user release.debian@packages.debian.org usertag 593683 squeeze-can-defer tag 593683 squeeze-ignore kthxbye As far as I'm concerned this is fixed. Not closing again because waldi reopened it, but tagging as not a blocker. It is fixed, and we should stop playing around with tags just because Bastian is confusing two different bugs. GRUB used to rely on debian-installer to set postinst_hook for it, and the kernel will still honour that. But on some systems where users have switched from LILO to GRUB while using lenny, the user did not know they should set this. Since we try to maintain the same kernel ABI during a stable release, there was never any *need* to update the GRUB menu until they upgraded from 2.6.26-2-flavour to 2.6.32-5-flavour. But the configuration was broken all along, and this problem is independent of the bug that Bastian originally reported. Bastian, if you still think the kernel should somehow work around this problem, please make a new report. But it should be severity important or lower, because a missing menu entry is in not grave! Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: fixed as far as I'm concerned
Processing commands for cont...@bugs.debian.org: tag 593683 - moreinfo squeeze-ignore unreproducible Bug #593683 [linux-2.6] linux-2.6 - images does not conflict with pre-policy versions of bootloaders Removed tag(s) unreproducible, squeeze-ignore, and moreinfo. notfound 593683 2.6.32-29 Bug #593683 [linux-2.6] linux-2.6 - images does not conflict with pre-policy versions of bootloaders There is no source info for the package 'linux-2.6' at version '2.6.32-29' with architecture '' Unable to make a source version for version '2.6.32-29' Bug No longer marked as found in versions 2.6.32-29. close 593683 2.6.32-22 Bug#593683: linux-2.6 - images does not conflict with pre-policy versions of bootloaders 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.6.32-22, send any further explanations to Bastian Blank wa...@debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 593683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593683 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.13068095424631.transcr...@bugs.debian.org
Processed: forcibly merging 490694 508374
Processing commands for cont...@bugs.debian.org: forcemerge 490694 508374 Bug#490694: linux-image-2.6.25-2-powerpc: OOPS on startup after upgrade 2.6.25-2-powerpc Bug#508374: Oops at startup: linux-image-2.6.26-1-powerpc Forcibly Merged 490694 508374. thanks Stopping processing here. Please contact me if you need assistance. -- 490694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490694 508374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508374 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.130681448618346.transcr...@bugs.debian.org
Bug#496917: marked as done (BUG: soft lockup - CPU#1 stuck for 4096s! [java:3174] and crash (kvm guest))
Your message dated Tue, 31 May 2011 04:59:17 +0100 with message-id 1306814357.4277.90.camel@localhost and subject line Re: BUG: soft lockup - CPU#1 stuck for 4096s! [java:3174] and crash (kvm guest) has caused the Debian Bug report #496917, regarding BUG: soft lockup - CPU#1 stuck for 4096s! [java:3174] and crash (kvm guest) 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.) -- 496917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-3 Severity: important Using kvm 72, the guest is started with: kvm -smp 2 \ -net nic,macaddr=DE:AD:BE:EF:21:71,model=virtio \ -net tap,ifname=tap02,script=/etc/kvm/kvm-ifup \ -net nic,macaddr=DE:AD:BE:EF:21:72,model=virtio \ -net tap,ifname=tap12,script=/etc/kvm/kvm-ifup-web \ -drive if=virtio,boot=on,file=/dev/vg0/web-root \ -drive if=virtio,file=/dev/vg0/web-log \ -drive if=virtio,file=/dev/vg0/web-srv \ -drive if=virtio,file=/dev/vg0/web-swap \ -m 3192 \ -kernel /boot/vmlinuz-2.6.26-1-amd64 \ -initrd /boot/initrd.img-2.6.26-1-amd64 \ -append root=/dev/vda ro \ -curses On the guest, I run the latest JDK from Sun 1.6.0_07, and the latest JBoss from Redhat 4.2.3.GA, default configuration (except that it's started via runit: exec chpst -u jboss:jboss -e ./env -o 65536 /opt/jboss/bin/run.sh -b host After restarting it a few times, I get the following crash of the guest kernel: Aug 28 14:38:06 web-new kernel: [ 6677.939474] BUG: soft lockup - CPU#0 stuck for 4096s! [master:2066] Aug 28 14:38:06 web-new kernel: [ 6677.941978] Modules linked in: ipv6 snd_pcsp snd_pcm parport_pc parport snd_timer serio_raw snd psmouse soundcore i2c_piix4 snd_page_alloc i2c_core button evdev dm_mirror dm_log dm_snapshot dm_mod ide_cd_mod cdrom ata_generic floppy piix ide_pci_generic thermal fan virtio_balloon virtio_pci virtio_ring virtio_rng rng_core virti o_net virtio_blk virtio freq_table processor thermal_sys raid1 raid0 md_mod atiixp ahci sata_nv sata_sil sata_via libata dock via82cxxx ide_core 3w_9xxx 3w_ scsi_mod xfs ext3 jbd ext2 mbcache reiserfs Aug 28 14:38:06 web-new kernel: [ 6677.941978] CPU 0: Aug 28 14:38:06 web-new kernel: [ 6677.941978] Modules linked in: ipv6 snd_pcsp snd_pcm parport_pc parport snd_timer serio_raw snd psmouse soundcore i2c_piix4 snd_page_alloc i2c_core button evdev dm_mirror dm_log dm_snapshot dm_mod ide_cd_mod cdrom ata_generic floppy piix ide_pci_generic thermal fan virtio_balloon virtio_pci virtio_ring virtio_rng rng_core virti o_net virtio_blk virtio freq_table processor thermal_sys raid1 raid0 md_mod atiixp ahci sata_nv sata_sil sata_via libata dock via82cxxx ide_core 3w_9xxx 3w_ scsi_mod xfs ext3 jbd ext2 mbcache reiserfs Aug 28 14:38:06 web-new kernel: [ 6677.941978] Pid: 2066, comm: master Not tainted 2.6.26-1-amd64 #1 Aug 28 14:38:06 web-new kernel: [ 6677.941978] RIP: 0033:[7fcf1e3d4c0a] [7fcf1e3d4c0a] Aug 28 14:38:06 web-new kernel: [ 6677.941978] RSP: 002b:7fff264e18e0 EFLAGS: 0202 Aug 28 14:38:06 web-new kernel: [ 6677.941978] RAX: 0002 RBX: 0086 RCX: Aug 28 14:38:06 web-new kernel: [ 6677.941978] RDX: 0430 RSI: 7fcf1e4dc903 RDI: 00401895 Aug 28 14:38:06 web-new kernel: [ 6677.941978] RBP: 005078bc R08: 7fcf1e4e4c98 R09: Aug 28 14:38:06 web-new kernel: [ 6677.941978] R10: R11: 0064 R12: 7fff264e1e50 Aug 28 14:38:06 web-new kernel: [ 6677.941978] R13: 7fff264e1ed0 R14: 7fcf1e298de0 R15: 7fff264e1f50 Aug 28 14:38:06 web-new kernel: [ 6677.941978] FS: 7fcf1e4d96d0() GS:8053b000() knlGS: Aug 28 14:38:06 web-new kernel: [ 6677.941978] CS: 0010 DS: ES: CR0: 8005003b Aug 28 14:38:06 web-new kernel: [ 6677.941978] CR2: 7f65642cb860 CR3: c4162000 CR4: 06e0 Aug 28 14:38:06 web-new kernel: [ 6677.941978] DR0: DR1: DR2: Aug 28 14:38:06 web-new kernel: [ 6677.941978] DR3: DR6: 0ff0 DR7: 0400 Aug 28 14:38:06 web-new kernel: [ 6677.941978] Aug 28 14:38:06 web-new kernel: [ 6677.941978] Call Trace: Aug 28 14:38:06 web-new kernel: [ 6677.941978] Aug 28 14:38:06 web-new kernel: [ 6677.939462] BUG: soft lockup - CPU#1 stuck for 4096s! [java:3174] Aug 28 14:38:06 web-new kernel: [ 6677.939462] Modules linked in: ipv6 snd_pcsp snd_pcm parport_pc parport snd_timer
Processed: tagging 490694
Processing commands for cont...@bugs.debian.org: tags 490694 + upstream Bug #490694 [linux-2.6] linux-image-2.6.25-2-powerpc: OOPS on startup after upgrade 2.6.25-2-powerpc Bug #508374 [linux-2.6] Oops at startup: linux-image-2.6.26-1-powerpc Added tag(s) upstream. Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 490694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490694 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.130681456418438.transcr...@bugs.debian.org
Bug#508492: linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error xlog_valid_rec_header(2)
On Thu, 2008-12-11 at 12:55 -0700, Bryan Stillwell wrote: Package: linux-image-2.6.26-1-parisc64 Version: 2.6.26-11 Severity: important When attempting to use XFS on /dev/sdb1 on an HP Visualize C3650, I'm seeing problems with very basic usage: [...] As stated previously, XFS did not work properly on hppa for a long time. It relied on CPU cache behaviour which hppa did not implement, and should not have been provided for hppa. In Debian 6.0 'squeeze' we have disabled XFS on hppa, to avoid the risk of data loss. Since Linux 2.6.34, XFS is supposed to work correctly on hppa. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: reassign 514459 to cryptsetup
Processing commands for cont...@bugs.debian.org: reassign 514459 cryptsetup Bug #514459 [linux-2.6] linux-image-2.6.25-2-486: encrypted root-partition not detected Bug reassigned from package 'linux-2.6' to 'cryptsetup'. Bug No longer marked as found in versions 2.6.25-7. thanks Stopping processing here. Please contact me if you need assistance. -- 514459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514459 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.130681598921615.transcr...@bugs.debian.org
Bug#508523: marked as done ([linux-image-2.6.26-1-vserver-amd64] Can't delete vservers or remove hashed files (works in 2.6.25))
Your message dated Tue, 31 May 2011 05:24:14 +0100 with message-id 1306815854.4277.104.camel@localhost and subject line Re: Fix for this issue has caused the Debian Bug report #508523, regarding [linux-image-2.6.26-1-vserver-amd64] Can't delete vservers or remove hashed files (works in 2.6.25) 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.) -- 508523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: util-vserver Version: 0.30.216~r2772-5 Severity: important root@rootwood:/home/ivan# vserver saturn5 delete Are you sure you want to delete the vserver saturn5 (y/N) y /bin/rm: cannot remove `/var/lib/vservers/saturn5/sbin/installkernel': Operation not permitted and so on, for hundreds of files... ls -l /var/lib/vservers/saturn5/sbin/installkernel -rwxr-xr-x 2 root root 2331 2008-06-27 07:21 /var/lib/vservers/saturn5/sbin/installkernel It appears that all the files it is complaining about were hashified and are thus shared between multiple vservers. I also cannot remove any shared files at all: root@rootwood:/home/ivan# vserver qis enter qis:/# rm -f /usr/local/share/perl/5.8.8/FS/cust_main.pm rm: cannot remove `/usr/local/share/perl/5.8.8/FS/cust_main.pm': Operation not permitted -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-vserver-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages util-vserver depends on: ii debconf 1.5.24 Debian configuration management sy ii iproute 20080725-2 networking and traffic control too ii libbeecrypt6 4.1.2-7open source C library of cryptogra ii libc6 2.7-16 GNU C Library: Shared libraries ii make 3.81-5 The GNU version of the make util ii net-tools 1.60-22The NET-3 networking toolkit ii util-linux2.13.1.1-1 Miscellaneous system utilities Versions of packages util-vserver recommends: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii debootstrap 1.0.10 Bootstrap a basic Debian system Versions of packages util-vserver suggests: ii iptables 1.4.1.1-4 administration tools for packet fi ii linux-image-2.6.24-1-amd64 [l 2.6.24-7 Linux 2.6.24 image on AMD64 ii linux-image-2.6.25-2-amd64 [l 2.6.25-7 Linux 2.6.25 image on AMD64 ii linux-image-2.6.25-2-vserver- 2.6.25-7 Linux 2.6.25 image on AMD64 ii linux-image-2.6.26-1-vserver- 2.6.26-11 Linux 2.6.26 image on AMD64, Linux ii module-init-tools 3.4-1 tools for managing Linux kernel mo ii procps1:3.2.7-9 /proc file system utilities pn vlan none (no description available) ii wget 1.11.4-2 retrieves files from the web pn yum none (no description available) -- debconf information: util-vserver/prerm_stop_running_vservers: true util-vserver/postrm_remove_vserver_configs: false ---End Message--- ---BeginMessage--- Version: 2.6.32-3 On Tue, 2009-05-12 at 14:38 +0100, b...@bristolwireless.net wrote: After a conversation on IRC with Herbert Pötzl it appears that the changes in the position of some xattr flags on the vserver patch used within the Debian kernel are to blame for this behaviour. There is an additional flag differences which affect chroot security which should also be changed also. #508523 is also probably related. The parts of the vserver patch Debian uses which need to be changed for consistency with the other vserver implementations (including consistency with Debian Etch's kernels) are: +#define FS_IXUNLINK_FL 0x0100 /* Immutable invert on unlink */ should be +#define FS_IXUNLINK_FL 0x0800 /* Immutable invert on unlink */ and +#define FS_BARRIER_FL 0x1000 /* Barrier for chroot() */ should be +#define FS_BARRIER_FL 0x0400 /* Barrier for chroot() */ I've documented a brief summary of what is happening at http://linux-vserver.org/Installation_on_Debian#Issues_with_the_current_2.6.26_Kernel I have very little knowledge of vserver, and I don't know how we came to use different values for these macros. Unfortunately we cannot change them in a stable update to
Bug#515201: marked as done (linux-image: sata drive connected via marvell controller crashes)
Your message dated Tue, 31 May 2011 05:37:13 +0100 with message-id 1306816633.4277.113.camel@localhost and subject line Re: Bug#515201: linux-image: sata drive connected via marvell controller crashes has caused the Debian Bug report #515201, regarding linux-image: sata drive connected via marvell controller crashes 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.) -- 515201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image Severity: important i have ASUS M2N32 WS Professionall mainboard with latest BIOS revision 2001. it has two controllers for sata: - standard (nvidia) - marvell and also i have two sata II disks: 1 - with Debian 32-bit, kernel 2.6.26-1-686-bigmem - plugged in standard sata 2 - with Debian 64-bit, kernel 2.6.26-1-amd64 - plugged in marvell sata the standard sata controller works fine, but i have problems with the marvell. * when booting disk 1 (disk 2 is connected to marvell controller) system does not boot up correctly. it holds-on - see photo: http://develop.euroimpex.pl/~marek/boot/dsc00226.jpg last few lines of long display in a loop if waiting longer.. * when booting disk 1, with disk 2 unplugged, system starts fine ofcourse, but when plugin disk 2 to marvell (when system is on), the message 'Disabling IRQ #16' appears in console and system hangs-up. * i tried also bootup from disk 2 (marvell controller), the grub started, kernel started to doing it's job, but it crashed - see photo: http://develop.euroimpex.pl/~marek/boot/dsc00227.jpg maybe i am doing something wrong? maybe my mainboard has a bug, or maybe it's something wrong in kernel? or maybe i have badly configured IRQs in the BIOS? - not sure cheers. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On Sun, 2010-05-02 at 20:49 +0200, Moritz Muehlenhoff wrote: On Mon, Nov 02, 2009 at 09:55:21PM +0100, Marek Poks wrote: On 11/01/2009 01:40 AM, Ben Hutchings wrote: On Sat, 2009-10-31 at 20:30 +0100, Mark Poks wrote: [...] I have latest lenny amd64 version (release 5.0.3 as i remember). it is provided with kernel 2.6.26-19lenny1. marvell still does not work. OK, noted. in few days i will test it with kernel 2.6.30-8~bpo50+1. Please do. Ben. with kernel 2.6.30-8~bpo50+1 it still does not boot. it loops same messages when trying to communicate device. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Closing due to lack of response. If you can reproduce this using a current kernel version, please let us know. I'm sorry I didn't progress this further when you reported against Linux 2.6.30. Unfortunately we have an overwhelming number of open bug reports. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#516187: marked as done (linux-image-2.6.26-1-amd64: r8169 module : ethernet port always down)
Your message dated Tue, 31 May 2011 05:38:21 +0100 with message-id 1306816701.4277.114.camel@localhost and subject line Re: linux-image-2.6.26-1-amd64: r8169 module : ethernet port always down has caused the Debian Bug report #516187, regarding linux-image-2.6.26-1-amd64: r8169 module : ethernet port always down 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.) -- 516187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important Ethernet port never switch to UP. It work under MS-Windows. It work during install but only if I boot MS-Windows before. It do not work anymore under Debian Lenny, even if I reboot first under MS-Windows. My computer is a laptop MSI GX600-073 Extreme Edition. If you need more information, mail me. Kind Regards, Olivier -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: root=/dev/sda3 ro quiet ** Tainted: P (1) ** Kernel log: [ 4908.771078] eth0: PHY reset until link up [ 4918.828455] eth0: PHY reset until link up [ 4928.877942] eth0: PHY reset until link up [ 4938.924255] eth0: PHY reset until link up [ 4948.960422] eth0: PHY reset until link up [ 4959.011260] eth0: PHY reset until link up [ 4969.056141] eth0: PHY reset until link up [ 4979.105140] eth0: PHY reset until link up [ 4989.146974] eth0: PHY reset until link up [ 4999.189266] eth0: PHY reset until link up [ 5009.335061] eth0: PHY reset until link up [ 5019.436561] eth0: PHY reset until link up [ 5029.521738] eth0: PHY reset until link up [ 5039.653001] eth0: PHY reset until link up [ 5048.749132] wlan0: switched to short barker preamble (BSSID=00:03:c9:8c:c0:c9) [ 5049.783408] eth0: PHY reset until link up [ 5059.898742] eth0: PHY reset until link up [ 5069.951189] eth0: PHY reset until link up [ 5080.000491] eth0: PHY reset until link up [ 5090.065816] eth0: PHY reset until link up [ 5100.103129] eth0: PHY reset until link up [ 5110.151498] eth0: PHY reset until link up [ 5120.182063] eth0: PHY reset until link up [ 5130.217184] eth0: PHY reset until link up [ 5140.295190] eth0: PHY reset until link up [ 5150.361832] eth0: PHY reset until link up [ 5160.410157] eth0: PHY reset until link up [ 5170.458938] eth0: PHY reset until link up [ 5180.499672] eth0: PHY reset until link up [ 5190.542756] eth0: PHY reset until link up [ 5200.589474] eth0: PHY reset until link up [ 5210.647583] eth0: PHY reset until link up [ 5220.693491] eth0: PHY reset until link up [ 5230.754683] eth0: PHY reset until link up [ 5240.821769] eth0: PHY reset until link up [ 5250.905526] eth0: PHY reset until link up [ 5260.988784] eth0: PHY reset until link up [ 5271.050887] eth0: PHY reset until link up [ 5281.117707] eth0: PHY reset until link up [ 5291.170610] eth0: PHY reset until link up [ 5301.288280] eth0: PHY reset until link up [ 5311.381599] eth0: PHY reset until link up [ 5321.460774] eth0: PHY reset until link up [ 5331.557786] eth0: PHY reset until link up [ 5341.670289] eth0: PHY reset until link up [ 5351.774825] eth0: PHY reset until link up [ 5361.874094] eth0: PHY reset until link up [ 5371.985108] eth0: PHY reset until link up [ 5382.056401] eth0: PHY reset until link up [ 5392.137381] eth0: PHY reset until link up [ 5402.190443] eth0: PHY reset until link up [ 5412.245285] eth0: PHY reset until link up [ 5422.328872] eth0: PHY reset until link up [ 5432.402516] eth0: PHY reset until link up [ 5442.483535] eth0: PHY reset until link up [ 5452.546399] eth0: PHY reset until link up [ 5462.639612] eth0: PHY reset until link up [ 5472.719900] eth0: PHY reset until link up [ 5482.797958] eth0: PHY reset until link up [ 5492.896312] eth0: PHY reset until link up [ 5502.973391] eth0: PHY reset until link up [ 5513.044985] eth0: PHY reset until link up [ 5523.135561] eth0: PHY reset until link up [ 5533.199198] eth0: PHY reset until link up [ 5543.287609] eth0: PHY reset until link up [ 5553.371844] eth0: PHY reset until link up [ 5563.484047] eth0: PHY reset until link up [ 5573.600853] eth0: PHY reset until link up [ 5583.666569] eth0: PHY reset until link up [ 5593.744181] eth0: PHY reset until link up [ 5603.851937] eth0: PHY reset until link up [ 5613.911937] eth0: PHY reset until link up [ 5623.992364] eth0: PHY reset until link up [ 5634.121176] eth0: PHY reset until link up [ 5644.227208] eth0: PHY reset until link up [
Processed: unmerging 516209
Processing commands for cont...@bugs.debian.org: unmerge 516209 Bug#516209: kernel bug: kpowernow_k8/kondemand Bug#605501: linux-image-2.6-amd64: Cool n Quiet causes system reboot after startup Disconnected #516209 from all other report(s). thanks Stopping processing here. Please contact me if you need assistance. -- 605501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605501 516209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516209 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.130681761325401.transcr...@bugs.debian.org
Bug#517449: marked as done (linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds))
Your message dated Tue, 31 May 2011 05:56:15 +0100 with message-id 1306817775.4277.116.camel@localhost and subject line Re: linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds) has caused the Debian Bug report #517449, regarding linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds) 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.) -- 517449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important Tags: patch * ISSUE Lenny's kernel is subject to the bug described here: http://lkml.org/lkml/2009/1/11/70 * ANALYSIS FIX and fixed with this thread: http://lkml.org/lkml/2009/1/15/107 (in particular with http://lkml.org/lkml/2009/1/15/231 and http://lkml.org/lkml/2009/1/15/240, AFAIU) FWIW, this seems to have made it to 2.6.28.y at least, with: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commit;h=046e7f77d734778a3b2e7d51ce63da3dbe7a8168 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commit;h=df94b12439ca449a852e579fc2952dac80f70c90 * TYPICAL SYMPTOMS Basically, running tasks at SCHED_IDLEPRIO (such as BOINC) renders the system sluggish and randomly unresponsive. Messages such as this one appear in dmesg: [1830473.188790] INFO: task pdflush:3945 blocked for more than 120 seconds. [1830473.269257] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [1830473.365255] pdflush D 81003c595800 0 3945 2 [1830473.365274] 81002f055d60 0046 81002f055d70 804289af [1830473.365278] 8100258eaee0 81003e966f60 8100258eb168 00028031dc67 [1830473.365281] 0008 a03445b4 81000a2e8340 000b [1830473.365283] Call Trace: [1830473.365380] [804289af] thread_return+0x6b/0xac [1830473.365448] [a03445b4] :xfs:xfs_log_move_tail+0x46/0x12c [1830473.365472] [a035b055] :xfs:xfs_buf_wait_unpin+0x86/0xa8 [1830473.365479] [8022c202] default_wake_function+0x0/0xe [1830473.365503] [a035b49b] :xfs:xfs_buf_iorequest+0x20/0x61 [1830473.365538] [a035ec2e] :xfs:xfs_bdstrat_cb+0x36/0x3a [1830473.365559] [a0357d59] :xfs:xfs_bwrite+0x5e/0xbb [1830473.365580] [a0352209] :xfs:xfs_syncsub+0x119/0x226 [1830473.365602] [a03600d4] :xfs:xfs_fs_write_super+0x1b/0x21 [1830473.365608] [8029cd90] sync_supers+0x60/0xa4 [1830473.365615] [802783f2] pdflush+0x0/0x211 [1830473.365619] [80277fb9] wb_kupdate+0x2d/0x10d [1830473.369036] [802783f2] pdflush+0x0/0x211 [1830473.369036] [80278556] pdflush+0x164/0x211 [1830473.369036] [80277f8c] wb_kupdate+0x0/0x10d [1830473.369036] [80246083] kthread+0x47/0x74 [1830473.369036] [80230196] schedule_tail+0x27/0x5c [1830473.369036] [8020cf28] child_rip+0xa/0x12 [1830473.369036] [80213299] restore_i387_ia32+0xb0/0xd4 [1830473.369036] [8024603c] kthread+0x0/0x74 [1830473.369036] [8020cf1e] child_rip+0x0/0x12 Sometimes keyboard input will yield repeated keystrokes. SSH session will stop echoing. And basically hell freezes over for 2 minutes. I believe this bug relates to #498328, #499046 and possibly #499198 This is an extremely nasty bug. I've seen it very frequently while running BOINC on Xen dom0 on a 16-core box (using debian xen kernel). A temporary workaround has been to cap BOINC to 90% CPU usage: freezes still happen but last less. HTH -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-1-amd64 recommends no packages. Versions of packages linux-image-2.6.26-1-amd64 suggests: ii grub 0.97-47lenny2
Bug#520928: marked as done (linux-image-2.6.26-1-686: PIIX4 /dev/hda performance regression (10x times, DMA dissabled))
Your message dated Tue, 31 May 2011 06:01:30 +0100 with message-id 1306818090.4277.120.camel@localhost and subject line Re: linux-image-2.6.26-1-686: PIIX4 /dev/hda performance regression (10x times, DMA dissabled) has caused the Debian Bug report #520928, regarding linux-image-2.6.26-1-686: PIIX4 /dev/hda performance regression (10x times, DMA dissabled) 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.) -- 520928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: important I have 450NX server board (two cpu Xeon II 450MHz). My ide controler is PIIX4. I found that after update to lenny's 2.6.26-1-xen-686 IDE performance droped to just 1.50MB/s (hdparm -t). With 2.6.18-6-xen-686 I had 21.54 MB/s. (Tested both in -xen-686 and -686, in signle user). Performance of scsi disc's doesn't changed. I found this messages in dmesg (2.6.26-1-xen-686): [3.662184] SCSI subsystem initialized [3.734253] Uniform Multi-Platform E-IDE driver [3.734253] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [3.829917] usbcore: registered new interface driver usbfs [3.830286] usbcore: registered new interface driver hub [3.845788] usbcore: registered new device driver usb [3.886790] ACPI: PCI Interrupt :01:03.0[A] - GSI 57 (level, low) - IRQ 57 [3.888465] sym0: 896 rev 0x1 at pci :01:03.0 irq 57 [3.904795] sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking [3.912491] sym0: SCSI BUS has been reset. [3.912721] scsi0 : sym-2.2.3 [3.916707] ACPI: PCI Interrupt :01:03.1[B] - GSI 56 (level, low) - IRQ 56 [3.916873] sym1: 896 rev 0x1 at pci :01:03.1 irq 56 [3.919506] sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking [3.923506] sym1: SCSI BUS has been reset. [3.925391] scsi1 : sym-2.2.3 [3.926118] ACPI: PCI Interrupt :00:08.0[A] - GSI 58 (level, low) - IRQ 58 [3.927288] sym2: 810a rev 0x23 at pci :00:08.0 irq 58 [3.928041] USB Universal Host Controller Interface driver v3.0 [3.931996] sym2: No NVRAM, ID 7, Fast-10, SE, parity checking [3.938010] sym2: SCSI BUS has been reset. [3.938028] scsi2 : sym-2.2.3 [3.939923] ACPI: PCI Interrupt :00:0c.2[D] - GSI 54 (level, low) - IRQ 54 [3.939923] uhci_hcd :00:0c.2: UHCI Host Controller [3.940073] uhci_hcd :00:0c.2: new USB bus registered, assigned bus number 1 [3.940426] uhci_hcd :00:0c.2: irq 54, io base 0x2c00 [3.941228] usb usb1: configuration #1 chosen from 1 choice [3.941577] hub 1-0:1.0: USB hub found [3.941833] hub 1-0:1.0: 2 ports detected [4.041535] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [4.041760] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.041962] usb usb1: Product: UHCI Host Controller [4.042144] usb usb1: Manufacturer: Linux 2.6.26-1-xen-686 uhci_hcd [4.042329] usb usb1: SerialNumber: :00:0c.2 [4.054227] piix: 450NX errata present, disabling IDE DMA. [4.054433] piix: A BIOS update may resolve this. [4.056035] PIIX4: IDE controller (0x8086:0x7111 rev 0x01) at PCI slot :00:0c.1 [4.056051] PIIX4: not 100% native mode: will probe irqs later [4.056051] PIIX4: IDE port disabled [4.056051] ide0: BM-DMA at 0x2c20-0x2c27 [4.056757] Probing IDE interface ide0... [4.349476] hda: IBM-DTLA-307030, ATA DISK drive [5.021402] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [5.021674] hda: no DMA mode selected [5.021888] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [5.022174] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [5.022815] PIIX4: IDE controller (0x8086:0x84ca rev 0x03) at PCI slot :00:10.0 [5.023074] PIIX4: device not capable of full native PCI mode [5.023259] PIIX4: device disabled (BIOS) [5.044348] No dock devices found. [5.284367] libata version 3.00 loaded. [5.384457] Floppy drive(s): fd0 is 1.44M [5.384457] floppy0: Unable to grab DMA2 for the floppy driver [5.428944] udev: renamed network interface eth1 to eth2 [5.865766] hda: max request size: 128KiB [5.887987] hda: 60036480 sectors (30738 MB) w/1916KiB Cache, CHS=59560/16/63 [5.888481] hda: cache flushes not supported [5.69] hda: hda1 hda3 [8.413933] floppy0: no floppy controllers found [8.731608] scsi 2:0:6:0: Direct-Access IBM DDRS-39130 S97B PQ: 0 ANSI: 2 [8.731856]
Bug#524438: cifs: Crash (OOPS or restart) when accessing Windows ME share with accented characters in filenames
On Tue, 2009-10-13 at 14:55 +0200, Benoit SIBAUD wrote: Hi, I believe this bug was fixed in Debian kernel package version 2.6.26-15lenny3. Can you check that this bug is no longer present in the current stable kernel version? Still a kernel panic with a 2.6.26-19 (linux-image-2.6.26-2-686_2.6.26-19_i386.deb). The stack trace seems to always contain CIFSFindNext+0x174/0x2dc [cifs]. (after a fresh reboot) $ smbmount //x/x-xxx /tmp/crash -o username=,workgroup=xxx $ cd /tmp/crash/__Archives/07_Communication_Information/Journées Techniques CORE/Journée du 27 octobre 2005 - Qualité des réseaux/journecore/ppt $ find . -type f /dev/null 21 [KERNEL PANIC] (in attachment, kernel panic screenshot) We got this fix via 2.6.26.7: commit 0752f1522a9120f731232919f7ad904e9e22b8ce Author: Steve French sfre...@us.ibm.com Date: Tue Oct 7 20:03:33 2008 + [CIFS] make sure we have the right resume info before calling CIFSFindNext But it requires these additional fixes which we're missing for some reason: commit b77d753c413e02559669df66e543869dad40c847 Author: Steve French sfre...@us.ibm.com Date: Wed Oct 8 19:13:46 2008 + [CIFS] Check that last search entry resume key is valid commit a364bc0b37f14ffd66c1f982af42990a9d77fa43 Author: Jeff Layton sfre...@us.ibm.com Date: Tue Oct 21 14:42:13 2008 + [CIFS] fix saving of resume key before CIFSFindNext Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 524438, tagging 524438
Processing commands for cont...@bugs.debian.org: tags 524438 - help Bug #524438 [linux-2.6] cifs: Crash (OOPS or restart) when accessing Windows ME share with accented sharacters in filenames Removed tag(s) help. tags 524438 + patch Bug #524438 [linux-2.6] cifs: Crash (OOPS or restart) when accessing Windows ME share with accented sharacters in filenames Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 524438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524438 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.130681872228892.transcr...@bugs.debian.org
Bug#524985: marked as done (python2.5: commands.getstatusoutput fails in i386 chroot)
Your message dated Tue, 31 May 2011 06:14:56 +0100
with message-id 1306818896.4277.126.camel@localhost
and subject line Re: python2.5: commands.getstatusoutput fails in i386 chroot
has caused the Debian Bug report #524985,
regarding python2.5: commands.getstatusoutput fails in i386 chroot
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.)
--
524985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python2.5
Version: 2.5.4-1
Severity: important
Hello,
We discovered that my builds of xorg-server for i386 had strange build
strings (see Build Operating System: ... in /var/log/Xorg.0.log if
you have xserver-xorg-core 1.6.1 installed).
The reason is that lsb_release -i -s fails in my i386 chroot:
morris:~# lsb_release -i -s
Traceback (most recent call last):
File /usr/bin/lsb_release, line 96, in module
main()
File /usr/bin/lsb_release, line 60, in main
distinfo = lsb_release.get_distro_information()
File /usr/lib/pymodules/python2.5/lsb_release.py, line 250, in
get_distro_information
distinfo = guess_debian_release()
File /usr/lib/pymodules/python2.5/lsb_release.py, line 209, in
guess_debian_release
rinfo = guess_release_from_apt()
File /usr/lib/pymodules/python2.5/lsb_release.py, line 151, in
guess_release_from_apt
releases = parse_apt_policy()
File /usr/lib/pymodules/python2.5/lsb_release.py, line 135, in
parse_apt_policy
policy = commands.getoutput('apt-cache policy 2/dev/null')
File /usr/lib/python2.5/commands.py, line 44, in getoutput
return getstatusoutput(cmd)[1]
File /usr/lib/python2.5/commands.py, line 54, in getstatusoutput
text = pipe.read()
IOError: [Errno 9] Bad file descriptor
close failed: [Errno 9] Bad file descriptor
morris:~# Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ftp.debian.org sid/main Packages
release o=Debian,a=unstable,l=Debian,c=main
origin ftp.debian.org
Pinned packages:
The machine is a amd64. lsb_release works fine in a similar amd64 chroot.
I narrowed down the problem using the following python program:
#!/usr/bin/python
import commands
commands.getstatusoutput('echo foobar')
It works outside of chroot on amd64 and i386, and in the amd64 chroot:
But it fails in the i386 chroot:
morris:~# ~bgoglin/test.py
foobar
Traceback (most recent call last):
File /home/bgoglin/test.py, line 3, in module
commands.getstatusoutput('echo foobar')
File /usr/lib/python2.5/commands.py, line 54, in getstatusoutput
text = pipe.read()
IOError: [Errno 9] Bad file descriptor
close failed: [Errno 9] Bad file descriptor
Brice
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-rc2=topinambour (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages python2.5 depends on:
ii libbz2-1.01.0.5-1high-quality block-sorting file co
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libdb4.5 4.5.20-13 Berkeley v4.5 Database Libraries [
ii libncursesw5 5.7+20090404-1 shared libraries for terminal hand
ii libreadline5 5.2-4 GNU readline and history libraries
ii libsqlite3-0 3.6.12-1 SQLite 3 shared library
ii libssl0.9.8 0.9.8g-16 SSL shared libraries
ii mime-support 3.44-1 MIME files 'mime.types' 'mailcap
ii python2.5-minimal 2.5.4-1A minimal subset of the Python lan
python2.5 recommends no packages.
Versions of packages python2.5 suggests:
pn python-profiler none (no description available)
pn python2.5-doc none (no description available)
-- no debconf information
---End Message---
---BeginMessage---
Version: 2.6.26-14
I believe this is a duplicate of #521863, which was fixed in the above
version.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
---End Message---
Processed: forcibly merging 524438 571239
Processing commands for cont...@bugs.debian.org: forcemerge 524438 571239 Bug#524438: cifs: Crash (OOPS or restart) when accessing Windows ME share with accented sharacters in filenames Bug#571239: linux-image-2.6.26-2-686: CIFS OOPS in cifs:CIFSFindNext+0x174/0x2dc Forcibly Merged 524438 571239. thanks Stopping processing here. Please contact me if you need assistance. -- 571239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571239 524438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524438 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.130681902329750.transcr...@bugs.debian.org
Processed: closing 584744
Processing commands for cont...@bugs.debian.org: # damnit close 584744 Bug#584744: linux-2.6: radeonfb builtin on sparc and powerpc 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Julien Cristau jcris...@debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 584744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584744 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.130681909729871.transcr...@bugs.debian.org
Processed: closing 508492, fixed 508492 in 2.6.32-32
Processing commands for cont...@bugs.debian.org:
# matching #423562
close 508492 2.6.34-1~experimental.1
Bug#508492: linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error
xlog_valid_rec_header(2)
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.34-1~experimental.1, send any further
explanations to Bryan Stillwell bryan.stillw...@hp.com
fixed 508492 2.6.32-32
Bug #508492 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error
xlog_valid_rec_header(2)
There is no source info for the package 'linux-2.6' at version '2.6.32-32' with
architecture ''
Unable to make a source version for version '2.6.32-32'
Bug Marked as fixed in versions 2.6.32-32.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
508492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508492
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.130681925130580.transcr...@bugs.debian.org
Processed: tagging 487190
Processing commands for cont...@bugs.debian.org: tags 487190 + wontfix Bug #487190 [linux-2.6] use mode 600 for /proc/*/maps Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 487190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487190 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.130681956932056.transcr...@bugs.debian.org
Processed: tagging 487190
Processing commands for cont...@bugs.debian.org: tags 487190 + upstream Bug #487190 [linux-2.6] use mode 600 for /proc/*/maps Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 487190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487190 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.130681957432070.transcr...@bugs.debian.org
Bug#521886: marked as done (linux-image-2.6.26-1-amd64: [iwl3945] should request firmware only once, not fill logs)
Your message dated Tue, 31 May 2011 06:29:05 +0100 with message-id 1306819745.4277.128.camel@localhost and subject line Re: linux-image-2.6.26-1-amd64: [iwl3945] should request firmware only once, not fill logs has caused the Debian Bug report #521886, regarding linux-image-2.6.26-1-amd64: [iwl3945] should request firmware only once, not fill logs 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.) -- 521886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: wishlist Hello, On first install of Debian, the firmware is not present because it is part of the non-free package. However, the module keeps asking for its firmware (through udev?), which fills the log for no purpose. This can be stopped by rmmod'ing the concerned module, however I believe this is not the best policy, the module should perform its request only once. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: root=/dev/sda1 ro ** Not tainted ** Kernel log: [ 758.788499] firmware: requesting iwlwifi-3945-1.ucode [ 758.799547] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 758.799560] iwl3945: Could not read microcode: -2 [ 758.799739] ACPI: PCI interrupt for device :0c:00.0 disabled [ 881.501380] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 881.504064] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) [ 881.504085] firmware: requesting iwlwifi-3945-1.ucode [ 881.513463] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 881.513463] iwl3945: Could not read microcode: -2 [ 881.513463] ACPI: PCI interrupt for device :0c:00.0 disabled [ 1003.973990] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 1003.974170] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) [ 1003.974485] firmware: requesting iwlwifi-3945-1.ucode [ 1003.983324] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 1003.983324] iwl3945: Could not read microcode: -2 [ 1003.983324] ACPI: PCI interrupt for device :0c:00.0 disabled [ 1127.106704] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 1127.106704] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) (and a lot more like this) ** Loaded modules: Module Size Used by iwl394592916 0 nls_utf86272 6 cifs 235408 6 nls_base 12932 2 nls_utf8,cifs i915 35072 2 drm91488 3 i915 ppdev 11656 0 parport_pc 31016 0 lp 14724 0 parport41776 3 ppdev,parport_pc,lp ipv6 288328 14 acpi_cpufreq 11792 1 cpufreq_stats 9120 0 cpufreq_powersave 6400 0 cpufreq_conservative11784 0 cpufreq_userspace 8452 0 cpufreq_ondemand 11792 1 freq_table 9344 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand sbp2 25356 0 loop 19468 0 snd_hda_intel 434904 1 snd_pcm_oss41760 0 snd_mixer_oss 18816 1 snd_pcm_oss snd_pcm81672 2 snd_hda_intel,snd_pcm_oss arc46272 2 ecb 7296 2 snd_seq_dummy 7428 0 crypto_blkcipher 21636 1 ecb snd_seq_oss33152 0 snd_seq_midi 11072 0 snd_rawmidi26784 1 snd_seq_midi snd_seq_midi_event 11904 2 snd_seq_oss,snd_seq_midi snd_seq54304 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event firmware_class 12544 1 iwl3945 snd_timer 25744 2 snd_pcm,snd_seq mac80211 162864 1 iwl3945 snd_seq_device 11668 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq led_class 8968 1 iwl3945 serio_raw 9860 0 i2c_i801 13596 0 snd63688 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device i2c_core 27936 1 i2c_i801 soundcore 12064 1 snd intel_agp 31728 1 iTCO_wdt
Bug#560831: marked as done (linux-2.6: make linux-headers automatically install headers for all currently installed kernel images)
Your message dated Tue, 31 May 2011 06:30:56 +0100 with message-id 1306819856.4277.130.camel@localhost and subject line Re: linux-2.6: make linux-headers automatically install headers for all currently installed kernel images has caused the Debian Bug report #560831, regarding linux-2.6: make linux-headers automatically install headers for all currently installed kernel images 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.) -- 560831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: linux-2.6 version: 2.6.32-1 severity: wishlist hi, a lot of module building issues could be solved if the linux-headers packages were to automagically install all of the corresponding headers for all of the currently installed kernel images (instead of just providing a virtual package to any set of headers). see bug #560822 for an example where this would make an impact. this will also reduce the complexity (as percieved by some users) of having to figure out which headers package is needed. best wishes, mike ---End Message--- ---BeginMessage--- On Sat, 2009-12-12 at 11:40 -0500, Michael Gilbert wrote: package: linux-2.6 version: 2.6.32-1 severity: wishlist hi, a lot of module building issues could be solved if the linux-headers packages were to automagically install all of the corresponding headers for all of the currently installed kernel images (instead of just providing a virtual package to any set of headers). see bug #560822 for an example where this would make an impact. this will also reduce the complexity (as percieved by some users) of having to figure out which headers package is needed. A maintainer script can't install another package. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Processed: retitle 628558 to Please enable CONFIG_FSCACHE_HISTOGRAM
Processing commands for cont...@bugs.debian.org: retitle 628558 Please enable CONFIG_FSCACHE_HISTOGRAM Bug #628558 [linux-2.6] Plaease enable Changed Bug title to 'Please enable CONFIG_FSCACHE_HISTOGRAM' from 'Plaease enable' thanks Stopping processing here. Please contact me if you need assistance. -- 628558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628558 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.13068199941390.transcr...@bugs.debian.org
