1 |
On Sun, Aug 24, 2014 at 1:03 PM, Randy Barlow |
2 |
<randy@×××××××××××××××××.com> wrote: |
3 |
> On 08/14/2014 10:00 AM, Randy Barlow wrote: |
4 |
>> I believe this issue is a kernel bug, which I was quite surprised to |
5 |
>> learn. I filed a bug about it here if anyone is interested: |
6 |
>> |
7 |
>> https://bugs.gentoo.org/show_bug.cgi?id=519666 |
8 |
> |
9 |
> I am now not so sure that this is a kernel bug. The reason I thought |
10 |
> that was that booting to kernel 3.12 would resolve the issue, while |
11 |
> running 3.14 would exhibit the issue. I've since tried 3.16, and the |
12 |
> issue remains there. It seems unlikely that a bug this severe would be |
13 |
> present across three kernel releases. |
14 |
> |
15 |
> Could it be that Cyrus just isn't compatible with kernel 3.14 and 3.16? |
16 |
> Is anybody successfully using Cyrus with 3.14 or 3.16? |
17 |
> |
18 |
> -- |
19 |
> R |
20 |
> |
21 |
|
22 |
I somehow doubt it's that the application isn't compatible with a |
23 |
newer kernel. If that was the case tell Linus/LKML about it because |
24 |
they do a lot to ensure that doesn't happen without really good |
25 |
reasons. However don't go that direction until the Cyrus people tell |
26 |
you it's the case. |
27 |
|
28 |
What follows is just opinion and not something you'd want to depend on... |
29 |
|
30 |
One possibility is there could be a software API issue down deep |
31 |
somewhere not being caught by emerge. I'd personally look at |
32 |
rebuilding the app and _all_ of it's libraries, checking app config |
33 |
files, etc.. That's usually fixed problems like this for me. |
34 |
|
35 |
In the couple of cases where I've had this sort of problem happen over |
36 |
the years (just a couple) I sort of hate to say my go-to solution is |
37 |
to just do an emerge -e @world about once a year. I'll check |
38 |
gcc-config, rebuild gcc, then rebuild the whole machine. When all else |
39 |
fails that's has fixed this sort of problem for me a couple of times. |
40 |
|
41 |
I'll also say that if it's really a kernel issue then consider |
42 |
bringing up a new kernel with a completely from scratch kernel config |
43 |
file. I've seen reports over the years where make oldconfig might have |
44 |
caused a problem with a newer kernel. |
45 |
|
46 |
I know some folks will say is was a waste of time, but I've got time |
47 |
for a rebuild (over night on a home server, etc.) but no patience for |
48 |
apps failing during the day when I'm trying to work. |
49 |
|
50 |
Best of luck, |
51 |
Mark |