On Fri, 19 Aug 2005 20:24:26 -0700, Andrew Morton wrote:
> Chuck Ebbert <[EMAIL PROTECTED]> wrote:
> >
> > +Controls overcommit of system memory:
>
> It should explain what "overcommit" is.
Here is an improved version.
Signed-off-by: Chuck Ebbert <[EMAIL PROTECTED]>
Documentation/filesystems
On Fri, 19 Aug 2005 at 20:02:27 -0700, Andrew Morton wrote:
> Chuck Ebbert <[EMAIL PROTECTED]> wrote:
> >
> > This patch enables tracking semaphore ownership.
>
> Why? I can't think of any bug in recent years which needed this..
It might be useful in new driver development. OTOH it is really
On Sat, 2005-08-20 at 11:06 +0400, Alexey Dobriyan wrote:
> On Sat, Aug 20, 2005 at 12:45:46AM -0600, Alejandro Bonilla Beeche wrote:
> > OK, now I would like to see a more official statement about this. Does
> > the linuxjournal.com pay $5000?
>
> Counting someone else money?
I'm not counting an
On Saturday 20 August 2005 16:31, Joel Becker wrote:
> On Fri, Aug 19, 2005 at 08:01:17PM -0700, Greg KH wrote:
> > The recent changes to sysfs should be ported to configfs to do this.
>
> Yeah, I've been meaning to do something, and resusing code is
> always a good plan.
Ending up with the
>
> Ok, with scripts/kernel-doc, I can produce some html files containing
> the functions' documentation.
>
> make pdfdocs or others targets don't work :|
You probarly need some additional packages.
But it's not easy to help you with no log of what happened.
Sam
-
To unsubscribe from t
This patch removes unnecessary critical section in ksize() function, as cli/sti
are rather expensive on modern CPUS.
Signed-off-by: Eric Dumazet <[EMAIL PROTECTED]>
diff -Nru linux-2.6.13-rc6-ed/mm/slab.c linux-2.6.13-rc6/mm/slab.c
--- linux-2.6.13-rc6-ed/mm/slab.c 2005-08-20 09:22:29.00
Hi!
> This patch expresses the same dependencies in a more simple way.
I have this currently in my tree:
depends on PM && SWAP && (X86 || ((FVR || PPC32) && !SMP))
(I really want to remove experimental), but it is not urgent enough to
push heavily.
On Sat, 2005-08-20 at 08:48 +0200, Emmanuel Fleury wrote:
> So, there is no project about this yet
No, not yet. The ALSA team has a contact at Creative, I guess the next
step is to ask them.
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
Thomas Gleixner wrote:
~
2. Drift of cyclic timers (armed by set_timer()):
Due to rounding errors and the drift adjustment code, the fixed
increment which is precalculated when the timer is set up and added on
rearm, I see creeping deviation from the timeline.
I have a patch lined up to base
Thomas Gleixner wrote:
George,
On Fri, 2005-08-19 at 17:19 -0700, George Anzinger wrote:
2. Drift of cyclic timers (armed by set_timer()):
Due to rounding errors and the drift adjustment code, the fixed
increment which is precalculated when the timer is set up and added on
rearm, I see creepi
Le Saturday 20 August 2005 a 09:08, Sam Ravnborg ecrivait:
> >
> > Ok, with scripts/kernel-doc, I can produce some html files containing
> > the functions' documentation.
> >
> > make pdfdocs or others targets don't work :|
>
> You probarly need some additional packages.
> But it's not easy to
> diff --git a/drivers/char/extint.c b/drivers/char/extint.c
> new file mode 100644
> --- /dev/null
> +++ b/drivers/char/extint.c
> @@ -0,0 +1,673 @@
> +/*
> + * This file is subject to the terms and conditions of the GNU General Public
> + * License. See the file "COPYING" in the main directory o
Please make sure this issue is reproducible without any binary only
drivers.
I uninstalled the NVIDIA drivers and tried again with the nv x.org driver.
Same problem. I also tried remaining in text mode (with no NVIDIA drivers
loaded). Same problem. In both cases it occurs when I start serio
> +config EXTINT_SGI_IOC4
> + tristate "Device driver for SGI IOC4 external interrupts"
> + depends on (IA64_GENERIC || IA64_SGI_SN2) && EXTINT && BLK_DEV_SGIIOC4
Is the ioc4 core abstraction config symbol really BLK_DEV_SGIIOC4?
That probably wants fixing in a separate patch.
> + T
Daniel Phillips <[EMAIL PROTECTED]> wrote:
> Biased. Fs is a mixed case acronym, nuff said.
But I'm still right:-)
David
-
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/majordo
On Fri, Aug 19, 2005 at 11:14:39PM -0400, Chuck Ebbert wrote:
> Someone complained about the docs for vm_overcommit_memory being wrong.
> This patch copies the text from the vm documentation into procfs.
> Please apply.
>...
Do we really need two copies of the same text?
Couldn't you instead wri
On Fri, Aug 19, 2005 at 03:07:09AM -0400, Jeff Garzik wrote:
> these two patches look OK to me, but didn't apply.
>
> Can you please resend, according to
>
> http://linux.yyz.us/patch-format.html
>
> ?
It seems the second of Jochen's patches does no longer apply (at least
against the la
Hi Linus,
On Fri, 19 Aug 2005, Linus Torvalds wrote:
> On Fri, 19 Aug 2005, Anton Altaparmakov wrote:
> > Yes, sure. I have applied your patch to our 2.6.11.4 tree (with the one
> > liner change I emailed you just now) and have kicked off a compile.
>
> Actually, hold on. The original patch had
Howard Chu writes:
> Nikita Danilov wrote:
[...]
>
> > What prevents transaction monitor from using, say, condition
> > variables to "yield cpu"? That would have an additional advantage of
> > blocking thread precisely until specific event occurs, instead of
> > blocking for some vague
On Fri, 2005-08-19 at 18:36 -0700, Andrew Morton wrote:
> Reuben Farrelly <[EMAIL PROTECTED]> wrote:
> >
> > ...
> > >> 4. PAM is complaining about "PAM audit_open() failed: Protocol not suppor
> > >> ted" and I can't log in as any user including root. I would have picked
> > >> this
> > >> was
Howard Chu <[EMAIL PROTECTED]> writes:
> In this specific example, we use whatever
> BerkeleyDB provides and we're certainly not about to write our own
> transactional embedded database engine just for this.
BerkeleyDB is free software after all that comes with source code.
Surely it can be fixe
Thomas Gleixner wrote:
>
> send_sigqueue is called from posix_timer_fn() and acquires
> tasklist_lock, which makes no sense to me.
>
> send_sigqueue()s (l)onl(e)y user is the posix_timer function
> (posix_timer_fn(), calling posix_timer_event()).
>
> Each posix timer blocks the task from vanishing
For my own purpose I would like to slow down the clock maintained by
the Linux kernel.
I want to simulate 10Gb/s network connection with roughly 1 TCP
connections. For this I want to use two (perhaps dual processor if
need be) PC computers connected with 1Gb/s Ethernet. To achieve this
goal
Hello !
After having accumulated a few weeks delay, the fourth hotfix for kernel
2.4.31 is finally out. It was also the right time to release it now that
the isofs and zlib stories came to an end.
Because of the ZISOFS security fix, users of older -hf or plain 2.4.X
should upgrade either to lates
Thomas Gleixner wrote:
On Fri, 2005-08-19 at 15:13 -0700, Darren Hart wrote:
I was trying to use another HRT clock source and couldn't get menuconfig
to let me select acpi-pm-timer, turns out it has been disabled in
arch/i386/Kconfig, but the description is still in the help...
# config HIG
--Andrew Morton <[EMAIL PROTECTED]> wrote (on Friday, August 19, 2005 04:33:31
-0700):
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc6/2.6.13-rc6-mm1/
>
> - Lots of fixes, updates and cleanups all over the place.
>
> - If you have the right debugging options set, t
I've already sent this to the maintainers, and this is now being sent to a
larger community audience. I have fixed a problem with the ia64 version of
build_sched_domains(), but a similar fix still needs to be made to the
generic build_sched_domains() in kernel/sched.c.
The "dynamic sched domains"
Hi Jeff,
Jeff Garzik <[EMAIL PROTECTED]> writes:
> Here is a list of problems with the patch. I'll paste this into the
> bug as well:
[Lot of interesting issues]
> 8) The DMA pad code is very buggy. It uses the dma_map_single() to
> map a buffer, but never synchronizes nor flushes the buffer.
In i6300esb.c watchdog card driver were 2 bugs (misused pc_match_device
and pci_dev_put wasn't called in one error case) and one little cleanup
was done (long line was converted to a shorter one with using built-in
macro).
Generated in 2.6.13-rc6-mm1 kernel version.
Signed-off-by: Jiri Slaby <[EM
On Sat, 2005-08-20 at 18:10 +0400, Oleg Nesterov wrote:
> posix_timer_event() first checks that the thread (SIGEV_THREAD_ID
> case) does not have PF_EXITING flag, then it calls send_sigqueue()
> which locks task list. But if the thread exits in between the kernel
> will oops.
> posix_timer_event(
On Sat, Aug 20, 2005 at 01:44:43AM +0200, Adrian Bunk wrote:
> "extern inline" doesn't make sense.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Thanks Adrian - I've committed it to my tree.
--
Russell King
Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.
Linus et Al,
Access mode of 3 is undocumented but it does do something halfway sane
on all linuxes (checked back to 2.0.X).
The open requires both read and write permission to succeed, but the
resulting file descriptor can neither be read nor written.
The responsible code in filp_open() is this:
[PATCH] fix send_sigqueue() vs thread exit race
posix_timer_event() first checks that the thread (SIGEV_THREAD_ID
case) does not have PF_EXITING flag, then it calls send_sigqueue()
which locks task list. But if the thread exits in between the kernel
will oops (->sighand == NULL after __exit_sighan
On Sat, 20 Aug 2005, Miklos Szeredi wrote:
>
> My question is: is this deliberate or accidental? Wouldn't it be more
> logical to not require any permission to open such file? Or is there
> some security concern with that?
It's deliberate but historical. It's been a long time since I worked o
On Fri, Aug 19, 2005 at 04:33:31AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.13-rc5-mm1:
>...
> git-ocfs2.patch
>...
> Subsystem trees
>...
gcc correctly tells that at least a part of this patch incorrect (not
that gcc says "is used", not "might be used"):
<-- snip -->
...
CC
On Sat, Aug 20, 2005 at 11:19:41AM +0200, Stephane Wirtel wrote:
> Le Saturday 20 August 2005 a 09:08, Sam Ravnborg ecrivait:
> > >
> > > Ok, with scripts/kernel-doc, I can produce some html files containing
> > > the functions' documentation.
> > >
> > > make pdfdocs or others targets don't wo
Thomas Gleixner wrote:
>
> On Sat, 2005-08-20 at 18:10 +0400, Oleg Nesterov wrote:
>
> > posix_timer_event() first checks that the thread (SIGEV_THREAD_ID
> > case) does not have PF_EXITING flag, then it calls send_sigqueue()
> > which locks task list. But if the thread exits in between the kerne
Hmm, some of this resembles my prototype from last month:
http://lists.lm-sensors.org/pipermail/lm-sensors/2005-July/013012.html
Both ended up with new driver probe() methods attaching to *devices* not
to busses, and used the probe signature the i2c core already handles.
That helps eliminate o
On Sat, 2005-08-20 at 10:30 -0700, Linus Torvalds wrote:
>
> On Sat, 20 Aug 2005, Miklos Szeredi wrote:
> >
> > My question is: is this deliberate or accidental? Wouldn't it be more
> > logical to not require any permission to open such file? Or is there
> > some security concern with that?
>
Hi,
I now use a notebook that uses RTL8139, and I encounter exactly the same
problems as this:
http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/1289.html
I know use Fedora Core 4 on this box.
With a Linux FC4 kernel (not customized yet).
As well as I still encounter the problem, I guess the
Nick Piggin wrote:
Robert Hancock wrote:
> I fail to see how sched_yield is going to be very helpful in this
> situation. Since that call can sleep from a range of time ranging
> from zero to a long time, it's going to give unpredictable results.
Well, not sleep technically, but yield the CP
I'm currently running 2.6.13-rc6+git as of today and whan I tell my
computer to reboot, it starts a reboot as sual and when it reached
kernel telling "Rebooting" the computer halts instead. I noticed it just
with an earlier post-rc6 snapshot and it's still there with current git.
PC, Duron 1.3
On Sat, 2005-08-20 at 10:31 +1000, Con Kolivas wrote:
> It's an X problem and it's being fixed. Get over it, we're not tuning
> the scheduler for a broken app.
>
You're right, this problem seems much, much better in Xorg 6.8.2. I
think the Damage extension might be responsible. There's definite
On Sat, 2005-08-20 at 03:07 -0400, Chuck Ebbert wrote:
> On Fri, 19 Aug 2005 at 20:02:27 -0700, Andrew Morton wrote:
>
> > Chuck Ebbert <[EMAIL PROTECTED]> wrote:
> > >
> > > This patch enables tracking semaphore ownership.
> >
> > Why? I can't think of any bug in recent years which needed this
On Sat, Aug 20, 2005 at 09:55:32AM +0400, Alexey Dobriyan wrote:
> On Sat, Aug 20, 2005 at 05:58:53AM +0200, Adrian Bunk wrote:
> > --- linux-2.6.13-rc6-mm1-full/scripts/ver_linux.old
> > +++ linux-2.6.13-rc6-mm1-full/scripts/ver_linux
>
> > -fdformat --version | awk -F\- '{print "util-linux
This patch fixes the following compile error with CONFIG_PROC_FS=n:
<-- snip -->
...
CC sound/core/memalloc.o
sound/core/memalloc.c: In function 'snd_mem_exit':
sound/core/memalloc.c:658: error: 'snd_mem_proc' undeclared (first use in this
function)
sound/core/memalloc.c:658: error: (Ea
I am using a LSIU160/Symbios 53c1010 Ultra3 scsi adapter and it works at
full speed (75 MB/sec) with kernel-2.6.12. And dmesg shows:
kernel: target0:0:0: Beginning Domain Validation
kernel: target0:0:0: asynchronous.
kernel: WIDTH IS 1
kernel: target0:0:0: wide asynchronous.
kernel: target0:
This patch contains the following possible cleanups:
- pci/cy82c693.c: make a needlessly global function static
- remove the following unneeded EXPORT_SYMBOL's:
- ide-taskfile.c: do_rw_taskfile
- ide-iops.c: default_hwif_iops
- ide-iops.c: default_hwif_transport
- ide-iops.c: wait_for_ready
On Fri, Aug 19, 2005 at 04:33:31AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.13-rc5-mm1:
>...
> git-net.patch
>...
> Subsystem trees
>...
This breaks the compilation with CONFIG_PROC_FS=n:
<-- snip -->
...
CC net/core/sysctl_net_core.o
net/core/sysctl_net_core.c:50: error:
"extern inline" doesn't make sense.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
include/linux/quotaops.h | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
--- linux-2.6.13-rc6-mm1/include/linux/quotaops.h.old 2005-08-20
14:40:53.0 +0200
+++ linux-2.6.13-r
On Fri, 2005-08-19 at 11:43 -0700, Paul E. McKenney wrote:
> On Fri, Aug 19, 2005 at 08:30:05PM +0200, Peter Zijlstra wrote:
> > On Fri, 2005-08-19 at 18:56 +0200, Peter Zijlstra wrote:
> > > Hi Ingo, Paul, others,
> > >
> > > I'm trying to run a user-mode-linux guest under the RT kernel however
>
C files should include the files with the prototypes for their global
functions.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.13-rc6-mm1/drivers/scsi/constants.c.old 2005-08-20
14:42:12.0 +0200
+++ linux-2.6.13-rc6-mm1/drivers/scsi/constants.c 2005-08-20
14:43:
This change could (at least in theory) allow a compiler better
optimization (especially in the n=1 case).
The practical effect seems to be nearly zero:
text data bss dechex filename
256172075850138 1827016 332943611fc0819 vmlinux-old
25617191
This patch makes two needlessly global functions static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.13-rc6-mm1/mm/filemap.c.old 2005-08-20 14:37:27.0
+0200
+++ linux-2.6.13-rc6-mm1/mm/filemap.c 2005-08-20 14:46:24.0 +0200
@@ -2034,7 +2034,7 @@
}
EXPOR
Nikita Danilov wrote:
That returns us to the core of the problem: sched_yield() is used to
implement a synchronization primitive and non-portable assumptions are
made about its behavior: SUS defines that after sched_yield() thread
ceases to run on the CPU "until it again becomes the head of its t
fs/befs/linuxvfs.c:466: error: conflicting types for 'befs_follow_link'
fs/befs/linuxvfs.c:44: error: previous declaration of 'befs_follow_link' was
here
fs/befs/linuxvfs.c: In function 'befs_follow_link':
fs/befs/linuxvfs.c:490: warning: return makes integer from pointer without a
cast
Signed-o
On Sat, Aug 20, 2005 at 03:48:40PM -0400, Dave Jones wrote:
> fs/befs/linuxvfs.c:466: error: conflicting types for 'befs_follow_link'
> fs/befs/linuxvfs.c:44: error: previous declaration of 'befs_follow_link' was
> here
> fs/befs/linuxvfs.c: In function 'befs_follow_link':
> fs/befs/linuxvfs.c:490
On Saturday 20 August 2005 20:45, David Howells wrote:
> Daniel Phillips <[EMAIL PROTECTED]> wrote:
> > Biased. Fs is a mixed case acronym, nuff said.
>
> But I'm still right:-)
Of course you are! We're only impugning your taste, not your logic ;-)
OK, the questions re your global consistency m
On Sat, Aug 20, 2005 at 08:58:07PM +0100, Al Viro wrote:
> On Sat, Aug 20, 2005 at 03:48:40PM -0400, Dave Jones wrote:
> > fs/befs/linuxvfs.c:466: error: conflicting types for 'befs_follow_link'
> > fs/befs/linuxvfs.c:44: error: previous declaration of 'befs_follow_link'
> > was here
> > fs/b
Rakotomandimby Mihamina wrote:
> Hi,
>
> I now use a notebook that uses RTL8139, and I encounter exactly the same
> problems as this:
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/1289.html
>
> I know use Fedora Core 4 on this box.
> With a Linux FC4 kernel (not customized yet).
>
>
On Sat, 2005-08-20 at 11:38 -0700, Howard Chu wrote:
> But I also found that I needed to add a new
> yield(), to work around yet another unexpected issue on this system -
> we have a number of threads waiting on a condition variable, and the
> thread holding the mutex signals the var, unlocks the
On Saturday 20 August 2005 13:01, Greg KH wrote:
> On Sat, Aug 20, 2005 at 10:50:51AM +1000, Daniel Phillips wrote:
> > Permissions set on ConfigFS attributes (aka files) do not stick.
>
> The recent changes to sysfs should be ported to configfs to do this.
No, it should go the other way, my fix i
Lee Revell wrote:
On Sat, 2005-08-20 at 11:38 -0700, Howard Chu wrote:
> But I also found that I needed to add a new yield(), to work around
> yet another unexpected issue on this system - we have a number of
> threads waiting on a condition variable, and the thread holding the
> mutex signals t
On Fri, Aug 19, 2005 at 09:22:09AM -0700, Peter Buckingham wrote:
> >The machine is working quite a bit better with pci=noacpi in leu of
> >disabling ACPI in the BIOS, but there are still those nasty errors in
> >reference to the ACPI tables being broken:
> >ACPI-0362: *** Error: Looking up [\
On 8/20/05, Alejandro Bonilla Beeche <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-08-19 at 22:13 -0700, alan wrote:
> > On Sat, 20 Aug 2005, Kernel Hacker wrote:
> >
> > > Friend,
> > > What fact is behind this article
> > > http://www.theinquirer.net/?article=25529.
> >
> > The article is also wrong.
On Sat, 2005-08-20 at 11:38 -0700, Howard Chu wrote:
> Nick Piggin wrote:
> > Robert Hancock wrote:
> > > I fail to see how sched_yield is going to be very helpful in this
> > > situation. Since that call can sleep from a range of time ranging
> > > from zero to a long time, it's going to give unp
On Thu, Aug 18, 2005 at 07:52:23PM +0900, Hiroyuki Machida wrote:
> Christoph Hellwig wrote:
> >On Wed, Aug 17, 2005 at 04:07:03AM +0900, Machida, Hiroyuki wrote:
> >>This is a take 2 of posix file attribute support on VFAT.
> >
> >
> >Sorry, but this is far too scary. Please just use one of the
On Sat, 2005-08-20 at 21:53 +0100, Nick Warne wrote:
> Here is the 'final' post after Mr Hirofumi
> found the cause of my issues:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/1709.html
I have a problem with it:
It's about patching, reverting, patching, reverting,...
I got lost. That's w
Howard Chu writes:
> Nikita Danilov wrote:
> > That returns us to the core of the problem: sched_yield() is used to
> > implement a synchronization primitive and non-portable assumptions are
> > made about its behavior: SUS defines that after sched_yield() thread
> > ceases to run on the CPU "
On Saturday 20 August 2005 21:53, you wrote:
> I have a problem with it:
> It's about patching, reverting, patching, reverting,...
> I got lost. That's why I asked for a... "straighter" one :-)
>> But I looked at what he said and found the real problem on my system (after
>> all that):
>> http://
On Sat, Aug 20, 2005 at 09:27:25PM +0200, Peter Zijlstra wrote:
> Jeff, could you help us out here?
> What exactly does uml need to get out of the calibrate delay loop?
Interrupts, it's not too demanding :-)
If it's not seeing VTALRM, then it will never leave the calibration loop.
Try stracing i
gcc kindly pointed me at jffs_create() with this warning :
fs/jffs/inode-v23.c:1279: warning: `inode' might be used uninitialized
in this function
And looking at the function :
static int
jffs_create(struct inode *dir, struct dentry *dentry, int mode,
struct nameidata *nd)
{
This patch adds the Dell Systems Management Base Driver with sysfs support.
This patch incorporates changes based on comments from the previous posting.
Summary of changes:
* Changed permissions on sysfs files so that only owner can read.
* Changed to use __uNN/__sNN types in structs.
* smi_data
Interestingly (we for me at least ;-) I have been
working on an SPI subsystem that was/is a copy of the
I2C subsystem with changes as SPI doesnt have a
protocol like I2C. I am at the stage of tidying up the
structures in the head files and looking at where they
are used in the core layer.
To me, w
Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-08-19 at 00:10 -0700, Andrew Morton wrote:
> > Rusty Russell <[EMAIL PROTECTED]> wrote:
> > > I believe we just ignored sparc64. That usually works for solving these
> > > kind of bugs. 8)
> >
> > heh. iirc, it was demonstrable on x86 also.
From: Adrian Bunk <[EMAIL PROTECTED]>
Date: Sat, 20 Aug 2005 21:03:09 +0200
> This breaks the compilation with CONFIG_PROC_FS=n:
..
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Applied, thanks Adrian.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Nick Warne <[EMAIL PROTECTED]> writes:
> On Saturday 20 August 2005 21:53, you wrote:
>> I have a problem with it:
>> It's about patching, reverting, patching, reverting,...
>> I got lost. That's why I asked for a... "straighter" one :-)
>
>>> But I looked at what he said and found the real proble
Howard Chu wrote:
Lee Revell wrote:
On Sat, 2005-08-20 at 11:38 -0700, Howard Chu wrote:
> But I also found that I needed to add a new yield(), to work around
> yet another unexpected issue on this system - we have a number of
> threads waiting on a condition variable, and the thread holding t
Here's a re-send of a small patch I sent on Aug. 9.
The patch removes a redundant variable `sig' from sys_prctl().
For some reason, when sys_prctl is called with option == PR_SET_PDEATHSIG
then the value of arg2 is assigned to an int variable named sig. Then sig
is tested with valid_signal() and
Gaah. I don't tend to bother about slashdot, because quite frankly, the
whole _point_ of slashdot is to have this big public wanking session with
people getting together and making their own "insightful" comment on any
random topic, whether they know anything about it or not.
[ And don't get m
Wieland Gmeiner <[EMAIL PROTECTED]> wrote:
>
> +asmlinkage long sys_getprlimit(pid_t pid, unsigned int resource, struct
> rlimit __user *rlim)
> +{
> +struct rlimit value;
> +task_t *p;
> +int retval = -EINVAL;
> +
> +if (resource >= RLIM_NLIMITS)
> +
Howard Chu wrote:
I'll note that we removed a number of the yield calls (that were in
OpenLDAP 2.2) for the 2.3 release, because I found that they were
redundant and causing unnecessary delays. My own test system is running
on a Linux 2.6.12.3 kernel (installed over a SuSE 9.2 x86_64 distro),
Hi,
here are kernbench results:
cpusched=ingosched
./kernbench -M -o 128
[..]
Average Optimal -j 128 Load Run:
Elapsed Time 365,4
User Time 620,8
System Time 64,6
Percent CPU 187,2
Context Switches 38296,8
Sleeps 37867
(reboot)
---
Hi USB developers, hi Andrew!
On Mon, 21 Mär 2005, preining wrote:
> Dear usb developers, dear Andrew!
>
> I found that my builtin sd card reader connected via USB port
> experiences several connect/reconnect cycles every time I boot.
>
> I am using 2.6.11-mm4.
Same now with 2.6.13-rc6-mm1. Thi
[1.] One line summary of the problem:
oops when shuting down system
[2.] Full description of the problem/report:
After kernbenching nicksched (heav load make -j128) I just record
results on cd and shutdown system.
[3.] Keywords (i.e., modules, networking, kernel):
plugsched, nicksched, sysfs, vfs
On Sun, 21 Aug 2005 11:34, Michal Piotrowski wrote:
> Hi,
Hi
> here are kernbench results:
Nice to see you using kernbench :)
> ./kernbench -M -o 128
> [..]
> Average Optimal -j 128 Load Run:
Was there any reason you chose 128? Optimal usually works out automatically
from kernbench to 4x numb
On Sun, 21 Aug 2005, Norbert Preining wrote:
> Hi USB developers, hi Andrew!
>
> On Mon, 21 Mär 2005, preining wrote:
> > Dear usb developers, dear Andrew!
> >
> > I found that my builtin sd card reader connected via USB port
> > experiences several connect/reconnect cycles every time I boot.
>
On Sat, Aug 20, 2005 at 05:33:27PM -0700, [EMAIL PROTECTED] wrote:
> Another annoying problem is that once the system reaches this 2GB
> limit, then every process which exits will receive a signal,
> SIGXFSZ. This signal is generated because an attempt was made to
> write beyond the limit for the
On Sam, 20 Aug 2005, Alan Stern wrote:
> Speaking in broad terms, it's normal to see new device connection and
> configuration messages like the ones above when a USB device is plugged in
> to your computer. What's not normal is to see disconnects. So you should
Mind that this is an *internal* b
Hi,
On 8/21/05, Con Kolivas <[EMAIL PROTECTED]> wrote:
> On Sun, 21 Aug 2005 11:34, Michal Piotrowski wrote:
> > Hi,
>
> Hi
>
> > here are kernbench results:
>
> Nice to see you using kernbench :)
>
> > ./kernbench -M -o 128
> > [..]
> > Average Optimal -j 128 Load Run:
>
> Was there any reas
On Sun, 21 Aug 2005 14:16, Michal Piotrowski wrote:
> Hi,
>
> On 8/21/05, Con Kolivas <[EMAIL PROTECTED]> wrote:
> > On Sun, 21 Aug 2005 11:34, Michal Piotrowski wrote:
> > > Hi,
> >
> > Hi
> >
> > > here are kernbench results:
> >
> > Nice to see you using kernbench :)
> >
> > > ./kernbench -M -o
{standard input}: Assembler messages:
{standard input}:397: Error: symbol `.Litfits' is already defined
{standard input}:585: Error: symbol `.Litfits' is already defined
Newer gcc's inline this it seems, which blows up.
--- linux-2.6.12/arch/s390/kernel/cpcmd.c~ 2005-08-18 15:12:51.0
Hi folks,
At boot time my Logitech mouse is detected as
I: Bus=0011 Vendor=0002 Product=0001 Version=
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=event1 ts0 mouse0
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3
After manually reloading psmouse I get the expected
I: Bus=001
On 8/21/05, Con Kolivas <[EMAIL PROTECTED]> wrote:
> Well it will survive all right, but eventually get into swap thrash territory
> and that's not a meaningful cpu scheduler benchmark.
>
> Cheers,
> Con
>
Ok. How about make -j? It's one of kernbench test runs, on my box load
average > 1500 ;).
On Sun, 21 Aug 2005 14:44, Michal Piotrowski wrote:
> On 8/21/05, Con Kolivas <[EMAIL PROTECTED]> wrote:
> > Well it will survive all right, but eventually get into swap thrash
> > territory and that's not a meaningful cpu scheduler benchmark.
> >
> > Cheers,
> > Con
>
> Ok. How about make -j? It's
On Sun, Aug 21, 2005 at 12:38:39AM -0400, Dave Jones wrote:
> {standard input}: Assembler messages:
> {standard input}:397: Error: symbol `.Litfits' is already defined
> {standard input}:585: Error: symbol `.Litfits' is already defined
>
> Newer gcc's inline this it seems, which blows up.
Eeek...
Harald Dunkel wrote:
At boot time my Logitech mouse is detected as
I: Bus=0011 Vendor=0002 Product=0001 Version=
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=event1 ts0 mouse0
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3
After manually reloading psmouse I get the expecte
On Saturday 20 August 2005 23:42, Harald Dunkel wrote:
> Hi folks,
>
> At boot time my Logitech mouse is detected as
>
> I: Bus=0011 Vendor=0002 Product=0001 Version=
> N: Name="PS/2 Generic Mouse"
> P: Phys=isa0060/serio1/input0
> H: Handlers=event1 ts0 mouse0
> B: EV=7
> B: KEY=7 0 0 0
On Sun, Aug 21, 2005 at 06:42:23AM +0200, Harald Dunkel wrote:
> Hi folks,
>
> At boot time my Logitech mouse is detected as
>
> I: Bus=0011 Vendor=0002 Product=0001 Version=
> N: Name="PS/2 Generic Mouse"
> P: Phys=isa0060/serio1/input0
> H: Handlers=event1 ts0 mouse0
> B: EV=7
> B: KEY=7
On Sun, Aug 21, 2005 at 06:11:31AM +0100, Al Viro wrote:
> On Sun, Aug 21, 2005 at 12:38:39AM -0400, Dave Jones wrote:
> > {standard input}: Assembler messages:
> > {standard input}:397: Error: symbol `.Litfits' is already defined
> > {standard input}:585: Error: symbol `.Litfits' is already de
1 - 100 of 104 matches
Mail list logo
