David S. Miller wrote:
> Could you send me a patch which fixes the problem in this way?
Sure. Here is the one. The occurrence of the IP_XXX corresponds the
one in switch/case.
Thank you for your time,
--- linux-2.4.0-test8-pre6/net/ipv4/ip_sockglue.c Fri Aug 11 05:01:26 2000
+++
Hello.
My kernel panicked at /net/core/skbuff.c (line: 93 "BUG();")
That was the first time when I booted into it.
The second time, it was fine till about 2 hours, while I was writing *this* mail.
Rebooted all of
a sudden (no idea as to where the problem was. It was _quick_. No messages,
From: NIIBE Yutaka <[EMAIL PROTECTED]>
Date: Sat, 09 Sep 2000 12:18:28 +0900
I'd like to explain my point clearly. My point is that accessing
with get_user as int is questionable. In my case, it's string. I
don't think all the string argment to the kernel should be aligned.
Ragnar Hojland Esp writes:
> On Fri, Sep 08, 2000 at 11:10:13PM +0200, Kurt Garloff wrote:
> > Stop making stupid statements like this, please, and comparing well-d=
> efined
> > RFC standards with proprietary formats.=20
> > MIME is a way for people that happen to use non 7bit characters to be=
On Fri, 8 Sep 2000, Adam wrote:
> Hmm can someone remind me what (if) is the reason root is not bound by
> write permissions?
Because linux is not a trusted operating system. On linux,
root = uid 0 = superuser.
> [root@pepsi /tmp]# su adam
> [adam@pepsi /tmp]$ touch blah
> [adam@pepsi
On Fri, Sep 08, 2000 at 11:10:13PM +0200, Kurt Garloff wrote:
> Stop making stupid statements like this, please, and comparing well-defined
> RFC standards with proprietary formats.
> MIME is a way for people that happen to use non 7bit characters to be able
> to print their name correctly, even
Hi David,
I'd like to explain my point clearly. My point is that accessing with
get_user as int is questionable. In my case, it's string. I don't
think all the string argment to the kernel should be aligned.
David S. Miller wrote:
> Why not make sure in the user tools that the argument is
For SH-4 (with virtually indexed, physically tagged cache), we have
problems with swap.
I think that there're bugs in do_swap_page and try_to_swap_out.
I've read "Documentation/cachetlb.txt" and I know that now is
the transition to newer interface, but we need a fix at the moment
with old
From: NIIBE Yutaka <[EMAIL PROTECTED]>
Date:Sat, 09 Sep 2000 11:25:28 +0900
Here's a patch, avoiding useless access.
This seems like a large ugly hack.
Why not make sure in the user tools that the argument is properly
aligned to 4 bytes?
IP-chains works fine on Alpha and
With ipchains, we have alignment problem. H. Kambara
<[EMAIL PROTECTED]> found that it core dumps on SuperH machine.
The cause of this problem is get_user accesses wrongly in
ip_setsockopt.
Here's a patch, avoiding useless access.
diff -ruN linux-2.4.0-test8-pre6/net/ipv4/ip_sockglue.c
Hi everybody,
my name is Andreas Eibach and it's the first time I'm here.
I'm aware of the fact that posting here requires having read ALL FAQs and
available documents before doing that.
I did this, of course.
But since the problem seems brand-new (due to the fact that these huge-sized
HDs are
On Wed, 6 Sep 2000, Linus Torvalds wrote:
> Apparently, if you follow the arguments, not having a kernel debugger
> leads to various maladies:
> - you crash when something goes wrong, and you fsck and it takes forever
>and you get frustrated.
> - people have given up on Linux kernel
On Fri, 8 Sep 2000, Russell King wrote:
> Jamie Lokier writes:
> > With laptops, people are willing
> > to assume the RAM is reliable -- accidentally pulling the plug out won't
> > lose the data.
>
> But a buggy apm implementation and the battery running down can.
>
> (and I've seen my
On Fri, 8 Sep 2000, Linus Torvalds wrote:
>
>
> On Sat, 9 Sep 2000, David Weinehall wrote:
> >
> > This patches changes the names of the init-functions for the
> > hamradio-drivers pt.c and pi2.c. None of the new names are used anywhere
> > else in the kernel.
>
> Patch applied, but I also
> Try attached patch, I hadn't noticed the segment counts were wrong
> because I have implicit recounting.
Yes, this patch fixes the problem, thanks. Once I aplied I could mount the
cd and write a file to it, so it seems to work.
Three semi-related comments.
The udf from cvs tree has
On Sat, 9 Sep 2000, David Weinehall wrote:
>
> This patches changes the names of the init-functions for the
> hamradio-drivers pt.c and pi2.c. None of the new names are used anywhere
> else in the kernel.
Patch applied, but I also wonder why these things are global names anyway?
Why not just
This patch fixes a init-function name-clash between some code in paride
and net/hamradio. Apparently, _noone_ uses these simultaneous, as this
bug has existed since the times of v2.0.xx at least...
This patches changes the names of the init-functions for the
hamradio-drivers pt.c and pi2.c. None
Em Fri, Sep 08, 2000 at 08:33:45PM +0200, Torben Mathiasen escreveu:
> On Fri, Sep 08 2000, Arnaldo Carvalho de Melo wrote:
> > Hi,
> >
> > Please take a look and consider applying. Some of it are small cleanups, if
> > they're deemed unnecessary, lemme now and I'm back it off. I think that
On Fri, Sep 08 2000, [EMAIL PROTECTED] wrote:
> Incorrect number of segments after building list
> nr_segments is 3
> counted segments is 20
> Flags 0 0
> Segment 0xc59cf920, blocks 4, addr 0x59177ff
[snip]
Try attached patch, I hadn't noticed the segment counts were wrong
because I have
Hi all,
I got this error when I tried to 'make bzImage' or 'make install' ...etc
the error is attached with this message and the makefile also attached
thankx for your help
Yours,
Ibrahim El-Shafei
_/\_/\_
/ 0 ! O \
0| <___> |0
\___/
Makefile
gcc -D__KERNEL__
it is no go for me. it panics kernel for me when I try to mount it. Panic
below. (note this panic actually does not finish, it just print this msg
but after this system is still running, but trying to unmount anything,
sync or shutdown will just hang..)
Linux version 2.4.0-test7-packet
On Sat, Sep 09, 2000 at 12:32:27AM +0200, Jamie Lokier wrote:
> You're right, but what you're missing is that with "noflushd", it was
> possible to keep the disk spun down _even with pending writes_.
You may tweak /proc/sys/vm/bdflush
to have it collect data for a long time before it is written
Jamie Lokier writes:
> Russell King wrote:
> > > With laptops, people are willing
> > > to assume the RAM is reliable -- accidentally pulling the plug out won't
> > > lose the data.
> >
> > But a buggy apm implementation and the battery running down can.
>
> Well, perhaps the risk is worth it.
> >Oops from 2.2.17 (some more before this, but it went offscreen):
...
> You need to capture and decode the first oops. Compile a kernel with a
> serial console and capture the oops log on a second machine.
Or set your console for more than 80x25 using SVGATextMode. I use
Linus Torvalds wrote:
> It's about the fact that when I chose the GPL, I did it because I wanted
> the source-code to be free and unencumbered. Forever. Whether I maintained
> that code or not. I didn't want my code to have any extra rules and
> regulations - the GPLv2 is already quite complex
On Fri, 8 Sep 2000, Leonard N. Zubkoff wrote:
>I'm testing the modified driver out in the released 2.2.17 and getting the
>following messages while running mke2fs. Is this a known problem with 2.2.17,
>or something introduced by the change in waiting behavior?
It's known VM problem (unrelated
Date:Fri, 8 Sep 2000 20:33:45 +0200
From: Torben Mathiasen <[EMAIL PROTECTED]>
How about converting the cli() code to spin_locks while we are at
it?
There are many protocols which are of this nature, I did appletalk
spinlocking for example. I didn't even finish cleaning
On Sat, 9 Sep 2000, Jamie Lokier wrote:
>
> > I think an appropriate concern. The future GPL is constrained by the GPLv2
> > clause 9 to be 'similar in spirit...'. You also dont ever have to take any
> > code that specifies GPLv3 or later.
>
> Linus, nobody can ever force GPLv3 upon you. If
Russell King wrote:
> > With laptops, people are willing
> > to assume the RAM is reliable -- accidentally pulling the plug out won't
> > lose the data.
>
> But a buggy apm implementation and the battery running down can.
Well, perhaps the risk is worth it.
-- Jamie
-
To unsubscribe from this
Hey David -
Since at least two of us agree that having dynamically allocated syscall
table entries would be handy, perhaps that is worth pursuing. I suppose
the one issue (as you mention below) is that you might need a large
number of these free entries. Does anyone know if there would be
Jamie Lokier writes:
> With laptops, people are willing
> to assume the RAM is reliable -- accidentally pulling the plug out won't
> lose the data.
But a buggy apm implementation and the battery running down can.
(and I've seen my Thinkpad 380XD with RH's 2.2.14-5.0 kernel and
RH's apmd run
Russell King wrote:
> > *a silent hard disk hard disk is no longer feasible since kernel
> > 2.2.11*.
>
> Yes it is. I have one of my machines (which NFS serves a NFS root
> client, both of which are on 24 hours a day) capable of spinning
> down for up to 4 hours at a time, with no kernel
Date: Thu, 7 Sep 2000 18:33:36 +0200 (CEST)
From: Andrea Arcangeli <[EMAIL PROTECTED]>
Andrea,
I'm testing the modified driver out in the released 2.2.17 and getting the
following messages while running mke2fs. Is this a known problem with 2.2.17,
or something introduced by the change in
On Fri, 08 Sep 2000 23:09:14 +0200,
Kenneth Johansson <[EMAIL PROTECTED]> wrote:
>I have now put "-k /boot/System.map-$(uname -r)" as argument to klogd
>so it can't possibly choose the wrong file but is there some
>reason to turn off the lookup in klogd and use ksymoops ??
klogd only handles
> And here's another sample output for you:
>
> CPU 1: Machine Check Exception: 0004<0>Bank 0: f20001000800general
>protection fault:
> CPU:1
> EIP:0010:[mcheck_fault+263/368]
> EFLAGS: 00010246
> ...
>
> I seldom get a log entry, most of the time I get the first
And here's another sample output for you:
CPU 1: Machine Check Exception: 0004<0>Bank 0: f20001000800general
protection fault:
CPU:1
EIP:0010:[mcheck_fault+263/368]
EFLAGS: 00010246
...
I seldom get a log entry, most of the time I get the first line on all my
On Fri, 8 Sep 2000 14:48:51 +0200,
Rasmus Andersen <[EMAIL PROTECTED]> wrote:
>I just got hold of an old machine (P75, 32MB RAM). On trying to install
>RH 6.2 on it, I got an oops after loading the kernel from the boot floppy.
>I then tried to boot a 2.4.0-test8-pre6 (made with make bzdisk), but
umsdos wont compile
make modules_install fails because
stallion.o doesnt exist
Regards
John
-
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'd love to have somebody (yes, you) look at the actual MP table and see
> if there is something special with the XXPRESS bus, but in the end even if
> we don't know a bus we're better off always just mentioning the fact
> ("Unknown bus ") and going on with our life. Maybe the system won't
On Fri, 8 Sep 2000, Torben Mathiasen wrote:
> > ipx is using cli() too.
> >
>
> Mmmm, any reason for this besides just lazyness? I'd hate to do it, cause
> I'd hate to test it 8)
Because it was never really needed.
If someone complains about it, it will be done.
-
To unsubscribe from
On Fri, 8 Sep 2000, Andrew Clayton wrote:
> I am running on a Compaq Armada E500 laptop, and after about a days worth
> of the pcmcia network card being registered, the system looses network
> connectivity with the following being logged to /var/log/messages
> eth0: Resetting the Tx ring
> > sites which RST these ECN carrying packets are the ones which disturb
> > me the most, in the Cisco PIX case does the firewall send a reset
>
> So, how would properly written pre-ECN software indicate
> rejection of packets with the unknown ECN flag?
By leaving the bits as zero
-
To
> Based on what bluesmoke.c said about my 2nd PII-333 CPU I just got
> Intel to give me an RMA number for its replacement. Thank you Alan Cox ;-)
I'd like to finish verifying the code first but umm ok. Do send me traces
if you get any of these exceptions. I've still had no answer to my request
> If anybody wants to explicitly state that their code will be valid under
> any version of the GPL (current or future - whatever they may look like),
> please send patches to say so for the code in question. If you've used the
> FSF boiler-place copyright notice, you already have this in place
On Fri, Sep 08, 2000 at 06:33:34PM +1100, Keith Owens wrote:
> Exmh handles MIME just fine and MIME is useful for some things. Other
> people (including Linus) have made it clear that MIME is not welcome on
> linux-kernel, plain text format is always better when you are sending
> plain text.
"Juan J. Quintela" wrote:
> > "kenneth" == Kenneth Johansson <[EMAIL PROTECTED]> writes:
>
> kenneth> Is there some way I can fix the old report I don't have a unprocessed
>version of the oops as klogd "fixed" it automatically.
>
> I don't think so. It is a good idea to run klogd with the
On Fri, Sep 08, 2000 at 12:25:48PM -0700, Linus Torvalds wrote:
> On Fri, 8 Sep 2000, Maciej W. Rozycki wrote:
> > I think we must panic() for an unknown bus that has an I/O APIC interrupt
> > routed from that is marked as "conforming to the bus spec" in the MP
> > table. Trying to assume any
On Fri, Sep 08 2000, Marcelo Tosatti wrote:
>
> On Fri, 8 Sep 2000, Torben Mathiasen wrote:
>
> > On Fri, Sep 08 2000, Arnaldo Carvalho de Melo wrote:
> > > Hi,
> > >
> > > Please take a look and consider applying. Some of it are small cleanups, if
> > > they're deemed unnecessary, lemme now
>
Based on what bluesmoke.c said about my 2nd PII-333 CPU I just got
Intel to give me an RMA number for its replacement. Thank you Alan Cox ;-)
:
~v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ
Tim Brunne writes:
> *a silent hard disk hard disk is no longer feasible since kernel
> 2.2.11*.
Yes it is. I have one of my machines (which NFS serves a NFS root
client, both of which are on 24 hours a day) capable of spinning
down for up to 4 hours at a time, with no kernel modifications
what
Ok, as the truncate problems really seem to be fixed, it's time to do an
official test8, the first development kernel in about a year and a half
that should have a working truncate() again. Thanks to everybody who
tested, and especially to Al Viro who did a lot of the heavy lifting.
There are a
umsdos wont compile
make modules_install fails because
stallion.o doesnt exist
Regards
John
-
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 Thu, Sep 07, 2000 at 10:00:05AM -0400, James Simmons wrote:
> On the console level their are complex issues as well. Consider a
> system with 4 VTs attached to one machine. What if one person pressed
> Ctrl-Alt-Del. Anyone can bring the system down when multiple people depend
> on it.
On Thu, Sep 07, 2000 at 10:46:58AM +0200, Martin Dalecki wrote:
> > I've done an implementation of some of the Win32 "system calls" in a kernel
> > module in an attempt to speed up Wine.
>
> Please by no way don't include this patch into the official tree.
> It's insane due to the following:
>
>
Rik van Riel wrote:
>
>
> > NDS provides no value to Linux unless it's integrated into the
> > OS, which will happen when MANOS goes out next year around
> > March. NDS is more of a Microsoft play than a Linux play and
> > Linux already has better internet directory technology than NDS
> > --
"J. Robert von Behren" <[EMAIL PROTECTED]> wrote:
> FWIW, this can be done with relatively low overhead by creating a
> miscelaneous character device, and just using write() to write in the
> arguments. This is a bit worse than passing things through registers,
> but doesn't seem all that bad.
On Fri, 8 Sep 2000, Torben Mathiasen wrote:
> On Fri, Sep 08 2000, Arnaldo Carvalho de Melo wrote:
> > Hi,
> >
> > Please take a look and consider applying. Some of it are small cleanups, if
> > they're deemed unnecessary, lemme now and I'm back it off. I think that there
> > are some more
On Fri, 8 Sep 2000, Maciej W. Rozycki wrote:
>
> I think we must panic() for an unknown bus that has an I/O APIC interrupt
> routed from that is marked as "conforming to the bus spec" in the MP
> table. Trying to assume any defaults is unsafe and is not any better --
> we may guess them upon
On Fri, Sep 08, 2000 at 03:41:27AM +0100, Anton Altaparmakov wrote:
> [kernel-2.4.0-test3 to kernel-2.4.0-test8-pre6, bug present in those two,
> didn't try others]
>
> I have been trying to get the linear md driver to work with NTFS volumes
> for several months and it never worked. - I was
On Fri, Sep 08, 2000 at 04:58:33PM +0400, Ivan Kokshaysky wrote:
> Yes, I can reproduce this with gcc-2.95.2 (compiles cleanly with 2.96).
> Looks like older gcc doesn't like when output operand 5 listed
> also as input. Hmm.
> Simple swapping operands 4 and 5 makes gcc happy.
I've got a patch
On Fri, Sep 08, 2000 at 08:36:58PM +0400, Ivan Kokshaysky wrote:
> FWIW, here are __xchg_u8 and __xchg_u16 for Alpha.
I like it.
r~
-
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
David S. Miller writes:
>From: Ulrich Kiermayr <[EMAIL PROTECTED]>
>
> Reserved: 6 bits
>
> Reserved for future use. Must be zero.
>
>
>The point is: 'must be zero' is redefined by rfc2481 (ECN).
>
> The authors of rfc793 probably, in all honesty, really meant
>
On Fri, 8 Sep 2000, Andi Kleen wrote:
:The source address does not matter.
Well from the attacker's point of view I believe it does. For many reasons
starting from the fact that the more ip addresses, the more difficult to
block (per ip-blocking firewall basis) and, if there is a chance
On Fri, Sep 08 2000, Arnaldo Carvalho de Melo wrote:
> Hi,
>
> Please take a look and consider applying. Some of it are small cleanups, if
> they're deemed unnecessary, lemme now and I'm back it off. I think that there
> are some more unchecked calls that need fixing, but I think its
On Fri, 8 Sep 2000, Jeff V. Merkey wrote:
> This thread is dead. I am porting the MANOS debugger to Linux,
Ohhh cool. While I don't use debuggers myself, I know people
who really like having a good debugger around and are more
productive finding and fixing problems when they have one.
A
This thread is dead. I am porting the MANOS debugger to Linux, and I
have dissolved TRG's incestuous relationship with Microsoft so we could
integrate a full NTFS on Linux -- two issues down. NDS provides no
value to Linux unless it's integrated into the OS, which will happen
when MANOS goes
>From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: [ANNOUNCE] Withdrawl of Open Source NDS Project/NTFS/M2FS for
Linux
>"The lack of a Kernel Debugger and other basic kernel level facilities on
>Linux make TRG's job about 20 times harder on Linux and take almost
On Fri, 8 Sep 2000, Alan Cox wrote:
> > PS: How the hell did we go from complaining about the "stubby modules tree"
>
> We ??
>
> I thought you were on a one man insulting session aimed at the
> Makefile maintainer ?
Maybe there's someone with him that prevents him from
releasing his
I am refering to:
>Date: Sat, 02 Sep 2000 15:00:20 -0600
>From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: [ANNOUNCE] Withdrawl of Open Source NDS Project/NTFS/M2FS for
Linux
>"The lack of a Kernel Debugger and other basic kernel level facilities on
>Linux
Martin Dalecki <[EMAIL PROTECTED]> writes:
> There is some facility allowing to implement this kind of things
> in the C++ part of the most recent EGCS version which makes implementing
> such things "relatively" easy - basiclly there is the provision to dump
> the parser trees as easy to process
Hi,
This project has been sleeping for a while, so I thought it was about time
something happened. And now it has - I've put up version 0.0.2c of the
CD-RW packet writing module, aka the "happy birthday grandma" release 8)
A summary of some of the changes:
- inc usage count of buffer heads
-
David Howells wrote:
> (2) Some sort of support for (dynamically allocated) system calls implemented
> in modules.
FWIW, this can be done with relatively low overhead by creating a
miscelaneous character device, and just using write() to write in the
arguments. This is a bit worse than
Hi,
Please take a look and consider applying. Some of it are small cleanups, if
they're deemed unnecessary, lemme now and I'm back it off. I think that there
are some more unchecked calls that need fixing, but I think its better to keep
the patches smaller and incremental, what do you
On Fri, 8 Sep 2000, Maciej W. Rozycki wrote:
>
> While you may surely use your patch for now, I don't think it's good as a
> general solution. I think we should either handle all busses (some of
> them were never actually used for i386 machines) or leave the code as is.
> By handling of all
On Thu, 7 Sep 2000, Marty Fouts wrote:
> FWIW, large system scalability, especially NUMA is not tractable
> with a 'one size (algorithm) fits all' approach, and can be a
> significant test of the degree of modularity in your system.
> Different relative costs of access to the different levels
This is the third in a series to add readonly BeOS fs
support to 2.2.16. Changes in this version:
o re-enabled functions in debug.c - must edit include/linux/beos_fs.h
and enable BEOS_DEBUG define to use. Removed most printk's.
o Beginning of write support. This does not work, yet.
Notes:
On Fri, 8 Sep 2000, Jean-Marc Saffroy wrote:
> We have here an older SMP machine (NCR Globalyst S40, quad Pentium 100)
> with an Intel Xtended Xpress (or XXPRESS) motherboard, and all development
> kernels since 2.3.20 don't boot with SMP on it, because they panic when
> they discover a bus type
On Sat, Sep 09, 2000 at 12:50:38AM +1100, Anton Blanchard wrote:
> Yeah on most architectures you cant do an xchg of a 16 bit quantity.
> Rusty has a patch:
>
...
FWIW, here are __xchg_u8 and __xchg_u16 for Alpha.
Ivan.
--- 2.4.0t8p6/include/asm-alpha/system.hThu Sep 7 19:01:46 2000
> The other day I got the patch for 2.2.17 and after just over a day of normal
> operation, while my sister was playing kpat (KDE solitaire) yesterday
> afternoon, X died and dropped her out to the console.
> After she told me about it later on I found this at the bottom of my dmesg:
>
> CPU 0:
> There are people today that refuse to use computers for writeing,
> and they have good arguments, ...
Harken back to David Miller, who wrote about occupying his hands
with something to keep them the hell off the keyboard while he is
meditating on a screen full of code.
One of my debugging
Hello!
> Well, it looks like you're getting hit with stream.c or raped.c and what
> I'm passing on is just what I picked up from a CERT guy at Usenix. He
> claimed that stream.c worked by exploiting a long path through the kernel
He just said a crap. All the discussion around stream.c is banal
Linus Torvalds <[EMAIL PROTECTED]> writes:
> Sure. I just don't see many end-users single-stepping through
> interrupt handlers etc.
>
> But yes, there probably are a few.
I think you would be surprised, and I speak as someone who has found
and fixed race conditions in your kernel.
There are
On 6 Sep 2000, at 14:03, Linus Torvalds wrote:
> In article <[EMAIL PROTECTED]>,
> >Linus Torvalds wrote:
>
> Think of rabbits. And think of how the wolf helps them in the end. Not
> by being nice, no. But the rabbits breed, and they are better for having
> to worry a bit.
No matter how much
Hello!
> > I guess Alexey point is that the current compiler doesn't notice that.
Rather I proposed explanation, why missing barrier does not
have any effect. 8)8)
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Fri, Sep 08, 2000 at 05:49:35PM +0300, George Athanassopoulos wrote:
> On Fri, 8 Sep 2000, Andi Kleen wrote:
>
> :The only way to fix that with TCP is to pull the plug. You probably didn't
> :understand it, but the RST is only *one* way where TCP replies, but there
> :are lots of other ways
Hi!
Recently I tried to read old VFAT-formatted MO disk with 2.4.0-test7 kernel.
Long time ago in the days of 2.3.x such operation caused no problems.
Today 2.4.0-testX kernels OOPSes at fat_file_read(), trying to
dereference NULL pointer at (inode->i_sb)->cvf_format->cvf_file_read
Due to 2028
On Fri, 8 Sep 2000, Andi Kleen wrote:
:The only way to fix that with TCP is to pull the plug. You probably didn't
:understand it, but the RST is only *one* way where TCP replies, but there
:are lots of other ways too (like ACKs)
I think I know how TCP works but seems like you analyze the
On Sat, 9 Sep 2000, Anton Blanchard wrote:
> Yeah on most architectures you cant do an xchg of a 16 bit quantity.
> Rusty has a patch:
That's what I thought as well, at least for Alpha's case. Thanks...will
try both patches and let you all know how it goes...
C
-
To unsubscribe from this
> Great. I'll apply the patch and see where the next breakage is :-P I
> believe there was a problem in the netfilter code
> (net/ipv4/netfilter/ipt_REJECT.c, lines 67-68) with the selection of
> which xchg() to use (either __xchg_u32() or __xchg_u64()as detailed in
>
On Fri, Sep 08, 2000 at 02:12:09PM +0100, David Howells wrote:
>
> (1) A death-knell callback list to be placed in the task structure. Each
> function so listed (if any) would be invoked upon exit, signal-death or
> execve.
The SGI accounting project (and other accouting projects
On Wed, 6 Sep 2000, George Anzinger wrote:
> Actually I was not quite correct. The call to timeout WILL return
> immediately, however, the timeout code will clean up the timer, so there
> should be no worry there. It is a bug in that the sleep does not happen
> as expected. I saw at least one
On Fri, 8 Sep 2000, Ivan Kokshaysky wrote:
> Yes, I can reproduce this with gcc-2.95.2 (compiles cleanly with 2.96).
> Looks like older gcc doesn't like when output operand 5 listed
> also as input. Hmm.
> Simple swapping operands 4 and 5 makes gcc happy.
Great. I'll apply the patch and see
On Fri, Sep 08, 2000 at 06:33:34PM +1100, Keith Owens wrote:
> plain text. What next, rich text format and HTML with multiple copies
> of the text, MSWord format?
don't joke. a certain government department here (that shall remain
unnamed) has an email system that *automatically* converts
On Fri, Sep 08, 2000 at 04:19:25AM -0400, Christopher C. Chimelis wrote:
> xor.c: In function `xor_block_alpha':
> xor.c:1791: inconsistent operand constraints in an `asm'
> xor.c: In function `xor_block_alpha_prefetch':
> xor.c:2213: inconsistent operand constraints in an `asm'
>
Yes, I can
Hi.
I just got hold of an old machine (P75, 32MB RAM). On trying to install
RH 6.2 on it, I got an oops after loading the kernel from the boot floppy.
I then tried to boot a 2.4.0-test8-pre6 (made with make bzdisk), but got
an oops. The same with 2.2.17.
Any help would be appreciated.
Oops
The other day I got the patch for 2.2.17 and after just over a day of normal
operation, while my sister was playing kpat (KDE solitaire) yesterday
afternoon, X died and dropped her out to the console.
After she told me about it later on I found this at the bottom of my dmesg:
CPU 0: Machine
While preparing my first ever post to lkml just now about a problem in 2.2.17
(which I will post after this hopefully), I was fortunate enough to get my
first ever oops. I was in X at the time so I was unaware of the happy occasion.
All I noticed was su segfault once or thrice and then I couldn't
Now that is what I want on a t-shirt. ;)
On Thu, 7 Sep 2000, Peter Samuelson wrote:
> [Now, centuries-old theological arguments may well be of supreme
> importance in some ways -- an undeniably subjective and personal
> judgment -- but in terms of Linux kernel development they are usually
>
On Fri, 8 Sep 2000, Mark Hindley wrote:
> I have just spent a frustrating day trying to rebuild the 2.2.17 kernel for
> my new Debian potato installation.
>
[Snipped...]
As a temporary work-around, try a 'append="mem=NNN"' in lilo.conf. So far
everybody who has had symptoms like this has been
> > the reserved flag bits are non-zero. The only things this protects
> > anyone from are extensions such as ECN :-)
>
> To be fair even older netfilter had the same problem (ipt_unclean would
> complain about the reserved bits). It is probably a common bug.
The current British Standard
1 - 100 of 243 matches
Mail list logo
