Messages in this thread | | | Date | Sun, 16 Nov 2014 07:42:09 -0800 | From | Guenter Roeck <> | Subject | Re: linux-next: Tree for Nov 14 |
| |
On 11/16/2014 12:37 AM, Jiang Liu wrote: > > > On 2014/11/16 16:24, Jiang Liu wrote: >> On 2014/11/16 14:56, Guenter Roeck wrote: >>> On 11/15/2014 08:20 PM, Jiang Liu wrote: >>> >>> I took the configuration file I had for the SMP case (located in the same >>> directory in the git repository), disabled SMP, and ran "make >>> savedefconfig". >>> "old" is relative in this context; I don't usually create new configuration >>> files for each new kernel release, so, yes, you could say that the file >>> I used is "old". >>> >>> CONFIG_X86_LOCAL_APIC is enabled. Keep in mind this is a configuration file >>> created with "make savedefconfig", so default settings are not included. >>> Correct, CONFIG_X86_IO_APIC is not enabled, but that is not really >>> surprising >>> since its dependencies are not met as far as I can see. >>> >>> Overall, I am not sure I understand what you are trying to say. X86_IO_APIC >>> depends on X86_64 (not set) or SMP (not set) or X86_32_NON_STANDARD (not >>> set) >>> or X86_UP_IOAPIC (not set because it depends on X86_UP_APIC which >>> depends on >>> !PCI_MSI). >>> >>> Does that mean that I'll have to disable PCI_MSI to get x86 uniprocessor >>> support to work after your patch ? >> Hi Guenter, >> Previously, X86_IO_APIC will be enabled if PCI_MSI is enabled. >> With my patch, x86_IO_APIC may be disabled even if PCI_MSI is enabled. >> If X86_LOCAL_APIC/PCI_MSI are enabled and X86_IO_APIC is disabled, it >> should work theoretically. I remember it works on my HP laptop. >> Could you please help to check whether it solve the issue by manually >> turning on X86_IO_APIC? > Or could you please help to apply this patch? > http://patchwork.ozlabs.org/patch/408402/ >
That patch does not help, unfortunately. The problem is exactly the same after applying it.
Guenter
| |