* Nick Piggin <[EMAIL PROTECTED]> wrote:
> 3/5
> The fundamental problem that Suresh has with balance on exec and fork
> is that it only tries to balance the top level domain with the flag
> set.
>
> This was worked around by removing degenerate domains, but is still a
> problem if people want
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> 2/5
> The previous patch fixed the last 2 places that directly access a
> runqueue's sched-domain and assume it cannot be NULL.
>
> We can now use a NULL domain instead of a dummy domain to signify
> no balancing is to happen. No functional changes.
>
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> > 2/5
>
> > The previous patch fixed the last 2 places that directly access a
> > runqueue's sched-domain and assume it cannot be NULL.
> >
> > We can now use a NULL domain instead of a dummy domain to
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> This is Suresh's patch with some modifications.
> Remove degenerate scheduler domains during the sched-domain init.
actually, i'd suggest to not do this patch. The point of booting with a
CONFIG_NUMA kernel on a non-NUMA box is mostly for testing,
building this sucker as a module caused grief.
drivers/net/chelsio/cxgb2.c:113: error: `__mod_pci_device_table' aliased
to external symbol `t1_pci_tbl'.
This seems to do the trick. (untested beyond compile)
Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
Dave
---
On Tue, 2005-04-05 at 06:13 +0200, Ingo Molnar wrote:
> * Lee Revell <[EMAIL PROTECTED]> wrote:
>
> > I can trigger latencies up to ~1.1 ms with a CVS checkout. It looks
> > like inside ext3_try_to_allocate_with_rsv, we spend a long time in this
> > loop:
> >
> > ext3_test_allocatable
On April 5, 2005 09:22 pm, Berck E. Nash wrote:
> 2.6.12-rc2-mm1 fails to build for me with the following error:
>
> arch/i386/lib/mmx.c:374: error: conflicting types for `mmx_clear_page'
> include/asm/mmx.h:11: error: previous declaration of `mmx_clear_page'
> make[1]: *** [arch/i386/lib/mmx.o]
On Tue, Apr 05, 2005 at 09:20:57PM -0400, Trond Myklebust wrote:
> ty den 05.04.2005 Klokka 11:46 (-0400) skreiv Benjamin LaHaise:
>
> > I can see that goal, but I don't think introducing iosems is the right
> > way to acheive it. Instead (and I'll start tackling this), how about
> > factoring
On Tue, 05 Apr 2005 21:48:22 PDT, David Mosberger wrote:
> > On Tue, 5 Apr 2005 17:33:59 -0700 (PDT), Christoph Lameter <[EMAIL
> > PROTECTED]> said:
>
> Christoph> Which benchmark would you recommend for this?
>
> I don't know about "recommend", but I think SPECweb, SPECjbb,
>
On Tue, Apr 05, 2005 at 11:46:41AM -0400, Benjamin LaHaise wrote:
> On Mon, Apr 04, 2005 at 01:56:35PM -0400, Trond Myklebust wrote:
> > IOW: the current semaphore implementations really all need to die, and
> > be replaced by a single generic version to which it is actually
> > practical to add
> On Tue, 5 Apr 2005 17:33:59 -0700 (PDT), Christoph Lameter <[EMAIL
> PROTECTED]> said:
Christoph> Which benchmark would you recommend for this?
I don't know about "recommend", but I think SPECweb, SPECjbb,
the-UNIX-multi-user-benchmark-whose-name-I-keep-forgetting, and in
general
On Tue, Apr 05, 2005 at 09:55:06AM +0800, Li Shaohua wrote:
> On Mon, 2005-04-04 at 23:33, Nathan Lynch wrote:
> > No. It should make zero difference to the scheduler whether the "play
> > dead" cpu hotplug or "physical" hotplug is being used.
> Keeping some fields like 'cpu_load' are meanless
[EMAIL PROTECTED] wrote:
Hey,
I apologize in advance if this is not the right place
to ask. Feel free to redirect me there :)
I just wanted to know if the 2.4 kernel is aware of
hyperthreading the same way the 2.6 kernel ist or if
the issues posted earlier
I'm not sure if the stock 2.4 kernels
Alan Cox wrote:
On Sad, 2005-04-02 at 05:50, Robert Hancock wrote:
I'm wondering if one does a ton of these cache-bypassing stores whether
something gets hosed because of that. Not sure what that could be
though. I don't imagine the chipset is involved with any of that on the
Athlon 64 - either
Derek Cheung wrote:
Below please find the patch file I "diff" against Linux 2.6.11.6. It
contains the I2C adaptor for ColdFire 5282 CPU. Since most ColdFire
CPU
shares the same I2C register set, the code can be easily adopted for
other ColdFire CPUs for I2C operations.
I have tested the code on a
Ingo Molnar wrote on Monday, April 04, 2005 8:05 PM
>
> latest patch attached. Changes:
>
> - stabilized calibration even more, by using cache flushing
>instructions to generate a predictable working set. The cache
>flushing itself is not timed, it is used to create quiescent
>cache
On Tue, Apr 05, 2005 at 10:18:15PM -0400, Derek Cheung wrote:
> Hi Greg and Andrew,
After you fix the diff issues that Randy pointed out, please be sure to
CC: the sensors mailing list as found in the MAINTAINERS file. I know
they will be able to give you feedback on the code.
thanks,
greg
unsubscribe linux-kernel
-
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/
I've been meaning to play with inotify for a while now and finally made
time for it tonight. I'm not much of a GUI guy, so I'm mostly interested
in exploring the command line applications of inotify --i.e., what sort of
havoc can I wreak with it in a script.
To that end I sat down tonight a threw
Derek Cheung wrote:
Below please find the patch file I "diff" against Linux 2.6.11.6. It
contains the I2C adaptor for ColdFire 5282 CPU. Since most ColdFire
CPU
shares the same I2C register set, the code can be easily adopted for
other ColdFire CPUs for I2C operations.
I have tested the code on a
$B"#"""#(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(B
(B $B!!7k:'!?M!'C#(B
(B $BM}A[$NAjhttp://www.deai2005.com/user.app?cmd=entry&[EMAIL PROTECTED]=sp
(B
(B $B"!"!2K$J?M!"Nx?M!&7k:'$r9M$($F$$$k$J$i"!"!(B
(B
On Wednesday 06 April 2005 04:50, you wrote:
> Since tasklets are typically used for bottom half processing, is it
> acceptable/recommended that they be scheduled from a process context
> (say an ioctl handler)?
>
> Should one try to minimize such scheduling and try to do things in process
>
Hi,
I have a query.
Since tasklets are typically used for bottom half
processing, is it acceptable/recommended that they
be scheduled from a process context (say an ioctl handler)?
Should one try to minimize such scheduling and try to
do things in process context if possible, as tasklets run
So nobody minds if I make this into a CONFIG option marked as Deprecated? :)
Shawn.
>
> > Do you know if /proc/acpi/sleep will be deprecated in
> > favour of /sys/power/state? If so, this thread will be
> > moot ;)
>
> No idea, deprecating it would be ok with me.
>
>Pavel
On Wednesday 06 April 2005 04:09, Matt Mackall wrote:
> While there may be reasons why mixed case is suboptimal, the real
> reason is that it's hard to keep track of which style is used where.
> It's annoying and error-prone to have to remember the naming format
> for everything in addition to its
Thanks Andrew. Enclosed please find the patch file.
Regards,
Derek
-Original Message-
From: Andrew Morton [mailto:[EMAIL PROTECTED]
Sent: April 5, 2005 10:22 PM
To: Derek Cheung
Cc: [EMAIL PROTECTED]; Linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel 2.6.11.6 - I2C adaptor for
"Derek Cheung" <[EMAIL PROTECTED]> wrote:
>
> Below please find the patch file I "diff" against Linux 2.6.11.6. It
> contains the I2C adaptor for ColdFire 5282 CPU. Since most ColdFire CPU
> shares the same I2C register set, the code can be easily adopted for
> other ColdFire CPUs for I2C
Hi Greg and Andrew,
Below please find the patch file I "diff" against Linux 2.6.11.6. It
contains the I2C adaptor for ColdFire 5282 CPU. Since most ColdFire CPU
shares the same I2C register set, the code can be easily adopted for
other ColdFire CPUs for I2C operations.
I have tested the code on
On Tuesday April 5, [EMAIL PROTECTED] wrote:
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Well, Seeing you asked...
PM resume certainly seems to be improving.
My main problem in rc1-mm3 is with PCMCIA.
If I stop cardmgr before
On Wed, Apr 06, 2005 at 03:29:21AM +0200, Kenneth Aafl?y wrote:
> Hi,
>
> while reading Documentation/CodingStyle for the nth time, I realized that I
> had
> read some conflicting coding style in some patch posted to the linux-kernel
> mailing-list; in include/linux/page-flags.h, there is a lot
Steven Cole <[EMAIL PROTECTED]> wrote:
>
> arch/i386/kernel/setup.c: In function 'setup_arch':
> arch/i386/kernel/setup.c:1571: warning: implicit declaration of function
> 'acpi_boot_table_init'
> arch/i386/kernel/setup.c:1572: warning: implicit declaration of function
> 'acpi_boot_init'
Norbert Preining <[EMAIL PROTECTED]> wrote:
>
> On Die, 05 Apr 2005, Pavel Machek wrote:
> > Well, I do not have working suspend-to-RAM setup close to me... Could
> > you try 2.6.12-rc1 to see if reboot problem is -mm specific or not?
>
> 2.6.12-rc2 suspends and resumes with the very same config
Hi,
while reading Documentation/CodingStyle for the nth time, I realized that I had
read some conflicting coding style in some patch posted to the linux-kernel
mailing-list; in include/linux/page-flags.h, there is a lot of defines that are
apparently frowned upon:
HOWEVER, while mixed-case names
arch/i386/lib/mmx.c:374: error: conflicting types for `mmx_clear_page'
include/asm/mmx.h:11: error: previous declaration of `mmx_clear_page'
make[1]: *** [arch/i386/lib/mmx.o] Error 1
CONFIG_X86_PC=y
CONFIG_MK7=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
Mingming Cao <[EMAIL PROTECTED]> wrote:
>
> I run the test(20 instances of fsx) with your patch on 2.6.12-rc1 with
> 512MB RAM (where I were able to constantly re-create the mem leak and
> lead to OOM before). The result is the kernel did not get into OOM after
> about 19 hours(before it took
2.6.12-rc2-mm1 fails to build for me with the following error:
arch/i386/lib/mmx.c:374: error: conflicting types for `mmx_clear_page'
include/asm/mmx.h:11: error: previous declaration of `mmx_clear_page'
make[1]: *** [arch/i386/lib/mmx.o] Error 1
make: *** [arch/i386/lib] Error 2
I hope this is
On Tue, 2005-04-05 at 17:53 -0700, Rusty Lynch wrote:
> From just a casual look, it seems like this could be used to monitor the
> comings and goings of processes by monitoring /proc. Unfortunately
> inotify doesn't seem to be getting all the events on the proc filesystem
> like it does on a
ty den 05.04.2005 Klokka 11:46 (-0400) skreiv Benjamin LaHaise:
> I can see that goal, but I don't think introducing iosems is the right
> way to acheive it. Instead (and I'll start tackling this), how about
> factoring out the existing semaphore implementations to use a common
>
"Barry K. Nathan" <[EMAIL PROTECTED]> wrote:
>
> On Tue, Apr 05, 2005 at 06:44:08AM -0700, Barry K. Nathan wrote:
> > swsusp: reading slkf;jalksfsadflkjas;dlfasdfkl (12345 pages): 34%
> > [sorry, I just got up so my short-term memory isn't working that well
> > yet]
> >
> > takes 10-30 minutes
On Tue, Apr 05, 2005 at 05:05:04PM -0700, Greg KH wrote:
> On Tue, 2005-04-05 at 19:46 -0400, Ryan Anderson wrote:
> > highlight WhitespaceEOL ctermbg=red guibg=red
> > match WhitespaceEOL /\s\+$/
>
> Very nice, thanks a lot for that.
let c_space_errors=1 also works great.
On Tue, 5 Apr 2005, David Mosberger wrote:
> What LMbench test other than fork/exec would you have expected to be
> affected by this? LMbench is not a good benchmark for this (remember:
> it's a _micro_ benchmark).
LMbench does a variety of things and I expected to see at least
something on the
> On Tue, 5 Apr 2005 17:15:53 -0700 (PDT), Christoph Lameter <[EMAIL
> PROTECTED]> said:
Christoph> On Thu, 24 Mar 2005, David Mosberger wrote:
>> That's definitely the case. See my earlier post on this topic:
>> http://www.gelato.unsw.edu.au/linux-ia64/0409/11012.html
>>
On Thu, 24 Mar 2005, David Mosberger wrote:
> That's definitely the case. See my earlier post on this topic:
>
> http://www.gelato.unsw.edu.au/linux-ia64/0409/11012.html
>
> Unfortunately, nobody reported any results for larger machines and/or
> more interesting workloads, so the patch is in
On Tue, Apr 05, 2005 at 10:54:09AM +0200, Ben Castricum wrote:
>
> 2.6.12-rc1 compiles and runs perfectly.
>
> gcc version 2.95.3 20010315 (release)
>
> CC [M] drivers/usb/class/cdc-acm.o
> In file included from drivers/usb/class/cdc-acm.c:63:
> include/linux/usb_cdc.h:117: field
On Tue, Apr 05, 2005 at 08:56:09PM +0200, Josselin Mouette wrote:
> Le mardi 05 avril 2005 à 12:50 -0600, Chris Friesen a écrit :
> > Josselin Mouette wrote:
> >
> > > The fact is also that mixing them with a GPLed software gives
> > > an result you can't redistribute - although it seems many
Jens Axboe wrote on Tuesday, April 05, 2005 7:54 AM
> On Tue, Mar 29 2005, Chen, Kenneth W wrote:
> > Jens Axboe wrote on Tuesday, March 29, 2005 12:04 PM
> > > No such promise was ever made, noop just means it does 'basically
> > > nothing'. It never meant FIFO in anyway, we cannot break the
Ingo Molnar wrote on Sunday, April 03, 2005 11:24 PM
> great! How long does the benchmark take (hours?), and is there any way
> to speed up the benchmarking (without hurting accuracy), so that
> multiple migration-cost settings could be tried? Would it be possible to
> try a few other values via
On Tue, 2005-04-05 at 19:46 -0400, Ryan Anderson wrote:
> highlight WhitespaceEOL ctermbg=red guibg=red
> match WhitespaceEOL /\s\+$/
Very nice, thanks a lot for that.
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Nick Wilson wrote:
Fixes compiler warnings:
warning: passing arg 2 of `writeb' makes pointer from integer without a cast
warning: passing arg 1 of `readw' makes pointer from integer without a cast
(added to CC list, just to update people on the status of these
warnings... I know they're
Hi Dave,
On Tue, 5 Apr 2005 13:57:37 -0700 "David S. Miller" <[EMAIL PROTECTED]> wrote:
>
> --- 1.19/include/asm-sparc64/compat.h 2005-02-17 21:53:03 -08:00
> +++ edited/include/asm-sparc64/compat.h 2005-04-05 12:37:58 -07:00
> @@ -51,11 +51,11 @@
> compat_dev_tst_rdev;
>
5/5
Any ideas about what to do with schedstats?
Do we really need balance on exec and fork as seperate
statistics?
Consolidate balance-on-exec with balance-on-fork. This is made easy
by the sched-domains RCU patches.
As well as the general goodness of code reduction, this allows
the runqueues to
On Tue, Apr 05, 2005 at 01:49:18PM -0700, Greg KH wrote:
> On Tue, 2005-04-05 at 13:27 -0700, David Mosberger wrote:
> > > On Tue, 5 Apr 2005 09:46:48 -0700, Greg KH <[EMAIL PROTECTED]> said:
> >
> > Greg> -stable review patch. If anyone has any objections, please
> > Greg> let us know.
4/5
One of the problems with the multilevel balance-on-fork/exec is that it
needs to jump through hoops to satisfy sched-domain's locking semantics
(that is, you may traverse your own domain when not preemptable, and
you may traverse others' domains when holding their runqueue lock).
3/5
The fundamental problem that Suresh has with balance on exec and fork
is that it only tries to balance the top level domain with the flag
set.
This was worked around by removing degenerate domains, but is still a
problem if people want to start using more complex sched-domains, especially
2/5
The previous patch fixed the last 2 places that directly access a
runqueue's sched-domain and assume it cannot be NULL.
We can now use a NULL domain instead of a dummy domain to signify
no balancing is to happen. No functional changes.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index:
This is Suresh's patch with some modifications.
--
SUSE Labs, Novell Inc.
Remove degenerate scheduler domains during the sched-domain init.
For example on x86_64, we always have NUMA configured in. On Intel EM64T
systems, top most sched domain will be of NUMA and with only one sched_group in
it.
Siddha, Suresh B wrote:
On Tue, Apr 05, 2005 at 05:33:49PM +1000, Nick Piggin wrote:
Suresh's underlying problem with the unnecessary sched domains
is a failing of sched-balance-exec and sched-balance-fork, which
That wasn't the only motivation. For example, on non-HT cpu's we shouldn't
be
On Tue, 2005-04-05 at 23:44 +0200, Andreas Schwab wrote:
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
>
> > After discussion with ATIs, it seems that the workarounds they initially
> > gave me were not completely correct.
> >
> > This patch implements the proper ones, which includes
Here comes version 2 of the disable built-in patch.
This patch makes it possible to disable built-in code from the kernel
command line. The patch is rather simple - it extends the compiled-in case
of module_init() to include __setup() with a name based on KBUILD_MODNAME.
As an example, if you
Dan Stromberg wrote:
Some questions for the list:
1) Is anyone on the list using AOE in production?
2) Is anyone on the list using AOE in combination with md and/or LVM2?
3) Is anyone on the list using AOE on a 64 bit platform?
While I think AoE is "neat", IMO you really want to use something
On Apr 5, 2005 4:10 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
>
> > On Mar 26, 2005 12:59 AM, Julien Wajsberg <[EMAIL PROTECTED]> wrote:
> >> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> >> experiment the following
Hi,
On Wed, 2005-03-30 at 12:59, Marcelo Tosatti wrote:
> > I'm not certain that this is right, but it seems possible and would
> > explain the symptoms. Maybe Stephen or Andrew could comments?
>
> Andrew, Stephen?
Sorry, was offline for a week last week; I'll try to look at this more
closely
On mar, 2005-04-05 at 16:56 +0200, Esben Stien wrote:
> Esben Stien <[EMAIL PROTECTED]> writes:
>
> > can't find a single problem with the device.
>
> I should mention a couple of things after some testing: There are some
> inconsistencies with regard to cruise control.
>
> When I press TOP
On Die, 05 Apr 2005, Pavel Machek wrote:
> Well, I do not have working suspend-to-RAM setup close to me... Could
> you try 2.6.12-rc1 to see if reboot problem is -mm specific or not?
2.6.12-rc2 suspends and resumes with the very same config file (well,
after running make oldconfig) without any
Please don't remove Linux-Kernel from the CC, I think this is an
important discussion.
On Apr 05, 2005, at 15:17, Renate Meijer wrote:
Strictly speaking, a definition starting with a double
underscore is reserved for use by the compiler and associated
libs
Well, _strictly_speaking_, it's
On Tue, 2005-04-05 at 19:20 +0200, Prakash Punnoor wrote:
> BTW, what else could I use to make use of inotify? I know fam, which afaik
> only uses dnotify.
Here is a little sample glib application that shows the ease-yet-power
of inotify.
On Tue, Apr 05, 2005 at 07:14:45AM -0700, Barry K. Nathan wrote:
> 2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
> 2.6.11-bk10 has the weird slowdown.
>
> I'll see if I can isolate it any further.
2.6.11-mm2 works, but 2.6.11-mm3 has the ridiculously slow resumes.
Later today
Jeff Garzik wrote:
Josselin Mouette wrote:
Finally, you shouldn't forget that, technically speaking, using hotplug
for uploading the firmware is much more flexible and elegant than
including it in the kernel. Upgrading the firmware and the module should
be two independent operations. People who
On Tue, Apr 05, 2005 at 05:45:58PM +0200, Jan Dittmer wrote:
> Something has broken make O= :
>
> HOSTCC scripts/kallsyms
> HOSTCC scripts/conmakehash
> make[1]: *** No rule to make target `include/asm', needed by
> `arch/alpha/kernel/asm-offsets.s'. Stop.
> make: *** [_all] Error 2
>
>
Hi Rany et all.
I have committed the following patch and it will be present in next -mm.
It is present (as the only additional cset) in
bk://linux-sam.bkbits.net/kconfig
davem - any suggestion for next step.
Preferably this goes to Linus via you - or?
Sam
# This is a BitKeeper
Actually I don't use CONFIG_DEVFS_FS as it tends to break things here
(and I found wasn't necessary for things to work, in fact it got in the
way of some things working, some of the autodetect/hotplug peripherels
didn't like it). Thank you for the reply though.
Bob
On Mon, 2005-04-04 at 20:14
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
> After discussion with ATIs, it seems that the workarounds they initially
> gave me were not completely correct.
>
> This patch implements the proper ones, which includes sleeping in PLL
> accesses, and thus requires the previous patch to make
Hi!
This fixes u32 vs. pm_message_t confusion in documentation, and
removes references to no-longer-existing (*save_state), too. With
exception of USB (I hope David will fix/apply my patch), this should
fix last piece of this confusion... famous last words.
Please apply,
On Apr 05, 2005, at 08:18, Richard B. Johnson wrote:
One cannot just use 'int' or 'long', in particular when interfacing
with an operating system. For example, look at the socket interface
code. Parameters are put into an array of longs and a pointer to
this array is passed to the socket
Hi!
This fixes u32 vs. pm_message_t confusion in drivers/video. Should
change no code. Please apply,
Pavel
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
--- clean-mm/drivers/video/backlight/corgi_bl.c 2005-03-19
Hi!
This fixes u32 vs. pm_message_t confusion in remaining
places. Fortunately there's few of them. Should
change no code. Please apply,
Pavel
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
--- clean-mm/arch/sh/kernel/cpu/bus.c
Hi!
> > I do not know why you can't unload them, but what about simply not
> > loading them at all? :-).
>
> hotplug.
>
>
> Whatever, booting with init=/bin/sh I get these processes running
> PID TTY STAT TIME COMMAND
> 1 ?R 0:00 /bin/bash
> 2 ?SN 0:00
Hi!
-rc2-mm1 still contains few places where u32 and pm_message_t. This
fixes drivers/serial [should change no code]. Please apply,
Pavel
--- clean-mm/drivers/serial/amba-pl010.c2004-12-25 13:35:01.0
+0100
+++
Hi!
> Actually, please do NOT apply this. It conflicts with other
> patches, which have been in the past few MM releases, have
> also been circulated on linux-usb-devel, and actually address
> some of the bugs which crept in as things have changed around
> the USB stack.
It seems to me that USB
[MFT set to -legal, as this is becoming legal arcana probably not
particularly interesting to any other list.]
On Tue, 05 Apr 2005, Sven Luther wrote:
> There are two solutions to this issue, either you abide by the GPL
> and provide also the source code of those firmware binaries (the
> prefered
On Die, 05 Apr 2005, Pavel Machek wrote:
> Well, I do not have working suspend-to-RAM setup close to me... Could
> you try 2.6.12-rc1 to see if reboot problem is -mm specific or not?
You mean rc2? with rc1-mm4 it is working.
> input is known for some funky behaviour, especially with
> synaptics.
This recently got changed to include a lot of kernel internal
stuff in the non-__KERNEL__ area of the header, which isn't
so kosher and breaks libc builds.
The fix is pretty simple.
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
= include/linux/atalk.h 1.12 vs edited =
---
Hi,
There are some problems I have on my laptop using SWSUPS. This is it's
summary:
1] When hibernate with different hw configuratin (USB devices, pcmcia
devices), computer freezes imeditially after reading hibernate file from swap
and after reset with hw configuration I had when hibernating,
On Tue, Apr 05, 2005 at 10:45:30PM +0200, Kay Sievers wrote:
> On Tue, 2005-04-05 at 15:38 -0400, Jan Harkes wrote:
> > Here is another stab at making the keyspan firmware easily loadable with
> > hotplug. Differences from the previous version,
> >
> > - keep the IHEX parser into a separate
Dmitry Torokhov wrote:
> On Apr 5, 2005 4:01 PM, Jaco Kroon <[EMAIL PROTECTED]> wrote:
>
>>btw Dmitri, that patch does not seem to work. But the kernel panic that
>>kicks in when X starts up does imply that _something_ changed. No sync
>>however, so no stack trace in the logs either. In fact,
Jeff Garzik wrote:
Brian Gerst wrote:
Jeff Garzik wrote:
Josselin Mouette wrote:
Finally, you shouldn't forget that, technically speaking, using hotplug
for uploading the firmware is much more flexible and elegant than
including it in the kernel. Upgrading the firmware and the module
should
be
On Apr 5, 2005 4:01 PM, Jaco Kroon <[EMAIL PROTECTED]> wrote:
>
> btw Dmitri, that patch does not seem to work. But the kernel panic that
> kicks in when X starts up does imply that _something_ changed. No sync
> however, so no stack trace in the logs either. In fact, looking at the
> dmesg
This patch changes some of the default behavior in the ppc64 Kconfig
file that was recently changed/added to 2.6.12-rc2-mm1 by Dave Hansen
in preparation for SPARSEMEM. Patch allows the display of both FLAT
and DISCONTIG models on pseries. As before, default is DISCONTIG for
SMP and PSERIES and
Hi,
I don't think anyone has the actual hardware, without which it's quite
difficult to fix the problem.
What was the last 2.6 kernel version that this worked with?
I guess I made a jump from 2.4.26 directly to 2.6.9 or maybe even
higher, but I can't remember if I used the scanner since then,
Hi!
> I'm working o
???
> > > [4294672.065000] ACPI: CPU0 (power states: C1[C1]
> > C2[C2] C3[C3])
> > > [4294676.827000] ACPI: (supports S0 S3 S4 S5)
> >
> >
> > ...aha, but your system does not support S1 aka
> > standby.
> >
>
> Right, so nothing should happen if I try to do it, but
>
Greg KH wrote:
On Tue, 2005-04-05 at 13:27 -0700, David Mosberger wrote:
On Tue, 5 Apr 2005 09:46:48 -0700, Greg KH <[EMAIL PROTECTED]> said:
Greg> -stable review patch. If anyone has any objections, please
Greg> let us know.
Nitpick: the patch introduces trailing whitespace.
Sorry about that,
Ross Biro wrote:
Currently Linux 2.6 assumes the BIOS (or firmware) sets the master abort
mode flag on PCI bridge chips in a coherent fashion. This is not always
the case and the consequences of getting this flag incorrect can cause
hardware to fail or silent data corruption. This patch lets
Hi All,
just for completeness, I've updated the hotfix tree to hf7. The
changelog is ridiculously small (2 patches: 1 doc, 1 minor). The
2.4.29-hf tree is now up to date with 2.4.30. I will start the
2.4.30-hf soon (when 2.4.31-pre emerges), and will keep updating
2.4.29-hf as long as possible.
On Tue, Apr 05, 2005 at 10:42:25AM -0700, Sridhar Samudrala wrote:
> On Mon, 4 Apr 2005, Sam Ravnborg wrote:
>
> >
> >Only bit that I am worried about is the statement in SCTP:
> > depends on IPV6 || IPV6=n
> >
> >That looked like a noop to me. It had the sideeffect that SCTP
> >menu entries
On Tue, 5 Apr 2005, Ingo Molnar wrote:
>
> esi: 009b63f9 edi: 0001 ebp: f543a000 esp: f543bfc8
>
> i.e. esp & 0xfff was 0xfc8 - while i think it should normally be 0xfc4
> (page boundary minus size of pt_regs == 0 - 0x3c == 0xfc4). So somewhere
> we lost 4 bytes of esp? An extra
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> > > So I'd actually prefer to get that mystery explained..
> > IIRC if the interrupt doesn't do the CPL
> > switch, the interrupt gate doesn't save
> > the stack, and so there may not be the
> > full "struct pt_regs" when the kernel
> > thread is
Dmitry Torokhov wrote:
> On Apr 5, 2005 1:20 PM, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>>Jaco Kroon wrote:
>>>Dmitry Torokhov wrote:
You should be able to control that in xorg.conf.
>>>
>>>My thoughts exactly. The same goes for gpm.
>>
>>No. AFAIK multifinger taps are handled by the
On Die, 05 Apr 2005, Pavel Machek wrote:
> I do not know why you can't unload them, but what about simply not
> loading them at all? :-).
hotplug.
Whatever, booting with init=/bin/sh I get these processes running
PID TTY STAT TIME COMMAND
1 ?R 0:00 /bin/bash
2 ?
I am trying to get any kernel to boot on dual core Opteron. I have
tried with kernels 2.6.9-2.6.12-rc2 all with virtually the same panic.
Here is the output with 2.6.12-rc2:
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 console=ttyS0)
Linux version 2.6.12-rc2andro ([EMAIL
The compat layer on sparc64 was not filling in the nanosecond
fields in properly for 32-bit compat tasks. This caused things
like the test-utime.c test to fail in the libc sources.
A problem still remains for native 64-bit binaries. Like Alpha
the normal stat structure doesn't have the
1 - 100 of 812 matches
Mail list logo
