Re: loop-aes in Debian Live
On 03/02/2011 06:12 AM, Ben Hutchings wrote: > I seem to recall that Debian Live used to support using loop-aes for > persistent storage, and that this is not possible (or difficult) in > squeeze because of the removal of prebuilt loop-aes modules generated by > linux-modules-extra. Is that correct? having the rootfs encrypted was supported through loop-aes, which is not possible with squeeze, yes. persistency was done through luks which should work with squeeze (it's not much tested though). > Max Vozeler worked on a replacement for loop-aes in the form of a > compatible cipher mode for dm-crypt; Milan Broz has since polished up > his changes; and they were accepted into Linux 2.6.38. nice. > If there are a substantial number of Debian Live users with loop-aes > partitions, I think we can justify adding a backport of these changes to > a point release of the kernel in squeeze. I don't know what changes > would be needed outside of the kernel. would be nice if you could include it, so we can advise people that build images with encryption to use backports of live-boot (by automatially including them from live.d.n with lb config -r live.debian.net), once we've updated live-boot to work with it. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/4d6dda8a.9070...@progress-technologies.net
Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1
On Tue, 2011-03-01 at 19:17 +, Adam D. Barratt wrote: > On Tue, 2011-03-01 at 18:19 +, Ben Hutchings wrote: > > On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: > > > On Mon, Feb 28, 2011 at 04:53, Ben Hutchings wrote: > > > ... > > > > I know that I need to upload in time for the installer team to rebuild > > > > the installer with the new kernel version, addressing the known issues > > > > with the kernel used in 6.0.0. Please could you let me know what the > > > > deadline is for that? > > > ... > > > > > > It depends on the ETA for 6.0.1. I'd a week before the targeted date > > > assuming it builds fine on all arches. For a confort level, I'd say a > > > cuple of weeks like a good time for we to update the installer for it. > > > > OK, so what's the targeted date? > > We're still working out the precise details, but the general plan is to > aim for 6.0.1 being during FTPMaster's upcoming meeting in Essen. That > starts on the 21st so, working backwards, two weeks would take us to the > coming weekend. > > If it's possible to get the source upload in by the end of the weekend, > that would be great. [...] That should be fine. That gives us time to include longterm release 2.6.32.30 and pick up a few other bug fixes. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
loop-aes in Debian Live
I seem to recall that Debian Live used to support using loop-aes for
persistent storage, and that this is not possible (or difficult) in
squeeze because of the removal of prebuilt loop-aes modules generated by
linux-modules-extra. Is that correct?
Max Vozeler worked on a replacement for loop-aes in the form of a
compatible cipher mode for dm-crypt; Milan Broz has since polished up
his changes; and they were accepted into Linux 2.6.38.
If there are a substantial number of Debian Live users with loop-aes
partitions, I think we can justify adding a backport of these changes to
a point release of the kernel in squeeze. I don't know what changes
would be needed outside of the kernel. I've prepared a backport
(patches attached), but I haven't tested it myself.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
From aa9b864f6201b649cc7ead5331b9c3b4a54c6399 Mon Sep 17 00:00:00 2001
From: Max Vozeler
Date: Sun, 17 Jan 2010 21:55:31 +1100
Subject: [PATCH 1/4] crypto: md5 - Add export support
commit 7d6f75eb21b84cdc5dfb09789974f02b42a89058 upstream.
This patch adds export/import support to md5. The exported type is
defined by struct md5_state.
This is modeled after the equivalent change to sha1_generic.
Signed-off-by: Max Vozeler
Signed-off-by: Herbert Xu
---
crypto/md5.c | 40
include/crypto/md5.h | 17 +
2 files changed, 41 insertions(+), 16 deletions(-)
create mode 100644 include/crypto/md5.h
diff --git a/crypto/md5.c b/crypto/md5.c
index 83eb529..9fda213 100644
--- a/crypto/md5.c
+++ b/crypto/md5.c
@@ -16,17 +16,13 @@
*
*/
#include
+#include
#include
#include
#include
#include
#include
-#define MD5_DIGEST_SIZE 16
-#define MD5_HMAC_BLOCK_SIZE 64
-#define MD5_BLOCK_WORDS 16
-#define MD5_HASH_WORDS 4
-
#define F1(x, y, z) (z ^ (x & (y ^ z)))
#define F2(x, y, z) F1(z, x, y)
#define F3(x, y, z) (x ^ y ^ z)
@@ -35,12 +31,6 @@
#define MD5STEP(f, w, x, y, z, in, s) \
(w += f(x, y, z) + in, w = (w<>(32-s)) + x)
-struct md5_ctx {
- u32 hash[MD5_HASH_WORDS];
- u32 block[MD5_BLOCK_WORDS];
- u64 byte_count;
-};
-
static void md5_transform(u32 *hash, u32 const *in)
{
u32 a, b, c, d;
@@ -141,7 +131,7 @@ static inline void cpu_to_le32_array(u32 *buf, unsigned int words)
}
}
-static inline void md5_transform_helper(struct md5_ctx *ctx)
+static inline void md5_transform_helper(struct md5_state *ctx)
{
le32_to_cpu_array(ctx->block, sizeof(ctx->block) / sizeof(u32));
md5_transform(ctx->hash, ctx->block);
@@ -149,7 +139,7 @@ static inline void md5_transform_helper(struct md5_ctx *ctx)
static int md5_init(struct shash_desc *desc)
{
- struct md5_ctx *mctx = shash_desc_ctx(desc);
+ struct md5_state *mctx = shash_desc_ctx(desc);
mctx->hash[0] = 0x67452301;
mctx->hash[1] = 0xefcdab89;
@@ -162,7 +152,7 @@ static int md5_init(struct shash_desc *desc)
static int md5_update(struct shash_desc *desc, const u8 *data, unsigned int len)
{
- struct md5_ctx *mctx = shash_desc_ctx(desc);
+ struct md5_state *mctx = shash_desc_ctx(desc);
const u32 avail = sizeof(mctx->block) - (mctx->byte_count & 0x3f);
mctx->byte_count += len;
@@ -194,7 +184,7 @@ static int md5_update(struct shash_desc *desc, const u8 *data, unsigned int len)
static int md5_final(struct shash_desc *desc, u8 *out)
{
- struct md5_ctx *mctx = shash_desc_ctx(desc);
+ struct md5_state *mctx = shash_desc_ctx(desc);
const unsigned int offset = mctx->byte_count & 0x3f;
char *p = (char *)mctx->block + offset;
int padding = 56 - (offset + 1);
@@ -220,12 +210,30 @@ static int md5_final(struct shash_desc *desc, u8 *out)
return 0;
}
+static int md5_export(struct shash_desc *desc, void *out)
+{
+ struct md5_state *ctx = shash_desc_ctx(desc);
+
+ memcpy(out, ctx, sizeof(*ctx));
+ return 0;
+}
+
+static int md5_import(struct shash_desc *desc, const void *in)
+{
+ struct md5_state *ctx = shash_desc_ctx(desc);
+
+ memcpy(ctx, in, sizeof(*ctx));
+ return 0;
+}
+
static struct shash_alg alg = {
.digestsize = MD5_DIGEST_SIZE,
.init = md5_init,
.update = md5_update,
.final = md5_final,
- .descsize = sizeof(struct md5_ctx),
+ .export = md5_export,
+ .import = md5_import,
+ .descsize = sizeof(struct md5_state),
.base = {
.cra_name = "md5",
.cra_flags = CRYPTO_ALG_TYPE_SHASH,
diff --git a/include/crypto/md5.h b/include/crypto/md5.h
new file mode 100644
index 000..65f299b
--- /dev/null
+++ b/include/crypto/md5.h
@@ -0,0 +1,17 @@
+#ifndef _CRYPTO_MD5_H
+#define _CRYPTO_MD5_H
+
+#include
+
+#define MD5_DIGEST_SIZE 16
+#define MD5_HMAC_BLOCK_SIZE 64
+#define MD5_BLOCK_WORDS 16
+#define MD5_HASH_WORDS 4
+
+struct md5_state {
+ u32 hash[MD5_HASH_WORDS];
+ u32 block[MD5_BLOCK_WORDS];
+ u64 byte_count;
+};
+
+#endif
--
1.7.4.1
From ef0ca15bcd522f72f62e74e28653d406be1cd500 Mon Sep 17 00:00:00 2001
From: Milan Broz
Date: Thu, 13 Jan 2011 19:59:54 +
Subject: [PATCH 2/4] dm crypt:
Processed: tagging 614583
Processing commands for cont...@bugs.debian.org: > tags 614583 + moreinfo Bug #614583 [linux-2.6] Keyboard fails to respond while starting Debian-Installer on Debian 6 "Squeeze" for PowerPC on a G5 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 614583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129903280213980.transcr...@bugs.debian.org
Bug#614583: Keyboard fails to respond while starting Debian-Installer on Debian 6 "Squeeze" for PowerPC on a G5
On Tue, 2011-02-22 at 13:02 +, Leandro Doctors wrote: > Package: installation-reports > > Hi, > > We've just tried to install Debian 6 "Squeeze" for PowerPC on a G5 and > got the same error as reported in #420027. > > (It boots fine from the CD.) > -Yaboot 1.3.13 shows the initial text screen (with black background) > asking to select the installation method. > -We select install mode (either "install" or "expert"). > (The kernel starts loading...) > -The system shows the next text screen (with white background), asking > to write "mac-install". From that point, the keyboard does not > respond anymore. Does this screen say 'Welcome to Open Firmware'? And does it prompt you to type 'mac-install' or 'mac-boot'? [...] > We have tried three keyboards: > -an standard USB Mac Keyboard (EN_US layout), > -a Microsoft Digital Media Keyboard 3000 USB keyboard for PC (FR_BE > layout), and > -a Microsoft Comfort Curve Keyboard 2000 USB Keyboard for PC (LATAM layout) > All of them work fine on a installed Debian system on amd64. (And they > also work fine before the second text screen appears). [...] I tried to reproduce this on a PowerBook G4 with an external USB keyboard. This keyboard worked at the boot prompts and in the installer. However, I was able to provoke similar symptoms by initially selecting 'install64' where I should have selected 'install'. Since the G5 is a 64-bit processor (unlike the G4), please try selecting 'install64' instead of 'install'. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 614583 linux-2.6 Bug #614583 [installation-reports] Keyboard fails to respond while starting Debian-Installer on Debian 6 "Squeeze" for PowerPC on a G5 Bug reassigned from package 'installation-reports' to 'linux-2.6'. > found 614583 2.6.32-29 Bug #614583 [linux-2.6] Keyboard fails to respond while starting Debian-Installer on Debian 6 "Squeeze" for PowerPC on a G5 There is no source info for the package 'linux-2.6' at version '2.6.32-29' with architecture '' Unable to make a source version for version '2.6.32-29' Bug Marked as found in versions 2.6.32-29. > thanks Stopping processing here. Please contact me if you need assistance. -- 614583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129902399612138.transcr...@bugs.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > submitter 533565 kushalkool...@gmail.com Bug #533565 [linux-2.6] linux-image-2.6.30-1-686: ATA bus error messages for PATA_SCH module Changed Bug submitter to 'kushalkool...@gmail.com' from 'Kushal Koolwal ' > owner 533565 kushalkool...@gmail.com Bug #533565 [linux-2.6] linux-image-2.6.30-1-686: ATA bus error messages for PATA_SCH module Owner recorded as kushalkool...@gmail.com. > quit Stopping processing here. Please contact me if you need assistance. -- 533565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.r.12990221015224.transcr...@bugs.debian.org
Bug#616017: [firmware-ralink] Please add rt3070
Package: firmware-ralink Version: 0.28 Severity: normal Please add support for rt3070. Upstream link: http://www.ralink.com.tw/license_us.php?n=2&p=0&t=U0wyRnpjMlYwY3k4eU1ERXhMekF4THpFM0wyUnZkMjVzYjJGa016STJNekEyTnpZek5DNWllakk5UFQweU1ERXhYekF4TURkZlVsUXpNRGN3WDFKVU16TTNNRjlNYVc1MWVGOVRWRUZmZGpJdU5TNHdMakZmUkZCUExuUmhjZz09Qw%3D%3D I install firmware-ralink but my device don`t work correctly. By default load module for rt2870 =( I try it on 2.6.32 and 2.6.37 kernel amd64 versions. lsusb: Bus 001 Device 004: ID 0b05:1784 ASUSTek Computer, Inc. USB-N13 802.11n Network Adapter [Ralink RT2870] --- System information. --- Architecture: amd64 Kernel: Linux 2.6.37-1-amd64 Debian Release: wheezy/sid 990 testing www.debian-multimedia.org 990 testing ftp.de.debian.org 990 testing apt.byteme.org.uk 500 unstable www.debian-multimedia.org 500 unstable ftp.de.debian.org 500 stable www.debian-multimedia.org 500 stable security.debian.org 500 stable ftp.de.debian.org 500 squeeze deb.playonlinux.com 500 sid www.lamaresh.net 1 experimental www.debian-multimedia.org 1 experimental ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== initramfs-tools | 0.98.8 linux-image | -- 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/4d6d58d1.9030...@rambler.ru
Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4
Whoops, looks like the Debian bug-tracker lost the CC list somehow. I believe I've got all the CCs re-added, sorry for any duplicate emails. On Mar 01, 2011, at 11:52, Kyle Moffett wrote: > Package: linux-2.6 > Version: 2.6.32-30 > Severity: important > > I'm getting a repeatable BUG from ext4, which seems to be caused by > Postfix processing its mail queue. The specific filesystem block device > that has the problem seems to be "dm-13", which on this boot is the > logical volume containing the "/var/spool/postfix" chroot. > > This is a completely standard Debian installation running on an Amazon EC2 > instance (x86_64). The filesystem is mounted in "data=journal" mode. > > This crash is *very* repeatable. It occurs almost every reboot when > there are more than 1 or 2 queued emails. I will try re-mounting the > filesystem in "data=ordered" mode momentarily. > > The relevant filesystems are: > /dev/mapper/system-root / ext4 rw,noatime,barrier=1,data=ordered 0 0 > /dev/mapper/system-var /var ext4 > rw,noatime,barrier=1,nodelalloc,data=journal 0 0 > /dev/mapper/system-log /var/log ext4 > rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0 > /dev/xvda1 /boot ext3 rw,noatime,user_xattr,acl,data=journal 0 0 > /dev/mapper/db-mail /var/mail ext4 > rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0 > /dev/mapper/db-postfix /var/spool/postfix ext4 > rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=journal 0 0 > /dev/mapper/db-smtp /var/lib/postfix ext4 > rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=journal 0 0 > /dev/mapper/db-smtpcfg /etc/postfix ext4 > rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=journal 0 0 > > In particular, I note that there was a previous report of a BUG at > fs/jbd2/commit.c:533 which never seemed to get isolated: > http://www.kerneltrap.com/mailarchive/linux-ext4/2009/9/2/6373283 > > I need to get this system operational again right now, but I'm going to > take a consistent snapshot of it so I can debug it later. > > NOTE: For followers on the linux-ext4 mailing list, this particular > system is running the Debian "squeeze" kernel (based on 2.6.32), so it's > theoretically possible this bug has been fixed upstream since then. > I didn't have any luck finding such a fix on Google, though. > > -- Package-specific info: > ** Version: > Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) > (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 05:46:49 UTC 2011 > > ** Command line: > root=/dev/mapper/system-root ro > > ** Tainted: D (128) > * Kernel has oopsed before. > > ** Kernel log: > [ 118.525038] alloc irq_desc for 526 on node -1 > [ 118.525040] alloc kstat_irqs on node -1 > [ 118.700415] device-mapper: uevent: version 1.0.3 > [ 118.700890] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: > dm-de...@redhat.com > [ 118.925563] EXT4-fs (dm-0): INFO: recovery required on readonly filesystem > [ 118.925580] EXT4-fs (dm-0): write access will be enabled during recovery > [ 118.968700] EXT4-fs (dm-0): orphan cleanup on readonly fs > [ 118.968716] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced > inode 790044 > [ 118.968761] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced > inode 790012 > [ 118.968768] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced > inode 790011 > [ 118.968775] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced > inode 790010 > [ 118.968782] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced > inode 790009 > [ 118.968788] EXT4-fs (dm-0): 5 orphan inodes deleted > [ 118.968794] EXT4-fs (dm-0): recovery complete > [ 118.979150] EXT4-fs (dm-0): mounted filesystem with ordered data mode > [ 119.293543] udev[204]: starting version 164 > [ 119.366778] input: PC Speaker as /devices/platform/pcspkr/input/input1 > [ 119.436417] Error: Driver 'pcspkr' is already registered, aborting... > [ 124.153241] Adding 4194296k swap on /dev/xvdb1. Priority:-1 extents:1 > across:4194296k SS > [ 125.156599] loop: module loaded > [ 138.650657] EXT4-fs (dm-21): Ignoring delalloc option - requested data > journaling mode > [ 138.650959] EXT4-fs (dm-21): mounted filesystem with journalled data mode > [ 138.660092] EXT4-fs (dm-22): mounted filesystem with ordered data mode > [ 138.674436] kjournald starting. Commit interval 5 seconds > [ 138.675145] EXT3 FS on xvda1, internal journal > [ 138.675155] EXT3-fs: mounted filesystem with journal data mode. > [ 138.728462] EXT4-fs (xvdc): mounted filesystem without journal > [ 138.745406] EXT4-fs (dm-17): mounted filesystem with ordered data mode > [ 138.748531] EXT4-fs (dm-18): mounted filesystem with ordered data mode > [ 138.774667] EXT4-fs (dm-19): mounted filesystem with ordered data mode > [ 138.780834] EXT4-fs (dm-2): Ignoring delalloc option - requested data > journaling mode > [ 138.781400] EXT4-fs (dm-2): mounted filesystem with journalled data mode > [ 138.784700] EXT4-fs (dm-1): Ignorin
Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1
* Adam D. Barratt [2011-03-01 19:17]: > Otavio: other than lkdi and the d-i build itself (which I guess could be > a binNMU this time?) It cannot be a binNMU since there are at least two changes in debian-installer for squeeze. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110301195813.go1...@jirafa.cyrius.com
Processed: Re: Bug#615962: linux-image-2.6.37-1-amd64: can not boot after updating to a new kernel 2-6.37-1
Processing commands for cont...@bugs.debian.org: > # fixed in libc 2.11.2-13 / 2.13-0exp3 > reassign 615962 libc-bin Bug #615962 [linux-2.6] linux-image-2.6.37-1-amd64: can not boot after updating to a new kernel 2-6.37-1 Bug reassigned from package 'linux-2.6' to 'libc-bin'. Bug No longer marked as found in versions 2.6.37-1. > forcemerge 615806 615962 Bug#615806: eglibc: Broken ldd due to wrong path for ld.so Bug#615962: linux-image-2.6.37-1-amd64: can not boot after updating to a new kernel 2-6.37-1 Bug#615839: Kernel panic - not syncing: No init found Forcibly Merged 615806 615839 615962. > End of message, stopping processing here. Please contact me if you need assistance. -- 615806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615806 615839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615839 615962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12990072805655.transcr...@bugs.debian.org
Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1
On Tue, 2011-03-01 at 18:19 +, Ben Hutchings wrote: > On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: > > On Mon, Feb 28, 2011 at 04:53, Ben Hutchings wrote: > > ... > > > I know that I need to upload in time for the installer team to rebuild > > > the installer with the new kernel version, addressing the known issues > > > with the kernel used in 6.0.0. Please could you let me know what the > > > deadline is for that? > > ... > > > > It depends on the ETA for 6.0.1. I'd a week before the targeted date > > assuming it builds fine on all arches. For a confort level, I'd say a > > cuple of weeks like a good time for we to update the installer for it. > > OK, so what's the targeted date? We're still working out the precise details, but the general plan is to aim for 6.0.1 being during FTPMaster's upcoming meeting in Essen. That starts on the 21st so, working backwards, two weeks would take us to the coming weekend. If it's possible to get the source upload in by the end of the weekend, that would be great. Hopefully getting all the builds in for squeeze quickly will be no problem; we sometimes ended up cutting things rather fine in the past for lenny (e.g. arm taking several days to build and a race condition somewhere in the build setup process which meant some architectures needed three attempts at the build for some uploads). Otavio: other than lkdi and the d-i build itself (which I guess could be a binNMU this time?) which obviously need to come afterwards, are any of your other proposed uploads dependent on the timing of the kernel uploads? Regards, Adam -- 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/1299007033.10572.59.ca...@hathi.jungle.funky-badger.org
Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1
On Tue, Mar 1, 2011 at 18:19, Ben Hutchings wrote: > On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: >> It depends on the ETA for 6.0.1. I'd a week before the targeted date >> assuming it builds fine on all arches. For a confort level, I'd say a >> cuple of weeks like a good time for we to update the installer for it. > > OK, so what's the targeted date? It doesn't depends on me. It is RMs' call. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/AANLkTi=qj43n57nyn9zod8vmjngugykne3hum5rl_...@mail.gmail.com
Bug#615598: I've seen something like this, too.
I've seen a similar problem, with the EDID complaint every so often, on a machine with Intel graphics, with each of 2.6.37-1 and 2.6.37-2. This machine's graphics continue to work. -- Thomas E. Vaughan -- 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/AANLkTimCMeY2Z--Xp1V8nNOcNWypUn-x6b3W6o-=w...@mail.gmail.com
Bug#590105: Same problem on LS-WSGL
* Benjamin Cama [2011-03-01 08:17]: > I can help for that. I have serial console access and I'm ready to try > different builds. BTW, there's nothing to flash (appart from kernel boot > prameters) on the Mini as the kernel is loaded directly from the disk > (images must be present on both sda1 and sdb1, on an ext2/3 FS). Can you please file a wishlist bug on oldsys-preseed to support this device? It would also be great if you could check out oldsys-preseed from git: git://git.debian.org/git/d-i/oldsys-preseed and send a patch. Looks at the code that is there for the LS Pro already. Can this be adapted for the Mini? Does the Mini use ext2/3 of XFS by default? (The LS Pro uses XFS, which we cannot read in Debian.) Anyway, please don't respond here (since this bug is really about a different machine) but open a new bug on oldsys-preseed. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110301183344.gm1...@jirafa.cyrius.com
Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1
On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: > On Mon, Feb 28, 2011 at 04:53, Ben Hutchings wrote: > ... > > I know that I need to upload in time for the installer team to rebuild > > the installer with the new kernel version, addressing the known issues > > with the kernel used in 6.0.0. Please could you let me know what the > > deadline is for that? > ... > > It depends on the ETA for 6.0.1. I'd a week before the targeted date > assuming it builds fine on all arches. For a confort level, I'd say a > cuple of weeks like a good time for we to update the installer for it. OK, so what's the targeted date? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110301181903.gg19...@decadent.org.uk
Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4
Package: linux-2.6 Version: 2.6.32-30 Severity: important I'm getting a repeatable BUG from ext4, which seems to be caused by Postfix processing its mail queue. The specific filesystem block device that has the problem seems to be "dm-13", which on this boot is the logical volume containing the "/var/spool/postfix" chroot. This is a completely standard Debian installation running on an Amazon EC2 instance (x86_64). The filesystem is mounted in "data=journal" mode. This crash is *very* repeatable. It occurs almost every reboot when there are more than 1 or 2 queued emails. I will try re-mounting the filesystem in "data=ordered" mode momentarily. The relevant filesystems are: /dev/mapper/system-root / ext4 rw,noatime,barrier=1,data=ordered 0 0 /dev/mapper/system-var /var ext4 rw,noatime,barrier=1,nodelalloc,data=journal 0 0 /dev/mapper/system-log /var/log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0 /dev/xvda1 /boot ext3 rw,noatime,user_xattr,acl,data=journal 0 0 /dev/mapper/db-mail /var/mail ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0 /dev/mapper/db-postfix /var/spool/postfix ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=journal 0 0 /dev/mapper/db-smtp /var/lib/postfix ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=journal 0 0 /dev/mapper/db-smtpcfg /etc/postfix ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=journal 0 0 In particular, I note that there was a previous report of a BUG at fs/jbd2/commit.c:533 which never seemed to get isolated: http://www.kerneltrap.com/mailarchive/linux-ext4/2009/9/2/6373283 I need to get this system operational again right now, but I'm going to take a consistent snapshot of it so I can debug it later. NOTE: For followers on the linux-ext4 mailing list, this particular system is running the Debian "squeeze" kernel (based on 2.6.32), so it's theoretically possible this bug has been fixed upstream since then. I didn't have any luck finding such a fix on Google, though. -- Package-specific info: ** Version: Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 05:46:49 UTC 2011 ** Command line: root=/dev/mapper/system-root ro ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 118.525038] alloc irq_desc for 526 on node -1 [ 118.525040] alloc kstat_irqs on node -1 [ 118.700415] device-mapper: uevent: version 1.0.3 [ 118.700890] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [ 118.925563] EXT4-fs (dm-0): INFO: recovery required on readonly filesystem [ 118.925580] EXT4-fs (dm-0): write access will be enabled during recovery [ 118.968700] EXT4-fs (dm-0): orphan cleanup on readonly fs [ 118.968716] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced inode 790044 [ 118.968761] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced inode 790012 [ 118.968768] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced inode 790011 [ 118.968775] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced inode 790010 [ 118.968782] EXT4-fs (dm-0): ext4_orphan_cleanup: deleting unreferenced inode 790009 [ 118.968788] EXT4-fs (dm-0): 5 orphan inodes deleted [ 118.968794] EXT4-fs (dm-0): recovery complete [ 118.979150] EXT4-fs (dm-0): mounted filesystem with ordered data mode [ 119.293543] udev[204]: starting version 164 [ 119.366778] input: PC Speaker as /devices/platform/pcspkr/input/input1 [ 119.436417] Error: Driver 'pcspkr' is already registered, aborting... [ 124.153241] Adding 4194296k swap on /dev/xvdb1. Priority:-1 extents:1 across:4194296k SS [ 125.156599] loop: module loaded [ 138.650657] EXT4-fs (dm-21): Ignoring delalloc option - requested data journaling mode [ 138.650959] EXT4-fs (dm-21): mounted filesystem with journalled data mode [ 138.660092] EXT4-fs (dm-22): mounted filesystem with ordered data mode [ 138.674436] kjournald starting. Commit interval 5 seconds [ 138.675145] EXT3 FS on xvda1, internal journal [ 138.675155] EXT3-fs: mounted filesystem with journal data mode. [ 138.728462] EXT4-fs (xvdc): mounted filesystem without journal [ 138.745406] EXT4-fs (dm-17): mounted filesystem with ordered data mode [ 138.748531] EXT4-fs (dm-18): mounted filesystem with ordered data mode [ 138.774667] EXT4-fs (dm-19): mounted filesystem with ordered data mode [ 138.780834] EXT4-fs (dm-2): Ignoring delalloc option - requested data journaling mode [ 138.781400] EXT4-fs (dm-2): mounted filesystem with journalled data mode [ 138.784700] EXT4-fs (dm-1): Ignoring delalloc option - requested data journaling mode [ 138.784773] EXT4-fs (dm-1): mounted filesystem with journalled data mode [ 138.790320] EXT4-fs (dm-4): Ignoring delalloc option - requested data journaling mode [ 138.790871] EXT4-fs (dm-4): mounted filesystem with journalled data mode [ 138.794955] EXT4-fs (dm-3): Ignoring delalloc option - requested dat
Processed: forcibly merging 613979 615966
Processing commands for cont...@bugs.debian.org: > forcemerge 613979 615966 Bug#613979: linux-image-2.6.37-1-amd64: kernel oops with snd-hda-intel: BUG: unable to handle kernel paging request at c90011c08000 Bug#615966: linux-image-2.6.37-2-amd64: suspend does not work Forcibly Merged 613979 615966. > thanks Stopping processing here. Please contact me if you need assistance. -- 613979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613979 615966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129899805428435.transcr...@bugs.debian.org
Processed: forcibly merging 603835 615969
Processing commands for cont...@bugs.debian.org: > forcemerge 603835 615969 Bug#603835: linux-image-2.6.32-5-amd64: page allocation failures while transferring data with virtio Bug#615969: linux-base: Tracking a moderate number of conenctions permanently kills network Forcibly Merged 603835 615969. > thanks Stopping processing here. Please contact me if you need assistance. -- 603835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603835 615969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129899786727634.transcr...@bugs.debian.org
Bug#615969: linux-base: Tracking a moderate number of conenctions permanently kills network
On Tue, Mar 01, 2011 at 02:09:36PM +0100, Alex wrote: > On Tue, Mar 01, 2011 at 12:55:19PM +, Ben Hutchings wrote: > > On Tue, 2011-03-01 at 12:28 +0100, Alex Bennee wrote: > > > Package: linux-base > > > Version: 2.6.32-30 > > > Severity: important > > > Tags: upstream > > > > > > > > > Starting up rtorrent on a number of torrents causes my VPS to loose > > > network > > > connectivity. > > [...] > > > > What virtualisation system are you using? Does the VPS use > > virtio_net? > > KVM and yes. > > I'm unsure if the problem is a result of conntrack fragmenting memory > as it's tracking all the extra connections or just exhaustion of the > virtio receive queue due to the peak in traffic as the torrents come > up. [...] This is a known bug and should be fixed soon in version 2.6.32-31 (Debian 6.0.1). Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110301164342.ge19...@decadent.org.uk
Re: [kernel] r16958 - in dists/trunk/linux-2.6/debian: . bin config templates/temp.image.plain
On Tue, Mar 01, 2011 at 05:44:45AM +, Ben Hutchings wrote: > + > +# This has not yet been reviewed > +Template: linux-image-=V/postinst/ignoring-ramdisk > +Type: error > +_Description: Ramdisk configuration must be updated > + Kernel packages will no longer run a specific ramdisk creator. The > + ramdisk creator package should install a script in > + /etc/kernel/postinst.d. Alternately, you can specify the command to > + create a ramdisk by setting the 'postinst_hook' variable in > + /etc/kernel-img.conf. Kill The last sentence, they are also deprecated, we should probably warn about them *now*. Plan is to really get rid of that file that nobody owns. -- maks -- 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/20110301155036.gc11...@vostochny.stro.at
Bug#615990: linux-image-2.6.37-2-amd64: b44 driver causes panic when using swiotlb
Package: linux-2.6 Version: 2.6.37-2 Severity: important Tags: upstream There is a know bug with the b44 driver that causes a kernel panic on boot. This may be limited to the Dell Vostro 1500 with more than 2 Gb of memory and 64 bit kernel. The following link describes the problem and a proposed patch: https://patchwork.kernel.org/patch/522971/ -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Vostro 1500 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A06 board_vendor: Dell Inc. board_name: 0NX907 board_version: ** Network interface configuration: auto lo iface lo inet loopback iface eth0 inet dhcp hwaddress ether 00:1E:37:86:3A:0F iface lowesguest inet dhcp pre-up ip link set wlan0 up wireless-mode master wireless-essid LOWESGUEST iface princeton inet dhcp pre-up ip link set wlan0 up wireless-mode master wireless-essid linksys iface cltnet inet dhcp pre-up ip link set wlan0 up wireless-mode master wireless-essid CLTNET iface conch inet dhcp pre-up ip link set wlan0 up wireless-mode master wireless-essid 'Conch Key Cottages' wireless-key *** iface serranet inet dhcp pre-up ip link set wlan0 up wpa-driver wext wpa-ssid: private wpa-psk: *** ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) Subsystem: Dell Device [1028:0228] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0228] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [8086:2a03] (rev 0c) Subsystem: Dell Device [1028:0228] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Device [1028:0228] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 02) Subsystem: Dell Device [1028:0228] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 02) (prog- if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 02) (prog- if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 02) (prog- if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2
Bug#615850: [linux-headers-2.6.37-1-amd64] can not boot the system
Hello I have the same thing. I m using grub2. But before 28/02/2011 I was able to boot on 2.6.37-1 with grub2. Thanks Thibault Cohen
Bug#615969: linux-base: Tracking a moderate number of conenctions permanently kills network
On Tue, Mar 01, 2011 at 12:55:19PM +, Ben Hutchings wrote: > On Tue, 2011-03-01 at 12:28 +0100, Alex Bennee wrote: > > Package: linux-base > > Version: 2.6.32-30 > > Severity: important > > Tags: upstream > > > > > > Starting up rtorrent on a number of torrents causes my VPS to loose network > > connectivity. > [...] > > What virtualisation system are you using? Does the VPS use > virtio_net? KVM and yes. I'm unsure if the problem is a result of conntrack fragmenting memory as it's tracking all the extra connections or just exhaustion of the virtio receive queue due to the peak in traffic as the torrents come up. Having said that even if virtio had to throw stuff away due to memory scarcity I would expect it to recover once memory returned. It's not as though the virtual machine hard OOOs. You can still log in via the serial console after the network has died. -- Alex, homepage: http://www.bennee.com/~alex/ Cleanliness is next to impossible. signature.asc Description: Digital signature
Bug#615972: firmware-bnx2: bnx2/bnx2-mips-09-6.2.1.fw missing
Package: firmware-bnx2 Version: 0.28 Severity: normal Hi, Linux kernel 2.6.38-rc6 (as currently in experimental) requires bnx2/bnx2-mips-09-6.2.1.fw for the bnx2 driver. Please, consider adding it in this package. Regards, Vincent -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-rc6-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash firmware-bnx2 depends on no packages. firmware-bnx2 recommends no packages. Versions of packages firmware-bnx2 suggests: ii initramfs-to 0.98.8 tools for generating an initramfs ii linux-image- 2.6.32-30 Linux 2.6.32 for 64-bit PCs ii linux-image- 2.6.37-1Linux 2.6.37 for 64-bit PCs ii linux-image- 2.6.38~rc6-1~experimental.1 Linux 2.6.38-rc6 for 64-bit PCs -- 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/20110301130834.1822.45012.reportbug@localhost.localdomain
Bug#615966: linux-image-2.6.37-2-amd64: suspend does not work
On Tue, 2011-03-01 at 12:51 +0100, Paul Menzel wrote: > Subject: linux-image-2.6.37-2-amd64: suspend does not work > Package: linux-2.6 > Version: 2.6.37-2 > Severity: normal > > Dear Debian folks, > > > suspending the system from the GNOME menu does not work and just > activates the GNOME Screensaver. Maybe it has something to do with this: [...] > ** Tainted: D (128) > * Kernel has oopsed before. > > ** Kernel log: > [ 29.953193] [] ? kernel_thread_helper+0x4/0x10 > [ 29.953193] [] ? kthread+0x0/0x82 > [ 29.953193] [] ? kernel_thread_helper+0x0/0x10 > [ 29.953193] Code: f4 01 00 00 ef 31 f6 48 89 df e8 29 dd ff ff 85 c0 0f 88 > 2b 03 00 00 48 89 ef e8 54 6c cc e0 8b 7b 40 e8 50 cf ba e0 48 8b 43 38 <66> > 8b 10 66 89 14 24 8b 43 14 83 e8 03 83 f8 01 77 32 31 d2 be > [ 29.953193] RIP [] azx_probe+0x3ad/0x86b [snd_hda_intel] > [ 29.953193] RSP > [ 29.953193] CR2: c90011b38000 > [ 29.953193] ---[ end trace 57a2073cba1d8976 ]--- [...] Which you already reported as bug #613979. Any problems that appear after a 'BUG'/'oops' message should be assumed to be a result of the original bug, and you should not report them separately. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 615969
Processing commands for cont...@bugs.debian.org: > tags 615969 + moreinfo Bug #615969 [linux-2.6] linux-base: Tracking a moderate number of conenctions permanently kills network Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 615969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129898413525503.transcr...@bugs.debian.org
Processed: reassign 615969 to linux-2.6
Processing commands for cont...@bugs.debian.org: > reassign 615969 linux-2.6 2.6.32-30 Bug #615969 [linux-base] linux-base: Tracking a moderate number of conenctions permanently kills network Bug reassigned from package 'linux-base' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-30. Bug #615969 [linux-2.6] linux-base: Tracking a moderate number of conenctions permanently kills network There is no source info for the package 'linux-2.6' at version '2.6.32-30' with architecture '' Unable to make a source version for version '2.6.32-30' Bug Marked as found in versions 2.6.32-30. > thanks Stopping processing here. Please contact me if you need assistance. -- 615969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129898406725040.transcr...@bugs.debian.org
Bug#615969: linux-base: Tracking a moderate number of conenctions permanently kills network
On Tue, 2011-03-01 at 12:28 +0100, Alex Bennee wrote: > Package: linux-base > Version: 2.6.32-30 > Severity: important > Tags: upstream > > > Starting up rtorrent on a number of torrents causes my VPS to loose network > connectivity. [...] What virtualisation system are you using? Does the VPS use virtio_net? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#615860: marked as done (bnx2 adapter periodically dropping received packets (pause frames))
Your message dated Tue, 01 Mar 2011 12:23:06 + with message-id <1298982186.3437.0.camel@localhost> and subject line Re: Bug#615860: bnx2 adapter periodically dropping received packets (pause frames) has caused the Debian Bug report #615860, regarding bnx2 adapter periodically dropping received packets (pause frames) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 615860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bnx2 Version: 2.6.32-5-amd64 Severity: normal Hi all, on my two Debian 6.0 (Squeeze) servers from HP (ProLiant DL380 G7) I have issues with the on-board Broadcom NetXtreme II BCM5709 Gigabit Ethernet adapters: they constantly drop received network packets, and the Cisco routing swtich 4948 is reporting pause frames coming from the network card during this time. I found the exact same bug report description including an upstream fix by David Miller here : https://bugzilla.redhat.com/show_bug.cgi?id=640026 They increased the ring buffer size as far as I understand. Please find further details concerning the network card and ethtool settings bekow. Kind regards, Joerg. cut - root@test-name:~# ethtool -a eth1 Pause parameters for eth1: Autonegotiate: on RX: on TX: on root@test-name:~# root@test-name:~# ethtool -c eth1 Coalesce parameters for eth1: Adaptive RX: off TX: off stats-block-usecs: 36 sample-interval: 0 pkt-rate-low: 0 pkt-rate-high: 0 rx-usecs: 18 rx-frames: 12 rx-usecs-irq: 18 rx-frames-irq: 2 tx-usecs: 80 tx-frames: 20 tx-usecs-irq: 18 tx-frames-irq: 2 rx-usecs-low: 0 rx-frame-low: 0 tx-usecs-low: 0 tx-frame-low: 0 rx-usecs-high: 0 rx-frame-high: 0 tx-usecs-high: 0 tx-frame-high: 0 root@test-name:~# lspci -v: -- 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) Subsystem: Hewlett-Packard Company NC382i Integrated Quad Port PCI Express Gigabit Server Adapter Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f400 (64-bit, non-prefetchable) [size=32M] [virtual] Expansion ROM at e410 [disabled] [size=64K] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] MSI: Enable- Count=1/16 Maskable- 64bit+ Capabilities: [a0] MSI-X: Enable+ Count=9 Masked- Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Device Serial Number 68-b5-99-ff-fe-6f-e5-f6 Capabilities: [110] Advanced Error Reporting Capabilities: [150] Power Budgeting Capabilities: [160] Virtual Channel Kernel driver in use: bnx2 cut - --- End Message --- --- Begin Message --- On Tue, 2011-03-01 at 12:24 +0100, Joerg Morbitzer wrote: [...] > Just for info: increasing the RX descriptor ring size to 1020 probably > fixed this issue, they was no further incident so far. > > Thanks for the hint, OK, closing. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#615969: linux-base: Tracking a moderate number of conenctions permanently kills network
Package: linux-base Version: 2.6.32-30 Severity: important Tags: upstream Starting up rtorrent on a number of torrents causes my VPS to loose network connectivity. Although conntrack only reports around 250 connections the kernel oops and the network will not respond any further. I can shell onto the machine via terminal but the only way to restore network connectivity so far is a reboot. Just before I loose connectivity I saw the following memory state: Slab Info nf_conntrack_expect 0 0168 241 : tunables000 : slabdata 0 0 0 nf_conntrack_c14c6a24262289240 171 : tunables000 : slabdata 17 17 0 Number of connections 252 Memory MemFree:9100 kB HighFree:300 kB LowFree:8800 kB SwapFree:1759612 kB HugePages_Free:0 The kernel shows a number of oops: Mar 1 10:01:45 socrates kernel: [ 1107.984836] swapper: page allocation failure. order:0, mode:0x20 Mar 1 10:01:45 socrates kernel: [ 1107.984846] Pid: 0, comm: swapper Not tainted 2.6.32-5-686 #1 Mar 1 10:01:45 socrates kernel: [ 1107.984848] Call Trace: Mar 1 10:01:45 socrates kernel: [ 1107.984879] [] ? __alloc_pages_nodemask+0x484/0x4d9 Mar 1 10:01:45 socrates kernel: [ 1107.984895] [] ? try_fill_recv+0x72/0x117 [virtio_net] Mar 1 10:01:45 socrates kernel: [ 1107.984900] [] ? virtnet_poll+0x45b/0x4d1 [virtio_net] Mar 1 10:01:45 socrates kernel: [ 1107.984914] [] ? hrtimer_get_next_event+0x8c/0xa0 Mar 1 10:01:45 socrates kernel: [ 1107.984934] [] ? net_rx_action+0x96/0x194 Mar 1 10:01:45 socrates kernel: [ 1107.984947] [] ? __do_softirq+0xaa/0x151 Mar 1 10:01:45 socrates kernel: [ 1107.984951] [] ? do_softirq+0x31/0x3c Mar 1 10:01:45 socrates kernel: [ 1107.984954] [] ? irq_exit+0x26/0x58 Mar 1 10:01:45 socrates kernel: [ 1107.984965] [] ? do_IRQ+0x78/0x89 Mar 1 10:01:45 socrates kernel: [ 1107.984969] [] ? common_interrupt+0x30/0x38 Mar 1 10:01:45 socrates kernel: [ 1107.984980] [] ? native_safe_halt+0x2/0x3 Mar 1 10:01:45 socrates kernel: [ 1107.984985] [] ? default_idle+0x3c/0x5a Mar 1 10:01:45 socrates kernel: [ 1107.984988] [] ? cpu_idle+0x89/0xa5 Mar 1 10:01:45 socrates kernel: [ 1107.984999] [] ? start_kernel+0x318/0x31d Mar 1 10:01:45 socrates kernel: [ 1107.985001] Mem-Info: Mar 1 10:01:45 socrates kernel: [ 1107.985006] DMA per-cpu: Mar 1 10:01:45 socrates kernel: [ 1107.985009] CPU0: hi:0, btch: 1 usd: 0 Mar 1 10:01:45 socrates kernel: [ 1107.985011] Normal per-cpu: Mar 1 10:01:45 socrates kernel: [ 1107.985013] CPU0: hi: 186, btch: 31 usd: 184 Mar 1 10:01:45 socrates kernel: [ 1107.985015] HighMem per-cpu: Mar 1 10:01:45 socrates kernel: [ 1107.985017] CPU0: hi: 18, btch: 3 usd: 17 Mar 1 10:01:45 socrates kernel: [ 1107.985023] active_anon:14275 inactive_anon:24343 isolated_anon:0 Mar 1 10:01:45 socrates kernel: [ 1107.985024] active_file:98037 inactive_file:97736 isolated_file:0 Mar 1 10:01:45 socrates kernel: [ 1107.985026] unevictable:0 dirty:24157 writeback:9 unstable:0 Mar 1 10:01:45 socrates kernel: [ 1107.985027] free:1323 slab_reclaimable:2077 slab_unreclaimable:1271 Mar 1 10:01:45 socrates kernel: [ 1107.985029] mapped:73828 shmem:3 pagetables:574 bounce:0 Mar 1 10:01:45 socrates kernel: [ 1107.985036] DMA free:3460kB min:64kB low:80kB high:96kB active_anon:864kB inactive_anon:1588kB active_file:4812kB inactive_file:4744kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15868kB mlocked:0kB dirty:16kB writeback:0kB mapped:132kB shmem:0kB slab_reclaimable:12kB slab_unreclaimable:60kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Mar 1 10:01:45 socrates kernel: [ 1107.985044] lowmem_reserve[]: 0 861 936 936 Mar 1 10:01:45 socrates kernel: [ 1107.985053] Normal free:1384kB min:3720kB low:4648kB high:5580kB active_anon:45276kB inactive_anon:83068kB active_file:361948kB inactive_file:360812kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:881880kB mlocked:0kB dirty:91924kB writeback:32kB mapped:279348kB shmem:0kB slab_reclaimable:8296kB slab_unreclaimable:5024kB kernel_stack:928kB pagetables:1264kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:2681 all_unreclaimable? no Mar 1 10:01:45 socrates kernel: [ 1107.985060] lowmem_reserve[]: 0 0 603 603 Mar 1 10:01:45 socrates kernel: [ 1107.985069] HighMem free:448kB min:128kB low:208kB high:288kB active_anon:10960kB inactive_anon:12716kB active_file:25388kB inactive_file:25388kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:77212kB mlocked:0kB dirty:4688kB writeback:4kB mapped:15832kB shmem:12kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:1032kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Mar 1 10:01:45 socrates kernel: [ 1107.985076] lowmem_reserve[]: 0 0 0 0
Bug#615966: linux-image-2.6.37-2-amd64: suspend does not work
Subject: linux-image-2.6.37-2-amd64: suspend does not work Package: linux-2.6 Version: 2.6.37-2 Severity: normal Dear Debian folks, suspending the system from the GNOME menu does not work and just activates the GNOME Screensaver. [ 9404.541049] PM: Syncing filesystems ... done. [ 9404.666574] PM: Preparing system for mem sleep [ 9404.33] Freezing user space processes ... [ 9424.680076] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0): [ 9424.680140] modprobe D 880132fc86c0 0 766 1 0x00820004 [ 9424.680278] 880132fc86c0 0082 880133a586f8 880132fcd100 [ 9424.680498] 000136c0 88012fa2dfd8 000136c0 000136c0 [ 9424.680717] 880132fc8998 880132fc89a0 880132fc86c0 000136c0 [ 9424.680936] Call Trace: [ 9424.680989] [] ? schedule_timeout+0x1d/0xb2 [ 9424.681043] [] ? check_preempt_wakeup+0x123/0x192 [ 9424.681097] [] ? check_preempt_curr+0x25/0x62 [ 9424.681150] [] ? wait_for_common+0xd1/0x14e [ 9424.681203] [] ? default_wake_function+0x0/0xe [ 9424.681255] [] ? work_on_cpu+0x94/0xa4 [ 9424.681308] [] ? local_pci_probe+0x0/0x92 [ 9424.681361] [] ? sysfs_do_create_link+0x148/0x1a2 [ 9424.681422] [] ? pci_device_probe+0xa6/0xef [ 9424.681475] [] ? driver_sysfs_add+0x66/0x8d [ 9424.681527] [] ? driver_probe_device+0xa8/0x138 [ 9424.681579] [] ? __driver_attach+0x4f/0x6f [ 9424.681641] [] ? __driver_attach+0x0/0x6f [ 9424.681701] [] ? bus_for_each_dev+0x44/0x78 [ 9424.681763] [] ? bus_add_driver+0xa8/0x1f0 [ 9424.681825] [] ? driver_register+0x90/0xf8 [ 9424.681887] [] ? __pci_register_driver+0x4e/0xc0 [ 9424.681954] [] ? alsa_card_azx_init+0x0/0x20 [snd_hda_intel] [ 9424.682026] [] ? do_one_initcall+0x78/0x131 [ 9424.682089] [] ? sys_init_module+0x97/0x1d3 [ 9424.682150] [] ? cstar_dispatch+0x7/0x2e [ 9424.682263] [ 9424.682317] Restarting tasks ... done. I have not yet tested other methods or another system. It works using DebPkg:linux-image-2.6.32-5-amd64. It could be and probably is related to my other problem reported in #613979 [1]. I wanted just to report it to the BTS and will update #613979 as soon as possible. Thanks, Paul [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613979 -- Package-specific info: ** Version: Linux version 2.6.37-2-amd64 (Debian 2.6.37-2) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-11) ) #1 SMP Sun Feb 27 12:32:01 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.37-2-amd64 root=/dev/mapper/speicher-root ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 29.953193] [] ? kernel_thread_helper+0x4/0x10 [ 29.953193] [] ? kthread+0x0/0x82 [ 29.953193] [] ? kernel_thread_helper+0x0/0x10 [ 29.953193] Code: f4 01 00 00 ef 31 f6 48 89 df e8 29 dd ff ff 85 c0 0f 88 2b 03 00 00 48 89 ef e8 54 6c cc e0 8b 7b 40 e8 50 cf ba e0 48 8b 43 38 <66> 8b 10 66 89 14 24 8b 43 14 83 e8 03 83 f8 01 77 32 31 d2 be [ 29.953193] RIP [] azx_probe+0x3ad/0x86b [snd_hda_intel] [ 29.953193] RSP [ 29.953193] CR2: c90011b38000 [ 29.953193] ---[ end trace 57a2073cba1d8976 ]--- [ 30.487762] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input5 [ 209.332709] EXT3-fs (dm-1): using internal journal [ 209.671234] loop: module loaded [ 211.573030] Adding 4194300k swap on /dev/mapper/speicher-swap. Priority:-1 extents:1 across:4194300k [ 213.161155] fuse init (API version 7.15) [ 213.300209] EXT3-fs: barriers not enabled [ 213.302701] kjournald starting. Commit interval 5 seconds [ 213.307193] EXT3-fs (md0): using internal journal [ 213.307336] EXT3-fs (md0): mounted filesystem with ordered data mode [ 213.377217] EXT3-fs: barriers not enabled [ 213.380248] kjournald starting. Commit interval 5 seconds [ 213.407184] EXT3-fs (dm-6): using internal journal [ 213.407333] EXT3-fs (dm-6): mounted filesystem with ordered data mode [ 213.523624] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 213.527164] SGI XFS Quota Management subsystem [ 213.571537] XFS mounting filesystem dm-7 [ 215.961722] Ending clean XFS mount for filesystem: dm-7 [ 216.011066] XFS mounting filesystem dm-8 [ 216.346703] Ending clean XFS mount for filesystem: dm-8 [ 216.400411] REISERFS (device dm-5): found reiserfs format "3.6" with standard journal [ 216.400525] REISERFS (device dm-5): using ordered data mode [ 216.411144] REISERFS (device dm-5): journal params: device dm-5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [ 216.412646] REISERFS (device dm-5): checking transaction log (dm-5) [ 216.
Bug#615860: bnx2 adapter periodically dropping received packets (pause frames)
On 02/28/2011 03:21 PM, Joerg Morbitzer wrote: > On 02/28/2011 03:14 PM, Ben Hutchings wrote: >> On Mon, 2011-02-28 at 14:22 +0100, Joerg Morbitzer wrote: >>> Package: bnx2 >>> Version: 2.6.32-5-amd64 >>> Severity: normal >>> >>> >>> Hi all, >>> >>> on my two Debian 6.0 (Squeeze) servers from HP (ProLiant DL380 G7) I have >>> issues with the on-board Broadcom NetXtreme II BCM5709 Gigabit >>> Ethernet adapters: they constantly drop received network packets, and the >>> Cisco routing swtich 4948 is reporting pause frames coming from the >>> network card during this time. >>> >>> I found the exact same bug report description including an upstream fix >>> by David Miller here : >> >> I think that's a different bug. And I don't see any fix by David Miller >> there. > > Hi Ben, > > thanks for your replay. I thought there was an upstream fix due to this > answer from Andy Gospodarek (Comment 30 in the Red Hat bug report). > >> >>> https://bugzilla.redhat.com/show_bug.cgi?id=640026 >>> >>> They increased the ring buffer size as far as I understand. >> [...] >> >> They increased the maximum allowed RX descriptor ring size. You should >> first try changing the value to the current maximum yourself, with >> ethtool -C. > > Ok, thanks for the hint with "ethtool -G", I will try to increase the RX > value from 255 to the maximum of 1020. Just for info: increasing the RX descriptor ring size to 1020 probably fixed this issue, they was no further incident so far. Thanks for the hint, kind regards, Joerg. -- 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/4d6cd76d.7090...@morbitzer.de
Bug#615962: linux-image-2.6.37-1-amd64: can not boot after updating to a new kernel 2-6.37-1
forcemerge 615806 615962 quit Hi, Pere Nubiola i Radigales wrote: > when I am install de new linux image version and reboot de computer, system > hans with this error: > [0.788804] Kernel panic - not syncing: No init found. Try passing init= > option to kernel. See Linux Documentation/init.txt for guidance. > [0.788852] Pid: 1, comm: swapper Not Tainted 2.6.37-1-amd64 #1 > [0.788890] Call Trace: > [0.788929] [] ? panic+0x92/0x1a1 > [0.788968] [] ? init_post+0xc0/0xc2 > [0.789007] [] ? kernel_init+0x1e1/0x1ec > [0.789047] [] ? kernel_thread_helper+0x4/0x10 > [0.789086] [] ? kernel_init+0x0/0x1ec > [0.789124] [] ? kernel_thread_helper+0x0/0x10 > > The computer boot well with the previous version 2.6.32-5 You already filed this. It was a libc bug. Update libc and reinstall the kernel and it should work again. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2011030626.GA32274@elie
Bug#615962: linux-image-2.6.37-1-amd64: can not boot after updating to a new kernel 2-6.37-1
Package: linux-2.6 Version: 2.6.37-1 Severity: important when I am install de new linux image version and reboot de computer, system hans with this error: [0.788804] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. [0.788852] Pid: 1, comm: swapper Not Tainted 2.6.37-1-amd64 #1 [0.788890] Call Trace: [0.788929] [] ? panic+0x92/0x1a1 [0.788968] [] ? init_post+0xc0/0xc2 [0.789007] [] ? kernel_init+0x1e1/0x1ec [0.789047] [] ? kernel_thread_helper+0x4/0x10 [0.789086] [] ? kernel_init+0x0/0x1ec [0.789124] [] ? kernel_thread_helper+0x0/0x10 The computer boot well with the previous version 2.6.32-5 -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: OEM product_name: OEM product_version: OEM chassis_vendor: OEM chassis_version: OEM bios_vendor: Phoenix Technologies, LTD bios_version: 6.00 PG board_vendor: Foxconn board_name: G31MX Series board_version: ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 10) Subsystem: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 10) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:0df7] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01) (prog-if 00 [UHCI]) Subsystem: Foxconn International, Inc. Device [105b:0df7] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:0df7] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: Foxconn International, Inc. Device [105b:0df7] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR-
