In article <90a065$5ai$[EMAIL PROTECTED]>,
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>Anyway, I do have this machine working now, although not everything is
>to my liking. Unlike older picture-books, for example, this one has a
>WinModem. Ugh. And the sound chip is supported, but only by the
On Thu, 30 Nov 2000, Dunlap, Randy wrote:
> Yes, that's how it looks to me also, so maybe it's not a kernel
> problem. Thanks for the tip.
>
> Here's more info, including the strace that Al Viro asked for.
> I also made sure that I'm using mount & umount version 2.10o.
> Please let me know
If I buy one of these machines for testing,
will I be able to upgrade the processor's Code
Morphing Software with the new version when it's
ready? I hear the new CMS code will almost
double the battery life.
Thanks,
Miles
-
To unsubscribe from this list: send the line "unsubscribe
On Sat, 2 Dec 2000, Chris Wedgwood wrote:
> On Sat, Dec 02, 2000 at 12:14:34AM -0500, Alexander Viro wrote:
>
> Not really. Anything that modifies directories holds both ->i_sem and
> ->i_zombie, lookups hold ->i_sem and emptiness checks (i.e. victim in
> rmdir and overwriting
Followup to: <[EMAIL PROTECTED]>
By author:Tigran Aivazian <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Second attempt -- the first one got lost due to some local mail client
> problems...
>
> Hi Linus,
>
> Here is the patch to microcode update driver to support the new P4
> CPU.
On Sat, 2 Dec 2000, Chris Wedgwood wrote:
> On Thu, Nov 30, 2000 at 08:24:02AM -0500, Richard B. Johnson wrote:
>
> This is actually a feature. The directory does not get truncated.
>
> Arguably directories could be truncated when objects towards the end
> are removed; I believe UFS
Followup to: <[EMAIL PROTECTED]>
By author:"Adam J. Richter" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Well, alas, it appears that linux-2.4.0-test12-pre3 freezes hard
> while reading the base address registers of the first PCI device
> (the "host bridge"). Actually, I
On Fri, Dec 01, 2000 at 09:22:22PM -0600, Peter Samuelson wrote:
>
> [Jamie Manley]
> > Yes, modversions was enabled. Should that be affecting the build of
> > the kernel proper?
>
> The bug you ran into is that MODVERSIONS messes up the
> 'get_module_symbol' function, which is a sort of
Minutes after slashdot ran their article saying that the
Transmeta recall was limited to about 300 Fujitsu computers, I ran
to Fry's and bought a Sony PictureBook PCG-C1VN. Thank heavens for
those extended Christmas hours I thought, while praying that the
statements about the Crusoe
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Fri, Dec 01, 2000 at 08:35:41AM +1100, Andrew Morton wrote:
> >
> > I bet this'll catch it:
> >
> > static __inline__ void list_del(struct list_head *entry)
> > {
> > __list_del(entry->prev, entry->next);
> > + entry->next = entry->prev =
[Christopher Friesen]
> I think you should re-read the GPL. You only have to provide source
> to people to whome you have distributed your new binaries, and you
> only have to provide that source if you are asked for it.
Oh, and you have to provide the complete text of the GPL as well, and
for
[Jamie Manley]
> Yes, modversions was enabled. Should that be affecting the build of
> the kernel proper?
The bug you ran into is that MODVERSIONS messes up the
'get_module_symbol' function, which is a sort of "optional dependency"
mechanism used by a few modules such as DRI (in this case: DRI
On Fri, Dec 01, 2000 at 08:04:52PM -0500, Jeff Dike wrote:
> boot memory allocator (see mm/bootmem.c). In the arch that I'm most familiar
> with (arch/um), that is usable from the beginning of start_kernel. I don't
> know about the other arches.
setup_arch does the necessary initialization
On Fri, Dec 01, 2000 at 02:52:11PM +, John Levon wrote:
> > [drm] The mga drm module requires the agpgart module to function correctly
> > Please load the agpgart module before you load the mga module
> >
> > Although XFree86 seems to be happy enough loading the dri and drm
> > modules.
> >
Jens Axboe wrote:
> On Tue, Nov 21 2000, [EMAIL PROTECTED] wrote:
> > > Believe it or not, but this is intentional. In that regard, the
> > > function name is a misnomer -- call it i/o scheduler instead :-)
> >
> > I never believe it intentional. If it is true, the current kernel
> > will be
[EMAIL PROTECTED] said:
> I was unsure if it was okay to be using kmalloc during early stages of
> init/main.c so I decided to follow the example allready set and just
> use a static array - can anyone advise on being able to do this
> dynamically?
kmalloc is usable after mem_init(), I think.
[Tracy Camp]
> I was unsure if it was okay to be using kmalloc during early stages
> of init/main.c so I decided to follow the example allready set and
> just use a static array - can anyone advise on being able to do this
> dynamically?
Have a static 'char *' somewhere. In the "root="
Followup to: <[EMAIL PROTECTED]>
By author:Paul Jakma <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Fri, 1 Dec 2000, Alan Cox wrote:
>
> > > Intel PXE uses tftp to download boot images and discards IP packets with
> > > the DF bit set; so a tftpd server on 2.4 with the default
>
> Hmmm, I don't like your array thing (also in v.I of the patch),
> limiting us to possible root devices, where n==8. A better
> approach might be to iterate over the root= arguments when mounting. I
> know why you used the array -- easier to code.
I was unsure if it was okay to be using
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Fri, Dec 01, 2000 at 08:35:41AM +1100, Andrew Morton wrote:
> >
> > I bet this'll catch it:
> >
> > static __inline__ void list_del(struct list_head *entry)
> > {
> > __list_del(entry->prev, entry->next);
> > + entry->next = entry->prev =
Hi
I'm using kernel version 2.2.14. When the mount
syscall or mount command is called, the user given
name of the mount point isn't resolved. These means
that /proc/mounts will have entries with symlinks
while /etc/mtab will have the real directory.
In the case of smbmnt, chdir is called on
On Fri, 1 Dec 2000 10:52:35 -0800 (PST),
Al Peat <[EMAIL PROTECTED]> wrote:
> I've followed the thread on "Persistent module
>storage" but haven't come across a general explanation
>of the changes to the inter-module symbol stuff
>between 2.4test10 and test11. Anyone care to comment
>on the
On Fri, 01 Dec 2000 09:41:58 -0700,
Roger Crandell <[EMAIL PROTECTED]> wrote:
>Killing interrupt handler
>scheduling in interrupt
>
>The kernel logs nothing and you must reset the machine to bring it back
linux/Documentation/oops-tracing.txt
linux/Documentation/serial-console.txt
-
To
On Fri, 1 Dec 2000 14:52:11 + (GMT),
John Levon <[EMAIL PROTECTED]> wrote:
>Probably you have modversions enabled (CONFIG_MODVERSION=y). Disable that
>and try again, or build as modules. 2.4 fixed this problem in the proper
>way, but I don't know what's going to happen about 2.2 ...
I have
[Roger Crandell]
> When I boot the machine with the multiprocessor kernel and run
> iptables, the kernel dumps several pages of hex and the final two
> lines of output are:
>
> Killing interrupt handler
> scheduling in interrupt
Look through the "several pages of hex" for any number in square
[I wrote]
> Your patch makes it impossible, in this situation, to override the
> default root device from the syslinux command line. A kludge to make
> it work again would be to process the root devices in reverse.
Better would be to reset the list of root devices with every 'root='
statement,
[Tracy Camp]
> A much cleaner patch prompted after right proper chastisement on the
> sloppy patch I sent a few days back. This one is against 2.4-pre11
Hmmm, I don't like your array thing (also in v.I of the patch),
limiting us to possible root devices, where n==8. A better
approach might
On Sat, Dec 02, 2000 at 06:56:43AM +1100, Neil Brown wrote:
> On Friday December 1, [EMAIL PROTECTED] wrote:
> > It's so slow that it's unusable. Especially writing. open() and
> > close()-calls often hang for 20 seconds or more.
> > write-calls hang for 3-4 seconds. This has to be a bug.
> > But
http://resourcemanagement.unixsolutions.hp.com/WaRM/schedpolicy.html
Changes included:
1.a new benchmark for realtime testing called sched_rr
2.a fix to YIELD code in pset.c which could result in a hang after
cpu assign of a busy cpu on Linux 2.2.16.
3.the release of a
On Fri, Dec 01, 2000 at 02:56:43PM -0500, Phillip Ezolt wrote:
> What data structure's would I look at? What should I investigate to
> verify this?
In the arch/alpha/kernel/pci_iommu.c change
#define DEBUG_ALLOC 0
to
#define DEBUG_ALLOC 2
Perhaps this will give us more info.
At the first look
Here's the oops. This is an AIC7xxx controller. This is a non-SMP kernel,
and there is only one processor installed in the machine. The value in eax
sure looks weird too me, esp. given that the failing instruction involves
a ld from (%eax)
This is a va2200 node, and this same kernel has booted
On Fri, Dec 01, 2000 at 08:28:57AM -0800, Reto Baettig wrote:
> Is there any chance that we will see this patch as well as your other
> Alpha patches included in future 2.2.X and 2.4.X releases?
Yes, for 2.2.x I'm waiting 2.2.19pre, for 2.4.x as DaveM suggested we first
need to cleanup the
On Fri, 1 Dec 2000 17:51:09 +0800, Andrey Savochkin <[EMAIL PROTECTED]> wrote:
> I've been promised that this issue would be looked up in Intel's errata by
> people who had the access to it, but I haven't got the results yet.
There is nothing relevant in the errata, unfortunately...
> The card
Hi!
It's great that you could fix that!
Is there any chance that we will see this patch as well as your other
Alpha patches included in future 2.2.X and 2.4.X releases?
Thanks,
Reto
Andrea Arcangeli wrote:
>
> There were a few SMP races that could trigger only using threads:
>
> 1)
Hello,
On Fri, 1 Dec 2000, Ben McCann wrote:
> I'm curious about how ICMP redirect is causing this problem.
> Would you elaborate on how ICMP is involved?
The masq box sends ICMP redirects to the internal host
when the destination host is on the same shared media, i.e.
I don't have really good numbers for either, but I can say that I was
really impressed with this firewall yesterday. there were other problems
in the system that caused things to clog up, but a 2.4 AMD950 PC133 ram
system was useable (slow, but useable) with 4000+ processes and a loadave
of > 300
[Marc Mutz]
> > +TOPDIR := $(shell pwd -P)
> That is specific to the bash builtin 'pwd'. GNU sh-util's pwd does
> not know that option (at least not my version, which is: "pwd (GNU
> sh-utils) 1.16")
It passed my 5-second shell feature portability test (ash). Checking
again, I see that the
On Fri, Dec 01, 2000 at 02:56:43PM -0500, Phillip Ezolt wrote:
> What data structure's would I look at? What should I investigate to
> verify this?
The relevant code is in arch/alpha/kernel/core_cia.c
> What would I have to do to test this? I have an ES40 & 3 miata's
Does the qlogic
Hi.
I recently investigated an 'unused function' warning in iph5526.c. Looking
at it (both the code causing the warning and the whole driver) convinced
me that the driver cannot be used without PCI enabled.
I therefore propose that we add a dependency in net/Config.in for this
driver and clean
On Fri, Dec 01, 2000 at 09:26:29AM +, David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > Not necessarily - it all depends on what your driver does. In many
> > cases, supporting 2.2 and 2.4 is easy, and all you need are a few
> > #if's. It's certainly much better to have a dozen or so
Andrea,
> large 2G. So it's maybe the second window between 1G and 2G that isn't set
> correctly?
What data structure's would I look at? What should I investigate to
verify this?
> Does the qlogic driver works on a tsunami southbridge?
What would I have to do to test this? I have
On Friday December 1, [EMAIL PROTECTED] wrote:
> On Fri, Dec 01, 2000 at 01:11:45PM +1100, Neil Brown wrote:
> > On Thursday November 30, [EMAIL PROTECTED] wrote:
> > > Hello people,
> > >
> > > I have some trouble with the raid-stuff.
...
> >
> > Is it just "very slow", but it eventually
On Friday December 1, [EMAIL PROTECTED] wrote:
> Please CC to me because I'm not a LKML subscriber.
>
> Hi,
>
> I found a real showstopper problem in the SoftwareRAID autodetect
> code; 2.4.0-test10 and 2.4.0-test11 are affected (I didn't test
> previous versions).
Fixed in 2.4.0-test12pre3.
On Wed, Nov 29, 2000 at 03:01:59PM -0700, Tom Rini wrote:
> As Dave Miller pointed out, DEV_MAC_HID sysctl conflicts with the RAID patches
That's right but OTOH I'd simply declare the sysctl-by-number interface dead
for new introduced sysctl. We need to preserve backwards compatibility of
course
On Fri, Dec 01, 2000 at 01:30:10PM -0500, Phillip Ezolt wrote:
> Any ideas? (Or patches that I can test... ;-) )
miata seems to use cia southbridge so it should set an iommu direct mapping
large 2G. So it's maybe the second window between 1G and 2G that isn't set
correctly? Does the qlogic
Alan Cox wrote:
>
> > > > my question is:
> > > > what kind of problem can have this serveur:
> > > > hardware or software ?
> > >
> > > What sort of watchdog are you using ?
> >
> > software. no hardware solution.
> >
On Fri, Dec 01, 2000 at 10:19:44AM -0800, David S. Miller wrote:
>I'm still left the #ifdef __alpha__ around the context[NR_CPUS] to
>avoid breakage of other archs but that should be probably removed:
>any CPU with per-CPU ASNs like alpha needs per-CPU per-MM context
>information
On Fri, 1 Dec 2000, Alan Cox wrote:
> > Intel PXE uses tftp to download boot images and discards IP packets with
> > the DF bit set; so a tftpd server on 2.4 with the default
>
> Then Intel PXE is buggy and you should go spank whoever provided
> it as well as doing the workarounds. Supporting
I've got a motherboard with the same Via686a chipset, and i've never had a
problem with DMA when it's enabled.
Using a pair of 20 gig IBM drives on the secondary, and a 3.2 quantum primary,
17.2 gig maxtor. All using DMA, all work. Using ultra/33, I wasn't even
aware this chipset is ultra/66
Hi,
On Tue, Nov 21, 2000 at 11:18:15AM -0500, Eric Lowe wrote:
>
> I have updated raw I/O patches with Andrea's and my fixes against 2.2.
> They check for CONFIG_BIGMEM so they can be applied and compiled
> without the bigmem patch.
I've just posted an assembly of all of the outstanding raw IO
I've followed the thread on "Persistent module
storage" but haven't come across a general explanation
of the changes to the inter-module symbol stuff
between 2.4test10 and test11. Anyone care to comment
on the differences or on whether this is going to be a
stable API for 2.4 (it won't be
Peter Samuelson wrote:
>
> +TOPDIR := $(shell pwd -P)
That is specific to the bash builtin 'pwd'. GNU sh-util's pwd does not
know that option (at least not my version, which is: "pwd (GNU sh-utils)
1.16")
I just wanted to note that...
Marc
--
Marc Mutz <[EMAIL PROTECTED]>
> With 2.4.0-test11, when ip_no_pmtu_disc is still 0/false we're seeing
> outbound udp packets with the IP DF bit set. Is this change in default
> behavior a fix or a break?
Its a change in behaviour
> So, it appears that 2.4 fixed a problem with 2.2, correct?
> [stop non expert thinking]
I've had second-hand reports of an issue with ACPI and cardbus, but I
haven't enough about this to actually diagnose the problem.
Is anyone experiencing this?
If so, could you please provide some more details to me, so we can get this
fixed ASAP?
Thanks -- Regards -- Andy
Date:Fri, 1 Dec 2000 15:18:42 +0100
From: Andrea Arcangeli <[EMAIL PROTECTED]>
I'm still left the #ifdef __alpha__ around the context[NR_CPUS] to
avoid breakage of other archs but that should be probably removed:
any CPU with per-CPU ASNs like alpha needs per-CPU per-MM
[Marc Mutz <[EMAIL PROTECTED]>]
> Should that not be first converted to paths that contain no symlinks?
I agree.
--- Makefile~ Tue Nov 28 21:53:31 2000
+++ MakefileFri Dec 1 12:25:28 2000
@@ -10,7 +10,7 @@
CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
else
Ivan,
I have tried test12-pre3 with and without your patch, it fails in the same
way.
The Qlogic SCSI controller continues to fail if we have >1 gig in the machine.
(But works fine without it.)
Any ideas? (Or patches that I can test... ;-) )
Thanks,
--Phil
Compaq: High Performance Server
Please, if you respond, send me a copy to my mailbox, too.
> Status: kernel 2.4.0-test10 (no patches added)
> Problem: getting dma problems - having to run system with no dma
> for disc access - seems to be a bus mastering problem.
> Hardware: Aopen AX34Pro mother board, Via chipset with
Followup to: <[EMAIL PROTECTED]>
By author:Matthew Kirkwood <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Hi,
>
> It looks like the random driver in 2.4test will return a
> short read, rather than blocking. This is breaking vpnd
> (http://sunsite.dk/vpnd/) which breaks with
On Fri, 1 Dec 2000, Olivier Galibert wrote:
> On Wed, Nov 29, 2000 at 04:40:29PM +, Tigran Aivazian wrote:
> > b) what should be the return of access(W_OK) (or, the same, open() for
> > write with switched uid) for devices on a readonly-mounted filesystems?
> >
> > Should the majority win?
Rainer Clasen wrote:
>
> Ciscos MAC based distribution limits each TCP connection to 100 Mbps.
>
What's even worse, is Cisco can also *clog* channels with traffic, if
your MAC addresses aren't balanced. (ie, one line can have all the
traffic, while the other is idle..
--
On Fri, 01 Dec 2000, Francois romieu wrote:
> [netdev Cced]
>
> The Thu, Nov 30, 2000 at 11:16:52AM -0800, Ivan Passos wrote :
> [...]
> > For synchronous network interfaces, besides configuring network parameters
> > such as IP address, netmask, MTU, etc., the system should also configure
> >
I've seen that happen with kernel version 2.2.16!
> Hi,
>
> It looks like the random driver in 2.4test will return a
> short read, rather than blocking. This is breaking vpnd
> (http://sunsite.dk/vpnd/) which breaks with "failed to
> gather random data" or similar.
>
> Here's a sample strace:
On Fri, 1 Dec 2000, Andrew Morton wrote:
> Alexander Viro wrote:
> >
> > Confirms. That's definitely an empty list_head at address 0xc3c49058 and -pre2
> > has O_SYNC patches.
>
> foo. The overnight run wedged tight in mmap002. No progress.
>
> I bet this'll catch it:
>
> ---
Ronald G Minnich <[EMAIL PROTECTED]> writes:
> Eric, here is the ksymoops (end of message) from that earlier failure. I'm
> just wondering if anyone out there has seen anything like this. Also, if
> anyone sees anything odd about the scsi configuration that would help too.
>
> Thanks in advance
Peter Samuelson wrote:
>
> Many people limit their e-mail messages to 80 columns. What for?
>
CF'mon, linebreaks are bloat! Those extra characters all around :-)
> The 'build' symlink is to make it easier for external module
> installation scripts to find the build directory for a given
Hi,
It looks like the random driver in 2.4test will return a
short read, rather than blocking. This is breaking vpnd
(http://sunsite.dk/vpnd/) which breaks with "failed to
gather random data" or similar.
Here's a sample strace:
open("/dev/random", O_RDONLY) = 3
read(3,
On Tue, 28 Nov 2000, John B. Jacobsen wrote:
>
> /* winbond-840.c: A Linux PCI network adapter skeleton device driver. */
It is already in 2.4.x
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please
On Fri, Dec 01, 2000 at 12:46:18PM +, Alan Cox wrote:
> > I was able to reproduce this oops with a somewhat more reliable ksymoops (I was
>ready for this nasty bug this time). Looks like the problem is in the sockets
> > code.
>
> The traces so far all match one description , this one
On Fri, 1 Dec 2000, T. Camp wrote:
> Hmm didn't know that, from the user-land portable C perspective I'm in the
> habit of zero'ing everything. - thanks.
Yes, sorry, I should have explained a bit more, perhaps. The point is that
when you have an unitialized variable like this:
int x;
the C
On Fri, Dec 01, 2000 at 09:05:23AM -0800, T. Camp wrote:
> Hmm didn't know that, from the user-land portable C perspective I'm in the
> habit of zero'ing everything. - thanks.
It's a requirement of the ISO C standard that all global/static (not
local) variables are initialized to 0 is not
On Wed, Nov 29, 2000 at 04:40:29PM +, Tigran Aivazian wrote:
> b) what should be the return of access(W_OK) (or, the same, open() for
> write with switched uid) for devices on a readonly-mounted filesystems?
>
> Should the majority win? I.e. should we say OK, as we do now?
My gut feeling
> indeed, much cleaner. But still not perfect.
>
> > + int root_device_index = 0;
>
> this initialisation is not needed. Just make it 'int root_device_index;'
> The kernel will do the right thing for you on boot, trust me.
>
> > +int number_root_devs = 0;
>
> this is not needed either.
Hmm
I should have mentioned this is a 4 processor machine with a 64 bit
buss.
Roger Crandell
-
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/
Hello,
On Fri, 1 Dec 2000, T. Camp wrote:
> A much cleaner patch prompted after right proper chastisement on the
indeed, much cleaner. But still not perfect.
> + int root_device_index = 0;
this initialisation is not needed. Just make it 'int root_device_index;'
The kernel will do the
A much cleaner patch prompted after right proper chastisement on the
sloppy patch I sent a few days back. This one is against 2.4-pre11 but so
far as I can tell should be good to go against any of the 2.4 series so
far.
I have not implemented a regex-like syntax as was suggested because 1) you
...forgot to mention - I DID try to play with
CONFIG_PCI_GOBIOS
CONFIG_PCI_GODIRECT
CONFIG_PCI_GOANY
in the kernel configuration - no use
Guennadi
___
Dr. Guennadi V. Liakhovetski
Department of Applied Mathematics
University of Sheffield, U.K.
email: [EMAIL PROTECTED]
-
To unsubscribe from
I have 2.4.0 test 10 and test 11 installed on a multiprocessor (Intel)
machine. I have tried both test versions of the kernel. I configured
the kernel for single
and multi processor. When I boot single processor, iptables will run
fine. When I boot the machine with the multiprocessor kernel
Actually, this is a continuation of the
"Re: DMA !NOT ONLY! for triton again..."
thread.
Mike Dresser wrote:
> I'm taking the case off the machine right now, i can guarantee you its
> not UDMA compatible, simply because this thing was made in early1997. :)
>
> Here we go:
>
> MDL
On Fri, 1 Dec 2000, Velizar Bodurski wrote:
>Date: Fri, 1 Dec 2000 01:06:50 +0200 (EET)
>From: Velizar Bodurski <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Subject: XFree 4.0 problems.
>
>Ok I don't have the system in question, but i use others'
Please CC to me because I'm not a LKML subscriber.
Hi,
I found a real showstopper problem in the SoftwareRAID autodetect
code; 2.4.0-test10 and 2.4.0-test11 are affected (I didn't test
previous versions).
I'm using two IDE disk with some RAIDed partitions:
md5 : active raid0 hdc5[1] hda5[0]
Patrick van de Lageweg wrote:
> Hi alan,
>
> This patches fixes several isues with the rio driver:
>
> - Implemented breaks
> - Fixed a DCD up/down crash
> - Added kmalloc return value check
Hmm. And introduces a new problem. Sorry. Please ignore this patch...
Andrew Morton [[EMAIL PROTECTED]] wrote:
> Andrew Morton wrote:
> >
> > Andrew Morton wrote:
> > >
> > > I bet this'll catch it:
> > >
> > > --- include/linux/list.h.orig Fri Dec 1 08:33:36 2000
> > > +++ include/linux/list.hFri Dec 1 08:33:55 2000
> > > @@ -90,6 +90,7 @@
> > >
Glad all this discussion helped at least one of us:-))
As for me, as I already mentioned in my last posting - I don't know why BIOS makes the
difference (as in your case) if ide.txt says it shouldn't?! Ok, chipset, perhaps, is
fine. But what about the hard drive? You told you had WDC AC21600H.
On Wed, 29 Nov 2000, Jamie Manley wrote:
> Finally got around to trying the 2.2.18pre series and the agp/drm
> backport and noticed something odd at bootup. Here's an extract from
> dmesg:
>
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory:
Hi,
I'm not sure where this is the right mailing list to ask this question,
but let me try. If not, could you excuse & help me to get to the right
place to express it. Thanks, :-).
Today i've got a strange message in /var/log/message (
kernel 2.4.0-test10 updated from SuSE7.0-2.2.17-pre):
Guennadi Liakhovetski wrote:
> Hi
> > will try tonight... and will let you know tomorrow...
> ... Nop, it didn't work. Mike and everybody having experience / knowledge of Western
>Digital Caviar AC21600H... If you compare WD's documents at:
> http://www.westerndigital.com/service/FAQ/dtr.html
Dries van Oosten wrote:
>
> On Fri, 1 Dec 2000, Dax Kelson wrote:
> > If you want to take full advantage of all the networking features, you
> > need to use iproute2.
> >
> > ftp://ftp.inr.ac.ru/ip-routing/iproute2-2.2.4-now-ss??.tar.gz
>
> I downloaded and compiled them and they don't
On Fri, Dec 01, 2000 at 02:56:19PM +0300, Ivan Kokshaysky wrote:
> Andrea, could you try this?
that's the right fix thanks (please send to Linus).
BTW, here is a preview of the asn SMP race fix for 2.4.x:
> > > my question is:
> > > what kind of problem can have this serveur:
> > > hardware or software ?
> >
> > What sort of watchdog are you using ?
>
> software. no hardware solution.
> http://www.ibiblio.org/pub/Linux/system/daemons/watchdog/watchdog-5.1.tar.gz
The software watchdog will fail
You're going to get a chuckle out of this one, i think. I was using my main
fileserver at home(different box from
the ones we're talking about)last night, and figured i'd poke around, do some speed
benchmarks for the hell of it. At
one point months, i had everything running in DMA mode,
Hi,
On Fri, Dec 01, 2000 at 08:35:41AM +1100, Andrew Morton wrote:
>
> I bet this'll catch it:
>
> static __inline__ void list_del(struct list_head *entry)
> {
> __list_del(entry->prev, entry->next);
> + entry->next = entry->prev = 0;
> }
No, because the buffer hash list is never
Alan Cox wrote:
>
> > We have a problem on a 2.2.17: sometimes it crashs
> > without any reason (no high load), there is no kernel panic,
> > the screan is black. We setup watchdog software and
> > we realized watchdog can not reboot this box whe it crashs
> > (on the others servers it works
In message <[EMAIL PROTECTED]>, Russell King wri
tes:
>We already have a standard interface for this, but many drivers do not
>support it. Its called "ifconfig eth0 media xxx":
The Ethtool interface is rather better.
p.
-
To unsubscribe from this list: send the line "unsubscribe
On Fri, 1 Dec 2000, Chris Wedgwood wrote:
> Actually; Ethernet badly needs something like this too. I would kill
> to be able to do something like:
>
> ifconfig eth0 speed 100 duplex full
Even if you are thinking about Ethernet only, it's not easy to do it. Most
modern NICs have MII
> We have a problem on a 2.2.17: sometimes it crashs
> without any reason (no high load), there is no kernel panic,
> the screan is black. We setup watchdog software and
> we realized watchdog can not reboot this box whe it crashs
> (on the others servers it works fine).
>
> my question is:
>
> It implements mono output and fixes a bug in the dma logic (reset necessary
> because some descriptors are already prefetched and are not updated
This is wrong. Linus please do not apply this patch, or if you have done back
it out. Not only does it do format conversions in kernel (which is a
Hi alan,
This patches fixes several isues with the rio driver:
- Implemented breaks
- Fixed a DCD up/down crash
- Added kmalloc return value check
Sorry for the late moment we submit this: the DCD bug was very, very hard
to find.
Patrick
diff -u -r
Russell King <[EMAIL PROTECTED]> écrit :
[...]
> We already have a standard interface for this, but many drivers do not
> support it. Its called "ifconfig eth0 media xxx":
>
> bash-2.04# ifconfig --help
> Usage:
> ifconfig [-a] [-i] [-v] [-s] [[] ]
> ...
> [mem_start ] [io_addr ] [irq ]
Hi Linus,
there is a warning in make docs and there is no documentation generated
for blk_init_queue because of another function declaration between the
comments and the definition .
This patch moves the declaration before the comments.
please apply .
---
1 - 100 of 254 matches
Mail list logo
