Displaying 5 results from an estimated 5 matches for "unsuable".
Did you mean:
unstable
2014 Oct 16
8
[Bug 85086] New: read/write faults leave machine unsuable
https://bugs.freedesktop.org/show_bug.cgi?id=85086
Bug ID: 85086
Summary: read/write faults leave machine unsuable
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at lists.freedesktop.org
Reporter: tethys...
2003 Jun 25
6
Mbuf Clusters on 4.8
...running out of mbuf
clusters. Im basically sending a 30k datachunk down
1000-4000 connections,
but 1000 is more than enough to quickly fill upp 8192
mbuf clusters. I also
tried setting maximum amount of mbuf clusters to 65536,
but that only made
the box hard-wire 86MB of 96MB RAM, making it just as
unsuable as a dead
machine.
Of course, when the machine runs out of mbuf clusters,
it dies. I also found
this with google:
"Finally, the fact that FreeBSD 3.x panics when it runs
out of
mbuf clusters is a well-known problem. The solution is
to not
let it run out of mbuf clusters by configuring a
suf...
2007 Aug 04
1
how to support xen in 2.6.23?
Hi folks
2.6.23 will support xen, but only partially. It lacks support for the
driver backends and other dom0 things.
We may just built it without xen-linux-system and without
hypervisor-compatibility settings, which makes update-grub to include it
with all available hypervisors. Or move the image away from /boot, which
makes it unusable with pygrub.
Bastian
--
He's dead, Jim.
-- McCoy,
2011 Dec 08
4
memory map issues with PV PCI passthrough
I have a system with several reserved ranges low in the e820 map which
cause problems when starting PV domains with PCI devices. The machine
memory map looks like:
(XEN) 0000000000000000 - 0000000000060000 (usable)
(XEN) 0000000000060000 - 0000000000068000 (reserved)
(XEN) 0000000000068000 - 000000000009ac00 (usable)
(XEN) 000000000009ac00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000
2001 Aug 06
5
rsync-2.4.7 NEWS file
I've gone through the CVS commit log and tried to get every
user-visible change since 2.4.6, so that we can make a proper
announcement for 2.4.7. Please let me know if anything is
missing/inaccurate.
At this stage I'm planning to release two 2.4.7pre tarballs, one with
the "large nohang patch" and one without. Some people inside VA will
be stress-testing both, and so we can