Re: My wi(4) ate itself (or Fun with no memory).

2002-12-31 Thread Ants Aader
I have had almost exactly same problems about year ago. Orinoco silver stopped two times after 25 - 28 day working with freebsd current under somewhat strong load. Even after reboot it didn't work anymore. I burned two times new firmware and the card started to wor

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Michael Ranner <[EMAIL PROTECTED]> writes: : Am Montag, 30. Dezember 2002 23:10 schrieb Lee Damon: : > I have the same problems on an IBM T30 with integrated wi running : > 4.7-STABLE. In fact, I've had this problem since 4.5 (which is where I : > started

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Juli Mallett <[EMAIL PROTECTED]> writes: : /var/log/messages:Dec 30 17:11:35 luna kernel: wi0: failed to allocate 1594 bytes on :NIC : : Like those? Those are usually an indication of no interrupts. Memory is allocated when packets are sent and deallo

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Juli Mallett
* De: Taavi Talvik <[EMAIL PROTECTED]> [ Data: 2002-12-30 ] [ Subjecte: Re: My wi(4) ate itself (or Fun with no memory). ] > On Mon, 30 Dec 2002, M. Warner Losh wrote: > > > In message: <[EMAIL PROTECTED]> > > Juli Mallett <[EMAIL PROTECTED

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Taavi Talvik
On Mon, 30 Dec 2002, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Juli Mallett <[EMAIL PROTECTED]> writes: > : I ran some stuff overnight which exhausted my system's memory fairly well, > : and was also thrashing around on my network, and I woke up to find that my > : wi(4

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Kevin Oberman
> Date: Mon, 30 Dec 2002 23:06:50 +0100 > From: Christian Brueffer <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > > --x+6KMIRAuhnl3hBn > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Mon, Dec 30, 2002 at 11:36:4

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Michael Ranner
Am Montag, 30. Dezember 2002 23:10 schrieb Lee Damon: > I have the same problems on an IBM T30 with integrated wi running > 4.7-STABLE. In fact, I've had this problem since 4.5 (which is where I > started on this system.) I think the "wi0: timeout in wi_cmd 0x; event status 0x8000" messages st

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Juli Mallett
* De: Christian Brueffer <[EMAIL PROTECTED]> [ Data: 2002-12-30 ] [ Subjecte: Re: My wi(4) ate itself (or Fun with no memory). ] > The bad thing is, that the chip is integrated in my notebook so i can't simply > take it out and back in again :-) > Is there any other way

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Lee Damon
I have the same problems on an IBM T30 with integrated wi running 4.7-STABLE. In fact, I've had this problem since 4.5 (which is where I started on this system.) nomad > On Mon, Dec 30, 2002 at 11:36:45AM -0800, Juli Mallett wrote: > > Hey, > >=20 > > I ran some stuff overnight which exhausted my

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Christian Brueffer
On Mon, Dec 30, 2002 at 11:36:45AM -0800, Juli Mallett wrote: > Hey, > > I ran some stuff overnight which exhausted my system's memory fairly well, > and was also thrashing around on my network, and I woke up to find that my > wi(4) blew up more or less: > > wi0: watchdog timeout > wi0: timeout i

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Juli Mallett <[EMAIL PROTECTED]> writes: : I ran some stuff overnight which exhausted my system's memory fairly well, : and was also thrashing around on my network, and I woke up to find that my : wi(4) blew up more or less: : : wi0: watchdog timeout : w

My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Juli Mallett
Hey, I ran some stuff overnight which exhausted my system's memory fairly well, and was also thrashing around on my network, and I woke up to find that my wi(4) blew up more or less: wi0: watchdog timeout wi0: timeout in wi_cmd 0x0002; event status 0x8000 wi0: timeout in wi_cmd 0x; event stat