* [lm-sensors] Core i3 support?
@ 2010-02-10 11:00 D. Can Celasun
2010-02-10 12:25 ` Jean Delvare
` (13 more replies)
0 siblings, 14 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-10 11:00 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 142 bytes --]
I have a i3 330M CPU and the latest sensors-detect cannot find anything.
sensors-detect and lspci outputs are attached.
Any ideas?
Thanks!
[-- Attachment #1.2: Type: text/html, Size: 164 bytes --]
[-- Attachment #2: lspci.txt --]
[-- Type: text/plain, Size: 2134 bytes --]
$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
02:00.0 VGA compatible controller: ATI Technologies Inc M92 LP [Mobility Radeon HD 4300 Series]
02:00.1 Audio device: ATI Technologies Inc RV710/730
04:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
[-- Attachment #3: sensors.txt --]
[-- Type: text/plain, Size: 3525 bytes --]
$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Dell Inc. Inspiron 1564
# Board: Dell Inc. 0M9XW4
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... No
Intel Atom thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... Yes
Found unknown chip with ID 0x8502
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
[-- Attachment #4: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
@ 2010-02-10 12:25 ` Jean Delvare
2010-02-10 12:28 ` D. Can Celasun
` (12 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-10 12:25 UTC (permalink / raw)
To: lm-sensors
On Wed, 10 Feb 2010 13:00:25 +0200, D. Can Celasun wrote:
> I have a i3 330M CPU and the latest sensors-detect cannot find anything.
>
> sensors-detect and lspci outputs are attached.
>
> Any ideas?
Please share the contents of /proc/cpuinfo with us. Also, which kernel
are you running?
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
2010-02-10 12:25 ` Jean Delvare
@ 2010-02-10 12:28 ` D. Can Celasun
2010-02-10 13:21 ` Jean Delvare
` (11 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-10 12:28 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 67 bytes --]
Thanks for the quick reply, cpuinfo is attached.
Kernel is 2.6.32
[-- Attachment #1.2: Type: text/html, Size: 77 bytes --]
[-- Attachment #2: cpuinfo.txt --]
[-- Type: text/plain, Size: 3396 bytes --]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
stepping : 2
cpu MHz : 933.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority ept vpid
bogomips : 4257.96
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
stepping : 2
cpu MHz : 933.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 2
apicid : 4
initial apicid : 4
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority ept vpid
bogomips : 4257.95
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
stepping : 2
cpu MHz : 933.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority ept vpid
bogomips : 4257.98
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
stepping : 2
cpu MHz : 933.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 2
apicid : 5
initial apicid : 5
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority ept vpid
bogomips : 4257.01
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
2010-02-10 12:25 ` Jean Delvare
2010-02-10 12:28 ` D. Can Celasun
@ 2010-02-10 13:21 ` Jean Delvare
2010-02-10 13:42 ` D. Can Celasun
` (10 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-10 13:21 UTC (permalink / raw)
To: lm-sensors
On Wed, 10 Feb 2010 14:28:49 +0200, D. Can Celasun wrote:
> Thanks for the quick reply, cpuinfo is attached.
>
> Kernel is 2.6.32
> cpu family : 6
> model : 37
> model name : Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
This is model 0x25, the highest model supported by the coretemp driver
so far is 0x1e. So your model isn't yet supported, but support could
probably be added easily if we knew the thermal limit for this CPU
model. Huaxu, care to send a patch for Core i3 support?
As for the SMBus, your kernel should support it, so if the i2c-i801
driver did not bind to the device, it probably means that ACPI
requested it first. In that case you should see a message similar to
that one in the kernel logs:
ACPI: I/O resource 0000:00:1f.3 [0x18e0-0x18ff] conflicts with ACPI region SMBI [0x18e0-0x18ef]
ACPI: Device needs an ACPI driver
In that case, all you can do is hope that ACPI is properly handling
thermal management on your machine.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (2 preceding siblings ...)
2010-02-10 13:21 ` Jean Delvare
@ 2010-02-10 13:42 ` D. Can Celasun
2010-02-10 14:44 ` Jean Delvare
` (9 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-10 13:42 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1316 bytes --]
Seems like I'll be waiting for an updated coretemp.
As for the kernel logs, couldn't see anything relevant but in case I'm
missing something, kernel log is attached.
On 10 February 2010 15:21, Jean Delvare <khali@linux-fr.org> wrote:
> On Wed, 10 Feb 2010 14:28:49 +0200, D. Can Celasun wrote:
> > Thanks for the quick reply, cpuinfo is attached.
> >
> > Kernel is 2.6.32
>
> > cpu family : 6
> > model : 37
> > model name : Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
>
> This is model 0x25, the highest model supported by the coretemp driver
> so far is 0x1e. So your model isn't yet supported, but support could
> probably be added easily if we knew the thermal limit for this CPU
> model. Huaxu, care to send a patch for Core i3 support?
>
> As for the SMBus, your kernel should support it, so if the i2c-i801
> driver did not bind to the device, it probably means that ACPI
> requested it first. In that case you should see a message similar to
> that one in the kernel logs:
> ACPI: I/O resource 0000:00:1f.3 [0x18e0-0x18ff] conflicts with ACPI region
> SMBI [0x18e0-0x18ef]
> ACPI: Device needs an ACPI driver
>
> In that case, all you can do is hope that ACPI is properly handling
> thermal management on your machine.
>
> --
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>
[-- Attachment #1.2: Type: text/html, Size: 1854 bytes --]
[-- Attachment #2: kernel.txt --]
[-- Type: text/plain, Size: 57448 bytes --]
Feb 10 00:37:12 dcclinux kernel: usb 2-1.1: new high speed USB device using ehci_hcd and address 4
Feb 10 00:37:12 dcclinux kernel: usb 2-1.1: configuration #1 chosen from 1 choice
Feb 10 00:37:12 dcclinux kernel: scsi5 : SCSI emulation for USB Mass Storage devices
Feb 10 00:37:12 dcclinux kernel: usb-storage: device found at 4
Feb 10 00:37:12 dcclinux kernel: usb-storage: waiting for device to settle before scanning
Feb 10 00:37:17 dcclinux kernel: scsi 5:0:0:0: Direct-Access WD 10EACS External 1.75 PQ: 0 ANSI: 4
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Feb 10 00:37:17 dcclinux kernel: usb-storage: device scan complete
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: [sdc] Write Protect is off
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: [sdc] Mode Sense: 23 00 00 00
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: [sdc] Assuming drive cache: write through
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: [sdc] Assuming drive cache: write through
Feb 10 00:37:17 dcclinux kernel: sdc: sdc1 sdc2 < sdc5 sdc6 >
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: [sdc] Assuming drive cache: write through
Feb 10 00:37:17 dcclinux kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Feb 10 00:37:18 dcclinux kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 10 00:37:18 dcclinux kernel: kjournald starting. Commit interval 5 seconds
Feb 10 00:37:18 dcclinux kernel: EXT3 FS on sdc5, internal journal
Feb 10 00:37:18 dcclinux kernel: EXT3-fs: recovery complete.
Feb 10 00:37:18 dcclinux kernel: EXT3-fs: mounted filesystem with writeback data mode.
Feb 10 00:37:18 dcclinux kernel: kjournald starting. Commit interval 5 seconds
Feb 10 00:37:18 dcclinux kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 10 00:37:18 dcclinux kernel: EXT3 FS on sdc6, internal journal
Feb 10 00:37:18 dcclinux kernel: EXT3-fs: recovery complete.
Feb 10 00:37:18 dcclinux kernel: EXT3-fs: mounted filesystem with writeback data mode.
Feb 10 01:05:00 dcclinux kernel: usb 2-1.1: USB disconnect, address 4
Feb 10 01:05:00 dcclinux kernel: EXT3-fs error (device sdc5): ext3_find_entry: reading directory #2 offset 0
Feb 10 01:05:00 dcclinux kernel: EXT3-fs error (device sdc5): ext3_find_entry: reading directory #2 offset 0
Feb 10 01:05:00 dcclinux kernel: ------------[ cut here ]------------
Feb 10 01:05:00 dcclinux kernel: WARNING: at fs/buffer.c:1159 mark_buffer_dirty+0x6a/0x80()
Feb 10 01:05:00 dcclinux kernel: Hardware name: Inspiron 1564
Feb 10 01:05:00 dcclinux kernel: Modules linked in: ext3 jbd fuse ext2 snd_hda_codec_atihdmi usbhid hid uvcvideo videodev v4l1_compat snd_hda_codec_realtek usb_storage snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_hda_intel snd_pcm_oss snd_hda_codec snd_hwdep snd_mixer_oss video snd_pcm ndiswrapper joydev output fan ac battery snd_timer fglrx(P) wmi snd soundcore snd_page_alloc i2c_i801 i2c_core r8169 mii thermal button dell_laptop iTCO_wdt iTCO_vendor_support rfkill pcspkr intel_agp agpgart ehci_hcd psmouse usbcore serio_raw evdev dcdbas sg cpufreq_ondemand acpi_cpufreq freq_table processor rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ahci libata scsi_mod
Feb 10 01:05:00 dcclinux kernel: Pid: 4234, comm: Thunar Tainted: P 2.6.32-ARCH #1
Feb 10 01:05:00 dcclinux kernel: Call Trace:
Feb 10 01:05:00 dcclinux kernel: [<c104041e>] ? warn_slowpath_common+0x6e/0xb0
Feb 10 01:05:00 dcclinux kernel: [<c11071ea>] ? mark_buffer_dirty+0x6a/0x80
Feb 10 01:05:00 dcclinux kernel: [<c1040473>] ? warn_slowpath_null+0x13/0x20
Feb 10 01:05:00 dcclinux kernel: [<c11071ea>] ? mark_buffer_dirty+0x6a/0x80
Feb 10 01:05:00 dcclinux kernel: [<f83b70c0>] ? T.988+0x40/0x80 [ext3]
Feb 10 01:05:00 dcclinux kernel: [<f83b7165>] ? ext3_handle_error+0x65/0xb0 [ext3]
Feb 10 01:05:00 dcclinux kernel: [<c12b6b16>] ? printk+0x17/0x21
Feb 10 01:05:00 dcclinux kernel: [<f83b74e4>] ? ext3_error+0x54/0x60 [ext3]
Feb 10 01:05:00 dcclinux kernel: [<f83b3827>] ? ext3_find_entry+0x4c7/0x660 [ext3]
Feb 10 01:05:00 dcclinux kernel: [<f83b41f6>] ? ext3_lookup+0x46/0x110 [ext3]
Feb 10 01:05:00 dcclinux kernel: [<c10f6815>] ? d_alloc+0x125/0x180
Feb 10 01:05:00 dcclinux kernel: [<c10ec6f2>] ? do_lookup+0x152/0x1c0
Feb 10 01:05:00 dcclinux kernel: [<c10ee8ba>] ? __link_path_walk+0x5da/0xc90
Feb 10 01:05:00 dcclinux kernel: [<c10c8a01>] ? handle_mm_fault+0x4b1/0x760
Feb 10 01:05:00 dcclinux kernel: [<c10ef113>] ? path_walk+0x43/0x90
Feb 10 01:05:00 dcclinux kernel: [<c10ef1b9>] ? do_path_lookup+0x59/0x90
Feb 10 01:05:00 dcclinux kernel: [<c10efcbd>] ? user_path_at+0x3d/0x80
Feb 10 01:05:00 dcclinux kernel: [<c10e7c27>] ? vfs_fstatat+0x37/0x70
Feb 10 01:05:00 dcclinux kernel: [<c10e7cb8>] ? vfs_lstat+0x18/0x20
Feb 10 01:05:00 dcclinux kernel: [<c10e7ccf>] ? sys_lstat64+0xf/0x30
Feb 10 01:05:00 dcclinux kernel: [<c10cbc37>] ? remove_vma+0x37/0x50
Feb 10 01:05:00 dcclinux kernel: [<c10ccb32>] ? do_munmap+0x212/0x270
Feb 10 01:05:00 dcclinux kernel: [<c10ccbd5>] ? sys_munmap+0x45/0x60
Feb 10 01:05:00 dcclinux kernel: [<c10039f3>] ? sysenter_do_call+0x12/0x28
Feb 10 01:05:00 dcclinux kernel: ---[ end trace 493ffa544ddd7221 ]---
Feb 10 01:09:32 dcclinux kernel: usb 2-1.1: new high speed USB device using ehci_hcd and address 5
Feb 10 01:09:32 dcclinux kernel: usb 2-1.1: configuration #1 chosen from 1 choice
Feb 10 01:09:32 dcclinux kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Feb 10 01:09:32 dcclinux kernel: usb-storage: device found at 5
Feb 10 01:09:32 dcclinux kernel: usb-storage: waiting for device to settle before scanning
Feb 10 01:09:37 dcclinux kernel: scsi 6:0:0:0: Direct-Access WD 10EACS External 1.75 PQ: 0 ANSI: 4
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0
Feb 10 01:09:37 dcclinux kernel: usb-storage: device scan complete
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: [sdc] Write Protect is off
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 10 01:09:37 dcclinux kernel: sdc: sdc1 sdc2 < sdc5 sdc6 >
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 10 01:09:37 dcclinux kernel: sd 6:0:0:0: [sdc] Attached SCSI disk
Feb 10 01:09:37 dcclinux kernel: kjournald starting. Commit interval 5 seconds
Feb 10 01:09:37 dcclinux kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 10 01:09:37 dcclinux kernel: EXT3 FS on sdc6, internal journal
Feb 10 01:09:37 dcclinux kernel: EXT3-fs: mounted filesystem with writeback data mode.
Feb 10 01:09:37 dcclinux kernel: kjournald starting. Commit interval 5 seconds
Feb 10 01:09:37 dcclinux kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 10 01:09:37 dcclinux kernel: EXT3 FS on sdc5, internal journal
Feb 10 01:09:37 dcclinux kernel: EXT3-fs: mounted filesystem with writeback data mode.
Feb 10 01:10:00 dcclinux kernel: loop: module loaded
Feb 10 01:10:01 dcclinux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Feb 10 01:10:01 dcclinux kernel: ISO 9660 Extensions: RRIP_1991A
Feb 10 01:11:20 dcclinux kernel: gedit[24793]: segfault at 94 ip 0806cbd8 sp bf8b4010 error 4 in gedit[8048000+94000]
Feb 10 01:39:34 dcclinux kernel: r8169: eth0: link down
Feb 10 01:39:35 dcclinux kernel: r8169: eth0: link up
Feb 10 01:39:36 dcclinux kernel: r8169: eth0: link down
Feb 10 01:42:24 dcclinux kernel: r8169: eth0: link up
Feb 10 01:42:24 dcclinux kernel: r8169: eth0: link down
Feb 10 01:42:51 dcclinux kernel: usb 2-1.3: USB disconnect, address 3
Feb 10 01:43:25 dcclinux kernel: r8169: eth0: link up
Feb 10 01:43:26 dcclinux kernel: r8169: eth0: link down
Feb 10 01:43:27 dcclinux kernel: r8169: eth0: link up
Feb 10 01:43:28 dcclinux kernel: r8169: eth0: link down
Feb 10 01:43:32 dcclinux kernel: r8169: eth0: link up
Feb 10 01:43:32 dcclinux kernel: r8169: eth0: link down
Feb 10 01:43:34 dcclinux kernel: r8169: eth0: link up
Feb 10 01:43:34 dcclinux kernel: r8169: eth0: link down
Feb 10 01:43:37 dcclinux kernel: r8169: eth0: link up
Feb 10 01:44:30 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 01:44:30 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 01:44:30 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 01:44:30 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 01:44:30 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 01:44:30 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 01:44:30 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 01:44:30 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 01:44:30 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 01:44:30 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 01:44:30 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 01:44:30 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 01:44:30 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 01:44:30 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 01:44:30 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 01:44:30 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 01:44:30 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 01:44:30 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 01:44:30 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 01:44:30 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 01:44:30 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 01:44:30 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 01:44:30 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 01:44:30 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 01:44:31 dcclinux kernel: PM: Marking nosave pages: 0000000000002000 - 0000000000006000
Feb 10 01:44:31 dcclinux kernel: PM: Marking nosave pages: 000000000009c000 - 0000000000100000
Feb 10 01:44:31 dcclinux kernel: PM: Basic memory bitmaps created
Feb 10 08:33:08 dcclinux kernel: PM: Syncing filesystems ... done.
Feb 10 08:33:09 dcclinux kernel: Freezing user space processes ... (elapsed 0.00 seconds) done.
Feb 10 08:33:09 dcclinux kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Feb 10 08:33:09 dcclinux kernel: PM: Preallocating image memory... done (allocated 607965 pages)
Feb 10 08:33:09 dcclinux kernel: PM: Allocated 2431860 kbytes in 0.83 seconds (2929.95 MB/s)
Feb 10 08:33:09 dcclinux kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 10 08:33:09 dcclinux kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 10 08:33:09 dcclinux kernel: ACPI handle has no context!
Feb 10 08:33:09 dcclinux kernel: HDA Intel 0000:02:00.1: PCI INT B disabled
Feb 10 08:33:09 dcclinux kernel: ACPI handle has no context!
Feb 10 08:33:09 dcclinux kernel: [fglrx] Power down the ASIC .
Feb 10 08:33:09 dcclinux kernel: [fglrx] Preparing suspend fglrx in kernel.
Feb 10 08:33:09 dcclinux kernel: ------------[ cut here ]------------
Feb 10 08:33:09 dcclinux kernel: WARNING: at mm/page_alloc.c:1805 __alloc_pages_nodemask+0x497/0x5e0()
Feb 10 08:33:09 dcclinux kernel: Hardware name: Inspiron 1564
Feb 10 08:33:09 dcclinux kernel: Modules linked in: isofs loop ext3 jbd fuse ext2 snd_hda_codec_atihdmi usbhid hid uvcvideo videodev v4l1_compat snd_hda_codec_realtek usb_storage snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_hda_intel snd_pcm_oss snd_hda_codec snd_hwdep snd_mixer_oss video snd_pcm ndiswrapper joydev output fan ac battery snd_timer fglrx(P) wmi snd soundcore snd_page_alloc i2c_i801 i2c_core r8169 mii thermal button dell_laptop iTCO_wdt iTCO_vendor_support rfkill pcspkr intel_agp agpgart ehci_hcd psmouse usbcore serio_raw evdev dcdbas sg cpufreq_ondemand acpi_cpufreq freq_table processor rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ahci libata scsi_mod
Feb 10 08:33:09 dcclinux kernel: Pid: 752, comm: pm-hibernate Tainted: P W 2.6.32-ARCH #1
Feb 10 08:33:09 dcclinux kernel: Call Trace:
Feb 10 08:33:09 dcclinux kernel: [<c104041e>] ? warn_slowpath_common+0x6e/0xb0
Feb 10 08:33:09 dcclinux kernel: [<c10b4e57>] ? __alloc_pages_nodemask+0x497/0x5e0
Feb 10 08:33:09 dcclinux kernel: [<c1040473>] ? warn_slowpath_null+0x13/0x20
Feb 10 08:33:09 dcclinux kernel: [<c10b4e57>] ? __alloc_pages_nodemask+0x497/0x5e0
Feb 10 08:33:09 dcclinux kernel: [<c105f94b>] ? up+0xb/0x40
Feb 10 08:33:09 dcclinux kernel: [<c10b4fb4>] ? __get_free_pages+0x14/0x30
Feb 10 08:33:09 dcclinux kernel: [<c10de142>] ? __kmalloc+0xe2/0x1e0
Feb 10 08:33:09 dcclinux kernel: [<f87b315b>] ? firegl_save_fb+0x3b/0x1a0 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<f87b2226>] ? firegl_pm_save_framebuffer+0x246/0x2d0 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<f87d4da4>] ? firegl_cmmqs_recoverable_surface_info+0xc4/0xd0 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<f87b53d1>] ? firegl_cail_powerdown+0xd1/0x240 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<c11867d3>] ? pci_set_power_state+0x63/0x2a0
Feb 10 08:33:09 dcclinux kernel: [<f879d276>] ? fglrx_pci_suspend+0x86/0x140 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<c118829b>] ? pci_legacy_suspend+0x2b/0xc0
Feb 10 08:33:09 dcclinux kernel: [<c11ff8f1>] ? pm_op+0x111/0x180
Feb 10 08:33:09 dcclinux kernel: [<c105fa7b>] ? down+0xb/0x40
Feb 10 08:33:09 dcclinux kernel: [<c11ffec4>] ? dpm_suspend_start+0x334/0x470
Feb 10 08:33:09 dcclinux kernel: [<c1076e2f>] ? hibernation_snapshot+0x6f/0x240
Feb 10 08:33:09 dcclinux kernel: [<c1075f7f>] ? freeze_processes+0x4f/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c10770d8>] ? hibernate+0xd8/0x1c0
Feb 10 08:33:09 dcclinux kernel: [<c1075a30>] ? state_store+0x0/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c1075ac4>] ? state_store+0x94/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c1075a30>] ? state_store+0x0/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c11725e0>] ? kobj_attr_store+0x20/0x30
Feb 10 08:33:09 dcclinux kernel: [<c11363a9>] ? sysfs_write_file+0x99/0x100
Feb 10 08:33:09 dcclinux kernel: [<c1136310>] ? sysfs_write_file+0x0/0x100
Feb 10 08:33:09 dcclinux kernel: [<c10e44b0>] ? vfs_write+0xa0/0x190
Feb 10 08:33:09 dcclinux kernel: [<c1025ac1>] ? do_page_fault+0x111/0x330
Feb 10 08:33:09 dcclinux kernel: [<c10e4661>] ? sys_write+0x41/0x70
Feb 10 08:33:09 dcclinux kernel: [<c10039f3>] ? sysenter_do_call+0x12/0x28
Feb 10 08:33:09 dcclinux kernel: ---[ end trace 493ffa544ddd7222 ]---
Feb 10 08:33:09 dcclinux kernel: pm-hibernate: page allocation failure. order:10, mode:0x4020
Feb 10 08:33:09 dcclinux kernel: Pid: 752, comm: pm-hibernate Tainted: P W 2.6.32-ARCH #1
Feb 10 08:33:09 dcclinux kernel: Call Trace:
Feb 10 08:33:09 dcclinux kernel: [<c10b4ea3>] ? __alloc_pages_nodemask+0x4e3/0x5e0
Feb 10 08:33:09 dcclinux kernel: [<c1004415>] ? apic_timer_interrupt+0x31/0x38
Feb 10 08:33:09 dcclinux kernel: [<c10b4fb4>] ? __get_free_pages+0x14/0x30
Feb 10 08:33:09 dcclinux kernel: [<c10de142>] ? __kmalloc+0xe2/0x1e0
Feb 10 08:33:09 dcclinux kernel: [<c10d194d>] ? remove_vm_area+0x6d/0x90
Feb 10 08:33:09 dcclinux kernel: [<c102634c>] ? iounmap+0x7c/0xc0
Feb 10 08:33:09 dcclinux kernel: [<f87b315b>] ? firegl_save_fb+0x3b/0x1a0 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<f87b2226>] ? firegl_pm_save_framebuffer+0x246/0x2d0 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<f87d4da4>] ? firegl_cmmqs_recoverable_surface_info+0xc4/0xd0 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<f87b53d1>] ? firegl_cail_powerdown+0xd1/0x240 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<c11867d3>] ? pci_set_power_state+0x63/0x2a0
Feb 10 08:33:09 dcclinux kernel: [<f879d276>] ? fglrx_pci_suspend+0x86/0x140 [fglrx]
Feb 10 08:33:09 dcclinux kernel: [<c118829b>] ? pci_legacy_suspend+0x2b/0xc0
Feb 10 08:33:09 dcclinux kernel: [<c11ff8f1>] ? pm_op+0x111/0x180
Feb 10 08:33:09 dcclinux kernel: [<c105fa7b>] ? down+0xb/0x40
Feb 10 08:33:09 dcclinux kernel: [<c11ffec4>] ? dpm_suspend_start+0x334/0x470
Feb 10 08:33:09 dcclinux kernel: [<c1076e2f>] ? hibernation_snapshot+0x6f/0x240
Feb 10 08:33:09 dcclinux kernel: [<c1075f7f>] ? freeze_processes+0x4f/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c10770d8>] ? hibernate+0xd8/0x1c0
Feb 10 08:33:09 dcclinux kernel: [<c1075a30>] ? state_store+0x0/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c1075ac4>] ? state_store+0x94/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c1075a30>] ? state_store+0x0/0xa0
Feb 10 08:33:09 dcclinux kernel: [<c11725e0>] ? kobj_attr_store+0x20/0x30
Feb 10 08:33:09 dcclinux kernel: [<c11363a9>] ? sysfs_write_file+0x99/0x100
Feb 10 08:33:09 dcclinux kernel: [<c1136310>] ? sysfs_write_file+0x0/0x100
Feb 10 08:33:09 dcclinux kernel: [<c10e44b0>] ? vfs_write+0xa0/0x190
Feb 10 08:33:09 dcclinux kernel: [<c1025ac1>] ? do_page_fault+0x111/0x330
Feb 10 08:33:09 dcclinux kernel: [<c10e4661>] ? sys_write+0x41/0x70
Feb 10 08:33:09 dcclinux kernel: [<c10039f3>] ? sysenter_do_call+0x12/0x28
Feb 10 08:33:09 dcclinux kernel: Mem-Info:
Feb 10 08:33:09 dcclinux kernel: DMA per-cpu:
Feb 10 08:33:09 dcclinux kernel: CPU 0: hi: 0, btch: 1 usd: 0
Feb 10 08:33:09 dcclinux kernel: CPU 1: hi: 0, btch: 1 usd: 0
Feb 10 08:33:09 dcclinux kernel: CPU 2: hi: 0, btch: 1 usd: 0
Feb 10 08:33:09 dcclinux kernel: CPU 3: hi: 0, btch: 1 usd: 0
Feb 10 08:33:09 dcclinux kernel: Normal per-cpu:
Feb 10 08:33:09 dcclinux kernel: CPU 0: hi: 186, btch: 31 usd: 153
Feb 10 08:33:09 dcclinux kernel: CPU 1: hi: 186, btch: 31 usd: 27
Feb 10 08:33:09 dcclinux kernel: CPU 2: hi: 186, btch: 31 usd: 92
Feb 10 08:33:09 dcclinux kernel: CPU 3: hi: 186, btch: 31 usd: 88
Feb 10 08:33:09 dcclinux kernel: HighMem per-cpu:
Feb 10 08:33:09 dcclinux kernel: CPU 0: hi: 186, btch: 31 usd: 7
Feb 10 08:33:09 dcclinux kernel: CPU 1: hi: 186, btch: 31 usd: 167
Feb 10 08:33:09 dcclinux kernel: CPU 2: hi: 186, btch: 31 usd: 167
Feb 10 08:33:09 dcclinux kernel: CPU 3: hi: 186, btch: 31 usd: 157
Feb 10 08:33:09 dcclinux kernel: active_anon:22696 inactive_anon:20140 isolated_anon:0
Feb 10 08:33:09 dcclinux kernel: active_file:10483 inactive_file:32816 isolated_file:0
Feb 10 08:33:09 dcclinux kernel: unevictable:4 dirty:1 writeback:0 unstable:0
Feb 10 08:33:09 dcclinux kernel: free:158987 slab_reclaimable:6641 slab_unreclaimable:2140
Feb 10 08:33:09 dcclinux kernel: mapped:15183 shmem:1754 pagetables:580 bounce:0
Feb 10 08:33:09 dcclinux kernel: DMA free:4776kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:1936kB inactive_file:9216kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15840kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:8kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Feb 10 08:33:09 dcclinux kernel: lowmem_reserve[]: 0 865 2957 2957
Feb 10 08:33:09 dcclinux kernel: Normal free:500720kB min:3728kB low:4660kB high:5592kB active_anon:0kB inactive_anon:0kB active_file:20232kB inactive_file:81416kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:885944kB mlocked:0kB dirty:0kB writeback:0kB mapped:20kB shmem:0kB slab_reclaimable:26564kB slab_unreclaimable:8552kB kernel_stack:1992kB pagetables:2320kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Feb 10 08:33:09 dcclinux kernel: lowmem_reserve[]: 0 0 16739 16739
Feb 10 08:33:09 dcclinux kernel: HighMem free:130452kB min:512kB low:2764kB high:5020kB active_anon:90784kB inactive_anon:80560kB active_file:19764kB inactive_file:40632kB unevictable:16kB isolated(anon):0kB isolated(file):0kB present:2142660kB mlocked:16kB dirty:4kB writeback:0kB mapped:60712kB shmem:7016kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:10175 all_unreclaimable? no
Feb 10 08:33:09 dcclinux kernel: lowmem_reserve[]: 0 0 0 0
Feb 10 08:33:09 dcclinux kernel: DMA: 34*4kB 32*8kB 24*16kB 3*32kB 1*64kB 2*128kB 2*256kB 0*512kB 1*1024kB 1*2048kB 0*4096kB = 4776kB
Feb 10 08:33:09 dcclinux kernel: Normal: 9874*4kB 6541*8kB 4390*16kB 2419*32kB 1020*64kB 431*128kB 202*256kB 116*512kB 25*1024kB 2*2048kB 0*4096kB = 500720kB
Feb 10 08:33:09 dcclinux kernel: HighMem: 4865*4kB 3414*8kB 1956*16kB 923*32kB 311*64kB 23*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 130452kB
Feb 10 08:33:09 dcclinux kernel: 45066 total pagecache pages
Feb 10 08:33:09 dcclinux kernel: 13 pages in swap cache
Feb 10 08:33:09 dcclinux kernel: Swap cache stats: add 55, delete 42, find 0/0
Feb 10 08:33:09 dcclinux kernel: Free swap = 4610392kB
Feb 10 08:33:09 dcclinux kernel: Total swap = 4610612kB
Feb 10 08:33:09 dcclinux kernel: 768000 pages RAM
Feb 10 08:33:09 dcclinux kernel: 540674 pages HighMem
Feb 10 08:33:09 dcclinux kernel: 17171 pages reserved
Feb 10 08:33:09 dcclinux kernel: 89474 pages shared
Feb 10 08:33:09 dcclinux kernel: 547883 pages non-shared
Feb 10 08:33:09 dcclinux kernel: [fglrx] Suspending fglrx in kernel completed.
Feb 10 08:33:09 dcclinux kernel: pci 0000:00:1f.3: PCI INT C disabled
Feb 10 08:33:09 dcclinux kernel: HDA Intel 0000:00:1b.0: PCI INT A disabled
Feb 10 08:33:09 dcclinux kernel: ACPI: Preparing to enter system sleep state S4
Feb 10 08:33:09 dcclinux kernel: PM: Saving platform NVS memory
Feb 10 08:33:09 dcclinux kernel: Disabling non-boot CPUs ...
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: Breaking affinity for irq 25
Feb 10 08:33:09 dcclinux kernel: CPU 1 is now offline
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: Breaking affinity for irq 26
Feb 10 08:33:09 dcclinux kernel: CPU 2 is now offline
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: Breaking affinity for irq 27
Feb 10 08:33:09 dcclinux kernel: CPU 3 is now offline
Feb 10 08:33:09 dcclinux kernel: SMP alternatives: switching to UP code
Feb 10 08:33:09 dcclinux kernel: Extended CMOS year: 2000
Feb 10 08:33:09 dcclinux kernel: PM: Creating hibernation image:
Feb 10 08:33:09 dcclinux kernel: PM: Need to copy 121438 pages
Feb 10 08:33:09 dcclinux kernel: PM: Normal pages needed: 52703 + 1024, available pages: 174468
Feb 10 08:33:09 dcclinux kernel: PM: Restoring platform NVS memory
Feb 10 08:33:09 dcclinux kernel: CPU0: Thermal monitoring handled by SMI
Feb 10 08:33:09 dcclinux kernel: Extended CMOS year: 2000
Feb 10 08:33:09 dcclinux kernel: Enabling non-boot CPUs ...
Feb 10 08:33:09 dcclinux kernel: SMP alternatives: switching to SMP code
Feb 10 08:33:09 dcclinux kernel: Booting processor 1 APIC 0x4 ip 0x6000
Feb 10 08:33:09 dcclinux kernel: Initializing CPU#1
Feb 10 08:33:09 dcclinux kernel: CPU: Physical Processor ID: 0
Feb 10 08:33:09 dcclinux kernel: CPU: Processor Core ID: 2
Feb 10 08:33:09 dcclinux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 10 08:33:09 dcclinux kernel: CPU: L2 cache: 256K
Feb 10 08:33:09 dcclinux kernel: CPU: L3 cache: 3072K
Feb 10 08:33:09 dcclinux kernel: CPU1: Thermal monitoring handled by SMI
Feb 10 08:33:09 dcclinux kernel: CPU 1 MCA banks SHD:6
Feb 10 08:33:09 dcclinux kernel: CPU1: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz stepping 02
Feb 10 08:33:09 dcclinux kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 0-1 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 0 1
Feb 10 08:33:09 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 0-1 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 1 0
Feb 10 08:33:09 dcclinux kernel: hpet: hpet3 irq 25 for MSI
Feb 10 08:33:09 dcclinux kernel: CPU1 is up
Feb 10 08:33:09 dcclinux kernel: Booting processor 2 APIC 0x1 ip 0x6000
Feb 10 08:33:09 dcclinux kernel: Initializing CPU#2
Feb 10 08:33:09 dcclinux kernel: CPU: Physical Processor ID: 0
Feb 10 08:33:09 dcclinux kernel: CPU: Processor Core ID: 0
Feb 10 08:33:09 dcclinux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 10 08:33:09 dcclinux kernel: CPU: L2 cache: 256K
Feb 10 08:33:09 dcclinux kernel: CPU: L3 cache: 3072K
Feb 10 08:33:09 dcclinux kernel: CPU2: Thermal monitoring handled by SMI
Feb 10 08:33:09 dcclinux kernel: CPU 2 MCA banks SHD:2 SHD:3 SHD:5 SHD:6
Feb 10 08:33:09 dcclinux kernel: CPU2: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz stepping 02
Feb 10 08:33:09 dcclinux kernel: checking TSC synchronization [CPU#0 -> CPU#2]: passed.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:33:09 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 08:33:09 dcclinux kernel: domain 1: span 0-2 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1
Feb 10 08:33:09 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 0-2 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 1 0,2 (cpu_power = 1178)
Feb 10 08:33:09 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:33:09 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 08:33:09 dcclinux kernel: domain 1: span 0-2 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1
Feb 10 08:33:09 dcclinux kernel: hpet: hpet4 irq 26 for MSI
Feb 10 08:33:09 dcclinux kernel: CPU2 is up
Feb 10 08:33:09 dcclinux kernel: Booting processor 3 APIC 0x5 ip 0x6000
Feb 10 08:33:09 dcclinux kernel: Initializing CPU#3
Feb 10 08:33:09 dcclinux kernel: CPU: Physical Processor ID: 0
Feb 10 08:33:09 dcclinux kernel: CPU: Processor Core ID: 2
Feb 10 08:33:09 dcclinux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 10 08:33:09 dcclinux kernel: CPU: L2 cache: 256K
Feb 10 08:33:09 dcclinux kernel: CPU: L3 cache: 3072K
Feb 10 08:33:09 dcclinux kernel: CPU3: Thermal monitoring handled by SMI
Feb 10 08:33:09 dcclinux kernel: CPU 3 MCA banks SHD:2 SHD:3 SHD:5 SHD:6
Feb 10 08:33:09 dcclinux kernel: CPU3: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz stepping 02
Feb 10 08:33:09 dcclinux kernel: checking TSC synchronization [CPU#0 -> CPU#3]: passed.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 08:33:09 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:33:09 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 08:33:09 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 08:33:09 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 08:33:09 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 08:33:09 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 08:33:09 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:33:09 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 08:33:09 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 08:33:09 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 08:33:09 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 08:33:09 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 08:33:09 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:09 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 08:33:09 dcclinux kernel: hpet: hpet5 irq 27 for MSI
Feb 10 08:33:09 dcclinux kernel: CPU3 is up
Feb 10 08:33:09 dcclinux kernel: ACPI: Waking up from system sleep state S4
Feb 10 08:33:09 dcclinux kernel: pcieport 0000:00:01.0: restoring config space at offset 0x7 (was 0x20002020, writing 0x2020)
Feb 10 08:33:09 dcclinux kernel: ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407)
Feb 10 08:33:09 dcclinux kernel: fglrx_pci 0000:02:00.0: restoring config space at offset 0x1 (was 0x40100107, writing 0x40100503)
Feb 10 08:33:09 dcclinux kernel: HDA Intel 0000:02:00.1: restoring config space at offset 0x1 (was 0x40100107, writing 0x40100103)
Feb 10 08:33:09 dcclinux kernel: r8169 0000:05:00.0: restoring config space at offset 0x1 (was 0x100107, writing 0x100507)
Feb 10 08:33:09 dcclinux kernel: ehci_hcd 0000:00:1a.0: setting latency timer to 64
Feb 10 08:33:09 dcclinux kernel: usb usb1: root hub lost power or was reset
Feb 10 08:33:09 dcclinux kernel: ehci_hcd 0000:00:1a.0: cache line size of 32 is not supported
Feb 10 08:33:09 dcclinux kernel: HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Feb 10 08:33:09 dcclinux kernel: HDA Intel 0000:00:1b.0: setting latency timer to 64
Feb 10 08:33:09 dcclinux kernel: ehci_hcd 0000:00:1d.0: setting latency timer to 64
Feb 10 08:33:09 dcclinux kernel: usb usb2: root hub lost power or was reset
Feb 10 08:33:09 dcclinux kernel: ehci_hcd 0000:00:1d.0: cache line size of 32 is not supported
Feb 10 08:33:09 dcclinux kernel: pci 0000:00:1e.0: setting latency timer to 64
Feb 10 08:33:09 dcclinux kernel: ahci 0000:00:1f.2: setting latency timer to 64
Feb 10 08:33:09 dcclinux kernel: pci 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Feb 10 08:33:09 dcclinux kernel: fglrx_pci 0000:02:00.0: setting latency timer to 64
Feb 10 08:33:09 dcclinux kernel: [fglrx] Preparing resume fglrx in kernel.
Feb 10 08:33:09 dcclinux kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 10 08:33:09 dcclinux kernel: ata1.00: configured for UDMA/133
Feb 10 08:33:09 dcclinux kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 10 08:33:09 dcclinux kernel: ata2.00: configured for UDMA/100
Feb 10 08:33:09 dcclinux kernel: [fglrx] Resuming fglrx in kernel completed.
Feb 10 08:33:09 dcclinux kernel: [fglrx] Power up the ASIC
Feb 10 08:33:09 dcclinux kernel: HDA Intel 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Feb 10 08:33:09 dcclinux kernel: HDA Intel 0000:02:00.1: setting latency timer to 64
Feb 10 08:33:09 dcclinux kernel: sd 0:0:0:0: [sda] Starting disk
Feb 10 08:33:09 dcclinux kernel: usb 1-1: reset high speed USB device using ehci_hcd and address 2
Feb 10 08:33:09 dcclinux kernel: usb 2-1: reset high speed USB device using ehci_hcd and address 2
Feb 10 08:33:09 dcclinux kernel: usb 1-1.5: reset high speed USB device using ehci_hcd and address 4
Feb 10 08:33:09 dcclinux kernel: usb 1-1.4: reset high speed USB device using ehci_hcd and address 5
Feb 10 08:33:09 dcclinux kernel: PM: Image restored successfully.
Feb 10 08:33:09 dcclinux kernel: Restarting tasks ... done.
Feb 10 08:33:09 dcclinux kernel: PM: Basic memory bitmaps freed
Feb 10 08:33:09 dcclinux kernel: usb 2-1.1: USB disconnect, address 5
Feb 10 08:33:22 dcclinux kernel: EXT3-fs error (device sdc5): ext3_find_entry: reading directory #2 offset 0
Feb 10 08:33:22 dcclinux kernel: EXT3-fs error (device sdc5): ext3_find_entry: reading directory #2 offset 0
Feb 10 08:33:26 dcclinux kernel: r8169: eth0: link up
Feb 10 08:33:26 dcclinux kernel: r8169: eth0: link up
Feb 10 08:33:26 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:33:26 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 08:33:26 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 08:33:26 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 08:33:26 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 08:33:26 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:33:26 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 08:33:26 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:26 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 08:33:26 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 08:33:26 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 08:33:26 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 08:33:26 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:26 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 08:33:26 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 08:33:26 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:33:26 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 08:33:26 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:26 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 08:33:26 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 08:33:26 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 08:33:26 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 08:33:26 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:33:26 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 08:53:52 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 08:53:52 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 08:53:52 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 08:53:52 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 08:53:52 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 08:53:52 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:53:52 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 08:53:52 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:53:52 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 08:53:52 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 08:53:52 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 08:53:52 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 08:53:52 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:53:52 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 08:53:52 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 08:53:52 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 08:53:52 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 08:53:52 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:53:52 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 08:53:52 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 08:53:52 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 08:53:52 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 08:53:52 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 08:53:52 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 08:53:54 dcclinux kernel: PM: Marking nosave pages: 0000000000002000 - 0000000000006000
Feb 10 08:53:54 dcclinux kernel: PM: Marking nosave pages: 000000000009c000 - 0000000000100000
Feb 10 08:53:54 dcclinux kernel: PM: Basic memory bitmaps created
Feb 10 10:37:12 dcclinux kernel: PM: Syncing filesystems ... done.
Feb 10 10:37:12 dcclinux kernel: Freezing user space processes ... (elapsed 0.01 seconds) done.
Feb 10 10:37:12 dcclinux kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Feb 10 10:37:12 dcclinux kernel: PM: Preallocating image memory... done (allocated 607967 pages)
Feb 10 10:37:12 dcclinux kernel: PM: Allocated 2431868 kbytes in 0.35 seconds (6948.19 MB/s)
Feb 10 10:37:12 dcclinux kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 10 10:37:12 dcclinux kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 10 10:37:12 dcclinux kernel: ACPI handle has no context!
Feb 10 10:37:12 dcclinux kernel: HDA Intel 0000:02:00.1: PCI INT B disabled
Feb 10 10:37:12 dcclinux kernel: ACPI handle has no context!
Feb 10 10:37:12 dcclinux kernel: [fglrx] Power down the ASIC .
Feb 10 10:37:12 dcclinux kernel: [fglrx] Preparing suspend fglrx in kernel.
Feb 10 10:37:12 dcclinux kernel: [fglrx] Suspending fglrx in kernel completed.
Feb 10 10:37:12 dcclinux kernel: pci 0000:00:1f.3: PCI INT C disabled
Feb 10 10:37:12 dcclinux kernel: HDA Intel 0000:00:1b.0: PCI INT A disabled
Feb 10 10:37:12 dcclinux kernel: ACPI: Preparing to enter system sleep state S4
Feb 10 10:37:12 dcclinux kernel: PM: Saving platform NVS memory
Feb 10 10:37:12 dcclinux kernel: Disabling non-boot CPUs ...
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: Breaking affinity for irq 25
Feb 10 10:37:12 dcclinux kernel: CPU 1 is now offline
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: Breaking affinity for irq 26
Feb 10 10:37:12 dcclinux kernel: CPU 2 is now offline
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: Breaking affinity for irq 27
Feb 10 10:37:12 dcclinux kernel: CPU 3 is now offline
Feb 10 10:37:12 dcclinux kernel: SMP alternatives: switching to UP code
Feb 10 10:37:12 dcclinux kernel: Extended CMOS year: 2000
Feb 10 10:37:12 dcclinux kernel: PM: Creating hibernation image:
Feb 10 10:37:12 dcclinux kernel: PM: Need to copy 106572 pages
Feb 10 10:37:12 dcclinux kernel: PM: Normal pages needed: 48962 + 1024, available pages: 178209
Feb 10 10:37:12 dcclinux kernel: PM: Restoring platform NVS memory
Feb 10 10:37:12 dcclinux kernel: CPU0: Thermal monitoring handled by SMI
Feb 10 10:37:12 dcclinux kernel: Extended CMOS year: 2000
Feb 10 10:37:12 dcclinux kernel: Enabling non-boot CPUs ...
Feb 10 10:37:12 dcclinux kernel: SMP alternatives: switching to SMP code
Feb 10 10:37:12 dcclinux kernel: Booting processor 1 APIC 0x4 ip 0x6000
Feb 10 10:37:12 dcclinux kernel: Initializing CPU#1
Feb 10 10:37:12 dcclinux kernel: CPU: Physical Processor ID: 0
Feb 10 10:37:12 dcclinux kernel: CPU: Processor Core ID: 2
Feb 10 10:37:12 dcclinux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 10 10:37:12 dcclinux kernel: CPU: L2 cache: 256K
Feb 10 10:37:12 dcclinux kernel: CPU: L3 cache: 3072K
Feb 10 10:37:12 dcclinux kernel: CPU1: Thermal monitoring handled by SMI
Feb 10 10:37:12 dcclinux kernel: CPU 1 MCA banks SHD:6
Feb 10 10:37:12 dcclinux kernel: CPU1: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz stepping 02
Feb 10 10:37:12 dcclinux kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 0-1 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 0 1
Feb 10 10:37:12 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 0-1 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 1 0
Feb 10 10:37:12 dcclinux kernel: hpet: hpet3 irq 25 for MSI
Feb 10 10:37:12 dcclinux kernel: CPU1 is up
Feb 10 10:37:12 dcclinux kernel: Booting processor 2 APIC 0x1 ip 0x6000
Feb 10 10:37:12 dcclinux kernel: Initializing CPU#2
Feb 10 10:37:12 dcclinux kernel: CPU: Physical Processor ID: 0
Feb 10 10:37:12 dcclinux kernel: CPU: Processor Core ID: 0
Feb 10 10:37:12 dcclinux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 10 10:37:12 dcclinux kernel: CPU: L2 cache: 256K
Feb 10 10:37:12 dcclinux kernel: CPU: L3 cache: 3072K
Feb 10 10:37:12 dcclinux kernel: CPU2: Thermal monitoring handled by SMI
Feb 10 10:37:12 dcclinux kernel: CPU 2 MCA banks SHD:2 SHD:3 SHD:5 SHD:6
Feb 10 10:37:12 dcclinux kernel: CPU2: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz stepping 02
Feb 10 10:37:12 dcclinux kernel: checking TSC synchronization [CPU#0 -> CPU#2]: passed.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 10:37:12 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 10:37:12 dcclinux kernel: domain 1: span 0-2 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1
Feb 10 10:37:12 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 0-2 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 1 0,2 (cpu_power = 1178)
Feb 10 10:37:12 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 10:37:12 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 10:37:12 dcclinux kernel: domain 1: span 0-2 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1
Feb 10 10:37:12 dcclinux kernel: hpet: hpet4 irq 26 for MSI
Feb 10 10:37:12 dcclinux kernel: CPU2 is up
Feb 10 10:37:12 dcclinux kernel: Booting processor 3 APIC 0x5 ip 0x6000
Feb 10 10:37:12 dcclinux kernel: Initializing CPU#3
Feb 10 10:37:12 dcclinux kernel: CPU: Physical Processor ID: 0
Feb 10 10:37:12 dcclinux kernel: CPU: Processor Core ID: 2
Feb 10 10:37:12 dcclinux kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 10 10:37:12 dcclinux kernel: CPU: L2 cache: 256K
Feb 10 10:37:12 dcclinux kernel: CPU: L3 cache: 3072K
Feb 10 10:37:12 dcclinux kernel: CPU3: Thermal monitoring handled by SMI
Feb 10 10:37:12 dcclinux kernel: CPU 3 MCA banks SHD:2 SHD:3 SHD:5 SHD:6
Feb 10 10:37:12 dcclinux kernel: CPU3: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz stepping 02
Feb 10 10:37:12 dcclinux kernel: checking TSC synchronization [CPU#0 -> CPU#3]: passed.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 10:37:12 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 10:37:12 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 10:37:12 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 10:37:12 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 10:37:12 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 10:37:12 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 10:37:12 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 10:37:12 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 10:37:12 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 10:37:12 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 10:37:12 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 10:37:12 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 10:37:12 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:12 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 10:37:12 dcclinux kernel: hpet: hpet5 irq 27 for MSI
Feb 10 10:37:12 dcclinux kernel: CPU3 is up
Feb 10 10:37:12 dcclinux kernel: ACPI: Waking up from system sleep state S4
Feb 10 10:37:12 dcclinux kernel: pcieport 0000:00:1c.1: restoring config space at offset 0x7 (was 0x5050, writing 0x60005050)
Feb 10 10:37:12 dcclinux kernel: ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407)
Feb 10 10:37:12 dcclinux kernel: fglrx_pci 0000:02:00.0: restoring config space at offset 0x1 (was 0x40100107, writing 0x100503)
Feb 10 10:37:12 dcclinux kernel: HDA Intel 0000:02:00.1: restoring config space at offset 0x1 (was 0x40100107, writing 0x100103)
Feb 10 10:37:12 dcclinux kernel: r8169 0000:05:00.0: restoring config space at offset 0x1 (was 0x100107, writing 0x100507)
Feb 10 10:37:12 dcclinux kernel: ehci_hcd 0000:00:1a.0: setting latency timer to 64
Feb 10 10:37:12 dcclinux kernel: usb usb1: root hub lost power or was reset
Feb 10 10:37:12 dcclinux kernel: ehci_hcd 0000:00:1a.0: cache line size of 32 is not supported
Feb 10 10:37:12 dcclinux kernel: HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Feb 10 10:37:12 dcclinux kernel: HDA Intel 0000:00:1b.0: setting latency timer to 64
Feb 10 10:37:12 dcclinux kernel: ehci_hcd 0000:00:1d.0: setting latency timer to 64
Feb 10 10:37:12 dcclinux kernel: usb usb2: root hub lost power or was reset
Feb 10 10:37:12 dcclinux kernel: ehci_hcd 0000:00:1d.0: cache line size of 32 is not supported
Feb 10 10:37:12 dcclinux kernel: pci 0000:00:1e.0: setting latency timer to 64
Feb 10 10:37:12 dcclinux kernel: ahci 0000:00:1f.2: setting latency timer to 64
Feb 10 10:37:12 dcclinux kernel: pci 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Feb 10 10:37:12 dcclinux kernel: fglrx_pci 0000:02:00.0: setting latency timer to 64
Feb 10 10:37:12 dcclinux kernel: [fglrx] Preparing resume fglrx in kernel.
Feb 10 10:37:12 dcclinux kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 10 10:37:12 dcclinux kernel: ata1.00: configured for UDMA/133
Feb 10 10:37:12 dcclinux kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 10 10:37:12 dcclinux kernel: ata2.00: configured for UDMA/100
Feb 10 10:37:12 dcclinux kernel: [fglrx] Resuming fglrx in kernel completed.
Feb 10 10:37:12 dcclinux kernel: [fglrx] Power up the ASIC
Feb 10 10:37:12 dcclinux kernel: HDA Intel 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Feb 10 10:37:12 dcclinux kernel: HDA Intel 0000:02:00.1: setting latency timer to 64
Feb 10 10:37:12 dcclinux kernel: sd 0:0:0:0: [sda] Starting disk
Feb 10 10:37:12 dcclinux kernel: usb 1-1: reset high speed USB device using ehci_hcd and address 2
Feb 10 10:37:12 dcclinux kernel: usb 1-1.5: reset high speed USB device using ehci_hcd and address 4
Feb 10 10:37:12 dcclinux kernel: usb 1-1.4: reset high speed USB device using ehci_hcd and address 5
Feb 10 10:37:12 dcclinux kernel: PM: Image restored successfully.
Feb 10 10:37:13 dcclinux kernel: Restarting tasks ... done.
Feb 10 10:37:13 dcclinux kernel: PM: Basic memory bitmaps freed
Feb 10 10:37:13 dcclinux kernel: usb 2-1: reset high speed USB device using ehci_hcd and address 2
Feb 10 10:37:14 dcclinux kernel: r8169: eth0: link down
Feb 10 10:37:15 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 10:37:15 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 10:37:15 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 10:37:15 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 10:37:15 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 10:37:15 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 10:37:15 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 10:37:15 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:15 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 10:37:15 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 10:37:15 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 10:37:15 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 10:37:15 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:15 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 10:37:15 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 10:37:15 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 10:37:15 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 10:37:15 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:15 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 10:37:15 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 10:37:15 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 10:37:15 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 10:37:15 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 10:37:15 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 12:01:51 dcclinux kernel: hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Feb 10 12:49:17 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 12:49:17 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 12:49:17 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 12:49:17 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 12:49:17 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 12:49:17 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 12:49:17 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 12:49:17 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 12:49:17 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 12:49:17 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 12:49:17 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 12:49:17 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 12:49:17 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 12:49:17 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 12:49:17 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 12:49:17 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 12:49:17 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 12:49:17 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 12:49:17 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 12:49:17 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 12:49:17 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 12:49:17 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 12:49:17 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 12:49:17 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 12:58:09 dcclinux kernel: i2c /dev entries driver
Feb 10 14:04:10 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:10 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:12 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:12 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:12 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:14 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:14 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:15 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:15 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:15 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:15 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:15 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:16 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:16 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:16 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:16 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:16 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:17 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:18 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:18 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:18 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:19 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:19 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:20 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:20 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:21 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:21 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:22 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:22 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:22 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:23 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:23 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:04:24 dcclinux kernel: [fglrx:firegl_acpi_video_event] *ERROR* Could not find private acpi context by video busid: LCD
Feb 10 14:19:03 dcclinux kernel: CPU0 attaching NULL sched-domain.
Feb 10 14:19:03 dcclinux kernel: CPU1 attaching NULL sched-domain.
Feb 10 14:19:03 dcclinux kernel: CPU2 attaching NULL sched-domain.
Feb 10 14:19:03 dcclinux kernel: CPU3 attaching NULL sched-domain.
Feb 10 14:19:03 dcclinux kernel: CPU0 attaching sched-domain:
Feb 10 14:19:03 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 14:19:03 dcclinux kernel: groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
Feb 10 14:19:03 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 14:19:03 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 14:19:03 dcclinux kernel: CPU1 attaching sched-domain:
Feb 10 14:19:03 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 14:19:03 dcclinux kernel: groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
Feb 10 14:19:03 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 14:19:03 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
Feb 10 14:19:03 dcclinux kernel: CPU2 attaching sched-domain:
Feb 10 14:19:03 dcclinux kernel: domain 0: span 0,2 level SIBLING
Feb 10 14:19:03 dcclinux kernel: groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
Feb 10 14:19:03 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 14:19:03 dcclinux kernel: groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
Feb 10 14:19:03 dcclinux kernel: CPU3 attaching sched-domain:
Feb 10 14:19:03 dcclinux kernel: domain 0: span 1,3 level SIBLING
Feb 10 14:19:03 dcclinux kernel: groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
Feb 10 14:19:03 dcclinux kernel: domain 1: span 0-3 level MC
Feb 10 14:19:03 dcclinux kernel: groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (3 preceding siblings ...)
2010-02-10 13:42 ` D. Can Celasun
@ 2010-02-10 14:44 ` Jean Delvare
2010-02-10 15:03 ` D. Can Celasun
` (8 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-10 14:44 UTC (permalink / raw)
To: lm-sensors
On Wed, 10 Feb 2010 15:42:44 +0200, D. Can Celasun wrote:
> Seems like I'll be waiting for an updated coretemp.
>
> As for the kernel logs, couldn't see anything relevant but in case I'm
> missing something, kernel log is attached.
The kernel log doesn't seem to contain all the messages since last
boot. You should be able to regenerate the relevant messages by
unloading the i2c-i801 driver and loading it again.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (4 preceding siblings ...)
2010-02-10 14:44 ` Jean Delvare
@ 2010-02-10 15:03 ` D. Can Celasun
2010-02-10 18:01 ` Darrick J. Wong
` (7 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-10 15:03 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 971 bytes --]
Here's the relevant output:
Feb 10 17:00:49 dcclinux kernel: ACPI: I/O resource 0000:00:1f.3
[0x1840-0x185f] conflicts with ACPI region SMBI [0x1840-0x184f]
Feb 10 17:00:49 dcclinux kernel: ACPI: If an ACPI driver is available for
this device, you should use it instead of the native driver
So I guess that's it for the SMBus. I'll be waiting for a coretemp patch for
the cpu.
Thanks for the help.
On 10 February 2010 16:44, Jean Delvare <khali@linux-fr.org> wrote:
> On Wed, 10 Feb 2010 15:42:44 +0200, D. Can Celasun wrote:
> > Seems like I'll be waiting for an updated coretemp.
> >
> > As for the kernel logs, couldn't see anything relevant but in case I'm
> > missing something, kernel log is attached.
>
> The kernel log doesn't seem to contain all the messages since last
> boot. You should be able to regenerate the relevant messages by
> unloading the i2c-i801 driver and loading it again.
>
> --
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>
[-- Attachment #1.2: Type: text/html, Size: 1505 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (5 preceding siblings ...)
2010-02-10 15:03 ` D. Can Celasun
@ 2010-02-10 18:01 ` Darrick J. Wong
2010-02-10 18:07 ` D. Can Celasun
` (6 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: Darrick J. Wong @ 2010-02-10 18:01 UTC (permalink / raw)
To: lm-sensors
On Wed, Feb 10, 2010 at 05:03:00PM +0200, D. Can Celasun wrote:
> Here's the relevant output:
>
> Feb 10 17:00:49 dcclinux kernel: ACPI: I/O resource 0000:00:1f.3
> [0x1840-0x185f] conflicts with ACPI region SMBI [0x1840-0x184f]
> Feb 10 17:00:49 dcclinux kernel: ACPI: If an ACPI driver is available for
> this device, you should use it instead of the native driver
>
> So I guess that's it for the SMBus. I'll be waiting for a coretemp patch for
> the cpu.
You might also try the i2c-scmi driver.... if the BIOS is set up correctly.
I don't remember when it went in the kernel other than it was in the 2.6.32/33
timeframe.
--D
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (6 preceding siblings ...)
2010-02-10 18:01 ` Darrick J. Wong
@ 2010-02-10 18:07 ` D. Can Celasun
2010-02-10 19:40 ` Jean Delvare
` (5 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-10 18:07 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 863 bytes --]
I can load the i2c-scmi driver, here is the relevant kernel log:
Feb 10 20:04:52 dcclinux kernel: i2c /dev entries driver
On 10 February 2010 20:01, Darrick J. Wong <djwong@us.ibm.com> wrote:
> On Wed, Feb 10, 2010 at 05:03:00PM +0200, D. Can Celasun wrote:
> > Here's the relevant output:
> >
> > Feb 10 17:00:49 dcclinux kernel: ACPI: I/O resource 0000:00:1f.3
> > [0x1840-0x185f] conflicts with ACPI region SMBI [0x1840-0x184f]
> > Feb 10 17:00:49 dcclinux kernel: ACPI: If an ACPI driver is available for
> > this device, you should use it instead of the native driver
> >
> > So I guess that's it for the SMBus. I'll be waiting for a coretemp patch
> for
> > the cpu.
>
> You might also try the i2c-scmi driver.... if the BIOS is set up correctly.
> I don't remember when it went in the kernel other than it was in the
> 2.6.32/33
> timeframe.
>
> --D
>
[-- Attachment #1.2: Type: text/html, Size: 1271 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (7 preceding siblings ...)
2010-02-10 18:07 ` D. Can Celasun
@ 2010-02-10 19:40 ` Jean Delvare
2010-02-10 20:23 ` D. Can Celasun
` (4 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-10 19:40 UTC (permalink / raw)
To: lm-sensors
> On 10 February 2010 20:01, Darrick J. Wong <djwong@us.ibm.com> wrote:
> > You might also try the i2c-scmi driver.... if the BIOS is set up correctly.
> > I don't remember when it went in the kernel other than it was in the
> > 2.6.32/33
> > timeframe.
The i2c-scmi driver was added in the 2.6.32 kernel.
On Wed, 10 Feb 2010 20:07:44 +0200, D. Can Celasun wrote:
> I can load the i2c-scmi driver, here is the relevant kernel log:
>
> Feb 10 20:04:52 dcclinux kernel: i2c /dev entries driver
This message is from i2c-dev, not i2c-scmi.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (8 preceding siblings ...)
2010-02-10 19:40 ` Jean Delvare
@ 2010-02-10 20:23 ` D. Can Celasun
2010-02-11 1:21 ` Darrick J. Wong
` (3 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-10 20:23 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 718 bytes --]
On 10 February 2010 21:40, Jean Delvare <khali@linux-fr.org> wrote:
> > On 10 February 2010 20:01, Darrick J. Wong <djwong@us.ibm.com> wrote:
> > > You might also try the i2c-scmi driver.... if the BIOS is set up
> correctly.
> > > I don't remember when it went in the kernel other than it was in the
> > > 2.6.32/33
> > > timeframe.
>
> The i2c-scmi driver was added in the 2.6.32 kernel.
>
> On Wed, 10 Feb 2010 20:07:44 +0200, D. Can Celasun wrote:
> > I can load the i2c-scmi driver, here is the relevant kernel log:
> >
> > Feb 10 20:04:52 dcclinux kernel: i2c /dev entries driver
>
> This message is from i2c-dev, not i2c-scmi.
>
> Then i2c-scmi doesn't raise any messages in kernel log.
> --
> Jean Delvare
>
[-- Attachment #1.2: Type: text/html, Size: 1377 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (9 preceding siblings ...)
2010-02-10 20:23 ` D. Can Celasun
@ 2010-02-11 1:21 ` Darrick J. Wong
2010-02-11 7:33 ` D. Can Celasun
` (2 subsequent siblings)
13 siblings, 0 replies; 25+ messages in thread
From: Darrick J. Wong @ 2010-02-11 1:21 UTC (permalink / raw)
To: lm-sensors
On Wed, Feb 10, 2010 at 10:23:00PM +0200, D. Can Celasun wrote:
> On 10 February 2010 21:40, Jean Delvare <khali@linux-fr.org> wrote:
>
> > > On 10 February 2010 20:01, Darrick J. Wong <djwong@us.ibm.com> wrote:
> > > > You might also try the i2c-scmi driver.... if the BIOS is set up
> > correctly.
> > > > I don't remember when it went in the kernel other than it was in the
> > > > 2.6.32/33
> > > > timeframe.
> >
> > The i2c-scmi driver was added in the 2.6.32 kernel.
> >
> > On Wed, 10 Feb 2010 20:07:44 +0200, D. Can Celasun wrote:
> > > I can load the i2c-scmi driver, here is the relevant kernel log:
> > >
> > > Feb 10 20:04:52 dcclinux kernel: i2c /dev entries driver
> >
> > This message is from i2c-dev, not i2c-scmi.
> >
> > Then i2c-scmi doesn't raise any messages in kernel log.
Does sensors-detect/i2cdetect find anything on either i2c controller?
--D
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (10 preceding siblings ...)
2010-02-11 1:21 ` Darrick J. Wong
@ 2010-02-11 7:33 ` D. Can Celasun
2010-02-11 8:17 ` Jean Delvare
2010-02-11 16:42 ` D. Can Celasun
13 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-11 7:33 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1225 bytes --]
Relevant sensors-detect output:
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
On 11 February 2010 03:21, Darrick J. Wong <djwong@us.ibm.com> wrote:
> On Wed, Feb 10, 2010 at 10:23:00PM +0200, D. Can Celasun wrote:
> > On 10 February 2010 21:40, Jean Delvare <khali@linux-fr.org> wrote:
> >
> > > > On 10 February 2010 20:01, Darrick J. Wong <djwong@us.ibm.com>
> wrote:
> > > > > You might also try the i2c-scmi driver.... if the BIOS is set up
> > > correctly.
> > > > > I don't remember when it went in the kernel other than it was in
> the
> > > > > 2.6.32/33
> > > > > timeframe.
> > >
> > > The i2c-scmi driver was added in the 2.6.32 kernel.
> > >
> > > On Wed, 10 Feb 2010 20:07:44 +0200, D. Can Celasun wrote:
> > > > I can load the i2c-scmi driver, here is the relevant kernel log:
> > > >
> > > > Feb 10 20:04:52 dcclinux kernel: i2c /dev entries driver
> > >
> > > This message is from i2c-dev, not i2c-scmi.
> > >
> > > Then i2c-scmi doesn't raise any messages in kernel log.
>
> Does sensors-detect/i2cdetect find anything on either i2c controller?
>
> --D
>
[-- Attachment #1.2: Type: text/html, Size: 1894 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (11 preceding siblings ...)
2010-02-11 7:33 ` D. Can Celasun
@ 2010-02-11 8:17 ` Jean Delvare
2010-02-11 16:42 ` D. Can Celasun
13 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-11 8:17 UTC (permalink / raw)
To: lm-sensors
> On 11 February 2010 03:21, Darrick J. Wong <djwong@us.ibm.com> wrote:
> > Does sensors-detect/i2cdetect find anything on either i2c controller?
On Thu, 11 Feb 2010 09:33:06 +0200, D. Can Celasun wrote:
> Relevant sensors-detect output:
>
> Do you want to probe the I2C/SMBus adapters now? (YES/no):
> Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> Sorry, no supported PCI bus adapters found.
> Module i2c-dev loaded successfully.
At that time, the i2c-i801 driver was loaded but not the i2c-scmi
driver. The i2c-i801 driver is hopeless (can't bind to the device). You
could try loading the i2c-scmi driver manually and running
sensors-detect again.
Darrick, any chance we could get the i2c-scmi driver to load
automatically on systems which need it?
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
` (12 preceding siblings ...)
2010-02-11 8:17 ` Jean Delvare
@ 2010-02-11 16:42 ` D. Can Celasun
2010-02-12 18:52 ` Darrick J. Wong
13 siblings, 1 reply; 25+ messages in thread
From: D. Can Celasun @ 2010-02-11 16:42 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]
On 11 February 2010 10:17, Jean Delvare <khali@linux-fr.org> wrote:
> > On 11 February 2010 03:21, Darrick J. Wong <djwong@us.ibm.com> wrote:
> > > Does sensors-detect/i2cdetect find anything on either i2c controller?
>
> On Thu, 11 Feb 2010 09:33:06 +0200, D. Can Celasun wrote:
> > Relevant sensors-detect output:
> >
> > Do you want to probe the I2C/SMBus adapters now? (YES/no):
> > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> > Sorry, no supported PCI bus adapters found.
> > Module i2c-dev loaded successfully.
>
> At that time, the i2c-i801 driver was loaded but not the i2c-scmi
> driver. The i2c-i801 driver is hopeless (can't bind to the device). You
> could try loading the i2c-scmi driver manually and running
> sensors-detect again.
>
> Tried that, doesn't make any difference.
> Darrick, any chance we could get the i2c-scmi driver to load
> automatically on systems which need it?
>
> --
> Jean Delvare
>
[-- Attachment #1.2: Type: text/html, Size: 1591 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-11 16:42 ` D. Can Celasun
@ 2010-02-12 18:52 ` Darrick J. Wong
0 siblings, 0 replies; 25+ messages in thread
From: Darrick J. Wong @ 2010-02-12 18:52 UTC (permalink / raw)
To: D. Can Celasun; +Cc: Jean Delvare, Huaxu Wan, lm-sensors, linux-acpi, lenb
On Thu, Feb 11, 2010 at 06:42:28PM +0200, D. Can Celasun wrote:
> On 11 February 2010 10:17, Jean Delvare <khali@linux-fr.org> wrote:
>
> > > On 11 February 2010 03:21, Darrick J. Wong <djwong@us.ibm.com> wrote:
> > > > Does sensors-detect/i2cdetect find anything on either i2c controller?
> >
> > On Thu, 11 Feb 2010 09:33:06 +0200, D. Can Celasun wrote:
> > > Relevant sensors-detect output:
> > >
> > > Do you want to probe the I2C/SMBus adapters now? (YES/no):
> > > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> > > Sorry, no supported PCI bus adapters found.
> > > Module i2c-dev loaded successfully.
> >
> > At that time, the i2c-i801 driver was loaded but not the i2c-scmi
> > driver. The i2c-i801 driver is hopeless (can't bind to the device). You
> > could try loading the i2c-scmi driver manually and running
> > sensors-detect again.
> >
> > Tried that, doesn't make any difference.
>
>
> > Darrick, any chance we could get the i2c-scmi driver to load
> > automatically on systems which need it?
I think all we need to do is add:
MODULE_DEVICE_TABLE(acpi, fan_device_ids);
to i2c-scmi.c, which will add the appropriate aliases to the module info.
That reminds me, I don't think that patch to add ACPI_SMBUS_IBM_HID to the ACPI
header files ever went in, did it? It doesn't seem to be in 2.6.33-rc7, but
maybe it's queued in someone else's ACPI tree for .34? If it's not, then I'd
imagine it's still blocking the patchset to i2c-scmi that works around broken
IBM BIOSes, so I'm hoping someone from the ACPI part of the world can comment?
--D
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
@ 2010-02-12 18:52 ` Darrick J. Wong
0 siblings, 0 replies; 25+ messages in thread
From: Darrick J. Wong @ 2010-02-12 18:52 UTC (permalink / raw)
To: D. Can Celasun; +Cc: Jean Delvare, Huaxu Wan, lm-sensors, linux-acpi, lenb
On Thu, Feb 11, 2010 at 06:42:28PM +0200, D. Can Celasun wrote:
> On 11 February 2010 10:17, Jean Delvare <khali@linux-fr.org> wrote:
>
> > > On 11 February 2010 03:21, Darrick J. Wong <djwong@us.ibm.com> wrote:
> > > > Does sensors-detect/i2cdetect find anything on either i2c controller?
> >
> > On Thu, 11 Feb 2010 09:33:06 +0200, D. Can Celasun wrote:
> > > Relevant sensors-detect output:
> > >
> > > Do you want to probe the I2C/SMBus adapters now? (YES/no):
> > > Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
> > > Sorry, no supported PCI bus adapters found.
> > > Module i2c-dev loaded successfully.
> >
> > At that time, the i2c-i801 driver was loaded but not the i2c-scmi
> > driver. The i2c-i801 driver is hopeless (can't bind to the device). You
> > could try loading the i2c-scmi driver manually and running
> > sensors-detect again.
> >
> > Tried that, doesn't make any difference.
>
>
> > Darrick, any chance we could get the i2c-scmi driver to load
> > automatically on systems which need it?
I think all we need to do is add:
MODULE_DEVICE_TABLE(acpi, fan_device_ids);
to i2c-scmi.c, which will add the appropriate aliases to the module info.
That reminds me, I don't think that patch to add ACPI_SMBUS_IBM_HID to the ACPI
header files ever went in, did it? It doesn't seem to be in 2.6.33-rc7, but
maybe it's queued in someone else's ACPI tree for .34? If it's not, then I'd
imagine it's still blocking the patchset to i2c-scmi that works around broken
IBM BIOSes, so I'm hoping someone from the ACPI part of the world can comment?
--D
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
2010-02-12 18:52 ` Darrick J. Wong
@ 2010-02-12 19:09 ` Jean Delvare
-1 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-12 19:09 UTC (permalink / raw)
To: djwong; +Cc: D. Can Celasun, Huaxu Wan, lm-sensors, linux-acpi, lenb
On Fri, 12 Feb 2010 10:52:41 -0800, Darrick J. Wong wrote:
> On Thu, Feb 11, 2010 at 06:42:28PM +0200, D. Can Celasun wrote:
> > On 11 February 2010 10:17, Jean Delvare <khali@linux-fr.org> wrote:
> > > Darrick, any chance we could get the i2c-scmi driver to load
> > > automatically on systems which need it?
>
> I think all we need to do is add:
>
> MODULE_DEVICE_TABLE(acpi, fan_device_ids);
I guess you mean:
MODULE_DEVICE_TABLE(acpi, acpi_smbus_cmi_ids);
>
> to i2c-scmi.c, which will add the appropriate aliases to the module info.
OK. Care to send a patch?
> That reminds me, I don't think that patch to add ACPI_SMBUS_IBM_HID to the ACPI
> header files ever went in, did it? It doesn't seem to be in 2.6.33-rc7, but
> maybe it's queued in someone else's ACPI tree for .34?
I have pinged Bjorn and Len twice already (December 17th, January 5th)
but never heard back.
> If it's not, then I'd
> imagine it's still blocking the patchset to i2c-scmi that works around broken
> IBM BIOSes, so I'm hoping someone from the ACPI part of the world can comment?
Yes it is blocking the i2c-scmi patch. And yes, please ACPI people take
care of it ASAP.
--
Jean Delvare
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
@ 2010-02-12 19:09 ` Jean Delvare
0 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-12 19:09 UTC (permalink / raw)
To: djwong; +Cc: D. Can Celasun, Huaxu Wan, lm-sensors, linux-acpi, lenb
On Fri, 12 Feb 2010 10:52:41 -0800, Darrick J. Wong wrote:
> On Thu, Feb 11, 2010 at 06:42:28PM +0200, D. Can Celasun wrote:
> > On 11 February 2010 10:17, Jean Delvare <khali@linux-fr.org> wrote:
> > > Darrick, any chance we could get the i2c-scmi driver to load
> > > automatically on systems which need it?
>
> I think all we need to do is add:
>
> MODULE_DEVICE_TABLE(acpi, fan_device_ids);
I guess you mean:
MODULE_DEVICE_TABLE(acpi, acpi_smbus_cmi_ids);
>
> to i2c-scmi.c, which will add the appropriate aliases to the module info.
OK. Care to send a patch?
> That reminds me, I don't think that patch to add ACPI_SMBUS_IBM_HID to the ACPI
> header files ever went in, did it? It doesn't seem to be in 2.6.33-rc7, but
> maybe it's queued in someone else's ACPI tree for .34?
I have pinged Bjorn and Len twice already (December 17th, January 5th)
but never heard back.
> If it's not, then I'd
> imagine it's still blocking the patchset to i2c-scmi that works around broken
> IBM BIOSes, so I'm hoping someone from the ACPI part of the world can comment?
Yes it is blocking the i2c-scmi patch. And yes, please ACPI people take
care of it ASAP.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* [PATCH] i2c-scmi: Provide module aliases for automatic loading
2010-02-12 19:09 ` Jean Delvare
@ 2010-02-12 21:51 ` Darrick J. Wong
-1 siblings, 0 replies; 25+ messages in thread
From: Darrick J. Wong @ 2010-02-12 21:51 UTC (permalink / raw)
To: Jean Delvare; +Cc: D. Can Celasun, Huaxu Wan, lm-sensors, linux-acpi, lenb
Ok, here's a quick patch to provide the module aliases. Lightly tested, and
requires the patch that defines ACPI_SMBUS_IBM_HID.
---
i2c-scmi: Provide module aliases for automatic loading
Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
---
drivers/i2c/busses/i2c-scmi.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/i2c/busses/i2c-scmi.c b/drivers/i2c/busses/i2c-scmi.c
index 4c9fb4c..388cbdc 100644
--- a/drivers/i2c/busses/i2c-scmi.c
+++ b/drivers/i2c/busses/i2c-scmi.c
@@ -54,6 +54,7 @@ static const struct acpi_device_id acpi_smbus_cmi_ids[] = {
{ACPI_SMBUS_IBM_HID, (kernel_ulong_t)&ibm_smbus_methods},
{"", 0}
};
+MODULE_DEVICE_TABLE(acpi, acpi_smbus_cmi_ids);
#define ACPI_SMBUS_STATUS_OK 0x00
#define ACPI_SMBUS_STATUS_FAIL 0x07
^ permalink raw reply related [flat|nested] 25+ messages in thread
* [lm-sensors] [PATCH] i2c-scmi: Provide module aliases for automatic
@ 2010-02-12 21:51 ` Darrick J. Wong
0 siblings, 0 replies; 25+ messages in thread
From: Darrick J. Wong @ 2010-02-12 21:51 UTC (permalink / raw)
To: Jean Delvare; +Cc: D. Can Celasun, Huaxu Wan, lm-sensors, linux-acpi, lenb
Ok, here's a quick patch to provide the module aliases. Lightly tested, and
requires the patch that defines ACPI_SMBUS_IBM_HID.
---
i2c-scmi: Provide module aliases for automatic loading
Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
---
drivers/i2c/busses/i2c-scmi.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/i2c/busses/i2c-scmi.c b/drivers/i2c/busses/i2c-scmi.c
index 4c9fb4c..388cbdc 100644
--- a/drivers/i2c/busses/i2c-scmi.c
+++ b/drivers/i2c/busses/i2c-scmi.c
@@ -54,6 +54,7 @@ static const struct acpi_device_id acpi_smbus_cmi_ids[] = {
{ACPI_SMBUS_IBM_HID, (kernel_ulong_t)&ibm_smbus_methods},
{"", 0}
};
+MODULE_DEVICE_TABLE(acpi, acpi_smbus_cmi_ids);
#define ACPI_SMBUS_STATUS_OK 0x00
#define ACPI_SMBUS_STATUS_FAIL 0x07
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply related [flat|nested] 25+ messages in thread
* Re: [PATCH] i2c-scmi: Provide module aliases for automatic loading
2010-02-12 21:51 ` [lm-sensors] [PATCH] i2c-scmi: Provide module aliases for automatic Darrick J. Wong
@ 2010-02-13 13:59 ` Jean Delvare
-1 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-13 13:59 UTC (permalink / raw)
To: djwong; +Cc: D. Can Celasun, Huaxu Wan, lm-sensors, linux-acpi, lenb
On Fri, 12 Feb 2010 13:51:21 -0800, Darrick J. Wong wrote:
> Ok, here's a quick patch to provide the module aliases. Lightly tested, and
> requires the patch that defines ACPI_SMBUS_IBM_HID.
> ---
> i2c-scmi: Provide module aliases for automatic loading
>
> Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
> ---
>
> drivers/i2c/busses/i2c-scmi.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
>
> diff --git a/drivers/i2c/busses/i2c-scmi.c b/drivers/i2c/busses/i2c-scmi.c
> index 4c9fb4c..388cbdc 100644
> --- a/drivers/i2c/busses/i2c-scmi.c
> +++ b/drivers/i2c/busses/i2c-scmi.c
> @@ -54,6 +54,7 @@ static const struct acpi_device_id acpi_smbus_cmi_ids[] = {
> {ACPI_SMBUS_IBM_HID, (kernel_ulong_t)&ibm_smbus_methods},
> {"", 0}
> };
> +MODULE_DEVICE_TABLE(acpi, acpi_smbus_cmi_ids);
>
> #define ACPI_SMBUS_STATUS_OK 0x00
> #define ACPI_SMBUS_STATUS_FAIL 0x07
Applied, thanks.
--
Jean Delvare
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] [PATCH] i2c-scmi: Provide module aliases for
@ 2010-02-13 13:59 ` Jean Delvare
0 siblings, 0 replies; 25+ messages in thread
From: Jean Delvare @ 2010-02-13 13:59 UTC (permalink / raw)
To: djwong; +Cc: D. Can Celasun, Huaxu Wan, lm-sensors, linux-acpi, lenb
On Fri, 12 Feb 2010 13:51:21 -0800, Darrick J. Wong wrote:
> Ok, here's a quick patch to provide the module aliases. Lightly tested, and
> requires the patch that defines ACPI_SMBUS_IBM_HID.
> ---
> i2c-scmi: Provide module aliases for automatic loading
>
> Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
> ---
>
> drivers/i2c/busses/i2c-scmi.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
>
> diff --git a/drivers/i2c/busses/i2c-scmi.c b/drivers/i2c/busses/i2c-scmi.c
> index 4c9fb4c..388cbdc 100644
> --- a/drivers/i2c/busses/i2c-scmi.c
> +++ b/drivers/i2c/busses/i2c-scmi.c
> @@ -54,6 +54,7 @@ static const struct acpi_device_id acpi_smbus_cmi_ids[] = {
> {ACPI_SMBUS_IBM_HID, (kernel_ulong_t)&ibm_smbus_methods},
> {"", 0}
> };
> +MODULE_DEVICE_TABLE(acpi, acpi_smbus_cmi_ids);
>
> #define ACPI_SMBUS_STATUS_OK 0x00
> #define ACPI_SMBUS_STATUS_FAIL 0x07
Applied, thanks.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Core i3 support?
2010-02-12 19:09 ` Jean Delvare
@ 2010-02-19 21:56 ` D. Can Celasun
-1 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-19 21:56 UTC (permalink / raw)
To: Jean Delvare; +Cc: linux-acpi, lm-sensors, Huaxu Wan, lenb
[-- Attachment #1.1: Type: text/plain, Size: 18 bytes --]
Any news on this?
[-- Attachment #1.2: Type: text/html, Size: 22 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [lm-sensors] Core i3 support?
@ 2010-02-19 21:56 ` D. Can Celasun
0 siblings, 0 replies; 25+ messages in thread
From: D. Can Celasun @ 2010-02-19 21:56 UTC (permalink / raw)
To: Jean Delvare; +Cc: linux-acpi, lm-sensors, Huaxu Wan, lenb
[-- Attachment #1.1: Type: text/plain, Size: 18 bytes --]
Any news on this?
[-- Attachment #1.2: Type: text/html, Size: 22 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2010-02-19 21:56 UTC | newest]
Thread overview: 25+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-10 11:00 [lm-sensors] Core i3 support? D. Can Celasun
2010-02-10 12:25 ` Jean Delvare
2010-02-10 12:28 ` D. Can Celasun
2010-02-10 13:21 ` Jean Delvare
2010-02-10 13:42 ` D. Can Celasun
2010-02-10 14:44 ` Jean Delvare
2010-02-10 15:03 ` D. Can Celasun
2010-02-10 18:01 ` Darrick J. Wong
2010-02-10 18:07 ` D. Can Celasun
2010-02-10 19:40 ` Jean Delvare
2010-02-10 20:23 ` D. Can Celasun
2010-02-11 1:21 ` Darrick J. Wong
2010-02-11 7:33 ` D. Can Celasun
2010-02-11 8:17 ` Jean Delvare
2010-02-11 16:42 ` D. Can Celasun
2010-02-12 18:52 ` Darrick J. Wong
2010-02-12 18:52 ` Darrick J. Wong
2010-02-12 19:09 ` Jean Delvare
2010-02-12 19:09 ` Jean Delvare
2010-02-12 21:51 ` [PATCH] i2c-scmi: Provide module aliases for automatic loading Darrick J. Wong
2010-02-12 21:51 ` [lm-sensors] [PATCH] i2c-scmi: Provide module aliases for automatic Darrick J. Wong
2010-02-13 13:59 ` [PATCH] i2c-scmi: Provide module aliases for automatic loading Jean Delvare
2010-02-13 13:59 ` [lm-sensors] [PATCH] i2c-scmi: Provide module aliases for Jean Delvare
2010-02-19 21:56 ` Core i3 support? D. Can Celasun
2010-02-19 21:56 ` [lm-sensors] " D. Can Celasun
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.