- #Unresponsive script firefox yahoo mail update#
- #Unresponsive script firefox yahoo mail archive#
- #Unresponsive script firefox yahoo mail Patch#
+ * Apply erratum 688 fix so machines without a BIOS +static void init_amd_on(struct cpuinfo_x86 *c)
#Unresponsive script firefox yahoo mail Patch#
To avoid unneeded complexity we propose this patch as V2, do you agree? Only machines having our APU will beįixed. Our initial patch would fix 3 broken models and 1 working model. My brother rejected the proposed patch because it does not provideĮquivalent functionality with the original. Thank you for your time! I have chosen reply to list and all recipients, To: Borislav Petkov +Cc: linux-kernel, Nikos Barkas 23:01 ` Borislav Petkov 0 siblings, 1 reply 24+ messages in thread 16:47 ` Borislav Petkov 21:51 ` sonofagun > Let's finish this patch first and we will fix that too but it appearsĭon't hesitate to ask if you need help.ĮCO tip #101: Trim your mails when you reply. Why, what's wrong with that one? That one should be all fixed! :-) > We have many AMD machines and we will need your help next week to patch our > What do you mean? It is not clear to me, Do you mean all the info we wroteĪll the info you wrote in the first mail. > disk(tomorrow I will dump it again if you want): > Here is a dump from an older installation some months ago I kept on my No, I just wanted to see them and you've pasted them here. > Do you want /proc/cpuinfo on the V2 patch e-mail? Both CPUs needed? You can build somewhere else and copy the kernel to the laptop. > that laptop would possibly need a whole day even with AC power!
#Unresponsive script firefox yahoo mail update#
> laptop and I will update the kernel and send you the V2 patch. > we are compiling the new patch right now but compiling is run on a different
> It seems better this way so that only affected APUs are patched. No, you need to apply the fix only on the models which need it. > not need it but I did not think it would be an issue since they have fixed > My brother told me that we apply a quirk to the last Ontario APUs that do You're not the only one making this experience. > will not fix it and we will not choose their laptops anymore. > Sorry for the late reply! This machine has caused nothing but trouble. To: sonofagun +Cc: linux-kernel, Nikos Barkasįirst of all, when you reply to a mail on lkml, please use the "reply-to-all"įunctionality of your mail client - otherwise replies might get missed on such a 21:51 ` sonofagun 0 siblings, 1 reply 24+ messages in threadįrom: Borislav Petkov 16:47 UTC ( / raw) 16:19 x86/AMD: Apply erratum 688 on machines without a BIOS fix 16:47 ` Borislav Petkov * Re: x86/AMD: Apply erratum 688 on machines without a BIOS fix Patch first and we will fix that too but it appears to be much more We have many AMD machines and we will need your help next week to patch Wrote on the e-mail, your comments or both? What do you mean? It is not clear to me, Do you mean all the info we > Then, keep that *whole* changelog above when sending v2 of the patch Power management: ts ttp tm stc 100mhzsteps hwpstate Vmmcall arat npt lbrv svm_lock nrip_save pausefilterĪddress sizes : 36 bits physical, 48 bits virtual Pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicidĪperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapicĬr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt hw_pstate Pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt Model name : AMD E-300 APU with Radeon(tm) HD Graphicsįlags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov Here is a dump from an older installation some months ago I kept on myĭisk(tomorrow I will dump it again if you want): Compiling to that laptop would possibly need a whole day evenĭo you want /proc/cpuinfo on the V2 patch e-mail? Both CPUs needed? Tomorrow I will haveĪccess to the laptop and I will update the kernel and send you the V2 On a different high end AMD machine of my brother. Patient, we are compiling the new patch right now but compiling is run It seems better this way so that only affected APUs are patched. My brother told me that we apply a quirk to the last Ontario APUs thatĭo not need it but I did not think it would be an issue since they have HP will not fix it and we will not choose their laptops anymore. Sorry for the late reply! This machine has caused nothing but trouble. 16:47 ` Borislav Petkov 0 siblings, 1 reply 24+ messages in thread
#Unresponsive script firefox yahoo mail archive#
Re: x86/AMD: Apply erratum 688 on machines without a BIOS fix LKML Archive on help / color / mirror / Atom feed * Re: x86/AMD: Apply erratum 688 on machines without a BIOS fix 16:19 sonofagun
0 kommentar(er)
