Re: [gentoo-user] ruby 22

[Stroller]

> On 20 Aug 2017, at 15:19, allan gottlieb  wrote:
> 
> I am currently running ruby21 (ruby-2.1.9).
> All such versions of ruby are masked so this is clearly a mistake
> on my part.  I was alerted to this error by dev-ruby/rdoc-4.2.0
> failing to build on today's emerge --update @world

If this was a mistake on your part then you're not alone.

I appear currently to have both ruby-2.1.9 and ruby-2.2.6 installed on two 
systems, last sync'd 6/7/2017 and 20/7/2017, with select showing ruby21 as 
current version on both.

Stroller.

Re: [gentoo-user] ruby 22

[allan gottlieb]

On Sun, Aug 20 2017, Alec Ten Harmsel wrote:

> On 08/20/2017 08:19 AM, allan gottlieb wrote:
>> I am currently running ruby21 (ruby-2.1.9).
>> All such versions of ruby are masked so this is clearly a mistake
>> on my part.  I was alerted to this error by dev-ruby/rdoc-4.2.0
>> failing to build on today's emerge --update @world
>>
>> After I do
>>eselect ruby set ruby22
>> can I simply
>>emerge --update @world
>> or must I explicitly rebuild some ruby packages?
>
> I don't believe that will be enough. You should update RUBY_TARGETS in
> /etc/portage/make.conf if you have it set. If you don't have it set
> and are still getting this error, that's a bug and should be filed on
> b.g.o. I have a custom RUBY_TARGETS as I do some ruby development, so
> I don't have a vanilla system to test this on.
>
> Also, you'll have to run a slightly different command to update (since
> RUBY_TARGETS, PYTHON_TARGETS, etc. are USE flags underneath):
>
> emerge --update --newuse --deep @world
>
> You shouldn't have to 'eselect ruby' either - portage will do this for
> you while updating.
>
> Alec

Not sure I understand.

1.  I should have been more complete about the command I run
  
  MAKEOPTS="--jobs=8 --load-average=5"
  emerge --ask --deep --tree --jobs --load-average=5 \
 --update --changed-use --with-bdeps=y @world

2.  I do not have "ruby" or "RUBY" anywhere in the tree rooted
at /etc/portage

3.  emerge did not offer to upgrade RUBY_TARGETS does
not seem happy with ruby21 since the emerge output includes
[ebuild   R]dev-ruby/test-unit-3.1.9  RUBY_TARGETS="(-ruby21%*)" 
[ebuild   R]dev-ruby/rdoc-4.2.0  RUBY_TARGETS="(-ruby21%*)" 
[ebuild   R]dev-ruby/minitest-5.8.4  RUBY_TARGETS="(-ruby21%*)" 

4.  I synced the tree today just before the emerge.  Might I have picked
up an inconsistent tree and hence should I resync?

5.  The emerge error msg is below.

6.  I have NOT done the eselect ruby set ruby 22.

Thanks for you help
allan



>>> Install rdoc-4.2.0 into /var/tmp/portage/dev-ruby/rdoc-4.2.0/image/ 
>>> category dev-ruby
 * Running install phase for ruby22 ...
 * Running install phase for all ...
 * ERROR: dev-ruby/rdoc-4.2.0::gentoo failed (install phase):
 *   USE Flag 'ruby_targets_ruby21' not in IUSE for dev-ruby/rdoc-4.2.0
 * 
 * Call stack:
 *  ebuild.sh, line  115:  Called src_install
 *environment, line 4405:  Called ruby-ng_src_install
 *environment, line 4105:  Called _ruby_invoke_environment 'all' 
'all_ruby_install'
 *environment, line  540:  Called all_ruby_install
 *environment, line  636:  Called use 'ruby_targets_ruby21'
 *   phase-helpers.sh, line  200:  Called die
 * The specific snippet of code:
 *  die "USE Flag '${u}' not in IUSE for 
${CATEGORY}/${PF}"
 * 
 * If you need support, post the output of `emerge --info 
'=dev-ruby/rdoc-4.2.0::gentoo'`,
 * the complete build log and the output of `emerge -pqv 
'=dev-ruby/rdoc-4.2.0::gentoo'`.

Re: [gentoo-user] Kernel 4.12.5 hard lockups, nothing in logs.

[Roman Dobosz]

On Sun, 20 Aug 2017 11:47:14 +0800
Bill Kenworthy  wrote:

> Hi all,
>   I am getting random lockups on kernel 4.12.5.
> 
> Three intel hosts (atom, early i7, i7 haswell) - its worse after a
> suspend resume session.  Because these are in use Ive gone back to
> 4.9.34 which is stable.
> 
> I also have some VM's and an MS surface pro 4 which are stable on
> 4.12.5, 6 and 8) - confusing!
> 
> Is anyone else seeing this?

Yup, on one of my laptops I use, I have also experienced lockups, so
I've been forced to downgrade to 4.9.x. On two other machines (one of
it is my personal pc used at daily basis, the other is just a PC for
storage purposes) I didn't noticed anything like that…

-- 
  -^-  _   something is grinding the emptiness:
   _ /O)_\//   Velvet Acid Christ - Caustic Disco
  (_(|__(_(_) grf.

Re: [gentoo-user] ruby 22

[Alec Ten Harmsel]

On 08/20/2017 08:19 AM, allan gottlieb wrote:

I am currently running ruby21 (ruby-2.1.9).
All such versions of ruby are masked so this is clearly a mistake
on my part.  I was alerted to this error by dev-ruby/rdoc-4.2.0
failing to build on today's emerge --update @world

After I do
   eselect ruby set ruby22
can I simply
   emerge --update @world
or must I explicitly rebuild some ruby packages?


I don't believe that will be enough. You should update RUBY_TARGETS in 
/etc/portage/make.conf if you have it set. If you don't have it set and 
are still getting this error, that's a bug and should be filed on b.g.o. 
I have a custom RUBY_TARGETS as I do some ruby development, so I don't 
have a vanilla system to test this on.


Also, you'll have to run a slightly different command to update (since 
RUBY_TARGETS, PYTHON_TARGETS, etc. are USE flags underneath):


emerge --update --newuse --deep @world

You shouldn't have to 'eselect ruby' either - portage will do this for 
you while updating.


Alec

[gentoo-user] ruby 22

[allan gottlieb]

I am currently running ruby21 (ruby-2.1.9).
All such versions of ruby are masked so this is clearly a mistake
on my part.  I was alerted to this error by dev-ruby/rdoc-4.2.0
failing to build on today's emerge --update @world

After I do
  eselect ruby set ruby22
can I simply
  emerge --update @world
or must I explicitly rebuild some ruby packages?

Thanks,
allan

Re: [gentoo-user] Nameserver lookups fail on virtual server after Kernel upgrade from version 4.9 to 4.12

[Ralph Seichter]

On 20.08.2017 08:17, Neil Bothwick wrote:

> I'd try again with a clean kernel tree but using make oldconfig. It's
> possible the automagic stuff answered n somewhere where you need a y.

As https://wiki.gentoo.org/wiki/Kernel/Upgrade/en#make_silentoldconfig
describes, "make silentoldconfig" (which I used) asks for a decision for
all newly introduced kernel options.

Most default to "no" anyway, but I have painstakingly read each of the
new descriptions to figure out if I might need the options. I've done it
several times, and I still cannot figure out if I missed anything. Here
is a subset of the options I have configured, perhaps you can spot if
something is amiss? Of course, grep VIRT is not exactly the most precise
approach...

  ### Server 1 (high volume traffic)
  $ grep VIRT .config | sort
  CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
  CONFIG_BLK_MQ_VIRTIO=y
  # CONFIG_DEBUG_VIRTUAL is not set
  # CONFIG_DMA_VIRT_OPS is not set
  CONFIG_DMA_VIRTUAL_CHANNELS=y
  # CONFIG_DRM_VIRTIO_GPU is not set
  # CONFIG_FB_VIRTUAL is not set
  CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
  CONFIG_HW_RANDOM_VIRTIO=y
  CONFIG_PARAVIRT_CLOCK=y
  # CONFIG_PARAVIRT_DEBUG is not set
  CONFIG_PARAVIRT_SPINLOCKS=y
  # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
  CONFIG_PARAVIRT=y
  CONFIG_SCSI_VIRTIO=y
  # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
  # CONFIG_VIRT_DRIVERS is not set
  CONFIG_VIRTIO_BALLOON=m
  # CONFIG_VIRTIO_BLK_SCSI is not set
  CONFIG_VIRTIO_BLK=y
  CONFIG_VIRTIO_CONSOLE=y
  # CONFIG_VIRTIO_INPUT is not set
  # CONFIG_VIRTIO_MMIO is not set
  CONFIG_VIRTIO_NET=y
  CONFIG_VIRTIO_PCI_LEGACY=y
  CONFIG_VIRTIO_PCI=y
  CONFIG_VIRTIO=y
  CONFIG_VIRT_TO_BUS=y
  # CONFIG_VIRTUALIZATION is not set

I have since updated a second virtual Gentoo server to Kernel 4.12. This
server sees a lot less network traffic, but after a couple of hours it
runs into the same timeouts when attempting to contact resolvers. Kernel
settings include:

  ### Server 2 (low volume traffic)
  $ grep VIRT .config | sort
  CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
  CONFIG_BLK_MQ_VIRTIO=y
  # CONFIG_DEBUG_VIRTUAL is not set
  # CONFIG_DMA_VIRT_OPS is not set
  CONFIG_DMA_VIRTUAL_CHANNELS=y
  # CONFIG_DRM_VIRTIO_GPU is not set
  # CONFIG_FB_VIRTUAL is not set
  CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
  CONFIG_HW_RANDOM_VIRTIO=y
  CONFIG_PARAVIRT_CLOCK=y
  # CONFIG_PARAVIRT_DEBUG is not set
  CONFIG_PARAVIRT_SPINLOCKS=y
  # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
  CONFIG_PARAVIRT=y
  CONFIG_SCSI_VIRTIO=y
  # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
  # CONFIG_VIRT_DRIVERS is not set
  CONFIG_VIRTIO_BALLOON=m
  # CONFIG_VIRTIO_BLK_SCSI is not set
  CONFIG_VIRTIO_BLK=y
  CONFIG_VIRTIO_CONSOLE=y
  # CONFIG_VIRTIO_INPUT is not set
  # CONFIG_VIRTIO_MMIO is not set
  CONFIG_VIRTIO_NET=y
  CONFIG_VIRTIO_PCI_LEGACY=y
  CONFIG_VIRTIO_PCI=y
  CONFIG_VIRTIO=y
  CONFIG_VIRT_TO_BUS=y
  CONFIG_VIRTUALIZATION=y

As you can see, I used CONFIG_VIRTUALIZATION=y in this case, even though
I believe this only affects running as a VM host. I carried this option
over from the previous 4.9 kernel.

-Ralph

Re: [gentoo-user] Kernel 4.12.5 hard lockups, nothing in logs.

[Mick]

On Sunday, 20 August 2017 10:39:51 BST Bill Kenworthy wrote:
> On 20/08/17 17:21, Alan McKinnon wrote:
> > On 20/08/2017 05:47, Bill Kenworthy wrote:
> >> Hi all,
> >> 
> >>I am getting random lockups on kernel 4.12.5.
> >> 
> >> Three intel hosts (atom, early i7, i7 haswell) - its worse after a
> >> suspend resume session.  Because these are in use Ive gone back to
> >> 4.9.34 which is stable.
> >> 
> >> I also have some VM's and an MS surface pro 4 which are stable on
> >> 4.12.5, 6 and 8) - confusing!
> >> 
> >> Is anyone else seeing this?
> >> 
> >> BillK
> > 
> > Neil's reply elsewhere to Ralph may have the smoking gun clue.
> > 
> > I'm seeing changes in 4.12 too and haven't bothered looking further as
> > 4.11 still works for me. My external monitors and USB keyboard & mouse
> > on laptops stopped working with 4.12 and other silliness which I forget.
> > 
> > My techie spidey-sense is telling me it all smells a lot like someone
> > tidied up .config and things moved around, so make oldconfig got confused.
> 
> Not to mention changing the bcache device numbering - instead of
> /dev/bacache0, /dev/bcache1 etc. its become /dev/bcache0, /dev/bcache16,
> /dev/bcache32, ... (offset of 16)
> 
> That bit me too ...
> 
> BillK

When running make oldconfig, which I prefer because it asks me to confirm 
settings for all new modules, Alan should make sure CONFIG_USB=y is set so.  
>From what I recall the oldconfig default setting is 'not set', so user input 
is required.

Unfortunately, I have no idea why Bill's hard lockups occur.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Kernel 4.12.5 hard lockups, nothing in logs.

[Bill Kenworthy]

On 20/08/17 17:21, Alan McKinnon wrote:
> On 20/08/2017 05:47, Bill Kenworthy wrote:
>> Hi all,
>>  I am getting random lockups on kernel 4.12.5.
>>
>> Three intel hosts (atom, early i7, i7 haswell) - its worse after a
>> suspend resume session.  Because these are in use Ive gone back to
>> 4.9.34 which is stable.
>>
>> I also have some VM's and an MS surface pro 4 which are stable on
>> 4.12.5, 6 and 8) - confusing!
>>
>> Is anyone else seeing this?
>>
>> BillK
>>
> 
> 
> Neil's reply elsewhere to Ralph may have the smoking gun clue.
> 
> I'm seeing changes in 4.12 too and haven't bothered looking further as
> 4.11 still works for me. My external monitors and USB keyboard & mouse
> on laptops stopped working with 4.12 and other silliness which I forget.
> 
> My techie spidey-sense is telling me it all smells a lot like someone
> tidied up .config and things moved around, so make oldconfig got confused.
> 

Not to mention changing the bcache device numbering - instead of
/dev/bacache0, /dev/bcache1 etc. its become /dev/bcache0, /dev/bcache16,
/dev/bcache32, ... (offset of 16)

That bit me too ...

BillK

Re: [gentoo-user] Kernel 4.12.5 hard lockups, nothing in logs.

[Alan McKinnon]

On 20/08/2017 05:47, Bill Kenworthy wrote:
> Hi all,
>   I am getting random lockups on kernel 4.12.5.
> 
> Three intel hosts (atom, early i7, i7 haswell) - its worse after a
> suspend resume session.  Because these are in use Ive gone back to
> 4.9.34 which is stable.
> 
> I also have some VM's and an MS surface pro 4 which are stable on
> 4.12.5, 6 and 8) - confusing!
> 
> Is anyone else seeing this?
> 
> BillK
> 


Neil's reply elsewhere to Ralph may have the smoking gun clue.

I'm seeing changes in 4.12 too and haven't bothered looking further as
4.11 still works for me. My external monitors and USB keyboard & mouse
on laptops stopped working with 4.12 and other silliness which I forget.

My techie spidey-sense is telling me it all smells a lot like someone
tidied up .config and things moved around, so make oldconfig got confused.

-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] Compiling full featured doxygen...replacing CLisp

[tuxic]

Hi,

For a test to create all documentation for the LUFA library
(USB/Arduino: http://fourwalledcubicle.com/LUFA.php) with doxygen,
I enabled all USE-flags for that package and start compiling.

One package failed to build: CLisp.
But I have working installation of sbcl installed, which
is as to my knowledge also common list compatible.

Before digging into the problems, why CLisp does not compile
and installing a second common lisp package (which I dont
use...I have sbcl and I am happy with it:)   :

Is there a way to explain emerge/portage just to use sbcl instead
of CLisp?

Thanks a lot for any help in advance!
Cheers
Meino

Re: [gentoo-user] Nameserver lookups fail on virtual server after Kernel upgrade from version 4.9 to 4.12

[Neil Bothwick]

I'd try again with a clean kernel tree but using make oldconfig. It's possible 
the automagic stuff answered n somewhere where you need a y. 

On 19 August 2017 21:28:05 EEST, Ralph Seichter  
wrote:
>It seems strange to me as I write it, but since I updated one of my
>virtual servers from Kernel version 4.9.34 to 4.12.5, the server
>(Gentoo
>Linux running as a KVM guest) is experiencing timeouts when trying to
>connect to DNS resolvers. For the Kernel update, I followed the same
>steps I used for years, like
>
>  cd /usr/src/linux
>  zcat /proc/config.gz >.config
>  make silentoldconfig (answering "no" whereever possible)
>  make ...
>
>After booting with Kernel 4.12, commands like "dig +trace www.ibm.com"
>work just fine for a while, duration depending on server load, but
>after
>some threshold is passed, all further attempts to contact resolvers
>fail
>due to timeouts.
>
>I have tried running a local, caching resolver (BIND 9) on the server,
>like I usually do, and also tried using the hoster's dedicated
>resolvers.
>With Kernel 4.12, I see timeouts in both cases. These problems do not
>occur when I boot with the 4.9 Kernel which I have been using for the
>past two months.
>
>It is also worth noting that I updated two other servers to Kernel 4.12
>without any issues, but these are "real" servers, not VMs. At this
>point
>I am searching for ways to debug the issue, vaguely suspecting some KVM
>magic behind it (without any proof). I know that Kernel 4.11 introduced
>several KVM related changes, but that's about it.
>
>I appreciate all pointers.
>
>-Ralph

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.