Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
Hi, John Johansen wrote (13 Mar 2012 16:33:53 GMT) : sorry I missed this, Thank you, John, for your answers :) yes you can pull them out of the tarball, That would be 0002-AppArmor-compatibility-patch-for-v5-interface.patch that can be found in the kernel-patches/$LATEST/ directory of the apparmor Debian source package. Given $LATEST == 3.1 currently, see bellow for the Ubuntu patches that were maybe refreshed. John, do you confirm this patch does not depend on any of the two others? (namely: 0001-AppArmor-compatibility-patch-for-v5-network-controll.patch and 0003-AppArmor-Allow-dfa-backward-compatibility-with-broke.patch) or from the ubuntu kernel tree. I guess that would be http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=commit;h=56f928f0cbf810c047a9a72e4e5c4840800437ec John, please correct me if I did not guess right. There are also a new set of patches available against the 3.3 kernel. The static parts of the interface have been updated and pushed into the 3.4 kernel. And the goal is to get the other part into the 3.5 kernel (still a wip). John: I guess the Linux 3.2 kernel shipped in Precise will carry those patches, and this is why the v5 compat' patches got recently reverted in Precise's kernel tree, right? Though those will require a more recent userspace. John: that will be called 2.8, right? Regards, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- 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/857gynbhu2@boum.org
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
On 03/14/2012 03:24 AM, intrigeri wrote: Hi, John Johansen wrote (13 Mar 2012 16:33:53 GMT) : sorry I missed this, Thank you, John, for your answers :) yes you can pull them out of the tarball, That would be 0002-AppArmor-compatibility-patch-for-v5-interface.patch that can be found in the kernel-patches/$LATEST/ directory of the apparmor Debian source package. Given $LATEST == 3.1 currently, see bellow for the Ubuntu patches that were maybe refreshed. John, do you confirm this patch does not depend on any of the two others? It does not but there may be a small conflict or two to resolve if 0001-AppArmor-compatibility-patch-for-v5-network-controll.patch is not applied first. If it doesn't apply cleanly I will be happy to update it for you. (namely: 0001-AppArmor-compatibility-patch-for-v5-network-controll.patch and 0003-AppArmor-Allow-dfa-backward-compatibility-with-broke.patch) or from the ubuntu kernel tree. I guess that would be http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=commit;h=56f928f0cbf810c047a9a72e4e5c4840800437ec John, please correct me if I did not guess right. You are right There are also a new set of patches available against the 3.3 kernel. The static parts of the interface have been updated and pushed into the 3.4 kernel. And the goal is to get the other part into the 3.5 kernel (still a wip). John: I guess the Linux 3.2 kernel shipped in Precise will carry those patches, and this is why the v5 compat' patches got recently reverted in Precise's kernel tree, right? correct Though those will require a more recent userspace. John: that will be called 2.8, right? correct. The 2.8 userspace release will ship with precise and will be compatible with both the older and newer kernel interfaces. -- 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/4f607461.6020...@canonical.com
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
Hi, John Johansen wrote (14 Mar 2012 10:35:13 GMT) : There are also a new set of patches available against the 3.3 kernel. The static parts of the interface have been updated and pushed into the 3.4 kernel. And the goal is to get the other part into the 3.5 kernel (still a wip). John: I guess the Linux 3.2 kernel shipped in Precise will carry those patches, and this is why the v5 compat' patches got recently reverted in Precise's kernel tree, right? correct If the Debian kernel team was willing to carry some kind of AppArmor kernel/userspace interface patch, I'm now unsure if the old or new ones would be better suited. (I assume AppArmor 2.8 is released long enough before the Wheezy freeze, so that we can ship it in there, and are given this choice.) On the one hand, the old compat' patches are confidence inspiring, as they are small and have been shipped by Ubuntu for a while. On the other hand, it seems the new patches are being upstreamed, which makes them more appealing somehow than the older ones. John, I think it would help if you could please point us more precisely to the commits of the new interface that have been upstreamed already, and to the ones that have not been, so that we can get a rough idea of where things are at. Kees, others, what do you think? Regards, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc | The impossible just takes a bit longer. -- 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/85r4wva0vw@boum.org
Bug#663433: closed by Bastian Blank wa...@debian.org (Bug#663433: fixed in linux-2.6 3.2.10-1)
Am Dienstag, 13. März 2012 schrieben Sie: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #663433: udev: does not load acpiphp on ThinkPad T520 although it is needed for ExpressCard hotplugging Many thanks for fixing this issue. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- 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/201203141530.07550.mar...@lichtvoll.de
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
On Mon, Mar 12, 2012 at 12:44:29PM -0500, Jonathan Nieder wrote: Dafydd Harries wrote: Ar 12/03/2012 am 17:11, ysgrifennodd Venkataraman, Meenakshi: Dafydd Harries wrote: Like others, the problems seemed to start around 2.6.39. [...] Sadly, my dpkg.log only goes back to 3.0, which was installed last July (!). Thanks for checking, and sorry for the lack of clarity. /var/log/dpkg.log.1 et al might go back further. Yes, my logs go back as far as dpkg.log.8, which is last July. -- 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/20120314153724.GB7496@nia
Bug#633423: marked as done (autofs4 interface is broken between x86 and x86_64)
Your message dated Wed, 14 Mar 2012 18:57:50 +0100 with message-id 87haxroyjl@turtle.gmx.de and subject line Linux 3.2.10 contains the fix has caused the Debian Bug report #633423, regarding autofs4 interface is broken between x86 and x86_64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 633423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 29-1 Severity: important Today I installed and booted (with init=/bin/systemd) systemd for the first time. Alas, it does not work for me. :-( The last output on the screen was from systemd-fsck which successfully checked the root partition, then the boot hung without further output requiring to reboot with SysRq-b. Note that while I'm running a self-compiled kernel, the problem also occurred with the official 2.6.39-2-amd64 Debian kernel. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.0.0-rc6-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii initscripts2.88dsf-13.10 scripts for initializing and shutt ii libaudit0 1.7.13-1.2Dynamic library for security audit ii libc6 2.13-10 Embedded GNU C Library: Shared lib ii libcap21:2.21-1 support for getting/setting POSIX. ii libcryptsetup1 2:1.3.0-3 libcryptsetup shared library ii libdbus-1-31.4.12-4 simple interprocess messaging syst ii libpam0g 1.1.3-2 Pluggable Authentication Modules l ii libselinux12.0.98-1.1SELinux runtime shared libraries ii libudev0 171-2 libudev shared library ii libwrap0 7.6.q-21 Wietse Venema's TCP wrappers libra ii udev 171-2 /dev/ and hotplug management daemo ii util-linux 2.19.1-2 Miscellaneous system utilities Versions of packages systemd recommends: ii libpam-systemd29-1 system and service manager - PAM m Versions of packages systemd suggests: ii python2.6.6-14 interactive high-level object-orie pn systemd-gui none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Package: linux-2.6 Version: 3.2.10-1 This bug has been fixed in Linux 3.2.10 (autofs: work around unhappy compat problem on x86-64). I could not test the Debian kernel because of bug #662891, but a self-built 3.2.10 kernel works. ---End Message---
Bug#663906: linux-image-2.6.32-5-amd64: ksm does not work
Package: linux-2.6
Version: 2.6.32-35squeeze2
Severity: normal
enabling ksm by echo 1 /sys/kernel/mm/ksm/run has no effect
full_scans are always 0, no increment in any of the other variables
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35squeeze2) (da...@debian.org) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Sep 9 20:23:16 UTC 2011
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64
root=UUID=49a2baa4-c4fb-4b25-a847-da38aabf6eb4 ro quiet
** Tainted: P (1)
* Proprietary module has been loaded.
** Kernel log:
[1888762.816160] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[1888762.816185] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[1888762.816188] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[1888762.816195] ata1.00: status: { DRDY }
[1888762.816207] ata1: hard resetting link
[1888763.136059] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[1888763.160243] ata1.00: configured for UDMA/100
[1888763.165702] ata1: EH complete
[1888793.816223] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[1888793.816236] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[1888793.816260] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[1888793.816264] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[1888793.816270] ata1.00: status: { DRDY }
[1888793.816284] ata1: hard resetting link
[1888794.136058] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[1888794.160243] ata1.00: configured for UDMA/100
[1888794.160859] ata1: EH complete
[124.816182] ata1.00: limiting speed to UDMA/66:PIO4
[124.816192] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[124.816202] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[124.816226] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[124.816230] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[124.816236] ata1.00: status: { DRDY }
[124.816249] ata1: hard resetting link
[125.136058] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[125.160243] ata1.00: configured for UDMA/66
[125.160812] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[125.160820] sr 0:0:0:0: [sr0] Sense Key : Aborted Command [current]
[descriptor]
[125.160827] Descriptor sense data with sense descriptors (in hex):
[125.160831] 72 0b 00 00 00 00 00 0e 09 0c 00 00 00 02 00 00
[125.160845] 00 08 00 00 a0 40
[125.160853] sr 0:0:0:0: [sr0] Add. Sense: No additional sense information
[125.160860] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[125.160874] end_request: I/O error, dev sr0, sector 33129740
[125.160907] ata1: EH complete
[155.816222] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[155.816235] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 05 2c 00 00 01 00
[155.816259] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[155.816263] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[155.816269] ata1.00: status: { DRDY }
[155.816283] ata1: hard resetting link
[156.136058] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[156.160244] ata1.00: configured for UDMA/66
[156.160811] ata1: EH complete
[1898559.432027] usb 1-6: new high speed USB device using ehci_hcd and address 4
[1898560.344047] hub 1-0:1.0: unable to enumerate USB device on port 6
[1898560.716021] usb 4-2: new full speed USB device using ohci_hcd and address 2
[1898560.918991] usb 4-2: not running at top speed; connect to a high speed hub
[1898560.942991] usb 4-2: New USB device found, idVendor=1949, idProduct=0004
[1898560.942998] usb 4-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[1898560.943004] usb 4-2: Product: Amazon Kindle
[1898560.943008] usb 4-2: Manufacturer: Amazon
[1898560.943012] usb 4-2: SerialNumber: B008D0A112830JDV
[1898560.944961] usb 4-2: configuration #1 chosen from 1 choice
[1898561.378518] Initializing USB Mass Storage driver...
[1898561.378723] scsi7 : SCSI emulation for USB Mass Storage devices
[1898561.378972] usbcore: registered new interface driver usb-storage
[1898561.378979] USB Mass Storage support registered.
[1898561.382766] usb-storage: device found at 2
[1898561.382772] usb-storage: waiting for device to settle before scanning
[1898566.382615] usb-storage: device scan complete
[1898566.389592] scsi 7:0:0:0: Direct-Access Kindle Internal Storage 0100
PQ: 0 ANSI: 2
[1898566.392415] sd 7:0:0:0: Attached scsi generic sg5 type 0
[1898566.416569] sd 7:0:0:0: [sdc] 6410688 512-byte logical blocks: (3.28
GB/3.05 GiB)
[1898566.534602] sd 7:0:0:0: [sdc] Write Protect is off
[1898566.534611] sd 7:0:0:0: [sdc] Mode Sense: 0f 00 00 00
[1898566.534616] sd 7:0:0:0: [sdc] Assuming drive cache: write through
Bug#663912: linux-image-3.3.0-rc6-amd64: please enable CONFIG_RTS5139 for SDcard support
Package: linux-2.6 Severity: wishlist Hi, Simply enabling CONFIG_RTS5139 as a module would add support for SDcard in some laptop such as the Asus Zenbook (UX31E). So it would be nice to have it enabled by default instead of having to recompile the kernel myself every time. Thanks. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-rc6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20120313220330.gc24...@gnuage.org
Bug#663981: linux-image-3.2.0-2-amd64: mdadm complain during booting
Package: linux-2.6 Version: 3.2.9-1 Severity: normal Hello! Sorry my bad english. After switch to kernel 3.x.x in syslog these messages: [2.383412] mdadm: sending ioctl 800c0910 to a partition! [2.383483] mdadm: sending ioctl 1261 to a partition! -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.9-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Mar 5 02:56:07 UTC 2012 ** Command line: BOOT_IMAGE=Linux ro root=901 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [2.383261] mdadm: sending ioctl 800c0910 to a partition! [2.383345] mdadm: sending ioctl 800c0910 to a partition! [2.383412] mdadm: sending ioctl 800c0910 to a partition! [2.383483] mdadm: sending ioctl 1261 to a partition! [2.383548] mdadm: sending ioctl 1261 to a partition! [2.383790] mdadm: sending ioctl 1261 to a partition! [2.383857] mdadm: sending ioctl 1261 to a partition! [2.415406] mdadm: sending ioctl 1261 to a partition! [2.415475] mdadm: sending ioctl 1261 to a partition! [2.415686] mdadm: sending ioctl 1261 to a partition! [2.426348] md: md0 stopped. [2.427770] md: bindsda1 [2.427940] md: bindsdb1 [2.429822] bio: create slab bio-1 at 1 [2.429987] md/raid1:md0: active with 2 out of 2 mirrors [2.430091] md0: detected capacity change from 0 to 1085603840 [2.430894] md0: unknown partition table [2.482738] md: md1 stopped. [2.483935] md: bindsda2 [2.484105] md: bindsdb2 [2.485084] md/raid1:md1: active with 2 out of 2 mirrors [2.485169] md1: detected capacity change from 0 to 318984486912 [2.487146] md1: unknown partition table [2.608330] PM: Starting manual resume from disk [2.608413] PM: Hibernation image partition 9:0 present [2.608415] PM: Looking for hibernation image. [2.608584] PM: Image not found (code -22) [2.608587] PM: Hibernation image not present or could not be loaded. [2.617257] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [2.617638] SGI XFS Quota Management subsystem [2.618931] XFS (md1): Mounting Filesystem [2.747562] XFS (md1): Ending clean mount [5.108931] udevd[372]: starting version 175 [5.924878] wmi: Mapper loaded [6.047692] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 [6.047783] ACPI: Power Button [PWRB] [6.047899] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [6.047983] ACPI: Power Button [PWRF] [6.049529] ACPI: processor limited to max C-state 1 [6.433546] parport_serial :04:05.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [6.433659] parport0: PC-style at 0xe000, irq 20 [PCSPP,TRISTATE,EPP] [6.464738] ACPI: resource piix4_smbus [io 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f] [6.464830] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.548540] :04:05.0: ttyS0 at I/O 0xe800 (irq = 20) is a 16550A [6.580495] :04:05.0: ttyS1 at I/O 0xe400 (irq = 20) is a 16550A [6.580576] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01 [6.581175] SP5100 TCO timer: mmio address 0xfec000f0 already in use [6.684063] MCE: In-kernel MCE decoding enabled. [6.780998] input: PC Speaker as /devices/platform/pcspkr/input/input4 [6.837276] EDAC MC: Ver: 2.1.0 [6.884895] AMD64 EDAC driver v3.4.0 [6.885060] EDAC amd64: DRAM ECC disabled. [6.885135] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [6.885136] Either enable ECC checking or force module loading by setting 'ecc_enable_override'. [6.885137] (Note that use of the override may cause unknown side effects.) [7.015948] nvidia: module license 'NVIDIA' taints kernel. [7.016030] Disabling lock debugging due to kernel taint [7.105737] nvidia :02:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [7.105816] nvidia :02:00.0: setting latency timer to 64 [7.105821] vgaarb: device changed decodes: PCI::02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [7.106062] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 295.20 Mon Feb 6 21:07:30 PST 2012 [7.127031] snd_au8830 :04:08.0: PCI INT A - GSI 23 (level, low) - IRQ 23 [7.127172] Vortex: init [7.384040] scsi_verify_blk_ioctl: 126 callbacks suppressed [7.384183] mdadm: sending ioctl 1261 to a partition! [7.384249] mdadm: sending ioctl 1261 to a partition! [7.384436] mdadm: sending ioctl 1261 to a partition! [7.384506] mdadm: sending ioctl 1261 to a partition! [7.384727] mdadm: sending ioctl 1261 to a partition! [7.384796] mdadm: sending ioctl 1261 to a partition! [7.388093] mdadm: sending ioctl 1261 to a partition! [7.388112] mdadm: sending ioctl 1261 to a partition! [
Bug#656899: mdadm: sending ioctl 1261 to a partition warnings,
same here. Fresh Squeeze 6.0.4 install. LVM over Raid1. System stable. root@asd:~# uname -a Linux asd 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux root@asd:~# Mar 13 10:47:07 asd kernel: [5.695630] mdadm: sending ioctl 1261 to a partition! Mar 13 10:47:07 asd kernel: [5.695636] mdadm: sending ioctl 1261 to a partition! Mar 13 10:47:07 asd kernel: [6.406926] mdadm: sending ioctl 1261 to a partition! Mar 13 10:47:07 asd kernel: [6.425660] mdadm: sending ioctl 1261 to a partition! Mar 13 10:47:07 asd kernel: [6.425666] mdadm: sending ioctl 1261 to a partition! Mar 13 22:07:15 asd kernel: [4.202070] mdadm: sending ioctl 1261 to a partition! Mar 13 22:07:15 asd kernel: [4.202075] mdadm: sending ioctl 1261 to a partition! additionaly update-grub borks about unknown LVM metadata headers, but this and ioctl 1261 seem somehow connected. root@asd:~# update-grub error: unknown LVM metadata header. error: unknown LVM metadata header. Generating grub.cfg ... error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. Found linux image: /boot/vmlinuz-2.6.32-5-686 Found initrd image: /boot/initrd.img-2.6.32-5-686 error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. error: unknown LVM metadata header. done root@asd:~# and corresponding dmesg: [89522.154518] grub-probe: sending ioctl 1261 to a partition! [89522.155065] grub-probe: sending ioctl 1261 to a partition! [89522.155069] grub-probe: sending ioctl 1261 to a partition! [89522.274417] grub-probe: sending ioctl 1261 to a partition! [89522.274422] grub-probe: sending ioctl 1261 to a partition! [89522.274945] grub-probe: sending ioctl 1261 to a partition! [89522.274949] grub-probe: sending ioctl 1261 to a partition! [89522.277214] grub-probe: sending ioctl 1261 to a partition! [89522.277219] grub-probe: sending ioctl 1261 to a partition! [89522.277931] grub-probe: sending ioctl 1261 to a partition! [89522.277935] grub-probe: sending ioctl 1261 to a partition! Best regards, -- Patryk Dawidziuk | pat...@dawidziuk.eu | 0xB54ADC05A in decimal -- 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/f5382352-4570-4f07-959b-bb6bb4a29...@dawidziuk.eu
Bug#663912: please enable CONFIG_RTS5139 for SDcard support
found 663912 linux-2.6/3.3~rc6-1~experimental.1 found 663912 linux-2.6/3.2.10-1 tags 663912 + patch quit Hi, Aurelien Jacobs wrote: Simply enabling CONFIG_RTS5139 as a module would add support for SDcard in some laptop such as the Asus Zenbook (UX31E). Sounds reasonable. The driver seems to have been merged in the 3.2 merge window, which is barely in time for us not to have to backport it for support in wheezy. Am I correct in assuming these card readers are only available as a built-in chip on x86 laptops, and not as a USB gadget that could be plugged in on machines with other processor architectures? Index: debian/changelog === --- debian/changelog(revision 18844) +++ debian/changelog(working copy) @@ -7,6 +7,9 @@ * aufs: Update to aufs3.x-rcN-20120312 * IB: Enable INFINIBAND_SRPT as module (Closes: #663041) + [ Jonathan Nieder ] + * [x86] Enable RTS5139 as module (Closes: #663912) + -- Ben Hutchings b...@decadent.org.uk Fri, 09 Mar 2012 05:27:29 + linux-2.6 (3.3~rc6-1~experimental.1) experimental; urgency=low Index: debian/config/kernelarch-x86/config === --- debian/config/kernelarch-x86/config (revision 18844) +++ debian/config/kernelarch-x86/config (working copy) @@ -1333,6 +1333,11 @@ CONFIG_R8712U=m +## +## file: drivers/staging/rts5139/Kconfig +## +CONFIG_RTS5139=m + ## ## file: drivers/staging/rts_pstor/Kconfig ## CONFIG_RTS_PSTOR=m -- 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/20120314221716.GE31686@burratino
Processed: Re: please enable CONFIG_RTS5139 for SDcard support
Processing commands for cont...@bugs.debian.org: found 663912 linux-2.6/3.3~rc6-1~experimental.1 Bug #663912 [linux-2.6] linux-image-3.3.0-rc6-amd64: please enable CONFIG_RTS5139 for SDcard support Marked as found in versions linux-2.6/3.3~rc6-1~experimental.1. found 663912 linux-2.6/3.2.10-1 Bug #663912 [linux-2.6] linux-image-3.3.0-rc6-amd64: please enable CONFIG_RTS5139 for SDcard support Marked as found in versions linux-2.6/3.2.10-1. tags 663912 + patch Bug #663912 [linux-2.6] linux-image-3.3.0-rc6-amd64: please enable CONFIG_RTS5139 for SDcard support Added tag(s) patch. quit Stopping processing here. Please contact me if you need assistance. -- 663912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133176344631840.transcr...@bugs.debian.org
Bug#622971: Fixed!
Linux-Image-3.2.9-1 does not freeze AND the atheros card works!! I noticed that it sometimes (very rarely) goes off line but recovers itself in a couple seconds unlike before that it needed modprobe -r ath9k, modprobe ath9k to come up again. I have been testing for about 3 days with no issues, THANKS! Marcos -- 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/201203150658.01387.marcos.ca...@gmail.com
Bug#663912: please enable CONFIG_RTS5139 for SDcard support
On Wed, Mar 14, 2012 at 05:17:16PM -0500, Jonathan Nieder wrote: Hi, Aurelien Jacobs wrote: Simply enabling CONFIG_RTS5139 as a module would add support for SDcard in some laptop such as the Asus Zenbook (UX31E). Sounds reasonable. The driver seems to have been merged in the 3.2 merge window, which is barely in time for us not to have to backport it for support in wheezy. Am I correct in assuming these card readers are only available as a built-in chip on x86 laptops, and not as a USB gadget that could be plugged in on machines with other processor architectures? It seems mostly used in recent laptops, but some desktops also features this chip. I don't know of any USB gadget with this chip, but as the chip is connected on the USB bus, it would be quite easy to conceive a USB gadget with it. Anyway, I guess it is better to enable it only on i386/amd64 until we discover some actual USB gadget using it. Thanks for the patch ! Aurel -- 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/20120314222703.gd24...@gnuage.org
Bug#658764: Radeon HD 6310: corrupt output unless firmware-linux-nonfree installed
On 12-Mar-2012, Jonathan Nieder wrote: Summary of information gathered so far: […] Yes, that looks right, thanks. Changes near v2.6.38-rc1~419^2~40^2 (drm/radeon/kms: add Ontario APU ucode loading support, 2010-11-22) might be responsible. If that is the cause, then 2.6.37-2 should work --- could you try it? I'm having difficulty finding a snapshots.debian.org URL that gives me that package in Wheezy, what would you suggest I use for the URL? -- \ “I have had a perfectly wonderful evening, but this wasn't it.” | `\ —Groucho Marx | _o__) | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Bug#622971: marked as done (ath9k: Ath9K wireless quite unreliable since upgrade to 2.6.38)
Your message dated Wed, 14 Mar 2012 18:40:05 -0500 with message-id 20120314234005.GA2159@burratino and subject line Re: Ath9K wireless quite unreliable since upgrade to 2.6.38 has caused the Debian Bug report #622971, regarding ath9k: Ath9K wireless quite unreliable since upgrade to 2.6.38 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 622971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-3 Severity: important File: ath9k ath9k disconects quite often (around 10 times a day) since upgrading the kernel to 2.6.38-2. Workaround is to modprob -r ath9k and then modprob ath9k. I am happy to test and collect more info, just tell me what to do. Cheers, Marcos -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=/dev/md0 ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [128307.280528] ath: Unable to set channel [128307.403124] ath: Unable to reset channel (2427 MHz), reset status -5 [128307.972551] ath: Unable to reset channel (2427 MHz), reset status -5 [128308.100140] ath: Unable to set channel [128308.100183] ath: Unable to set channel [128308.100220] ath: Unable to set channel [128308.100256] ath: Unable to set channel [128308.100291] ath: Unable to set channel [128308.100327] ath: Unable to set channel [128308.100362] ath: Unable to set channel [128308.100397] ath: Unable to set channel [128308.100433] ath: Unable to set channel [128308.100468] ath: Unable to set channel [128308.100504] ath: Unable to set channel [128308.100550] ath: Unable to set channel [128308.223125] ath: Unable to reset channel (2427 MHz), reset status -5 [128308.845761] ath: Unable to reset channel (2427 MHz), reset status -5 [128308.972129] ath: Unable to set channel [128308.972172] ath: Unable to set channel [128308.972208] ath: Unable to set channel [128308.972244] ath: Unable to set channel [128308.972279] ath: Unable to set channel [128308.972315] ath: Unable to set channel [128308.972350] ath: Unable to set channel [128308.972386] ath: Unable to set channel [128308.972421] ath: Unable to set channel [128308.972456] ath: Unable to set channel [128308.972492] ath: Unable to set channel [128308.972538] ath: Unable to set channel [128309.095171] ath: Unable to reset channel (2427 MHz), reset status -5 [128315.158076] ath: Unable to reset channel (2427 MHz), reset status -5 [128315.284105] ath: Unable to set channel [128315.284182] ath: Unable to set channel [128315.284251] ath: Unable to set channel [128315.284319] ath: Unable to set channel [128315.284387] ath: Unable to set channel [128315.284455] ath: Unable to set channel [128315.284523] ath: Unable to set channel [128315.284591] ath: Unable to set channel [128315.284659] ath: Unable to set channel [128315.284726] ath: Unable to set channel [128315.284794] ath: Unable to set channel [128315.284873] ath: Unable to set channel [128315.407475] ath: Unable to reset channel (2427 MHz), reset status -5 [128320.532887] ath9k :05:06.0: PCI INT A disabled [128320.532936] ath9k: Driver unloaded [128325.380139] cfg80211: Calling CRDA to update world regulatory domain [128325.825609] ath9k :05:06.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [128326.257128] ath: EEPROM regdomain: 0x809c [128326.257130] ath: EEPROM indicates we should expect a country code [128326.257131] ath: doing EEPROM country-regdmn map search [128326.257132] ath: country maps to regdmn code: 0x52 [128326.257133] ath: Country alpha2 being used: CN [128326.257134] ath: Regpair used: 0x52 [128326.260718] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [128326.261221] Registered led device: ath9k-phy0::radio [128326.261234] Registered led device: ath9k-phy0::assoc [128326.261248] Registered led device: ath9k-phy0::tx [128326.261260] Registered led device: ath9k-phy0::rx [128326.261263] ieee80211 phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81 mem=0xc900117a, irq=20 [128330.909935] ADDRCONF(NETDEV_UP): wlan0: link is not ready [128335.849109] ADDRCONF(NETDEV_UP): wlan0: link is not ready [128336.106890] ADDRCONF(NETDEV_UP): wlan0: link is not ready [128339.564767] wlan0: authenticate with 94:0c:6d:fe:2d:84 (try 1) [128339.567338] wlan0: authenticated [128339.567385] wlan0: associate with 94:0c:6d:fe:2d:84 (try
Bug#663981: linux-image-3.2.0-2-amd64: mdadm complain during booting
On Wed, Mar 14, 2012 at 09:33:53PM +0700, Yoric Kotchukov wrote: Package: linux-2.6 Version: 3.2.9-1 Severity: normal Hello! Sorry my bad english. After switch to kernel 3.x.x in syslog these messages: [2.383412] mdadm: sending ioctl 800c0910 to a partition! [2.383483] mdadm: sending ioctl 1261 to a partition! [...] Many ioctl operations have been disabled on disk partitions and logical volumes because they can affect the whole disk. (This problem is designated CVE-2011-4127.) It is supposed to be possible to assign a partition or LV to some user without letting them access any other part of the disk. Operations that fail due to this new restriction are logged so that if this breaks some program it is easy to see which operation it was attempting. But if mdadm continues to work properly, don't worry about it. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20120314234352.gc12...@decadent.org.uk
Bug#656899: mdadm: sending ioctl 1261 to a partition warnings,
On Wed, Mar 14, 2012 at 11:02:04PM +0100, Patryk Dawidziuk wrote: same here. Fresh Squeeze 6.0.4 install. LVM over Raid1. System stable. [...] additionaly update-grub borks about unknown LVM metadata headers, but this and ioctl 1261 seem somehow connected. root@asd:~# update-grub error: unknown LVM metadata header. [...] That doesn't look good, but it may be unrelated. Can you explain how the RAID and LVM are configured? Is /boot within an LV? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20120314234801.gd12...@decadent.org.uk
Bug#656899: mdadm: sending ioctl 1261 to a partition warnings,
Wiadomość napisana przez Ben Hutchings w dniu 15 mar 2012, o godz. 00:48: That doesn't look good, but it may be unrelated. Can you explain how the RAID and LVM are configured? Is /boot within an LV? Ben. Here it is: root@asd:~# cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[0] sdb1[1] 488383352 blocks super 1.2 [2/2] [UU] unused devices: none root@asd:~# pvdisplay --- Physical volume --- PV Name /dev/md0 VG Name wolumen PV Size 465,76 GiB / not usable 888,00 KiB Allocatable yes (but full) PE Size 4,00 MiB Total PE 119234 Free PE 0 Allocated PE 119234 PV UUID 8qDqeM-ItfB-hJZ0-8hsj-bHBx-F3Gk-J2QDzb It's just as you say - /boot within LV. LMV is on top of md0 device. Best regards -- Patryk Dawidziuk | pat...@dawidziuk.eu | +48 665313370 -- 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/10676ebe-0c61-44ee-a8b8-dc6ff67b3...@dawidziuk.eu
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Like others, the problems seemed to start around 2.6.39. Thought I should note here, my system showed this problem with 2.6.36 through 2.6.39. It seems to have stopped showing the problem (possibly due to a memory upgrade many months ago), but it still has chronic instability of the connection (drops out for varying intervals), and often, network-manager doesn't seem aware of the failure - reloading the driver isn't a reliable solution (sometimes appears to work, often does not) FWIW. Shannon C. Dealy | DeaTech Research Inc. de...@deatech.com | - Custom Software Development - Phone: (800) 467-5820 | - Natural Building Instruction - or: (541) 929-4089 | www.deatech.com -- 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/alpine.deb.2.00.1203142027440.28...@nashapur.deatech.com
