openSUSE Kernel March 2011

kernel@lists.opensuse.org

29 participants
16 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] RFC: Use tarballs for -rc and stable releases?
by Michal Marek 04 May '11

04 May '11

Hi, currently, -rc and stable release updates are done by adding patches to patches.kernel.org/. Especially the -rc1 patches are *huge* and cannot be paired with any other object in the repository, so their gzip-compressed size adds to the total repository size: $ git cat-file -p b9044e3353ff21f12a86788a18cf36ba1071b6ab:patches.kernel.org/patch-2.6.37-rc1 | gzip -c -9 | wc -c 14627847 that is almost 14 megabytes. So I would like to propose to more or less discontinue patches.kernel.org and instead use the SRCVERSION variable in rpm/config.sh. This is already used in the vanilla and linux-next branches and it works. Code changes are more easily reviewed in the kernel.git nowadays, tar-up.sh and sequence-patch also work if you don't have the tarball around (it generates one from git, which is arguably slower, but works), so I think it's worth doing it. Opinions? Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 9

[opensuse-kernel] Strange USB-Storage device
by Stefan Seyfried 26 Mar '11

26 Mar '11

Hi, I have a strange USB-Stick here. It's some "nano"-4G stick, only slightly bigger than the actual USB plug. With usb_storage.delay_use=1, it's found as: [139787.814139] usb 2-2: new high speed USB device using ehci_hcd and address 26 [139787.929698] usb 2-2: New USB device found, idVendor=14cd, idProduct=125b [139787.929706] usb 2-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2 [139787.929713] usb 2-2: Product: Micro Line [139787.929717] usb 2-2: Manufacturer: Intenso [139787.929722] usb 2-2: SerialNumber: 000000000021 [139787.930263] scsi23 : usb-storage 2-2:1.0 [139789.842530] scsi 23:0:0:0: Direct-Access Intenso Micro Line PQ: 0 ANSI: 0 CCS [139789.842802] sd 23:0:0:0: Attached scsi generic sg1 type 0 [139790.090805] sd 23:0:0:0: [sdb] 8054783 512-byte logical blocks: (4.12 GB/3.83 GiB) and everything is fine. With usb_storage.delay_use=5 (which is default in vanilla kernel AFAICS), it is found as: [140044.180139] usb 2-2: new high speed USB device using ehci_hcd and address 27 [140044.295636] usb 2-2: New USB device found, idVendor=14cd, idProduct=125b [140044.295644] usb 2-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2 [140044.295650] usb 2-2: Product: Micro Line [140044.295655] usb 2-2: Manufacturer: Intenso [140044.295660] usb 2-2: SerialNumber: 000000000021 [140044.296327] scsi24 : usb-storage 2-2:1.0 [140049.296759] scsi 24:0:0:0: Direct-Access-RBC PQ: 2 ANSI: 4 [140049.296943] scsi 24:0:0:0: Attached scsi generic sg1 type 14 and it does not work. Now even if it works by accident with a SUSE kernel, I'm still interested in why it is so strange. Is this a bug to report on LKML? -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 6

[opensuse-kernel] Kernel oops in shrink_dcache_for_umount_subtree+0x15d/0x230, reiserfs_xattr_shutdown
by Stefan Lucke 25 Mar '11

25 Mar '11

Hi, can you have a look at https://bugzilla.novell.com/show_bug.cgi?id=682089 . screen shot: https://bugzillafiles.novell.org/attachment.cgi?id=421283 It looks like: Re: [opensuse-kernel] Oops with 2.6.37.1-1.2-desktop OpenSUSE 11.4 was: 2.6.34.8-15 http://lists.opensuse.org/opensuse-kernel/2011-03/msg00034.html except that it is x86_64. Stefan Lucke -- 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] Question: what are the differences of kernels in opensuse repositories
by Andrés Augusto Nogueiras Meléndez 24 Mar '11

24 Mar '11

Hi to all, I'm using openSuSE 11.3 on a machine with xen. Have four machines inside: one is Dom-U and other three are virtual (two with openSuSE 11.3 and one with WinXP). I just installed the physical machine from distribution/11.3/repo/ repositories/Virtualization/openSUSE_11.3/ and updated it from update/11.3/ Now my kernels, for all my machines are the same 2.6.34.7-0.7-xen #1 SMP 2010-12-13 11:13:53 +0100 x86_64 x86_64 x86_64 GNU/Linux later I included in the real machine (DomU) repositories repositories/Kernel:/openSUSE-11.3/openSUSE_11.3/ to test the new ones available. I just discover (but can't confirm) that with one of the kernel available xen was not able to start the virtual machines. And later, browsing the repository tree discover that there are also kernels available in repositories/Kernel:/stable/openSUSE_11.3/ repositories/Kernel:/HEAD/openSUSE_11.3 Now the question (from my deepest ignorance): What are the differences of kernels in the different opensuse repositories? My guess is that repo and update contains the two very stable versions, but the other three are a mystery to me! All the best, -- [ Prof. Andrés Augusto Nogueiras Meléndez ] [ Electronic Technology Department University of Vigo ] [ Campus Lagoas Marcosende, 9 http://www.dte.uvigo.es/ ] [ 36310 - Vigo, Pontevedra Spain ]

2 1

[opensuse-kernel] xc4000 patch
by Mariusz Fik 24 Mar '11

24 Mar '11

Hi, I tested recently with folks on forum.suse.pl a patch[1] for some dvb-t tuner, which is available at http://istvanv.users.sourceforge.net/v4l/xc4000.html I made kernel[2] with it and users reported it works fine (with addition firmware, of course). And now I have a question, is there a way to push it upstream while I'm not an author of this patch? [1] - attachment [2] - https://build.opensuse.org/project/show?project=home:Fisiu:xc4000 -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member

3 3

[opensuse-kernel] XFS leaking memory?
by Stefan Seyfried 23 Mar '11

23 Mar '11

Hi all, I have seen the following repeatedly, from time to time during the last years, but only today I have probably found a way to trigger it: * create some heavy FS workload on XFS, probably pushing the machine heavily into swap * stop the workload (probably that "make -j" in a big C++ project is not such a good idea after all...) * machine stays slow, as if it had no memory, starts swapping even though there are apparently gigabytes of free memory * free shows there is lots of memory free: susi:~ # free total used free shared buffers cached Mem: 3949728 3583132 366596 0 348 199180 -/+ buffers/cache: 3383604 566124 Swap: 2093052 317460 1775592 * swapoff often fails, even though there should be enough memory according to "free" * slabtop shows there is quite some amount of space in use: Active / Total Objects (% used) : 160024 / 14304077 (1.1%) Active / Total Slabs (% used) : 11111 / 778760 (1.4%) Active / Total Caches (% used) : 117 / 220 (53.2%) Active / Total Size (% used) : 104352.71K / 3073816.64K (3.4%) Minimum / Average / Maximum Object : 0.02K / 0.21K / 4096.00K OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 13434482 0 0% 0.20K 707078 19 2828312K xfs_btree_cur 507270 0 0% 0.39K 50727 10 202908K xfs_efi_item 167297 8 0% 0.22K 9841 17 39364K xfs_buf_item 24752 21011 84% 0.03K 221 112 884K size-32 * there is no way to get rid of this short of unloading the XFS kernel module. Only unmounting the FS's does not help. I guess this is not really a SUSE kernel bug. Where to report this? And has maybe someone else seen something similar? Running FACTORY, 2.6.38-24-desktop (Kernel:HEAD), Thinkpad X200s with 4GB RAM, but I have seen similar things at least two years ago on a then current openSUSE server at home, also x86_64, also XFS. Until today I had guessed it had something to do with sparse files (running lots of kvm guests from images stored on XFS seemed to trigger it sometimes), but today it was clearly triggered by "overload the machine heavily by unbounded make -j", no sparse files involved and no kvm guests running at all. Thanks, seife -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 6

[opensuse-kernel] help needed to fix conflict in file series.conf
by doiggl＠velocitynet.com.au 22 Mar '11

22 Mar '11

Hello, How do I fix the error 'conflict in file series.conf' listed at [1] Thanks Glenn [1] https://build.opensuse.org/package/view_file?expand=0&file=series.conf&pack… My series.conf only has these lines in it. patches.rpmify/reiser4-for-2.6.37.patch patches.kernel.org/patch-2.6.37.1 patches.kernel.org/patch-2.6.37.1-2 patches.kernel.org/patch-2.6.37.2-3 patches.kernel.org/patch-2.6.37.3-4 project detail https://build.opensuse.org/package/files?package=kernel-reiser4&project=hom… -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] VMI kernel
by Trifle Menot 21 Mar '11

21 Mar '11

I read VMware will discontinue VMI. What's the status/plan for VMI kernel at suse? -- Web mail, POP3, and SMTP http://www.beewyz.com/freeaccounts.php -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

5 6

[opensuse-kernel] Problems with bind mount on OpenSUSE 11.4
by richard -rw- weinberger 16 Mar '11

16 Mar '11

Hi, bind mounts seem not to work as expected on OpenSUSE 11.4. E.g: $ mount /home /mnt -o bind $ mount | grep mnt /dev/sda1 on /mnt type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=600,barrier=0,data=ordered) $ mount | grep sda1 /dev/sda1 on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=600,barrier=0,data=ordered) /dev/sda1 on /mnt type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=600,barrier=0,data=ordered) mount shows me the for both / and /mnt /dev/sda1 as device. The expected output is: /home on /mnt type none (rw,bind) The read-only bind mount also does not work. $ mount -o bind,ro /home /mnt mount: warning: /mnt seems to be mounted read-write. $ mount | grep mnt /dev/sda1 on /mnt type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=600,barrier=0,data=ordered) I can reproduce this on OpenSUSE 11.4 using kernel-desktop-2.6.37.1-1.2.2.i586, kernel-vanilla-2.6.37.1-1.2.2.i586 and kernel-vanilla-2.6.37.3-16.1.i586 (from tumbleweed repo) But, on a CentOS 5.5 box with a hand compiled 2.6.37.3 kernel everything works as expected. Now I'm confused, is this a OpenSUSE or a kernel issue? Any ideas? -- Thanks, //richard -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 7

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Kernel March 2011