Hi,
I'm running kernel 2.4.0 on Redhat 7.0. I tried to get direct
rendering running (it failed, but that's another story). Today I
noticed something strange in /proc: dri appears there 4 times.
ls /proc:
...
-r--r--r--1 root root0 Jan 16 08:57 dma
dr-xr-xr-x3 root
Hi,
2.4.0ac9 still kills the mouse on this machine. dmesg is attached.
Something I find interesting is that the PCMCIA bridge is on IRQ12.
We can't change the mouse or the PCMCIA bridges' interrupt.
I'll be happy to provide additional info.
Regards,
Igmar
Jan 16
I get this message when logging into a box via ssh.
the box is running 2.4 Kernel with devfsd installed on debian potato.
I have a *hunch* that this may be to do with devfsd, and the fact that devfsd
is not creating the /dev/pts/x files correctly (or in a timely manner)
to prove this, I check
When running 'quotaon -a' I get message 'quotaon: using /quota.user on
/dev/hdc3: Invalid argument'. This occurs at least with 2.4.0-ac4 and
2.4.0-ac9, but not with 2.4.0.
_
Get Your Private, Free E-mail from MSN Hotmail at
On Tue, 16 Jan 2001, Vlad Bolkhovitine wrote:
> > My box thinks quite highly of that patch fwiw, but insists that he needs
> > to apply Jens Axboes' blk patch first ;-) (Not because of tiobench)
>
> New data:
>
> 2.4.1pre3 + Marcelo's patch
>
>File Block Num Seq ReadRand Read
Under 2.4.0-ac4 I find lots of mentions of the Sangoma S514 PCI Multiprotocol
Wide Area Networking card in
drivers/net/wan/sdla*
But in Documentation/Configure.help under CONFIG_VENDOR_SANGOMA I only see
mention of the S502E(A), S503 and S508. These same cards are listed in
Hi:
After diging around for some problems (shutdown/unmount related) I found
that some processes where hidden from ps, pidoff, ls /proc, etc.
A strace reveled that:
open("/proc", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 7
fstat(7, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
fcntl(7, F_SETFD,
Hello,
I got this in my logs:
ip_conntrack: maximum limit of 16368 entries exceeded
what does this mean, I know i can change the limits in
/proc/sys/net/ipv4/ip_conntrack_max, but I want to know what this is for.
P.S. I looked into linux/Documentation but did not find any mention of
this
Mike Galbraith wrote:
>
> On 15 Jan 2001, Zlatko Calusic wrote:
>
> > "Vlad Bolkhovitine" <[EMAIL PROTECTED]> writes:
> >
> > > Here is updated info for 2.4.1pre3:
> > >
> > > Size is MB, BlkSz is Bytes, Read, Write, and Seeks are MB/sec
> > >
> > > with mmap()
> > >
> > > File Block Num
> And if anybody else understands pirq routing, speak up. It's a black art.
>
I have some experience with PIRQ and Serverworks, but I missed the first
bit of this discussion - can someone catch me up?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, 15 Jan 2001, dean gaudet wrote:
> On Mon, 15 Jan 2001, Ingo Molnar wrote:
>
> > just for kicks i've implemented sendpath() support.
> >
> > _syscall4 (int, sendpath, int, out_fd, char *, path, off_t *, off, size_t, size)
>
> hey so how do you implement transmit timeouts with
On Mon, Jan 15, 2001 at 10:16:57AM -0700, Eric W. Biederman wrote:
> Heck if we wanted to we could even lie about PAGE_SIZE, and say it was huge.
> I'd have to have a clear example before I give it up that easily.
> mmap has never allowed totally arbitrary offsets, and mmap(MAP_FIXED)
> is
On Mon, 15 Jan 2001, Ingo Molnar wrote:
> just for kicks i've implemented sendpath() support.
>
> _syscall4 (int, sendpath, int, out_fd, char *, path, off_t *, off, size_t, size)
hey so how do you implement transmit timeouts with sendpath() ? (i.e.
drop the client after 30 seconds of no
On Mon, 15 Jan 2001, Dunlap, Randy wrote:
>
> Thanks for looking into this. I'll be out of touch for
> the rest of this week, but Petr ([EMAIL PROTECTED])
> should be able to test patches that Ingo comes up with.
>
> > Ok. That means that the problem is that we _should_ look at
> > the pirq
On Monday 15 January 2001 20:00, Steven Cole wrote:
> Got this for 2.4.1-pre7
>
> make[2]: *** No rule to make target `/usr/src/linux/incl', needed by
> `softirq.o'. Stop.
> make[2]: *** Waiting for unfinished jobs
> make[2]: Leaving directory `/usr/src/linux-2.4.1-pre7/kernel'
> make[1]:
On Mon, 15 Jan 2001, Tim Hockin wrote:
> Just built a new system with Linux-2.4.0.
>
> Motherboard (MSI 694D-AR) has Via Apollo Pro chipset, those IDE drives seem
> fine. Board also has a promise PDC20265 RAID/ATA100 controller. On each
> channel of this controller I have an IBM 45 GB ATA100
Roger Larsson wrote:
>
> On Sunday 14 January 2001 01:06, george anzinger wrote:
> > Nigel Gamble wrote:
> > > On Sat, 13 Jan 2001, Roger Larsson wrote:
> > > > A rethinking of the rescheduling strategy...
> > >
> > > Actually, I think you have more-or-less described how successful
> > >
Followup to: <[EMAIL PROTECTED]>
By author:"Maciej W. Rozycki" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Mon, 15 Jan 2001, H. Peter Anvin wrote:
>
> > Right, but I'd also like to see the global flags exported explicitly to
> > /proc/cpuinfo.
>
> That's desirable, but how
Hi,
I just asked on the linuxppc-dev list, but here is proably the better
place to ask.
We had a linuxppc_2_3 tree which had the #defines below disabled.
The fresh linuxppc_2_4 tree doesn't have it anymore.
The 2.4.0-ac9 patch has the current status of
linclude/asm-ppc/semaphore.h:
...
On 15 Jan 2001, Linus Torvalds wrote:
> Now, I'm not saying your filesystem is toast. I'm just saying that if
> you booted up in pre6, I'd suggest a quick reboot into a better kernel
> might be a good idea (be a jock, and do a sync and just push the reset
> button to force a proper fsck when it
Just built a new system with Linux-2.4.0.
Motherboard (MSI 694D-AR) has Via Apollo Pro chipset, those IDE drives seem
fine. Board also has a promise PDC20265 RAID/ATA100 controller. On each
channel of this controller I have an IBM 45 GB ATA100 drive as master.
(hde and hdg?). BIOS sees these
In article <[EMAIL PROTECTED]>,
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>Linus Torvalds wrote:
>> In article <[EMAIL PROTECTED]>,
>> Jeff Garzik <[EMAIL PROTECTED]> wrote:
>> >$!@#@! pre6 is already out :)
>
>> Yes, and for heavens sake don't use it, [...]
>
>Too late... First and foremost, a
Linus Torvalds wrote:
> In article <[EMAIL PROTECTED]>,
> Jeff Garzik <[EMAIL PROTECTED]> wrote:
> >$!@#@! pre6 is already out :)
> Yes, and for heavens sake don't use it, [...]
Too late... First and foremost, a correction: The VM data I posted was
for pre1, not pre5. Here is the VM data
Got this for 2.4.1-pre7
make[2]: *** No rule to make target `/usr/src/linux/incl', needed by
`softirq.o'. Stop.
make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory `/usr/src/linux-2.4.1-pre7/kernel'
make[1]: *** [first_rule] Error 2
Waiting for 2.4.1-pre8.
Steven
-
To
In article <[EMAIL PROTECTED]>,
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>$!@#@! pre6 is already out :)
Yes, and for heavens sake don't use it, because the reiserfs merge got
some dirty inode logic wrong. pre7 fixes just that one line and should
be ok again.
>Anyway, this may be a totally
On Mon, Jan 15 2001, David Michael Norris wrote:
> During boot of the 2.4.1-pre3 kernel, I received this oops:
>
> BUG() in slab.c:804
> EIP: 0010:[]
> Code: 0f 0b 83 c4 0c 8b 1b 81 fb 7c 52 27 c0 75 c2 a1 7c 52 27 c0
module_init marks loop_init __init, and ll_rw_blk:blk_dev_init calls
it too.
On Mon, 15 Jan 2001 20:09:14 -0200 (BRST),
Marcelo Tosatti <[EMAIL PROTECTED]> wrote:
>On Tue, 16 Jan 2001, Rainer Mager wrote:
>>>EIP; f889e044<=
>Trace; f889d966
>
>It seems the oops is happening in a module's function.
>
>You have to make ksymoops parse the oops output against a
During boot of the 2.4.1-pre3 kernel, I received this oops:
BUG() in slab.c:804
EIP:0010:[]
Code: 0f 0b 83 c4 0c 8b 1b 81 fb 7c 52 27 c0 75 c2 a1 7c 52 27 c0
ksymoops 2.3.5 on i586 2.4.1-pre2. Options used
-V (default)
-K (specified)
-L (specified)
-o
Hi,
How do i remove an object file. Like if I have a "mparallel.o"
file and need to remove and regenerate it. how do i do this if
i may ask?. "/lib/modules/misc/mparallel.o".
J
_
Get your FREE download of MSN Explorer at
$!@#@! pre6 is already out :)
Anyway, this may be a totally subjective (and incorrect) perception, but
it seems to me like the recent 2.4.x-test kernels and thereafter start
swapping things out really quickly. Case in point: "diff -urN
linux.vanilla linux" command swaps out Konqueror and
On Tue, 16 Jan 2001, Dominik Kubla wrote:
> On Mon, Jan 15, 2001 at 03:22:58PM -0500, Richard B. Johnson wrote:
> >
> > In any case, there is no way to correlate the device number with a
> > PC connector slot just as there is no way to find out which of the
> > 4 INT lines go to these
It sounds like it might be useful in the embedded OS space.
Miles
-
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 Monday January 15, [EMAIL PROTECTED] wrote:
>
>
> On Mon, 15 Jan 2001, Jure Pecar wrote:
>
> >
> > There is something not that usual about my setup: i run raid1 /boot and
> > raid5 root with one disk disconnected (its simply too loud...), so the
> > array is in degraded mode all the time.
Is there a linux qos mailing list?
thanks,
j.d.
-
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/
Jure, you write:
> I was running 2.4.0test10pre5 happily for months and wanted to see how
> things stand in the 'latest stuff'. Here's what i found:
>
> I compiled 2.4.0-ac8 with nearly the same .config as test10pre5 (with
> latest gcc on rh7). Then i booted it and used X for some normal
On Tue, 16 Jan 2001, Rainer Mager wrote:
> Ok, now were making progress. I did as you said and have attached (really!)
> the new parsed output. Now we have some useful information (I hope). I still
> got lots of warnings on symbols (which I have edited out of the parsed file
> for the sake of
Ok, now were making progress. I did as you said and have attached (really!)
the new parsed output. Now we have some useful information (I hope). I still
got lots of warnings on symbols (which I have edited out of the parsed file
for the sake of briefness). What's the next step?
--Rainer
>
Hi, all. I'm trying to get matroxfb running on a G400Max (dualhead).
Of course, I have i2c bit-banging on and the relevant Matrox options
turned on (as modules or compiled-in), and I don't see the expected
`framebuffer: blah' after the `matroxfb: Matrox Millennium G400 MAX (AGP)
detected'.
I
> I have been trying to figure out
> why linux tcp is failing to ack
> properly in some situations.
This is exactly the same problem I'm seeing with a Solaris box talking
to my Linux box. It has a similar problem with Linux as well, but does
not manifest as bad against a 2.2 kernel machine.
On Tue, 16 Jan 2001, Rainer Mager wrote:
> I knew that, I was just testing you all. ;-)
>>EIP; f889e044<=
Trace; f889d966
Trace; c0140c10
Trace; c0140e7c
Trace; c0140f9e
Trace; c0140e7c
It seems the oops is happening in a module's function.
You have to make ksymoops parse the
On Mon, 15 Jan 2001, Albert Cranford wrote:
> I have a working PA-2007 but use a small hard disk. Can I help.
[...]
> Detected 239.833 MHz processor.
[...]
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[...]
> hda: WDC AC2540F, ATA DISK drive
> hda:
I knew that, I was just testing you all. ;-)
\e hides his head in shame
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Marcelo Tosatti
> Sent: Tuesday, January 16, 2001 6:47 AM
> To: Rainer Mager
> Cc: [EMAIL PROTECTED]
> Subject: Re: Oops
David Balazic <[EMAIL PROTECTED]> writes:
> A recent 2.4.0 ( not the final , but close ) kernel prints this :
>
> mtrr: detected mtrr type: intel
>
> I have an AMD K7 Duron 700 CPU
>
> Is this correct ?
Yes. The K7 supports MTRRs exactly according to the Intel specs, as
opposed to the
On Tue, 16 Jan 2001, Rainer Mager wrote:
> Attached is my oops.txt and the result sent through ksymoops. The results
> don't look particularly useful to me so perhaps I'm doing something wrong.
> PLEASE tell me if I should parse this differently. Likewise, if there is
> anything else I
Tcp developers: (Alan Cox: you probably could fix in a minute)
I've been told that this is THE PLACE to contact
linux kernel developers. Ok, I've got a repeatable
bug that I've reported elsewhere to no avail. Hope
this is the place:
Includes 2 perl scripts to reproduce it and info about what
I
On Mon, 15 Jan 2001, Robert Reither wrote:
> I encounted really bad problems with 2048 Bytes/sec MO-Drive.
> I'm using an Olympus PowerMO 640.
> MO was formated with FAT32.
>
> i try to read a file from it (used : 'pico /mo/file.txt') ...
> And got a nice crash : Segmentation Fault
Even
Hi all,
I have a 100% reproducable bug in all of the 2.4.0 kernels including the
latest stable one. The issue is that if I compile the kernel to support 4GB
RAM (I have 1 GB) and then try to access a samba mount I get an oops. This
ALWAYS happens. Usually after this the system is frozen
I've been doing some work on the Initio 9100UW SCSI driver that is
distributed with 2.4.0. I've fixed a couple of bugs and added /proc
support to my copy of the source.
Is there an active maintainer of this driver at present?
Is there anything that tells what to do to add support for the new
Hi all,
I have been running 2.4.0 for 8 days with no problem. Then standard
RedHat cron job (slocate.cron) generated an oops:
ksymoops 2.3.4 on i686 2.4.0. Options used
-v /usr/src/linux/vmlinux
On Mon, 15 Jan 2001, Jure Pecar wrote:
> Hi all,
>
> I was running 2.4.0test10pre5 happily for months and wanted to see how
> things stand in the 'latest stuff'. Here's what i found:
>
> I compiled 2.4.0-ac8 with nearly the same .config as test10pre5 (with
> latest gcc on rh7). Then i booted
Hi all,
I was running 2.4.0test10pre5 happily for months and wanted to see how
things stand in the 'latest stuff'. Here's what i found:
I compiled 2.4.0-ac8 with nearly the same .config as test10pre5 (with
latest gcc on rh7). Then i booted it and used X for some normal browsing
and mp3s.
On 15 Jan 2001, Linus Torvalds wrote:
> The performance problem is _probably_ due to the kernel having to
> double-buffer the IO requests, coupled with bad MTRR settings (ie
> memory above the 4GB range is probably marked as non-cacheable or
> something, which means that you'll get really bad
I think I've found a bug in swapfs:
fstab:
swapfs /dev/shmswapfs defaults 0 0
swapfs /tmpswapfs defaults 0 0
When I hit on a tar.gz file in Midnight Commander nothing happens. If
I do a umonut /tmp and hit again it works as It should (I see the
archived
On 13 Jan 2001, Kai Henningsen wrote:
> [EMAIL PROTECTED] (Joe Pranevich) wrote on 06.01.01 in
><[EMAIL PROTECTED]>:
>
> >much of the code, including a long awaited combination of the PPP
> >layers from the ISDN layer and the serial device PPP layer, such as
>
> I've heard about that
On Mon, 15 Jan 2001, Ronny Buchmann wrote:
> i have the following problem with kernel 2.4.0 (also with -ac6):
>
> kernel BUG at slab.c:1095!
> invalid operand:
> CPU: 0
I could reproduce the problem, the appended patch fixes it here. Linus,
could you please apply this for 2.4.1?
> ..
On Sunday 14 January 2001 01:06, george anzinger wrote:
> Nigel Gamble wrote:
> > On Sat, 13 Jan 2001, Roger Larsson wrote:
> > > A rethinking of the rescheduling strategy...
> >
> > Actually, I think you have more-or-less described how successful
> > preemptible kernels have already been
I had a similar experience. All I can say is windows 98
and ME seem to have it out for Linux drives running late
2.3.x and 2.4.0 test and release. I had windows completely
fry my Linux drive and I lost everything. I had some old
backups and was able to restore at least the majority of
On Mon, 15 Jan 2001, H. Peter Anvin wrote:
> Right, but I'd also like to see the global flags exported explicitly to
> /proc/cpuinfo.
That's desirable, but how would we fit it into the existing layout?
Would it be feasible to put it into /proc/cpuflags, instead? Anyway, with
all necessary
Followup to: <[EMAIL PROTECTED]>
By author:Linus Torvalds <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Mon, 15 Jan 2001, Tobias Ringstrom wrote:
> >
> > Last time I checked this was issued for perfectly known and valid bridges
> > that advertice no IO resources. Isn't it a
"Maciej W. Rozycki" wrote:
>
> On Mon, 15 Jan 2001, H. Peter Anvin wrote:
>
> > I would personally prefer to export the global flags separately from the
> > per-CPU flags. Not only is it more correct, it would help catch these
> > kinds of bugs!!!
>
> That's what I am going to do. Basically
On Mon, 15 Jan 2001, H. Peter Anvin wrote:
> I would personally prefer to export the global flags separately from the
> per-CPU flags. Not only is it more correct, it would help catch these
> kinds of bugs!!!
That's what I am going to do. Basically to recode cpu_has_* macros to
use global
On Friday 12 January 2001 10:33, Marcel Weber wrote:
> SuSE Linux 7.0, Kernel 2.4.0
>
> Adaptec 3950U2
> Adaptec 2940
>
>
> Although the kernel is complaining about the following things:
>
> kernel: scsi0: PCI error Interrupt at seqaddr= 0x4e
> kernel: scsi0: Data Parity
On Mon, 15 Jan 2001, Hugh Dickins wrote:
> That's how "notsc" used to behave, but since 2.4.0-test11
> "notsc" has left "tsc" in /proc/cpuinfo. setup.c has a bogus
> "#ifdef CONFIG_TSC" which should be "#ifndef CONFIG_X86_TSC".
Confirmed.
> HPA, Maciej and I discussed that around 5 Dec 2000;
In article <[EMAIL PROTECTED]>,
Paul Hubbard <[EMAIL PROTECTED]> wrote:
>
>We're having some problems with the 2.4.0 kernel on our SGI 1450, and
>were hoping for some help.
> The box is a quad Xeon 700/2MB, with 4GB of memory, ServerSet III HE
>chipset, RH6.1 (slightly modified for local
Ok. Here's a question for anyone. I have a computer here that I'm trying to
get IDE-SCSI to work on. It seems to be a complete dud from this point of
view.
System config: Dual P3-550, 256MB Ram
Scsi card: Adaptec 2940U2W.
2 Seagate LVD drives connected
Primary
Hi Doug,
On Tue, Jan 09, 2001 at 03:53:02PM -0500, Douglas Gilbert wrote:
> There is also a problem report with the SnapScan 1236 <--> aha152x
> combination also based on SANE 1.0.3 . This one is looking
> like an "uninitialized errno" bug fixed in SANE 1.0.4 .
This should be solved with the
running 2.4.0 with kdb patch
[1.] Bonnie on NBD w/ memory pressure deadlocks (problem in wait_for_tcp_memory?)
[2.] Full description
This bug appears to be totally reproducable on different hardware and kernel versions.
The conditions that create the problem:
2 machines (client, server)
On Sun, Jan 14 2001, Martin Maciaszek wrote:
> Since I installed Kernel 2.4.0 VMware is no longer able to
> recognize my cdrom drive. VMware shows a dialog box on power up
> with following content:
> [...]
> CDROM: '/dev/scd0' exists, but does not appear tobe a CDROM device.
>
> Error connecting
Title: oracle 8.1.7 on 2.4.0?
what is the status of oracle 8.1.7 on 2.4?
Did the O_SYNC stuff ever get sorted out?
Should I stick with 2.2.18?
In article <[EMAIL PROTECTED]>,
Albert D. Cahalan <[EMAIL PROTECTED]> wrote:
>Ingo Molnar writes:
>> On Mon, 15 Jan 2001, Jonathan Thackray wrote:
>
>>> It's a very useful system call and makes file serving much more
>>> scalable, and I'm glad that most Un*xes now have support for it
>>> (Linux,
We're having some problems with the 2.4.0 kernel on our SGI 1450, and
were hoping for some help.
The box is a quad Xeon 700/2MB, with 4GB of memory, ServerSet III HE
chipset, RH6.1 (slightly modified for local configuration) distribution.
a) If we compile the kernel with no high memory
Hugh Dickins wrote:
>
> That's how "notsc" used to behave, but since 2.4.0-test11
> "notsc" has left "tsc" in /proc/cpuinfo. setup.c has a bogus
> "#ifdef CONFIG_TSC" which should be "#ifndef CONFIG_X86_TSC".
>
> HPA, Maciej and I discussed that around 5 Dec 2000; but HPA
> was of Andrea's
On 15 Jan 2001, Zlatko Calusic wrote:
> "Vlad Bolkhovitine" <[EMAIL PROTECTED]> writes:
>
> > Here is updated info for 2.4.1pre3:
> >
> > Size is MB, BlkSz is Bytes, Read, Write, and Seeks are MB/sec
> >
> > with mmap()
> >
> > File Block Num Seq ReadRand Read Seq Write
On 15 Jan 2001, Linus Torvalds wrote:
> int fd = open(..)
> fstat(fd..);
> sendfile(fd..);
> close(fd);
>
> is any slower than
>
> .. cache stat() in user space based on name ..
> sendpath(name, ..);
>
> on any real load.
just for kicks i've implemented
"Vlad Bolkhovitine" <[EMAIL PROTECTED]> writes:
> Here is updated info for 2.4.1pre3:
>
> Size is MB, BlkSz is Bytes, Read, Write, and Seeks are MB/sec
>
> with mmap()
>
> File Block Num Seq ReadRand Read Seq Write Rand Write
> DirSize SizeThr Rate (CPU%) Rate
Ingo Molnar writes:
> On Mon, 15 Jan 2001, Jonathan Thackray wrote:
>> It's a very useful system call and makes file serving much more
>> scalable, and I'm glad that most Un*xes now have support for it
>> (Linux, FreeBSD, HP-UX, AIX, Tru64). The next cool feature to add to
>> Linux is
On Thu, 11 Jan 2001, Linus Torvalds wrote
(under Subject: Re: 2.4.1-pre1 breaks XFree 4.0.2 and "w"):
>
> We _want_ /proc/cpuinfo to reflect the fact that the kernel considers
> FSXR/XMM to not exist. That is true information, and is in fact something
> that install scripts etc can find
On Mon, 15 Jan 2001 04:00:29 +0100, Petr Vandrovec wrote:
>(1) You missed some zeros in MSR_K7_ definitions
Oops :-(
>(2) AMD's MSR are real 64bit (well, 47bit) values, so high
>MSR dword must be set to -1, not to 0
Correct. That was a copy-paste error from the P6 code.
When writing to a
On Mon, 8 Jan 2001, Alan Cox wrote:
> And have identical bad problems with auth failures. Right now I've given up
> trying to make 2.4 and YP mix because my RH setup assumes NIS auth will fail
> fast during boot up scripts and it doesnt.
>
> Unfortunately for the quickfix folks, Dave is right
On Mon, 15 Jan 2001, Jack Hammer wrote:
> My adapter configuration utility needs to instruct the user which physical
> adapter needs attention ( when there may be multiple adapters in the system
> ).My question is : How do I determine the ( machine ) slot number of a
> PCI adapter ?
>
> In
Followup to: <[EMAIL PROTECTED]>
By author:Matti Aarnio <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> One thing about 'sendfile' (and likely 'sendpath') is that
> current (hammered into running binaries -> unchangeable)
> syscalls support only up to 2GB files at
Followup to: <[EMAIL PROTECTED]>
By author:J Sloan <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Linus Torvalds wrote:
>
> > Of course, you may be right on wuftpd. It obviously wasn't designed with
> > security in mind, other alternatives may be better.
>
> I run proftpd on all my
* David S. Miller ([EMAIL PROTECTED]) wrote:
>
> Now against 2.4.1-pre2:
>
> ftp.kernel.org:/pub/linux/kernel/people/davem/zerocopy-2.4.1p2-1.diff.gz
Tried it with 2.4.1-pre3, didn't have any problem applying it, but
when I rebooted the system it pretty much had no interest in talking
On Mon, 15 Jan 2001, Linus Torvalds wrote:
> On Mon, 15 Jan 2001, Tobias Ringstrom wrote:
> >
> > Last time I checked this was issued for perfectly known and valid bridges
> > that advertice no IO resources. Isn't it a bit silly to issue that
> > warning for that case, or am I missing something?
"Albert D. Cahalan" wrote:
>
> It looks like we let Microsoft fill the design guide void.
> If you were to write "PC DESIGN GUIDE - For the Linux Operating
> System" and a pile of test code, then there would be an
> alternative to point people at.
>
> Complaining is pretty useless.
I was
On Mon, Jan 15, 2001 at 11:52:12AM -0800, Linus Torvalds wrote:
> On Mon, 15 Jan 2001, Tobias Ringstrom wrote:
> > Last time I checked this was issued for perfectly known and valid bridges
> > that advertice no IO resources. Isn't it a bit silly to issue that
> > warning for that case, or am I
Pierre Rousselet writes:
> 1) top (procps-2.0.7) gives me the messages :
> 'bad data in /proc/uptime'
> 'bad data in /proc/loadavg'
> cat /proc/uptime
> 1435.30 904.74
> cat /proc/loadavg
> 0.01 0.21 0.29 1/17 19444
> What is wrong ?
Which 2.4.0-x kernel, and how was procps compiled?
(the
On Saturday, January 13, 2001 11:41:51 PM -0800 hugang
<[EMAIL PROTECTED]> wrote:
[ patch ]
Odd, the create_vi op should never be null, so the real fix is somewhere
else. We'll look into this.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, 15 Jan 2001, Tobias Ringstrom wrote:
>
> Last time I checked this was issued for perfectly known and valid bridges
> that advertice no IO resources. Isn't it a bit silly to issue that
> warning for that case, or am I missing something?
Ehh - so what do they bridge, then?
I'd say
Tobias Ringstrom wrote:
>
> On Mon, 15 Jan 2001, David Balazic wrote:
>
> > It also reports something like :
> > PCI chipset unknown : assuming transparent
>
> Are you sure it's not
>
> Unknown bridge resource 0: assuming transparent
Might be, I don't remember the exact wording.
--
David
On Sat, Jan 13, 2001 at 12:01:04PM +1100, Andrew Morton wrote:
> Tim Wright wrote:
[...]
> > p_lock(lock);
> > retry:
> > ...
> > if (condition where we need to sleep) {
> > p_sema_v_lock(sema, lock);
> > /* we got woken up */
> > p_lock(lock);
> > goto retry;
> > }
> > ...
>
>
On Mon, Jan 15, 2001 at 07:54:47PM +0100, David Balazic wrote:
> Is there a way to change the geometry from fdisk ?
> I tried expert mode and 'set sectors' and 'set heads',
> but after I exit fdisk with 'w' , it is unchanged.
As you know, a disk does not have a geometry, but
the location of a
On Mon, 15 Jan 2001, David Balazic wrote:
> It also reports something like :
> PCI chipset unknown : assuming transparent
Are you sure it's not
Unknown bridge resource 0: assuming transparent
(which is just about every kernel log I have seen...)
Last time I checked this was issued for
On Mon, 15 Jan 2001, Jonathan Thackray wrote:
> It's a very useful system call and makes file serving much more
> scalable, and I'm glad that most Un*xes now have support for it
> (Linux, FreeBSD, HP-UX, AIX, Tru64). The next cool feature to add to
> Linux is sendpath(), which does the open()
A recent 2.4.0 ( not the final , but close ) kernel prints this :
mtrr: detected mtrr type: intel
I have an AMD K7 Duron 700 CPU
Is this correct ?
It also reports something like :
PCI chipset unknown : assuming transparent
I have a VIA KT133 chipset
--
David Balazic
--
"Be
H. Peter Anvin writes:
> "Maciej W. Rozycki" wrote:
>> On Wed, 10 Jan 2001, H. Peter Anvin wrote:
>>> URRRK. I get a feeling these specs are either there to make life extra
>>> difficult for programmers, because the people that design them are too
>>> stupid to tie their own shoes, or because
Ralf Baechle <[EMAIL PROTECTED]> writes:
> On Mon, Jan 15, 2001 at 01:41:06AM -0700, Eric W. Biederman wrote:
>
> (Cc list truncated since probably not so many people do care ...)
>
> > shared mmap. This is the important one. Since we have a logical
> > backing store this is easy to handle.
On Mon, 15 Jan 2001, Robert Kaiser wrote:
>
> I finally found the reason why 386es have trouble booting the 2.4.0 kernel:
Good job.
> Pentiums are only lucky to not crash because they have a bigger TLB than 386s.
Actually, with the 4M pages, it's not a question of luck any more - they
just
I encounted really bad problems with 2048 Bytes/sec MO-Drive.
I'm using an Olympus PowerMO 640.
230MB Media works fine, but if i try to use 640(2048B/S) medias i'm really
in troubles. Looks quite the same as the problems i've reported for the
2.1.x kernels some time ago. (2.2.17/18 works fine 4
My adapter configuration utility needs to instruct the user which physical
adapter needs attention ( when there may be multiple adapters in the system
).My question is : How do I determine the ( machine ) slot number of a
PCI adapter ?
In BIOS and other OS's this may be doneby examining the
1 - 100 of 306 matches
Mail list logo
