Re: 11.0 and tw_cli fail

[Larry Rosenman]

On Tue, May 30, 2017 at 11:40:48PM +0100, Gary Palmer wrote:
> 
> % file tw_cli
> tw_cli: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically 
> linked, for FreeBSD 5.4, stripped
> 
> Try COMPAT_FREEBSD5
> 
> Regards,
> 
> Gary
> 

Out of curiousity, how much code (binary) do the COMPAT_FREEBSD* bits add to 
the kernel/modules?


-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 and tw_cli fail

[Gary Palmer]

% file tw_cli
tw_cli: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically 
linked, for FreeBSD 5.4, stripped

Try COMPAT_FREEBSD5

Regards,

Gary

On Tue, May 30, 2017 at 03:55:03PM -0600, CBL wrote:
> Yeah, I have a custom kernel with COMPAT_FREEBSD10 already in it and no
> joy. However, I checked GENERIC and it works. Then I tried COMPAT_FREEBSD9
> too and no go.. guess I'll keep playing.
> 
> On Tue, May 30, 2017 at 3:33 PM, Alan Somers  wrote:
> 
> > Was the tw_cli utility built for FreeBSD 10?  If so, you need to
> > either rebuilt it, or build your kernel with COMPAT_FREEBSD10 in the
> > config file.  It's in the GENERIC config file, so you'll have it if
> > you don't use a custom kernel.
> > -Alan
> >
> > On Tue, May 30, 2017 at 3:19 PM, CBL  wrote:
> > > Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
> > > Now the tw_cli utility is now throwing "Bad system call (core dumped).
> > >
> > > Anybody have any suggestions?  Was working fine on 10.3.
> > >
> > > Thanks
> > > ___
> > > freebsd-stable@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org
> > "
> >
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 and tw_cli fail

[Martin MATO]

 

From my experience;

 

I posess one 9650se card 12 ports with a computer build with freeBSD 

with a custom kernel build.

i haved this particular error one day (it uses old mmap calls, which have 
removed  some time ago)

 

you can see why it fails by invoking the tw_cli after the truss(1) command

 

# truss tw_cli
readlink("/etc/malloc.conf",0x7fffea50,63)   ERR#2 'No such file or 
directory'
issetugid()  = 0 (0x0)
compat6.mmap(0x0,0x1000,0x3,0x1002,0x,0x0,0x0) = 34366898176 
(0x8006d4000)
break(0x78f000)  = 0 (0x0)
break(0x79)  = 0 (0x0)
break(0x791000)  = 0 (0x0)
sysarch(AMD64_SET_FSBASE,0x7fffeb10) = 0 (0x0)
snip

 

the tw_cli utility worked again  with COMPAT_FREEBSD6 compiled in the kernel

and the compat libraries from the same version also installed...

 

this two things solved this very particular problem; for me at least.

 

hope  it helps you.

 

Regards.

 

> Message du 30/05/17 23:34
> De : "Alan Somers" 
> A : "CBL" 
> Copie à : "FreeBSD" 
> Objet : Re: 11.0 and tw_cli fail
> 
> Was the tw_cli utility built for FreeBSD 10? If so, you need to
> either rebuilt it, or build your kernel with COMPAT_FREEBSD10 in the
> config file. It's in the GENERIC config file, so you'll have it if
> you don't use a custom kernel.
> -Alan
> 
> On Tue, May 30, 2017 at 3:19 PM, CBL  wrote:
> > Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
> > Now the tw_cli utility is now throwing "Bad system call (core dumped).
> >
> > Anybody have any suggestions? Was working fine on 10.3.
> >
> > Thanks
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 and tw_cli fail

[Michael Sinatra]

I am pretty sure you're going to need to go all the way back to 
COMPAT_FREEBSD5 for that.  Or just do what GENERIC does and go all the 
way back to COMPAT_FREEBSD32 (and everything in between).


michael

On 5/30/17 2:55 PM, CBL wrote:

Yeah, I have a custom kernel with COMPAT_FREEBSD10 already in it and no
joy. However, I checked GENERIC and it works. Then I tried COMPAT_FREEBSD9
too and no go.. guess I'll keep playing.

On Tue, May 30, 2017 at 3:33 PM, Alan Somers  wrote:


Was the tw_cli utility built for FreeBSD 10?  If so, you need to
either rebuilt it, or build your kernel with COMPAT_FREEBSD10 in the
config file.  It's in the GENERIC config file, so you'll have it if
you don't use a custom kernel.
-Alan

On Tue, May 30, 2017 at 3:19 PM, CBL  wrote:

Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
Now the tw_cli utility is now throwing "Bad system call (core dumped).

Anybody have any suggestions?  Was working fine on 10.3.

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

"


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



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

Re: 11.0 and tw_cli fail

[CBL]

For those curious, COMPAT_FREEBSD6 and COMPAT_FREEBSD7 were the ticket to
get tw_cli working on FreeBSD 11.0. Wish Broadcom would roll a new binary.

On Tue, May 30, 2017 at 3:55 PM, CBL  wrote:

> Yeah, I have a custom kernel with COMPAT_FREEBSD10 already in it and no
> joy. However, I checked GENERIC and it works. Then I tried COMPAT_FREEBSD9
> too and no go.. guess I'll keep playing.
>
> On Tue, May 30, 2017 at 3:33 PM, Alan Somers  wrote:
>
>> Was the tw_cli utility built for FreeBSD 10?  If so, you need to
>> either rebuilt it, or build your kernel with COMPAT_FREEBSD10 in the
>> config file.  It's in the GENERIC config file, so you'll have it if
>> you don't use a custom kernel.
>> -Alan
>>
>> On Tue, May 30, 2017 at 3:19 PM, CBL  wrote:
>> > Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
>> > Now the tw_cli utility is now throwing "Bad system call (core dumped).
>> >
>> > Anybody have any suggestions?  Was working fine on 10.3.
>> >
>> > Thanks
>> > ___
>> > freebsd-stable@freebsd.org mailing list
>> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@fr
>> eebsd.org"
>>
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 and tw_cli fail

[CBL]

Yeah, I have a custom kernel with COMPAT_FREEBSD10 already in it and no
joy. However, I checked GENERIC and it works. Then I tried COMPAT_FREEBSD9
too and no go.. guess I'll keep playing.

On Tue, May 30, 2017 at 3:33 PM, Alan Somers  wrote:

> Was the tw_cli utility built for FreeBSD 10?  If so, you need to
> either rebuilt it, or build your kernel with COMPAT_FREEBSD10 in the
> config file.  It's in the GENERIC config file, so you'll have it if
> you don't use a custom kernel.
> -Alan
>
> On Tue, May 30, 2017 at 3:19 PM, CBL  wrote:
> > Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
> > Now the tw_cli utility is now throwing "Bad system call (core dumped).
> >
> > Anybody have any suggestions?  Was working fine on 10.3.
> >
> > Thanks
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org
> "
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 and tw_cli fail

[Alan Somers]

Was the tw_cli utility built for FreeBSD 10?  If so, you need to
either rebuilt it, or build your kernel with COMPAT_FREEBSD10 in the
config file.  It's in the GENERIC config file, so you'll have it if
you don't use a custom kernel.
-Alan

On Tue, May 30, 2017 at 3:19 PM, CBL  wrote:
> Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
> Now the tw_cli utility is now throwing "Bad system call (core dumped).
>
> Anybody have any suggestions?  Was working fine on 10.3.
>
> Thanks
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.0 and tw_cli fail

[CBL]

Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
Now the tw_cli utility is now throwing "Bad system call (core dumped).

Anybody have any suggestions?  Was working fine on 10.3.

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

Re: 11.1-PRERELEASE, waagent crashes attaching reosurce disc in Azure

[Pete French]

A bit more investigation on this and I think I found what the differece is
at least. waagent is using camcontrol periphlist 3:1:0 to find devices,
and this has chnaged from placing the discs before the pass
devices to afterwards. So on an earlier version I get this:

root@joanna-may:/home/webadmin # camcontrol periphlist 3:1:0
da1:  generation: 4 index: 1 status: MORE
pass1:  generation: 4 index: 2 status: LAST

and on the box with the issue it does this:

root@backup-db:/home/webadmin # camcontrol periphlist 3:1:0
pass1:  generation: 4 index: 1 status: MORE
da1:  generation: 4 index: 2 status: LAST

So that box finds 'pass1' as the device when it should be finding 'da1'
which leads to the error. I have a vague memory of seeing a commit for this
go past too.

On the other hand, the oython looks like it shuold handle this, as it
appears to try and detect which devices are disks from the output of
gpart list, which should not let it use pass1 as if it was a disc.

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