Re: Applying e1000e patch to the Debian 2.6.26 kernel
Ben Hutchings wrote: On Tue, Jun 16, 2009 at 12:50:34AM +0800, Thomas Goirand wrote: [...] So I'm wondering, did somebody applied some patches for e1000e between the release of Lenny 5.01? Or maybe, the e1000e on the X8STi-3F is different from the one of my Thinkpad t500? Is there even different versions of the board at Intel? [...] There are many slightly different chips handled by the e1000e driver. If it was broken for all of them we would have fixed it before release! You have to test on the specific model which the kernel from lenny doesn't work on. Ben. That is quite what I think as well. Here's what I am up to. 1/ The Debian kernel, which USED to have no support for my Thinkpad e1000e works fully now. Someone MUST have done something to the kernel, because I'm 100% sure that at the time of Lenny, it was not working. 2/ On our last test on the Supermicro board, it did FAIL last week. Now, I have asked my hardware supplier to put one of these X8STi-F online in order to test with it, he has been very nice, and he said he will. I'll be able to do a full test and report here. Thanks to you all for helping me to find out what's going on! Thomas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533276: linux-image-2.6.26-2-686-bigmem: mount.cifs : option dir_mode not apply in mount point
Package: linux-image-2.6.26-2-686-bigmem Version: 2.6.26-15lenny3 Severity: normal With kernel 2.6.26-2, when i mount using the option dir_mode=0755, the mask is not apply to the mount point but just on the sub-dir. This problem occurs on some windows shares (that are automatically made by a external program on my windows 2003 server). $ mount -t cifs //192.168.224.1/MYSHARE$ TEST -o username=admin,uid=10066,gid=1,dir_mode=0755 --verbose $ ll . dr-xr-xr-x 1 admin utilisa._du_domaine0 jun 11 17:14 TEST When i boot from kernel 2.6.24 with exactly same command, everything works as expect : $ mount -t cifs //192.168.224.1/MYSHARE$ TEST -o username=admin,uid=10066,gid=1,dir_mode=0755 --verbose $ ll . drwxr-xr-x 1 admin utilisa._du_domaine0 jun 11 17:19 TEST I use mount-2.13.1.1-1, smbfs-3.2.5-4lenny2 and samba-common-3.2.5-4lenny2 thanks, -- Package-specific info: -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-486 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-686-bigmem 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 Versions of packages linux-image-2.6.26-2-686-bigmem recommends: ii libc6-i6862.7-18 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-2-686-bigmem suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- debconf information: linux-image-2.6.26-2-686-bigmem/preinst/overwriting-modules-2.6.26-2-686-bigmem: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-686-bigmem/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-686-bigmem/postinst/bootloader-test-error-2.6.26-2-686-bigmem: linux-image-2.6.26-2-686-bigmem/postinst/depmod-error-2.6.26-2-686-bigmem: false linux-image-2.6.26-2-686-bigmem/preinst/initrd-2.6.26-2-686-bigmem: linux-image-2.6.26-2-686-bigmem/preinst/abort-overwrite-2.6.26-2-686-bigmem: linux-image-2.6.26-2-686-bigmem/preinst/bootloader-initrd-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/postinst/depmod-error-initrd-2.6.26-2-686-bigmem: false linux-image-2.6.26-2-686-bigmem/postinst/create-kimage-link-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/preinst/lilo-initrd-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/prerm/would-invalidate-boot-loader-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/preinst/failed-to-move-modules-2.6.26-2-686-bigmem: linux-image-2.6.26-2-686-bigmem/prerm/removing-running-kernel-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/postinst/old-dir-initrd-link-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/preinst/elilo-initrd-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/preinst/abort-install-2.6.26-2-686-bigmem: linux-image-2.6.26-2-686-bigmem/postinst/old-initrd-link-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/postinst/old-system-map-link-2.6.26-2-686-bigmem: true linux-image-2.6.26-2-686-bigmem/postinst/bootloader-error-2.6.26-2-686-bigmem: linux-image-2.6.26-2-686-bigmem/postinst/kimage-is-a-directory: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533087: linux-image-2.6.29-2-686: udev meddling breaks networking
-Original Message- From: Ben Hutchings [mailto:b...@decadent.org.uk] Sent: 15 June 2009 22:35 To: Chris Carr Cc: 533...@bugs.debian.org Subject: Re: Bug#533087: linux-image-2.6.29-2-686: udev meddling breaks networking On Mon, 2009-06-15 at 21:45 +0100, Chris Carr wrote: On Sun, 2009-06-14 at 23:07 +0100, Ben Hutchings wrote: [...] I think you want to map MAC address 00:e0:18:f1:05:7b to eth0, so change /etc/udev/rules.d/70-persistent-net.rules accordingly. Please let us know whether this solves the problem for you. Sadly not, but thanks to both you and Maximilian for the replies. I attach /etc/udev/rules.d/70-persistent-net.rules (having edited the last entry to point to eth0 as you suggested). Did you reboot or restart udev after changing this file? Yes, I rebooted to test it (twice - once to see if it fixed 2.6.29, once to see if it broke 2.6.26). The ip.addr.show.2.6.2* attachments were created after the reboots. Can you send a new kernel log? Will do. CC -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532908: initramfs-tools: initrd image not created on custom kernels
On Monday 15 Jun 2009 14:42:11 maximilian attems wrote: explained in debian/changelog, by disabling the check you have busted now the ability to install linux-2.6 officialy build linux images. so status stays the same people that care about kernel-package, should come forward with a good patch. I don't have the background on what exactly the bug is caused by. and your very brief explanation doesn't enlighten much. I did run a native package and yes, it doesn't generate an initrd image there. But we can do better in the current way we are handling. Instead of just silently exiting, you could atleast warn the user. Attached is the patch. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. --- /etc/kernel/postinst.d/initramfs-tools 2009-06-16 13:58:47.838409200 +0530 +++ /tmp/initramfs-tools.mod 2009-06-16 13:58:06.152409180 +0530 @@ -6,7 +6,7 @@ [ -z $1 ] exit 0 # kernel-package passes an extra arg; hack to not run under kernel-package -[ -z $2 ] || exit 0 +[ -z $2 ] || (echo -en WARNING: kernel-package generated deb.\nWill not generate an initrd image\n; exit 0) # we're good - create initramfs. update runs do_bootloader update-initramfs -c -t -k $1 signature.asc Description: This is a digitally signed message part.
Bug#529785: closed by Bastian Blank wa...@debian.org (Bug#529785: fixed in linux-2.6 2.6.30-1)
# I just tested the linux-image-2.6.30-1-amd64 (2.6.30-1) kernel # in my lenny system and I still experience the inability to send # files from my phone to the laptop after a hibernate/resume cycle reopen 529785 thanks Debian Bug Tracking System a scris: This is an automatic notification regarding your Bug report which was filed against the linux-image-2.6.29-2-amd64 package: #529785: [regression] the entire bluetooth stack needs a restart after resume It has been closed by Bastian Blank wa...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Bastian Blank wa...@debian.org by replying to this email. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#529785 closed by Bastian Blank wa...@debian.org (Bug#529785: fixed in linux-2.6 2.6.30-1)
Processing commands for cont...@bugs.debian.org: # I just tested the linux-image-2.6.30-1-amd64 (2.6.30-1) kernel # in my lenny system and I still experience the inability to send # files from my phone to the laptop after a hibernate/resume cycle reopen 529785 Bug#529785: [regression] the entire bluetooth stack needs a restart after resume 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. 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#533292: linux-image-2.6.30-1-686 (sid), KMS enabled: black screen
Package: linux-image-2.6.30-1-686 (2.6.30-1, Sid) System: Debian/sid, KMS enabled (module i915 modeset=1 loaded) Processor: Intel Pentium M 1.70 GHz Chipset: 852GM/855GM Severity: important After upgrading the kernel-image to linux-image-2.6.30-1-686 (Sid) booting ends with a black screen, no more key input, not starting X. This only happens when KMS is enabled by loading module i915 modeset=1 at boot time. Loading module i915 modeset=0 boots normally. This issue didn't occur with linux-image-2.6.30-rc8-686 (snapshot 13741) and previous releases from Debian kernel-archive. Cheers, Jos van Wolput -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#533292: linux-image-2.6.30-1-686 (sid), KMS enabled: black screen
Processing commands for cont...@bugs.debian.org: reassign 533292 linux-2.6 Bug#533292: linux-image-2.6.30-1-686 (sid), KMS enabled: black screen Warning: Unknown package '2.6.30-1' Warning: Unknown package 'sid' Bug reassigned from package `linux-image-2.6.30-1-686 (2.6.30-1, sid)' to `linux-2.6'. -- 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#444182: linux-image-2.6.29: drivers-ata-ata_piix-postpone-pata.patch prevents hotplug/unplug of the ultrabay of the ultrabase X3 to work
Package: linux-image-2.6.29-2-686 Version: 2.6.29-2 Severity: normal File: linux-image-2.6.29 The drivers-ata-ata_piix-postpone-pata.patch activates the piix driver instead of the ata_piix driver for my thinkpad X32. This makes the hotplug of the ultrabase X3 not working (DVD drive of the ultrabay not recognised) and the unplug when booting on the ultrabay to freeze the kernel. Reverting the patch (on a debian 2.6.30 kernel tree) fixes this problem. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (10, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-2-686 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.29-2-686 recommends: ii libc6-i6862.9-12 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.29-2-686 suggests: ii grub-pc [grub] 1.96+20090317-1 GRand Unified Bootloader, version pn linux-doc-2.6.29 none (no description available) -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.29-2-686/postinst/depmod-error-2.6.29-2-686: false linux-image-2.6.29-2-686/postinst/kimage-is-a-directory: linux-image-2.6.29-2-686/preinst/overwriting-modules-2.6.29-2-686: true linux-image-2.6.29-2-686/postinst/bootloader-error-2.6.29-2-686: linux-image-2.6.29-2-686/preinst/abort-install-2.6.29-2-686: linux-image-2.6.29-2-686/postinst/create-kimage-link-2.6.29-2-686: true linux-image-2.6.29-2-686/preinst/failed-to-move-modules-2.6.29-2-686: linux-image-2.6.29-2-686/preinst/initrd-2.6.29-2-686: linux-image-2.6.29-2-686/postinst/old-dir-initrd-link-2.6.29-2-686: true linux-image-2.6.29-2-686/postinst/old-initrd-link-2.6.29-2-686: true linux-image-2.6.29-2-686/prerm/removing-running-kernel-2.6.29-2-686: true linux-image-2.6.29-2-686/postinst/bootloader-test-error-2.6.29-2-686: linux-image-2.6.29-2-686/postinst/old-system-map-link-2.6.29-2-686: true linux-image-2.6.29-2-686/preinst/bootloader-initrd-2.6.29-2-686: true linux-image-2.6.29-2-686/postinst/depmod-error-initrd-2.6.29-2-686: false linux-image-2.6.29-2-686/preinst/elilo-initrd-2.6.29-2-686: true linux-image-2.6.29-2-686/prerm/would-invalidate-boot-loader-2.6.29-2-686: true linux-image-2.6.29-2-686/preinst/lilo-initrd-2.6.29-2-686: true linux-image-2.6.29-2-686/preinst/abort-overwrite-2.6.29-2-686: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533276: adding parm to mount.cifs
I've found the answer. When enabling mount.cifs debug mode (echo 3 /proc/fs/cifs/cifsFYI), we can see errors in the dmesg output : # dmesg [ 7845.389949] fs/cifs/xattr.c: CIFS VFS: in cifs_getxattr as Xid: 50 with uid: 0 [ 7845.389953] fs/cifs/xattr.c: illegal xattr request security.selinux (only user namespace supported) [ 7845.389956] fs/cifs/xattr.c: CIFS VFS: leaving cifs_getxattr (xid = 50) rc = -95 [ 7845.389964] fs/cifs/xattr.c: CIFS VFS: in cifs_getxattr as Xid: 51 with uid: 0 [ 7845.389967] fs/cifs/xattr.c: CIFS VFS: leaving cifs_getxattr (xid = 51) rc = -95 so using the parm nouser_xattr fix the issue : $ mount -t cifs //192.168.224.1/MYSHARE$ TEST -o username=admin,uid=10066,gid=1,dir_mode=0755,nouser_xattr --verbose $ ll . drwxr-xr-x 1 admin utilisa._du_domaine 0 jun 11 17:14 TEST
Processed: tagging 533258
Processing commands for cont...@bugs.debian.org: tags 533258 pending Bug#533258: scripts/init-top/framebuffer: i915 needs intel-agp too Tags were: patch Tags added: pending 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532159: [iwlagn] Does not take kill switch changes into account
On Sun, 07 Jun 2009, Josselin Mouette wrote: Package: linux-2.6 Version: 2.6.29-5 Severity: normal When the iwlagn module is loaded, it takes into account the kill switch status; radio is disabled when the switch is off. However, it doesn’t take into account any changes in the switch status. To enable radio, I have to unload the module, change the switch state, and load the module again. My hardware: 14:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) Subsystem: Intel Corporation Device 1101 Flags: fast devsel, IRQ 19 Memory at fe40 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlagn Kernel modules: iwlagn can you please retest on 2.6.30? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533292: linux-image-2.6.30-1-686 (sid), KMS enabled: black screen
On Tue, 16 Jun 2009, Jos van Wolput wrote: Package: linux-image-2.6.30-1-686 (2.6.30-1, Sid) System: Debian/sid, KMS enabled (module i915 modeset=1 loaded) Processor: Intel Pentium M 1.70 GHz Chipset: 852GM/855GM Severity: important After upgrading the kernel-image to linux-image-2.6.30-1-686 (Sid) booting ends with a black screen, no more key input, not starting X. This only happens when KMS is enabled by loading module i915 modeset=1 at boot time. Loading module i915 modeset=0 boots normally. This issue didn't occur with linux-image-2.6.30-rc8-686 (snapshot 13741) and previous releases from Debian kernel-archive. Cheers, Jos van Wolput please stop reporting the same bug Nxtimes, report upstream on bugzilla.kernel.org with correct info dmesg lscpi -vv and let us know the bug number -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533258: scripts/init-top/framebuffer: i915 needs intel-agp too
On Mon, 15 Jun 2009, Aaron M. Ucko wrote: Package: initramfs-tools Version: 0.93.3 Severity: normal Tags: patch The i915 DRM module doubles as a framebuffer of sorts, at least in kernel mode-setting setups; like its cousins intelfb and i810fb, it effectively requires intel-agp despite not actually using any of its symbols. As such, could you please arrange for scripts/init-top/framebuffer to give it the same treatment, per the following patch?: thanks, applied see latest git http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 533208 is forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1287
Processing commands for cont...@bugs.debian.org: forwarded 533208 http://bugzilla.openvz.org/show_bug.cgi?id=1287 Bug#533208: IPv6 not working in OpenVZ containers with Lenny 2.6.26-openvz kernel Noted your statement that Bug has been forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1287. 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533357: linux-2.6: please add b43: Add fw capabilities, to support OpenFWWF 5.1
Package: linux-2.6
Version: 2.6.30-1
Severity: wishlist
Tags: patch
Hi
I am currently packaging [1], [2] the OpenFWWF (GPL2) [3] firmware for
core revision 5 Broadcom AirForce wlan chipsets [4], while the most
important patches to support OpenFWWF have already been merged for 2.6.30,
b43: Add fw capabilities 403a3a136122457165321e90b7569a321cc9ac12
has only been merged mainline yesterday [5].
I would really appreciate if you could consider adding that patch to the
next 2.6.30 kernel upload for Debian (I am using it successfully since
kernel 2.6.29), as it would make packaging openfwwf significantly easier
and avoid ugly upgrade handling.
To explain the reasoning for my request (an overview is presented at [6]),
as of now OpenFWWF doesn't support hardware encryption and QoS yet, which
are available in the proprietary Broadcom firmware (b43-fwcutter/
non-free), while b43 (until 2.6.30-git9) enables both on default, making
b43 to failing to authentificate and resulting numerous PHY resets
and firmware crashes/ restarts (potential log spam). While it is possible
to force b43 into disabling both features through a modprobe.d override
[7], this would only be required until kernel 2.6.31 enters the archive and
present some problems with the upgrade handling (introducing
/etc/modprobe.d/openfwwf.conf as a Debian conffile for ~3 months and
subsequently removing it) and additionally hard-disables QoS even in case
OpenFWWF and the proprietary firmware (b43-fwcutter/ non-free) are
coinstalled (since kernel 2.6.30, b43 first probes ${FIRMWARE_DIRS}/b43/,
before falling back to ${FIRMWARE_DIRS}/b43-open/, provided by OpenFWWF).
Assuming this patch would be merged into 2.6.30-2, this would not affect
compatibility with previous kernels, because ${FIRMWARE_DIRS}/b43-open/
is ignored until kernel 2.6.30 and therefore isn't eligible to the
described problems (only 2.6.30-1 would be).
openfwwf and b43-asm (its build-dependency), as a dfsg-free firmware for,
many devices covered by b43 are basically ready and only pending your
decision, as this patch has already been merged upstream for 2.6.31, it
only applies to kernel 2.6.30. Backports to lenny's 2.6.26 are not
reasonable (as it would require installing openfwwf under
${FIRMWARE_DIRS}/b43/ in conflict with b43-fwcutter/ non-free and the
modprobe overrides at [7]), while it would be compatible lenny-and-a-half,
assuming b43: Add fw capabilities is present.
Regarding DebianKernelPatchAcceptanceGuidelines:
- Security Fixes: FAIL
- Driver Fixes: depending on the interpretation, it was meant
to go into
2.6.30, but fell through the
cracks and basically makes a new feature
of 2.6.30 (transparent OpenFWWF
compatibility) work for the first
time and would allow to operate
these devices solely with packages
from main, once openfwwf enters
the archive.
- Stability Fixes: FAIL
- New features: YES, strictly speaking
- Out-of Tree Drivers: NO
- My favourite patch-set: NO, single patch already merged upstream
I am aware that this patch is borderline following these patch acceptance
guidelines, but hope that you might consider it nevertheless.
A short word regarding the current state of OpenFWWF, for core revision 5
devices [4], it is mostly stable, but as a reverse engineering efforts
there may be still unknown corner cases and behaviour under (articifically)
high package pressure is said to be still slightly erratic (I haven't been
able to observe such issues myself) and a decent replacement for the
proprietary firmware. core revision 6-10 devices are likely to work, but
might expose several problems in practice and are not claimed to be
supported upstream yet. core revision =11 devices do not work yet. I am
personally using this patch successfully since early 2.6.29 kernels on
BCM4306 (rev 5 core) in STA and AP modi, BCM4318 (rev 9 core) works, but
not perfectly and I have positive feedback from BCM4311/1 (rev 5 core) and
BCM4318 (rev 5 core) users.
Potential real world compatibility scenarios:
- for users who have the proprietary firmware installed already, this patch
is basically a no-op, because ${FIRMWARE_DIRS}/b43/ is always preferred
by b43.
- users with kernel = 2.6.29 and only openfwwf installed won't experience
any change, their b43 module ignores ${FIRMWARE_DIRS}/b43-open/
(openfwwf) - recent compat-wireless snapshots contain this patch already.
- users with vanilla 2.6.30 or linux-2.6 2.6.30-1 and _only_ openfwwf
installed, are not able to get a connection with b43 and openfwwf and do
experience numerous PHY resets and firmware restarts (triggered by the
netdev watchdog), manifesting itself in syslog/ kern.log (not rate
limited).
Bug#533211: xserver-xorg-video-radeon: kernel oops at shutdown if X is running with radeon
reassign 533211 drm-modules-source 2.4.11+git+20090519+f355ad8-1 Thanks On Mon, Jun 15, 2009 at 1:56 PM, Brice Goglin brice.gog...@ens-lyon.orgwrote: reassign 533211 linux-2.6 2.6.29-2 thank you Chaogui Zhang wrote: Package: xserver-xorg-video-radeon Version: 1:6.12.2-2 Severity: normal After upgrading my system a couple of days ago, the system crashes everytime I try to shutdown or reboot when X is running with the radeon driver. It drops out of X and would go into the shutdown sequence, but before it can finish that, a kernel oops occurs and it hangs there. The message scrolls through so fast that I cannot see most of it except the last part. I have to press the power button to get the system back to life. A kernel oops is a kernel bug. I am reassign to linux-2.6 then. You might want to try kernel 2.6.30. And netconsole might help you get the oops backtrace. Brice It turns out to be a problem with the drm module compiled from drm-modules-source. It does not panic if using the original drm modules from the kernel package. Sorry for the confusion. Chaogui
Processed: Re: Bug#533211: xserver-xorg-video-radeon: kernel oops at shutdown if X is running with radeon
Processing commands for cont...@bugs.debian.org: reassign 533211 drm-modules-source 2.4.11+git+20090519+f355ad8-1 Bug#533211: xserver-xorg-video-radeon: kernel oops at shutdown if X is running with radeon Bug reassigned from package `linux-2.6' to `drm-modules-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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510478: linux-image-2.6.26-1-486: kernel hangs on leap second
The actual upstream fix appears to be this: commit b845b517b5e3706a3729f6ea83b88ab85f0725b0 Author: Peter Zijlstra a.p.zijls...@chello.nl Date: Fri Aug 8 21:47:09 2008 +0200 printk: robustify printk Avoid deadlocks against rq-lock and xtime_lock by deferring the klogd wakeup by polling from the timer tick. This applies successfully to 2.6.26 and doesn't seem to be dependent on any intervening changes. It's not clear to me whether there are other cases in 2.6.26 where a printk() could trigger this deadlock. If not then I'd rather go with the simple workaround for this one case. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#531425: base: Loss of ethernet connectivity (bmac ethernet driver) after random amount of time
On Sun, 2009-06-14 at 12:09 +0200, Tor Arne Benjaminsen wrote: Sun, 14 Jun 2009 Ben Hutchings b...@decadent.org.uk wrote: On Montag, 1. Juni 2009, Tor Arne Benjaminsen wrote: Running Debian on a PowerBook G3 'WallStreet'. Using the bmac ethernet driver. Experiencing loss of ethernet connectivity (100% packet loss) after a random amount of time. Have tried running bmac as both in-kernel and as a module. Running as a module seems to lengthen the delay before loss of connectivity occurs. I am clueless as to how to diagnose this problem and would appreciate any help. Unfortunately this driver doesn't support the usual diagnostic interfaces, so there's not much I can suggest. Which kernel version are you seeing this on, and was there an earlier kernel version that did not have this problem? I'm seeing this on 2.6.29. The only other kernel version tried on the system was the one on the Debian Installer CD (2.6.26 I believe). While I didn't experience the problem on 2.6.26, the system was never running that kernel for prolonged periods of time, so I can't really say if the problem exists there or not. Would it be helpful if I compiled up an earlier version kernel and which one would you suggest? You could try installing and running kernel version 2.6.26 from lenny for a while. The only kind of diagnostic input I can provide is that I was connected to the box over SSH (using PuTTY from a Windows box) once the network went down, and the error PuTTY gave me was Incorrect MAC received on packet This implies some sort of data corruption, though that should usually be detected and corrected by TCP. If this happens again, please run ifconfig, save the output to a file, and send it to this bug. This should show some useful statistics (assuming the driver updates them properly, which I haven't checked). Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
