On Wed, Nov 12, 2008 at 02:49:15PM +0200, Andriy Gapon wrote:
on 12/11/2008 14:33 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 02:20:41PM +0200, Andriy Gapon wrote:
on 12/11/2008 14:14 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon
on 12/11/2008 13:53 Nate Eldredge said the following:
On Wed, 12 Nov 2008, Andriy Gapon wrote:
on 05/11/2008 17:24 Andriy Gapon said the following:
[...]
I have a legacy-free system (no PS/2 ports, only USB) and I wanted to
try a kernel without atkbd and psm (with ums, ukbd, kbdmux), but
on 12/11/2008 15:21 Jeremy Chadwick said the following:
I don't know what to say to ***ANY*** of the above, other than this:
No one is doing anything about this problem because there does not
appear to be a 100% reproducible always-screws-up-when-I-do-this
scenario that happens to *every
I've got an Asus P5E3WSPro with 8 SATA ports and 8 disks attached. 6 disks
are on
one controller (and work perfectly) and 2 are on a second Marvell
controller.
FreeBSD sees the controller, but not the disks. If I move a working disk to
the
Marvell controller I can boot off it up to the stage of
Am Wed, 12 Nov 2008 12:36:19 +0300
schrieb pluknet [EMAIL PROTECTED]:
I have the same problem with my ukbdums:
they are power off'ed during the boot and I should to re-attach them .
MB: Asus p5k.
Hi,
I've noticed one thing today. I can switch off USB-Keyboard support in
my BIOS. In this
On Wed, Nov 12, 2008 at 02:20:41PM +0200, Andriy Gapon wrote:
on 12/11/2008 14:14 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote:
[snip]
2. if ukbd driver is not attached then I don't see any way USB keyboard
would work in non-legacy way
on 12/11/2008 14:14 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote:
[snip]
2. if ukbd driver is not attached then I don't see any way USB keyboard
would work in non-legacy way
Regarding #2: at which stage? boot0/boot2/loader require an AT or
Am Wed, 12 Nov 2008 05:21:24 -0800
schrieb Jeremy Chadwick [EMAIL PROTECTED]:
Until we settle down, stop replying to Emails with one-liner
injections, and compile a list of test scenarios/cases that people
can perform, and get these people to provide both 1) full hardware
details, 2) full
Michael Grant-3 wrote:
GlusterFS http://www.gluster.org seems promising. It is a replication
layer that sits on top of FUSE (Filesystem in Userspace
http://fuse.sf.net). You can replicate pretty much any type of file
system, ufs, zfs, dos...etc. In other words, you don't need to
Jeremy Chadwick wrote:
What really needs to happen here should be obvious: we need some form of
inexpensive keyboard-only USB support in boot2/loader.
I would *love* to know how Linux and Windows solve this problem.
If I remember right, UnixWare used(s) the BIOS calls in the loader.
-SB
On Wed, 12 Nov 2008, Andriy Gapon wrote:
on 05/11/2008 17:24 Andriy Gapon said the following:
[...]
I have a legacy-free system (no PS/2 ports, only USB) and I wanted to
try a kernel without atkbd and psm (with ums, ukbd, kbdmux), but was
bitten hard when I made a mistake and kernel could not
2008/11/11 Martin [EMAIL PROTECTED]:
Am Tue, 11 Nov 2008 10:55:45 -0800
schrieb Peter Wemm [EMAIL PROTECTED]:
Some bioses have a list of MBR partition id's and use that to
determine what to do with the USB keyboard. One of my ol older amd64
motherboards worked but would always disable the
I've been playing around with snapshots lately but I've got a problem on
one of my servers running 7-STABLE amd64:
FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51
GMT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PALADIN amd64
I run the mksnap_ffs command to take
on 05/11/2008 17:24 Andriy Gapon said the following:
System is FreeBSD 7.1-BETA2 amd64.
Looking through my dmesg I see that relative order of ukbd attachment
and root mounting is not deterministic. Sometime keyboard is attached
first, sometimes root filesystem is mounted first. Quite more
Sergey Babkin [EMAIL PROTECTED] writes:
Jeremy Chadwick [EMAIL PROTECTED] writes:
What really needs to happen here should be obvious: we need some
form of inexpensive keyboard-only USB support in boot2/loader.
If I remember right, UnixWare used(s) the BIOS calls in the loader.
So does
on 11/11/2008 20:55 Peter Wemm said the following:
Some bioses have a list of MBR partition id's and use that to
determine what to do with the USB keyboard. One of my ol older amd64
motherboards worked but would always disable the usb keyboard right as
loader started. I discovered the
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-freebsd-
[EMAIL PROTECTED] On Behalf Of Tim Bishop
Sent: 12 November 2008 07:58 PM
To: freebsd-stable@freebsd.org
Cc: [EMAIL PROTECTED]
Subject: System deadlock when using mksnap_ffs
FreeBSD paladin 7.1-PRERELEASE FreeBSD
Hello!
Currently, when a program built without OpenMP (-fopenmp) is trying to
dlopen a library, built with the feature, the result is a crash from
bad system call:
#0 0x0008009a223c in ksem_init () from /lib/libc.so.7
#1 0x000800998a8f in sem_init () from /lib/libc.so.7
#2
On Wed, Nov 12, 2008 at 06:22:35PM +, Tim Bishop wrote:
On Wed, Nov 12, 2008 at 08:10:50PM +0200, David Peall wrote:
FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10
20:49:51 GMT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PALADIN amd64
I run the mksnap_ffs
Sent by Kostik Belousov:
On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote:
Hello!
Currently, when a program built without OpenMP (-fopenmp) is trying to
dlopen a library, built with the feature, the result is a crash from
bad system call:
#0 0x0008009a223c in
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I've been playing around with snapshots lately but I've got a problem on
one of my servers running 7-STABLE amd64:
FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51
GMT 2008 [EMAIL
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I run the mksnap_ffs command to take the snapshot and some time later
the system completely freezes up:
paladin# cd /u2/.snap/
paladin# mksnap_ffs /u2 test.1
Someone (not named because they choose not to reply to the list) gave me
On Tue, Nov 4, 2008 at 8:47 AM, Adam McDougall [EMAIL PROTECTED] wrote:
Eduardo Meyer wrote:
Hello,
I have some serious issue. Sometimes something happens and my disk
usage performance find its limit quickly. I follow with gstat and
iostat -xw1, and everything usually happens just fine,
Sent by Daniel Eischen:
On Wed, 12 Nov 2008, Mikhail Teterin wrote:
Sent by Kostik Belousov:
On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote:
Hello!
Currently, when a program built without OpenMP (-fopenmp) is trying
to dlopen a library, built with the feature, the result
on 12/11/2008 14:33 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 02:20:41PM +0200, Andriy Gapon wrote:
on 12/11/2008 14:14 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote:
[snip]
2. if ukbd driver is not attached then I don't see
Sent by Daniel Eischen:
No, I simply meant that you saw it was returning bad system
call from sem_init/ksem_init.
Instead, I suspected, that it is the OpenMP, that's at fault. I'm sorry
for failing to live up to your expectations of a true FreeBSD user.
A little investigation would have turned
On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote:
Hello!
Currently, when a program built without OpenMP (-fopenmp) is trying to
dlopen a library, built with the feature, the result is a crash from
bad system call:
#0 0x0008009a223c in ksem_init () from
On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote:
on 12/11/2008 13:53 Nate Eldredge said the following:
On Wed, 12 Nov 2008, Andriy Gapon wrote:
on 05/11/2008 17:24 Andriy Gapon said the following:
[...]
I have a legacy-free system (no PS/2 ports, only USB) and I wanted to
On Wed, Nov 12, 2008 at 07:49:28PM +, Tim Bishop wrote:
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I run the mksnap_ffs command to take the snapshot and some time later
the system completely freezes up:
paladin# cd /u2/.snap/
paladin# mksnap_ffs /u2 test.1
On 13/11/2008, at 8:43 AM, Oliver Lehmann wrote:
Philip Murray wrote:
I used to get this (FreeBSD 6.1 days) all the time, the controller
would just lock up almost on a daily basis (and have to wait for the
fsck 4 out of 24 hours in the day).
Anyway, I stopped running 3dmd (or 3dm2 I think
Philip Murray wrote:
I used to get this (FreeBSD 6.1 days) all the time, the controller
would just lock up almost on a daily basis (and have to wait for the
fsck 4 out of 24 hours in the day).
Anyway, I stopped running 3dmd (or 3dm2 I think it's called now) to
monitor it, and the
On Wed, 12 Nov 2008, Mikhail Teterin wrote:
Sent by Kostik Belousov:
On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote:
Hello!
Currently, when a program built without OpenMP (-fopenmp) is trying to
dlopen a library, built with the feature, the result is a crash from bad
On Wed, 12 Nov 2008, Mikhail Teterin wrote:
Sent by Daniel Eischen:
On Wed, 12 Nov 2008, Mikhail Teterin wrote:
Sent by Kostik Belousov:
On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote:
Hello!
Currently, when a program built without OpenMP (-fopenmp) is trying to
dlopen
On Wed, Nov 12, 2008 at 08:10:50PM +0200, David Peall wrote:
FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10
20:49:51 GMT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PALADIN amd64
I run the mksnap_ffs command to take the snapshot and some time later
the system
I'm getting the following with clean, up to date sources (with the
BIND 9.4.2-P2 update, but that doesn't touch this area):
cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo
date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo
kenv.lo kill.lo ln.lo ls.lo mkdir.lo
On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote:
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I've been playing around with snapshots lately but I've got a problem on
one of my servers running 7-STABLE amd64:
FreeBSD paladin 7.1-PRERELEASE FreeBSD
On Thu, Nov 13, 2008 at 12:41:02AM +, Tim Bishop wrote:
On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote:
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I've been playing around with snapshots lately but I've got a problem on
one of my servers running
Jeremy Chadwick writes:
[snip]
| The rest of the below information is good -- but I'm confused about
| something: is there anyone out there who can use mksnap_ffs on a
| filesystem (/usr is a good test source) and NOT experience this
| deadlocking problem? Literally *every* FreeBSD box I
On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote:
...
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I've been playing around with snapshots lately but I've got a problem on
one of my servers running 7-STABLE amd64:
FreeBSD paladin 7.1-PRERELEASE
Kostik Belousov writes:
| On Wed, Nov 12, 2008 at 07:49:28PM +, Tim Bishop wrote:
| On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
| I run the mksnap_ffs command to take the snapshot and some time later
| the system completely freezes up:
|
| paladin# cd /u2/.snap/
|
On Wed, Nov 12, 2008 at 09:02:50PM -0800, David Wolfskill wrote:
On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote:
...
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I've been playing around with snapshots lately but I've got a problem
on
one of
Quoting Jeremy Chadwick, who wrote on Wed, Nov 12, 2008 at 08:42:00PM -0800 ..
On Thu, Nov 13, 2008 at 12:41:02AM +, Tim Bishop wrote:
On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote:
On Wed, Nov 12, 2008 at 05:58:26PM +, Tim Bishop wrote:
I've been playing around
On 2008-Nov-12 20:47:37 -0800, Doug Ambrisko [EMAIL PROTECTED] wrote:
I plan to commit it tomorrow since I sent it to Tim to test. The 10 can
be tuned but it has kept a bunch of machines at work up. Glad people
don't think it is that it is to wrong :-) It probably could be made
a little more
(moving my thread from -fs to -stable)
Before touching anything, here's a description of the symptoms I
see... Rather busy system, with quite a bit of filesystem activity
occurring while the snapshot is being made. Quad CPU amd64 box with
16GB of ram, 6x10Krpm RAID array. Should be
44 matches
Mail list logo
