On 13 Feb 2001, Stig Brautaset wrote:
> I have a Xircom Combo CardBus (32 bit) 10/100 Ethernet Card + 56k
> Modem (didn't try the modem part) that I have not been able to run
> under 2.2.18 or 2.4.0. The weird part is that everything seems to load
> fine, and I am able to configure the card with
Hi all,
I am observing a problem with 2.4.1 (and 2.4.0, all the -test releases
were fine) with pcmcia on my laptop. At boot time, I have to pop the
ethernet card twice after the bus detection and before the card's
module gets loaded or eth0 isn't found. Actually, I don't have to do
it
Hi all,
I have a machine with kernel 2.4.1 . It exports some volume via NFS
(installed with RedHat 7.0 + custom 2.4.1 kernel)
NFSD dies unexpectedly with a Oops (see below).
At the beginning, I have 8 NFSD processes, but suddenly, they all die. I
can't see why it happens, because the machine is
Andrew Morton wrote:
>
> Alan Cox wrote:
> >
> > > > queued_writes=1;
> > > > return;
> > > > }
> > > > }
> > >
> > > Unfortunately, that means that if machine crashes in interrupt, it may
> > > "loose" printk message. That is considered
On Tue, 13 Feb 2001 07:47:33 +0100,
"Ph. Marek" <[EMAIL PROTECTED]> wrote:
>and the modules dependencies are not all set!
>make modules_install does not check for modules compilation - says
>"cp: file not found". I think that's because modules_install doesn't
>depend on the modules
Correct.
Hello,
I have been trying to get a solution to a minor problem but unfortunately i
have not been able to solve it or get some help on it and i am stuck up from
a long time.
Is there any way i can find out that there has been a change in the kernel
routing table in linux ?
In the file
The only change is to update things to 2.4.2-pre3:
ftp://ftp.kernel.org/pub/linux/kernel/people/davem/zerocopy-2.4.2p3-1.diff.gz
All the reports I am getting now appear to be consistent,
and they all basically show me that:
1) There are no known bugs (as in things that crash the
kernel or
> Not good enough in isolation. Suppose the kernel freezes at a very early
> stage, such as while detecting the CPU(s) or PCI bridge - are your geeky
> reaction times fast enough to dismiss the logo in time to see the relevant
> messages? I agree with others that this should be a boot option -
I have 2 ether cards 59x (eth0) and 509 (eth1). I have been adding 509
at boot in lilo.conf. Using this same config in 2.4.1 results in
the hardware addresses for the cards to be swapped. If I remove 509 from
Lilo I get the same result. Suggestions would be appreciated
-
To unsubscribe from
Andrew Morton writes:
> Changing the memory copy function did make some difference
> in my setup. But the performance drop on send(8k) is only approx 10%,
> partly because I changed the way I'm testing it - `cyclesoak' is
> now penalised more heavily by cache misses, and amount of cache
>
On Sun, 11 Feb 2001, James Brents wrote:
> Sorry, I wrote that in a hurry. Its a 3Com PCI 3c905C Tornado. I can
> successfully use wakeonlan if I power off the machine immeadiatly after
> turning it on. Using the shutdown command, which it will when I need it
> to power back up, it will not
Hello again,
When i originally posted this, it was _highly_ OT. the machine in question
runs windows ME, but i figured the best place to find hardware gurus was
here.
the topic has rather degraded, and while i enjoy getting mail from alan,
the fact that it has nothing to do with me dampens the
>I need the output from these commands on a running 2.4.x kernel
>compiled for duron.
>
>grep _mmx_memcpy /proc/ksyms
>strings -a `/sbin/modprobe -l '*tulip*'` | grep _mmx_memcpy
Short version: it's caused by CONFIG_MODVERSIONS=y.
see the logs on the end.
If I turn it off and compile again, it
On Mon, 12 Feb 2001, Marcelo Tosatti wrote:
> On Sun, 11 Feb 2001, Mike Galbraith wrote:
>
> > On Sun, 11 Feb 2001, Rik van Riel wrote:
> >
> > > On Sun, 11 Feb 2001, Mike Galbraith wrote:
> > > > On Sun, 11 Feb 2001, Mike Galbraith wrote:
> > > >
> > > > > Something else I see while watching
Adrian Levi wrote:
>
> I usually lurk on the list and don't contribute but I would like to
> place my 2 bob in to the fro. Would a modified X-Modem protocol stack suit
> this operation? No sliding window and don't send anything until you
> receive an ack back?
>
Not particularly. Xmodem and
I have a software raid setup using the latest kernel, but the system keeps
crashing.
Each drive is connected to the respective ide port via ATA100 capable
cables. Each drive is a master..no slaves. The configuration is that
/dev/hdc is a hot spare and /dev/hd[e,g,i,k,m,o,q,s] are all setup
Re: Tom's message (below)
Thanks for your comments and description of symptoms. There may well
be an underlying common cause. Have you looked at the MTU/MSS
settings?
>Do you get errors on your ppp0 interface? Just curious. Now that I know I'm
>not just crazy maybe I'll look into it
Alan Cox wrote:
>
> > > It seems that people are using open source software to do idiotic
> > > things. Many open source references were made in the article, I should
> > > see if the article is online at all to maybe be able to use it as a
> > > reference.
> >
> > You probably mean that one:
On Sun, Feb 11, 2001 at 11:47:18PM +0100, Pavel Machek wrote:
> > Right. Add the option. Default to "spew mode",
> > but make it easy for distributions to show people
> > a non-threatening boot process.
>
> Wrong.
> >
> > Since, as Christophe mentions, the boot messages would
> > still be
>I've seen in recently purchased computers that the very initial
>messages, like memory test, are masked by some kind of picture or logo
>(example are the HP kayaks). They display a message saying that pressing
>ESC or some function key displays the messages. Why not having the same
>in this
Is there any kernel patch that would allow Linux to properly recognize,
and execute gzipped executables?
I know I could use binfmt_misc to run a wrapper script:
decompress to /tmp/prog.decompressed
execute /tmp/prog.decompressed
rm /tmp/prog.decompressed
But that's not as clean,
On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote:
> On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote:
> [snip]
> > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout
>with(0x70)!
>
> Please try the attached patch.
> Actually, it's designed to solve
Quoting [EMAIL PROTECTED]:
> Symptoms: The browser (Netscape or Lynx) will not download from remote
> web sites (dynamic ppp connection via external modem).
>
> This looks to be a problem for my PC and the 2.4.x kernel,
It is very interesting that your are having this problem. I have been
On Mon, 12 Feb 2001, george anzinger wrote:
> Excuse me if I am off base here, but wouldn't an atomic operation be
> better here. There are atomic inc/dec and add/sub macros for this. It
> just seems that that is all that is needed here (from inspection of the
> patch).
Most functions which
I've seen in recently purchased computers that the very initial
messages, like memory test, are masked by some kind of picture or logo
(example are the HP kayaks). They display a message saying that pressing
ESC or some function key displays the messages. Why not having the same
in this pretty
On Mon, Feb 12, 2001 at 06:49:13PM -0800, xcp wrote:
> I have a machine here with a discrepency on the pci information
> in /proc/pci:
> us 0, device 20, function 0:
> Ethernet controller: 3Com Unknown device (rev 48).
> Vendor id=10b7. Device id=7646.
> Medium devsel. IRQ 12.
Carlos Carvalho wrote:
>
> Doug Ledford ([EMAIL PROTECTED]) wrote on 9 February 2001 16:41:
> >The latest patch I sent Alan had both the hosts.c fix and some other fixes, so
> >I'm thinking it hasn't made it into his 2.2.19pre9 kernel. The next one
> >should work fine as far as aic7xxx is
Excuse me if I am off base here, but wouldn't an atomic operation be
better here. There are atomic inc/dec and add/sub macros for this. It
just seems that that is all that is needed here (from inspection of the
patch).
George
Rasmus Andersen wrote:
>
> On Mon, Jan 29, 2001 at 07:30:01PM
I may be off base here, but the problem as described below does _NOT_
seem to be OT so I removed that from the subject line. A clock drift
change with an OS update is saying _something_ about the OS, not the
hardware. In this case it seems to be the 2.4.x OS that is loosing
time. I suspect the
I have a machine here with a discrepency on the pci information
in /proc/pci:
us 0, device 20, function 0:
Ethernet controller: 3Com Unknown device (rev 48).
Vendor id=10b7. Device id=7646.
Medium devsel. IRQ 12. Master Capable. Latency=32. Min
Gnt=10.Max Lat=10.
I/O
Symptoms: The browser (Netscape or Lynx) will not download from remote
web sites (dynamic ppp connection via external modem).
This is a second post. The problem is still not resolved, but can now
be described in more detail, thanks to help given by David Woodhouse
(and others) and my ISP.
The attached patch corrects the linux kernel reservation handling. Currently
linux fails badly when presented with SCSI reservations in a clustered
environment. The patch also completes Doug Gilbert's reset injection system
in the sg driver. The patches have no effect on the main line SCSI
Test.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
Hey Vojtech,
Thanks for your response. I tried using 2.4.2-pre3 and the same problem
occurs, in exactly the same manner. The only other problem I can identify
is a boot message:
IRQ routing conflict in pirq table for device 00:0a.0
lspci reveals that 00:0a.0 is my network card:
00:0a.0
On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote:
[snip]
> Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout
>with(0x70)!
Please try the attached patch.
Actually, it's designed to solve another problem, but may be your one has the
same origin as that other.
Best
On Tue, Feb 13, 2001 at 02:28:06AM +0200, Olli Lounela wrote:
>
> Okay, I goofed. The motherboard reset the interrupts to the same old stoopid
> values when I shuffled the cards. I have now separated them, no difference.
Progress: not only did I goof, I was wrong too.
This time it booted once
Hi,
Niibe Yutaka noted (and added an entry on the MM bugzilla system) that
cache flushing on do_swap_page() is buggy. Here:
---
struct page *page = lookup_swap_cache(entry);
pte_t pte;
if (!page) {
lock_kernel();
On Mon, 12 Feb 2001, Ion Badulescu wrote:
> Here is an incremental patch from the version in 2.2.19pre10 to the latest
> version of starfire.c. Please apply, the 2219pre10 version doesn't work if
> compiled-in (because drivers/net builds net.a not net.o). It also fixes
> the MII interface
Hi,
I notice the entities in the subject line have appeared in Linux 2.4.
What is their functional specification? I guess they trigger if no bytes
are received/send within a consecutive period. How does the app get the
error? -EPIPE for a blocking read/write? If so, does SIGPIPE
get raised? Or
On Tue, Feb 13, 2001 at 01:55:01AM +0200, Olli Lounela wrote:
>
> Finally got 2.4.2pre3 nosmp boot dmesg, attached. Also current lspci -vvvxx
Okay, I goofed. The motherboard reset the interrupts to the same old stoopid
values when I shuffled the cards. I have now separated them, no difference.
I asked for some information and seems at least 1 person took the "tone"
of my email to mean I had an attitude while asking.
On the premise that perhaps I did ask with an attitude, even if I don't
see it, I'd like to ask for some information.
Here is a synopsis of what I'm running up against
James Sutherland wrote:
> >
> > Well, any time there is a network there needs to be buffering, if you
> > want to have any kind of ACK protocol.
>
> Yes, but only the last packet sent, if you limit to one packet at a
> time... Shouldn't be a problem, even for the smallest code.
>
Of course.
Alan Cox wrote:
>
> > I'm sure you can. That doesn't mean it's the right solution.
>
> And the UDP proposal will be at least as big if it does retransmits, and if
> it doesnt , its junk. It will also need as much buffering, if not the same
> packing trick
>
Within limits, you're right, of
On Mon, 12 Feb 2001, H. Peter Anvin wrote:
> James Sutherland wrote:
> > >
> > > Depends on what the client can handle. For the kernel, that might be
> > > true, but for example a boot loader may only have a few K worth of buffer
> > > space.
> >
> > Fortunately, the bulky stuff (printk's from
Tim Wright wrote:
>
> Yup,
> those who fail to learn from TCP are doomed to re-invent it, badly, at the
> wrong level .
> Seriously, the console subsystem on the Sequent (now IBM) NUMA-Q systems
> originally used UDP. It wound up as a serious mess. We changed to TCP.
> I'll admit that the NUMA-Q
On Mon, 12 Feb 2001, Scott Murray wrote:
Thanks!
The isapnp=0 fixed it. I don't actually have an isapnp.conf file.
On my next compile I'll just disable the ISA Pnp driver.
I don't actually need it, but it's something that I've never bothered to
turn off. :)
CF
> On Mon, 12 Feb 2001, Chris
I am no kernel hacker, but I would like to file a bug-report none the
less. Please CC me with follow-ups (if any ;-) since I am not
subscribing to the mailing list.
I have a Xircom Combo CardBus (32 bit) 10/100 Ethernet Card + 56k
Modem (didn't try the modem part) that I have not been able to
On Tuesday, February 13, 2001 01:39:02 AM +0300 Hans Reiser
<[EMAIL PROTECTED]> wrote:
> Chris, your quoting is very confusing above. but I get your very
> interesting remark (thanks for noticing) that the nulls are specific to
> crashes on 2.2, and therefor could be due to the elevator bug
Yup,
those who fail to learn from TCP are doomed to re-invent it, badly, at the
wrong level .
Seriously, the console subsystem on the Sequent (now IBM) NUMA-Q systems
originally used UDP. It wound up as a serious mess. We changed to TCP.
I'll admit that the NUMA-Q console subsystem does more than
Well what do you know...
I added isapnp=0 and it worked.
at 0x370
at 0x534 irq 5 dma 1,0
at 0x330 irq 5 dma -1,0
The dma and the MSS address (0x534) looks odd, but at least it
seems to play now.
And no, AFAIK, this driver has never been able to detect PNP settings.
If you try to run it
> I'm sure you can. That doesn't mean it's the right solution.
And the UDP proposal will be at least as big if it does retransmits, and if
it doesnt , its junk. It will also need as much buffering, if not the same
packing trick
-
To unsubscribe from this list: send the line "unsubscribe
All,
I just compiled 2.4.1-ac10 with the loop-3 patch from adoeb and it seems to fix
the loopback problems. This is for someone NOT using the encrypted FS since I
did not test this.
If anyone has a better way to make sure everything is working correctly other
than using mkinitrd to test if the
On Mon, 12 Feb 2001, Chris Funderburg wrote:
>
> After the updates to the opl3sa2 driver (2.4.2-pre3?) my card isn't being
> detected anymore. Are there further updates to come, or do I need to
> change the settings? The driver is being loaded as a module with the
> following in
On Mon, Feb 12, 2001 at 09:02:00AM -0800, Leonard N. Zubkoff wrote:
>
> I seem to recall that the Intel Providence motherboard has been
> problematic in many configurations. Have you contacted Mylex Technical
> Support to inquire about compatibility issues between the AcceleRAID 250
> and the
> Then HPA may ask: but why do you want to run the serial console at
> 115200?? The answer is simple: because we ...
... don't want to drag out debugging the kernel on a 38400 connection.
Because printks are our only debugging option ("thanks", Linus), and a slow
serial port block and can change
Alan Cox wrote:
>
> > Depends on what the client can handle. For the kernel, that might be
> > true, but for example a boot loader may only have a few K worth of buffer
> > space.
>
> That same constraint is true of any UDP protocol too, and indeed any protocol
> not entirely based on FEC
On Sat, Feb 10, 2001 at 11:18:25AM -0500, Nick Papadonis wrote:
> I saw a posting about the DC-395 from you.
>
> What the current state of the driver? Where is it? =20
http://www.garloff.de/kurt/linux/dc395/
Works perfectly for most people, but corrupts data for some.
> I just bought the
James Sutherland wrote:
> >
> > Depends on what the client can handle. For the kernel, that might be
> > true, but for example a boot loader may only have a few K worth of buffer
> > space.
>
> Fortunately, the bulky stuff (printk's from the booting kernel) will be
> going from the boot loader
> > The midi works fine, but 'modprobe sound' reports:
> > opl3sa2: No cards found
> > opl3sa2: 0 PnP card(s) found.
Thats ok, it may not be set up for isapnp
> Try to add "isapnp=3D0" to the opl3sa2 options list :
>
> opl3sa2 mss_io=3D0x530 irq=3D5 dma=3D1 dma2=3D0 mpu_io=3D0x330 io=3D0x3=
>
On Mon, Feb 12, 2001 at 03:17:04PM -0800, Ivan Passos wrote:
>
> On Mon, 12 Feb 2001, Scott Laird wrote:
> >
> > On 12 Feb 2001, H. Peter Anvin wrote:
> > >
> > > Just checked my own code, and SYSLINUX does indeed support 115200 (I
> > > changed this to be a 32-bit register ages ago,
On Mon Feb 12, 2001 at 14:04:20 +0100, Jan-Benedict Glaw wrote:
> I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID
> controller. The mainboard is ServerWorks based and however, 2.4.2-pre3
> fails to find the RAID controller. I think there's a problem at
> scanning PCI busses
Chris Funderburg wrote:
> following in /etc/modules.conf:
>
> alias sound-slot-0 opl3sa2
> options sound dmabuf=1
> alias midi opl3
> options opl3 io=0x388
> options opl3sa2 mss_io=0x530 irq=5 dma=1 dma2=0 mpu_io=0x330 io=0x370
>
> The midi works fine, but 'modprobe sound' reports:
>
>
On Mon, 12 Feb 2001, H. Peter Anvin wrote:
> Alan Cox wrote:
> >
> > > > Explain 'controlled buffer overrun'.
> > >
> > > That's probably the ability to send new data even if there's unacked old
> > > data (e.g. because the receiver can't keep up or because we've had losses).
> >
> > Well let
> Depends on what the client can handle. For the kernel, that might be
> true, but for example a boot loader may only have a few K worth of buffer
> space.
That same constraint is true of any UDP protocol too, and indeed any protocol
not entirely based on FEC (which rather rules out ethernet
> I *REALLY* don't know if that is reasonable; it may have to fall into the
> category of "supported but not required". Requiring an SHA hash in a
> small bootstrap loader may not exactly be a reasonable expectation!
tea is very very small so may be appropriate instead.
> However, I think the
Well, it's back up again now.
I've been using the patches for a couple of months with no problems.
This is on a 4-processor P6 box, so the SMP support seems sound. I only have
a CDRW attached on this SCSI bus so I can't comment on disk support etc.
Kurt, have you submitted this driver to be
After the updates to the opl3sa2 driver (2.4.2-pre3?) my card isn't being
detected anymore. Are there further updates to come, or do I need to
change the settings? The driver is being loaded as a module with the
following in /etc/modules.conf:
alias sound-slot-0 opl3sa2
options sound dmabuf=1
Alan Cox wrote:
>
> > This is true, but one thing I'd really like to have is controlled buffer
> > overrun, which TCP *doesn't* have. I really think an ad hoc UDP protocol
> > (I've already begun sketching on the details) is more appropriate in this
> > particular case.
>
> Explain 'controlled
Alan Cox wrote:
>
> > > Explain 'controlled buffer overrun'.
> >
> > That's probably the ability to send new data even if there's unacked old
> > data (e.g. because the receiver can't keep up or because we've had losses).
>
> Well let me see, the typical window on the other end of the
Chris Mason wrote:
>
> On Monday, February 12, 2001 11:42:38 PM +0300 Hans Reiser
> <[EMAIL PROTECTED]> wrote:
>
> >> Chris,
> >>
> >> Do you know if the people reporting the corruption with reiserfs on
> >> 2.4 were using IDE drives with PIO mode and IDE multicount turned on?
> >>
> >> If so,
On Mon, 12 Feb 2001, Scott Laird wrote:
>
> On 12 Feb 2001, H. Peter Anvin wrote:
> >
> > Just checked my own code, and SYSLINUX does indeed support 115200 (I
> > changed this to be a 32-bit register ages ago, apparently.) Still
> > doesn't answer the question "why"... all I think you do is
> > Explain 'controlled buffer overrun'.
>
> That's probably the ability to send new data even if there's unacked old
> data (e.g. because the receiver can't keep up or because we've had losses).
Well let me see, the typical window on the other end of the connection if
its a normal PC class
Alan Cox wrote:
> Explain 'controlled buffer overrun'.
That's probably the ability to send new data even if there's unacked old
data (e.g. because the receiver can't keep up or because we've had losses).
Such a feature would be mainly useful in cases where data becomes useless
if too old, e.g.
Chris Mason wrote:
>
> On Monday, February 12, 2001 11:42:38 PM +0300 Hans Reiser
> <[EMAIL PROTECTED]> wrote:
>
> >> Chris,
> >>
> >> Do you know if the people reporting the corruption with reiserfs on
> >> 2.4 were using IDE drives with PIO mode and IDE multicount turned on?
> >>
> >> If so,
On Monday, February 12, 2001 11:42:38 PM +0300 Hans Reiser
<[EMAIL PROTECTED]> wrote:
>> Chris,
>>
>> Do you know if the people reporting the corruption with reiserfs on
>> 2.4 were using IDE drives with PIO mode and IDE multicount turned on?
>>
>> If so, it may be caused by the problem
On Mon, 12 Feb 2001, H. Peter Anvin wrote:
> James Sutherland wrote:
> >
> My thinking at the moment is to require kernel IP configuration (either
> ip= or RARP/BOOTP/DHCP). It seems to be the only practical way;
> otherwise you miss too much at the beginning. However, that mechanism is
>
> It's not a huge undertaking, I know, but UDP will probably still be
> a bit simpler. Turn the question around: would using TCP bring any real
> benefits, in a system which will only be used to shift a few kb each boot
> time?
Im not convinced it will be any smaller by the time your UDP code
Hi,
I am a computer scientist from France. I currently play with
a source code analyser of mine.
Here are some "bugs" (or are they not ?) it detected :
(my own comments begin with ->)
/usr/src/linux-2.4.1/include/asm-parisc/som.h : EOF in comment
-> this one is self explained ..
On Mon, 12 Feb 2001, Alan Cox wrote:
> > > I have toyed a few times about having a simple Ethernet- or UDP-based
> > > console protocol (TCP is too heavyweight, sorry) where a machine would
> > > seek out a console server on the network. Anyone has any ideas about
> > > it?
> >
> > Excellent
On Sun, 11 Feb 2001, Mike Galbraith wrote:
> On Sun, 11 Feb 2001, Rik van Riel wrote:
>
> > On Sun, 11 Feb 2001, Mike Galbraith wrote:
> > > On Sun, 11 Feb 2001, Mike Galbraith wrote:
> > >
> > > > Something else I see while watching it run: MUCH more swapout than
> > > > swapin. Does that
On Mon, Feb 12, 2001 at 10:50:23PM +0100, John B. Jacobsen wrote:
> Starting lpd: Warning - lp: cannot open lp device '/dev/lp0' - No such device
> Warning - dj: cannot open lp device '/dev/lp0' - No such device
>
> Why is that ? /dev/lp surely exists !
It's telling you that the driver is not
Hi!,
We have several machines running Supermicro 370DLE motherboad with dual
733MHz Processors.
We are running reiserfs on some partitions. 2 x 9.1GB SCSI HDD and 1 x
18GB SCSI HDD.
Kernel 2.2.18
Every so often the machines freezes, possibly whilst we are rsyncing to
the machine, but it does
Alan Cox writes:
> I suspect adding
>
> #define BUG() __asm__ __volatile__("call_pal 129 # bugchk")
>
> to include/asm-alpha/page.h will do the right thing, since it works on 2.4
You have to add a few bits to arch/alpha/kernel/traps.c
I could be wrong though...
Later,
David S.
On Mon, 12 Feb 2001 [EMAIL PROTECTED] wrote:
> Hello!
>
> > Machine (IP address 1.2.3.4) is running kernel 2.2.13 and dials in
> > over an annoyingly high-latency PPP link via ordinary modems.
> >
> > Machine (IP address 5.6.7.8) connects via a cable modem and is running
> > RH6.2 and kernel
Martin Laberge wrote:
> Juergen Schneider wrote:
>
>
>> Hello everybody,
>>
>> 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
> > That was Im afraid pure luck. Jens is currently sorting out the
> > loop problems and has test patches
>
> By any chance, are these loop problems the same ones affecting
> 2.4.2-pre2 and -pre3?
And to varying degrees all 2.4.x kernels right now
-
To unsubscribe from this list: send the line
> This is true, but one thing I'd really like to have is controlled buffer
> overrun, which TCP *doesn't* have. I really think an ad hoc UDP protocol
> (I've already begun sketching on the details) is more appropriate in this
> particular case.
Explain 'controlled buffer overrun'. BTW if you
Or you could just check Sender which is already there.
On 12 Feb 2001, Kai Henningsen wrote:
>
> Indeed. What a bad idea that would be.
>
> > If you want to pre-filter messages traveling thru linux-kernel list,
> > all you need to do is to check the content of Return-Path: header.
>
>
On Mon, Feb 12, 2001 at 09:58:43PM +, Alan Cox wrote:
> > Kernel 2.4.1ac9 works OK from that point of view.
>
> That was Im afraid pure luck. Jens is currently sorting out the
> loop problems and has test patches
By any chance, are these loop problems the same ones affecting
> Hmm... Looks more difficult than I expected. Can we just change the
> one call to BUG to something sensible on alphas? I'm really eager to
> run this kernel..
The 'something sensible' is what you need to define BUG() to be, so its no
harder to do it right IMHO
I suspect adding
#define BUG()
Alan Cox wrote:
>
> Sounds like MOP on the old Vaxen. TCP btw isnt as heavyweight as people
> sometimes think. You can (and people have) implemented a simple TCP client
> and IP and SLIP in 8K of EPROM on a 6502. There is a common misconception
> that a TCP must be complex.
>
> All you actually
Alan Cox ([EMAIL PROTECTED]) wrote on 12 February 2001 21:49:
>The ideal solution would be for someone to provide BUG() on the
>Alpha platform as in 2.4. That would sort things cleanly
Hmm... Looks more difficult than I expected. Can we just change the
one call to BUG to something sensible on
>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.
>Is there a generic approach to finding where this sort of problem lies?
The exact same thing happens to me too. Winbook XL2 laptop.
I can ssh to the
Those patches are online somewhere ???
If you need a hand (trained monkey willing to do compilings, testing
and traceing :) I'm here.
Mircea C.
Alan Cox wrote:
>
> > Kernel 2.4.1ac9 works OK from that point of view.
>
> That was Im afraid pure
Kai Henningsen wrote:
>
> [EMAIL PROTECTED] (Matti Aarnio) wrote on 12.02.01 in
><[EMAIL PROTECTED]>:
>
> > On Mon, Feb 12, 2001 at 11:20:40AM +, Guennadi Liakhovetski wrote:
> > > Dear all (and list maintainers in particular)
> > >
> > > Wouldn't it be a good idea to prepend all lkml
FYI:
With ac5 I could mount loopback filesystems that were aes encrypted. All
I get with ac10 is a lockup.
Will test patches.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hello all.
We've written a module for kernel 2.2.14 that includes a driver
for 2 "virtual" devices. These devices don't actually exist,
they're implemented with two circular buffers; what's written
into one of the devices is read from the other, and viceversa.
We believe the buffer is
> Kernel 2.4.1ac9 works OK from that point of view.
That was Im afraid pure luck. Jens is currently sorting out the loop problems
and has test patches
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Pavel Machek wrote:
> Hi!
>
>
>> Right. Add the option. Default to "spew mode",
>> but make it easy for distributions to show people
>> a non-threatening boot process.
>
> Wrong.
We're talking about an _option_. In fact, it could
be set up as a boot time parameter. Then, if a boot
I got the following warning when I compiled
kernel 2.4.0 and 2.4.1 :
Starting lpd: Warning - lp: cannot open lp device '/dev/lp0' - No such device
Warning - dj: cannot open lp device '/dev/lp0' - No such device
Why is that ? /dev/lp surely exists !
regards
John
-
To unsubscribe from this
1 - 100 of 496 matches
Mail list logo
