* PROBLEM: tickless scheduling
@ 2010-05-11 0:18 Donald Allen
2010-05-11 0:27 ` Robert Hancock
2010-05-11 0:54 ` john stultz
0 siblings, 2 replies; 23+ messages in thread
From: Donald Allen @ 2010-05-11 0:18 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
1. Network file transfers and fscks stop on Toshiba netbook unless
system receives external events
2. I have a new Toshiba NB305 on which I installed the beta release of
Slackware 13.1, which provides a 2.6.33.3 kernel with the tickless
option enabled. With this machine on my ethernet, I attempted to rsync
my home directory to it, about 9 Gb, from a workstation that is my
primary system (running Slackware 13). The transfer proceeded normally
for awhile and then stopped, which I could see in the xterm on the
workstation. I went to the netbook to see what was going on there and
when I began typing, the transfer resumed. I ran 'top' on the netbook
and it would freeze after a few updates, coinciding with the file
transfer pausing again. Typing would get things moving. At another
point, I tested pm-suspend on the netbook. Suspending worked, but
awakening did not, so I had to power-cycle the machine. I use ext2 for
reasons which I won't attempt to justify here, so when the machine
came back up, it fsck'ed the root filesystem. Here again I saw things
grind to a halt -- the progress meter stopped and the there was no
disk activity. But if I moved my finger on the touchpad, things would
get moving again. The only way to get the fsck to complete was to
constantly be tickling the touchpad. I corresponded with Patrick
Volkerding, telling him I suspected a scheduling problem and he
informed me that the 13.1 kernel had tickless enabled, unlike 13. So I
built a 2.6.33.3 kernel (from the Slackware-supplied kernel sources)
with tickless disabled. With that kernel running, I power-cycled the
machine to force a fsck of the root filesystem. This one proceeded to
completion normally -- no external stimuli needed.
3. Tickless, scheduler
4. 2.6.33.3
7.1 ver_linux output attached
7.2 /proc/cpuinfo attached
7.3 /proc/modules attached
7.4 /proc/ioports, /proc/iomem attached
7.5 lspci attached
7.6 /proc/scsi/scsi attached
[-- Attachment #2: ver_linux --]
[-- Type: application/octet-stream, Size: 1414 bytes --]
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux olympia 2.6.33.3 #1 Sun May 9 17:48:03 EDT 2010 x86_64 Intel(R) Atom(TM) CPU N450 @ 1.66GHz GenuineIntel GNU/Linux
Gnu C 4.4.3
Gnu make 3.81
binutils 2.20.51.0.8.20100412
util-linux 2.17.2
mount support
module-init-tools 3.11.1
e2fsprogs 1.41.11
jfsutils 1.1.14
reiserfsprogs 3.6.21
xfsprogs 3.1.1
pcmciautils 015
quota-tools 3.17.
PPP 2.4.5
Linux C Library 2.11.1
Dynamic linker (ldd) 2.11.1
Procps 3.2.7
Net-tools 1.60
Kbd 1.15.2
oprofile 0.9.6
Sh-utils 8.5
wireless-tools 29
Modules Loaded snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 cpufreq_ondemand acpi_cpufreq freq_table ath9k usb_storage ath9k_common i915 mac80211 drm_kms_helper snd_hda_intel snd_hda_codec drm ath9k_hw thermal processor rtc_cmos snd_hwdep i2c_algo_bit i2c_i801 ath rtc_core snd_pcm video rtc_lib thermal_sys intel_agp uhci_hcd snd_timer battery ac button hwmon i2c_core sg output psmouse snd agpgart ehci_hcd cfg80211 evdev soundcore snd_page_alloc led_class
[-- Attachment #3: cpuinfo --]
[-- Type: application/octet-stream, Size: 618 bytes --]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 28
model name : Intel(R) Atom(TM) CPU N450 @ 1.66GHz
stepping : 10
cpu MHz : 1000.000
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm
bogomips : 3324.77
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 48 bits virtual
power management:
[-- Attachment #4: modules --]
[-- Type: application/octet-stream, Size: 2851 bytes --]
snd_seq_dummy 1487 0 - Live 0xffffffffa0368000
snd_seq_oss 28735 0 - Live 0xffffffffa0359000
snd_seq_midi_event 5332 1 snd_seq_oss, Live 0xffffffffa0352000
snd_seq 48034 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event, Live 0xffffffffa033d000
snd_seq_device 5459 3 snd_seq_dummy,snd_seq_oss,snd_seq, Live 0xffffffffa0336000
snd_pcm_oss 39751 0 - Live 0xffffffffa0325000
snd_mixer_oss 15990 1 snd_pcm_oss, Live 0xffffffffa031b000
ipv6 267123 18 - Live 0xffffffffa02c6000
cpufreq_ondemand 7941 1 - Live 0xffffffffa02be000
acpi_cpufreq 4784 1 - Live 0xffffffffa02a9000
freq_table 2411 2 cpufreq_ondemand,acpi_cpufreq, Live 0xffffffffa02a3000
ath9k 73214 0 - Live 0xffffffffa0288000
usb_storage 42444 0 - Live 0xffffffffa0273000
ath9k_common 2441 1 ath9k, Live 0xffffffffa00a4000
i915 291335 2 - Live 0xffffffffa0217000
mac80211 166507 2 ath9k,ath9k_common, Live 0xffffffffa01e1000
drm_kms_helper 24087 1 i915, Live 0xffffffffa01d4000
snd_hda_intel 21448 0 - Live 0xffffffffa01c7000
snd_hda_codec 64903 1 snd_hda_intel, Live 0xffffffffa01ad000
drm 161995 3 i915,drm_kms_helper, Live 0xffffffffa0175000
ath9k_hw 219395 2 ath9k,ath9k_common, Live 0xffffffffa0134000
thermal 12593 0 - Live 0xffffffffa012a000
processor 26467 2 acpi_cpufreq, Live 0xffffffffa011c000
rtc_cmos 8917 0 - Live 0xffffffffa00c6000
snd_hwdep 6392 1 snd_hda_codec, Live 0xffffffffa00b5000
i2c_algo_bit 5175 1 i915, Live 0xffffffffa0095000
i2c_i801 8595 0 - Live 0xffffffffa008b000
ath 8844 2 ath9k,ath9k_hw, Live 0xffffffffa0054000
rtc_core 14154 1 rtc_cmos, Live 0xffffffffa0062000
snd_pcm 69435 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec, Live 0xffffffffa0105000
video 18977 1 i915, Live 0xffffffffa003f000
rtc_lib 1922 1 rtc_core, Live 0xffffffffa0003000
thermal_sys 14036 3 thermal,processor,video, Live 0xffffffffa00fb000
intel_agp 27267 1 - Live 0xffffffffa00ed000
uhci_hcd 21348 0 - Live 0xffffffffa00e1000
snd_timer 18484 2 snd_seq,snd_pcm, Live 0xffffffffa00d6000
battery 9884 0 - Live 0xffffffffa00cd000
ac 3171 0 - Live 0xffffffffa00bf000
button 4925 1 i915, Live 0xffffffffa00b8000
hwmon 1329 1 thermal_sys, Live 0xffffffffa00b2000
i2c_core 18495 5 i915,drm_kms_helper,drm,i2c_algo_bit,i2c_i801, Live 0xffffffffa00a6000
sg 24927 0 - Live 0xffffffffa0098000
output 1964 1 video, Live 0xffffffffa0092000
psmouse 39024 0 - Live 0xffffffffa007f000
snd 56436 10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer, Live 0xffffffffa0067000
agpgart 29048 2 drm,intel_agp, Live 0xffffffffa0058000
ehci_hcd 35310 0 - Live 0xffffffffa0049000
cfg80211 127647 4 ath9k,ath9k_common,mac80211,ath, Live 0xffffffffa001d000
evdev 9006 8 - Live 0xffffffffa0014000
soundcore 5519 1 snd, Live 0xffffffffa000d000
snd_page_alloc 7113 2 snd_hda_intel,snd_pcm, Live 0xffffffffa0006000
led_class 2785 1 ath9k, Live 0xffffffffa0000000
[-- Attachment #5: ioports --]
[-- Type: application/octet-stream, Size: 1156 bytes --]
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0070-0071 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
03c0-03df : vga+
04d0-04d1 : pnp 00:01
0800-080f : pnp 00:01
0cf8-0cff : PCI conf1
1000-107f : pnp 00:01
1000-1003 : ACPI PM1a_EVT_BLK
1004-1005 : ACPI PM1a_CNT_BLK
1008-100b : ACPI PM_TMR
1010-1015 : ACPI CPU throttle
1020-1020 : ACPI PM2_CNT_BLK
1028-102f : ACPI GPE0_BLK
1180-11bf : pnp 00:01
164e-174c : pnp 00:01
1820-183f : 0000:00:1d.0
1820-183f : uhci_hcd
1840-185f : 0000:00:1d.1
1840-185f : uhci_hcd
1860-187f : 0000:00:1d.2
1860-187f : uhci_hcd
1880-189f : 0000:00:1d.3
1880-189f : uhci_hcd
18a0-18bf : 0000:00:1f.3
18a0-18bf : i801_smbus
18c0-18cf : 0000:00:1f.2
18c0-18cf : ahci
18d0-18d7 : 0000:00:02.0
18d8-18db : 0000:00:1f.2
18d8-18db : ahci
18dc-18df : 0000:00:1f.2
18dc-18df : ahci
18e0-18e7 : 0000:00:1f.2
18e0-18e7 : ahci
18e8-18ef : 0000:00:1f.2
18e8-18ef : ahci
2000-2fff : PCI Bus 0000:09
2000-20ff : 0000:09:00.0
3000-3fff : PCI Bus 0000:05
4000-4fff : PCI Bus 0000:07
fe00-fe00 : pnp 00:01
[-- Attachment #6: iomem --]
[-- Type: application/octet-stream, Size: 1487 bytes --]
00000000-0009dbff : System RAM
0009dc00-0009ffff : reserved
000dc000-000dffff : reserved
000e4000-000fffff : reserved
00100000-7f5cffff : System RAM
01000000-0136e510 : Kernel code
0136e511-01676e2f : Kernel data
016eb000-0175509f : Kernel bss
7f5d0000-7f5dffff : ACPI Tables
7f5e0000-7f5e2fff : ACPI Non-volatile Storage
7f5e3000-7fffffff : reserved
80000000-801fffff : PCI Bus 0000:05
80200000-803fffff : PCI Bus 0000:05
80400000-805fffff : PCI Bus 0000:07
80600000-809fffff : PCI Bus 0000:09
80a00000-80a03fff : 0000:00:1b.0
80a00000-80a03fff : ICH HD audio
80a04000-80a043ff : 0000:00:1d.7
80a04000-80a043ff : ehci_hcd
80a04400-80a047ff : 0000:00:1f.2
80a04400-80a047ff : ahci
80a05000-80a05fff : Intel Flush Page
d0000000-dfffffff : 0000:00:02.0
e0000000-efffffff : PCI MMCONFIG 0000 [bus 00-ff]
e0000000-efffffff : reserved
e0000000-efffffff : pnp 00:01
f0000000-f00fffff : 0000:00:02.0
f0100000-f01fffff : PCI Bus 0000:07
f0100000-f010ffff : 0000:07:00.0
f0100000-f010ffff : ath9k
f0200000-f027ffff : 0000:00:02.0
f0280000-f02fffff : 0000:00:02.1
f0500000-f05fffff : PCI Bus 0000:09
f0510000-f051ffff : 0000:09:00.0
f0520000-f0520fff : 0000:09:00.0
f0540000-f055ffff : 0000:09:00.0
f8000000-fbffffff : pnp 00:01
fec00000-fec0ffff : reserved
fec00000-fec003ff : IOAPIC 0
fed00000-fed003ff : HPET 0
fed14000-fed17fff : pnp 00:01
fee00000-fee00fff : Local APIC
fee00000-fee00fff : reserved
fef00000-feffffff : pnp 00:01
ff000000-ffffffff : reserved
[-- Attachment #7: lspci --]
[-- Type: application/octet-stream, Size: 22333 bytes --]
00:00.0 Host bridge: Intel Corporation Pineview DMI Bridge
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information <?>
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp
00:02.0 VGA compatible controller: Intel Corporation Pineview Integrated Graphics Controller (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device ff30
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 29
Region 0: Memory at f0200000 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at 18d0 [size=8]
Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at f0000000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0100c Data: 41a1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: i915
Kernel modules: i915
00:02.1 Display controller: Intel Corporation Pineview Integrated Graphics Controller
Subsystem: Toshiba America Info Systems Device ff30
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at f0280000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at 80a00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0100c Data: 4199
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: 80000000-801fffff
Prefetchable memory behind bridge: 0000000080200000-00000000803fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal+ Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled+ Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
Slot # 0, PowerLimit 0.000000; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal+ PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0100c Data: 4161
Capabilities: [90] Subsystem: Toshiba America Info Systems Device ff00
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: f0100000-f01fffff
Prefetchable memory behind bridge: 0000000080400000-00000000805fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal+ Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
Slot # 2, PowerLimit 10.000000; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal+ PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0100c Data: 4169
Capabilities: [90] Subsystem: Toshiba America Info Systems Device ff00
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: 80600000-809fffff
Prefetchable memory behind bridge: 00000000f0500000-00000000f05fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal+ Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #3, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
Slot # 3, PowerLimit 10.000000; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
Changed: MRL- PresDet- LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal+ PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0100c Data: 4171
Capabilities: [90] Subsystem: Toshiba America Info Systems Device ff00
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 23
Region 4: I/O ports at 1820 [size=32]
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 4: I/O ports at 1840 [size=32]
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 4: I/O ports at 1860 [size=32]
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin D routed to IRQ 16
Region 4: I/O ports at 1880 [size=32]
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 23
Region 0: Memory at 80a04000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=11, subordinate=11, sec-latency=32
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Subsystem: Toshiba America Info Systems Device ff00
00:1f.0 ISA bridge: Intel Corporation Tigerpoint LPC Controller (rev 02)
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information <?>
00:1f.2 SATA controller: Intel Corporation 82801GR/GH (ICH7 Family) SATA AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 27
Region 0: I/O ports at 18e8 [size=8]
Region 1: I/O ports at 18dc [size=4]
Region 2: I/O ports at 18e0 [size=8]
Region 3: I/O ports at 18d8 [size=4]
Region 4: I/O ports at 18c0 [size=16]
Region 5: Memory at 80a04400 (32-bit, non-prefetchable) [size=1K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0100c Data: 4181
Capabilities: [70] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
Subsystem: Toshiba America Info Systems Device ff00
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin B routed to IRQ 19
Region 4: I/O ports at 18a0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c-i801
07:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Accton Technology Corporation Device e811
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f0100000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000 Data: 0000
Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB
Capabilities: [100] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP+ BadDLLP- Rollover+ Timeout+ NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12
Capabilities: [170] Power Budgeting <?>
Kernel driver in use: ath9k
Kernel modules: ath9k
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Subsystem: Toshiba America Info Systems Device ff30
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at 2000 [size=256]
Region 2: Memory at f0520000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at f0510000 (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at f0540000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 01
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB
Capabilities: [ac] MSI-X: Enable- Count=2 Masked-
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [cc] Vital Product Data
Unknown small resource type 00, will not decode more.
Capabilities: [100] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP+ BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 01-00-00-00-00-00-00-00
[-- Attachment #8: scsi --]
[-- Type: application/octet-stream, Size: 336 bytes --]
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: FUJITSU MJA2160B Rev: 0040
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: Generic- Model: Multi-Card Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: PROBLEM: tickless scheduling
2010-05-11 0:18 PROBLEM: tickless scheduling Donald Allen
@ 2010-05-11 0:27 ` Robert Hancock
2010-05-11 0:34 ` Donald Allen
2010-05-11 0:54 ` john stultz
1 sibling, 1 reply; 23+ messages in thread
From: Robert Hancock @ 2010-05-11 0:27 UTC (permalink / raw)
To: Donald Allen; +Cc: linux-kernel
On 05/10/2010 06:18 PM, Donald Allen wrote:
> 1. Network file transfers and fscks stop on Toshiba netbook unless
> system receives external events
> 2. I have a new Toshiba NB305 on which I installed the beta release of
> Slackware 13.1, which provides a 2.6.33.3 kernel with the tickless
> option enabled. With this machine on my ethernet, I attempted to rsync
> my home directory to it, about 9 Gb, from a workstation that is my
> primary system (running Slackware 13). The transfer proceeded normally
> for awhile and then stopped, which I could see in the xterm on the
> workstation. I went to the netbook to see what was going on there and
> when I began typing, the transfer resumed. I ran 'top' on the netbook
> and it would freeze after a few updates, coinciding with the file
> transfer pausing again. Typing would get things moving. At another
> point, I tested pm-suspend on the netbook. Suspending worked, but
> awakening did not, so I had to power-cycle the machine. I use ext2 for
> reasons which I won't attempt to justify here, so when the machine
> came back up, it fsck'ed the root filesystem. Here again I saw things
> grind to a halt -- the progress meter stopped and the there was no
> disk activity. But if I moved my finger on the touchpad, things would
> get moving again. The only way to get the fsck to complete was to
> constantly be tickling the touchpad. I corresponded with Patrick
> Volkerding, telling him I suspected a scheduling problem and he
> informed me that the 13.1 kernel had tickless enabled, unlike 13. So I
> built a 2.6.33.3 kernel (from the Slackware-supplied kernel sources)
> with tickless disabled. With that kernel running, I power-cycled the
> machine to force a fsck of the root filesystem. This one proceeded to
> completion normally -- no external stimuli needed.
> 3. Tickless, scheduler
> 4. 2.6.33.3
> 7.1 ver_linux output attached
> 7.2 /proc/cpuinfo attached
> 7.3 /proc/modules attached
> 7.4 /proc/ioports, /proc/iomem attached
> 7.5 lspci attached
> 7.6 /proc/scsi/scsi attached
Can you post dmesg output from bootup?
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-11 0:27 ` Robert Hancock
@ 2010-05-11 0:34 ` Donald Allen
2010-05-11 0:38 ` Robert Hancock
0 siblings, 1 reply; 23+ messages in thread
From: Donald Allen @ 2010-05-11 0:34 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
On Mon, May 10, 2010 at 8:27 PM, Robert Hancock <hancockrwd@gmail.com> wrote:
> On 05/10/2010 06:18 PM, Donald Allen wrote:
>>
>
> Can you post dmesg output from bootup?
See attached.
/Don Allen
>
[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 28533 bytes --]
Linux version 2.6.33.3 (root@olympia) (gcc version 4.4.3 (GCC) ) #1 Sun May 9 17:48:03 EDT 2010
Command line: auto BOOT_IMAGE=Linux ro root=803 vt.default_utf8=0
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009dc00 (usable)
BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000dc000 - 00000000000e0000 (reserved)
BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007f5d0000 (usable)
BIOS-e820: 000000007f5d0000 - 000000007f5e0000 (ACPI data)
BIOS-e820: 000000007f5e0000 - 000000007f5e3000 (ACPI NVS)
BIOS-e820: 000000007f5e3000 - 0000000080000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
NX (Execute Disable) protection: active
DMI present.
No AGP bridge found
last_pfn = 0x7f5d0 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CFFFF write-protect
D0000-DFFFF uncachable
E0000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask 080000000 write-back
1 base 07F600000 mask 0FFE00000 uncachable
2 base 07F800000 mask 0FF800000 uncachable
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
initial memory mapped : 0 - 20000000
init_memory_mapping: 0000000000000000-000000007f5d0000
0000000000 - 007f400000 page 2M
007f400000 - 007f5d0000 page 4k
kernel direct mapping tables up to 7f5d0000 @ 8000-c000
ACPI: RSDP 00000000000f7d00 00024 (v02 TOSCPL)
ACPI: XSDT 000000007f5d4f25 00074 (v01 TOSCPL TOSCPL00 06040000 LTP 00000000)
ACPI: FACP 000000007f5dfc60 000F4 (v03 TOSCPL TOSCPL00 06040000 PTL 00000002)
ACPI: DSDT 000000007f5d60bb 09B31 (v01 TOSCPL TOSCPL00 06040000 MSFT 03000000)
ACPI: FACS 000000007f5e2fc0 00040
ACPI: TCPA 000000007f5dfd54 00032 (v01 Phoeni x 06040000 TL 00000000)
ACPI: HPET 000000007f5dfd86 00038 (v01 DELL M09 06040000 LOHR 0000005A)
ACPI: MCFG 000000007f5dfdbe 0003C (v01 INTEL CRESTLNE 06040000 LOHR 0000005A)
ACPI: SLIC 000000007f5dfdfa 00176 (v01 TOSCPL TOSCPL00 06040000 LOHR 00000000)
ACPI: APIC 000000007f5dff70 00068 (v01 TOSCPL TOSCPL00 06040000 LTP 00000000)
ACPI: BOOT 000000007f5dffd8 00028 (v01 TOSCPL TOSCPL00 06040000 LTP 00000001)
ACPI: SSDT 000000007f5d551b 0025F (v01 PmRef Cpu0Tst 00003000 INTL 20050624)
ACPI: SSDT 000000007f5d5475 000A6 (v01 PmRef Cpu1Tst 00003000 INTL 20050624)
ACPI: SSDT 000000007f5d4f99 004DC (v02 PmRef CpuPm 00003000 INTL 20050624)
ACPI: Local APIC address 0xfee00000
(7 early reservations) ==> bootmem [0000000000 - 007f5d0000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0001000000 - 00017550a0] TEXT DATA BSS ==> [0001000000 - 00017550a0]
#2 [000009dc00 - 0000100000] BIOS reserved ==> [000009dc00 - 0000100000]
#3 [0001756000 - 00017561b0] BRK ==> [0001756000 - 00017561b0]
#4 [0000001000 - 0000003000] TRAMPOLINE ==> [0000001000 - 0000003000]
#5 [0000003000 - 0000007000] ACPI WAKEUP ==> [0000003000 - 0000007000]
#6 [0000008000 - 000000a000] PGTABLE ==> [0000008000 - 000000a000]
[ffffea0000000000-ffffea0001bfffff] PMD -> [ffff880001c00000-ffff8800037fffff] on node 0
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000000 -> 0x0000009d
0: 0x00000100 -> 0x0007f5d0
On node 0 totalpages: 521581
DMA zone: 56 pages used for memmap
DMA zone: 107 pages reserved
DMA zone: 3834 pages, LIFO batch:0
DMA32 zone: 7077 pages used for memmap
DMA32 zone: 510507 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 1/0x1 ignored.
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009d000 - 000000000009e000
PM: Registered nosave memory: 000000000009e000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000dc000
PM: Registered nosave memory: 00000000000dc000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 00000000000e4000
PM: Registered nosave memory: 00000000000e4000 - 0000000000100000
Allocating PCI resources starting at 80000000 (gap: 80000000:60000000)
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 514341
Kernel command line: auto BOOT_IMAGE=Linux ro root=803 vt.default_utf8=0
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Checking aperture...
No AGP bridge found
Memory: 2046288k/2086720k available (3513k kernel code, 396k absent, 39480k reserved, 3106k data, 456k init)
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:288
Extended CMOS year: 2000
Console: colour VGA+ 80x25
console [tty0] enabled
hpet clockevent registered
Fast TSC calibration using PIT
Detected 1662.283 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 3324.56 BogoMIPS (lpj=1662283)
Security Framework initialized
Mount-cache hash table entries: 256
mce: CPU supports 5 MCE banks
CPU0: Thermal monitoring handled by SMI
using mwait in idle threads.
Performance Events: Atom events, Intel PMU driver.
... version: 3
... bit width: 40
... generic registers: 2
... value mask: 000000ffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 0000000700000003
CPU: Intel(R) Atom(TM) CPU N450 @ 1.66GHz stepping 0a
ACPI: Core revision 20091214
ftrace: converting mcount calls to 0f 1f 44 00 00
ftrace: allocating 14901 entries in 59 pages
Setting APIC routing to flat
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
devtmpfs: initialized
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
ACPI: No dock devices found.
ACPI Error (dsfield-0143): [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node ffff88007f014bc0), AE_ALREADY_EXISTS
ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000d3fff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000e0000-0x000e3fff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x80000000-0xf7ffffff] (ignored)
pci_root PNP0A08:00: host bridge window [io 0x0d00-0xfdff] (ignored)
pci 0000:00:02.0: reg 10: [mem 0xf0200000-0xf027ffff]
pci 0000:00:02.0: reg 14: [io 0x18d0-0x18d7]
pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff pref]
pci 0000:00:02.0: reg 1c: [mem 0xf0000000-0xf00fffff]
pci 0000:00:02.1: reg 10: [mem 0xf0280000-0xf02fffff]
pci 0000:00:1b.0: reg 10: [mem 0xf0500000-0xf0503fff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1d.0: reg 20: [io 0x1820-0x183f]
pci 0000:00:1d.1: reg 20: [io 0x1840-0x185f]
pci 0000:00:1d.2: reg 20: [io 0x1860-0x187f]
pci 0000:00:1d.3: reg 20: [io 0x1880-0x189f]
pci 0000:00:1d.7: reg 10: [mem 0xf0504000-0xf05043ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.2: reg 10: [io 0x18e8-0x18ef]
pci 0000:00:1f.2: reg 14: [io 0x18dc-0x18df]
pci 0000:00:1f.2: reg 18: [io 0x18e0-0x18e7]
pci 0000:00:1f.2: reg 1c: [io 0x18d8-0x18db]
pci 0000:00:1f.2: reg 20: [io 0x18c0-0x18cf]
pci 0000:00:1f.2: reg 24: [mem 0xf0504400-0xf05047ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 20: [io 0x18a0-0x18bf]
pci 0000:00:1c.0: PCI bridge to [bus 05-05]
pci 0000:00:1c.0: bridge window [io 0x0000-0x0fff]
pci 0000:07:00.0: reg 10: [mem 0xf0100000-0xf010ffff 64bit]
pci 0000:07:00.0: supports D1
pci 0000:07:00.0: PME# supported from D0 D1 D3hot
pci 0000:07:00.0: PME# disabled
pci 0000:00:1c.1: PCI bridge to [bus 07-07]
pci 0000:00:1c.1: bridge window [mem 0xf0100000-0xf01fffff]
pci 0000:09:00.0: reg 10: [io 0x2000-0x20ff]
pci 0000:09:00.0: reg 18: [mem 0xf0520000-0xf0520fff 64bit pref]
pci 0000:09:00.0: reg 20: [mem 0xf0510000-0xf051ffff 64bit pref]
pci 0000:09:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
pci 0000:09:00.0: supports D1 D2
pci 0000:09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:09:00.0: PME# disabled
pci 0000:00:1c.2: PCI bridge to [bus 09-09]
pci 0000:00:1c.2: bridge window [io 0x2000-0x2fff]
pci 0000:00:1c.2: bridge window [mem 0xf0500000-0xf05fffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 11-11] (subtractive decode)
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI Error (dsfield-0143): [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node ffff88007f014bc0), AE_ALREADY_EXISTS
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
pci 0000:00:1c.0: can't reserve window [io 0x0000-0x0fff]
pci 0000:00:1b.0: address space collision: [mem 0xf0500000-0xf0503fff 64bit] already in use
pci 0000:00:1b.0: can't reserve [mem 0xf0500000-0xf0503fff 64bit]
pci 0000:00:1d.7: address space collision: [mem 0xf0504000-0xf05043ff] already in use
pci 0000:00:1d.7: can't reserve [mem 0xf0504000-0xf05043ff]
pci 0000:00:1f.2: address space collision: [mem 0xf0504400-0xf05047ff] already in use
pci 0000:00:1f.2: can't reserve [mem 0xf0504400-0xf05047ff]
HPET: 3 timers in total, 0 timers will be used for per-cpu timer
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 8 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [io 0x0800-0x080f] has been reserved
system 00:01: [io 0x1000-0x107f] has been reserved
system 00:01: [io 0x1180-0x11bf] has been reserved
system 00:01: [io 0x04d0-0x04d1] has been reserved
system 00:01: [io 0xfe00] has been reserved
system 00:01: [io 0x164e-0x174c] has been reserved
system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
system 00:01: [mem 0xfed14000-0xfed17fff] has been reserved
system 00:01: [mem 0xf8000000-0xfbffffff] has been reserved
system 00:01: [mem 0xfef00000-0xfeffffff] has been reserved
pci 0000:00:1c.0: BAR 8: assigned [mem 0x80000000-0x801fffff]
pci 0000:00:1c.0: BAR 9: assigned [mem 0x80200000-0x803fffff 64bit pref]
pci 0000:00:1c.1: BAR 9: assigned [mem 0x80400000-0x805fffff 64bit pref]
pci 0000:00:1c.2: BAR 8: assigned [mem 0x80600000-0x809fffff]
pci 0000:00:1b.0: BAR 0: assigned [mem 0x80a00000-0x80a03fff 64bit]
pci 0000:00:1b.0: BAR 0: set to [mem 0x80a00000-0x80a03fff 64bit] (PCI address [0x80a00000-0x80a03fff]
pci 0000:00:1c.0: BAR 7: assigned [io 0x3000-0x3fff]
pci 0000:00:1c.1: BAR 7: assigned [io 0x4000-0x4fff]
pci 0000:00:1d.7: BAR 0: assigned [mem 0x80a04000-0x80a043ff]
pci 0000:00:1d.7: BAR 0: set to [mem 0x80a04000-0x80a043ff] (PCI address [0x80a04000-0x80a043ff]
pci 0000:00:1f.2: BAR 5: assigned [mem 0x80a04400-0x80a047ff]
pci 0000:00:1f.2: BAR 5: set to [mem 0x80a04400-0x80a047ff] (PCI address [0x80a04400-0x80a047ff]
pci 0000:00:1c.0: PCI bridge to [bus 05-05]
pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
pci 0000:00:1c.0: bridge window [mem 0x80000000-0x801fffff]
pci 0000:00:1c.0: bridge window [mem 0x80200000-0x803fffff 64bit pref]
pci 0000:00:1c.1: PCI bridge to [bus 07-07]
pci 0000:00:1c.1: bridge window [io 0x4000-0x4fff]
pci 0000:00:1c.1: bridge window [mem 0xf0100000-0xf01fffff]
pci 0000:00:1c.1: bridge window [mem 0x80400000-0x805fffff 64bit pref]
pci 0000:09:00.0: BAR 6: assigned [mem 0xf0540000-0xf055ffff pref]
pci 0000:00:1c.2: PCI bridge to [bus 09-09]
pci 0000:00:1c.2: bridge window [io 0x2000-0x2fff]
pci 0000:00:1c.2: bridge window [mem 0x80600000-0x809fffff]
pci 0000:00:1c.2: bridge window [mem 0xf0500000-0xf05fffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 11-11]
pci 0000:00:1e.0: bridge window [io disabled]
pci 0000:00:1e.0: bridge window [mem disabled]
pci 0000:00:1e.0: bridge window [mem pref disabled]
pci 0000:00:1c.0: enabling device (0000 -> 0003)
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
pci_bus 0000:05: resource 0 [io 0x3000-0x3fff]
pci_bus 0000:05: resource 1 [mem 0x80000000-0x801fffff]
pci_bus 0000:05: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
pci_bus 0000:07: resource 0 [io 0x4000-0x4fff]
pci_bus 0000:07: resource 1 [mem 0xf0100000-0xf01fffff]
pci_bus 0000:07: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
pci_bus 0000:09: resource 0 [io 0x2000-0x2fff]
pci_bus 0000:09: resource 1 [mem 0x80600000-0x809fffff]
pci_bus 0000:09: resource 2 [mem 0xf0500000-0xf05fffff 64bit pref]
pci_bus 0000:11: resource 3 [io 0x0000-0xffff]
pci_bus 0000:11: resource 4 [mem 0x00000000-0xffffffffffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
UDP hash table entries: 1024 (order: 3, 32768 bytes)
UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
NET: Registered protocol family 1
pci 0000:00:02.0: Boot video device
PCI: CLS 32 bytes, default 64
Simple Boot Flag at 0x35 set to 0x1
Intel AES-NI instructions are not detected.
audit: initializing netlink socket (disabled)
type=2000 audit(1273530106.215:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 3997
alg: No test for cipher_null (cipher_null-generic)
alg: No test for ecb(cipher_null) (ecb-cipher_null)
alg: No test for digest_null (digest_null-generic)
alg: No test for compress_null (compress_null-generic)
alg: No test for fcrypt (fcrypt-generic)
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X
pcieport 0000:00:1c.1: setting latency timer to 64
pcieport 0000:00:1c.1: irq 25 for MSI/MSI-X
pcieport 0000:00:1c.2: setting latency timer to 64
pcieport 0000:00:1c.2: irq 26 for MSI/MSI-X
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
floppy0: no floppy controllers found
loop: module loaded
Loading iSCSI transport class v2.0-870.
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: irq 27 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0x80a04400 port 0x80a04500 irq 27
ata2: SATA max UDMA/133 abar m1024@0x80a04400 port 0x80a04580 irq 27
ata3: SATA max UDMA/133 abar m1024@0x80a04400 port 0x80a04600 irq 27
ata4: SATA max UDMA/133 abar m1024@0x80a04400 port 0x80a04680 irq 27
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata1.00: ATA-8: FUJITSU MJA2160BH G2, 00400018, max UDMA/100
ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access ATA FUJITSU MJA2160B 0040 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
registered taskstats version 1
VFS: Mounted root (ext2 filesystem) readonly on device 8:3.
devtmpfs: mounted
Freeing unused kernel memory: 456k freed
Write protecting the kernel read-only data: 6144k
Freeing unused kernel memory: 564k freed
Freeing unused kernel memory: 828k freed
udev: starting version 153
sd 0:0:0:0: Attached scsi generic sg0 type 0
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: using broken periodic workaround
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0x80a04000
input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0c/PNP0C0D:00/input/input1
ACPI: Lid Switch [LID0]
ACPI: AC Adapter [ACAD] (on-line)
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0C:00/input/input2
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
ACPI: Power Button [PWRF]
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.33.3 ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001820
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.33.3 uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001840
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.33.3 uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001860
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.33.3 uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001880
usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: UHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.33.3 uhci_hcd
usb usb5: SerialNumber: 0000:00:1d.3
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
Linux agpgart interface v0.103
ACPI: Battery Slot [BAT1] (battery present)
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
agpgart-intel 0000:00:00.0: Intel Pineview Chipset
agpgart-intel 0000:00:00.0: detected 8188K stolen memory
cfg80211: Calling CRDA to update world regulatory domain
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
ACPI: SSDT 000000007f5d5de4 00203 (v02 PmRef Cpu0Ist 00003000 INTL 20050624)
ACPI: SSDT 000000007f5d577a 005E5 (v02 PmRef Cpu0Cst 00003001 INTL 20050624)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Monitor-Mwait will be used to enter C-3 state
Marking TSC unstable due to TSC halts in idle
Switching to clocksource hpet
usb 1-4: new high speed USB device using ehci_hcd and address 2
rtc_cmos 00:04: RTC can wake from S4
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[drm] Initialized drm 1.1.0 20060810
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 28 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
usb 1-4: New USB device found, idVendor=0bda, idProduct=0158
usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4: Product: USB2.0-CRW
usb 1-4: Manufacturer: Generic
usb 1-4: SerialNumber: 20071114173400000
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
i915 0000:00:02.0: irq 29 for MSI/MSI-X
[drm] set up 7M of stolen space
usb 1-8: new high speed USB device using ehci_hcd and address 3
[drm] initialized overlay support
Initializing USB Mass Storage driver...
scsi4 : usb-storage 1-4:1.0
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
[drm] Big FIFO is enabled
usb 1-8: New USB device found, idVendor=04f2, idProduct=b15d
usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 1-8: Product: Chicony USB 2.0 Camera
usb 1-8: Manufacturer: Chicony
[drm] Big FIFO is enabled
[drm] Big FIFO is enabled
[drm] Big FIFO is enabled
Console: switching to colour frame buffer device 128x37
fb0: inteldrmfb frame buffer device
registered panic notifier
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
ath9k 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ath9k 0000:07:00.0: setting latency timer to 64
ath: EEPROM regdomain: 0x65
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x65
phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registered led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
phy0: Atheros AR9285 Rev:2 mem=0xffffc90020a20000, irq=17
cfg80211: World regulatory domain updated:
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04731/0xa40000
Adding 2000084k swap on /dev/sda2. Priority:-1 extents:1 across:2000084k
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input4
scsi 4:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS
sd 4:0:0:0: Attached scsi generic sg1 type 0
sd 4:0:0:0: [sdb] Attached SCSI removable disk
wlan0: direct probe to AP 00:13:f7:fd:ab:e3 (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:13:f7:fd:ab:e3 (try 1)
wlan0: authenticated
wlan0: associate with AP 00:13:f7:fd:ab:e3 (try 1)
wlan0: RX AssocResp from 00:13:f7:fd:ab:e3 (capab=0x431 status=0 aid=3)
wlan0: associated
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
wlan0: no IPv6 routers present
[drm] Big FIFO is enabled
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: PROBLEM: tickless scheduling
2010-05-11 0:34 ` Donald Allen
@ 2010-05-11 0:38 ` Robert Hancock
2010-05-11 0:53 ` Donald Allen
0 siblings, 1 reply; 23+ messages in thread
From: Robert Hancock @ 2010-05-11 0:38 UTC (permalink / raw)
To: Donald Allen; +Cc: linux-kernel
On 05/10/2010 06:34 PM, Donald Allen wrote:
> On Mon, May 10, 2010 at 8:27 PM, Robert Hancock<hancockrwd@gmail.com> wrote:
>> On 05/10/2010 06:18 PM, Donald Allen wrote:
>>>
>
>>
>> Can you post dmesg output from bootup?
>
> See attached.
>
> /Don Allen
>>
I don't see anything too abnormal, except this:
ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 1/0x1 ignored.
I assume your kernel is compiled without SMP support, but you have an
Atom CPU that supports hyperthreading. I don't know if it's related but
you could try fixing that and see if it changes anything.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-11 0:38 ` Robert Hancock
@ 2010-05-11 0:53 ` Donald Allen
0 siblings, 0 replies; 23+ messages in thread
From: Donald Allen @ 2010-05-11 0:53 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-kernel
On Mon, May 10, 2010 at 8:38 PM, Robert Hancock <hancockrwd@gmail.com> wrote:
> On 05/10/2010 06:34 PM, Donald Allen wrote:
>>
>> On Mon, May 10, 2010 at 8:27 PM, Robert Hancock<hancockrwd@gmail.com>
>> wrote:
>>>
>>> On 05/10/2010 06:18 PM, Donald Allen wrote:
>>>>
>>
>>>
>>> Can you post dmesg output from bootup?
>>
>> See attached.
>>
>> /Don Allen
>>>
>
> I don't see anything too abnormal, except this:
>
> ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 1/0x1 ignored.
>
> I assume your kernel is compiled without SMP support, but you have an Atom
> CPU that supports hyperthreading. I don't know if it's related but you could
> try fixing that and see if it changes anything.
The dmesg (and all other data I supplied) is from the system running
with the custom kernel I built, which has tickless disabled and does
not fail in the way described in the report. So, to be clear, the
dmesg is not from the failing kernel. Unfortunately, it was only after
I'd installed the non-tickless kernel that I was pretty certain of
what was happening and therefore in a position to file a bug report.
Thanks for pointing out the non-smp bug. I'll fix and rebuild my
kernel, but that is not relevant to the tickless issue.
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-11 0:18 PROBLEM: tickless scheduling Donald Allen
2010-05-11 0:27 ` Robert Hancock
@ 2010-05-11 0:54 ` john stultz
2010-05-11 0:59 ` Donald Allen
1 sibling, 1 reply; 23+ messages in thread
From: john stultz @ 2010-05-11 0:54 UTC (permalink / raw)
To: Donald Allen; +Cc: linux-kernel, Thomas Gleixner
On Mon, May 10, 2010 at 5:18 PM, Donald Allen <donaldcallen@gmail.com> wrote:
> 1. Network file transfers and fscks stop on Toshiba netbook unless
> system receives external events
Can you provide /proc/timer_list output?
I assume booting with nohz=off from grub resolves the issue?
Sounds similar to https://bugzilla.kernel.org/show_bug.cgi?id=12118
thanks
-john
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-11 0:54 ` john stultz
@ 2010-05-11 0:59 ` Donald Allen
2010-05-11 1:12 ` john stultz
0 siblings, 1 reply; 23+ messages in thread
From: Donald Allen @ 2010-05-11 0:59 UTC (permalink / raw)
To: john stultz; +Cc: linux-kernel, Thomas Gleixner
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On Mon, May 10, 2010 at 8:54 PM, john stultz <johnstul@us.ibm.com> wrote:
> On Mon, May 10, 2010 at 5:18 PM, Donald Allen <donaldcallen@gmail.com> wrote:
>> 1. Network file transfers and fscks stop on Toshiba netbook unless
>> system receives external events
>
> Can you provide /proc/timer_list output?
Attached, but again, this is from the system running with tickless disabled.
>
> I assume booting with nohz=off from grub resolves the issue?
Didn't know about the boot-time option (thanks for pointing it out),
but I wanted to build a custom kernel anyway, so i did so and disabled
tickless.
>
> Sounds similar to https://bugzilla.kernel.org/show_bug.cgi?id=12118
Sure does.
/Don
>
> thanks
> -john
>
[-- Attachment #2: timer_list --]
[-- Type: application/octet-stream, Size: 5516 bytes --]
Timer List Version: v0.5
HRTIMER_MAX_CLOCK_BASES: 2
now at 2038238554393 nsecs
cpu: 0
clock 0:
.base: ffffffff8162a080
.index: 0
.resolution: 1 nsecs
.get_time: ktime_get_real
.offset: 1273530107051966489 nsecs
active timers:
#0: <ffff88006ec81d28>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, firefox-bin/1573
# expires at 1273532145346808000-1273532145346858000 nsecs [in 1273530107108253607 to 1273530107108303607 nsecs]
#1: <ffff88006ec5fd28>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, firefox-bin/1572
# expires at 1273532145642135000-1273532145642185000 nsecs [in 1273530107403580607 to 1273530107403630607 nsecs]
#2: <ffff88006ee77d28>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, firefox-bin/7355
# expires at 1273532195713167000-1273532195713217000 nsecs [in 1273530157474612607 to 1273530157474662607 nsecs]
#3: <ffff88006efe7d28>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, firefox-bin/5049
# expires at 1273532372263808000-1273532372263858000 nsecs [in 1273530334025253607 to 1273530334025303607 nsecs]
#4: <ffff88007c151d28>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, firefox-bin/3153
# expires at 1273532372273411000-1273532372273461000 nsecs [in 1273530334034856607 to 1273530334034906607 nsecs]
#5: <ffff88007c1d5d28>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, firefox-bin/3152
# expires at 1273532374484269000-1273532374484319000 nsecs [in 1273530336245714607 to 1273530336245764607 nsecs]
clock 1:
.base: ffffffff8162a0c0
.index: 1
.resolution: 1 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
#0: <ffffffff8162ab40>, tick_sched_timer, S:01, hrtimer_start_range_ns, swapper/0
# expires at 2038239000000-2038239000000 nsecs [in 445607 to 445607 nsecs]
#1: <ffff88007d9e2628>, posix_timer_fn, S:01, hrtimer_start_range_ns, ntpd/1144
# expires at 2038562705182-2038562705182 nsecs [in 324150789 to 324150789 nsecs]
#2: <ffff88006ed27918>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, emacs/6449
# expires at 2038587106151-2038587605274 nsecs [in 348551758 to 349050881 nsecs]
#3: <ffff88007d8c9918>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, emacs/1535
# expires at 2038732762531-2038733260195 nsecs [in 494208138 to 494705802 nsecs]
#4: <ffff88007e589918>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, X/1511
# expires at 2038879271882-2038879916879 nsecs [in 640717489 to 641362486 nsecs]
#5: <ffff88007d963060>, it_real_fn, S:01, hrtimer_start, emacs/1535
# expires at 2039219558819-2039219558819 nsecs [in 981004426 to 981004426 nsecs]
#6: <ffff88007e5c5a68>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, hald-addon-stor/1203
# expires at 2039948541752-2039950535749 nsecs [in 1709987359 to 1711981356 nsecs]
#7: <ffff88007f0a1918>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, init/1
# expires at 2042330172846-2042335172843 nsecs [in 4091618453 to 4096618450 nsecs]
#8: <ffff8800590a7e98>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, sleep/9386
# expires at 2047604666909-2047604716909 nsecs [in 9366112516 to 9366162516 nsecs]
#9: <ffff88007d031a68>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, ROX-Filer/1556
# expires at 2047946066686-2047956066684 nsecs [in 9707512293 to 9717512291 nsecs]
#10: <ffff88007e56ba68>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, hald/1165
# expires at 2049948229208-2049978082206 nsecs [in 11709674815 to 11739527813 nsecs]
#11: <ffff88006ec4ba68>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, gconfd-2/1569
# expires at 2050786095879-2050816066877 nsecs [in 12547541486 to 12577512484 nsecs]
#12: <ffff88007e603e98>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, crond/1220
# expires at 2053948156852-2053948206852 nsecs [in 15709602459 to 15709652459 nsecs]
#13: <ffff88007da56060>, it_real_fn, S:01, hrtimer_start, syslogd/948
# expires at 2059783231304-2059783231304 nsecs [in 21544676911 to 21544676911 nsecs]
#14: <ffff88007db4fe98>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, atd/1222
# expires at 3641894552578-3641894602578 nsecs [in 1603655998185 to 1603656048185 nsecs]
#15: <ffff88006ec59a68>, hrtimer_wakeup, S:01, hrtimer_start_range_ns, firefox-bin/1570
# expires at 67571657741081-67571757741081 nsecs [in 65533419186688 to 65533519186688 nsecs]
.expires_next : 2038239000000 nsecs
.hres_active : 1
.nr_events : 2242854
.nr_retries : 989
.nr_hangs : 0
.max_hang_time : 0 nsecs
.nohz_mode : 0
.idle_tick : 0 nsecs
.tick_stopped : 0
.idle_jiffies : 0
.idle_calls : 0
.idle_sleeps : 0
.idle_entrytime : 0 nsecs
.idle_waketime : 0 nsecs
.idle_exittime : 0 nsecs
.idle_sleeptime : 0 nsecs
.last_jiffies : 0
.next_jiffies : 0
.idle_expires : 0 nsecs
jiffies: 4296705534
Tick Device: mode: 1
Broadcast device
Clock Event Device: hpet
max_delta_ns: 149983005959
min_delta_ns: 5000
mult: 61496114
shift: 32
mode: 3
next_event: 2038239000000 nsecs
set_next_event: hpet_legacy_next_event
set_mode: hpet_legacy_set_mode
event_handler: tick_handle_oneshot_broadcast
tick_broadcast_mask: 00000001
tick_broadcast_oneshot_mask: 00000000
Tick Device: mode: 1
Per CPU device: 0
Clock Event Device: lapic
max_delta_ns: 807212358
min_delta_ns: 1443
mult: 44633599
shift: 32
mode: 3
next_event: 2038239000000 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: hrtimer_interrupt
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-11 0:59 ` Donald Allen
@ 2010-05-11 1:12 ` john stultz
2010-05-11 1:52 ` Donald Allen
0 siblings, 1 reply; 23+ messages in thread
From: john stultz @ 2010-05-11 1:12 UTC (permalink / raw)
To: Donald Allen; +Cc: linux-kernel, Thomas Gleixner
On Mon, 2010-05-10 at 20:59 -0400, Donald Allen wrote:
> On Mon, May 10, 2010 at 8:54 PM, john stultz <johnstul@us.ibm.com> wrote:
> > On Mon, May 10, 2010 at 5:18 PM, Donald Allen <donaldcallen@gmail.com> wrote:
> >> 1. Network file transfers and fscks stop on Toshiba netbook unless
> >> system receives external events
> >
> > Can you provide /proc/timer_list output?
>
> Attached, but again, this is from the system running with tickless disabled.
Is it possible to boot with the kernel showing the issue and provide the
details?
> > I assume booting with nohz=off from grub resolves the issue?
>
> Didn't know about the boot-time option (thanks for pointing it out),
> but I wanted to build a custom kernel anyway, so i did so and disabled
> tickless.
Ok. It may still be of value to know booting with nohz=off does avoid
the problem.
thanks
-john
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-11 1:12 ` john stultz
@ 2010-05-11 1:52 ` Donald Allen
2010-05-12 19:54 ` Donald Allen
0 siblings, 1 reply; 23+ messages in thread
From: Donald Allen @ 2010-05-11 1:52 UTC (permalink / raw)
To: john stultz; +Cc: linux-kernel, Thomas Gleixner
On Mon, May 10, 2010 at 9:12 PM, john stultz <johnstul@us.ibm.com> wrote:
> On Mon, 2010-05-10 at 20:59 -0400, Donald Allen wrote:
>> On Mon, May 10, 2010 at 8:54 PM, john stultz <johnstul@us.ibm.com> wrote:
>> > On Mon, May 10, 2010 at 5:18 PM, Donald Allen <donaldcallen@gmail.com> wrote:
>> >> 1. Network file transfers and fscks stop on Toshiba netbook unless
>> >> system receives external events
>> >
>> > Can you provide /proc/timer_list output?
>>
>> Attached, but again, this is from the system running with tickless disabled.
>
> Is it possible to boot with the kernel showing the issue and provide the
> details?
It's a minor pain, but I'll do it.
>
>
>> > I assume booting with nohz=off from grub resolves the issue?
>>
>> Didn't know about the boot-time option (thanks for pointing it out),
>> but I wanted to build a custom kernel anyway, so i did so and disabled
>> tickless.
>
> Ok. It may still be of value to know booting with nohz=off does avoid
> the problem.
Ok. When I've got the original kernel installed and bootable, I'll try
it. I won't be able to get to this for a day or so.
/Don
>
>
> thanks
> -john
>
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-11 1:52 ` Donald Allen
@ 2010-05-12 19:54 ` Donald Allen
2010-05-12 20:52 ` john stultz
0 siblings, 1 reply; 23+ messages in thread
From: Donald Allen @ 2010-05-12 19:54 UTC (permalink / raw)
To: john stultz; +Cc: linux-kernel, Thomas Gleixner
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]
Before doing what you asked, I ran my home-brew backup script, which
tars up the whole machine, save my home directory, to a big sata drive
in a usb shoebox. I did so by booting the most recent Arch Linux
install/live CD (while I use Slackware, the Slackware install CDs are
not suitable for this sort of thing, having very old versions of
things like tar). While doing so, I observed exactly the same symptoms
I did with the Slackware 13.1 install, which I described in the bug
report. So rather than messing with the hard-won custom kernel that I
now have installed on the netbook, I am attaching the various things
from /proc gathered with the Arch kernel running. Yes, it's a somewhat
older kernel (2.6.30), but I'm hoping that things haven't changed much
in tickless land. If that's not the case, then I will attempt to
reproduce this with the newer kernel on the Slackware 13.1 install
DVD. Let me know if you need me to do this. The attached tar file is
bzip2-compressed, so you want xjf to extract.
/Don
On Mon, May 10, 2010 at 9:52 PM, Donald Allen <donaldcallen@gmail.com> wrote:
> On Mon, May 10, 2010 at 9:12 PM, john stultz <johnstul@us.ibm.com> wrote:
>> On Mon, 2010-05-10 at 20:59 -0400, Donald Allen wrote:
>>> On Mon, May 10, 2010 at 8:54 PM, john stultz <johnstul@us.ibm.com> wrote:
>>> > On Mon, May 10, 2010 at 5:18 PM, Donald Allen <donaldcallen@gmail.com> wrote:
>>> >> 1. Network file transfers and fscks stop on Toshiba netbook unless
>>> >> system receives external events
>>> >
>>> > Can you provide /proc/timer_list output?
>>>
>>> Attached, but again, this is from the system running with tickless disabled.
>>
>> Is it possible to boot with the kernel showing the issue and provide the
>> details?
>
> It's a minor pain, but I'll do it.
>
>>
>>
>>> > I assume booting with nohz=off from grub resolves the issue?
>>>
>>> Didn't know about the boot-time option (thanks for pointing it out),
>>> but I wanted to build a custom kernel anyway, so i did so and disabled
>>> tickless.
>>
>> Ok. It may still be of value to know booting with nohz=off does avoid
>> the problem.
>
> Ok. When I've got the original kernel installed and bootable, I'll try
> it. I won't be able to get to this for a day or so.
>
> /Don
>
>>
>>
>> thanks
>> -john
>>
>>
>
[-- Attachment #2: tickless.tbz2 --]
[-- Type: application/octet-stream, Size: 13078 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-12 19:54 ` Donald Allen
@ 2010-05-12 20:52 ` john stultz
2010-05-15 17:11 ` Donald Allen
0 siblings, 1 reply; 23+ messages in thread
From: john stultz @ 2010-05-12 20:52 UTC (permalink / raw)
To: Donald Allen; +Cc: linux-kernel, Thomas Gleixner
On Wed, 2010-05-12 at 15:54 -0400, Donald Allen wrote:
> Before doing what you asked, I ran my home-brew backup script, which
> tars up the whole machine, save my home directory, to a big sata drive
> in a usb shoebox. I did so by booting the most recent Arch Linux
> install/live CD (while I use Slackware, the Slackware install CDs are
> not suitable for this sort of thing, having very old versions of
> things like tar). While doing so, I observed exactly the same symptoms
> I did with the Slackware 13.1 install, which I described in the bug
> report. So rather than messing with the hard-won custom kernel that I
> now have installed on the netbook, I am attaching the various things
> from /proc gathered with the Arch kernel running. Yes, it's a somewhat
> older kernel (2.6.30), but I'm hoping that things haven't changed much
> in tickless land. If that's not the case, then I will attempt to
> reproduce this with the newer kernel on the Slackware 13.1 install
> DVD. Let me know if you need me to do this. The attached tar file is
> bzip2-compressed, so you want xjf to extract.
Hmm.. Sorry, but I have another quick request. Could you send
your /proc/interrupts output from the kernel having the problem?
thanks
-john
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-12 20:52 ` john stultz
@ 2010-05-15 17:11 ` Donald Allen
2010-05-16 16:14 ` Stefan Biereigel
2010-05-16 23:36 ` Thomas Gleixner
0 siblings, 2 replies; 23+ messages in thread
From: Donald Allen @ 2010-05-15 17:11 UTC (permalink / raw)
To: john stultz; +Cc: linux-kernel, Thomas Gleixner
[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]
On Wed, May 12, 2010 at 4:52 PM, john stultz <johnstul@us.ibm.com> wrote:
> On Wed, 2010-05-12 at 15:54 -0400, Donald Allen wrote:
>> Before doing what you asked, I ran my home-brew backup script, which
>> tars up the whole machine, save my home directory, to a big sata drive
>> in a usb shoebox. I did so by booting the most recent Arch Linux
>> install/live CD (while I use Slackware, the Slackware install CDs are
>> not suitable for this sort of thing, having very old versions of
>> things like tar). While doing so, I observed exactly the same symptoms
>> I did with the Slackware 13.1 install, which I described in the bug
>> report. So rather than messing with the hard-won custom kernel that I
>> now have installed on the netbook, I am attaching the various things
>> from /proc gathered with the Arch kernel running. Yes, it's a somewhat
>> older kernel (2.6.30), but I'm hoping that things haven't changed much
>> in tickless land. If that's not the case, then I will attempt to
>> reproduce this with the newer kernel on the Slackware 13.1 install
>> DVD. Let me know if you need me to do this. The attached tar file is
>> bzip2-compressed, so you want xjf to extract.
>
> Hmm.. Sorry, but I have another quick request. Could you send
> your /proc/interrupts output from the kernel having the problem?
Attached. This is from the 2.6.30 kernel on the Arch Linux install cd.
Here's another bit of data. As I've said previously, the problems I'm
reporting were observed on a Toshiba NB310-305 netbook with a
single-core Atom 450 processor. I just built myself a mini-ITX system
using the Intel D510MO motherboard, which provides a dual-core D510
Atom processor. The other hardware on the board is similar to the
Toshiba. I installed the same Slackware snapshot I used on the
Toshiba, and did the home directory transfer without any problem at
all with the default tickless kernel. The hardware isn't identical,
and while I don't know the internals of the Linux kernel at all, my
gut, backed up by many years of OS development work in scheduling and
memory management, is telling me that the key difference is dual- vs.
single-core. Just a guess.
Hope this helps --
/Don
>
> thanks
> -john
>
>
>
[-- Attachment #2: interrupts --]
[-- Type: application/octet-stream, Size: 1162 bytes --]
CPU0 CPU1
0: 1872 1878 IO-APIC-edge timer
1: 227 183 IO-APIC-edge i8042
8: 64 65 IO-APIC-edge rtc0
9: 345 349 IO-APIC-fasteoi acpi
12: 13384 13381 IO-APIC-edge i8042
16: 0 0 IO-APIC-fasteoi uhci_hcd:usb5
17: 0 0 IO-APIC-fasteoi ath
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
19: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
22: 90 89 IO-APIC-fasteoi HDA Intel
23: 1353 1346 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
27: 96 93 PCI-MSI-edge ahci
NMI: 0 0 Non-maskable interrupts
LOC: 6286 5831 Local timer interrupts
SPU: 0 0 Spurious interrupts
RES: 5919 2009 Rescheduling interrupts
CAL: 22 39 Function call interrupts
TLB: 125 135 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
ERR: 0
MIS: 0
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: PROBLEM: tickless scheduling
2010-05-15 17:11 ` Donald Allen
@ 2010-05-16 16:14 ` Stefan Biereigel
2010-05-16 20:41 ` Arjan van de Ven
2010-05-17 15:26 ` Donald Allen
2010-05-16 23:36 ` Thomas Gleixner
1 sibling, 2 replies; 23+ messages in thread
From: Stefan Biereigel @ 2010-05-16 16:14 UTC (permalink / raw)
To: Donald Allen; +Cc: john stultz, linux-kernel, Thomas Gleixner
> Attached. This is from the 2.6.30 kernel on the Arch Linux install cd.
>
> Here's another bit of data. As I've said previously, the problems I'm
> reporting were observed on a Toshiba NB310-305 netbook with a
> single-core Atom 450 processor. I just built myself a mini-ITX system
> using the Intel D510MO motherboard, which provides a dual-core D510
> Atom processor. The other hardware on the board is similar to the
> Toshiba. I installed the same Slackware snapshot I used on the
> Toshiba, and did the home directory transfer without any problem at
> all with the default tickless kernel. The hardware isn't identical,
> and while I don't know the internals of the Linux kernel at all, my
> gut, backed up by many years of OS development work in scheduling and
> memory management, is telling me that the key difference is dual- vs.
> single-core. Just a guess.
>
> Hope this helps --
>
> /Don
>
Hello everyone,
I hope I can add something here, because I am experiencing the exact
same Problem as Don describes. I'm running a PackardBell EasyNote MB89
featuring a Core 2 Duo, 4 GB of RAM, Intel Chipset (Santa Rosa), SATA
HDD. My Machine even hangs at boot, absolutely doing nothing until i
wiggle the touchpad. This is definately reproduceable, but I think it
doesn't occur that often in X-Window-System, if X is off I can just wait
a couple of seconds and there I go.
I compiled other kernels myself with tickless disabled and Ticks set to
various values (250, 1000) which completely resolved my problem. If you
want, I can get you some Output/logs/whatever because I'm fixed to using
this kernel ATM (which doesn't really hurt because I use X and son't
shut down my Notebook that often).
Even though I don't know what exact kernel-version this problem brings
(using another machine ATM from vacation) I can say that I existed since
Opensuse 11.1 I guess, so maybe 2.6.30 and above.
Hope I can help --
Stefan
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-16 16:14 ` Stefan Biereigel
@ 2010-05-16 20:41 ` Arjan van de Ven
2010-05-17 15:26 ` Donald Allen
1 sibling, 0 replies; 23+ messages in thread
From: Arjan van de Ven @ 2010-05-16 20:41 UTC (permalink / raw)
To: Stefan Biereigel; +Cc: Donald Allen, john stultz, linux-kernel, Thomas Gleixner
On Sun, 16 May 2010 18:14:07 +0200
Stefan Biereigel <security@biereigel-wb.de> wrote:
> Hello everyone,
>
> I hope I can add something here, because I am experiencing the exact
> same Problem as Don describes. I'm running a PackardBell EasyNote
> MB89 featuring a Core 2 Duo, 4 GB of RAM, Intel Chipset (Santa Rosa),
> SATA HDD. My Machine even hangs at boot, absolutely doing nothing
> until i wiggle the touchpad. This is definately reproduceable, but I
> think it doesn't occur that often in X-Window-System, if X is off I
> can just wait a couple of seconds and there I go.
this has nothing to do with tickless or not... you're losing interrupts.
if you're not tickless, there's just so many regular interrupts
happening that you don't notice that other interrupts are lost.
try disabling MSI (iirc pci=nomsi) to see if that helps..
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-16 16:14 ` Stefan Biereigel
2010-05-16 20:41 ` Arjan van de Ven
@ 2010-05-17 15:26 ` Donald Allen
2010-05-17 16:15 ` Stefan Biereigel
1 sibling, 1 reply; 23+ messages in thread
From: Donald Allen @ 2010-05-17 15:26 UTC (permalink / raw)
To: Stefan Biereigel; +Cc: john stultz, linux-kernel, Thomas Gleixner
Stefan --
Would you check the BIOS on your machine and report the maker and
version number? If you've followed this, I'm especially interested to
know if it's a Phoenix BIOS.
Thanks --
/Don
On Sun, May 16, 2010 at 12:14 PM, Stefan Biereigel
<security@biereigel-wb.de> wrote:
>
>> Attached. This is from the 2.6.30 kernel on the Arch Linux install cd.
>>
>> Here's another bit of data. As I've said previously, the problems I'm
>> reporting were observed on a Toshiba NB310-305 netbook with a
>> single-core Atom 450 processor. I just built myself a mini-ITX system
>> using the Intel D510MO motherboard, which provides a dual-core D510
>> Atom processor. The other hardware on the board is similar to the
>> Toshiba. I installed the same Slackware snapshot I used on the
>> Toshiba, and did the home directory transfer without any problem at
>> all with the default tickless kernel. The hardware isn't identical,
>> and while I don't know the internals of the Linux kernel at all, my
>> gut, backed up by many years of OS development work in scheduling and
>> memory management, is telling me that the key difference is dual- vs.
>> single-core. Just a guess.
>>
>> Hope this helps --
>>
>> /Don
>>
>
> Hello everyone,
>
> I hope I can add something here, because I am experiencing the exact same
> Problem as Don describes. I'm running a PackardBell EasyNote MB89 featuring
> a Core 2 Duo, 4 GB of RAM, Intel Chipset (Santa Rosa), SATA HDD. My Machine
> even hangs at boot, absolutely doing nothing until i wiggle the touchpad.
> This is definately reproduceable, but I think it doesn't occur that often in
> X-Window-System, if X is off I can just wait a couple of seconds and there I
> go.
>
> I compiled other kernels myself with tickless disabled and Ticks set to
> various values (250, 1000) which completely resolved my problem. If you
> want, I can get you some Output/logs/whatever because I'm fixed to using
> this kernel ATM (which doesn't really hurt because I use X and son't shut
> down my Notebook that often).
> Even though I don't know what exact kernel-version this problem brings
> (using another machine ATM from vacation) I can say that I existed since
> Opensuse 11.1 I guess, so maybe 2.6.30 and above.
>
> Hope I can help --
>
> Stefan
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-17 15:26 ` Donald Allen
@ 2010-05-17 16:15 ` Stefan Biereigel
0 siblings, 0 replies; 23+ messages in thread
From: Stefan Biereigel @ 2010-05-17 16:15 UTC (permalink / raw)
To: Donald Allen; +Cc: john stultz, linux-kernel, Thomas Gleixner
Am 17.05.2010 17:26, schrieb Donald Allen:
> Stefan --
>
> Would you check the BIOS on your machine and report the maker and
> version number? If you've followed this, I'm especially interested to
> know if it's a Phoenix BIOS.
>
> Thanks --
> /Don
Hello Don,
I did try some things here. pci=nomsi didn't work really, but I think it
decreased the rate of stucks, even though I'm not sure. My BIOS is a
Phoenix TrustedCore with version number PG2G3A08, should be from 7/2009
or so.
I will try my next boot with hpet=disable and report my results. Thanks
for your help!
Stefan DK3SB
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-15 17:11 ` Donald Allen
2010-05-16 16:14 ` Stefan Biereigel
@ 2010-05-16 23:36 ` Thomas Gleixner
2010-05-17 13:44 ` Donald Allen
1 sibling, 1 reply; 23+ messages in thread
From: Thomas Gleixner @ 2010-05-16 23:36 UTC (permalink / raw)
To: Donald Allen; +Cc: john stultz, LKML, Arjan van de Ven
Donald,
On Sat, 15 May 2010, Donald Allen wrote:
> Attached. This is from the 2.6.30 kernel on the Arch Linux install cd.
>
> Here's another bit of data. As I've said previously, the problems I'm
> reporting were observed on a Toshiba NB310-305 netbook with a
> single-core Atom 450 processor. I just built myself a mini-ITX system
> using the Intel D510MO motherboard, which provides a dual-core D510
> Atom processor. The other hardware on the board is similar to the
> Toshiba. I installed the same Slackware snapshot I used on the
> Toshiba, and did the home directory transfer without any problem at
> all with the default tickless kernel. The hardware isn't identical,
> and while I don't know the internals of the Linux kernel at all, my
> gut, backed up by many years of OS development work in scheduling and
> memory management, is telling me that the key difference is dual- vs.
> single-core. Just a guess.
I fear you are wrong.
The key difference is almost certainly that the BIOS of your netbook
tries to be overly clever vs. power management and is not aware of the
fact that the Linux kernel uses timer hardware in a very different way
than the other OS which comes preinstalled on that machine.
The overly clever BIOS power management which works nicely with the
vendor provided "drivers" for the other OS is just interfering with
the kernels way of dealing with the problem.
Can you please boot with "hpet=disable" on the kernel command line ?
Thanks,
tglx
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-16 23:36 ` Thomas Gleixner
@ 2010-05-17 13:44 ` Donald Allen
2010-05-17 14:02 ` Donald Allen
2010-05-17 14:04 ` Arjan van de Ven
0 siblings, 2 replies; 23+ messages in thread
From: Donald Allen @ 2010-05-17 13:44 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: john stultz, LKML, Arjan van de Ven
On Sun, May 16, 2010 at 7:36 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> Donald,
>
> On Sat, 15 May 2010, Donald Allen wrote:
>> Attached. This is from the 2.6.30 kernel on the Arch Linux install cd.
>>
>> Here's another bit of data. As I've said previously, the problems I'm
>> reporting were observed on a Toshiba NB310-305 netbook with a
>> single-core Atom 450 processor. I just built myself a mini-ITX system
>> using the Intel D510MO motherboard, which provides a dual-core D510
>> Atom processor. The other hardware on the board is similar to the
>> Toshiba. I installed the same Slackware snapshot I used on the
>> Toshiba, and did the home directory transfer without any problem at
>> all with the default tickless kernel. The hardware isn't identical,
>> and while I don't know the internals of the Linux kernel at all, my
>> gut, backed up by many years of OS development work in scheduling and
>> memory management, is telling me that the key difference is dual- vs.
>> single-core. Just a guess.
>
> I fear you are wrong.
Please don't be afraid.
>
> The key difference is almost certainly that the BIOS of your netbook
> tries to be overly clever vs. power management and is not aware of the
> fact that the Linux kernel uses timer hardware in a very different way
> than the other OS which comes preinstalled on that machine.
>
> The overly clever BIOS power management which works nicely with the
> vendor provided "drivers" for the other OS is just interfering with
> the kernels way of dealing with the problem.
>
> Can you please boot with "hpet=disable" on the kernel command line ?
I did, and it made no difference.
To be specific, the test I am doing involves booting with the Arch
Linux 2009.08 install/live cd. I then run
fsck.ext2 -f -r /dev/sda3
to do a read-only check of my root filesystem. I watch the
disk-activity light, and it reliably goes out and then you've got a
long wait if you do nothing. Tickling the touchpad gets things moving
again. This happens reliably with or without the boot-time option you
requested above.
I just noticed something else, however, that may lend credence to the
opinion expressed by Arjan van de Ven that this has nothing to do with
tickless. I originally noticed this problem on the Toshiba netbook
when I installed the Slackware 13.1 x86_64 beta on this machine, which
comes with a tickless 2.6.33.3 kernel. The first symptom I observed
was attempting to rsync my home directory from another machine to this
new install and, as previously described, I had to help things along
by activating the touchpad, or pressing the ctrl key (any kind of
external stimulus that would generate an interrupt seemed to work).
Anyway, after some discussion with Patrick Volkerding, I decided to
build a custom kernel for the netbook and disabled tickless in that
kernel. After getting that kernel working, I re-did the tests that
failed with the tickless kernel and they all worked fine, so I thought
we had our culprit. But just now, after doing the test you requested
above, I rebooted the system from its installed kernel (the tickful
kernel I built), and it hung during booting. At first I thought it was
taking awhile to do the dance with the dhcp server, but after waiting
longer than I thought this should take, I touched the touchpad and
forward progress began again immediately (disk light came on, boot
time chatter proceeded, etc.). So, my current guess, for what it's
worth, is that there's a race here that causes the system to miss the
fact that it has a runnable process, and the probability of hitting it
is reduced, but not to zero, by using tickful scheduling.
I will do the experiment suggested by Arjan van de Ven and report the
results of that separately.
/Don
>
> Thanks,
>
> tglx
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-17 13:44 ` Donald Allen
@ 2010-05-17 14:02 ` Donald Allen
2010-05-17 14:04 ` Arjan van de Ven
1 sibling, 0 replies; 23+ messages in thread
From: Donald Allen @ 2010-05-17 14:02 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: john stultz, LKML, Arjan van de Ven
On Mon, May 17, 2010 at 9:44 AM, Donald Allen <donaldcallen@gmail.com> wrote:
> On Sun, May 16, 2010 at 7:36 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
>> Donald,
>>
>> On Sat, 15 May 2010, Donald Allen wrote:
>>> Attached. This is from the 2.6.30 kernel on the Arch Linux install cd.
>>>
>>> Here's another bit of data. As I've said previously, the problems I'm
>>> reporting were observed on a Toshiba NB310-305 netbook with a
>>> single-core Atom 450 processor. I just built myself a mini-ITX system
>>> using the Intel D510MO motherboard, which provides a dual-core D510
>>> Atom processor. The other hardware on the board is similar to the
>>> Toshiba. I installed the same Slackware snapshot I used on the
>>> Toshiba, and did the home directory transfer without any problem at
>>> all with the default tickless kernel. The hardware isn't identical,
>>> and while I don't know the internals of the Linux kernel at all, my
>>> gut, backed up by many years of OS development work in scheduling and
>>> memory management, is telling me that the key difference is dual- vs.
>>> single-core. Just a guess.
>>
>> I fear you are wrong.
>
> Please don't be afraid.
>
>>
>> The key difference is almost certainly that the BIOS of your netbook
>> tries to be overly clever vs. power management and is not aware of the
>> fact that the Linux kernel uses timer hardware in a very different way
>> than the other OS which comes preinstalled on that machine.
>>
>> The overly clever BIOS power management which works nicely with the
>> vendor provided "drivers" for the other OS is just interfering with
>> the kernels way of dealing with the problem.
>>
>> Can you please boot with "hpet=disable" on the kernel command line ?
>
> I did, and it made no difference.
>
> To be specific, the test I am doing involves booting with the Arch
> Linux 2009.08 install/live cd. I then run
>
> fsck.ext2 -f -r /dev/sda3
>
> to do a read-only check of my root filesystem. I watch the
> disk-activity light, and it reliably goes out and then you've got a
> long wait if you do nothing. Tickling the touchpad gets things moving
> again. This happens reliably with or without the boot-time option you
> requested above.
>
> I just noticed something else, however, that may lend credence to the
> opinion expressed by Arjan van de Ven that this has nothing to do with
> tickless. I originally noticed this problem on the Toshiba netbook
> when I installed the Slackware 13.1 x86_64 beta on this machine, which
> comes with a tickless 2.6.33.3 kernel. The first symptom I observed
> was attempting to rsync my home directory from another machine to this
> new install and, as previously described, I had to help things along
> by activating the touchpad, or pressing the ctrl key (any kind of
> external stimulus that would generate an interrupt seemed to work).
> Anyway, after some discussion with Patrick Volkerding, I decided to
> build a custom kernel for the netbook and disabled tickless in that
> kernel. After getting that kernel working, I re-did the tests that
> failed with the tickless kernel and they all worked fine, so I thought
> we had our culprit. But just now, after doing the test you requested
> above, I rebooted the system from its installed kernel (the tickful
> kernel I built), and it hung during booting. At first I thought it was
> taking awhile to do the dance with the dhcp server, but after waiting
> longer than I thought this should take, I touched the touchpad and
> forward progress began again immediately (disk light came on, boot
> time chatter proceeded, etc.). So, my current guess, for what it's
> worth, is that there's a race here that causes the system to miss the
> fact that it has a runnable process, and the probability of hitting it
> is reduced, but not to zero, by using tickful scheduling.
>
> I will do the experiment suggested by Arjan van de Ven and report the
> results of that separately.
I just booted with pci=nomsi and the fsck ran normally without any
help from my finger on the touchpad. So I think Arjan is closing in on
this ...
/Don
>
> /Don
>
>
>>
>> Thanks,
>>
>> tglx
>>
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-17 13:44 ` Donald Allen
2010-05-17 14:02 ` Donald Allen
@ 2010-05-17 14:04 ` Arjan van de Ven
2010-05-17 14:11 ` Donald Allen
1 sibling, 1 reply; 23+ messages in thread
From: Arjan van de Ven @ 2010-05-17 14:04 UTC (permalink / raw)
To: Donald Allen; +Cc: Thomas Gleixner, john stultz, LKML
On Mon, 17 May 2010 09:44:47 -0400
Donald Allen <donaldcallen@gmail.com> wrote:
> I will do the experiment suggested by Arjan van de Ven and report the
> results of that separately.
since you're losing interrupts.. another good option to try is "irqpoll"
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-17 14:04 ` Arjan van de Ven
@ 2010-05-17 14:11 ` Donald Allen
2010-05-17 14:29 ` Arjan van de Ven
0 siblings, 1 reply; 23+ messages in thread
From: Donald Allen @ 2010-05-17 14:11 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: Thomas Gleixner, john stultz, LKML
On Mon, May 17, 2010 at 10:04 AM, Arjan van de Ven <arjan@infradead.org> wrote:
> On Mon, 17 May 2010 09:44:47 -0400
> Donald Allen <donaldcallen@gmail.com> wrote:
>
>> I will do the experiment suggested by Arjan van de Ven and report the
>> results of that separately.
Just for my own information, is this correct:
I assume that tickless scheduling, rather than relying on periodic
clock interrupts to wake up the scheduler, relies on interrupt
handlers to somehow signal the system that the scheduler needs to run
because they've just processed an event that has changed the state of
the system?
If so, then it looks like using the msi-style device-specific
interrupts isn't working reliably on this hardware? Or somehow the
kernel (or a driver) is failing to handle the interrupts properly with
msi enabled on certain hardware? I mention the latter only because of
the report yesterday from someone else seeing the same symptoms I am
on completely different hardware.
/Don
>
>
> since you're losing interrupts.. another good option to try is "irqpoll"
>
>
> --
> Arjan van de Ven Intel Open Source Technology Centre
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-17 14:11 ` Donald Allen
@ 2010-05-17 14:29 ` Arjan van de Ven
2010-05-17 14:45 ` Donald Allen
0 siblings, 1 reply; 23+ messages in thread
From: Arjan van de Ven @ 2010-05-17 14:29 UTC (permalink / raw)
To: Donald Allen; +Cc: Thomas Gleixner, john stultz, LKML
On Mon, 17 May 2010 10:11:51 -0400
Donald Allen <donaldcallen@gmail.com> wrote:
> On Mon, May 17, 2010 at 10:04 AM, Arjan van de Ven
> <arjan@infradead.org> wrote:
> > On Mon, 17 May 2010 09:44:47 -0400
> > Donald Allen <donaldcallen@gmail.com> wrote:
> >
> >> I will do the experiment suggested by Arjan van de Ven and report
> >> the results of that separately.
>
> Just for my own information, is this correct:
>
> I assume that tickless scheduling, rather than relying on periodic
> clock interrupts to wake up the scheduler, relies on interrupt
> handlers to somehow signal the system that the scheduler needs to run
> because they've just processed an event that has changed the state of
> the system?
well.. it relies on the hardware to signal the kernel that there's work
pending for a specific device.
technically this is true for both tickless and without tickless.
but without tickless there's so much activity in the system that it
never really goes quiet (and in fact, some different power management
decisions may be made because of that)
>
> If so, then it looks like using the msi-style device-specific
> interrupts isn't working reliably on this hardware? Or somehow the
that looks like a correct assumption to me.
> kernel (or a driver) is failing to handle the interrupts properly with
> msi enabled on certain hardware? I mention the latter only because of
> the report yesterday from someone else seeing the same symptoms I am
> on completely different hardware.
BIOSes breaking MSI is not entirely uncommon. Windows XP does not use
MSI for various things Linux does use MSI for, and so machines that come
with XP by default may not have this feature very well tested
unfortunately.
>
> /Don
>
> >
> >
> > since you're losing interrupts.. another good option to try is
> > "irqpoll"
> >
> >
> > --
> > Arjan van de Ven Intel Open Source Technology Centre
> > For development, discussion and tips for power savings,
> > visit http://www.lesswatts.org
> >
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: PROBLEM: tickless scheduling
2010-05-17 14:29 ` Arjan van de Ven
@ 2010-05-17 14:45 ` Donald Allen
0 siblings, 0 replies; 23+ messages in thread
From: Donald Allen @ 2010-05-17 14:45 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: Thomas Gleixner, john stultz, LKML
On Mon, May 17, 2010 at 10:29 AM, Arjan van de Ven <arjan@infradead.org> wrote:
> On Mon, 17 May 2010 10:11:51 -0400
> Donald Allen <donaldcallen@gmail.com> wrote:
>
>> On Mon, May 17, 2010 at 10:04 AM, Arjan van de Ven
>> <arjan@infradead.org> wrote:
>> > On Mon, 17 May 2010 09:44:47 -0400
>> > Donald Allen <donaldcallen@gmail.com> wrote:
>> >
>> >> I will do the experiment suggested by Arjan van de Ven and report
>> >> the results of that separately.
>>
>> Just for my own information, is this correct:
>>
>> I assume that tickless scheduling, rather than relying on periodic
>> clock interrupts to wake up the scheduler, relies on interrupt
>> handlers to somehow signal the system that the scheduler needs to run
>> because they've just processed an event that has changed the state of
>> the system?
>
> well.. it relies on the hardware to signal the kernel that there's work
> pending for a specific device.
>
> technically this is true for both tickless and without tickless.
> but without tickless there's so much activity in the system that it
> never really goes quiet (and in fact, some different power management
> decisions may be made because of that)
>
>>
>> If so, then it looks like using the msi-style device-specific
>> interrupts isn't working reliably on this hardware? Or somehow the
>
> that looks like a correct assumption to me.
Thanks for above explanation.
>
>> kernel (or a driver) is failing to handle the interrupts properly with
>> msi enabled on certain hardware? I mention the latter only because of
>> the report yesterday from someone else seeing the same symptoms I am
>> on completely different hardware.
>
> BIOSes breaking MSI is not entirely uncommon. Windows XP does not use
> MSI for various things Linux does use MSI for, and so machines that come
> with XP by default may not have this feature very well tested
> unfortunately.
This machine did come with XP.
I've changed the lilo.config (this is Slackware -- no grub by
default!) to boot by default with pci=nomsi. Tried it once and the
system came up without getting stuck. I will rebuild the kernel with
tickless enabled, since that appears to be a red herring, and will
report results when I have them.
I will also report to Toshiba and the BIOS supplier (Phoenix --
SecureCore v1.40).
/Don
>
>>
>> /Don
>>
>> >
>> >
>> > since you're losing interrupts.. another good option to try is
>> > "irqpoll"
>> >
>> >
>> > --
>> > Arjan van de Ven Intel Open Source Technology Centre
>> > For development, discussion and tips for power savings,
>> > visit http://www.lesswatts.org
>> >
>
>
> --
> Arjan van de Ven Intel Open Source Technology Centre
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
>
^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2010-05-17 16:15 UTC | newest]
Thread overview: 23+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-11 0:18 PROBLEM: tickless scheduling Donald Allen
2010-05-11 0:27 ` Robert Hancock
2010-05-11 0:34 ` Donald Allen
2010-05-11 0:38 ` Robert Hancock
2010-05-11 0:53 ` Donald Allen
2010-05-11 0:54 ` john stultz
2010-05-11 0:59 ` Donald Allen
2010-05-11 1:12 ` john stultz
2010-05-11 1:52 ` Donald Allen
2010-05-12 19:54 ` Donald Allen
2010-05-12 20:52 ` john stultz
2010-05-15 17:11 ` Donald Allen
2010-05-16 16:14 ` Stefan Biereigel
2010-05-16 20:41 ` Arjan van de Ven
2010-05-17 15:26 ` Donald Allen
2010-05-17 16:15 ` Stefan Biereigel
2010-05-16 23:36 ` Thomas Gleixner
2010-05-17 13:44 ` Donald Allen
2010-05-17 14:02 ` Donald Allen
2010-05-17 14:04 ` Arjan van de Ven
2010-05-17 14:11 ` Donald Allen
2010-05-17 14:29 ` Arjan van de Ven
2010-05-17 14:45 ` Donald Allen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).