Bug#601110: linux-image-2.6.32-5-openvz-amd64: iwlagn hangs with 802.11n network on WiFi Link 5300
Package: linux-2.6 Version: 2.6.32-25 Severity: normal Trying to associate WiFi Link 5300 card with 802.11bgn network results in intermittent connection and packets stopping to come through after several minutes. ping starts spewing out 'No space in buffer' errors and driver sends the following errors to dmesg: [90821.446469] iwlagn :03:00.0: iwl_tx_agg_start on ra = 30:46:9a:17:bf:cd tid = 0 Reloading iwlagn module alleviates the problem for a few minutes. The following workaround fixes the problem by disabling 802.11n (not sure whether swcrypto options are really necessary): $ cat /etc/modprobe.d/iwlagn.conf options iwlagn swcrypto=1 swcrypto50=1 11n_disable=1 11n_disable50=1 -- Package-specific info: ** Version: Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-25) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Oct 15 01:38:41 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-openvz-amd64 root=/dev/mapper/leibnitz-root ro quiet reboot=pci ** Not tainted ** Kernel log: [91330.942482] wlan0: deauthenticated from 30:46:9a:17:bf:cd (Reason: 7) [91331.053698] wlan0: direct probe to AP 30:46:9a:17:bf:cd (try 1) [91331.057313] wlan0: direct probe responded [91331.057317] wlan0: authenticate with AP 30:46:9a:17:bf:cd (try 1) [91331.059491] wlan0: authenticated [91331.059509] wlan0: associate with AP 30:46:9a:17:bf:cd (try 1) [91331.106235] wlan0: RX AssocResp from 30:46:9a:17:bf:cd (capab=0x411 status=0 aid=1) [91331.106239] wlan0: associated [91334.628952] wlan0: deauthenticated from 30:46:9a:17:bf:cd (Reason: 7) [91334.745641] wlan0: direct probe to AP 30:46:9a:17:bf:cd (try 1) [91334.749282] wlan0: direct probe responded [91334.749285] wlan0: authenticate with AP 30:46:9a:17:bf:cd (try 1) [91334.751472] wlan0: authenticated [91334.751484] wlan0: associate with AP 30:46:9a:17:bf:cd (try 1) [91334.798483] wlan0: RX AssocResp from 30:46:9a:17:bf:cd (capab=0x411 status=0 aid=1) [91334.798487] wlan0: associated [91338.315373] wlan0: deauthenticated from 30:46:9a:17:bf:cd (Reason: 7) [91338.429222] wlan0: direct probe to AP 30:46:9a:17:bf:cd (try 1) [91338.432831] wlan0: direct probe responded [91338.432834] wlan0: authenticate with AP 30:46:9a:17:bf:cd (try 1) [91338.435040] wlan0: authenticated [91338.435051] wlan0: associate with AP 30:46:9a:17:bf:cd (try 1) [91338.482114] wlan0: RX AssocResp from 30:46:9a:17:bf:cd (capab=0x411 status=0 aid=1) [91338.482119] wlan0: associated [91341.591941] wlan0: deauthenticated from 30:46:9a:17:bf:cd (Reason: 2) [91341.709197] wlan0: direct probe to AP 30:46:9a:17:bf:cd (try 1) [91341.713003] wlan0: direct probe responded [91341.713007] wlan0: authenticate with AP 30:46:9a:17:bf:cd (try 1) [91341.715347] wlan0: authenticated [91341.715360] wlan0: associate with AP 30:46:9a:17:bf:cd (try 1) [91341.762608] wlan0: RX AssocResp from 30:46:9a:17:bf:cd (capab=0x411 status=0 aid=1) [91341.762612] wlan0: associated [91345.893043] wlan0: deauthenticated from 30:46:9a:17:bf:cd (Reason: 7) [91346.011655] wlan0: direct probe to AP 30:46:9a:17:bf:cd (try 1) [91346.015322] wlan0: direct probe responded [91346.015326] wlan0: authenticate with AP 30:46:9a:17:bf:cd (try 1) [91346.017508] wlan0: authenticated [91346.017523] wlan0: associate with AP 30:46:9a:17:bf:cd (try 1) [91346.065026] wlan0: RX AssocResp from 30:46:9a:17:bf:cd (capab=0x411 status=0 aid=1) [91346.065030] wlan0: associated [91350.193863] wlan0: deauthenticated from 30:46:9a:17:bf:cd (Reason: 7) [91350.316646] wlan0: direct probe to AP 30:46:9a:17:bf:cd (try 1) [91350.320326] wlan0: direct probe responded [91350.320330] wlan0: authenticate with AP 30:46:9a:17:bf:cd (try 1) [91350.322546] wlan0: authenticated [91350.322561] wlan0: associate with AP 30:46:9a:17:bf:cd (try 1) [91350.369911] wlan0: RX AssocResp from 30:46:9a:17:bf:cd (capab=0x411 status=0 aid=1) [91350.369916] wlan0: associated [91354.085093] wlan0: deauthenticated from 30:46:9a:17:bf:cd (Reason: 7) [91354.205217] wlan0: direct probe to AP 30:46:9a:17:bf:cd (try 1) [91354.208820] wlan0: direct probe responded [91354.208823] wlan0: authenticate with AP 30:46:9a:17:bf:cd (try 1) [91354.211078] wlan0: authenticated [91354.211089] wlan0: associate with AP 30:46:9a:17:bf:cd (try 1) [91354.258786] wlan0: RX AssocResp from 30:46:9a:17:bf:cd (capab=0x411 status=0 aid=1) [91354.258789] wlan0: associated [91356.164166] wlan0: deauthenticating from 30:46:9a:17:bf:cd by local choice (reason=3) [91356.288139] Registered led device: iwl-phy5::radio [91356.288400] Registered led device: iwl-phy5::assoc [91356.288594] Registered led device: iwl-phy5::RX [91356.288781] Registered led device: iwl-phy5::TX [91356.301287] ADDRCONF(NETDEV_UP): wlan0: link is not ready [91356.604220] e1000e :00:19.0: irq 28 for MSI/MSI-X [91356.660111] e1000e :00:19.0: irq 28 for MSI/MSI-X [91356.660628] ADDRCONF(NETDEV_UP): eth0: link is not ready [91359.457287] Registered led device: iwl-phy5::radio [91359.457509] Registered led device:
Bug#407217: Multicast broken in r8169 for one version of Thecus N2100
Twas brillig at 02:30:22 15.02.2010 UTC+01 when j...@inutil.org did gyre and gimble: Jon, Sjoerg, Mikhail, Wouter: can one of you please test this kernel to see if it works on the N2100: http://merkel.debian.org/~tbm/tmp/kernel/linux-image-2.6.32-trunk-iop32x_2.6.32-4_armel.deb MM Did anyone test the kernel build? Just tested it. Works fine here (mDNS resolves without promisc mode on interface), thanks. -- http://fossarchy.blogspot.com/ pgpjejAGDQvrM.pgp Description: PGP signature
Bug#407217: Multicast broken in r8169 for one version of Thecus N2100
Twas brillig at 14:41:10 07.03.2010 UTC+00 when t...@cyrius.com did gyre and gimble: Just tested it. Works fine here (mDNS resolves without promisc mode on interface), thanks. MM Good to hear! That patch also included some debugging output. Can MM you please send the output from dmesg? Attached. [looking at dmesg: wow, looks like I just found wireless card I lost some time ago - it's mini-PCI slot in NAS :] -- http://fossarchy.blogspot.com/ pgpVUt7LrooGF.pgp Description: PGP signature 15.01] pci :00:04.0: reg 20 io port: [0x9800-0x981f] [ 15.01] pci :00:04.0: supports D1 D2 [ 15.01] pci :00:04.0: PME# supported from D0 D1 D2 D3hot [ 15.01] pci :00:04.0: PME# disabled [ 15.01] pci :00:04.1: reg 20 io port: [0x9820-0x983f] [ 15.01] pci :00:04.1: supports D1 D2 [ 15.01] pci :00:04.1: PME# supported from D0 D1 D2 D3hot [ 15.01] pci :00:04.1: PME# disabled [ 15.01] pci :00:04.2: reg 10 32bit mmio: [0x800a1400-0x800a14ff] [ 15.01] pci :00:04.2: supports D1 D2 [ 15.01] pci :00:04.2: PME# supported from D0 D1 D2 D3hot [ 15.01] pci :00:04.2: PME# disabled [ 15.01] pci :00:05.0: reg 10 32bit mmio: [0x800a-0x800a0fff] [ 15.01] pci :00:05.0: PME# supported from D0 D3hot D3cold [ 15.01] pci :00:05.0: PME# disabled [ 15.01] PCI: bus0: Fast back to back transfers disabled [ 15.01] bio: create slab bio-0 at 0 [ 15.01] vgaarb: loaded [ 15.02] NET: Registered protocol family 2 [ 15.02] IP route cache hash table entries: 4096 (order: 2, 16384 bytes) [ 15.03] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [ 15.03] TCP bind hash table entries: 16384 (order: 4, 65536 bytes) [ 15.03] TCP: Hash tables configured (established 16384 bind 16384) [ 15.03] TCP reno registered [ 15.03] NET: Registered protocol family 1 [ 15.03] Unpacking initramfs... [ 17.13] Freeing initrd memory: 6612K [ 17.13] NetWinder Floating Point Emulator V0.97 (double precision) [ 17.13] audit: initializing netlink socket (disabled) [ 17.13] type=2000 audit(17.130:1): initialized [ 17.14] VFS: Disk quotas dquot_6.5.2 [ 17.14] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 17.14] msgmni has been set to 1007 [ 17.14] alg: No test for stdrng (krng) [ 17.15] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 17.15] io scheduler noop registered [ 17.15] io scheduler anticipatory registered [ 17.15] io scheduler deadline registered [ 17.15] io scheduler cfq registered (default) [ 17.16] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 17.16] serial8250.0: ttyS0 at MMIO 0xfe80 (irq = 0) is a 16550A [ 17.16] physmap platform flash device: 0100 at f000 [ 17.16] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank [ 17.16] Intel/Sharp Extended Query Table at 0x0031 [ 17.16] Intel/Sharp Extended Query Table at 0x0031 [ 17.16] Using buffer write method [ 17.16] cfi_cmdset_0001: Erase suspend on write enabled [ 17.16] erase region 0: offset=0x0,size=0x2,blocks=128 [ 17.16] Searching for RedBoot partition table in physmap-flash.0 at offset 0xfe [ 17.48] 6 RedBoot partitions found on MTD device physmap-flash.0 [ 17.48] Creating 6 MTD partitions on physmap-flash.0: [ 17.48] 0x-0x0004 : RedBoot [ 17.48] 0x0004-0x00d4 : ramdisk [ 17.48] 0x00d4-0x00ea : kernel [ 17.48] 0x00ea-0x00fc : user [ 17.48] 0x00fc-0x00fc1000 : RedBoot config [ 17.48] mtd: partition RedBoot config doesn't end on an erase block -- force read-only [ 17.48] 0x00fe-0x0100 : FIS directory [ 17.49] mice: PS/2 mouse device common for all mice [ 17.49] i2c /dev entries driver [ 17.49] rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.6 [ 17.49] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0 [ 17.50] pca9532 0-0060: setting platform data [ 17.50] Registered led device: n2100:red:satafail0 [ 17.50] Registered led device: n2100:red:satafail1 [ 17.50] Registered led device: n2100:blue:usb [ 17.50] Registered led device: n2100:red:usb [ 17.50] Registered led device: n2100:orange:system [ 17.50] Registered led device: n2100:red:system [ 17.50] input: N2100 beeper as /devices/virtual/input/input0 [ 17.52] iop-adma iop-adma.0: Intel(R) IOP: ( cpy intr ) [ 17.54] iop-adma iop-adma.1: Intel(R) IOP: ( cpy intr ) [ 17.54] TCP cubic registered [ 17.54] NET: Registered protocol family 17 [ 17.54] XScale DSP coprocessor detected. [ 17.54] registered taskstats version 1 [
Bug#407217: Multicast broken in r8169 for one version of Thecus N2100
Twas brillig at 02:30:22 15.02.2010 UTC+01 when j...@inutil.org did gyre and gimble: Jon, Sjoerg, Mikhail, Wouter: can one of you please test this kernel to see if it works on the N2100: http://merkel.debian.org/~tbm/tmp/kernel/linux-image-2.6.32-trunk-iop32x_2.6.32-4_armel.deb MM Did anyone test the kernel build? Sorry, don't have serial attached to recover in case of problems. Is it enough to unpack the kernel and modules and load it using kexec? -- http://fossarchy.blogspot.com/ pgpTDAd8m2dyG.pgp Description: PGP signature
Bug#492268: linux-image-2.6.25-2-iop32x: Please enable kexec
Twas brillig at 19:23:30 09.08.2008 UTC+03 when [EMAIL PROTECTED] did gyre and gimble: kexec works fine in armel architecture (tested in OpenEmbedded and Slind) - please enable it. Corresponding bugreport for kexec-tools is filed as #489175 MM Maybe you can check if it works with 2.6.26 in unstable. It works. Thanks. -- pgpLu3NRMjo7A.pgp Description: PGP signature
Bug#492268: linux-image-2.6.25-2-iop32x: Please enable kexec
Package: linux-image-2.6.25-2-iop32x Version: 2.6.25-6 Severity: wishlist kexec works fine in armel architecture (tested in OpenEmbedded and Slind) - please enable it. Corresponding bugreport for kexec-tools is filed as #489175 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 2.6.25-2-iop32x Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.25-2-iop32x depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.25-2-iop32x recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-iop32x/postinst/depmod-error-initrd-2.6.25-2-iop32x: false linux-image-2.6.25-2-iop32x/preinst/overwriting-modules-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/prerm/removing-running-kernel-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/preinst/elilo-initrd-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/postinst/bootloader-test-error-2.6.25-2-iop32x: linux-image-2.6.25-2-iop32x/postinst/create-kimage-link-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-iop32x/prerm/would-invalidate-boot-loader-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/preinst/abort-install-2.6.25-2-iop32x: linux-image-2.6.25-2-iop32x/postinst/old-system-map-link-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/postinst/old-dir-initrd-link-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/postinst/kimage-is-a-directory: linux-image-2.6.25-2-iop32x/preinst/lilo-initrd-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/preinst/already-running-this-2.6.25-2-iop32x: linux-image-2.6.25-2-iop32x/preinst/failed-to-move-modules-2.6.25-2-iop32x: linux-image-2.6.25-2-iop32x/preinst/abort-overwrite-2.6.25-2-iop32x: linux-image-2.6.25-2-iop32x/postinst/depmod-error-2.6.25-2-iop32x: false linux-image-2.6.25-2-iop32x/postinst/old-initrd-link-2.6.25-2-iop32x: true linux-image-2.6.25-2-iop32x/postinst/bootloader-error-2.6.25-2-iop32x: linux-image-2.6.25-2-iop32x/preinst/initrd-2.6.25-2-iop32x: linux-image-2.6.25-2-iop32x/preinst/bootloader-initrd-2.6.25-2-iop32x: true -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486442: Test package for multi/broadcast packet problem on n2100
Twas brillig at 10:37:11 24.07.2008 UTC-07 when [EMAIL PROTECTED] did gyre and gimble: MM Francois Romieu sent me a patch to test for the multi/broadcast MM packet problem on n2100. MM Can you please test the package from MM http://merkel.debian.org/~tbm/tmp/n2100/r8169/ to see if it makes MM any difference. Tested it - behavior is exactly the same as it was before. -- pgphulIL6JUhU.pgp Description: PGP signature
Bug#407217: r8169: Thecus N2100, multicast packets problem
Hello, I'm experiencing a problem with RTL-8169 network card on Thecus N2100 NAS device on 2.6.24 and 2.6.25 kernels (did not try other versions). System seems to be unable either to receive or to transmit multicast packets until promiscous mode is set on interface: mDNS does not work on this device, both for resolving other .local names or answering mDNS requests. Running tcpdump corrects the situation. Unicast packets work fine. I'm not on the list, so please keep me in CC. Additional info: [EMAIL PROTECTED]:~]1% cat /proc/cpuinfo Processor : XScale-80219 rev 0 (v5l) BogoMIPS: 593.10 Features: swp half fastmult edsp CPU implementer : 0x69 CPU architecture: 5TE CPU variant : 0x0 CPU part: 0x2e3 CPU revision: 0 Cache type : undefined 5 Cache clean : undefined 5 Cache lockdown : undefined 5 Cache format: Harvard I size : 32768 I assoc : 32 I line length : 32 I sets : 32 D size : 32768 D assoc : 32 D line length : 32 D sets : 32 Hardware: Thecus N2100 Revision: Serial : [EMAIL PROTECTED]:~]% lspci 00:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) 00:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) 00:03.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01) 00:04.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 62) 00:04.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 62) 00:04.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) [EMAIL PROTECTED]:~]% lspci -n 00:01.0 0200: 10ec:8169 (rev 10) 00:02.0 0200: 10ec:8169 (rev 10) 00:03.0 0180: 1095:3512 (rev 01) 00:04.0 0c03: 1106:3038 (rev 62) 00:04.1 0c03: 1106:3038 (rev 62) 00:04.2 0c03: 1106:3104 (rev 65) [EMAIL PROTECTED]:~]% uname -a Linux homenas 2.6.25-2-iop32x #2 Sat Jun 28 16:10:57 UTC 2008 armv5tel GNU/Linux -- pgpcoIKogwUiW.pgp Description: PGP signature
Bug#407217: RTL-8169 multicast bug
BTW, there are two more similara bugreports: #486442 and #488495 -- pgpD8mUDzphL2.pgp Description: PGP signature
Bug#407217: RTL-8169 multicast bug
Twas brillig at 23:55:16 05.07.2008 UTC+07 when [EMAIL PROTECTED] did gyre and gimble: MG This behavior is repeatable even with BROADCAST flag on the MG interface (actually running tcpdump is critical due to some MG reason). Oops, please ignore this :) Why did I think about BROADCAST? -- pgpHlQVEyjQEI.pgp Description: PGP signature
Bug#407217: RTL-8169 multicast bug
Twas brillig at 16:14:58 05.07.2008 UTC+01 when [EMAIL PROTECTED] did gyre and gimble: JD Sure -- I'm CCing debian-arm incase someone there has a n2100 JD running one of those kernels already -- it will take me days to JD build it :) JD Can someone verify that the rtl 8169 multicast bug is present on JD modern kernels: best way is to ensure your iface is not promisc, JD and run something like mt-daapd and see if after 30 minutes or so JD your share disappears from the network, and whether setting the JD iface to promisc fixes it. I confirm this bug. I run the avahi-daemon on the device and it does not respond on multicast queries until tcpdump is started and then it works fine. This behavior is repeatable even with BROADCAST flag on the interface (actually running tcpdump is critical due to some reason). [EMAIL PROTECTED]:~]% uname -a Linux homenas 2.6.25-2-iop32x #2 Sat Jun 28 16:10:57 UTC 2008 armv5tel GNU/Linux [EMAIL PROTECTED]:~]1% cat /proc/cpuinfo Processor : XScale-80219 rev 0 (v5l) BogoMIPS: 593.10 Features: swp half fastmult edsp CPU implementer : 0x69 CPU architecture: 5TE CPU variant : 0x0 CPU part: 0x2e3 CPU revision: 0 Cache type : undefined 5 Cache clean : undefined 5 Cache lockdown : undefined 5 Cache format: Harvard I size : 32768 I assoc : 32 I line length : 32 I sets : 32 D size : 32768 D assoc : 32 D line length : 32 D sets : 32 Hardware: Thecus N2100 Revision: [EMAIL PROTECTED]:~]% apt-cache policy linux-image-2.6.25-2-iop32x linux-image-2.6.25-2-iop32x: Installed: 2.6.25-6 Candidate: 2.6.25-6 Version table: *** 2.6.25-6 0 100 /var/lib/dpkg/status -- pgpypRDRO7kwX.pgp Description: PGP signature
Bug#486442: linux-image-2.6.25-1-iop32x: Thecus n2100: RTL-8169 network card receives multi/broadcast packets only in promiscous mode
Twas brillig at 09:34:05 16.06.2008 UTC+02 when [EMAIL PROTECTED] did gyre and gimble: I suppose that network dump is useless in this case, as merely running tcpdump makes cards work fine, so I'm pretty out of ideas what should I add to the bug report :) MM Do you know if the same happened with older versions of the kernel? Yes, that's why I tried to install 2.6.25 (oops, it's not in archive, taken from link in [EMAIL PROTECTED] I believe). The same problem was with the 2.6.24-1-iop32x. -- pgp9TLq3TML0V.pgp Description: PGP signature
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
You ([EMAIL PROTECTED]) wrote: H If you know more, please add your knowledge below. [skip] 2.6.14-2 still enables the outdated ieee80211 :( Fixing this is simply a matter of disabling CONFIG_IEEE80211. This will allow to use ipw2200 (ipw2100 also) drivers built using module-assistant as before. -- Mikhail Gusarov ICQ UIN: 111575219 JID: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
Hello, I've encountered the problem with 2.6.14 kernels: they are shipped with ancient version of ipw2200 drivers (1.0.0 while current version is 1.0.7) and ancient version of ieee80211 subsystem (copyrighted as 2004, so also outdated). This breaks compilation of module from ipw2200-source package (because it links against in-kernel ieee80211). Is there way to modularize builds to exclude ieee80211 or just disable it (along with ipw2200) because it is outdated and current vesion is shipped in ieee80211-source package? -- Mikhail Gusarov ICQ UIN: 111575219 JID: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New config options for 2.6.13 on i386/amd64
You ([EMAIL PROTECTED]) wrote: This change between configurations of 2.6.12-1-686 and 2.6.13-1-686 breaks compilation of realtime-lsm module. 3019c3108 CONFIG_SECURITY_CAPABILITIES=m --- CONFIG_SECURITY_CAPABILITIES=y H Has anyone been able to confirm this? What is the mode of breakage? Compilation fails with message -- Failed: Security Capabilities not configured as module Realtime LSM will not work with /usr/src/linux-headers-2.6.13-1-686 -- I think it can be easily confirmed with just module-assistant -l 2.6.13-1-686 auto-install realtime-lsm And yes, I think requiring security capabilities to be compiled as a module is a serious brain-damage of realtime-lsm authors. -- Mikhail Gusarov ICQ UIN: 111575219 JID: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New config options for 2.6.13 on i386/amd64
You ([EMAIL PROTECTED]) wrote: JS Apparently I was the first person to run split-config on the JS 2.6.13 kernel configs, so it also set a bunch of unrelated JS options (I have used the defaults). I am including the log of the JS changes for documentation purposes, please make sure that it is JS sane and in sync with other arches. This change between configurations of 2.6.12-1-686 and 2.6.13-1-686 breaks compilation of realtime-lsm module. 3019c3108 CONFIG_SECURITY_CAPABILITIES=m --- CONFIG_SECURITY_CAPABILITIES=y -- Mikhail Gusarov ICQ UIN: 111575219 JID: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
