Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-21 Thread Doug Barton 
On 10/21/2011 22:42, Craig Rodrigues wrote:
> Hi,
> 
> I tried following:
> 
> (1)   Run svnversion in non-svn directory:
> 
>return status == 0

Return status isn't everything. :)

>prints out "exported"

In my case (1.7) it says "Unversioned directory"

But my point (which perhaps I should have made more explicit) is that
given the fact that svnversion handles non-svn directories gracefully
it's faster (simpler, etc.) to just run foo=`svnversion` and then make
sure that $foo is rational than it is to run 2 commands.

Doug

-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-21 Thread Craig Rodrigues 
Hi,

I tried following:

(1)   Run svnversion in non-svn directory:

   return status == 0
   prints out "exported"

time:
real0m0.043s
user0m0.000s
sys 0m0.045s

(2)  Run svnversion in svn directory:

   return status == 0
   prints out "223847M"

time:
real0m2.563s
user0m0.980s
sys 0m1.187s


(3)  Run "svn info --non-interactive  ." in non-svn directory:

   return status == 1
   prints out "svn: '.' is not a working copy"

time:

real0m0.056s
user0m0.007s
sys 0m0.046s


(4)   Run "svn info --non-interactive ." in svn directory:

return status == 0
prints out "a bunch of info about from svn"

time:

real0m0.023s
user0m0.000s
sys 0m0.024s



I thought that since svnversion seems to always have a return status of 0, and
is almost 2 seconds slower than "svn info" when run inside a svn directory,
that using "svn info" is a preferable way inside a script of determining
if a directory is part of a svn repo or not.

--
Craig Rodrigues
rodr...@crodrigues.org



On Fri, Oct 21, 2011 at 6:11 PM, Doug Barton  wrote:
> On 10/21/2011 17:51, Craig Rodrigues wrote:
>> Can you come up with a patch which invoke "svn info ." (if the svn
>> binary exists)?
>> This is slightly faster than svnversion.
>>
>> If "svn info ." doesn't error out, you can assume that the directory
>> is under SVN control.
>
> Doesn't svnversion error out pretty quickly in the same circumstance? My
> brief testing seems to indicate that it does.
>
>
> --
>
>        Nothin' ever doesn't change, but nothin' changes much.
>                        -- OK Go
>
>        Breadth of IT experience, and depth of knowledge in the DNS.
>        Yours for the right price.  :)  http://SupersetSolutions.com/
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>



-- 
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

[head tinderbox] failure on powerpc/powerpc

2011-10-21 Thread FreeBSD Tinderbox 
TB --- 2011-10-22 04:33:53 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2011-10-22 04:33:53 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2011-10-22 04:33:53 - cleaning the object tree
TB --- 2011-10-22 04:34:06 - cvsupping the source tree
TB --- 2011-10-22 04:34:06 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/powerpc/powerpc/supfile
TB --- 2011-10-22 04:34:18 - building world
TB --- 2011-10-22 04:34:18 - CROSS_BUILD_TESTING=YES
TB --- 2011-10-22 04:34:18 - MAKEOBJDIRPREFIX=/obj
TB --- 2011-10-22 04:34:18 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2011-10-22 04:34:18 - SRCCONF=/dev/null
TB --- 2011-10-22 04:34:18 - TARGET=powerpc
TB --- 2011-10-22 04:34:18 - TARGET_ARCH=powerpc
TB --- 2011-10-22 04:34:18 - TZ=UTC
TB --- 2011-10-22 04:34:18 - __MAKE_CONF=/dev/null
TB --- 2011-10-22 04:34:18 - cd /src
TB --- 2011-10-22 04:34:18 - /usr/bin/make -B buildworld
>>> World build started on Sat Oct 22 04:34:19 UTC 2011
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
[...]
ranlib libllvmbitreader.a
===> lib/clang/libllvmbitwriter (all)
c++ -O2 -pipe -I/src/lib/clang/libllvmbitwriter/../../../contrib/llvm/include 
-I/src/lib/clang/libllvmbitwriter/../../../contrib/llvm/tools/clang/include 
-I/src/lib/clang/libllvmbitwriter/../../../contrib/llvm/lib/Bitcode/Writer -I. 
-I/src/lib/clang/libllvmbitwriter/../../../contrib/llvm/../../lib/clang/include 
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS 
-O1 -DLLVM_HOSTTRIPLE=\"powerpc-unknown-freebsd10.0\" -fstack-protector 
-fno-exceptions -fno-rtti -c 
/src/lib/clang/libllvmbitwriter/../../../contrib/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
/src/lib/clang/libllvmbitwriter/../../../contrib/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp:
 In function 'void WriteConstants(unsigned int, unsigned int, const 
llvm::ValueEnumerator&, llvm::BitstreamWriter&, bool)':
/src/lib/clang/libllvmbitwriter/../../../contrib/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp:678:
 internal compiler error: Segmentation fault: 11
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
*** Error code 1

Stop in /src/lib/clang/libllvmbitwriter.
*** Error code 1

Stop in /src/lib/clang.
*** Error code 1

Stop in /src/lib.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2011-10-22 05:36:09 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2011-10-22 05:36:09 - ERROR: failed to build world
TB --- 2011-10-22 05:36:09 - 2968.79 user 516.89 system 3735.85 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: IPv6 accept_rtadv + bfe0

2011-10-21 Thread Doug Barton 
On 10/19/2011 00:29, Hiroki Sato wrote:
> Mattia Rossi  wrote
>   in <4e9dfe11.2070...@swin.edu.au>:
> 
> mr> So the _ipv6 bit doesn't take care of passing "inet6" to ifconfig
> mr> automatically?
> 
>  No.  You always need to add the inet6 keyword wherever needed.

That seems redundant, and contrary to how the IPv4 equivalents work. And
obviously it's confusing to users. From what I can see looking at some
7.x and 8.x systems it also seems to be a POLA violation.

Perhaps this is something that you should reconsider?


Doug

-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-21 Thread Doug Barton 
On 10/21/2011 17:51, Craig Rodrigues wrote:
> Can you come up with a patch which invoke "svn info ." (if the svn
> binary exists)?
> This is slightly faster than svnversion.
> 
> If "svn info ." doesn't error out, you can assume that the directory
> is under SVN control.

Doesn't svnversion error out pretty quickly in the same circumstance? My
brief testing seems to indicate that it does.


-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-21 Thread Craig Rodrigues 
Hi,

Can you come up with a patch which invoke "svn info ." (if the svn
binary exists)?
This is slightly faster than svnversion.

If "svn info ." doesn't error out, you can assume that the directory
is under SVN control.

--
Craig Rodrigues
rodr...@crodrigues.org

On Fri, Oct 21, 2011 at 2:12 PM, David Wolfskill  wrote:
> On Fri, Oct 21, 2011 at 04:36:05PM -0400, John Baldwin wrote:
>> 
>> I'm not sure what the best fix is.  One could possibly always run svnversion
>> if it exists?
>
> Sure -- and use the result as long as the exit status is 0.  (It's
> certainly possible that svnversion exists, but the sources in question
> aren't in a subversion working copy, after all.)
>
> I could cobble up a patch to do that, if y'all like
>
> Alternatively, see the more extended comments I made to Jilles' comments
> (to the PR) of a similar nature;
> .  Summary: I believe
> that newvers.sh ought to be intrinsically SCM-agnostic.
>
> Peace,
> david
> --
> David H. Wolfskill                              da...@catwhisker.org
> Depriving a girl or boy of an opportunity for education is evil.
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>



-- 
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Gunnar Schaefer 
On Oct 21, 2011, at 2:37 PM, Andriy Gapon wrote:

> on 22/10/2011 00:27 Andriy Gapon said the following:
>> on 21/10/2011 23:33 John Baldwin said the following:
>>> On Friday, October 21, 2011 4:58:51 am Dennis Koegel wrote:
 On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
> I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i 
>>> mirror)
> as test. [...]
> It was fresh install and I choose guided partitioning (GPT)
> But after reboot my server don't boot from hd.
 
 We have the same issue on a DL580 G7. Install runs fine, but when it's
 time for the first boot, the bootcode emits a single '-' (where usually
 it would be "spinning" for a moment while loading), hangs for about two
 seconds, and then reboots.
>>> 
>>> Working offline with Dennis, we found that changing the CFLAGS in 
>>> sys/boot/i386/gptboot/Makefile from "-O1" to "-Os -mrtd" (partially 
>>> reverting 
>>> an earlier commit) fixed gptboot.  The next test for someone to do would be 
>>> to 
>>> try just adding "-mrtd" and leaving "-O1" as-is to see if that fixes it.
>> 
>> Hmm, this is quite unexpected...  Do you have a hypothesis why not using 
>> -mrtd
>> could cause a problem (a miscompilation?) ?
> 
> I've just got one: maybe the trouble is caused by the sio_putc procedure in
> sys/boot/i386/btx/btx/btx.S.  It seems to be the only place in the boot code
> where 'ret ' instruction is explicitly used.
> 
> A litmus question: do those experiencing the trouble all have BTX_SERIAL 
> defined?

Not sure where BTX_SERIAL would be defined, but I'm seeing the problem with the 
generic kernel. Does that answer your question?

Also, how does this relate to my observation that my system boots in IDE mode, 
but hangs in AHCI mode?

> P.S. BTW, is BTX_SERIAL documented anywhere?
> 
> -- 
> Andriy Gapon
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Andriy Gapon 
on 22/10/2011 00:27 Andriy Gapon said the following:
> on 21/10/2011 23:33 John Baldwin said the following:
>> On Friday, October 21, 2011 4:58:51 am Dennis Koegel wrote:
>>> On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
 I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i 
>> mirror)
 as test. [...]
 It was fresh install and I choose guided partitioning (GPT)
 But after reboot my server don't boot from hd.
>>>
>>> We have the same issue on a DL580 G7. Install runs fine, but when it's
>>> time for the first boot, the bootcode emits a single '-' (where usually
>>> it would be "spinning" for a moment while loading), hangs for about two
>>> seconds, and then reboots.
>>
>> Working offline with Dennis, we found that changing the CFLAGS in 
>> sys/boot/i386/gptboot/Makefile from "-O1" to "-Os -mrtd" (partially 
>> reverting 
>> an earlier commit) fixed gptboot.  The next test for someone to do would be 
>> to 
>> try just adding "-mrtd" and leaving "-O1" as-is to see if that fixes it.
> 
> Hmm, this is quite unexpected...  Do you have a hypothesis why not using -mrtd
> could cause a problem (a miscompilation?) ?

I've just got one: maybe the trouble is caused by the sio_putc procedure in
sys/boot/i386/btx/btx/btx.S.  It seems to be the only place in the boot code
where 'ret ' instruction is explicitly used.

A litmus question: do those experiencing the trouble all have BTX_SERIAL 
defined?

P.S. BTW, is BTX_SERIAL documented anywhere?

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ipmi(4)/isa woes

2011-10-21 Thread Arnaud Lacombe 
Hi,

On Fri, Oct 21, 2011 at 4:19 PM, John Baldwin  wrote:
> On Tuesday, October 11, 2011 6:53:11 pm Arnaud Lacombe wrote:
>> Hi,
>>
>> On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe  wrote:
>> > Hi folks,
>> >
>> > I've got a machine where ipmi(4) seem to be unable to fully attach.
>> > 10-current kernel complains the following way:
>> >
>> > ipmi0:  at iomem 0-0x1 on isa0
>> > ipmi0: KCS mode found at mem 0x0 alignment 0x1 on isa
>> > ipmi0: couldn't configure I/O resource
>> > device_attach: ipmi0 attach returned 6
>
> Resource 0 is not right and will not work.  In this case your BIOS has a buggy
> SMBIOS / DMI table entry for IPMI.
>
>> Actually, I can bypass this issue by enabling acpi(4):
>>
>> ipmi0:  port 0xca2,0xca3 on acpi0
>> ipmi0: KCS mode found at io 0xca2 on acpi
>> ipmi1:  on isa0
>> device_attach: ipmi1 attach returned 16
>> pmtimer0 on isa0
>> ipmi1:  on isa0
>> device_attach: ipmi1 attach returned 16
>
> You can ignore the ipmi1 messages.
>
>> However, the driver fails right after with:
>>
>> ipmi0: Timed out waiting for GET_DEVICE_ID
>
> Are you sure you have working IPMI?  The timeouts and the busted DMI table
> is consistent with a machine where IPMI is available via an optional
> daughterboard, but the daughterboard isn't installed.
>
Well, I'm not sure exactly what's the hardware layout looks like[0],
but when ipmi0 is "attached" on isa0, I can access the IPMI
controller, get the various information, set/reset the watchdog.
ipmitool(1) works like a charm. However, at some point, the KCS is
unable to reach the IPMI controller. Typical error is:

ipmi0: KCS: Reply address mismatch
ipmi0: KCS error: 01
ipmi0: KCS: Reply address mismatch
ipmi0: KCS error: 01
ipmi0: Failed to set watchdog

over an undetermined period of time. Sometimes it stops before the
watchdog triggers, sometimes it [falsely] triggers the watchdog.

 - Arnaud

[0]: I'll have a look to the physical machine and let you know.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Andriy Gapon 
on 21/10/2011 23:33 John Baldwin said the following:
> On Friday, October 21, 2011 4:58:51 am Dennis Koegel wrote:
>> On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
>>> I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i 
> mirror)
>>> as test. [...]
>>> It was fresh install and I choose guided partitioning (GPT)
>>> But after reboot my server don't boot from hd.
>>
>> We have the same issue on a DL580 G7. Install runs fine, but when it's
>> time for the first boot, the bootcode emits a single '-' (where usually
>> it would be "spinning" for a moment while loading), hangs for about two
>> seconds, and then reboots.
> 
> Working offline with Dennis, we found that changing the CFLAGS in 
> sys/boot/i386/gptboot/Makefile from "-O1" to "-Os -mrtd" (partially reverting 
> an earlier commit) fixed gptboot.  The next test for someone to do would be 
> to 
> try just adding "-mrtd" and leaving "-O1" as-is to see if that fixes it.

Hmm, this is quite unexpected...  Do you have a hypothesis why not using -mrtd
could cause a problem (a miscompilation?) ?  I previously assumed that -O1 is
typically a quite safe optimization, not sure if it's even worth trying -O0 for
a test.

Or could this be about a size of gptboot blob?

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-21 Thread David Wolfskill 
On Fri, Oct 21, 2011 at 04:36:05PM -0400, John Baldwin wrote:
> 
> I'm not sure what the best fix is.  One could possibly always run svnversion 
> if it exists?

Sure -- and use the result as long as the exit status is 0.  (It's
certainly possible that svnversion exists, but the sources in question
aren't in a subversion working copy, after all.)

I could cobble up a patch to do that, if y'all like

Alternatively, see the more extended comments I made to Jilles' comments
(to the PR) of a similar nature;
.  Summary: I believe
that newvers.sh ought to be intrinsically SCM-agnostic.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpcxbHcJqUkS.pgp
Description: PGP signature

Re: orm0/ISA strangeness on HEAD preventing drivers from probe/attach?

2011-10-21 Thread John Baldwin 
On Thursday, October 20, 2011 7:01:42 pm Bjoern A. Zeeb wrote:
> Hi,
> 
> I am seeing some strangeness on booting a recent HEAD on an atom machine;  
the entire orm0 and related stuff looks wrong.  Also some things like a 
watchdog driver etc. no longer probe or attach it seems.  Anyone an idea?

The orm0 stuff is normal after some of the NEW_PCIB changes.  The first ting 
to try for the watchdog not working on an Intel system by failing to allocate 
its GCS registers is a known issue, but I don't have a workaround for that 
currently.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-21 Thread John Baldwin 
On Thursday, October 20, 2011 8:21:21 am David Wolfskill wrote:
> On Thu, Oct 20, 2011 at 04:48:44AM -0700, David Wolfskill wrote:
> > ...
> > Well, as of subversion-1.7, we don't have a ".svn" directory in
> > ${SYSDIR} any more -- it's only at the root of the working copy
> > (/usr/src, in this case).  So "svnversion" is never invoked.
> > 
> > So I've just hacked my copy to parallel the "git" stanza & look for
> > ${SYSDIR}/../.svn,  Not sure that's ideal, but there appears to be
> > precedent :-}
> > 
> > It might be handy to resolve this prior to 9.0-RELEASE, I think.
> > ...
> 
> Finished building head, and the change worked; here are uname strings
> from yesterday & today:
> 
> FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #625: Wed 
Oct 19 05:22:52 PDT 2011 
r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC  i386
> 
> FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #626 
r226563M: Thu Oct 20 05:04:03 PDT 2011 
r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC  i386
> 
> I've attached a copy of the patch, in case my description wasn't
> clear.  And I'll plan on filing a PR a bit later today.

Hmm, that won't always work, the problem is if someone just checks out a 
kernel tree then .svn will be in SYSDIR.  Alternatively, if you have a tree 
like mine which has work/freebsd/svn/ with various subdirs (head/, stable/ 
with subdirs for 7, 8, 9) but all rooted at the upperlevel, just looking two 
levels up won't work.

I'm not sure what the best fix is.  One could possibly always run svnversion 
if it exists?

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread John Baldwin 
On Friday, October 21, 2011 4:58:51 am Dennis Koegel wrote:
> On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
> > I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i 
mirror)
> > as test. [...]
> > It was fresh install and I choose guided partitioning (GPT)
> > But after reboot my server don't boot from hd.
> 
> We have the same issue on a DL580 G7. Install runs fine, but when it's
> time for the first boot, the bootcode emits a single '-' (where usually
> it would be "spinning" for a moment while loading), hangs for about two
> seconds, and then reboots.

Working offline with Dennis, we found that changing the CFLAGS in 
sys/boot/i386/gptboot/Makefile from "-O1" to "-Os -mrtd" (partially reverting 
an earlier commit) fixed gptboot.  The next test for someone to do would be to 
try just adding "-mrtd" and leaving "-O1" as-is to see if that fixes it.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ipmi(4)/isa woes

2011-10-21 Thread John Baldwin 
On Tuesday, October 11, 2011 6:53:11 pm Arnaud Lacombe wrote:
> Hi,
> 
> On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe  wrote:
> > Hi folks,
> >
> > I've got a machine where ipmi(4) seem to be unable to fully attach.
> > 10-current kernel complains the following way:
> >
> > ipmi0:  at iomem 0-0x1 on isa0
> > ipmi0: KCS mode found at mem 0x0 alignment 0x1 on isa
> > ipmi0: couldn't configure I/O resource
> > device_attach: ipmi0 attach returned 6

Resource 0 is not right and will not work.  In this case your BIOS has a buggy 
SMBIOS / DMI table entry for IPMI.

> Actually, I can bypass this issue by enabling acpi(4):
> 
> ipmi0:  port 0xca2,0xca3 on acpi0
> ipmi0: KCS mode found at io 0xca2 on acpi
> ipmi1:  on isa0
> device_attach: ipmi1 attach returned 16
> pmtimer0 on isa0
> ipmi1:  on isa0
> device_attach: ipmi1 attach returned 16

You can ignore the ipmi1 messages.

> However, the driver fails right after with:
> 
> ipmi0: Timed out waiting for GET_DEVICE_ID

Are you sure you have working IPMI?  The timeouts and the busted DMI table
is consistent with a machine where IPMI is available via an optional
daughterboard, but the daughterboard isn't installed.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 9.0 and cdparanoia

2011-10-21 Thread Christian Jachmann 
Fri, Oct 21, 2011 at 12:56:10PM -0600, Tim Nackos :
> My temporary solution was to use 'pkg_add -r cdparanoia' which worked. That's 
> not a fix for the build error however.
> 

So, I do have problems using the binary ...see:

# cdparanoia -vsQ
cdparanoia III release 9.8 (March 23, 2001)

Checking /dev/cd0 for cdrom...
Could not open SCSI device: cam_lookup_pass: CAMGETPASSTHRU 
ioctl failed
cam_lookup_pass: Inappropriate ioctl for device: Inappropriate ioctl for device
CDROM sensed: Generic cooked ioctl CDROM

Verifying drive can read CDDA...

Unable to read any data; drive probably not CDDA capable.
006: Could not read any data from drive

Cdparanoia could not find a way to read audio from this drive.
# 

I do have pass in my kernel ... doesn't seem to work in 9

$cdcontrol info  works just fine

Thanks 
Christian Jachmann
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: LLVM: llvm-as, llvm-ld and so on not contained in FreeBSD core contrib?

2011-10-21 Thread Hartmann, O. 
On 06/26/11 15:42, Dimitry Andric wrote:
> On 2011-06-25 17:53, Hartmann, O. wrote:
>> On 06/25/11 10:10, Roman Divacky wrote:
>>> On Sat, Jun 25, 2011 at 09:57:52AM +0200, Hartmann, O. wrote:
 Hello.
 Just for my couriosity: I'm missing llvm-as, llvm-ld and other
 binutils
 from LLVM and was wondering why they are contained in the port's llvm
 collection but not in FreeBSD's source contribution.
>>>
>>> There's no use for these utilities in FreeBSD base system.
>>>
 I build FreeBSD 9 with CLANG. But as a missing llvm-as and llvm-ld (or
 llvm-ar) would imply, the binaries are generated via binutils from
 theGNU suite, aren't they?
>>> llvm-{as,ld,ar} are not replacements for those from binutils. llvm-*
>>> work on the llvm bitcode only and are of no use for normal object
>>> files.
>>>
>>> dim@ made a patch that adds those utilities if you really need them
>>>
>>> http://lists.freebsd.org/pipermail/freebsd-toolchain/2011-June/000216.html
>>>
>>>
>>> By default when you compile things with clang it uses its own assembler
>>> (ie. it goes directly from C ->   .o) so typically only gnu ld is used
>>> in the compilation chain.
>>>
>>>
>>> roman
>> Thank you very much. Patched and works.
>
> What's the general opinion on applying this to -current?  Otherwise
> it'll be sitting in my private tree, possibly bit-rotting. :)  For
> people that are experimenting with llvm and/or clang, these additional
> tools might sometimes come in handy.
>
> For normal users, it won't have any impact, except for a few extra
> source files in the tree.  These tools will not be built by default.


Is there a chance to get the missing pieces of LLVM built by the above
mentioned method enabled in /etc/src.conf? As I can see,
even in FreeBSD 10.0-CURRENT the LLVM stuff didn't make it in. My built
is quite old, since I added the patch three months has been passed by ...

Regards,
Oliver
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 9.0 and cdparanoia

2011-10-21 Thread Kevin Oberman 
On Fri, Oct 21, 2011 at 11:56 AM, Tim Nackos  wrote:
> My temporary solution was to use 'pkg_add -r cdparanoia' which worked. That's 
> not a fix for the build error however.
>
>
>
> On Oct 21, 2011, at 11:52 AM, Christian Jachmann  wrote:
>
>> Hello my friends.
>>
>> Last two days I switched form 8 to 9
>>
>> following is bad:
>>
>> ===>  Building for cdparanoia-3.9.8_9
>> cd interface && gmake all
>> gmake[1]: Entering directory 
>> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
>> gmake libcdda_interface.a CFLAGS="-O -O2 -pipe -fno-strict-aliasing"
>> gmake[2]: Entering directory 
>> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
>> cc -O -O2 -pipe -fno-strict-aliasing -c scsi_interface.c
>> scsi_interface.c: In function 'handle_scsi_cmd':
>> scsi_interface.c:370: error: 'struct scsi_sense_data' has no member named 
>> 'flags'
>> scsi_interface.c:381: error: 'struct scsi_sense_data' has no member named 
>> 'add_sense_code'
>> scsi_interface.c:382: error: 'struct scsi_sense_data' has no member named 
>> 'add_sense_code_qual'
>> scsi_interface.c: In function 'scsi_read_map':
>> scsi_interface.c:967: error: 'struct scsi_sense_data' has no member named 
>> 'flags'
>> scsi_interface.c:968: error: 'struct scsi_sense_data' has no member named 
>> 'add_sense_code'
>> scsi_interface.c:969: error: 'struct scsi_sense_data' has no member named 
>> 'add_sense_code_qual'
>> gmake[2]: *** [scsi_interface.o] Error 1
>> gmake[2]: Leaving directory 
>> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
>> gmake[1]: *** [all] Error 2
>> gmake[1]: Leaving directory 
>> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
>> gmake: *** [all] Error 2
>> *** Error code 1
>>
>> Stop in /usr/ports/audio/cdparanoia.
>>
>>
>>
>> So you got any idea what to do ?
>> How to access CDDA ?
>>
>>

danfe is hoping to commit the current version of cdparanoia to ports
before the 9.0 freeze, but until then you can build it with the patch
in ports/161760. (Thanks to Ken Merry). It basically replaces the
scsi_interface.c with the current version.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Gunnar Schaefer 
On Oct 21, 2011, at 1:58 AM, Dennis Koegel wrote:

> On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
>> I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i mirror)
>> as test. [...]
>> It was fresh install and I choose guided partitioning (GPT)
>> But after reboot my server don't boot from hd.
> 
> We have the same issue on a DL580 G7. Install runs fine, but when it's
> time for the first boot, the bootcode emits a single '-' (where usually
> it would be "spinning" for a moment while loading), hangs for about two
> seconds, and then reboots.

I'm seeing the same behavior on a Supermicro X8DT3 BIOS. The latest BIOS update 
changed the behavior from hanging forever to hanging for 2 seconds before 
rebooting.

The problem occurs with BETA3 and RC1, but not with BETA2.

Changing SATA mode from AHCI to IDE in the BIOS gets the OS to boot just fine.

Cheers,

  Gunnar


> I've used the BETA3 bsdinstall on other (amd64) hardware with GPT and it
> worked fine. Also, manually adding the GPT label, partitions and
> bootcode using gpart, then rebooting, shows the exact same behaviour
> (this was done using the BETA3 "Live CD").
> 
> I suspect it's something in the vicinity of "pmbr bootcode vs.  newer
> HP BIOS".
> 
> (BTW, not related to this issue: hw.memtest.tests=0 should be default.
> The kernel on a system with 128 GB of RAM needs about two minutes (!)
> before emitting a single line of output. At first we didn't know about
> this test and thought there was a serious problem.)
> 
> - D.
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 9.0 and cdparanoia

2011-10-21 Thread Tim Nackos 
My temporary solution was to use 'pkg_add -r cdparanoia' which worked. That's 
not a fix for the build error however.



On Oct 21, 2011, at 11:52 AM, Christian Jachmann  wrote:

> Hello my friends.
> 
> Last two days I switched form 8 to 9 
> 
> following is bad:
> 
> ===>  Building for cdparanoia-3.9.8_9
> cd interface && gmake all
> gmake[1]: Entering directory 
> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
> gmake libcdda_interface.a CFLAGS="-O -O2 -pipe -fno-strict-aliasing" 
> gmake[2]: Entering directory 
> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
> cc -O -O2 -pipe -fno-strict-aliasing -c scsi_interface.c
> scsi_interface.c: In function 'handle_scsi_cmd':
> scsi_interface.c:370: error: 'struct scsi_sense_data' has no member named 
> 'flags'
> scsi_interface.c:381: error: 'struct scsi_sense_data' has no member named 
> 'add_sense_code'
> scsi_interface.c:382: error: 'struct scsi_sense_data' has no member named 
> 'add_sense_code_qual'
> scsi_interface.c: In function 'scsi_read_map':
> scsi_interface.c:967: error: 'struct scsi_sense_data' has no member named 
> 'flags'
> scsi_interface.c:968: error: 'struct scsi_sense_data' has no member named 
> 'add_sense_code'
> scsi_interface.c:969: error: 'struct scsi_sense_data' has no member named 
> 'add_sense_code_qual'
> gmake[2]: *** [scsi_interface.o] Error 1
> gmake[2]: Leaving directory 
> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
> gmake[1]: *** [all] Error 2
> gmake[1]: Leaving directory 
> `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
> gmake: *** [all] Error 2
> *** Error code 1
> 
> Stop in /usr/ports/audio/cdparanoia.
> 
> 
> 
> So you got any idea what to do ?
> How to access CDDA ?
> 
> 
> Thanks and best regards
> Christian Jachmann
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

9.0 and cdparanoia

2011-10-21 Thread Christian Jachmann 
Hello my friends.

Last two days I switched form 8 to 9 

following is bad:

===>  Building for cdparanoia-3.9.8_9
cd interface && gmake all
gmake[1]: Entering directory 
`/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
gmake libcdda_interface.a CFLAGS="-O -O2 -pipe -fno-strict-aliasing" 
gmake[2]: Entering directory 
`/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
cc -O -O2 -pipe -fno-strict-aliasing -c scsi_interface.c
scsi_interface.c: In function 'handle_scsi_cmd':
scsi_interface.c:370: error: 'struct scsi_sense_data' has no member named 
'flags'
scsi_interface.c:381: error: 'struct scsi_sense_data' has no member named 
'add_sense_code'
scsi_interface.c:382: error: 'struct scsi_sense_data' has no member named 
'add_sense_code_qual'
scsi_interface.c: In function 'scsi_read_map':
scsi_interface.c:967: error: 'struct scsi_sense_data' has no member named 
'flags'
scsi_interface.c:968: error: 'struct scsi_sense_data' has no member named 
'add_sense_code'
scsi_interface.c:969: error: 'struct scsi_sense_data' has no member named 
'add_sense_code_qual'
gmake[2]: *** [scsi_interface.o] Error 1
gmake[2]: Leaving directory 
`/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory 
`/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
gmake: *** [all] Error 2
*** Error code 1

Stop in /usr/ports/audio/cdparanoia.



So you got any idea what to do ?
How to access CDDA ?


Thanks and best regards
Christian Jachmann
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: '/bin/ls' broken by SVN r226509

2011-10-21 Thread Kevin Oberman 
On Thu, Oct 20, 2011 at 10:52 PM, Lars Engels  wrote:
> On Fri, Oct 21, 2011 at 09:00:47AM +1030, Daniel O'Connor wrote:
>>
>> On 20/10/2011, at 22:21, Anton Shterenlikht wrote:
>> > On Thu, Oct 20, 2011 at 11:58:41AM +0100, Tom Evans wrote:
>> >> On Wed, Oct 19, 2011 at 7:47 PM, Anton Shterenlikht  
>> >> wrote:
>> >>>
>> >>> Thanks. Can you also please remind
>> >>> how to reinstall just /bin/ls,
>> >>> without the "make buildworld"?
>> >>>
>> >>
>> >> cp /rescue/ls /bin/ls
>> >
>> > oh.. of course. I've forgotten about /rescue.
>> > In fact, I only had to use it once before.
>>
>>
>> This is the crunched binary and is pretty big (unlikely to be an issue on a 
>> modern system though).
>>
>> You can do..
>> cd /usr/src/bin/ls
>> make all install
>
> And as a workaround: "echo *" :)

At work one of our standard questions for candidates for Unix admin
postings was how you can get a listing of the files in a directory if
ls(1) won't run. echo(1) was the official answer, but we got quite a
number of other, perfectly valid ones, some quite inventive and some,
like using awk and sed to format the directory file, were kind of
awkward, but they all work. Since the interviewees were often not
FreeBSD people, use of rescue was never suggested, although it's
probably the easiest on a FreeBSD system.

ls(1) with no options is such a basic operation that there are
probably dozens of ways to do the job in shell, Perl, or Python.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

panic at vm_page_wire with FreeBSD 9.0 Beta 3

2011-10-21 Thread Penta Upa 
Hi,

I'm facing a kernel panic at vm_page_wire(). Page is locked with
vm_page_lock() yet i get the following panic
panic: mutex page lock not owned at /usr/src/sys/vm/vm_page:1845

Code sequence is as below
vm_page_lock(pp);
vm_page_lock_assert(pp, MA_OWNED); /* No panic here */
vm_page_wire(pp); /* Panic here for the same assertion as above, strange */
vm_page_unlock(pp);

Kernel on the system is unchanged after install. The only thing which
occurred out the way was that the first time install failed for checksum
mismatch for src.txz. Also there were some SCSI errors/warnings with the CD
drive during install. So the next time, i only installed the base and
kernel and later unpacked src.txz under /usr/src . Could this lead to any
issues ?

Attached is a test module (vmtest) and the makefile used. Uname output from
the system is

FreeBSD scache 9.0-BETA3 FreeBSD 9.0-BETA3 #0: Sat Sep 24 21:31:28 UTC
2011
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

Is there anything i'm doing wrong here ? Kindly help.

Regards,
Penta


Makefile
Description: Binary data
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?

2011-10-21 Thread Martin Sugioarto 
Am Thu, 20 Oct 2011 23:40:05 -0700
schrieb Garrett Cooper :

> If I fire up an xterm without setting TERM={ansi,vt100,xterm},
> etc, xterm wraps my command output to 80 columns, even if I resize the
> window to something larger, issue reset (which I thought was supposed
> to fix the console settings by rescanning the window size, etc). I
> thought that SIGWINCH was also supposed to force a proper rescan if
> the terminal application had a handler installed. This isn't new (I've
> been seeing it since 8.x or 9.x, but it's just gotten to the point
> where it irritates me enough that I thought I should check around
> first).

Hi!

Is this related to the problem, that if you reconnect to sysutils/screen
(screen -r) while a port is in the "make config" phase e.g., you see
garbled output on wide monitors?

--
Martin


signature.asc
Description: PGP signature

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Lars Engels 
On Fri, Oct 21, 2011 at 10:58:51AM +0200, Dennis Koegel wrote:
> On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
> > I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i mirror)
> > as test. [...]
> > It was fresh install and I choose guided partitioning (GPT)
> > But after reboot my server don't boot from hd.
> 
> We have the same issue on a DL580 G7. Install runs fine, but when it's
> time for the first boot, the bootcode emits a single '-' (where usually
> it would be "spinning" for a moment while loading), hangs for about two
> seconds, and then reboots.
> 
> I've used the BETA3 bsdinstall on other (amd64) hardware with GPT and it
> worked fine. Also, manually adding the GPT label, partitions and
> bootcode using gpart, then rebooting, shows the exact same behaviour
> (this was done using the BETA3 "Live CD").
> 
> I suspect it's something in the vicinity of "pmbr bootcode vs.  newer
> HP BIOS".
> 
> (BTW, not related to this issue: hw.memtest.tests=0 should be default.
> The kernel on a system with 128 GB of RAM needs about two minutes (!)
> before emitting a single line of output. At first we didn't know about
> this test and thought there was a serious problem.)

Or at least there should be a message that the memtest is running...


pgpY4GqxDI5oP.pgp
Description: PGP signature

Re: '/bin/ls' broken by SVN r226509

2011-10-21 Thread Lars Engels 
On Fri, Oct 21, 2011 at 09:00:47AM +1030, Daniel O'Connor wrote:
> 
> On 20/10/2011, at 22:21, Anton Shterenlikht wrote:
> > On Thu, Oct 20, 2011 at 11:58:41AM +0100, Tom Evans wrote:
> >> On Wed, Oct 19, 2011 at 7:47 PM, Anton Shterenlikht  
> >> wrote:
> >>> 
> >>> Thanks. Can you also please remind
> >>> how to reinstall just /bin/ls,
> >>> without the "make buildworld"?
> >>> 
> >> 
> >> cp /rescue/ls /bin/ls
> > 
> > oh.. of course. I've forgotten about /rescue.
> > In fact, I only had to use it once before.
> 
> 
> This is the crunched binary and is pretty big (unlikely to be an issue on a 
> modern system though).
> 
> You can do..
> cd /usr/src/bin/ls
> make all install

And as a workaround: "echo *" :)


pgpmr63HEF3vI.pgp
Description: PGP signature

Re: config(8) does not add post-processing for source file with compile-with command in sys/conf/files

2011-10-21 Thread Paul Ambrose 
There are many other compile-with  not started with ${NORMAL_C}, your
patch adds
${NORMAL_CTFCONVERT}  to them too, which could not be suitable for this.

2011/10/19 Ryan Stone :
> I have run into the same issue recently.  I have been testing the
> following patch(on 8.2-RELEASE) and it seems to have worked for me:
>
> --- mkmakefile.c 11:09:30.0 -0400
> +++ mkmakefile.c        2011-10-06 11:13:31.0 -0400
> @@ -742,15 +742,16 @@
>                                break;
>                        }
>                        snprintf(cmd, sizeof(cmd),
> -                           "${%s_%c%s}\n.if defined(NORMAL_CTFCONVERT) && "
> -                           "!empty(NORMAL_CTFCONVERT)\n"
> -                           "\t${NORMAL_CTFCONVERT}\n.endif", ftype,
> +                           "${%s_%c%s}\n", ftype,
>                            toupper(och),
>                            ftp->f_flags & NOWERROR ? "_NOWERROR" : "");
>                        compilewith = cmd;
>                }
>                *cp = och;
> -               fprintf(f, "\t%s\n\n", compilewith);
> +               fprintf(f, "\t%s\n", compilewith);
> +               fprintf(f, ".if defined(NORMAL_CTFCONVERT) && "
> +                            "!empty(NORMAL_CTFCONVERT)\n"
> +                            "\t${NORMAL_CTFCONVERT}\n.endif\n\n");
>        }
>  }
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?

2011-10-21 Thread Jilles Tjoelker 
On Fri, Oct 21, 2011 at 12:52:17AM -0700, Garrett Cooper wrote:
> # Increased the window size here.
> [gcooper@fallout ~]$ uname -a
> FreeBSD fallout.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r226332M:
> Wed Oct 12 22:48:55 PDT 2011
> root@fallout.local:/usr/obj/usr/src/sys/FALLOUT  amd64
> [gcooper@fallout ~]$ stty size
> 60 156
> [gcooper@fallout ~]$ exit
> Connection to fallout.local closed.
> [gcooper@bayonetta ~]$ uname -a
> FreeBSD bayonetta.local 9.0-BETA2 FreeBSD 9.0-BETA2 #0 r225653M: Tue
> Sep 20 08:36:49 PDT 2011
> gcooper@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA  amd64
> [gcooper@bayonetta ~]$ stty size
> 60 156
> # Line was wrapping in above uname -a.

> [gcooper@bayonetta ~]$ ssh starr-wireless
> # Increased the window size here from the default.
> starr:~ gcooper$ uname -a
> Darwin starr.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7
> 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386
> starr:~ gcooper$ echo $TERM
> xterm
> starr:~ gcooper$ logout
> Connection to starr-wireless.local closed.
> [gcooper@bayonetta ~]$ uname -a
> FreeBSD bayonetta.local 9.0-BETA2 FreeBSD 9.0-BETA2 #0 r225653M: Tue
> Sep 20 08:36:49 PDT 2011
> gcooper@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA  amd64

> ssh'ing in to a remote terminal and resizing it is an example I
> could think of that's semi-deterministic. It seems like it's an
> application bug or OS caveat; I'm not sure if anything can really be
> done about it because the signal might be masked in ssh when it
> connects to the other side -- would have to check to be sure.

By default, bash only updates its internal idea of the window size (and
the LINES and COLUMNS environment variables) when it receives SIGWINCH,
so only if bash is in the foreground when the change happens. You can do
  shopt -s checkwinsize
to make it check more often.

libedit (as used in sh) is different; it appears to check the size
before reading each line.

-- 
Jilles Tjoelker
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Pavel Timofeev 
2011/10/21 Dennis Koegel 

> On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
> > I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i
> mirror)
> > as test. [...]
> > It was fresh install and I choose guided partitioning (GPT)
> > But after reboot my server don't boot from hd.
>
> We have the same issue on a DL580 G7. Install runs fine, but when it's
> time for the first boot, the bootcode emits a single '-' (where usually
> it would be "spinning" for a moment while loading), hangs for about two
> seconds, and then reboots.
>
> I've used the BETA3 bsdinstall on other (amd64) hardware with GPT and it
> worked fine. Also, manually adding the GPT label, partitions and
> bootcode using gpart, then rebooting, shows the exact same behaviour
> (this was done using the BETA3 "Live CD").
>
> I suspect it's something in the vicinity of "pmbr bootcode vs.  newer
> HP BIOS".
>
> (BTW, not related to this issue: hw.memtest.tests=0 should be default.
> The kernel on a system with 128 GB of RAM needs about two minutes (!)
> before emitting a single line of output. At first we didn't know about
> this test and thought there was a serious problem.)
>
My proliant have 1Gb RAM =)


>
> - D.
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Pavel Timofeev 
2011/10/21 Dennis Koegel 

> On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
> > I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i
> mirror)
> > as test. [...]
> > It was fresh install and I choose guided partitioning (GPT)
> > But after reboot my server don't boot from hd.
>
> We have the same issue on a DL580 G7. Install runs fine, but when it's
> time for the first boot, the bootcode emits a single '-' (where usually
> it would be "spinning" for a moment while loading), hangs for about two
> seconds, and then reboots.
>
> I've used the BETA3 bsdinstall on other (amd64) hardware with GPT and it
> worked fine. Also, manually adding the GPT label, partitions and
> bootcode using gpart, then rebooting, shows the exact same behaviour
> (this was done using the BETA3 "Live CD").
>
> I suspect it's something in the vicinity of "pmbr bootcode vs.  newer
> HP BIOS".
>
I don't know, but earlier snapshots, for example,
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/FreeBSD-9.0-CURRENT-201105-amd64-dvd1.iso
doesn't have such problems.
Does anybody have BETA-2 iso?


> (BTW, not related to this issue: hw.memtest.tests=0 should be default.
> The kernel on a system with 128 GB of RAM needs about two minutes (!)
> before emitting a single line of output. At first we didn't know about
> this test and thought there was a serious problem.)
>
> - D.
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: '/bin/ls' broken by SVN r226509

2011-10-21 Thread Dag-Erling Smørgrav 
"Daniel O'Connor"  writes:
> This is the crunched binary and is pretty big (unlikely to be an issue
> on a modern system though).
>
> You can do..
> cd /usr/src/bin/ls
> make all install

I think you missed the point.  Reinstalling ls from broken sources
wasn't going to help.  He needed subversion to update his tree so he
could build a working ls, but he needed a working ls to build
subversion.  The simplest solution would have been either

# export PATH=/rescue:$PATH

or

# ln -f /rescue/ls /bin/ls

which would have allowed him to build subversion.

DES
-- 
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fresh installed Freebsd 9 don't boot from hd

2011-10-21 Thread Dennis Koegel 
On Thu, Oct 20, 2011 at 11:28:08AM +0400, Pavel Timofeev wrote:
> I used FreeBSD 9 amd64 on my HP Proliant DL360 G5 (smart array p400i mirror)
> as test. [...]
> It was fresh install and I choose guided partitioning (GPT)
> But after reboot my server don't boot from hd.

We have the same issue on a DL580 G7. Install runs fine, but when it's
time for the first boot, the bootcode emits a single '-' (where usually
it would be "spinning" for a moment while loading), hangs for about two
seconds, and then reboots.

I've used the BETA3 bsdinstall on other (amd64) hardware with GPT and it
worked fine. Also, manually adding the GPT label, partitions and
bootcode using gpart, then rebooting, shows the exact same behaviour
(this was done using the BETA3 "Live CD").

I suspect it's something in the vicinity of "pmbr bootcode vs.  newer
HP BIOS".

(BTW, not related to this issue: hw.memtest.tests=0 should be default.
The kernel on a system with 128 GB of RAM needs about two minutes (!)
before emitting a single line of output. At first we didn't know about
this test and thought there was a serious problem.)

- D.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?

2011-10-21 Thread Garrett Cooper 
On Fri, Oct 21, 2011 at 12:15 AM, Garrett Cooper  wrote:
> On Fri, Oct 21, 2011 at 12:08 AM, Ed Schouten  wrote:
>> * Garrett Cooper , 20111021 09:00:
>>> On Thu, Oct 20, 2011 at 11:59 PM, Ed Schouten  wrote:
>>> > Hi Garrett,
>>> >
>>> > * Garrett Cooper , 20111021 08:40:
>>> >>     If I fire up an xterm without setting TERM={ansi,vt100,xterm},
>>> >> [...]
>>> >
>>> > So what's the idea behind this? Why not just set TERM properly?
>>>
>>> It is set properly though -- that's the confusing part:
>>>
>>> $ echo $TERM
>>> xterm
>>
>> Oh, okay. So you mean "If I fire up an xterm without changing the
>> default TERM, [...]", right?
>>
>> Can you check whether `stty size' does return the correct numbers? That
>> way we can determine if it's a problem in xterm, your shell (or maybe
>> the kernel). Thanks!
>
> I'll run that in the next window I find that's acting funky.
> Unfortunately my system is behaving properly right now.
> Thanks for the tip :)!

Here's an example:


# Increased the window size here.
[gcooper@fallout ~]$ uname -a
FreeBSD fallout.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r226332M:
Wed Oct 12 22:48:55 PDT 2011
root@fallout.local:/usr/obj/usr/src/sys/FALLOUT  amd64
[gcooper@fallout ~]$ stty size
60 156
[gcooper@fallout ~]$ exit
Connection to fallout.local closed.
[gcooper@bayonetta ~]$ uname -a
FreeBSD bayonetta.local 9.0-BETA2 FreeBSD 9.0-BETA2 #0 r225653M: Tue
Sep 20 08:36:49 PDT 2011
gcooper@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA  amd64
[gcooper@bayonetta ~]$ stty size
60 156
# Line was wrapping in above uname -a.

[gcooper@bayonetta ~]$ ssh starr-wireless
# Increased the window size here from the default.
starr:~ gcooper$ uname -a
Darwin starr.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7
16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386
starr:~ gcooper$ echo $TERM
xterm
starr:~ gcooper$ logout
Connection to starr-wireless.local closed.
[gcooper@bayonetta ~]$ uname -a
FreeBSD bayonetta.local 9.0-BETA2 FreeBSD 9.0-BETA2 #0 r225653M: Tue
Sep 20 08:36:49 PDT 2011
gcooper@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA  amd64

ssh'ing in to a remote terminal and resizing it is an example I
could think of that's semi-deterministic. It seems like it's an
application bug or OS caveat; I'm not sure if anything can really be
done about it because the signal might be masked in ssh when it
connects to the other side -- would have to check to be sure.
Thanks,
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?

2011-10-21 Thread Garrett Cooper 
On Fri, Oct 21, 2011 at 12:08 AM, Ed Schouten  wrote:
> * Garrett Cooper , 20111021 09:00:
>> On Thu, Oct 20, 2011 at 11:59 PM, Ed Schouten  wrote:
>> > Hi Garrett,
>> >
>> > * Garrett Cooper , 20111021 08:40:
>> >>     If I fire up an xterm without setting TERM={ansi,vt100,xterm},
>> >> [...]
>> >
>> > So what's the idea behind this? Why not just set TERM properly?
>>
>> It is set properly though -- that's the confusing part:
>>
>> $ echo $TERM
>> xterm
>
> Oh, okay. So you mean "If I fire up an xterm without changing the
> default TERM, [...]", right?
>
> Can you check whether `stty size' does return the correct numbers? That
> way we can determine if it's a problem in xterm, your shell (or maybe
> the kernel). Thanks!

I'll run that in the next window I find that's acting funky.
Unfortunately my system is behaving properly right now.
Thanks for the tip :)!
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?

2011-10-21 Thread Ed Schouten 
* Garrett Cooper , 20111021 09:00:
> On Thu, Oct 20, 2011 at 11:59 PM, Ed Schouten  wrote:
> > Hi Garrett,
> >
> > * Garrett Cooper , 20111021 08:40:
> >>     If I fire up an xterm without setting TERM={ansi,vt100,xterm},
> >> [...]
> >
> > So what's the idea behind this? Why not just set TERM properly?
> 
> It is set properly though -- that's the confusing part:
> 
> $ echo $TERM
> xterm

Oh, okay. So you mean "If I fire up an xterm without changing the
default TERM, [...]", right?

Can you check whether `stty size' does return the correct numbers? That
way we can determine if it's a problem in xterm, your shell (or maybe
the kernel). Thanks!

-- 
 Ed Schouten 
 WWW: http://80386.nl/


pgpjm8lpdY66F.pgp
Description: PGP signature

Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?

2011-10-21 Thread Garrett Cooper 
On Thu, Oct 20, 2011 at 11:59 PM, Ed Schouten  wrote:
> Hi Garrett,
>
> * Garrett Cooper , 20111021 08:40:
>>     If I fire up an xterm without setting TERM={ansi,vt100,xterm},
>> [...]
>
> So what's the idea behind this? Why not just set TERM properly?

It is set properly though -- that's the confusing part:

$ echo $TERM
xterm

Thanks,
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?

2011-10-21 Thread Ed Schouten 
Hi Garrett,

* Garrett Cooper , 20111021 08:40:
> If I fire up an xterm without setting TERM={ansi,vt100,xterm},
> [...]

So what's the idea behind this? Why not just set TERM properly?

-- 
 Ed Schouten 
 WWW: http://80386.nl/


pgphKqlDvo4XU.pgp
Description: PGP signature