aka Vadim Goncharov schrieb
mit Datum Wed, 08 Sep 2010 04:31:46 +0700 in m2n.fbsd.stable:
|You do not understand the problem. It is not in notices & volunteers, but
|rather in the Project's policy - delete something which could still work.
|Personally, I don't use ISDN, so didn't said anythin
aka Kip Macy schrieb
mit Datum Fri, 12 Jun 2009 13:54:40 -0700 in m2n.fbsd.stable:
|show sleepchain
|show thread 100263
|
|On Fri, Jun 12, 2009 at 6:56 AM, Andriy Gapon wrote:
|>
|> I did zfs rollback x...@yyy
|> And then did ls on a directory in the rolled-back fs.
|> panic: sleeping thread
T
aka Peter Much schrieb
mit Datum Wed, 22 Jul 2009 09:51:52 GMT in m2n.fbsd.stable:
|After upgrading my system from 7.2-PRERELEASE to 7.2-STABLE (as
|of last week), and accordingly upgrading my Pools from Version
|6 to Version 13, I get this error when moving arbitrary files
|between different
Hi ZFS gurus!
After upgrading my system from 7.2-PRERELEASE to 7.2-STABLE (as
of last week), and accordingly upgrading my Pools from Version
6 to Version 13, I get this error when moving arbitrary files
between different ZFS filesystems.
While this seems not to do much harm (mv returns with 0),
aka Chuck Swiger schrieb
mit Datum Fri, 17 Jul 2009 13:49:10 -0700 in m2n.fbsd.stable:
|On Jul 17, 2009, at 12:12 PM, Peter Much wrote:
|[ ... ]
|> One other thing did happen between 03:51 and 03:52 - the DSL
|> internet connection did disconnect/reconnect and obtained a new
|>
The first thing I noticed was that my nameserver had gone.
I searched for the reason and found:
>Jul 15 04:04:52 edge kernel: swap_pager_getswapspace(3): failed
< ... hundreds more of these ... >
>Jul 15 04:05:07 edge kernel: pid 47113 (named), uid 53, was
killed: out of swap
! I'm also seeing the same issue, but I'm running a custom kernel. I've
! attached a diff from GENERIC.
Okay, I send You my diff. Good luck with experimenting!
Aeh, FYI: my graphics card identifies itself as
Matrox Graphics, Inc. MGA G400/G450 rev 4
and the "device mgadrm" has something to do
Hi all,
to make a long story short, I got trapped in the Xorg upgrade
problems (concerning HAL etc.) that were widely reported during
January.
After reading thru the material I figured out that there are
not much chances that somebody would take effort and fix these
things for a 6.3 Release.
So
Hi folks, hi Freddy,
sorry, missed Your note last year this time.
aka Freddie Cash schrieb
mit Datum Wed, 26 Mar 2008 14:04:00 -0700 in m2n.fbsd.stable:
|On March 22, 2008 01:01 pm Peter Much wrote:
|> Both of them were running Release 5.5, and they were doing all that
|> is needed, and
! Try the rev. 1.24 of the devfs_rule.c. In fact, it is fixed by somewhat
! bigger patch that I inlined below. It is already in CURRENT and RELENG_7.
Thanks, this is cool: it seems to work on Rel. 6.3. :)
rgds,
PMc
___
freebsd-stable@freebsd.org mailing
On Wed, Mar 26, 2008 at 10:06:04PM +0100, Kris Kennaway wrote:
! Software always has bugs, and it is a mistake to think that the "stable"
! designation does not mean "has no bugs". It's unfortunate that you have
! hit a couple of them, but please continue to work through the process of
! docume
On Wed, Mar 26, 2008 at 05:00:12PM -0400, John Baldwin wrote:
! Try this patch for de(4).
Thanks fpr the reply. I'll try this patch at next reboot.
! You need to supply the panic details for the devfs
! one (I've used devfs rules w/o issue on lots of machines
! via /etc/devfs.conf).
I have fo
Dear all,
I have two computers.
Both of them were running Release 5.5, and they were doing all that
is needed, and I was perfectly happy with this.
Now, as we know, security support for Release 5.5 will terminate
during this spring, and as my computers are exposed to the Internet,
this means
And the party continues...
When starting my usual environment, there is already the next pagefault
kernel panic!
Tracking it down... it's the "type" keyword in devfs rules. According
to the manpage, support for this was _not_ withdrawn.
But actually, entering something like
devfs rule
14 matches
Mail list logo
