openSUSE Kernel January 2011

kernel@lists.opensuse.org

36 participants
33 discussions

[opensuse-kernel] [patch #2 0/5] scripts/sequence-patch.sh: Add some useful options
by Jeff Mahoney 05 Oct '11

05 Oct '11

Hi all - There are a few things I do every time I expand the source tree with sequence-patch.sh. Or, rather, things I should do and forget to do a lot. The first I always remember to do: Copy the config I want to test with to my build directory. The second I forget more often than not: Expand the kABI references into my build directory. One of the things that bites me occasionally is when there are kABI changes that go un-noticed until the automated build checker flags them and sends me an email yelling at me for my carelessness. This patch adds three options to scripts/sequence-patch.sh to take care of these automatically. --build-dir=PATH allows you to specify the build directory you'll be using. It will create the directory if it doesn't exist. It defaults to $PATCH_DIR. --config=ARCH-FLAVOR allows you to specify the config you'll use. It will copy the config to your build directory. It is not a fatal error if the config does not exist. It will just not copy one. --kabi allows you to direct sequence-patch to expand the kABI references into your build directory. Since the references are arch/flavor specific, it depends on --config=ARCH-FLAVOR. It is not a fatal error if the kABI reference doesn't exist since this is always the case in the master branch. The --build-dir PATH is subject to shell expansion. It is expanded late enough in the script that most variables should be available. There are also three new variables available when --config is used: $CONFIG contains the --config contents. $CONFIG_ARCH contains the arch part of the config. $CONFIG_FLAVOR contains the flavor part. For reference, I have this in my .bashrc: export SEQUENCE_PATCH_ARGS="--config=x86_64-desktop --build-dir=~/src/scratch/build/\$CONFIG_ARCH/linux-\$SRCVERSION-\$TAG-\$CONFIG_FLAVOR --kabi" I've also added patches for --ctags and --cscope which will automatically generate the databases for either of those tools in the build directory after the source tree is expanded. - Issues addressed in patchset #2: - Help text is now a here document for easy addition of more documentation - Explanation of which variables are allowed by --build-dir - Missing rpm/modversions script is not an error on older branches - Missing symvers files are not errors - Uses true/false for simple feature flags -Jeff -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

5 13

[opensuse-kernel] [PATCH] scripts: add patch-tags-from-git
by Brandon Philips 09 Mar '11

09 Mar '11

usage: patch-tags-from-git <filename> <kernel checkout> Adds a Git-commit: tag from the From header also adds a Patch-mainline: tag if <kernel checkout> is given Signed-off-by: Brandon Philips <bphilips(a)suse.de> --- scripts/patch-tags-from-git | 62 +++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 62 insertions(+), 0 deletions(-) create mode 100755 scripts/patch-tags-from-git diff --git a/scripts/patch-tags-from-git b/scripts/patch-tags-from-git new file mode 100755 index 0000000..2277376 --- /dev/null +++ b/scripts/patch-tags-from-git @@ -0,0 +1,62 @@ +#!/bin/bash +# Add suse Kernel repo headers to a patch created using git-format-patch +# +# Brandon Philips <bphilips(a)suse.de> + +if [ $# -lt 1 ]; then + echo "usage: $0 <filename> <kernel checkout>" + echo "Adds a Git-commit: tag from the From header" + echo "also adds a Patch-mainline: tag if <kernel checkout> is given" + exit 1 +fi + +FILE=$1 + +if [ ! -f $FILE ]; then + echo "No such file $1" + exit 2 +fi + +commit=$(head -n1 $FILE | sed -n "s%From\s$[0-9a-f]*$\s.*%\1%p") + +if [ "z$commit" = "z" ]; then + echo "$FILE doesn't look like a patch from git" +else + patch-tag -A git-commit="$commit" $FILE +fi + +if [ $# -ne 2 ]; then + exit 0 +fi + +DIR=$2 + +commit=$(patch-tag -p git-commit $FILE | grep -i "git-commit:" | sed "s%.*:\s$.*$%\1%g") + +if [ "z$commit" = "z" ]; then + echo "No git-commit tag in $FILE" + exit 3 +fi + +export GIT_DIR=$DIR/.git + +if [ ! -d $GIT_DIR ]; then + echo "No such directory $GIT_DIR" + echo 4 +fi + +mainline=$(git describe --contains $commit 2> /dev/null) + +if [ "z$mainline" = "z" ]; then + git show $commit > /dev/null + if git show $commit > /dev/null 2> /dev/null; then + merged=$(basename $DIR) + patch-tag -A Patch-mainline="Merged into $merged" $FILE + exit 0 + else + echo "$commit from $FILE does not exist in $DIR" + exit 5 + fi +fi + +patch-tag -A Patch-mainline="$mainline" $FILE -- 1.7.2.2 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 4

[opensuse-kernel] Testmail
by Sascha Manns 30 Jan '11

30 Jan '11

Just a testmail. Please ignore -- Sincerely Yours Sascha Manns openSUSE Community & Support Agent openSUSE Membership Comitee openSUSE Electioncomitee openSUSE Marketing Team Packager in Build Service Blog: http://saigkill.wordpress.com Web: http://www.saschamanns.de -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

Re: [opensuse-kernel] Patch Kernel 2.6.34.7-0.7-desktop and rebuilt it - problem building rpm
by Crismon 29 Jan '11

29 Jan '11

Now I win!!!! :) This is an italian how-to: http://www.crismonblog.org/opensuse-11.2/pinnacle-pctv-340e-se-opensuse-11.… kernel-2.6.35.x-applicare-patch.html Thanks again for your support -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] invalid option in make cloneconfig
by Dave Howorth 27 Jan '11

27 Jan '11

I recently experienced an error whilst trying to compile a kernel and I don't understand what it is or what its implications might be, so I'm hoping someboady can advise me. I have an 11.2 system and I have installed the kernel from the Kernel:/HEAD/11.2 repository. I'm intending to make a minor change to investigate a hardware issue, but first I tried to set up my compile environment and simply recompile that kernel. Here's what I saw: /usr/src/linux # ls -ld ../linux lrwxrwxrwx 1 root root 15 Jan 25 23:43 ../linux -> linux-2.6.37-41 /usr/src/linux # make clean /usr/src/linux # make cloneconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf Cloning configuration file /proc/config.gz scripts/kconfig/conf: invalid option -- 'D' See README for usage info make[1]: *** [cloneconfig] Error 1 make: *** [cloneconfig] Error 2 I looked at the README but didn't find anything. I grepped the tree but didn't find any info. I googled and found one hit to the forums with a post suggesting to "zcat /proc/config.gz > .config". After I did that, the make cloneconfig ran without error. So I'm interested in what went wrong and whether it has any lasting effects that will come back to bite me. Cheers, Dave -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 2

[opensuse-kernel] preload kmp failing in Kernel:stable
by Greg KH 24 Jan '11

24 Jan '11

Hi all, The preload kmp is failing again in Kernel:stable. I can't seem to figure out where the "canonical" version of this code is at in order to fix it. Anyone know which repo is the "real" one? Is it the one in Kernel:HEAD? If so, it's failing there as well :) Actually, why do we require this kmp in the first place? I'm getting tired of having it keep the Tumbleweed kernel updates from pushing out to users properly. If it's so necessary, shouldn't we merge the thing upstream? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

7 16

[opensuse-kernel]
by Michal Hocko 24 Jan '11

24 Jan '11

subscribe -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] Cpuscaling - need to modprobe acpi-cpufreq
by Bjørn Lie 23 Jan '11

23 Jan '11

Hi Need some input as to whether this is a bug or expected behavior. In order to have working cpu freq scaling i need to modprobe acpi-cpufreq manually. ie it does not get loaded during boot I see this in both 11.3 livecd and in current factory ( using kernel 2.6.37-18-desktop ) grep model.name /proc/cpuinfo model name : Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz Note that this is a desktop system, not a laptop. ------ I tried however a ubuntu livecd and there i had cpuscaling ( speedsteping ) out of the box If more info is needed please advise as to what. ..... //Bjørn -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

4 6

[opensuse-kernel] openSUSE-11.4 branch is open / master is now 2.6.38-rc2
by Jeff Mahoney 22 Jan '11

22 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - Now that 2.6.38-rc2 has been released, I've merged it into master. The 2.6.37-based kernel has been branched for the 11.4 release into, predictably, the openSUSE-11.4 branch. Current users of Kernel:HEAD for 11.4 testing should switch to the Kernel:openSUSE-11.4 repository once it's established. Michal - When you get a chance, can you add the Kernel:openSUSE-11.4 project to OBS? I tried to but don't seem to have the needed permissions in the Kernel project. It wouldn't have gotten updates yet anyway, but I was going to copy the Kernel:HEAD packages to it. Thanks! - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk07YacACgkQLPWxlyuTD7JeQwCbBv9bm2U404QQPF4n/Ccr6h4/ g74AoJxs94lIY7aUYc8osLPnRRTjBNuD =9sah -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] {error message} - File listed twice
by doiggl＠velocitynet.com.au 20 Jan '11

20 Jan '11

Hello, When compiling a patched vanilla kernel I get a message "File listed twice" in the build process. Questions - In what file is it listed twice ?, I ask so the second entry can be removed before the check is done. - What routine calls this check? RPM build errors: File listed twice: /boot/vmlinux-2.6.36.3-27-vanilla.gz File listed twice: /boot/vmlinux-2.6.36.3-27-vanilla.gz Installed (but unpackaged) file(s) found: /lib/firmware/3com/3C359.bin /lib/firmware/3com/typhoon.bin . . . [ 2587.788870] SysRq : Power Off [ 2589.544596] Power down. For a full log see near end of [1] {its a long logfile}. Spec file is at [2] Thanks for your help Glenn [1] - https://build.opensuse.org/package/rawlog?arch=x86_64&package=kernel-vanill… [2] - https://build.opensuse.org/package/view_file?file=kernel-vanilla.spec&packa… -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Kernel January 2011