1. 06 12月, 2011 1 次提交
  2. 22 7月, 2011 1 次提交
  3. 21 7月, 2011 1 次提交
  4. 15 9月, 2010 1 次提交
  5. 15 7月, 2010 1 次提交
  6. 18 5月, 2010 1 次提交
  7. 29 4月, 2010 1 次提交
  8. 23 1月, 2010 1 次提交
  9. 16 11月, 2009 1 次提交
    • P
      x86: AMD Northbridge: Verify NB's node is online · 303fc087
      Prarit Bhargava 提交于
      Fix panic seen on some IBM and HP systems on 2.6.32-rc6:
      
       BUG: unable to handle kernel NULL pointer dereference at (null)
       IP: [<ffffffff8120bf3f>] find_next_bit+0x77/0x9c
        [...]
        [<ffffffff8120bbde>] cpumask_next_and+0x2e/0x3b
        [<ffffffff81225c62>] pci_device_probe+0x8e/0xf5
        [<ffffffff812b9be6>] ? driver_sysfs_add+0x47/0x6c
        [<ffffffff812b9da5>] driver_probe_device+0xd9/0x1f9
        [<ffffffff812b9f1d>] __driver_attach+0x58/0x7c
        [<ffffffff812b9ec5>] ? __driver_attach+0x0/0x7c
        [<ffffffff812b9298>] bus_for_each_dev+0x54/0x89
        [<ffffffff812b9b4f>] driver_attach+0x19/0x1b
        [<ffffffff812b97ae>] bus_add_driver+0xd3/0x23d
        [<ffffffff812ba1e7>] driver_register+0x98/0x109
        [<ffffffff81225ed0>] __pci_register_driver+0x63/0xd3
        [<ffffffff81072776>] ? up_read+0x26/0x2a
        [<ffffffffa0081000>] ? k8temp_init+0x0/0x20 [k8temp]
        [<ffffffffa008101e>] k8temp_init+0x1e/0x20 [k8temp]
        [<ffffffff8100a073>] do_one_initcall+0x6d/0x185
        [<ffffffff8108d765>] sys_init_module+0xd3/0x236
        [<ffffffff81011ac2>] system_call_fastpath+0x16/0x1b
      
      I put in a printk and commented out the set_dev_node()
      call when and got this output:
      
       quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x0
       quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x1
       quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x2
       quirk_amd_nb_node: current numa_node = 0x0, would set to val & 7 = 0x3
      
      I.e. the issue appears to be that the HW has set val to a valid
      value, however, the system is only configured for a single
      node -- 0, the others are offline.
      
      Check to see if the node is actually online before setting
      the numa node for an AMD northbridge in quirk_amd_nb_node().
      Signed-off-by: NPrarit Bhargava <prarit@redhat.com>
      Cc: bhavna.sarathy@amd.com
      Cc: jbarnes@virtuousgeek.org
      Cc: andreas.herrmann3@amd.com
      LKML-Reference: <20091112180933.12532.98685.sendpatchset@prarit.bos.redhat.com>
      [ v2: clean up the code and add comments ]
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      303fc087
  10. 10 9月, 2009 1 次提交
  11. 24 4月, 2009 1 次提交
  12. 18 4月, 2009 1 次提交
  13. 10 3月, 2009 1 次提交
  14. 13 1月, 2009 1 次提交
  15. 17 12月, 2008 1 次提交
    • J
      x86: enable HPET on Fujitsu u9200 · bacbe999
      Janne Kulmala 提交于
      Impact: auto-enable HPET on Fujitsu u9200
      
      HPET timer is listed in the ACPI table, but needs a quirk entry in order to
      work. Unfortunately, the quirk code runs after first HPET hpet_enable() which
      has already determined that the timer doesn't work (reads 0xFFFFFFFF). This
      patch allows hpet_enable() to be called again after running the quirk code.
      Signed-off-by: NJanne Kulmala <janne.t.kulmala@tut.fi>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      bacbe999
  16. 16 10月, 2008 1 次提交
  17. 06 9月, 2008 1 次提交
  18. 14 7月, 2008 2 次提交
  19. 21 6月, 2008 1 次提交
    • J
      x86: add PCI ID for 6300ESB force hpet · f3561810
      Joe Buehler 提交于
      00:1f.0 ISA bridge: Intel Corporation 6300ESB LPC Interface Controller (rev 02)
      00:1f.0 Class 0601: 8086:25a1 (rev 02)
      
      kernel: pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
      kernel: hpet clockevent registered
      kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
      kernel: hpet0: 3 64-bit timers, 14318180 Hz
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      f3561810
  20. 18 6月, 2008 1 次提交
  21. 05 6月, 2008 1 次提交
  22. 13 5月, 2008 2 次提交
  23. 22 3月, 2008 1 次提交
    • Z
      x86: hpet clock enable quirk on nVidia nForce 430 · 96bcf458
      Zbigniew Luszpinski 提交于
      this patch allows hpet=force on nVidia nForce 430 southbridge.
      This patch was tested by me on my old Asus A8N-VM CSM (where bios does not
      support hpet and does not advertise it via acpi entry). My nForce430 version:
      lspci -nn | grep LPC
      00:0a.0 ISA bridge [0601]: nVidia Corporation MCP51 LPC Bridge [10de:0260]
      (rev a2)
      
      Kernel 2.6.24.3 after patching and using hpet=force reports this:
      dmesg | grep -i hpet
      Kernel command line: root=/dev/sda8 ro vga=773 video=vesafb:mtrr:4,ywrap
      vt.default_utf8=0 hpet=force
      Force enabled HPET at base address 0xfed00000
      hpet clockevent registered
      Time: hpet clocksource has been installed.
      
      grep -i hpet /proc/timer_list
      Clock Event Device: hpet
       set_next_event: hpet_legacy_next_event
       set_mode:       hpet_legacy_set_mode
      
      grep Clock /proc/timer_list (before patching)
      Clock Event Device: pit
      Clock Event Device: lapic
      
      grep Clock /proc/timer_list (after patching)
      Clock Event Device: hpet
      Clock Event Device: lapic
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      96bcf458
  24. 12 2月, 2008 1 次提交
    • M
      Use proper abstractions in quirk_intel_irqbalance · 9585ca02
      Matthew Wilcox 提交于
      Since we may not have a pci_dev for the device we need to access, we can't
      use pci_read_config_word.  But raw_pci_read is an internal implementation
      detail; it's better to use the architected pci_bus_read_config_word
      interface.  Using PCI_DEVFN instead of a mysterious constant helps
      reassure everyone that we really do intend to access device 8.
      
      [ Thanks to Grant Grundler for pointing out to me that this is exactly
        what the write immediately above this is doing -- enabling device 8 to
        respond to config space cycles.
      					- Matthew
      
        Grant also says:
      
      	"Can you also add a comment which points at the Intel
      	 documentation?
      
      	 The 'Intel E7320 Memory Controller Hub (MCH) Datasheet' at
      
      	  http://download.intel.com/design/chipsets/datashts/30300702.pdf
      
      	 Page 69 documents register F4h (DEVPRES1).
      
      	 And I just doubled checked that the 0xf4 register value is
      	 restored later in the quirk (obvious when you look at the code
      	 but not from the patch"
      
        so here it is.
      					 - Linus ]
      Signed-off-by: NMatthew Wilcox <willy@linux.intel.com>
      Acked-by: NGrant Grundler <grundler@parisc-linux.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9585ca02
  25. 11 2月, 2008 1 次提交
  26. 07 2月, 2008 1 次提交
  27. 02 2月, 2008 1 次提交
  28. 30 1月, 2008 1 次提交
  29. 24 10月, 2007 2 次提交
  30. 20 10月, 2007 3 次提交
  31. 13 10月, 2007 4 次提交
  32. 11 10月, 2007 1 次提交