FYI, I just MFC'ed this change to RELENG_6. I do not plan to MFC it to
RELENG_5. I believe this will help avoid the symptoms of the most common
user errors that we see complaints about on the mailing list, and my
personal mailbox.
I tested the changes thoroughly on both HEAD and RELENG_6, so I do
Daniel Dvoøák wrote:
> Hi all,
>
> first of all, I´m sorry maybe for my bad English.
>
> We have 2 routers which I maintain in our mesh wireless community network.
>
> The Router 1 has 2 atheros adapters, ath0=wistron cm9, ath1=wistron cm10, of
> course some sisX, fxpX and so on.
> The Router
On Fri, 01 Sep 2006 21:26:05 +0600
"S. M. Ibrahim (Lavlu)" <[EMAIL PROTECTED]> wrote:
> i am totally new with freeBSD 6.1
> I installed it yesterday. Everything goes ok, but problem with sound
> card, It's a builtin Intl HDA on gigabyte 915G-DU motherboard.
> I added the line
>
> sound_load="YES"
Hi all,
first of all, I´m sorry maybe for my bad English.
We have 2 routers which I maintain in our mesh wireless community network.
The Router 1 has 2 atheros adapters, ath0=wistron cm9, ath1=wistron cm10, of
course some sisX, fxpX and so on.
The Router 2 has 1 atheros adapter, ath1=wistron
Hi all,
first of all, I´m sorry maybe for my bad English.
We have 2 routers which I maintain in our mesh wireless community network.
The Router 1 has 2 atheros adapters, ath0=wistron cm9, ath1=wistron cm10, of
course some sisX, fxpX and so on.
The Router 2 has 1 atheros adapter, ath0=wistron
On closer inspection this means that we've run out of KVA. In
principle it should be handled more gracefully, but the 1GB KVA
limitation is really a 32-bit artifact. It might be worth wading
through the kernel memory allocations to see if a subsystem has gone
beserk.
Kip Macy wrote:
I've seen this when running stress2 with a large number of
incarnations. Why don't we return an error to the user?
programmer ENOTIME
patch welcome!
-Kip
On 9/1/06, Julian Elischer <[EMAIL PROTECTED]> wrote:
Vyacheslav Vovk wrote:
can you see how many t
Hello Vyacheslav,
Friday, September 1, 2006, 10:07:57 PM, you wrote:
> Hello Julian,
> Friday, September 1, 2006, 7:27:15 PM, you wrote:
>> Vyacheslav Vovk wrote:
>> can you see how many threads thre are in the system?
>> I think you will have to extract this information frome the zone allocat
i was seeing up to 14s suspends on /scr10 prior to the reconfig causing
mount point to be unresponsive on the clients. i'm using async option
also. the rsync is still going so won't go live again 'til next week.
thanks for the help.
--
Kevin Kramer
Sr. Systems Admi
I've seen this when running stress2 with a large number of
incarnations. Why don't we return an error to the user?
-Kip
On 9/1/06, Julian Elischer <[EMAIL PROTECTED]> wrote:
Vyacheslav Vovk wrote:
can you see how many threads thre are in the system?
I think you will have to ext
Hello Julian,
Friday, September 1, 2006, 7:27:15 PM, you wrote:
> Vyacheslav Vovk wrote:
> can you see how many threads thre are in the system?
> I think you will have to extract this information frome the zone allocator.
how to do it practically?
> I just realised there is no effective limit
On Fri, Sep 01, 2006 at 10:16:09AM -0500, Kevin Kramer wrote:
> I've already redone the whole thing. here are the steps i took
>
> umount /scr09
> umount /scr10
> gjournal stop da2.journal
> gjournal stop da4.journal
>
> ** had not done this on the first attempt
> newfs /dev/da1
> newfs /dev/da3
Patrick M. Hausen wrote:
Hi, all!
We just set a brand new Intel SSR212CC box into production.
This is basically a standard server with 2 LSI SATA RAID
controllers and 12 drive bays in 2 rack units height.
Intel sells it as a storage product. There's a variant
of Windows 2003 server that turns t
Hi, all!
We just set a brand new Intel SSR212CC box into production.
This is basically a standard server with 2 LSI SATA RAID
controllers and 12 drive bays in 2 rack units height.
Intel sells it as a storage product. There's a variant
of Windows 2003 server that turns this box into an iSCSI
targe
On Friday 01 September 2006 11:26 am, S. M. Ibrahim (Lavlu) wrote:
> i am totally new with freeBSD 6.1
> I installed it yesterday. Everything goes ok, but problem with
> sound card, It's a builtin Intl HDA on gigabyte 915G-DU
> motherboard. I added the line
>
> sound_load="YES"
> snd_driver_load="Y
Vyacheslav Vovk wrote:
can you see how many threads thre are in the system?
I think you will have to extract this information frome the zone allocator.
I just realised there is no effective limit on kernel threads in the system.
probably one could cause this with a fork bomb appoach using forks
Robert Watson wrote, On 1.9.2006 11:46:
>
> On Thu, 31 Aug 2006, Václav Haisman wrote:
>
>> I found this in logs of 6.1 box that I admin this morning. The machine
>> keeps running after that.
>
> Indeed, there does appear to be a problem in the TCP socket option code
> with respect to performi
On Fri, Sep 01, 2006 at 09:54:23PM +0600, S. M. Ibrahim (Lavlu) wrote:
> On Fri, 2006-09-01 at 21:02 +0530, Joseph Koshy wrote:
> > > I installed it yesterday. Everything goes ok, but problem
> > > with sound card, It's a builtin Intl HDA on gigabyte 915G-DU
> > > motherboard. I added the line
> >
On Fri, 2006-09-01 at 21:02 +0530, Joseph Koshy wrote:
> > I installed it yesterday. Everything goes ok, but problem
> > with sound card, It's a builtin Intl HDA on gigabyte 915G-DU
> > motherboard. I added the line
> >
> > sound_load="YES"
> > snd_driver_load="YES"
> > snd_cmi_load="YES"
> >
> > t
I installed it yesterday. Everything goes ok, but problem
with sound card, It's a builtin Intl HDA on gigabyte 915G-DU
motherboard. I added the line
sound_load="YES"
snd_driver_load="YES"
snd_cmi_load="YES"
to /boot/loader.conf but sound is not working.
Things to check:
- Does loading the dri
i am totally new with freeBSD 6.1
I installed it yesterday. Everything goes ok, but problem with sound
card, It's a builtin Intl HDA on gigabyte 915G-DU motherboard.
I added the line
sound_load="YES"
snd_driver_load="YES"
snd_cmi_load="YES"
to /boot/loader.conf but sound is not working.
Moreove
I've already redone the whole thing. here are the steps i took
umount /scr09
umount /scr10
gjournal stop da2.journal
gjournal stop da4.journal
** had not done this on the first attempt
newfs /dev/da1
newfs /dev/da3
gjournal label -v /dev/da2 /dev/da1
gjournal label -v /dev/da4 /dev/da3
newfs
On Fri, Sep 01, 2006 at 08:12:23AM -0500, Kevin Kramer wrote:
> we left the journaling devices raw. do i need to newfs the journaling device?
> is eveything else ok besides the newfs of the daX.journal?
Journal switch times are very long, but this could be caused by SU.
Could you try to disable S
Hi,
Search on conferences has not given the answer, only the reference to
similar problems
(http://lists.freebsd.org/pipermail/freebsd-stable/2006-June/026010.html),
therefore I shall ask here.
As well as in the above-stated reference there is highly loaded
machine, which periodically panic since
On Fri, 01 Sep 2006 10:54:57 -0300
chmod000 <[EMAIL PROTECTED]> wrote:
> Now I wish to know how to tune the loader.conf (I'm using relese 6.1)
> upgrading console resolution.
This is *not* done in /boot/loader.conf, but in /etc/rc.conf, see below.
>
> At a linux box I can set, in the boot loade
Hi,
On 9/1/06, chmod000 <[EMAIL PROTECTED]> wrote:
Hi there,
I'm starting my freebsd one way trip now.
I've allready installed basic system and some other stuffs via ports.
Now I wish to know how to tune the loader.conf (I'm using relese 6.1)
upgrading console resolution.
At a linux box I ca
Hi there,
I'm starting my freebsd one way trip now.
I've allready installed basic system and some other stuffs via ports.
Now I wish to know how to tune the loader.conf (I'm using relese 6.1)
upgrading console resolution.
At a linux box I can set, in the boot loader, this parameter: vga=791.
I
we left the journaling devices raw. do i need to newfs the journaling
device? is eveything else ok besides the newfs of the daX.journal?
--
Kevin Kramer
Sr. Systems Administrator
512.418.5725
Centaur Technology, Inc.
www.centtech.com
Pawel Jakub Dawidek wrote the
Pawel Jakub Dawidek wrote:
Hmm, using SU with gjournal is really bad choice and you didn't tell
file system that it is on gjournaled device. Try:
I suggest this to be prominent in the documentation :)
___
freebsd-stable@freebsd.org mailing list
http
On Thu, Aug 31, 2006 at 02:01:34PM -0500, Kevin Kramer wrote:
> Pavel,
>
> running 6.1-stable with these patches
> rebuilt kernel/world as of 8/28 @ 2p CST w/ these patches
>
> gjournal6_20060808.patch
> vfs_subr.c.3.patch
>
> the backend RAID presents 4 luns, this is how we config'd it.
> da1 -
On Thu, 31 Aug 2006, Václav Haisman wrote:
I found this in logs of 6.1 box that I admin this morning. The machine keeps
running after that.
Indeed, there does appear to be a problem in the TCP socket option code with
respect to performing copyin/copyout while holding the inpcb lock. This
p
31 matches
Mail list logo
