headers
Julian Elischer | 9 Feb 22:48
Picon
Favicon

known problems with 8.x and HP DL16 G5 server?

does anyone know of problems with freebsd and this system?

the kernel We tried to boot seems to stop somewhere in the ahci probing.

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Alexander Motin | 8 Feb 23:22
Picon
Favicon

Re: siisch1: Error while READ LOG EXT

On 08.02.2012 23:27, Jeremy Chadwick wrote:
> On Wed, Feb 08, 2012 at 04:00:57PM -0500, Mike Tancsa wrote:
>> I have a 4 port eSata PCIe card with 3 external port multipliers attached on an AMD64 box (8G of RAM),
RELENG8 from Feb1st.
>>
>> siis0 <at> pci0:5:0:0:       class=0x010400 card=0x71241095 chip=0x31241095 rev=0x02 hdr=0x00
>>      vendor     = 'Silicon Image Inc (Was: CMD Technology Inc)'
>>      device     = 'PCI-X to Serial ATA Controller (SiI 3124)'
>>      class      = mass storage
>>      subclass   = RAID
>>      bar   [10] = type Memory, range 64, base 0xb4408000, size 128, enabled
>>      bar   [18] = type Memory, range 64, base 0xb4400000, size 32768, enabled
>>      bar   [20] = type I/O Port, range 32, base 0x3000, size 16, enabled
>>      cap 01[64] = powerspec 2  supports D0 D1 D2 D3  current D0
>>      cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 12 split transactions
>>      cap 05[54] = MSI supports 1 message, 64 bit enabled with 1 message
>>
>> siis0:<SiI3124 SATA controller>  port 0x3000-0x300f mem
0xb4408000-0xb440807f,0xb4400000-0xb4407fff irq 19 at device 0.0 on pci5
>> siis0: [ITHREAD]
>> siisch0:<SIIS channel>  at channel 0 on siis0
>> siisch0: [ITHREAD]
>> siisch1:<SIIS channel>  at channel 1 on siis0
>> siisch1: [ITHREAD]
>> siisch2:<SIIS channel>  at channel 2 on siis0
>> siisch2: [ITHREAD]
>> siisch3:<SIIS channel>  at channel 3 on siis0
>> siisch3: [ITHREAD]
>>
>> # camcontrol devlist
(Continue reading)

Permalink | Reply | 8 comments |
headers
Mike Tancsa | 8 Feb 22:00

siisch1: Error while READ LOG EXT

I have a 4 port eSata PCIe card with 3 external port multipliers attached on an AMD64 box (8G of RAM), RELENG8
from Feb1st.

siis0 <at> pci0:5:0:0:       class=0x010400 card=0x71241095 chip=0x31241095 rev=0x02 hdr=0x00
    vendor     = 'Silicon Image Inc (Was: CMD Technology Inc)'
    device     = 'PCI-X to Serial ATA Controller (SiI 3124)'
    class      = mass storage
    subclass   = RAID
    bar   [10] = type Memory, range 64, base 0xb4408000, size 128, enabled
    bar   [18] = type Memory, range 64, base 0xb4400000, size 32768, enabled
    bar   [20] = type I/O Port, range 32, base 0x3000, size 16, enabled
    cap 01[64] = powerspec 2  supports D0 D1 D2 D3  current D0
    cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 12 split transactions
    cap 05[54] = MSI supports 1 message, 64 bit enabled with 1 message

siis0: <SiI3124 SATA controller> port 0x3000-0x300f mem
0xb4408000-0xb440807f,0xb4400000-0xb4407fff irq 19 at device 0.0 on pci5
siis0: [ITHREAD]
siisch0: <SIIS channel> at channel 0 on siis0
siisch0: [ITHREAD]
siisch1: <SIIS channel> at channel 1 on siis0
siisch1: [ITHREAD]
siisch2: <SIIS channel> at channel 2 on siis0
siisch2: [ITHREAD]
siisch3: <SIIS channel> at channel 3 on siis0
siisch3: [ITHREAD]

# camcontrol devlist
<WDC WD2001FASS-00U0B0 01.00101>   at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD2001FASS-00U0B0 01.00101>   at scbus0 target 1 lun 0 (pass1,ada1)
(Continue reading)

Permalink | Reply | 3 comments |
headers
Victor Balada Diaz | 8 Feb 13:11

i18n not working during startup

Hello,

I tried freebsd-i18n but no one answered, so i will try better luck here. Sorry
for the people who are subscribed to both lists.

----- Forwarded message from Victor Balada Diaz <victor <at> bsdes.net> -----

Date: Thu, 2 Feb 2012 19:17:21 +0100
From: Victor Balada Diaz <victor <at> bsdes.net>
To: freebsd-i18n <at> freebsd.org
Subject: i18n not working during startup
User-Agent: Mutt/1.5.21 (2010-09-15)

Hello,

I've setup login classes by handbook recommendation but seems that daemons started by rc
at system bootup don't use it. What i'm actually trying to do is configure tomcat to
use UTF-8 by default. I've configured it's user class on /etc/login.conf adding:

        :setenv=LC_ALL=en_US.UTF-8:\
        :lang=en_US.UTF-8:\

rebuilt login.conf db and tried rebooting. It doesn't seem to have lang or lc_all set
in their environment. As a workaround i thought about adding export lines at start of
/etc/rc.conf, but that's an ugly hack. 

Is there any other way of setting up lang settings for system startup daemons?

FreeBSD version: 7.4
Arch: amd64
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tim Bishop | 8 Feb 10:52
Gravatar

MFC misc/124164 (Add SHA-256/512 hash algorithm to crypt(3)) to stable/8?

Are there any committers willing to merge PR misc/124164 to stable/8
before the 8.3 release freeze? It's already in HEAD and stable/9 so it's
had some testing.

misc/124164 adds support for SHA256/512 to crypt(3). This is something
we make use of on Linux and FreeBSD 9, and it'd be great to have the
same support on FreeBSD 8.

http://www.freebsd.org/cgi/query-pr.cgi?pr=124164

SVN Revs: 220496 220497

I've tried markm@ already and had no response.

Thanks,

Tim.

--

-- 
Tim Bishop
http://www.bishnet.net/tim/
PGP Key: 0x5AE7D984
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Adam Vande More | 7 Feb 23:36
Picon

sndstat verbosity

The Handbook page on setting up sound says to find out which driver bound
to the system after doing a "kldload snd_driver" to run"cat /dev/sndstat".
In my versions of 8/9-STABLE, there is no way to determine what that driver
is from sndstat without increasing the verbosity of "hw.snd.verbose".  IMO,
either a bug should be filed against docs to include a mention of
increasing the verbosity, or sndstat should list the bound module in it's
default output.  Does anyone have feedback on this and if the bug should be
a doc or sndstat related one?

--

-- 
Adam Vande More
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Eugene M. Zheganin | 7 Feb 09:36
Picon
Gravatar

zfs arc and amount of wired memory

Hi.

I have a server with 9.0/amd64 and 4 Gigs of RAM.
Today's questions are about the amount of memory in 'wired' state and 
the ARC size.

If I use the script from http://wiki.freebsd.org/ZFSTuningGuide , it says:

===Cut===
ARC Size:                               12.50%  363.14  MiB
         Target Size: (Adaptive)         12.50%  363.18  MiB
         Min Size (Hard Limit):          12.50%  363.18  MiB
         Max Size (High Water):          8:1     2.84    GiB
===Cut===

At the same time I have 3500 megs in wired state:

===Cut===
Mem: 237M Active, 36M Inact, 3502M Wired, 78M Cache, 432K Buf, 37M Free
===Cut===

First question - what is the actual size of ARC, and how can it be 
determined ?
Solaris version of the script is more comprehensive (ran on Solaris):

===Cut===
ARC Size:
          Current Size:             6457 MB (arcsize)
          Target Size (Adaptive):   6457 MB (c)
          Min Size (Hard Limit):    2941 MB (zfs_arc_min)
(Continue reading)

Permalink | Reply | 31 comments |
headers
Eugene M. Zheganin | 6 Feb 19:47
Picon
Gravatar

VOP_WRITE <hex> is not exclusive locked but should be

Hi.

I have a server with an 8.2-RELEASE/amd64.
It's primary use for routing/ipsec+gre tunneling. It's also running zfs.

Sometimes it's locking up: it stops to respond to the network, but the 
console is still alive, though it doesn't log me in - the 'password:' 
prompt never comes up (I only can type my username or enter key).

I've built a kernel with DEBUG_LOCKS/DEBUG_VFS_LOCKS, KDB/DDB, 
INVARIANTS, WITNESS and stuff.
The only problem is that when booting such a new kernel and 
DEBUG_LOCKS/DEBUG_VFS_LOCKS are present, I get

VOP_PUTPAGES: <hex> is not exclusive locked but should be

and the kernel immidiately enters ddb. This happens on a daemons startup 
after the kernel is boot up and filesystems are mounted.

Is this something that is safe to ignore (then how do I ignore that ? 
'continue' only makes a new VOP_PUTPAGES message appear) ? Is it 
something that can lock up my server later on and should I report that ?

I saw similar message (only it was about VOP_WRITE) in this maillist 
about 7-STABLE, someone said to try a memtest. I did one pass of a 
memtest (I know this isn't enough, but I cannot run it there for a day, 
and, furthermore, I got this message in subject immidiately on multiuser 
boot sequence so my guess is - the errors should appear immidiately too) 
and it didn't find any errors.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ken Smith | 6 Feb 13:52
Favicon

Schedule for 8.3-RELEASE...


Just a quick note to say the target schedule for 8.3-RELEASE has been
set and is available here:

	http://www.freebsd.org/releases/8.3R/schedule.html

The summary of the target dates is:

Code Freeze:    Feb 15, 2012 
BETA1 builds:   Feb 17, 2012 
RC1 builds:     Mar  2, 2012 
RC2 builds:     Mar 16, 2012 
REL builds:     Mar 23, 2012 

The Security Officer has pushed back the estimated End of Life for
8.2-RELEASE to July 31, 2012.  That will give three months between the
release of 8.3-RELEASE and the EoL for 8.2-RELEASE.  It is expected that
8.3-RELEASE will be an Extended Support release.  See:

	http://www.freebsd.org/security/#sup

for the full details of the currently supported releases.

Thanks.

--

-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith <at> buffalo.edu
  there, funny things are everywhere.   |
                      - Theodor Geisel  |
(Continue reading)

Permalink | Reply | 2 comments |
headers
Patrick M. Hausen | 6 Feb 11:57
Picon
Favicon

Swap on zvol - recommendable?

Hi, all,

is it possible to make a definite statement about swap on zvols?

I found some older discussions about a resource starvation
scenario when ZFS arc would be the cause of the system
running out of memory, trying to swap, yet the ZFS would
not be accessible until some memory was freed - leading to
a deadlock.

Is this still the case with RELENG_8? The various Root on
ZFS guides mention both choices (decicated or gmirror
partition vs. zvol), yet don't say anything about the respective
merits or risks. I am aware of the fact that I cannot dump to
a raidz2 zvol ...

Thanks for any hints,
Patrick
--

-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info <at> punkt.de       http://www.punkt.de
Gf: Jürgen Egeling      AG Mannheim 108285

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dewayne | 5 Feb 10:09
Picon
Gravatar

9.0 Stable unable to buildworld, missing KERN_PROC_ENV in kvm_proc.c

Unfortunately 9.0 Stable fails to compile due to missing declaration of KERN_PROC_ENV in /usr/src/lib/libkvm/kvm_proc.c.
csup'ed from today. 

Please refer to the following changes on 30-Jan-2012: 
http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libkvm/kvm_proc.c.diff?r1=1.106.2.1;r2=1.106.2.2;f=h

Compile error reads:
cc -O2 -pipe -pipe -O2 -g0 -DSTRIP_FBSDID -UDEBUGGING -march=prescott -mtune=prescott  -DLIBC_SCCS -I/usr/src/lib/libkvm
-DNDEBUG -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /usr/src/lib/libkvm/kvm_proc.c
/usr/src/lib/libkvm/kvm_proc.c: In function 'kvm_argv':
/usr/src/lib/libkvm/kvm_proc.c:663: error: 'KERN_PROC_ENV' undeclared (first use in this function)
/usr/src/lib/libkvm/kvm_proc.c:663: error: (Each undeclared identifier is reported only once
/usr/src/lib/libkvm/kvm_proc.c:663: error: for each function it appears in.)

Am I the last person using i386 architecture?  ;) I'm half joking. The buildworld completes successfully
for architecture=amd64.

Regards, Dewayne

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |

Gmane