Re: drbd in linux-2.6
On Wed, Apr 07, 2010 at 12:39:47AM +0200, maximilian attems wrote: On Tue, Apr 06, 2010 at 04:09:54PM -0600, dann frazier wrote: My plan is therefore to: 1) Commit these changes for inclusion in the next linux-2.6 upload 2) After that upload, I will file an RC bug to request the removal of the drbd8-source binary from the drbd8 source package Comments? 2.6.32-12 is expected soonish once the libata HPA patches are finaly cooked. I'd prefer to keep that a minimal fix release. So that we can push -4 into squeeze. could drdb wait for -13, is that ok? Sure. -- dann frazier -- 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/20100406225525.gd9...@lackof.org
Re: drbd in linux-2.6
On Tue, Mar 30, 2010 at 11:45:54PM +0200, Moritz Muehlenhoff wrote: On 2010-03-30, dann frazier da...@debian.org wrote: drbd maintainers, As you no doubt know, linux-modules-extra has been dropped for squeeze. The recommended[1] direction for building out-of-tree module is to either: a) get merged into linux-2.6 b) use the dkms framework DRBD is now merged upstream, so it seems like a good candidate for option a. Do the drbd8 maintainers know of any issue with that (userspace tool compatability, etc)? Are you ok with dropping the drbd8-source binary package if we include this in linux-2.6? I've backported the latest upstream DRBD bits into our kernel targeted at squeeze: http://people.debian.org/~dannf/drbd/ I'd appreciate it if an existing drbd user could test it. [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html I've done the same 3-4 weeks ago and likewise send them the patch for testing, unfortunately they we unable to test it yet. Oh, sorry - I must've missed that. Did you get a response or just silence? I was thinking that if we didn't get a response in a couple of days, I could contact some of the drbd8 bug reporters and see if we can recruit them to test :) -- dann frazier -- 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/20100330220222.ga...@lackof.org
Bug#574529: release-notes: [SQUEEZE] vserver kernel flavors deprecated
Package: release-notes Severity: normal As mentioned in [1], the vserver featureset is planned to be removed from the Debian linux kernel after the squeeze release. Debian suggests that users consider migrating vserver systems to either the LXC (Linux Containers) features of the upstream kernel or to the openvz featureset. [1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100318202433.8204.30376.report...@krebs.dannf
Bug#573531: drbd8-modules-2.6.26-2-amd64: Can not load drbd module
On Mon, Mar 15, 2010 at 11:30:31AM -0400, David Miller wrote: I've also been bitten by this bug - noticed it last Friday and it doesn't seem to be fixed this morning. Is there an ETA on a fix with packages? Packages are now available in the security repo (an apt-get upgrade should suffice). I'm hoping to get a CVE ID before sending out a formal DSA. -- 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/20100315165651.ga15...@lackof.org
Re: linux-modules-extra-2.6_2.6-26-6+lenny2_ia64.changes REJECTED
On Mon, Mar 15, 2010 at 05:17:26PM +, Archive Administrator wrote: Reject Reasons: linux-modules-extra-2.6_2.6-26-6+lenny2.dsc: old version (2.6.18-7+etch4) in oldstable = new version (2.6-26-6+lenny2) targeted at proposed-updates. linux-modules-extra-2.6_2.6-26-6+lenny2.dsc: old version (2.6.26-6+lenny1) in stable = new version (2.6-26-6+lenny2) targeted at proposed-updates. Looks like a typo in the version string (2.6-26 vs. 2.6.26) - will correct and reupload. -- dann frazier -- 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/20100315172711.gb15...@lackof.org
Re: Bug#573531: drbd8-modules-2.6.26-2-amd64: Can not load drbd module
On Mon, Mar 15, 2010 at 06:50:58PM +0100, Moritz Muehlenhoff wrote: On 2010-03-15, dann frazier da...@debian.org wrote: On Mon, Mar 15, 2010 at 11:30:31AM -0400, David Miller wrote: I've also been bitten by this bug - noticed it last Friday and it doesn't seem to be fixed this morning. Is there an ETA on a fix with packages? Packages are now available in the security repo (an apt-get upgrade should suffice). I'm hoping to get a CVE ID before sending out a formal DSA. Why? That should be covered by the CVE ID for the original connector security bug. Just to make sure we're talking about the same thing... One reason for this upload is to deal with the ABI breakage from the kernel upload which fixed CVE-2009-3725. I agree that no additional CVE is warranted to deal with that. However, as part of fixing this, we discovered that drbd contains a security issue as well. This issue is in the same class as the issues covered by CVE-2009-3725. However, CVE-2009-3725 has an explicit list of 4 subsystems it covers, and drbd is not one of them. -- dann frazier -- 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/20100315181306.gc15...@lackof.org
Re: Bug#573531: drbd8-modules-2.6.26-2-amd64: Can not load drbd module
On Mon, Mar 15, 2010 at 07:39:58PM +0100, Moritz Muehlenhoff wrote: On Mon, Mar 15, 2010 at 12:13:06PM -0600, dann frazier wrote: On Mon, Mar 15, 2010 at 06:50:58PM +0100, Moritz Muehlenhoff wrote: On 2010-03-15, dann frazier da...@debian.org wrote: On Mon, Mar 15, 2010 at 11:30:31AM -0400, David Miller wrote: I've also been bitten by this bug - noticed it last Friday and it doesn't seem to be fixed this morning. Is there an ETA on a fix with packages? Packages are now available in the security repo (an apt-get upgrade should suffice). I'm hoping to get a CVE ID before sending out a formal DSA. Why? That should be covered by the CVE ID for the original connector security bug. Just to make sure we're talking about the same thing... One reason for this upload is to deal with the ABI breakage from the kernel upload which fixed CVE-2009-3725. I agree that no additional CVE is warranted to deal with that. However, as part of fixing this, we discovered that drbd contains a security issue as well. This issue is in the same class as the issues covered by CVE-2009-3725. However, CVE-2009-3725 has an explicit list of 4 subsystems it covers, and drbd is not one of them. Ack. But since the underlying issue is identical I don't think a separate CVE ID is warranted. The CVE description can still be updated later if needed. I would agree with the above if the same fix for issues 1-4 also fixed this issue - but in this case, it doesn't. All of these fixes required an underlying change in the connector subsystem (allowing the passing of creds into the callback). But, *using* that change requires a separate change in each subsystem. It is completely possible to fix one subsystem and leave the others unfixed. They will compile fine, though there would be a non-fatal compiler warning that could go unnoticed. I don't think it makes sense to go back and add drbd to the CVE after the fact, because it changes the semantics. It is quite possible that some other vendor is out there shipping drbd and has already fixed CVE-2009-3725. Doing an update instead of a new CVE may cause this additional issue to go unnoticed/unfixed. In other words I think that, once distros have fixed a CVE, it isn't ok to add more fixes to that CVE which contradict the distro's statement that the CVE is fixed. Particularly when a new CVE could be used instead. For some precedence, see the recent regression fixes in CVE-2009-453[6-8]. Those are fixes for regressions introduced by previous CVE fixes - but they chose to allocate new CVEs instead of updating the existing ones. I'm sure we could dig up precedence to the contrary - CVE-2010-0307 might be an example, if we consider 1dfc76ec to be a security fix vs. just a regression. That said, it really is MITRE's call - so we'll see how they respond to my request. If they prefer to update the existing CVE, that's fine by me. -- dann frazier -- 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/20100315193908.gd15...@lackof.org
Bug#573531: drbd8-modules-2.6.26-2-amd64: Can not load drbd module
On Mon, Mar 15, 2010 at 02:45:13PM -0400, David Miller wrote: dann frazier wrote: On Mon, Mar 15, 2010 at 11:30:31AM -0400, David Miller wrote: I've also been bitten by this bug - noticed it last Friday and it doesn't seem to be fixed this morning. Is there an ETA on a fix with packages? Packages are now available in the security repo (an apt-get upgrade should suffice). I'm hoping to get a CVE ID before sending out a formal DSA. Am I doing something st00pid, as usual? No - turns out we had a typo that prevents apt from upgrading. A new version is currently being built and should be released later today. -- 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/20100315194220.ge15...@lackof.org
Re: Bug#573531: drbd8-modules-2.6.26-2-amd64: Can not load drbd module
On Mon, Mar 15, 2010 at 08:45:46PM +0100, Moritz Muehlenhoff wrote: On Mon, Mar 15, 2010 at 01:39:08PM -0600, dann frazier wrote: On Mon, Mar 15, 2010 at 07:39:58PM +0100, Moritz Muehlenhoff wrote: On Mon, Mar 15, 2010 at 12:13:06PM -0600, dann frazier wrote: On Mon, Mar 15, 2010 at 06:50:58PM +0100, Moritz Muehlenhoff wrote: On 2010-03-15, dann frazier da...@debian.org wrote: On Mon, Mar 15, 2010 at 11:30:31AM -0400, David Miller wrote: I've also been bitten by this bug - noticed it last Friday and it doesn't seem to be fixed this morning. Is there an ETA on a fix with packages? Packages are now available in the security repo (an apt-get upgrade should suffice). I'm hoping to get a CVE ID before sending out a formal DSA. Why? That should be covered by the CVE ID for the original connector security bug. Just to make sure we're talking about the same thing... One reason for this upload is to deal with the ABI breakage from the kernel upload which fixed CVE-2009-3725. I agree that no additional CVE is warranted to deal with that. However, as part of fixing this, we discovered that drbd contains a security issue as well. This issue is in the same class as the issues covered by CVE-2009-3725. However, CVE-2009-3725 has an explicit list of 4 subsystems it covers, and drbd is not one of them. Ack. But since the underlying issue is identical I don't think a separate CVE ID is warranted. The CVE description can still be updated later if needed. I would agree with the above if the same fix for issues 1-4 also fixed this issue - but in this case, it doesn't. All of these fixes required an underlying change in the connector subsystem (allowing the passing of creds into the callback). But, *using* that change requires a separate change in each subsystem. It is completely possible to fix one subsystem and leave the others unfixed. They will compile fine, though there would be a non-fatal compiler warning that could go unnoticed. I don't think it makes sense to go back and add drbd to the CVE after the fact, because it changes the semantics. It is quite possible that some other vendor is out there shipping drbd and has already fixed CVE-2009-3725. Doing an update instead of a new CVE may cause this additional issue to go unnoticed/unfixed. In other words I think that, once distros have fixed a CVE, it isn't ok to add more fixes to that CVE which contradict the distro's statement that the CVE is fixed. Particularly when a new CVE could be used instead. For some precedence, see the recent regression fixes in CVE-2009-453[6-8]. Those are fixes for regressions introduced by previous CVE fixes - but they chose to allocate new CVEs instead of updating the existing ones. I'm sure we could dig up precedence to the contrary - CVE-2010-0307 might be an example, if we consider 1dfc76ec to be a security fix vs. just a regression. That said, it really is MITRE's call - so we'll see how they respond to my request. If they prefer to update the existing CVE, that's fine by me. Ok. But I recommend against holding back the update until a CVE is assigned. MITRE isn't working properly these days, we already needed to release several DSA w/o CVE IDs being assigned so far. Just write Not yet available as done for DSA 2013, DSA 2016 and DSA 2008. ok, I'll do that. fyi, it should go out in a couple hours (last build just completed). -- dann frazier -- 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/20100315234127.gf15...@lackof.org
Bug#569704: potential fix
On Fri, Mar 12, 2010 at 04:06:41PM +0100, Tollef Fog Heen wrote: ]] dann frazier | A coworker was seeing the same symptoms on a system from the | same-era loaned me the system to debug. The issue ended up being | due to a change in the SRAT table, and a backport of the following | fixed it for me. | | I've committed it to the lenny branch - would you be able to test it? Sure, I should be able to test it. Just grab current lenny + the patch listed below? It is already committed, so you should be able to: wget http://yrmirror/debian/pool/main/l/linux-2.6/linux-2.6_2.6.26.orig.tar.gz tar xfz linux-2.6_2.6.26.orig.tar.gz cd linux-2.6-2.6.26 svn export svn://svn.debian.org/svn/kernel/dists/lenny/linux-2.6/debian debian fakeroot ./debian/rules debian/control dpkg-buildpackage -rfakeroot -uc -us -B -- dann frazier -- 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/20100312163559.ge22...@lackof.org
Bug#573490: Check kernel config during drbd8 builds
On Fri, Mar 12, 2010 at 04:52:46AM +, Ben Hutchings wrote:
This patch adds the config script to the package (as done in unstable)
and ensures that it runs at build time. Given this, you can adjust the
config script or the code to report a fatal error if it detects the
insecure connector API.
Thanks Ben, that works great.
My suggestion would then be to add a #warning message if built against
old headers, but allow it to complete anyway. My reasoning is that
we provide prebuilt binaries on lenny, and we can guarantee that those
binaries get fixed (by only signing good builds).
The only people building the modules directly are likely running some
self-maintained kernel. This kernel may or may not be keeping up with
security patches - that we can't control - but we can avoid a
regression in functionality. The drbd build is also currently free of
warnings, so this one should stick out.
Attached is a combined patch that implements this.
diff -u drbd8-8.0.14/debian/drbd8-source.drbd-Makefile drbd8-8.0.14/debian/drbd8-source.drbd-Makefile
--- drbd8-8.0.14/debian/drbd8-source.drbd-Makefile
+++ drbd8-8.0.14/debian/drbd8-source.drbd-Makefile
@@ -14,0 +15,9 @@
+# Automatically update config
+$(addprefix $(obj)/,$(drbd-objs)): $(obj)/linux/drbd_config.h
+$(obj)/linux/drbd_config.h: FORCE
+ $(Q)if [ $(obj) != $(src) ]; then \
+ mkdir -p $(@D) \
+ cp $(src)/linux/drbd_config.h $@; \
+ fi
+ cd $(obj) KDIR=$(objtree) $(src)/../scripts/adjust_drbd_config_h.sh
+.PHONY: FORCE
diff -u drbd8-8.0.14/debian/rules drbd8-8.0.14/debian/rules
--- drbd8-8.0.14/debian/rules
+++ drbd8-8.0.14/debian/rules
@@ -113,7 +113,8 @@
cp debian/drbd8-source.Makefile debian/$(PACKAGE)-source/usr/src/modules/drbd8/Makefile
cp debian/drbd8-source.drbd-Makefile debian/$(PACKAGE)-source/usr/src/modules/drbd8/drbd/Makefile
cp drbd/linux/drbd_config.h debian/$(PACKAGE)-source/usr/src/modules/drbd8
-# cp -a scripts/adjust_drbd_config_h.sh debian/$(PACKAGE)-source/usr/src/modules/drbd/scripts/
+ mkdir debian/$(PACKAGE)-source/usr/src/modules/drbd8/scripts
+ cp scripts/adjust_drbd_config_h.sh debian/$(PACKAGE)-source/usr/src/modules/drbd8/scripts/
# install debian/ files
mkdir -p debian/$(PACKAGE)-source/usr/src/modules/drbd8/debian/
diff -u drbd8-8.0.14/debian/changelog drbd8-8.0.14/debian/changelog
--- drbd8-8.0.14/debian/changelog
+++ drbd8-8.0.14/debian/changelog
@@ -1,3 +1,11 @@
+drbd8 (2:8.0.14-2+lenny1) stable-security; urgency=high
+
+ * Update for connector API change in linux-2.6_2.6.26-21lenny4
+(Closes: #573490)
+ * Restrict netlink calls to users with CAP_SYS_ADMIN (CVE Requested)
+
+ -- dann frazier da...@debian.org Thu, 11 Mar 2010 15:47:53 -0700
+
drbd8 (2:8.0.14-2) unstable; urgency=low
* Drop dpatch build-dependency.
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/drbd_nl.c
+++ drbd8-8.0.14/drbd/drbd_nl.c
@@ -1764,9 +1764,15 @@
};
+#ifdef KERNEL_HAS_CN_SKB_PARMS
+STATIC void drbd_connector_callback(struct cn_msg *req, struct netlink_skb_parms *nsp)
+{
+#else
+#warning Possible security issue. Please update your headers/kernel.
STATIC void drbd_connector_callback(void *data)
{
struct cn_msg *req = data;
+#endif
struct drbd_nl_cfg_req *nlp = (struct drbd_nl_cfg_req *)req-data;
struct cn_handler_struct *cm;
struct cn_msg *cn_reply;
@@ -1782,13 +1788,20 @@
return;
}
+#ifdef KERNEL_HAS_CN_SKB_PARMS
+ if (!cap_raised(nsp-eff_cap, CAP_SYS_ADMIN)) {
+ retcode = ERR_PERM;
+ goto fail;
+ }
+#endif
+
mdev = ensure_mdev(nlp);
if (!mdev) {
retcode = MinorNotKnown;
goto fail;
}
- TRACE(TraceTypeNl, TraceLvlSummary, nl_trace_packet(data););
+ TRACE(TraceTypeNl, TraceLvlSummary, nl_trace_packet(req););
if (nlp-packet_type = P_nl_after_last_packet) {
retcode = UnknownNetLinkPacket;
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/linux/drbd_config.h
+++ drbd8-8.0.14/drbd/linux/drbd_config.h
@@ -85,4 +85,8 @@
//#define NEED_SG_SET_BUF
#define HAVE_LINUX_SCATTERLIST_H
+/* In 2.6.32 we finally fixed connector to pass netlink_skb_parms to the callback
+ */
+#define KERNEL_HAS_CN_SKB_PARMS
+
#endif
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/linux/drbd.h
+++ drbd8-8.0.14/drbd/linux/drbd.h
@@ -140,6 +140,7 @@
CSUMSResyncRunning, /* DRBD 8.2 only */
VERIFYIsRunning, /* DRBD 8.2 only */
DataOfWrongCurrent,
+ ERR_PERM,
/* insert new ones above this line */
AfterLastRetCode
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/user/drbdsetup.c
+++ drbd8-8.0.14/user/drbdsetup.c
@@ -408,6 +408,7 @@
EM(ProtocolCRequired) = Protocol C required,
EM(VMallocFailed) = vmalloc() failed. Out of memory?,
EM(DataOfWrongCurrent) = Can only attach to the data we lost last (see kernel log).,
+ EM(ERR_PERM) = Permission denied. CAP_SYS_ADMIN necessary,
};
#define MAX_ERROR (sizeof(error_messages)/sizeof(*error_messages))
const char * error_to_string(int err_no)
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/scripts/adjust_drbd_config_h.sh
Bug#573490: drbd fails to load: drbd: disagrees about version of symbol cn_add_callback
On Thu, Mar 11, 2010 at 09:43:45PM +0100, Tomas Pospisek wrote: Package: linux-2.6 Version: 2.6.26-21lenny4 Severity: critical drbd fails to load and there goes my failover high available cluster... *t well, crap - we ignored that ABI change because google showed only an old/deprecated module as an out-of-tree user, but we obviously missed drbd. We'll work on an update to the drbd modules. -- 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/20100311213823.ga22...@lackof.org
Bug#524542: closed by dann frazier da...@debian.org (Bug#524542: fixed in linux-2.6 2.6.26-22)
On Thu, Mar 11, 2010 at 01:42:01PM -0800, Alok Kataria wrote: Hi Dann, Thanks for including this fix. Can you please let me know when will this kernel update be released ? I see this on the queue for proposed-updates, but no information about the release schedule is forthcoming from this link below. http://release.debian.org/proposed-updates/stable.html Some of our customers are hit by these TSC issues and will like to get a kernel build with the proper fixes for this issue. The 5.0.5 release has not been scheduled, though we aim for a stable point release about every two months. Until then, your customers are welcome to add proposed-updates to their sources.list. Builds for all other architectures should appear over the next several days. -- dann frazier -- 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/20100311222103.gb22...@lackof.org
Bug#573490: drbd fails to load: drbd: disagrees about version of symbol cn_add_callback
tags 573490 + patch
affects 573490 drbd8-source
thanks
On Thu, Mar 11, 2010 at 02:38:23PM -0700, dann frazier wrote:
On Thu, Mar 11, 2010 at 09:43:45PM +0100, Tomas Pospisek wrote:
Package: linux-2.6
Version: 2.6.26-21lenny4
Severity: critical
drbd fails to load and there goes my failover high available cluster...
*t
well, crap - we ignored that ABI change because google showed only an
old/deprecated module as an out-of-tree user, but we obviously missed
drbd. We'll work on an update to the drbd modules.
This patch builds for me, but I don't have a drbd setup. I'd
appreciate it if someone could test it :)
diff -u drbd8-8.0.14/debian/changelog drbd8-8.0.14/debian/changelog
--- drbd8-8.0.14/debian/changelog
+++ drbd8-8.0.14/debian/changelog
@@ -1,3 +1,10 @@
+drbd8 (2:8.0.14-2+lenny1) UNRELEASED; urgency=high
+
+ * Update for connector API change in linux-2.6_2.6.26-21lenny4
+ * Restrict netlink calls to users with CAP_SYS_ADMIN (CVE Requested)
+
+ -- dann frazier da...@debian.org Thu, 11 Mar 2010 15:47:53 -0700
+
drbd8 (2:8.0.14-2) unstable; urgency=low
* Drop dpatch build-dependency.
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/user/drbdsetup.c
+++ drbd8-8.0.14/user/drbdsetup.c
@@ -408,6 +408,7 @@
EM(ProtocolCRequired) = Protocol C required,
EM(VMallocFailed) = vmalloc() failed. Out of memory?,
EM(DataOfWrongCurrent) = Can only attach to the data we lost last (see kernel log).,
+ EM(ERR_PERM) = Permission denied. CAP_SYS_ADMIN necessary,
};
#define MAX_ERROR (sizeof(error_messages)/sizeof(*error_messages))
const char * error_to_string(int err_no)
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/drbd_nl.c
+++ drbd8-8.0.14/drbd/drbd_nl.c
@@ -1764,9 +1764,14 @@
};
+#ifdef KERNEL_HAS_CN_SKB_PARMS
+STATIC void drbd_connector_callback(struct cn_msg *req, struct netlink_skb_parms *nsp)
+{
+#else
STATIC void drbd_connector_callback(void *data)
{
struct cn_msg *req = data;
+#endif
struct drbd_nl_cfg_req *nlp = (struct drbd_nl_cfg_req *)req-data;
struct cn_handler_struct *cm;
struct cn_msg *cn_reply;
@@ -1782,13 +1787,20 @@
return;
}
+#ifdef KERNEL_HAS_CN_SKB_PARMS
+ if (!cap_raised(nsp-eff_cap, CAP_SYS_ADMIN)) {
+ retcode = ERR_PERM;
+ goto fail;
+ }
+#endif
+
mdev = ensure_mdev(nlp);
if (!mdev) {
retcode = MinorNotKnown;
goto fail;
}
- TRACE(TraceTypeNl, TraceLvlSummary, nl_trace_packet(data););
+ TRACE(TraceTypeNl, TraceLvlSummary, nl_trace_packet(req););
if (nlp-packet_type = P_nl_after_last_packet) {
retcode = UnknownNetLinkPacket;
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/linux/drbd_config.h
+++ drbd8-8.0.14/drbd/linux/drbd_config.h
@@ -85,4 +85,8 @@
//#define NEED_SG_SET_BUF
#define HAVE_LINUX_SCATTERLIST_H
+/* In 2.6.32 we finally fixed connector to pass netlink_skb_parms to the callback
+ */
+#define KERNEL_HAS_CN_SKB_PARMS
+
#endif
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/linux/drbd.h
+++ drbd8-8.0.14/drbd/linux/drbd.h
@@ -140,6 +140,7 @@
CSUMSResyncRunning, /* DRBD 8.2 only */
VERIFYIsRunning, /* DRBD 8.2 only */
DataOfWrongCurrent,
+ ERR_PERM,
/* insert new ones above this line */
AfterLastRetCode
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/scripts/adjust_drbd_config_h.sh
+++ drbd8-8.0.14/scripts/adjust_drbd_config_h.sh
@@ -104,6 +104,11 @@
have_linux_scatterlist_h=0
need_sg_set_buf=1
fi
+ if grep_q netlink_skb_parms $KDIR/include/linux/connector.h ; then
+have_netlink_skb_parms=1
+ else
+have_netlink_skb_parms=0
+ fi
else
# not a 2.6. kernel. just leave it alone...
exit 0
@@ -131,6 +136,8 @@
{ ( $need_sg_set_buf ? '' : '//' ) . \$1}e;
s{.*(#define HAVE_LINUX_SCATTERLIST_H.*)}
{ ( $have_linux_scatterlist_h ? '' : '//' ) . \$1}e;
+ s{.*(#define KERNEL_HAS_CN_SKB_PARMS.*)}
+ { ( $have_netlink_skb_parms ? '' : '//' ) . \$1}e;
\
./linux/drbd_config.h \
./linux/drbd_config.h.new
Bug#569704: potential fix
A coworker was seeing the same symptoms on a system from the same-era loaned me the system to debug. The issue ended up being due to a change in the SRAT table, and a backport of the following fixed it for me. I've committed it to the lenny branch - would you be able to test it? commit 4c31e92b97b6d7e7b19ee5e54a22571ffdebb305 Author: Yinghai Lu ying...@... Date: Wed Apr 22 14:19:27 2009 -0700 x86: check boundary in setup_node_bootmem() Commit dc09855 (x86/uv: fix init of memory-less nodes) causes a two sockets system (where node-1 doesn't have RAM installed) to crash. That commit makes node_possible include cpu nodes that do not have memory. So check boundary in setup_node_bootmem(). [ Impact: fix boot crash on RAM-less NUMA node system ] Signed-off-by: Yinghai Lu ying...@... Cc: Jack Steiner stei...@... LKML-Reference: 49ef89df.9090...@... Signed-off-by: Ingo Molnar mi...@... diff --git a/arch/x86/mm/numa_64.c b/arch/x86/mm/numa_64.c index d73aaa8..2d05a12 100644 --- a/arch/x86/mm/numa_64.c +++ b/arch/x86/mm/numa_64.c @@ -188,6 +188,9 @@ void __init setup_node_bootmem(int nodeid, unsigned long start, const int pgdat_size = roundup(sizeof(pg_data_t), PAGE_SIZE); int nid; + if (!end) + return; + start = roundup(start, ZONE_ALIGN); printk(KERN_INFO Bootmem setup node %d %016lx-%016lx\n, nodeid, -- 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/20100311070642.gc13...@ldl.fc.hp.com
Bug#570554: linux: /proc/pid/maps empty
On Tue, Mar 09, 2010 at 09:35:05PM +0100, Kurt Roeckx wrote: On Fri, Feb 19, 2010 at 12:45:08PM -0700, dann frazier wrote: On Fri, Feb 19, 2010 at 08:02:13PM +0100, maximilian attems wrote: On Fri, Feb 19, 2010 at 08:01:14PM +0100, Kurt Roeckx wrote: Source: linux-2.6 Version: 2.6.26-21lenny3 Hi, I'm seeing a regression test failure in elfutils because on some of the buildds /proc/pid/maps is empty. I have succesful logs and failed logs with 2.6.26-2-amd64, as reported by uname. But they're obviously not running the same version anymore. As far as I can see all the buildds I have a problem with run 2.6.26-21lenny3. yep this is reported as #569683 and should have severity important, not yet reviewed by dannf. ACK; I'll look at this soon. Any update on this? I currently can't get elfutils build because all the buildds and porter boxes for some arches run that kernel. I don't want to ignore the testsuite result because it's prevening uploads for arches that are not properly supported. Kernel is uploading as I type this :) The fix will be released via security in 2.6.26-21lenny4 and will also be available from proposed-updates as 2.6.26-22 (w/ additional changes). -- dann frazier -- 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/20100309214148.ga9...@lackof.org
Scheduling 2.6.26-22 (ABI++)
Based on IRC conversation, I'd like to upload a 2.6.26-22 to p-u this weekend. Since this adds a nic driver, it implies that we'll want to respin d-i for 5.0.5, so it is probably a good opportunity to merge in the abi breaker branch as it includes several fixes we've been sitting on for a while. -- dann frazier -- 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/20100305164723.ga24...@lackof.org
Bug#570552: FTBFS - dh_testroot: You must run this as root (or use fakeroot)
Source: tgt Version: 1:1.0.1-1 Severity: serious tgt runs dh_testroot in the build rule. I believe this violates section 4.9 of Debian Policy which states: The build target must not do anything that might require root privilege. Relevant piece of build log follows: [...] /usr/bin/make -C scripts clean make[2]: Entering directory `/build/buildd-tgt_1.0.1-1-hppa-dXx9ky/tgt-1.0.1/scripts' make[2]: Nothing to be done for `clean'. make[2]: Leaving directory `/build/buildd-tgt_1.0.1-1-hppa-dXx9ky/tgt-1.0.1/scripts' make[1]: Leaving directory `/build/buildd-tgt_1.0.1-1-hppa-dXx9ky/tgt-1.0.1' dh_clean debian/rules build dh_testdir dh_testroot dh_testroot: You must run this as root (or use fakeroot). make: *** [build-stamp] Error 255 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100219185910.gv12...@ldl.fc.hp.com
Bug#570554: linux: /proc/pid/maps empty
On Fri, Feb 19, 2010 at 08:02:13PM +0100, maximilian attems wrote: On Fri, Feb 19, 2010 at 08:01:14PM +0100, Kurt Roeckx wrote: Source: linux-2.6 Version: 2.6.26-21lenny3 Hi, I'm seeing a regression test failure in elfutils because on some of the buildds /proc/pid/maps is empty. I have succesful logs and failed logs with 2.6.26-2-amd64, as reported by uname. But they're obviously not running the same version anymore. As far as I can see all the buildds I have a problem with run 2.6.26-21lenny3. yep this is reported as #569683 and should have severity important, not yet reviewed by dannf. ACK; I'll look at this soon. -- dann frazier -- 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/20100219194508.ga17...@lackof.org
Bug#569704: linux-image-2.6.26-2-amd64: does not boot on HP DL385 G1
On Sun, Feb 14, 2010 at 08:27:17PM +0100, Tollef Fog Heen wrote: ]] dann frazier | On Sun, Feb 14, 2010 at 05:01:15PM +, Ben Hutchings wrote: | On Sat, 2010-02-13 at 17:00 +0100, Tollef Fog Heen wrote: | Package: linux-2.6 | Version: 2.6.26-21lenny3 | Severity: normal | | as per IRC conversation with Womble2, this kernel does not boot on a HP | DL385 G1. The only output I get is: | | Kernel alive | kernel direct mapping tables up to 1 @ 8000-d000 | PANIC: early exception 06 rip 10:805935b2 error 0 cr2 0 | | Not sure what other useful information I can provide about the system, | but I'll be happy to test a patch if you can provide one. | | I'm afraid I cannot find any obvously relevant changes. It would be | very helpful if you could check that this does not occur in 2.6.27 and | then bisect between 2.6.26 and 2.6.27 to find how it was fixed (note: in | this case you have to invert 'good' and 'bad'). However I understand | that this is a production machine and you are not likely to be able to | do this soon. | | I'll see if I can hunt one of these systems down... If you can't, I should be able to reproduce on one of the less-production ones I have access to, but I first need to get the iLO passwords. I found one, but it booted fine: Booting 'Debian GNU/Linux, kernel 2.6.26-2-amd64 Default' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz root=/dev/cciss/c0d0p1 ro console=ttyS0 115200n8 [Linux-bzImage, setup=0x3000, size=0x1a9870] initrd /boot/initrd.img [Linux-initrd @ 0x7fac4000, 0x52bb89 bytes] savedefault Probing EDD (edd=off to disable)... ok [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-2-amd64 (Debian 2.6.26-21lenny3) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Thu Feb 11 00:59:32 UTC 2010 [0.00] Command line: root=/dev/cciss/c0d0p1 ro console=ttyS0 115200n8 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f400 (usable) [0.00] BIOS-e820: 0009f400 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - f57f8000 (usable) [0.00] BIOS-e820: f57f8000 - f580 (ACPI data) [...] This reports BIOS version A05, released 03/01/2006. What BIOS are you running? -- dann frazier -- 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/20100216155324.gm28...@lackof.org
Bug#569704: linux-image-2.6.26-2-amd64: does not boot on HP DL385 G1
On Sun, Feb 14, 2010 at 05:01:15PM +, Ben Hutchings wrote: On Sat, 2010-02-13 at 17:00 +0100, Tollef Fog Heen wrote: Package: linux-2.6 Version: 2.6.26-21lenny3 Severity: normal as per IRC conversation with Womble2, this kernel does not boot on a HP DL385 G1. The only output I get is: Kernel alive kernel direct mapping tables up to 1 @ 8000-d000 PANIC: early exception 06 rip 10:805935b2 error 0 cr2 0 Not sure what other useful information I can provide about the system, but I'll be happy to test a patch if you can provide one. I'm afraid I cannot find any obvously relevant changes. It would be very helpful if you could check that this does not occur in 2.6.27 and then bisect between 2.6.26 and 2.6.27 to find how it was fixed (note: in this case you have to invert 'good' and 'bad'). However I understand that this is a production machine and you are not likely to be able to do this soon. I'll see if I can hunt one of these systems down... -- dann frazier -- 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/20100214190654.gj28...@lackof.org
Bug#569704: linux-image-2.6.26-2-amd64: does not boot on HP DL385 G1
On Sat, Feb 13, 2010 at 05:00:59PM +0100, Tollef Fog Heen wrote: Package: linux-2.6 Version: 2.6.26-21lenny3 Severity: normal as per IRC conversation with Womble2, this kernel does not boot on a HP DL385 G1. The only output I get is: Kernel alive kernel direct mapping tables up to 1 @ 8000-d000 PANIC: early exception 06 rip 10:805935b2 error 0 cr2 0 Not sure what other useful information I can provide about the system, but I'll be happy to test a patch if you can provide one. Is this a regression from a previous release - if so, which release worked previously? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
debian's openvz CVE-2010-0307
hey Vitaliy/Ola,
The fixes for CVE-2010-0307 remove the TIF_ABI_PENDING bit from
arch-specific code. Since this #define no longer exists, our openvz
patch needs to be updated to not reference it.
It looks as though openvz only references to clear all arch-specific
flags, so I prepared the following fix. Please let me know if you see
any problem with it.
This applies after the following list of commits:
- 221af7f87 (Split 'flush_old_exec' into two functions)
- 05d43ed8a (x86: get rid of the insane TIF_ABI_PENDING bit)
- 7ab02af42 (Fix 'flush_old_exec()/setup_new_exec()' split)
- 94f28da84 (powerpc: TIF_ABI_PENDING bit removal)
diff -urpN a/kernel/cpt/cpt_process.c b/kernel/cpt/cpt_process.c
--- a/kernel/cpt/cpt_process.c 2010-02-09 12:02:40.0 -0700
+++ b/kernel/cpt/cpt_process.c 2010-02-09 12:13:10.0 -0700
@@ -941,7 +941,7 @@ static int dump_one_process(cpt_object_t
v-cpt_64bit = 0;
#ifdef CONFIG_X86_64
/* Clear x86_64 specific flags */
- v-cpt_thrflags = ~(_TIF_FORK|_TIF_ABI_PENDING|_TIF_IA32);
+ v-cpt_thrflags = ~(_TIF_FORK|_TIF_IA32);
if (!(task_thread_info(tsk)-flags _TIF_IA32)) {
ctx-tasks64++;
v-cpt_64bit = 1;
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian's openvz CVE-2010-0307
On Tue, Feb 09, 2010 at 08:45:53PM +0100, Ola Lundqvist wrote: Hi Dann What was TIF_ABI_PENDING defined to earlier? I assume this is not a problem, however Vitaliy knows this in much more details so I want him to look at this as well. Take a look at this change for the details: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=05d43ed8a -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Please reject linux-2.6 2.6.32-7
On Fri, Feb 05, 2010 at 05:25:43PM +0100, Alexander Reichle-Schmehl wrote: Alexander Reichle-Schmehl wrote: Okay, I just rejected linux-2.6_2.6.32-7_alpha.changes, linux-2.6_2.6.32-7_hppa.changes, linux-2.6_2.6.32-7_i386.changes, linux-2.6_2.6.32-7_ia64.changes and linux-2.6_2.6.32-7_s390.changes. linux-2.6_2.6.32-7_sparc.changes rejected, too. Best regards, Alexander thanks! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Please reject linux-2.6 2.6.32-7
On Thu, Feb 04, 2010 at 08:22:32AM +, Ben Hutchings wrote: linux-2.6 version 2.6.32-7 includes an incomplete bug fix that will result in failure to boot 32-bit userland on a 64-bit kernel. 2.6.32-8 will have the complete bug fix. Looks like the amd64 build has been approved - can we avoid accepting the other archs? i386, in particular, will cause a lot of problems. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568416: 64-bit kernel/32-bit userland boot failure
Source: linux-2.6 Version: 2.6.32-7 Severity: grave This release is known to cause boot problems on 32-bit systems w/ a 64-bit kernel: http://article.gmane.org/gmane.linux.kernel/946249 -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568457: FTBFS [powerpc] - format '%x' expects type 'unsigned int'
Source: linux-2.6 Version: 2.6.32-7 Severity: serious I tried to do a local build of trunk on powerpc, and hit the following bug (apparently introduced in 2.6.32-7): cc1: warnings being treated as errors /tmp/buildd/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/time.c: In function 'register_decrementer_clockevent': /tmp/buildd/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/time.c:922: error: format '%x' expects type 'unsigned int', but argument 3 has type 'long unsigned int' -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563847: Please enable the f-trace tracers
On Tue, Jan 05, 2010 at 12:53:23PM -0700, Troy Heber wrote: Source: linux-2.6 Version: 2.6.32-3 Severity: wishlist Currently Ftrace is enabled in the kernel, CONFIG_FTRACE=y and CONFIG_DYNAMIC_FTRACE=y. However, some the most useful tracers, such as CONFIG_FUNCTION_TRACER and CONFIG_STACK_TRACER, are disabled. For example: CONFIG_FTRACE=y # CONFIG_FUNCTION_TRACER is not set # CONFIG_IRQSOFF_TRACER is not set # CONFIG_SYSPROF_TRACER is not set # CONFIG_SCHED_TRACER is not set # CONFIG_FTRACE_SYSCALLS is not set ... # CONFIG_POWER_TRACER is not set # CONFIG_STACK_TRACER is not set Since Dynamic Ftrace is already enabled, I can't think of down side to enabling the actual tracers. Please consider this a wishlist request to enabled them. Of FUNCTION_TRACER, Kconfig says: If it's runtime disabled (the bootup default), then the overhead of the instructions is very small and not measurable even in micro-benchmarks. And for STACK_TRACER: If this is configured with DYNAMIC_FTRACE then it will not have any overhead while the stack tracer is disabled. So I've gone ahead and enabled them in svn. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
On Thu, Jan 28, 2010 at 10:50:16PM +, Ben Hutchings wrote: On Mon, 2010-01-25 at 20:19 +0100, Andreas Barth wrote: * Ben Hutchings (b...@decadent.org.uk) [100125 20:14]: On Mon, Jan 25, 2010 at 08:02:31PM +0100, Andreas Barth wrote: * Julien Cristau (jcris...@debian.org) [100125 19:27]: On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote: I guess this means that the next version is no candidate for the release unless it gets a stable ABI (versioning) and should block the kernel from migrating for the time being? The 2.6.30 kernel and the current 2.6.32 one aren't candidates either, so I'm not sure what difference blocking the next one makes. That our testing users don't have to life with strange error messages they wouldn't get if the abi would be bumped properly. OK, maybe we should start numbering ABIs with this next version. I'd appreciate that very much. There has been some argument over whether we should do this or not. Bastian and Max seem to think that many more ABI-changing config changes will still be needed seems likely and do not want to start numbering yet. I'm not convinced that changing the ABI number repeatedly in testing/unstable will even hurt that much since we no longer have to worry about dependent module packages in the archive. It may add to cruft on users' systems but this can be fixed after a reboot with 'apt-get autoremove'. yeah, i think people running sid/testing who do use oot modules shouldn't have much problem w/ frequent module rebuilds - esp if the abi is silently changing and they may really need to rebuild anyway. [Like with a module on my mythbox recently :)] I do want to see this argument resolved before building and uploading, but I also don't want to hold back security and stability fixes. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566057: hostap: hostap_main.c prism2.5 error. Squeeze.
Please try 2.6.32. 2.6.32 is in sid and can be installed on squeeze systems. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562525: linux-2.6: [s390] Etch proposed-updates kernel boot failure
On Wed, Jan 06, 2010 at 02:22:37PM -0700, dann frazier wrote: On Mon, Jan 04, 2010 at 01:12:56AM +0100, Frans Pop wrote: On Sunday 03 January 2010, dann frazier wrote: Thanks. This suggests that the fixes for CVE-2009-0029 are causal. To verify, can you test this kernel which drops only those fixes? zelenka.debian.org:~dannf/linux-headers-2.6.18-6-s390_2.6.18.dfsg.1-26et ch1+nocve20090029_s390.deb s/headers/image/ :-) Linux version 2.6.18-6-s390 (Debian 2.6.18.dfsg.1-26etch1+nocve20090029) [...] mordor login: Just an fyi, I've installed a hercules setup and can reproduce this. I'll use that to try find a fix. This fixes the issue for me, can you verify? zelenka.debian.org:~dannf/linux-image-2.6.18-6-s390_2.6.18.dfsg.1-27~562525.testfix.1_s390.deb -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kernel audit code bugs in Debian stable
On Fri, Dec 25, 2009 at 04:55:59PM +0300, Sergey Sireskin wrote: Hi All, I would like to report, that current Debian 2.6.26-2 kernel packages are unstable (soft and hard locks occur) when intensively using audit features. There are already fixes by Eric Paris and Al Viro for these bugs in mainline kernel. These patches should be included in Debian kernels as well. Otherwise Debian kernels are competely useless in cases when audit system is enabled and audit.rules are configured. The following patch commits have to be included: def57543418a5f47debae28a0a9dea2effc11692 8f7b0ba1c853919b85b54774775f567f30006107 As well as these two patches on top of them: http://www.gossamer-threads.com/lists/linux/kernel/1169784 http://www.gossamer-threads.com/lists/linux/kernel/1169785 Thanks Sergey. Would you mind filing a bug for these so it can be tracked? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562525: linux-2.6: [s390] Etch proposed-updates kernel boot failure
On Mon, Jan 04, 2010 at 01:12:56AM +0100, Frans Pop wrote: On Sunday 03 January 2010, dann frazier wrote: Thanks. This suggests that the fixes for CVE-2009-0029 are causal. To verify, can you test this kernel which drops only those fixes? zelenka.debian.org:~dannf/linux-headers-2.6.18-6-s390_2.6.18.dfsg.1-26et ch1+nocve20090029_s390.deb s/headers/image/ :-) Linux version 2.6.18-6-s390 (Debian 2.6.18.dfsg.1-26etch1+nocve20090029) [...] mordor login: Just an fyi, I've installed a hercules setup and can reproduce this. I'll use that to try find a fix. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562525: linux-2.6: [s390] Etch proposed-updates kernel boot failure
On Sat, Jan 02, 2010 at 11:19:41PM +0100, Frans Pop wrote: On Saturday 02 January 2010, you wrote: Can you try: zelenka.debian.org:~dannf/linux-image-2.6.18-6-s390_2.6.18.dfsg.1-26etch 1+div64_s390.deb Linux version 2.6.18-6-s390 (Debian 2.6.18.dfsg.1-26etch1+div64) [...] Failed to execute /init Kernel panic - not syncing: No init found. Try passing init= option to kernel. If that *doesn't* work, can you then try: zelenka.debian.org:~dannf/linux-image-2.6.18-6-s390_2.6.18.dfsg.1-24+cve 20090029_s390.deb Linux version 2.6.18-6-s390 (Debian 2.6.18.dfsg.1-24+cve20090029) Failed to execute /init Kernel panic - not syncing: No init found. Try passing init= option to kernel. Thanks. This suggests that the fixes for CVE-2009-0029 are causal. To verify, can you test this kernel which drops only those fixes? zelenka.debian.org:~dannf/linux-headers-2.6.18-6-s390_2.6.18.dfsg.1-26etch1+nocve20090029_s390.deb -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562525: linux-2.6: [s390] Etch proposed-updates kernel boot failure
On Wed, Dec 30, 2009 at 12:04:00AM +0100, Frans Pop wrote: On Tuesday 29 December 2009, dann frazier wrote: I don't see an obvious cause for the failure. Can you try booting 24etch1 in an effort to bisect the failure? In case you can't find the deb (I couldn't) I've built one that you can find in my home directory on zelenka.debian.org. Linux version 2.6.18-6-s390 (Debian 2.6.18.dfsg.1-24etch1) (da...@debian.org) [...] [...] Freeing unused kernel memory: 100k freed Failed to execute /init Kernel panic - not syncing: No init found. Try passing init= option to kernel. There's a suspicious similarity to [1] maybe? I won't be able to compile any kernels myself on this one, but I can test what you build. Appreciated. Can you try: zelenka.debian.org:~dannf/linux-image-2.6.18-6-s390_2.6.18.dfsg.1-26etch1+div64_s390.deb If that *doesn't* work, can you then try: zelenka.debian.org:~dannf/linux-image-2.6.18-6-s390_2.6.18.dfsg.1-24+cve20090029_s390.deb -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: scheduling 2.6.26-21
On Wed, Nov 25, 2009 at 01:32:01PM -0700, dann frazier wrote: On Tue, Nov 24, 2009 at 02:02:25PM -0700, dann frazier wrote: We have several pending changes, plus we need to merge in the latest DSAs. I'll plan on uploading tomorrow, so let me know if you have any changes pending that might need more time. The p-u processing isn't working at the moment, and there's no real point in uploading until it is - so I'm postponing.. p-u processing is going again, albeit manually, so I'd like to reschedule this for tomorrow. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Uploading kernel packages to unstable
On Thu, Dec 24, 2009 at 03:44:54AM +, Ben Hutchings wrote: I would like to upload linux-2.6 tomorrow, fixing the build failure on ia64 and a couple of security bugs. There should be no new binary packages. Any objections? (Dan, do you have vserver ready to add?) Yes, I do. I'll go ahead and commit it. If you do want to avoid new binary packages, feel free to revert before uploading. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550898: DASD DIAG driver doesn't work for read-only minidisks (s390, s390x only)
On Thu, Dec 17, 2009 at 11:01:40AM -0500, Stephen Powell wrote: An official fix has now been published for this problem by upstream development for kernel 2.6.33. See http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=22825ab7693fd29769518a0d25ba43c01a50092a Please consider backporting it to 2.6.32 so that when Squeeze freezes, this fix will be included. Also please consider backporting it to 2.6.26 (Lenny) in the next stable point release I'll look into the lenny backport. or in a security update. Suse considered this fix important enough to backport it to 2.6.27 (SLES11) and 2.6.16 (SLES10). (See http://lists.debian.org/debian-s390/2009/12/msg00013.html) For the security argument, please see http://lists.debian.org/debian-s390/2009/12/msg00025.html. I don't think this is should be considered a security problem. This posting also contains a link to my unofficial backport of the fix to 2.6.26. As the author, I hereby grant permission to anyone to use it for any purpose whatsoever. Or, if you prefer, you can do your own backport. I will try to get upstream to include the patch in one of their stable updates for 2.6.32 as well, but it would help if I had some allies at Debian. That's definitely the right approach for 2.6.32/squeeze thanks. If stable@ rejects it, please let us know. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561332: Vfork bug on hppa = FTBS emacs 23
On Wed, Dec 16, 2009 at 12:14:05PM +0100, Bastian Blank wrote: severity 561332 important tags 561332 moreinfo thanks On Wed, Dec 16, 2009 at 11:40:42AM +0100, Bastien ROUCARIES wrote: Package: linux-2.6 Please use reportbug to add proper information from the machine in question. severity: serious hppa is no release architecture. Last I heard it was.. http://lists.debian.org/debian-devel-announce/2009/10/msg0.html And the buildd stability problems have been resolved since. This bug block emacs since one month. Please correct. See http://article.gmane.org/gmane.linux.ports.parisc/2403 for a testcase. This testcase emits warnings and works after been fixed on paer. Bastian -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561332: Vfork bug on hppa = FTBS emacs 23
On Wed, Dec 16, 2009 at 04:45:52PM +0100, Bastian Blank wrote: On Wed, Dec 16, 2009 at 04:15:53PM +0100, Bastien ROUCARIES wrote: On Wed, Dec 16, 2009 at 12:14 PM, Bastian Blank wa...@debian.org wrote: On Wed, Dec 16, 2009 at 11:40:42AM +0100, Bastien ROUCARIES wrote: Package: linux-2.6 Please use reportbug to add proper information from the machine in question. I have not the machine, I have just forwarded a FTBS bug from emacs package likely due to a kernel bug. The provided information is incomplete. If you are not able to provide the necessary information, reportbug is instructed to gather them, then try to find someone that can. The buildds were running a 2.6.31/parisc64 kernel from the Debian archive. These buildds are now running 2.6.32-1, so I'll retry a build to confirm that this problem still persists. This bug block emacs since one month. Please correct. See http://article.gmane.org/gmane.linux.ports.parisc/2403 for a testcase. They are another information on http://article.gmane.org/gmane.linux.ports.parisc/2402 This looks like a different problem. fyi, the hppa porters can reproduce and are actively looking into this problem. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Uploading kernel packages to unstable
On Wed, Dec 16, 2009 at 05:54:29PM +, Ben Hutchings wrote: I intend to upload linux-2.6, linux-latest-2.6 and firmware-nonfree tonight. There should be no new binary packages for linux-2.6. Any objections? No objections here. Micah and I have been working w/ vserver upstream and have a patch ready for 2.6.32. Of course, that means new binary packages, so if we want to avoid NEW processing I can hold off on committing... -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Uploading kernel packages to unstable
On Wed, Dec 16, 2009 at 06:30:21PM +, Ben Hutchings wrote: On Wed, Dec 16, 2009 at 11:10:15AM -0700, dann frazier wrote: On Wed, Dec 16, 2009 at 05:54:29PM +, Ben Hutchings wrote: I intend to upload linux-2.6, linux-latest-2.6 and firmware-nonfree tonight. There should be no new binary packages for linux-2.6. Any objections? No objections here. Micah and I have been working w/ vserver upstream and have a patch ready for 2.6.32. Of course, that means new binary packages, so if we want to avoid NEW processing I can hold off on committing... Can you hold that back for the next upload (hopefully with a stable ABI and therefore changing all package names)? Sure. I'll build some packages out-of-band so micah et. al. can get going on some testing in the meantime. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561332: emacs23 has built
After upgrading the buildds to 2.6.32, emacs23 builds fine. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: using the zoom slider on Microsoft keyboard
On Tue, Dec 08, 2009 at 05:07:15PM +0100, Richard KLINDA wrote: The Microsoft Natural Ergonomic Keyboard 4000 has a zoom slide at the center of the keyboard. Here is a picture: http://pcworld.hu/apix/0707/natural.jpg Unfortunately the program xev doesn't report this button upon pressing it, so it is unusuable under X. But there is a trivial patch floating around, that makes this button (actually, it is two buttons, up and down) usable: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264287 (a search for the word KEY_ZOOMIN will get you to the actual patch on the page). Would it be possible, to incorporate this patch into Debian's official kernel? If that workaround gets accepted upstream, then we can likely backport it. See: http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines But it sounds like the real issue here maybe with X? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: uploading 2.6.32-1
On Sat, Dec 05, 2009 at 04:48:59PM +0100, Bastian Blank wrote: On Thu, Dec 03, 2009 at 10:04:52PM -0700, dann frazier wrote: There's some security issues fixed in 2.6.32, so I'd like to see us upload 2.6.32-1 relatively soon. How about an upload tomorrow? Okay, lets do this with an ABINAME of trunk and without stable ABI. Ok, I'll start preparing an upload using: http://people.debian.org/~dannf/linux-2.6_2.6.30.orig.tar.gz Please poke me on IRC if you need me to abort/delay. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: uploading 2.6.32-1
On Sun, Dec 06, 2009 at 09:51:12AM -0700, dann frazier wrote: On Sat, Dec 05, 2009 at 04:48:59PM +0100, Bastian Blank wrote: On Thu, Dec 03, 2009 at 10:04:52PM -0700, dann frazier wrote: There's some security issues fixed in 2.6.32, so I'd like to see us upload 2.6.32-1 relatively soon. How about an upload tomorrow? Okay, lets do this with an ABINAME of trunk and without stable ABI. Ok, I'll start preparing an upload using: http://people.debian.org/~dannf/linux-2.6_2.6.30.orig.tar.gz Oops - uploaded wrong one, but looks like waldi is taking it over so I'll just blow away my .32 orig. Please poke me on IRC if you need me to abort/delay. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559202: squeeze: freeze on shutdown, hibernate, suspend
On Thu, Dec 03, 2009 at 03:19:27PM +0100, Florian Marienfeld wrote: That works! I need my old little tweaks to make suspend work (other video-quirks and a hook that kills the hung vbetool), but thats as good as before. I am now compiling 2.6.32rc in squeeze, would that be the way to go, if it worked? You can install the deb directly from sid, no need to recompile. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
uploading 2.6.32-1
hey, There's some security issues fixed in 2.6.32, so I'd like to see us upload 2.6.32-1 relatively soon. How about an upload tomorrow? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559202: squeeze: freeze on shutdown, hibernate, suspend
On Wed, Dec 02, 2009 at 07:28:28PM +0100, Florian Marienfeld wrote: Package: linux-image-2.6-686 Version: 2.6.30+21 Severity: normal Hi, I run squeeze on an acer travelmate 4002. shutdown, hibernate, and suspend don't work. Shutdown says will now halt and spins down the disk, but then task halt was blocked for more than 120 seconds. For suspend/hibernate pm-suspend.log ends with performing suspend/performing hibernate but the screen never powers down. when hibernating I can still move to ttys but not type into them, switching to tty7 freezes the system. suspend freezes right away. the only way out is a hard shutdown in either case. This is probably a kernel issue (2.6.30) as Ubuntu on the same machine started behaving the same way after upgrading the kernel from 2.6.28 to 2.6.31. Following a hint I tried giving grub the kernel parameter pci=nomsi. no effect. I also compiled a vanilla 2.6.31 kernel. no effect. Please test the 2.6.32-rc8 in sid and let us know the results. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559064: new pciid for hpilo
Package: linux-2.6
Version: 2.6.26-20
Severity: important
Tags: lenny
This change from upstream simply adds a new pci id (well, and revs the
module version - I'll probably use 0.06lenny1 instead of 1.0 though).
Author: David Altobelli david.altobe...@hp.com
Date: Fri Feb 27 14:03:09 2009 -0800
hpilo: new pci device
Future iLO devices will have an HP vendor id.
Signed-off-by: David Altobelli david.altobe...@hp.com
Signed-off-by: Andrew Morton a...@linux-foundation.org
Signed-off-by: Linus Torvalds torva...@linux-foundation.org
diff --git a/drivers/misc/hpilo.c b/drivers/misc/hpilo.c
index f26667a..cf99185 100644
--- a/drivers/misc/hpilo.c
+++ b/drivers/misc/hpilo.c
@@ -710,6 +710,7 @@ out:
static struct pci_device_id ilo_devices[] = {
{ PCI_DEVICE(PCI_VENDOR_ID_COMPAQ, 0xB204) },
+ { PCI_DEVICE(PCI_VENDOR_ID_HP, 0x3307) },
{ }
};
MODULE_DEVICE_TABLE(pci, ilo_devices);
@@ -758,7 +759,7 @@ static void __exit ilo_exit(void)
class_destroy(ilo_class);
}
-MODULE_VERSION(0.06);
+MODULE_VERSION(1.0);
MODULE_ALIAS(ILO_NAME);
MODULE_DESCRIPTION(ILO_NAME);
MODULE_AUTHOR(David Altobelli david.altobe...@hp.com);
--
dann frazier
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?
On Tue, Dec 01, 2009 at 11:27:59PM +0530, Mohan R wrote: Package: linux-headers-2.6.26-2-amd64 Severity: minor Hi, A newcommer to Debian, forgive me if I do any mistakes, I'm trying to compile broadcom-sta following http://wiki.debian.org/wl wiki page. While installing linux-headers-2.6.26-2-amd64, I noticed that it depends on gcc-4.1, but when I installed 'gcc' package, aptitude installed 'gcc-4.3'. gcc-4.1 is provided in the gcc-4.1 package. Is gcc-4.1 desperately needed for this package? I don't recall the details... can't we change the dependency to accept = gcc-4.1? As far as Debian is concerned, its not a bug to use a compiler still available in the distribution. It can be a wishlist bug if a package doesn't work w/ a newer compiler, but it won't be a candidate for a stable release. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?
reassign 559069 linux-2.6 thanks On Wed, Dec 02, 2009 at 11:46:15AM +0530, Mohan R wrote: package linux-headers-2.6.26-2-amd64 severity 559069 wishlist thanks dann frazier wrote: As far as Debian is concerned, its not a bug to use a compiler still available in the distribution. It can be a wishlist bug if a package doesn't work w/ a newer compiler, but it won't be a candidate for a stable release. I just concerned about the conflicts if I install two version of gcc. Installing gcc-4.1(with its dependencies) just for linux-headers-2.6.26.2-amd64 package seems waste of bandwidth and storage. Because I already installed 'gcc-4.3' and its working smoothly. Sorry, this won't happen in a stable release - saving space on a development system isn't sufficient reason to break stable systems or make kernel packages unbuildable. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: scheduling 2.6.26-21
On Tue, Nov 24, 2009 at 02:02:25PM -0700, dann frazier wrote: We have several pending changes, plus we need to merge in the latest DSAs. I'll plan on uploading tomorrow, so let me know if you have any changes pending that might need more time. The p-u processing isn't working at the moment, and there's no real point in uploading until it is - so I'm postponing.. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
scheduling 2.6.26-21
We have several pending changes, plus we need to merge in the latest DSAs. I'll plan on uploading tomorrow, so let me know if you have any changes pending that might need more time. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522922: regression tests
The igb driver in stable currently supports these device: #define E1000_DEV_ID_82575EB_COPPER 0x10A7 #define E1000_DEV_ID_82575EB_FIBER_SERDES 0x10A9 #define E1000_DEV_ID_82575GB_QUAD_COPPER 0x10D6 I obtained access to cards containing the first two chips[1] and did some basic testing (discovery/dhcp/ssh connections). All ports worked fine using both the current kernel in stable and with Ben's patch. I don't see any changes in the patch that would affect the 82575GB_COPPER that don't apply to the 82575EB_COPPER. I'll have access to these cards for a while, so I can run any additional tests upon request. Ben: are you ok with me applying this to stable? [1] 2 copper cards (single port/dual port), 1 fiber (dual port) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: /proc/acpi/event in backported kernel
On Fri, Nov 20, 2009 at 05:13:48PM +0100, Kiss Gabor (Bitman) wrote: Dear folks, I've just realized that backported lenny kernel linux-image-2.6.30-bpo.2-686 (2.6.30-8~bpo50+1) does not have /proc/acpi/event. However /usr/sbin/acpid definitely requires it. (1.0.8-1lenny1) Package maintaner of linux-image-2.6.30-bpo.2-686 is Debian Kernel Team debian-kernel@lists.debian.org The kernel team does not maintain the kernel in backports.org. You can use the sid/squeeze binaries directly on lenny though. So who could reenable CONFIG_ACPI_PROC_EVENT? See #516079. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538372: linux-libc-dev-2.6.26_20
On Wed, Nov 11, 2009 at 12:01:00PM +0100, Helge Bahmann wrote: The change to /usr/include/linux/socket.h introduced in linux-libc-dev 2.6.26 (from proposed-updates) now breaks the following simple test program: #include stddef.h #include linux/socket.h #include linux/netlink.h Several autoconf-scripts (notably strace) try to compile this program to detect linux/netlink.h and consequently fail. Please revert the change that remove the sub-includes from linux/socket.h Thanks for testing! Does anyone have an alternate fix, or should we just revert this for now? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555531: linux-image-2.6.26-2-amd64: sound not working in OSS games after update
On Tue, Nov 10, 2009 at 12:16:19AM -0800, Brandon Del Bel wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-19lenny2 Severity: normal After the latest kernel update, sound no longer works in tyr-quake or other id engine games. I have 'tyr-quake 0 0 disable direct' in /proc/asound/card0/pcm0p/oss. It was working the day before I updated. Can you revert to the 2.6.26-19lenny1 kernel and retest? I don't see anything new in 19lenny2 that could obviously break this. It would also be useful to verify w/o the nvidia driver loaded, if possible. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
On Tue, Nov 10, 2009 at 01:15:40AM -0600, Karl O. Pinc wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal Hello, I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2 with the latest security update and I found my system would hang during the boot. By 'hang' I mean that the boot process seems to stop -- no further messages on the console and the network never came up. Would you be able to test the 2.6.26-19lenny1 kernel to verify that it did work? I don't see anything in 2.6.26-19lenny2 that could obviously cause this, so it would be good to confirm that we're looking in the right place. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Request to Join Project kernel
On Tue, Nov 03, 2009 at 11:02:07PM +, nore...@alioth.debian.org wrote: I would like to help the kernel team. I usually try out kernels as soon as they are built, and have several machines on which to try them with various hardware. I've noticed that builds have recently stopped of newer kernels and hope I could help out with that. Thanks for the offer and the testing, but builds are done automatically by the buildd infrastructure, not by the kernel team. The issues w/ 2.6.31 should be worked out soon. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: No new builds?
On Tue, Nov 03, 2009 at 04:05:32PM -0600, Wes Keene wrote: I've noticed recently that ftp.debian.org no longer produces new kernel deb's. I do use these to get newer kernel features, but I'm fine with the latest 2.6.30.8 for now. Is there any particular reason this is happening? I realize the kernel team is quite busy and it's also quite a tight group of folks, however, if there is any room to help out, I'm more than willing. This is due to ongoing changes in the archive, preventing processing of the new queue for the time being. You'll see that 2.6.31 is in sid, but only the amd64 build until these changes are completed. You can always do your own build from the source in the archive, or from what is in svn. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515741: please test p-u kernel
On Sun, Nov 01, 2009 at 04:37:06PM +0100, amuel...@targz.de wrote: hey, after 5 days of testing we got no further error messages and system did not hang. So I assume that the bug is fixed. (used your testkernel) Thanks in Advance! Great, thanks for the verification. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515741: please test p-u kernel
There is a potential fix for this issue in the 2.6.26-20 kernel in proposed-updates. Can someone who has seen this issue please verify the fix? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFC: Bug handling policy
ask the submitter to report it
upstream at bugzilla.kernel.org under a specific Product and Component,
and to tell us the upstream bug number. We do not report bugs directly
because follow-up questions from upstream need to go to the submitter,
not to us. Given the upstream bug number, we mark the bug as forwarded.
bts-link then updates its status.
We tried to capture a lot of the common user-triage processes here:
http://wiki.debian.org/DebianKernelReportingBugs
Maybe we could update that/reference it in this doc?
6. Keeping bugs separate
Many submitters search for a characteristic error message and treat this
as indicating a specific bug. This can lead to many 'me too' follow-ups
where, for example, the message indicates a driver bug and the second
submitter is using a different driver from the original submitter. We
should try to respond to such a follow-up quickly, requesting a separate
bug report. Otherwise the original report is likely to turn into a mess
of conflicting information about two or more different bugs.
Where the original report describes more than one bug ('...and other
thing...'), we should clone it and deal with each separately.
It might be valuable to just close any bugs that have gotten
confusing overtime and clone a new bug for each *real* issue described
within, with a good explanation that helps prevent confusion.
JUST BECAUSE YOU ARE SEEING A SOFT LOCKUP DOES NOT MEAN THIS IS YOUR
BUG.
7. Applying patches
Patches should normally be reviewed and accepted by the relevant
upstream maintainer (aside from necessary adjustments for an older
kernel version) before being applied.
8. Talking to submitters
nice section.
We should always be polite to submitters. Not only is this implied by
the Social Contract, but it is likely to lead to a faster resolution of
the bug. If a submitter overrated the severity, quietly downgrade
it.
Or downgrade it w/ a pointer to this document, so it is clearly not personal.
If a submitter has done something stupid, request that they undo that
and report back. 'Sorry', and 'please' make a big difference in tone.
--
dann frazier
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542250: Xen amd64 image for 2.6.26-20
On Mon, Oct 26, 2009 at 11:07:25AM +, Marc Warne wrote: I notice that 2.6.26-20 is now available in the Debian FTP archive, but can't find a Xen amd64 image there (although there is a Xen 686 image). Is this an omission, coming soon or can I just not find it? It will be there as soon as it gets built, signed and uploaded. As far as I can tell, #542250 affects amd64 as well as i386/i686. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: 2.6.29 Kernel, Lenny backports
On Mon, Oct 26, 2009 at 09:04:04PM +, Steve Gane wrote: Hello, I'm trying to use the linux-headers-2.6.29-bpo.2-686 package from Lenny/backports, but aptitude says it depends on linux-kbuild-2.6.29, which is not available in Lenny, or Lenny backports, or Squeeze. I don't know if any of the backports.org people monitor this list - you might try contacting them directly. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552422: linux-2.6 2.6.31-1 FTBFS on mipsel
On Mon, Oct 26, 2009 at 11:03:27AM +0100, Aurelien Jarno wrote:
Martin Michlmayr a écrit :
* Andreas Barth a...@not.so.argh.org [2009-10-26 07:22]:
Package: linux-2.6
Version: 2.6.31-1
Severity: serious
this package FTBFS on mipsel:
MODPOST vmlinux.o
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
ld:arch/mips/kernel/vmlinux.lds:168: syntax error
Aurelien, can you take a look at this?
I'll try to have a look, but I don't know when. There are plenty of RC
bugs on eglibc to fix first.
Could it be this? I don't have hardware to test.
commit d71789b6fa37c21ce5eb588d279f57904a62e7e2
Author: Manuel Lauss manuel.la...@gmail.com
Date: Thu Sep 24 21:44:24 2009 +0200
mips: fix build of vmlinux.lds
Commit 51b563fc93c8cb5bff1d67a0a71c374e4a4ea049 (arm, cris, mips,
sparc, powerpc, um, xtensa: fix build with bash 4.0) removed a few
CPPFLAGS with vital include paths necessary to build vmlinux.lds
on MIPS, and moved the calculation of the 'jiffies' symbol
directly to vmlinux.lds.S but forgot to change make ifdef/... to
cpp macros.
Signed-off-by: Manuel Lauss manuel.la...@gmail.com
[sam: moved assignment of CPPFLAGS arch/mips/kernel/Makefile]
Signed-off-by: Sam Ravnborg s...@ravnborg.org
Acked-by: Dmitri Vorobiev dmitri.vorob...@movial.com
diff --git a/arch/mips/kernel/Makefile b/arch/mips/kernel/Makefile
index e961221..eecd2a9 100644
--- a/arch/mips/kernel/Makefile
+++ b/arch/mips/kernel/Makefile
@@ -2,6 +2,8 @@
# Makefile for the Linux/MIPS kernel.
#
+CPPFLAGS_vmlinux.lds := $(KBUILD_CFLAGS)
+
extra-y:= head.o init_task.o vmlinux.lds
obj-y += cpu-probe.o branch.o entry.o genex.o irq.o process.o \
diff --git a/arch/mips/kernel/vmlinux.lds.S b/arch/mips/kernel/vmlinux.lds.S
index 9bf0e3d..162b299 100644
--- a/arch/mips/kernel/vmlinux.lds.S
+++ b/arch/mips/kernel/vmlinux.lds.S
@@ -11,15 +11,15 @@ PHDRS {
note PT_NOTE FLAGS(4); /* R__ */
}
-ifdef CONFIG_32BIT
- ifdef CONFIG_CPU_LITTLE_ENDIAN
+#ifdef CONFIG_32BIT
+ #ifdef CONFIG_CPU_LITTLE_ENDIAN
jiffies = jiffies_64;
- else
+ #else
jiffies = jiffies_64 + 4;
- endif
-else
+ #endif
+#else
jiffies = jiffies_64;
-endif
+#endif
SECTIONS
{
--
dann frazier
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522922: test build available
hey, Here's a build that includes Ben's patch. If you have this hardware, (or, for that matter, any hardware that uses igb) please test report back your results. http://people.debian.org/~dannf/bugs/522922 -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: upload 2.6.31 sid
On Fri, Oct 23, 2009 at 02:04:37PM +0200, maximilian attems wrote: any objections against uploading 2.6.31 to unstable tomorrow? fyi, ia64 is working fine (though there are no builds appearing in experimental for whatever reason) -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522922: fixed in sid/squeeze
Version: 2.6.28-1 This appears to have gone upstream in 2.6.27, so its first appearance in debian would've been 2.6.28-1 (we skipped 2.6.27). -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: increasing default value of mmap_min_addr
On Wed, Oct 21, 2009 at 02:54:59PM -0600, dann frazier wrote: hey, The kernel team is discussing the possibility of increase the default value of mmap_min_addr in lenny (it has already been done for sid). Obviously this has implications for the wine and dosemu packages (are there others?) The current proposal is to notify users in the next kernel DSA that we will be making this change in the next point release and point users to a wiki page that explains the problem and describes how to bump the setting in the meantime. I saw some discussion in #505247 about maybe adding a debconf question/stub file in /etc/sysctl.d to drop this value on a per-package basis. Do wine/dosemu have plans to do this? I wonder if we should consider including something like that in stable? I've created the following wiki page, which I plan to reference in the next kernel security advisory (will go out RSN): http://wiki.debian.org/mmap_min_addr Please review for accuracy. Maintainers should pay special attention to the application-specific notes towards the end. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Setting vm.mmap_min_addr for lenny?
On Fri, Aug 14, 2009 at 01:10:21PM +0200, Florian Weimer wrote: I wonder if it makes sense to set vm.mmap_min_addr to 4096 (instead of 0) for lenny. It seems to me that unstable already made this switch, and given the apparently neverending sequence of kernel NULL dereferences, this might be quite helpful. I didn't do this for the pending security update (which added some other protections), but I don't think it's a bad idea. The kernel currently recommends 65536 for x86/ia64/ppc64 and 32768 for arm and other archs. Though, 4096-for-all seems like a good solution to me. I was thinking that in the pending DSA[1] we could warn users that this default will change in the next point release, and provide instructions for making a local configuration change now. Maybe link to a wiki page w/ instructions, so that we can clarify/tweak later? As for packages that need a low min_mmap_addr, should we ask them to somehow start setting this tunable themselves (e.g., by dropping in an /etc/sysctl.d file)? Anyone know what Ubuntu is doing here? [1] http://svn.debian.org/wsvn/kernel-sec/dsa-texts/2.6.26-19lenny1 (currently awaiting 1 more arch build) -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Stable update?
On Mon, Oct 12, 2009 at 09:37:42PM +0100, Ben Hutchings wrote: On Mon, 2009-10-12 at 13:24 -0600, dann frazier wrote: On Sun, Oct 11, 2009 at 07:37:33PM +0100, Ben Hutchings wrote: I've collected quite a few bug fixes for 2.6.26-20. It seems like it might be worth uploading to stable-proposed-updates now. This will make it easier for the submitters to verify these fixes and for other submitters to check whether they address similar bug reports. Makes sense. I'd like to get a security update out this week as well. Should we do security update, merge, then p-u upload? It sounds like in general we can include some queued p-u stuff into security uploads, but in this case we have enough p-u content that we may want to bake those changes in p-u first. That makes sense to me. security update is about ready, just waiting on one more build. I'll start preparing a p-u upload that incorporates those changes - please let me know if there's any changes in-the-works we should wait for. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
increasing default value of mmap_min_addr
hey, The kernel team is discussing the possibility of increase the default value of mmap_min_addr in lenny (it has already been done for sid). Obviously this has implications for the wine and dosemu packages (are there others?) The current proposal is to notify users in the next kernel DSA that we will be making this change in the next point release and point users to a wiki page that explains the problem and describes how to bump the setting in the meantime. I saw some discussion in #505247 about maybe adding a debconf question/stub file in /etc/sysctl.d to drop this value on a per-package basis. Do wine/dosemu have plans to do this? I wonder if we should consider including something like that in stable? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: a question about a new kernel module
On Tue, Oct 20, 2009 at 05:12:04PM +0200, Luca Arzeni wrote: Hi, please excuse me if I'm sending to you this request but I'm not sure of where should I pose this question, so feel free to point me to other targets if you think so. --- I recently have bought an internal PCI modem WITH controller (not a winmodem). It's a robotics 2981 (chipser exar) and it's supported under linux from kernel 2.6.18 onward. According to the vendor, the kernel support for this controller is flawed, or not fully working, so the vendor release a module to make the modem work properly. The module is released as: EXAR Multiport Device Driver Ver 4.4 Installation Guide for Linux Kernel 2.6.18 (Tested with openSuse 10.2) Copyright (C) 2007, EXAR. All the drivers and utilities are published in form of source code under GNU General Public License in this version. Please refer to GNU General Public License announcement in each source code file for more detail. So it should be all compatible with the kernel policy. - Question is: may I contribute this module to you for including it into next kernel releases? The correct path is to get the necessary changes accepted upstream. We can then backport the necessary fixes into new kernel releases. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Stable update?
On Sun, Oct 11, 2009 at 07:37:33PM +0100, Ben Hutchings wrote: I've collected quite a few bug fixes for 2.6.26-20. It seems like it might be worth uploading to stable-proposed-updates now. This will make it easier for the submitters to verify these fixes and for other submitters to check whether they address similar bug reports. Makes sense. I'd like to get a security update out this week as well. Should we do security update, merge, then p-u upload? It sounds like in general we can include some queued p-u stuff into security uploads, but in this case we have enough p-u content that we may want to bake those changes in p-u first. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550190: linux-image-2.6.31-trunk-amd64: SCSI warnings/errors with LSI SAS1064E controller
On Thu, Oct 08, 2009 at 08:17:30PM +1100, Jason White wrote: Package: linux-2.6 Version: 2.6.31-1~experimental.1 Severity: normal After upgrading to 2.6.31 from 2.6.30, I get the following, quite frequently, in my log. Oct 8 19:15:03 jdc kernel: [34919.532016] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) Oct 8 19:15:37 jdc kernel: [34953.528772] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) Oct 8 19:15:37 jdc kernel: [34953.540511] sd 6:1:0:0: Queue depth not changed yet hmm.. wonder if this would help: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9d2e9d66a3f032667934144cd61c396ba49f090d Would you be able to test that? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496917: definitely present in Lenny
On Thu, Jun 25, 2009 at 01:12:58PM +0200, Philipp Hübner wrote: Hi, this bug is definitely present in up2date Lenny. There are optional, more up to date kvm modules in lenny. Are you using those? Does the problem go away if you do? This sequence of commands should build/install them for you: apt-get install kvm-source module-assistant m-a prepare m-a a-i kvm I have several machines running kvm, and they all have this problem. Guests at high load get stuck and cause 100% cpu load on as many cores/cpus in the host as have been assigned to the guest virtually. Using a newer kernel like 2.6.29 in the guest didn't change anything. I didn't try 2.6.29 on the host because for some reason kvm could not assign more than 3,5 Gb RAM to a guest then, while this works with 2.6.26= =2E Regards, --=20 .''`. Philipp H=FCbner debala...@arcor.de : :' : pgp fp: BA61 0B0A 2626 D49C BFC6 1C18 1619 74E4 C259 E0E8 `. `'` HP: http://debalance.funpic.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550010: hfsplus corrupts filesystems 2TB
On Wed, Oct 07, 2009 at 03:37:18AM +0100, Ben Hutchings wrote:
This is my suggested change, so far only compile-tested:
--- a/fs/hfsplus/wrapper.c
+++ b/fs/hfsplus/wrapper.c
@@ -99,6 +99,10 @@
if (hfsplus_get_last_session(sb, part_start, part_size))
return -EINVAL;
+ if (part_start + part_size = 0x1) {
+ pr_err(hfs: volumes larger than 2TB are not supported yet\n);
+ return -EINVAL;
+ }
minor point, but maybe s/hfs/hfsplus/ ?
while (1) {
bh = sb_bread512(sb, part_start + HFSPLUS_VOLHEAD_SECTOR, vhdr);
if (!bh)
--- END ---
Ben.
--
dann frazier
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kernel panic with 64G High Memory Support enabled
On Fri, Oct 02, 2009 at 12:54:03PM +0200, Patrick Maier wrote: Hi, I've [...] tried to build a new kernel (2.6.30) [...] with High Memory Support 64G. But after a reboot there is a kernel panic With High Memory Support set to 4G the kernel works fine. Tough to say, but since it is an upstream problem I'd suggest trying the latest upstream kernel You are building a self-compiled upstream kernel right? If the problem is reproducible with upstream kernels, you really need to report it there, and ideally with results/screen shots from 2.6.32-rc1 or 2.6.31. To point out, I've a RAID controller installed (HighPoint RocketRaid 3120). Hmmm I've installed the 2.6.30 kernel from debian unstable. It wasn't clear since you original said tried to build new kernel. Either way, please file this upstream: http://bugzilla.kernel.org/ upstream kernel? Sorry, but I'm not so familiar with that. I've tried to get the kernel-messages with serial, and netconsole, but I didn't get it to work, so I've attached images from the boot messages. So how can I get 2.6.32-rc1? Is it available with apt? It is not. If you are building your own kernel, you can download the source from kernel.org. If not, just report the issue upstream and note your kernel version (and include lspci output as Ben suggested). -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kernel panic with 64G High Memory Support enabled
On Fri, Oct 02, 2009 at 09:34:51PM +0200, Patrick Maier wrote: Hi, Either way, please file this upstream: http://bugzilla.kernel.org/ Ok so I've created an account there but I don't know how to report a bug, and in what category that goes. Memory Management, IO/Storage, Drivers and then which sub category. IO/Storage-Serial ATA I would guess. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Processed: owner 515741
On Thu, Oct 01, 2009 at 07:48:21AM +, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
owner 515741 marc.ko...@mni.fh-giessen.de
Bug #515741 {Done: dann frazier da...@debian.org}
[linux-image-2.6.26-1-amd64] flock() error with ocfs2/dlm
Owner recorded as marc.ko...@mni.fh-giessen.de.
Sven,
Is that really what you meant to do?
owner bugnumber address | !
Sets address to be the owner of #bugnumber. The owner of a bug
claims responsibility for fixing it. This is useful to share out
work in cases where a package has a team of maintainers.
If you wish to become the owner of the bug yourself, you can use
the ! shorthand or specify your own email address.
Maybe you meant to use submitter?
submitter bugnumber originator-address | !
Changes the originator of #bugnumber to originator-address.
If you wish to become the new originator of the report you can use
the ! shorthand or specify your own email address.
While the reopen command changes the originator of other bugs
merged with the one being reopened, submitter does not affect
merged bugs.
See:
http://www.debian.org/Bugs/server-control#submitter
http://www.debian.org/Bugs/server-control#owner
--
dann frazier
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kernel panic with 64G High Memory Support enabled
On Thu, Oct 01, 2009 at 11:31:25PM +0200, Patrick Maier wrote: Hi, I've [...] tried to build a new kernel (2.6.30) [...] with High Memory Support 64G. But after a reboot there is a kernel panic With High Memory Support set to 4G the kernel works fine. Tough to say, but since it is an upstream problem I'd suggest trying the latest upstream kernel I've booted the kernel without the quiet option and here is a bit more detail. I've attached an image with the last screen and the Kernel panic. Hope this brings a bit more light in the problem. You are building a self-compiled upstream kernel right? If the problem is reproducible with upstream kernels, you really need to report it there, and ideally with results/screen shots from 2.6.32-rc1 or 2.6.31. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kernel panic with 64G High Memory Support enabled
On Wed, Sep 30, 2009 at 11:49:34PM +0200, Patrick Maier wrote: Hi @all, I've a new raid controller HighPoint RocketRaid 3120 and tried to build a new kernel (2.6.30) for that. I've 16GB ram, so I activated the High Memory Support from 4G to 64G. Then did the normal procedure with make-kpkg and update-initramfs -u -k 2.6.30 But after a reboot there is a kernel panic: (I've GRUB2 installed) === snip === Loading, please wait... [1.700017] ata4: softreset failed (device not ready) [2.035670] end_request: I/O error, dev sda, sector 82264479 [2.035788] end_request: I/O error, dev sda, sector 82264479 run-init: /sbin/init: I/O error [2.035973] Kernel panic - not syncing: Attempted to kill init! === snip === With High Memory Support set to 4G the kernel works fine. I've attached the .config for the not working kernel and the grub.cfg Tough to say, but since it is an upstream problem I'd suggest trying the latest upstream kernel and, if the problem still exists, reporting a bug at: http://bugzilla.kernel.org -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515741: please test
hey, Can you test this kernel and report back the results? http://people.debian.org/~dannf/bugs/515741/ -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: firmware-linux package non-free?
On Mon, Sep 28, 2009 at 11:30:04AM -0700, Ben Hutchings wrote: On Mon, 2009-09-28 at 17:06 +0200, Jürgen Kertz wrote: Hello! Thank you all for explaining the matter to me! I finally understand why there has to be this non-free firmware package. Hopefully there will be a convenient exception for the squeeze release similar to the vote for lenny, but i guess this has to be discussed somewhere else. There will be no such exception. You should assume that you will need to provide firmware on separate media such as a USB flash drive when installing squeeze. (This is already the case for lenny when using some wireless devices for installation.) Though note that you can mod your installer to include any necessary firmware - assuming your driver has support for loading it. Here's a script to do that, which works w/ the firmware redistributed in non-free: http://dannf.org/bloggf/tech/add-firmware-to.html -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530636: Issue stille present
On Tue, Sep 15, 2009 at 06:51:33PM +0200, jazz wrote: I ran the test kernel for a day with no oops (fyi, it used to oops in about 30 min. max). Great, thanks for testing. This fix should be included in the next stable release. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530636: Issue stille present
On Mon, Sep 14, 2009 at 02:18:54PM +0200, jazz wrote: After a lot of issue i'm finally about to test your fix ! The build server still appears to be down ... correct ? Correct. You can grab a build from here: http://people.debian.org/~dannf/bugs/530636/ -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Looking for source pkg of old kernel (linux-image-2.6.18.dfsg.1-22etch2)
On Thu, Sep 10, 2009 at 08:02:29PM +0200, Ico Doornekamp wrote: Hello, I'm trying to trace a kernel quirk on an embedded system. I found a debian bug report (#496850) stating that the bug I'm looking at exists in linux-image-2.6.18.dfsg.1-22etch2 but was not found in 2.6.18.dfsg-1-22. I'd like to compare the two to find the cause of the issue. I have been looking for the source packages of these versions, but no luck. I found 2.6.18.dfsg.1-[12/24/26] but not these version. Are these available somewhere, and if yes, where do I find them ? You can always pull them from svn. svn export svn://svn.debian.org/svn/kernel/releases/linux-2.6/2.6.18.dfsg.1-22 svn export svn://svn.debian.org/svn/kernel/releases/linux-2.6/2.6.18.dfsg.1-22etch2 -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Driver for HP arry P410I ZM SAS array controller
On Wed, Sep 09, 2009 at 12:14:20PM +0200, Olivier JUDITH wrote: Sorry , i made i big mistake . I'm very confuse. The problem not coming from the P410i card but from a P212 SAS PCI controller which is directly attached to the HP MSL Tape library. same driver module is used for both card. I have no information and device for P212 card and can not see the tape library on debian. /proc/scsi/scsi on debian Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: TEAC Model: DV-28S-V Rev: C.0F Type: CD-ROM ANSI SCSI revision: 05 /proc/scsi/scsi on Redhat Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: TEAC Model: DV-28S-V Rev: C.0F Type: CD-ROM ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: HP Model: Ultrium 3-SCSI Rev: C25W Type: Sequential-AccessANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: HP Model: MSL G3 SeriesRev: 4.60 Type: Medium Changer ANSI SCSI revision: 05 Sorry bad informations in my previous email Can you provide the 'dmesg' output from the Red Hat system? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540831: missing appointments
On Wed, Sep 09, 2009 at 08:40:19AM +0800, jida...@jidanni.org wrote: I'm missing too many appointments and email notifications. I'm putting a modprobe into /etc/rc.local as a workaround. Hope I remember to take it back out when this bug is fixed. I don't see how this comment helps the bug report at all - perhaps you could post such stream of consciousness comments to a personal blog? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Problems with kernel 2.6.26-2-686-bigmem
On Fri, Aug 28, 2009 at 12:08:35PM -0600, David Vanfleet wrote: Luk Claes wrote: David Vanfleet wrote: Hi, I'm trying to get Debian (Lenny) to recognize 6 Gig of memory on a Dell PE 2650 server. I installed the basic 5.02a Debian system with just a minimal install then I installed the 2.6.26-2-686-bigmem kernel so it will see all the memory. When I boot into the bigmem kernel it fails to boot, the errors I get are: WARNING boot device may be renamed. Try root=/dev/hda3 ... ALERT! /dev/sda3 does not exist Did you try with changing the root device for the bigmem kernel to /dev/hda3? If you use grub for booting you could do that by pressing 'e' (for edit on the line with the bigmem kernel) and afterwards pressing 'b' (for boot) while in the grub menu (to just try it) or updating /boot/grub/menu.lst (for the bigmem kernel) and running update-grub before rebooting into the bigmem kernel. Thanks for your response, I did try what you suggested but got the same error, except it says that /dev/hda3 does not exist. Looking in /dev there is no sda* or hda*, there only an hda which I think is the CD drive. When I boot to the default Kernel then /dev/sda3 exists and is used to boot the kernel. Any other ideas? Does this system use the aacraid driver? If so, please try testing the kernel from lenny-proposed-updates (2.6.26-19). -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530636: Issue stille present
On Fri, Aug 28, 2009 at 02:46:15PM +0200, jazz wrote: i'm currently experiencing issues with my platform, i'll update the bug as soon as i'll be able to reproduce. Btw, i was using the standard x86 linux kernel packaged with debian stable. I'm tried all of the update done since lenny was released (the last try was with 2.6.26-17lenny2). ok - that is the version I was after. When your system is available again, can you test a lenny snapshot build? I committed a fix there that might help. See this page for information on accessing snapshots: http://wiki.debian.org/DebianKernel (Note that the build server is offline at the moment) -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530636: Issue stille present
On Tue, Aug 25, 2009 at 02:42:15PM +0200, jazz wrote: The issue is still present in the latest debian kernel release. Can you be specific about the version? (hint: cat /proc/version) -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543398: linux-image-2.6.30-1-686: e100 is missing a dependency on linux-firmware
On Mon, Aug 24, 2009 at 07:24:28PM +0100, Jon Thackray wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: important In the 2.6.30 kernel, but not in 2.6.26, e100 depends on d101m_ucode.bin, from firmware-linux. The kernel package is not marked as depending on this. Packages in main cannot depend upon packages in non-free. Further, this isn't a strict dependency - only certain devices require firmware files. I won't argue that the current mechanism is ideal - there is a warning on upgrade (from initramfs-tools), but it doesn't tell you precisely what to do about it. Consequently, if you reboot into your newly installed 2.6.30 kernel, your networking, if using an E10/100 card for instance, is irretrievably broken. Irretrievably? Can't you reboot your old kernel and install firmware-linux? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542695: cannot use crypto loop aes
On Thu, Aug 20, 2009 at 10:14:46PM +0200, J.M.Roth wrote: Package: loop-aes-modules-2.6.26-2-686 Version: 2.6.26+3.2c-6+lenny1 This isn't a debian kernel version. Can you reproduce with the lenny kernel? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542358: linux-image-2.6.30-1-686: e100 module refuses to load
On Wed, Aug 19, 2009 at 10:28:44AM +0200, Jan Prunk wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal Hello ! I have recently upgraded the kernel to 2.6.30 (squeeze) from a running 2.6.26. During the upgrade I got this error: Setting up linux-image-2.6.30-1-686 (2.6.30-5) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100 You probably need to install the firmware-linux package from non-free. Please let us know if this fixes the issue for you. Running update-grub. In 2.6.26 kernel the dmesg will tell me: [ 10.884256] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex [ 10.888710] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Which enables the e100 module to be working. However in 2.6.30 I cannot connect anymore to the machine over the internet, I assume that it is becouse of this ethernet module which I am using. The machine seems to boot into 2.6.30 and then it hangs there. I cannot investigate any further, becouse of the remote access. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542358: linux-image-2.6.30-1-686: e100 module refuses to load
On Wed, Aug 19, 2009 at 05:59:29PM +0200, Jan Prunk wrote: Thank you for your suggestion, this indeed fixes this bug report ! Great, closing. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RL meeting
On Tue, Aug 18, 2009 at 10:50:26PM +0100, Steve McIntyre wrote: So, how's everybody getting on with organising their trip? I'm told that prices for the conf go up again at the end of the month, so if you haven't already sorted that out then please do so ASAP. Steve also just mentioned that the hotel rooms at the Marriott may be expensive, so if you want to stay there then it would probably be sensible to work out sharing rooms. Talk to me? :-) I've registered and booked travel, arriving Tuesday evening. My employer has agreed to help out with some of my expenses as well, including my room which I'll be sharing w/ a coworker. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
