On Sun, 3 Feb 2008, Kostik Belousov wrote:
KB Di you have the UFS volume mounted from the eSATA drive ? If yes, then the
KB panic is the natural consequence of the device disappearing from under the
KB UFS. If not, and fault address 0x3020e0b30 looks suspicious, it could mean
KB some kernel
Hi!
There is any plan for the ethernet driver Broadcom BCM5906M?
I have a new laptop (Dell Vostro 1400) with this ethernet, but doesn't
work with bge or any b*e driver :-(
Thank you very much and please, excuse me the cross-posting.
--
Have a nice day ;-)
TooManySecrets
I have a dell vostro 1000 and I had the nic working under 6.2 using NDIS but
I have have not been able to get my NIC working under 6.3 or 7 using any
windows drivers and ndis.
Darran
http://www.deejc.net
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
TB --- 2008-02-03 08:49:47 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-02-03 08:49:47 - starting RELENG_7 tinderbox run for amd64/amd64
TB --- 2008-02-03 08:49:47 - cleaning the object tree
TB --- 2008-02-03 08:50:15 - cvsupping the source tree
TB --- 2008-02-03 08:50:15 -
On Sun, Feb 03, 2008 at 12:05:44PM +0300, Dmitry Morozovsky wrote:
On Sun, 3 Feb 2008, Kostik Belousov wrote:
KB Di you have the UFS volume mounted from the eSATA drive ? If yes, then the
KB panic is the natural consequence of the device disappearing from under the
KB UFS. If not, and fault
TB --- 2008-02-03 09:40:09 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2008-02-03 09:40:09 - starting RELENG_7 tinderbox run for i386/i386
TB --- 2008-02-03 09:40:09 - cleaning the object tree
TB --- 2008-02-03 09:40:31 - cvsupping the source tree
TB --- 2008-02-03 09:40:31 -
On Sun, 3 Feb 2008, Kostik Belousov wrote:
KB (kgdb) p *vp
KB $2 = {v_type = VDIR, v_tag = 0x8039319c ufs, v_op =
KB 0x804e98e0, v_data = 0xff003fab0480, v_mount =
0xff00050dc650,
KB The *v_mount and *(struct ufs_mount *)(v_mount-mnt_data) content shall
KB be enough
I had originally enabled gjournal and seemed to have no problems but I
was seeing errors in messages regarding dma write failures and after
some research concluded I had setup gjournal incorrectly.
I setup the gjournal again properly with soft updates disabled and
doing a fresh newfs, mount
Chris wrote:
Came back to see box had rebooted itself from a journal related panic.
panic: Journal overflow (joffset=49905408 active=499691355136 inactive=4990$
cpuid = 0
AFAIK this means that the journal is too small for your machine - try
doubling it until there are no more panics.
On Sun, Feb 03, 2008 at 09:35:44PM +0100, Ivan Voras wrote:
Chris wrote:
Came back to see box had rebooted itself from a journal related panic.
panic: Journal overflow (joffset=49905408 active=499691355136
inactive=4990$
cpuid = 0
AFAIK this means that the journal is too small for
Ivan Voras wrote:
Chris wrote:
Came back to see box had rebooted itself from a journal related panic.
panic: Journal overflow (joffset=49905408 active=499691355136
inactive=4990$
cpuid = 0
AFAIK this means that the journal is too small for your machine - try
doubling it until there
I did some experimentation with gjournal a few weeks ago to determine
how I might partition
a new server, as well as how large to make my journals and where. I did
find that for the computers
I have tested so far, a 1 gig (default size) journal seems to be
sufficient, but half of that or
AFAIK this means that the journal is too small for your machine - try
doubling it until there are no more panics.
If so, this is the same class of errors as ZFS (some would call it
tuning errors), only this time the space reserved for the on-disk
journal is too small, and the fast drives
Gary Palmer wrote:
On Sun, Feb 03, 2008 at 09:35:44PM +0100, Ivan Voras wrote:
If so, this is the same class of errors as ZFS (some would call it
tuning errors), only this time the space reserved for the on-disk
journal is too small, and the fast drives fill it up before data can be
Chris wrote:
If the only advantage of journaling is to avoid slow fsck's then I may
decide I can live without it, the real attraction to me was been able
to use the much glamorised async which is what made me so shocked when
write speeds were low.
If I understood this thread correctly, the
If I understood this thread correctly, the impression of poor
performance is based on a configuration where both the journal and the
data are on the same physical drive. Intuitively, this will likely
penalize any transaction on the volume, read or write, since you're
asking the drive to not
Michael Butler wrote:
I would think that journaling on one drive and storing the resultant
data-set on another would improve performance enormously (reduced
seek-lengths) and more so if they were 1) high-rpm drives (less
rotational latency) and 2) on different buses (no bus/controller
Chris wrote:
AFAIK this means that the journal is too small for your machine - try
doubling it until there are no more panics.
If so, this is the same class of errors as ZFS (some would call it
tuning errors), only this time the space reserved for the on-disk
journal is too small, and the fast
On Fri, Feb 01, 2008 at 03:56:17PM +0200, Andriy Gapon wrote:
on 01/02/2008 15:42 Andriy Gapon said the following:
on 01/02/2008 14:36 Pyun YongHyeon said the following:
After applying attached patch and let me know the output of
devid : xxx, revid : xxx, pwr = xxx. It would be even
On Mon, 4 Feb 2008, Ganbold wrote:
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
What does fstat /dev/cuad0 say?
--
Daniel O'Connor software and network engineer
for Genesis Software -
Hi,
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
daemon# uname -an
FreeBSD daemon.micom.mng.net 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0:
Mon Jan 14 16:49:57 ULAT 2008
[EMAIL
Daniel O'Connor wrote:
On Mon, 4 Feb 2008, Ganbold wrote:
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
What does fstat /dev/cuad0 say?
It says:
daemon# fstat /dev/cuad0
USER CMD
On Mon, Feb 04, 2008 at 12:53:58PM +0800, Ganbold wrote:
Hi,
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
Does the same happen if you do `cu -l ttyd0 -s 9600`?
How to check whether something is using
Jeremy Chadwick wrote:
On Mon, Feb 04, 2008 at 12:53:58PM +0800, Ganbold wrote:
Hi,
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
Does the same happen if you do `cu -l ttyd0 -s 9600`?
It works
On Mon, Feb 04, 2008 at 02:37:31PM +0800, Ganbold wrote:
Jeremy Chadwick wrote:
On Mon, Feb 04, 2008 at 12:53:58PM +0800, Ganbold wrote:
Hi,
I'm trying to use serial port but the system says device busy.
daemon# cu -l /dev/cuad0 -s 9600
/dev/cuad0: Device busy
link down
Does
Personally, I never understood the concept of dial-in and call-out
devices on FreeBSD. I ran BBS software for years on both Apple II
hardware and PC hardware; there was no distinction between such devices.
A serial port is a serial port. Chances are I'm not understanding why
there's a
26 matches
Mail list logo
