PROBLEM: Opaque kernel bug in work with bzip2(?)

2005-07-23 Thread Игорь Богомазов
The letter itself is in an attached file. Intended for: linux-kernel@vger.kernel.org Hello dear Linux Developer (sorry, I do not know precisely whom I'm writing to), PROBLEM: Opaque kernel bug in work with bzip2(?) It occures every time I try to bunzip2 (1.0.2) the linux-2.6.11.10.tar.bz2 tarbal

PROBLEM: Opaque kernel bug in work with bzip2(?)

2005-07-23 Thread Игорь Богомазов
The letter itself is in an attached file. Intended for: linux-kernel@vger.kernel.org Hello dear Linux Developer (sorry, I do not know precisely whom I'm writing to), PROBLEM: Opaque kernel bug in work with bzip2(?) It occures every time I try to bunzip2 (1.0.2) the linux-2.6.11.10.tar.bz2 tarbal

Re: [patch 2.6.13-rc3a] i386: inline restore_fpu

2005-07-23 Thread Chuck Ebbert
On Date: Fri, 22 Jul 2005 at 16:19:25 -0700 (PDT), Linus Torvalds wrote: > /* >* The "nop" is needed to make the instructions the same >* length. >*/ > #define restore_fpu(tsk)\ > alternative_input( \ >

Re: [patch 2.6.13-rc3a] i386: inline restore_fpu

2005-07-23 Thread Chuck Ebbert
On Fri, 22 Jul 2005 at 13:27:56 +1000, Andrew Morton wrote: > Chuck Ebbert <[EMAIL PROTECTED]> wrote: > > After: > > > > 12534 math_state_restore 130.5625 > > 8354 device_not_available 203.7561 > > - > > 20888 > > Next step should be to physica

Re: fix suspend/resume irq request free for yenta..

2005-07-23 Thread Russell King
On Sat, Jul 23, 2005 at 02:29:24AM +0200, Pavel Machek wrote: > > Is it necessary to do free_irq for suspend? Shouldn't disable_irq > > be enough? > > Due to recent changes in ACPI, yes, it is neccessary. What if some other driver is sharing the IRQ, and requires IRQs to be enabled for the resume

We are looking for active communicative people in Canada, UK, DE, US

2005-07-23 Thread Homestretch T. Cervixes
Our company deals with the software development, creation of human-engineered interface web-sites and modern design. We work with the clients from Canada, United Kingdom, Deutschland and the USA. Our Head Office is located in Lithuania. Our employees are all around the world and they work with

Re: [PATCH] turn many #if $undefined_string into #ifdef $undefined_string

2005-07-23 Thread Chuck Ebbert
On Fri, 22 Jul 2005 at 16:48:05 +0200, Olaf Hering wrote: > turn many #if $undefined_string into #ifdef $undefined_string > to fix some warnings after -Wno-def was added to global CFLAGS Shouldn't that be "#if defined($undefined_string)"? #ifdef is obsolete... __ Chuck - To unsubscribe from

Re: [PATCH] turn many #if $undefined_string into #ifdef $undefined_string

2005-07-23 Thread Coywolf Qi Hunt
On 7/23/05, Chuck Ebbert <[EMAIL PROTECTED]> wrote: > On Fri, 22 Jul 2005 at 16:48:05 +0200, Olaf Hering wrote: > > > turn many #if $undefined_string into #ifdef $undefined_string > > to fix some warnings after -Wno-def was added to global CFLAGS > > > Shouldn't that be "#if defined($undefined_

Re: Giving developers clue how many testers verified certain kernel version

2005-07-23 Thread Con Kolivas
On Sat, 23 Jul 2005 01:34 pm, Lee Revell wrote: > On Fri, 2005-07-22 at 20:31 -0700, Linus Torvalds wrote: > > On Fri, 22 Jul 2005, Lee Revell wrote: > > > Con's interactivity benchmark looks quite promising for finding > > > scheduler related interactivity regressions. > > > > I doubt that _any_ o

Re: [PATCH] 1 Wire drivers illegally overload NETLINK_NFLOG

2005-07-23 Thread Evgeniy Polyakov
On Sat, Jul 23, 2005 at 08:54:27AM -0400, Harald Welte ([EMAIL PROTECTED]) wrote: > Hi Dave, > Hi Evgeniy, > > the following patch fixes the illegal use of NETLINK_NFLOG by the > 1wire drivers. It assumes that the netlink tap families can now safely > be reclaimed, which is the case according to

Re: Giving developers clue how many testers verified certain kernel version

2005-07-23 Thread Jesper Krogh
I gmane.linux.kernel, skrev Blaisorblade: > Forgot drivers testing? That is where most of the bugs are hidden, and where > wide user testing is definitely needed because of the various hardware bugs > and different configurations existing in real world. A way that could raise the testing upon

PATCH 2.6: tms380tr update: move to DMA API

2005-07-23 Thread Jochen Friedrich
Hi Jeff, this patch makes tms380tr use the new DMA API. Now that on Alpha, this API also supports bus master DMA for ISA (platform) devices, i changed the driver to use this new API. This also works around a bug in the firmware loader: The example provided in Documentation/firmware_class no longe

Re: Supermount

2005-07-23 Thread Oliver Neukum
Am Freitag, 22. Juli 2005 18:38 schrieb Lasse Kärkkäinen / Tronic: > > Supermount is obsolete there are other tools in userspace that do the > > job perfectly. > > e.g ivman which uses hal and dbus. > > They cannot mount on demand, thus cannot do the same job. The boot > partition, for example, is

Re: Kernel cached memory

2005-07-23 Thread Oliver Neukum
Am Freitag, 22. Juli 2005 19:58 schrieb Lee Revell: > On Fri, 2005-07-22 at 15:25 +0200, Gábor Lénárt wrote: > > Anyway, want to have 'free memory' is a thing like having dozens of cars > > in your garage which don't want to be used ... > > > > Really? I thought it was good to leave some memory

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Fri, 22 Jul 2005, Arjan van de Ven wrote: > Also I'd rather not add the non-msec ones... either you're raw and use > HZ, or you are "cooked" and use the msec variant.. I dont' see the point > of adding an "in the middle" one. (Yes this means that several users > need to be transformed to m

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Arjan van de Ven
On Sat, 2005-07-23 at 12:50 +0200, Roman Zippel wrote: > Hi, > > On Fri, 22 Jul 2005, Arjan van de Ven wrote: > > > Also I'd rather not add the non-msec ones... either you're raw and use > > HZ, or you are "cooked" and use the msec variant.. I dont' see the point > > of adding an "in the middle"

[PATCH] 2.6.13rc3: RLIMIT_RTPRIO broken

2005-07-23 Thread Andreas Steinmetz
RLIMIT_RTPRIO is supposed to grant non privileged users the right to use SCHED_FIFO/SCHED_RR scheduling policies with priorites bounded by the RLIMIT_RTPRIO value via sched_setscheduler(). This is usually used by audio users. Unfortunately this is broken in 2.6.13rc3 as you can see in the excerpt

Re: HPT370 errors under 2.6.13-rc3-mm1

2005-07-23 Thread mdew
looks like 2.6.12 does the same sort of thing.. On 7/23/05, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote: > Hi, > > Does vanilla kernel 2.6.12 work for you? > It doesn't contain hpt366 driver update. > > Bartlomiej > > On 7/22/05, mdew <[EMAIL PROTECTED]> wrote: > > I'm unable to mount

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > What's wrong with using jiffies? > > A lot of the (driver) users want a wallclock based timeout. For that, > miliseconds is a more obvious API with less chance to get the jiffies/HZ > conversion wrong by the driver writer. We have helper fun

Re: HPT370 errors under 2.6.13-rc3-mm1

2005-07-23 Thread Jurriaan on adsl-gate
On Sat, Jul 23, 2005 at 11:50:43PM +1200, mdew wrote: > looks like 2.6.12 does the same sort of thing.. > As a data-point, my dual HPT374 controllers are fine with 2.6.13-rc3-mm1. One onboard, one in a pci-slot in an Epox 4PCA3+ (socket 478, i875 chipset) motherboard. Linux adsl-gate 2.6.13-rc3-m

Re: Kernel cached memory

2005-07-23 Thread Denis Vlasenko
On Saturday 23 July 2005 00:43, John Pearson wrote: > Wouldn't having (practically) all your memory used for cache slow down > starting a new program? First it would have to free up that space, and then > put stuff in that space, taking potentially twice as long. I think there > should be a system

[2.6.12.3] dyntick 050610-1 breaks makes S3 suspend

2005-07-23 Thread Jan De Luyck
Hello, I recently tried out dyntick 050610-1 against 2.6.12.3, works great, it actually makes a noticeable difference on my laptop's battery life. I don't have hard numbers, lets just say that instead of the usual ~3 hours i get out of it, i was ~4 before it started nagging, usual use pattern a

Re: [2.6.12.3] dyntick 050610-1 breaks makes S3 suspend

2005-07-23 Thread Christian Hesse
On Saturday 23 July 2005 14:35, Jan De Luyck wrote: > Hello, > > I recently tried out dyntick 050610-1 against 2.6.12.3, works great, it > actually makes a noticeable difference on my laptop's battery life. I don't > have hard numbers, lets just say that instead of the usual ~3 hours i get > out of

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Arjan van de Ven
On Sat, 2005-07-23 at 13:55 +0200, Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > > What's wrong with using jiffies? > > > > A lot of the (driver) users want a wallclock based timeout. For that, > > miliseconds is a more obvious API with less chance to get the

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > > What's wrong with using jiffies? > > > > > > A lot of the (driver) users want a wallclock based timeout. For that, > > > miliseconds is a more obvious API with less chance to get the jiffies/HZ > > > conversion wrong by the driver writer.

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Arjan van de Ven
On Sat, 2005-07-23 at 15:04 +0200, Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > > > > What's wrong with using jiffies? > > > > > > > > A lot of the (driver) users want a wallclock based timeout. For that, > > > > miliseconds is a more obvious API with less ch

Re: [patch 2/2] Touchscreen support for sharp sl-5500

2005-07-23 Thread Pavel Machek
This adds support for touchscreen on Sharp Zaurus sl-5500. Please apply, Pavel Signed-off-by: Pavel Machek <[EMAIL PROTECTED]> diff --git a/drivers/input/touchscreen/Kconfig b/drivers/input/touchscreen/Kconfig --- a/drivers/input/touchscre

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Arjan van de Ven wrote: > jiffies/HZ is the more powerful API. The msec one which also sets > current to (un)interruptible is the simplified wrapper on top. So why do you want to hide it? Make the jiffies based API the primary one and add some convenience functions, whe

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Arjan van de Ven
On Sat, 2005-07-23 at 15:29 +0200, Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > jiffies/HZ is the more powerful API. The msec one which also sets > > current to (un)interruptible is the simplified wrapper on top. > > So why do you want to hide it? I don't wa

Re: [patch 2/2] Touchscreen support for sharp sl-5500

2005-07-23 Thread Pavel Machek
Hi! > > This adds support for touchscreen on Sharp Zaurus sl-5500. Vojtech, > > please apply, > > I have couple more commnets... Sorry, I never really worked with kthreads. Applied all those, > > +static int ucb1x00_ts_open(struct input_dev *idev) > > +{ > > + struct ucb1x00_ts *ts = (struct

Re: kernel optimization

2005-07-23 Thread Simon Strandman
christos gentsis skrev: so if i want to play with and see what happens i have to change it manually in each make file... good i may create a kernel like that to see what will happens (just for test) ;) thanks Chris Just edit the top level Makefile and add your custom CFLAGS there. But you

Re: [patch 2.6.13-rc3a] i386: inline restore_fpu

2005-07-23 Thread Andi Kleen
Andrew Morton <[EMAIL PROTECTED]> writes: > > We do have the `used_math' optimisation in there which attempts to avoid > doing the FP save/restore if the app isn't actually using math. But > there's code in glibc startup which always does a > bit of float, so that optimisation is always defeated

Re: Mouse Freezes in Xorg on ASUS P4C800 Deluxe

2005-07-23 Thread Jesper Juhl
On 7/23/05, cengizkirli <[EMAIL PROTECTED]> wrote: > distro: Debian Unstable > kernels tested with: 2.6.13-rc3, 2.6.13-rc3-git5, 2.6.13-rc3-mm1 > compiler used: Debian gcc-4.0.1-2 > Xorg: Debian xorg-6.8.2-4 > ASUS P4C800 Deluxe BIOS: 1019 (2005-11-08) > > with or wihout ACPI enabled (acpi=off or

Re: fix suspend/resume irq request free for yenta..

2005-07-23 Thread Zwane Mwaikambo
On Sat, 23 Jul 2005, Russell King wrote: > On Sat, Jul 23, 2005 at 02:29:24AM +0200, Pavel Machek wrote: > > > Is it necessary to do free_irq for suspend? Shouldn't disable_irq > > > be enough? > > > > Due to recent changes in ACPI, yes, it is neccessary. > > What if some other driver is sharing

Re: PROBLEM: Opaque kernel bug in work with bzip2(?)

2005-07-23 Thread Zwane Mwaikambo
On Sat, 23 Jul 2005, [koi8-r] ? ? wrote: > The letter itself is in an attached file. Run memtest, it sounds like you have failing hardware.

Re: Mouse Freezes in Xorg on ASUS P4C800 Deluxe

2005-07-23 Thread cengizkirli
On 7/23/05, Jesper Juhl <[EMAIL PROTECTED]> wrote: > On 7/23/05, cengizkirli <[EMAIL PROTECTED]> wrote: > > distro: Debian Unstable > > kernels tested with: 2.6.13-rc3, 2.6.13-rc3-git5, 2.6.13-rc3-mm1 > > compiler used: Debian gcc-4.0.1-2 > > Xorg: Debian xorg-6.8.2-4 > > ASUS P4C800 Deluxe BIOS: 1

Re: oz6812, yenta_socket and madwifi

2005-07-23 Thread Daniel Ritz
hi since i'm the one that put that code there in the first place i guess i have to comment on it :) the attached patch should also fix your problem. and it cleans up the magic numbers a bit. rgds -daniel - [PATCH] disable read prefetch/write burst on old O2Micro bridges older O2Mi

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > jiffies/HZ is the more powerful API. The msec one which also sets > > > current to (un)interruptible is the simplified wrapper on top. > > > > So why do you want to hide it? > > I don't want to hide it at all. I want to provide a simpler v

Re: [ckrm-tech] Re: 2.6.13-rc3-mm1 (ckrm)

2005-07-23 Thread Mark Hahn
> > if CKRM is just extensions, I think it should be an external patch. > > if it provides a path towards unifying the many disparate RM mechanisms > > already in the kernel, great! > > OK, so if it provides a path towards unifying these, what should happen > to the old interfaces when they confli

Re: CheckFS: Checkpoints and Block Level Incremental Backup (BLIB)

2005-07-23 Thread Theodore Ts'o
On Sat, Jul 23, 2005 at 11:30:07AM +0530, Amit S. Kale wrote: > > We started it from 2.6.7 last year and then it was sitting idle for several > months for lack of resources. We'll go back to that version and generate a > diff that's easier to read. > > Yes, changing the name has made the task o

Re: HELP: NFS mount hangs when attempting to copy file

2005-07-23 Thread Trond Myklebust
on den 20.07.2005 Klokka 18:56 (-0400) skreiv Timothy Miller: > My research suggests that NFS client mounting is kernel-based, so > that's why I'm posting here. If there's a more appropriate list to > post to, I apologise, but I am not a list member. > > I'm having a bit of a problem doing simple

Re: kernel oops with x64_86 crossing 4Gb boundary

2005-07-23 Thread Andi Kleen
Francois Pepin <[EMAIL PROTECTED]> writes: > Hi, > > I am getting pseudo-random kernel oops on my Opteron box (Tyan Thunder > K8W) with 4Gb RAM. I am running RedHad FC3 with kernel > 2.6.11-1.35_FC3smp. > > It runs well with default BIOS settings, but only 3.5Gb RAM are visible. > Using the "Sof

[UPDATE PATCH] Add schedule_timeout_{interruptible,uninterruptible}_msecs() interfaces

2005-07-23 Thread Nishanth Aravamudan
On 23.07.2005 [12:30:00 +1000], Andrew Morton wrote: > Nishanth Aravamudan <[EMAIL PROTECTED]> wrote: > > > > > > +/* > > + * schedule_timeout_msecs - sleep until timeout > > + * @timeout_msecs: timeout value in milliseconds > > + * > > + * A human-time (but otherwise identical) alternative to > >

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Nishanth Aravamudan
On 23.07.2005 [12:50:45 +0200], Roman Zippel wrote: > Hi, > > On Fri, 22 Jul 2005, Arjan van de Ven wrote: > > > Also I'd rather not add the non-msec ones... either you're raw and use > > HZ, or you are "cooked" and use the msec variant.. I dont' see the point > > of adding an "in the middle" one

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Nishanth Aravamudan
On 23.07.2005 [13:55:58 +0200], Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > > What's wrong with using jiffies? > > > > A lot of the (driver) users want a wallclock based timeout. For that, > > miliseconds is a more obvious API with less chance to get the jif

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Nishanth Aravamudan
On 23.07.2005 [15:04:44 +0200], Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > > > > What's wrong with using jiffies? > > > > > > > > A lot of the (driver) users want a wallclock based timeout. For that, > > > > miliseconds is a more obvious API with less chanc

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Nishanth Aravamudan
On 23.07.2005 [15:29:42 +0200], Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > > jiffies/HZ is the more powerful API. The msec one which also sets > > current to (un)interruptible is the simplified wrapper on top. > > So why do you want to hide it? Make the jiffie

Re: Giving developers clue how many testers verified certain kernel version

2005-07-23 Thread Lee Revell
On Sat, 2005-07-23 at 19:05 +1000, Con Kolivas wrote: > Indeed, and the purpose of the benchmark is to quantify something rather than > leave it to subjective feeling. Fortunately if I was to quantify the current > kernel's situation I would say everything is fine. Agreed. Unfortunately everyth

Re: [2.6 patch] sound drivers select'ing ISAPNP must depend on PNP && ISA

2005-07-23 Thread Adrian Bunk
On Tue, Jul 19, 2005 at 10:50:53PM +0200, Bodo Eggert wrote: > On Tue, 19 Jul 2005, Adrian Bunk wrote: > > On Sun, Jul 17, 2005 at 05:07:48PM +0200, Bodo Eggert wrote: > > > > In sound/isa/Kconfig, select ISAPNP and depend on ISAPNP are intermixed, > > > resulting in funny behaviour. (Soundcarts

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Nishanth Aravamudan wrote: > set_current_state(TASK_{,UN}INTERRUPTIBLE); > schedule_timeout(msecs_to_jiffies(some_constant_msecs)); > > just have an interface that allows > > schedule_timeout_msecs_{,un}interruptible(some_constant_msecs); > > and push

[2.6 patch] sound/core/memalloc.c: fix PROC_FS=n compilation

2005-07-23 Thread Adrian Bunk
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:657: error: 'snd_mem_proc' undeclared (first use in this function) sound/core/memalloc.c:657: error: (Ea

Re: [PATCH] 2.6.13rc3: RLIMIT_RTPRIO broken

2005-07-23 Thread Lee Revell
On Sat, 2005-07-23 at 13:42 +0200, Andreas Steinmetz wrote: > RLIMIT_RTPRIO is supposed to grant non privileged users the right to use > SCHED_FIFO/SCHED_RR scheduling policies with priorites bounded by the > RLIMIT_RTPRIO value via sched_setscheduler(). This is usually used by > audio users. > > U

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Nishanth Aravamudan wrote: > > Keep the thing as simple as possible and jiffies _are_ simple. Please show > > me the problem, that needs to be fixed. > > I am not sure why jiffies are any simpler than milliseconds. In the > millisecond case, conversion happens in common

Re: [linux-pm] Re: [RFT] solve "swsusp plays yoyo" with disks

2005-07-23 Thread Rafael J. Wysocki
Hi, On Thursday, 21 of July 2005 21:20, Pavel Machek wrote: > hi! > > > >>I'd like to get this tested under as many configurations as > > >>possible. With this, your hdd should no longer do "yoyo" (spindown, > > >>spinup, spindown) during suspend... > > > > > > > > >It looks like the patch is now

Re: [2.6 patch] drivers/net/hamradio/: cleanups

2005-07-23 Thread Adrian Bunk
On Sun, Jun 26, 2005 at 07:00:13PM -0400, Jeff Garzik wrote: > randy_dunlap wrote: > >On Sun, 26 Jun 2005 18:26:49 -0400 Jeff Garzik wrote: > > > >| Adrian Bunk wrote: > >| > This patch contains the following cleanups: > >| > - dmascc.c: remove the unused global function dmascc_setup > >| > >| Bet

Re: [PATCH] 2.6.13rc3: RLIMIT_RTPRIO broken

2005-07-23 Thread Andreas Steinmetz
Lee Revell wrote: > On Sat, 2005-07-23 at 13:42 +0200, Andreas Steinmetz wrote: > >>RLIMIT_RTPRIO is supposed to grant non privileged users the right to use >>SCHED_FIFO/SCHED_RR scheduling policies with priorites bounded by the >>RLIMIT_RTPRIO value via sched_setscheduler(). This is usually used

Re: [patch 2.6.13-rc3a] i386: inline restore_fpu

2005-07-23 Thread Linus Torvalds
On Sat, 23 Jul 2005, Chuck Ebbert wrote: > >Probably a very minor point, but shouldn't it be > > "m" ((tsk)->thread.i387.fxsave)) > > because that's the largest possible operand that could end up being read? Yes, I ended up fixing that already (along with handling

Re: Supermount

2005-07-23 Thread Lasse Kärkkäinen / Tronic
> To mount on demand use autofs. Unmounting and dealing with media removal > is the problem. Granted, that can get pretty close. However, having to use /auto/* instead of mounting directly where required often limits using it quite a bit. Thus, I don't see it as a real alternative. - Tronic - s

Re: [patch 2.6.13-rc3a] i386: inline restore_fpu

2005-07-23 Thread Linus Torvalds
On Sat, 23 Jul 2005, Chuck Ebbert wrote: > > This patch (may not apply cleanly to unpatched -rc3) drops overhead > a few more percent: That really is pretty ugly. I'd rather hope for something like function-sections to just make games like this be unnecessary. The linker really should be able

Re: [patch 2.6.13-rc3a] i386: inline restore_fpu

2005-07-23 Thread Arjan van de Ven
On Sat, 2005-07-23 at 10:38 -0700, Linus Torvalds wrote: > So maybe a few hints to the binutils people might just make them go: "try > this patch/cmdline flag", and solve many more problems. They likely have a > lot of this kind of code _already_, or have at least been thinking about > it. > >

Re: [patch 2.6.13-rc3a] i386: inline restore_fpu

2005-07-23 Thread Linus Torvalds
On Sat, 23 Jul 2005, Arjan van de Ven wrote: > > For the kernel the runtime measurement is obviously tricky (kgprof > anyone?) Ehh, doesn't "opgprof" do that already? Anyway, judging by real life, people just don't _do_ profile runs. Any build automation that depends on the user profiling the

[PATCH 2.6.13rc3] IPv6: Check interface bindings on IPv6 raw socket reception

2005-07-23 Thread Andrew McDonald
Take account of whether a socket is bound to a particular device when selecting an IPv6 raw socket to receive a packet. Also perform this check when receiving IPv6 packets with router alert options. Signed-off-by: Andrew McDonald <[EMAIL PROTECTED]> diff -uprN linux-2.6.13-rc3.orig/include/net/ra

Re: Memory Management

2005-07-23 Thread Neil Horman
On Fri, Jul 22, 2005 at 08:23:19PM -0300, Márcio Oliveira wrote: > > > Roger, thanks for the information. > > I'm using Update 4 kernels (2.4.21-27.ELsmp - This kernel have some > mm / oom fixes) and don't have big problems when create large files, > plus the server is a 32-bit machine. > >

Re: [PATCH] Re: relayfs documentation sucks?

2005-07-23 Thread Christoph Hellwig
On Fri, Jul 22, 2005 at 01:01:32PM -0700, Paul Jackson wrote: > Another vote in favor of relayfs here ... > > I am reminded by my good colleagues at SGI that relayfs is a key > to the Linux Trace Toolkit (LTT), which is in turn an important > technology for some product(s) on which SGI is working.

Re: relayfs as infrastructure, ltt, systemtap, diskstat

2005-07-23 Thread Christoph Hellwig
On Fri, Jul 22, 2005 at 10:33:21PM +0200, bert hubert wrote: > On Fri, Jul 22, 2005 at 01:01:32PM -0700, Paul Jackson wrote: > > Another vote in favor of relayfs here ... > > At OLS the 'SystemTAP' idea was presented, which has been partially > implemented already, and it builds on relayfs as well

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Nishanth Aravamudan
On 23.07.2005 [19:17:37 +0200], Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Nishanth Aravamudan wrote: > > > > Keep the thing as simple as possible and jiffies _are_ simple. Please > > > show > > > me the problem, that needs to be fixed. > > > > I am not sure why jiffies are any simpler

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Nishanth Aravamudan
On 23.07.2005 [19:01:57 +0200], Roman Zippel wrote: > Hi, > > On Sat, 23 Jul 2005, Nishanth Aravamudan wrote: > > > set_current_state(TASK_{,UN}INTERRUPTIBLE); > > schedule_timeout(msecs_to_jiffies(some_constant_msecs)); > > > > just have an interface that allows > > > > schedule_ti

Re: tx queue start entry x dirty entry y (was 8139too PCI IRQ issues)

2005-07-23 Thread OGAWA Hirofumi
Mark Burton <[EMAIL PROTECTED]> writes: > Hi, > I'm getting similar results to Nick Warne, in that when my ethernet is > stressed at all (for instance by NFS), I end up with > nfs: server. not responding, still trying > nfs: server OK > > With a realtec card, I get errors in /var/spool/me

[BUG] Tulip for ULi M5263: No packets transmitted

2005-07-23 Thread Ricardo Bugalho
Hello, the tulip driver isn't work out for my ULi M5263 network adapter. The driver loads and the interface receives packets but it won't transmit any. Running a packet capture on it shows no outbound packets, so I guess the driver thinks the card is screwed up and can't transmit. I have a 939 AX8

Re: HPT370 errors under 2.6.13-rc3-mm1

2005-07-23 Thread Alan Cox
On Gwe, 2005-07-22 at 22:47 -0400, Bartlomiej Zolnierkiewicz wrote: > Hi, > > Does vanilla kernel 2.6.12 work for you? > It doesn't contain hpt366 driver update. Its nothing to do with the driver. Read the trace Bartlomiej > > Jul 23 01:30:21 localhost kernel: hdf: dma timeout error: status=0x25

Re: kernel optimization

2005-07-23 Thread Alan Cox
On Sad, 2005-07-23 at 02:30 -0400, [EMAIL PROTECTED] wrote: > Larger does not always mean slower. If it did, nobody would implement a > loop unrolling optimization. Generally speaking nowdays it does. Almost all loop unrolls are a loss on PIV. > ex. Look at how GCC generates jump tables for swit

Re: HPT370 errors under 2.6.13-rc3-mm1

2005-07-23 Thread Alan Cox
On Sad, 2005-07-23 at 14:28 +1200, mdew wrote: > I'm unable to mount an ext2 drive using the hpt370A raid card. > > upon mounting the drive, dmesg will spew these errors..I've tried > different cables and drive is fine. > Jul 23 01:30:21 localhost kernel: hdf: dma timeout error: status=0x25 > { D

Re: [PATCH] reset VGA adapters via BIOS on resume... (non-fbdev/con)

2005-07-23 Thread Alan Cox
On Sad, 2005-07-23 at 00:17 +0100, Matthew Garrett wrote: > Dave Airlie <[EMAIL PROTECTED]> wrote: > > > At OLS at lot of people were giving out about cards not resuming, > > so using a patch from Michael Marineau and help from lots of people > > sitting around in a circle at OLS I've gotten a

Re: Mouse Freezes in Xorg on ASUS P4C800 Deluxe

2005-07-23 Thread cengizkirli
I've posted the original mail to [EMAIL PROTECTED], too. - 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] kill bio->bi_set

2005-07-23 Thread Peter Osterlund
Jens Axboe <[EMAIL PROTECTED]> writes: > Dunno why I didn't notice before, but ->bi_set is totally unnecessary > bloat of struct bio. Just define a proper destructor for the bio and it > already knows what bio_set it belongs too. This causes crashes on my computer. > +void bio_free(struct bio *b

Device supported by the OSS trident driver not supported by ALSA

2005-07-23 Thread Adrian Bunk
I'm currently creating a list of OSS drivers where all the hardware supported by them is also supported by ALSA. The goal is to schedule them for removal (except someone tells that for one or more of them ALSA support is inferior). The OSS trident driver has 5 different pci_device_id entries.

[PATCH] pcibios_bus_to_resource for parisc [Was: Re: [PATCH 8/8] pci and yenta: pcibios_bus_to_resource]

2005-07-23 Thread Dominik Brodowski
On Mon, Jul 18, 2005 at 01:42:16PM -0600, Grant Grundler wrote: > On Tue, Jul 12, 2005 at 12:21:38AM +0200, Dominik Brodowski wrote: > > In yenta_socket, we default to using the resource setting of the CardBus > > bridge. However, this is a PCI-bus-centric view of resources and thus > > needs to be

Re: [PATCH 2.6.13-rc3] pcmcia: pcmcia_request_irq for !IRQ_HANDLE_PRESENT

2005-07-23 Thread Dominik Brodowski
Hi, > When a driver calls pcmcia_request_irq with IRQ_HANDLE_PRESENT unset, it looks > for an open IRQ by request_irq()ing with a dummy handler and NULL dev_info. > free_irq uses dev_info as a key for identifying the handler to free among > those > sharing an IRQ, so request_irq returns -EINVAL i

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Nishanth Aravamudan wrote: > > Jiffies are the basic time unit for kernel timers, hiding that fact gives > > users only wrong expectations about them. > > We already have msleep() and msleep_interruptible(), which hide jiffies > in milliseconds. These interfaces are the

Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces

2005-07-23 Thread Roman Zippel
Hi, On Sat, 23 Jul 2005, Nishanth Aravamudan wrote: > > What's wrong with just: > > > > > > schedule_timeout_{,un}interruptible(msecs_to_jiffies(some_constant_msecs)); > > Nothing, I suppose. I just prefer directly using msecs. I understand > your point more now, I think. You are worried a

Re: [PATCH] kill bio->bi_set

2005-07-23 Thread Jens Axboe
On Sat, Jul 23 2005, Peter Osterlund wrote: > Jens Axboe <[EMAIL PROTECTED]> writes: > > > Dunno why I didn't notice before, but ->bi_set is totally unnecessary > > bloat of struct bio. Just define a proper destructor for the bio and it > > already knows what bio_set it belongs too. > > This caus

Re: [2.6 patch] drivers/ieee1394/sbp2.c: fix warnings with -Wundef

2005-07-23 Thread Stefan Richter
On 22 Jul, Adrian Bunk wrote: > drivers/ieee1394/sbp2.c:202:5: warning: "CONFIG_IEEE1394_SBP2_DEBUG" is not > defined > drivers/ieee1394/sbp2.c:207:7: warning: "CONFIG_IEEE1394_SBP2_DEBUG" is not > defined > drivers/ieee1394/sbp2.c:2053:6: warning: "CONFIG_IEEE1394_SBP2_DEBUG" is not > defined >

[cpufreq] ondemand works, conservative doesn't

2005-07-23 Thread Sven Köhler
Hi, currently, i'm using the ondemand governor. My CPU supports the frequencies 800, 1800 and 2000 MHz (AMD Athlon64 Desktop with Cool&Quiet). The simple bash commands while true do true done cause 100% CPU usage, and the CPU immediatly switched from 800 to 2000MHz. Using the conserva

Re: kernel optimization

2005-07-23 Thread cutaway
I submit that sparse switch jump table's are not an "unusual" construct in the Linux kernel/drivers. GCC only creates a table large enough to cover the largest of the sparse values - it doesn't have to be 0...255. 0...60 with 10 values sparsely scattered would generate a 61 element jump table. T

[-mm patch] DLM must depend on SYSFS

2005-07-23 Thread Adrian Bunk
CONFIG_DLM=y and CONFIG_SYSFS=n results in the following compile error: <-- snip --> ... LD vmlinux drivers/built-in.o:(.data+0x271e80): undefined reference to `kernel_subsys' make: *** [vmlinux] Error 1 <-- snip --> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- linux-2.6.13-r

[2.6 patch] SECURITY must depend on SYSFS

2005-07-23 Thread Adrian Bunk
CONFIG_SECURITY=y and CONFIG_SYSFS=n results in the following compile error: <-- snip --> ... LD vmlinux security/built-in.o: In function `securityfs_init': inode.c:(.init.text+0x1c2): undefined reference to `kernel_subsys' make: *** [vmlinux] Error 1 <-- snip --> Signed-off-by: Ad

[2.6 patch] net/ipv4/: possible cleanups

2005-07-23 Thread Adrian Bunk
This patch contains the following possible cleanups: - make needlessly global code static - #if 0 the following unused global function: - xfrm4_state.c: xfrm4_state_fini - remove the following unneeded EXPORT_SYMBOL's: - ip_output.c: ip_finish_output - ip_output.c: sysctl_ip_default_ttl - f

[2.6 patch] FB_INTEL must depend on HW_CONSOLE

2005-07-23 Thread Adrian Bunk
CONFIG_FB_INTEL=y and CONFIG_HW_CONSOLE results in the following compile error: <-- snip --> ... LD vmlinux drivers/built-in.o: In function `intelfb_pci_register': intelfbdrv.c:(.text+0x171960): undefined reference to `color_table' intelfbdrv.c:(.text+0x171971): undefined reference to `

[2.6 patch] merge some from Rusty's trivial patches

2005-07-23 Thread Adrian Bunk
This patch contains the most trivial from Rusty's trivial patches: - spelling fixes - remove duplicate includes I don't see a reason why they shouldn't be merged now. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- Documentation/mono.txt |2 +- Documentation/pci.txt

Re: kernel page size explanation

2005-07-23 Thread Gaspar Bakos
Hi, Jesper, RE: > > 2. how can one tune it (for 2.6.*)? > > For some archs the page size can be set at compile-time with > CONFIG_PAGE_SIZE_4KB, CONFIG_PAGE_SIZE_8KB etc - mips is an example of > such an arch (also take a look at CONFIG_HUGETLB_PAGE and friends). OK, now i figured it out. On AMD

[2.6 patch] DEBUG_FS must depend on SYSFS

2005-07-23 Thread Adrian Bunk
CONFIG_DEBUG_FS=y and CONFIG_SYSFS=n results in the following compile error: <-- snip --> ... LD vmlinux fs/built-in.o: In function `debugfs_init': inode.c:(.init.text+0x31be): undefined reference to `kernel_subsys' make: *** [vmlinux] Error 1 <-- snip --> Signed-off-by: Adrian Bun

[patch 2.6.13-rc3] i386: add alternative_output() for altinstructions

2005-07-23 Thread Chuck Ebbert
This patch adds alternative_output() for altinstructions that have output. Only one output is allowed. It also cleans up the comments for alternative_input(). With this patch in place, I cleaned up the i387 save/restore in my local copy so it now looks like this: ==

Re: [PATCH] reset VGA adapters via BIOS on resume... (non-fbdev/con)

2005-07-23 Thread Dave Airlie
> > For Intel at least the recommendation is to use the BIOS "save > mode"/"restore mode" interface. I'm going to see about implementing that on my PC when I get back to home, it doesn't seem like too bad an idea either... We are also going to provide some hooks out to userspace as well.. but I'

Re: fix suspend/resume irq request free for yenta..

2005-07-23 Thread Dave Airlie
. > > > > What if some other driver is sharing the IRQ, and requires IRQs to be > > enabled for the resume to complete? All drivers re-enable IRQs on their way back up in their resume code, they shouldn't be doing anything before that point.. > This certainly is the case on many laptops. Well at

Re: Memory Management

2005-07-23 Thread Márcio Oliveira
Neil, The best way I can think to do that is take a look at /proc/slabinfo. That will likely give you a pointer to which area of code is eating up your memory. OK. I will monitor the /proc/slabinfo file. Based on the sysrq-m info you posted it looks like due to fragmentation the largest c

Re: [PATCH] i386: Selectable Frequency of the Timer Interrupt

2005-07-23 Thread randy_dunlap
On Sat, 16 Jul 2005 23:55:17 -0400 Lee Revell wrote: > On Sat, 2005-07-16 at 19:35 -0700, Nish Aravamudan wrote: > > As you've seen, I think it depends on the timesource: for the PIT, it > > would be arch/i386/kernel/timers/timer_pit.c::setup_pit_timer(). > > That one looks pretty straightforwar

Re: fix suspend/resume irq request free for yenta..

2005-07-23 Thread Daniel Ritz
hi the patch is wrong. yenta_request_irq() registers the wrong handler. plus yenta_probe_cb_irq() has nothing to do with suspend/resume (besides it frees the irq in the very same function). correct patch below. somebody cares to explain me why the free_irq() is necessary before a suspend? rgds -

Re: [PATCH] i386: Selectable Frequency of the Timer Interrupt

2005-07-23 Thread randy_dunlap
On Fri, 15 Jul 2005 05:46:44 +0200 Jesper Juhl wrote: > +static int __init jiffies_increment_setup(char *str) > +{ > + printk(KERN_NOTICE "setting up jiffies_increment : "); > + if (str) { > + printk("kernel_hz = %s, ", str); > + } else { > + printk("kernel_hz i

Re: [PATCH] i386: Selectable Frequency of the Timer Interrupt

2005-07-23 Thread Jesper Juhl
On 7/24/05, randy_dunlap <[EMAIL PROTECTED]> wrote: > On Fri, 15 Jul 2005 05:46:44 +0200 Jesper Juhl wrote: > > > +static int __init jiffies_increment_setup(char *str) > > +{ > > + printk(KERN_NOTICE "setting up jiffies_increment : "); > > + if (str) { > > + printk("kernel_hz =

[-mm PATCH] v4l: hybrid dvb: fix warnings with -Wundef

2005-07-23 Thread Michael Krufky
This patch adds a missing #ifdef to saa7134-dvb.c (thanks to Mauro Carvalho Chehab) and changes #if to #ifdef in both files. Signed-off-by: Michael Krufky <[EMAIL PROTECTED]> linux/drivers/media/video/cx88/cx88-dvb.c | 24 linux/drivers/media/video/saa7134/saa7134-dvb.

  1   2   >