September 2007 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] 2.6.22.7-13.1 warning
by Jan Engelhardt 26 Sep '07

26 Sep '07

nux-2.6.22.7-13.1/security/apparmor/lsm.c:948: warning: initialization from inco static int apparmor_file_mmap(struct file *file, unsigned long reqprot, unsigned long prot, unsigned long flags, unsigned long addr, unsigned long addr_only) { return aa_mmap(file, "file_mmap", prot, flags); } The file_mmap hook in struct security_operations does not have addr_only. This is already the patched SUSE variant. -- 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] Fwd: Re: Linux 2.6.22.8, pata_ali issue
by Jan Engelhardt 26 Sep '07

26 Sep '07

---------- Forwarded message ---------- Date: Tue, 25 Sep 2007 21:38:02 +0200 (CEST) From: Jan Engelhardt <jengelh(a)computergmbh.de> To: Greg KH <gregkh(a)suse.de> Cc: Oliver Pinter <oliver.pntr(a)gmail.com>, Linux Kernel Mailing List <linux-kernel(a)vger.kernel.org>, Andrew Morton <akpm(a)linux-foundation.org>, <torvalds(a)linux-foundation.org>, <stable(a)kernel.org> Subject: Re: Linux 2.6.22.8, pata_ali issue On Sep 25 2007 10:35, Greg KH wrote: >On Tue, Sep 25, 2007 at 07:03:24PM +0200, Jan Engelhardt wrote: >> So, here is something that I think should go into the next 2.6.22. >> A proper fix is already in 2.6.23-git-du-jour. > >Feel free to send the patch, with the git commit id of the upstream >commit to the stable(a)kernel.org address and we will be glad to review it >that way. 'right, it is already in the mainline kernel. So it's again the suse kernel src rpm that has it screwed up... another story. Here's your culprit: libata-update-libata-to-libata-dev-upstream-5ddf.patch * Replaces ali_init_chipset() with some new bits, essentially it removes the call to pci_read_config_byte() since the revision is now found in struct pci_dev->revision Basically 2.6.23 stuff. libata-fix-up-build-after-upstream-update.patch * changes it back to the 2.6.22 api, so that it compiles again. But only that. It FORGETS to add pci_read_config_byte() back. === libata-fix-up-build-after-upstream-update.patch >From 54ee7cd26c5e438dc15d13b60c9f8a54ca05e3fb Mon Sep 17 00:00:00 2001 From: Tejun Heo <htejun(a)gmail.com> Date: Fri, 3 Aug 2007 02:21:51 +0900 Subject: [PATCH] libata: fix up build after upstream update References: 288078 Signed-off-by: Tejun Heo <htejun(a)gmail.com> === The bug is still present in current suse kotd. >:-( Please fix it there. A cc will go to opensuse-kernel@, but other than that, I am in the wrong mood right now to do anything. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

4 5

[opensuse-kernel] Issues with USB 2.0 on one machine.
by Martin Møller 22 Sep '07

22 Sep '07

Hi there. For a long time now I have had some issues with USB 2.0 enabled on one of my machines, but *only* in Linux. In Windows everything works fine, which makes me think that there's simply something that is not implemented/wrongly detected in Linux. I get a bunch of these when the ehci-hcd module is loaded: hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad? At least 100 and they continue to show up until I unload the ehci-hcd module. My load with ehci-hcd loaded is very high. Typically about 2-3 whereas it would be around 0.5 otherwise. At one point I replied to a bug with a similar problem on the vanilla kernel and got a patch that could block a USB hub, which took care of the load issue, but would also result in my wireless rt2570 disappearing. It was loaded like this: #!/bin/sh modprobe ehci-hcd sleep 1s echo 2 > /sys/class/usb_hub/usbhub5.2/ignore date > /tmp/fix-usb.log 2&>1 I have (hopefully) attached the patch to this message. Is there any way that we can get closer to what the real problem is here? Even if it means installing some debug software in Windows and running a battery of tests, I would just really like to have working USB 2.0 again... I also wonder why the patch never made it to the kernel. It was scheduled for inclusion at one point. Maybe it has issues? For the record: This happens with almost all 2.6 kernels I have tried, SUSE or otherwise. I think I didn't see it around 2.6.5, but I'm not quite sure. 2.4.x kernels do not have the problem as far as I can tell, but then USB 2.0 is a 2.6 feature, right? If I do not load the ehci-hcd module I *can* actually see and use my wireless adapter, but naturally it maxes out at 12 Mbit/s... The machine is pretty responsive even with the high load, but is does not seem right that is should behave this way.

7 31

[opensuse-kernel] notify_change
by Miquel A. Noguera 07 Sep '07

07 Sep '07

Hi. When I try to compile: error = notify_change(dentry, &attr); under openSUSE kernel, it aborts with: error: too few arguments to function ‘notify_change' (it compiles fine with vanilla or ubuntu kernels). Can you help me to get this line succesfully compiled in openSUSE kernel too? Thanks. Miquel. -- 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] Release date for 10.1 update kernel (to catch up SLE 10 SP1)
by Andreas Vetter 06 Sep '07

06 Sep '07

Hi, is there a (planned) release date for the 10.1 update kernel that is supposed to be the same as the SLE 10 SP1 kernel released this week? We are waiting for a long time for a 10.1 kernel update now. Is there a policy for 10.1 SLE10 kernel update release dates? Or maybe it is just some (one-time) problem that delays the 10.1 update? Cheers, Andreas -- Andreas Vetter Fakultaet fuer Physik und Astronomie Universitaet Wuerzburg -- 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] building debug kernel on sles9u3
by Daniel Li 05 Sep '07

05 Sep '07

On a sles9u3 system with kernel 2.6.5-7.244-smp, 'task_struct' as defined by /usr/src/linux/include/linux sched.h in the 'kernel-source' package has been changed from sles9 base to include one more member 'unsigned long long last_run', among other changes. However, I noticed the header file 'sched.h' under /usr/include/linux has NOT been changed from the sles 9 base version, thus missing the new definition. Now, when I build my debug linux kernel from /usr/src/linux, the build process is looking under /usr/include for the kernel header files, and that causes inconsistency in the final compiled debug kernel and the running kernel, and hence my debugging session to fail. Here are my questions: 1) Why are the kernel header files under /usr/include out of sync, even after I downloaded and applied the latest patch using yast? 2) If I can't get my /usr/include header files up to date, is there a way to change the build process of 'kernel-source' to use its own include files under /usr/src/include instead of those in the standard kernel header files under /usr/include? Thanks, Daniel -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1