Firmware-nonfree in wheezy-backports
On Sat, Aug 02, 2014 at 09:11:02PM +0300, Touko Korpela wrote: Could you update wheezy backports version of firmware-nonfree too (now at version 0.41 while jessie/sid has 0.43)? bpo version is still 0.41 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140819082013.GA3227@tiikeri
Re: linux_3.14.13-2~bpo70+1_multi.changes ACCEPTED into wheezy-backports, wheezy-backports
Could you update wheezy backports version of firmware-nonfree too (now at version 0.41 while jessie/sid has 0.43)? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140802181102.GA4894@tiikeri
Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
On Sun, Jul 14, 2013 at 06:32:05PM +0200, Moritz Mühlenhoff wrote: Version: 3.9-1 On Fri, Jul 12, 2013 at 11:19:56AM +0300, Martin-Éric Racine wrote: It still does with 3.2 in stable, but not with 3.9 in testing. Closing with that version, then. No such version (3.9-1) was uploaded, 3.9.4-1 was first 3.9 upload. -- 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/20130714181954.GA3982@lisko
Bug#701953: closed by Michael Prokop m...@debian.org (Bug#700572: fixed in initramfs-tools 0.110)
I think that initramfs-tools 0.110 fixes should go to sid/wheezy. Or make kernels in experimental depend on this version or higher. -- 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/20130305152336.GA5272@tiikeri.vuoristo.local
Should intel-microcode recommends be versioned (firmware-linux)?
When using squeeze system, with wheezy (backports) of kernel and firmware, recently firmware-linux started to recommend intel-microcode and amd64-microcode packages. I think that intel-microcode recommends can be versioned, so that it prefers reworked versions (1.20120606.1 or newer) instead of old squeeze version. -- 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/20130123211537.GA11194@lisko
Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support
On Fri, Jan 04, 2013 at 05:13:35PM +0100, Julien Cristau wrote: On Mon, Nov 26, 2012 at 22:28:56 +0100, Julien Cristau wrote: New image is up at http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. diff against svn at http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff New image: - rebased on 3.2.35-2 - updated drm to 3.4.24 - with additional patches from 3.2.y that were missing in 3.4.y diff at http://people.debian.org/~jcristau/drm-backport-3.2.35-3~jcristau.1.patch http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-686-pae_3.2.35-3~jcristau.1_i386.deb sha1sum 17980ee5bafc40bb4e7bf42576ce40ac81c75833 Lightly tested on Dell latitude D520 with intel 945gm graphics, and squeeze userspace. http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.35-3~jcristau.1_amd64.deb sha1sum f6711fe6d0d924aab82ec82fe1a86102a69a8c32 Amd64 deb works fine with Asus 1215B (AMD Radeon 6310 APU), wheezy xfce -- 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/20130105190234.GA25564@tiikeri.vuoristo.local
Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support
On Mon, Nov 26, 2012 at 10:28:56PM +0100, Julien Cristau wrote: New image is up at http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. diff against svn at http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff Tested working with Asus 1215B (AMD Radeon Brazos APU), wheezy No problems found (compared to 3.2.32-1) -- 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/20121203130554.GA25187@tiikeri.vuoristo.local
Bug#692234: Intel DH77EB (H77): sporadic freeze and increased power consumption
On Sun, Dec 02, 2012 at 01:54:51PM +0100, Ingo wrote: Since 2 weeks I an running kernel 3.4 from kernel.org. I used config from Debian's 3.4.4-1~experimental.1 with make silentoldconfig and accepted defaults fo 5 new items. This is a long term kernel as well and thus still maintained. I started with 3.4.18, updated to 3.4.19 and now using 3.4.20. All without any problems including VirtualBox 4.1.18 from Wheezy repo. This also appears a viable alternative to current 3.2? Julien Cristau wrote at bug #687442 --- New image is up at http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. diff against svn at http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff --- That kernel image is based on 3.2 with graphics system backported from 3.4 It would help if you can test that version too. -- 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/20121203132353.GA26414@tiikeri.vuoristo.local
Re: linux_3.2.29-1_multi.changes ACCEPTED into unstable, unstable
amd64 debs aren't yet available from my mirror (ftp.fi.debian.org) for some reason, do they show up in other places? -- 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/20120920125902.GA23780@tiikeri.vuoristo.local
Re: linux_3.2.29-1_multi.changes ACCEPTED into unstable, unstable
On Thu, Sep 20, 2012 at 03:59:02PM +0300, Touko Korpela wrote: amd64 debs aren't yet available from my mirror (ftp.fi.debian.org) for some reason, do they show up in other places? nevermind, latest mirror update has it -- 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/20120920160732.GA28600@tiikeri.vuoristo.local
Re: Bug#679252: bugs intended for linux being filed against src
On Wed, Jun 27, 2012 at 02:39:29PM +0100, Ben Hutchings wrote: On Wed, 2012-06-27 at 07:56 -0500, Jonathan Nieder wrote: Source: linux Version: 3.2.20-1 Hi kernel maintainers, Gergely Nagy wrote: reassign 679226 src:linux-2.6 3.2.20-1 Several bugs seem to have been filed against the nonexistent 'src' package recently. I am guessing this means reportbug or some related tool does not know how to deal with 'src:linux' as a package name. Please use plain 'linux' for now. reportbug-ng is doing this. Let's get it fixed. Recent bugs reported against 'src' have X-Mailer: reportbug 6.4 Looks like reportbug is buggy too. -- 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/20120725113034.GA13155@lisko
Bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sun, Jul 01, 2012 at 11:03:02AM -0400, Milan Kupcevic wrote: On 07/01/2012 07:05 AM, Touko Korpela wrote: ... +if test $post_2_6_38; then + XZ=xz --check=crc32 -8 +else + XZ=false +fi From xz(1) manual page (you can ignore DecMem): Preset DictSize CompCPU CompMem DecMem -0 256 KiB 03 MiB1 MiB -1 1 MiB 19 MiB2 MiB -2 2 MiB 2 17 MiB3 MiB -3 4 MiB 3 32 MiB5 MiB -4 4 MiB 4 48 MiB5 MiB -5 8 MiB 5 94 MiB9 MiB -6 8 MiB 6 94 MiB9 MiB -7 16 MiB 6 186 MiB 17 MiB -8 32 MiB 6 370 MiB 33 MiB -9 64 MiB 6 674 MiB 65 MiB Better to use default setting -6 that has lower memory requirement. Here is timing for re-compression from gzip to xz on Pegasos II with Freescale 7447 1GhZ processor and 1Gb RAM: Use of -8 option isn't a good thing for systems having only 512 Mib or less memory. This operation shouldn't force to use slow swap space or OOM. set time compressed size -91m43.962s9.5MB -81m44.824s9.5MB -61m35.097s9.6MB -31m10.080s10.6MB -20m45.609s10.7MB -00m19.286s11.1MB I've originally decided to go with -8, mainly because the same preset is used in mkinitramfs form initramfs-tools package. It may be worth hearing arguments about the timing given that all presets currently produce vmlinuz smaller than the 12MB limit, but the compression time is very different. Your size numbers show that -8 produces only marginally smaller images. If mkinitramfs (initramfs-tools) uses -8 for xz compression, it should be changed too. -- 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/20120702110728.GA3295@tiikeri.vuoristo.local
Bug#549681: bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sat, Jun 30, 2012 at 11:01:47PM -0400, Milan Kupcevic wrote: The attached patch brings vmlinuz from about 13MB to about 9.5MB, which is well under the 12MB limit. Downside is that xz compressing is noticeably slower than currently used gzip, but decompressing speed difference is not noticeable. I've tested it on Pegasos II machine, it boots really fast. Updated mkvmlinuz package is waiting on mentors.debian.net for a willing sponsor for upload. ... +if test $post_2_6_38; then + XZ=xz --check=crc32 -8 +else + XZ=false +fi From xz(1) manual page (you can ignore DecMem): Preset DictSize CompCPU CompMem DecMem -0 256 KiB 03 MiB1 MiB -1 1 MiB 19 MiB2 MiB -2 2 MiB 2 17 MiB3 MiB -3 4 MiB 3 32 MiB5 MiB -4 4 MiB 4 48 MiB5 MiB -5 8 MiB 5 94 MiB9 MiB -6 8 MiB 6 94 MiB9 MiB -7 16 MiB 6 186 MiB 17 MiB -8 32 MiB 6 370 MiB 33 MiB -9 64 MiB 6 674 MiB 65 MiB Better to use default setting -6 that has lower memory requirement. -- 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/20120701110505.GA6166@tiikeri.vuoristo.local
Bug#678636: initramfs-tools: dm-crypt partitions not further working. No asking password to encrypt. System will not boot
On Sat, Jun 23, 2012 at 01:13:04PM +0200, Pierre Bernhardt wrote: Package: initramfs-tools Version: 0.106 Severity: critical Tags: upstream Justification: breaks the whole system After patching my system 3 days ago it will not further boot up. The initramfs prompt comes before the keypass has to been normally asked for to decrypt my root partition with the contained lvm root vol disk group. Before the upgrade been made I didn't hat the problem. I guess this comes with the upgrade of the initramfs-tools from 0.103 to 0.106. Work around at the moment is to use cryptsetup luksOpen manually and start all lvmvolumes before continue with the boot process by using Crtl-D. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 11M Jun 22 13:21 /boot/initrd.img-2.6.32-5-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/rootdg-root ro This lists both 2.6.32-5 and 3.2.0-2 kernels. What kernel version do you try to boot, and is its initramfs updated? By default only most recent kernel does have initramfs updated when updating packages. Your setup has many moving parts that can go wrong. Please list versions of mdadm, dmsetup, libdevmapper*, *cryptsetup* -- /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] md50 : active raid5 sda1[0] sdd1[3] sde1[5] 625137664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] bitmap: 1/3 pages [4KB], 65536KB chunk md1 : active raid1 sdc2[0] 28812480 blocks [1/1] [U] bitmap: 4/220 pages [16KB], 64KB chunk md0 : active raid1 sdc1[0] 489856 blocks [1/1] [U] bitmap: 0/60 pages [0KB], 4KB chunk -- System Information: Debian Release: wheezy/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable'), (300, 'testing'), (200, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) You are using mixed system, packages may have bugs in their depends, so that manual updating or bug reporting is maybe needed. Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-7 GNU cpio -- a program to manage ar ii klibc-utils 2.0-2 small utilities built with klibc f ii module-init-tools 3.12-2 tools for managing Linux kernel mo ii udev 175-3.1/dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.19.3-7 Tiny utilities for small and embed Versions of packages initramfs-tools suggests: pn bash-completion none (no description available) -- no debconf information -- 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/20120623121314.GA29005@tiikeri.vuoristo.local
Bug#678636: initramfs-tools: dm-crypt partitions not further working. No asking password to encrypt. System will not boot
On Sat, Jun 23, 2012 at 01:13:04PM +0200, Pierre Bernhardt wrote: -- /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] md50 : active raid5 sda1[0] sdd1[3] sde1[5] 625137664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] bitmap: 1/3 pages [4KB], 65536KB chunk md1 : active raid1 sdc2[0] 28812480 blocks [1/1] [U] bitmap: 4/220 pages [16KB], 64KB chunk md0 : active raid1 sdc1[0] 489856 blocks [1/1] [U] bitmap: 0/60 pages [0KB], 4KB chunk unused devices: none Your raid1 arrays look strange, with only one component device in each. -- 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/2012062312.GA30199@tiikeri.vuoristo.local
Bug#636010: linux-2.6 - linux source renaming
I think it would make sense to display note or news item at 'linux-2.6' PTS page at http://packages.qa.debian.org/l/linux-2.6.html telling that source package is now renamed to 'linux'. -- 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/20120615193613.GA13284@lisko
Re: Linux features for wheezy
On Sat, Jun 02, 2012 at 11:47:03PM +0100, Ben Hutchings wrote: Some hardware support; this can still be done after the freeze but the sooner the better: - [armhf] omapdrm driver - [x86] gma500 support for new chips - [x86] i915 improvements in Ivy Bridge support - radeon support for new chips - NVMe driver - tg3 support for 57766 chip - ipheth support for iPhone 4S - DRM/KMS driver for DisplayLink - qmi_wwan driver (#670241) 3.2.20 has some radeon fixes/new chip support from 3.4.x, nice. What about improvements that went in at 3.3 kernel (hope link is right): http://lists.freedesktop.org/archives/dri-devel/2012-January/018076.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/20120612123900.GA14746@tiikeri.vuoristo.local
Bug#664767: Brcmsmac driver woes, possible regression?
On Sun, Jun 03, 2012 at 02:21:28PM +0200, Camaleón wrote: 2012/6/1 Camaleón noela...@gmail.com: OTOH, I will try to reproduce the instability state with 3.2.16-1 over the weekend and will comment the results here. Okay, I'm afraid the problem is still present in kernel 3.2.17-1 :-( Wireless was stable when I tested because I had loaded wl driver instead (I completely forgot about that), once I changed to brcmsmac I got a disconnect after 3-4 hours... Sorry for the noise. Anyway, if applying all the patches is not possible I can run individual tests to cherry-pick some of them but as Jonathan pointed I'll need some guidance to make the tryouts. It would be good if you tried Debian kernel 3.2.18-1 (or newer). It has endless retry of A-MPDU transmissions patch in brcmsmac. Maybe it makes some difference. -- 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/20120604084200.GA30645@tiikeri.vuoristo.local
Re: Linux features for wheezy
On Mon, Jun 04, 2012 at 04:58:42AM +0100, Ben Hutchings wrote: Here's what that change looks like: -$(BUILD_DIR)/linux-source-$(UPSTREAMVERSION).tar.bz2: SOURCE_DIR=$(BUILD_DIR)/source +define copy_source +rsync --delete --exclude debian --exclude .pc --exclude .svk --exclude .svn --link-dest=. -a . '$(1)' +endef + $(BUILD_DIR)/linux-source-$(UPSTREAMVERSION).tar.bz2: DIR = $(BUILD_DIR)/linux-source-$(UPSTREAMVERSION) -$(BUILD_DIR)/linux-source-$(UPSTREAMVERSION).tar.bz2: $(STAMPS_DIR)/source +$(BUILD_DIR)/linux-source-$(UPSTREAMVERSION).tar.bz2: rm -rf '$@' '$(DIR)' - cp -al '$(SOURCE_DIR)' '$(DIR)' + $(call copy_source,$(DIR)) chmod -R u+rw,go=rX '$(DIR)' cd '$(BUILD_DIR)'; tar -cjf 'linux-source-$(UPSTREAMVERSION).tar.bz2' 'linux-source-$(UPSTREAMVERSION)' rm -rf '$(DIR)' This uses still bzip2? ifeq ($(TAR_ORIG),) $(error Cannot find orig tarball $(TAR_ORIG_NAME)) else mkdir -p ../orig - tar -C ../orig -xzf $(TAR_ORIG) + tar -C ../orig -xJf $(TAR_ORIG) When extracting, you don't need to pass compression option to tar anymore (so it can be removed). === --- debian/templates/control.source.in(revision 19077) +++ debian/templates/control.source.in(working copy) @@ -3,7 +3,7 @@ Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Uploaders: Bastian Blank wa...@debian.org, Frederik Schüler f...@debian.org, maximilian attems m...@debian.org, Ben Hutchings b...@decadent.org.uk Standards-Version: 3.9.2 -Build-Depends: debhelper ( 7), cpio, kmod | module-init-tools, python (= 2.6.6-3~), lzma [armel], kernel-wedge (= 2.83), quilt +Build-Depends: debhelper ( 7), cpio, kmod | module-init-tools, python (= 2.6.6-3~), lzma [armel], kernel-wedge (= 2.83), quilt, rsync Build-Depends-Indep: bzip2, xmlto Shouldn't lzma build-depend be now set on all architectures? -- 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/20120604091950.GA30694@tiikeri.vuoristo.local
Re: Linux features for wheezy
On Mon, Jun 04, 2012 at 04:40:25PM +0100, Ben Hutchings wrote: --- debian/templates/control.source.in(revision 19077) +++ debian/templates/control.source.in(working copy) @@ -3,7 +3,7 @@ Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Uploaders: Bastian Blank wa...@debian.org, Frederik Schüler f...@debian.org, maximilian attems m...@debian.org, Ben Hutchings b...@decadent.org.uk Standards-Version: 3.9.2 -Build-Depends: debhelper ( 7), cpio, kmod | module-init-tools, python (= 2.6.6-3~), lzma [armel], kernel-wedge (= 2.83), quilt +Build-Depends: debhelper ( 7), cpio, kmod | module-init-tools, python (= 2.6.6-3~), lzma [armel], kernel-wedge (= 2.83), quilt, rsync Build-Depends-Indep: bzip2, xmlto Shouldn't lzma build-depend be now set on all architectures? Yes, thanks. armel lzma build-depend was for kernel image compression, so it's little different What about xz-utils build-depend? It's higher priority and tar suggests it (tar could remove suggest now that xz-utils is Priority: required, and kernel not need add build depend on it?) (There is also xz-lzma compatibility package available for in place of lzma ). -- 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/20120604164857.GA7061@tiikeri.vuoristo.local
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
On Thu, May 24, 2012 at 05:44:23PM +0300, Touko Korpela wrote: I don't know if it's regression or not but when I rebooted 3.2.18-1, kernel oopsed during shutdown (it wasn't logged). I don't remember that happened before. False alarm, it wasn't kernel oops, it was X server segfault at shutdown bug #671812, fixed by xorg-server 2:1.12.1.902-1 -- 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/20120526105221.GA27110@tiikeri.vuoristo.local
Bug#672891: wireless brcms_c_wait_for_tx_completion warning
On Fri, May 25, 2012 at 11:34:07AM -0500, Jonathan Nieder wrote: Hi, Touko Korpela wrote: Here is log from 3.2.18-1 kernel with X125 laptop. WARNING is there. [...] Linux version 3.2.0-2-686-pae (Debian 3.2.18-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Mon May 21 18:24:12 UTC 2012 [...] [ cut here ] WARNING: at [...]/drivers/net/wireless/brcm80211/brcmsmac/main.c:8241 brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac]() Hardware name: X125 Modules linked in: cryptd aes_i586 aes_generic bridge stp bnep rfcomm powernow_k8 mperf cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave fuse loop snd_hda_codec_hdmi joydev arc4 brcmsmac mac80211 brcmutil snd_hda_codec_realtek radeon snd_hda_intel ttm drm_kms_helper drm uvcvideo snd_hda_codec snd_hwdep snd_pcm snd_seq tpm_tis tpm tpm_bios snd_timer ac button videodev media btusb evdev sp5100_tco snd_seq_device video battery processor k10temp snd samsung_laptop i2c_algo_bit pcspkr power_supply i2c_piix4 i2c_core bluetooth cfg80211 shpchp rfkill psmouse serio_raw soundcore crc8 snd_page_alloc cordic ext4 mbcache jbd2 crc16 usb_storage uas sd_mod crc_t10dif ohci_hcd ahci libahci libata ehci_hcd scsi_mod thermal thermal_sys usbcore usb_common sky2 [last unloaded: scsi_wait_scan] Pid: 3127, comm: kworker/u:2 Not tainted 3.2.0-2-686-pae #1 Call Trace: [c1038468] ? warn_slowpath_common+0x68/0x79 [f8759e22] ? brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac] [c1038486] ? warn_slowpath_null+0xd/0x10 [f8759e22] ? brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac] [f875110f] ? brcms_ops_flush+0x1f/0x29 [brcmsmac] [f86abdca] ? ieee80211_scan_work+0x36a/0x3fb [mac80211] [c1049aef] ? process_one_work+0x112/0x1fa [f86aba60] ? ieee80211_scan_rx+0x139/0x139 [mac80211] [c104a7fa] ? worker_thread+0xa9/0x122 [c104a751] ? manage_workers.isra.23+0x13d/0x13d [c104d13b] ? kthread+0x63/0x68 [c104d0d8] ? kthread_worker_fn+0x101/0x101 [c12c5c7e] ? kernel_thread_helper+0x6/0x10 ---[ end trace b3b9484c4306740d ]--- This is 20 hours after boot so I'm guessing it's not easy to reproduce. Alas. Thanks for reporting it. Do you think the patch added in 3.2.18 made a difference? How often were you getting the wait_for_tx_completion WARNING before, and are you getting it less often now? (I'm asking because this information would probably be helpful to upstream in diagnosing this.) (last followup was sent to cloned bug by mistake) Hard to say if it made difference, maybe made it more rare. Logs show only a few this kind of warnings in last weeks running 3.2.1x It always happens after many hours of uptime except 3.2.17-1 case that happened sooner but it doesn't mean much. That computer is always on doing some backround calculations that causes small amount of network traffic and is sometimes used locally for browsing and applying updates. But should this bug be opened 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/20120525180914.GA5996@tiikeri.vuoristo.local
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
On Thu, May 17, 2012 at 12:34:10AM +0300, Touko Korpela wrote: Patch works, warning is gone after couple of hours of use. I let you know if situation changes. This patch and INTERMEDIATE but not AMPDU only when tracing looks like good to have also in upstream stable kernel. Thanks. This patch (?) causes possible regression. On another laptop (Asus 1215B), that doesn't use encrypted wlan and didn't have this warning bug, now when it's updated to 3.2.18-1 kernel have these in kernel log: [ 6403.270153] ieee80211 phy0: AMPDU status: BA Timeout, seq 152, in_transit 0 [ 8460.377520] ieee80211 phy0: AMPDU status: BA Timeout, seq 1655, in_transit 0 [122948.312642] ieee80211 phy0: AMPDU status: BA Timeout, seq 1909, in_transit 0 [127769.562872] ieee80211 phy0: AMPDU status: BA Timeout, seq 1514, in_transit 0 [138206.258059] ieee80211 phy0: AMPDU status: BA Timeout, seq 1955, in_transit 0 [138208.157102] ieee80211 phy0: AMPDU status: BA Timeout, seq 2019, in_transit 0 [138209.256180] ieee80211 phy0: AMPDU status: BA Timeout, seq 2083, in_transit 0 [138333.091352] ieee80211 phy0: AMPDU status: BA Timeout, seq 1998, in_transit 0 [138691.811699] ieee80211 phy0: AMPDU status: BA Timeout, seq 3480, in_transit 0 [138691.821426] ieee80211 phy0: AMPDU status: BA Timeout, seq 3481, in_transit 0 [138693.625124] ieee80211 phy0: AMPDU status: BA Timeout, seq 3545, in_transit 0 [138876.798913] ieee80211 phy0: wl0: ampdu tx phy error (0x20) [138898.244949] ieee80211 phy0: AMPDU status: BA Timeout, seq 3473, in_transit 0 [138928.721483] ieee80211 phy0: AMPDU status: BA Timeout, seq 368, in_transit 0 [138928.750952] ieee80211 phy0: AMPDU status: BA Timeout, seq 371, in_transit 0 [138983.464116] ieee80211 phy0: AMPDU status: BA Timeout, seq 2109, in_transit 0 [138987.335330] ieee80211 phy0: AMPDU status: BA Timeout, seq 2260, in_transit 0 [138987.407104] ieee80211 phy0: AMPDU status: BA Timeout, seq 2263, in_transit 0 [138989.645811] ieee80211 phy0: AMPDU status: BA Timeout, seq 2324, in_transit 0 [138989.712585] ieee80211 phy0: AMPDU status: BA Timeout, seq 2327, in_transit 0 [139238.835879] ieee80211 phy0: AMPDU status: BA Timeout, seq 3351, in_transit 0 [139479.485788] ieee80211 phy0: AMPDU status: BA Timeout, seq 778, in_transit 0 [139575.576971] ieee80211 phy0: AMPDU status: BA Timeout, seq 551, in_transit 0 [139592.867088] ieee80211 phy0: AMPDU status: BA Timeout, seq 1231, in_transit 0 [139903.037705] ieee80211 phy0: AMPDU status: BA Timeout, seq 2731, in_transit 0 [139983.445525] ieee80211 phy0: AMPDU status: BA Timeout, seq 2094, in_transit 0 -- 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/20120524094201.GA29470@tiikeri.vuoristo.local
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
On Thu, May 24, 2012 at 08:36:02AM -0500, Jonathan Nieder wrote: Touko Korpela wrote: This patch (?) causes possible regression. On another laptop (Asus 1215B), that doesn't use encrypted wlan and didn't have this warning bug, now when it's updated to 3.2.18-1 kernel have these in kernel log: [ 6403.270153] ieee80211 phy0: AMPDU status: BA Timeout, seq 152, in_transit 0 [ 8460.377520] ieee80211 phy0: AMPDU status: BA Timeout, seq 1655, in_transit 0 These are harmless and suppressed by commit 2b0a53d51b5f263bb581bbdb40ebb9f7e09609b1 Author: Arend van Spriel ar...@broadcom.com Date: Thu Feb 23 18:38:23 2012 +0100 brcm80211: smac: only print block-ack timeout message at trace level In regular use block-ack timeouts can happen so it does not make sense to fill the log with these messages. in 3.3. [...] [138693.625124] ieee80211 phy0: AMPDU status: BA Timeout, seq 3545, in_transit 0 [138876.798913] ieee80211 phy0: wl0: ampdu tx phy error (0x20) This is the one that seemed potentially interesting. Does it happen often? Not very often, in between dozens BA Timeout messages, only two of those ampdu tx phy error messages are printed (40min apart, time 10:00 and 10:40). Also in time 10:25 is printed brcms_c_ampdu_dotxstatus_complete:supr_status 0x18 I have reported also bug #671803 I don't know if it's regression or not but when I rebooted 3.2.18-1, kernel oopsed during shutdown (it wasn't logged). I don't remember that happened before. -- 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/20120524144423.GA3559@tiikeri.vuoristo.local
Bug#674435: Please upload new firmware packages
Package: firmware-brcm80211 Version: 0.35 Severity: wishlist Upstream repository has some new/updated firmwares available. Also it would be good to ask if Broadcom has new firmwares available for wireless cards (firmware-brcm80211). -- 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/20120524152948.10136.37688.reportbug@lisko
Bug#664767: Brcmsmac driver woes, possible regression?
On Mon, May 21, 2012 at 09:07:51AM -0500, Jonathan Nieder wrote: Camaleón wrote: Although kernel 3.3 still logs the trace (despite having applied all of the suggested the patches), there's an overall stability improvement in the wireless driver when compared to kernel 3.2.12 where: - Wireless link is more prone to connection resets which require for user interaction to reconnect again - Reconnects make some running programs to segfault [...] Apr 6 19:56:22 stt300 kernel: [32987.534515] gnome-shell[2062]: segfault at 24 ip b76bbb31 sp bfbf7920 error 4 in libgnome-shell.so[b7681000+a] Apr 6 19:58:02 stt300 kernel: [33086.718790] mail-notificati[2077]: segfault at 4c ip 08060063 sp bfe8d4a0 error 4 in mail-notification[8048000+5c000] That's no good. It would be nice to get this fixed in 3.2.y upstream if possible. Maybe try also new 3.2.18-1 kernel (available today in unstable) to see how stable it works. -- 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/20120521164748.GA12479@tiikeri.vuoristo.local
Bug#673194: closed by maximilian attems m...@stro.at (Re: Bug#673194: initramfs-tools: mkinitramfs silently creates non-bootable initramfs when run as non-root user)
On Fri, May 18, 2012 at 02:30:24PM +, maximilian attems wrote: On Fri, May 18, 2012 at 03:55:56PM +0300, Markus Vuorio wrote: no error provided, command is meant to be also run as normal user thus assertion by report is invalid, closing. The resulting initramfs doesn't work, kernel can't find init there. have you tried to compare the content of both initramfs? I think closing of this bug was done too fast. Markus, you can compare initramfs contents using lsinitramfs -l command. -- 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/20120520234235.GA7193@lisko
Bug#673511: brcmsmacs: mode IBSS not implemented for Broadcom Wirless LAN controllers
On Sat, May 19, 2012 at 10:26:37AM +0200, Paul Menzel wrote: Package: linux-2.6 Version: 3.2.17-1 Severity: normal Tags: upstream Dear Debian folks, the `brcmsmac` [1] module does not support IBSS [2] needed to create ad-hoc networks [3][4][5]. This prevents for example using shared WLAN connections from smart phones. `/var/log/syslog` contains the following messages. ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: disassociated ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled false, count 1 wpa_supplicant[2209]: nl80211: Failed to set interface into IBSS mode wpa_supplicant[2209]: Association request to the driver failed 1. Would it be better to use the module `b43` by default which is supposed to support all modes [3]? 2. If support for IBSS in `brcmsmac` is implemented, could that be backported to Linux 3.2? What is exact model of your adapter (lspci -nn)? I have adapter 14e4:4727 model in my laptop, that is only supported by brcmsmac. -- 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/20120519110922.GA9231@tiikeri.vuoristo.local
xz compression support
Binary packages built from linux-2.6 source are now xz compressed (or was that reverted)? What about kernel images (vmlinuz) and initramfs images? Is it enabled only for some architectures (arm)? Another issue is source package. Shouldn't it be xz compressed (upstream tarballs are available also in xz)? P.s. Is xz-utils update coming soon, package has some bugs accumulated. -- 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/20120517121415.GA5219@lisko
Re: xz compression support
On Thu, May 17, 2012 at 03:14:15PM +0300, Touko Korpela wrote: Another issue is source package. Shouldn't it be xz compressed (upstream tarballs are available also in xz)? Apparently this requires converting source package to new 3.0 format. It seems to have good and not-so-good properties with it. Seems solvable, debian-devel list has current topic about it. -- 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/20120517184657.GA30516@lisko
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
Again failure :( It seems that brcmsmac is enabled by some Debian patch, that don't get enabled when building from upstream 3.2.x git tree. It would make sense to offer current Debian kernel git tree also. That kernel has this in dmesg: [4.468517] b43-phy0: Broadcom 4313 WLAN found (core revision 24) [4.469335] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8, Revision 1) [4.469389] b43: probe of bcma0:0 failed with error -95 Attached is diff between official Debian config and custom config. 3c3 # Linux/i386 3.2.17 Kernel Configuration --- # Linux/x86 3.2.17 Kernel Configuration 126a127 CONFIG_CGROUP_MEM_RES_CTLR_DISABLED=y 446a448 CONFIG_EFI_STUB=y 1056d1057 # CONFIG_COPS is not set 1361a1363 # CONFIG_GENERIC_CPU_DEVICES is not set 1743a1746 CONFIG_HYPERV_STORAGE=m 2405a2409,2410 CONFIG_BRCMUTIL=m CONFIG_BRCMSMAC=m 2406a2412 # CONFIG_BRCMDBG is not set 2549a2556 CONFIG_HYPERV_NET=m 4230d4236 CONFIG_SND_CS46XX_NEW_DSP=y 4408a4415 CONFIG_HYPERV_MOUSE=m 5054,5056d5060 CONFIG_HYPERV_STORAGE=m CONFIG_HYPERV_NET=m CONFIG_HYPERV_MOUSE=m 5063,5064d5066 # CONFIG_WLAGS49_H2 is not set # CONFIG_WLAGS49_H25 is not set 5127a5130 CONFIG_AMILO_RFKILL=m 5174a5178,5181 # # Microsoft Hyper-V guest support # 5374a5382,5398 CONFIG_AUFS_FS=m CONFIG_AUFS_BRANCH_MAX_127=y # CONFIG_AUFS_BRANCH_MAX_511 is not set # CONFIG_AUFS_BRANCH_MAX_1023 is not set # CONFIG_AUFS_BRANCH_MAX_32767 is not set CONFIG_AUFS_SBILIST=y # CONFIG_AUFS_HNOTIFY is not set CONFIG_AUFS_EXPORT=y # CONFIG_AUFS_RDU is not set # CONFIG_AUFS_PROC_MAP is not set # CONFIG_AUFS_SP_IATTR is not set # CONFIG_AUFS_SHWH is not set # CONFIG_AUFS_BR_RAMFS is not set # CONFIG_AUFS_BR_FUSE is not set CONFIG_AUFS_BR_HFSPLUS=y CONFIG_AUFS_BDEV_LOOP=y # CONFIG_AUFS_DEBUG is not set 5500a5525,5529 CONFIG_PROTECTED_LINKS=y CONFIG_PROTECTED_SYMLINKS=y CONFIG_PROTECTED_SYMLINKS_SYSCTL=1 CONFIG_PROTECTED_HARDLINKS=y CONFIG_PROTECTED_HARDLINKS_SYSCTL=1 5511a5541 CONFIG_MAGIC_SYSRQ_DEFAULT_MASK=0x01b6 5550c5580,5581 # CONFIG_DEBUG_INFO is not set --- CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_INFO_REDUCED is not set
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
On Wed, May 16, 2012 at 12:00:05PM -0500, Jonathan Nieder wrote: Touko Korpela wrote: It seems that brcmsmac is enabled by some Debian patch, that don't get enabled when building from upstream 3.2.x git tree. It would make sense to offer current Debian kernel git tree also. There is [1], but it doesn't get updated as frequently. [...] That kernel has this in dmesg: [4.468517] b43-phy0: Broadcom 4313 WLAN found (core revision 24) [4.469335] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8, Revision 1) [4.469389] b43: probe of bcma0:0 failed with error -95 Oh, right. The relevant Debian-specific change is * Enable BCMA as module, BCMA_HOST_PCI and B43_BCMA (Closes: #649567) but limit these to devices not supported by brcmsmac To get brcmsmac, disable BCMA: make nconfig Device Drivers → Broadcom specific AMBA → BCMA support: N Device Drivers → Network device support → Wireless LAN → Broadcom IEEE802.11n PCIe SoftMAC WLAN driver: M Or from the command line: scripts/config --disable BCMA scripts/config --module BRCMSMAC Now build stops with: drivers/net/wireless/brcm80211/brcmsmac/main.c: In function ‘brcms_c_recvctl’: drivers/net/wireless/brcm80211/brcmsmac/main.c:7882:4: error: too few arguments to function ‘brcms_b_mute’ drivers/net/wireless/brcm80211/brcmsmac/main.c:2538:13: note: declared here make[5]: *** [drivers/net/wireless/brcm80211/brcmsmac/main.o] Error 1 make[4]: *** [drivers/net/wireless/brcm80211/brcmsmac] Error 2 make[3]: *** [drivers/net/wireless/brcm80211] Error 2 -- 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/20120516172712.GA26152@tiikeri.vuoristo.local
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
Patch works, warning is gone after couple of hours of use. I let you know if situation changes. This patch and INTERMEDIATE but not AMPDU only when tracing looks like good to have also in upstream stable kernel. 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/20120516213410.GA31083@tiikeri.vuoristo.local
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
Package: linux-2.6 Version: 3.2.17-1 Severity: normal Samsung X125 laptop. This kind of warning was logged. Also earlier 3.2.x kernels do this. -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.17-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Sun May 13 07:51:23 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-2-686-pae root=UUID=8d1825b0-128e-48b9-b21d-c189ccdf9506 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [4.561024] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [4.568751] [drm] PCIE GART of 512M enabled (table at 0xC004). [4.574151] radeon :01:05.0: WB enabled [4.611273] [drm] ring test succeeded in 0 usecs [4.611412] [drm] radeon: ib pool ready. [4.611501] [drm] ib test succeeded in 0 usecs [4.614899] [drm] Radeon Display Connectors [4.614903] [drm] Connector 0: [4.614905] [drm] LVDS [4.614909] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [4.614911] [drm] Encoders: [4.614913] [drm] LCD1: INTERNAL_KLDSCP_LVTMA [4.614915] [drm] Connector 1: [4.614917] [drm] VGA [4.614920] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [4.614922] [drm] Encoders: [4.614924] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [4.614926] [drm] Connector 2: [4.614928] [drm] HDMI-A [4.614929] [drm] HPD1 [4.614932] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [4.614934] [drm] Encoders: [4.614936] [drm] DFP1: INTERNAL_UNIPHY [4.615068] [drm] radeon: power management initialized [5.197346] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa4/0xa [5.239840] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10 [5.650317] [drm] fb mappable at 0xC0142000 [5.650321] [drm] vram apper at 0xC000 [5.650324] [drm] size 4325376 [5.650326] [drm] fb depth is 24 [5.650328] [drm]pitch is 5632 [5.650478] fbcon: radeondrmfb (fb0) is primary device [5.731785] Console: switching to colour frame buffer device 170x48 [5.747596] fb0: radeondrmfb frame buffer device [5.747599] drm: registered panic notifier [5.747677] [drm] Initialized radeon 2.12.0 20080528 for :01:05.0 on minor 0 [5.952706] EXT4-fs (sdb2): re-mounted. Opts: (null) [6.019072] EXT4-fs (sdb2): re-mounted. Opts: errors=remount-ro [6.069379] loop: module loaded [6.830368] EXT4-fs (sdb1): mounted filesystem without journal. Opts: (null) [7.125166] fuse init (API version 7.17) [8.057107] powernow-k8: Found 1 AMD Athlon(tm) II Neo K125 Processor (1 cpu cores) (version 2.20.00) [8.057155] powernow-k8:0 : pstate 0 (1700 MHz) [8.057158] powernow-k8:1 : pstate 1 (1300 MHz) [8.057161] powernow-k8:2 : pstate 2 (800 MHz) [8.214473] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [8.214482] Bluetooth: BNEP filters: protocol multicast [8.243742] Bluetooth: RFCOMM TTY layer initialized [8.243755] Bluetooth: RFCOMM socket layer initialized [8.243761] Bluetooth: RFCOMM ver 1.11 [8.250949] Bridge firewalling registered [9.518051] ieee80211 phy0: brcms_ops_config: change monitor mode: false (implement) [9.522516] ieee80211 phy0: brcms_ops_config: change power-save mode: false (implement) [9.527546] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) [9.532333] ADDRCONF(NETDEV_UP): wlan0: link is not ready [9.538671] sky2 :03:00.0: eth0: enabling interface [9.538958] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 410.536349] wlan0: authenticate with 00:24:a5:da:fa:e8 (try 1) [ 410.540145] wlan0: authenticated [ 410.540189] wlan0: associate with 00:24:a5:da:fa:e8 (try 1) [ 410.543376] wlan0: RX AssocResp from 00:24:a5:da:fa:e8 (capab=0x411 status=0 aid=1) [ 410.543382] wlan0: associated [ 410.543990] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 410.544024] ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: associated [ 410.544031] ieee80211 phy0: changing basic rates failed: -22 [ 410.544036] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement) [ 410.544322] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 410.618222] Intel AES-NI instructions are not detected. [ 414.731944] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement) [ 420.912148] wlan0: no IPv6 routers present [ 1210.372008] [ cut here ] [ 1210.372039] WARNING: at /build/buildd-linux-2.6_3.2.17-1-i386-rPdRhH/linux-2.6-3.2.17/debian/build/source_i386_none/drivers/net/wireless/brcm80211/brcmsmac/main.c:8241 brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac]() [ 1210.372046] Hardware name: X125 [ 1210.372049]
Bug#672891: wireless brcms_c_wait_for_tx_completion warning
Package: linux-2.6 Severity: normal Here is previous warning with 3.2.16-1. [90251.832010] [ cut here ] [90251.832040] WARNING: at /build/buildd-linux-2.6_3.2.16-1-i386-xAlW9F/linux-2.6-3.2.16/debian/build/source_i386_none/drivers/net/wireless/brcm80211/brcmsmac/main.c:8233 brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac]() [90251.832047] Hardware name: X125 [90251.832050] Modules linked in: cryptd aes_i586 aes_generic bridge stp rfcomm bnep powernow_k8 mperf cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave fuse loop snd_hda_codec_hdmi joydev arc4 snd_hda_codec_realtek brcmsmac snd_hda_intel mac80211 brcmutil snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device sp5100_tco tpm_tis tpm snd tpm_bios pcspkr evdev radeon battery ttm drm_kms_helper drm psmouse btusb i2c_algo_bit samsung_laptop uvcvideo ac videodev serio_raw power_supply media button processor video i2c_piix4 i2c_core k10temp soundcore bluetooth cfg80211 snd_page_alloc rfkill crc8 cordic shpchp ext4 mbcache jbd2 crc16 sd_mod crc_t10dif usb_storage uas ohci_hcd ahci libahci ehci_hcd libata scsi_mod thermal thermal_sys sky2 usbcore usb_common [last unloaded: scsi_wait_scan] [90251.832133] Pid: 3271, comm: kworker/u:1 Not tainted 3.2.0-2-686-pae #1 [90251.832137] Call Trace: [90251.832147] [c10384b8] ? warn_slowpath_common+0x68/0x79 [90251.832167] [f8a0ae1e] ? brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac] [90251.832173] [c10384d6] ? warn_slowpath_null+0xd/0x10 [90251.832190] [f8a0ae1e] ? brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac] [90251.832204] [f8a0210f] ? brcms_ops_flush+0x1f/0x29 [brcmsmac] [90251.83] [f8621dca] ? ieee80211_scan_work+0x36a/0x3fb [mac80211] [90251.832229] [c1049b63] ? process_one_work+0x112/0x1fa [90251.832245] [f8621a60] ? ieee80211_scan_rx+0x139/0x139 [mac80211] [90251.832251] [c104a86e] ? worker_thread+0xa9/0x122 [90251.832256] [c104a7c5] ? manage_workers.isra.23+0x13d/0x13d [90251.832261] [c104d1af] ? kthread+0x63/0x68 [90251.832266] [c104d14c] ? kthread_worker_fn+0x101/0x101 [90251.832272] [c12c5afe] ? kernel_thread_helper+0x6/0x10 [90251.832276] ---[ end trace ed08b3df81233578 ]---
Bug#671803: linux-image-3.2.0-2-amd64: brcmsmac/80211 wireless, kernel prints some errors
On Mon, May 07, 2012 at 03:30:14AM +0300, Touko Korpela wrote: Package: linux-2.6 Version: 3.2.16-1 Severity: normal Thanks for brcmsmac: INTERMEDIATE but not AMPDU only when tracing fix in 3.2.16-1. Kernel still prints some wlan errors, but they don't cause major trouble in my light use. Still, maybe this can be fixed. Something is broken in this driver, I think. I commented wlan entries in /etc/network/interfaces, to put interface under wicd control. Interface /doesn't come up right during boot. I reported wicd bug #671838 about it, but /there looks like to be also bug in kernel (or could it be boot ordering /issue, system boots quite fast from SSD). -- 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/20120507173324.GA32599@tiikeri.vuoristo.local
Bug#671803: linux-image-3.2.0-2-amd64: brcmsmac/80211 wireless, kernel prints some errors
Package: linux-2.6 Version: 3.2.16-1 Severity: normal Thanks for brcmsmac: INTERMEDIATE but not AMPDU only when tracing fix in 3.2.16-1. Kernel still prints some wlan errors, but they don't cause major trouble in my light use. Still, maybe this can be fixed. -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.16-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Apr 30 05:20:23 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/LISKO_VG-rootlv ro quiet ** Not tainted ** Kernel log: [8.729883] [drm] Encoders: [8.729886] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [8.729973] [drm] Internal thermal controller without fan control [8.730114] [drm] radeon: power management initialized [8.731062] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [8.759879] cfg80211: World regulatory domain updated: [8.759888] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [8.759894] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.759899] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.759905] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.759910] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.759914] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.760407] cfg80211: Calling CRDA for country: US [8.772343] cfg80211: Regulatory domain changed to country: US [8.772351] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [8.772358] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2700 mBm) [8.772363] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) [8.772368] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.772373] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.772378] cfg80211: (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.772382] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) [9.197344] [drm] fb mappable at 0xC0142000 [9.197350] [drm] vram apper at 0xC000 [9.197353] [drm] size 4325376 [9.197356] [drm] fb depth is 24 [9.197359] [drm]pitch is 5632 [9.197735] fbcon: radeondrmfb (fb0) is primary device [9.610259] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1c0b1, caps: 0xd04733/0xa4/0xa0400 [9.682588] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input9 [9.719153] Console: switching to colour frame buffer device 170x48 [9.725856] fb0: radeondrmfb frame buffer device [9.725859] drm: registered panic notifier [9.725889] [drm] Initialized radeon 2.12.0 20080528 for :00:01.0 on minor 0 [9.726105] snd_hda_intel :00:01.1: PCI INT B - GSI 19 (level, low) - IRQ 19 [9.726245] snd_hda_intel :00:01.1: irq 44 for MSI/MSI-X [9.726285] snd_hda_intel :00:01.1: setting latency timer to 64 [9.747210] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0 [9.747433] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input10 [9.747897] snd_hda_intel :00:14.2: PCI INT A - GSI 16 (level, low) - IRQ 16 [9.803112] input: HDA ATI SB Mic as /devices/pci:00/:00:14.2/sound/card1/input11 [9.803293] input: HDA ATI SB Headphone as /devices/pci:00/:00:14.2/sound/card1/input12 [ 10.282109] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 10.354361] EXT4-fs (dm-1): re-mounted. Opts: commit=60,errors=remount-ro [ 10.435938] loop: module loaded [ 11.308327] Adding 974844k swap on /dev/mapper/LISKO_VG-swap--1. Priority:-1 extents:1 across:974844k SS [ 11.385273] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 11.396651] EXT4-fs (dm-3): mounted filesystem without journal. Opts: commit=60 [ 11.808047] RPC: Registered named UNIX socket transport module. [ 11.808054] RPC: Registered udp transport module. [ 11.808058] RPC: Registered tcp transport module. [ 11.808061] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 11.836050] FS-Cache: Loaded [ 11.860396] FS-Cache: Netfs 'nfs' registered for caching [ 11.882704] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 12.019327] ieee80211 phy0: brcms_ops_config: change monitor mode: false (implement) [ 12.019336] ieee80211 phy0: brcms_ops_config: change power-save mode: false (implement) [ 12.019838] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 12.020920] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 12.271306] fuse init (API version 7.17) [ 12.687535] wlan0: authenticate with 02:24:a5:da:fa:e8 (try 1) [ 12.689640] wlan0: authenticated [ 12.693079] wlan0:
Re: cpufrequtils doesn't support new AMD cpus
#hardware support severity 654957 important quit Here is modified patch to add support for AMD Bulldozer (21) and Llano (18) processors. I hope someone can check this and upload cpufrequtils. --- debian/cpufrequtils.loadcpufreq.init.dist 2011-08-03 14:50:31.0 +0300 +++ debian/cpufrequtils.loadcpufreq.init 2012-05-01 21:46:50.282085437 +0300 @@ -119,7 +119,7 @@ # K7 MODULE=powernow-k7 ;; -15|16|17|20) +15|16|17|18|20|21) # K8 MODULE=powernow-k8 ;;
Re: cpufrequtils: New upstream release (008)
Cpufrequtils homepage link (under kernel.org) doesn't seem to work anymore. I found https://github.com/emagii/cpufrequtils It says: Clone of kernel.org cpufrequtils, until it is back in business Can it considered new home of cpufrequtils for now? It has some changes after 008 too. -- 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/20120501194721.GA4021@lisko
Re: Time to update initramfs-tools version at backports?
On Sat, Apr 28, 2012 at 10:59:30PM +0200, Alexander Wirt wrote: Touko Korpela schrieb am Saturday, den 28. April 2012: Squeeze-backports is at version 0.99, while wheezy/sid has now 0.102 That per se is no reason for a backport. If backport is already available (like this package), it should be kept in sync (if possible) with testing, so new features and bugfixes also reach backport users. -- 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/20120429143812.GA18810@tiikeri.vuoristo.local
Time to update initramfs-tools version at backports?
Squeeze-backports is at version 0.99, while wheezy/sid has now 0.102 -- 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/20120428204732.GA11166@lisko
Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]
On Sun, Apr 22, 2012 at 08:04:36PM -0500, Jonathan Nieder wrote: Teodor MICU wrote: I just tested this (linux image from stable-proposed-updates) and there is no change: the console is fuzzy during boot. Great, thanks for testing. How about the second question --- is the radeon firmware installed? You can find out with dpkg -l firmware-linux Just to be clear, if the bug is only reproducible when the radeon firmware is not installed, it would still be an important bug. That would just help us to know where to look. I think you should check if firmware-linux-nonfree package is installed (because Radeon firmware is located there). -- 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/20120423101735.GA32036@tiikeri.vuoristo.local
Bug#649448: radeon (evergreen): random-looking pattern of pixels when firmware not installed
Installer has also a bug report about this (#661069). It would be good if Debian kernel radeon driver learned to fall back sensibly if running on hardware where firmware is required. Also installer should warn user about what happens if firmware is missing. -- 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/20120423182150.GA8524@tiikeri.vuoristo.local
brcmsmac patch for INTERMEDIATE but not AMPDU log spam
I'm seeing a lot of kernel log entries like this under wheezy kernels: ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU This patch should hide them: http://article.gmane.org/gmane.linux.kernel.wireless.general/89512 -- 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/20120423200558.GA28974@lisko
Re: cpufrequtils doesn't support new AMD cpus
On Fri, Feb 03, 2012 at 04:14:52AM +, Ben Hutchings wrote: On Fri, 2012-02-03 at 04:16 +0200, Touko Korpela wrote: On Sat, Jan 07, 2012 at 03:30:04PM +0200, Touko Korpela wrote: I think you should also add family 18 (AMD Fusion Llano). http://www.phoronix.com/vr.php?view=16292 On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: Package: cpufrequtils Version: 007-2 Severity: normal Tags: patch /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have a CPU family of 21. The processor is supported by the powernow_k8 module. --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 23:35:24.867961318 -0600 +++ debian/cpufrequtils.loadcpufreq.init2012-01-06 23:35:32.759956550 -0600 @@ -119,7 +119,7 @@ # K7 MODULE=powernow-k7 ;; -15|16|17|20) +15|16|17|20|21) # K8 MODULE=powernow-k8 ;; I hope that you upload cpufrequtils with support for AMD processor families 18 and 21 There has been some work to generate module aliases and uevents for x86 CPU features. This would allow udev to load cpufreq drivers just like any other device, removing the need for cpufrequtils to know which drivers handle which CPUs. It looks like this will be going into Linux 3.4 but I would be open to backporting this feature to 3.2 for wheezy. The changes I see in linux-next are: I hope that some solution can be found for this issue, either in cpufrequtils or in kernel. -- 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/20120423214003.GA13325@tiikeri.vuoristo.local
Bug#663269: [3.2.7 - 3.2.9 regression] rt flavor: Hard freezes when starting KDM
On Sun, Mar 11, 2012 at 07:37:51PM +0400, Boris Pek wrote: Hi, startx command launched LXDE (I have both KDE and LXDE) and it worked normally. Thanks --- this is a very useful detail. So probably non-accelarated rendering works fine, and it is something in 3d codepaths that makes it freeze. Ok. I saw interesting instructions in bug report #663379. Could I help in a same way? I can build kernel (or few modules) with patches for tests. Today I have a little free time for this. But I have only 32 system for tests... dmesg log is attached. But it also useless I think. When system freezes logs are not updated... The attached log seems to be for a boot with the non-rt kernel. Am I understanding correctly? Yes, you are right. Sorry, but I don't know how I can get logs from previous boot. As I wrote earlier /var/log/Xorg.1.log is outdated. Maybe check /var/log/Xorg.0.log.old (logs between Xorg.0.log and Xorg.1.log)? -- 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/20120311211752.GA22162@tiikeri.vuoristo.local
Bug#659948: [initramfs-tools] Fails to upgrade (Sid)
On Wed, Feb 15, 2012 at 12:23:47PM +0200, David Baron wrote: On Wednesday 15 February 2012 11:40:02 Michael Prokop wrote: * David Baron [Wed Feb 15, 2012 at 10:49:53AM +0200]: --- Please enter the report below this line. --- On attempted upgrade From which initramfs-tools version are you upgrading? Previous Sid version. update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-1-686-pae /rootfs: No such file or directory mkinitramfs: for root /rootfs missing /rootfs /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-3.2.0-1-686-pae with 1. dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: initramfs-tools Did you recently switch to the usage of root=UUID=df24bea0-5520-4281-b053-021bd5a96628 or did you use the very same kernel command line also with the older version of initramfs-tools? No change here. -- /etc/initramfs-tools/initramfs.conf MODULES=dep Same question for MODULES=dep (and as noted in the error message switching to MODULES=most will work around your issue). This makes things too big for lilo (or at least did so previously) Please try to enable large-memory option in lilo.conf. It should help at loading larger initramfs. -- 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/20120216152232.GA26559@tiikeri.vuoristo.local
Re: cpufrequtils doesn't support new AMD cpus
On Fri, Feb 03, 2012 at 04:14:52AM +, Ben Hutchings wrote: On Fri, 2012-02-03 at 04:16 +0200, Touko Korpela wrote: On Sat, Jan 07, 2012 at 03:30:04PM +0200, Touko Korpela wrote: I think you should also add family 18 (AMD Fusion Llano). http://www.phoronix.com/vr.php?view=16292 On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: Package: cpufrequtils Version: 007-2 Severity: normal Tags: patch /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have a CPU family of 21. The processor is supported by the powernow_k8 module. --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 23:35:24.867961318 -0600 +++ debian/cpufrequtils.loadcpufreq.init2012-01-06 23:35:32.759956550 -0600 @@ -119,7 +119,7 @@ # K7 MODULE=powernow-k7 ;; -15|16|17|20) +15|16|17|20|21) # K8 MODULE=powernow-k8 ;; I hope that you upload cpufrequtils with support for AMD processor families 18 and 21 There has been some work to generate module aliases and uevents for x86 CPU features. This would allow udev to load cpufreq drivers just like any other device, removing the need for cpufrequtils to know which drivers handle which CPUs. It looks like this will be going into Linux 3.4 but I would be open to backporting this feature to 3.2 for wheezy. The changes I see in linux-next are: Nice, but until kernel has this feature, I think that cpufrequtils should be updated. -- 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/20120203134216.GA28354@tiikeri.vuoristo.local
cpufrequtils doesn't support new AMD cpus
On Sat, Jan 07, 2012 at 03:30:04PM +0200, Touko Korpela wrote: I think you should also add family 18 (AMD Fusion Llano). http://www.phoronix.com/vr.php?view=16292 On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: Package: cpufrequtils Version: 007-2 Severity: normal Tags: patch /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have a CPU family of 21. The processor is supported by the powernow_k8 module. --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 23:35:24.867961318 -0600 +++ debian/cpufrequtils.loadcpufreq.init2012-01-06 23:35:32.759956550 -0600 @@ -119,7 +119,7 @@ # K7 MODULE=powernow-k7 ;; -15|16|17|20) +15|16|17|20|21) # K8 MODULE=powernow-k8 ;; I hope that you upload cpufrequtils with support for AMD processor families 18 and 21 -- 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/20120203021658.GA14357@tiikeri.vuoristo.local
Bug#649448: udev loading radeon drivers garbles screen output
On Mon, Nov 21, 2011 at 09:33:28AM -0500, Alex Deucher wrote: On Sun, Nov 20, 2011 at 10:12 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2011-11-20 at 19:02 -0600, Jonathan Nieder wrote: reassign 649448 src:linux-2.6 linux-2.6/3.0.0-3 severity 649448 important retitle 649448 radeon (evergreen): random-looking pattern of pixels when firmware not installed tags 649448 + upstream quit Hi Martin, Martin von Gagern wrote: Version: 3.0.0-3 [...] Just installed a wheezy setup using debootstrap, adding grub-pc and linux-image-amd64 after the chroot was created. The kernel boots, the initrd seems all right. When the main system boots up, udev gets launced pretty early. Soon after it is started, the screen turns into a pretty random-looking pattern of pixels, making the console pretty unusable. This also happens in recovery i.e. single-user mode. [...] Possible workarounds seem to include: [...] - Adding a line blacklist radeon to /etc/modprobe.d/blacklist.conf, followed by running depmod -a. [...] [ 150.125768] r600_cp: Failed to load firmware radeon/SUMO2_pfp.bin [ 150.125818] [drm:evergreen_startup] *ERROR* Failed to load firmware! [ 150.125859] radeon :00:01.0: disabling GPU acceleration Yes, the radeon driver currently copes poorly when firmware is missing. Compare [1], [2], [3]. [...] Not having GPU accelleration due to lack of free firmware is acceptable. Not having a usable text console can be a real problem. Agreed. The radeon driver should be bailing out when firmware is missing for cards that need it, but that is not working for some reason. [...] At the time I converted the radeon driver to load external firmware, it was apparently only required for 3D acceleration and both KMS and 2D acceleration of X worked without it, at least on those systems I tested (which were quite old, R100-R300 families). Therefore failure to load firmware would only result in DRM (3D acceleration support) being disabled. However, it looks like driver support for the R600 family onward now absolutely requires the 'RLC' firmware blobs: commit d8f60cfc93452d0554f6a701aa8e3236cbee4636 Author: Alex Deucher alexdeuc...@gmail.com Date: Tue Dec 1 13:43:46 2009 -0500 drm/radeon/kms: Add support for interrupts on r6xx/r7xx chips (v3) And the 'Northern Islands' GPUs and 'Fusion' APUs appear to require the 'MC' firmware blobs: commit 0af62b0168043896a042b005ff88caa77dd94d04 Author: Alex Deucher alexdeuc...@gmail.com Date: Thu Jan 6 21:19:31 2011 -0500 drm/radeon/kms: add ucode loader for NI Therefore I think that at least r600_init(), rv770_init(), evergreen_init() and cayman_init() should be treating failure to load firmware as a fatal error. R6xx, r7xx should work ok without the RLC ucode, you just won't get acceleration. With chips that require the MC ucode, the driver will bail if the MC ucode is not available. In what kernel versions should that be true? These bugs are reported that question it (some are reported against older kernels). http://bugs.debian.org/607194 http://bugs.debian.org/637943 http://bugs.debian.org/627497 and also my report: http://bugs.debian.org/646306 -- 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/2022120853.GA17965@tiikeri.vuoristo.local
Re: Needed cpufrequtils version
On Sun, Oct 30, 2011 at 01:41:17PM +0200, Touko Korpela wrote: Should current kernel Break cpufrequtils versions lower than 007-2 because of bug #636141? Any comment on this? I think squeeze users (or others that still use 007-1) using wheezy/sid kernel may have broken cpu frequency scaling. -- 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/2003125608.GA17599@lisko
Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing
On Mon, Oct 24, 2011 at 11:01:01AM +0200, Jort Koopmans wrote: On Sun, 2011-10-23 at 14:05 +0300, Touko Korpela wrote: [..] madduck called testing for experimental version of mdadm. where it can be downloaded? My bad, I missed the initscripts package from sid (instead of testing). I must note that none of the involved packages are available in experimental (and mdadm and debianutils are equal in testing and unstable atm). Upgraded initscripts; initscripts [2.88dsf-13.11 - 2.88dsf-13.12] Reinstalled mdadm (from sid, but same version), generated a new initrd just to be safe. But again that didnt fix the problem. I know difference between sid and experimental. Is there more recent version of mdadm available than is in sid now? (experimental suite doesn't have it) -- 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/20111024110332.GA3769@tiikeri.vuoristo.local
Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing
On Sun, Oct 23, 2011 at 12:09:11PM +0200, Jort Koopmans wrote: Is there anything else I can do to triage this bug? I'd be happy to try any suggestions to get this bug solved (in a future release). Waiting for any response, Jort Koopmans madduck called testing for experimental version of mdadm. where it can be downloaded? -- 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/20111023110509.GA6888@tiikeri.vuoristo.local
Re: Re: linux-image-2.26.32-5-686: Kerneloops and race condition after USB2 HDD disconnection, preventing clean shutdown
On Sat, Oct 08, 2011 at 10:51:46AM +0100, Ad L. wrote: (Re-sent to the correct address) I really should spend time on studying for an exam coming up in a few days, and reportbug doesn't seem to run as it should, or it secretly sent a mail twice. Tried it as normal user and as root, but really shouldn't be searching for answers now, whether on man pages, reference manual or internet. For convenience, I'm including a quickly shortened version of the report with this post, in plain text format. Attachments: bug-report_000_short.log (plain text) No solution for this issue, but you attachment was encoded as binary file, not as plain text. So it it doesn't show inline at some mail setups. -- 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/20111016131501.GA28513@tiikeri.vuoristo.local
Re: [Pkg-sysvinit-devel] Bug#644572: sysvinit: Spins disk up briefly from standby during poweroff
On Thu, Oct 06, 2011 at 09:57:05PM -0300, Henrique de Moraes Holschuh wrote: On Fri, 07 Oct 2011, Touko Korpela wrote: I suspect that -h option that halt gets during poweroff is buggy and shouldn't spin disks up that are already at sleep. Nowadays we're supposed to trust the kernel to do it right, and your disk should spin up only if it has crap firmware (unlikely). Unless you're using the deprecated old ide drivers (/dev/hd*), in which case all bets are off. Please edit /etc/init.d/halt and make it not add -h to the halt invocation (but make sure to add sync ; sleep 5 before the halt command just in case). Does that fix the issue? It doesn't make a difference. So maybe it's a kernel issue then. Same happens with another laptop that has Hitachi HTS54502 disk, so this issue is more common. This has a Seagate disk. Here is some lines from kernel 3.0.0-1-amd64 (Debian 3.0.0-3) boot dmesg. [1.425212] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [1.651042] SCSI subsystem initialized [1.681254] ahci :00:11.0: AHCI 0001.0200 32 slots 1 ports 3 Gbps 0x1 impl SATA mode [1.690438] scsi0 : ahci [1.690697] ata1: SATA max UDMA/133 abar m1024@0xfeb4c000 port 0xfeb4c100 irq 19 [2.196281] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.504191] ata1.00: ATA-8: ST9500325AS, 0003SDM1, max UDMA/133 [2.504199] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [2.506494] ata1.00: configured for UDMA/133 [2.507008] scsi 0:0:0:0: Direct-Access ATA ST9500325AS 0003 PQ: 0 ANSI: 5 [2.517044] scsi1 : usb-storage 2-2:1.0 [2.518624] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) [2.518751] sd 0:0:0:0: [sda] Write Protect is off [2.518757] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [2.518810] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.548221] sda: sda1 sda2 sda3 sda4 [2.549024] sd 0:0:0:0: [sda] Attached SCSI disk [3.650505] scsi 1:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0 [4.608143] sd 1:0:0:0: [sdb] Attached SCSI removable disk -- 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/20111007112906.GA25171@tiikeri.vuoristo.local
Re: Bug#644572: Spins disk up briefly from standby during poweroff
On Fri, Oct 07, 2011 at 02:29:06PM +0300, Touko Korpela wrote: On Thu, Oct 06, 2011 at 09:57:05PM -0300, Henrique de Moraes Holschuh wrote: Nowadays we're supposed to trust the kernel to do it right, and your disk should spin up only if it has crap firmware (unlikely). Unless you're using the deprecated old ide drivers (/dev/hd*), in which case all bets are off. Please edit /etc/init.d/halt and make it not add -h to the halt invocation (but make sure to add sync ; sleep 5 before the halt command just in case). Does that fix the issue? It doesn't make a difference. So maybe it's a kernel issue then. Same happens with another laptop that has Hitachi HTS54502 disk, so this issue is more common. This has a Seagate disk. Here is some lines from kernel 3.0.0-1-amd64 (Debian 3.0.0-3) boot dmesg. [1.425212] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [1.651042] SCSI subsystem initialized [1.681254] ahci :00:11.0: AHCI 0001.0200 32 slots 1 ports 3 Gbps 0x1 impl SATA mode [1.690438] scsi0 : ahci [1.690697] ata1: SATA max UDMA/133 abar m1024@0xfeb4c000 port 0xfeb4c100 irq 19 [2.196281] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.504191] ata1.00: ATA-8: ST9500325AS, 0003SDM1, max UDMA/133 [2.504199] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [2.506494] ata1.00: configured for UDMA/133 [2.507008] scsi 0:0:0:0: Direct-Access ATA ST9500325AS 0003 PQ: 0 ANSI: 5 [2.517044] scsi1 : usb-storage 2-2:1.0 [2.518624] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) [2.518751] sd 0:0:0:0: [sda] Write Protect is off [2.518757] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [2.518810] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.548221] sda: sda1 sda2 sda3 sda4 [2.549024] sd 0:0:0:0: [sda] Attached SCSI disk [3.650505] scsi 1:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0 [4.608143] sd 1:0:0:0: [sdb] Attached SCSI removable disk Here is missing ahci lines from that dmesg [1.681098] ahci :00:11.0: version 3.0 [1.681139] ahci :00:11.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [1.681262] ahci :00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part -- 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/20111007122559.GA27624@tiikeri.vuoristo.local
Bug#635826: hda-intel (CX20549 (Venice)): external speaker output and mic inputs mute
On Thu, Aug 25, 2011 at 07:16:34PM +0200, Johann Felix Soden wrote: Hi, Since I have a hardware failure now and have not reported this bug upstream yet, I would be glad, if you, Antony, could take care of this. For the same reason, I cannot say anything about ogg123. Some time ago, I used HDA Analyzer [1] and could enable the external speaker output by enabling EAPD, unmuting and raising the volume of the right pin. Best regards, Johann Felix [1] http://www.alsa-project.org/main/index.php/HDA_Analyzer Unfortunately, Alsa upstream support seems to be nonexistent lately. Nobody takes any action on bugs reported to bug tracker there. Also if you try to mail alsa-devel list and you're not subscribed, your mail is stuck in some hole (it should be reviewed by moderators instead). -- 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/20110828140454.GA10116@tiikeri.vuoristo.local
Bug#635826: hda-intel (CX20549 (Venice)): external speaker output and mic inputs mute
On Sun, Aug 28, 2011 at 06:52:44PM +0100, Ben Hutchings wrote: On Sun, 2011-08-28 at 17:04 +0300, Touko Korpela wrote: [1] http://www.alsa-project.org/main/index.php/HDA_Analyzer Unfortunately, Alsa upstream support seems to be nonexistent lately. Nobody takes any action on bugs reported to bug tracker there. The bug tracker is a trap. Bugs reported to the mailing list or a specific driver maintainer are more likely to get fixed. It would make sense if driver maintainers were following bugs that are reported under their own section. However many bugs are in wrong section. Also if you try to mail alsa-devel list and you're not subscribed, your mail is stuck in some hole (it should be reviewed by moderators instead). You can whitelist yourself by subscribing to the list and then setting the no-mail option. -- 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/20110828181020.GA15231@tiikeri.vuoristo.local
Re: lkcl interference with initramfs-tools bug handling
On Tue, Aug 23, 2011 at 08:05:26PM +, maximilian attems wrote: On Mon, Aug 22, 2011 at 09:10:17PM +0100, Ben Hutchings wrote: Luke Kenneth Casson Leighton l...@lkcl.net (lkcl) reported bug #636123, which then received a follow-up which is very clearly (to me) this guy is adding to much noise, so that various bug reports get useless. if strong words didn't help yet, please cut him off. Maybe give him one more chance. I told him that messages to bug address don't reach bug submitter (he wasn't aware of it, now he knows). That has caused some miscommunication before. It would be good if more people could help with bugs if right ways are told. -- 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/20110823205833.GA31830@tiikeri.vuoristo.local
Bug#638878: linux-image-3.0.0-1-amd64: Maybe report Debian kernel version with uname
Package: linux-2.6 Version: 3.0.0-2 Severity: wishlist Would it be possible to report Debian kernel version in uname output? Maybe it can be added to kernel version string, uname -v (now it's #1 SMP Wed Aug 17 05:07:22 UTC 2011. This information is present in /proc/version and could be in uname too. -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-2) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-5) ) #1 SMP Wed Aug 17 05:07:22 UTC 2011 ** Model information sys_vendor: ASUSTeK Computer INC. product_name: 1215B product_version: x.x chassis_vendor: ASUSTeK Computer INC. chassis_version: x.x bios_vendor: American Megatrends Inc. bios_version: 0401 board_vendor: ASUSTeK Computer INC. board_name: 1215B board_version: x.xx ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1510] Subsystem: Advanced Micro Devices [AMD] Device [1022:1510] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9802] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84a5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 43 Region 0: Memory at c000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at f000 [size=256] Region 2: Memory at feb0 (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: radeon 00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:1314] Subsystem: ASUSTeK Computer Inc. Device [1043:84a5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 44 Region 0: Memory at feb44000 (32-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1512] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: fea0-feaf Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (prog-if 01 [AHCI 1.0]) Subsystem: ATI Technologies Inc Device [1002:4390] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 Interrupt: pin A routed to IRQ 19 Region 0: I/O ports at f140 [size=8] Region 1: I/O ports at f130 [size=4] Region 2: I/O ports at f120 [size=8] Region 3: I/O ports at f110 [size=4] Region 4: I/O ports at f100 [size=16] Region 5: Memory at feb4c000 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ahci 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 18 Region 0: Memory at feb4b000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] (prog-if 20 [EHCI]) Subsystem: ATI Technologies Inc SB700/SB800 USB EHCI
Bug#638878: linux-image-3.0.0-1-amd64: Maybe report Debian kernel version with uname
On Mon, Aug 22, 2011 at 01:44:03PM -0500, Jonathan Nieder wrote: Ben Hutchings wrote: Touko Korpela wrote: Would it be possible to report Debian kernel version in uname output? Maybe it can be added to kernel version string, uname -v (now it's #1 SMP Wed Aug 17 05:07:22 UTC 2011. This information is present in /proc/version and could be in uname too. [...] I don't think uname(1) should be changed; it is supposed to report just what uname(2) does. We should change the behaviour of the latter, if anything. Ah, ok. I admit my bias is towards not passing this information back from uname(2), since application authors could be tempted to parse it to provide Debian-specific behavior changes (for example, to work around bugs using the Debian kernel version number instead of finding some robust way to work around them that applies to other distros, too). On the other hand, as a human-readable version identifier, linux-2.6 3.0.0-2 as compiled by Ben Hutchings on 2011-08-17 04:08:52 is more convenient than Linux 3.0.0-1-amd64 #1 SMP Wed Aug 17 04:08:52 UTC 2011 x86_64 GNU/Linux What is the underlying problem being solved? Is it that it is hard when reporting bugs to tell the difference between the package version and ABI version in order to provide the former? For example when reporting bugs upstream and using their scripts. It's true that you can sometimes guess Debian version number from the compile time (that shows in uname) but if Debian version can be added there I say go for it. -- 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/20110822191533.GA31021@tiikeri.vuoristo.local
Bug#638878: linux-image-3.0.0-1-amd64: Maybe report Debian kernel version with uname
On Mon, Aug 22, 2011 at 11:27:10AM -0600, Bob Proulx wrote: tags 638878 + moreinfo thanks Touko Korpela wrote: Would it be possible to report Debian kernel version in uname output? Maybe it can be added to kernel version string, uname -v (now it's #1 SMP Wed Aug 17 05:07:22 UTC 2011. This information is present in /proc/version and could be in uname too. Exactly what information is it precisely that you wish included in 'uname' output? Because uname already includes the kernel version information. $ uname -a Linux example 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux It shows now only Debian package name (3.0.0-1-amd64 part), not version (3.0.0-2). I don't yet know what information you want to access from /proc/version but since accessing specific information from /proc/version is intrinsically non-portable it seems bad to hack it into 'uname' making it more non-portable. And since it is trivial to read it from /proc/version directly there doesn't seem to be any need to hack this into 'uname'. Why not read it from /proc/version directly? It's simpler if you don't need to find data from many places. I think uname -a should tell version of kernel package used if that information is available. -- 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/20110822194408.GB31021@tiikeri.vuoristo.local
Bug#638896: clarification
On Mon, Aug 22, 2011 at 08:48:24PM +0100, Luke Kenneth Casson Leighton wrote: valentijn, hi, Your messages don't reach valentijn if you only send mail to bugnumber address...people aren't automatically subscribed to bugs. -- 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/2011082142.GA3977@tiikeri.vuoristo.local
Bug#638896: linux-image-2.6.39-bpo.2-amd64 root filesystem not found on boot [SOLVED?]
On Mon, Aug 22, 2011 at 10:47:24PM +0200, Valentijn Scholten wrote: After making some backups, I tried to upgrade the kernel again. Guess what? It just works now. The term.log section looks nothing like the one above. Also the old kernel has been retained. Please use reply fuction when posting to existing bug, if possible. Failure to do so breaks threading. -- 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/20110822231709.GA5332@tiikeri.vuoristo.local
Bug#634681: linux-image-2.6.39-2-686-pae: Usb oops with 2.6.39 (elv_put_request)
Package: linux-2.6 Version: 2.6.39-3 Severity: important Plug/unplug (interface disconnected)/plug cycle with Huawei E1552 USB 3G modem (also emulates cdrom) sometimes causes kernel oops. Wlan was disabled at crash time. Oops message is at end of this message. -- Package-specific info: ** Version: Linux version 2.6.39-2-686-pae (Debian 2.6.39-3) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Tue Jul 5 03:48:49 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.39-2-686-pae root=UUID=62cb7fd9-4ec9-4341-a4f6-9b8915f25a70 ro quiet ** Tainted: WC (1536) * Taint on warning. * Module from drivers/staging has been loaded. ** Kernel log: [ 11.864809] [drm] Connector 1: [ 11.864811] [drm] VGA [ 11.864813] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [ 11.864816] [drm] Encoders: [ 11.864817] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 11.864820] [drm] Connector 2: [ 11.864821] [drm] HDMI-A [ 11.864823] [drm] HPD1 [ 11.864825] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [ 11.864828] [drm] Encoders: [ 11.864829] [drm] DFP1: INTERNAL_UNIPHY [ 11.936853] [drm] radeon: power management initialized [ 11.991446] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 11.993499] Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa4/0xa [ 12.045115] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8 [ 12.106383] HDA Intel :00:14.2: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 12.187711] hda_codec: ALC269VB: BIOS auto-probing. [ 12.191024] input: HDA ATI SB Mic as /devices/pci:00/:00:14.2/sound/card0/input9 [ 12.191167] input: HDA ATI SB Headphone as /devices/pci:00/:00:14.2/sound/card0/input10 [ 12.957622] [drm] fb mappable at 0xC0141000 [ 12.957626] [drm] vram apper at 0xC000 [ 12.957628] [drm] size 4325376 [ 12.957630] [drm] fb depth is 24 [ 12.957632] [drm]pitch is 5632 [ 12.957798] fbcon: radeondrmfb (fb0) is primary device [ 13.011803] Console: switching to colour frame buffer device 170x48 [ 13.027432] fb0: radeondrmfb frame buffer device [ 13.027435] drm: registered panic notifier [ 13.027443] [drm] Initialized radeon 2.9.0 20080528 for :01:05.0 on minor 0 [ 13.027488] HDA Intel :01:05.1: PCI INT B - GSI 19 (level, low) - IRQ 19 [ 13.027548] HDA Intel :01:05.1: setting latency timer to 64 [ 13.342919] EXT4-fs (sdc1): re-mounted. Opts: (null) [ 13.427712] EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro [ 13.470358] loop: module loaded [ 13.727521] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 14.584343] fuse init (API version 7.16) [ 15.948604] powernow-k8: Found 1 AMD Athlon(tm) II Neo K125 Processor (1 cpu cores) (version 2.20.00) [ 15.948647] powernow-k8:0 : pstate 0 (1700 MHz) [ 15.948650] powernow-k8:1 : pstate 1 (1300 MHz) [ 15.948653] powernow-k8:2 : pstate 2 (800 MHz) [ 16.310958] Bluetooth: RFCOMM TTY layer initialized [ 16.310969] Bluetooth: RFCOMM socket layer initialized [ 16.310974] Bluetooth: RFCOMM ver 1.11 [ 16.364565] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.364574] Bluetooth: BNEP filters: protocol multicast [ 16.402401] Bridge firewalling registered [ 18.387806] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 18.397134] sky2 :03:00.0: eth0: enabling interface [ 18.397500] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 25.385107] EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro,commit=60 [ 25.398795] EXT4-fs (sdb1): re-mounted. Opts: commit=60 [ 408.184184] usb 2-2: new high speed USB device number 3 using ehci_hcd [ 408.327872] usb 2-2: New USB device found, idVendor=12d1, idProduct=1446 [ 408.327882] usb 2-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 408.327890] usb 2-2: Product: HUAWEI Mobile [ 408.327895] usb 2-2: Manufacturer: HUAWEI Technology [ 408.334085] scsi6 : usb-storage 2-2:1.0 [ 408.334540] scsi7 : usb-storage 2-2:1.1 [ 409.075787] usb 2-2: USB disconnect, device number 3 [ 415.880194] usb 2-2: new high speed USB device number 4 using ehci_hcd [ 416.023850] usb 2-2: New USB device found, idVendor=12d1, idProduct=1001 [ 416.023861] usb 2-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 416.023869] usb 2-2: Product: HUAWEI Mobile [ 416.023874] usb 2-2: Manufacturer: HUAWEI Technology [ 416.032158] scsi11 : usb-storage 2-2:1.3 [ 416.034134] scsi12 : usb-storage 2-2:1.4 [ 416.138395] usbcore: registered new interface driver usbserial [ 416.138413] USB Serial support registered for generic [ 416.138912] usbcore: registered new interface driver usbserial_generic [ 416.138915] usbserial: USB Serial Driver core [ 416.183585] USB Serial support registered for GSM modem (1-port) [ 416.184222] option 2-2:1.0: GSM modem (1-port) converter detected [ 416.184400] usb 2-2: GSM modem (1-port)
Bug#632968: (linux-image-2.6.32-5-686-bigmem: Kernel log fill with repeated network driver errors)
On Fri, Jul 08, 2011 at 02:19:21AM +0100, Ben Hutchings wrote: On Thu, 2011-07-07 at 17:17 +0300, Touko Korpela wrote: I noticed that firmware-nonfree (0.30) has updated brcm80211 firmware that contains unspecified stability fixes. Maybe updated firmware-nonfree should go to stable updates too? Yes, possibly. Have you tested that version, and does it fix this problem? I think it makes these errors more rare, with new fw only one error has been logged. I'm going to try newer kernel next, with updated drivers and other fixes. -- 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/20110708090911.GA20260@tiikeri.vuoristo.local
Bug#632968: Acknowledgement (linux-image-2.6.32-5-686-bigmem: Kernel log fill with repeated network driver errors)
I noticed that firmware-nonfree (0.30) has updated brcm80211 firmware that contains unspecified stability fixes. Maybe updated firmware-nonfree should go to stable updates too? -- 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/20110707141731.GA2081@tiikeri.vuoristo.local
yaird support/bugreports against linux-2.6
Maybe you could take a look for reportbug script code example from glibc. They added script for preventing bogus bug reports against their package. Could same be added to kernel package telling it's bug in yaird and not in kernel? In my opinion you should keep support for alternate initrd generators. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392915: Is this fixed in 2.6.22?
Is fix for this freeze included in recent kernels? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434597: reopening 434597, severity of 434597 is grave, reassign 434597 to yaird
# Automatically generated email from bts, devscripts version 2.10.6 reopen 434597 severity 434597 grave #reassigning to yaird, you shouldn't close bugs too fast reassign 434597 yaird 0.0.12-20 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394742: Bluetooth related panic
Why did you downgrade this to normal? And didn't you have policy of a bug to be at least important severity for a fix to be included in stable kernel update. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430887: reopen
reopen 430887 thanks DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=4.0 (installer build 20070127-03:50) X_INSTALLATION_MEDIUM=cdrom umame -a: Linux portatel 2.6.18-3-486 #1 Sun Dec 10 18:57:11 UTC 2006 i686 unknown Your CD isn't official etch 4.0 but older. I don't know if that makes difference but it has slightly newer 2.6.18 kernel. You can update it without fully downloading new image by using jigdo-lite program from jigdo-file package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431055: probably pump issue
Pump is buggy, please try dhcp3-client instead. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: update-initramfs -k all -u
Tim Dijkstra wrote: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You should fix your mail system not to send quoted-printable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403871: Is this still relevant?
Is this patch still needed in 2.6.18.dfsg.1-12 or 2.6.20-1 ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
