On Wed, 11 Oct 2000, Alan Cox wrote:
The was an error reported for 2.2.17:
Oct 12 14:55:46 iq kernel: VM: do_try_to_free_pages failed for kupdate...
...
Oct 12 00:50:49 iq kernel: VM: do_try_to_free_pages failed for smbd...
Oct 12 00:50:51 iq last message repeated 226 times
...
Oct 12 00:50:47 iq
On Wed, Oct 11, 2000 at 12:15:08AM +0200, Matthias Andree wrote:
> On Tue, 10 Oct 2000, Kurt Garloff wrote:
>
> > Actually, 2.0e3 did include one rather important fix which solved the
>
> Uh. Fix? This sounds like working around very broken devices to me, or
> are devices allowed to wreak havoc
I merged the stuff that was sent
-
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 Mon, 02 Oct 2000, Alan Cox wrote:
> 2.2.18pre11
> o Fix dead/clashing define for NFS(Trond Myklebust)
> 2.2.18pre9
> o NFSv3 support and NFS updates (Trond Myklebust and co)
2.2.18pre15's NFS support looks strange to me. My menuconfig screen
looks li
On Tue, 10 Oct 2000, Kurt Garloff wrote:
> Actually, 2.0e3 did include one rather important fix which solved the
Uh. Fix? This sounds like working around very broken devices to me, or
are devices allowed to wreak havoc if sync negotiation is tried in spite
of not being advertised in inquiry data
Kurt Garloff wrote:
> Actually, 2.0e3 did include one rather important fix which solved the
> trouble: Some devices get upset, when the driver tries to negotiate sync
> (or wide) connections, but the device actually does not support it.
> So, the driver now waits for the first INQUIRY result and
On Tue, Oct 10, 2000 at 11:52:33AM +0200, Matthias Andree wrote:
> On Mon, 02 Oct 2000, Alan Cox announced:
> > 2.2.18pre15
>
> I'd like to know if there are any issues with the current dc390-2.0e or
> 2.0e3 drivers that prevent its inclusion/that prevent Kurt from
> submitting it for inclusion.
On Mon, 02 Oct 2000, Alan Cox announced:
> 2.2.18pre15
I'd like to know if there are any issues with the current dc390-2.0e or
2.0e3 drivers that prevent its inclusion/that prevent Kurt from
submitting it for inclusion. As per the web page, 2.0e was supposed to
be sent to Linux for 2.4, so it sh
> Alan Cox wrote:
> > - Fix the megaraid (revert if need be)
>
> is this the source of repeated "Blocked mailbox..!!" messages which
> cause lock-ups on three Dell PowerEdge 2450s we have with AMI MegaRaid
> Enterprise 1500 controllers in them?
The current 2.2.18pre does this with certain sp
Alan Cox wrote:
> - Fix the megaraid (revert if need be)
is this the source of repeated "Blocked mailbox..!!" messages which
cause lock-ups on three Dell PowerEdge 2450s we have with AMI MegaRaid
Enterprise 1500 controllers in them?
Rob
--
Robert Brooks,Systems Manager,
On Wed, 4 Oct 2000 16:06:14 +0200 (CEST),
Michael Liljeblad <[EMAIL PROTECTED]> wrote:
>when compiling under Debian 2.2 the following (4) files are not compiled
>using gcc272. Is that the intended behaviour?
>
>scripts/mkdep.c
>scripts/split-include.c
>conmakehash.c
>tools/build.c
Not a problem.
Hi,
when compiling under Debian 2.2 the following (4) files are not compiled
using gcc272. Is that the intended behaviour?
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/mkdep
scripts/mkdep.c
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
scripts/split-include scri
Bug squash number three.
ARM, Alpha and x86 should be completely sorted for the loops_per_sec change.
S/390 merge yet to be done. PPC and Sparc still won't build.
Alan
Stuff left to do for 2.2.18final
- loops_per_jiffy for non x86, Alpha, ARM
- Merge the S/390 stuff and make S/390
13 matches
Mail list logo
