Bug#724560: marked as done (Suggesting 'linux-image' prevents auto-removal of any linux-image package)
Your message dated Mon, 24 Feb 2014 10:00:11 + with message-id e1whskz-0004tb...@franck.debian.org and subject line Bug#724560: fixed in firmware-nonfree 0.41 has caused the Debian Bug report #724560, regarding Suggesting 'linux-image' prevents auto-removal of any linux-image package 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.) -- 724560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:firmware-nonfree Version: 0.40 Severity: important Control: affects -1 src:linux Currently APT's auto-removal criteria are very conservative; it will not remove any package where another package has any level of dependency on it (Depends, Recommends or Suggests). This includes cases where the dependency is on a virtual package that is also provided by multiple packages - none of them can be removed. To allow auto-removal of linux-image-* packages, nothing should depend on/recommend/suggest the virtual package 'linux-image'. Ben. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: firmware-nonfree Source-Version: 0.41 We believe that the bug you reported is fixed in the latest version of firmware-nonfree, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated firmware-nonfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Feb 2014 21:45:10 + Source: firmware-nonfree Binary: firmware-linux firmware-adi firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux-nonfree firmware-myricom firmware-netxen firmware-qlogic firmware-ralink firmware-realtek firmware-ti-connectivity Architecture: source all Version: 0.41 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Description: firmware-adi - Binary firmware for Analog Devices Inc. DSL modem chips firmware-atheros - Binary firmware for Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell Libertas 8xxx wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qlogic - Binary firmware for QLogic IBA7220, QLA1xxx, ISP2xxx and SP2x2 firmware-ralink - Binary firmware for Ralink wireless cards firmware-realtek - Binary firmware for Realtek wired and wireless network adapters firmware-ti-connectivity - Binary firmware for TI Connectivity wireless network adapters Closes: 628676 724560 738615 739798 Changes: firmware-nonfree (0.41) unstable; urgency=medium . * To allow auto-removal of linux-image-* packages, do not suggest virtual package linux-image (Closes: #724560) * Update to linux-support-3.13-1 * Fix wrapping of file lists in package description (Closes: #739798) * qlogic: Update QLogic ISP2422, ISP2432[M], SP222, SP232 and ISP2532 firmware to
Bug#738615: marked as done (wrong firmware for intel iwlwifi 7260)
Your message dated Mon, 24 Feb 2014 10:00:11 + with message-id e1whskz-0004tg...@franck.debian.org and subject line Bug#738615: fixed in firmware-nonfree 0.41 has caused the Debian Bug report #738615, regarding wrong firmware for intel iwlwifi 7260 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.) -- 738615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-iwlwifi Version: 0.40 Hi I downloaded the unstable firmware as I saw it had the firmware I needed for my new laptop and copied the file into the right place. Not a normal install... I'm running testing. The firmware is too old even for testing. Sadly the firmware doesn't work well at all, regular disconnects and lots of errors in the kernel log. Others have seen exactly this problem: http://ubuntuforums.org/showthread.php?t=2189035page=3 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221202 I grabbed the new images from: http://wireless.kernel.org/en/users/Drivers/iwlwifi And they work perfectly so far, no errors, no disconnects, much better throughput. Thanks, M ---End Message--- ---BeginMessage--- Source: firmware-nonfree Source-Version: 0.41 We believe that the bug you reported is fixed in the latest version of firmware-nonfree, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 738...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated firmware-nonfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Feb 2014 21:45:10 + Source: firmware-nonfree Binary: firmware-linux firmware-adi firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux-nonfree firmware-myricom firmware-netxen firmware-qlogic firmware-ralink firmware-realtek firmware-ti-connectivity Architecture: source all Version: 0.41 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Description: firmware-adi - Binary firmware for Analog Devices Inc. DSL modem chips firmware-atheros - Binary firmware for Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell Libertas 8xxx wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qlogic - Binary firmware for QLogic IBA7220, QLA1xxx, ISP2xxx and SP2x2 firmware-ralink - Binary firmware for Ralink wireless cards firmware-realtek - Binary firmware for Realtek wired and wireless network adapters firmware-ti-connectivity - Binary firmware for TI Connectivity wireless network adapters Closes: 628676 724560 738615 739798 Changes: firmware-nonfree (0.41) unstable; urgency=medium . * To allow auto-removal of linux-image-* packages, do not suggest virtual package linux-image (Closes: #724560) * Update to linux-support-3.13-1 * Fix wrapping of file lists in package description (Closes: #739798) * qlogic: Update QLogic ISP2422, ISP2432[M], SP222, SP232 and ISP2532 firmware to version 7.01.00 * linux-nonfree: Update Chelsio T4 firmware to version 1.9.23.0; add Chelsio T5 firmware * libertas: Update PCIE8897 firmware to version 15.69.2.p11 (WLAN) / 15.28.2.p11 (BT); add SD8897
Bug#628676: marked as done (firmware-nonfree: add ti-connectivity firmware)
Your message dated Mon, 24 Feb 2014 10:00:11 + with message-id e1whskz-0004t0...@franck.debian.org and subject line Bug#628676: fixed in firmware-nonfree 0.41 has caused the Debian Bug report #628676, regarding firmware-nonfree: add ti-connectivity firmware 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.) -- 628676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-nonfree Version: 0.30 Severity: wishlist Hi, Please consider adding a package for ti-connectivity (which can be found in the linux-firmware.git). The firmware is needed for TI's WLAN module, which is mainly used on mobile platforms (e.g. pandaboard, nokia n900). -- Sebastian ---End Message--- ---BeginMessage--- Source: firmware-nonfree Source-Version: 0.41 We believe that the bug you reported is fixed in the latest version of firmware-nonfree, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 628...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated firmware-nonfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Feb 2014 21:45:10 + Source: firmware-nonfree Binary: firmware-linux firmware-adi firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux-nonfree firmware-myricom firmware-netxen firmware-qlogic firmware-ralink firmware-realtek firmware-ti-connectivity Architecture: source all Version: 0.41 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Description: firmware-adi - Binary firmware for Analog Devices Inc. DSL modem chips firmware-atheros - Binary firmware for Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell Libertas 8xxx wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qlogic - Binary firmware for QLogic IBA7220, QLA1xxx, ISP2xxx and SP2x2 firmware-ralink - Binary firmware for Ralink wireless cards firmware-realtek - Binary firmware for Realtek wired and wireless network adapters firmware-ti-connectivity - Binary firmware for TI Connectivity wireless network adapters Closes: 628676 724560 738615 739798 Changes: firmware-nonfree (0.41) unstable; urgency=medium . * To allow auto-removal of linux-image-* packages, do not suggest virtual package linux-image (Closes: #724560) * Update to linux-support-3.13-1 * Fix wrapping of file lists in package description (Closes: #739798) * qlogic: Update QLogic ISP2422, ISP2432[M], SP222, SP232 and ISP2532 firmware to version 7.01.00 * linux-nonfree: Update Chelsio T4 firmware to version 1.9.23.0; add Chelsio T5 firmware * libertas: Update PCIE8897 firmware to version 15.69.2.p11 (WLAN) / 15.28.2.p11 (BT); add SD8897 firmware * iwlwifi: Update Intel Wireless 3160 and 7260 firmware to version 22.1.7.0 (ABI 7) and version 22.15.8.0 (ABI 8) (Closes: #738615) * linux-nonfree: Add Radeon HD 7790/8770/8950 series SMC microcode, Radeon R9 290 series and Radeon R5/R7 IGP 200 series microcode * brcm80211: Add Broadcom BCM43241, BCM4329, BCM4330, BCM4334 and BCM4335 firmware for use with
firmware-nonfree_0.41_i386.changes ACCEPTED into unstable, unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 22 Feb 2014 21:45:10 +
Source: firmware-nonfree
Binary: firmware-linux firmware-adi firmware-atheros firmware-bnx2
firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00
firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux-nonfree
firmware-myricom firmware-netxen firmware-qlogic firmware-ralink
firmware-realtek firmware-ti-connectivity
Architecture: source all
Version: 0.41
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
Changed-By: Ben Hutchings b...@decadent.org.uk
Description:
firmware-adi - Binary firmware for Analog Devices Inc. DSL modem chips
firmware-atheros - Binary firmware for Atheros wireless cards
firmware-bnx2 - Binary firmware for Broadcom NetXtremeII
firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb
firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards
firmware-intelwimax - Binary firmware for Intel WiMAX Connection
firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and
pvrusb2 d
firmware-iwlwifi - Binary firmware for Intel Wireless cards
firmware-libertas - Binary firmware for Marvell Libertas 8xxx wireless cards
firmware-linux - Binary firmware for various drivers in the Linux kernel
(meta-pac
firmware-linux-nonfree - Binary firmware for various drivers in the Linux
kernel
firmware-myricom - Binary firmware for Myri-10G Ethernet adapters
firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and
3100 Se
firmware-qlogic - Binary firmware for QLogic IBA7220, QLA1xxx, ISP2xxx and
SP2x2
firmware-ralink - Binary firmware for Ralink wireless cards
firmware-realtek - Binary firmware for Realtek wired and wireless network
adapters
firmware-ti-connectivity - Binary firmware for TI Connectivity wireless
network adapters
Closes: 628676 724560 738615 739798
Changes:
firmware-nonfree (0.41) unstable; urgency=medium
.
* To allow auto-removal of linux-image-* packages, do not suggest
virtual package linux-image (Closes: #724560)
* Update to linux-support-3.13-1
* Fix wrapping of file lists in package description (Closes: #739798)
* qlogic: Update QLogic ISP2422, ISP2432[M], SP222, SP232 and ISP2532
firmware to version 7.01.00
* linux-nonfree: Update Chelsio T4 firmware to version 1.9.23.0;
add Chelsio T5 firmware
* libertas: Update PCIE8897 firmware to version 15.69.2.p11 (WLAN) /
15.28.2.p11 (BT); add SD8897 firmware
* iwlwifi: Update Intel Wireless 3160 and 7260 firmware to version
22.1.7.0 (ABI 7) and version 22.15.8.0 (ABI 8) (Closes: #738615)
* linux-nonfree: Add Radeon HD 7790/8770/8950 series SMC microcode,
Radeon R9 290 series and Radeon R5/R7 IGP 200 series microcode
* brcm80211: Add Broadcom BCM43241, BCM4329, BCM4330, BCM4334 and
BCM4335 firmware for use with brcmfmac driver
* realtek: Add RTL8188EU firmware for use with the rtl8188eu driver,
RTL8821AE firmware for use with the rtl8821ae driver and new
RTL8192CU firmware for use with the rtl8192cu driver
* iwlwifi: Update Intel Wireless 7260 Bluetooth firmware, fixing:
- sometimes device doesn't response to HCI_reset after multiple reboot
- issue with HCI stress testing
- issue with some multi profile cases
* iwlwifi: Add Intel Wireless 3160 Bluetooth firmware for use with
the btusb driver
* Add firmware-ti-connectivity package containing firmware for the
Texas Instruments WL1251, WL127x, WL128x and WL18xx wireless network
chips, for use with the wl1251, wl12xx and wl18xx drivers
(Closes: #628676)
* linux-nonfree: Update wildcards and date for files under the AMD
licences
* linux-nonfree: Update wildcard and date for files under the Chelsio
licence
* Suppress lintian warnings and errors due to our unusual mixture of
licences
* debian/control: Allow debhelper to add dependencies through
${misc:Depends}
* ivtv, ipw2x00: Add one-line copyright notices above licence text
* debian/control: Update Standards-Version to 3.9.5:
- linux: Move to the 'non-free/metapackages' section
- libertas, linux-nonfree: Use 'Breaks' relation rather than 'Conflicts'
where files have been moved from another package
Checksums-Sha1:
28d517a2f51fab086345e6c36de4d629378f2972 2927 firmware-nonfree_0.41.dsc
598892e4e3e01f622bb04f6cb3cd14d9915c4aba 24507839 firmware-nonfree_0.41.tar.gz
b5e499d0021da170da90e8df24c34925e0e16beb 9580 firmware-linux_0.41_all.deb
0cd83ff01dcb28540293295240f4ffcf98b63472 165494 firmware-adi_0.41_all.deb
3ed427d0685904c9891d6dd0ce43944543d5e67b 873026 firmware-atheros_0.41_all.deb
097f197e4e71a626007856430026961180cd2f61 126554 firmware-bnx2_0.41_all.deb
b41f886799f77495f81ad805728c5fe1c0fd35a7 1974478
Bug#739968: linux-libc-dev: binfmts.h defines MAX_ARG_STRLEN using PAGE_SIZE which is not defined in armhf's libc
Package: linux-libc-dev Version: 3.12.9-1 Severity: important Trying to build a software package that uses MAX_ARG_STRLEN on armhf I hit a build failure caused by PAGE_SIZE being undefined, we probably need to define MAX_ARG_STRLEN in a different fashion for armhf: #define MAX_ARG_STRLEN (PAGE_SIZE * 32) Thanks, Gustavo Noronha -- 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/20140224122409.6057.13777.reportbug@goiaba.horta
Bug#739978: kernel panic enabling wifi using rtl8187 on loongson-2f
Package: linux-image-3.12-1-loongson-2f
Version: 3.12.9-1
Tags: patch
Forwarded: https://bugzilla.kernel.org/show_bug.cgi?id=54391
Hi,
When I run ifup wlan0 to enable the wireless interface on my Lemote
Yeeloong, the kernel panics in the rtl8187 driver. I've verified that
the attached patch, extracted from upstream, fixes this problem.
This problem also occurs in the experimental kernel (i.e.,
3.13-1~exp1), but not in the stable kernel, 3.2.54-2.
--
Matt
commit b6213e413a4e0c66548153516b074df14f9d08e0
Author: Stanislaw Gruszka stf...@wp.pl
Date: Mon Feb 10 22:38:28 2014 +0100
rtl8187: fix regression on MIPS without coherent DMA
This patch fixes regression caused by commit a16dad77634 MIPS: Fix
potencial corruption. That commit fixes one corruption scenario in
cost of adding another one, which actually start to cause crashes
on Yeeloong laptop when rtl8187 driver is used.
For correct DMA read operation on machines without DMA coherence, kernel
have to invalidate cache, such it will refill later with new data that
device wrote to memory, when that data is needed to process. We can only
invalidate full cache line. Hence when cache line includes both dma
buffer and some other data (written in cache, but not yet in main
memory), the other data can not hit memory due to invalidation. That
happen on rtl8187 where struct rtl8187_priv fields are located just
before and after small buffers that are passed to USB layer and DMA
is performed on them.
To fix the problem we align buffers and reserve space after them to make
them match cache line.
This patch does not resolve all possible MIPS problems entirely, for
that we have to assure that we always map cache aligned buffers for DMA,
what can be complex or even not possible. But patch fixes visible and
reproducible regression and seems other possible corruptions do not
happen in practice, since Yeeloong laptop works stable without rtl8187
driver.
Bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=54391
Reported-by: Petr Pisar petr.pi...@atlas.cz
Bisected-by: Tom Li biergaizi2...@gmail.com
Reported-and-tested-by: Tom Li biergaizi2...@gmail.com
Cc: sta...@vger.kernel.org
Signed-off-by: Stanislaw Gruszka stf...@wp.pl
Acked-by: Larry Finger larry.fin...@lwfinger.next
Acked-by: Hin-Tak Leung ht...@users.sourceforge.net
Signed-off-by: John W. Linville linvi...@tuxdriver.com
diff --git a/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h
b/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h
index 56aee06..a6ad79f 100644
--- a/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h
+++ b/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h
@@ -15,6 +15,8 @@
#ifndef RTL8187_H
#define RTL8187_H
+#include linux/cache.h
+
#include rtl818x.h
#include leds.h
@@ -139,7 +141,10 @@ struct rtl8187_priv {
u8 aifsn[4];
u8 rfkill_mask;
struct {
- __le64 buf;
+ union {
+ __le64 buf;
+ u8 dummy1[L1_CACHE_BYTES];
+ } cacheline_aligned;
struct sk_buff_head queue;
} b_tx_status; /* This queue is used by both -b and non-b devices */
struct mutex io_mutex;
@@ -147,7 +152,8 @@ struct rtl8187_priv {
u8 bits8;
__le16 bits16;
__le32 bits32;
- } *io_dmabuf;
+ u8 dummy2[L1_CACHE_BYTES];
+ } *io_dmabuf cacheline_aligned;
bool rfkill_off;
u16 seqno;
};
--
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/20140224135459.ga2...@ftbfs.org
Processed: reassign 739978 src:linux
Processing commands for cont...@bugs.debian.org: reassign 739978 src:linux 3.12.9-1 Bug #739978 [linux-image-3.12-1-loongson-2f] kernel panic enabling wifi using rtl8187 on loongson-2f Bug reassigned from package 'linux-image-3.12-1-loongson-2f' to 'src:linux'. No longer marked as found in versions linux/3.12.9-1. Ignoring request to alter fixed versions of bug #739978 to the same values previously set Bug #739978 [src:linux] kernel panic enabling wifi using rtl8187 on loongson-2f Marked as found in versions linux/3.12.9-1. -- Stopping processing here. Please contact me if you need assistance. -- 739978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739978 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.139325225428254.transcr...@bugs.debian.org
[PATCH] Bug #709632 - Fix broken -R option for preferred_realm
Hi, I opened the above bug in May last year and didn't hear anything about it. The current version of the gssd daemon shipped with nfs-utils doesn't honor any parameter given for the -R option and therefore can't the used in our multi-realm Kerberos/NFS4 setup :-( The bug contains a patch which has already been approved and accepted by upstream and I would really love to see this fixed in Debian as we currently have to build own packages for this. I had hoped that we could drop this when migrating to Wheezy. If there's anything I can do to help, please let me know. Thanks for you effort! Kind regards Max -- Alles sollte so einfach wie möglich gemacht sein. Aber nicht einfacher. (Einstein) -- 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/20140224143344.gk28...@principal.rfc2324.org
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Sat, 2014-02-22 at 22:56 +, Ben Hutchings wrote: On Mon, 2013-09-30 at 20:25 +1000, Kris Shannon wrote: I was eagerly awating the release of linux-2.6_2.6.32-48squeeze4 because it would fix #701744 (fallout from XSA-39: Linux netback DoS via malicious guest ring) It turns out I should have read the bug report more closely. #701744 was only about the xen-netback side of things. I haven't been able to find a debian bug about the REAL bug - the xen-netfront gso overflow. Upstream have patched this: http://git.kernel.org/linus/9ecd1a75d977e2e8c48139c7d3efed183f898d94 netfront: reduce gso_max_size to account for max TCP header Is this likely to go into a squeeze kernel? Maybe. Ian, is this going to be possible to backport? It looks fairly small and self contained, so I suspect so. Wei -- does that sound right (the backport target is Debian Wheezy which is 2.6.32) The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? Ian. The xen environment I'm running these squeeze VM's in is running on CentOS dom0's and Redhat have closed the visible bugs I can find on this as Not a bug :( Right, the over-64K skbs are very definitely a netfront bug and it is correct for dom0 to reject them from an unpatched guest. As a temporary workaround I think that turning off TSO on netfront would avoid the problem, but it will reduce network TX performance. Ben. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1393256906.16570.89.ca...@kazak.uk.xensource.com
Re: [PATCH 21/21] ARM: Kirkwood: Remove DT support
On Thu, 2014-02-20 at 18:26 -0500, Jason Cooper wrote: On Thu, Feb 20, 2014 at 11:39:16AM +, Ian Campbell wrote: On Thu, 2014-02-20 at 11:19 +, Russell King - ARM Linux wrote: What's wrong with the soc subsystem (drivers/base/soc.c). This provides a way to export SoC through standardised interfaces. It looks like the thing to use to me. It seems to have been around only since v3.3 though, which makes it a bit tricky to use when upgrading from running board-file based v3.2 system (Debian Wheezy) to a newer DTB based kernel, we need to select the new DTB while running the old system. I'd prefer to use this thing as the primary mechanism but it seems like I'd have to implement some sort of fallback at least for one Debian release cycle. I'm sure it is doable... back in v3.2, lspci should still work. Would that given you the information you need? I expect it will, yes. Ian. -- 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/1393257630.16570.95.ca...@kazak.uk.xensource.com
Re: [PATCH 21/21] ARM: Kirkwood: Remove DT support
On Fri, 2014-02-21 at 02:00 +, Ben Hutchings wrote: On Thu, 2014-02-20 at 14:24 +, Ian Campbell wrote: On Thu, 2014-02-20 at 14:23 +0100, Andrew Lunn wrote: [...] What i suspect we will end up doing it dropping the last patch for the moment and ensuring ARCH_KIRKWOOD still supports all the DT machines. I think that just needs care with arch/arm/boot/dts/Makefile. Once we have the last four converted over to DT, you can then do a straight swap, mach-kirkwood for mach-mvebu. That sounds like a good plan, thanks! If we are going to do a straight swap I suppose it might as go for a v5 multiplatform flavour instead of a mvebu specific one. [...] I would love it if we could do that. By the way, we still have the problem that at least one supported orion5x machine (D-Link DNS-323) only has a ~1.5 MB kernel partition. So we would probably have to keep a reduced orion5x config for those machines, alongside the mvebu or multiplatform kernel. Sure. I think at worst we should aim to end up with as many flavour as we have today, in reality I expect we should be able to end up with fewer (even if only -= 1). BTW, someone (I forget who) at Debconf in Cambridge last year floated the idea of putting a stage 2 loader in flash to pull the real kernel from some larger storage. I don't know if that is realistic here, and in any case I don't intend to work on it myself. Ian. -- 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/1393257795.16570.98.ca...@kazak.uk.xensource.com
Re: [PATCH 21/21] ARM: Kirkwood: Remove DT support
On Mon, 2014-02-24 at 17:24 +0100, Andrew Lunn wrote: What's wrong with the soc subsystem (drivers/base/soc.c). This provides a way to export SoC through standardised interfaces. It looks like the thing to use to me. It seems to have been around only since v3.3 though, which makes it a bit tricky to use when upgrading from running board-file based v3.2 system (Debian Wheezy) to a newer DTB based kernel, we need to select the new DTB while running the old system. I'd prefer to use this thing as the primary mechanism but it seems like I'd have to implement some sort of fallback at least for one Debian release cycle. I'm sure it is doable... back in v3.2, lspci should still work. Would that given you the information you need? I expect it will, yes. 3.14 with the new PCIe driver will also work. The patch was accepted and considered a regression so made it into one of the -rc's. Great! Thanks. Ian. -- 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/1393259176.16570.102.ca...@kazak.uk.xensource.com
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Mon, Feb 24, 2014 at 03:48:26PM +, Ian Campbell wrote: On Sat, 2014-02-22 at 22:56 +, Ben Hutchings wrote: On Mon, 2013-09-30 at 20:25 +1000, Kris Shannon wrote: I was eagerly awating the release of linux-2.6_2.6.32-48squeeze4 because it would fix #701744 (fallout from XSA-39: Linux netback DoS via malicious guest ring) It turns out I should have read the bug report more closely. #701744 was only about the xen-netback side of things. I haven't been able to find a debian bug about the REAL bug - the xen-netfront gso overflow. Upstream have patched this: http://git.kernel.org/linus/9ecd1a75d977e2e8c48139c7d3efed183f898d94 netfront: reduce gso_max_size to account for max TCP header Is this likely to go into a squeeze kernel? Maybe. Ian, is this going to be possible to backport? It looks fairly small and self contained, so I suspect so. Wei -- does that sound right (the backport target is Debian Wheezy which is 2.6.32) Yes, you're right. It should be fairly easy to backport. Wei. The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? Ian. The xen environment I'm running these squeeze VM's in is running on CentOS dom0's and Redhat have closed the visible bugs I can find on this as Not a bug :( Right, the over-64K skbs are very definitely a netfront bug and it is correct for dom0 to reject them from an unpatched guest. As a temporary workaround I think that turning off TSO on netfront would avoid the problem, but it will reduce network TX performance. Ben. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140224160557.ga16...@zion.uk.xensource.com
Re: [PATCH 21/21] ARM: Kirkwood: Remove DT support
What's wrong with the soc subsystem (drivers/base/soc.c). This provides a way to export SoC through standardised interfaces. It looks like the thing to use to me. It seems to have been around only since v3.3 though, which makes it a bit tricky to use when upgrading from running board-file based v3.2 system (Debian Wheezy) to a newer DTB based kernel, we need to select the new DTB while running the old system. I'd prefer to use this thing as the primary mechanism but it seems like I'd have to implement some sort of fallback at least for one Debian release cycle. I'm sure it is doable... back in v3.2, lspci should still work. Would that given you the information you need? I expect it will, yes. 3.14 with the new PCIe driver will also work. The patch was accepted and considered a regression so made it into one of the -rc's. Andrew -- 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/20140224162413.ge18...@lunn.ch
Re: [PATCH 21/21] ARM: Kirkwood: Remove DT support
On Mon, Feb 24, 2014 at 04:26:16PM +, Ian Campbell wrote: On Mon, 2014-02-24 at 17:24 +0100, Andrew Lunn wrote: What's wrong with the soc subsystem (drivers/base/soc.c). This provides a way to export SoC through standardised interfaces. It looks like the thing to use to me. It seems to have been around only since v3.3 though, which makes it a bit tricky to use when upgrading from running board-file based v3.2 system (Debian Wheezy) to a newer DTB based kernel, we need to select the new DTB while running the old system. I'd prefer to use this thing as the primary mechanism but it seems like I'd have to implement some sort of fallback at least for one Debian release cycle. I'm sure it is doable... back in v3.2, lspci should still work. Would that given you the information you need? I expect it will, yes. 3.14 with the new PCIe driver will also work. The patch was accepted and considered a regression so made it into one of the -rc's. Great! Thanks. fyi: 322a8e91844f PCI: mvebu: Use Device ID and revision from underlying endpoint It's in -rc4 and it's flagged for stable from v3.11 on up. v3.11 is when the pcie driver was introduced (and thus, the regression). hth, Jason. -- 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/20140224163442.gf14...@titan.lakedaemon.net
Bug#739992: linux-image-3.13-1-amd64: discrete video card not available, sometimes hangs on boot
Package: src:linux Version: 3.13.4-1 Severity: critical Justification: breaks the whole system Dear Maintainer, after installing 3.13.4-1 linux kernel I found out that discrete video card is not available. During the boot process I experience a long delay at Waiting for /dev to be fully populated stage and can see something like pciehp :00:03.0:pcie04: Device :02:00.0 already exists at :02:00, cannot hot-add After succesful booting lspci doesn't show my discrete video card and xrandr --listproviders shows only integrated video card. Sometimes kernel hangs at boot during Waiting for /dev to be fully populated stage. With 3.12.9-1 linux kernel everything works OK. Cheers! Lev Lamberov -- Package-specific info: ** Version: Linux version 3.13-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-14) ) #1 SMP Debian 3.13.4-1 (2014-02-22) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.13-1-amd64 root=UUID=1257503e-04c4-40f9-b35e-bdc8ef96c279 ro quiet radeon.audio=1 radeon.dpm=1 nmi_watchdog=0 ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 20.920652] power level 1sclk: 4 mclk: 9 vddc: 1000 vddci: 0 [ 20.920653] power level 2sclk: 6 mclk: 9 vddc: 1000 vddci: 0 [ 20.920654] status: r [ 21.038536] [drm] radeon: finishing device. [ 21.038546] [drm] Disabling audio 0 support [ 21.047750] [ cut here ] [ 21.047785] WARNING: CPU: 0 PID: 162 at /build/linux-YhyeNj/linux-3.13.4/drivers/gpu/drm/drm_mm.c:578 ttm_bo_man_takedown+0x29/0x60 [ttm]() [ 21.047789] Memory manager not clean during takedown. [ 21.047793] Modules linked in: snd_hda_codec_hdmi joydev hp_wmi sparse_keymap evdev kvm_amd kvm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core arc4 rt2800pci rt2800mmio rt2800lib rt2x00pci rt2x00mmio rt2x00lib eeprom_93cx6 mac80211 psmouse serio_raw videodev media edac_mce_amd edac_core snd_hda_codec_idt k10temp cfg80211 rtsx_pci_ms snd_hda_intel snd_hda_codec snd_hwdep btusb bluetooth snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer snd sp5100_tco i2c_piix4 radeon ttm wmi drm_kms_helper drm hp_accel battery video lis3lv02d soundcore acpi_cpufreq input_polldev i2c_algo_bit processor button ac i2c_core memstick crc_ccitt rfkill shpchp ext4 crc16 mbcache jbd2 sd_mod crct10dif_generic sg sr_mod cdrom crc_t10dif crct10dif_common rtsx_pci_sdmmc mmc_core ehci_pci ahci libahci libata ohci_pci ohci_hcd ehci_hcd xhci_hcd scsi_mod usbcore usb_common thermal thermal_sys rtsx_pci mfd_core r8169 mii [ 21.047907] CPU: 0 PID: 162 Comm: kworker/0:2 Not tainted 3.13-1-amd64 #1 Debian 3.13.4-1 [ 21.047912] Hardware name: Hewlett-Packard HP Pavilion dv6 Notebook PC/164B, BIOS F.21 09/13/2011 [ 21.047923] Workqueue: pciehp-3 pciehp_power_thread [ 21.047927] 0009 814a08cd 880213c95c28 8105ba72 [ 21.047935] 88021685da40 880213c95c78 880214c4a848 8802141ab300 [ 21.047941] 8105bad7 a02afb80 0018 [ 21.047947] Call Trace: [ 21.047958] [814a08cd] ? dump_stack+0x41/0x51 [ 21.047966] [8105ba72] ? warn_slowpath_common+0x72/0x90 [ 21.047972] [8105bad7] ? warn_slowpath_fmt+0x47/0x50 [ 21.047988] [a02ca6dc] ? ttm_bo_force_list_clean+0x3c/0xb0 [ttm] [ 21.048001] [a02cf6a9] ? ttm_bo_man_takedown+0x29/0x60 [ttm] [ 21.048042] [a0353e2a] ? radeon_ttm_fini+0xaa/0x170 [radeon] [ 21.048077] [a03547e9] ? radeon_bo_fini+0x9/0x20 [radeon] [ 21.048121] [a039cd1a] ? evergreen_fini+0x9a/0xc0 [radeon] [ 21.048150] [a0339e31] ? radeon_device_fini+0x31/0x100 [radeon] [ 21.048181] [a033bc04] ? radeon_driver_unload_kms+0x44/0x60 [radeon] [ 21.048201] [a028af61] ? drm_dev_unregister+0x21/0xd0 [drm] [ 21.048219] [a028b042] ? drm_put_dev+0x32/0x60 [drm] [ 21.048228] [812a1cde] ? pci_device_remove+0x2e/0xa0 [ 21.048237] [81354845] ? __device_release_driver+0x75/0xf0 [ 21.048244] [813548d9] ? device_release_driver+0x19/0x30 [ 21.048250] [8129c0ad] ? pci_stop_bus_device+0x8d/0xb0 [ 21.048257] [8129c1c9] ? pci_stop_and_remove_bus_device+0x9/0x20 [ 21.048264] [812b47d0] ? pciehp_unconfigure_device+0xa0/0x1a0 [ 21.048270] [812b411b] ? pciehp_disable_slot+0x5b/0x1f0 [ 21.048277] [812b4329] ? pciehp_power_thread+0x79/0xe0 [ 21.048285] [81074c2d] ? process_one_work+0x16d/0x420 [ 21.048291] [810757f6] ? worker_thread+0x116/0x3b0 [ 21.048298] [810756e0] ? rescuer_thread+0x330/0x330 [ 21.048304] [8107bae1] ? kthread+0xc1/0xe0 [ 21.048310] [8107ba20] ? kthread_create_on_node+0x180/0x180 [ 21.048318] [814ada4c] ? ret_from_fork+0x7c/0xb0 [ 21.048324] [8107ba20] ? kthread_create_on_node+0x180/0x180 [ 21.048328]
Bug#510528: marked as done (/etc/init.d/nfs-common is run twice, why?)
Your message dated Mon, 24 Feb 2014 19:33:37 + with message-id e1wi1hv-00021p...@franck.debian.org and subject line Bug#510528: fixed in nfs-utils 1:1.2.8-6 has caused the Debian Bug report #510528, regarding /etc/init.d/nfs-common is run twice, why? 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.) -- 510528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.1.2-6lenny1 Severity: minor hi, I have noticed that the script /etc/init.d/nfs-common is run twice at start, since it is installed into /etc/rc.? by the command update-rc.d nfs-common start 20 2 3 4 5 . stop 20 0 1 6 . start 44 S Similarl when using insserv, since its LSB headers say # Default-Start: 2 3 4 5 S # Default-Stop: 0 1 6 This is a bit weird... I read thru /etc/init.d/nfs-common, but I fail to see what is the reason for starting this script twice. a. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.110 add and remove users and groups ii initscripts 2.86.ds1-61Scripts for initializing and shutt ii libc6 2.7-16 GNU C Library: Shared libraries ii libcomerr21.41.3-1 common error description library ii libevent1 1.3e-3 An asynchronous event notification ii libgssglue1 0.1-2 mechanism-switch gssapi library ii libkrb53 1.6.dfsg.4~beta1-4 MIT Kerberos runtime libraries ii libnfsidmap2 0.20-1 An nfs idmapping library ii librpcsecgss3 0.18-1 allows secure rpc communication us ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii netbase 4.34 Basic TCP/IP networking system ii portmap 6.0-9 RPC port mapper ii ucf 3.0011 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information -- Andrea Mennucc E' un mondo difficile. Che vita intensa! (Tonino Carotone) signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.8-6 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 510...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2014 18:11:17 + Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source amd64 Version: 1:1.2.8-6 Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Steve Langasek vor...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 510528 715478 731479 736059 Changes: nfs-utils (1:1.2.8-6) unstable; urgency=medium . * Fix the sec=krb5* handling in debian/nfs-common.init to properly match all cases. Closes: #715478. * Move the rpc.svcgssd(8) symlink to nfs-common along with the rest of it, and add the Replaces: on old versions of nfs-kernel-server to support upgrades properly. Closes: #731479. * Only start nfs-common in runlevel S; it doesn't need to be started more than once (and startpar won't actually run it more than once, anyway). Closes: #510528. * Fix obsolete invocations of update-rc.d by switching nfs-common to use dh_installinit. Closes: #736059. * Tweak nfs-common preinst to not remove nfs state
Bug#731479: marked as done (nfs-kernel-server man page rpc.svcgssd.8 is a dangling symlink)
Your message dated Mon, 24 Feb 2014 19:33:37 + with message-id e1wi1hv-000222...@franck.debian.org and subject line Bug#731479: fixed in nfs-utils 1:1.2.8-6 has caused the Debian Bug report #731479, regarding nfs-kernel-server man page rpc.svcgssd.8 is a dangling symlink 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.) -- 731479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-kernel-server Version: 1:1.2.8-4 Severity: minor Dear Maintainer, rebuilding mandb following adding some unrelated man pages # mandb -c Processing manual pages under /usr/share/man... Updating index cache for path `/usr/share/man/man8'. Wait...mandb: warning: /usr/share/man/man8/rpc.svcgssd.8 is a dangling symlink dpkg-query -S rpc.svcgssd.8 nfs-kernel-server: /usr/share/man/man8/rpc.svcgssd.8 dpkg-query -S svcgssd.8.gz nfs-common: /usr/share/man/man8/svcgssd.8.gz apt-cache policy nfs-kernel-server nfs-kernel-server: Installed: 1:1.2.8-4 Candidate: 1:1.2.8-4 Version table: *** 1:1.2.8-4 0 500 http://ftp-chi.osuosl.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status ll |egrep svcg lrwxrwxrwx 1 root root 9 Jun 1 2013 rpc.svcgssd.8 - svcgssd.8 -rw-r--r-- 1 root root 762 Jun 1 2013 svcgssd.8.gz (gz vs .8 file) # rm rpc.svcgssd.8 ; ln -s svcgssd.8.gz rpc.svcgssd.8.gz # mandb -c (no longer reported an error) -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 50194 status 1000241 tcp 36516 status -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=4 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS=--manage-gids NEED_SVCGSSD= RPCSVCGSSDOPTS= -- /etc/exports -- -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-kernel-server depends on: ii libblkid1 2.20.1-5.5 ii libc6 2.17-97 ii libcap2 1:2.22-1.2 ii libgssglue1 0.4-2 ii libsqlite3-0 3.8.1-1 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-24 ii lsb-base 4.1+Debian12 ii nfs-common1:1.2.8-4 ii ucf 3.0027+nmu1 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.8-6 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 731...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2014 18:11:17 + Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source amd64 Version: 1:1.2.8-6 Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Steve Langasek vor...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 510528 715478 731479 736059 Changes: nfs-utils (1:1.2.8-6) unstable; urgency=medium . * Fix the sec=krb5* handling in debian/nfs-common.init to properly match all cases. Closes: #715478. * Move the rpc.svcgssd(8) symlink to nfs-common along with the rest of it, and add the Replaces: on old versions of nfs-kernel-server to support upgrades properly. Closes: #731479. * Only start nfs-common in runlevel S; it doesn't need to be started more than once (and startpar won't actually run it more than once, anyway). Closes:
Processing of nfs-utils_1.2.8-6_amd64.changes
nfs-utils_1.2.8-6_amd64.changes uploaded successfully to localhost along with the files: nfs-utils_1.2.8-6.dsc nfs-utils_1.2.8-6.debian.tar.bz2 nfs-kernel-server_1.2.8-6_amd64.deb nfs-common_1.2.8-6_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1wi14a-sc...@franck.debian.org
Bug#736059: marked as done (nfs-common: using deprecated update-rc.d options)
Your message dated Mon, 24 Feb 2014 19:33:37 + with message-id e1wi1hv-000227...@franck.debian.org and subject line Bug#736059: fixed in nfs-utils 1:1.2.8-6 has caused the Debian Bug report #736059, regarding nfs-common: using deprecated update-rc.d options 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.) -- 736059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.8-5 Severity: minor Tags: patch During installation, dpkg says: Setting up nfs-common (1:1.2.8-5) ... Installing new version of config file /etc/init.d/nfs-common ... Replacing config file /etc/idmapd.conf with new version update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults [ ok ] Stopping NFS common utilities: idmapd statd. [ ok ] Starting NFS common utilities: statd idmapd. Note that the start and stop actions are no longer used; check the update-rc.d manpage for more details. Also, the start levels (20 and 44 in the postinst) are now worked out dynamically from the dependency information in the initscript headers: on my system, I have: polya:~ $ /bin/ls -1 /etc/rc?.d/*nfs-common /etc/rc0.d/K07nfs-common /etc/rc1.d/K07nfs-common /etc/rc2.d/S19nfs-common /etc/rc3.d/S19nfs-common /etc/rc4.d/S19nfs-common /etc/rc5.d/S19nfs-common /etc/rc6.d/K07nfs-common /etc/rcS.d/S19nfs-common So the patch is to replace the complex update-rc.d call in the postinst with just: update-rc.d nfs-common defaults HTH, Julian ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.8-6 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 736...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2014 18:11:17 + Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source amd64 Version: 1:1.2.8-6 Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Steve Langasek vor...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 510528 715478 731479 736059 Changes: nfs-utils (1:1.2.8-6) unstable; urgency=medium . * Fix the sec=krb5* handling in debian/nfs-common.init to properly match all cases. Closes: #715478. * Move the rpc.svcgssd(8) symlink to nfs-common along with the rest of it, and add the Replaces: on old versions of nfs-kernel-server to support upgrades properly. Closes: #731479. * Only start nfs-common in runlevel S; it doesn't need to be started more than once (and startpar won't actually run it more than once, anyway). Closes: #510528. * Fix obsolete invocations of update-rc.d by switching nfs-common to use dh_installinit. Closes: #736059. * Tweak nfs-common preinst to not remove nfs state files except on package removal (i.e., these should not be removed when the package is deconfigured temporarily). * debian/nfs-kernel-server.init: don't try to check for nfsv3 configuration in nfsd and pass --no-nfs-version 3 to mountd if absent; the check is buggy and impossible to make reliable, and there's no reason to single out NFSv3 here (and the original rationale for this behavior is lost). Closes LP: #897644, LP: #1284210. * Provide quoted entries by default in debian/nfs-kernel-server.default, consistent with other default files, so that users who edit the file to add multiple options don't accidentally cause shell syntax bugs. Checksums-Sha1: 9fcfaa5e6dbd5e0f3372203d23d3a95b55c199a8 2254 nfs-utils_1.2.8-6.dsc 6ca69e13f43b23a8f57c4950c7cd42924c54fc85 39164 nfs-utils_1.2.8-6.debian.tar.bz2 f2924ea82a15c7789732f895b1e6d45b7791bd2b 114440 nfs-kernel-server_1.2.8-6_amd64.deb 89f961c4c4f698f36cc23146777118dcd2a68496 204508
Bug#715478: marked as done (Correctly match *,sec=krb5,*)
Your message dated Mon, 24 Feb 2014 19:33:37 + with message-id e1wi1hv-00021v...@franck.debian.org and subject line Bug#715478: fixed in nfs-utils 1:1.2.8-6 has caused the Debian Bug report #715478, regarding Correctly match *,sec=krb5,* 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.) -- 715478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.6-4 Severity: normal Tags: patch The fourth krb5 case wrongly matches krb5i (nfs-common.init:59). diff -urwN a/debian/nfs-common.init b/debian/nfs-common.init --- a/debian/nfs-common.init 2013-05-11 14:38:17.0 +0200 +++ b/debian/nfs-common.init 2013-07-09 15:07:06.497879734 +0200 @@ -50,13 +50,14 @@ continue ;; esac - # FSTYPE nfs can be NFSv4 now -#if [ $FSTYPE = nfs4 ]; then + +# FSTYPE nfs can be NFSv4 now, so always start idmapd AUTO_NEED_IDMAPD=yes -#fi -case $OPTS in -sec=krb5|*,sec=krb5|sec=krb5,*|*,sec=krb5i,*|sec=krb5i|*,sec=krb5i|sec=krb5i,*|*,sec=krb5i,*|sec=krb5p|*,sec=krb5p|sec=krb5p,*|*,sec=krb5p,*) +case $OPTS in +sec=krb5|*,sec=krb5|sec=krb5,*|*,sec=krb5,*|\ +sec=krb5i|*,sec=krb5i|sec=krb5i,*|*,sec=krb5i,*|\ +sec=krb5p|*,sec=krb5p|sec=krb5p,*|*,sec=krb5p,*) AUTO_NEED_GSSD=yes ;; esac ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.8-6 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 715...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2014 18:11:17 + Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source amd64 Version: 1:1.2.8-6 Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Steve Langasek vor...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 510528 715478 731479 736059 Changes: nfs-utils (1:1.2.8-6) unstable; urgency=medium . * Fix the sec=krb5* handling in debian/nfs-common.init to properly match all cases. Closes: #715478. * Move the rpc.svcgssd(8) symlink to nfs-common along with the rest of it, and add the Replaces: on old versions of nfs-kernel-server to support upgrades properly. Closes: #731479. * Only start nfs-common in runlevel S; it doesn't need to be started more than once (and startpar won't actually run it more than once, anyway). Closes: #510528. * Fix obsolete invocations of update-rc.d by switching nfs-common to use dh_installinit. Closes: #736059. * Tweak nfs-common preinst to not remove nfs state files except on package removal (i.e., these should not be removed when the package is deconfigured temporarily). * debian/nfs-kernel-server.init: don't try to check for nfsv3 configuration in nfsd and pass --no-nfs-version 3 to mountd if absent; the check is buggy and impossible to make reliable, and there's no reason to single out NFSv3 here (and the original rationale for this behavior is lost). Closes LP: #897644, LP: #1284210. * Provide quoted entries by default in debian/nfs-kernel-server.default, consistent with other default files, so that users who edit the file to add multiple options don't accidentally cause shell syntax bugs. Checksums-Sha1: 9fcfaa5e6dbd5e0f3372203d23d3a95b55c199a8 2254 nfs-utils_1.2.8-6.dsc 6ca69e13f43b23a8f57c4950c7cd42924c54fc85 39164 nfs-utils_1.2.8-6.debian.tar.bz2 f2924ea82a15c7789732f895b1e6d45b7791bd2b 114440 nfs-kernel-server_1.2.8-6_amd64.deb 89f961c4c4f698f36cc23146777118dcd2a68496 204508 nfs-common_1.2.8-6_amd64.deb Checksums-Sha256: edb374ecf3af92383040b9058c796d9904d703b17b19fa5bcaf47d6e5dcd 2254 nfs-utils_1.2.8-6.dsc
nfs-utils_1.2.8-6_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2014 18:11:17 + Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source amd64 Version: 1:1.2.8-6 Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Steve Langasek vor...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 510528 715478 731479 736059 Changes: nfs-utils (1:1.2.8-6) unstable; urgency=medium . * Fix the sec=krb5* handling in debian/nfs-common.init to properly match all cases. Closes: #715478. * Move the rpc.svcgssd(8) symlink to nfs-common along with the rest of it, and add the Replaces: on old versions of nfs-kernel-server to support upgrades properly. Closes: #731479. * Only start nfs-common in runlevel S; it doesn't need to be started more than once (and startpar won't actually run it more than once, anyway). Closes: #510528. * Fix obsolete invocations of update-rc.d by switching nfs-common to use dh_installinit. Closes: #736059. * Tweak nfs-common preinst to not remove nfs state files except on package removal (i.e., these should not be removed when the package is deconfigured temporarily). * debian/nfs-kernel-server.init: don't try to check for nfsv3 configuration in nfsd and pass --no-nfs-version 3 to mountd if absent; the check is buggy and impossible to make reliable, and there's no reason to single out NFSv3 here (and the original rationale for this behavior is lost). Closes LP: #897644, LP: #1284210. * Provide quoted entries by default in debian/nfs-kernel-server.default, consistent with other default files, so that users who edit the file to add multiple options don't accidentally cause shell syntax bugs. Checksums-Sha1: 9fcfaa5e6dbd5e0f3372203d23d3a95b55c199a8 2254 nfs-utils_1.2.8-6.dsc 6ca69e13f43b23a8f57c4950c7cd42924c54fc85 39164 nfs-utils_1.2.8-6.debian.tar.bz2 f2924ea82a15c7789732f895b1e6d45b7791bd2b 114440 nfs-kernel-server_1.2.8-6_amd64.deb 89f961c4c4f698f36cc23146777118dcd2a68496 204508 nfs-common_1.2.8-6_amd64.deb Checksums-Sha256: edb374ecf3af92383040b9058c796d9904d703b17b19fa5bcaf47d6e5dcd 2254 nfs-utils_1.2.8-6.dsc 859c6f354bdb8f20afe9aad0c487699c14cd2af202b5a89bca71575c90eff42c 39164 nfs-utils_1.2.8-6.debian.tar.bz2 d229e3fba1f1420f4282fac39f480e4526acf03b23d3b2726b4525dc3e619aec 114440 nfs-kernel-server_1.2.8-6_amd64.deb a2580d0324e19235844c14b726f593b5897dd209ed1d344bc4f66620fd5dd5fc 204508 nfs-common_1.2.8-6_amd64.deb Files: ea14c411e237494c3c07a1b1e19be5aa 2254 net standard nfs-utils_1.2.8-6.dsc d8ef56c3ce0b15daaded260c7afcff9f 39164 net standard nfs-utils_1.2.8-6.debian.tar.bz2 54806ec103bdac9d7f1b30ea2cff74ca 114440 net optional nfs-kernel-server_1.2.8-6_amd64.deb e245c4770481c793cb92fe51863fd14a 204508 net standard nfs-common_1.2.8-6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTC5oUAAoJEFaNMPMhshM90TEQAJX8M5WhTnDhDQBhp1AixYPj nxDAwgWWU8ELL3vzt+amHC/MzpgN93Qqf0KMzysAD7FCmRJvZMFoq2jnMNbrOxqp AC49JDiKogAFPJbnye7QMBQfxOLckVFNtsio2XFwzNFunUTr2jgCCVFAemZOMDMx vbor1CRA/D7cqc0d0BaEcVdZjH82yn00HqOSYr8Iy1Hbs9Fw/051EpcPEV1iOdjV 0Cu1ZTi4G5vec33VbTjAJ38DTq6MA6klq2L/sx9RleEIMQbJ3zaMLAQzxEdOCAkF xvUmmdsNzH7BkO32wHQrFelvc0Ge86cPWRBevq6/YZ6b0Sbt8whg1WlSeMH31x8x it1Oy/ChE+yxr+VzQwJTygMF99siA3kL1nrUn90YX1sjtzN7uPlnhHTvvXFz0ODL lyX0WUGt5EVQtVbiQSK10fqbsFS0Q0Ued5788kKZ3Wjrdw0kpT8yzC03jFqBgTKg bLipQjWKLLZtqKEsoXv/S5H7Jkpzx73qMN7lLq3BS17KUhE3mBTeXRfnInX+Lotb fZBhkPHCv9fdcy2PcQKURtzHZcJRYazU3sqKULPsD3qCtgwjfqXri67cLtfpg/XB 0dvT1dFG68/Z7U2V1rG1NuLx9YOUroF3w3U1SoulYFC/ILp5I6Ot9gThGoy7o8eQ 3fP3y0LHI7zi70uPGSP0 =dUSQ -END PGP SIGNATURE- Thank you for your contribution to Debian. -- 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/e1wi1hv-00021g...@franck.debian.org
Re: [PATCH 21/21] ARM: Kirkwood: Remove DT support
On Mon, 2014-02-24 at 16:03 +, Ian Campbell wrote: On Fri, 2014-02-21 at 02:00 +, Ben Hutchings wrote: On Thu, 2014-02-20 at 14:24 +, Ian Campbell wrote: On Thu, 2014-02-20 at 14:23 +0100, Andrew Lunn wrote: [...] What i suspect we will end up doing it dropping the last patch for the moment and ensuring ARCH_KIRKWOOD still supports all the DT machines. I think that just needs care with arch/arm/boot/dts/Makefile. Once we have the last four converted over to DT, you can then do a straight swap, mach-kirkwood for mach-mvebu. That sounds like a good plan, thanks! If we are going to do a straight swap I suppose it might as go for a v5 multiplatform flavour instead of a mvebu specific one. [...] I would love it if we could do that. By the way, we still have the problem that at least one supported orion5x machine (D-Link DNS-323) only has a ~1.5 MB kernel partition. So we would probably have to keep a reduced orion5x config for those machines, alongside the mvebu or multiplatform kernel. Sure. I think at worst we should aim to end up with as many flavour as we have today, in reality I expect we should be able to end up with fewer (even if only -= 1). BTW, someone (I forget who) at Debconf in Cambridge last year floated the idea of putting a stage 2 loader in flash to pull the real kernel from some larger storage. I don't know if that is realistic here, and in any case I don't intend to work on it myself. I do remember that, and I like it. But in order to rely on this, I think we would need to provide a mostly automatic and safe upgrade path in Debian. Unless someone is prepared to spend the (possibly substantial) effort to do that, we're stuck with that limitation. Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: This is a digitally signed message part
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Mon, 2014-02-24 at 15:48 +, Ian Campbell wrote: On Sat, 2014-02-22 at 22:56 +, Ben Hutchings wrote: On Mon, 2013-09-30 at 20:25 +1000, Kris Shannon wrote: I was eagerly awating the release of linux-2.6_2.6.32-48squeeze4 because it would fix #701744 (fallout from XSA-39: Linux netback DoS via malicious guest ring) It turns out I should have read the bug report more closely. #701744 was only about the xen-netback side of things. I haven't been able to find a debian bug about the REAL bug - the xen-netfront gso overflow. Upstream have patched this: http://git.kernel.org/linus/9ecd1a75d977e2e8c48139c7d3efed183f898d94 netfront: reduce gso_max_size to account for max TCP header Is this likely to go into a squeeze kernel? Maybe. Ian, is this going to be possible to backport? It looks fairly small and self contained, so I suspect so. Wei -- does that sound right (the backport target is Debian Wheezy which is 2.6.32) The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? A regression due to a security fix is also a valid reason for a further security update. Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: This is a digitally signed message part
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Mon, 2014-02-24 at 20:11 +, Ben Hutchings wrote: On Mon, 2014-02-24 at 15:48 +, Ian Campbell wrote: The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? A regression due to a security fix is also a valid reason for a further security update. Ah, I'd forgotten that was why this was. I'll try and take a look but I'm travelling for the next ~10 days. Is there a bug # for this issue separate from the already closed backend one? Ian. -- 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/1393272871.9640.7.ca...@dagon.hellion.org.uk
Re: Bug#739972: missing kernel config options for support of mirabox
Control: reassign -1 src:linux 3.13-1~exp1 On Lu, 24 feb 14, 14:22:03, Jasmin Schnatterbeck wrote: Source: linux-image-3.13-trunk-armmp Version: 3.13-1~exp1 Severity: important the mentioned multiplatform kernel ist intended to run on armada 370 SOCs. A system using this SOC is the Mirabox. I noticed, that the following modules are missing in the armmp kernel to support the device properly: xhci controller: CONFIG_USB_XHCI_HCD=m mwifiex wifi: CONFIG_MWIFIEX=m CONFIG_MWIFIEX_SDIO=m Futhermore hctosys-on-boot does not work. As the /etc/init.d/hwlock.sh script does not run in rcS, because udev is already active, the system time relies on the kernel, that needs to set it from rtc on boot time. In order to make this work, the rtc driver must be compiled-in (as far as I investigated the situation): RTC_DRV_MV=y Furthermore the PCI-Controller of the device needs the following kernel option to make it work: CONFIG_PCI_MVEBU=y The mentioned modifications are tested locally and work. If the options for RTC and PCI (non-module) conflict with other options (related to another device), a separated flavour would still be necessary. Cheers Jasmin -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Processed: Re: Bug#739972: missing kernel config options for support of mirabox
Processing control commands: reassign -1 src:linux 3.13-1~exp1 Bug #739972 [src:linux-image-3.13-trunk-armmp] missing kernel config options for support of mirabox Warning: Unknown package 'src:linux-image-3.13-trunk-armmp' Bug reassigned from package 'src:linux-image-3.13-trunk-armmp' to 'src:linux'. No longer marked as found in versions linux-image-3.13-trunk-armmp/3.13-1~exp1. Ignoring request to alter fixed versions of bug #739972 to the same values previously set Bug #739972 [src:linux] missing kernel config options for support of mirabox Marked as found in versions linux/3.13-1~exp1. -- 739972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739972 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.b739972.139327351114918.transcr...@bugs.debian.org
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Mon, 2014-02-24 at 20:14 +, Ian Campbell wrote: On Mon, 2014-02-24 at 20:11 +, Ben Hutchings wrote: On Mon, 2014-02-24 at 15:48 +, Ian Campbell wrote: The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? A regression due to a security fix is also a valid reason for a further security update. Ah, I'd forgotten that was why this was. I'll try and take a look but I'm travelling for the next ~10 days. Is there a bug # for this issue separate from the already closed backend one? It doesn't look like it. Kris, please open a new bug report. Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: This is a digitally signed message part
Re: Accepted nfs-utils 1:1.2.8-6 (source amd64)
[Steve Langasek] * Only start nfs-common in runlevel S; it doesn't need to be started more than once (and startpar won't actually run it more than once, anyway). Closes: #510528. Actually, the question is not if it need to be started more than once, but if it should be restarted when switching to runlevel 1, and back to runlevels 2-5. :) So all daemons started in rcS.d (which really should be named rcboot.d :) should have start symlinks in runlevels 2-5 too, to make sure runlevel 1 have a chance of working. :) -- Happy hacking Petter Reinholdtsen -- 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/20140224202656.gx3...@ulrik.uio.no
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Mon, 2014-02-24 at 21:23 +, Wei Liu wrote: On Mon, Feb 24, 2014 at 08:14:31PM +, Ian Campbell wrote: On Mon, 2014-02-24 at 20:11 +, Ben Hutchings wrote: On Mon, 2014-02-24 at 15:48 +, Ian Campbell wrote: The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? A regression due to a security fix is also a valid reason for a further security update. Ah, I'd forgotten that was why this was. I'll try and take a look but I'm travelling for the next ~10 days. Given the simplicity of the patch I can provide trivial backport as well. However it would probably take more time for me to familiarize with Debian's workflow than to actually backport the patch! :-) If you are interested in how the Debian kernel is put together and want to take a stab at it I'd be happy to advise etc, but if not I'll just take care of it myself. I'll assume not unless you say otherwise... Ian. Wei. Is there a bug # for this issue separate from the already closed backend one? Ian. -- 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/1393277441.9640.10.ca...@dagon.hellion.org.uk
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Mon, Feb 24, 2014 at 08:14:31PM +, Ian Campbell wrote: On Mon, 2014-02-24 at 20:11 +, Ben Hutchings wrote: On Mon, 2014-02-24 at 15:48 +, Ian Campbell wrote: The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? A regression due to a security fix is also a valid reason for a further security update. Ah, I'd forgotten that was why this was. I'll try and take a look but I'm travelling for the next ~10 days. Given the simplicity of the patch I can provide trivial backport as well. However it would probably take more time for me to familiarize with Debian's workflow than to actually backport the patch! :-) Wei. Is there a bug # for this issue separate from the already closed backend one? Ian. -- 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/20140224212350.ga18...@zion.uk.xensource.com
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On Mon, Feb 24, 2014 at 09:30:41PM +, Ian Campbell wrote: On Mon, 2014-02-24 at 21:23 +, Wei Liu wrote: On Mon, Feb 24, 2014 at 08:14:31PM +, Ian Campbell wrote: On Mon, 2014-02-24 at 20:11 +, Ben Hutchings wrote: On Mon, 2014-02-24 at 15:48 +, Ian Campbell wrote: The other question is whether there will be any more updates to the Squeeze kernel at all, aren't we into security fixes only mode for Squeeze by now? A regression due to a security fix is also a valid reason for a further security update. Ah, I'd forgotten that was why this was. I'll try and take a look but I'm travelling for the next ~10 days. Given the simplicity of the patch I can provide trivial backport as well. However it would probably take more time for me to familiarize with Debian's workflow than to actually backport the patch! :-) If you are interested in how the Debian kernel is put together and want to take a stab at it I'd be happy to advise etc, but if not I'll just take care of it myself. I'll assume not unless you say otherwise... I took a stab but couldn't get it to work. So I guess you need to take care of it then. Wei. Ian. Wei. Is there a bug # for this issue separate from the already closed backend one? Ian. -- 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/20140224225417.gb18...@zion.uk.xensource.com
Bug#740018: start run levels in rc2-5 are not properly clean up on upgrades
Package: nfs-common Version: 1:1.2.8-6 Severity: important The nfs-common LSB header was updated to only start the service in runlevel S, and no longer in S 2 3 4 5. The existing start symlinks are not removed on upgrades though: ls -la /etc/rc?.d/???nfs-common lrwxrwxrwx 1 root root 20 Sep 28 02:46 /etc/rc0.d/K06nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 root root 20 Sep 28 02:46 /etc/rc1.d/K06nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 root root 20 Feb 5 14:42 /etc/rc2.d/S16nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 root root 20 Feb 5 14:42 /etc/rc3.d/S16nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 root root 20 Feb 5 14:42 /etc/rc4.d/S16nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 root root 20 Feb 5 14:42 /etc/rc5.d/S16nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 root root 20 Sep 28 02:46 /etc/rc6.d/K06nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 root root 20 Feb 5 14:42 /etc/rcS.d/S16nfs-common - ../init.d/nfs-common This also leads to insserv: warning: current start runlevel(s) (2 3 4 5 S) of script `nfs-common' overrides LSB defaults (S). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-51 ii libc6 2.18-3 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.9-3 ii libdevmapper1.02.1 2:1.02.83-2 ii libevent-2.0-5 2.0.21-stable-1 ii libgssglue1 0.4-2 ii libk5crypto31.12+dfsg-2 ii libkeyutils11.5.6-1 ii libkrb5-3 1.12+dfsg-2 ii libmount1 2.20.1-5.6 ii libnfsidmap20.25-5 ii libtirpc1 0.2.2-5.1 ii libwrap07.6.q-25 ii lsb-base4.1+Debian12 ii rpcbind 0.2.1-3 ii ucf 3.0027+nmu1 Versions of packages nfs-common recommends: ii python 2.7.5-5 Versions of packages nfs-common suggests: pn open-iscsi none pn watchdognone Versions of packages nfs-kernel-server depends on: ii libblkid1 2.20.1-5.6 ii libc6 2.18-3 ii libcap2 1:2.22-1.2 ii libgssglue1 0.4-2 ii libsqlite3-0 3.8.3.1-1 ii libtirpc1 0.2.2-5.1 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian12 ii ucf 3.0027+nmu1 -- 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/20140224234531.6650.45523.report...@pluto.milchstrasse.xx
Bug#740042: linux: The module chromeos_laptop is not enabled in kernel 3.13, needed to enable touchpad on chromebooks
Source: linux Version: 3.13 Severity: important Dear Maintainer, * What led up to the situation? I upgraded the kernel from 3.12 to 3.13 and found my touchpad was not working. This is due to the fact that 3.13 does not have the chromeos_laptop module anymore. * What exactly did you do (or not do) that was effective (or ineffective)? Nothing * What was the outcome of this action? The touchpad no longer works because of missing chromeos_laptop module * What outcome did you expect instead? I expected the touchpad to continue to work and the chromeos_laptop module to be included with the update. Thanks to the folks at #debian-next on OFTC it seems that the modules were moved to a new directory. Because of this a new kernel config line needs to be toggled to enable the chromeos_laptop module again. Info of this is here, https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ab0431059ed0d0e3a9e532ad0488ada25021249d -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 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/20140225053156.7001.11339.reportbug@AcerChromebook-debian
Re: linux-2.6_2.6.32-48squeeze4 and Bug #701744
On 25/02/2014 7:44 am, Ben Hutchings wrote: On Mon, 2014-02-24 at 20:14 +, Ian Campbell wrote: On Mon, 2014-02-24 at 20:11 +, Ben Hutchings wrote: A regression due to a security fix is also a valid reason for a further security update. Ah, I'd forgotten that was why this was. I'll try and take a look but I'm travelling for the next ~10 days. Is there a bug # for this issue separate from the already closed backend one? It doesn't look like it. Kris, please open a new bug report. Ben. #740041 BTW, this is no longer an active problem for us since Redhat finally included the netback patch in their RHEL5 kernel (and it trickled down to CentOS) -- 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/530c30be.6050...@shannon.id.au
Bug#740042: linux: The module chromeos_laptop is not enabled in kernel 3.13, needed to enable touchpad on chromebooks
As a workaround, I copied /boot/config-3.13-1-amd64 to /boot/config-3.13-1-amd64-chrome and added the line CONFIG_CHROME_PLATFORMS=y Then at the point in the modified cros-haswell-modules.sh for Debian where it notices config has changed, I answered m. (Should I have set CONFIG_CHROME_PLATFORMS to m in the first place?) I modified cros-haswell-modules.sh for 3.13 following the directions from: https://wiki.archlinux.org/index.php/Acer_C720_Chromebook and pulling in the modified /boot/config-3.13-1-amd64-chrome for the config. Note that the module is built and installed in a new directory platform/chrome not platform/x86. -- 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/CABZaEK6m-SF+1=E7nbykVYVRtYb3Hw-g7uu1Thk3VPe9aQO=a...@mail.gmail.com
