Hi, During some tests I've noticed that the VIDIOCGMBUF ioctl hangs on my bttv video device. It simply does not return and the process is stuck in the D+ state. With Kernel 2.6.22.9 the (attached) testcase works like a charm. The V4L2 interface is working with 2.6.24, too (at least displays xawtv the usual pixel snow). Hard and Software: 64 bit Linux 2.6.24-rc6 (todays pull) on a Intel Core 2 Duo WinTV PCI: 05:02.0 0400: 109e:036e (rev 02) 05:02.1 0480: 109e:0878 (rev 02) dmesg: Rincewin...

The kernel has a divide by zero crash when trying to run the system timer less than 100Hz. The problem is x/(HZ/USER_HZ) and related. Now x*(USER_HZ/HZ) will be used if HZ<USER_HZ. I'm running the Linux kernel under qemu and went to run a slower system timer to take less CPU (and battery) on the host. I found that the kernel paniced under emulation because of a divide by zero in three places. Here is the patch. The base git was updated today 01-05-2008. I went for a 20Hz system time by addi...

The http://www.kerneloops.org website collects kernel oops and warning reports from various mailing lists and bugzillas as well as with a client users can install to auto-submit oopses. Below is a top 10 list of the oopses collected in the last 7 days. (Reports prior to 2.6.23 have been omitted in collecting the top 10) This week, a total of 49 oopses and warnings have been reported, compared to 53 reports in the previous week. Rank 1: __ieee80211_rx Warning at net/mac80211/rx.c:1672 Report...

Practically certain to be fixed by 6addb1d6de1968b84852f54561cc9a999909b5a9; it's list_for_each_entry() walking from the entry that just got list_del() and kernels without that sucker have no protection of the list in question pissfs locking problems; AFAICS, its sysfs_get_dentry() walking into already unlinked sysfs directory node on the way to target; no exclusion against that is there and it's not trivial to add. --

This message contains a list of some regressions from 2.6.23 reported since 2.6.24-rc1 was released, for which there are no fixes in the mainline I know of.  If any of them have been fixed already, please let me know. If you know of any other unresolved regressions from 2.6.23, please let me know either and I'll add them to the list.  Also, please let me know if any of the entries below are invalid. Listed regressions statistics: Date Total Pending Unresolved -----------------...

HPT374 patch was posted. We also have a newly reported regression in USB pl2303 See [pl2303 regression] Linux 2.6.23 breaks gpsbabel's DG-100 support on linux-usb@vger.kernel.org No bug # yet but will try and sort a patch out next week. --

I just wanted to let people know that as a result of a discussion on linux-mm I've added support for the new slab allocator to my collectl utility, now making it real easy to dynamically monitor allocations along with all the other types of monitoring collectl does. I've also put together a webpage at http://collectl.sourceforge.net/SlabInfo.html to give a taste of how this all works as well as to show a few different types of output. -mark --

since the call to device_del() will occur while the pm_sleep_rwsem is still locked for writing. That's why I suggested not unregistering these devices until after everything else has been resumed and the rwsem has been dropped. Another thing to watch out for: Just in case somebody ends up calling destroy_suspended_device(dev) from within dev's own resume method, you should interchange the resume_device() and the list_move_tail() calls in dpm_resume(). Alan Stern --

It's still necessary, because destroy_suspended_device() still has to move the device from one list to another. You don't want it to end up on the dpm_locked list. Alan Stern --

That should never happen. The whole idea of destroy_suspended_device() is that the device couldn't be resumed and in fact should be unregistered because it is no longer working or no longer present. A suspend routine won't detect this sort of thing since it doesn't try to resume the device. But it wouldn't hurt to mention in the kerneldoc that destroy_suspended_device() is meant to be called only during a system resume. Alan Stern --

In the commit: =========== author Jerrold Jones <digireco@gmail.com> Mon, 22 Oct 2007 04:59:47 +0000 (00:59 -0400) committer Dmitry Torokhov <dmitry.torokhov@gmail.com> Mon, 22 Oct 2007 04:59:47 +0000 (00:59 -0400) committer Dmitry14e4020630b364cc564172a476cd6a6ac4bc7393 tree 08c56cb99138275991993b62bb28ce3b92dee833 tree | snapshot parent 858711c55f757872b11574599bfa836df8ab34c9 commit | diff Input: usbtouchscreen - add support for GoTop tablet devices Add support for GoTop Super_Q...

I recently rebased my kernel tree and discovered that my nfsroot setup no longer worked. Here's the relevat part of my cmdline: ip=192.168.2.200:192.168.2.185:192.168.2.1:255.255.255.0::eth0:off nfsroot=192.168.2.185:/my_nfsroot,v3,tcp root=/dev/nfs I discovered that now I had to change the autoconfiguration option to "on" in order to make nfsroot work. I only want to specify the IP address manually so I don't really want autoconfiguration. The current code works since it will not try autoconfigur...

Hi folks, The help for iwl3945 suggests to read some Documentation/networking/\ README.iwlwifi, but obviously this file is not there. Regards Harri --

Reorganize USB Kconfig Menu, and move USB_GADGET out into the Device Driver Menu.  This helps the USB Kconfig Menu to be more logical/usable. Patchset against 2.6.23 arch/arm/Kconfig | 2 ++ arch/v850/Kconfig | 2 ++ drivers/Kconfig | 2 ++ drivers/usb/Kconfig | 26 ++++++++++++-------------- drivers/usb/atm/Kconfig | 12 ++++++------ drivers/usb/class/Kconfig | 6 +++++- drivers/usb/core/Kconfig | 7 +++++++ drivers/usb/...

Your patch description fails to mention what is wrong with the existing solution. -- Stefan Richter -=====-==--- ---= --=-= http://arcgraph.de/sr/ --

We try not to use 'select' on subsystems and try to limit its use to library-like code that is relatively small. Selecting SCSI breaks both of those efforts. Furthermore, we try to give the user help here in both the comments and help text. --- ~Randy desserts: http://www.xenotime.net/linux/recipes/ --

Only if used within the current limitations of Kconfig. And that requires you to use select only to select symbols with no dependencies. In this case we do not know if BLOCK is enabled or not. Sam --

We are not talking about Aunt Tillie [1] since she anyway does not build her own kernel. The vast majority of kconfig users should be covered by the "system administrator" use case. And for them it's a lot easier if they simply find the options for their hardware in the logical places without additional hassle. Whether or not an option requires an additional subsystem like e.g. SCSI or SSB are hardware and implementation details we shouldn't bother kconfig users with. cu Adrian [1]...

Better IMO to include such updates with the patch that reorganizes that part of the menu ... it's conceptually a single change, and fragmenting it will cause bisection problems. In fact, moving the gadget Kconfig in a separate step would make your main changes more clear too. --

Not everything in drivers/ is suitable for every ARM configuration. It was felt at the time better for ARM to remain separate because people didn't want to pollute drivers/Kconfig with the ARM specific conditionals. (mtd is conditional because it's not supported on ARM CPUs without alignment trap support.) -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: --

Today we would have used HAVE_ for the problematic parts and thus it would have been easy to not select what ARM does not support. But unfortunately thats not how it got designed. It would be nice to revist one day to see how much is actually needed to cleanly supprt ARM in drivers/Kconfig. Sam --

Reorganize USB Kconfig Menu, and move USB_GADGET out into the Device Driver Menu. Cc: David Brownell <david-b@pacbell.net> Cc: Greg KH <greg@kroah.com> Cc: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Al Boldi <a1426z@gawab.com> --- --- 23.a/drivers/Kconfig +++ 23.b/drivers/Kconfig @@ -70,6 +70,8 @@ source "drivers/hid/Kconfig" source "drivers/usb/Kconfig" +source "drivers/usb/gadget/Kconfig" + source "drivers/mmc/Kconfig" source "drivers...

Hi This patchset moves le*_add_cpu and be*_add_cpu functions from OCFS2 to core header (1st), converts ext3 filesystem to this API (2nd) and replaces XFS different named functions with new ones (3rd). There are many places where these functions will be useful. Just look at: grep -r 'cpu_to_[ble12346]*([ble12346]*_to_cpu.*[-+]' linux-src/ Patch for ext3 is an example how conversions will probably look like. ps: this patchset depends on http://lkml.org/lkml/2007/12/25/35 (which is in ocfs2 g...

replace all: little_endian_variable = cpu_to_leX(leX_to_cpu(little_endian_variable) + expression_in_cpu_byteorder); with: leX_add_cpu(&little_endian_variable, expression_in_cpu_byteorder); sparse didn't generate any new warning with this patch Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com> --- fs/ext3/balloc.c | 7 ++----- fs/ext3/ialloc.c | 12 ++++-------- fs/ext3/resize.c | 12 ++++-------- fs/ext3/super.c | 2 +- fs/ext3/xattr.c | 6 ++---- 5 file...

Hi Now the compat-wireless-2.6 package is working and I get an Internet connection with my rtl8187 based card. (It's on an ASUS P5B Deluxe) I used the compat-wireless-2.6 package for this log, but I have the same problem with the version integrated in kernel 2.6.24-rc6 The Access Point is some rooms away so the signal is not the best at my location. When starting the device with no fixed rate it wants to connect with 54MBit/s and as iwconfig says it was successful but I can't ping any device i...