On Wed, Jul 20, 2005 at 05:23:52PM +0200, Antonio Vargas wrote:
> Most probably the cost of programming and debugging the hand-made
> paging on 32bit machines will cost more than the difference for a
> 64bit machine.
I'll second that. There may not even be a price difference.
I've had quotes for
On Thursday 21 July 2005 00:32, Nigel Cunningham wrote:
> (Fixed to remove the latent mention of syncthreads).
>
> This patch implements freezer support for workqueues. The current
> refrigerator implementation makes all workqueues NOFREEZE, regardless of
> whether they need to be or not.
>
I
Hi,
On Thursday 21 July 2005 00:24, Pavel Machek wrote:
>
> +config TOUCHSCREEN_COLLIE
> + tristate "Collie touchscreen (for Sharp SL-5500)"
> + depends on MCP_UCB1200 && INPUT
I don't think you need && INPUT here.
>
> obj-$(CONFIG_TOUCHSCREEN_BITSY) += h3600_ts_input.o
>
(Fixed to remove the latent mention of syncthreads).
This patch implements freezer support for workqueues. The current
refrigerator implementation makes all workqueues NOFREEZE, regardless of
whether they need to be or not.
While this doesn't appear to have caused any problems with swsusp (ie
Hi!
> >>I have rebuilt agpgart and amd64-agp into the kernel and now it has
> >>resumed successfully for the first time. Thank you for the hint!
> >>
> >>But I still wonder, why that makes a difference.
> >
> >
> >Before resume the module is not present. When it gets loaded from the
> >image it
On Fri, Jul 15, 2005 at 01:22:55PM +0200, Jörn Engel wrote:
> On Fri, 15 July 2005 04:06:11 -0700, Andrew Morton wrote:
> > > +
> > > + /* There is no sane reason to use O_DIRECT */
> > > + BUG_ON(file->f_flags & O_DIRECT);
> >
> > err, this seems like an easy way for people to make the kernel go
>Len, ACPI people - can we fix this regression, please?
>
>Rafael even pinpoints exactly which patches are causing the
>problem, so why didn't they get reverted before sending them off to me?
Linus,
I'm sorry it was in '-rc3' -- that is as soon as I could
muster the bk->git transition. Now that
Hi!
> New revision. Anything left to fix up?
It certainly looks better now.
> +static int lzf_compress_init(void *context)
> +{
> + struct lzf_ctx *ctx = (struct lzf_ctx *)context;
> +
> + /* Get LZF ready to go */
> + ctx->hbuf = vmalloc_32((1 << hlog) * sizeof(char *));
> + if
From: John Lenz <[EMAIL PROTECTED]>
This adds low-level suspend/resume support to locomo.c.
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
diff --git a/arch/arm/common/locomo.c b/arch/arm/common/locomo.c
--- a/arch/arm/common/locomo.c
+++ b/arch/arm/common/locomo.c
@@ -541,6 +541,103 @@
Hi!
This adds support for touchscreen of sharp zaurus sl-5500. I got the
patches from John Lenz <[EMAIL PROTECTED]>, but lots of copyrights are
Russell King. To do so, it needs to add quite a bit of
infrastructure. If there's better place for some code, please let me
know (I already moved
This patch implements a new PF_SYNCTHREAD flag, which allows upcoming
the refrigerator implementation to know that a thread is syncing data to
disk. This allows the refrigerator to be more reliable, even under heavy
load, because it can separate userspace processes that are submitting
I/O from
This fixes wrong number of arguments in call to write_scoop_reg, fixes
map_name and John's email. Please apply,
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
diff --git a/arch/arm/mach-sa1100/collie.c b/arch/arm/mach-sa1100/collie.c
--- a/arch/arm/mach-sa1100/collie.c
+++
Hi!
> >[...]
> > Q3 : I'm not sure JBD can be used for FAT improvements. Do you
> >have any comments ?
>
> I might not be the best person to answer this, but this just seems so
> obvious:
>
> If you plan to let a recently hot-unplugged device to be used in another
> OS that doesn't
I'd like to learn some details of how RPC's FSM works (e.g. the
changing graph of all states). I know one possibility is to read the
source code, but it is a little time consuming.
Can someone kindly direct me to some documents about the rpc
implementatino? Thanks in advance!
-x
-
To
This patch implements freezer support for workqueues. The current
refrigerator implementation makes all workqueues NOFREEZE, regardless of
whether they need to be or not.
While this doesn't appear to have caused any problems with swsusp (ie
Pavel's version) to date, this is no guarantee for the
Signed-off-by: Miles Bader <[EMAIL PROTECTED]>
arch/v850/Makefile |7
arch/v850/README | 62 ++-
arch/v850/configs/rte-ma1-cb_defconfig | 605 +
arch/v850/configs/rte-me2-cb_defconfig | 453
Jiri Slaby wrote:
Are these files obsolete and could be deleted from tree.
Does anybody use them? Could anybody compile them?
[snip]
fs/binfmt_flat.c
This is not obsolate, it is used by most MMUless architectures
as the primary executable file loader.
It compiles (and works).
Regards
Greg
Howdy.
New revision. Anything left to fix up?
Regards,
Nigel
Kconfig |7 +
Makefile |1
lzf.c| 377 +++
3 files changed, 385 insertions(+)
diff -ruNp 260-crypto-api-lzf-support.patch-old/crypto/Kconfig
Ingo,
Attached is a patch for 51-28 which brings PPC
up to date for 2.6.12 PREEMPT_RT. My goal was to
get a more recent vintage of this work building and
minimally booting for PPC. Yet this has been stable
even under our internal stress tests. We now have
this running on 8560 and 8260 PPC
Hi.
On the testing twice, fair enough. I'll send a new version with the
refrigerator changes, as jbd won't need that dirty big if..else then
since there's no danger of a deadlock.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the
On Wed, 20 Jul 2005 16:08:35 -0400 (EDT) Mark Whittington wrote:
> Added a sysctl (KERN_PRINTK_TIME) and by proxy an entry in
> /proc/sys/kernel to enable and disable printk interval information when
> CONFIG_PRINTK_TIME is compiled in.
1/ That explains "what." How about "why?"
2/ The
>> My question is, what is the recommended driver to use for the PATA
>>channel?
>
>If you're just using hard drives, there should be no problem using
>libata for both PATA and SATA.
>
>However, in general, the IDE driver (CONFIG_IDE) is recommended for PATA.
>
> Jeff
I took Jeff's
Michael Krufky wrote:
This patch series spans both video4linux and linux-dvb trees.
Remove the dvb_pll_desc from the lgdt3302 frontend and replace with a
pll_set-callback to isolate the tuner programming from the frontend.
Select the RF input connector based upon the type of demodulation
Michael Krufky wrote:
This patch series spans both video4linux and linux-dvb trees.
Remove the dvb_pll_desc from the lgdt3302 frontend and replace with a
pll_set-callback to isolate the tuner programming from the frontend.
Select the RF input connector based upon the type of demodulation
Michael Krufky wrote:
This patch series spans both video4linux and linux-dvb trees.
Remove the dvb_pll_desc from the lgdt3302 frontend and replace with a
pll_set-callback to isolate the tuner programming from the frontend.
Select the RF input connector based upon the type of demodulation
Michael Krufky wrote:
This patch series spans both video4linux and linux-dvb trees.
Remove the dvb_pll_desc from the lgdt3302 frontend and replace with a
pll_set-callback to isolate the tuner programming from the frontend.
Select the RF input connector based upon the type of demodulation
This patch series spans both video4linux and linux-dvb trees.
Remove the dvb_pll_desc from the lgdt3302 frontend and replace with a
pll_set-callback to isolate the tuner programming from the frontend.
Select the RF input connector based upon the type of demodulation selected. ANT
RF
Johannes Stezenbach wrote:
Graeme Christie wrote:
It seems to me as if this bug has resurfaced again.
It probably got lost because it was
applied to the kernel which v4l was maintainer- and CVS-less.
http://groups-beta.google.com/group/linux.kernel/msg/6a27dd3dc46a5b5b?dmode=source=en
It
Hi,
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.
Signed-off-by: Jens Axboe <[EMAIL PROTECTED]>
diff --git a/drivers/md/dm-io.c b/drivers/md/dm-io.c
---
Jiri Slaby wrote:
> Are these files obsolete and could be deleted from tree.
> Does anybody use them? Could anybody compile them?
>
> (...)
> drivers/scsi/NCR5380.c
> drivers/scsi/NCR5380.h
> (...)
The above are used by (at least) the PAS16 SCSI driver. The PAS16 is
a 16-bit ISA soundcard that,
On Wed, July 20, 2005 12:57 pm, Pavel Machek said:
> BTW is there some place where I can find modifications Sharp did to
> mainline 2.4 kernel?
First, sharp's modifications were not to the base 2.4 kernels, but you
first applied the rmk patch and then the pxa patch.
I have tried to split up the
Jesper Juhl <[EMAIL PROTECTED]> wrote:
> On 7/11/05, Michael S. Tsirkin <[EMAIL PROTECTED]> wrote:
> [snip]
> > 3e. sizeof
> > space after the operator
> > sizeof a
> I don't think that's a hard rule, there's plenty of code that does
> "sizeof(type)" and not "sizeof (type)",
Hi.
On Wed, 2005-07-20 at 20:54, Hiroyuki Machida wrote:
> Hi,
>
>
> With this function, system needs to mount read-write file systems on
> every boot cycle, due to avoid inconsistency between FS and memory.
> How did you address this problem? Did kernel check RW FS remained as
> mounted on
Well said, Mark. Thanks.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
The 2.6.13-rc3 version of KDB (Linux Kernel Debugger) supports a USB
keyboard (CONFIG_KDB_USB). At the moment it only supports the OHCI
interface, this is what SGI hardware uses. If anybody has hardware
that uses the UHCI interface for the keyboard and can create a kdb
patch, that patch will be
Rafael J. Wysocki wrote:
On Thursday, 21 of July 2005 00:07, Michal Schmidt wrote:
I also tried putting a printk before restore_processor_state(), but I'm
not sure if it is safe to use printk there.
Yes, it is, but you may be unable to see the message if the box reboots before
it can be
Jan wrote:
> (Find source files, expand tab chars to their on-screen length, print if
> >= 80, count lines)
The bulk of the longest lines are in the sound and drivers subtrees.
One example on the "high end", with 546 chars in one line:
==
drivers/scsi/BusLogic.c:
%2d%5d %5d %5d%5d
Bert wrote:
> the diskstat tools require relayfs
That way might lay the real value of relayfs, as a common
technology basis for specific tools that are developed
and maintained on top of relayfs.
--
I won't rest till it's the best ...
Programmer, Linux
Rolf Eike Beer wrotes:
Send a patch, you know the addresses.
kernel 2.6.13-rc3-git4
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
--- a/MAINTAINERS 2005-07-21 01:13:32.0 +0200
+++ b/MAINTAINERS 2005-07-21 01:17:41.0 +0200
@@ -204,8 +204,6 @@
ADVANSYS SCSI
On Thursday, 21 of July 2005 00:07, Michal Schmidt wrote:
> Rafael J. Wysocki wrote:
> > On Tuesday, 19 of July 2005 23:26, Michal Schmidt wrote:
> >>I have rebuilt agpgart and amd64-agp into the kernel and now it has
> >>resumed successfully for the first time. Thank you for the hint!
> >>
>
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 "Software Memory Hole" option in the BIOS (version 3.02)
remaps
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 copies over an NFS mount.
The client is running Linux (2.6.11), and
If these are reasonable numbers, is there any methods available to improve the
responsiveness of X? I find I can't get smooth drawing, both scrolling text
(in konsole) and dragging windows around, yields "skips" where the drawing
isn't fluid.
Secondly, what are the suggested settings for
Jesper Juhl <[EMAIL PROTECTED]> writes:
> I don't think that's a hard rule, there's plenty of code that does
> "sizeof(type)" and not "sizeof (type)", and whitespace cleanup
> patches I've done that change "sizeof (type)" into "sizeof(type)" have
> generally been accepted.
Sure, the common
Hi list, I have the Wireless IntelliMouse Explorer USB In my linux , and
when I try to configure (mouseconf , USB mouse) the mouse on the X dont work
properly, when I move the mouse , the cursor only go to up and down.
Anyone can help me to make my mouse work good ?
My distro is Slack 10.1
Rafael J. Wysocki wrote:
On Tuesday, 19 of July 2005 23:26, Michal Schmidt wrote:
I have rebuilt agpgart and amd64-agp into the kernel and now it has
resumed successfully for the first time. Thank you for the hint!
But I still wonder, why that makes a difference.
Before resume the module
Hi Greg,
> > Convert i2c-isa from a dumb i2c_adapter into a pseudo i2c-core for
> > ISA hardware monitoring drivers. The isa i2c_adapter is no more
> > registered with i2c-core, drivers have to explicitely connect to it
> > using the new i2c_isa_{add,del}_driver interface.
>
> Ick, when I did
>
> When I'm debugging something requiring detailed tracing, I don't want
> to have to think about whether the tracing tool has the particular
> behaviour, performance, data loss, and other such characteristics
> needed for my immediate needs. It is easier to code up some little
> ad hoc
Steve wrote:
> The reason I would like to see this merged, so kernel hackers don't need
> to constantly write there own logging buffers everytime you need to
> debug a complex area of the kernel.
But I doubt that relayfs, or anything resembling it, will accomplish
this purpose, at least for some
Manfred Spraul wrote:
Autsch.
Yes, you are right. Sorry for that, I should have reread the patch once
more.
No problem :)
I've been running v0.38 since my last mail. No problems at all.
Thanks for your continued work on the driver.
Daniel
-
To unsubscribe from this list: send the line
> > 3c. * in types
> > Leave space between name and * in types.
> > Multiple * dont need additional space between them.
> >
> > struct foo **bar;
> >
> Don't put spaces between `*' and the name when declaring variables,
> even if it's not a double pointer. int * foo;
Hi Greg,
> > +/* Next four are needed by i2c-isa */
> > +EXPORT_SYMBOL(i2c_adapter_dev_release);
> > +EXPORT_SYMBOL(i2c_adapter_driver);
> > +EXPORT_SYMBOL(i2c_adapter_class);
> > +EXPORT_SYMBOL(i2c_bus_type);
>
> EXPORT_SYMBOL_GPL() instead? As these were, core, GPL only symbols
> before you
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Oh, sorry, we're talking about two different patches. I sent in a
> different patch yesterday, because Andi Kleen didn't seem very
> enthusiastic about fixnx2.patch. Here's the patch that I sent
> yesterday (attached as file init.c.patch).
On Mon, 2005-07-18 at 13:42 +0200, Pavel Machek wrote:
> Hi!
> > Any comments or feedback would be greatly appreciated.
> > +#ifdef CONFIG_TIME_INTERPOLATION
> > +void time_interpolator_update(long delta_nsec);
> > +#else
> > +#define time_interpolator_update(x)
>
> do {} while (0) is safer...
On Wednesday, July 20, 2005, 9:44:57 PM, Willy Tarreau wrote:
> Hello,
Hello Willy,
> just some basic questions :
> - did your configuration change before the oopses started ? (eg: new
> matches, etc...)
One new machine appears but it generates small traffic rate (by now
it's almost
Added a sysctl (KERN_PRINTK_TIME) and by proxy an entry in
/proc/sys/kernel to enable and disable printk interval information when
CONFIG_PRINTK_TIME is compiled in.
Signed-off-by: Mark Whittington <[EMAIL PROTECTED]>
diff -ruN linux-2.6.12/Documentation/sysctl/kernel.txt
Hello,
just some basic questions :
- did your configuration change before the oopses started ? (eg: new
matches, etc...)
- did the traffic change recently (protocols, data rate) ? eg: new
applications on the network, etc...
- is it possible that it's being targetted by an attack
David Lewis wrote:
Greetings,
I am developing a system using the Intel SE7520BD2 motherboard. It has an
ICH5 with two SATA ports and one PATA channel. I am able to drive the PATA
channel with either the normal PIIX IDE driver or the libata driver which I
am using for the SATA ports. Ultimately
Hayes, Stuart wrote:
> Ingo Molnar wrote:
>> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>>> Ingo Molnar wrote:
there's one problem with the patch: it breaks things that need the
low 1MB executable (e.g. APM bios32 calls). It would at a minimum
be needed to exclude the BIOS
I just changed kernels from 2.6.11.4 to 2.6.13-rc3 and upon boot I now
see these errors on the console and in the syslog:
localhost kernel: hda: dma_timer_expiry: dma status == 0x21
localhost kernel: hda: DMA timeout error
localhost kernel: hda: dma timeout error: status=0x58 { DriveReady
Linus Torvalds wrote:
"sendfile()" in general I think has been a mistake. It's too specialized,
and the interface has always sucked.
Ok, you're right. I will have a look at the pipe buffer stuff.
As Andrew pointed out, it actually
needs to limit the number of buffers in flight partly
Jan Blunck wrote:
I don't want to tell where these are in general, I need an easy way to
seek to the m'th directory + offset position without reading every
single dirent. With i_sizes != 0 it is straight forward to use "the
sum of the m directory's i_sizes + offset" as the f_pos to seek to.
Jan Blunck wrote:
Also, how is lseek + readdir supposed to work in general?
This is how libc is reading directories (at least on arch s390x):
getdents() != 0
lseek() to d_off of last dirent
getdents() != 0
lseek() to d_off of last dirent
getdents() == 0
return
Therefore I really need
Resending dell_rbu driver after making a few more improvements and also
using the new request_firmware_nowait kernel API sent in the firmware_class.c
patch.
This patch has been tested on i386 and x86-64 systems along with the
firmware_class.c patch and it works fine.
Signed-off-by: Abhay
Reseending the patch for firmware_class.c submitted earlier ,the patch
upgrades the request_firmware_nowait function to not start the hotplug
action on a firmware update.
This patch is tested along with dell_rbu driver on i386 and x86-64 systems.
Andrew, could you please add this patch to the
Chris Wedgwood wrote:
To my understanding, you can lseek to any "proper" offset inside a
directory. Proper means that the offset marks the beginning of a
new dirent (or end of file) in the interpretation of the filesystem.
But you can never tell where these are in general.
I don't want
Hi,
attached patch implements IOAPIC_CACHE on x86_64,
if I haven't forgotten something
Note that in the patch, IOAPIC_POSTFLUSH is initially not set.
Thats different to plain -51-32.
Works fine here on a K8T800 Mobo.
Would be fine, if some guys could give this a try ontop of -51-32.
Thanks,
On Wed, Jul 20, 2005 at 08:09:18PM +0200, Lars Marowsky-Bree wrote:
> On 2005-07-20T09:55:31, "Walker, Bruce J (HP-Labs)" <[EMAIL PROTECTED]> wrote:
>
> > Like Lars, I too was under the wrong impression about this configfs
> > "nodemanager" kernel component. Our discussions in the cluster
> >
Chris Wedgwood wrote:
Hos does that work if offset >= m?
Eerrh, did you actually read my patch? The i_size of a directory is
increased by SIMPLE_BOGO_DIRENT_SIZE for every entry in the directory.
>>So you can seek to m*+ to access an offset into
>>> >something at depth m?
>>> >
>>
>> Yes.
On Wed, Jul 20, 2005 at 12:54:09PM -0500, Nathan Lynch wrote:
> Matt Domsch wrote:
> > On Tue, Jul 19, 2005 at 06:07:41PM -0600, Moore, Eric Dean wrote:
> > > On Tuesday, July 12, 2005 8:17 PM, Matt Domsch wrote:
> > > > In general, this construct:
> > > >
> > > > > > -#if (LINUX_VERSION_CODE <
On Wed, Jul 20, 2005 at 01:21:27PM +0200, J?rn Engel wrote:
> To my understanding, you can lseek to any "proper" offset inside a
> directory. Proper means that the offset marks the beginning of a
> new dirent (or end of file) in the interpretation of the filesystem.
But you can never tell where
On 2005-07-20T09:55:31, "Walker, Bruce J (HP-Labs)" <[EMAIL PROTECTED]> wrote:
> Like Lars, I too was under the wrong impression about this configfs
> "nodemanager" kernel component. Our discussions in the cluster
> meeting Monday and Tuesday were assuming it was a general service that
> other
Hi!
> > > ...and that's well known; but now I did some back tracking, and
> > > 2.6.12-rc1 works, 2.6.12-rc2 does *not* and 2.6.12-rc2 with arm
> > > changes reverted works. I'll play a bit more.
> >
> > This fixes at least one break-the-boot bug in -rc2...
> >
> >
On 7/19/05, Moore, Eric Dean <[EMAIL PROTECTED]> wrote:
> On Tuesday, July 12, 2005 8:17 PM, Matt Domsch wrote:
> > In general, this construct:
> >
> > > > -#if (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,6))
> > > > -static int inline scsi_device_online(struct scsi_device *sdev)
> > > > -{
> > > > -
Matt Domsch wrote:
> On Tue, Jul 19, 2005 at 06:07:41PM -0600, Moore, Eric Dean wrote:
> > On Tuesday, July 12, 2005 8:17 PM, Matt Domsch wrote:
> > > In general, this construct:
> > >
> > > > > -#if (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,6))
> > > > > -static int inline
On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
> Hi,
"You are not allowed to post to this mailing list, and your message has
been automatically rejected. If you think that your messages are
being rejected in error, contact the mailing list owner at
[EMAIL PROTECTED]"
Please don't
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>> 3) If a normal line of code is more than 80 characters, one of the
>> following is probably true: you need to break the line up and use temps
>> for clarity, or your function is so big that you're tabbing over too
>> far.
>
> (Find source files,
On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
> Hi,
> I just released a new version of kernel-desktop. New features are:
> - Realtime LSM module (Useful for jack audio server)
2.6.12 supports RLIMIT_RTPRIO and RLIMIT_NICE so this is no longer
needed.
The distros need to get with
Like Lars, I too was under the wrong impression about this configfs
"nodemanager" kernel component. Our discussions in the cluster meeting Monday
and Tuesday were assuming it was a general service that other kernel components
could/would utilize and possibly also something that could send
On 2005-07-20T11:35:46, David Teigland <[EMAIL PROTECTED]> wrote:
> > Also, eventually we obviously need to have state for the nodes - up/down
> > et cetera. I think the node manager also ought to track this.
> We don't have a need for that information yet; I'm hoping we won't ever
> need it in
On Sun, 2005-07-17 at 20:00 +0200, Roman Zippel wrote:
> On Fri, 15 Jul 2005, john stultz wrote:
>
> > In my attempts to rework the timeofday subsystem, it was suggested I
> > try to avoid mixing cleanups with functional changes. In response to the
> > suggestion I've tried to break out the
On Wed, Jul 20, 2005 at 12:49:00PM +0530, [EMAIL PROTECTED] wrote:
>
> Hi David ,
>
> On my controller CF INPACK pin is connected to 3.3v. so Comapct
> flash with DMA capabilty will not be supported , i understood this .
> but i did not undesrtand why only PIO mode 1 is supported is it ,
> why
On Jul 19, 2005 16:15 +0200, Adrian Bunk wrote:
> This patch contains the following cleanups:
> - make needlessly global functions static
> - journal.c: remove the unused global function __journal_internal_check
> and move the check to journal_init
> - remove the following write-only
I had the following happen last night while running while running Con's
Interbench. Looking back through my log, I do see one other case where
the same BUG triggered from running updatedb (2.6.12-RT-V0.7.51-31), but
it didn't have all of the ext3 errors that followed this one. I really
don't
Mauricio Lin wrote:
Hi Brady,
On 7/20/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The following shell gets the shared values for the
first httpd process:
FIRST_HTTPD=`ps -C httpd -o pid= | head -1 | tr -d ' '`
HTTPD_STATM_SHARED=$(expr 4 '*' `cut -f3 -d' ' /proc/$FIRST_HTTPD/statm`)
On Wed, Jul 20, 2005 at 10:05:13AM -0500, Dmitry Torokhov wrote:
> On 7/20/05, Sergey Vlasov <[EMAIL PROTECTED]> wrote:
> > Another option is to change the
> > PSMOUSE_TRACKPOINT value so that it is less than PSMOUSE_GENPS,
>
> No, protocol numbers should not be changed as userspace
ACPI spec. states that the location of the RSDP structure is found by searching
* The first 1 KB of the Extended BIOS Data Area (EBDA).
* The BIOS read-only memory space between 0Eh and 0Fh
The EBDA scan looks wrong. The patch below against 2.6.12 should correct this.
-Udo.
---
Hi Brady,
On 7/20/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Mauricio Lin wrote:
> > Hi,
> >
> > On 7/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> >>Andrew Morton wrote:
> >>
> >>>OK, please let us know how it goes.
> >>
> >>It went very well. I could find no problems at all.
Hi,
I just released a new version of kernel-desktop. New features are:
- Based on FC4 2.6.12-1.1398_FC4 kernel
- Include 2.6.12.3pre patch
- Include Con Kolivas CK8 patchset (with Staircase11)
Kernel-desktop is based on the standard FC3 kernel, with the folowing
additions:
- NTFS read-only
-
On 7/20/05, Erik Mouw <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 20, 2005 at 01:35:07PM +, Miquel van Smoorenburg wrote:
> > In article <[EMAIL PROTECTED]>,
> > Erik Mouw <[EMAIL PROTECTED]> wrote:
> > >On Wed, Jul 20, 2005 at 02:16:36PM +0200, Bastiaan Naber wrote:
> > >AFAIK you can't use a
>I want to know if this is possible before spending 10,000 euros on a machine
>that has 16 GB of memory.
I can get a Dual Opteron 242 with 16G for less than 10K euro. :)
Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 7/20/05, Sergey Vlasov <[EMAIL PROTECTED]> wrote:
> On Tue, 19 Jul 2005 23:40:18 -0400 Stephen Evanchik wrote:
>
> > I have been receiving a lot of complaints that TrackPoints on
> > Synaptics pass-thru ports stopped working with 2.6.12. I retested
> > 2.6.9 and 2.6.11-rc3 successfully, I
Ingo Molnar wrote:
> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>> Ingo Molnar wrote:
>>> there's one problem with the patch: it breaks things that need the
>>> low 1MB executable (e.g. APM bios32 calls). It would at a minimum be
>>> needed to exclude the BIOS area in 0xd-0xf.
>>>
Alexander Nyberg wrote:
spin_lock_irqsave is only needed when a lock is taken both in normal
context and in interrupt context. Clearly this lock is not intended to
be taken in interrupt context.
According to Rusty's unreliable guide
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> > there's one problem with the patch: it breaks things that need the
> > low 1MB executable (e.g. APM bios32 calls). It would at a minimum be
> > needed to exclude the BIOS area in 0xd-0xf.
> >
> > Ingo
>
> I
Hello,
I have bridge firewall (linux box) with three fast ethernet cards (one
rtl8139 for management and two e100 for bridge). It is running 2.4.31
kernel and iptables v1.2.11. It works ok about one month. Few weeks
ago It started ooopsing. First thought was hardware, but it was
replaced with a
On Tuesday 19 Jul 2005 17:47, Karim Yaghmour wrote:
> I have a usb-attached HD that I use from time to time. When it's connected
> to my desktop through a hub it works flawlessly. When connected to my Dell
> D600 Laptop, however, it sometimes randomly exhibits a loud click (as if
> the heads went
rbt wrote:
> I have a script that automatically builds kernels for testing. Would it
> be possible to put the kernel version number (2.6.12.3) into the
> 'LATEST-IS-VERSION' file on http://www.kernel.org/pub/linux/kernel/v2.6/
> or, is there some other file that traditionally has stored this info?
Ingo Molnar wrote:
> there's one problem with the patch: it breaks things that need the
> low 1MB executable (e.g. APM bios32 calls). It would at a minimum be
> needed to exclude the BIOS area in 0xd-0xf.
>
> Ingo
I wrote it to make everything below 1MB executable, if it isn't
On Tue, 19 Jul 2005 23:40:18 -0400 Stephen Evanchik wrote:
> I have been receiving a lot of complaints that TrackPoints on
> Synaptics pass-thru ports stopped working with 2.6.12. I retested
> 2.6.9 and 2.6.11-rc3 successfully, I believe 2.6.11.7 may also work
> but that is unconfirmed at this
1 - 100 of 334 matches
Mail list logo
