On Wed, Nov 29, 2000 at 01:38:01AM +0100, you [Andrea Arcangeli] claimed:
> On Tue, Nov 28, 2000 at 01:44:18PM +0200, Ville Herva wrote:
> > try Andrea's vm-global-7 now. It seems to include the bits Rik posted, or
>
> It doesn't include the bits Rik posted because they were unnecessary.
Ummh. W
On Tue, Nov 28, 2000 at 01:44:18PM +0200, Ville Herva wrote:
> try Andrea's vm-global-7 now. It seems to include the bits Rik posted, or
It doesn't include the bits Rik posted because they were unnecessary.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
> Yes. The other problem I saw with 2.2.18pre vm wasn't an oops, it was a
> rampaging vm rambo that slaughtered my X while it was idle. Admittedly
That sounds like the vm stuff being sorted on yes.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Tue, Nov 28, 2000 at 12:57:59PM +, you [Alan Cox] claimed:
> > I wasn't the one who used cdrom, so it is possible, that the person in
> > question had been able to eject the cd without unmounting it first. I'll
> > check if the door locking on that device works.
>
> Also rpm -e magicdev --
> I wasn't the one who used cdrom, so it is possible, that the person in
> question had been able to eject the cd without unmounting it first. I'll
> check if the door locking on that device works.
Also rpm -e magicdev --nodeps if magicdev is on the box.
> But you are certain that the oops was e
On Tue, Nov 28, 2000 at 12:45:49PM +, you [Alan Cox] claimed:
> > BTW: What are those seemingly harmless "VFS: busy inodes on changed
> > media." messages I'm getting tons of?
>
> They are not harmless. Someone forcibly unmounted a disk of some sort
> from a device that was in use, and while
> BTW: What are those seemingly harmless "VFS: busy inodes on changed
> media." messages I'm getting tons of?
They are not harmless. Someone forcibly unmounted a disk of some sort
from a device that was in use, and while that shouldnt have killed the box
it seems it did
Alan
-
To unsubscribe fr
Short answer UHCI JE does work for me, no more strange errors...
The weird thig is that I have used 2.2 USB backports since the begining,
but I have always used the other UHCI, and up till now it used to work for
me, except for now, but now it seems to be ok w/ the JE variant.
Thanks for the hel
On Fri, Nov 03, 2000 at 02:08:53AM +0100, Sasi Peter wrote:
> On Thu, 2 Nov 2000, Greg KH wrote:
>
> > Could you send the result of /proc/interrupts and 'lspci -v'?
> > Also, have you tried the alternate UHCI controller driver?
> > Or tried USB as modules, instead of compiled in?
>
> Here you go
On Fri, Nov 03, 2000, Sasi Peter <[EMAIL PROTECTED]> wrote:
> On Thu, 2 Nov 2000, Greg KH wrote:
>
> > Could you send the result of /proc/interrupts and 'lspci -v'?
> > Also, have you tried the alternate UHCI controller driver?
> > Or tried USB as modules, instead of compiled in?
>
> Here you go
On Thu, 2 Nov 2000, Greg KH wrote:
> Could you send the result of /proc/interrupts and 'lspci -v'?
> Also, have you tried the alternate UHCI controller driver?
> Or tried USB as modules, instead of compiled in?
Here you go. I did work w/ the very same hw with pre15.
I have never really knew wha
On Thu, Nov 02, 2000 at 11:26:18AM +0100, Sasi Peter wrote:
> Hi!
>
> Seems like something in USB went wrong from pre15, I get something like
> what is in the attachment.
>
> I have tried using HID + mouse, HID BP, disabling event interface,
> disabling hot-plug support, disabling preliminary U
On Thu, 2 Nov 2000, Sasi Peter wrote:
> Seems like something in USB went wrong from pre15, I get something like
> what is in the attachment.
In now.
> I have tried using HID + mouse, HID BP, disabling event interface,
> disabling hot-plug support, disabling preliminary USB fs, disabling
> band
13 matches
Mail list logo
