Hello!
0x44 is the primary bus number of the host bridge, and 0x45 is the
subordinate bus number for the bridge. Just like a PCI-PCI bridge, but
different :) Since there are two CNB30 functions, each has unique values
for this. The primary bus of the second bridge must be the subordinate
Hello!
The ServerWorks peer bus problem is still present on the 2.4.1 kernel. The
problem stems from the fact that there can be more than one secondary bus
for a given north bridge. For example, the Compaq Proliant DL580 has two
"root busses" coming off of a single north bridge. I'm
hi
Linux Enthusiasts !
I am a newbie to RedHat Linux and the partitioning stuff...
I have an AMD Athlon 1.2 Ghz processor with an IBM deskstar 45 GB h/disk
the system already came with Windows 98 and then I installed Windows 2000
and Red hat Linux 7.0
However I am not able to boot
David S. Miller wrote:
- hash = hash ^ (hash D_HASHBITS) ^ (hash D_HASHBITS*2);
+ hash = hash ^ (hash D_HASHBITS) ^
+ (hash (D_HASHBITS+(D_HASHBITS/2)));
Two comments:
1. The inode-cache has the exact same problem, but it'll require a lot
of RAM to run into it.
Hi Christoph,
While testing Jens' loop-4 patch (and not being able to find
any way to lock it up), I stumbled onto a strange behavior.
I set up an interleaved swap with one swap partition, and one
swapfile in a loopback mounted reiserfs - populated tmpfs with
a kernel tree and did hefty make -j
Hi Mike,
On Thu, 8 Feb 2001, Mike Galbraith wrote:
Hi Christoph,
While testing Jens' loop-4 patch (and not being able to find
any way to lock it up), I stumbled onto a strange behavior.
I set up an interleaved swap with one swap partition, and one
swapfile in a loopback mounted reiserfs
Mitchell Blank Jr writes:
1. The inode-cache has the exact same problem, but it'll require a lot
of RAM to run into it. The buffer and page caches don't have the
same problem.
Yep, fix attached. You just need 1GB ram to hit that case.
2. Given that D_HASHBITS is not a
There seems to be some movement in the driver and the latest one
is not working for me (again), so I'm giving a subjective status report
for the versions I have tried lately:
Working epic100 drivers:
- 2.4.0
- 2.4.0-ac9
Broken epic100 drivers:
- 2.4.0-ac4
- 2.4.1-ac2
- 2.4.1-ac4
I have
On Wed, Feb 07, 2001 at 11:59:05PM -0800, Ion Badulescu wrote:
I don't think it fixes *this* bug. However, the bug workaround effectively
reinitializes the chip, so it might serve as a generic 'reset and try
again' kind of workaround. In that case, we might as well enable it
Btw, GFS (http://www.sistina.com) also needs 64bit inode
number support. They offer a patch called inode.patch that is a
backport of the 2.4 code.
Pedro
On 8 Feb 2001, at 0:15, Andi Kleen wrote:
Tigran Aivazian [EMAIL PROTECTED] writes:
Hi,
Under 2.4.1, after a little bit of
On Thu, Feb 08, 2001 at 03:00:10AM -0800, Ion Badulescu wrote:
At the same time, the /var/log/messages receives thousands of messages from the
NET: subsystem.
So what _were_ those messages? Can you post them?
No I can't because they were suppressed by the syslogd (DOS protection), only
On Tue, Feb 06, 2001 at 10:14:21AM -0800, Linus Torvalds wrote:
I will claim that you CANNOT merge at higher levels and get good
performance.
Sure, you can do read-ahead, and try to get big merges that way at a high
level. Good for you.
But you'll have a bitch of a time trying to merge
On Thu, 8 Feb 2001 20:15:39 +0900, Augustin Vidovic [EMAIL PROTECTED] wrote:
So what _were_ those messages? Can you post them?
No I can't because they were suppressed by the syslogd (DOS protection), only
their number being reported (several thousands every few seconds).
syslogd does not
hi!
I've created a patch for kernel 2.4.1 that adds some fancy options for
the framebuffer console driver concerning the boot logo.
I've added logo animation and logo centering.
People may find this not very useful but nice to look at. :-)
Long time ago I joked that win2000 will have
Hi!
I understand that both ext3fs and
reiserfs will try to fix corrupt filesystems (or at least filesystems
with unprocessed log entries) in-place even if they're mounted
read-only. Clearly, virtual replay means more work, but -- just for
fun -- here are some cases in which it might
On 8 Feb 01 at 6:04, Mikael Pettersson wrote:
ordering and offsets in processor.h and head.S. The resulting
kernel works ok on my UP P6.
(Petr: can you check that it still works on your K7?)
I'll try.
I have another question for UP APIC NMI: As I reported some time ago,
if performance
Hi!
Reading write(2):
EAGAIN Non-blocking I/O has been selected using O_NONBLOCK and there was
no room in the pipe or socket connected to fd to write the data
immediately.
I see no reason why "aio function have to block waiting for
Hi!
Its arguing against making a smart application block on the disk while its
able to use the CPU for other work.
There are currently no other alternatives in user space. You'd have to
create whole new interfaces for aio_read/write, and ways for the kernel to
inform user space that
Peter Horton wrote:
On Thu, Feb 08, 2001 at 03:35:00AM +0100, Udo A. Steinberg wrote:
After upgrading my Asus A7V Bios from 1003 to 1005D
Similiar problems here after my upgrade to 1005D.
you are not booting from a floppy, are you ?
--
Hello,
I've hit a Kernel BUG with the combination of nonstandart kernel
modules. So dear linux-kernel readers, this bug report may or may not
apply to the standart kernel. But if you have any comments, please CC
me.
We use the dolphinics psb66 clustering card and a GForce 256 graphics
card.
On Thu, Feb 08, 2001 at 03:26:51AM -0800, Ion Badulescu wrote:
syslogd does not suppress messages, it suppresses *identical* messages.
So what was the *first* message logged by syslogd, the one followed by
"last message repeated XXX times"?
It's not "last message repeatead XXX times", it's :
I think it is better to remove statements about rescue discs from patch
because rescue discs are often interactive systems and needs messages even
more than desktops.
And statement about saving disk space by removing messages can irritate
some kernel people.
I write it now a little bit
On Thu, 8 Feb 2001, Augustin Vidovic wrote:
This suppression of thousands of lines was described as a DOS-protection
in the docs I read.
Still, there should be something before these suppressed messages started.
With my patch, the test becomes (eeprom[3] 0x03), which is not null
for every
On Thu Feb 08, 2001 at 03:06:27 -0800, Andre Hedrick wrote:
Have you got a hack for 2.2.18/19x ??
I do not have problems with 2.2.x Kernels here. They see all the PCI
devices just fine.
Adam
--
Adam [EMAIL PROTECTED]
Lackorzynski http://a.home.dhs.org
-
To
It looks like ac6 (which I believe includes the patch you posted) is
still a no-go with 7892. The boot halts and it just prints this once a
second:
(SCSI0:0:3:1) Synchronous at 160 Mbyte/sec offset 31
(SCSI0:0:3:1) CRC error during data in phase
(SCSI0:0:3:1) CRC error in intermediate CRC
On Thu, Feb 08, 2001 at 03:53:10AM -0800, Ion Badulescu wrote:
Still, there should be something before these suppressed messages started.
No, sorry, but absolutely nothing since the boot.
It goes like this:
bit0 = 1 means the workaround may be omitted when operating at 10 Mbit
bit1 = 1
I'm not sure whether this is related to the ominous ps/2 mouse bug
you have been chasing, but this problem is 100% reproducible and
very annoying.
snip
I'm also seeing a ps/2 mouse bug, with 2.4.0-pre5 (I think) on a
CS433 (486/33 laptop)
Freezes after some time in X, killing keyboard.
On Thu, 8 Feb 2001, Mikael Pettersson wrote:
No, poking into MSRs not explicitly defined on the current CPU is
inherently unsafe. I have several x86 CPU data sheets here in front
of me which say the same thing: "Don't write to undocumented MSRs."
Your point is right -- the problem are not
/me wrote:
Louis Garcia [EMAIL PROTECTED] wrote:
I'm using XFree86-4.0.1 with the nv driver. You are right, it's ver
0.9.2 for the fb.
Where can I get the patch? Should I upgrade to XFree86-4.0.2?
Not yet, we have to write that patch first... :) I'll grab an XFree
source soon.
On Wed, 7 Feb 2001, Mr. James W. Laferriere wrote:
Date: Wed, 7 Feb 2001 04:43:19 -0800 (PST)
From: Mr. James W. Laferriere [EMAIL PROTECTED]
To: Matt Bernstein [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: increasing the 512 process limit at
OK, talked with someone who knows a little more about this than i do.
According to him, one reason I may be getting these errors is due to the
fact that the HPT370 controller is using IRQ18 which falls in the APIC
extended IRQ range (16 - 31).
If this is a problem is there a work-around? I
In article [EMAIL PROTECTED] you wrote:
It looks like support for this is available at:
http://opensource.compaq.com/sourceforge/project/?group_id=13
If that server would actually work - everytime I try to access it
it is down. (Not even PINGable).
Christoph
--
Of course it
Hi
I am a relatively newb in the kenel programming. I am using the
function "schedule_timeout" for sleeping for some time. But in some cases
the function returns after the specified timeout but in some instance it
returns immediately, without decrementing the timeout value passed as the
On Thu, 8 Feb 2001, Pavel Machek wrote:
I've created a patch for kernel 2.4.1 that adds some fancy options for
the framebuffer console driver concerning the boot logo.
I've added logo animation and logo centering.
People may find this not very useful but nice to look at. :-)
Long time ago I
I am a relatively newb in the kenel programming. I am using the
function "schedule_timeout" for sleeping for some time. But in some cases
the function returns after the specified timeout but in some instance it
returns immediately, without decrementing the timeout value passed as the
Hi,
On Thu, Feb 08, 2001 at 12:15:13AM +0100, Pavel Machek wrote:
EAGAIN is _not_ a valid return value for block devices or for regular
files. And in fact it _cannot_ be, because select() is defined to always
return 1 on them - so if a write() were to return EAGAIN, user space would
Hello Matti ,
On Thu, 8 Feb 2001, Matti Aarnio wrote:
...snip...
Answer to the self-education question above:
The NAME fields in usual BIND systems get appended the current $ORIGIN
string value when the data in the field does not end with a dot:
Wrong: IN MX 10
I hope this is OK, comments more than welcome
--- Documentation/DocBook/kernel-hacking.tmpl.old Tue Feb 6 20:06:15 2001
+++ Documentation/DocBook/kernel-hacking.tmpl Tue Feb 6 21:14:42 2001
@@ -336,6 +336,11 @@
/para
para
+ If all your routine does is read or write some
On Thu, 8 Feb 2001, Stephen C. Tweedie wrote:
snip
How do you write high-performance ftp server without threads if select
on regular file always returns "ready"?
Select can work if the access is sequential, but async IO is a more
general solution.
Even async IO (ie
Hello,
I have dual PIII 800 machine running as mail server on DAC 960 RAID
reiserfs comming with 2.4.1kernel.
Under very high loads I get following messages in my kernel log:
kernel: vs-13060: reiserfs_update_sd: stat data of object [7906789
7906806 0x0 SD](nlink == 1) not found (pos 23)
On Thu, 8 Feb 2001, Pavel Machek wrote:
Hi!
Its arguing against making a smart application block on the disk while its
able to use the CPU for other work.
There are currently no other alternatives in user space. You'd have to
create whole new interfaces for aio_read/write, and ways
Ok it seems not important to have a nice boot process but each time you show a linux
machine to a M$ normal user (normal = not a programmer) his first reaction is
something like ""what are all these strange output lines?". And it's the first thing
that keep Windows user in the dark side.
This patch contains two CPU detection bug fixes:
- arch/i386/kernel/apic.c:detect_init_APIC():
This is being run before identify_cpu(), so the x86_vendor
field wasn't properly defined. It only _seemed_ to work before
because uninitialised == 0 == X86_VENDOR_INTEL.
The basic CPU detection
Hi!
So you consider inability to select() on regular files _feature_?
select on files is unimplementable. You can't do background file IO the
same way you do background receiving of packets on socket. Filesystem is
synchronous. It can block.
It can be a pretty serious problem with slow
On Thu, Feb 08 2001, Alan Cox wrote:
total request sizes. I would rather fix this limitation then, and
would also be interested to know if any of the (older) SCSI drivers
have such limitations too.
And some new ones. One of my i2o scsi controllers has that problem.
Ok thanks, I'll do
On Tue, 6 Feb 2001, Linus Torvalds wrote:
There are currently no other alternatives in user space. You'd have to
create whole new interfaces for aio_read/write, and ways for the kernel to
inform user space that "now you can re-try submitting your IO".
Could be done. But that's a big thing.
I have had great success with the 2.4.x series of kernels so far. I am
using 2.4.1. However, with 2.4.0 and 2.4.1 (haven't tried the pre for 2
yet), I have been having tulip networking cards up the wazoo. I turn my
switch off and back on and that seems to help.
Is this a hardware problem or
On Thu, 8 Feb 2001, Ben LaHaise wrote:
snip
(besides, latency would suck. I bet you're better off waiting for the
requests if they are all used up. It takes too long to get deep into the
kernel from user space, and you cannot use the exclusive waiters with its
anti-herd behaviour etc).
Hi,
friend of mine bought g400 on my recommendation, and unfortunately,
mga drm driver did not worked for me. I tracked it down to missing
pci_enable_device and pci_set_master in mga* driver. But even after
looking more than hour into that code I have no idea where I should
place this call, as
On Thu, 8 Feb 2001, Marcelo Tosatti wrote:
On Thu, 8 Feb 2001, Ben LaHaise wrote:
snip
(besides, latency would suck. I bet you're better off waiting for the
requests if they are all used up. It takes too long to get deep into the
kernel from user space, and you cannot use the
How do you write high-performance ftp server without threads if select
on regular file always returns "ready"?
Select can work if the access is sequential, but async IO is a more
general solution.
Even async IO (ie aio_read/aio_write) should block on the request queue if
its full
On Thu, 8 Feb 2001, Mikulas Patocka wrote:
How do you write high-performance ftp server without threads if select
on regular file always returns "ready"?
Select can work if the access is sequential, but async IO is a more
general solution.
Even async IO (ie
On Thu, Feb 08 2001, Mikulas Patocka wrote:
Even async IO (ie aio_read/aio_write) should block on the request queue if
its full in Linus mind.
This is not problem (you can create queue big enough to handle the load).
Well in theory, but in practice this isn't a very good idea. At some
On Thu, Feb 08, 2001 at 07:53:55AM -0500, you [Doug Ledford] claimed:
Ville Herva wrote:
It looks like ac6 (which I believe includes the patch you posted) is
still a no-go with 7892. The boot halts and it just prints this once a
second:
(SCSI0:0:3:1) Synchronous at 160 Mbyte/sec
On Thu, 8 Feb 2001, Petr Vandrovec wrote:
So it came to my mind - why (on K7 we easy can, as counter has 48 bits)
we do not reload NMI watchdog in each timer interrupt with 5sec timeout,
and if we receive even one NMI, we are locked up? It should increase
performance, as we'll do same number
On Thu, 8 Feb 2001, Francois Romieu wrote:
Working epic100 drivers:
- 2.4.0
- 2.4.0-ac9
Could you give a look at ac12 (fine here) ?
No, does not work, same problem.
Arnd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, 7 Feb 2001, Linus Torvalds wrote:
On Wed, 7 Feb 2001, Hugh Dickins wrote:
None of those optimizes this: I believe the semantics of "||" (don't
try next test if first succeeds) forbid the optimization "|" gives?
No. The optimization is entirely legal - but the fact that
On Thu, 8 Feb 2001, osamu wrote:
someone knows a good sendmail mailing list ? active like this one ?
I doubt it, if only because sendmail wouldn't be able to
handle the load.
(yeah, I know it's off-topic; but I couldn't resist this one)
cheers,
Rik
--
Linux MM bugzilla:
On Thu, 8 Feb 2001, Mikulas Patocka wrote:
The problem is that aio_read and aio_write are pretty useless for ftp or
http server. You need aio_open.
Could you explain this?
If the server is sending many small files, disk spends huge amount time
walking directory tree and seeking
On Thu, Feb 08, 2001 at 04:24:23PM +, Hugh Dickins wrote:
On Wed, 7 Feb 2001, Linus Torvalds wrote:
On Wed, 7 Feb 2001, Hugh Dickins wrote:
None of those optimizes this: I believe the semantics of "||" (don't
try next test if first succeeds) forbid the optimization "|" gives?
Switching from kernel 2.2.18 to 2.4.0 I found that my serial ports work no
more. And while using serial mouse it is quite ugly situation.
Some infos:
- QDI PII440BX B-1 motherboard
- 2 COMs + 1 internal modem - requested state:
/dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
/dev/ttyS1 at 0x02f8 (irq
I'm not sure about the mga source, but you can enable busmaster manually
as root. See the dri-devel list for more. I can't remember the exact
message off hand. THere was also some discussion of this last week I
think.
Alex
Hi,
friend of mine bought g400 on
This is actually a repost of a problem that received few serious replies
(IMNSHO).
Basically 2.4.0 detects 192 MB(maybe 191, but big whoop) of memory. This
is correct. However, 2.4.1-ac6 (as did Linus-blessed 2.4.1) detects 64.
The problem is simple. 2.4.1 and later for some reason uses
On Thu, 8 Feb 2001, David Weinehall wrote:
Well, after all, it's debugging code, and the code now is easy to read.
Your code, while more efficient, isn't. I think that clarity takes
priority over efficiency in non-critical code such as debugging
code. Of course, this is my personal
On Thu, 8 Feb 2001, Mikulas Patocka wrote:
You need aio_open.
Could you explain this?
If the server is sending many small files, disk spends huge
amount time walking directory tree and seeking to inodes. Maybe
opening the file is even slower than reading it
Not if you have a big
On Thu, 8 Feb 2001, Hugh Dickins wrote:
On Thu, 8 Feb 2001, David Weinehall wrote:
Well, after all, it's debugging code, and the code now is easy to read.
Your code, while more efficient, isn't. I think that clarity takes
priority over efficiency in non-critical code such as debugging
On Thu, 8 Feb 2001, Hugh Dickins wrote:
On Wed, 7 Feb 2001, Linus Torvalds wrote:
On Wed, 7 Feb 2001, Hugh Dickins wrote:
None of those optimizes this: I believe the semantics of "||" (don't
try next test if first succeeds) forbid the optimization "|" gives?
No. The
On Thu, 8 Feb 2001, Rik van Riel wrote:
On Thu, 8 Feb 2001, Mikulas Patocka wrote:
You need aio_open.
Could you explain this?
If the server is sending many small files, disk spends huge
amount time walking directory tree and seeking to inodes. Maybe
opening the file is even
I wasn't talking about the drm driver I was talking about programming
the PCI controller directly using setpci 1.0.0 or some such
command, I can't remember off hand. Which turns on busmastering if it
is off for a particular device.
Alex
Jeff Hartmann wrote:
Alex Deucher wrote:
I'm
"Richard B. Johnson" wrote:
[snip]
Another problem with 'volatile' has to do with pointers. When
it's possible for some object to be modified by some external
influence, we see:
volatile struct whatever *ptr;
Now, it's unclear if gcc knows that we don't give a damn about
the
fast_clear_page() uses mmx instructions for clearing a page, what about
using sse instructions?
sse instructions can store 128 bit in one instruction, mmx only 64 bit.
On a Pentium III it isn't faster, but it should be faster on a Pentium
4.
I've written a user space test app - could someone
On 8 Feb 01 at 12:15, Alex Deucher wrote:
I wasn't talking about the drm driver I was talking about programming
the PCI controller directly using setpci 1.0.0 or some such
command, I can't remember off hand. Which turns on busmastering if it
is off for a particular device.
OK.
In article [EMAIL PROTECTED] you wrote:
fast_clear_page() uses mmx instructions for clearing a page, what about
using sse instructions?
sse instructions can store 128 bit in one instruction, mmx only 64 bit.
the sse FP registers might be lossy. On my athlon, the in-kernel mmx
functions are
Petr Vandrovec wrote:
On 8 Feb 01 at 12:15, Alex Deucher wrote:
I wasn't talking about the drm driver I was talking about programming
the PCI controller directly using setpci 1.0.0 or some such
command, I can't remember off hand. Which turns on busmastering if it
is off for a
Francois romieu wrote:
The Wed, Feb 07, 2001 at 10:48:17PM -0500, Jeff Garzik wrote :
[...]
diff -urN --exclude-from=/home/davej/.exclude linux/drivers/net/epic100.c
linux-dj/drivers/net/epic100.c
--- linux/drivers/net/epic100.c Wed Feb 7 21:55:56 2001
+++
On Thu, 8 Feb 2001, Pavel Machek wrote:
There are currently no other alternatives in user space. You'd have to
create whole new interfaces for aio_read/write, and ways for the kernel to
inform user space that "now you can re-try submitting your IO".
Why is current select() interface
On Thu, 8 Feb 2001, Stephen Wille Padnos wrote:
"Richard B. Johnson" wrote:
[snip]
Another problem with 'volatile' has to do with pointers. When
it's possible for some object to be modified by some external
influence, we see:
volatile struct whatever *ptr;
Now, it's
[EMAIL PROTECTED] (Matti Aarnio) writes:
NSes and MXes must ALWAYS point to NAMEs with A//A6 records for
them, specifically those names MUST NOT be CNAMEs. With NSes the
NS: must not
MX: should not
...stickler for details. ;-)
Henning
--
Dipl.-Inf. (Univ.)
On Thu, 8 Feb 2001, Martin Dalecki wrote:
But you'll have a bitch of a time trying to merge multiple
threads/processes reading from the same area on disk at roughly the same
time. Your higher levels won't even _know_ that there is merging to be
done until the IO requests hit the wall
On Thu, 8 Feb 2001, Marcelo Tosatti wrote:
On Thu, 8 Feb 2001, Stephen C. Tweedie wrote:
snip
How do you write high-performance ftp server without threads if select
on regular file always returns "ready"?
Select can work if the access is sequential, but async IO is a more
Jeff Hartmann wrote:
Petr Vandrovec wrote:
On 8 Feb 01 at 12:15, Alex Deucher wrote:
I wasn't talking about the drm driver I was talking about programming
the PCI controller directly using setpci 1.0.0 or some such
command, I can't remember off hand. Which turns on
"Richard B. Johnson" wrote:
On Thu, 8 Feb 2001, Stephen Wille Padnos wrote:
"Richard B. Johnson" wrote:
[snip]
Another problem with 'volatile' has to do with pointers. When
it's possible for some object to be modified by some external
influence, we see:
volatile
On Thu, Feb 08, 2001 at 02:41:19PM +0300, Ivan Kokshaysky wrote:
- Don't trust IRQs assigned by ARC console on ruffian any more;
use interrupt routing table provided by [EMAIL PROTECTED] instead.
This fixes cards reporting bogus interrupt pin (ES1969).
Oh cool. I think this was the only
On 8 Feb 01 at 13:14, Alex Deucher wrote:
Jeff Hartmann wrote:
Petr Vandrovec wrote:
It does not use dynamic DMA mapping, because it doesn't do PCI DMA at
all. It uses AGP DMA. Actually, it shouldn't be too hard to get it to
work on the Alpha (just a few 32/64 bit issues probably.)
Arjan van de Ven wrote:
In article [EMAIL PROTECTED] you wrote:
fast_clear_page() uses mmx instructions for clearing a page, what about
using sse instructions?
sse instructions can store 128 bit in one instruction, mmx only 64 bit.
the sse FP registers might be lossy.
I thought that
On Thu, 8 Feb 2001, Rik van Riel wrote:
On Thu, 8 Feb 2001, Mikulas Patocka wrote:
You need aio_open.
Could you explain this?
If the server is sending many small files, disk spends huge
amount time walking directory tree and seeking to inodes. Maybe
opening the file is even
christophe barbe wrote:
Ok it seems not important to have a nice boot process but each time you show a linux
machine to a M$ normal user (normal = not a programmer) his first reaction is
something like ""what are all these strange output lines?". And it's the first thing
that keep Windows
There is preliminary support for pcigart in the dri tree. I believe
some people have had some success with it.
Alex
Petr Vandrovec wrote:
On 8 Feb 01 at 13:14, Alex Deucher wrote:
Jeff Hartmann wrote:
Petr Vandrovec wrote:
It does not use dynamic DMA mapping, because it doesn't
The latest LKCD (Linux Kernel Crash Dumps) patches/RPMs/etc. are
available for download for linux-2.4.{0,1} kernels. You can get
LKCD from:
http://oss.sgi.com/projects/lkcd/download/current/
Please E-mail [EMAIL PROTECTED] if you have any questions/problems.
Thanks.
--Matt
-
To
On Thu, 8 Feb 2001, Petr Vandrovec wrote:
On 8 Feb 01 at 13:14, Alex Deucher wrote:
Jeff Hartmann wrote:
Petr Vandrovec wrote:
It does not use dynamic DMA mapping, because it doesn't do PCI DMA at
all. It uses AGP DMA. Actually, it shouldn't be too hard to get it to
work on
Hi,
I was trying out a modem on RedHat 7 running kernel 2.2.16 and when trying
to upload a file via ftp I get an OOPS.
I am using pppd version 2.4.0 on a Pentium III 450 with 128MB of RAM.
Here is the output of kysymoops:
[root@cpagano_redhat7 cpagano]# ksymoops oops.feb8.txt -m
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.1-ac7
o Rebalance the 2.4.1 VM (Rik van Riel)
| This should make things feel a lot faster especially
| on small boxes .. feedback to Rik
o Silence osf syscall error printk
Hello all
I can not get sound working on a computer with a Gigabyte
GA-7ZX mainboard (KT133 chipset). Is this a known problem?
I have attached some config info. Mail me for further details.
Thanks in advance,
Martin Braun
--
On Thu, 8 Feb 2001, Stephen Wille Padnos wrote:
"Richard B. Johnson" wrote:
On Thu, 8 Feb 2001, Stephen Wille Padnos wrote:
"Richard B. Johnson" wrote:
[snip]
Another problem with 'volatile' has to do with pointers. When
it's possible for some object to be modified by some
two mistakes:
a) [EMAIL PROTECTED], not veritas.com! (it was pine, not me -- default
domain etc :)
b) it was ac6 which fixed it, not ac7 (but I am running ac7)
On Thu, 8 Feb 2001, Tigran Aivazian wrote:
Doug,
I confirm that ac7 fixed all the aic7xxx problems on my machine.
Thanks,
Hello!
Here is a patch which may not solve the underlying
This does not. refcnt cannot be 1 at this point.
assuming that the latter messages aren't serious?
They are fatal. Machine must be rebooted after them.
I hope the networking gurus can find the real bugs here.
Well, someone
Doug,
I confirm that ac7 fixed all the aic7xxx problems on my machine.
Thanks,
Tigran
-
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/
In article [EMAIL PROTECTED],
Martin Mares [EMAIL PROTECTED] wrote:
What leads you to your belief it's correct? The lspci dump Adam has sent
to the list shows that there's something utterly wrong with our understanding
of the ServerWorks config registers -- they seem to say that the primary
bus
In article [EMAIL PROTECTED],
Tony Finch [EMAIL PROTECTED] wrote:
Dan Kegel [EMAIL PROTECTED] wrote:
Tony, are people using the TCP_NOPUSH define as a way to detect
the presence of T/TCP support?
No, MSG_EOF is the right way to do that.
However, I think ank is at least partially correct:
Hi,
On Thu, Feb 08, 2001 at 03:52:35PM +0100, Mikulas Patocka wrote:
How do you write high-performance ftp server without threads if select
on regular file always returns "ready"?
No, it's not really possible on Linux. Use SYS$QIO call on VMS :-)
Ahh, but even VMS SYS$QIO is
1 - 100 of 395 matches
Mail list logo
