Hi,
On Thu, Oct 12, 2000 at 02:19:27PM +0100, Tigran Aivazian wrote:
> Having done a few more reboots I got more info -- one of the eepro100
> interfaces is dead only in 4 out 5 cases. So, sometimes, doing ifdown eth0
> ; ifup eth0 does help.
Tigran, please check if you have any driver's message
On Thu, 12 Oct 2000, James Simmons wrote:
>
> > > every CPU to avoid slowdowns. So that if you set that eth0's
> > > IRQ will be handled by CPU1, the MTRRs of CPU1 will be set
> > > accordingly, and the other CPUs will not care about eth0,
> > > so they do not need eth0's MTRR settings.
> >
> >
On Fri, Oct 13, 2000 at 12:26:02AM +0100, Alan Cox wrote:
> egcs-1.1.2 builds 2.2.18pre. I know this because thats the compiler I use
> to build it. Its also the recommended compiler.
What do you mean by _the_ recommended compiler? Is 2.7.2.3 recommended no
more? Is there some benefit using egcs-
On Tue, 10 Oct 2000, Vojtech Pavlik wrote:
> On Tue, Oct 10, 2000 at 12:20:07PM -0400, Mark Hahn wrote:
>
> > > Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
> > > setup where would be just one drive and a really short, 40-wire cable
> > > without problems as well. I've even
>> Is there any way to call system call from a kernel module???
>yes, just call it. system calls are just functions (mostly exported and
>when otherwise, use sys_call_table[] which is exported, but it won't work
>on __mips__) so you can just call them.
thanks tigran, but i am new to kernel pro
On Thu, 12 Oct 2000, David S. Miller wrote:
>
>page_table_lock is supposed to protect normal page table activity (like
>what's done in page fault handler) from swapping out.
>However, grabbing this lock in swap-out code is completely missing!
>
> Audrey, vmlist_access_{un,}lock ==
On Thu, 12 Oct 2000, David S. Miller wrote:
>
>Any of the mm gurus give the patch below a quick once over ? Is
>this adequate, or is there more to this than the description
>implies?
>
> It might make more sense to just make rss an atomic_t.
Agreed.
Linus
-
To u
hi all,
For dma transfers to/from user space buffer, one need to lock that user
space buffer so that it won't be swaped out. and also
its bus address is obtained by call virt_to_bus and then this bus address
is written to dma controller.
but do we explicitly need to map that user buffer into kerne
On Thu, Oct 12, 2000 at 09:25:47PM -0700, David S. Miller wrote:
>Date: Fri, 13 Oct 2000 12:34:30 +0800
>From: Andrey Savochkin <[EMAIL PROTECTED]>
>
>page_table_lock is supposed to protect normal page table activity (like
>what's done in page fault handler) from swapping out.
>
Date: Fri, 13 Oct 2000 12:34:30 +0800
From: Andrey Savochkin <[EMAIL PROTECTED]>
page_table_lock is supposed to protect normal page table activity (like
what's done in page fault handler) from swapping out.
However, grabbing this lock in swap-out code is completely missing!
Audrey
Hello,
On Fri, Oct 13, 2000 at 01:20:23AM +0100, [EMAIL PROTECTED] wrote:
> > 9. To Do
> > * mm->rss is modified in some places without holding the
> > page_table_lock (sct)
>
> Any of the mm gurus give the patch below a quick once over ?
> Is this adequate, or is there more to this th
Timur Tabi wrote:
> ** Reply to message from "Robert B. Easter" <[EMAIL PROTECTED]> on Thu,
> 12 Oct 2000 18:47:22 -0400
>
> > Since installing a
> > second CPU and recompiling the kernel for SMP and recompiling ALSA with
> > --with-smp=yes, the sound loops. I can hear the sound, but it doesn't
I am attaching the debug output on bootup after defining DEBUG in pci.c
and the i386 pci header file with test10-pre2
Note: this is a Dell Lattitude docking station. The devices which are
having resource problems are on the docking station. Works fine with 2.2
kernels.
Yes, this is on RH7 with k
On Fri, Oct 13, 2000 at 03:50:41AM +0100, Ian Stirling wrote:
> >
> > On Fri, Oct 13, 2000 at 04:19:49AM +, Ingo Rohloff wrote:
>
> > 2.4 has already broken backwards compatibility to 2.2 (IV changed
> > from disk absolute to relative). When you change it now (before 2.4.0)
> > it is relati
>
> On Fri, Oct 13, 2000 at 04:19:49AM +, Ingo Rohloff wrote:
> 2.4 has already broken backwards compatibility to 2.2 (IV changed
> from disk absolute to relative). When you change it now (before 2.4.0)
> it is relatively painless. I think the change is a good idea.
I've been away from th
On Fri, Oct 13, 2000 at 04:19:49AM +, Ingo Rohloff wrote:
> Hi again,
>
> Marc Mutz wrote:
>
> > > The loop device supports different IVs;
> > > the IVs are initilized with the requested block
> > > number.
>
> > > I believe a better way is to use the requested
> > > sector number from CURR
[Jan-Benedict Glaw]
> Your kernel was probably patched te become a 2.2.17. The "problem"
> is diff. It can
> - add lines
> - remove lines
> - add files
> but it *cannot remove files. The only way to "remove" a file is to
> delete all ist contents, but the (empty) file remains...
Hi again,
Marc Mutz wrote:
> > The loop device supports different IVs;
> > the IVs are initilized with the requested block
> > number.
> > I believe a better way is to use the requested
> > sector number from CURRENT->sector.
> > Using this value should make the encryption and decryption
> > pr
Ookay, hopefully I've got the right place. I've seen everyone post
bttv problems to lkml, so here it goes ;)
I am currently running with 2.2.17
I modprobe the bttv drivers (output):
Linux video capture interface: v1.00
i2c: initialized
bttv0: Brooktree Bt848 (rev 17) bus: 0, devfn: 80, irq: 12,
Date:Thu, 12 Oct 2000 12:48:27 -0700 (PDT)
From: Linus Torvalds <[EMAIL PROTECTED]>
David, you know this code, would you mind giving it another pair of
eyes? I hate code that doesn't make sense.
Ok, the deal is that the tpnt->present handling during unregister is
really brok
Here is a patch against 2.4.0-test9,
which adds information about the modules produced by netfilter.
Please let me know if it is suitable.
Paul Schulz
** This message was bounced when I tried to send it to:
** Axil Boldt ([EMAIL PROTECTED])
** (Email address at the top of the file.. has this
On Thu, 12 Oct 2000, Thorsten Kranzkowski wrote:
> > > Alpha DP264 (UP), SCSI, floppy
> > >
> > > ... if I read from
> > > /dev/fd0, it used to buffer the whole thing, so a second read would be
> > > fast -- now it hits the floppy again.
>
> Huh - your floppy is working?
>
> Mine does not (wit
* Dr. Kelsey Hudson <[EMAIL PROTECTED]> [001004 19:06]:
> Machine:
> SPARCstation 20, 1xTMS390Z55 50MHz SuperSPARC II w/1MB SuperCACHE
> 48MB RAM, about 9G total disk space spanned over 3 drives, TGX...
Ok, if you wanna try it, snarf from the vger cvs tree or just change
DBRI_NO_INTS in drivers/s
From: [EMAIL PROTECTED]
Date:Fri, 13 Oct 2000 01:20:23 +0100 (BST)
Any of the mm gurus give the patch below a quick once over ? Is
this adequate, or is there more to this than the description
implies?
It might make more sense to just make rss an atomic_t.
Later,
David S.
More improvements/fixups to arch/i386/kernel/setup.c
Some of which are forward ports from 2.2.18pre, others
have been accumulating/missing for a while.
o Boot time 'disable_serial' option.
(Taken from Similar routine by Andrea Arcangeli)
o Inserted missing mcheck_init() call.
o Pentium IV
> 9. To Do
> * mm->rss is modified in some places without holding the
> page_table_lock (sct)
Any of the mm gurus give the patch below a quick once over ?
Is this adequate, or is there more to this than the description implies?
regards,
Dave.
--
| Dave Jones <[EMAIL PROTECTED]> htt
We really need real S3 framebuffer devices that work across many
platforms.
> It's port of patch from http://www.colonel-panic.com (for kernel 2.2.12)
> to 2.4.0-test10-pre1. It's quite useful if you have older s3 video card
> (i.e. Virge) without VBE 2.0, but it's rather tricky so it is not in
On Thu, 12 Oct 2000, David Woodhouse wrote:
> > * USB: system hang with USB audio driver {CRITICAL} (David
> >Woodhouse, Randy Dunlap, Narayan Desai)
>
> That fixes failure mode #1, in which the NMI watchdog gets triggered and
> all subsequent attempts to open /dev/audio just block.
Hi!
Unfortunatelly I couldn't apply it:
[root@iq src]# bzcat VM-global-2.2.18pre9-6.bz2 |patch -p0
patching file `VM/drivers/block/rd.c'
patching file `VM/fs/binfmt_aout.c'
patching file `VM/fs/binfmt_elf.c'
patching file `VM/fs/buffer.c'
patching file `VM/fs/coda/file.c'
patching file `VM/fs/dca
Problem:
A returned address from kmalloc() can be overwritten to a wrong place in
rpcauth_lookup_credcache() routine.
rpcauth_lookup_credcache(struct rpc_auth *auth, int taskflags)
{
...
if (!cred) {
cred = auth->au_ops->crcreate(taskflags);
}
if (cred)
rpcauth_insert_credcache(
On Thu, Oct 12, 2000 at 07:19:32PM -0400, Dan Maas wrote:
> The memory map of a user process on x86 looks like this:
>
> -
> KERNEL (always present here)
> 0xC000
> -
> 0xBFFF
> STACK
> -
> MAPPED FILES (incl. shared libs)
> 0x4000
> ---
if you aren't comfortable with dropping a lot of the 2.2.18preX stuff onto
a production box, there is also the 2.2.18pre2aa2 kernel that andrea made
which has the VM stuff. check out andrea/proposed/v2.2/2.2.18pre2 or
andrea/kernels/v2.2/2.2.18pre2aa2
unless you've made substantial updates to y
On Thu, 12 Oct 2000 11:02:50 -0400,
"Chris Swiedler" <[EMAIL PROTECTED]> wrote:
>But the kernel should be able to write directly to the screen, even if it's
>extremely minimal information. Something like how LILO does it: test the
>common hang-on-boot conditions (like wrong CPU type) and print a
On Thu, 12 Oct 2000, Krzysztof Sierota wrote:
> Our 3 machines went unresponsive, just the way you describe it. The error
> was the same. We had this on 2.2.17 and on 2.2.18pre3 , didn't try 2.2.18pre15.
> Marcelo Tosati assembled a kernel for us that had Andrea Arcangeli patches
> applied and so
It's port of patch from http://www.colonel-panic.com (for kernel 2.2.12)
to 2.4.0-test10-pre1. It's quite useful if you have older s3 video card
(i.e. Virge) without VBE 2.0, but it's rather tricky so it is not in main
tree.
URL:http://republika.pl/bkz/240t10p1-s3lfb.diff (7kB)
extremely sl
> I will use 2.95.2, so that egcs seems to not being able to build 18-preX.
egcs-1.1.2 builds 2.2.18pre. I know this because thats the compiler I use
to build it. Its also the recommended compiler. 2.95 is still 'probably works'.
In truth I think 2.95 is now at the point where if anything kernel
The memory map of a user process on x86 looks like this:
-
KERNEL (always present here)
0xC000
-
0xBFFF
STACK
-
MAPPED FILES (incl. shared libs)
0x4000
-
HEAP (brk()/malloc())
EXECUTABLE CODE
0x08048000
-
On Fri, 13 Oct 2000 01:30:57 Igmar Palsenberg wrote:
> Forget 2.96. It's a prerelease, and produces broken kernel, IF it
> produces
> them.
>
> > TIA, and sorry for the 'long long' message...
>
> Read the docs. It says what works and what doens't.
>
Thanks, I thought 2.96 was a 'real' version
On Thu, Oct 12, 2000 at 12:39:09PM -0400, Ed Taranto wrote:
> Anyone out there have any further information or insight into this?
You can check the routes in the rtcache by using route --cache. Maybe
you can see a pattern.
>
> One thing that concerns me is that rt_garbage_collect will only ma
On Thu, 12 Oct 2000, Roy C. Bixler wrote:
> I just had our mail server running 2.2.18pre15 (compiled with GCC 2.7.2.3)
> go unresponcive yesterday. The console was flooded with
> 'do_try_to_free_pages failed' messages for various processes and had to be
> hard booted to the last stable kernel, whi
** Reply to message from "Robert B. Easter" <[EMAIL PROTECTED]> on Thu,
12 Oct 2000 18:47:22 -0400
> Since installing a
> second CPU and recompiling the kernel for SMP and recompiling ALSA with
> --with-smp=yes, the sound loops. I can hear the sound, but it doesn't
> continue to play normall
Hi there,
as of devfs and devfsd Xterm seems to need suid bit set so that chown
of /dev/pts/{pts number} can be done. devpts fs does not need it.
So it is buggy devfs/devfsd or it is a feature?
The first allocation of pts number has good ownership but if it is freed
and another allocation is do
Greg KH wrote:
On Thu, Oct 12, 2000 at 08:06:46AM -0400, [EMAIL PROTECTED]
wrote:
> * USB: booting with USB compiled into
kernel causes a lot of syslog
> entries as the root hubs
are probed by all drivers (this is
> especially obnoxious as
the usb-serial drivers start up)
Fixed
I'm using ALSA sound modules with a VIA 82C686A onboard audio chip on a MSI
694D-ProA motherboard. When I only had one cpu installed and the kernel and
ALSA were compiled for non-SMP, the sound worked fine. Since installing a
second CPU and recompiling the kernel for SMP and recompiling ALSA
There's a chunky comment near the beginning of filemap_nopage() that after a test and
then following the source seems to me to be untrue:
/*
* Semantics for shared and private memory areas are different
* past the end of the file. A shared mapping past the last page
> Hi, everybody.
>
> I have a little problem when compiling new kernels. I run Mandrake 7.1
> with many many updates (its almost 7.2beta).
> Kernel 2.2.18-pre15 compiles fine under gcc-2.95.2. It is just plain
> 2.2.17 with Alan's patch to 18-pre15.
>
> I downloaded the gcc-2.96 rpms from rufus
> * USB: system hang with USB audio driver {CRITICAL} (David
>Woodhouse, Randy Dunlap, Narayan Desai)
This is necessary but not sufficient:
Index: drivers/usb/audio.c
===
RCS file: /net/passion/inst/cvs/linux/drivers/u
> Can anyone tell me which manufacture of sound cards has been the most open
> with programming information for their cards. I am looking for
> complete documents that would allow me to write my own low-latency driver
> for a particular application.
Probably the trident 4dwave
-
To unsubscribe
Hi, everybody.
I have a little problem when compiling new kernels. I run Mandrake 7.1
with many many updates (its almost 7.2beta).
Kernel 2.2.18-pre15 compiles fine under gcc-2.95.2. It is just plain
2.2.17 with Alan's patch to 18-pre15.
I downloaded the gcc-2.96 rpms from rufus, and the compila
Krzysztof Sierota <[EMAIL PROTECTED]> writes:
> Hi,
> I recently changed the kernel from 2.2.15 to 2.2.17 and added new promise 100
> card. During 3 days 2 production servers crashed 4 times and had several
> lockups when there was zillion messages like
> VM: do_try_to_free_memmory failed for XXX
On Thu, 12 Oct 2000, Timur Tabi wrote:
> Of course, you could define a pointer to be a 48-bit value, but I
> doubt that would really work.
no, x86 virtual memory is 32 bits - segmentation only provides a way to
segment this 4GB virtual memory, but cannot extend it. Under Linux there
is 3GB virt
On Wed, 11 Oct 2000, Alan Cox wrote:
The was an error reported for 2.2.17:
Oct 12 14:55:46 iq kernel: VM: do_try_to_free_pages failed for kupdate...
...
Oct 12 00:50:49 iq kernel: VM: do_try_to_free_pages failed for smbd...
Oct 12 00:50:51 iq last message repeated 226 times
...
Oct 12 00:50:47 iq
Timur Tabi writes:
> ** Reply to message from Jeff Epler <[EMAIL PROTECTED]> on Thu, 12 Oct 2000
> 13:08:19 -0500
> > What the support for >4G of memory on x86 is about, is the "PAE", Page Address
> > Extension, supported on P6 generation of machines, as well as on Athlons
> > (I think). With the
There's a test10-2 out there.
Notable change to people Cc'd on this mail: this contains the fix for the
vmalloc() and ioremap() race condition, which deletes the set_pgdir()
function and instead depends on the page table entries being distributed
to the other page directories automatically. Some
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 11, 2000 5:43 PM
>
> I've taken a look at that list, and it looks fairly obsolete, as far as
> I could tell. There is an actively maintained list which I post
> periodically to the Linux-Kernel mailing list, and whic
Hello kernel list
Can anyone tell me which manufacture of sound cards has been the most open
with programming information for their cards. I am looking for
complete documents that would allow me to write my own low-latency driver
for a particular application.
Thank you,
Daniel
On Thu, 12 Oct 2000, Torben Mathiasen wrote:
>
> We want to make sure that all hostadapters have been unregistered
> befor we pull it out of the scsi_hosts list. We do tpnt->present--
> for every hostadaper we unregister.
>
> Prior to the new init code, we'd just do something like,
>
>
On Thu, Oct 12 2000, Linus Torvalds wrote:
>
>
> On Thu, 12 Oct 2000, Torben Mathiasen wrote:
> >
> > Attached patch should fix the oops's people have been getting
> > while using /proc/scsi.
>
> This patch makes no sense. Why
>
> if (!present)
>
> when that is obviously the wrong way
Hi,
Got my hands on 2.4 using test-9 tree from fsmlabs.
Looks like for Mesquite to run it still has to have the same patch as
was made for 2.2, attached below against fsmlabs 2_3 snapshot tree
fom Oct 10.
2.4 on Mesquite shows rather wierd behavior, does not accept command line
and has a problem
** Reply to message from "Richard B. Johnson" <[EMAIL PROTECTED]> on Thu,
12 Oct 2000 15:17:15 -0400 (EDT)
> With ix86 processors in the kernel, you can create multiple segments
> and multiple page-tables.
Does the kernel provide services for this, or will I have to hack up the x86
page tables
On Thu, 12 Oct 2000, Torben Mathiasen wrote:
>
> Attached patch should fix the oops's people have been getting
> while using /proc/scsi.
This patch makes no sense. Why
if (!present)
when that is obviously the wrong way around.
I'm sure it fixes an oops - I just want to understand wh
> > Am I reading this correctly--the address of the main() function for a
> > process is guaranteed to be the lowest possible virtual address?
> >
> > chris
> >
>
> It is one of the lowest. The 'C' runtime library puts section
> .text (the code) first, then .data, then .bss, then .stack. The
> .s
On Thu, 12 Oct 2000, Timur Tabi wrote:
> ** Reply to message from Jeff Epler <[EMAIL PROTECTED]> on Thu, 12 Oct 2000
> 13:08:19 -0500
>
>
> > What the support for >4G of memory on x86 is about, is the "PAE", Page Address
> > Extension, supported on P6 generation of machines, as well as on Athlo
} Hi,
}
} > How? If you compile with egcs-2.91.66 without frame pointers on ix86 then
} > __builtin_return_address() yields garbage. Does anybody have a generic
} > solution to this problem, other than "compile with frame pointers"? Or is
} > it fixed in newer versions of gcc?
}
} Are you sur
Linus,
Attached patch should fix the oops's people have been getting
while using /proc/scsi.
Patch is against test10p1.
--
Torben Mathiasen <[EMAIL PROTECTED]>
Linux ThunderLAN maintainer
http://tlan.kernel.dk
--- linux-test10p1/drivers/scsi/scsi.c Thu Oct 12 20:18:47 2000
+++ linux/drive
Hi,
> How? If you compile with egcs-2.91.66 without frame pointers on ix86 then
> __builtin_return_address() yields garbage. Does anybody have a generic
> solution to this problem, other than "compile with frame pointers"? Or is
> it fixed in newer versions of gcc?
Are you sure? I just I trie
On Wed, Oct 11, 2000 at 09:04:07PM -0400, Alexander Viro wrote:
> On Thu, 12 Oct 2000, Tom Holroyd wrote:
>
> > Alpha DP264 (UP), SCSI, floppy
> >
> > If I do a dd if=/dev/zero of=/tmp/moo count=10, I don't see any
> > increase in buffers, as reported by vmstat. Furthermore, if I read from
** Reply to message from Jeff Epler <[EMAIL PROTECTED]> on Thu, 12 Oct 2000
13:08:19 -0500
> What the support for >4G of memory on x86 is about, is the "PAE", Page Address
> Extension, supported on P6 generation of machines, as well as on Athlons
> (I think). With these, the kernel can use >4G
On Thu, Oct 12, 2000 at 10:36:38AM -0700, Kiril Vidimce wrote:
> Allocate = malloc(). The process needs to be able to operate on >4 GB
> chunks of memory. I understand that it's only a 32 bit address space
> which is why I was surprised when I read that Linux 2.4.x will support
> upwards of 64 GB'
The attached 1-character change fixes a performance bug in
linux-2.4.0-test9 (and earlier). Without this patch, something as
simple as "cat /proc/self/maps" will read the "maps" file line by
line.
--david
--- linux-2.4.0-test9/fs/proc/array.c Fri Sep 8 14:34:59 2000
+++ lia64-kdb/fs/
>On Thu, 12 Oct 2000, Oliver Xymoron wrote:
>> On Wed, 11 Oct 2000, Kiril Vidimce wrote:
>>
>> > My primary concern is whether a process can allocate more than 4 GB of
>> > memory, rather than just be able to use more than 4 GB of physical
>> > memory in the system.
>>
>> Define allocate. T
On Wed, 11 Oct 2000, Kiril Vidimce wrote:
>
> Hi there,
>
> I am trying to find out more information on large memory support (> 4 GB)
> for Linux IA32. Is there a document that elaborates on what is supported
> and what isn't and how this scheme actually works in the kernel?
>
> My primary co
On Thu, 12 Oct 2000, Oliver Xymoron wrote:
> On Wed, 11 Oct 2000, Kiril Vidimce wrote:
>
> > My primary concern is whether a process can allocate more than 4 GB of
> > memory, rather than just be able to use more than 4 GB of physical
> > memory in the system.
>
> Define allocate. There are tr
> > > I can think of a number of uses for such a tool. For example, to read
> > > the documentation of a package before installing it on a different
> > > (Linux-based) system; or to unpack a source-rpm in order to build it
> > > with Cygwin.
> >
> > Bad idea. Most RPM'S contain specific RH pat
On Thu, 12 Oct 2000, Oliver Xymoron wrote:
> On Wed, 11 Oct 2000, Kiril Vidimce wrote:
>
> > My primary concern is whether a process can allocate more than 4 GB of
> > memory, rather than just be able to use more than 4 GB of physical
> > memory in the system.
>
> Define allocate. There are t
On Wed, 11 Oct 2000, Kiril Vidimce wrote:
> My primary concern is whether a process can allocate more than 4 GB of
> memory, rather than just be able to use more than 4 GB of physical
> memory in the system.
Define allocate. There are tricks you can play, but userspace is still a
flat 32-bit a
On 2000/10/12, Igmar Palsenberg wrote:
>
> > I can think of a number of uses for such a tool. For example, to read
> > the documentation of a package before installing it on a different
> > (Linux-based) system; or to unpack a source-rpm in order to build it
> > with Cygwin.
>
> Bad idea. Most
Yong Chi wrote:
> Hopefully this will do for SMP locks. =)
You must not hold a spinlock across put_user - instead you must copy the
get_queued_event(user) into a local variable, spinunlock and then copy
it to userspace.
Compare drivers/sbus/char/sunkbd.c, function kbd_read from 2.2 and 2.4:
2.2
Take 2 based on semaphore -)
Jan-Simon Pendry wrote:
> holding a spin lock across a (potential) sleep is a bug - it can
> lead to deadlock.
>
> jan-simon.
>
> Jakub Jelinek wrote:
> >
> > On Thu, Oct 12, 2000 at 11:38:11AM -0400, Yong Chi wrote:
> > > Hopefully this will do for SMP locks. =)
>
> I can think of a number of uses for such a tool. For example, to read
> the documentation of a package before installing it on a different
> (Linux-based) system; or to unpack a source-rpm in order to build it
> with Cygwin.
Bad idea. Most RPM'S contain specific RH patches, most of them being
On Thu, Oct 12 2000, Young-Ho Cha wrote:
> I have adaptec 20160 scsi adapter and plextor 32x cdrom.
>
> I played audio cd with gtcd(gnome app) and eject cdrom with gtcd(eject button)
>
> , gtcd died and dmesg out...
Eek, bad bug. Try this patch.
--
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs
On Thu, 12 Oct 2000, Dag Bakke wrote:
>
> Linus,
> I realized there was one more test to do before deeming the hardware sane.
>
> PCMCIA (16-bit) in my laptop is tested and works fine with three different
> types of cards.
> Another Xircom card behaved just the same (non-functional) in my lato
On Thu, 12 Oct 2000, Jeff Garzik wrote:
> "Richard B. Johnson" wrote:
> > --- linux-2.2.17/drivers/scsi/BusLogic.h.orig Thu Oct 12 11:22:44 2000
> > +++ linux-2.2.17/drivers/scsi/BusLogic.hThu Oct 12 11:47:07 2000
> > @@ -1509,6 +1509,7 @@
> > void BusLogic_AcquireHostAdapterLock(BusLo
Note to linux-kenrel readers: This discussion is the Nth attempt to find
a solution to handle both legacy IOs and PCI IOs on machines with several
IO busses memory mapped at different locations in the CPU space.
>No please, is there anybody bloat-conscious on this damned list ? Burying
>more and
Note to linux-kenrel readers: This discussion is the Nth attempt to find
a solution to handle both legacy IOs and PCI IOs on machines with several
IO busses memory mapped at different locations in the CPU space.
>No please, is there anybody bloat-conscious on this damned list ? Burying
>more and
> > every CPU to avoid slowdowns. So that if you set that eth0's
> > IRQ will be handled by CPU1, the MTRRs of CPU1 will be set
> > accordingly, and the other CPUs will not care about eth0,
> > so they do not need eth0's MTRR settings.
>
> A little question. Why do we want to bind irq of eth0 to
Sudhindra Herle, you write:
> I just got two separate crashes using 2.2.17 and reiserfs.
You should probably contact the reiserfs mailing list because reiserfs
is not in the official kernel.
> I have lost faith in reiserfs. So, I'll rebuild the kernel and move back
> to EXT2.
Oh well...
Cheers
I'm running kernel version 2.2.14 as a firewall with moderately high load.
After a few hours, i start getting "dst cache overflow" log messages. That
apparently comes from rt_garbage_collect in route.c
I have seen a few discussions about this in the archives, but nothing ever
seemed too conclus
"Richard B. Johnson" wrote:
> --- linux-2.2.17/drivers/scsi/BusLogic.h.orig Thu Oct 12 11:22:44 2000
> +++ linux-2.2.17/drivers/scsi/BusLogic.hThu Oct 12 11:47:07 2000
> @@ -1509,6 +1509,7 @@
> void BusLogic_AcquireHostAdapterLock(BusLogic_HostAdapter_T *HostAdapter,
>
On Thu, Oct 12, 2000 at 08:06:46AM -0400, [EMAIL PROTECTED] wrote:
> * USB: booting with USB compiled into kernel causes a lot of syslog
>entries as the root hubs are probed by all drivers (this is
>especially obnoxious as the usb-serial drivers start up)
Fixed in test9. If a
On Thu, 12 Oct 2000, Matthias Andree wrote:
> > Note that the sync-rate of target 6, the device I added, has been
> > turned down to try to eliminate any hardware problems. Also note
> > that the entire drive has been read/written with the BusLogic BIOS
> > diagnostic setup utility.
>
> That BIO
holding a spin lock across a (potential) sleep is a bug - it can
lead to deadlock.
jan-simon.
Jakub Jelinek wrote:
>
> On Thu, Oct 12, 2000 at 11:38:11AM -0400, Yong Chi wrote:
> > Hopefully this will do for SMP locks. =)
>
> Holding a spinlock for this long (especially when you might sleep t
On Thu, Oct 12, 2000 at 11:38:11AM -0400, Yong Chi wrote:
> Hopefully this will do for SMP locks. =)
Holding a spinlock for this long (especially when you might sleep there in two
places (interruptible_sleep_on, put_user)) is basically a bad idea.
spinlocks are designed to be holded only for sho
Hopefully this will do for SMP locks. =)
Todo list also said that on UP, sleep_on() use is unsafe. It uses
"interruptible_sleep_on()" and "wake_up_interruptible()" calls. Are they
not safe on UP?
Thanks
--- ds.c.bakWed Oct 11 13:05:16 2000
+++ ds.cThu Oct 12 11:25:20 2000
@@ -9
>> - I mean, it's legal to include linux/fs.h from userland,
>
>Everybody who thinks so will be severely disappointed.
Ok, so if it's not, then I have to fix that app. Thanks.
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROT
On Thu, 12 Oct 2000, Keith Owens wrote:
> If anything is going to detect the mismatch and complain, it has to be
> the boot loader, after uncompressing and before entering the kernel
> proper.
Perhaps we can add the processor type to linux_banner and print it from
setup.S.
--
"Love the dolphin
"Maciej W. Rozycki" wrote:
>
> On Fri, 13 Oct 2000, Andrew Morton wrote:
>
> > > Oct 9 17:29:02 fwintern kernel: eth0: Interrupt posted but not
> > > delivered -- IRQ blocked by another device?
> >
> > This is the infamous APIC bug. I have about ten reports of this over a
> > four-month period
On Thu, Oct 12, 2000 at 05:00:49PM +0200, Benjamin Herrenschmidt wrote:
> - I mean, it's legal to include linux/fs.h from userland,
Everybody who thinks so will be severely disappointed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Francois romieu wrote:
> token = (unsigned long)ioremap(pci_resource_start(pdev, 0),
> pci_resource_len(pdev, 0));
Looks great except for one small point -- we have been going through
drivers cleaning up where they start casting like this. You sh
On Wed, 11 Oct 2000, Linus Torvalds wrote:
>
> On Thu, 12 Oct 2000, Benjamin C.R. LaHaise wrote:
> >
> > Note the fragment above those portions of the patch where the
> > pte_xchg_clear is done on the page table: this results in a page fault
> > for any other cpu that looks at the pte while it
1 - 100 of 171 matches
Mail list logo
