> Stock 2.0.36 kernel on Debian potato system, got the following
> after 33 then 35 days of uptime:
>
> (usually works just fine with my 2/4 dat)
>
> Jan 6 04:31:00 oi kernel: st: Unloaded.
> Jan 6 04:30:01 oi kernel: st0: Can't allocate tape buffer.
> Jan 6 04:30:01 oi kernel: st: Can't allocate new tape buffer (nbr 0).
> Jan 6 04:30:01 oi kernel: No tape buffers allocated at initialization.
> Jan 6 04:30:01 oi kernel: st: Can't allocate new tape buffer (nbr 0).
> Jan 6 04:30:01 oi kernel: Detected scsi tape st0 at scsi0, channel 0, id
> 2, lun 0
Memory fragmentation. You can work around it by quitting
Netscape or doing something else that frees up a ton of
memory.
There's no real fix for it in 2.2. We probably should
do something about it for 2.3...
Even a workaround where we reserve half a meg for DMA
buffers is probably better than the current situation.
cheers,
Rik -- If a Microsoft product fails, who do you sue?
+-------------------------------------------------------------------+
| Linux memory management tour guide. riel@humbolt.geo.uu.nl |
| Scouting Vries cubscout leader. http://humbolt.geo.uu.nl/~riel |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/