1. 26 7月, 2011 1 次提交
  2. 18 7月, 2011 5 次提交
  3. 16 7月, 2011 1 次提交
  4. 15 7月, 2011 1 次提交
  5. 14 7月, 2011 1 次提交
  6. 13 7月, 2011 3 次提交
  7. 12 7月, 2011 10 次提交
  8. 11 7月, 2011 6 次提交
  9. 10 7月, 2011 4 次提交
    • G
      hwmon: (pmbus) Improve auto-detection of temperature status register · 22e6b231
      Guenter Roeck 提交于
      It is possible that a PMBus device supports the READ_TEMPERATURE2 and/or
      READ_TEMPERATURE3 registers but does not support READ_TEMPERATURE1.
      Improve temperature status register detection to address this condition.
      Reported-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NGuenter Roeck <guenter.roeck@ericsson.com>
      Acked-by: NJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org # 2.6.39+
      22e6b231
    • G
      hwmon: (lm95241) Fix negative temperature results · 0c2a40e2
      Guenter Roeck 提交于
      Negative temperatures were returned in degrees C instead of milli-Degrees C.
      Also, negative temperatures were reported for remote temperature sensors even
      if the chip was configured for positive-only results.
      
      Fix by detecting temperature modes, and by treating negative temperatures
      similar to positive temperatures, with appropriate sign extension.
      Signed-off-by: NGuenter Roeck <guenter.roeck@ericsson.com>
      Acked-by: NJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org # 2.6.30+
      0c2a40e2
    • J
      natsemi: fix another dma-debug report · ff181774
      Jim Cromie 提交于
      commit 2fb83cd6
      Author: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Date:   Sun Jul 3 22:34:29 2011 -0700
      
      Above commit fixed previously reported warning, but I later
      noticed another one at shutdown.  This commit fixes it.
      
      ------------[ cut here ]------------
      WARNING: at /home/jimc/projects/lx/linux-2.6/lib/dma-debug.c:820 check_unmap+0x1fe/0x56c()
      natsemi 0000:00:06.0: DMA-API: device driver frees DMA memory with different size [device address=0x0000000007356840] [map size=1538 bytes] [unmap size=1522 bytes]
      Modules linked in: bridge stp llc x_tables ipv6 pc87360 hwmon_vid scx200_hrt pc8736x_gpio scx200_gpio nsc_gpio scx200_acb i2c_core arc4 rtl8180 mac80211 eeprom_93cx6 cfg80211 pcspkr scx200 rfkill ide_gd_mod ide_pci_generic ohci_hcd usbcore sc1200 ide_core [last unloaded: ebtables]
      Pid: 3996, comm: ifconfig Not tainted 3.0.0-rc6-skc-dyndbg+ #104
      Call Trace:
       [<c011ca97>] warn_slowpath_common+0x4a/0x5f
       [<c0261ca5>] ? check_unmap+0x1fe/0x56c
       [<c011cb10>] warn_slowpath_fmt+0x26/0x2a
       [<c0261ca5>] check_unmap+0x1fe/0x56c
       [<c0116505>] ? check_preempt_curr+0x5a/0x6a
       [<c0262186>] debug_dma_unmap_page+0x53/0x5b
       [<c02aaaf9>] pci_unmap_single+0x4d/0x57
       [<c02aab51>] drain_rx+0x4e/0x74
       [<c02acc6e>] netdev_close+0x103/0x1b8
       [<c02f097e>] ? spin_unlock_bh.clone.30+0x12/0x14
       [<c02f10aa>] ? dev_deactivate_many+0xc1/0xef
       [<c02e05e9>] __dev_close_many+0x69/0x86
       [<c02e0625>] __dev_close+0x1f/0x2c
       [<c02e3200>] __dev_change_flags+0x92/0x107
       [<c02e32db>] dev_change_flags+0x13/0x3f
       [<c031e7ea>] devinet_ioctl+0x248/0x4b3
       [<c02e3a9e>] ? dev_ioctl+0x50a/0x54c
       [<c031f509>] inet_ioctl+0x8e/0xa7
       [<c02d506f>] sock_ioctl+0x1b6/0x1da
       [<c02d4eb9>] ? sock_fasync+0x61/0x61
       [<c0183db4>] do_vfs_ioctl+0x44d/0x47f
       [<c0113cdb>] ? do_page_fault+0x268/0x299
       [<c01339d0>] ? __put_cred+0x34/0x36
       [<c0177d83>] ? sys_faccessat+0x13e/0x14b
       [<c0183e14>] sys_ioctl+0x2e/0x4a
       [<c035bc95>] syscall_call+0x7/0xb
      ---[ end trace 7013a1bdac403e56 ]---
      Signed-off-by: NJim Cromie <jim.cromie@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ff181774
    • S
      firewire: ohci: do not bind to Pinnacle cards, avert panic · 7f7e3711
      Stefan Richter 提交于
      When firewire-ohci is bound to a Pinnacle MovieBoard, eventually a
      "Register access failure" is logged and an interrupt storm or a kernel
      panic happens.  https://bugzilla.kernel.org/show_bug.cgi?id=36622
      
      Until this is sorted out (if that is going to succeed at all), let's
      just prevent firewire-ohci from touching these devices.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      Cc: <stable@kernel.org>
      7f7e3711
  10. 09 7月, 2011 8 次提交