Re: [gentoo-user] Bug in run-crons?

[Wols Lists]

On 13/12/2021 22:03, Frank Steinmetzger wrote:

If they are involved multiple times
with the default options I think any attempt to scrub something that
is already being scrubbed is just a no-op.  Obviously if you don't
want all that IO during the day you'll have to do something more
clever - you can instruct it to pause and resume so you could have a
couple of crontab entries and scripts to do just that.



Or, since I am the only user of that system, I could go back to my previous
way: just run the scrub manually every other month or so before I go to bed.
Because then I know that nothing will interfere with it and it won’t
interfere with anything else.


Yup. I was thinking that. The problem with scrubs et al auto-resuming or 
firing at boot is that disk i/o is then knackered for ages, and 
interferes with whatever it is you're actually trying to do :-)


Cheers,
Wol

Re: [gentoo-user] Bug in run-crons?

[Frank Steinmetzger]

Am Mon, Dec 13, 2021 at 04:54:30PM -0500 schrieb Rich Freeman:
> On Mon, Dec 13, 2021 at 4:42 PM Michael Orlitzky  wrote:
> >
> > On Mon, 2021-12-13 at 22:38 +0100, Frank Steinmetzger wrote:
> > >
> > > Well I *could* disable run-crons altogether and add entries to fcron’s own
> > > crontab which would run those scripts in /etc/cron.{hourly,daily,...}
> > > instead.
> > >
> > > However, I like predictable times at which those jobs will run. Especially
> > > if one of them is a zfs scrub; the NAS is powered down for weeks, 
> > > sometimes
> > > months. And when I power it up, it’s for a reason. And that reason usually
> > > is not a scrub, which—at the current zfs fill level—takes 10½ hours.
> > >
> >
> > Why choose fcron then? It sounds like you have the same rationale as I
> > do: "no, I don't want to run the 4am backup job in the middle of the
> > business day just because it wasn't run at 4am."

Fair point.
Fcron has a serialisation feature, so that for instance updatedb and mandb
don’t run at the same time. Me kinda liky.

> fcron is perfectly capable of running jobs at either set times or at
> loosely-defined intervals that are compensated for if the machine is
> off.

Indeed, I can say "@monthly * 0 *" to run a monthly job (like the scrub)
only at night. *pondering*

> Systemd timers can also be set that way, and can also have
> limits put on scheduling (daily nominally at 3AM but allowed between
> 11PM and 5AM or whatever).  Obviously the more expressive the crontab
> equivalent is, the more you can tweak it to do what you want it to.

I’ve gotten used to systemd on my Arch-based desktops. But the NAS is still
on good-ol’ openrc. :)

> I'll also note that zfs scrubs checkpoint at shutdown and will
> auto-resume where you leave off.

That’s a nice bit of knowledge.

> If they are involved multiple times
> with the default options I think any attempt to scrub something that
> is already being scrubbed is just a no-op.  Obviously if you don't
> want all that IO during the day you'll have to do something more
> clever - you can instruct it to pause and resume so you could have a
> couple of crontab entries and scripts to do just that.

Or, since I am the only user of that system, I could go back to my previous
way: just run the scrub manually every other month or so before I go to bed.
Because then I know that nothing will interfere with it and it won’t
interfere with anything else.

-- 
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

This message was written using only recycled electrons.


signature.asc
Description: PGP signature

Re: [gentoo-user] Bug in run-crons?

[Rich Freeman]

On Mon, Dec 13, 2021 at 4:42 PM Michael Orlitzky  wrote:
>
> On Mon, 2021-12-13 at 22:38 +0100, Frank Steinmetzger wrote:
> >
> > Well I *could* disable run-crons altogether and add entries to fcron’s own
> > crontab which would run those scripts in /etc/cron.{hourly,daily,...}
> > instead.
> >
> > However, I like predictable times at which those jobs will run. Especially
> > if one of them is a zfs scrub; the NAS is powered down for weeks, sometimes
> > months. And when I power it up, it’s for a reason. And that reason usually
> > is not a scrub, which—at the current zfs fill level—takes 10½ hours.
> >
>
> Why choose fcron then? It sounds like you have the same rationale as I
> do: "no, I don't want to run the 4am backup job in the middle of the
> business day just because it wasn't run at 4am."
>
> If you pick a dumber cron, the crontab entries are run only at the
> specified times.

There really are no one-size-fits all solutions obviously.  You can
either have predictable times and if the machine is down things get
skipped, or you can run opportunistically in which case you lose
predictable times at least until the machine goes back to running
24x7.  The machine has no way to know if you'll leave it on overnight
the NEXT night - only if you did so the one before.

fcron is perfectly capable of running jobs at either set times or at
loosely-defined intervals that are compensated for if the machine is
off.  Systemd timers can also be set that way, and can also have
limits put on scheduling (daily nominally at 3AM but allowed between
11PM and 5AM or whatever).  Obviously the more expressive the crontab
equivalent is, the more you can tweak it to do what you want it to.

The default configs are a one-size-fits all approach that tend to do
the right thing if you leave the machine on 24x7, or if you run it at
random times.  If you want to specify exact behavior just edit the
config files and make it do so.

I'll also note that zfs scrubs checkpoint at shutdown and will
auto-resume where you leave off.  If they are involved multiple times
with the default options I think any attempt to scrub something that
is already being scrubbed is just a no-op.  Obviously if you don't
want all that IO during the day you'll have to do something more
clever - you can instruct it to pause and resume so you could have a
couple of crontab entries and scripts to do just that.

-- 
Rich

Re: [gentoo-user] Bug in run-crons?

[Michael Orlitzky]

On Mon, 2021-12-13 at 22:38 +0100, Frank Steinmetzger wrote:
> 
> Well I *could* disable run-crons altogether and add entries to fcron’s own
> crontab which would run those scripts in /etc/cron.{hourly,daily,...}
> instead.
> 
> However, I like predictable times at which those jobs will run. Especially
> if one of them is a zfs scrub; the NAS is powered down for weeks, sometimes
> months. And when I power it up, it’s for a reason. And that reason usually
> is not a scrub, which—at the current zfs fill level—takes 10½ hours.
> 

Why choose fcron then? It sounds like you have the same rationale as I
do: "no, I don't want to run the 4am backup job in the middle of the
business day just because it wasn't run at 4am."

If you pick a dumber cron, the crontab entries are run only at the
specified times.

Re: [gentoo-user] Bug in run-crons?

[Frank Steinmetzger]

Am Mon, Dec 13, 2021 at 04:33:32PM -0500 schrieb Michael Orlitzky:
> On Mon, 2021-12-13 at 22:19 +0100, Frank Steinmetzger wrote:
> > 
> > For the record: The checks in run-crons that I referred to earlier are
> > actually more for those cases in which the machine was powered off for a
> > while in order to restore cron completeness as early as possible after boot.
> > 
> 
> The run-crons quackery has been causing problems since 2004:
> 
>   https://bugs.gentoo.org/69777
> 
> One-liners with run-parts (NOT run-crons) are a lot more predictable.

Well I *could* disable run-crons altogether and add entries to fcron’s own
crontab which would run those scripts in /etc/cron.{hourly,daily,...}
instead.

However, I like predictable times at which those jobs will run. Especially
if one of them is a zfs scrub; the NAS is powered down for weeks, sometimes
months. And when I power it up, it’s for a reason. And that reason usually
is not a scrub, which—at the current zfs fill level—takes 10½ hours.

-- 
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

A preposition is something you should never end a sentence with.


signature.asc
Description: PGP signature

Re: [gentoo-user] Bug in run-crons?

[Michael Orlitzky]

On Mon, 2021-12-13 at 22:19 +0100, Frank Steinmetzger wrote:
> 
> For the record: The checks in run-crons that I referred to earlier are
> actually more for those cases in which the machine was powered off for a
> while in order to restore cron completeness as early as possible after boot.
> 

The run-crons quackery has been causing problems since 2004:

  https://bugs.gentoo.org/69777

One-liners with run-parts (NOT run-crons) are a lot more predictable.

Re: [gentoo-user] Bug in run-crons?

[Frank Steinmetzger]

Am Mon, Dec 13, 2021 at 03:18:44PM -0500 schrieb Rich Freeman:
> On Sun, Dec 12, 2021 at 2:07 PM Frank Steinmetzger  wrote:
> >
> > Am Sun, Dec 12, 2021 at 01:41:33PM -0500 schrieb Rich Freeman:
> > > On Sun, Dec 12, 2021 at 1:21 PM Frank Steinmetzger  wrote:
> > > >
> > >
> > > I don't use this, but I believe there should be an hourly crontab
> > > entry that deletes the cron.hourly file, which would mean it gets run
> > > on the next 10min cycle (or maybe sooner - I'm not sure if those jobs
> > > are run in parallel or serial).
> >
> > The check that I mentioned above is actually the deletion which you mention:
> > run-crons looks for the state file for the given interval and - if it is old
> > enough - deletes it.
> 
> The check I'm talking about isn't in run-crons at all.  It is in
> /etc/crontab.  It doesn't look at the age of the file and
> unconditionally deletes it every hour:
> 59  *  * * *rm -f /var/spool/cron/lastrun/cron.hourly

I had a look at files and docs on the net again. Thus I found exactly those
rm entries in /etc/crontab, which by itself is not used by fcron. But after
I understood all the logic behind it, I added them to fcron to be run
serially before run-crons. Now everything is as I wanted it.

For the record: The checks in run-crons that I referred to earlier are
actually more for those cases in which the machine was powered off for a
while in order to restore cron completeness as early as possible after boot.

-- 
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

“Selfies are electronic masturbation.” — Karl Lagerfeld


signature.asc
Description: PGP signature

Re: [gentoo-user] Bug in run-crons?

[Rich Freeman]

On Sun, Dec 12, 2021 at 2:07 PM Frank Steinmetzger  wrote:
>
> Am Sun, Dec 12, 2021 at 01:41:33PM -0500 schrieb Rich Freeman:
> > On Sun, Dec 12, 2021 at 1:21 PM Frank Steinmetzger  wrote:
> > >
> >
> > I don't use this, but I believe there should be an hourly crontab
> > entry that deletes the cron.hourly file, which would mean it gets run
> > on the next 10min cycle (or maybe sooner - I'm not sure if those jobs
> > are run in parallel or serial).
>
> The check that I mentioned above is actually the deletion which you mention:
> run-crons looks for the state file for the given interval and - if it is old
> enough - deletes it.

The check I'm talking about isn't in run-crons at all.  It is in
/etc/crontab.  It doesn't look at the age of the file and
unconditionally deletes it every hour:
59  *  * * *rm -f /var/spool/cron/lastrun/cron.hourly

-- 
Rich

Re: [gentoo-user] Bug in run-crons?

[Frank Steinmetzger]

Am Sun, Dec 12, 2021 at 01:41:33PM -0500 schrieb Rich Freeman:
> On Sun, Dec 12, 2021 at 1:21 PM Frank Steinmetzger  wrote:
> >
> > It uses state files in /var/spool/cron/lastrun/ to know when each interval
> > was last run, so it only runs once per period. But: the age threshold for
> > the state file is period + 5 minutes. Shouldn’t that be period - 5 minutes?
> >
> > My reasoning: assume run-crons is run hourly, at the 0 minute sharp. So at
> > the next run, the state file is exactly one hour old. Since this is not old
> > enough for the check, run-crons thinks that the last run is too recent and
> > ignores this period. As a result, each period is only run on every other
> > iteration.
> 
> I don't use this, but I believe there should be an hourly crontab
> entry that deletes the cron.hourly file, which would mean it gets run
> on the next 10min cycle (or maybe sooner - I'm not sure if those jobs
> are run in parallel or serial).

The check that I mentioned above is actually the deletion which you mention:
run-crons looks for the state file for the given interval and - if it is old
enough - deletes it.

The part that executes the individual cron scripts is only executed if there
is no state file. The first thing it then does is to create a new state file.


In pseudo code:
1. look for period state file that is older than interval + 5 mins
found one?
delete it

2. Look for period state file
none found?
create state file
execute cron scripts for that interval

-- 
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

The boss is a human just like everyone else, he just doesn’t know.


signature.asc
Description: PGP signature

Re: [gentoo-user] Bug in run-crons?

[Rich Freeman]

On Sun, Dec 12, 2021 at 1:21 PM Frank Steinmetzger  wrote:
>
> It uses state files in /var/spool/cron/lastrun/ to know when each interval
> was last run, so it only runs once per period. But: the age threshold for
> the state file is period + 5 minutes. Shouldn’t that be period - 5 minutes?
>
> My reasoning: assume run-crons is run hourly, at the 0 minute sharp. So at
> the next run, the state file is exactly one hour old. Since this is not old
> enough for the check, run-crons thinks that the last run is too recent and
> ignores this period. As a result, each period is only run on every other
> iteration.

I don't use this, but I believe there should be an hourly crontab
entry that deletes the cron.hourly file, which would mean it gets run
on the next 10min cycle (or maybe sooner - I'm not sure if those jobs
are run in parallel or serial).

The overall result is that things will get run at traditional crontab
times no matter what, but if those are missed and enough time is
accrued then run-crons will catch this and run the job on the next
10min cycle, such as a missed daily overnight slot.

So if you don't have your computer on a 3AM then the job will get run
a bit more than 24h after the last time it was run.  Then if you leave
it on overnight that night it will run at 3AM despite it not being
24h, but at that point if you leave it on it will run at 3AM daily
since it will no longer be missed.  The fixed times serve to anchor
the actual execution times if you do leave the computer on.

-- 
Rich

Re: [gentoo-user] [bug] uClibc-ng-1.0.33 won't fetch

[Michael Orlitzky]

On 5/5/20 9:59 PM, akater wrote:
> Michael Orlitzky  writes:
> 
>> www-client/pybugz
> 
> I have that one installed, actually!  But I'd rather use it through
> Elisp interface... which I'm likely to write if nobody else does but
> it's unlikely to happen in the upcoming months.  And I'm concerned of
> being banned during prototyping.
> 

You should be able to set up a local instance of BugZilla and test
against that. It's normally an ordeal to install, but in this case you
don't need it to live very long, so you can cut some corners.

Re: [gentoo-user] [bug] uClibc-ng-1.0.33 won't fetch

[akater]

Michael Orlitzky  writes:

> www-client/pybugz

I have that one installed, actually!  But I'd rather use it through
Elisp interface... which I'm likely to write if nobody else does but
it's unlikely to happen in the upcoming months.  And I'm concerned of
being banned during prototyping.


signature.asc
Description: PGP signature

Re: [gentoo-user] [bug] uClibc-ng-1.0.33 won't fetch

[Michael Orlitzky]

On 5/5/20 5:43 PM, tastytea wrote:

> 
>> If there's an Emacs-friendly way to post bugs, I'd be glad to know:
>> there are ≈6 bugs and patches waiting in my queue.
> 
> I searched a few weeks ago but couldn't find anything. :-(
> 

www-client/pybugz

Re: [gentoo-user] [bug] uClibc-ng-1.0.33 won't fetch

[tastytea]

On 2020-05-05T15:15+
akater  wrote:

> tastytea  writes:
> 
> > Same here. You should report it to
> > .  
> 
> Thanks for checking.  I'm sorry but the only way I could post to
> bugzilla now is from a web browser—which is very unpleasant on its
> own, and on top of that I only have graphical browser available on a
> handheld device at the moment.  Bugzilla insists that a submitter
> provides emerge --info output for any bug report posted.  With a web
> browser on a handheld device, I can do it but not today.

I've reported it: .

> If there's an Emacs-friendly way to post bugs, I'd be glad to know:
> there are ≈6 bugs and patches waiting in my queue.

I searched a few weeks ago but couldn't find anything. :-(

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpkJDkyZT9zz.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] [bug] uClibc-ng-1.0.33 won't fetch

[akater]

tastytea  writes:

> Same here. You should report it to
> .

Thanks for checking.  I'm sorry but the only way I could post to
bugzilla now is from a web browser—which is very unpleasant on its own,
and on top of that I only have graphical browser available on a handheld
device at the moment.  Bugzilla insists that a submitter provides emerge
--info output for any bug report posted.  With a web browser on a
handheld device, I can do it but not today.

There's a python tool that I plugged in but I'm not comfortable with it
in the absence of a proper interface; I'm unlikely to get to writing the
interface in the upcoming months.

If there's an Emacs-friendly way to post bugs, I'd be glad to know:
there are ≈6 bugs and patches waiting in my queue.


signature.asc
Description: PGP signature

Re: [gentoo-user] [bug] uClibc-ng-1.0.33 won't fetch

[tastytea]

On 2020-05-05T12:03+
akater  wrote:

> I can't fetch sys-libs/uclibc-ng-1.0.33 from distfiles.gentoo.org
> (404), and the file fetched from downloads-uclibc-ng.org has a hash
> different from that in Manifest.  Thus, uclibc-ng-1.0.33 can't be
> installed, and I guess it's a bug.

Same here. You should report it to
.

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpA2KN7NLidS.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] BUG : kernel 4.5.1 and ALSA

[Yuri K. Shatroff]

21.04.2016 11:28, Alexander Kapshuk wrote:

On Thu, Apr 21, 2016 at 10:59 AM, Yuri K. Shatroff  wrote:

Hi gentoo-users,

A few days ago I updated linux kernel to 4.5.1. Yesterday I got a disk space
overflow in my /home partition. Cleaned it up and rebooted, just to run into
the same issue today morning. Investigations revealed that the
`.xsessions-errors` had grown to tremendous 100G full of messages like:

 AL lib: (EE) ALCplaybackAlsa_mixerProc: start failed: File
descriptor in a bad state

It is - *50G per DAY!*

Thinking about a possible cause and bearing in mind I've not updated ALSA
recently rather than the kernel, I went to the kernel's changelog and found
that version 4.5.2 fixes several ALSA-related bugs. I upgraded immediately
and got rid of the error.

So I advise everyone not to install the 4.5.1 kernel and suggest removing it
from portage ASAP. If anyone knows how I could submit such a request, I'm
all ears.

Thanks for your attention!

--
Regards,
Yuri K. Shatroff



That's interesting. That was certainly not my experience running vanilla 4.5.1.
Although I compiled the kernel sources I had previously downloaded
from the kernel.org's git repository.
How did you obtain your kernel sources?


I emerged gentoo-sources==4.5.1.

I believe this is the related commit:

ALSA: hda - Fix regression of monitor_present flag in eld proc file

This can be wrong, but anyway, I listed some facts supporting the 
hypothesis of a problem in the 4.5.1 version.


--
Regards,
Yuri K. Shatroff

Re: [gentoo-user] BUG : kernel 4.5.1 and ALSA

[Alexander Kapshuk]

On Thu, Apr 21, 2016 at 10:59 AM, Yuri K. Shatroff  wrote:
> Hi gentoo-users,
>
> A few days ago I updated linux kernel to 4.5.1. Yesterday I got a disk space
> overflow in my /home partition. Cleaned it up and rebooted, just to run into
> the same issue today morning. Investigations revealed that the
> `.xsessions-errors` had grown to tremendous 100G full of messages like:
>
> AL lib: (EE) ALCplaybackAlsa_mixerProc: start failed: File
> descriptor in a bad state
>
> It is - *50G per DAY!*
>
> Thinking about a possible cause and bearing in mind I've not updated ALSA
> recently rather than the kernel, I went to the kernel's changelog and found
> that version 4.5.2 fixes several ALSA-related bugs. I upgraded immediately
> and got rid of the error.
>
> So I advise everyone not to install the 4.5.1 kernel and suggest removing it
> from portage ASAP. If anyone knows how I could submit such a request, I'm
> all ears.
>
> Thanks for your attention!
>
> --
> Regards,
> Yuri K. Shatroff
>

That's interesting. That was certainly not my experience running vanilla 4.5.1.
Although I compiled the kernel sources I had previously downloaded
from the kernel.org's git repository.
How did you obtain your kernel sources?

Re: [gentoo-user] Bug in spidermonkey? SOLVED!!

[Elias Diem]

Hello there

Just for the record: I was able to solve the problem!!

I created a separate environment file in /etc/portage/env.

The content of this file is:

-8---

CFLAGS=-pipe 
CXXFLAGS=${CFLAGS} 

MAKEOPTS=-j1 

-8---

The CFLAGS normally is -02 -pipe -march=k8  and the job 
count for make is 4.

I guess I can further tune the process now.

-- 
Greetings
Elias

Re: [gentoo-user] Bug in spidermonkey?

[Elias Diem]

Hi there

Well I did reinstall my whole system but without luck. 
Emerging gnome-light showed the very same error when 
compiling spidermonkey.

Then I thought I will install awesome, because it does not 
need spidermonkey. But the same problem here when compiling 
awesome. `Illegal statement' in the build.log.

Next I thought about installing xmonad. And this time it 
worked. So I will use xmonad for the future.

Thanks for your help Nilesh and Walt!

-- 
Greetings
Elias

Re: [gentoo-user] Bug in spidermonkey?

[Elias Diem]

On 2013-02-12,  Elias Diem wrote:

 `Illegal statement' in the build.log.

The above should read `Illegal instruction'.

-- 
Greetings
Elias

Re: [gentoo-user] Bug in spidermonkey?

[Elias Diem]

On 2013-02-07,  Nilesh Govindrajan wrote:

 Seems like one. Try compiling an older version?

Actually I can compile version 1.7.0

But: When I want to update world, it needs (I think) version 
1.8.5-r1

-- 
Greetings
Elias

Re: [gentoo-user] Bug in spidermonkey?

[Nilesh Govindrajan]

On Friday 08 February 2013 07:46:16 PM IST, Elias Diem wrote:
 On 2013-02-07,  Nilesh Govindrajan wrote:

 Seems like one. Try compiling an older version?

 Actually I can compile version 1.7.0

 But: When I want to update world, it needs (I think) version
 1.8.5-r1


Try adding =dev-lang/spidermonkey-1.8.5-r1 in package.mask.
If it works, good, else skip the update of spidermonkey and any 
dependent packages (I believe there are not many applications which 
depend on this).

--
Nilesh Govindarajan
http://nileshgr.com

Re: [gentoo-user] Bug in spidermonkey?

[Nilesh Govindrajan]

On Thu, Feb 7, 2013 at 10:49 PM, Elias Diem pub.li...@webconect.ch wrote:
 Hello all

 I'm encountering a bug when emerging spidermonkey.

 The output from build.log is attached.

 If you need more info, please tell me so.

 Thanks.


Seems like one. Try compiling an older version?

-- 
Nilesh Govindrajan
http://nileshgr.com

Re: [gentoo-user] Bug in spidermonkey?

[Elias Diem]

Hi Nilesh

On 2013-02-07,  Nilesh Govindrajan wrote:

 Seems like one. Try compiling an older version?

I'm about to try. I will report back.

-- 
Greetings
Elias

Re: [gentoo-user] Bug 290437 (gcc-config)

[Florian Philipp]

Am 22.09.2011 12:22, schrieb Jonas de Buhr:
 Hi guys,
 
 i just ran into this bug again:
 
 sys-devel/gcc-config suggests gcc re-merge when profile is invalid
 https://bugs.gentoo.org/show_bug.cgi?id=290437
 
 which is in status RESOLVED FIXED which is clearly not the case. 
 
 who can change the status of a bug?
 
 /jonas
 

Hmm, odd. I thought everyone used to be able to reopen bugs.

Well, it looks like mailto:vap...@gentoo.org (Mike Frysinger) closed the
bug, so you might ask him about it. Or write to
mailto:toolch...@gentoo.org as this herd is currently assigned to the
bug. Vapier and halcy0n seem to be the only ones in that herd.

Hope this helps,
Florian Philipp



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] Bug 290437 (gcc-config)

[Jonas de Buhr]

Hmm, odd. I thought everyone used to be able to reopen bugs.

Ooops. i assumed the opposite because several people complained about
having the same bug after it was closed in the comments but did not
reopen it. But in fact i did not try. Shame on me :)

Well, it looks like mailto:vap...@gentoo.org (Mike Frysinger) closed
the bug, so you might ask him about it. Or write to
mailto:toolch...@gentoo.org as this herd is currently assigned to the
bug. Vapier and halcy0n seem to be the only ones in that herd.

Ok, thanks!

Re: [gentoo-user] BUG: using smp_processor_id() in preemptible [00000000] code: X/4018

[Volker Armin Hemmann]

On Tuesday 01 February 2011 13:02:46 Adam Carter wrote:

 Volker - do you have CONFIG_TREE_PREEMPT_RCU set?

  (X) Tree-based hierarchical RCU

  RCU Implementation (Tree-based hierarchical RCU)  ---

│ │   
  │ │[ ] Enable tracing for RCU 
   
│ │   
  │ │(64) Tree-based hierarchical RCU fanout value  
   
│ │   
  │ │[ ] Disable tree-based hierarchical RCU auto-balancing 
   
│ │   
  │ │[ ] Accelerate last non-dyntick-idle CPU's grace periods   
   
│ │   
  │ │  

Re: [gentoo-user] BUG: using smp_processor_id() in preemptible [00000000] code: X/4018

[Volker Armin Hemmann]

On Sunday 30 January 2011 18:08:50 Mark Knecht wrote:

 None the less it seems like the message suggests that the driver is
 coded incorrectly.

more likely the gentoo-sources patchset is broken.

Re: [gentoo-user] BUG: using smp_processor_id() in preemptible [00000000] code: X/4018

[Volker Armin Hemmann]

On Sunday 30 January 2011 12:40:29 Mark Knecht wrote:
 Hi,
I haven't used the closed source ATI driver for long but I don't
 remember seeing this dmesg error before. It's not high priority for me
 as I'll be switching out the graphics card to an NVidia card hopefully
 tomorrow, but is this something that should get reported somewhere, or
 is it just the nature of the fglrx driver? Or maybe I've not
 configured the kernel as well as it could before this driver?
 
Kernel is 2.6.36-gentoo-r6, ati-drivers-10.11.
 
I did do a modules-rebuild -X rebuild and reboot to ensure it's
 repeatable.
 
I suspect the LKML doesn't want this report as it's a closed source
 driver. Do the XFree guys want it? 

certainly not. You don't use anything from Xfree.

 AMD maybe?
 

certainly. If you can reproduce it with a vanilla kernel.
Because I don't see anything like this with vanilla kernels.

Re: [gentoo-user] BUG: using smp_processor_id() in preemptible [00000000] code: X/4018

[Adam Carter]

I use gentoo-sources and have been getting that for as long as i've used
fglrx (since 9.6, ie driver version 8.62). I don't notice any issue so just
ignore it.

Re: [gentoo-user] BUG: using smp_processor_id() in preemptible [00000000] code: X/4018

[Mark Knecht]

On Sun, Jan 30, 2011 at 2:34 PM, Volker Armin Hemmann
volkerar...@googlemail.com wrote:
 On Sunday 30 January 2011 12:40:29 Mark Knecht wrote:
 Hi,
    I haven't used the closed source ATI driver for long but I don't
 remember seeing this dmesg error before. It's not high priority for me
 as I'll be switching out the graphics card to an NVidia card hopefully
 tomorrow, but is this something that should get reported somewhere, or
 is it just the nature of the fglrx driver? Or maybe I've not
 configured the kernel as well as it could before this driver?

    Kernel is 2.6.36-gentoo-r6, ati-drivers-10.11.

    I did do a modules-rebuild -X rebuild and reboot to ensure it's
 repeatable.

    I suspect the LKML doesn't want this report as it's a closed source
 driver. Do the XFree guys want it?

 certainly not. You don't use anything from Xfree.


My bad. Really I guess I meant X.org

http://xorg.freedesktop.org/wiki/

They supply the server, correct? And everything going to the fglrx
driver comes from the server, somehow, doesn't it?

None the less it seems like the message suggests that the driver is
coded incorrectly.

Please note that I don't actually see any problems. The system
continues to work about as well as it ever has with this card/driver
combination, and there's only a few of these messages in dmesg.

 AMD maybe?


 certainly. If you can reproduce it with a vanilla kernel.
 Because I don't see anything like this with vanilla kernels.


Yeah, probably too much work for the time I have available right now,
and if I remove the HD 5770 in favor of the new NVidia card tomorrow
afternoon then it won't happen until I try the card in some system at
a future date. (Assuming I don't sell it as 'used' and just be done
with ATI for the 4th time...)

Also, there is a 10.12 driver in portage that wasn't available when I
switched to fglrx. I should try that also.

Cheers,
Mark

Thanks,
Mark

Re: [gentoo-user] BUG: using smp_processor_id() in preemptible [00000000] code: X/4018

[Mark Knecht]

On Sun, Jan 30, 2011 at 5:27 PM, Adam Carter adamcart...@gmail.com wrote:
 I use gentoo-sources and have been getting that for as long as i've used
 fglrx (since 9.6, ie driver version 8.62). I don't notice any issue so just
 ignore it.


Thanks Adam! I guess it's been there for the last week (when I gave up
on the Open Source driver) and I probably never looked at dmesg.

Cheers,
Mark

Re: [gentoo-user] Bug about possibly incomplete bugfix

[Alan McKinnon]

On Saturday 10 July 2010 19:21:28 Nuno J. Silva wrote:
 (I asked this on IRC more than an hour ago, got no reply, so here goes
 it to the list.)
 
 What's the policy when you think that a change made due to a FIXED bug
 needs more changes? Should you just comment it, fill another bug or
 change the state (I can't do the later, anyway)?
 
 As an example (the one I am dealing with, bug 283744), I found out a
 package was changed to add a behavior which wasn't documented in the
 ebuild.
 
 On one hand, the suggestion to add elog messages should belong to the
 original bug (now RESOLVED FIXED).
 
 But on the other hand this is a new problem introduced by the fix for
 that first bug, and then should have its own request.
 
 (And, as I can't change the first bug - which is FIXED, a separate bug
 would be initially marked as OPEN, which suits the case of a new, IMHO
 still unsolved issue.)
 
 But what's the most polite thing to do?


Open a new bug and refer to the old one. Let the bug owner decide what's the 
best thing to do next.



-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Bug

[KH]

Am 19.04.2010 00:41, schrieb dan blum:

Dale,

Thanks for following up. HOw do you start a new thread?

It is slightly annoying when you change a setting and reverts back to the original; the 
whole (computer) system should be more user friendly. Either way, it is good that there 
is an easy fix, which I will do.

I will have much more complex issues to discuss shortly.

Thanks.


[...]

Hi,

well there might be more than one way but usually I move my mouse to the 
new email option in thunderbird. Then I write 
gentoo-user@lists.gentoo.org in the field to. So I am set.
The difference is: when you use answer and just change the subject 
field, it still is shown as answer to the other email. If you ever tried 
to find something with google from a mailing list you pretty fast start 
to hat those guys.


Also keep in mind, that the subject field should be a little more 
catchy. Things like help, bug, to all veterans ... will likely 
lead to very few readers.


Also most people on this list (I hope this won't start a discussion 
again) don't like top posting.


Regards

kh

Re: [gentoo-user] Bug

[dan blum]

Dale,

Your fix worked, so far so good. Previously, I tried setting the time from KDE 
and using the date function and both were overridden on re-boot. One would 
think that either one of these functions would override the factory presets. 

I see 'date' is a binary file. Does kde also use this function to change its 
time and date? Where would one find the source package for 'date'?

Dan 

--- On Wed, 4/14/10, Dale rdalek1...@gmail.com wrote:

 From: Dale rdalek1...@gmail.com
 Subject: Re: [gentoo-user] Bug
 To: gentoo-user@lists.gentoo.org
 Date: Wednesday, April 14, 2010, 12:12 PM
 dan blum wrote:
  I run KDE on my system and my clock is wrong. I
 corrected several times from KDE, which sets the time to
 next boot, when it reverts to the old setting. This looks
 like slight bug.
     
 
 Since mailing list users generally use threaded messages,
 please start a new message instead of replying to a old
 one.
 
 This may not be a bug.  It depends on how you set your
 clock.  You need to check the settings in
 /etc/conf.d/clock and make sure you have it set up
 correctly.  Also, if you are dual booting with windoze,
 that makes you have to have additional settings from what I
 have read in the past.  Windoze sets the BIOS clock
 differently than Linux.  I don't have windoze so
 someone else will have to help with that.
 
 Dale
 
 :-)  :-)
 
 

Re: [gentoo-user] Bug

[Paul Hartman]

On Mon, Apr 19, 2010 at 12:14 PM, dan blum dan_...@yahoo.com wrote:
 I see 'date' is a binary file. Does kde also use this function to change its 
 time and date? Where would one find the source package for 'date'?

$ equery b `which date`
 * Searching for /usr/bin/date ...
sys-apps/coreutils-8.4 (/bin/date)

(if you don't have equery, it is in gentoolkit)

Re: [gentoo-user] Bug

[Dale]

dan blum wrote:

Dale,

Your fix worked, so far so good. Previously, I tried setting the time from KDE 
and using the date function and both were overridden on re-boot. One would 
think that either one of these functions would override the factory presets.

I see 'date' is a binary file. Does kde also use this function to change its 
time and date? Where would one find the source package for 'date'?

Dan

--- On Wed, 4/14/10, Dalerdalek1...@gmail.com  wrote:

   

From: Dalerdalek1...@gmail.com
Subject: Re: [gentoo-user] Bug
To: gentoo-user@lists.gentoo.org
Date: Wednesday, April 14, 2010, 12:12 PM
dan blum wrote:
 

I run KDE on my system and my clock is wrong. I
   

corrected several times from KDE, which sets the time to
next boot, when it reverts to the old setting. This looks
like slight bug.
 


   

Since mailing list users generally use threaded messages,
please start a new message instead of replying to a old
one.

This may not be a bug.  It depends on how you set your
clock.  You need to check the settings in
/etc/conf.d/clock and make sure you have it set up
correctly.  Also, if you are dual booting with windoze,
that makes you have to have additional settings from what I
have read in the past.  Windoze sets the BIOS clock
differently than Linux.  I don't have windoze so
someone else will have to help with that.

Dale

:-)  :-)
 


The date command has nothing to do with KDE.  The date command is part 
of this package:


r...@smoker ~ # equery belongs date
 * Searching for date ...
sys-apps/coreutils-8.4 (/bin/date)
r...@smoker ~ #

That is a system package.  KDE gets the time info from the system 
itself.  Keep in mind, Linux is a command line OS.  You are able to put 
a GUI such as KDE, Gnome etc etc, on top of that system.  Unlike 
Windoze, you can have a system with absolutely no monitor at all.  Heck, 
most servers run that way.  They have no monitor, no keyboard, no mouse 
or anything of the sort.  Most windoze boxes need that and have a GUI 
even if you don't use the monitor.  Gentoo usually teaches a person 
that.  The first time you boot up, if you follow the handbook, you get a 
command line and nothing else.  I usually cheat a little bit and can get 
a GUI tho.  ;-)


Linux has a factory preset but you have to tell it what time zone you 
are in.  Same with any OS I guess.  After all, you can have a OS 
anywhere in the world.  The computer has no idea where the heck it is 
until someone tells it.


Glad you got that one sorted tho.

Dale

:-)  :-)

Re: [gentoo-user] Bug

[dan blum]

Dale,

Thanks for following up. HOw do you start a new thread? 

It is slightly annoying when you change a setting and reverts back to the 
original; the whole (computer) system should be more user friendly. Either way, 
it is good that there is an easy fix, which I will do.

I will have much more complex issues to discuss shortly.

Thanks.

--- On Wed, 4/14/10, Dale rdalek1...@gmail.com wrote:

 From: Dale rdalek1...@gmail.com
 Subject: Re: [gentoo-user] Bug
 To: gentoo-user@lists.gentoo.org
 Date: Wednesday, April 14, 2010, 12:12 PM
 dan blum wrote:
  I run KDE on my system and my clock is wrong. I
 corrected several times from KDE, which sets the time to
 next boot, when it reverts to the old setting. This looks
 like slight bug.
     
 
 Since mailing list users generally use threaded messages,
 please start a new message instead of replying to a old
 one.
 
 This may not be a bug.  It depends on how you set your
 clock.  You need to check the settings in
 /etc/conf.d/clock and make sure you have it set up
 correctly.  Also, if you are dual booting with windoze,
 that makes you have to have additional settings from what I
 have read in the past.  Windoze sets the BIOS clock
 differently than Linux.  I don't have windoze so
 someone else will have to help with that.
 
 Dale
 
 :-)  :-)
 
 

Re: [gentoo-user] Bug

[Dale]

dan blum wrote:

Dale,

Thanks for following up. HOw do you start a new thread?

It is slightly annoying when you change a setting and reverts back to the original; the 
whole (computer) system should be more user friendly. Either way, it is good that there 
is an easy fix, which I will do.

I will have much more complex issues to discuss shortly.

Thanks.
   


You started a new thread with this one.  ;-)  It really depends on your 
email program.  Mine, I can just chose to compose a new message and type 
in the email address.  I can also right click on the email address, 
usually from another message, and then select 'Compose New Mail' to and 
it starts a shiney new thread.  Tell us what you are using and I'm sure 
someone here uses it and can tell you more specifics on how to start a 
new thread.


Questions about your setup.  Do you dual boot windows?   Do you dual 
boot another OS, even Linux?  Is Linux the only OS you have installed?  
I only have one OS that I boot here so my settings will be different 
from yours if you dual boot something else.  We need more info first 
tho.  Also, can you give a little info about how the clock is set in 
your BIOS?  This is really needed if you are dual booting.


Dale

:-)  :-)

Re: [gentoo-user] Bug

[Paul Hartman]

On Wed, Apr 14, 2010 at 10:46 AM, dan blum dan_...@yahoo.com wrote:
 I run KDE on my system and my clock is wrong. I corrected several times from 
 KDE, which sets the time to next boot, when it reverts to the old setting. 
 This looks like slight bug.

Check this option in your file /etc/conf.d/hwclock

# If you want to set the Hardware Clock to the current System Time
# (software clock) during shutdown, then say YES here.
# You normally don't need to do this if you run a ntp daemon.
clock_systohc=YES

Re: [gentoo-user] Bug

[Dale]

dan blum wrote:

I run KDE on my system and my clock is wrong. I corrected several times from 
KDE, which sets the time to next boot, when it reverts to the old setting. This 
looks like slight bug.
   


Since mailing list users generally use threaded messages, please start a 
new message instead of replying to a old one.


This may not be a bug.  It depends on how you set your clock.  You need 
to check the settings in /etc/conf.d/clock and make sure you have it set 
up correctly.  Also, if you are dual booting with windoze, that makes 
you have to have additional settings from what I have read in the past.  
Windoze sets the BIOS clock differently than Linux.  I don't have 
windoze so someone else will have to help with that.


Dale

:-)  :-)

Re: [gentoo-user] Bug 246672 ATI-DRIVERS

[Volker Armin Hemmann]

On Mittwoch 26 November 2008, James wrote:
 I've got an ati/amd64 system that no matter what combo
 of xorg-server, xorg-x11 and ati-drivers, I cannot get
 it to work.

 lspci shows:
 00:00.0 Host bridge: ATI Technologies Inc
 RD580 [CrossFire Xpress 3200]
 Chipset
 Host Bridge
 00:02.0 PCI bridge: ATI Technologies Inc RS480 PCI-X Root Port
 00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge

 01:00.0 VGA compatible controller: ATI Technologies Inc
 R580 [Radeon X1900 XT](Primary)
 01:00.1 Display controller: ATI Technologies Inc
 R580 [Radeon X1900 XT] (Secondary)


 It all worked fine until an update a few days ago.

 I do not need the latest version of anything just something that works.


 Any suggestions are most appreciated

 Currently the system is booted and kde is working but I removed
 ati-drivers trying to fix it. Now I cannot get any version of
 ati-drivers to work, despite trying the latest ideas in bug 246672.


 Any help is appreciated. Precise version numbers of xorg-server
 xorg-x11 and ati-drivers is what I really need. Just advise
 on a combo that works with a r580 chipset.


 James

 x11-base/xorg-server
 Installed versions:  1.5.2

media-libs/mesa
Installed versions:  7.2

x11-base/xorg-x11
Installed versions:  7.4

x11-drivers/ati-drivers
Installed versions:  8.552-r2

Re: [gentoo-user] Bug 246672 ATI-DRIVERS

[Volker Armin Hemmann]

On Dienstag 25 November 2008, James wrote:
 Hello,

 One of my (ati) systems has been screwed up a few days now because of
 bug 246672.

 Long story short, I have no ati-drivers installed and when I try to
 emerge it, I get:

 Cannot write to '/usr/lib32/opengl/ati/extensions'
 Please check permissions and directories for broken symlinks

go to /usr/lib32/opengl/ati/ and remoce extensions dir or symlink or whatever 
it is. Retry.

Re: [gentoo-user] Bug 246672 ATI-DRIVERS

[Rodolphe Rocca]

James wrote:
 Hello,
 
 One of my (ati) systems has been screwed up a few days now because of
 bug 246672.
 
 Long story short, I have no ati-drivers installed and when I try to
 emerge it, I get:
 
 Cannot write to '/usr/lib32/opengl/ati/extensions'
 Please check permissions and directories for broken symlinks
 
 
 Obviously, I've tried all sorts of things but 
 ati-drivers-8.552-r2 just won't compile.
 
 

You must first unmerge ati-drivers : it will properly delete files and
this directory too. Then emerge ati-drivers.

Re: [gentoo-user] Bug in /etc/init.d/netmount?

[Matthias Fechner]

Hi Dan,

Dan Farrell wrote:
 AFAIK you are correct, this is a bug in a few of the initscripts that
 don't behave sensibly if the root fs is network mounted.  

thx for your answer a raised a bug report with the number: 194967.


Bye
Matthias

-- 

Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning. --
Rich Cook
-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Bug in /etc/init.d/netmount?

[Dan Farrell]

On Fri, 5 Oct 2007 14:33:02 +0200
Matthias Fechner [EMAIL PROTECTED] wrote:

 Hi,
 
 I have here a gentoo diskless system which boots over pxeboot and
 mount everything over NFS from my big Gentoo server.
 
 But at shutdown I get the error message:
 Failed to simply unmount filesystems
   Unmounting network filesystems (retry #1) ...
 INIT: no more processes left in this runlevel
 
 After some investigation I found a work-around.
 I deleted the line
 [[ -z $(umount -art ${rcfilesystems} 21) ]]
 in /etc/init.d/netmount (function stop() )
 
 I think the problem here is that netmount unmounts all partitions
 (including /) and so the shutdown process cannot be continued.
 
 Should not netmount skip unmounting / ?
 
 Best regards,
 Matthias
 

AFAIK you are correct, this is a bug in a few of the initscripts that
don't behave sensibly if the root fs is network mounted.  

Another one that gets messed up is IPTAbles.  I didn't think much of it
because I figured I was the only person in the world crazy enough to
have a diskless router/firewall.  

Interestingly, some of my diskless hosts do all right with this, others
fail to shut down.  

-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Bug in bash ?

[Jan Seeger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This is no bug. Bash globs everything that begins with A-Z (also
directories) and then gives that list to ls. So ls lists all these files
and the directories that begin with A-Z. Strangely though, bash seems to
ignore case. (When I try your command, ls gives me all the files that
begin with a letter and excludes files that begin with a number) 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGKc7ZMmLQdC6jvocRAjoiAJ9guN8zoA5A2ZxQIZxEeyGxdb9TggCdFbgb
c0NkXZqd15DLXNNsd1liS5Y=
=m/kr
-END PGP SIGNATURE-
-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Bug in bash ?

[Renat Golubchyk]

On Sat, 21 Apr 2007 10:44:09 +0200 Jan Seeger [EMAIL PROTECTED]
wrote:
 This is no bug. Bash globs everything that begins with A-Z (also
 directories) and then gives that list to ls. So ls lists all these
 files and the directories that begin with A-Z. Strangely though, bash
 seems to ignore case. (When I try your command, ls gives me all the
 files that begin with a letter and excludes files that begin with a
 number)

That happens because of your locale setting. If LC_COLLATE is not C
or POSIX then e.g. [A-D] can be equal to [AbBcCdD] or [AaBbCcD]. So
set LC_COLLATE to C and you'll get a portable behaviour.

Cheers,
Renat

-- 
Probleme kann man niemals mit derselben Denkweise loesen,
durch die sie entstanden sind.
  (Einstein)


signature.asc
Description: PGP signature

Re: [gentoo-user] Bug in bash ?

[Bo Ørsted Andresen]

On Saturday 21 April 2007 09:52:40 [EMAIL PROTECTED] wrote:
 Can somebody explain why
 ls [A-Z]*
 works as ls * (or ls -R):
 It seems that [A-Z] is ignored by bash-3.1.17 on amd64.
 The expression works as expected with zsh...

Try `ls [[:upper:]]*`. Also -R is recursive. You should google that since you 
don't seem to know what it means..

-- 
Bo Andresen


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

Re: [gentoo-user] bug in usermod, full name of options doesn't work

[Benno Schulenberg]

Allan Gottlieb wrote:
 Goal: add gottlieb to group scanner.

 It seems that -aG works but --append --groups doesn't

Please try attached patch.

I'll report this bug upstream, mentioning that you found it.

Benno
diff -ur cvs-shadow/src/usermod.c shadow/src/usermod.c
--- cvs-shadow/src/usermod.c	2006-11-14 16:40:54.0 +0100
+++ shadow/src/usermod.c	2007-01-13 14:59:02.0 +0100
@@ -905,7 +905,7 @@
 		 */
 		int c;
 		static struct option long_options[] = {
-			{append, required_argument, NULL, 'a'},
+			{append, no_argument, NULL, 'a'},
 			{comment, required_argument, NULL, 'c'},
 			{home, required_argument, NULL, 'd'},
 			{expiredate, required_argument, NULL, 'e'},

Re: [gentoo-user] bug in usermod, full name of options doesn't work

[Allan Gottlieb]

At Sat, 13 Jan 2007 15:13:18 +0100 Benno Schulenberg [EMAIL PROTECTED] wrote:

 Allan Gottlieb wrote:
 Goal: add gottlieb to group scanner.

 It seems that -aG works but --append --groups doesn't

 Please try attached patch.
 I'll report this bug upstream, mentioning that you found it.

Thanks,
allan
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] bug in usermod, full name of options doesn't work

[Bo Ørsted Andresen]

On Friday 12 January 2007 18:46, Allan Gottlieb wrote:
 Goal: add gottlieb to group scanner.

 It seems that -aG works but --append --groups doesn't

 I will file a bug in b.g.o. unless I did something wrong.

I wouldn't be surprised if it would be RESOLVED UPSTREAM. Guess there's only 
one way to find out.. I guess you could comment on bug #145416 too (which 
isn't quite the same issue)..

-- 
Bo Andresen


pgpeyQiRqQ2UP.pgp
Description: PGP signature

Re: [gentoo-user] BUG 2.6.17-gentoo-r8 does not compile

[Jean-Marc Beaune]

Hi,

I don't know if it's relevant but as the installation guide says, I do 'make  make modules_install'.
Otherwise you could try to use genkernel, just to see if kernel sources are corrupted.
On 9/13/06, Helmut Jarausch [EMAIL PROTECTED] wrote:
Hi,gentoo doesn't seem to like me.Trying to install gentoo, I didUSE=-doc symlink emerge gentoo-sources
After menuconfigmaketerminates due to a shell syntax error.Are the gentoo kernel patches buggy?Many thanks for hint,Helmut JarauschLehrstuhl fuer Numerische MathematikRWTH - Aachen University
D 52056 Aachen, Germany--gentoo-user@gentoo.org mailing list-- /JM 

Re: [gentoo-user] BUG 2.6.17-gentoo-r8 does not compile

[Iain Buchanan]

 After menuconfig
 make
 terminates due to a shell syntax error.
 Are the gentoo kernel patches buggy?
 
 Many thanks for hint,

hint:  posting an exact copy of the output from your terminal would
probably get you more help ;)

-- 
Iain Buchanan iaindb at netspace dot net dot au

Does the name Pavlov ring a bell?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] BUG 2.6.17-gentoo-r8 does not compile

[Neil Bothwick]

On Wed, 13 Sep 2006 13:04:40 +0200 (CEST), Helmut Jarausch wrote:

 After menuconfig
 make
 terminates due to a shell syntax error.
 Are the gentoo kernel patches buggy?

Who knows? Maybe if the error message wasn't considered Top Secret,
someone would be able to shed some light on the cause.

I've compiled and am running -r8 on x64, amd64 and PPC systems with no
such messages, secret or otherwise.


-- 
Neil Bothwick

Don't let your mind wander, it's too little to be let out alone.


signature.asc
Description: PGP signature

Re: [gentoo-user] Bug report.

[Paul Varner]

On Tue, 2005-12-20 at 15:22 -0300, Allan Spagnol Comar wrote:
 Where Do I do a bug report
 
 I received this a moment ago when I run emerge --sync.
  Updating Portage cache:   88%!!! Cannot resolve a virtual package
 name to an ebuild.
 !!! This is a bug, please report it. (virtual/x11-6.8)
 
 don´t know where to post it

Bug reports go to http://bugs.gentoo.org

This, however, is a known bug - http://bugs.gentoo.org/show_bug.cgi?id=114798

The problem is that you have an older portage that needs to be updated.

#emerge --av portage
#emerge --sync

Regards,
Paul

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Bug report.

[Paul Varner]

On Tue, 2005-12-20 at 15:22 -0300, Allan Spagnol Comar wrote:
 Where Do I do a bug report
 
 I received this a moment ago when I run emerge --sync.
  Updating Portage cache:   88%!!! Cannot resolve a virtual package
 name to an ebuild.
 !!! This is a bug, please report it. (virtual/x11-6.8)

I have a typo in my previous response.  The commands to update should
be:

# emerge -av portage
# emerge --sync

Regards,
Paul
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Bug report.

[Dale]

Allan Spagnol Comar wrote:


Where Do I do a bug report

I received this a moment ago when I run emerge --sync.
 


Updating Portage cache:   88%!!! Cannot resolve a virtual package
   


name to an ebuild.
!!! This is a bug, please report it. (virtual/x11-6.8)

don´t know where to post it
--
An application asked:
Requeires Windows 9x, NT4 or better,
so I´ve installed Linux

 




http://bugs.gentoo.org/



That should be a good place.

Dale
:-)


--
To err is human, I'm most certainly human.

I have four rigs:

1:  Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two 
80GB hard drives.
2:  Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive.
3:  Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB 
drive.
4:  Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB 
SCSI drive.

All run Gentoo Linux, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers.  


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Bug report.

[Allan Spagnol Comar]

thanks All

On 12/20/05, Dale [EMAIL PROTECTED] wrote:
 Allan Spagnol Comar wrote:

 Where Do I do a bug report
 
 I received this a moment ago when I run emerge --sync.
 
 
 Updating Portage cache:   88%!!! Cannot resolve a virtual package
 
 
 name to an ebuild.
 !!! This is a bug, please report it. (virtual/x11-6.8)
 
 don´t know where to post it
 --
 An application asked:
 Requeires Windows 9x, NT4 or better,
 so I´ve installed Linux
 
 
 

  http://bugs.gentoo.org/


 That should be a good place.

 Dale
 :-)


 --
 To err is human, I'm most certainly human.

 I have four rigs:

 1:  Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now 
 two 80GB hard drives.
 2:  Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive.
 3:  Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB 
 drive.
 4:  Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 
 4.3GB SCSI drive.

 All run Gentoo Linux, all run folding. #1 is my desktop, 2, 3, and 4 are set 
 up as servers.

 --
 gentoo-user@gentoo.org mailing list




--
An application asked:
Requeires Windows 9x, NT4 or better,
so I´ve installed Linux

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Bug in net.eth0?

[Neil Bothwick]

On Thu, 17 Nov 2005 15:01:29 -0800, Hareesh Nagarajan wrote:

 Version: # $Header:
 /home/cvsroot/gentoo-src/rc-scripts/init.d/net.eth0,v 1.41 2004/05/10
 14:16:35 agriffis Exp $

This looks like a very old script. /etc/init.d/net.eth0 should now be a
symlink to net.lo.


-- 
Neil Bothwick

Press any key to continue... click Except that one..


signature.asc
Description: PGP signature

Re: [gentoo-user] BUG in glibc????

[Billy Holmes]

capsel wrote:

j=strcmp( log, *(lines+i) );
printf( ble\n );
if( strcmp( log, *(lines+i) ) == 0 )
{
printf( ble2\n );


it looks to me like you're probably getting an invalid pointer 
reference. When that happens, your program is undefined. More then 
likely, you're going out of bounds on your array, try adding some debug 
code, or looking at it in gdb. You'll want to keep an eye on i.

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] BUG in glibc????

[John Myers]

On Sunday 30 October 2005 13:54, capsel wrote:
 is it a bug in glibc or in my code?
Probably not a bug in glibc. I'm 99% sure that there are no bugs that obvious 
in printf or strcmp. glibc is absolutely the most tested code in a GNU/Linux 
system, aside from the kernel itself, seeing as it is used by the *vast* 
majority of users, for every app on their system. And printf is probably one 
of the most-used and abused functions in glibc.

so, the answer to 'did I find a bug in printf?' is almost invariably 'Most 
likely not.'


pgpXvXZtUYBl9.pgp
Description: PGP signature

Re: [gentoo-user] BUG in glibc???? [WAY OT]

[Richard Fish]

capsel wrote:


Hi all,

is it a bug in glibc or in my code?
 



This is so far off topic, it isn't even funny.  But, I see a couple bugs 
in your code.  I will cover them inline:



if( ( config_content == NULL ) || ( config_content==0 ) )
 



Not really a bug here, but since NULL and 0 are the same value, you only 
need one side of the comparison.



*(lines) = config_content;
for( i = 0; i  config_contentl; i++ )
{
if( *(config_content+i) == '\n' )
{
lines = (char**) realloc( lines, sizeof( char** 
)*(linesc+1) );
if( lines == NULL )
{
fprintf( logi, = B³±d alokacji\n );
return 0;
}
linesc++;
*(lines+linesc) = (config_content+i+1);
*(config_content+i) = '\0';
printf( - linesc++\n );
}
}
 



There is a possible off-by-one error for linesc if config_content does 
not end with a newline.  For example, consider a config file with a 
single line that does not end with a newline.  In that case, linesc will 
be 0 in your code, and you will not process anything.


I suggest setting linesc = 1 before the loop, and then adjust the 
internals appropriately.



fprintf( stdout, - linesc = %u\n, linesc );
for( i = 0; i  linesc; i++ )
{
if( *(*(lines+i)) == '#' )
{
continue;
}
 



Again, not a bug, but a readability recommendation.  Use a temporary 
variable inside your loop for the current line:


char* line = lines[i];

Then replace all *(lines+i) with line.


if( strcmp( log, *(lines+i) ) == 0 )
{
config_configpathl = strlen( eqch+1 );
config_configpath = (char*) malloc( config_configpathl 
);
if( config_configpath == NULL )
{
fprintf( logi, = B³±d alokacji pamiêci na nazwe 
pliku loga dla linii %i\n,i );
free( lines );
return 0;
}
strcpy( config_configpath, eqch+1 );
fprintf( stdout, - log = `%s'\n, eqch+1 );
continue;
}
 



This is your major bug, a memory overflow.  You are only allocated 
enough memory for the characters of the string, not including the 
terminating null character.  Strcpy copies the characters of the string, 
_plus_ the terminating null, which is where you get a memory overflow.


Get rid of config_configpathl and the strlen line, and replace the 
malloc and strcpy with strdup().


-Richard

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Bug, or PEBKAC?

[Billy Holmes]

are you using distcc or ccache?
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Bug, or PEBKAC?

[Billy Holmes]

FEATURES=autoconfig ccache distlocks fixpackages sandbox sfperms strict
userpriv usersandbox


I would try getting rid of ccache, first.. and if you have distcc 
installed (portage still could be using it if you updated your profile 
and path).

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Bug, or PEBKAC?

[Richard Fish]

Holly Bostick wrote:


Hey,

I've been trying to run an emerge -uaDtv world for the past couple of
days, and dev-libs/liboil fails to upgrade from 0.3.2 to 0.3.3 with the
following error:

conv_sse.c: In function `conv_f32_s32_sse':
conv_sse.c:44: error: `__m128' undeclared (first use in this function)
 


snip


CFLAGS=-O2 -march=athlon-xp -mfpmath=sse -mmmx -msse -mno-sse2
-mno-sse3 -m3dnow -fomit-frame-pointer -pipe
 



snip


USE=x86 16bit 3dnow X aalib acpi alsa audiofile avi bash-completion
bigger-fonts bitmap-fonts bonobo caps cddb cdr crypt cups curl dbus dga
directfb divx4linux dv dvd emboss encode esd fbcon firefox flac
font-server foomaticdb fortran gd gdbm ggi gif gimpprint glut gnome gpm
gstreamer gtk gtk2 gtkhtml guile hal iconv imagemagick imlib inkjar jack
java jikes jpeg kdeenablefinal kdexdeltas lcms ldap libcaca libg++
libwww mad maildir mikmod mmx mng motif mozilla mp3 mpeg mpi nas ncurses
nfs nls nptl offensive ogg oggvorbis openexr opengl oss pdflib perl pic
png portaudio povray python qt quicktime readline samba sdl slang
sndfile socks5 speex spell sse ssl svg svga symlink tcltk tcpd tetex
threads tiff toolbar truetype truetype-fonts type1-fonts unicode v4l
vorbis wmf xine xml xml2 xmms xprint xv xvid yv12 zlib linguas_nl
userland_GNU kernel_linux elibc_glibc
 



Try:

CFLAGS=-O2 -march athlon-xp -pipe emerge -v dev-libs/liboil

If it works, you can then try adding the CFLAGS back in one-by-one.

My advice though is generally to remove all the mmx, sse, and 3dnow 
options from CFLAGS.  Compiling _everything_ with these settings is 
asking for trouble.  IMO it is better to just enable all the 
mmx/sse/3dnow USE flags to let them be enabled for those packages where 
they are known to work.


-Richard

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] BUG? - bridge-utils no binary?

[Rumen Yotov]

Hi,
...SKIP...


 Ognjen Bezanov wrote:

 Hello

 I am building a linux AP using a clean installation of gentoo and this
 howto:

 http://gentoo-wiki.com/HOWTO_Building_a_Wireless_Access_Point_With_Gentoo


 Everything was going great until I came to emerging bridge-utils.

 the actual emerging didnt fail (using emerge bridge-utils -av) but
 typing the command brctl it tells me '-bash: brctl: command not found'

 next I try whereis brctl, resulting in:

 brctl: /usr/man/man8/brctl.8.gz /usr/share/man/man8/brctl.8.gz

 ok, so the man files are there, it seems the package was installed. but
 no binary.

 Using find / -name brctl  i also got nothing.

 It seems that there is no binary, I have tried emerging again,
 unmerging, updating and the like, still the same problem.  The emerge
 itself doesnt fail with the usual Error... so I presume thats fine (or
 am i wrong that
 emerge would halt on all errors?)

 Any help appreciated as I am somewhat at a loss as to whats going on.

 thanks



It's in /sbin/brctl. Could use 'qfile brctl' to get the package (part
of portage-utils).
Or use which brctl as root to get: /sbin/brctl
HTH. Rumen



smime.p7s
Description: S/MIME Cryptographic Signature