Bug#675922: [armel] please support dreamplug platform
On Thu, 2012-06-14 at 22:09 +0200, Arnaud Patard wrote: I've made a deb with the patches you've listed so it has dreamplug DT support (I've even added iconnect). You'll find it here: http://www.rtp-net.org/kirkwood/linux-image-3.2.0-2-kirkwood_3.2.20-2_armel.deb Can you please test it ? On install I got: Setting up linux-image-3.2.0-2-kirkwood (3.2.20-2) ... Internal Error: Could not find image (/boot/vmlinuz-3.2.0-2-kirkwood) dpkg: error processing linux-image-3.2.0-2-kirkwood (--install): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: linux-image-3.2.0-2-kirkwood and indeed: $ dpkg -c linux-image-3.2.0-2-kirkwood_3.2.20-2_armel.deb | grep \\./boot drwxr-xr-x root/root 0 2012-06-12 15:50 ./boot/ -rw-r--r-- root/root107503 2012-06-12 15:50 ./boot/config-3.2.0-2-kirkwood -rw-r--r-- root/root 1199780 2012-06-12 15:50 ./boot/System.map-3.2.0-2-kirkwood $ dpkg -c linux-image-3.2.0-2-kirkwood_3.2.20-2_armel.deb | grep vmlinu $ -- Ian Campbell One is not born a woman, one becomes one. -- Simone de Beauvoir signature.asc Description: This is a digitally signed message part
Bug#656899: mdadm: sending ioctl 1261 to a partition warnings in kernel log
Another one, confirming existence in 2.6.32-45. System has recently been upgraded from oldstable. No actual problems detected, just the messages. dorfl:~# cat /proc/version Linux version 2.6.32-5-686-bigmem (Debian 2.6.32-45) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:39:05 UTC 2012 dorfl:~# grep md /var/log/dmesg [ 4.376264] md: raid0 personality registered for level 0 [ 4.378696] md: raid1 personality registered for level 1 [ 4.395482] mdadm: sending ioctl 1261 to a partition! [ 4.395484] mdadm: sending ioctl 1261 to a partition! [ 4.395632] mdadm: sending ioctl 1261 to a partition! [ 4.395636] mdadm: sending ioctl 1261 to a partition! [ 4.413568] mdadm: sending ioctl 1261 to a partition! [ 4.413570] mdadm: sending ioctl 1261 to a partition! [ 4.413674] mdadm: sending ioctl 1261 to a partition! [ 4.413676] mdadm: sending ioctl 1261 to a partition! [ 4.413788] mdadm: sending ioctl 800c0910 to a partition! [ 4.413791] mdadm: sending ioctl 800c0910 to a partition! [ 4.417101] md: md0 stopped. [ 4.417847] md: bindsdb1 [ 4.417967] md: bindsda1 [ 4.418703] raid1: raid set md0 active with 2 out of 2 mirrors [ 4.418717] md0: detected capacity change from 0 to 4301717504 [ 4.419235] md0: [ 4.421492] md: md1 stopped. [ 4.422680] md: bindsdb2 [ 4.422803] md: bindsda2 [ 4.423530] raid1: raid set md1 active with 2 out of 2 mirrors [ 4.423544] md1: detected capacity change from 0 to 2154954752 [ 4.424045] md1: unknown partition table [ 4.432681] md: md2 stopped. [ 4.433223] md: bindsdb3 [ 4.47] md: bindsda3 [ 4.434080] raid1: raid set md2 active with 2 out of 2 mirrors [ 4.434094] md2: detected capacity change from 0 to 743696826368 [ 4.434621] md2: [ 8.113984] Adding 4200888k swap on /dev/md0. Priority:-1 extents:1 across:4200888k [ 9.392446] EXT3 FS on md1, internal journal dorfl:~# grep md /var/log/syslog Jun 19 08:38:50 dorfl kernel: [1806233.314730] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.314734] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.365106] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.365110] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.395145] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.395150] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.419005] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.419010] mdadm: sending ioctl 1261 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.451229] mdadm: sending ioctl 800c0910 to a partition! Jun 19 08:38:50 dorfl kernel: [1806233.451233] mdadm: sending ioctl 800c0910 to a partition! -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Bug#678116: linux: Please backport x86 CPU driver autoprobing from Linux 3.4 to 3.2
Source: linux Version: 3.2.20-1 Severity: normal Tags: upstream affects: cpufrequtils Dear Debian folks, »x86 CPU driver autoprobing« was merged to Linux 3.4 [1]. There's a growing number of drivers that support a specific x86 feature or CPU. Currently loading these drivers currently on a generic distribution requires various driver specific hacks and it often doesn't work. For example a common issue is not loading the SSE 4.2 accelerated CRC module: this can significantly lower the performance of Btrfs which relies on fast CRC. Another issue is loading the right CPUFREQ driver for the current CPU. Currently distributions often try all all possible driver until one sticks, which is not really a good way to do this. Linux already has autoprobing mechanisms for drivers, based in kernel notifications and udev. In this release, Linux adds auto probing support for CPU drivers, based on the x86 CPUID information, in particular based on vendor/family/model number and also based on CPUID feature bits. Code: (commit 1), 2, 3, 4, 5, 6, 7, 8, 9) This feature would also make `cpufrequtils` [2] currently shipping an init.d script for loading the CPUFREQ driver [2] obsolete for x86 based systems. Since Debian Wheezy is going to ship Linux 3.2 the recommendation gotten on systemd-devel to use a newer Linux kernel [3] do not help much. It would be great if that feature could be backported. Probably all distributions shipping Linux 3.2 are interested in this so it would be great if that could be done at the upstream stable Linux 3.2. Thanks, Paul [1] http://kernelnewbies.org/Linux_3.4#head-9df4e508cb97f4e138c590b9ccff3e0eda6cc7fc [2] http://packages.debian.org/sid/cpufrequtils [3] http://lists.freedesktop.org/archives/systemd-devel/2012-June/005514.html -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: This is a digitally signed message part
Bug#658764: free ATI driver corrupts output on Radeon HD 6310
package linux-2.6 found 658764 3.2.19-1 thanks I have installed ‘linux-image-3.2.0-2-amd64’ version 3.2.19-1 now that it is in Wheezy, and confirmed the same behaviour. -- \ “Never use a long word when there's a commensurate diminutive | `\available.” —Stan Kelly-Bootle | _o__) | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Processed: Re: Bug#658764: free ATI driver corrupts output on Radeon HD 6310
Processing commands for cont...@bugs.debian.org: package linux-2.6 Limiting to bugs with field 'package' containing at least one of 'linux-2.6' Limit currently set to 'package':'linux-2.6' found 658764 3.2.19-1 Bug #658764 [linux-2.6] linux-image-3.1.0-1-amd64: free ATI driver corrupts output on Radeon HD 6310 Bug #646306 [linux-2.6] corrupted display on Asus 1215b (device [1002:9802]) There is no source info for the package 'linux-2.6' at version '3.2.19-1' with architecture '' Unable to make a source version for version '3.2.19-1' Marked as found in versions 3.2.19-1. Marked as found in versions 3.2.19-1. thanks Stopping processing here. Please contact me if you need assistance. -- 646306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646306 658764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658764 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.134010426417371.transcr...@bugs.debian.org
Processed: reassign 664813 to src:linux, reassign 678116 to src:linux, forcibly merging 664813 678116
Processing commands for cont...@bugs.debian.org: reassign 664813 src:linux Bug #664813 [src:linux-2.6] Please use the ondemand cpufreq governor by default (CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND) Bug reassigned from package 'src:linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #664813 to the same values previously set Ignoring request to alter fixed versions of bug #664813 to the same values previously set reassign 678116 src:linux 3.2.20-1 Bug #678116 [src:linux] linux: Please backport x86 CPU driver autoprobing from Linux 3.4 to 3.2 Ignoring request to reassign bug #678116 to the same package Bug #678116 [src:linux] linux: Please backport x86 CPU driver autoprobing from Linux 3.4 to 3.2 Ignoring request to alter found versions of bug #678116 to the same values previously set forcemerge 664813 678116 Bug #664813 [src:linux] Please use the ondemand cpufreq governor by default (CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND) Bug #664813 [src:linux] Please use the ondemand cpufreq governor by default (CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND) Marked as found in versions linux/3.2.20-1. Added tag(s) upstream. Bug #678116 [src:linux] linux: Please backport x86 CPU driver autoprobing from Linux 3.4 to 3.2 Severity set to 'wishlist' from 'normal' Added tag(s) pending. Merged 664813 678116 thanks Stopping processing here. Please contact me if you need assistance. -- 664813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664813 678116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678116 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.134010648028590.transcr...@bugs.debian.org
Bug#571251: base: hp pavillon won't start (30% success)
This is said to be fixed by the change: commit 9d1ac34ec3a67713308ae0883c3359c557f14d17 Author: Larry Finger larry.fin...@lwfinger.net Date: Fri May 14 22:08:58 2010 -0500 ssb: Handle alternate SSPROM location which was included in Linux 2.6.32.18 and Debian's package version 2.6.32-20. Do you still see the problem, or do you agree that it is now fixed? Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault. signature.asc Description: This is a digitally signed message part
Bug#678110: [squeeze] LSI 926x w/ CacheCade 2.0 Pro feature activated requires updated megaraid_sas driver module
Hi Thomas, Thomas Baetzler wrote: We've recently decided to try LSI's CacheCade Pro 2.0 software feature package on some systems utilizing their Megaraid 9260 controller. This feature package implements tiered storage that utilizes SSD drives as additional non-volatile cache. It has been my experience that enabling this feature with the standard Debian kernel leads to filesystem corruption and data loss. Oh, dear. Do you happen to know what change fixed this? [...] I would like to ask that the current stable kernel package is upgraded to the newer driver version. If you need me to bring this to the attention of the upstream maintainer, please let me know. Currently we are using the stock driver from 2.6.32.y, so notifying upstream would be useful, yes. Please cc either me or this bug log when doing so so we can track it. Thanks much for the heads up, 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/20120619130658.GA7766@burratino
Bug#678110: [squeeze] LSI 926x w/ CacheCade 2.0 Pro feature activated requires updated megaraid_sas driver module
Hi again, Jonathan Nieder wrote: Currently we are using the stock driver from 2.6.32.y, so notifying upstream would be useful, yes. Please cc either me or this bug log when doing so so we can track it. Correction: we have the following commits on top of 2.6.32.y: c35188377f12 Add poll mechanism to megaraid sas driver 72c4fd36dc7f add sysfs for AEN polling 879111224d07 Add new megaraid SAS 2 controller support to the driver 7bebf5c79cb6 allocate the application cmds to sas2 controller 0c79e681eef1 Fix the fix for fw hang caused by megaraid sas application And these add support for your controller. So we should probably do a little more investigation before notifying upstream. Can you try a 3.x.y kernel from sid, experimental, or squeeze-backports? The only packages needed for this test from outside squeeze are the kernel image itself, linux-base, and initramfs-tools. 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/20120619131148.GB7766@burratino
Bug#678071: linux-image-3.4-trunk-686-pae: Kernel 3.4 does not include CONFIG_MOUSE_SYNAPTICS_USB
I can enable it right now, That would be very welcome, yes. but the next stable release (Debian 7.0, 'wheezy') will use Linux 3.2. Yes, I know. Do you want it added to that as well? That would be super awesome, but the synaptics-usb module was only added to the 3.4 kernel. It looks like it wouldn't be too hard to do. I guess you're referring to backporting it to the 3.2 kernel. I'd be very happy if you did, but I won't hold it against you if you don't ;-) Thank you, Stefan -- 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/jwvpq8vzbmt.fsf-monnier+in...@gnu.org
Bug#678110: [squeeze] LSI 926x w/ CacheCade 2.0 Pro feature activated requires updated megaraid_sas driver module
Thomas Baetzler wrote: We've recently decided to try LSI's CacheCade Pro 2.0 software feature package on some systems utilizing their Megaraid 9260 controller. This feature package implements tiered storage that utilizes SSD drives as additional non-volatile cache. It has been my experience that enabling this feature with the standard Debian kernel leads to filesystem corruption and data loss. A kernel log that demonstrates this happening is attached to this bug report. It was created by booting from an older GRML live cd but I can vouch for the same thing happening with a plain Squeeze install. I have since built a new kernel module using dkms from LSI's own updated driver for Ubuntu Lucid Lynx available at http://www.lsi.com/downloads/Public/MegaRAID%20Common%20Files/Ubuntu_10.04_LTS_05.30.zip. More details: The module version was updated from 05.29-rc1 to 05.34-rc1 in mainline in v2.6.39-rc1~440^2~19. 3.0.y has 05.38-rc1. 2.6.34.y has 04.17.1-rc1. 2.6.32.y has 04.01. Debian squeeze has 04.01 + some, but not all, changes up to 04.12. I assume 3.0.y works fine. I suppose what would be most interesting is to try 2.6.34.y; if that doesn't work, we can work with upstream to get it working (and if it does work, we have a much narrower range to search for the fix). Instructions: 0. prerequisites: apt-get install git build-essential 1. get the kernel history if you do not already have it: git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2. add point releases: cd linux git remote add stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git git fetch stable 3. configure, build, test: git checkout stable/linux-2.6.34.y cp /boot/config-$(uname -r) .config; # current configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root reboot ... test test test ... Sorry for the slow start, 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/20120619140017.GD7766@burratino
Processed: Re: st - slow tape read/write rate
Processing commands for cont...@bugs.debian.org: found 675934 linux-2.6/2.6.32-45 Bug #675934 [linux-2.6] st - slow tape read/write rate Marked as found in versions linux-2.6/2.6.32-45. End of message, stopping processing here. Please contact me if you need assistance. -- 675934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675934 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.13401257376735.transcr...@bugs.debian.org
Processed: Re: linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out
Processing commands for cont...@bugs.debian.org: found 526983 linux-2.6/2.6.35-1~experimental.1 Bug #526983 [linux-2.6] linux-image-2.6.29-1-amd64: NETDEV WATCHDOG: eth0 (r8169): transmit timed out Bug #528362 [linux-2.6] linux-image-2.6.29-2-686: r8169 hangs when your transmission speed is really high. Marked as found in versions linux-2.6/2.6.35-1~experimental.1. Marked as found in versions linux-2.6/2.6.35-1~experimental.1. End of message, stopping processing here. Please contact me if you need assistance. -- 526983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526983 528362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528362 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.134012726415483.transcr...@bugs.debian.org
Bug#664767: Brcmsmac driver woes, possible regression?
2012/6/11 Camaleón noela...@gmail.com: Mmmm, this is something I can still try (an earlier working kernel). As per my comment #167 [1], candidates could be lower versions starting from 3.2.4-1, which according to the snapshot [2] could be: 3.2.2-1 (source: linux-2.6 3.2.2-1) 3.2.1-2 (source: linux-2.6 3.2.1-2) 3.2.1-1 (source: linux-2.6 3.2.1-1) Will do on these these -time permitting- and report here. Update: I've been running kernel 3.2.2-1 over 4 days (since last Saturday until today) and still haven't experienced any disconnection. Not sure if this can be of any help because of the brief testing time-frame but I used to get a reconnect once a day with the other kernels I've been trying... Greetings, -- Camaleón -- 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/CAKprTDHYMyDwvxA52Z9zxP75ZUY5ÿcgptzzg9zxtxrefj...@mail.gmail.com
Bug#664767: Brcmsmac driver woes, possible regression?
Camaleón wrote:
Update: I've been running kernel 3.2.2-1 over 4 days (since last
Saturday until today) and still haven't experienced any disconnection.
Interesting. I wonder if the workaround in f96b08a7e6f6 (brcmsmac:
fix tx queue flush infinite loop, 2012-01-17) has too short a timeout
and is backfiring.
How about this patch, for 3.2.y kernels? I suggest the following
steps for testing:
0. prerequisites:
apt-get install git build-essential
1. get the kernel history, if you do not already have it:
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
2. add point releases:
cd linux
git remote add stable \
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch stable
3. configure, build, test:
git checkout stable/linux-3.2.y
cp /boot/config-$(uname -r) .config; # current configuration
scripts/config --disable DEBUG_INFO
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -jnum for parallel build
dpkg -i ../name of package; # as root
reboot
... test test test ...
Hopefully it reproduces the disconnection. So
4. try the patch:
cd linux
git revert f96b08a7e6f6
make deb-pkg; # maybe with -j4
dpkg -i ../name of package; # as root
reboot
... test test test ...
From: Jonathan Nieder jrnie...@gmail.com
Date: Tue, 19 Jun 2012 12:57:27 -0500
Subject: Revert brcmsmac: fix tx queue flush infinite loop
This reverts commit f96b08a7e6f69c0f0a576554df3df5b1b519c479.
Just testing something, nothing deeper to see here.
---
drivers/net/wireless/brcm80211/brcmsmac/main.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/net/wireless/brcm80211/brcmsmac/main.c
b/drivers/net/wireless/brcm80211/brcmsmac/main.c
index 833cbefcbfd2..364200cfb21c 100644
--- a/drivers/net/wireless/brcm80211/brcmsmac/main.c
+++ b/drivers/net/wireless/brcm80211/brcmsmac/main.c
@@ -8225,21 +8225,13 @@ int brcms_c_get_curband(struct brcms_c_info *wlc)
void brcms_c_wait_for_tx_completion(struct brcms_c_info *wlc, bool drop)
{
- int timeout = 20;
-
/* flush packet queue when requested */
if (drop)
brcmu_pktq_flush(wlc-pkt_queue-q, false, NULL, NULL);
/* wait for queue and DMA fifos to run dry */
- while (!pktq_empty(wlc-pkt_queue-q) || brcms_txpktpendtot(wlc) 0) {
+ while (!pktq_empty(wlc-pkt_queue-q) || brcms_txpktpendtot(wlc) 0)
brcms_msleep(wlc-wl, 1);
-
- if (--timeout == 0)
- break;
- }
-
- WARN_ON_ONCE(timeout == 0);
}
void brcms_c_set_beacon_listen_interval(struct brcms_c_info *wlc, u8 interval)
--
1.7.11.rc3
Bug#647004: marked as done (r8169: connection is not stable, transmit queue 0 timed out)
Your message dated Tue, 19 Jun 2012 13:26:56 -0500 with message-id 20120619182656.GA19642@burratino and subject line Re: Realtek Ethernet adapters (r8169 driver) has caused the Debian Bug report #647004, regarding r8169: connection is not stable, transmit queue 0 timed out 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.) -- 647004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-34 Severity: important The r8169 driver in this kernel version is missing important bug fixes for the RTL8102E and RTL8168DP. 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--- ---BeginMessage--- Hi Loïc, Jonathan Nieder wrote: Jonathan Nieder wrote: Can you attach dmesg output from booting up and loading the r8169 driver? Ping. Did you get a chance to try this? Closing due to lack of response. If you have any more information, please don't hesitate to let us know, though. ---End Message---
Bug#642025: (r8169): transmit queue 0 timed out
Hi Andrei, Андрей Василишин wrote: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Sorry for the long silence. Did this happen only once, or was it reproducible? If the latter, is it still reproducible? What kernel are you using these days? Thanks for writing, 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/20120619191035.GA19914@burratino
Processed: Re: wireless brcms_c_wait_for_tx_completion warning
Processing commands for cont...@bugs.debian.org: tags 672891 - pending Bug #672891 [linux-2.6] brcmsmac wireless brcms_c_wait_for_tx_completion warning Removed tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 672891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672891 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.134013404618633.transcr...@bugs.debian.org
Bug#669314: NFS: kernel forces trailing slash for export in /proc/self/mounts
Hi Alexander Viro et al,
This is an escalation of Debian Bug #669314 http://bugs.debian.org/669314,
which I will
re-elaborate in this email for your convenience.
You committed a change to the way the linux kernel reports NFS mounts - now
with a
trailing slash for the remote export (among other changes). The change happened
here:
commit c7f404b40a3665d9f4e9a927cc5c1ee0479ed8f9
Author: Al Viro v...@zeniv.linux.org.uk
Date: Wed Mar 16 06:59:40 2011 -0400
vfs: new superblock methods to override /proc/*/mount{s,info}
a) -show_devname(m, mnt) - what to put into devname columns in mounts,
mountinfo and mountstats
b) -show_path(m, mnt) - what to put into relative path column in
mountinfo
Leaving those NULL gives old behaviour. NFS switched to using those.
Signed-off-by: Al Viro v...@zeniv.linux.org.uk
The problematic behavior is that NFS exports now have a trailing slash in
/proc/self/mounts.
This still seems to be the case in newer kernels, for example in Debian's
3.3.2-1~experimental.1.
and HEAD in Linus Torvalds' master branch, presently commit:
02edf6abe01610a5fb379df442de3c837ad99467
I believe it is/was convention to leave a trailing slash off of the nfs export
in /etc/fstab, e.g.:
nfsserver:/srv/ubuntu-32 /mnt/ubuntu-32 nfs
ro,nfsvers=3,soft,intr,tcp,nodev,noatime,nosuid,rsize=32768,wsize=32768
and I'd also expect the same in /proc/self/mounts
Expected Result:
I expect /proc/self/mounts to show (notice no trailing slash on the export):
nfsserver:/srv/ubuntu-32 /mnt/ubuntu-32 nfs
ro,nosuid,nodev,noatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=198.202.1.1,mountvers=3,mountport=41576,mountproto=tcp,local_lock=none,addr=198.202.1.1
0 0
Actual Result:
But instead in /proc/self/mounts I get (notice the trailing slash):
nfsserver:/srv/ubuntu-32/ /mnt/ubuntu-32 nfs
ro,nosuid,nodev,noatime,vers=3,rsize=32768,wsize=32768,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=198.202.1.1,mountvers=3,mountport=41576,mountproto=tcp,local_lock=none,addr=198.202.1.1
0 0
Rammifications:
This simple change has a lot of implications because lots of things parse
/etc/fstab and /proc/self/mounts, for example system configuration tools
and mount.nfs and umount.nfs.
If you use the former convention and try to umount an export on a newer
kernel it will fail:
user@hostname:/proc/self$ sudo umount.nfs nfsserver:/srv/ubuntu-32
umount.nfs: nfsserver:/srv/ubuntu-32: not found
And if you run sudo mount -va, mount will not recognize that the fstab mounts
have already been mounted; mounting all mounts twice on the same mount point.
This quickly gets messy.
If there is a new convention to display the trailing slash, we need to update
our tools to handle this change. If there is not a new convention, I'd argue
this is a bug.
So is this a new convention or not? What is the appropriate way for Debian to
move forward?
Thanks,
Chris Hiestand
--
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/8f8193bd-84c6-4905-8789-de7eb2579...@salk.edu
Bug#678215: linux-image-3.2.0-2-: USB mouse not recognized after resuming from suspend to RAM
Package: linux-image-3.2.0-2-686-pae Version: 3.2.20-1 Severity: important Dear Debian folks, after replacing a broken PS/2 mouse, which worked fine before that, with an USB mouse $ lsusb # output from after the resume and replugged Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 046d:c30f Logitech, Inc. Logicool HID-Compliant Keyboard (106 key) Bus 002 Device 003: ID 058f:9254 Alcor Micro Corp. Hub Bus 003 Device 003: ID 1241:1122 Belkin Typhoon Stream Optical Mouse USB+PS/2 the mouse is not working after resuming from suspend to RAM. Replugging the mouse works although that is quite inconvenient. $ dmesg | grep -i usb [1.526486] usbcore: registered new interface driver usbfs [1.526515] usbcore: registered new interface driver hub [1.531004] usbcore: registered new device driver usb [1.531600] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.531688] ehci_hcd :00:13.5: new USB bus registered, assigned bus number 1 [1.531720] ehci_hcd :00:13.5: applying AMD SB600/SB700 USB freeze workaround [1.540144] ehci_hcd :00:13.5: USB 2.0 started, EHCI 1.00 [1.540202] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [1.540205] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.540208] usb usb1: Product: EHCI Host Controller [1.540210] usb usb1: Manufacturer: Linux 3.2.0-2-686-pae ehci_hcd [1.540213] usb usb1: SerialNumber: :00:13.5 [1.540349] hub 1-0:1.0: USB hub found [1.540878] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.540939] ohci_hcd :00:13.0: new USB bus registered, assigned bus number 2 [1.600050] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [1.600056] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.600059] usb usb2: Product: OHCI Host Controller [1.600062] usb usb2: Manufacturer: Linux 3.2.0-2-686-pae ohci_hcd [1.600064] usb usb2: SerialNumber: :00:13.0 [1.600228] hub 2-0:1.0: USB hub found [1.603453] ohci_hcd :00:13.1: new USB bus registered, assigned bus number 3 [1.660039] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [1.660042] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.660045] usb usb3: Product: OHCI Host Controller [1.660047] usb usb3: Manufacturer: Linux 3.2.0-2-686-pae ohci_hcd [1.660050] usb usb3: SerialNumber: :00:13.1 [1.660210] hub 3-0:1.0: USB hub found [1.660571] ohci_hcd :00:13.2: new USB bus registered, assigned bus number 4 [1.720027] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [1.720031] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.720034] usb usb4: Product: OHCI Host Controller [1.720036] usb usb4: Manufacturer: Linux 3.2.0-2-686-pae ohci_hcd [1.720039] usb usb4: SerialNumber: :00:13.2 [1.720200] hub 4-0:1.0: USB hub found [1.720309] ohci_hcd :00:13.3: new USB bus registered, assigned bus number 5 [1.780066] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [1.780069] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.780072] usb usb5: Product: OHCI Host Controller [1.780074] usb usb5: Manufacturer: Linux 3.2.0-2-686-pae ohci_hcd [1.780076] usb usb5: SerialNumber: :00:13.3 [1.780246] hub 5-0:1.0: USB hub found [1.780584] ohci_hcd :00:13.4: new USB bus registered, assigned bus number 6 [1.840051] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 [1.840054] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.840057] usb usb6: Product: OHCI Host Controller [1.840059] usb usb6: Manufacturer: Linux 3.2.0-2-686-pae ohci_hcd [1.840062] usb usb6: SerialNumber: :00:13.4 [1.840220] hub 6-0:1.0: USB hub found [2.228017] usb 2-1: new low-speed USB device number 2 using ohci_hcd [2.401061] usb 2-1: New USB device found, idVendor=046d, idProduct=c30f [2.401066] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Bug#598144: Probably reproduced
I probably reproduced this after testing a wheezy daily on an ASUS Z71A using an RT2500. I got this error message and several others. It happened as soon as I logged in to the minimal console install, with tty1 full of such messages. The laptop was 1 meter away from the router. The image was http://cdimage.debian.org/cdimage/daily-builds/daily/20120619-5/i386/iso-cd/debian-testing-i386-netinst.iso which uses Linux 3.2. I used the 486 image. When I search, I see lots of hits related to this error message, but few recently (after 2010). For example, https://bugzilla.redhat.com/show_bug.cgi?id=626818 Unfortunately, I was just installing to test another bug and I won't be using that install - in fact, I already lost it. I may retest at one point, and investigate more if this persists when testing's Linux becomes current again. -- 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/4fe11427.6000...@gmail.com
Processed: tagging 576723
Processing commands for cont...@bugs.debian.org: tags 576723 - experimental Bug #576723 [linux-2.6] linux-2.6: [2.6.33] mising rt2860sta; rt2800 not suitable for replacement Removed tag(s) experimental. thanks Stopping processing here. Please contact me if you need assistance. -- 576723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576723 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.134015228415762.transcr...@bugs.debian.org
Bug#576723: marked as done (linux-2.6: [2.6.33] mising rt2860sta; rt2800 not suitable for replacement)
Your message dated Wed, 20 Jun 2012 01:35:23 +0100 with message-id 1340152523.6871.83.ca...@deadeye.wl.decadent.org.uk and subject line Re: linux-2.6: [2.6.33] mising rt2860sta; rt2800 not suitable for replacement has caused the Debian Bug report #576723, regarding linux-2.6: [2.6.33] mising rt2860sta; rt2800 not suitable for replacement 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.) -- 576723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.33-1~experimental.2, 2.6.33-1~experimental.4 Severity: normal Tags: experimental user: debian-eeepc-de...@lists.alioth.debian.org usertag: features usertag: 901 Hi, The 2.6.33 linux-image in experimental removed the rt2860sta driver from staging and it seems to offer the rt2800 driver as a replacement. The later doesn't work for me, however. I can't associate with my access point using WPA2. Hardware is Asus EeePC 901 (details in the info below). Would it be possible to restore rt2860sta? -- Package-specific info: ** Version: Linux version 2.6.33-2-686 (Debian 2.6.33-1~experimental.4) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Mar 18 07:30:30 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.33-2-686 root=UUID=4e436c23-73dc-44f1-85be-ffc868c92769 ro quiet i915.modeset=1 acpi_osi=Linux rfkill.default_state=1 ** Not tainted ** Kernel log: [3.497662] usb usb4: Product: UHCI Host Controller [3.497666] usb usb4: Manufacturer: Linux 2.6.33-2-686 uhci_hcd [3.497671] usb usb4: SerialNumber: :00:1d.2 [3.504715] hub 4-0:1.0: USB hub found [3.504729] hub 4-0:1.0: 2 ports detected [3.504849] uhci_hcd :00:1d.3: PCI INT D - GSI 16 (level, low) - IRQ 16 [3.504866] uhci_hcd :00:1d.3: setting latency timer to 64 [3.504873] uhci_hcd :00:1d.3: UHCI Host Controller [3.504893] uhci_hcd :00:1d.3: new USB bus registered, assigned bus number 5 [3.504951] uhci_hcd :00:1d.3: irq 16, io base 0xdc00 [3.505035] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [3.505042] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.505047] usb usb5: Product: UHCI Host Controller [3.505052] usb usb5: Manufacturer: Linux 2.6.33-2-686 uhci_hcd [3.505057] usb usb5: SerialNumber: :00:1d.3 [3.509041] hub 5-0:1.0: USB hub found [3.509054] hub 5-0:1.0: 2 ports detected [3.533294] eeepc_laptop: Eee PC Hotkey Driver [3.533313] eeepc_laptop: Hotkey init flags 0x41 [3.672083] usb 1-8: new high speed USB device using ehci_hcd and address 2 [3.820149] [drm] Initialized drm 1.1.0 20060810 [3.949161] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [3.949171] i915 :00:02.0: setting latency timer to 64 [3.993935] [drm] set up 7M of stolen space [4.124233] rt2800pci :01:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [4.124247] rt2800pci :01:00.0: setting latency timer to 64 [4.226869] phy0: Selected rate control algorithm 'minstrel' [4.228381] Registered led device: rt2800pci-phy0::radio [4.228478] Registered led device: rt2800pci-phy0::assoc [4.228574] Registered led device: rt2800pci-phy0::quality [4.233376] usb 1-8: New USB device found, idVendor=05e3, idProduct=0505 [4.233384] usb 1-8: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [4.233390] usb 1-8: Product: USB 2.0 Camera [4.264156] elantech.c: assuming hardware version 2, firmware version 2.48 [4.367916] elantech.c: Synaptics capabilities query result 0x00, 0x02, 0x64. [4.372520] [drm] initialized overlay support [4.641088] Linux video capture interface: v2.00 [4.660808] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (05e3:0505) [4.829636] [drm:edid_is_valid] *ERROR* EDID checksum is invalid, remainder is 219 [4.829705] [drm:edid_is_valid] *ERROR* Raw EDID: [4.829765] 300 ff ff ff ff ff ff 00 06 af 20 10 00 00 00 00 .. . [4.829771] 301 12 01 03 80 13 0b 78 0a fa 56 92 56 54 98 24 ...x..V.VT.$ [4.829777] 31a 4f 54 00 00 00 01 01 01 01 01 01 01 01 01 01 .OT. [4.829783] 301 01 01 01 01 01 b0 13 00 40 41 58 19 20 18 88 .@AX. .. [4.829788] 303 01 c3 71 00 00 00 18 00 00 00 0f 00 00 00 00 ...q [4.829794] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [4.829800] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [4.829805] 300 00 00 00 00 00 00 00 00
Bug#677273: [PATCH] staging: zsmalloc: Finish conversion to a separate module
ZSMALLOC is tristate, but the code has no MODULE_LICENSE and since it
depends on GPL-only symbols it cannot be loaded as a module. This in
turn breaks zram which now depends on it. I assume it's meant to be
Dual BSD/GPL like the other z-stuff.
There is also no module_exit, which will make it impossible to unload.
Add the appropriate module_init and module_exit declarations suggested
by comments.
Reported-by: Christian Ohm chr@gmx.net
References: http://bugs.debian.org/677273
Cc: sta...@vger.kernel.org # v3.4
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
This is compile-tested only.
Ben.
drivers/staging/zsmalloc/zsmalloc-main.c | 33 +++---
1 file changed, 7 insertions(+), 26 deletions(-)
diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c
b/drivers/staging/zsmalloc/zsmalloc-main.c
index 4496737..8ded9a0 100644
--- a/drivers/staging/zsmalloc/zsmalloc-main.c
+++ b/drivers/staging/zsmalloc/zsmalloc-main.c
@@ -425,12 +425,6 @@ static struct page *find_get_zspage(struct size_class
*class)
}
-/*
- * If this becomes a separate module, register zs_init() with
- * module_init(), zs_exit with module_exit(), and remove zs_initialized
-*/
-static int zs_initialized;
-
static int zs_cpu_notifier(struct notifier_block *nb, unsigned long action,
void *pcpu)
{
@@ -489,7 +483,7 @@ fail:
struct zs_pool *zs_create_pool(const char *name, gfp_t flags)
{
- int i, error, ovhd_size;
+ int i, ovhd_size;
struct zs_pool *pool;
if (!name)
@@ -516,28 +510,9 @@ struct zs_pool *zs_create_pool(const char *name, gfp_t
flags)
}
- /*
-* If this becomes a separate module, register zs_init with
-* module_init, and remove this block
- */
- if (!zs_initialized) {
- error = zs_init();
- if (error)
- goto cleanup;
- zs_initialized = 1;
- }
-
pool-flags = flags;
pool-name = name;
- error = 0; /* Success */
-
-cleanup:
- if (error) {
- zs_destroy_pool(pool);
- pool = NULL;
- }
-
return pool;
}
EXPORT_SYMBOL_GPL(zs_create_pool);
@@ -753,3 +728,9 @@ u64 zs_get_total_size_bytes(struct zs_pool *pool)
return npages PAGE_SHIFT;
}
EXPORT_SYMBOL_GPL(zs_get_total_size_bytes);
+
+module_init(zs_init);
+module_exit(zs_exit);
+
+MODULE_LICENSE(Dual BSD/GPL);
+MODULE_AUTHOR(Nitin Gupta ngu...@vflare.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/1340155871.6871.93.ca...@deadeye.wl.decadent.org.uk
Processed: tagging 677273
Processing commands for cont...@bugs.debian.org: tags 677273 + pending Bug #677273 [linux-2.6] zcache and friends stopped working as modules in 3.4 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 677273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677273 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.13401561763498.transcr...@bugs.debian.org
Bug#671860: marked as done (Disk freeze on 2.6.32 and 3.x kernels: blkback blocked for more than 120 seconds)
Your message dated Wed, 20 Jun 2012 02:42:19 +0100 with message-id 1340156539.6871.95.ca...@deadeye.wl.decadent.org.uk and subject line Re: Disk freeze on 2.6.32 and 3.x kernels: blkback blocked for more than 120 seconds has caused the Debian Bug report #671860, regarding Disk freeze on 2.6.32 and 3.x kernels: blkback 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.) -- 671860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-3.2.0-0.bpo.1-amd64 Version: 3.2.1-2~bpo60+1 Severity: grave Actually, all kernels from 2.6.32 to (at least) 3.2.1 seem to be affected. I run two identical machines: Debian6 AMD64, raid1 software mirror for data disks, on /dev/mdx is lvm2 configured. The /dev/mapper devices are synced to the other machine using drbd. These drb-devices are used for virtual machines. Sometimes, one machine degrades. Apparently the mdX_resync process and blkback collide. Until now, I only observed this on Windows HVM used disk devices. Details: A DomU running Windows Server 2003 (usually) or 2008R2 Server (rare) (both with GPLPV, but different versions) get stuck accessing their harddisk provided by xen from the drb device. Other linux domUs on the same machine continue to work. The dom0 kern.log shows that the blkback driver is blocked for more than 120 seconds. The windows domU can't be stopped regularly with xm shutdown or xm destroy. Graceful shutdown of the xen host isn't possible either; only echo b /proc/sysrq-trigger is possible. This problem reappears every few weeks, usually in the night Saturday to Sunday. The Windows domUs worked previously on older xen hosts with no problem, then were moved to the current machine pair with Debian 6 with Xen; all versions from debian-stable i.e. kernel 2.6.32 and xen 4.0. After the problem arose, I gradually updated the versions (xen 4.0-4.1, then kernel 2.6.32-3.1-3.2). Currently, both machines run linux-image-3.2.0-0.bpo.1-amd64 and xen-hypervisor-4.1-amd64 4.1.1-1 incl xen-tools-4.1; problem persists. Today I realized that the main trigger for the failure seems the periodic check from /etc/cron.d/mdadm, which checks on the first day of a month at 0:57. Last month, the check didn't trigger the error, but yesterday it hit me again after 58d uptime. For now, I hot-fixed this by setting /etc/default/mdadm to autocheck=false, but other access patterns seem to trigger the failure too. Here's a snippet from the kern.log; this pattern will reapperar every 2 minutes until hard-resetted. May 6 01:06:24 lady kernel: [4979042.044157] INFO: task blkback.12.hdb:16636 blocked for more than 120 seconds. May 6 01:06:24 lady kernel: [4979042.044255] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. May 6 01:06:24 lady kernel: [4979042.044345] blkback.12.hdb D 880002c817e0 0 16636 2 0x May 6 01:06:24 lady kernel: [4979042.044355] 880002c817e0 0246 8800 8160d020 May 6 01:06:24 lady kernel: [4979042.044366] 00013540 880007dbffd8 880007dbffd8 00013540 May 6 01:06:24 lady kernel: [4979042.044375] 880002c817e0 880007dbe010 81013949 000107cacc78 May 6 01:06:24 lady kernel: [4979042.044385] Call Trace: May 6 01:06:24 lady kernel: [4979042.044398] [81013949] ? sched_clock+0x5/0x8 May 6 01:06:24 lady kernel: [4979042.044423] [a0103673] ? wait_barrier+0x94/0xcd [raid1] May 6 01:06:24 lady kernel: [4979042.044432] [81045e84] ? try_to_wake_up+0x190/0x190 May 6 01:06:24 lady kernel: [4979042.01] [a0104a94] ? make_request+0x11d/0x1689 [raid1] May 6 01:06:24 lady kernel: [4979042.044454] [a010cc7b] ? __split_and_process_bio+0x520/0x532 [dm_mod] May 6 01:06:24 lady kernel: [4979042.044463] [810068e5] ? xen_force_evtchn_callback+0x9/0xa May 6 01:06:24 lady kernel: [4979042.044469] [81006f92] ? check_events+0x12/0x20 May 6 01:06:24 lady kernel: [4979042.044481] [a00d7a9b] ? md_make_request+0xbe/0x1b1 [md_mod] May 6 01:06:24 lady kernel: [4979042.044490] [8135ab25] ? _raw_spin_unlock_irqrestore+0x10/0x11 May 6 01:06:24 lady kernel: [4979042.044498] [811a807e] ? generic_make_request+0x8e/0xcd May 6 01:06:24 lady kernel: [4979042.044504] [811a8196] ? submit_bio+0xd9/0xf7 May 6 01:06:24 lady kernel: [4979042.044512] [8112caf5] ? bio_alloc_bioset+0x44/0xb3 May 6
Bug#677273: [PATCH] staging: zsmalloc: Finish conversion to a separate module
(+cc: devel@driverdev) Hi Ben, Ben Hutchings wrote: ZSMALLOC is tristate, but the code has no MODULE_LICENSE and since it depends on GPL-only symbols it cannot be loaded as a module. This in turn breaks zram which now depends on it. I assume it's meant to be Dual BSD/GPL like the other z-stuff. Yep, the opening comment in the file says so. There is also no module_exit, which will make it impossible to unload. Add the appropriate module_init and module_exit declarations suggested by comments. Reported-by: Christian Ohm chr@gmx.net I sent a similar patch + fixup last week[*]. Yours has a clearer description. The only other difference aside from reordering lines is that I marked zs_init as __init and zs_exit as __exit. [...] This is compile-tested only. Someone using zram tested last week's patch (which is almost identical) against 3.4.y and let me know it worked by private email, but I don't have permission to name that person. So for what it's worth, Reviewed-by: Jonathan Nieder jrnie...@gmail.com Thanks. Jonathan [*] http://driverdev.linuxdriverproject.org/pipermail/devel/2012-June/027377.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/20120620014605.GB2961@burratino
Bug#677273: [PATCH] staging: zsmalloc: Finish conversion to a separate module
On Tue, 2012-06-19 at 20:46 -0500, Jonathan Nieder wrote: (+cc: devel@driverdev) Hi Ben, Ben Hutchings wrote: ZSMALLOC is tristate, but the code has no MODULE_LICENSE and since it depends on GPL-only symbols it cannot be loaded as a module. This in turn breaks zram which now depends on it. I assume it's meant to be Dual BSD/GPL like the other z-stuff. Yep, the opening comment in the file says so. There is also no module_exit, which will make it impossible to unload. Add the appropriate module_init and module_exit declarations suggested by comments. Reported-by: Christian Ohm chr@gmx.net I sent a similar patch + fixup last week[*]. Yours has a clearer description. The only other difference aside from reordering lines is that I marked zs_init as __init and zs_exit as __exit. Ah, but you made the mistake of marking it 'RFC'. :-) [...] This is compile-tested only. Someone using zram tested last week's patch (which is almost identical) against 3.4.y and let me know it worked by private email, but I don't have permission to name that person. So for what it's worth, Reviewed-by: Jonathan Nieder jrnie...@gmail.com Thanks. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Bug#675934: st - slow tape read/write rate
Yury O. Tabolin wrote: Hi, so, I tried the kernels. First I tried to upgrade kernel to 2.6.32-45. Nothing has changed, the rate is same low. Good, thanks for confirming. [...] Then I installed 3.2.18-1~bpo60+1 kernel from squeeze-backports. Segfault disappeared. The rate increased slightly, but still Ok, so now there are two different tasks to work on: i) applying the improvement that eliminated the segfault to squeeze ii) fixing the rest of the speed regression relative to etch for future kernels. For (i): could you try 2.6.37-2 and 2.6.38-rc6 from snapshot.debian.org and let us know how it goes? For (ii): if you get a change to try 3.4.y from experimental, that would be very useful. The only packages from outside squeeze aside from the kernel itself that should be needed to test it are linux-base and initramfs-tools, both of which can be found in squeeze-backports. If the speed regression is still present, we can get help from upstream. If it's fixed, we can try to find the patch that fixes it and apply it to the wheezy and squeeze kernels. So either result is progress. Thanks again 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/20120620032255.GC2961@burratino
Bug#598144: rt2500pci: very low transfers and link quality (Re: Probably reproduced)
Hi Filipus, Filipus Klutiero wrote: I probably reproduced this after testing a wheezy daily on an ASUS Z71A using an RT2500. I got this error message and several others. Ok, now I finally got a chance to look up the bug. So do you mean that transfers were very slow and you got the message phy0 - rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16). ? Thanks much for that, if so. [...] Unfortunately, I was just installing to test another bug and I won't be using that install - in fact, I already lost it. I may retest at one point, and investigate more if this persists when testing's Linux becomes current again. Filling in between the lines: does this mean you have another network adapter you are using instead or that you are avoiding the bug some other way (for example by avoiding that machine altogether)? 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/20120620033443.GA4112@burratino
