All,
TASK_UNMAPPED_SIZE is defined in include/asm-i386/processor.h as:
#define TASK_UNMAPPED_SIZE(TASK_SIZE / 3)
The value of TASK_SIZE is defined as PAGE_OFFSET which is set to 0xC000
(page.h). This works out to be a value of 0x400.
The question is:
Are there any negative side ef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've recently changed kernel versions, from 2.2.17 to 2.4.0-test10. Since
then, I have 'grainy' sound while playing mp3's as a user (a bit like an
old record). This does not happen when I play the mp3's as root. I didn't
have this problem in 2.2.
Hello!
> It is not safe, just not worse than 2.2.
Andi.. 8)
That issue, which was meant here, it is 100% safe.
I start to suspect you did not look into this code since 2.2.
I acn assume that nothing has changed in ISDN,
in other drivers big changes happened. 8)
Alexey
-
To unsubscribe fro
http://resourcemanagement.unixsolutions.hp.com/WaRM/schedpolicy.html
come and see the updates for November to plugin scheduler policies for Linux:
- support for Linux 2_4 test 9
- support for IA64 kernels
- a performance enhancement related to sched yield correctness
- utilities fix
I would like to get the IP address of one of the interfaces of the
machine that I'm currently on from within some C++ code. It looks like
I should be able to do this by doing an
ioctl(atoi(fd, SIOCGIFADDR, &ifr)
with the interface name set in the appropriate field in ifr, but I'm not
sure how I
> 10. To Do But Non Showstopper
>
> * Loop device can still hang (William Stearns has script that will
>hang 2.4.0-test7, Peter Enderborg has a short sequence that will
>hang 2.4.0test9)
I think I have the same problem with 2.4.0-test10 (with rieserfs-patch).
With small imag
On Fri, Nov 03 2000, Mike Galbraith wrote:
> > I very much agree. Kflushd is still hungry for free write
> > bandwidth here.
>
> In the LKML tradition of code talks and silly opinions walk...
>
> Attached is a diagnostic patch which gets kflushd under control,
> and takes make -j30 bzImage buil
> > How recent of a test kernel. Yes their was a problem with the console
> > palette but it is now fixed in the most recent test kernels.
>
> 2.4.0-test10-pre5
Please upgrade to a newer kernel. This problem has been fixed :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-k
Rob Landley <[EMAIL PROTECTED]> writes:
> 3) Java sucks in many ways. Today's way is that it
> never occurred to Sun that a machine might have more
> than one IP address assigned to it, so
> InetAddress.getLocalHost() returns exactly one
> address. Unfortunately, just about EVERY machine has
>
> * VGA Console can cause SMP deadlock when doing printk {CRITICAL}
>(Keith Owens)
Still not fixed :-( Here is the patch again. Keith give it a try and tell
me if it solves your problems.
--- vgacon.c.orig Tue Oct 24 18:45:58 2000
+++ vgacon.cTue Oct 24 19:08:51 2000
@@ -
On Fri, Nov 03 2000, David Mansfield wrote:
> Hi Jens.
>
> I've tried your blk-8 patch and it oopses during boot. I only hand
> copied the stack trace, and ran it through ksymoops:
>
> Call Trace: [] [] [] []
> [] [] []
> [] [] [] [] []
> []
> Warning (Oops_read): Code line not seen, du
ooops...
--- Forwarded Message
<[EMAIL PROTECTED]>: host vger.rutgers.edu[128.6.14.121] said: 550
<[EMAIL PROTECTED]>... User unknown
Date: Fri, 3 Nov 2000 09:54:19 -0800 (PST)
From: Grant Grundler <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: PATC
I've been receiving these error messages during times of near complete
memory depletion. This particular machine runs a bare minimum of
processes and a our own application which is a threaded long running (1
day, 5:39) which consumes most of the resources on the machine. Oddly
enough however, the
On Mon, Oct 30 2000, Miles Lane wrote:
> I just reproduced the problem in test10-pre7. Here's the
> output you requested:
Thanks
> vmstat 1
> procs memoryswap io system cpu
> r b w swpd free buff cache si sobibo incs
--- Philippe Troin <[EMAIL PROTECTED]> wrote:
> Rob Landley <[EMAIL PROTECTED]> writes:
> > So the question is, is the stack's behavior right?
> If
> > not, what's involved in fixing it, and if so, is
> it
> > documented anywhere?
>
> I think historically, BSD stacks were routing
> 255.255.255.2
On Fri, Nov 03, 2000 at 03:38:56PM +, Alan Cox wrote:
> [..] while thats very
> sensible [..]
Not that it matters much but jfs means "journalling filesystem" and fs/jfs
isn't a filesystem in the ext3 patch, so it doesn't look that sensible to me.
Andrea
-
To unsubscribe from this list: send
Michael Boman writes:
> It seems like both IBM's JFS and ext3 wants to use fs/jfs .. IMHO that
> is like asking for problem.. A more logic location for ext3 should be
> fs/ext3, no?
Actually, if you would look in linux/fs, you will see that ext3 IS in
linux/fs/ext3. However, there is a second co
> > * Spin doing ioctls on a down netdeice as it unloads == BOOM
> >(prumpf, Alan Cox) Possible other net driver SMP issues (andi
> >kleen)
>
> Turns out to be safe according to Jeff and ANK
It is not safe, just not worse than 2.2.
-Andi
-
To unsubscribe from this list: sen
Running mke2fs on a raid5 which is still syncing causes a *variety* of
filesystem corruption errors:
(sample errs)
-
- ...kernel: EXT2-fs error (device md(9,0)): ext2_check_descriptors:
Block bitmap for group 4 not in group (block 0)!
- e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/0
Hi,
I tried the linux-2.4.0-test9-resiserfs-3.6.18-patch on both 2.4.0-test9
and test2.4.0-test10
and got the following PANIC I originally saw this PANIC when doing a 'cp
-a / /reiserfs'.
I narrowed it done to a simple symlink
Andy
[root@client19 /reiserfs]# ln -s foo.tar foo
Unable to ha
Hi Jens.
I've tried your blk-8 patch and it oopses during boot. I only hand
copied the stack trace, and ran it through ksymoops:
Call Trace: [] [] [] []
[] [] []
[] [] [] [] []
[]
Warning (Oops_read): Code line not seen, dumping what data is available
Trace; c01310e0 <__wait_on_buffer+
While auditing the PIII-4 patch for 2.2.x I found a local security problem in
SETFPXREGS that affects 2.4.0-test10 too when it's compiled for PIII
processors and run on a PIII CPU. The problem is that any user can break the
FPU by uploading into the kernel a not valid mxcsr value.
I verified with
Hi, Peter
> [Vladislav Malyshkin <[EMAIL PROTECTED]>]
> > Also, the function remove_duplicates can be written using make rules
> > and functions. Using functions "foreach" "if" from make and
> > comparison you can easily build a function remove_duplicates in make,
> > no shell involved.
>
> Coul
On Fri, 3 Nov 2000, bert hubert wrote:
>> Thanks! That patch did the trick - our machine is now running lovely.
>
>Your very rare problem was solved in 3 hours and 50 minutes. Most commercial
>support shops try and fail to deliver 4 hour response times - this makes me
>feel warm inside :-)
To be
>
> 3. Security
>
> * Fix module remove race bug (still to be done: TTY, ldisc, I2C,
>video_device - Al Viro) (Rogier Wolff will handle ATM)
TBD: sysctl, kernel_thread
* drivers/input/mousedev.c dereferences userspace pointers directly. We
should make this fail for a bit to catch
On Fri, 3 Nov 2000, Tigran Aivazian wrote:
> Hi Hans,
>
> Simply starting the validation phase of SPEC SFS with NFS mounted reiserfs
> filesystem panics as shown in the log below. A quick look at the source
> suggests that _get_block_create_0() (and therefore, more generally,
> reiserfs_get_bloc
Hi Hans,
Simply starting the validation phase of SPEC SFS with NFS mounted reiserfs
filesystem panics as shown in the log below. A quick look at the source
suggests that _get_block_create_0() (and therefore, more generally,
reiserfs_get_block()) was passed a buffer head bh_result with ->b_data =
> * Palmax PD1100 hangs during boot since 2.4.0-test9 (Alan Cox)
Fixed in pre10.
> * AIC7xxx doesnt work non PCI ? (Doug says OK, new version due
>anyway)
This is now in Justin Gibbs hand but will take time to move on. Doug confirmed
his current code is now merged too.
>
Anyone interested in advanced debuging features:
I've reved the SysRQ Registration Patch, available at:
http://bama.ua.edu/~dunna001/sysrq-register/
The latest is 0.10, and applies to 2.2.18-pre9, 2.4.0-test10-pre6,
and 2.4.0-test10-pre7. I got tired of reving the patch accross
6 versions, so I
On Fri, 3 Nov 2000, Mike Galbraith wrote:
> On Thu, 2 Nov 2000, Jens Axboe wrote:
>
> > On Thu, Nov 02 2000, Val Henson wrote:
> > > > > 3) combine this with the elevator starvation stuff (ask Jens
> > > > >Axboe for blk-7 to alleviate this issue) and you have a
> > > > >scenario where p
> It seems like both IBM's JFS and ext3 wants to use fs/jfs .. IMHO that
> is like asking for problem.. A more logic location for ext3 should be
> fs/ext3, no?
fs/jfs is the general purpose journalling layer. Of course while thats very
sensible it does clash with the ibm jfs. Maybe fs/journalling
On Wed, Nov 01, 2000 at 10:03:27PM +0100, Yann Dirson wrote:
> On Wed, Nov 01, 2000 at 02:59:01PM -0200, Rik van Riel wrote:
> > it appears there has been amazingly little research on this
> > subject and it's completely unknown which approach will work
> > "best" ... or even, what kind of behavio
Travel and other things have kept me more than a little busy lately, so
I fell a bit behind during the test10-pre* series, and didn't have a
chance to issue new updates of the 2.4 TODO list as often as I would
like. I've caught up on my backlog, however, and this is as up to date
as I can make i
Linux job accounting will be demo'd at the SGI booth
next week at SuperComputing 2000 in Dallas. I think
the SGI and LANL lawyers are down to the last legal issue
to be resolved, and then the source will be available at
http://oss.sgi.com/projects/csa.
We've got some testing to compl
-Original Message-
From: Christoph Rohland [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 03, 2000 7:54 AM
To: Rik van Riel
Cc: Jonathan George; '[EMAIL PROTECTED]';
'[EMAIL PROTECTED]'
Subject: Re: 2.4.0-test10 Sluggish After Load
Hi Rik,
>On Wed, 1 Nov 2000, Rik van Riel wrote:
>>
Hi Gurus,
I was trying to build a super-big kernel with allot of Journaling File
System inside it to try out what is best for us to use. Now, I
encountered a problem..
It seems like both IBM's JFS and ext3 wants to use fs/jfs .. IMHO that
is like asking for problem.. A more logic location for ex
(forgot to CC: this to the list when i replied to Jens, and decided to add
another paragraph)
I just tried my Seagate drive, and i can read my tapes in it. If i swap
over to the HP, i can't read the tapes. I'll look today, whether the
Seagate replies with a bunch of those I/O Errors. It's not
Hello,
Having tried the 2.4.0-test9 patch of reiserfs under 2.4.0-test10 I got
the following panic (see kdb session below). I was running bonnie on it
over NFS and at the same time running tar xIf linux-2.4.0-test10.tar.bz2
locally.
Regards,
Tigran
root@hilbert:~# reiserfs: checking transaction
Alan Cox wrote:
>
> > + lea cpuid_fail_msg, %si
> > + callprtstr
> > +1: jmp 1b
> > +cpuid_fail_msg:
> > + .string "Required CPU features are not present - compile kernel for the
>proper CPU type."
> > +cpuid_pass:
>
> Only one very minor suggestion
>
> 1: hlt
>
Relax everyone. Andre has not gone insane from coding (or is he even
sane to begin with?). He knows the site is a joke.
Like he said earlier. He just wanted a reason to say "That Dirty Son of
a Bitch, Bill Gates!!!"
"Richard B. Johnson" wrote:
>
> On Thu, 2 Nov 2000, Andre Hedrick wrote:
> It's
On Thu, 2 Nov 2000, Andre Hedrick wrote:
It's a joke, man. read it!
Cheers,
Dick Johnson
Penguin : Linux version 2.2.17 on an i686 machine (801.18 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtai
> > want 2.4test or 2.2.18pre18 + ide patch
> how?
> which driver?
2.2.18pre19 or 2.4.0test10 + the codec init patch
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Fri, 3 Nov 2000, Paul Marquis wrote:
> It shows that even though select() says a file descriptor is not
> writable, a write() can still succeed. This code is not used anywhere
> in the real world, or at least my real world :-P. It just demonstrates
> "the bug".
>
It demonstrates nothing ex
Hi Rik,
On Wed, 1 Nov 2000, Rik van Riel wrote:
> The 2.4 VM is basically pretty good when you're not
> thrashing and has efficient management of the VM until
> your working set reaches the size of physical memory.
>
> But once you hit the thrashing point, the VM falls
> flat on its face. This i
> + lea cpuid_fail_msg, %si
> + callprtstr
> +1: jmp 1b
> +cpuid_fail_msg:
> + .string "Required CPU features are not present - compile kernel for the proper
>CPU type."
> +cpuid_pass:
Only one very minor suggestion
1: hlt
j 1b
Q: are any of the thi
Hi all,
new check_region() removal patchset (for 2.4.0-test10) is here :)
Best regards,
Andrey
--
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
diff -urN /mnt/disk/linux/drivers/net/ac3
Vitali Lieder wrote:
>
> Hallo.
>
> Ich have test new NVdriver 0.95 with new kernel 2.4.0test10, but
> have the output:
> ***unresolved symbols in /lib/modules/2.4.0-test10/video/NVdriver
Just add the following lines somewhere on top of nv.c and recompile
the nvidia module.
#define mem_map_inc
I'm in the process of updating the 2.4 bug list for test10, and as near
as I can tell, there was a lot of discussion about two different ways of
fixing this bug:
> 9. To Do
> * mm->rss is modified in some places without holding the
> page_table_lock (sct)
To wit, either making mm->rss
In article <[EMAIL PROTECTED]> you write:
> There are two immediate reasons I can come up with for this:
I do not quite follow you on these two reasons. I daily work on an
Alpha machine, which runs under Linux, and I use the Compaq C compiler
since it gives better code on the applications I am de
Tim Riker wrote:
>
> ok, a very valid point. The "C++ kernel code" reference is very telling.
> (ouch). ;-)
>
> Obviously the changes to support non-gcc compilers should have the goal
> of minimal impact on gcc users lives. I recognize that the mainstream
> will still use gcc.
>
> Q: Why should
Dunlap, Randy writes:
> David is entitled to his opinion (IMO).
> And I dislike this patch, as he and I have already discussed.
>
> Short of fixing the link order, I like Jeff's suggestion
> better (if it actually works, that is): go back to the
> way it was a few months ago by calling usb_init(
> eth0: Invalid EEPROM checksum 0x8107, check settings before activating
> this device.
all Cobalt's RAQ are this errors.
Octave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml
I have this problem also. I am running vesafb and X4.01 w/ a voodoo3500.
Switching to a vc sometimes gives you black text (hiliting w/ mouse fixes it) and
alternating green and red pixels across the top of the screen.
-b
[EMAIL PROTECTED] wrote:
> On Thu, Nov 02, 2000 at 07:38:56PM +0100, Rag
Hallo.
Ich have test new NVdriver 0.95 with new kernel 2.4.0test10, but
have the output:
***unresolved symbols in /lib/modules/2.4.0-test10/video/NVdriver
I know that NVdriver are not for dev.kernel, but they worked perfektly
with 2.4.0-test9.
Thanks.
T..
-
To unsubscribe from this lis
On Fri, Nov 03, 2000 at 10:30:54AM +0100, [EMAIL PROTECTED] wrote:
%
%
% Hello,
%
% I've found an unfortunate bug in the "linux/timex.h" file. This file
% include "sys/time.h" and this cause any program that use the adjtimex
% syscall to be unable to compile (You get a lot of multiple defini
On Thu, 2 Nov 2000, James Simmons wrote:
> > Console colors are completely messed up (read: black, I even suspect
> > the font to be corrupt somehow) if switching back to console mode
> > from X (either by quitting or ctrl-alt-fX) in recent 2.4.0-textXX
> > kernels. 2.2.XX do work just fine. Is t
Hello,
I've found an unfortunate bug in the "linux/timex.h" file. This file include
"sys/time.h" and this cause any program that use the adjtimex syscall to be unable to
compile (You get a lot of multiple definition error message). The only work-around,
I've
made is to comment the "#include
g'day all,
I am having problems with my Intel Ether Express Pro 100 card.
I keep getting this message :
eth0: Invalid EEPROM checksum 0x8107, check settings before activating
this device.
What does this mean?
Can I do anything to solve this problem ?
Or has the card gone bad ?
Mof.
-
To unsub
After I generated the patch, I noticed some stuff I didn't want to release, so
I edited the patch by hand, and of course, messed it up.
So, the new patch is available at http://sourceforge.net/project/filelist.php?g
roup_id=429 as usual.
Jeff
-
To unsubscribe f
101 - 159 of 159 matches
Mail list logo
