Re: [PATCH] mmc: Multi-sector writes

Pierre Ossman <[EMAIL PROTECTED]> wrote: > > >I'm thinking that it would be better to not have the config option there > >and then re-add it late in the 2.6.14 cycle if someone reports problems > >which cannot be fixed. Or at least make it default to 'y' so we get more > >testing coverage,

Re: [PATCH] mmc: Multi-sector writes

Andrew Morton wrote: >The fact that this is enabled under the experimental >CONFIG_MMC_BULKTRANSFER seems unfortunate. I mean, if the code works OK >then we should just enable it unconditionally, no? > > > It was made this way to make Russell more open to it. I have since not recieved any

Re: [PATCH] add transport class symlink to device object

On Mon, Aug 15, 2005 at 09:32:44AM +0100, Russell King wrote: > On Mon, Aug 15, 2005 at 01:43:03AM +0100, Matthew Wilcox wrote: > > On Sun, Aug 14, 2005 at 11:25:25PM +0100, Russell King wrote: > > > Eww. Do you really want one struct device per tty with all the > > > memory each one eats? > > >

Re: [PATCH] cpm_uart: Fix dpram allocation and non-console uarts

On 8/8/05, Kumar Gala <[EMAIL PROTECTED]> wrote: > (A believe Marcelo would like to see this in 2.6.13, but I'll let him > fight over that ;) > > * Makes dpram allocations work > * Makes non-console UART work on both 8xx and 82xx > * Fixed whitespace in files that were touched > > Signed-off-by:

Re: [PATCH] add transport class symlink to device object

On Mon, Aug 15, 2005 at 05:41:17PM -0500, James Bottomley wrote: > On Sun, 2005-08-14 at 16:02 +0100, Matthew Wilcox wrote: > > /sys/class/tty/ttyS0/device -> > > ../../../devices/parisc/0/0:0/pci:00/:00:04.0 > > /sys/class/tty/ttyS1/device -> > >

Re: ACPI Standby and nvidia ethernet driver causes network errors and drops

Hi Avuton, I have not been able to duplicate this without going into standby, thus this bug may have existed before 2.6.12, as I just started using ACPI standby. Could you try the attached patch? Lots of error are often caused by half duplex/full duplex mismatches, and such a bug was just

[RFC/PATCH]reconfigure MSI registers after resume

Hi, It appears pci_enable_msi doesn't reconfigure msi registers if it successfully look up a msi for a device. It assumes the data and address registers unchanged after calling pci_disable_msi. But this isn't always true, such as in a suspend/resume circle. In my test system, the registers

2.2.26 kernel on FC1

Hai.. I want to install 2.2.26 kernel on FC1 (2.4.22) for testing purpose of my modem.. How can I install it... regards aruran __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To

Re: [PATCH] Add pci_walk_bus function to PCI core (nonrecursive)

On Thu, Aug 18, 2005 at 02:58:28PM +1000, Benjamin Herrenschmidt wrote: > I wonder if it's finally time to implement proper race free list > iterators in the kernel. Not that difficult... A small struct iterator > with a list head and the current elem pointer, and the "interated" list > containing

[patch 2.6.13-rc6] watchdog: fix oops in softdog driver

Wim, The softdog watchdog timer has a bug that can create an oops: 1. Load the module without the nowayout option. 2. Open the driver and close it without writing 'V' before close. 3. Unload the module. The timer will continue to run... 4. Oops happens when timer fires. Reported

Re: pmac_nvram problems

> I'm not sure why alloc_bootmem is used at all (is the nvram larger than > a couple of pages on any machine? And if it is, should it really be > cached in RAM?), but I think it should be sufficient to just use kmalloc > (well, it works for me). There used to be cases where we used the nvram

Re: [PATCH] Add pci_walk_bus function to PCI core (nonrecursive)

On Thu, 2005-08-18 at 14:33 +1000, Paul Mackerras wrote: > The PCI error recovery infrastructure needs to be able to contact all > the drivers affected by a PCI error event, which may mean traversing > all the devices under a given PCI-PCI bridge. This patch adds a > function to the PCI core that

Re: [patch] Real-Time Preemption, -RT-2.6.13-rc6-V0.7.53-11

* David Brownell <[EMAIL PROTECTED]> wrote: > > > 1 ALWAYS complete() with IRQs disabled > > > > > > 2 NEVER complete() with them disabled > > > > > > 3 SOMETIMEs complete() with them disabled. > > > > > > Right now we're with #1 which is simple, consistent and guaranteed. > > > > > >

Re: [PATCH 5/5] 2.6.13-rc5-mm1, driver for IBM Automatic Server Restart watchdog

On 229, 08 17, 2005 at 01:14:15PM -0700, Andrew Morton wrote: > Andrey Panin <[EMAIL PROTECTED]> wrote: > > > > > > This patch adds driver for IBM Automatic Server Restart watchdog hardware > > found in some IBM eServer xSeries machines. This driver is based on the ugly > > driver provided by

Re: [PATCH/RFT 4/5] CLOCK-Pro page replacement

From: Andrew Morton <[EMAIL PROTECTED]> Date: Wed, 17 Aug 2005 21:05:32 -0700 > Perhaps by uprevving the compiler version? Can't be, we definitely support gcc-2.95 and that compiler definitely has the bug on sparc64. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

[PATCH] Add pci_walk_bus function to PCI core (nonrecursive)

The PCI error recovery infrastructure needs to be able to contact all the drivers affected by a PCI error event, which may mean traversing all the devices under a given PCI-PCI bridge. This patch adds a function to the PCI core that traverses all the PCI devices on a PCI bus and under any PCI-PCI

Re: [PATCH/RFT 4/5] CLOCK-Pro page replacement

"David S. Miller" <[EMAIL PROTECTED]> wrote: > > From: Andrew Morton <[EMAIL PROTECTED]> > Date: Wed, 17 Aug 2005 17:38:18 -0700 > > > I'm prety sure we fixed that somehow. But I forget how. > > I wish you could remember :-) I honestly don't think we did. > The DEFINE_PER_CPU() definition

RE: Debugging kernel semaphore contention and priority inversion

> From: Keith Mannthey [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 17, 2005 5:33 PM > > On 8/17/05, Davda, Bhavesh P (Bhavesh) <[EMAIL PROTECTED]> wrote: > > Is there a way to know which task has a particular (struct > semaphore > > *) down()ed, leading to another task's down()

Re: [-mm PATCH 1/32] include: update jiffies/{m,u}secs conversion functions

On 17.08.2005 [16:35:06 -0700], Andrew Morton wrote: > Nishanth Aravamudan <[EMAIL PROTECTED]> wrote: > > > > Description: Clarify the human-time units to jiffies conversion > > functions by using the constants in time.h. This makes many of the > > subsequent patches direct copies of the current

Re: Latency with Real-Time Preemption with 2.6.12

On Wed, 2005-08-17 at 19:38 -0700, Sundar Narayanaswamy wrote: > Hi, > I am trying to experiment using 2.6.12 kernel with the realtime-preempt > V0.7.51-38 patch to determine the kernel preemption latencies with the > CONFIG_PREEMPT_RT mode. The test program I wrote does the following on > a

Re: [PATCH] struct file cleanup : the very large file_ra_state is now allocated only on demand.

Andi Kleen wrote: You don't want to always have bad performance though, so you could attempt to allocate if either the pointer is null _or_ it points to the global structure? Remember it's after a GFP_KERNEL OOM. If that fails most likely you have deadlocked somewhere else already because

Re: sched_yield() makes OpenLDAP slow

Joseph Fannin wrote: On Thu, Aug 18, 2005 at 02:50:16AM +0200, Bernardo Innocenti wrote: The relative timestamp reveals that slapd is spending 50ms after yielding. Meanwhile, GCC is probably being scheduled for a whole quantum. Reading the man-page of sched_yield() it seems this isn't the

Re: [PATCH] struct file cleanup : the very large file_ra_state is now allocated only on demand.

> You don't want to always have bad performance though, so you > could attempt to allocate if either the pointer is null _or_ it > points to the global structure? Remember it's after a GFP_KERNEL OOM. If that fails most likely you have deadlocked somewhere else already because Linux's handling of

[PATCH] DVB: lgdt330x check callback fix

- FIX: check if the callback is set, before calling it. - Clean up whitespace / indentation. Signed-off-by: Patrick Boettcher <[EMAIL PROTECTED]> Signed-off-by: Michael Krufky <[EMAIL PROTECTED]> --- linux/drivers/media/dvb/frontends/lgdt330x.c | 50 +-- 1 files changed, 25

Re: [PATCH] struct file cleanup : the very large file_ra_state is now allocated only on demand.

Andi Kleen wrote: I would just set the ra pointer to a single global structure if the allocation fails. Then you can avoid all the other checks. It will slow down things and trash some state, but not fail and nobody should expect good performance after out of memory anyways. The only check

Re: [PATCH/RFT 4/5] CLOCK-Pro page replacement

From: Andrew Morton <[EMAIL PROTECTED]> Date: Wed, 17 Aug 2005 17:38:18 -0700 > I'm prety sure we fixed that somehow. But I forget how. I wish you could remember :-) I honestly don't think we did. The DEFINE_PER_CPU() definition still looks the same, and the way the .data.percpu section is

Re: [PATCH] struct file cleanup : the very large file_ra_state is now allocated only on demand.

From: Andi Kleen <[EMAIL PROTECTED]> Date: Thu, 18 Aug 2005 03:05:25 +0200 > I would just set the ra pointer to a single global structure if the > allocation fails. Then you can avoid all the other checks. It will > slow down things and trash some state, but not fail and nobody > should expect

Re: 2.6.13-rc6-rt6

On Wed, 2005-08-17 at 20:02 -0400, Steven Rostedt wrote: > So I went back to the laptop's original config, and did one change. I > disabled CONFIG_SCHED_SMT, rebooted, and the system booted up. It > hasn't locked up after four boots. It did once get into some crazy bug > with scheduling while

Latency with Real-Time Preemption with 2.6.12

Hi, I am trying to experiment using 2.6.12 kernel with the realtime-preempt V0.7.51-38 patch to determine the kernel preemption latencies with the CONFIG_PREEMPT_RT mode. The test program I wrote does the following on a thread with highest priority (99) and SCHED_FIFO policy to simulate a real

Re: [RFC] [PATCH] cache pollution aware __copy_from_user_ll()

On Wed, 17 Aug 2005 23:30:13 +0900 Akira Tsukamoto <[EMAIL PROTECTED]> mentioned: > > I'm trying to understand this mechanism but I don't > > understand very well. > > My explanation was a bit ambiguous, see the code below. > Where the fp register saved? It saves fp register *inside*

Re: sched_yield() makes OpenLDAP slow

Joseph Fannin wrote: >The behavior of sched_yield changed for 2.6. I suppose the man > page didn't get updated. Now I remember reading about that on LWN or maybe KernelTraffic. Thanks! >>I also think OpenLDAP is wrong. First, it should be calling >>pthread_yield() because slapd is a

Kernel BUG at "fs/exec.c":777

(A courteasy CC: on replies would be appreciated, thanks) Hi! I get the above oops message (full details below) sometimes when running the CVS version of "cv", a gtk+ image viewer. I use kernel 2.6.12.5, but it occured on 2.6.11 that I ran earlier, too. Unfortunately, it only happens during

Re: [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update)

Wieland Gmeiner <[EMAIL PROTECTED]> writes: Is there a realistic use case where this new system call is actually useful and solves something that cannot be solved without it? If not I think it's better not to merge this to avoid unnecessary bloat. -Andi - To unsubscribe from this list: send the

Re: [PATCH 2.6.13-rc6 2/2] New Syscall: set rlimits of any process (update)

* Wieland Gmeiner ([EMAIL PROTECTED]) wrote: > diff -uprN -X linux-2.6.13-rc6-vanilla/Documentation/dontdiff > linux-2.6.13-rc6-getprlimit/include/linux/security.h > linux-2.6.13-rc6-setprlimit/include/linux/security.h > --- linux-2.6.13-rc6-getprlimit/include/linux/security.h 2005-08-17 >

Re: [patch 2.6.13-rc6] net/802/tr: use interrupt-safe locking

On Wed, Aug 17, 2005 at 02:48:25PM -0700, Jay Vosburgh wrote: > John W. Linville <[EMAIL PROTECTED]> wrote: > >Signed-off-by: Jay Vosburg <[EMAIL PROTECTED]> > > Pretty close. > > Signed-off-by: Jay Vosburgh <[EMAIL PROTECTED]> Ooops...sorry! Tired, sloppy typing... :-( > I

Re: [PATCH] struct file cleanup : the very large file_ra_state is now allocated only on demand.

On 8/18/05, Eric Dumazet <[EMAIL PROTECTED]> wrote: > Andi Kleen a écrit : > > > > >>(because of the insane struct file_ra_state f_ra. I wish this structure > >>were dynamically allocated only for files that really use it) > > > > > > How about you submit a patch for that instead? > > > > -Andi >

Re: [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update)

* Wieland Gmeiner ([EMAIL PROTECTED]) wrote: > diff -uprN -X linux-2.6.13-rc6-vanilla/Documentation/dontdiff > linux-2.6.13-rc6-vanilla/kernel/sys.c linux-2.6.13-rc6-getprlimit/kernel/sys.c > --- linux-2.6.13-rc6-vanilla/kernel/sys.c 2005-08-09 16:03:21.0 > +0200 > +++

Re: sched_yield() makes OpenLDAP slow

On Thu, Aug 18, 2005 at 02:50:16AM +0200, Bernardo Innocenti wrote: > The relative timestamp reveals that slapd is spending 50ms > after yielding. Meanwhile, GCC is probably being scheduled > for a whole quantum. > > Reading the man-page of sched_yield() it seems this isn't > the correct

Re: [PATCH] struct file cleanup : the very large file_ra_state is now allocated only on demand.

On Thu, Aug 18, 2005 at 02:40:46AM +0200, Eric Dumazet wrote: > Andi Kleen a ?crit : > > > > >>(because of the insane struct file_ra_state f_ra. I wish this structure > >>were dynamically allocated only for files that really use it) > > > > > >How about you submit a patch for that instead? > >

[PATCH 2.6.13-rc6 2/2] New Syscall: set rlimits of any process (update)

This is the second of two patches, it implements the setprlimit() syscall. Implementation: This patch provides a new syscall setprlimit() for writing a given process resource limits for i386. Its implementation follows closely the setrlimit syscall. It is given a pid as an additional argument.

[PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update)

Hi! I incorporated the changes suggested by Greg KH and Kyle Moffett and isolated some duplicated code (between setrlimit/setprlimit resp. getprlimit/setprlimit) into helper functions. This is the first of two patches, it implements the getprlimit() call. Rationale: Currently usage limits

Re: sched_yield() makes OpenLDAP slow

On Thu, 18 Aug 2005 10:50 am, Bernardo Innocenti wrote: > Hello, > > I've been investigating a performance problem on a > server using OpenLDAP 2.2.26 for nss resolution and > running kernel 2.6.12. > > When a CPU bound process such as GCC is running in the > background (even at nice 10), many

sched_yield() makes OpenLDAP slow

Hello, I've been investigating a performance problem on a server using OpenLDAP 2.2.26 for nss resolution and running kernel 2.6.12. When a CPU bound process such as GCC is running in the background (even at nice 10), many trivial commands such as "su" or "groups" become extremely slow and take

[PATCH] struct file cleanup : the very large file_ra_state is now allocated only on demand.

Andi Kleen a écrit : (because of the insane struct file_ra_state f_ra. I wish this structure were dynamically allocated only for files that really use it) How about you submit a patch for that instead? -Andi OK, could you please comment this patch ? The problem of dynamically

Re: [PATCH/RFT 4/5] CLOCK-Pro page replacement

"David S. Miller" <[EMAIL PROTECTED]> wrote: > > > +DEFINE_PER_CPU(unsigned long, evicted_pages); > > DEFINE_PER_CPU() needs an explicit initializer to work > around some bugs in gcc-2.95, wherein on some platforms > if you let it end up as a BSS candidate it won't end up > in the per-cpu section

[PATCH] Fix manual binding infinite loop

Fix for manual binding of drivers to devices. Problem is if you pass in a valid device id, but the driver refuses to bind. Infinite loop as write() tries to resubmit the data it just sent. Thanks to Michal Ostrowski <[EMAIL PROTECTED]> for pointing the problem out. Signed-off-by: Greg

[PATCH 6/7] rename locking functions - convert init_MUTEX* users, part 4

Convert users of init_MUTEX and init_MUTEX_LOCKED to init_mutex and init_mutex_locked - part 4. Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- fs/xfs/linux-2.6/xfs_buf.c |4 ++-- kernel/printk.c |2 +- mm/slab.c|2 +-

RE: Question regarding HPET the 2.6 series kernel.

When it is supported in BIOS, you will see a HPET line similar to below in initial ACPI messages. ACPI: OEMB (v001 A M I AMI_OEM 0x05000510 MSFT 0x0097) @ 0xdffdf040 ACPI: HPET (v001 A M I OEMHPET 0x05000510 MSFT 0x0097) @ 0xdffd7480 And when it is supported in BIOS, kernel always

[PATCH 4/7] rename locking functions - convert init_MUTEX* users, part 2

Convert users of init_MUTEX and init_MUTEX_LOCKED to init_mutex and init_mutex_locked - part 2. Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- drivers/infiniband/ulp/ipoib/ipoib_main.c |4 ++-- drivers/input/gameport/gameport.c |2 +- drivers/input/input.c

[PATCH 3/7] rename locking functions - convert init_MUTEX* users, part 1

Convert users of init_MUTEX and init_MUTEX_LOCKED to init_mutex and init_mutex_locked - part 1. Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- Documentation/i2c/writing-clients|2 +- arch/arm/oprofile/common.c |2 +- arch/i386/kernel/ldt.c

[PATCH 0/7] rename locking functions

Consider the naming of these functions : sema_init() init_MUTEX() init_MUTEX_LOCKED() init_rwsem() They are not named very consistent, the naming is confusing and ugly with the mix of case and some are named init_* and some *_init. I propose to clean that up by renaming the functions so

[PATCH 5/7] rename locking functions - convert init_MUTEX* users, part 3

Convert users of init_MUTEX and init_MUTEX_LOCKED to init_mutex and init_mutex_locked - part 3. Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- drivers/s390/net/ctctty.c |2 +- drivers/s390/s390mach.c |2 +- drivers/sbus/char/vfc_dev.c |2 +-

[PATCH 2/7] rename locking functions - convert sema_init users

Convert users of sema_init to use init_sema instead. Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- arch/ia64/kernel/perfmon.c|2 +- arch/ia64/kernel/salinfo.c|4 ++-- arch/ia64/sn/kernel/xp_main.c |2 +-

[PATCH 1/7] rename locking functions - do the rename

This patch renames sema_init to init_sema, init_MUTEX to init_mutex and init_MUTEX_LOCKED to init_mutex_locked and at the same time creates 3 (deprecated) wrapper functions with the old names. Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- include/asm-alpha/semaphore.h | 31

[PATCH 7/7] rename locking functions - add entry to feature-removal-schedule.txt

Document sema_init, init_MUTEX & init_MUTEX_LOCKED as being deprecated and going away in early 2006. Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- Documentation/feature-removal-schedule.txt |9 + 1 files changed, 9 insertions(+) ---

Re: 2.6.13-rc6-rt6

On Wed, 2005-08-17 at 18:23 +0200, Ingo Molnar wrote: > > > > Using IPI Shortcut mode > > khelper/794[CPU#0]: BUG in set_new_owner at kernel/rt.c:916 > > this is a 'must not happen'. Somehow lock->held list got non-empty. > Maybe some use-after-free thing? Havent seen it myself. Well, I added

Re: [PATCH] fix dst_entry leak in icmp_push_reply()

Ollie Wild wrote: If the ip_append_data() call in icmp_push_reply() fails, ip_flush_pending_frames() needs to be called. Otherwise, ip_rt_put() is never called on inet_sk(icmp_socket->sk)->cork.rt, which prevents the route (and net_device) from ever being freed. I've attached a patch which

Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6

On Thu, 18 Aug 2005 09:48 am, Peter Williams wrote: > Con Kolivas wrote: > > On Thu, 18 Aug 2005 09:15 am, Peter Williams wrote: > >>Con Kolivas wrote: > > He did a make allyesconfig which is a bit different and probably far too > > i/o bound. By the way a single kernel compile is hardly a

Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6

Con Kolivas wrote: On Thu, 18 Aug 2005 09:15 am, Peter Williams wrote: Con Kolivas wrote: On Wed, 17 Aug 2005 18:10, Peter Williams wrote: Michal Piotrowski wrote: Hi, here are schedulers benchmark (part2): [bits deleted] Here's a summary of your output generated using the attached

BUG? [PATCH] driver core: Add the ability to bind drivers to devices from userspace

If a driver's probe function returns -ENXIO or -ENODEV, driver_probe_device() will translate that to return 0 (comments argue it is not an error). Consequently driver_bind() will return 0 resulting in the write system-call that initiated all of this in returning 0 as well. If one uses "echo" to

Re: Debugging kernel semaphore contention and priority inversion

On 8/17/05, Davda, Bhavesh P (Bhavesh) <[EMAIL PROTECTED]> wrote: > Is there a way to know which task has a particular (struct semaphore *) > down()ed, leading to another task's down() blocking on it? I would add a field to struct semaphore that tracks the current process. In your various up and

Re: [-mm PATCH 1/32] include: update jiffies/{m,u}secs conversion functions

Nishanth Aravamudan <[EMAIL PROTECTED]> wrote: > > Description: Clarify the human-time units to jiffies conversion > functions by using the constants in time.h. This makes many of the > subsequent patches direct copies of the current code. > > > /* Parameters used to convert the timespec

Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6

On Thu, 18 Aug 2005 09:15 am, Peter Williams wrote: > Con Kolivas wrote: > > On Wed, 17 Aug 2005 18:10, Peter Williams wrote: > >>Michal Piotrowski wrote: > >>>Hi, > >>>here are schedulers benchmark (part2): > >>>[bits deleted] > >> > >>Here's a summary of your output generated using the attached

Delivery reports about your e-mail

ALERT! This e-mail, in its original form, contained one or more attached files that were infected with a virus, worm, or other type of security threat. This e-mail was sent from a Road Runner IP address. As part of our continuing initiative to stop the spread of malicious viruses, Road Runner

Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6

Con Kolivas wrote: On Wed, 17 Aug 2005 18:10, Peter Williams wrote: Michal Piotrowski wrote: Hi, here are schedulers benchmark (part2): [bits deleted] Here's a summary of your output generated using the attached Python script. | Build Statistics | Overall Statistics

Re: [rfc][patch] API for timer hooks

On Wed, 2005-08-17 at 21:41 +0400, Stas Sergeev wrote: > I guess now I realized how you (and Nish) > assume I could use it: is it that I > should set CONFIG_HZ to the value I > need at compile-time, and just remove > all the timer reprogramming from the > driver in a hope the dynamic-tick patch >

Re: [PATCH] mmc: Multi-sector writes

Pierre Ossman <[EMAIL PROTECTED]> wrote: > > Adds support for writing multiple sectors at once. This allows > back-to-back transfers of sectors giving roughly double write throughput. > > To be able to detect which sector is causing problems the system falls > back to single sector writes if a

Debugging kernel semaphore contention and priority inversion

Is there a way to know which task has a particular (struct semaphore *) down()ed, leading to another task's down() blocking on it? I'm trying to debug a priority inversion caused by potentially a real low priority SCHED_OTHER task (potentially a kernel thread like kjournald) holding an

Re: watchdog-mm git tree

>Author: Jiri Slaby <[EMAIL PROTECTED]> >Date: Tue Aug 16 14:35:42 2005 -0700 > >[WATCHDOG] removes pci_find_device from i6300esb.c > >This patch changes >pci_find_device to pci_get_device (encapsulated in for_each_pci_dev) in >i6300esb watchdog card with appropriate adding pci_dev_put. Generated

Re: [UPDATE PATCH] push rounding up of relative request to schedule_timeout()

On 17.08.2005 [12:51:17 -0700], George Anzinger wrote: > Nishanth Aravamudan wrote: > ~ > >>IMNSHO we should not get too parental with kernel only interfaces. > >>Adding 1 is easy enough for the caller and even easier to explain in the > >>instructions (i.e. this call sleeps for X jiffies

[PATCH] proc_ipmi_root depends on CONFIG_PROC_FS

proc_ipmi_root is only defined for CONFIG_PROC_FS, #ifdef it for export as well. Signed-Off-By: Baruch Even <[EMAIL PROTECTED]> -- drivers/char/ipmi/ipmi_msghandler.c |2 ++ 1 files changed, 2 insertions(+) Index: k/drivers/char/ipmi/ipmi_msghandler.c

Re: fix-comment-in-loopback-driver.patch added to -mm tree

Applied. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [patch 2.6.13-rc6] net/802/tr: use interrupt-safe locking

From: "John W. Linville" <[EMAIL PROTECTED]> Date: Wed, 17 Aug 2005 16:49:59 -0400 > Change operations on rif_lock from spin_{un}lock_bh to > spin_{un}lock_irq{save,restore} equivalents. Some of the > rif_lock critical sections are called from interrupt context via >

Re: [patch 2.6.13-rc6] net/802/tr: use interrupt-safe locking

John W. Linville <[EMAIL PROTECTED]> wrote: >Change operations on rif_lock from spin_{un}lock_bh to >spin_{un}lock_irq{save,restore} equivalents. Some of the >rif_lock critical sections are called from interrupt context via >tr_type_trans->tr_add_rif_info. The TR NIC drivers call tr_type_trans

Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6

On Thu, 18 Aug 2005 04:04, Michal Piotrowski wrote: > Hi, > here are additional staircase scheduler benchmarks. > > (make all -j8) > > scheduler: > staircase > > sched_compute=1 > real49m48.619s > user77m20.788s > sys 6m7.653s Very nice thank you. Since you are benchmarking, here is

help! forcedeth network errors and packet drops - Was: ACPI Standby and nvidia ethernet driver causes network errors and drops

Reference (was): http://marc.theaimsgroup.com/?l=linux-kernel=112421051105982=2 Corrections: 1) It is not the 'nvidia' driver, it is the 'forcedeth' ethernet driver 2) It does _not_ only happen after standby, I have finally experienced errors and drops without going into standby. Now, with this

[PATCH] ppc64: iommu vmerge fix]

From: Brian King <[EMAIL PROTECTED]> (Looks quite bad, should probably get in right away) The patch below fixes a bug in the PPC64 iommu vmerge code which results in the potential for iommu_unmap_sg to go off unmapping more than it should. This was found on a test system which resulted in PCI

Re: [RFC] IPV4 long lasting timer function

From: Thomas Gleixner <[EMAIL PROTECTED]> Date: Wed, 17 Aug 2005 22:59:01 +0200 > Shouldn't this be converted to a workqueue, which gets triggered by a > timer instead of blocking the timer softirq and therefor the delivery of > other timer functions that long ? We could, and I'd be happy to

Re: [RFC,PATCH] Use RCU to protect tasklist for unicast signals

On Wed, Aug 17, 2005 at 06:35:03PM +0400, Oleg Nesterov wrote: > Paul E. McKenney wrote: > > > > > The other thing that jumped out at me is that signals are very different > > > animals from a locking viewpoint depending on whether they are: > > > > > > 1.ignored, > > > > > > 2.

[PATCH] DVB: Clarify description text for dvb-bt8xx in Kconfig

Sorry for sending this twice... The first time I cc'd the wrong email address for LKML... Patrick Keene wrote to the linux-dvb list, asking where in menuconfig he can enable dvb-bt8xx for his AVerMedia DVB card. I pointed the following out to him: config DVB_BT8XX tristate

[patch 2.6.13-rc6] net/802/tr: use interrupt-safe locking

Change operations on rif_lock from spin_{un}lock_bh to spin_{un}lock_irq{save,restore} equivalents. Some of the rif_lock critical sections are called from interrupt context via tr_type_trans->tr_add_rif_info. The TR NIC drivers call tr_type_trans from their packet receive handlers.

Re: [PATCH 2.6.12.4] ACPI oops during ipmi_si driver init

On Wednesday 17 August 2005 2:30 pm, Corey Minyard wrote: > Basically, the IPMI system interface needs information from a specific > IPMI table to know how to configure itself. Those tables can reference > GPEs, so the driver can use those (though AFAIK it has never been tested). The

Re: [2.6.13-rc6-latest] SCSI disk registration msgs repeat themselves

On Tue, Aug 16, 2005 at 10:51:13PM -0700, Pete Zaitcev wrote: > On Tue, 16 Aug 2005 21:39:33 -0700, Patrick Mansfield <[EMAIL PROTECTED]> > wrote: > > On Tue, Aug 16, 2005 at 11:01:30PM -0400, Chuck Ebbert wrote: > > > > I just added some usb-storage devices to my system and got the below. >

[RFC] IPV4 long lasting timer function

Hi, while tracking down some timer related ugliness I stumbled over the timer driven function rt_secret_rebuild(), which does a loop over rt_has_mask (1024 in my case) entries and possibly some subsequent variable sized loops inside each step. On a 300MHZ PPC system this accumulated to a worst

[EMAIL PROTECTED]: [AIO] aio-2.6.13-rc6-B1]

Sorry if this comes through as a duplicate, but the mail client hung on my first attempt at sending this through - Forwarded message from Benjamin LaHaise <[EMAIL PROTECTED]> - Subject: [AIO] aio-2.6.13-rc6-B1 From: Benjamin LaHaise <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc:

RE: [PATCH] fix cciss DMA unmap brokenness

Alex wrote: > >The CCISS driver seems to loose track of DMA mappings > created by it's > fill_cmd() routine. Neither callers of this routine are > extracting the DMA address created in order to do the unmap. > Instead, they simply try to unmap 0x0. It's easy to see this > problem on an

Re: [patch] Real-Time Preemption, -RT-2.6.13-rc6-V0.7.53-11

> > > > > Interrupts are disabled during usb_hcd_giveback_urb because that's > > > > > how it was done originally and nobody has made an effort to remove > > > > > this assumption from the USB device drivers. > > > > Also Host Controller Drivers (HCDs). You do sort of have to > > remember who's

[PATCH] pull XFS support out of Kconfig submenu

It seems slightly odd to me that XFS support should be in a separate submenu, when all the other filesystems are not using submenus but are directly selectable from the Filesystems menu. This patch makes XFS Kconfig entries behave like everything else. Ignore if there's a good reason for the

[AIO] aio-2.6.13-rc6-B1

The bugfix followup to the last aio rollup is now available at: http://www.kvack.org/~bcrl/patches/aio-2.6.13-rc6-B1-all.diff with the split up in: http://www.kvack.org/~bcrl/patches/aio-2.6.13-rc6-B1/ This fixes the bugs noticed in the -B0 variant. Major changes in this

[PATCH] pull XFS support out of Kconfig submenu

It seems slightly odd to me that XFS support should be in a seperate submenu, when all the other filesystems are not using submenus but are directly selectable from the Filesystems menu. This patch makes XFS Kconfig entries behave like everything else. Ignore if there's a good reason for the

Re: [PATCH 2.6.12.4] ACPI oops during ipmi_si driver init

Peter Martuccelli wrote: On Mon, 2005-08-15 at 18:13, Bjorn Helgaas wrote: On Friday 12 August 2005 1:44 pm, Peter Martuccelli wrote: Stumbled into this problem working on the ipmi_si driver. When the ipmi_si driver initialization fails the acpi_tb_get_table call, after rsdt_info

[PATCH] fix dst_entry leak in icmp_push_reply()

If the ip_append_data() call in icmp_push_reply() fails, ip_flush_pending_frames() needs to be called. Otherwise, ip_rt_put() is never called on inet_sk(icmp_socket->sk)->cork.rt, which prevents the route (and net_device) from ever being freed. I've attached a patch which fixes the problem.

Re: [PATCH 5/5] 2.6.13-rc5-mm1, driver for IBM Automatic Server Restart watchdog

Andrey Panin <[EMAIL PROTECTED]> wrote: > > > This patch adds driver for IBM Automatic Server Restart watchdog hardware > found in some IBM eServer xSeries machines. This driver is based on the ugly > driver provided by IBM. Driver was tested on IBM eServer 226. > > ... > + > + case

Re: Undefined behaviour with get_cpu_vendor

Andi Kleen <[EMAIL PROTECTED]> wrote: > On Wed, Aug 17, 2005 at 11:54:23AM +0200, Christian Ehrhardt wrote: > > Your Patch at (URL wrapped) > > > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git; \ > > a=commit;h=99c6e60afff8a7bc6121aeb847dab27c556cf0c9 > >

[PATCH] small cleanup; remove check for NULL before kfree() in driver core

Remove needless checking of variable for NULL before calling kfree() on it. Applies to 2.6.13-rc6-git9 Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]> --- drivers/base/class.c |6 ++ 1 files changed, 2 insertions(+), 4 deletions(-) --- linux-2.6.13-rc6-git9-orig/drivers/base/class.c

Re: 2.6.13-rc6-rt8

2.6.13-rc6-rt8 fails to build with my configuration (attached): net/built-in.o: In function `ip_rt_init': : undefined reference to `__you_cannot_kmalloc_that_much' make[1]: *** [.tmp_vmlinux1] Error 1 make[1]: Leaving directory `/usr/src/linux-2.6.13-rc6' make: *** [stamp-build] Error 2 --

Re: Multiple virtual address mapping for the same code on IA-64 linux kernel.

On Wed, 17 Aug 2005, vamsi krishna wrote: > Seems like most of core size(VmSize) on ipf (126MB) is coming from the > code size(VmExe) i.e 97MB. While the code size is just 62MB on amd64. > > Looks like IA-64 wastes a lot of VM due to big instruction sizes, so > big instruction sizes will improve

Re: [UPDATE PATCH] push rounding up of relative request to schedule_timeout()

Nishanth Aravamudan wrote: ~ IMNSHO we should not get too parental with kernel only interfaces. Adding 1 is easy enough for the caller and even easier to explain in the instructions (i.e. this call sleeps for X jiffies edges). This allows the caller to do more if needed and, should he ever

Re: [RFC] Cleanup line-wrapping in pgtable.h

On Wed, Aug 17, 2005 at 06:56:01PM +0100, Christoph Hellwig wrote: > > +static inline int pte_user(pte_t pte) > > + { return (pte).pte_low & _PAGE_USER; } > > Once you start reformatting things please make sure the result version > matches the documented codingstyle. That would be: > > static

Re: 2.6.13-rc6-rt6

On Wed, 2005-08-17 at 21:27 +0200, Ingo Molnar wrote: > > Now that printk is in essence preemptible, there shouldnt be any > warnings from netconsole - if there are any then it should be possible > to fix them. > Then I guess write_msg in netconsole.c needs to remove all the

  1   2   3   4   5   >