Re: [RFC] Updating boot loaders in lenny and squeeze
On Sat, Jun 26, 2010 at 08:50:27PM +0100, Ben Hutchings wrote: On Wed, 2010-06-23 at 23:31 +0200, Jonas Smedegaard wrote: On Wed, Jun 23, 2010 at 10:12:42AM -0400, Stephen Powell wrote: That does seem like a more general-purpose solution, rather than having lilo and zipl treated as special cases. But please keep the appropriate parties informed of any future design changes to update-initramfs. I myself have never used yaird, but I assume that to be consistent it should have a similar hook system. A great while back initramfs-tools and kernel packages broke the ABI coordinated across initramfs-tools, linux-2.6, yaird and kernel-package. Sure would be nice with a stable ABI again, and getting informed if it changes. That is a separate issue. What we need here is an interface for the initramfs builder to update the boot loader if necessary. No such interface exists yet, AFAIK. Agreed, this is a different ABI. The wish for such ABI being treated as a cross-package ABI still exist. One approach would be to create a page at wiki.debian.org which all interested parties could then subscribe to. I would dislike if (as in the past) we simply rely on whatever internal routines implemented by the most popular packages (initramfs-tools and minux-2.6) which others then need to track sources of. I suggest something like the following: 1. Boot loaders that maintain block lists install a script under /etc/mkinitramfs/post-update.d which takes two arguments: the kernel ABI version (uname -r) and the absolute path to an initramfs. 2. Initramfs builders call the scripts in this directory after creating, updating or deleting an initramfs by running: run-parts --verbose --exit-on-error --arg=$version --arg=$path /etc/mkinitramfs/post-update.d or similar. We could alternately use multiple directories or an argument to distinguish creation, update and deletion. However, I suspect that these scripts will need to invoke the same command in all cases. Seems reasonable to me. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#587215: [linux-image-2.6.32-5-686]
Package: linux-image-2.6.32-5-686 Version: 2.6.32-15 --- Please enter the report below this line. --- --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686 Debian Release: squeeze/sid 500 unstable mirror.hro.nl 500 unstable ftp.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== module-init-tools | 3.12~pre2-3 linux-base (= 2.6.32-15) | 2.6.32-15 initramfs-tools (= 0.55) | 0.97 OR linux-initramfs-tool | Package Status (Version) | Installed =-+-=== firmware-bnx2 | firmware-bnx2x | firmware-ipw2x00 | firmware-ivtv | firmware-iwlwifi | firmware-linux | firmware-linux-nonfree | firmware-qlogic | firmware-ralink | xen-hypervisor | Recommends (Version) | Installed ===-+- firmware-linux-free (= 2.6.32) | 2.6.32-15 libc6-i686 | 2.11.2-2 Suggests (Version) | Installed ===-+-=== linux-doc-2.6.32 | grub | OR lilo | 1:22.8-8.1 -8---8---8---8---8---8---8---8---8-- Please attach the file: /tmp/reportbug-ng-linux-image-2.6.32-5-686-pLZ_RR.txt to the mail. I'd do it myself if the output wasn't too long to handle. Thank you! -8---8---8---8---8---8---8---8---8--
Bug#587215: Info received ([linux-image-2.6.32-5-686])
--- Output from package bug script --- ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:59:47 UTC 2010 ** Command line: auto BOOT_IMAGE=Linux ro root=UUID=a9777dc3-55f7-4c80-a03a-9e9ba9ad5539 ** Not tainted ** Kernel log: [4.221225] uhci_hcd :00:1d.3: new USB bus registered, assigned bus number 5 [4.221335] uhci_hcd :00:1d.3: irq 19, io base 0xbf20 [4.221427] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [4.221490] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.221568] usb usb5: Product: UHCI Host Controller [4.221626] usb usb5: Manufacturer: Linux 2.6.32-5-686 uhci_hcd [4.221686] usb usb5: SerialNumber: :00:1d.3 [4.222116] usb usb5: configuration #1 chosen from 1 choice [4.48] hub 5-0:1.0: USB hub found [4.222310] hub 5-0:1.0: 2 ports detected [4.262744] intel_rng: FWH not detected [4.404334] usb 1-7: new high speed USB device using ehci_hcd and address 2 [4.447818] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x180b1, caps: 0xa04713/0x20/0x0 [4.486442] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 [4.536822] usb 1-7: New USB device found, idVendor=0ace, idProduct=1211 [4.536885] usb 1-7: New USB device strings: Mfr=16, Product=32, SerialNumber=0 [4.536964] usb 1-7: Product: USB2.0 WLAN [4.537019] usb 1-7: Manufacturer: ZyDAS [4.537152] usb 1-7: configuration #1 chosen from 1 choice [4.648027] usb 1-8: new high speed USB device using ehci_hcd and address 3 [4.793204] usb 1-8: New USB device found, idVendor=0b95, idProduct=1780 [4.793270] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4.79] usb 1-8: Product: AX88178 [4.793388] usb 1-8: Manufacturer: ASIX Elec. Corp. [4.793446] usb 1-8: SerialNumber: 02 [4.793929] usb 1-8: configuration #1 chosen from 1 choice [4.917708] ricoh-mmc: Ricoh MMC Controller disabling driver [4.917787] ricoh-mmc: Copyright(c) Philip Langdale [4.917870] ricoh-mmc: Ricoh MMC controller found at :02:01.2 [1180:0843] (rev 1) [4.917960] ricoh-mmc: Controller is now disabled. [5.256328] cfg80211: Using static regulatory domain info [5.256393] cfg80211: Regulatory domain: US [5.256448] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [5.256527] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [5.256590] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.256652] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.256714] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.256777] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.256839] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [5.257111] cfg80211: Calling CRDA for country: US [5.288800] sdhci: Secure Digital Host Controller Interface driver [5.288866] sdhci: Copyright(c) Pierre Ossman [5.288925] ieee80211: 802.11 data/management/control stack, git-1.1.13 [5.288985] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [5.334097] [drm] Initialized drm 1.1.0 20060810 [5.353700] firewire_ohci :02:01.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [5.432028] firewire_ohci: Added fw-ohci device :02:01.0, OHCI version 1.10 [5.469905] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [5.469987] ipw2200: Copyright(c) 2003-2006 Intel Corporation [5.470112] ipw2200 :02:03.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [5.470230] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [5.470326] ipw2200 :02:03.0: firmware: requesting ipw2200-bss.fw [5.843136] ipw2200: Radio Frequency Kill Switch is On: [5.843138] Kill switch must be turned off for wireless networking to work. [5.844320] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels) [5.844421] sdhci-pci :02:01.1: SDHCI controller found [1180:0822] (rev 19) [5.844518] sdhci-pci :02:01.1: PCI INT B - GSI 18 (level, low) - IRQ 18 [5.846677] Registered led device: mmc0:: [5.847783] mmc0: SDHCI controller on PCI [:02:01.1] using DMA [5.932111] firewire_core: created device fw0: GUID 424fc00034f71050, S400 [6.001693] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [6.001770] i915 :00:02.0: setting latency timer to 64 [6.015543] [drm] set up 7M of stolen space [6.134840] udev: renamed network interface eth0 to eth1 [6.159347] b44 :02:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [6.160961] composite sync not supported [6.161525] [drm] initialized overlay support [6.660031] usb 1-7: reset high speed USB device using ehci_hcd and address 2 [6.660156] ssb: Sonics Silicon Backplane
Processed: Re: Bug#585677: linux-image-2.6.32-5-486: impossible to mount partitions (except /)
Processing commands for cont...@bugs.debian.org: reassign 585677 initscripts Bug #585677 [initramfs-tools] linux-image-2.6.32-5-486: impossible to mount partitions (except /) Bug reassigned from package 'initramfs-tools' to 'initscripts'. Bug No longer marked as found in versions initramfs-tools/0.94.4. stop Stopping processing here. Please contact me if you need assistance. -- 585677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127763826012661.transcr...@bugs.debian.org
Processed: reassign 587290 to linux-base
Processing commands for cont...@bugs.debian.org: # initramfs-tools does not modify yaboot.conf reassign 587290 linux-base Bug #587290 [initramfs-tools] initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab Bug reassigned from package 'initramfs-tools' to 'linux-base'. Bug No longer marked as found in versions initramfs-tools/0.97. thanks Stopping processing here. Please contact me if you need assistance. -- 587290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127763850413922.transcr...@bugs.debian.org
Bug#585677: linux-image-2.6.32-5-486: impossible to mount partitions (except /)
reassign 585677 initscripts stop On Sat, Jun 26, 2010 at 09:57:21PM +0100, Ben Hutchings wrote: On Fri, 2010-06-25 at 22:49 +0200, Stéphane Blondon wrote: 2010/6/20 Ben Hutchings b...@decadent.org.uk: Please try booting with 'break=premount' added to the kernel parameters. When the boot process stops you should get an '(initramfs)' prompt. At the prompt, please run 'blkid' and send the output. Feel free to abbreviate the UUIDs if you copy the output by hand. This is what I get (the longest UUID are abbreviated (those for swap and ext3)): (initramfs) blkid /dev/sda1: SEC_TYPE=msdos UUID=6466-FB4C TYPE=vfat /dev/sda3: UUID=1E21-1DFD TYPE=vfat /dev/sda5: LABEL=XP UUID=8444-ACD1 TYPE=vfat /dev/sda6: UUID=0bd127f7-...89d0 TYPE=swap /dev/sda7: UUID=9e7a1cee-...806a SEC_TYPE=ext2 TYPE=ext3 /dev/sdb5: UUID=58027110-...91d1 SEC_TYPE=ext2 TYPE=ext3 /dev/sdb6: UUID=8a64c937-...52db SEC_TYPE=ext2 TYPE=ext3 /dev/sdb7: UUID=47f58f90-...64e5 SEC_TYPE=ext2 TYPE=ext3 (initramfs) Given that the kernel command-line has 'root=UUID=9e7a1cee-d7c8-4244-95fe-757af64d806a', and that that filesystem is accessible, I think this must be some strange bug in the initramfs scripts and not the kernel. I'll reassign it accordingly. Ben. given that the root is mounted correctly and the initramfs business is not to mount cat and dogs of /etc/fstsab, reassigning: dpkg -S /etc/init.d/mountall.sh initscripts but it might very well be a util-linux bug. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100627112156.gx9...@baikonur.stro.at
Bug#586558: [stable] [PATCH] Btrfs: should add a permission check for setfacl
On Sat, Jun 26, 2010 at 09:55:47AM -0700, Greg KH wrote:
On Sat, Jun 26, 2010 at 06:47:05AM +0200, Bastian Blank wrote:
On Fri, Jun 25, 2010 at 03:47:05PM -0700, Greg KH wrote:
On Sun, Jun 20, 2010 at 06:30:21PM +0200, Bastian Blank wrote:
This was commit 2f26afba46f0ebf155cf9be746496a0304a5b7cf.
now queued up.
Whoops, sorry. I mixed the patches up. The sent one does not even
compile with 2.6.32.
So what I now have in the stable queue for .32 is not good?
Yep.
Let me know if I need to fix something up.
The following patch is known working with .32. (The function gets a
struct inode in .32 and .34 instead of the dentry in HEAD.)
Bastian
diff --git a/fs/btrfs/acl.c b/fs/btrfs/acl.c
index 3616042..38ebe78 100644
--- a/fs/btrfs/acl.c
+++ b/fs/btrfs/acl.c
@@ -157,6 +157,9 @@ static int btrfs_xattr_set_acl(struct inode *inode, int
type,
int ret = 0;
struct posix_acl *acl = NULL;
+ if (!is_owner_or_cap(inode))
+ return -EPERM;
+
if (value) {
acl = posix_acl_from_xattr(value, size);
if (acl == NULL) {
--
You! What PLANET is this!
-- McCoy, The City on the Edge of Forever, stardate 3134.0
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100627114817.ga24...@wavehammer.waldi.eu.org
Processed: retitle 585609 to linux-base: Difficult to recover from failed device ID transition
Processing commands for cont...@bugs.debian.org: retitle 585609 linux-base: Difficult to recover from failed device ID transition Bug #585609 [linux-base] linux-base: postinstall script fails on loop-aes partitions Changed Bug title to 'linux-base: Difficult to recover from failed device ID transition' from 'linux-base: postinstall script fails on loop-aes partitions' thanks Stopping processing here. Please contact me if you need assistance. -- 585609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127764022623642.transcr...@bugs.debian.org
Bug#587290: initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab
Please send the files /etc/fstab, /etc/yaboot.conf.old and /etc/yaboot.conf from your system. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 587290, found 587290 in 2.6.32-15
Processing commands for cont...@bugs.debian.org: tags 587290 moreinfo Bug #587290 [linux-base] initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab Added tag(s) moreinfo. found 587290 2.6.32-15 Bug #587290 [linux-base] initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab Bug Marked as found in versions linux-2.6/2.6.32-15. thanks Stopping processing here. Please contact me if you need assistance. -- 587290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127764122632649.transcr...@bugs.debian.org
Bug#488566: some info
- Forwarded message from Fito . binaura...@hotmail.com - Date: Sat, 26 Jun 2010 03:39:59 + From: Fito . binaura...@... To: t...@cyrius.com Subject: kernel bug hello. i'm writing to you to inform that there's a working patch (at least it worked for me) for an important kernel bug. here's the bug and the patch: https://bugzilla.kernel.org/show_bug.cgi?id=10743 i'm a newbie on debian and linux (just a month today), so i don't know the protocol to follow informing such things, i don't know how to use the Bug Tracking System, so i write to you because i see your email on the debian bug page: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488566 i've already send an email to a person on kernel.org. Actually the patch is already on linux kernel 2.6.34, but i would really love to see it on debian packages, at least i hope it will be on squeeze. well that's all, i hope i didn't bother you, if i did sorry. thanks. _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3 - End forwarded message - -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100627135759.ge8...@jirafa.cyrius.com
Bug#587329: nfs-common: does not ignore commented out lines in fstab
Package: nfs-common
Version: 1:1.2.2-1
Severity: important
Tags: patch
The fstab read while loop in /etc/init.d/nfs-common catched my eye.
There's a real danger things may go wrong there, as commented out lines
are _not_ ignored.
The lenny version of the init script suffers from the same problem.
Please find attached a series of small patches which attempt to both
correct the potentional error mentioned above and enhance the script.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages nfs-common depends on:
ii adduser 3.112 add and remove users and groups
ii initscripts 2.88dsf-9 scripts for initializing and shutt
ii libc62.11.2-2Embedded GNU C Library: Shared lib
ii libcap2 1:2.17-2support for getting/setting POSIX.
ii libcomerr2 1.41.12-2 common error description library
ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification
ii libgssapi-krb5-2 1.8.1+dfsg-5MIT Kerberos runtime libraries - k
ii libgssglue1 0.1-4 mechanism-switch gssapi library
ii libk5crypto3 1.8.1+dfsg-5MIT Kerberos runtime libraries - C
ii libkrb5-31.8.1+dfsg-5MIT Kerberos runtime libraries
ii libnfsidmap2 0.23-2 An nfs idmapping library
ii librpcsecgss30.19-2 allows secure rpc communication us
ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra
ii lsb-base 3.2-23.1Linux Standard Base 3.2 init scrip
ii netbase 4.42Basic TCP/IP networking system
ii portmap 6.0.0-2 RPC port mapper
ii ucf 3.0025 Update Configuration File: preserv
nfs-common recommends no packages.
nfs-common suggests no packages.
-- no debconf information
Cheers,
--
Cristian--- nfs-common.~1~ 2008-07-14 12:02:48.0 +0200
+++ nfs-common 2010-06-27 15:02:17.0 +0200
@@ -81,7 +81,7 @@
esac
case $NEED_IDMAPD in
-yes|no)
+yes|no)
;;
*)
NEED_IDMAPD=$AUTO_NEED_IDMAPD
@@ -89,7 +89,7 @@
esac
case $NEED_GSSD in
-yes|no)
+yes|no)
;;
*)
NEED_GSSD=$AUTO_NEED_GSSD
--- nfs-common.~2~ 2010-06-27 15:02:17.0 +0200
+++ nfs-common 2010-06-27 15:06:38.0 +0200
@@ -23,7 +23,7 @@
NEED_GSSD=
PIPEFS_MOUNTPOINT=/var/lib/nfs/rpc_pipefs
RPCGSSDOPTS=
-if [ -f $DEFAULTFILE ]; then
+if [ -r $DEFAULTFILE ]; then
. $DEFAULTFILE
fi
@@ -40,7 +40,7 @@
AUTO_NEED_IDMAPD=no
AUTO_NEED_GSSD=no
-if [ -f /etc/fstab ]; then
+if [ -r /etc/fstab ]; then
exec 90 /etc/fstab
while read DEV MTPT FSTYPE OPTS REST
@@ -68,7 +68,7 @@
# condition in nfs-kernel-server's init script does, which has a value in
# itself.
#
-if [ -f /etc/exports ] grep -q '^[[:space:]]*[^#]*/' /etc/exports; then
+if [ -r /etc/exports ] grep -q '^[[:space:]]*[^#]*/' /etc/exports; then
AUTO_NEED_IDMAPD=yes
fi
@@ -97,7 +97,7 @@
esac
do_modprobe() {
-if [ -x /sbin/modprobe -a -f /proc/modules ]
+if [ -x /sbin/modprobe -a -r /proc/modules ]
then
modprobe -q $1 || true
fi
--- nfs-common.~3~ 2010-06-27 15:06:38.0 +0200
+++ nfs-common 2010-06-27 15:11:19.0 +0200
@@ -45,6 +45,11 @@
while read DEV MTPT FSTYPE OPTS REST
do
+ case $DEV in
+ ''|\#*)
+ continue
+ ;;
+ esac
if [ $FSTYPE = nfs4 ]; then
AUTO_NEED_IDMAPD=yes
fi
--- nfs-common.~4~ 2010-06-27 15:11:19.0 +0200
+++ nfs-common 2010-06-27 15:13:39.0 +0200
@@ -50,15 +50,15 @@
continue
;;
esac
-if [ $FSTYPE = nfs4 ]; then
-AUTO_NEED_IDMAPD=yes
-fi
-case $OPTS in
-
-sec=krb5|*,sec=krb5|sec=krb5,*|*,sec=krb5i,*|sec=krb5i|*,sec=krb5i|sec=krb5i,*|*,sec=krb5i,*|sec=krb5p|*,sec=krb5p|sec=krb5p,*|*,sec=krb5p,*)
- AUTO_NEED_GSSD=yes
-;;
-esac
+ if [ $FSTYPE = nfs4 ]; then
+ AUTO_NEED_IDMAPD=yes
+ fi
+ case $OPTS in
+
+ sec=krb5|*,sec=krb5|sec=krb5,*|*,sec=krb5i,*|sec=krb5i|*,sec=krb5i|sec=krb5i,*|*,sec=krb5i,*|sec=krb5p|*,sec=krb5p|sec=krb5p,*|*,sec=krb5p,*)
+ AUTO_NEED_GSSD=yes
+ ;;
+ esac
done
exec 09 9-
@@ -79,32 +79,32 @@
case $NEED_STATD in
yes|no)
-;;
+ ;;
*)
-NEED_STATD=yes
-;;
+ NEED_STATD=yes
+ ;;
esac
case $NEED_IDMAPD in
yes|no)
-;;
+ ;;
*)
-NEED_IDMAPD=$AUTO_NEED_IDMAPD
+ NEED_IDMAPD=$AUTO_NEED_IDMAPD
;;
esac
case $NEED_GSSD in
yes|no)
-;;
+ ;;
*)
-NEED_GSSD=$AUTO_NEED_GSSD
+
Re: Call for Testing: initramfs-tools 0.97
Michael Prokop m...@debian.org wrote on 2010-06-18 23:48: we - the initramfs-tools maintainers in Debian - want to provide a solid initramfs-tools version for squeeze. The new release 0.97 is expected to fix many longstanding problems. It would be great if we could receive feedback from testers. The new release is available from Debian/unstable and is expected to install without problems in at least lenny, squeeze and sid: http://cdn.debian.net/debian/pool/main/i/initramfs-tools/initramfs-tools_0.97_all.deb SHA256:56eb56d472d0dd24c8f2fd030222586e258ec882b716f02d114865cef9c19639 No matter how your partition layout looks like (rootfs on lvm, crypto, sw-raid,...), if you're booting on physical hardware or a virtualized system (Xen, openvz, kvm,...) - please give it a shot and report any possible problems. I have checked the scripts and I was very happy to see that lilo is furthermore supported by initramfs-tools (script update-initramfs). Can I be sure that this support stay in your package? Because of changes in some other packages this would be nearly an existential question. FYI: Lilo have again an upstream developer - myself. If you have some hints for better work together with your package so feel free to send me a mail. Have a nice day, Joachim (Germany) signature.asc Description: PGP signature
Bug#587215: [linux-image-2.6.32-5-686]
linux-image-2.6.32-5-686.bug Description: Binary data
Bug#587329: fix for some errors introduced with patch 11
Another patch attached.
Cheers,
--
Cristian--- nfs-common.~13~ 2010-06-27 16:06:58.0 +0200
+++ nfs-common 2010-06-27 16:54:58.0 +0200
@@ -179,13 +179,13 @@
if [ $NEED_IDMAPD = yes ]
then
log_progress_msg idmapd
- start-stop-daemon --stop --oknodo --quiet --name rpc.idmapd || {
+ start-stop-daemon --stop --oknodo --quiet --name rpc.idmapd ||
do_errout $?
fi
if [ $NEED_STATD = yes ]
then
log_progress_msg statd
- start-stop-daemon --stop --oknodo --quiet --name rpc.statd || {
+ start-stop-daemon --stop --oknodo --quiet --name rpc.statd ||
do_errout $?
fi
do_umount $PIPEFS_MOUNTPOINT 2/dev/null || :
RE: setup multimodem gprs on debian (multitech system
After having download the firmware, # cp /home/dis/Download/mts_gsm.fw/lib//firmware/ # rmmod ti_usb_3410_5052 modprobe ti_usb_3410_5052 ERROR: Module ti_usb_3410_5052 does not exist in /proc/modules From: b...@decadent.org.uk To: jtam...@hotmail.com CC: bluestonech...@gmail.com; bj...@mork.no; basilarc...@gmail.com; debian-kernel@lists.debian.org Date: Sat, 26 Jun 2010 23:49:55 +0100 Subject: Re: setup multimodem gprs on debian (multitech system On Sat, 2010-06-26 at 22:19 +, lejkt lejkt wrote: Hello, i recently buy a multi-tech system modem (multi-modem GRPS, model: MTCBA-G-U-F4), using USB to connect to my computer. My system is debian 5.0, with kernel (version 2.6.34) After connection, i should normaly see device detected at /dev/ttyUSB0. But i saw nothing. # lsusb(show) Bus 001 Device 004: ID 06e0:f111 Multi-Tech Systems, Inc i also perform: dmesg and less /proc/bus/usb/devices Nothing nothing... Thank for help. It looks like we're missing the firmware for this. Please download http://git.infradead.org/users/dwmw2/linux-firmware.git/blob_plain/master:/mts_gsm.fw and install it in the directory /lib/firmware, then run: rmmod ti_usb_3410_5052 modprobe ti_usb_3410_5052 This should get the modem working. Let us know whether it does. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. After having download the firmware, # cp /home/dis/Download/mts_gsm.fw/lib//firmware/ # rmmod ti_usb_3410_5052 modprobe ti_usb_3410_5052 ERROR: Module ti_usb_3410_5052 does not exist in /proc/modules _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
RE: setup multimodem gprs on debian (multitech system
On Sun, 2010-06-27 at 15:46 +, lejkt lejkt wrote: After having download the firmware, # cp /home/dis/Download/mts_gsm.fw/lib//firmware/ # rmmod ti_usb_3410_5052 modprobe ti_usb_3410_5052 ERROR: Module ti_usb_3410_5052 does not exist in /proc/modules That's odd. Just 'modprobe ti_usb_3410_5052' then. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#587329: fix for some errors introduced with patch 11
On Sun, 2010-06-27 at 17:05 +0200, Cristian Ionescu-Idbohrn wrote: Another patch attached. So far as I can see, these patches break down as: 02. I don't think we want to do this. I think the script should fail noisily if files are present but unreadable. 03. Fixes this bug. 10. Fixes another minor bug. 11 + 13. Worthwhile cleanup. 12. Worthwhile cleanup. 01, 04-09. Stylistic changes, matter of preference. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
VCS for nfs-utils and ethtool
Since we're co-maintaining nfs-utils, I think it's about time we put it in version control. I would favour putting it in git under the kernel project. Similarly for ethtool. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: (was Bug#570350) Google Chrome
On 27/06/10 03:02, Ben Hutchings wrote: On Fri, 2010-06-25 at 12:01 +0100, Berni Elbourn wrote: Re: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570350 Sorry but the patch at the bottom of the thread doesn't seem to like me: Preparation: apt-get source linux-2.6 apt-get install build-essential fakeroot apt-get build-dep linux-2.6 cd linux-2.6-2.6.26 fakeroot debian/rules source fakeroot make -f debian/rules.gen setup_amd64_none_amd64 Applying the patch: red:~/linux-2.6-2.6.26# patch -p1 ../linux-patches/0001-pid_ns-zap_pid_ns_processes-fix-the-child_reaper-cha.patch patching file kernel/pid_namespace.c Hunk #1 FAILED at 179. 1 out of 1 hunk FAILED -- saving rejects to file kernel/pid_namespace.c.rej [...] You're trying to apply the patch in the wrong directory. The top level contains Linux 2.6.26, unmodified except for DFSG-compliance. You need to apply the patch in debian/build/source_amd64_none, where the source is copied and patched prior to building the package. However, given that the patch filename ends in '~' it seems that I accidentally sent the wrong version of the patch. Also, I think we should actually apply a second patch. So, please try the two attached patches. Ben. Patches now applied and kernel built fine. First I am testing testing on an Amd64 laptop which needed m-a to compile the broadco-sta modules. The binary-arch_amd64_none_amd64 procedure did not produce: linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb which is a needed by: linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb Pressing on I used headers common version from the online live Lenny repositories. So far no Google-chrome kernel errors. More in a few days time. Berni PS: For future how does one build the official headers common package on Amd64? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c278f81.1050...@elbournb.fsnet.co.uk
Bug#587215: [linux-image-2.6.32-5-686]
OK, and for comparison, can you repeat that while using the original driver? (Temporarily remove the driver you got from the manufacturer.) Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#587329: fix for some errors introduced with patch 11
On Sun, 27 Jun 2010, Ben Hutchings wrote: On Sun, 2010-06-27 at 17:05 +0200, Cristian Ionescu-Idbohrn wrote: Another patch attached. So far as I can see, these patches break down as: 02. I don't think we want to do this. I think the script should fail noisily if files are present but unreadable. Seems reasonable. But in that case you may want to abort, instead of continueing, when prequisites are not fulfilled. 03. Fixes this bug. Check. 10. Fixes another minor bug. Check. 11 + 13. Worthwhile cleanup. Check. 12. Worthwhile cleanup. Check. 01, 04-09. Stylistic changes, matter of preference. Right. Cherripick as you please, but think efficientcy and maintainence ease ;) Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1006272001040.21...@somehost
Re: [RFC] Updating boot loaders in lenny and squeeze
On Sat, 2010-06-26 at 22:43 -0400, Stephen Powell wrote: On Sat, 26 Jun 2010 20:45:58 -0400 (EDT), Ben Hutchings wrote: On Sat, 2010-06-26 at 20:35 -0400, Stephen Powell wrote: Sounds reasonable to me. This is for Squeeze+1, right? No, we need something like this for squeeze. On Fri, 18 Jun 2010 17:51:11 +0200, Maximilian Attems wrote: On Fri, 18 Jun 2010 10:55:35 -0400 (EDT), Stephen Powell wrote: As for update-initramfs -u, it *will* invoke lilo if lilo is installed and do_bootloader = yes is specified in /etc/kernel-img.conf, which I highly recommend. this fall back will be gone as soon as squeeze is out. so you'd really need to gear up. (The above quotes are from the bug log for Debian bug number 505609.) This led me to believe that, for lilo and zipl anyway, specifying do_bootloader = yes in /etc/kernel-img.conf would be sufficient to get the boot loader run when update-initramfs -u is executed at least through and including the Squeeze release. But in Squeeze+1 this fallback, as Max put it, will no longer work and therefore a new architecture will be needed. Did I misunderstand something? Maybe we can scrape along without changing this, but since we already need to change the boot loader packages for squeeze we may as well sort this out. This also gives Jonas a chance to make yaird just work without having to introduce the same sort of kluge. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: [RFC] Updating boot loaders in lenny and squeeze
On Sun, 2010-06-27 at 10:19 +0200, Jonas Smedegaard wrote: On Sat, Jun 26, 2010 at 08:50:27PM +0100, Ben Hutchings wrote: On Wed, 2010-06-23 at 23:31 +0200, Jonas Smedegaard wrote: On Wed, Jun 23, 2010 at 10:12:42AM -0400, Stephen Powell wrote: That does seem like a more general-purpose solution, rather than having lilo and zipl treated as special cases. But please keep the appropriate parties informed of any future design changes to update-initramfs. I myself have never used yaird, but I assume that to be consistent it should have a similar hook system. A great while back initramfs-tools and kernel packages broke the ABI coordinated across initramfs-tools, linux-2.6, yaird and kernel-package. Sure would be nice with a stable ABI again, and getting informed if it changes. That is a separate issue. What we need here is an interface for the initramfs builder to update the boot loader if necessary. No such interface exists yet, AFAIK. Agreed, this is a different ABI. The wish for such ABI being treated as a cross-package ABI still exist. One approach would be to create a page at wiki.debian.org which all interested parties could then subscribe to. I would dislike if (as in the past) we simply rely on whatever internal routines implemented by the most popular packages (initramfs-tools and minux-2.6) which others then need to track sources of. I agree. I suggest something like the following: 1. Boot loaders that maintain block lists install a script under /etc/mkinitramfs/post-update.d which takes two arguments: the kernel ABI version (uname -r) and the absolute path to an initramfs. 2. Initramfs builders call the scripts in this directory after creating, updating or deleting an initramfs by running: run-parts --verbose --exit-on-error --arg=$version --arg=$path /etc/mkinitramfs/post-update.d or similar. We could alternately use multiple directories or an argument to distinguish creation, update and deletion. However, I suspect that these scripts will need to invoke the same command in all cases. Seems reasonable to me. There is a minor problem with this, which is that it will likely result in updating the boot loader twice during a kernel installation or upgrade. We could avoid that by specifying that: 3. Boot loaders must install kernel hook scripts named beginning with 'zz-'. All other packages must use names that sort before this. (This ensures that the boot loader update happens last.) 4. Initramfs builders may omit calling initramfs hook scripts when they are invoked from a kernel hook script. We're still left with the question of how to transition from the current mess. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#587290: initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab
On 06/27/10 08:19, Ben Hutchings wrote: Please send the files /etc/fstab, /etc/yaboot.conf.old and /etc/yaboot.conf from your system. Ben. OK. Here they are: /etc/yaboot.conf from the hda6 partition (see note [1]) ## yaboot.conf generated by debian-installer ## ## run: man yaboot.conf for details. Do not make changes until you have!! ## see also: /usr/share/doc/yaboot/examples for example configurations. ## ## For a dual-boot menu, add one or more of: ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ # boot = /dev/hda2 boot = /dev/disk/by-label/bootstrap device=/p...@f200/mac...@17/at...@1f000/d...@0: partition=6 # root = /dev/hda6 root = UUID=88a47bea-8c36-4a09-b418-747e2396feb2 timeout=100 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot enablecdboot image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img image=/boot/vmlinux.old label=old read-only initrd=/boot/initrd.img.old # This entry automatically added by the Debian installer for an existing # Linux installation on /dev/hda4. image=/p...@f200/mac...@17/at...@1f000/d...@0:4,/boot/vmlinux label=hda4-Linux root=/p...@f200/mac...@17/at...@1f000/d...@0:4 append=root=/dev/hda4 ro initrd=/p...@f200/mac...@17/at...@1f000/d...@0:4,/boot/initrd.img # This entry added by Rick for an existing # Linux installation on /dev/hda5. image=/p...@f200/mac...@17/at...@1f000/d...@0:5,/boot/vmlinux-2.6.27-1.ydl61.5 label=hda5-Linux read-only root=/p...@f200/mac...@17/at...@1f000/d...@0:5 append=rhgb quiet root=/dev/hda5 initrd=/p...@f200/mac...@17/at...@1f000/d...@0:5,/boot/initrd-2.6.27-1.ydl61.5.img /etc/fstab from hda6 [1] # /etc/fstab: static file system information. # # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc /proc procdefaults 0 0 # / was on /dev/hda6 during installation UUID=88a47bea-8c36-4a09-b418-747e2396feb2 / ext3 errors=remount-ro 0 1 # /home was on /dev/md127 during installation # UUID=fa18ea9a-bf45-42c6-9eb5-9d67aa80eeb9 /home ext3defaults 0 2 /dev/md127/home ext3defaults 0 3 # swap was on /dev/hda3 during installation # /dev/hda3 noneswapsw 0 0 LABEL=SWAP-hda3 noneswapsw 0 0 # /dev/hdc/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/cdrom/media/cdrom0 udf,iso9660 user,noauto 0 0 /etc/fstab from hda4 [2] # /etc/fstab: static file system information. # # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procdefaults0 0 # / was on /dev/hda4 during installation UUID=2494caa7-fb49-4cbe-81ee-b594788f4d85 / ext3 errors=remount-ro 0 1 # swap was on /dev/hda3 during installation UUID=e672ba0d-2c2e-4b03-9e4e-7a71f39c44b9 noneswapsw 0 0 /dev/hdc/media/cdrom0 udf,iso9660 user,noauto 0 0 /etc/yaboot.conf from hda4 [2] ## yaboot.conf generated by debian-installer ## ## run: man yaboot.conf for details. Do not make changes until you have!! ## see also: /usr/share/doc/yaboot/examples for example configurations. ## ## For a dual-boot menu, add one or more of: ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ boot=/dev/hda2 device=/p...@f200/mac...@17/at...@1f000/d...@0: partition=4 root=/dev/hda4 timeout=100 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot enablecdboot image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img image=/boot/vmlinux.old label=old read-only initrd=/boot/initrd.img.old # This entry automatically added by the Debian installer for an existing # Linux installation on /dev/hda5. image=/p...@f200/mac...@17/at...@1f000/d...@0:5,/boot/vmlinux-2.6.27-1.ydl61.5 label=hda5-linux root=/p...@f200/mac...@17/at...@1f000/d...@0:5 append=ro rhgb quiet root=LABEL=/ initrd=/p...@f200/mac...@17/at...@1f000/d...@0:5,/boot/initrd-2.6.27-1.ydl61.5.img # This entry automatically added by the Debian installer for an existing # Linux installation on /dev/hda6.
Bug#488566: some info
On Sun, 2010-06-27 at 14:57 +0100, Martin Michlmayr wrote:
- Forwarded message from Fito . binaura...@hotmail.com -
Date: Sat, 26 Jun 2010 03:39:59 +
From: Fito . binaura...@...
To: t...@cyrius.com
Subject: kernel bug
hello.
i'm writing to you to inform that there's a working patch (at least it
worked for me) for an important kernel bug. here's the bug and the
patch:
https://bugzilla.kernel.org/show_bug.cgi?id=10743
i'm a newbie on debian and linux (just a month today), so i don't know
the protocol to follow informing such things, i don't know how to use
the Bug Tracking System, so i write to you because i see your email on
the debian bug page:
The BTS is email-based; you can click on the bug number at the top of a
report to start writing a message in your mail client. But now you
should just reply-to-all.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488566
i've already send an email to a person on kernel.org. Actually the
patch is already on linux kernel 2.6.34, but i would really love to
see it on debian packages, at least i hope it will be on squeeze.
well that's all, i hope i didn't bother you, if i did sorry.
OK, here are two new versions of that patch which can be applied to the
kernel packages in 'lenny' or 'squeeze'. Please can you test one or
both of them, following the procedure at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
to rebuild the kernel package.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
From: Bart Hartgers bart.hartg...@gmail.com
Date: Sun, 14 Feb 2010 13:04:50 +0100
Subject: [PATCH] sata_via: Delay on vt6420 when starting ATAPI DMA write
commit a55ab496ea9c820b7192c15ef1fbf3291edfe638 upstream.
When writing a disc on certain lite-on dvd-writers (also rebadged
as optiarc/LG/...) connected to a vt6420, the ATAPI CDB ends
up in the datastream and on the disc, causing silent corruption.
Delaying between sending the CDB and starting DMA seems to
prevent this.
I do not know if there are burners that do not suffer from
this, but the patch should be safe for those as well.
There are many reports of this issue, but AFAICT no solution was
found before. For example:
http://lkml.indiana.edu/hypermail/linux/kernel/0802.3/0561.html
Signed-off-by: Bart Hartgers bart.hartg...@gmail.com
Signed-off-by: Jeff Garzik jgar...@redhat.com
[bwh: Adjust context for 2.6.32]
---
drivers/ata/sata_via.c | 17 -
1 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/drivers/ata/sata_via.c b/drivers/ata/sata_via.c
index 2a17fa3..08f6549 100644
--- a/drivers/ata/sata_via.c
+++ b/drivers/ata/sata_via.c
@@ -40,6 +40,8 @@
#include linux/blkdev.h
#include linux/delay.h
#include linux/device.h
+#include scsi/scsi.h
+#include scsi/scsi_cmnd.h
#include scsi/scsi_host.h
#include linux/libata.h
@@ -72,6 +74,7 @@ static int vt8251_scr_write(struct ata_link *link, unsigned int scr, u32 val);
static int svia_scr_write(struct ata_port *ap, unsigned int sc_reg, u32 val);
static void svia_noop_freeze(struct ata_port *ap);
static int vt6420_prereset(struct ata_link *link, unsigned long deadline);
+static void vt6420_bmdma_start(struct ata_queued_cmd *qc);
static int vt6421_pata_cable_detect(struct ata_port *ap);
static void vt6421_set_pio_mode(struct ata_port *ap, struct ata_device *adev);
static void vt6421_set_dma_mode(struct ata_port *ap, struct ata_device *adev);
@@ -107,6 +110,7 @@ static struct ata_port_operations vt6420_sata_ops = {
.inherits = ata_bmdma_port_ops,
.freeze = svia_noop_freeze,
.prereset = vt6420_prereset,
+ .bmdma_start = vt6420_bmdma_start,
};
static struct ata_port_operations vt6421_pata_ops = {
@@ -247,6 +251,17 @@ static int vt6420_prereset(struct ata_link *link, unsigned long deadline)
return 0;
}
+static void vt6420_bmdma_start(struct ata_queued_cmd *qc)
+{
+ struct ata_port *ap = qc-ap;
+ if ((qc-tf.command == ATA_CMD_PACKET)
+ (qc-scsicmd-sc_data_direction == DMA_TO_DEVICE)) {
+ /* Prevents corruption on some ATAPI burners */
+ ata_sff_pause(ap);
+ }
+ ata_bmdma_start(qc);
+}
+
static int vt6421_pata_cable_detect(struct ata_port *ap)
{
struct pci_dev *pdev = to_pci_dev(ap-host-dev);
From e9879d6c97f6a7605a0a4c03cdb8afd80ed771f3 Mon Sep 17 00:00:00 2001
From: Ben Hutchings b...@decadent.org.uk
Date: Sun, 27 Jun 2010 19:04:56 +0100
Subject: [PATCH] sata_via: Delay on vt6420 when starting ATAPI DMA write
commit a55ab496ea9c820b7192c15ef1fbf3291edfe638 upstream.
When writing a disc on certain lite-on dvd-writers (also rebadged
as optiarc/LG/...) connected to a vt6420, the ATAPI CDB ends
up in the datastream and on the disc, causing silent corruption.
Delaying between sending the CDB and starting DMA seems to
prevent this.
I do not know if there are burners that do not suffer from
this, but the patch should be safe for those as well.
There are many reports of this issue, but AFAICT no
Processed: unarchiving 570350, reopening 570350, fixed 570350 in 2.6.32-5
Processing commands for cont...@bugs.debian.org:
unarchive 570350
Bug #570350 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] [chrome]
linux-image-2.6.26-2-amd64: kernel BUG at kernel/exit.c:822!
Bug #542115 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] [chrome]
linux-image-2.6.26-2-686: kernel BUG at kernel/exit.c:822!
Unarchived Bug 570350
Unarchived Bug 542115
reopen 570350
Bug #570350 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] [chrome]
linux-image-2.6.26-2-amd64: kernel BUG at kernel/exit.c:822!
Bug #542115 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] [chrome]
linux-image-2.6.26-2-686: kernel BUG at kernel/exit.c:822!
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
fixed 570350 2.6.32-5
Bug #570350 [linux-2.6] [chrome] linux-image-2.6.26-2-amd64: kernel BUG at
kernel/exit.c:822!
Bug #542115 [linux-2.6] [chrome] linux-image-2.6.26-2-686: kernel BUG at
kernel/exit.c:822!
There is no source info for the package 'linux-2.6' at version '2.6.32-5' with
architecture ''
Unable to make a source version for version '2.6.32-5'
Bug Marked as fixed in versions 2.6.32-5.
Bug Marked as fixed in versions 2.6.32-5.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
570350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.12776687861974.transcr...@bugs.debian.org
Bug#585609: linux-base: postinstall script fails on loop-aes partitions
On Saturday 26 June 2010 22:50:42 Ben Hutchings wrote: On Fri, 2010-06-25 at 14:45 +0100, Adam Spragg wrote: r...@host:~# dpkg --configure --pending Setting up linux-base (2.6.32-15) ... tune2fs 1.41.12 (17-May-2010) tune2fs: Bad magic number in super-block while trying to open /dev/sda6 Couldn't find valid filesystem superblock. tune2fs failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1045, STDIN line 10. Without asking any questions? Hmm, that makes things difficult. Yup, no questions at all asked, and no apparent way to recover. I think you can work around this by purging linux-base and then reintstalling. Yup, that then asked me if I wanted to update fstab and friends to use UUIDs instead of (unstable) device names, to which I replied no, and it installed fine then. But I should change the post-installation script to recover from this and start asking questions again. Probably a good idea. :-) Thanks, Adam -- Adam Spragg adam.spr...@octaltelecom.co.uk Developer Octal Telecom http://www.octaltelecom.co.uk/ It reverses the logical flow of conversation! Why? No. Should I top post? http://www.google.com/search?q=%22top+posting%22 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201006272103.34537.adam.spr...@octaltelecom.co.uk
Bug#587355: i915: X locks up when trying to play DVD on Thinkpad X40
Package: linux-image-2.6.32-5-686 Version: 2.6.32-15 Severity: important I ran into this on a freshly installed Thinkpad X40 with todays Debian/Squeeze. The external VGA connector is connected to a video projector. I plugged in a USB DVD player, installed libdvdcss2 and tried to play the DVD using vlc. This caused X to lock up and the kernel to report a crash. Searching for Hangcheck timer elapsed... GPU hung on bugs.debian.org using Google, sent me to similar bugs, but not for this model. Some bugs are URL: http://bugs.debian.org/551803 , URL: http://bugs.debian.org/573264 , URL: http://bugs.debian.org/574478 and URL: http://bugs.debian.org/576848 . The last one point to a kernel patch available from URL: https://bugs.freedesktop.org/show_bug.cgi?id=27187 that is said to fix a cache coherency issue. I have not tested it myself. Before the crash, the VGA output would flicker a lot whenever the machine was doing anything (like I moved the mouse or installed a package), and the image would only stand still when I did not move the mouse. This seem similar to the bug report URL: http://bugs.debian.org/570696 , but I am not sure if it is the same one. [250593.916039] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [250593.916058] render error detected, EIR: 0x [250593.916090] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 114368 at 114367) [250593.975787] [ cut here ] [250593.975797] kernel BUG at /build/buildd-linux-2.6_2.6.32-15-i386-fb7Hfg/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/gpu/drm/i915/intel_display.c:1917! [250593.975804] invalid opcode: [#1] SMP [250593.975809] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_full [250593.975814] Modules linked in: isofs udf crc_itu_t nfs lockd fscache nfs_acl auth_rpcgss sunrpc acpi_cpufreq cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats ppdev lp parport rfcomm sco bridge stp bnep l2cap crc16 bluetooth binfmt_misc uinput fuse sg sr_mod cdrom loop snd_intel8x0 snd_intel8x0m snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm pcmcia snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq yenta_socket ipw2200 rsrc_nonstatic snd_timer i915 libipw snd_seq_device pcmcia_core lib80211 drm_kms_helper pl2303 snd thinkpad_acpi drm tpm_tis usb_storage usbserial i2c_i801 rfkill shpchp nsc_ircc i2c_algo_bit tpm tpm_bios evdev battery irda crc_ccitt psmouse serio_raw pcspkr nvram ac soundcore snd_page_alloc i2c_core rng_core video pci_hotplug button output processor ext3 jbd mbcache dm_mod sd_mod crc_t10dif ata_generic uhci_hcd sdhci_pci sdhci ata_piix mmc_core thermal libata ehci_hcd led_class e1000 thermal_sys scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] [250593.975926] [250593.975931] Pid: 24769, comm: Xorg Not tainted (2.6.32-5-686 #1) 2371H4G [250593.975935] EIP: 0060:[f8423647] EFLAGS: 00013282 CPU: 0 [250593.975958] EIP is at intel_crtc_dpms_overlay+0x31/0x42 [i915] [250593.975962] EAX: fffb EBX: ef65d180 ECX: EDX: 0001bec0 [250593.975966] ESI: ef668000 EDI: 6014 EBP: 00070180 ESP: c9c93c5c [250593.975970] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [250593.975975] Process Xorg (pid: 24769, ti=c9c92000 task=eff4aec0 task.ti=c9c92000) [250593.975979] Stack: [250593.975981] f8425325 ef5a f6f4e400 00070184 00070008 f6f4e400 [250593.975989] 0 ef5a 0003 f84228e9 ef5a f8434100 f6f4e6ec f84354a4 [250593.975998] 0 f837272f f6f4e6e0 c9c93d74 e2a55900 0002 f6f4e5ac f8373a50 [250593.976007] Call Trace: [250593.976007] [f8425325] ? i9xx_crtc_dpms+0x181/0x264 [i915] [250593.976007] [f84228e9] ? intel_crtc_dpms+0x1c/0xb5 [i915] [250593.976007] [f837272f] ? drm_helper_disable_unused_functions+0x104/0x130 [drm_kms_helper] [250593.976007] [f8373a50] ? drm_crtc_helper_set_config+0x544/0x6b5 [drm_kms_helper] [250593.976007] [c109b51d] ? unmap_mapping_range+0x7b/0x1f9 [250593.976007] [c10c23ec] ? destroy_inode+0x1c/0x2b [250593.976007] [c10bfb93] ? d_kill+0x3e/0x43 [250593.976007] [c10bfb93] ? d_kill+0x3e/0x43 [250593.976007] [c10ae5c0] ? kmem_cache_free+0x78/0xaf [250593.976007] [c10c1100] ? d_alloc_name+0x41/0x4c [250593.976007] [f82c78ca] ? drm_framebuffer_cleanup+0x4a/0xa7 [drm] [250593.976007] [f842492f] ? intel_user_framebuffer_destroy+0x1f/0x4a [i915] [250593.976007] [f82c733c] ? drm_fb_release+0x4c/0x65 [drm] [250593.976007] [f82c0dcf] ? drm_release+0x2c2/0x4c5 [drm] [250593.976007] [c10b4207] ? __fput+0xd5/0x170 [250593.976007] [c10b18dc] ? filp_close+0x4e/0x54 [250593.976007] [c103252c] ? put_files_struct+0x60/0xa6 [250593.976007] [c1033b87] ? do_exit+0x1d4/0x5c6 [250593.976007] [c1033fd8] ? do_group_exit+0x5f/0x82 [250593.976007] [c103e926] ? get_signal_to_deliver+0x30d/0x32f [250593.976007] [c103d19d] ? signal_wake_up+0x23/0x31
Bug#587290: initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab
reassign 587290 yaboot thanks On Sun, 2010-06-27 at 15:12 -0400, Rick Thomas wrote: On 06/27/10 08:19, Ben Hutchings wrote: Please send the files /etc/fstab, /etc/yaboot.conf.old and /etc/yaboot.conf from your system. [...] [1] the hda6 partition is using my modified /usr/sbin/ybin that I submitted with my bugreport #580455. So it capable of dealing with fstab and yaboot.conf using UUID= to identify partitions. Without the modified ybin, I have to edit those files to use the conventional /dev/hdxn designations. [2] the hda4 partition has the stock, unmodified, /usr/sbin/ybin . Fortunately, the installed creates its /etc/yaboot.conf using conventional /dev/hdxn. But it leaves a ticking time-bomb in the form of UUID= designations in /etc/fstab . The next time yaboot.conf is created (e.g. with a kernel upgrade) it will pick up those designations and ybin will crash. The kernel package does *not* modify /etc/yaboot.conf like this. (linux-base will modify it one-time only.) This is a bug in the yabootconfig script which is part of yaboot. yaboot maintainers, you need to make yabootconfig accept UUID and LABEL specfications in /etc/fstab and in the kernel root parameter. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#587290: initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab
Processing commands for cont...@bugs.debian.org: reassign 587290 yaboot Bug #587290 [linux-base] initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab Bug reassigned from package 'linux-base' to 'yaboot'. Bug No longer marked as found in versions linux-2.6/2.6.32-15. thanks Stopping processing here. Please contact me if you need assistance. -- 587290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12776739909582.transcr...@bugs.debian.org
Bug#573144: linux-image-2.6-686: kernel freezes related to i915 handle error
Hello, I am experiencing the same problem in 2.6.32-5-686 and 2.6.34-1-686 on my Acer laptop with i855 chipset. System freezes randomly as described by Eric. I guess that 2.6.32-3-686 was fine, but I am not sure (have not this kernel anymore). Thanks, Zbynek -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4724.595.936-4489-1144568503-1277673...@seznam.cz
Re: [RFC] Updating boot loaders in lenny and squeeze
On Sun, 27 Jun 2010 14:22:07 -0400 (EDT), Ben Hutchings wrote: There is a minor problem with this, which is that it will likely result in updating the boot loader twice during a kernel installation or upgrade. We could avoid that by specifying that: 3. Boot loaders must install kernel hook scripts named beginning with 'zz-'. All other packages must use names that sort before this. (This ensures that the boot loader update happens last.) I'm glad to see that someone is finally beginning to see the need for a naming convention for hook scripts to control execution order. Franz Pop brought up this topic in May of 2009, but no-one seemed to think it was important then. (See http://lists.debian.org/debian-kernel/2009/03/msg00611.html) 4. Initramfs builders may omit calling initramfs hook scripts when they are invoked from a kernel hook script. We're still left with the question of how to transition from the current mess. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1832443220.328974.1277684570933.javamail.r...@md01.wow.synacor.com
[DRAFT] Policy for Linux kernel, initramfs, boot loader update process
I propose the following policy for squeeze and later releases. This affects all Linux kernel, initramfs builder and boot loader packages, and the installer. I regret that this is happening so late in the release cycle, but currently a kernel update can easily leave the system unbootable and this does need to be addressed before release and I want to do so in a way that is reasonably clean and maintainable. --- 1. Packages for boot loaders that need to be updated whenever the files they load are modified (i.e. those that store a block list) must install hook scripts in /etc/kernel/postinst.d and /etc/kernel/postrm.d, which will be called on installation/upgrade and removal of kernel packages, respectively. The arguments given to all kernel hook scripts are the kernel ABI version (the string that uname -r reports) and the absolute path to the kernel image. The environment variable DEB_MAINT_PARAMS will contain the arguments given to the kernel maintainer script, single-quoted. Since these boot loaders should be updated as the last step during installation/upgrade and removal, hook scripts for boot loaders must be named using the prefix 'zz-' and no other packages may use this prefix or one that sorts later by the rules used by run-parts. A postrm hook script should warn but exit with code 0 if the boot loader configuration file still refers to the kernel image that has been removed. 2. Packages for boot loaders that need to be updated whenever the files they load are modified must also install hook scripts in /etc/mkinitramfs/post-update.d. Initramfs builders must call these scripts using run-parts after they create, update or delete an initramfs. The arguments given to these hook scripts are the kernel ABI version and the absolute path to the initramfs image. 3. Initramfs builders must complete their work before returning from the kernel postinst hook script. [initramfs-tools currently uses a trigger to defer this because it can also be invoked twice, but this means it also has to know how to update specific boot loaders.] 4. During a kernel package installation, upgrade or removal, various boot loader hooks may be invoked (in this order): a. A postinst_hook or postrm_hook command set by the user or the installer in /etc/kernel-img.conf b. A hook script in /etc/mkinitramfs/post-update.d c. A hook script in /etc/kernel/postinst.d or .../postrm.d To avoid unnecessary updates, the hooks invoked at step a and b may check whether $DPKG_MAINTSCRIPT_PACKAGE begins with 'linux-image-' and do nothing in this case. [Is this sensible or is it too 'clever'?] 5. Kernel and initramfs builder packages must not invoke boot loaders except via hooks. If /etc/kernel-img.conf contains an explicit 'do_bootloader = yes', kernel package maintainer scripts should warn that this is now ignored. 6. The installer must not define do_bootloader, postinst_hook or postrm_hook in /etc/kernel-img.conf. --- I'm particularly interested to hear whether there are any upgrade issues I have not addressed. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
