Hello,
The kernel is 2.2.18pre22 SMP + reiserfs 3.5.27. The activity
is on the reiserfs partition. The oops is at the end of the message.
There are no ksymoops texts but after analyzing the oops, the problem
is here, in inline remove_shared_vm_struct():
EIP:
H. Peter Anvin wrote:
> I suggested include/kernel and include/arch with include/linux and
> include/asm being reserved for the kernel interfaces (ioctl and their
> structures mostly.)
That sounds good. One other refinement I would like to see is that
architecture specific but always present
On Thu, 23 Nov 2000 02:25:33 -0500,
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>Keith Owens wrote:
>> #define PCITBL(v,d,sv,sd) \
>> { PCI_VENDOR_ID_##v, PCI_DEVICE_ID_##d, \
>>PCI_VENDOR_ID_##sv, PCI_DEVICE_ID_##sd }
>
>* your macro fails for the 'ANY' case, because the proper macro is
> 540028982 = 0x20303036 = " 336"
> 540024880 = 0x20302030 = " 3 3"
> 170926128 = 0x0a302030 = "\n3 3"
>
These should be:
540028982 = 0x20303036 = " 006"
540024880 = 0x20302030 = " 0 0"
170926128 = 0x0a302030 = "\n0 0"
/Pär-Ola Nilsson
-
To unsubscribe from this list: send the line
Others have reported similar problems, i.e.
NOTHING after the "booting kernel message".
My case is:
Dual P-II Xeons, Intel 440GX chipset.
Booting with loadlin or syslinux-1.50
root-partition: /dev/hdc3
Kernel freatures:
CPU set to Pentium-II
No module support
No plug
[Adam J. Richter]
> +static struct pci_device_id atp870u_pci_tbl[] __initdata = {
> +{vendor: 0x1191, device: 0x8002, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
> +{vendor: 0x1191, device: 0x8010, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
It would make it easier to read and safer to
Mohammad A. Haque writes:
> I just got these while doing many compiles on my box
>
> Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
> ext2_unlink: Deleting nonexistent file (622295), 0
> Nov 23 00:40:06 viper kernel: = 1
> Nov 23 00:40:06 viper kernel: EXT2-fs error
> It is linux-2.2, guy. 8) "threads" are not threaded there.
>
> Semaphores (rtnl_lock, particularly) protects only areas, which
> are going to _schedule_ excplicitly or implicitly.
ok, thanks a lot Alexey, now I understand.
> Please, read comments. People used to consider comments as
On Thursday November 23, [EMAIL PROTECTED] wrote:
> I just got these while doing many compiles on my box
>
> Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
> ext2_unlink: Deleting nonexistent file (622295), 0
> Nov 23 00:40:06 viper kernel: = 1
> Nov 23 00:40:06 viper
This patch needs to be reviewed before it goes to Linus.
The ELF 64 bit spec defines
NameSizeAlignment Purpose
Elf64_Addr8 8 Unsigned program address
Elf64_Off 8 8 Unsigned file offset
Elf64_Half2 2
I just got these while doing many compiles on my box
Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
ext2_unlink: Deleting nonexistent file (622295), 0
Nov 23 00:40:06 viper kernel: = 1
Nov 23 00:40:06 viper kernel: EXT2-fs error (device ide0(3,3)):
ext2_free_blocks:
[Patrick van de Lageweg]
> diff -u -r --new-file linux-2.4.0-test11.clean/drivers/atm/firestream.c
>linux-2.4.0-test11.fs50+atmrefcount/drivers/atm/firestream.c
Since you are submitting in the form of a source patch, you ought to
include the relevent bits of
drivers/atm/Makefile
After Linus' recent changes there were many complaints
about bugs in the isofs handling. Still, his code is fine.
I know about some things that still need to be done, and
already corrected two flaws yesterday or so, but people
sent me their isofs images and their problem was not caused
by
[Alan Cox]
> Changes in 2.4.0test11ac2
> o Work arounds for broken Dell laptop APM (me)
> | If you have an Inspiron 5000e please send
> | me the dmesg of this kernel booting. Thanks
Inspiron 5000, is this close enough?
Linux version 2.4.0-test11-ac2 (peter@kendall)
Hi, I installed 2.4.0-test11 on a Dual P3-550 [Tyan Tiger 133 with
S1834 BIOS]. I updated the mobo with the latest bios found on Tyan's
website
http://www.tyan.com/support/html/b_tg_133.html
Reading dmesg, I found the following
mtrr: your CPUs had inconsistent variable MTRR settings
mtrr:
On Thu, Nov 23, 2000 at 12:26:30AM +, Russell King wrote:
> Albert D. Cahalan writes:
> > > Function entered at [] from []
> > > Function entered at [] from []
> > > Code: e51f2024 e5923000 (e5813000) e3a0 e51f3030
> >
> > All those numbers get looked up. Keep going for another 25 lines
On Wed, 22 Nov 2000 21:54:48 -0500 (EST),
"Albert D. Cahalan" <[EMAIL PROTECTED]> wrote:
>Under NO circumstances should klogd or ksymoops mangle the
>original oops. The raw oops data MUST be completely preserved.
>It is a serious bug that this is not what currently happens.
ksymoops prints the
Russell King writes:
> Albert D. Cahalan writes:
>> All these numbers get looked up.
>
> These numbers should NOT get looked up - if they are, then very
> useful information will be lost;
WOAH, STOP!!! You say "lost"???
Under NO circumstances should klogd or ksymoops mangle the
original oops.
Hi Alan,
Alan Cox <[EMAIL PROTECTED]> writes:
>
> Changes in 2.4.0test11ac2
>
> o APM update (Stephen Rothwell)
> o Work arounds for broken Dell laptop APM (me)
Here is (in my opinion) a better patch. It also means that we can
use apm as a
I seem to be having a problem with dropped packets using Olicom's
driver v 1.37 in the linux 2.2.16-22 kernel. The system is a Dell
Poweredge 2400 server with 2 CPUs. The rest of the ring is Olicom
microchannel cards on NCR UNIX. These are running with an MTU of 4088
as opposed to linux' 2000.
[Albert D. Cahalan]
> The infamous LINK_FIRST infrastructure was sort of half-way done.
I disagree: it could handle all cases I could see that we might
reasonably care about. I challenge anyone to come up with a
non-pathological case that could not be taken care of with a single
LINK_FIRST
The following patch adds a pci_device_id table and a
MODULE_DEVICE_TABLE delcaration to each remaining PCI driver
in linux-2.4.0-test11/drivers/char/. I have used the named initializer
format for drivers that have only one or two PCI entries, initialize from
anonymous integers or where
> Thats because too many things get put on a line then.
> And because we do [] [] not [][] ?
In the good old times we had foo bar for a total of 8*(8+1) = 72
positions. Now we have [] [] which takes 8*(8+1+4) = 104
positions. If you turned this into 6 items per line instead of 8,
it would
On Wed, 22 Nov 2000 20:58:28 -0500 (EST),
"Albert D. Cahalan" <[EMAIL PROTECTED]> wrote:
>The infamous LINK_FIRST infrastructure was sort of half-way done.
>
>It would be best to cause drivers with an unspecified link order
>to move around a bit, so that errors may be discovered more quickly.
>"Adam J. Richter" wrote:
>> Just to avoid duplication of effort, I am posting this preliminary
>> patch which adds PCI MODULE_DEVICE_TABLE declarations to the three PCI
>> drivers in linux-2.4.0-test11/drivers/block. In response to input from
>> Christoph Hellwig, I have reduced my
On Thu, 23 Nov 2000 02:49:27 +0100,
Frank van de Pol <[EMAIL PROTECTED]> wrote:
>After upgrade to 2.4.0-test11 my copy of ALSA 0.6pre1 (cvs version) stopped
>working (causing OOPS on module load of snd-card-sbawe). I reverted back to
>2.4.0-test10 and verified that the problem does not exist in
Peter Samuelson writes:
> [Neil Brown]
>> In drivers/md/Makefile, swap the order of "raid5.o xor.o" to be
>> "xor.o raid5.o", recompile, install, reboot.
>
> Don't forget the part about adding a comment saying that xor.c does in
> fact need to come before raid5.c. This is the part that most
After upgrade to 2.4.0-test11 my copy of ALSA 0.6pre1 (cvs version) stopped
working (causing OOPS on module load of snd-card-sbawe). I reverted back to
2.4.0-test10 and verified that the problem does not exist in that version.
I'm running an SMP kernel in case that matters. Similar problem was
[Matt D. Robinson]
> Any way we can standardize 'make install' in the kernel? It's
> disturbing to have different install mechanisms per platform ...
> I can make the changes for a few platforms.
2.5 material, already on the todo list.
Peter
-
To unsubscribe from this list: send the line
> along the dmesg output from bootup on a Dell Inspiron 5000e. I have
Thanks a lot
> for the fixes to APM, and if there is any more information I can
> provide that would be useful in getting full APM support on the 5000e
> please e-mail me directly, as I do not normally read linux-kernel.
Per the request in the 2.4.0-test11-ac2 announcement I am sending
along the dmesg output from bootup on a Dell Inspiron 5000e. I have
also included the output of cat /proc/apm. Reading /proc/apm no longer
causes an oops, but the battery information is disabled. Many thanks
for the fixes to
On Wed, Nov 22, 2000 at 02:35:43PM -0800, H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:"LA Walsh" <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> >
> > Linus has mentioned a desire to move kernel internal interfaces into
> > a separate kernel include directory.
Thanks for the patch... but it does not quite work. It applies cleanly,
but upon booting the patched kernel, the machine freezes completely upon
PCMCIA initialisation (it got to the point where the init script said
'Loading modules' then nothing). CTRL+ALT+DEL does not work, either.
Anyone
[Neil Brown]
> In drivers/md/Makefile, swap the order of "raid5.o xor.o" to be
> "xor.o raid5.o", recompile, install, reboot.
Don't forget the part about adding a comment saying that xor.c does in
fact need to come before raid5.c. This is the part that most likely
will not happen, so that two
Adam J. Richter writes:
> + { PCI_VENDOR_ID_DEC, PCI_DEVICE_ID_DEC_21285, PCI_ANY_ID, PCI_ANY_ID},
No no no no no no no.
This "device" should be identified by either the class code OR the
subsystem device/vendor IDs.
By using "PCI_VENDOR_ID_DEC" and "PCI_DEVICE_ID_DEC_21285" you are
> The EIP is not pushed out of sight horizontally, but vertically.
> (Maybe you never saw a i386 oops. With [<>] the call trace takes
> twice as many lines (on a 25x80 screen) as without.)
Thats because too many things get put on a line then. And because we
do [] [] not [][] ?
>
-
To
From [EMAIL PROTECTED] Thu Nov 23 00:17:21 2000
Well, in my experience, values of PC (or EIP is x86 speak) rarely
appear over column 50 on the screen. Therefore, removing them is
only going to save width, not height.
The EIP is not pushed out of sight horizontally, but
To change the topic a bit.
Just an interesting thought, I realize that for every pro there is a
con. But what about implimenting in some kind of background "process"(for
lack of a better word right now), and probibly in a duplicate copy
of the current kernel. Checks on the system memory and
On Wed, Nov 22, 2000 at 11:24:16PM +0100, Kurt Garloff wrote:
> On Sat, Nov 18, 2000 at 11:20:09AM +0100, Andi Kleen wrote:
> > Index: include/asm-i386/hw_irq.h
> > ===
> > RCS file: /cvs/linux/include/asm-i386/hw_irq.h,v
> >
Albert D. Cahalan writes:
> > Function entered at [] from []
> > Function entered at [] from []
> > Code: e51f2024 e5923000 (e5813000) e3a0 e51f3030
>
> All those numbers get looked up. Keep going for another 25 lines too.
Oh, missed this one. Here you're wrong again. The numbers in [< >]
> Little question about 'uname'. Does it read data from kernel, /proc or
> get its data from other source ?
'strace' was made to answer questions like this.
DS
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Hi all,
For those who has C-Media 8338/8738-based sound card or as on-board
sound chip and need to work with Linux or BeOS, please download the beta
driver at http://members.home.net/puresoft/cmedia.html. The Linux driver
can work with kernel 2.2 and 2.4.
For questions, please e-mail to [EMAIL
On Thu, 23 Nov 2000, J . A . Magallon wrote:
> Little question about 'uname'. Does it read data from kernel, /proc or
> get its data from other source ?
uname(1) utility calls uname(2) syscall.
--
Alex
--
Excellent.. now
Hi all,
Linux Logical Volume Manager 0.8.1 (this is 0.8final plus patches)
and 0.9 are available for download at www.sistina.com.
Please see further information below, test it and help us
to make an even better LVM for Linux :-)
Regards,
Heinz -- The LVM guy --
The Logical Volume
Albert D. Cahalan writes:
> > c1e97ee0:c00251f8 c280007c
> > c1e97f00: 6013 c1e97fac c1e97f18 c0026194 c280006c c1e37000 c1e38000
>
> [ --- CHOP --- ]
>
> All these numbers get looked up.
These numbers should NOT get looked
Keith Owens writes:
> On Wed, 22 Nov 2000 23:12:25 + (GMT),
> Russell King <[EMAIL PROTECTED]> wrote:
> >if (copy_from_user(mod+1, mod_user+1, mod->size-sizeof(*mod))) {
>
> Using sizeof(struct module) is a nono in sys_init_module(), the code
> has to use the user space size. Does
Hi Matthias,
On Wed, Nov 22, 2000 at 02:06:18AM +0100, Matthias Andree wrote:
> I ran that script several times since it did not collect all devices,
Strange.
> and at one time, I got two oopsen that I decoded.
> * dc390 2.0e3
> Warning (compare_maps): ksyms_base symbol
MontaVista Software's latest preemptible kernel patch,
preempt-2.4.0-test11-1.patch.bz2, is now available in
ftp://ftp.mvista.com/pub/Area51/preemptible_kernel/
Here is an extract from the README file:
The patches in this directory, when applied to the corresponding
kernel source, will define a
Hi everyone.
Little question about 'uname'. Does it read data from kernel, /proc or
get its data from other source ?
uname info page:
$ uname -a
Linux hayley 1.0.4 #3 Thu May 12 18:06:34 1994 i486
my system:
uname -a
Linux werewolf 2.2.18-pre23-vm #3 SMP Wed Nov 22 22:33:53 CET 2000 i686
Russell King writes:
> [EMAIL PROTECTED] writes:
>> Of course. But since there is no information in [< >]
>> (their presence is syntactically determined, not semantically)
>> the tools you mention can be trivially patched to work without
>> this [< >] kludge. On the other hand, when the system
The documentation for this driver seems to be old in v2.4.0-test11-pre5:
You need to build a new kernel to use this device, even if you want to
use a loadable module.
Apply the patch to a 2.2.x kernel:
# cd linux
# patch -p1 http://www.tux.org/lkml/
Jes Sorensen wrote:
> I think the most important issue is when doing header files to make
> sure they go with the driver code and not in include/linux unless
> there really is a reason to expose them to user space. No reason to
> export register definitions for Ethernet cards down there.
Agreed,
Hello,
I'm using Debian Potato with linux-2.2.18pre22. This version of Potato
uses netatalk (1.4b2+asun2.1.3).
Everything works just fine if I have the two interfaces:
lo
eth0
As soon as I alias eth0 and have the interfaces:
lo
eth0
eth0:0
eth0:1
eth0:2
netatalk refuses to start and I
> "Rogier" == Rogier Wolff <[EMAIL PROTECTED]> writes:
Rogier> Mitchell Blank Jr wrote:
>> First, I'd like to make a couple points about driver style that I'm
>> trying to move towards with the ATM drivers. You're free to take
>> them or leave them, but I want to eventually move the tree in
Keith Owens writes:
> Christian Gennerat <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] a =E9crit :
>>> I also left something else
>>> that always annoyed me: valuable screen space (on a 24x80 vt)
>>> is lost by these silly [< >] around addresses in an Oops.
>>> They provide no information at
Jes Sorensen writes:
> > "Miles" == Miles Lane <[EMAIL PROTECTED]> writes:
>
> Miles> I attempted to reply to a message from Alan and got the
> Miles> following response.
>
> No it isn't, Alan uses ORBS and you are obviously black listed there
> (www.orbs.org).
>
> This one seems to come
On Wed, 22 Nov 2000 23:12:25 + (GMT),
Russell King <[EMAIL PROTECTED]> wrote:
>if (copy_from_user(mod+1, mod_user+1, mod->size-sizeof(*mod))) {
Using sizeof(struct module) is a nono in sys_init_module(), the code
has to use the user space size. Does this untested patch fix the
[EMAIL PROTECTED] writes:
> From [EMAIL PROTECTED] Wed Nov 22 19:20:52 2000
> They provide no information to the human reader, but they tell klogd
> (and other tools) that the enclosed value is a kernel address that
> should be looked up in the System.map file and decoded into
Hi,
There appears to be an incompatibility between modutils 2.3.14 and kernel
2.4.0-test11.
This occurs because modutils knows only of an 84-byte struct module, but
the kernel knows about a 96-byte struct module.
Unfortunately, the kernel "forgets" about the 12 bytes, which are part of
the
> this is a newer cleaning patch for vgacon.c against test11.
> It includes the one I sent a couple of days ago.Could you check this too
> and if OK send it to Linus?Unless of course it violates the code-freeze
> policy :-)
The changes look fine except I have to question the
Mitchell Blank Jr wrote:
> First, I'd like to make a couple points about driver style that I'm trying
> to move towards with the ATM drivers. You're free to take them or leave
> them, but I want to eventually move the tree in this direction.
> * I don't like header files that define the
On Wed, Nov 22, 2000 at 04:27:51PM -0500, Brian Kress wrote:
> "Heinz J. Mauelshagen" wrote:
> >
> > On Wed, Nov 22, 2000 at 04:05:39PM -0500, Brian Kress wrote:
> > > Question about /proc/partitions and LVM. LVM devices in
> > > /proc/partitions currently show up as lvma, lvmb, etc,
> > |> > > #define __bad_udelay() panic("Udelay called with too large a constant")
> > |>
> > |> Can't we change that to :
> > |> #error "Udelay..."
> >
> > No.
>
> ?? I think I'm missing something here.
preprocessor stuff is done too early for this
-
To unsubscribe from this list: send the
Yo Miles!
Well I see 216.200.176.7 in ORBS:
$ chk-rly 216.200.176.7
rbl.maps.vix.com =>
rss.maps.vix.com =>
dul.maps.vix.com =>
relays.orbs.org => 127.0.0.4
relays.orbs.org => untestable - above.net has multiple open relays and has blocked
the ORBS tester.
outputs.orbs.org =>
RGDS
GARY
cat /proc/cpuinfo shows like this for 2.4.0-test11 (also in ac2)
cpu MHz : 132.000956
The "000" seems to be excess. linux/arch/i386/kernel/time.c has it
right in time_init().
diff -u linux/arch/i386/kernel/setup.c\~ linux/arch/i386/kernel/setup.c
--- linux/arch/i386/kernel/setup.c~
Alan Cox wrote:
>> Okay, please explain why ORBS tells me it does *not*
>> identify my ISP's SMTP server as an open relay?
>>
>> mail.megapathdsl.net = 216.200.176.7
>
>
> Your mail goes out via your isps outgoing feed ns1.megapath.net
> which is in ORBS (216.200.176.4)
Thank you,
I will go
On Mon Nov 20 2000, Alessandro Suardi wrote:
> there is a buglet in fs/isofs/namei.c, corrected in test11-final.
Hmmm.
/var/log/warn says
Nov 21 23:07:06 elfie kernel: _isofs_bmap: block >= EOF (1633681408, 4096)
Nov 21 23:07:08 elfie kernel: _isofs_bmap: block >= EOF (559939584, 4096)
Nov
Followup to: <[EMAIL PROTECTED]>
By author:"LA Walsh" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Linus has mentioned a desire to move kernel internal interfaces into
> a separate kernel include directory. In creating some code, I'm wondering
> what the name of this should/will
> |> > > #define __bad_udelay() panic("Udelay called with too large a constant")
> |>
> |> Can't we change that to :
> |> #error "Udelay..."
>
> No.
?? I think I'm missing something here.
> Andreas.
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Andi Kleen wrote:
>
> On Wed, Nov 22, 2000 at 05:14:38PM -0500, Jeff Garzik wrote:
> > *This* is the over-engineering attitude I was talking about. The only
> > reason why you are preferring named initializers is because
> > pci_device_id MIGHT be changed. And if it is changed, it makes the
>
Alan Cox wrote:
> I see higher performance with 4K block sizes. I should see higher
> latency too but have never been able to measure it. Maybe it depends
> on the file system.
> It certainly depends on the nature of requests
If the files get somewhat bigger (eg. > 1G) having a bigger block
Okay, please explain why ORBS tells me it does *not*
identify my ISP's SMTP server as an open relay?
mail.megapathdsl.net = 216.200.176.7
ORBS says:
Database Check - 216.200.176.7
216.200.176.7 is not in the main automated
open relay database
Thanks,
Miles
-
> Q: When I send private e-mail to Alan Cox, it bounces. Why?
> A: Alan has blocked all incoming e-mail except from a list of addresses
> known to be good. You'll need to post to the list to be seen by him.
Try
A: Alan like many people filters mail using the MAPS RBL, DUL and ORBS
spam relay
On Sat, Nov 18, 2000 at 11:20:09AM +0100, Andi Kleen wrote:
> Index: include/asm-i386/hw_irq.h
> ===
> RCS file: /cvs/linux/include/asm-i386/hw_irq.h,v
> retrieving revision 1.11
> diff -u -u -r1.11 hw_irq.h
> ---
On Wed, 22 Nov 2000 14:42:05 +0100,
Christian Gennerat <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] a écrit :
>
>> I also left something else
>> that always annoyed me: valuable screen space (on a 24x80 vt)
>> is lost by these silly [< >] around addresses in an Oops.
>> They provide no
Jeff,
>>Is this assumption correct, and does this comply with TPC rules for ORACLE and
>>other DBMS benchmarks? It looks like a good patch that will perform
>>very fast for O_SYNC.
Why would that be a problem? If you look at our benchmarks we normally use raw I/O
to bypass buffers altogether
On Wed, Nov 22, 2000 at 05:14:38PM -0500, Jeff Garzik wrote:
> *This* is the over-engineering attitude I was talking about. The only
> reason why you are preferring named initializers is because
> pci_device_id MIGHT be changed. And if it is changed, it makes the
> changeover just tad easier.
"Adam J. Richter" wrote:
> Just to avoid duplication of effort, I am posting this preliminary
> patch which adds PCI MODULE_DEVICE_TABLE declarations to the three PCI
> drivers in linux-2.4.0-test11/drivers/block. In response to input from
> Christoph Hellwig, I have reduced my
On Thu, 23 Nov 2000, Miles Lane wrote:
> host lightning.swansea.uk.linux.org says:
> 550 rejected: administrative prohibition
I think this one needs to go into the FAQ!
Q: When I send private e-mail to Alan Cox, it bounces. Why?
A: Alan has blocked all incoming e-mail except from a list of
On Thu, 23 Nov 2000, Miles Lane wrote:
> I attempted to reply to a message from Alan
> and got the following response.
> SMTP module(domain lxorguk.ukuu.org.uk) reports:
> host lightning.swansea.uk.linux.org says:
> 550 rejected: administrative prohibition
You're in ORBS. Fix your open
> "Miles" == Miles Lane <[EMAIL PROTECTED]> writes:
Miles> I attempted to reply to a message from Alan and got the
Miles> following response.
No it isn't, Alan uses ORBS and you are obviously black listed there
(www.orbs.org).
This one seems to come up every now and then, and always turns
> under 1 gig in size. You can exhibit the problem by mounting the dvd movie
> "The World is Not Enough" as it contains a video_ts.vob which is larger than
> 1 gigabyte. You will see that most of the file lengths are incorrect due to
> the "cruft mounting option" hacking off the high order
Just to avoid duplication of effort, I am posting this preliminary
patch which adds PCI MODULE_DEVICE_TABLE declarations to the three PCI
drivers in linux-2.4.0-test11/drivers/block. In response to input from
Christoph Hellwig, I have reduced my threshhold on using named initializers
to
I attempted to reply to a message from Alan
and got the following response.
Original Message
Subject: Undeliverable mail: Re: Linux 2.4.0test11-ac2
Date: Wed, 22 Nov 2000 11:46:54 -0800
From: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Failed to deliver to '[EMAIL PROTECTED]'
Hi all,
There is a pretty bad bug in the "/fs/isofs/inode.c" file under linux kernel
version 2.2.17. Search the file for the word "dipshit" (not a joke) and
look at the cruft mounting code. It assumes that the maximum size of a
dvd-rom file is 1 gigabyte. This is certainly not a correct
> The reason that everyone else uses copy_{to,from}_user is that there
> is no way to guarantee that the userspace pointer is valid. That
> memory may have been swapped out. The copy macros are prepared to
> fault the memory in. The rest of the kernel is not.
>
> Jeff
I may be wrong on this, but
Jeff Dike wrote:
>
> The user-mode port of 2.4.0-test11 is available.
>
> UML is now able to run as a daemon, i.e. with no stdin/stdout/stderr.
>
> The hostfs filesystem now works as a readonly filesystem. It's now
> configurable. I'm using it as a module. It ought to work compiled into the
"Heinz J. Mauelshagen" wrote:
>
> On Wed, Nov 22, 2000 at 04:05:39PM -0500, Brian Kress wrote:
> > Question about /proc/partitions and LVM. LVM devices in
> > /proc/partitions currently show up as lvma, lvmb, etc, depending on
> > their device number. This breaks things like mount by
On Wed, Nov 22, 2000 at 04:05:39PM -0500, Brian Kress wrote:
> Question about /proc/partitions and LVM. LVM devices in
> /proc/partitions currently show up as lvma, lvmb, etc, depending on
> their device number. This breaks things like mount by filesystem
> name. Back when LVM existed
Question about /proc/partitions and LVM. LVM devices in
/proc/partitions currently show up as lvma, lvmb, etc, depending on
their device number. This breaks things like mount by filesystem
name. Back when LVM existed as a patch, I believe there was some
support in
In article <[EMAIL PROTECTED]> you wrote:
> Linus has mentioned a desire to move kernel internal interfaces into
> a separate kernel include directory. In creating some code, I'm wondering
> what the name of this should/will be. Does it follow that convention
> would point toward a linux/sys
On Wed, 22 Nov 2000, Rik van Riel wrote:
> On Wed, 22 Nov 2000, Szabolcs Szakacsits wrote:
>
> >- OOM killing takes place only in do_page_fault() [no two places in
> > the kernel for process killing]
>
> ... disable OOM killing for non-x86 architectures.
> This doesn't seem like a
Linus has mentioned a desire to move kernel internal interfaces into
a separate kernel include directory. In creating some code, I'm wondering
what the name of this should/will be. Does it follow that convention
would point toward a linux/sys directory?
-l
--
L A Walsh|
On Wed, 22 Nov 2000, Szabolcs Szakacsits wrote:
>- OOM killing takes place only in do_page_fault() [no two places in
> the kernel for process killing]
... disable OOM killing for non-x86 architectures.
This doesn't seem like a smart move ;)
> diff -urw
Jeff Epler wrote:
> Well, a copy of that document *is* the first hit for a google search on
> 'linux signal 11 faq'
> http://www.google.com/search?q=linux+signal+11+faq
>
> In other words, someone who does the slightest bit of research will
> find the answer.
Perhaps, but if a new user
It seems like lastest kernels cannot run lmbench successfully.
lmbench stops at "Local networking", between lat_connect
and bw_tcp, as far as I can see from 'top'.
No errors reported, lat_connect or bw_tcp exit silently.
All 2.4.0-test[5-11] seem to have this problem.
2.4.0-test1 and 2.2.x all
Hello,
I tested many hours before I sent you this eMail. I never
sent Bug-Reports, so please be friendly if I did something
wrong :-)
I used the formular to produce a bug-report:
1.) See subject
2.) I have trouble using DMA mode with my Siemens Fujitsu
harddisk on a NMC 6vcx Motherboard. I
The link inside configure help for ip tunneling
"http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html"
appears to be non-existent
Andrew
-
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
On Wed, 22 Nov 2000, David Ford wrote:
> > > * Remove compile warnings in xstrcat.
> > > * snprintf cleanups.
> > > * Set safemode when uid != euid.
> > > * Strip quotes from shell responses.
> > + add RedHat ism's with a --rhc (red hat compatible) -i -m (-F)
> >
> > Daniel Stone
> > Linux Kernel Developer
> ^^
>
> If you were, you'd have written something that makes sense.
Touche. I didn't claim to be a Linus, but I have got a few things in the
kernel (sb16 driver, netfilter). Plus you can't ask much when I've gone 5
days without
1 - 100 of 398 matches
Mail list logo
