| 1 |
john <jdm@××××××××××××.uk> wrote: |
| 2 |
|
| 3 |
>On Mon, 19 Nov 2012 22:57:49 +0100 |
| 4 |
>"J. Roeleveld" <joost@××××××××.org> wrote: |
| 5 |
> |
| 6 |
>> john <jdm@××××××××××××.uk> wrote: |
| 7 |
>> |
| 8 |
>> >On Mon, 19 Nov 2012 20:15:24 +0000 |
| 9 |
>> >john <jdm@××××××××××××.uk> wrote: |
| 10 |
>> > |
| 11 |
>> >> Hi Gentoo. |
| 12 |
>> >> |
| 13 |
>> >> I have recently got a FX8350 and all is going very well. |
| 14 |
>> >> After a week of using I have had no issues and then realised I had |
| 15 |
>> >not |
| 16 |
>> >> set man number of cpus in kernel config. |
| 17 |
>> >> |
| 18 |
>> >> This was set to 6. So as FX8350 is an eight core beast. I decided |
| 19 |
>> >> to set to 8. |
| 20 |
>> >> |
| 21 |
>> >> Upon reboot the boot hangs at |
| 22 |
>> >> |
| 23 |
>> >> waiting for uevents to be processed. |
| 24 |
>> >> |
| 25 |
>> >> This hangs for 60 seconds and then starts spitting out the |
| 26 |
>> >> following |
| 27 |
>> >> |
| 28 |
>> >> timeout killing /sbin/modprobe -bv xcpu_vendor 0002 + lots of 4 |
| 29 |
>> >> long numbers. Sorry, I cannot trap these as they fly by. |
| 30 |
>> >> |
| 31 |
>> >> in a continous loop. |
| 32 |
>> >> |
| 33 |
>> >> Reset required. |
| 34 |
>> >> |
| 35 |
>> >> Booting from old kernel is still ok (6 cores set). |
| 36 |
>> >> |
| 37 |
>> >> Looking in /proc/cpuinfo there are only 6 cores. |
| 38 |
>> >> |
| 39 |
>> >> I can boot ok from Windows which shows 8 cores and I have also |
| 40 |
>> >updated |
| 41 |
>> >> BIOS to latest version. |
| 42 |
>> >> |
| 43 |
>> >> Any ideas |
| 44 |
>> >> |
| 45 |
>> >> Is there any way to detect or test that I using 8 cores? |
| 46 |
>> >> |
| 47 |
>> > |
| 48 |
>> >Have tried booting from Arch linux which boots fine and shows 8 |
| 49 |
>cores |
| 50 |
>> >in /proc/cpuinfo |
| 51 |
>> > |
| 52 |
>> >I must be missing a kernel config option somewhere but do not |
| 53 |
>> >understand why a simple change from 6 to 8 cpus should make a |
| 54 |
>> >difference. |
| 55 |
>> |
| 56 |
>> John. |
| 57 |
>> |
| 58 |
>> Have you tried comparing the kernel config between your kernel and |
| 59 |
>> the one arch linux uses? |
| 60 |
>> |
| 61 |
>> -- |
| 62 |
>> Joost |
| 63 |
> |
| 64 |
>Tried the 3.6.6 kernel which sorts this problem (same as Arch). Perhaps |
| 65 |
>a kernel bug ??? But have no idea really. Fascinating. Will have |
| 66 |
>another dig tomorrow |
| 67 |
> |
| 68 |
>Was using 3.5.7. Did try make mrproper, removing all modules from boot |
| 69 |
>but nothing helped with that kernel. |
| 70 |
> |
| 71 |
>Although I didn't compare the kernels it suggested to me to use a |
| 72 |
>different version which sorted the issue. |
| 73 |
> |
| 74 |
>I can now use all 8 cores. What will I do? I've never know such times |
| 75 |
> |
| 76 |
> |
| 77 |
>thanks |
| 78 |
|
| 79 |
If it isn't broke. Don't try to fix it. |
| 80 |
|
| 81 |
In other words. I would keep the working kernel. Bugs do occasionally appear. |
| 82 |
|
| 83 |
-- |
| 84 |
Joost |
| 85 |
-- |
| 86 |
Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
Archives