Re: [CFT] packaging the base system with pkg(8)

[Andreas Nilsson]

On Mon, Mar 7, 2016 at 2:38 AM, Graham Menhennitt 
wrote:

>
>
> On 7/03/2016 12:28 PM, Warren Block wrote:
>
>> On Sun, 6 Mar 2016, Glen Barber wrote:
>>
>> On Sun, Mar 06, 2016 at 12:39:57PM +0100, Baptiste Daroussin wrote:
>>>
 On Thu, Mar 03, 2016 at 10:27:00AM +, Matthew Seaman wrote:

 It is planned to have a "precious" flag for packages which will prevent
 pkg
 delete -a from dropping them


>>> Note, there are valid use cases for deleting all packages, even those
>>> marked as 'precious'.  For example, a test chroot(8) or jail(8).  So the
>>> 'precious' flag would also need an override.
>>>
>>
>> # pkg delete -f --delete-my-precious-yes-i-know-just-do-it-already -a
>>
>
> No.
>
>   # pkg delete -f --mount-doom -a
>
> is the only way to destroy a preciou.
>
> Graham
>
> No, Mount Doom is a place. The way to destroy it is
--cast-it-into-the-fire.

The problem is that such a naming scheme belongs is some hobby Linux dist,
not in a serious production os.

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

Re: [CFT] packaging the base system with pkg(8)

[Graham Menhennitt]

On 7/03/2016 12:28 PM, Warren Block wrote:

On Sun, 6 Mar 2016, Glen Barber wrote:


On Sun, Mar 06, 2016 at 12:39:57PM +0100, Baptiste Daroussin wrote:

On Thu, Mar 03, 2016 at 10:27:00AM +, Matthew Seaman wrote:

It is planned to have a "precious" flag for packages which will 
prevent pkg

delete -a from dropping them



Note, there are valid use cases for deleting all packages, even those
marked as 'precious'.  For example, a test chroot(8) or jail(8).  So the
'precious' flag would also need an override.


# pkg delete -f --delete-my-precious-yes-i-know-just-do-it-already -a


No.

  # pkg delete -f --mount-doom -a

is the only way to destroy a preciou.

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

Re: [CFT] packaging the base system with pkg(8)

[Warren Block]

On Sun, 6 Mar 2016, Glen Barber wrote:


On Sun, Mar 06, 2016 at 12:39:57PM +0100, Baptiste Daroussin wrote:

On Thu, Mar 03, 2016 at 10:27:00AM +, Matthew Seaman wrote:

On 03/02/16 23:54, Glen Barber wrote:

Also note (as repeated below), running 'pkg delete -a' will implicitly
remove base system packages after they are installed.


This has the potential for many feet to be shot, given that up to now,
'pkg delete -a' would always leave you with a viable system.

We already make an exception for pkg itself -- you need 'pkg delete -fa'
to actually remove pkg(8) as well.  (Note to self: this needs to be
documented in the pkg-delete(8) man page.)

We should have similar exceptions for the essential bits of the base
system -- at minimum everything you need to boot the system up and
install stuff from a package repository.

We should also have a command line that will remove all ported software
but leave the base intact.   Maybe by adding '-r reponame' functionality
to 'pkg delete'?



It is planned to have a "precious" flag for packages which will prevent pkg
delete -a from dropping them



Note, there are valid use cases for deleting all packages, even those
marked as 'precious'.  For example, a test chroot(8) or jail(8).  So the
'precious' flag would also need an override.


# pkg delete -f --delete-my-precious-yes-i-know-just-do-it-already -a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: lldb input issue

[Pedro Giffuni]

On 03/06/16 15:20, Pedro Giffuni wrote:



El 06/03/2016 a las 15:05, Baptiste Daroussin escribió:

On Sun, Mar 06, 2016 at 10:55:27PM +0300, Roman Bogorodskiy wrote:

   Baptiste Daroussin wrote:


On Sun, Mar 06, 2016 at 07:44:34PM +0300, Roman Bogorodskiy wrote:

Hi,

I'm seeing an issue with lldb: when I start it (without arguments) and
try to type commands, it looks like this:

$  lldb
(lldb) \U+7F68\U+7F65\U+7F6C\U+7F70\U+7F0A

So, basically, I cannot execute any command and cannot even exit from
its shell, only by ctrl-z and killing it.

This happens to me on today's -CURRENT / amd64.

I was wondering if that's an issue with my user's locale, but the
behavior is same for root.

Also, I can see exactly the same behavior with lldb on FreeBSD.

^^^
Oops, that's supposed to be 'freefall'.


Is that some known issue or maybe configuration problem?

Thanks,

Roman Bogorodskiy



Sounds like an issue with libedit, probably due to the latest import
of libedit
(just a guess)

It could be. BTW, I've installed lldb38 using pkg and it works fine.


Which is linked to libedit from ports (older that in base) so it seems
to prove
that libedit update might be the issue there.


Hmm ... most of the changes were cosmetical. I will take a look though.



Actually we have had two updates lately with sufficient changes that it
is not easy to find which may be the culprit. I will revert the last
change in the hope that it is enough.

Sorry about this.

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

Re: lldb input issue

[Pedro Giffuni]

El 06/03/2016 a las 15:05, Baptiste Daroussin escribió:

On Sun, Mar 06, 2016 at 10:55:27PM +0300, Roman Bogorodskiy wrote:

   Baptiste Daroussin wrote:


On Sun, Mar 06, 2016 at 07:44:34PM +0300, Roman Bogorodskiy wrote:

Hi,

I'm seeing an issue with lldb: when I start it (without arguments) and
try to type commands, it looks like this:

$  lldb
(lldb) \U+7F68\U+7F65\U+7F6C\U+7F70\U+7F0A

So, basically, I cannot execute any command and cannot even exit from
its shell, only by ctrl-z and killing it.

This happens to me on today's -CURRENT / amd64.

I was wondering if that's an issue with my user's locale, but the
behavior is same for root.

Also, I can see exactly the same behavior with lldb on FreeBSD.

^^^
Oops, that's supposed to be 'freefall'.


Is that some known issue or maybe configuration problem?

Thanks,

Roman Bogorodskiy



Sounds like an issue with libedit, probably due to the latest import of libedit
(just a guess)

It could be. BTW, I've installed lldb38 using pkg and it works fine.


Which is linked to libedit from ports (older that in base) so it seems to prove
that libedit update might be the issue there.


Hmm ... most of the changes were cosmetical. I will take a look though.

Pedro.

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

Re: lldb input issue

[Baptiste Daroussin]

On Sun, Mar 06, 2016 at 10:55:27PM +0300, Roman Bogorodskiy wrote:
>   Baptiste Daroussin wrote:
> 
> > On Sun, Mar 06, 2016 at 07:44:34PM +0300, Roman Bogorodskiy wrote:
> > > Hi,
> > > 
> > > I'm seeing an issue with lldb: when I start it (without arguments) and
> > > try to type commands, it looks like this:
> > > 
> > > $  lldb
> > > (lldb) \U+7F68\U+7F65\U+7F6C\U+7F70\U+7F0A
> > > 
> > > So, basically, I cannot execute any command and cannot even exit from
> > > its shell, only by ctrl-z and killing it.
> > > 
> > > This happens to me on today's -CURRENT / amd64.
> > > 
> > > I was wondering if that's an issue with my user's locale, but the
> > > behavior is same for root.
> > > 
> > > Also, I can see exactly the same behavior with lldb on FreeBSD.
>^^^
> Oops, that's supposed to be 'freefall'.
> 
> > > Is that some known issue or maybe configuration problem?
> > > 
> > > Thanks,
> > > 
> > > Roman Bogorodskiy
> > 
> > 
> > 
> > Sounds like an issue with libedit, probably due to the latest import of 
> > libedit
> > (just a guess)
> 
> It could be. BTW, I've installed lldb38 using pkg and it works fine.
> 

Which is linked to libedit from ports (older that in base) so it seems to prove
that libedit update might be the issue there.

I have CC pfg@ who has updated libedit

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: lldb input issue

[Roman Bogorodskiy]

  Baptiste Daroussin wrote:

> On Sun, Mar 06, 2016 at 07:44:34PM +0300, Roman Bogorodskiy wrote:
> > Hi,
> > 
> > I'm seeing an issue with lldb: when I start it (without arguments) and
> > try to type commands, it looks like this:
> > 
> > $  lldb
> > (lldb) \U+7F68\U+7F65\U+7F6C\U+7F70\U+7F0A
> > 
> > So, basically, I cannot execute any command and cannot even exit from
> > its shell, only by ctrl-z and killing it.
> > 
> > This happens to me on today's -CURRENT / amd64.
> > 
> > I was wondering if that's an issue with my user's locale, but the
> > behavior is same for root.
> > 
> > Also, I can see exactly the same behavior with lldb on FreeBSD.
   ^^^
Oops, that's supposed to be 'freefall'.

> > Is that some known issue or maybe configuration problem?
> > 
> > Thanks,
> > 
> > Roman Bogorodskiy
> 
> 
> 
> Sounds like an issue with libedit, probably due to the latest import of 
> libedit
> (just a guess)

It could be. BTW, I've installed lldb38 using pkg and it works fine.


Roman Bogorodskiy


signature.asc
Description: PGP signature

Re: [CFT] packaging the base system with pkg(8)

[Glen Barber]

On Sun, Mar 06, 2016 at 12:39:57PM +0100, Baptiste Daroussin wrote:
> On Thu, Mar 03, 2016 at 10:27:00AM +, Matthew Seaman wrote:
> > On 03/02/16 23:54, Glen Barber wrote:
> > > Also note (as repeated below), running 'pkg delete -a' will implicitly
> > > remove base system packages after they are installed.
> > 
> > This has the potential for many feet to be shot, given that up to now,
> > 'pkg delete -a' would always leave you with a viable system.
> > 
> > We already make an exception for pkg itself -- you need 'pkg delete -fa'
> > to actually remove pkg(8) as well.  (Note to self: this needs to be
> > documented in the pkg-delete(8) man page.)
> > 
> > We should have similar exceptions for the essential bits of the base
> > system -- at minimum everything you need to boot the system up and
> > install stuff from a package repository.
> > 
> > We should also have a command line that will remove all ported software
> > but leave the base intact.   Maybe by adding '-r reponame' functionality
> > to 'pkg delete'?
> > 
> 
> It is planned to have a "precious" flag for packages which will prevent pkg
> delete -a from dropping them
> 

Note, there are valid use cases for deleting all packages, even those
marked as 'precious'.  For example, a test chroot(8) or jail(8).  So the
'precious' flag would also need an override.

Glen



signature.asc
Description: PGP signature

Re: lldb input issue

[Baptiste Daroussin]

On Sun, Mar 06, 2016 at 07:44:34PM +0300, Roman Bogorodskiy wrote:
> Hi,
> 
> I'm seeing an issue with lldb: when I start it (without arguments) and
> try to type commands, it looks like this:
> 
> $  lldb
> (lldb) \U+7F68\U+7F65\U+7F6C\U+7F70\U+7F0A
> 
> So, basically, I cannot execute any command and cannot even exit from
> its shell, only by ctrl-z and killing it.
> 
> This happens to me on today's -CURRENT / amd64.
> 
> I was wondering if that's an issue with my user's locale, but the
> behavior is same for root.
> 
> Also, I can see exactly the same behavior with lldb on FreeBSD.
> 
> Is that some known issue or maybe configuration problem?
> 
> Thanks,
> 
> Roman Bogorodskiy



Sounds like an issue with libedit, probably due to the latest import of libedit
(just a guess)

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Larry Rosenman]

On 2016-03-06 10:40, Nikolai Lifanov wrote:

On 2016-03-06 11:33, Dimitry Andric wrote:

On 06 Mar 2016, at 17:17, Larry Rosenman  wrote:


On 2016-03-06 08:54, Larry Rosenman wrote:

On 2016-03-06 08:49, Larry Rosenman wrote:

On 2016-03-06 08:40, Nikolai Lifanov wrote:

...

I loaded everything in this list other than acpi_dsdt override.
- Nikolai Lifanov

still breaks for me without the dsdt override :(

+list
https://svnweb.freebsd.org/changeset/base/296428 fixes it after 
installing the new boot1.efi


Thanks for the confirmation.  I could reproduce the panic locally, by
preloading the modules from the boot loader.

-Dimitry


I tend to load only what's absolutely necessary for a successful boot
from loader.conf
and load the rest from kld_list in rc.conf so that single user mode
has the greatest
chance of working.

- Nikolai Lifanov

However, it's a POLA violation to HAVE to do that :)

Thanks Dimitry for the quick fix.


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

lldb input issue

[Roman Bogorodskiy]

Hi,

I'm seeing an issue with lldb: when I start it (without arguments) and
try to type commands, it looks like this:

$  lldb
(lldb) \U+7F68\U+7F65\U+7F6C\U+7F70\U+7F0A

So, basically, I cannot execute any command and cannot even exit from
its shell, only by ctrl-z and killing it.

This happens to me on today's -CURRENT / amd64.

I was wondering if that's an issue with my user's locale, but the
behavior is same for root.

Also, I can see exactly the same behavior with lldb on FreeBSD.

Is that some known issue or maybe configuration problem?

Thanks,

Roman Bogorodskiy


signature.asc
Description: PGP signature

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Nikolai Lifanov]

On 2016-03-06 11:33, Dimitry Andric wrote:

On 06 Mar 2016, at 17:17, Larry Rosenman  wrote:


On 2016-03-06 08:54, Larry Rosenman wrote:

On 2016-03-06 08:49, Larry Rosenman wrote:

On 2016-03-06 08:40, Nikolai Lifanov wrote:

...

I loaded everything in this list other than acpi_dsdt override.
- Nikolai Lifanov

still breaks for me without the dsdt override :(

+list
https://svnweb.freebsd.org/changeset/base/296428 fixes it after 
installing the new boot1.efi


Thanks for the confirmation.  I could reproduce the panic locally, by
preloading the modules from the boot loader.

-Dimitry


I tend to load only what's absolutely necessary for a successful boot 
from loader.conf
and load the rest from kld_list in rc.conf so that single user mode has 
the greatest

chance of working.

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

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Dimitry Andric]

On 06 Mar 2016, at 17:17, Larry Rosenman  wrote:
> 
> On 2016-03-06 08:54, Larry Rosenman wrote:
>> On 2016-03-06 08:49, Larry Rosenman wrote:
>>> On 2016-03-06 08:40, Nikolai Lifanov wrote:
...
 I loaded everything in this list other than acpi_dsdt override.
 - Nikolai Lifanov
>>> still breaks for me without the dsdt override :(
>> +list
> https://svnweb.freebsd.org/changeset/base/296428 fixes it after installing 
> the new boot1.efi

Thanks for the confirmation.  I could reproduce the panic locally, by
preloading the modules from the boot loader.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Larry Rosenman]

On 2016-03-06 08:54, Larry Rosenman wrote:

On 2016-03-06 08:49, Larry Rosenman wrote:

On 2016-03-06 08:40, Nikolai Lifanov wrote:

On 2016-03-06 09:28, Larry Rosenman wrote:

On 2016-03-06 08:20, Larry Rosenman wrote:

On Sun, Mar 06, 2016 at 03:15:10PM +0100, Dimitry Andric wrote:

On 06 Mar 2016, at 06:20, Larry Rosenman  wrote:
>
> On 2016-03-05 18:46, Dimitry Andric wrote:
>> On 06 Mar 2016, at 00:30, Dimitry Andric  wrote:
>>> On 05 Mar 2016, at 22:32, Dimitry Andric  wrote:
 I imported the (tentative) 3.8.0 release of clang, llvm, lldb and
 compiler-rt into head, in r296417.  The upstream release is going to be
 very soon now, but I do not expect any changes anymore.
 This was tested with make universe, and a few exp-runs, but there is
 always a chance that you might run into something unexpected, either
 with the base system or ports.  In such cases, please file bugs, and
 make sure you note somewhere in the description that it is related to
 this import.
>>> Please hold off upgrading for now, if you are on amd64, and loading the
>>> aesni.ko module.  It appears that loading this module can cause the
>>> kernel ELF linker to panic, but it is not yet clear why.  This is being
>>> tracked in PR207729 [1].
>> It should be safe again after r296419.  Thanks to Kostik Belousov for
>> the quick fix.  (Clang 3.8.0 generates a different type for unwind
>> sections on amd64, and this was unexpected in the kernel linker.)
>> -Dimitry
>> [1] https://svnweb.freebsd.org/changeset/base/296419
> I'm getting a crash at startup (mi_startup) with a clang 3.8.0 kernel.
>
> Picture at:
> http://www.lerctr.org/~ler/FreeBSD/20160305_225532.jpg

It's pretty hard to make out, but it looks like it is panic'ing in
link_elf_reloc_local().  That should have been fixed with r296419, 
but
maybe there is yet another edge case that wasn't fixed.  Do you 
have a

crash dump and/or a backtrace?  Which modules are you preloading?

-Dimitry



loader,conf:

kern.msgbuf_clear="1"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
ichsmb_load="YES"
hwpmc_load="YES"
aesni_load="YES"
cryptodev_load="YES"
dtraceall_load="YES"
cpuctl_load="YES"
cuse_load="YES"
coretemp_load="YES"
#hw.usb.quirk.0="0x0bda 0x0129 0x3960 0x3960
UQ_MSC_FORCE_WIRE_BBB,UQ_MSC_FORCE_PROTO_SCSI"
#hw.usb.umass.debug="-1"

I'll see if I can get a better  pic with a backtrace.  This crash 
is

WAY early, so no dump :(



acpi_dsdt_load="YES"  # DSDT Overriding
acpi_dsdt_name="/boot/dsdt.aml"
#hw.psm.synaptics_support="1"


new pic: http://www.lerctr.org/~ler/FreeBSD/20160306_082426.jpg


I loaded everything in this list other than acpi_dsdt override.

- Nikolai Lifanov


still breaks for me without the dsdt override :(


+list
https://svnweb.freebsd.org/changeset/base/296428 fixes it after 
installing the new boot1.efi

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Larry Rosenman]

On 2016-03-06 08:49, Larry Rosenman wrote:

On 2016-03-06 08:40, Nikolai Lifanov wrote:

On 2016-03-06 09:28, Larry Rosenman wrote:

On 2016-03-06 08:20, Larry Rosenman wrote:

On Sun, Mar 06, 2016 at 03:15:10PM +0100, Dimitry Andric wrote:

On 06 Mar 2016, at 06:20, Larry Rosenman  wrote:
>
> On 2016-03-05 18:46, Dimitry Andric wrote:
>> On 06 Mar 2016, at 00:30, Dimitry Andric  wrote:
>>> On 05 Mar 2016, at 22:32, Dimitry Andric  wrote:
 I imported the (tentative) 3.8.0 release of clang, llvm, lldb and
 compiler-rt into head, in r296417.  The upstream release is going to be
 very soon now, but I do not expect any changes anymore.
 This was tested with make universe, and a few exp-runs, but there is
 always a chance that you might run into something unexpected, either
 with the base system or ports.  In such cases, please file bugs, and
 make sure you note somewhere in the description that it is related to
 this import.
>>> Please hold off upgrading for now, if you are on amd64, and loading the
>>> aesni.ko module.  It appears that loading this module can cause the
>>> kernel ELF linker to panic, but it is not yet clear why.  This is being
>>> tracked in PR207729 [1].
>> It should be safe again after r296419.  Thanks to Kostik Belousov for
>> the quick fix.  (Clang 3.8.0 generates a different type for unwind
>> sections on amd64, and this was unexpected in the kernel linker.)
>> -Dimitry
>> [1] https://svnweb.freebsd.org/changeset/base/296419
> I'm getting a crash at startup (mi_startup) with a clang 3.8.0 kernel.
>
> Picture at:
> http://www.lerctr.org/~ler/FreeBSD/20160305_225532.jpg

It's pretty hard to make out, but it looks like it is panic'ing in
link_elf_reloc_local().  That should have been fixed with r296419, 
but
maybe there is yet another edge case that wasn't fixed.  Do you 
have a

crash dump and/or a backtrace?  Which modules are you preloading?

-Dimitry



loader,conf:

kern.msgbuf_clear="1"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
ichsmb_load="YES"
hwpmc_load="YES"
aesni_load="YES"
cryptodev_load="YES"
dtraceall_load="YES"
cpuctl_load="YES"
cuse_load="YES"
coretemp_load="YES"
#hw.usb.quirk.0="0x0bda 0x0129 0x3960 0x3960
UQ_MSC_FORCE_WIRE_BBB,UQ_MSC_FORCE_PROTO_SCSI"
#hw.usb.umass.debug="-1"

I'll see if I can get a better  pic with a backtrace.  This crash is
WAY early, so no dump :(



acpi_dsdt_load="YES"  # DSDT Overriding
acpi_dsdt_name="/boot/dsdt.aml"
#hw.psm.synaptics_support="1"


new pic: http://www.lerctr.org/~ler/FreeBSD/20160306_082426.jpg


I loaded everything in this list other than acpi_dsdt override.

- Nikolai Lifanov


still breaks for me without the dsdt override :(


+list
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Nikolai Lifanov]

On 2016-03-06 09:28, Larry Rosenman wrote:

On 2016-03-06 08:20, Larry Rosenman wrote:

On Sun, Mar 06, 2016 at 03:15:10PM +0100, Dimitry Andric wrote:

On 06 Mar 2016, at 06:20, Larry Rosenman  wrote:
>
> On 2016-03-05 18:46, Dimitry Andric wrote:
>> On 06 Mar 2016, at 00:30, Dimitry Andric  wrote:
>>> On 05 Mar 2016, at 22:32, Dimitry Andric  wrote:
 I imported the (tentative) 3.8.0 release of clang, llvm, lldb and
 compiler-rt into head, in r296417.  The upstream release is going to be
 very soon now, but I do not expect any changes anymore.
 This was tested with make universe, and a few exp-runs, but there is
 always a chance that you might run into something unexpected, either
 with the base system or ports.  In such cases, please file bugs, and
 make sure you note somewhere in the description that it is related to
 this import.
>>> Please hold off upgrading for now, if you are on amd64, and loading the
>>> aesni.ko module.  It appears that loading this module can cause the
>>> kernel ELF linker to panic, but it is not yet clear why.  This is being
>>> tracked in PR207729 [1].
>> It should be safe again after r296419.  Thanks to Kostik Belousov for
>> the quick fix.  (Clang 3.8.0 generates a different type for unwind
>> sections on amd64, and this was unexpected in the kernel linker.)
>> -Dimitry
>> [1] https://svnweb.freebsd.org/changeset/base/296419
> I'm getting a crash at startup (mi_startup) with a clang 3.8.0 kernel.
>
> Picture at:
> http://www.lerctr.org/~ler/FreeBSD/20160305_225532.jpg

It's pretty hard to make out, but it looks like it is panic'ing in
link_elf_reloc_local().  That should have been fixed with r296419, 
but
maybe there is yet another edge case that wasn't fixed.  Do you have 
a

crash dump and/or a backtrace?  Which modules are you preloading?

-Dimitry



loader,conf:

kern.msgbuf_clear="1"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
ichsmb_load="YES"
hwpmc_load="YES"
aesni_load="YES"
cryptodev_load="YES"
dtraceall_load="YES"
cpuctl_load="YES"
cuse_load="YES"
coretemp_load="YES"
#hw.usb.quirk.0="0x0bda 0x0129 0x3960 0x3960
UQ_MSC_FORCE_WIRE_BBB,UQ_MSC_FORCE_PROTO_SCSI"
#hw.usb.umass.debug="-1"

I'll see if I can get a better  pic with a backtrace.  This crash is
WAY early, so no dump :(



acpi_dsdt_load="YES"  # DSDT Overriding
acpi_dsdt_name="/boot/dsdt.aml"
#hw.psm.synaptics_support="1"


new pic: http://www.lerctr.org/~ler/FreeBSD/20160306_082426.jpg


I loaded everything in this list other than acpi_dsdt override.

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

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Larry Rosenman]

On 2016-03-06 08:20, Larry Rosenman wrote:

On Sun, Mar 06, 2016 at 03:15:10PM +0100, Dimitry Andric wrote:

On 06 Mar 2016, at 06:20, Larry Rosenman  wrote:
>
> On 2016-03-05 18:46, Dimitry Andric wrote:
>> On 06 Mar 2016, at 00:30, Dimitry Andric  wrote:
>>> On 05 Mar 2016, at 22:32, Dimitry Andric  wrote:
 I imported the (tentative) 3.8.0 release of clang, llvm, lldb and
 compiler-rt into head, in r296417.  The upstream release is going to be
 very soon now, but I do not expect any changes anymore.
 This was tested with make universe, and a few exp-runs, but there is
 always a chance that you might run into something unexpected, either
 with the base system or ports.  In such cases, please file bugs, and
 make sure you note somewhere in the description that it is related to
 this import.
>>> Please hold off upgrading for now, if you are on amd64, and loading the
>>> aesni.ko module.  It appears that loading this module can cause the
>>> kernel ELF linker to panic, but it is not yet clear why.  This is being
>>> tracked in PR207729 [1].
>> It should be safe again after r296419.  Thanks to Kostik Belousov for
>> the quick fix.  (Clang 3.8.0 generates a different type for unwind
>> sections on amd64, and this was unexpected in the kernel linker.)
>> -Dimitry
>> [1] https://svnweb.freebsd.org/changeset/base/296419
> I'm getting a crash at startup (mi_startup) with a clang 3.8.0 kernel.
>
> Picture at:
> http://www.lerctr.org/~ler/FreeBSD/20160305_225532.jpg

It's pretty hard to make out, but it looks like it is panic'ing in
link_elf_reloc_local().  That should have been fixed with r296419, but
maybe there is yet another edge case that wasn't fixed.  Do you have a
crash dump and/or a backtrace?  Which modules are you preloading?

-Dimitry



loader,conf:

kern.msgbuf_clear="1"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
ichsmb_load="YES"
hwpmc_load="YES"
aesni_load="YES"
cryptodev_load="YES"
dtraceall_load="YES"
cpuctl_load="YES"
cuse_load="YES"
coretemp_load="YES"
#hw.usb.quirk.0="0x0bda 0x0129 0x3960 0x3960
UQ_MSC_FORCE_WIRE_BBB,UQ_MSC_FORCE_PROTO_SCSI"
#hw.usb.umass.debug="-1"

I'll see if I can get a better  pic with a backtrace.  This crash is
WAY early, so no dump :(



acpi_dsdt_load="YES"  # DSDT Overriding
acpi_dsdt_name="/boot/dsdt.aml"
#hw.psm.synaptics_support="1"


new pic: http://www.lerctr.org/~ler/FreeBSD/20160306_082426.jpg


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Larry Rosenman]

On Sun, Mar 06, 2016 at 03:15:10PM +0100, Dimitry Andric wrote:
> On 06 Mar 2016, at 06:20, Larry Rosenman  wrote:
> > 
> > On 2016-03-05 18:46, Dimitry Andric wrote:
> >> On 06 Mar 2016, at 00:30, Dimitry Andric  wrote:
> >>> On 05 Mar 2016, at 22:32, Dimitry Andric  wrote:
>  I imported the (tentative) 3.8.0 release of clang, llvm, lldb and
>  compiler-rt into head, in r296417.  The upstream release is going to be
>  very soon now, but I do not expect any changes anymore.
>  This was tested with make universe, and a few exp-runs, but there is
>  always a chance that you might run into something unexpected, either
>  with the base system or ports.  In such cases, please file bugs, and
>  make sure you note somewhere in the description that it is related to
>  this import.
> >>> Please hold off upgrading for now, if you are on amd64, and loading the
> >>> aesni.ko module.  It appears that loading this module can cause the
> >>> kernel ELF linker to panic, but it is not yet clear why.  This is being
> >>> tracked in PR207729 [1].
> >> It should be safe again after r296419.  Thanks to Kostik Belousov for
> >> the quick fix.  (Clang 3.8.0 generates a different type for unwind
> >> sections on amd64, and this was unexpected in the kernel linker.)
> >> -Dimitry
> >> [1] https://svnweb.freebsd.org/changeset/base/296419
> > I'm getting a crash at startup (mi_startup) with a clang 3.8.0 kernel.
> > 
> > Picture at:
> > http://www.lerctr.org/~ler/FreeBSD/20160305_225532.jpg
> 
> It's pretty hard to make out, but it looks like it is panic'ing in
> link_elf_reloc_local().  That should have been fixed with r296419, but
> maybe there is yet another edge case that wasn't fixed.  Do you have a
> crash dump and/or a backtrace?  Which modules are you preloading?
> 
> -Dimitry
> 

loader,conf:

kern.msgbuf_clear="1"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
ichsmb_load="YES"
hwpmc_load="YES"
aesni_load="YES"
cryptodev_load="YES"
dtraceall_load="YES"
cpuctl_load="YES"
cuse_load="YES"
coretemp_load="YES"
#hw.usb.quirk.0="0x0bda 0x0129 0x3960 0x3960 
UQ_MSC_FORCE_WIRE_BBB,UQ_MSC_FORCE_PROTO_SCSI"
#hw.usb.umass.debug="-1"

I'll see if I can get a better  pic with a backtrace.  This crash is WAY early, 
so no dump :(



acpi_dsdt_load="YES"# DSDT Overriding
acpi_dsdt_name="/boot/dsdt.aml"
#hw.psm.synaptics_support="1"



-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[Dimitry Andric]

On 06 Mar 2016, at 06:20, Larry Rosenman  wrote:
> 
> On 2016-03-05 18:46, Dimitry Andric wrote:
>> On 06 Mar 2016, at 00:30, Dimitry Andric  wrote:
>>> On 05 Mar 2016, at 22:32, Dimitry Andric  wrote:
 I imported the (tentative) 3.8.0 release of clang, llvm, lldb and
 compiler-rt into head, in r296417.  The upstream release is going to be
 very soon now, but I do not expect any changes anymore.
 This was tested with make universe, and a few exp-runs, but there is
 always a chance that you might run into something unexpected, either
 with the base system or ports.  In such cases, please file bugs, and
 make sure you note somewhere in the description that it is related to
 this import.
>>> Please hold off upgrading for now, if you are on amd64, and loading the
>>> aesni.ko module.  It appears that loading this module can cause the
>>> kernel ELF linker to panic, but it is not yet clear why.  This is being
>>> tracked in PR207729 [1].
>> It should be safe again after r296419.  Thanks to Kostik Belousov for
>> the quick fix.  (Clang 3.8.0 generates a different type for unwind
>> sections on amd64, and this was unexpected in the kernel linker.)
>> -Dimitry
>> [1] https://svnweb.freebsd.org/changeset/base/296419
> I'm getting a crash at startup (mi_startup) with a clang 3.8.0 kernel.
> 
> Picture at:
> http://www.lerctr.org/~ler/FreeBSD/20160305_225532.jpg

It's pretty hard to make out, but it looks like it is panic'ing in
link_elf_reloc_local().  That should have been fixed with r296419, but
maybe there is yet another edge case that wasn't fixed.  Do you have a
crash dump and/or a backtrace?  Which modules are you preloading?

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: HEADS UP: clang/llvm/lldb/compiler-rt 3.8.0 imported

[O. Hartmann]

Am Sun, 6 Mar 2016 01:46:44 +0100
Dimitry Andric  schrieb:

> On 06 Mar 2016, at 00:30, Dimitry Andric  wrote:
> > 
> > On 05 Mar 2016, at 22:32, Dimitry Andric  wrote:  
> >> 
> >> I imported the (tentative) 3.8.0 release of clang, llvm, lldb and
> >> compiler-rt into head, in r296417.  The upstream release is going to be
> >> very soon now, but I do not expect any changes anymore.
> >> 
> >> This was tested with make universe, and a few exp-runs, but there is
> >> always a chance that you might run into something unexpected, either
> >> with the base system or ports.  In such cases, please file bugs, and
> >> make sure you note somewhere in the description that it is related to
> >> this import.  
> > 
> > Please hold off upgrading for now, if you are on amd64, and loading the
> > aesni.ko module.  It appears that loading this module can cause the
> > kernel ELF linker to panic, but it is not yet clear why.  This is being
> > tracked in PR207729 [1].  
> 
> It should be safe again after r296419.  Thanks to Kostik Belousov for
> the quick fix.  (Clang 3.8.0 generates a different type for unwind
> sections on amd64, and this was unexpected in the kernel linker.)
> 
> -Dimitry
> 
> [1] https://svnweb.freebsd.org/changeset/base/296419
> 

"make delete-old-dirs" complains about not empty dir as shown below:
 
 [src] ll -R /usr/lib/clang/3.7.1
total 12
802562 drwxr-xr-x  3 root  wheel  -  512B Mar  6 10:38 ./
803264 drwxr-xr-x  4 root  wheel  -  512B Mar  6 10:34 ../
802584 drwxr-xr-x  3 root  wheel  -  512B Dec 26 12:59 lib/

/usr/lib/clang/3.7.1/lib:
total 12
802584 drwxr-xr-x  3 root  wheel  -  512B Dec 26 12:59 ./
802562 drwxr-xr-x  3 root  wheel  -  512B Mar  6 10:38 ../
802592 drwxr-xr-x  2 root  wheel  -  512B Mar  6 10:38 freebsd/

/usr/lib/clang/3.7.1/lib/freebsd:
total 12
802592 drwxr-xr-x  2 root  wheel  -  512B Mar  6 10:38 ./
802584 drwxr-xr-x  3 root  wheel  -  512B Dec 26 12:59 ../
802657 -r--r--r--  1 root  wheel  -  980B Jan 10 10:11 
libclang_rt.asan-preinit-x86_64.a


Nice to have 3.8.0 now, thanks for all the work!

Regards,
Oliver


pgp_IlHsHOtfL.pgp
Description: OpenPGP digital signature

Re: Contributing

[Eax Melanhovich]

Hello, Aneesh

I believe that "Guide to contribute to kernel video drivers" thread
could interest you:

https://lists.freebsd.org/pipermail/freebsd-x11/2016-February/thread.html#17226

Also in this thread you will find actual books and articles regarding
FreeBSD kernel development.

-- 
Best regards,
Eax Melanhovich
http://eax.me/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] packaging the base system with pkg(8)

[Baptiste Daroussin]

On Thu, Mar 03, 2016 at 10:27:00AM +, Matthew Seaman wrote:
> On 03/02/16 23:54, Glen Barber wrote:
> > Also note (as repeated below), running 'pkg delete -a' will implicitly
> > remove base system packages after they are installed.
> 
> This has the potential for many feet to be shot, given that up to now,
> 'pkg delete -a' would always leave you with a viable system.
> 
> We already make an exception for pkg itself -- you need 'pkg delete -fa'
> to actually remove pkg(8) as well.  (Note to self: this needs to be
> documented in the pkg-delete(8) man page.)
> 
> We should have similar exceptions for the essential bits of the base
> system -- at minimum everything you need to boot the system up and
> install stuff from a package repository.
> 
> We should also have a command line that will remove all ported software
> but leave the base intact.   Maybe by adding '-r reponame' functionality
> to 'pkg delete'?
> 

It is planned to have a "precious" flag for packages which will prevent pkg
delete -a from dropping them

Best regards,
Bapt


signature.asc
Description: PGP signature