Bug#463606: Does the 2.6.24 -486 kernel work on your C3 box?
Yes, -486 kernel booted properly. I forgot that 2.6.22 kernel I have used before was also of -486 variety. On Feb 13, 2008 9:43 PM, Graham [EMAIL PROTECTED] wrote: Hi Arie I wonder if your C3 suffers from the same limitation as Joey's TM5800. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464962#75 Does the -486 kernel boot correctly on your C3? -- graham -- Arie
Bug#464197: linux-image-2.6.24-1-686: module snd-cs46xx still missing
severity 464197 wishlist tags 464197 help thanks On Wed, Feb 13, 2008 at 01:33:05PM -0600, Jan Hetges wrote: could please someone reenable snd-cs46xx ? No. Not until you provided a patch which seperates the firmware. Bastian -- Prepare for tomorrow -- get ready. -- Edith Keeler, The City On the Edge of Forever, stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#464197: linux-image-2.6.24-1-686: module snd-cs46xx still missing
Processing commands for [EMAIL PROTECTED]: severity 464197 wishlist Bug#464197: snd-cs46xx.ko module seems to be missing from linux-image-2.6.24-1-686 Severity set to `wishlist' from `important' tags 464197 help Bug#464197: snd-cs46xx.ko module seems to be missing from linux-image-2.6.24-1-686 There were no tags set. Tags added: help thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 465677 is normal
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 severity 465677 normal Bug#465677: linux-source-2.6.24 Severity set to `normal' from `important' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: Firewire support in lenny
Hi, On Tuesday 12 February 2008 12:31, Guus Sliepen wrote: I do not see why making the old stack available again, but blacklisted by default, discourages testing of the newer stack. If you have both available, then yes, users can switch to the new stack more easily, but at least they will still be using Debian kernel packages, and they can switch back to the juju stack just as well. If you do not make this option available, those who have problems with the new stack will have to compile their own kernels, and then they will not track the Debian kernel packages anymore. I see this happening all around... (users compiling their own kernels cause they have to and stop tracking debian kernels) Please make the old stack available. regards, Holger pgpA1FYBwoopT.pgp Description: PGP signature
Re: bnx2 request_firmware patch - first try
On Thu, Feb 07, 2008 at 04:10:56PM +0100, Bastian Blank wrote:
This is the first version of the bnx2 request_firmware patch. It works
with the 4.0.5 firmware from the bnx2 version in 2.6.25.
Second version, it fixes the problems and changes the firmware names a
little bit.
I also attached the updated firmware extractor.
Bastian
--
Our missions are peaceful -- not for conquest. When we do battle, it
is only because we have no choice.
-- Kirk, The Squire of Gothos, stardate 2124.5
diff --git a/drivers/net/bnx2.c b/drivers/net/bnx2.c
index 8b552c6..ec72b56 100644
--- a/drivers/net/bnx2.c
+++ b/drivers/net/bnx2.c
@@ -46,11 +46,10 @@
#include linux/crc32.h
#include linux/prefetch.h
#include linux/cache.h
-#include linux/zlib.h
+#include linux/firmware.h
#include bnx2.h
-#include bnx2_fw.h
-#include bnx2_fw2.h
+#include bnx2_fw_file.h
#define FW_BUF_SIZE 0x1
@@ -58,12 +57,20 @@
#define PFX DRV_MODULE_NAME :
#define DRV_MODULE_VERSION 1.7.3
#define DRV_MODULE_RELDATE January 29, 2008
+#define FW_FILE_06 bnx2-06-4.0.5.fw
+#define FW_FILE_09 bnx2-09-4.0.5.fw
#define RUN_AT(x) (jiffies + (x))
/* Time in jiffies before concluding the transmitter is hung. */
#define TX_TIMEOUT (5*HZ)
+#ifdef DEBUG
+# define DPRINTK(fmt, args...) printk(KERN_DEBUG %s: fmt, __FUNCTION__ , ## args)
+#else
+# define DPRINTK(fmt, args...)
+#endif
+
static const char version[] __devinitdata =
Broadcom NetXtreme II Gigabit Ethernet Driver DRV_MODULE_NAME v DRV_MODULE_VERSION ( DRV_MODULE_RELDATE )\n;
@@ -71,6 +78,8 @@ MODULE_AUTHOR(Michael Chan [EMAIL PROTECTED]);
MODULE_DESCRIPTION(Broadcom NetXtreme II BCM5706/5708 Driver);
MODULE_LICENSE(GPL);
MODULE_VERSION(DRV_MODULE_VERSION);
+MODULE_FIRMWARE(FW_FILE_06);
+MODULE_FIRMWARE(FW_FILE_09);
static int disable_msi = 0;
@@ -3161,26 +3170,32 @@ bnx2_set_rx_mode(struct net_device *dev)
spin_unlock_bh(bp-phy_lock);
}
-static void
-load_rv2p_fw(struct bnx2 *bp, __le32 *rv2p_code, u32 rv2p_code_len,
- u32 rv2p_proc)
+static int
+load_rv2p_fw(struct bnx2 *bp, u32 rv2p_proc, const struct bnx2_fw_file_section *fw_section)
{
- int i;
+ int i, len, offset;
+ u32 *data;
u32 val;
+ len = be32_to_cpu(fw_section-len);
+ offset = be32_to_cpu(fw_section-offset);
+
+ if (!len || !offset || len + offset bp-firmware-size)
+ return -EINVAL;
+ DPRINTK(load rv2p firmware with length %u from file offset %u\n, len, offset);
+
+ data = (u32 *)(bp-firmware-data + offset);
- for (i = 0; i rv2p_code_len; i += 8) {
- REG_WR(bp, BNX2_RV2P_INSTR_HIGH, le32_to_cpu(*rv2p_code));
- rv2p_code++;
- REG_WR(bp, BNX2_RV2P_INSTR_LOW, le32_to_cpu(*rv2p_code));
- rv2p_code++;
+ for (i = 0; i (len / 4); i += 2) {
+ REG_WR(bp, BNX2_RV2P_INSTR_HIGH, be32_to_cpu(data[i]));
+ REG_WR(bp, BNX2_RV2P_INSTR_LOW, be32_to_cpu(data[i+1]));
if (rv2p_proc == RV2P_PROC1) {
- val = (i / 8) | BNX2_RV2P_PROC1_ADDR_CMD_RDWR;
+ val = (i / 2) | BNX2_RV2P_PROC1_ADDR_CMD_RDWR;
REG_WR(bp, BNX2_RV2P_PROC1_ADDR_CMD, val);
}
else {
- val = (i / 8) | BNX2_RV2P_PROC2_ADDR_CMD_RDWR;
+ val = (i / 2) | BNX2_RV2P_PROC2_ADDR_CMD_RDWR;
REG_WR(bp, BNX2_RV2P_PROC2_ADDR_CMD, val);
}
}
@@ -3192,14 +3207,18 @@ load_rv2p_fw(struct bnx2 *bp, __le32 *rv2p_code, u32 rv2p_code_len,
else {
REG_WR(bp, BNX2_RV2P_COMMAND, BNX2_RV2P_COMMAND_PROC2_RESET);
}
+
+ return 0;
}
static int
-load_cpu_fw(struct bnx2 *bp, struct cpu_reg *cpu_reg, struct fw_info *fw)
+load_cpu_fw(struct bnx2 *bp, struct cpu_reg *cpu_reg,
+ const struct bnx2_fw_file_entry *fw_entry)
{
+ u32 addr, len, file_offset;
u32 offset;
u32 val;
- int rc;
+ u32 *data;
/* Halt the CPU. */
val = bnx2_reg_rd_ind(bp, cpu_reg-mode);
@@ -3208,64 +3227,87 @@ load_cpu_fw(struct bnx2 *bp, struct cpu_reg *cpu_reg, struct fw_info *fw)
bnx2_reg_wr_ind(bp, cpu_reg-state, cpu_reg-state_value_clear);
/* Load the Text area. */
- offset = cpu_reg-spad_base + (fw-text_addr - cpu_reg-mips_view_base);
- if (fw-gz_text) {
+ addr = be32_to_cpu(fw_entry-text.addr);
+ len = be32_to_cpu(fw_entry-text.len);
+ file_offset = be32_to_cpu(fw_entry-text.offset);
+ data = (u32 *)(bp-firmware-data + file_offset);
+ DPRINTK(load text section to %x with length %u from file offset %x\n, addr, len, file_offset);
+
+ offset = cpu_reg-spad_base + (addr - cpu_reg-mips_view_base);
+ if (len) {
int j;
- rc = zlib_inflate_blob(fw-text, FW_BUF_SIZE, fw-gz_text,
- fw-gz_text_len);
- if (rc 0)
- return rc;
-
- for (j = 0; j (fw-text_len / 4); j++, offset += 4) {
- bnx2_reg_wr_ind(bp, offset, le32_to_cpu(fw-text[j]));
+ for (j = 0; j (len / 4); j++, offset += 4) {
+ bnx2_reg_wr_ind(bp, offset, be32_to_cpu(data[j]));
}
}
/* Load the Data area. */
- offset = cpu_reg-spad_base + (fw-data_addr - cpu_reg-mips_view_base);
- if (fw-data) {
+ addr = be32_to_cpu(fw_entry-data.addr);
+ len = be32_to_cpu(fw_entry-data.len);
+ file_offset = be32_to_cpu(fw_entry-data.offset);
+
Bug#464962: Test app won't compile on etch
The above test program won't compile on Etch; it seems that as from binutils 2.17 doesn't understand the long NOP instructions. Could the opcode bytes be written literally? (For example, on old Watcom compilers, I had to write the CPUID instruction as db 0fh, 0a2h.) -- graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463244: solved :-)
just upgraded to linux-image-2.6.24-1-686 and it worked fine :-) i had to down grade the firmware for it to work since i have misunderstood the instructions that where posted there three weeks ago (on b43 site : http://linuxwireless.org/en/users/Drivers/b43 ) but i just saw that they change the instruction :-) so all is just fine. i have a pcmcia Linksys WPC54G (ver.1.2) PC Card (model 4306) 0x4320 0x1737 0x4320 this is the messages i was getting just after the kernel upgrade: b43-phy0 ERROR: YOUR FIRMWARE IS TOO NEW. Please downgrade your firmware. b43-phy0 ERROR: Use this firmware tarball: http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2 b43-phy0 ERROR: Use this b43-fwcutter tarball: http://bu3sch.de/b43/fwcutter/b43-fwcutter-009.tar.bz2 b43-phy0 ERROR: Read, understand and _do_ what this message says, please. so i downloaded the firmware and the extraction tool and installed it. also, i am not getting the ide_cd errors (kernel panic) any more while loading this kernel. (i was getting them in the last 3 updates of the TRUNK versions) so...let us close this issue :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463244: marked as done (b43-phy4 ERROR: PHY transmission error ( authenticationtimed out))
Your message dated Thu, 14 Feb 2008 16:32:04 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#463244: solved :-) has caused the Debian Bug report #463244, regarding b43-phy4 ERROR: PHY transmission error ( authenticationtimed out) 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 [EMAIL PROTECTED] immediately.) -- 463244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463244 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-1~experimental.2~snapshot.10239 Severity: normal --- Please enter the report below this line. --- i use debian sid (updated) on a Compaq presarion 1500 with linksys wpc54g pcmcia nic - Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) Linksys WPC54G (ver.1.2) PC Card 4306 0x4320 0x1737 0x4320 i was using kernel 2.6.23 which was working fine with this card and now that i have upgraded to 2.6.24 i can not connect to the AP (linksys wrt54gl) dmesg: pccard: CardBus card inserted into slot 0 PCI: Enabling device :03:00.0 ( - 0002) ACPI: PCI Interrupt :03:00.0[A] - Link [C0B8] - GSI 11 (level, low) - IRQ 11 PCI: Setting latency timer of device :03:00.0 to 64 b43-phy3: Broadcom 4306 WLAN found phy3: Selected rate control algorithm 'simple' ssb: Sonics Silicon Backplane found on PCI device :03:00.0 udev: renamed network interface wmaster0 to eth2 b43-phy4: Broadcom 4306 WLAN found phy4: Selected rate control algorithm 'simple' udev: renamed network interface wmaster0 to eth2 input: b43-phy4 as /class/input/input16 Registered led device: b43-phy4:tx Registered led device: b43-phy4:rx Registered led device: b43-phy4:radio ADDRCONF(NETDEV_UP): wlan0_rename: link is not ready b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: authentication with AP 00:18:39:bc:52:67 timed out wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 printk: 29 messages suppressed. b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: authentication with AP 00:18:39:bc:52:67 timed out printk: 6 messages suppressed. b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error printk: 16 messages suppressed. b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error usb 1-1: USB disconnect, address 3 usb 1-2: USB disconnect, address 4 Clocksource tsc unstable (delta = -390098523 ns) printk: 16 messages suppressed. b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error b43-phy4 ERROR: PHY transmission error wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 printk: 1 messages suppressed. b43-phy4 ERROR: PHY transmission error wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: authenticate
Bug#465760: initramfs-tools: Needs to create /lib/modules/${version}/modules.dep in initramfs in case no modules are required
Package: initramfs-tools
Version: 0.91d
Severity: minor
Tags: patch
this bug is un update to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393688
If your kernel configuration is such that no modules are required in
the initramfs then /lib/modules/${version}/modules.dep is never
created and on boot
you get some noisy message:
FATAL: Could not load /lib/modules/${version}/modules.dep: No such
file or directory
(several times)
the dirty fix is below
--- mkinitramfs 2008-02-14 10:56:55.0 -0500
+++ /usr/sbin/mkinitramfs 2008-02-14 11:18:49.0 -0500
@@ -183,6 +183,7 @@
for d in bin conf/conf.d etc lib/modules sbin scripts ${MODULESDIR}; do
mkdir -p ${DESTDIR}/${d}
done
+touch ${DESTDIR}/${MODULESDIR}/modules.dep
# MODULES=list case. Always honour.
for x in ${CONFDIR}/modules /usr/share/initramfs-tools/modules.d/*; do
Debian Installer Lenny Beta1: Status Update 1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, This mail tries to inform interest people where we are and what's missing. As you can bet, it's a long mail. Please respect the reply-to header and please follow up to debian-boot mailing list. Bellow is the timeline we're following. +--+---+ | Date | What happens | +--+---+ |February 5, 2007 |translation update request is send | +--+---+ |February 15, 2007 |mass upload of translation updates | = +--+---+ |February 18, 2007 |mass migration of udebs| +--+---+ |February 19, 2007 |debian-installer is uploaded | +--+---+ |February 21, 2007 |daily images are changed to use lenny installer| +--+---+ |February 23, 2007 |test of images starts | +--+---+ |March 1, 2007 |final image builds | +--+---+ |March 3, 2007 |planned release date | +--+---+ Translations are synced on svn repository, from master files, at 22:47 UTC and all porters and main maintainers of packages should check their packages and see if they have pending l10n updates after the sync commit. There're 51 packages (right now) that falls into this category. You can check the full list using the script available in our svn repository at scripts/l10n/list-unreleased-l10n-only. All team help on this is important since it's a huge list of packages. Today I've also uploaded tasksel reverting the xorg related change otherwise we wouldn't be able to use the lastest tasksel version of tasks for Beta1. This should go to testing in a cuple of days. Another thing that we all need to get done is the release announce text. A draft has been written and team people is welcome to send improvements for it. Several XXX items remain open to be fixed there and I'm sure people can help to get it done. Bellow goes the current general status update. New stuff = * All architectures have moved to 2.6.22; Solved issues = * Progress bar will not restart from zero several times during the phase where the base system is installed. General issues == * Time out on NTP server connection is too long (#448871]) * option to use relatime does not work because busybox' mount command does not support it (#460824]) Kernel status = * linux-modules-di-m68k-2.6 isn't uploaded due the lack of loop-aes and squashfs since linux-headers lack modules.lds files (#402061). Blockers for Beta1 release == * loop-aes is missing in testing (debs, not udebs) Blockers for final release == * linux-libc-dev has type declaration conflict (#434040, #435700) (ignored for beta1 since a workaround is used) * m68k has floppy flavors disabled due a full-disk. (ignored since m68k isn't a release-set arch) * installer doesn't start on mips and mipsel if using mklibs (#445507) (ignored for beta1 since a workaround is used) * dependencies of excluded packages on the cd, making netinst huge (#410418) (worked around in debian-cd by no longer including alternative dependencies by default) I hope it gives a better overview of all things happening behind the scenes and what you can do to help us to get the release out. Cheers, Otavio Salvador Debian Installer Release Manager -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8+ http://mailcrypt.sourceforge.net/ iD8DBQFHtH3aLqiZQEml+FURAslpAKCo6u4NDOrtQgmA8KVwIc8QpYWpGQCdFePQ qOxMLI+PLvVVPiHsaIRuvIs= =x5zo -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463606: More Virtual PC results
I tried the long NOP test application on Virtual PC... http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464962#143 and was very surprised to see it return yes. It appears that the long NOP instruction executes correctly inside the test program, but not during boot. This doesn't make sense to me. Because MS VPC seems to be a special case, I suggest that we use this bug (#463606) for MS VPC only, and use bug #464962 for further discussion of this issue on real CPUs. Also, I could be mistaken, but I think that the failure case for the -486 kernel on MS VPC is a completely separate issue. In MS VPC, cat /proc/cpuinfo shows information about my real CPU. The only oddity inside MS VPC is that some flags that are actually supported by this processor are missing. Here's a transcription: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 9 model name : Intel(R) Pentium(R) M processor 1400MHz stepping : 5 cpu MHz : 1307.580 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme pse tsc msr cx8 sep pge cmov acpi mmx fxsr sse sse2 up bogomips : 2679.67 clflush size : 32 -- graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465775: b43: ethX is renamed to wlan0_rename when b43 wireless module loads
Package: linux-image-2.6.24-1-686 Version: 2.6.24-4 Severity: important File: b43 *** Please type your report below this line *** when system loads, udev: renamed network interface wmaster0 to eth2 but later on, when i am logged into KDE. i notice i have another wireless interface : wlan0_rename and eth2 is empty. wlan0_rename works fine but where is it coming from ? (i want my eth2 back ;-) laptop:~# ifconfig eth1 Link encap:Ethernet HWaddr 00:08:02:ba:ac:f9 inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:701 errors:0 dropped:0 overruns:0 frame:0 TX packets:472 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:964853 (942.2 KiB) TX bytes:34913 (34.0 KiB) eth2 Link encap:UNSPEC HWaddr 00-12-17-B6-8D-E5-77-6C-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:300 errors:0 dropped:0 overruns:0 frame:0 TX packets:300 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22593 (22.0 KiB) TX bytes:22593 (22.0 KiB) wlan0_rename Link encap:Ethernet HWaddr 00:12:17:b6:8d:e5 inet addr:192.168.1.106 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::212:17ff:feb6:8de5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:323 errors:0 dropped:0 overruns:0 frame:0 TX packets:222 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:197199 (192.5 KiB) TX bytes:45976 (44.8 KiB) cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 auto lo # The primary network interface allow-hotplug eth1 iface eth0 inet dhcp iface eth1 inet dhcp #auto eth1 iface eth2 inet dhcp ##post-up cp -f /etc/resolv.conf.netvision /etc/resolv.conf wireless-channel 11 wireless-essid kaval wireless-ap auto wireless-mode managed auto eth2 # added to support new b43 module (2.6.24-X) iface wlan0_rename inet dhcp wireless-essid kaval ##post-up cp -f /etc/resolv.conf.netvision /etc/resolv.conf wireless-channel 11 wireless-mode managed wireless-ap auto auto wlan0_rename -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Mon Feb 11 14:37:45 UTC 2008 ** Command line: root=/dev/hda1 ro ** Tainted: G (128) ** Kernel log: b43-phy1: Broadcom 4306 WLAN found phy1: Selected rate control algorithm 'simple' udev: renamed network interface wmaster0 to eth2 input: b43-phy1 as /class/input/input18 Registered led device: b43-phy1:tx Registered led device: b43-phy1:rx Registered led device: b43-phy1:radio wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: RX authentication from 00:18:39:bc:52:67 (alg=0 transaction=2 status=0) wlan0_rename: authenticated wlan0_rename: associate with AP 00:18:39:bc:52:67 wlan0_rename: RX AssocResp from 00:18:39:bc:52:67 (capab=0x1 status=0 aid=1) wlan0_rename: associated wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: RX authentication from 00:18:39:bc:52:67 (alg=0 transaction=2 status=0) wlan0_rename: authenticated wlan0_rename: associate with AP 00:18:39:bc:52:67 wlan0_rename: RX ReassocResp from 00:18:39:bc:52:67 (capab=0x1 status=0 aid=1) wlan0_rename: associated wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: RX authentication from 00:18:39:bc:52:67 (alg=0 transaction=2 status=0) wlan0_rename: authenticated wlan0_rename: associate with AP 00:18:39:bc:52:67 wlan0_rename: RX ReassocResp from 00:18:39:bc:52:67 (capab=0x1 status=0 aid=1) wlan0_rename: associated NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth1: link is not ready wlan0_rename: no IPv6 routers present wlan0_rename: RX deauthentication from 00:18:39:bc:52:67 (reason=7) wlan0_rename: deauthenticated wlan0_rename: authenticate with AP 00:18:39:bc:52:67 wlan0_rename: RX authentication from 00:18:39:bc:52:67 (alg=0 transaction=2 status=0) wlan0_rename: authenticated wlan0_rename: associate with AP 00:18:39:bc:52:67 wlan0_rename: RX ReassocResp from
Please add following hint to block linux-2.6 until Beta1 is out
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello RM and SRM teams, I hereby ask for a block on linux-2.6 source package until d-i Beta1 gets out. If it migrates before we do the final images we can need to delay d-i release. As discussed[1] previously at debian-boot we've decided to stay at 2.6.22 for this release and do a release as fast as possible with 2.6.24. 1. http://lists.debian.org/debian-boot/2008/02/msg00012.html Cheers, - -- O T A V I OS A L V A D O R - - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - - Microsoft sells you Windows ... Linux gives you the whole house. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8+ http://mailcrypt.sourceforge.net/ iD8DBQFHtI1OLqiZQEml+FURAt0AAJ43VceXRalH3Sgvr+dDViwn7C2jUQCdEEa8 o1HfEFYnT4OUdIZw8HddUtw= =FHpN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Changes for 2.6.25
Hi folks I intend to do the following changes to the linux-2.6 core before 2.6.25. Generic: - Deprecate kernel-package method. It is still used for alpha, arm, armel, hppa, ia64, mips, mipsel, sparc. It will be removed after the 2.6.25 release to make it possible to use features like out-of-tree builds. - Drop ext2 built-in exception for arm and mips. Patchsystem: - Use new patch series infrastructure (used for genorig already). - Make patches mutal. This removes the abbility to use linux-2.6 as source for the kernel udebs. Further changes coming. Bastian -- Conquest is easy. Control is not. -- Kirk, Mirror, Mirror, stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please add following hint to block linux-2.6 until Beta1 is out
On Thu, 14 Feb 2008, Otavio Salvador wrote: Hello RM and SRM teams, I hereby ask for a block on linux-2.6 source package until d-i Beta1 gets out. If it migrates before we do the final images we can need to delay d-i release. nacked as maintainer, you are blocking for more then 2 weeks linux-2.6 migration to testing. we need massife testing of 2.6.24 for etch+half, sid is not enough. also 2.6.22 was meant to be ready 4 month ago, sorry but that schedule is over. As discussed[1] previously at debian-boot we've decided to stay at 2.6.22 for this release and do a release as fast as possible with 2.6.24. 1. http://lists.debian.org/debian-boot/2008/02/msg00012.html very bad decision 2.6.24 is needed for a lot of recent hardware, d-i doesn't install on those. signature.asc Description: Digital signature
Re: Please add following hint to block linux-2.6 until Beta1 is out
Hi, On Thu Feb 14, 2008 at 16:49:51 -0200, Otavio Salvador wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello RM and SRM teams, I hereby ask for a block on linux-2.6 source package until d-i Beta1 gets out. If it migrates before we do the final images we can need to delay d-i release. ACK from SRM side. -- Martin Zobel-Helas [EMAIL PROTECTED] | Debian Release Team Member Debian GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please add following hint to block linux-2.6 until Beta1 is out
On Thu, Feb 14, 2008 at 05:17:08PM -0200, Otavio Salvador wrote: Mike Hommey [EMAIL PROTECTED] writes: On Thu, Feb 14, 2008 at 07:56:55PM +0100, maximilian attems wrote: On Thu, 14 Feb 2008, Otavio Salvador wrote: Hello RM and SRM teams, I hereby ask for a block on linux-2.6 source package until d-i Beta1 gets out. If it migrates before we do the final images we can need to delay d-i release. nacked as maintainer, you are blocking for more then 2 weeks linux-2.6 migration to testing. we need massife testing of 2.6.24 for etch+half, sid is not enough. also 2.6.22 was meant to be ready 4 month ago, sorry but that schedule is over. As discussed[1] previously at debian-boot we've decided to stay at 2.6.22 for this release and do a release as fast as possible with 2.6.24. 1. http://lists.debian.org/debian-boot/2008/02/msg00012.html very bad decision 2.6.24 is needed for a lot of recent hardware, d-i doesn't install on those. ... and etch+1 2.6.24 should just be built with the proper options to still include deprecated /proc/acpi stuff (and probably disable the new interfaces for them, too, as it can have bad side effects on, e.g. hal (though I don't know if etch's hal supports /sys/class/power_supply)). This needs to be done, specially for Etch+Half kernels. It has been done for sid kernels in 2.6.24-3 upload. Though 2.6.24-3 onwards also includes the /sys/class/power_supply stuff, and unless hal gets fixed (and it is fixed in upstream git), a few software will report twice as much batteries as really present. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please add following hint to block linux-2.6 until Beta1 is out
maximilian attems [EMAIL PROTECTED] writes: On Thu, 14 Feb 2008, Otavio Salvador wrote: Hello RM and SRM teams, I hereby ask for a block on linux-2.6 source package until d-i Beta1 gets out. If it migrates before we do the final images we can need to delay d-i release. nacked as maintainer, you are blocking for more then 2 weeks linux-2.6 migration to testing. we need massife testing of 2.6.24 for etch+half, sid is not enough. also 2.6.22 was meant to be ready 4 month ago, sorry but that schedule is over. As discussed[1] previously at debian-boot we've decided to stay at 2.6.22 for this release and do a release as fast as possible with 2.6.24. 1. http://lists.debian.org/debian-boot/2008/02/msg00012.html very bad decision 2.6.24 is needed for a lot of recent hardware, d-i doesn't install on those. All your comments are right and that's why a Beta2 release is scheduled for just after Beta1 is out. The idea is to release Lenny Beta2 with bugfixes for Beta1 issues and kernel update only. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465790: gfs2-tools: gfs2_tools gettune uses (null) as fs name
Package: gfs2-tools Version: 2.20080208-2 Severity: normal gfs2_tools gettune fails because it tries to read an unexisting patch in /sys. See the following messages: node01:/replicated# mount | grep gfs2 /dev/drbd0 on /replicated type gfs2 (rw,hostdata=jid=0:id=196609:first=1) node01:/replicated# gfs2_tool gettune /replicated/ gfs2_tool: can't open /sys/fs/gfs2/(null)/tune: No such file or directory Instead of (null), it should be using cluster:replicated: node01:/replicated# ls /sys/fs/gfs2/cluster\:replicated/tune/ atime_quantum incore_log_blockslog_flush_secs new_files_jdata quota_quantum quota_warn_period stall_secs complain_secs jindex_refresh_secs max_readahead quota_cache_secs quota_scale reclaim_limit statfs_quantum demote_secslogd_secsnew_files_directio quotad_secs quota_simul_sync recoverd_secs statfs_slow linux-image-2.6.24-1-686 version 2.6.24-4 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (300, 'testing'), (200, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gfs2-tools depends on: ii libc6 2.7-6 GNU C Library: Shared libraries ii libncurses5 5.6+20080119-1 Shared libraries for terminal hand ii libvolume-id0 0.114-2libvolume_id shared library ii psmisc22.6-1 Utilities that use the proc filesy gfs2-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#463606: Linux 2.6.24 fails to boot on MS Virtual PC 2007
I get the same error on boot up. This is not on a virtual machine but a SBC from Advantech. The SBC is a PCM-3375 VIA Mark PC-104 Module. I had previously been using 2.6.18-4-686 with no issues. Graham-12 wrote: Package: linux-image-2.6.24-1-686 Version: 2.6.24-2 This image is failing to boot on my Virtual PC 2007. I will attach a screen capture, and also a best-effort transcription. Uncompressing Linux... Ok, booting the kernel. BUG: Int 6: CR2 EDI ESI 1000 EBP 0020 ESP c0373f54 EBX c03e5140 EDX 0006 ECX EAX c034f3e0 err EIP c0389390 CS 0060 flg 0082 Stack: 0010 1800 c039a9ec c03b934c c0373fe8 c03800c8 c039a9ec c037d0b8 0083 c0304c0f 0871 c039a9ec c03b934c c0373fe8 0871 c039a9ec c03b934c c0373fe8 c037d4ef c0304a56 00bf The screen capture contains a grey blip in the bottom left corner. This actually contains two blinking characters in bright white. The characters appear to be ASCII 144 (0x90). I'm not passing any strange parameters to the kernel, just root=/dev/hda2 ro. I tried reinstalling; it didn't help. Let me know what else I should try. Linux 2.6.22 and 2.6.23 work fine on the same VM. (With the exception of bug 433815, of course.) -- graham -- View this message in context: http://www.nabble.com/Bug-463606%3A-Linux-2.6.24-fails-to-boot-on-MS-Virtual-PC-2007-tp15233046p15488548.html Sent from the debian-kernel mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please add following hint to block linux-2.6 until Beta1 is out
Le February 14, 2008 01:56:55 pm maximilian attems, vous avez écrit : On Thu, 14 Feb 2008, Otavio Salvador wrote: Hello RM and SRM teams, I hereby ask for a block on linux-2.6 source package until d-i Beta1 gets out. If it migrates before we do the final images we can need to delay d-i release. nacked as maintainer, you are blocking for more then 2 weeks linux-2.6 migration to testing. linux-2.6 can't migrate to testing with normal delays before 2008-02-21. The planned beta release on 2008-03-03 is 11 days later. Also, this assumes that linux-2.6 2.6.24-4 will migrate to testing. In reality, it's unlikely that linux-2.6 would migrate before March.
Re: Please add following hint to block linux-2.6 until Beta1 is out
Philippe Cloutier [EMAIL PROTECTED] writes: Le February 14, 2008 01:56:55 pm maximilian attems, vous avez écrit : On Thu, 14 Feb 2008, Otavio Salvador wrote: Hello RM and SRM teams, I hereby ask for a block on linux-2.6 source package until d-i Beta1 gets out. If it migrates before we do the final images we can need to delay d-i release. nacked as maintainer, you are blocking for more then 2 weeks linux-2.6 migration to testing. linux-2.6 can't migrate to testing with normal delays before 2008-02-21. The planned beta release on 2008-03-03 is 11 days later. Also, this assumes that linux-2.6 2.6.24-4 will migrate to testing. In reality, it's unlikely that linux-2.6 would migrate before March. I know it and this is one of major reasons we choosen 2.6.22 for Beta1 and want to make Beta2 sonner. This gives time for kernel to mature on sid and we to test d-i. Beta2 should be a nice release for Etch+Halt to trust. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house.
Bug#463606: Test results on Geode
Guys: Seeing similar problems here too, with 2.6.24-686. 2.6.23-686 worked fine. My details: # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping: 2 cpu MHz : 499.904 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow up bogomips: 1001.54 clflush size: 32 (Yes, I know this machine isn't _technically_ a 686!). linux-image-2.6.24-1-486 seems to run fine. b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please add following hint to block linux-2.6 until Beta1 is out
On Thu, 14 Feb 2008, Philippe Cloutier wrote: linux-2.6 can't migrate to testing with normal delays before 2008-02-21. The planned beta release on 2008-03-03 is 11 days later. Also, this assumes that linux-2.6 2.6.24-4 will migrate to testing. In reality, it's unlikely that linux-2.6 would migrate before March. that is totally untrue. linux-2.6 always needs hint from the release team to migrate. properly set up it can happen in less then a week. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please add following hint to block linux-2.6 until Beta1 is out
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 maximilian attems [EMAIL PROTECTED] writes: On Thu, 14 Feb 2008, Philippe Cloutier wrote: linux-2.6 can't migrate to testing with normal delays before 2008-02-21. The planned beta release on 2008-03-03 is 11 days later. Also, this assumes that linux-2.6 2.6.24-4 will migrate to testing. In reality, it's unlikely that linux-2.6 would migrate before March. that is totally untrue. linux-2.6 always needs hint from the release team to migrate. properly set up it can happen in less then a week. So it puts even more urgency to the block. If it migrates we'll be in bad shape for Beta1 release. - -- O T A V I OS A L V A D O R - - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - - Microsoft sells you Windows ... Linux gives you the whole house. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8+ http://mailcrypt.sourceforge.net/ iD8DBQFHtNcyLqiZQEml+FURAhypAJ96CGXRE61mh7OE4lRHzlVQJx+xEwCeLjUX xOup68AAhNu/fvLmcnW2vn4= =rWse -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465508: Hardware problem?
I have not freezes with kernel 2.6.22-3-686. Anyway, i will pass a memtest86+ ok?
Bug#465807: linux-image-2.6.22-3-686: CD-ROM drive semi-permanently addled by a bad CD-ROM
Package: linux-image-2.6.22-3-686
Version: 2.6.22-6.lenny1
Severity: normal
I was attempting to read a cracked CD-ROM in the hopes of
recovering something. No luck.Instead, the drive
became permantently confused and inoperative (until the
next re-boot). See attached log.Similar error messages
continued even after the disk was removed, for several hours
until I rebooted the system. When the CD-ROM was in the drive,
the system was painfully slow, freezing for several seconds
at a time. Performance returned to normal once I ejected it
(apart from the error messages).
The CR-ROM was an audio CD, and the table of contents was at
least partially readable. It would play (partially) in
a dedicated CD player.
The drive is a circa 2003 24x10x40 CR-RW drive, running on p-ide,
a LITE-ON LTR-24102B . /proc/ide/hdd/driver is ide-cdrom version 4.61.
$ cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: hdd
drive speed:8
drive # of slots: 1
Can close tray: 1
Can open tray: 1
Can lock tray: 1
Can change speed: 1
Can select disk:0
Can read multisession: 1
Can read MCN: 1
Reports media changed: 1
Can play audio: 1
Can write CD-R: 1
Can write CD-RW:1
Can read DVD: 0
Can write DVD-R:0
Can write DVD-RAM: 0
Can read MRW: 1
Can write MRW: 1
Can write RAM: 1
$
-- Package-specific info:
** Version:
Linux version 2.6.22-3-686 (Debian 2.6.22-6.lenny1) ([EMAIL PROTECTED]) (gcc
version 4.1.3 20071209 (prerelease) (Debian 4.1.2-18)) #1 SMP Sun Feb 10
20:20:49 UTC 2008
** Not tainted
** Kernel log:
Feb 13 19:49:46 gpk spamd[4422]: spamd: result: Y 18 -
BAYES_99,DOS_OE_TO_MX,HTML_MESSAGE,NO_RDNS2,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_PBL,SARE_FROM_SPAM_WORD3,URIBL_AB_SURBL,URIBL_BLACK,URIBL_JP_SURBL,URIBL_OB_SURBL,URIBL_SC_SURBL,URIBL_WS_SURBL
scantime=9.0,size=1736,user=nobody,uid=65123,required_score=5.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=47764,mid=[EMAIL
PROTECTED],bayes=1.00,autolearn=spam
Feb 13 19:49:46 gpk spamd[3625]: prefork: child states: II
Feb 13 19:52:55 gpk kernel: hdd: DMA timeout retry
Feb 13 19:52:55 gpk kernel: hdd: timeout waiting for DMA
Feb 13 19:52:55 gpk kernel: hdd: status timeout: status=0xd0 { Busy }
Feb 13 19:52:55 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:52:55 gpk kernel: hdd: drive not ready for command
Feb 13 19:52:55 gpk kernel: hdd: status timeout: status=0xd0 { Busy }
Feb 13 19:52:55 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:52:55 gpk kernel: hdd: drive not ready for command
Feb 13 19:52:55 gpk kernel: Clocksource tsc unstable (delta = 9373923424 ns)
Feb 13 19:52:55 gpk kernel: Time: acpi_pm clocksource has been installed.
Feb 13 19:52:55 gpk kernel: hdd: status timeout: status=0xd0 { Busy }
Feb 13 19:52:55 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:52:55 gpk kernel: hdd: drive not ready for command
Feb 13 19:52:55 gpk kernel: hdd: status timeout: status=0xd0 { Busy }
Feb 13 19:52:55 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:52:55 gpk kernel: hdd: drive not ready for command
Feb 13 19:52:55 gpk kernel: hdd: status timeout: status=0xd0 { Busy }
Feb 13 19:52:55 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:52:55 gpk kernel: hdd: drive not ready for command
Feb 13 19:52:58 gpk kernel: [FIAIF_INVALID]:IN= OUT=eth0 SRC=192.168.1.65
DST=80.252.91.41 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=62036 DF PROTO=TCP
SPT=50818 DPT=80 WINDOW=212 RES=0x00 ACK FIN URGP=0
Feb 13 19:54:10 gpk kernel: [FIAIF_INVALID]:IN= OUT=eth0 SRC=192.168.1.65
DST=80.252.91.41 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=62037 DF PROTO=TCP
SPT=50818 DPT=80 WINDOW=212 RES=0x00 ACK FIN URGP=0
Feb 13 19:57:39 gpk kernel: [FIAIF_DROP]:IN=eth1 OUT=
MAC=ff:ff:ff:ff:ff:ff:00:e0:4c:7d:bd:c9:08:00 SRC=192.168.2.96
DST=192.168.2.255 LEN=236 TOS=0x00 PREC=0x00 TTL=128 ID=34737 PROTO=UDP SPT=138
DPT=138 LEN=216
Feb 13 19:59:20 gpk kernel: hdd: irq timeout: status=0xd0 { Busy }
Feb 13 19:59:20 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:59:20 gpk kernel: hdd: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Feb 13 19:59:20 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:59:20 gpk kernel: hdd: drive not ready for command
Feb 13 19:59:20 gpk kernel: hdd: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Feb 13 19:59:20 gpk kernel: ide: failed opcode was: unknown
Feb 13 19:59:20 gpk kernel: hdd: drive not ready for command
Feb 13 19:59:20 gpk kernel: hdd: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Feb 13 19:59:20 gpk kernel: ide: failed opcode was: unknown
** Loaded modules:
Module Size Used by
nls_iso8859_1 4128 1
nls_cp437 5792 1
vfat 12032 1
fat48508 1 vfat
tun10560 0
Re: Please add following hint to block linux-2.6 until Beta1 is out
Le February 14, 2008 06:33:20 pm maximilian attems, vous avez écrit : On Thu, 14 Feb 2008, Philippe Cloutier wrote: linux-2.6 can't migrate to testing with normal delays before 2008-02-21. The planned beta release on 2008-03-03 is 11 days later. Also, this assumes that linux-2.6 2.6.24-4 will migrate to testing. In reality, it's unlikely that linux-2.6 would migrate before March. that is totally untrue. linux-2.6 always needs hint from the release team to migrate. properly set up it can happen in less then a week. What do you mean? What it can happen in less than one week?
Bug#465816: I forgot to mention which part of syslog to look at.
The relevant part(s) of syslog are the ones that read: Feb 15 11:15:20 hades kernel: eth1: txs packet size do not coinsist with txd txd_:0xa520, txs_:0x000105be! Feb 15 11:15:20 hades kernel: txd read ptr: 0x33c Feb 15 11:15:20 hades kernel: txs-behind:0x800105be Feb 15 11:15:20 hades kernel: txs-before:0x000105be Feb 15 11:15:20 hades kernel: eth1: txs packet size do not coinsist with and txd_:0xefca5297, txs_:0x2656! Feb 15 11:15:20 hades kernel: txd read ptr: 0x1edc Feb 15 11:15:20 hades kernel: txs-behind:0x000105be Feb 15 11:15:20 hades kernel: txs-before:0x0005019c Feb 15 11:15:27 hades kernel: NETDEV WATCHDOG: eth1: transmit timed out Feb 15 11:15:28 hades kernel: ATL2: eth1 NIC Link is Up100 Mbps Full Duplex Notice on the last two lines the netdev watchdog kicks in. This causes the connection to be reset and the transmission continues for a few more seconds until it gets jammed up again. It may not be obvious from the bug report but this causes the transfer speed over ethernet to drop dramatically. This only happens on local network transfers because (I'm guessing) that's the only time the interface is saturated. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465816: Just for reference, Debian is not the only sufferer of this problem.
It appears at least two other people are having this problem on Ubuntu. https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/147639 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#465816: atl2-modules-2.6.22-3-amd64: Network cuts out during large transfers. Also causes lock-ups of other network apps.
Processing commands for [EMAIL PROTECTED]: reassign 465816 atl2-source Bug#465816: atl2-modules-2.6.22-3-amd64: Network cuts out during large transfers. Also causes lock-ups of other network apps. Bug reassigned from package `atl2-modules-2.6.22-3-amd64' to `atl2-source'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
