I haven't been able to get PCMCIA working under Linux 2.4 with any kind
of serial devices (Cardbus or normal ISA), at least not reliably, on my
Vaio 505TX. I've tried both yenta_socket and i82365. It works about
one time in ten, but I've never figured out what causes it to work or
not work.
On Fri, Dec 08, 2000 at 07:37:55AM +, Anton Altaparmakov wrote:
Hearing how many people trash their partition I would agree to comment out
the NTFS write option altogether. I will make a patch for both 2.4.0-testX
and 2.2.18latest and send them off to Linus/Alan over the weekend if no
On Fri, Dec 08, 2000 at 06:02:57PM +0100, Martin Kacer wrote:
Is there any chance to get rid of these VMM failures?
You should apply this patch on top of 2.2.18pre25:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.18pre25/VM-global-2.2.18pre25-7.bz2
It
Folks, see if the following patch helps. AFAICS it closes a pretty real
race - we could call block_write_full_page() for a page that has sync
IO in progress and blindly change -b_end_io callbacks on the bh with
pending requests. With a little bit of bad luck they would complete before
we got to
On Fri, Dec 08, 2000 at 10:47:46AM +0100, Willy Tarreau wrote:
|Bus 0, device 2, function 1:
| Unknown class: Intel OEM MegaRAID Controller (rev 5).
|Medium devsel. Fast back-to-back capable. BIST capable. IRQ 10. Master
Capable. Latency=64.
|Prefetchable 32 bit memory at
spin_lock_irq(io_request_lock);
we finish the request and return to the add_request function which calls
spin_unlock_irqrestore(io_request_lock,flags);
and restores the flags.
Isn't it possible now that the flags which we restore are out of date now?
Is this idiom
On 8 Dec 2000, Christoph Rohland wrote:
here is my first shot for cleaning up the shm handling. It did survive
some basic testing but is not ready for inclusion.
The only comment I have right now is that you probably should not mark the
page dirty in "nopage" - theoretically somebody
Date: Fri, 8 Dec 2000 11:41:07 -0500 (EST)
From: Pavel Roskin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], Pete Zaitcev [EMAIL PROTECTED],
Jaroslav Kysela [EMAIL PROTECTED]
--- ./drivers/sound/Config.in Thu Dec 7 10:59:06 2000
+++ ./drivers/sound/Config.in Fri
On Fri, Dec 08, 2000 at 07:28:15AM -0800, David S. Miller wrote:
Date: Fri, 8 Dec 2000 16:31:54 +0100
From: Andi Kleen [EMAIL PROTECTED]
On Fri, Dec 08, 2000 at 06:54:28AM -0800, David S. Miller wrote:
No, unfortunately nobody has the time to do this.
The RFC evaluation
On Fri, 8 Dec 2000, Pete Zaitcev wrote:
+++ ./drivers/sound/ac97_codec.cThu Dec 7 11:00:44 2000
@@ -61,6 +61,7 @@
} ac97_codec_ids[] = {
{0x414B4D00, "Asahi Kasei AK4540 rev 0", NULL},
{0x414B4D01, "Asahi Kasei AK4540 rev 1", NULL},
+ {0x41445303, "Yamaha YMF"
On Fri, 8 Dec 2000, Alexander Viro wrote:
Fix: postpone changing -b_end_io until the call of ll_rw_block(); if by
the time of ll_rw_block() some fragments will still have IO in progress -
wait on them.
Comments?
Yes.
On the other hand, I have this suspicion that there is an even
Hello!
They irritated you so much that you only noticed after six months ?
I really edit and even read skbuff.h not every day and even not every
month. Is this bad? 8)
"Irritated" is wrong word. "To get a scare" is closer to truth.
Alexey
-
To unsubscribe from this list: send the line
Hi,
We run a heavily accessed Apache 1.3.6 Web server on a Redhat 6.0 distro
over 2.2.17. We upgraded from 2.2.16 and I now got some kernel oops.
System is :
AMD Athlon 600 Mhz.
512 MB RAM.
gcc version egcs-2.91.66
glibc 2.1.3-21
Kernel tweaks :
echo 1 /proc/sys/net/ipv4/tcp_syncookies
In article [EMAIL PROTECTED] you wrote:
BTW what is this? It is just a question, I missed even the moment, when these
things appeared:
It allows us to generate man9 sets for that part of the kernel and other
documentation sets
That could even be automated when this little patch (against
On Thu, 7 Dec 2000, Peter Samuelson wrote:
[Dick Johnson]
Do:
char main[]={0xff,0xff,0xff,0xff};
Oh come on, at least pick an *interesting* invalid opcode:
char main[]={0xf0,0x0f,0xc0,0xc8}; /* try also on NT (: */
What's funny, is that this actually executes on SPARC
On Fri, 8 Dec 2000, Alexander Viro wrote:
Erm... So you want to make -commit_write() page-unlocking? Fine with me,
but that will make for somewhat bigger patch. Hey, _you_ are in position
to change the locking rules, freeze or not, so if it's OK with you...
No.
Read the code a bit more.
On Fri, 8 Dec 2000, Alan Cox wrote:
I have seen two failure modes: on my machine (linux 2.2.5-22, glibc
2.1.1), when run under gdb 5.0, the created pthreads stick around as
glibc 2.1.1 definitely has problems with several bits of pthreads. You
want 2.1.3 or higher I believe.
So you're
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote:
On Thu, 7 Dec 2000, Jeff V. Merkey wrote:
I think there may be a case when a process forks, that the MMU or some
other subsystem is either not setting the page bits correctly, or
mapping in a bad page. It's a LEVEL I bug in 2.4 is this is the
On Wed, 6 Dec 2000, Andrey Savochkin wrote:
The sympthomes are that the card triggers Flow Control Pause condition (and
interrupt) on the last stages of the initialization or right after.
And it happens with flow control being explicitly turned off.
High network load considerably
Bad day, Alan? ;)
Umm no but having people _keep_ sending you do
nothing patches gets annoying after a while ;)
Please accept all my apologies, Alan. When I quickly
sent you the last patch, I didn't notice that some
other broken code had been removed, what I discovered
later back home and
David Howells [EMAIL PROTECTED] writes:
Can you help me with an SHM related problem?
I'm currently writing a Win32 emulation kernel module to help speed Wine up,
and I'm writing the file mapping support stuff at the moment
(CreateFileMapping and MapViewOfFile).
These two calls were
Hi.
The following patch eliminates an 'defined but not used' warning when
compiling drivers/net/arlan.c without module support (240t12p3). It
also fixes a typo.
It should apply cleanly.
--- linux-240-t12-pre3-clean/drivers/net/arlan.cWed Nov 22 22:41:40 2000
+++
"I'm sure" meaning "I didn't test it" ?
absolutely, I believed that the driver was *exactly*
the same as the previous release which didn't boot and
needed the fix, but another fix has been applied and
corrected it. Now I think it will work with a clean
2.2.18pre25. Anyway, I left a kernel
(I sent the following to [EMAIL PROTECTED], but forgot to cc linux-kernel).
Hi.
The following patch removes some 'defined but not used' warnings when
compiling drivers/net/eepro.c (240t12p7) without modular support.
--- linux-240-t12-pre7-clean/drivers/net/eepro.cFri Dec 8 00:44:58
Hi Peter.
On Tue, 5 Dec 2000, H. Peter Anvin wrote:
Linus Torvalds wrote:
Actually, I bet I know what's up.
Want to bet $5 USD that suspend/resume saves the keyboard A20 state,
but does NOT save the fast-A20 gate information?
So anything that enables A20 with only the fast A20 gate will
Hi.
The following patch removes a 'defined but not used' warning from drivers/
new/hp100.c when compiling without CONFIG_PCI (240t12p3). It should apply
cleanly.
--- linux-240-t12-pre3-clean/drivers/net/hp100.cSat Nov 4 23:27:07 2000
+++ linux/drivers/net/hp100.c Sat Dec 2 16:07:27
Ion Badulescu wrote:
The fact that apparently only the people using 82559 chips are seeing this
seems to confirm my analysis above.
If you could try the attached patch (and maybe pass it onto the other
people who are experiencing this problem), that would be great.
+ /*
Hi.
The following patch moves the page_table_lock in mm/* to cover the
modification of mm-rss in 240-test12-pre7. It was inspired by a
similar patch from davej(?) which covered too much, AFAIR. The item
is on Tytso's ToDo list.
Please comment.
diff -Naur linux-240-t12-pre7-clean/mm/memory.c
Hallo,
at startup of 2.4.0-test12pre7 I receive a bug-message as part of the
following boot.msg. I hope this will be helpfull. If you need more info, let
me know.
kind regards
Norbert
snip --
kernel BUG at buffer.c:827!
No no. That's that the whole point of a gate. You make a controlled
transition to ring 0 including stack switching. There are complex
protection checking rules, however as long as the DPL of the gate
descriptor is 3 then ring 3 is allowed to make the transition to ring 0. A
stack fault in
Hi.
The following patch makes some 'defined but not used' warnings go away
when compiling drivers/char/moxa.c without CONFIG_PCI (240t12p3). It should
apply cleanly.
--- linux-240-t12-pre3-clean/drivers/char/moxa.cWed May 3 10:45:18 2000
+++ linux/drivers/char/moxa.c Wed Nov 29
The following patch moves the page_table_lock in mm/* to cover the
modification of mm-rss in 240-test12-pre7. It was inspired by a
can't we just change rss to count pages?
or are we worried about rss's over ~16 TB?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Hi.
The following patch makes some 'defined but not used' warnings go
away when compiling drivers/char/mxser.c without CONFIG_PCI (240t12p3).
It should apply cleanly.
--- linux-240-t12-pre3-clean/drivers/char/mxser.c Wed Nov 22 22:41:39 2000
+++ linux/drivers/char/mxser.c Wed Nov 29
Hi.
The following patch makes a 'defined but not used' warning go away
when compiling drivers/char/random.c without sysctl support (240t12p3).
(but should apply cleanly). I am aware that there is a sysctl section
of this code, but the function seems to belong where it is. I would be
happy to
Hello!
I just found two serious bugs in the YMF PCI legacy driver (i.e. the
driver that puts it to the Sound Blaster compatible mode).
pci_unregister_driver() was not called from the cleanup routine, which
caused a recoverable oops while running /sbin/lspci.
Also some module parameters were
Exactly, and you wouldn't set DPL=3 for interrupt 8 since a double-fault
can only occur from ring 0..
Richard Moore - RAS Project Lead - Linux Technology Centre (PISC).
http://oss.software.ibm.com/developerworks/opensource/linux
Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183
IBM
Hi.
(Does anyone know the maintainer of this code?)
When compiling drivers/net/rclanmtl.c (240t12p3) I get a warning about
incompatible pointer assignment. As far as I can tell it has appeared
because PU32 has been changed to __u32* since test9 (where it was an
unsigned long*). The following
Hi.
This patch makes a 'defined but not used' warning go away when compiling
drivers/net/tokenring/smctr.c without module support (kernel 240t12p3).
(It should apply cleanly.)
--- linux-240-t12-pre3-clean/drivers/net/tokenring/smctr.c Sat Nov 4 23:27:09
2000
+++
On Fri, 8 Dec 2000, Udo A. Steinberg wrote:
+ /* disable advertising the flow-control capability */
+ sp-advertising = ~0x0400;
+ mdio_write(ioaddr, sp-phy[0] 0x1f, sp-advertising);
^^^
On Fri, 08 Dec 2000, Linus Torvalds wrote:
Btw, I also think that the dirty buffer flushing should get the page lock.
Right now it touches the buffer list without holding the lock on the page
that the buffer is on, which means that there is really nothign that
prevents it from racing with the
Hi.
The following patch makes a 'defined but not used' warning go
away when compiling drivers/net/irda/w83977af_ir.c without
modular support (kernel 240t12p7). It also removes some unneeded
zero initializations.
--- linux-240-t12-pre7-clean/drivers/net/irda/w83977af_ir.c Wed Nov 22
Jeff Garzik wrote:
Clayton Weaver wrote:
Shouldn't the setting of the CSR0 value for x86 switch between normal
(0x01A08000) and cautious (0x01A04800) based on some notion of
what generation of pci bus is installed rather than what cpu the kernel
is compiled for?
No, you
This email is here to announce the availability of a port of ORBit (the
GNOME ORB) to the Linux kernel. This ORB, named kORBit, is available from
our sourceforge web site (http://korbit.sourceforge.net/). A kernel ORB
allows you to write kernel extensions in CORBA and have the kernel call
into
Er... Well, the traditional solution has been "don't build it into your
kernel if you don't want it", but in the case of stock kernels, that
isn't always an option, I suppose. Theoretically, the two devices
shouldn't step on each other, but this is a computer. Theory is so far
removed from
On Fri, 8 Dec 2000, Daniel Phillips wrote:
[ flush-buffers taking the page lock ]
This is great when you have buffersize==pagesize. When there are
multiple buffers per page it means that some of the buffers might have
to wait for flushing just because bdflush started IO on some other
Date:Fri, 8 Dec 2000 15:36:35 -0500 (EST)
From: Mark Hahn [EMAIL PROTECTED]
can't we just change rss to count pages?
This is what it does now.
or are we worried about rss's over ~16 TB?
If we weren't, we could just use an atomic_t for this problem.
We can't.
This patch
I didn't have time to do more than just quickly apply the patch and leave
in a hurry, but my Vaio certainly recognized the serial port on the combo
cardbus card I have with this patch. Everything looked fine - I got a
message saying it found a 16450 on ttyS4 when I plugged the card in.
Ted, I
On Fri, 8 Dec 2000, Matan Ziv-Av wrote:
Hi,
I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with
large disks. I use a jumper to clip it to 32GB size, so the bios can
boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB,
and not the true size, and even
On Fri, Dec 08, 2000 at 01:27:51PM -0800, Linus Torvalds wrote:
(Of course, I use tulip instead of epic100, so maybe there's an epic
driver bug, but it's definitely hotplug-aware).
There could be a problem in the epic driver; I've never had a card
that uses this driver and have only limited
On Fri, 8 Dec 2000, Alan Cox wrote:
Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
;-)
Please boot 2.2.18pre24 (not pre25) [...]
Please pardon the naive question: is pre-patch-2.2.18-24 to be applied
Resent patch, hope that it will be acknowledged or discussed.
Xuân. :o)
Hello,
I discovered a bug in netfilter and worked the last 4 days to track it
down (I'm not a kernel hacker...):
Symptoms:
"Sometimes" the ip_conntrack module won't unload. rmmod or modprobe -r
would stay unkillably
Petr,
Thanks for testing this and finding a working counterexample! I am still
professionally interested to know if the difference is that you are
running a 2.4 kernel, or the glibc. Anyone running a 2.2 kernel with
glibc 2.2 want to drop me a line?
-Peter
(gdb) run
...
[New Thread 25452]
On Fri, 8 Dec 2000 11:30:06 -0500 (EST),
"Georg Nikodym" [EMAIL PROTECTED] wrote:
But since you seem to and while we're doing extreme surgery, why have
klogd at all? Every other unix, kernel messages are handled by the
syslog system. What problem did klogd solve and does that problem
still
Mike Kravetz wrote:
George,
I can't answer your question. However, have you noticed that this
lock ordering has changed in the test11 kernel. The new sequence is:
read_lock_irq(tasklist_lock);
spin_lock(runqueue_lock);
Perhaps the person who made this change could
On Fri, 8 Dec 2000, Jeff V. Merkey wrote:
I have not seen it on UP systems either. I only see it on SMP systems.
After trying very hard last night, I was able to get my 4 x PPro system to
do it with 2.4.0-12. It seems related to loading in some way. If you
have more than two processors,
On Fri, 8 Dec 2000, Linus Torvalds wrote:
On Fri, 8 Dec 2000, Alexander Viro wrote:
Erm... So you want to make -commit_write() page-unlocking? Fine with me,
but that will make for somewhat bigger patch. Hey, _you_ are in position
to change the locking rules, freeze or not, so if
Petr,
It ran fine on my stock Mandrake 7.2 system - linux-2.2.17-21mdk and
glibc-2.2-5mdk. The program ran fine in both environments - command line
and gdb-5.0. Loadavg creeps up slowly as the program continues to run. At
thread #37000, loadavb is 3.65. The ps command indicates 4 threads
On Fri, 8 Dec 2000 07:58:06 -0500 (EST),
"Richard B. Johnson" [EMAIL PROTECTED] wrote:
Too many people just want to argue without even reading what they
are arguing against. Again, I implied nothing. I said;
(1) User traps, CPL3, stack for trap is in CPL0.
(2) CPL0 has stack-fault (bad ring
Hi,
I was a GlobeCom 2 weeks ago, and I noticed a few articles
relevant to Linux networking that you might be interested in
reading...
On ECN :
--
Archan Misra, John Baras Teunis Ott. Generalised TCP
Congestion Avoidance and its Effect on Bandwidth Sharing and
Ion Badulescu wrote:
Ok. Can you send me the entire dump? Also, it would be helpful if you
could try to determine when exactly it happens (upon insmod, upon ifconfig
up, or upon receiving some packets later).
I have the eepro driver compiled into a monolithic kernel. After rebooting
a
On 8 Dec 2000, Christoph Rohland wrote:
Linus Torvalds [EMAIL PROTECTED] writes:
On 8 Dec 2000, Christoph Rohland wrote:
here is my first shot for cleaning up the shm handling. It did
survive some basic testing but is not ready for inclusion.
The only comment I have right
On Fri, 8 Dec 2000, Alexander Viro wrote:
I'm quite aware of that fact ;-) However, you said
On the other hand, I have this suspicion that there is an even simpler
solution: stop using the end_buffer_io_sync version for writes
altogether.
If that happens (i.e. if write
On Fri, Dec 08, 2000 at 11:24:56PM +0200, Matan Ziv-Av wrote:
I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with
large disks. I use a jumper to clip it to 32GB size, so the bios can
boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB,
and not the true size,
* put cable in *
eth0: card reports no RX buffers.
eth0: card reports no resources.
eth0: card reports no RX buffers.
eth0: card reports no resources.
you know, this might be entirely unrelated, but i had the exact same type of
problem with a brand new machine running a not-so-brand new
On Fri, 8 Dec 2000 14:14:31 -0500,
"Jean-Francois Nadeau" [EMAIL PROTECTED] wrote:
Dec 7 17:01:54 trinity kernel: EIP:
0010:[update_vm_cache_conditional+138/328]
You are letting klogd convert the oops, it is broken. Change klogd to
run with "klogd -x", reproduce the oops and get a clean
David Woodhouse [EMAIL PROTECTED] said:
[...]
I quote from the X devel list, which perhaps I shouldn't do but this is
hardly NDA'd stuff:
On Mon 20 Nov 2000, [EMAIL PROTECTED] said:
I have seen random crashes on dual P3 BX boards (Tyan) and dual Xeon
GX boards (Intel). XFree86 core
In article [EMAIL PROTECTED] you wrote:
That could even be automated when this little patch (against -test11, but
-test12pre works too) is applied...
Ok, I should actually attach the test11-final patch ;)
Christoph
--
Whip me. Beat me. Make me maintain AIX.
diff -uNr
On Thu, 7 Dec 2000, Johannes Erdfelt wrote:
Could you try the alternate UHCI driver? You may need to disable the
UHCI driver you have configured for the option to become visible.
Differently broken:
uhci: host controller process error. something bad happened
uhci: host
Loading the module would cause a very loud monotone
squeal, like some kind of theft detection device. The computer
Thats actually a generic bug in both ALSA and the kernel AC97 driver
(fixed in 2.2 and by Linus in 2.4test). It is feedback between the microphone
and speakers
-
To
Yes, and I believe that this is what's broken about the SCSI midlayer. The the
io_request_lock cannot be completely released in a SCSI HBA because the flags
You can drop it with spin_unlock_irq and that is fine. I do that with no problems
in the I2O scsi driver for example
-
To unsubscribe
Well, I've found that VM-global patch before, of course. Until now, the
last version was against pre18. Since I do not know the exact rules for
including new things into Alan's tree, I thought that VM-global patch was
already included in pre24. Sorry for my lack of experience. ;-)) I
{0x414B4D01, "Asahi Kasei AK4540 rev 1", NULL},
+ {0x41445303, "Yamaha YMF" , NULL},
Are you sure it's correct? I am almost certain that no YMFxxx
Its definitely wrong
has on-chip AC97. I'd like to see a document that allows you
the change quoted above.
4144 is
That could even be automated when this little patch (against -test11, but
-test12pre works too) is applied...
+# MANPATH specifies where to install the manpages created from
+# inline documentation
+#
+
+MANDIR := /usr/share/man
+
End user installed so
/usr/local/man or
So you're saying that you got this to work? Because I certainly couldn't
get it working with a higher version either. I would really love a
I read straight down it anf realised you referenced obsolete versions of
tg-created and thus broadcast incorrectly
I apologize for my ignorance -- I
I'll try.
Jeff
On Fri, Dec 08, 2000 at 10:24:55PM +, David Woodhouse wrote:
On Fri, 8 Dec 2000, Jeff V. Merkey wrote:
I have not seen it on UP systems either. I only see it on SMP systems.
After trying very hard last night, I was able to get my 4 x PPro system to
do it with
On Fri, 8 Dec 2000, Alan Cox wrote:
Yes, and I believe that this is what's broken about the SCSI midlayer. The the
io_request_lock cannot be completely released in a SCSI HBA because the flags
You can drop it with spin_unlock_irq and that is fine. I do that with no
problems in the I2O
I am running the 2.2.14 linux kernel, and doing
buffered writes to disk. Whenever kupdate runs, I
notice that the I/Os freeze up, sometimes taking 10-20
seconds to complete. Are there any patches to the
kernel to prevent thsi kind of behaviour ? I am using
the standard bdflush parameters. Is this
Just in case you didn't catch it: this is not a PCI v2.0 vs. v2.1 issue.
The older Tulips work great with PCI v2.0 and v2.1. The bug is with longer
bursts and a specific i486 chipset/motherboard.
Which chipset. I can then add it to the PCI quirks and we can do it nicely
in 2.4 so that
On Fri, 8 Dec 2000, Alan Cox wrote:
Yes, and I believe that this is what's broken about the SCSI midlayer. The the
io_request_lock cannot be completely released in a SCSI HBA because the flags
You can drop it with spin_unlock_irq and that is fine. I do that with no
problems
With the purpose of having two printers connected to my Linux server I
bought a PCI (single port) parallel port card thinking that installation
would be straightforward.
Parport was already compiled into the kernel (version 2.2.17), and lp is
a module.
After looking at the output from 'lspci
On Fri, Dec 08, 2000 at 04:03:58PM -0800, Matthew Jacob wrote:
On Fri, 8 Dec 2000, Alan Cox wrote:
Yes, and I believe that this is what's broken about the SCSI midlayer. The the
io_request_lock cannot be completely released in a SCSI HBA because the flags
You can drop it with
On Fri, 8 Dec 2000, Alan Cox wrote:
Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
;-)
Please boot 2.2.18pre24 (not pre25) [...]
Please pardon the naive question: is pre-patch-2.2.18-24 to
I am actually concerned about the following case:
The add_request ON CPU_1 function calls
spin_lock_irqsave(io_request_lock,flags);
Our I/O Function unlocks the spinlock and goes to sleep.
Finally, the add_request function, NOW ON CPU_2 calls
On Fri, 8 Dec 2000, Alan Cox wrote:
Yes, and I believe that this is what's broken about the SCSI midlayer. The the
io_request_lock cannot be completely released in a SCSI HBA because the flags
You can drop it with spin_unlock_irq and that is fine. I do that with no
You can drop it with spin_unlock_irq and that is fine. I do that with no
problems in the I2O scsi driver for example
I am (like, I think I *finally* got locking sorta right in my QLogic driver),
but doesn't this still leave ints blocked for this CPU at least?
spin_unlock_irq
This is a second posting, I just got back onto the
kernel mailing list. The first was sent via dejanews. So If this looks
familiar... It is. Ignore It.
Hi all, I seem to be having some problems
configuring kernels 2.2.16 and 2.2.17 to nfsroot boot. I have two machines at a
friends house I
On Sat, 9 Dec 2000, Alan Cox wrote:
Just in case you didn't catch it: this is not a PCI v2.0 vs. v2.1 issue.
The older Tulips work great with PCI v2.0 and v2.1. The bug is with longer
bursts and a specific i486 chipset/motherboard.
Which chipset. I can then add it to the PCI quirks and
In article [EMAIL PROTECTED] you wrote:
This email is here to announce the availability of a port of ORBit (the
GNOME ORB) to the Linux kernel.
OMG you guys are so cool :)
Hey, this is real craftsmanship (not sure if it useful :)
Does this revamp the Micro Kernel Discussin? ONLY KIDDING :)
Hi guys,
Not sure if this is the right list for this, but I'll spew this forward
too you. Redirects to right place is definitiely welcome. Since I added the
reiserfs kernel patch , I figured I'd mention it.
Problem:
When building the kernel things buld fine with no errors other than the
Alan wrote :
struct wireless_physical
struct wireless_80211
struct wireless_auth
Please do not underestimate 802.11 (and others). Even two
cards based on the same MAC controller can have very different way to
On Fri, Dec 08, 2000, David Woodhouse [EMAIL PROTECTED] wrote:
On Thu, 7 Dec 2000, Johannes Erdfelt wrote:
Could you try the alternate UHCI driver? You may need to disable the
UHCI driver you have configured for the option to become visible.
Differently broken:
uhci: host
On Fri, Dec 08, 2000, Johannes Erdfelt [EMAIL PROTECTED] wrote:
On Fri, Dec 08, 2000, David Woodhouse [EMAIL PROTECTED] wrote:
On Thu, 7 Dec 2000, Johannes Erdfelt wrote:
Could you try the alternate UHCI driver? You may need to disable the
UHCI driver you have configured for the
Alan Cox wrote:
Why is 2.2.18 proc_fs.c different than both 2.2.17 and 2.4.0? Cox, would
you accept a patch that makes 2.2.18 define create_proc_info_entry and
related functions the same way that 2.4.0 does?
Send me a diff and I'll be happy to
Here it is, both inlined and as an
On Fri, 8 Dec 2000 16:53:16 -0800,
"David D.W. Downey" [EMAIL PROTECTED] wrote:
When building the kernel things buld fine with no errors other than the
standard warnings generated by -Wall. Running the make dep bzImage modules
modules_install command completes. Nothing big there, but when i
I reported this earlier. Now with 2.2.18pre25 and today's CVS is is past
the place where it crashed.
Sorry for the red herring.
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vin~a del Mar, Chile +56 32 672616
-
To unsubscribe from
Alan,
The mouse problems have gone away with the 2.2.18-25 pre-patch. I
am not seeing the problems anymore on the affected systems. I am
trying this evening to apply the 2.4 patch sent to me to see if it
helps with the page cache corruption problem with fork().
Jeff
-
To unsubscribe from
Donald Becker [EMAIL PROTECTED] said:
[...]
The best way to check for this buggy chipset was to check for a 486
processor. There are very few 486 chips on non-buggy motherboards, and the
performance impact of shorter PCI bursts is minimal given the slow speed of
the 486.
Enable it #if
Marc,
if more / other information is needed let me know.
I'll try to go through the points as described in
/usr/src/linux/REPORTING-BUGS:
[1.] Bug reported on system startup.
[2.] no obvious problem detected besides this message
besides apic errors on both CPUs.
[3.] kernel BUG at
Michael Rothwell wrote:
Alan Cox wrote:
Why is 2.2.18 proc_fs.c different than both 2.2.17 and 2.4.0? Cox, would
you accept a patch that makes 2.2.18 define create_proc_info_entry and
related functions the same way that 2.4.0 does?
Send me a diff and I'll be happy to
Here it
On Fri, 8 Dec 2000, Linus Torvalds wrote:
Looking more at this issue, I suspect that the easiest pretty solution
that everybody can probably agree is reasonable is to either pass down the
end-of-io callback to ll_rw_block as you suggested, or, preferably by just
forcing the _caller_ to do
301 - 400 of 420 matches
Mail list logo
