Processed: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0
Processing commands for cont...@bugs.debian.org: retitle 526525 amd64 kernel cannot find bnx2 PCI device base address Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see root RAID device /dev/md0 Changed Bug title to `amd64 kernel cannot find bnx2 PCI device base address' from `Kernel linux-image-2.6.26-2-amd64 does not see root RAID device /dev/md0'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0
retitle 526525 amd64 kernel cannot find bnx2 PCI device base address thanks also sprach Tony Godshall t...@of.net [2009.05.09.0117 +0200]: If you cannot boot, append break=mount to the kernel line, and at the initramfs prompt, type rm /etc/mdadm/mdadm.conf /scripts/local-top/mdadm ctrl-d and then fix the initramfs. I'm not interested in deleting mdadm.conf or taking any other steps that might break the existing functionality. I considered it a necessary step in my analysis, but if you prefer to do things your way, it's your system. Note that I would have never proposed anything that made permanent changes without adequate warning. I'm not reporting this bug because I must have an amd64 kernel- like I said, the 686 and 686bigmem kernels are working. I initiated this bug to help get the amd64 version of the kernel (or mdadm?) fixed. I'm interested in steps that will help fix the packages, not manually work around its flaws. Then please provide all the necessary infos. mdadm works perfectly fine with amd64 kernels. I think your problem is that the kernel doesn't initialise the drives you're using properly, so mdadm doesn't find them when trying to assemble. You will have to make sure the kernel sees your drives. From what you've allowed me to see, I can conclude that this is not a RAID problem. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems fashions have done more harm than revolutions. -- victor hugo digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#527926: linux-image-2.6.29-2-amd64: breaks tcpdump
Package: linux-image-2.6.29-2-amd64 Version: 2.6.29-4 Severity: important When I boot the linux-image-2.6.29-2-amd64 kernel (userspace is 32-bit), I cannot use tcpdump. Old 64-bit kernels work, and the -686 variant of 2.6.29-2 also works. The error displayed by tcpdump (while pinging 192.168.1.1) is: tcpdump: pcap_loop: corrupted frame on kernel ring mac offset 94 + caplen 98 frame len 160 -- Package-specific info: ** Version: Linux version 2.6.29-2-amd64 (Debian 2.6.29-4) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-8) ) #1 SMP Sun May 3 15:03:04 UTC 2009 ** Command line: root=/dev/mapper/aep-root ro nomsi quiet resume=/dev/mapper/aep-swap_1 ** Not tainted ** Kernel log: [ 22.136104] iwlagn :0c:00.0: PCI INT A disabled [ 22.136253] wmaster0 (iwlagn): not using net_device_ops yet [ 22.136548] phy0: Selected rate control algorithm 'iwl-agn-rs' [ 22.137647] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1a0b1, caps: 0xa04711/0x202000 [ 22.176094] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input10 [ 22.363586] uvcvideo: Found UVC 1.00 device OEM Camera (046d:09b2) [ 22.367909] input: OEM Camera as /devices/pci:00/:00:1a.7/usb1/1-3/1-3:1.0/input/input11 [ 22.373848] wlan0 (iwlagn): not using net_device_ops yet [ 22.385150] usbcore: registered new interface driver uvcvideo [ 22.385214] USB Video Class driver (v0.1.0) [ 22.740668] HDA Intel :00:1b.0: power state changed by ACPI to D0 [ 22.740740] HDA Intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [ 22.740867] HDA Intel :00:1b.0: setting latency timer to 64 [ 24.596246] EXT3 FS on dm-1, internal journal [ 25.077976] loop: module loaded [ 25.137776] tun: Universal TUN/TAP device driver, 1.6 [ 25.137837] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 27.213848] kjournald starting. Commit interval 5 seconds [ 27.216317] EXT3 FS on dm-3, internal journal [ 27.216414] EXT3-fs: mounted filesystem with ordered data mode. [ 27.250377] Adding 2654200k swap on /dev/mapper/aep-swap_1. Priority:-1 extents:1 across:2654200k [ 30.049631] Bridge firewalling registered [ 30.068893] device tun0 entered promiscuous mode [ 30.071253] device tun1 entered promiscuous mode [ 30.073516] device tun2 entered promiscuous mode [ 30.075822] device tun3 entered promiscuous mode [ 30.078210] device tun4 entered promiscuous mode [ 30.080688] device tun5 entered promiscuous mode [ 30.083157] device tun6 entered promiscuous mode [ 30.085585] device tun7 entered promiscuous mode [ 30.087710] br0: port 8(tun7) entering learning state [ 30.087768] br0: port 7(tun6) entering learning state [ 30.087824] br0: port 6(tun5) entering learning state [ 30.087880] br0: port 5(tun4) entering learning state [ 30.087937] br0: port 4(tun3) entering learning state [ 30.087993] br0: port 3(tun2) entering learning state [ 30.088070] br0: port 2(tun1) entering learning state [ 30.088133] br0: port 1(tun0) entering learning state [ 30.841115] NET: Registered protocol family 10 [ 30.841845] lo: Disabled Privacy Extensions [ 32.723973] vbetool: vm86 mode not supported on 64 bit kernel [ 35.861649] lp0: using parport0 (interrupt-driven). [ 35.872623] ppdev: user-space parallel port driver [ 40.936058] tun0: no IPv6 routers present [ 41.452086] tun6: no IPv6 routers present [ 41.540087] tun5: no IPv6 routers present [ 41.556056] br0: no IPv6 routers present [ 41.576056] tun2: no IPv6 routers present [ 41.668060] tun1: no IPv6 routers present [ 41.688059] tun7: no IPv6 routers present [ 41.836085] tun3: no IPv6 routers present [ 41.836092] tun4: no IPv6 routers present [ 45.085063] br0: topology change detected, propagating [ 45.085153] br0: port 8(tun7) entering forwarding state [ 45.085223] br0: topology change detected, propagating [ 45.085292] br0: port 7(tun6) entering forwarding state [ 45.085361] br0: topology change detected, propagating [ 45.085430] br0: port 6(tun5) entering forwarding state [ 45.085499] br0: topology change detected, propagating [ 45.085568] br0: port 5(tun4) entering forwarding state [ 45.085638] br0: topology change detected, propagating [ 45.085707] br0: port 4(tun3) entering forwarding state [ 45.089065] br0: topology change detected, propagating [ 45.089136] br0: port 3(tun2) entering forwarding state [ 45.089205] br0: topology change detected, propagating [ 45.089274] br0: port 2(tun1) entering forwarding state [ 45.089344] br0: topology change detected, propagating [ 45.089413] br0: port 1(tun0) entering forwarding state [ 45.914041] Bluetooth: Core ver 2.14 [ 45.915777] NET: Registered protocol family 31 [ 45.915850] Bluetooth: HCI device and connection manager initialized [ 45.915928] Bluetooth: HCI socket layer initialized [ 45.942805] Bluetooth: L2CAP ver 2.11 [ 45.942878] Bluetooth: L2CAP socket layer initialized [ 46.136667] Bluetooth: RFCOMM
Bug#527926: Not fixed in trunk
This bug also applies to linux-image-2.6.30-rc4-amd64_2.6.30~rc4-1~experimental.1~snapshot.13587_i386.deb However, on my Gentoo system, I can run tcpdump just fine even with a self-compiled 64-bit kernel and 32-bit userspace -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#527926: linux-image-2.6.29-2-amd64: breaks tcpdump
Processing commands for cont...@bugs.debian.org: severity 527926 normal Bug#527926: linux-image-2.6.29-2-amd64: breaks tcpdump Severity set to `normal' from `important' reassign 527926 libpcap0.8 Bug#527926: linux-image-2.6.29-2-amd64: breaks tcpdump Bug reassigned from package `linux-image-2.6.29-2-amd64' to `libpcap0.8'. merge 527926 517098 Bug#517098: libpap 1.0.0-1_i386 broken on 64-bit kernel Bug#527926: linux-image-2.6.29-2-amd64: breaks tcpdump Merged 517098 527926. quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527926: linux-image-2.6.29-2-amd64: breaks tcpdump
severity 527926 normal reassign 527926 libpcap0.8 merge 527926 517098 quit Alexander E. Patrakov patra...@gmail.com writes: When I boot the linux-image-2.6.29-2-amd64 kernel (userspace is 32-bit), I cannot use tcpdump. Old 64-bit kernels work, and the -686 variant of 2.6.29-2 also works. That's bug #517098. -- Romain Francoise rfranco...@debian.org http://people.debian.org/~rfrancoise/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#513695: fetchmail: race in MSG_PEEK
Processing commands for cont...@bugs.debian.org: reassign 513695 linux-2.6 2.6.28-1 Bug#513695: fetchmail: race in MSG_PEEK. Bug reassigned from package `fetchmail' to `linux-2.6'. forwarded 513695 http://www.spinics.net/lists/netdev/msg96676.html Bug#513695: fetchmail: race in MSG_PEEK. Noted your statement that Bug has been forwarded to http://www.spinics.net/lists/netdev/msg96676.html. tags 513695 patch Bug#513695: fetchmail: race in MSG_PEEK. Tags were: upstream moreinfo Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513695: fetchmail: race in MSG_PEEK
reassign 513695 linux-2.6 2.6.28-1 forwarded 513695 http://www.spinics.net/lists/netdev/msg96676.html tags 513695 patch thanks The cause of these errors has been traced to the kernel. The errors are bogus and due to a test that's no longer correct after a code change in 2.6.28. The errors have also been seen with other applications than fetchmail: kernel: TCP(kio_imap4:5646): Application bug, race in MSG_PEEK kernel: TCP(wget:4137): Application bug, race in MSG_PEEK A (tested) patch is available in http://www.spinics.net/lists/netdev/msg96700.html which is expected to get included in 2.6.30 and probably the next 2.6.29 stable update. Cheers, FJP -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527963: Regression bug - xirc2ps_cs kernel module works under Etch, fails under Lenny
Package: linux-image-2.6.26-2-686 Version: 2.6.26-15 Severity: normal I have two laptops. One is an IBM ThinkPad 390E running Debian Etch (kernel linux-image-2.6.18-6-686). The other is an IBM ThinkPad 600 running Debian Lenny (kernel linux-image-2.6.26-2-686). I have a 16-bit PC Card 10/100 Ethernet adapter that works in the Etch machine but does not work in the Lenny machine. The card has COMPAQ 10/100 PC CARD and 292811-008 on the front and various things on the back such as COMPAQ, With Integrated 100Mbps Transceiver, 292811-009, Series NNB108, N260, CE, PC Card, and some other stuff. I am using the patch cable (or dongle, or whatever you want to call it) that came with the card. Linux recognizes the card as fully supported and loads kernel module xirc2ps_cs to drive it. Under Etch, the card works fine. Under Lenny, the failure occurrs with a timeout of DHCP configuration. I can use other 16-bit and 32-bit Ethernet cards successfully in the Lenny machine, but not the Compaq card. lspcmcia -v lists the card as a Compaq Netelligent 10/100 card, though the word Netelligent is not physically printed on the card anywhere.
Bug#527968: adjust SHIFT_PLL to improve NTP convergence
Package: linux-2.6
Version: 2.6.26-15
Please apply this patch to the next stable kernel update.
- Forwarded message from tip-bot for john stultz johns...@us.ibm.com -
From: tip-bot for john stultz johns...@us.ibm.com
To: linux-tip-comm...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org, r...@redhat.com, h...@zytor.com,
mi...@redhat.com, a...@linux-foundation.org, johns...@us.ibm.com,
t...@linutronix.de, mi...@elte.hu
Subject: [tip:timers/ntp] ntp: adjust SHIFT_PLL to improve NTP convergence
Commit-ID: 22cfbbfd9f67b67fe073010f51cb71d3632387d5
Gitweb: http://git.kernel.org/tip/22cfbbfd9f67b67fe073010f51cb71d3632387d5
Author: john stultz johns...@us.ibm.com
AuthorDate: Wed, 6 May 2009 11:43:57 +0200
Committer: Ingo Molnar mi...@elte.hu
CommitDate: Wed, 6 May 2009 11:44:02 +0200
ntp: adjust SHIFT_PLL to improve NTP convergence
The conversion to the ntpv4 reference model
f19923937321244e7dc334767eb4b67e0e3d5c74 (ntp: convert to the NTP4
reference model) in 2.6.19 added nanosecond resolution the adjtimex
interface, but also changed the stiffness of the frequency adjustments,
causing NTP convergence time to greatly increase.
SHIFT_PLL, which reduces the stiffness of the freq adjustments, was
designed to be inversely linked to HZ, and the reference value of 4 was
designed for Unix systems using HZ=100. However Linux's clock steering
code mostly independent of HZ.
So this patch reduces the SHIFT_PLL value from 4 to 2, which causes NTPd
behavior to match kernels prior to 2.6.19, greatly reducing convergence
times, and improving close synchronization through environmental thermal
changes.
The patch also changes some l's to L's in nearby code to avoid misreading
50l as 501.
[ Impact: tweak NTP algorithm for faster convergence ]
Signed-off-by: John Stultz johns...@us.ibm.com
Acked-by: Rik van Riel r...@redhat.com
Cc: zip...@linux-m68k.org
Signed-off-by: Andrew Morton a...@linux-foundation.org
LKML-Reference: 200905051956.n45juvo9025...@imap1.linux-foundation.org
Signed-off-by: Ingo Molnar mi...@elte.hu
---
include/linux/timex.h | 42 +++---
1 files changed, 31 insertions(+), 11 deletions(-)
diff --git a/include/linux/timex.h b/include/linux/timex.h
index aa3475f..0daf961 100644
--- a/include/linux/timex.h
+++ b/include/linux/timex.h
@@ -170,17 +170,37 @@ struct timex {
#include asm/timex.h
/*
- * SHIFT_KG and SHIFT_KF establish the damping of the PLL and are chosen
- * for a slightly underdamped convergence characteristic. SHIFT_KH
- * establishes the damping of the FLL and is chosen by wisdom and black
- * art.
+ * SHIFT_PLL is used as a dampening factor to define how much we
+ * adjust the frequency correction for a given offset in PLL mode.
+ * It also used in dampening the offset correction, to define how
+ * much of the current value in time_offset we correct for each
+ * second. Changing this value changes the stiffness of the ntp
+ * adjustment code. A lower value makes it more flexible, reducing
+ * NTP convergence time. A higher value makes it stiffer, increasing
+ * convergence time, but making the clock more stable.
*
- * MAXTC establishes the maximum time constant of the PLL. With the
- * SHIFT_KG and SHIFT_KF values given and a time constant range from
- * zero to MAXTC, the PLL will converge in 15 minutes to 16 hours,
- * respectively.
+ * In David Mills' nanokenrel reference implmentation SHIFT_PLL is 4.
+ * However this seems to increase convergence time much too long.
+ *
+ * https://lists.ntp.org/pipermail/hackers/2008-January/003487.html
+ *
+ * In the above mailing list discussion, it seems the value of 4
+ * was appropriate for other Unix systems with HZ=100, and that
+ * SHIFT_PLL should be decreased as HZ increases. However, Linux's
+ * clock steering implementation is HZ independent.
+ *
+ * Through experimentation, a SHIFT_PLL value of 2 was found to allow
+ * for fast convergence (very similar to the NTPv3 code used prior to
+ * v2.6.19), with good clock stability.
+ *
+ *
+ * SHIFT_FLL is used as a dampening factor to define how much we
+ * adjust the frequency correction for a given offset in FLL mode.
+ * In David Mills' nanokenrel reference implmentation SHIFT_PLL is 2.
+ *
+ * MAXTC establishes the maximum time constant of the PLL.
*/
-#define SHIFT_PLL 4 /* PLL frequency factor (shift) */
+#define SHIFT_PLL 2 /* PLL frequency factor (shift) */
#define SHIFT_FLL 2 /* FLL frequency factor (shift) */
#define MAXTC 10 /* maximum time constant (shift) */
@@ -192,10 +212,10 @@ struct timex {
#define SHIFT_USEC 16 /* frequency offset scale (shift) */
#define PPM_SCALE ((s64)NSEC_PER_USEC (NTP_SCALE_SHIFT - SHIFT_USEC))
#define PPM_SCALE_INV_SHIFT 19
-#define PPM_SCALE_INV ((1ll (PPM_SCALE_INV_SHIFT + NTP_SCALE_SHIFT)) / \
+#define PPM_SCALE_INV ((1LL (PPM_SCALE_INV_SHIFT + NTP_SCALE_SHIFT)) / \
PPM_SCALE + 1)
Bug#463860: any chance to see this fixed in 2.6.26 ?
Hello everybody, 2 things: - I think this other bug report talks about the same bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524132 Is it a good idea to group them together ? - I read this and if I understanded well, this will never be fixed and we have to wait for the next version of the kernel containing a ath5k driver without bug ? If I can help, I encountered the same problem and tried to locate it (dmesg, strace ifup ath0, ...). Just tell me. Jean-Marc -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#347186: linux-image-2.6.26-2-alpha-generic: Matroxfb alpha
Package: linux-image-2.6.26-2-alpha-generic Followup-For: Bug #347186 I tried on my dp264 using exaclty the same video card with the current lenny kernel and everything seems to work just fine. BTW: for the console to show up it's required to load the fbcon module as well -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (900, 'stable') Architecture: alpha Kernel: Linux 2.6.26-2-alpha-generic 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 linux-image-2.6.26-2-alpha-generic depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-2-alpha-generic recommends no packages. Versions of packages linux-image-2.6.26-2-alpha-generic suggests: ii aboot 1.0~pre20040408-3 Linux bootloader for the SRM conso ii fdutils5.5-20060227-3Linux floppy utilities pn linux-doc-2.6.26 none(no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#347186: linux-image-2.6.26-2-alpha-generic: Matroxfb alpha
On Sat, May 09, 2009 at 01:31:59PM -0700, Gabriele Gorla wrote: Package: linux-image-2.6.26-2-alpha-generic Followup-For: Bug #347186 I tried on my dp264 using exaclty the same video card with the current lenny kernel and everything seems to work just fine. Does that include running 'bterm'? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513695: sorry
I switched to getmail4 and I'm happy with it, so I can't help more. -- Ian Zimmerman i...@buug.org gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD Ham is for reading, not for eating. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#435134: linux-image-2.6.22-1-alpha-smp: various modules cannot be loaded
Package: linux-image-2.6.26-2-alpha-smp Followup-For: Bug #435134 I have not noticed any module loading issues with current lenny kernels (either generic or smp). In particular xfs and ipv6 load just fine. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (900, 'stable') Architecture: alpha Kernel: Linux 2.6.26-2-alpha-smp (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 linux-image-2.6.26-2-alpha-smp depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-2-alpha-smp recommends no packages. Versions of packages linux-image-2.6.26-2-alpha-smp suggests: ii aboot 1.0~pre20040408-3 Linux bootloader for the SRM conso ii fdutils5.5-20060227-3Linux floppy utilities pn linux-doc-2.6.26 none(no description available) -- debconf information: linux-image-2.6.26-2-alpha-smp/preinst/lilo-initrd-2.6.26-2-alpha-smp: true * linux-image-2.6.26-2-alpha-smp/preinst/bootloader-initrd-2.6.26-2-alpha-smp: false linux-image-2.6.26-2-alpha-smp/preinst/already-running-this-2.6.26-2-alpha-smp: linux-image-2.6.26-2-alpha-smp/preinst/abort-install-2.6.26-2-alpha-smp: linux-image-2.6.26-2-alpha-smp/postinst/old-initrd-link-2.6.26-2-alpha-smp: true linux-image-2.6.26-2-alpha-smp/postinst/depmod-error-2.6.26-2-alpha-smp: false linux-image-2.6.26-2-alpha-smp/preinst/elilo-initrd-2.6.26-2-alpha-smp: true linux-image-2.6.26-2-alpha-smp/prerm/removing-running-kernel-2.6.26-2-alpha-smp: true linux-image-2.6.26-2-alpha-smp/preinst/failed-to-move-modules-2.6.26-2-alpha-smp: linux-image-2.6.26-2-alpha-smp/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-alpha-smp/postinst/kimage-is-a-directory: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-alpha-smp/preinst/overwriting-modules-2.6.26-2-alpha-smp: true linux-image-2.6.26-2-alpha-smp/prerm/would-invalidate-boot-loader-2.6.26-2-alpha-smp: true linux-image-2.6.26-2-alpha-smp/postinst/create-kimage-link-2.6.26-2-alpha-smp: true linux-image-2.6.26-2-alpha-smp/postinst/depmod-error-initrd-2.6.26-2-alpha-smp: false linux-image-2.6.26-2-alpha-smp/preinst/abort-overwrite-2.6.26-2-alpha-smp: linux-image-2.6.26-2-alpha-smp/postinst/bootloader-test-error-2.6.26-2-alpha-smp: linux-image-2.6.26-2-alpha-smp/preinst/initrd-2.6.26-2-alpha-smp: linux-image-2.6.26-2-alpha-smp/postinst/old-system-map-link-2.6.26-2-alpha-smp: true linux-image-2.6.26-2-alpha-smp/postinst/bootloader-error-2.6.26-2-alpha-smp: linux-image-2.6.26-2-alpha-smp/postinst/old-dir-initrd-link-2.6.26-2-alpha-smp: true -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516382: tg3: Corrupted MAC on input and scatter gather
Package: linux-image-2.6.26-2-alpha-generic Version: 2.6.26-15 Followup-For: Bug #516382 vanilla kernel 2.6.29 does not work as well. However, disabling scatter gather with ethtool seems to make the issue disappear. ethtool -K ethX sg off this may help in narrowing down the issue to a specific part of the driver. as a side note, ethtool complains about device flags (I have not seen this on a different tg3 supported card I own). # ethtool -k eth0 Offload parameters for eth0: Cannot get device flags: Operation not supported rx-checksumming: on tx-checksumming: on scatter-gather: off tcp segmentation offload: off udp fragmentation offload: off generic segmentation offload: on large receive offload: off -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
