FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 06-26-2012, 10:46 AM
Martin Steigerwald
 
Default Bug#679094: linux-image-3.4-trunk-amd64: 3.2, 3.3 and 3.4 debian kernels lack latencytop support

Package: linux-2.6
Version: 3.4.1-1~experimental.1
Severity: normal

Dear Maintainer,

On reporting

latencytop: fails with error "no protocol specified" I found:
http://bugs.debian.org/679091


I found:

ms@mango:~> sux
Passwort:
xauth: file /root/.Xauthority does not exist
bash: Kann die Prozessgruppe des Terminals nicht setzen (-1).: Unpassender IOCTL (I/O-Control) für das Gerät
bash: Keine Job Steuerung in dieser Shell.
mango:/home/ms# latencytop
mount: none already mounted or /sys/kernel/debug/ busy
mount: according to mtab, none is already mounted on /sys/kernel/debug
Please enable the CONFIG_LATENCYTOP configuration in your kernel.
Exiting...


The current Debian kernels all lack latencytop support:

mango:~# grep LATENCY /boot/config-*
/boot/config-3.2.0-2-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y
/boot/config-3.2.0-2-amd64:# CONFIG_LATENCYTOP is not set
/boot/config-3.3.0-trunk-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y
/boot/config-3.3.0-trunk-amd64:# CONFIG_LATENCYTOP is not set
/boot/config-3.4-trunk-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y
/boot/config-3.4-trunk-amd64:# CONFIG_LATENCYTOP is not set


Please consider activating this support again.

Otherwise someone who wants to use latencytop needs to recompile the
kernel which greatly reduces the usefulness of the latencytop package.

Thanks,
Martin

-- Package-specific info:
** Version:
Linux version 3.4-trunk-amd64 (Debian 3.4.1-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Wed Jun 6 10:34:53 CEST 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.4-trunk-amd64 root=UUID=459c3940-f915-460f-a673-386121d7a8c6 ro resume=/dev/sda7 no_console_suspend

** Tainted: WO (4608)
* Taint on warning.
* Out-of-tree module has been loaded.

** Kernel log:
[ 8225.257334] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
[ 8225.257337] snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X
[ 8225.257376] ehci_hcd 0000:00:1d.0: setting latency timer to 64
[ 8225.257389] usb usb2: root hub lost power or was reset
[ 8225.257396] pci 0000:00:1e.0: setting latency timer to 64
[ 8225.257413] ahci 0000:00:1f.2: setting latency timer to 64
[ 8225.261287] ehci_hcd 0000:00:1d.0: cache line size of 32 is not supported
[ 8225.306523] parport_pc 00:0a: activated
[ 8225.306774] serial 00:0b: activated
[ 8225.577530] ata8: SATA link down (SStatus 0 SControl 300)
[ 8225.577561] ata7: SATA link down (SStatus 0 SControl 300)
[ 8225.577591] ata5: SATA link down (SStatus 0 SControl 300)
[ 8225.613435] usb 1-1: reset high-speed USB device number 2 using ehci_hcd
[ 8225.749017] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 8225.749107] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 8225.749137] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 8225.752692] ata4.00: configured for UDMA/100
[ 8225.755299] ata3.00: configured for UDMA/133
[ 8225.755417] sd 2:0:0:0: [sda] Starting disk
[ 8225.757292] ata6.00: configured for UDMA/133
[ 8225.757367] sd 5:0:0:0: [sdb] Starting disk
[ 8225.856806] usb 2-1: reset high-speed USB device number 2 using ehci_hcd
[ 8226.060330] usb 1-1.4: reset high-speed USB device number 3 using ehci_hcd
[ 8227.038062] usb 2-1.8: reset low-speed USB device number 4 using ehci_hcd
[ 8227.576710] usb 2-1.7: reset low-speed USB device number 3 using ehci_hcd
[ 8227.870701] PM: restore of devices complete after 2624.032 msecs
[ 8227.870807] PM: Image restored successfully.
[ 8227.870809] Restarting tasks ... done.
[ 8227.873014] PM: Basic memory bitmaps freed
[ 8228.008570] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 8903.147658] scsi_verify_blk_ioctl: 444 callbacks suppressed
[ 8903.147664] mdadm: sending ioctl 1261 to a partition!
[ 8903.147668] mdadm: sending ioctl 1261 to a partition!
[ 8903.294210] mdadm: sending ioctl 1261 to a partition!
[ 8903.294217] mdadm: sending ioctl 1261 to a partition!
[ 8903.385724] mdadm: sending ioctl 1261 to a partition!
[ 8903.385728] mdadm: sending ioctl 1261 to a partition!
[ 8903.489773] mdadm: sending ioctl 1261 to a partition!
[ 8903.489780] mdadm: sending ioctl 1261 to a partition!
[ 8903.649346] mdadm: sending ioctl 1261 to a partition!
[ 8903.649350] mdadm: sending ioctl 1261 to a partition!
[ 8908.319036] scsi_verify_blk_ioctl: 44 callbacks suppressed
[ 8908.319039] mdadm: sending ioctl 1261 to a partition!
[ 8908.319041] mdadm: sending ioctl 1261 to a partition!
[ 8908.415940] mdadm: sending ioctl 1261 to a partition!
[ 8908.415947] mdadm: sending ioctl 1261 to a partition!
[ 8908.884496] JFS: nTxBlock = 8192, nTxLock = 65536
[ 8908.935072] NTFS driver 2.1.30 [Flags: R/W MODULE].
[ 8908.995222] QNX4 filesystem 0.2.3 registered.
[ 8909.024033] fuse init (API version 7.18)
[ 8910.918371] blockdev: sending ioctl 125d to a partition!
[ 8910.918377] blockdev: sending ioctl 125d to a partition!
[ 8910.931572] blockdev: sending ioctl 125d to a partition!
[ 8910.931579] blockdev: sending ioctl 125d to a partition!
[ 8912.293901] blockdev: sending ioctl 125d to a partition!
[ 8912.293908] blockdev: sending ioctl 125d to a partition!
[ 8913.351698] scsi_verify_blk_ioctl: 10 callbacks suppressed
[ 8913.351704] blockdev: sending ioctl 125d to a partition!
[ 8913.351709] blockdev: sending ioctl 125d to a partition!
[ 8913.358008] blockdev: sending ioctl 125d to a partition!
[ 8913.358015] blockdev: sending ioctl 125d to a partition!
[ 8918.864451] mdadm: sending ioctl 1261 to a partition!
[ 8918.864455] mdadm: sending ioctl 1261 to a partition!
[ 8918.954252] mdadm: sending ioctl 1261 to a partition!
[ 8918.954256] mdadm: sending ioctl 1261 to a partition!
[ 8919.021224] mdadm: sending ioctl 1261 to a partition!
[ 8919.021228] mdadm: sending ioctl 1261 to a partition!
[ 8919.121668] mdadm: sending ioctl 1261 to a partition!
[ 8919.121672] mdadm: sending ioctl 1261 to a partition!
[ 8919.202569] mdadm: sending ioctl 1261 to a partition!
[ 8919.202573] mdadm: sending ioctl 1261 to a partition!
[11867.701992] BUG: Bad rss-counter state mm:ffff88032b082440 idx:1 val:-1
[11867.701996] BUG: Bad rss-counter state mm:ffff88032b082440 idx:2 val:1
[14637.135121] Netfilter messages via NETLINK v0.30.
[14637.152407] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[14637.161669] ctnetlink v0.93: registering with nfnetlink.
[14687.514360] ip_tables: (C) 2000-2006 Netfilter Core Team
[15550.329184] NET: Unregistered protocol family 11
[18464.704762] Bluetooth: Core ver 2.16
[18464.704795] NET: Registered protocol family 31
[18464.704800] Bluetooth: HCI device and connection manager initialized
[18464.704805] Bluetooth: HCI socket layer initialized
[18464.704809] Bluetooth: L2CAP socket layer initialized
[18464.704819] Bluetooth: SCO socket layer initialized
[18609.914865] ------------[ cut here ]------------
[18609.914875] WARNING: at /media/data/mattems/src/linux-2.6-3.4.1/debian/build/source_amd64_none/kernel/trace/trace.c:2933 tracing_ctrl_write+0x85/0xfa()
[18609.914878] Hardware name: ESPRIMO P9900
[18609.914879] tracing_enabled is deprecated. Use tracing_on
[18609.914881] Modules linked in: bluetooth rfkill msr cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats nf_conntrack_ipv4 nf_defrag_ipv4 xt_state iptable_filter ip_tables x_tables nf_conntrack_netlink nf_conntrack nfnetlink fuse ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs reiserfs ext3 jbd ext2 pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ppdev lp cachefiles nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc appletalk ipx p8023 netrom ax25 ext4 crc16 jbd2 mbcache loop snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc psmouse parport_pc parport i915 evdev drm_kms_helper i2c_i801 snd_timer drm i2c_algo_bit acpi_cpufreq mperf iTCO_wdt coretemp iTCO_vendor_support snd pcspkr serio_raw i2c_core soundcore container video tpm_tis tpm tpm_bios processor crc32c_intel microcode button thermal_sys xfs btrfs crc32c libcrc32c zlib_deflate dm_mod usbhid hid usb_storage uas raid1 md_mod sd_mod sr_m
od cdrom
crc_t10dif ehci_hcd usbcore usb_common ahci libahci ata_generic e1000e libata scsi_mod [last unloaded: rose]
[18609.914971] Pid: 21453, comm: latencytop Tainted: G O 3.4-trunk-amd64 #1
[18609.914974] Call Trace:
[18609.914981] [<ffffffff81039697>] ? warn_slowpath_common+0x78/0x8c
[18609.914984] [<ffffffff81039743>] ? warn_slowpath_fmt+0x45/0x4a
[18609.914989] [<ffffffff81057ccf>] ? should_resched+0x5/0x23
[18609.914995] [<ffffffff81358cd6>] ? _cond_resched+0x6/0x1b
[18609.914997] [<ffffffff810a15f8>] ? tracing_ctrl_write+0x85/0xfa
[18609.915001] [<ffffffff810fe0ec>] ? vfs_write+0xa2/0xe9
[18609.915003] [<ffffffff810fe2c9>] ? sys_write+0x45/0x6b
[18609.915008] [<ffffffff8135e779>] ? system_call_fastpath+0x16/0x1b
[18609.915010] ---[ end trace f75088e2f0b0fe06 ]---

** Model information
sys_vendor: FUJITSU
product_name: ESPRIMO P9900
product_version:
chassis_vendor: FUJITSU
chassis_version: C$PIP4
bios_vendor: FUJITSU // Phoenix Technologies Ltd.
bios_version: 6.00 R1.20.2912.A1
board_vendor: FUJITSU
board_name: D2912-A1
board_version: S26361-D2912-A1

** Loaded modules:
bluetooth
rfkill
msr
cpufreq_conservative
cpufreq_powersave
cpufreq_userspace
cpufreq_stats
nf_conntrack_ipv4
nf_defrag_ipv4
xt_state
iptable_filter
ip_tables
x_tables
nf_conntrack_netlink
nf_conntrack
nfnetlink
fuse
ufs
qnx4
hfsplus
hfs
minix
ntfs
vfat
msdos
fat
jfs
reiserfs
ext3
jbd
ext2
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
ppdev
lp
cachefiles
nfsd
nfs
nfs_acl
auth_rpcgss
fscache
lockd
sunrpc
appletalk
ipx
p8023
netrom
ax25
ext4
crc16
jbd2
mbcache
loop
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_intel
snd_hda_codec
snd_hwdep
snd_pcm
snd_page_alloc
psmouse
parport_pc
parport
i915
evdev
drm_kms_helper
i2c_i801
snd_timer
drm
i2c_algo_bit
acpi_cpufreq
mperf
iTCO_wdt
coretemp
iTCO_vendor_support
snd
pcspkr
serio_raw
i2c_core
soundcore
container
video
tpm_tis
tpm
tpm_bios
processor
crc32c_intel
microcode
button
thermal_sys
xfs
btrfs
crc32c
libcrc32c
zlib_deflate
dm_mod
usbhid
hid
usb_storage
uas
raid1
md_mod
sd_mod
sr_mod
cdrom
crc_t10dif
ehci_hcd
usbcore
usb_common
ahci
libahci
ata_generic
e1000e
libata
scsi_mod

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0040] (rev 02)
Subsystem: Fujitsu Technology Solutions Device [1734:1168]
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: <access denied>
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Fujitsu Technology Solutions Device [1734:1168]
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 42
Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 1890 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915

00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
Subsystem: Fujitsu Technology Solutions Device [1734:1168]
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 11
Region 0: Memory at f0424000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>

00:16.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset PT IDER Controller [8086:3b66] (rev 06) (prog-if 85 [Master SecO PriO])
Subsystem: Fujitsu Technology Solutions Device [1734:1168]
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 C routed to IRQ 22
Region 0: I/O ports at 18a8 [size=8]
Region 1: I/O ports at 189c [size=4]
Region 2: I/O ports at 18a0 [size=8]
Region 3: I/O ports at 1898 [size=4]
Region 4: I/O ports at 1880 [size=16]
Capabilities: <access denied>
Kernel driver in use: ata_generic

00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400 Series Chipset KT Controller [8086:3b67] (rev 06) (prog-if 02 [16550])
Subsystem: Fujitsu Technology Solutions Device [1734:1168]
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 B routed to IRQ 21
Region 0: I/O ports at 18b0 [size=8]
Region 1: Memory at f0426000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: serial

00:19.0 Ethernet controller [0200]: Intel Corporation 82578DM Gigabit Network Connection [8086:10ef] (rev 05)
Subsystem: Fujitsu Technology Solutions Device [1734:1174]
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 40
Region 0: Memory at f0400000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f0427000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 1820 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e

00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) (prog-if 20 [EHCI])
Subsystem: Fujitsu Technology Solutions Device [1734:1167]
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 19
Region 0: Memory at f0428000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd

00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05)
Subsystem: Fujitsu Technology Solutions Device [1734:118c]
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 43
Region 0: Memory at f0420000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) (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: 00002000-00002fff
Memory behind bridge: c0000000-c01fffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
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: <access denied>
Kernel driver in use: pcieport

00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05) (prog-if 20 [EHCI])
Subsystem: Fujitsu Technology Solutions Device [1734:1167]
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 20
Region 0: Memory at f0429000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5) (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
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: <access denied>

00:1f.0 ISA bridge [0601]: Intel Corporation 5 Series Chipset LPC Interface Controller [8086:3b0a] (rev 05)
Subsystem: Fujitsu Technology Solutions Device [1734:1167]
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: <access denied>

00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b22] (rev 05) (prog-if 01 [AHCI 1.0])
Subsystem: Fujitsu Technology Solutions Device [1734:1167]
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 41
Region 0: I/O ports at 18c8 [size=8]
Region 1: I/O ports at 18bc [size=4]
Region 2: I/O ports at 18c0 [size=8]
Region 3: I/O ports at 18b8 [size=4]
Region 4: I/O ports at 1840 [size=32]
Region 5: Memory at f042a000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 05)
Subsystem: Fujitsu Technology Solutions Device [1734:1167]
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 D routed to IRQ 18
Region 0: Memory at f042b000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at 1860 [size=32]
Kernel driver in use: i801_smbus

ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c61] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
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

ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
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

ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
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

ff:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2d11] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
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

ff:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d12] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
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

ff:02.3 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d13] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
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


** USB devices:
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 003: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 002 Device 004: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)


-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (450, 'unstable'), (110, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.4-trunk-amd64 depends on:
ii debconf [debconf-2.0] 1.5.43
ii initramfs-tools [linux-initramfs-tool] 0.106
ii kmod 8-2
ii linux-base 3.5
ii module-init-tools 8-2

Versions of packages linux-image-3.4-trunk-amd64 recommends:
ii firmware-linux-free 3

Versions of packages linux-image-3.4-trunk-amd64 suggests:
ii grub-pc 1.99-22.1
ii linux-doc-3.4 3.4.1-1~experimental.1

Versions of packages linux-image-3.4-trunk-amd64 is related to:
pn firmware-atheros <none>
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-brcm80211 <none>
pn firmware-intelwimax <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-libertas <none>
pn firmware-linux <none>
pn firmware-linux-nonfree <none>
pn firmware-myricom <none>
pn firmware-netxen <none>
pn firmware-qlogic <none>
pn firmware-ralink <none>
pn firmware-realtek <none>
pn xen-hypervisor <none>

-- debconf information:
linux-image-3.4-trunk-amd64/postinst/missing-firmware-3.4-trunk-amd64:
linux-image-3.4-trunk-amd64/prerm/removing-running-kernel-3.4-trunk-amd64: true
linux-image-3.4-trunk-amd64/postinst/depmod-error-initrd-3.4-trunk-amd64: false
linux-image-3.4-trunk-amd64/postinst/ignoring-ramdisk:



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120626104614.23032.7998.reportbug@mango.of.teami x.net">http://lists.debian.org/20120626104614.23032.7998.reportbug@mango.of.teami x.net
 
Old 06-27-2012, 03:11 AM
Ben Hutchings
 
Default Bug#679094: linux-image-3.4-trunk-amd64: 3.2, 3.3 and 3.4 debian kernels lack latencytop support

On Tue, 2012-06-26 at 12:46 +0200, Martin Steigerwald wrote:
[...]
> The current Debian kernels all lack latencytop support:
[...]
> Please consider activating this support again.

What do you mean, 'again'?

> Otherwise someone who wants to use latencytop needs to recompile the
> kernel which greatly reduces the usefulness of the latencytop package.

This costs 1680 or 3360 bytes of non-paged memory for every thread in
the system (depending on word size), even if the feature is never
actually used. On my laptop, for example, this would be about a
megabyte. I really don't think this is a good idea.

It is probably possible to change the way the latency records are kept
so that this memory is allocated only when needed, but I'm unlikely to
find the time to do that.

Ben.

--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
 
Old 06-27-2012, 08:34 AM
Martin Steigerwald
 
Default Bug#679094: linux-image-3.4-trunk-amd64: 3.2, 3.3 and 3.4 debian kernels lack latencytop support

Am Mittwoch, 27. Juni 2012 schrieb Ben Hutchings:
> On Tue, 2012-06-26 at 12:46 +0200, Martin Steigerwald wrote:
> [...]
>
> > The current Debian kernels all lack latencytop support:
> [...]
>
> > Please consider activating this support again.
>
> What do you mean, 'again'?

I thought this was once working out of the box, but maybe that was at a time
where I compiled my own kernels and had it enabled.

> > Otherwise someone who wants to use latencytop needs to recompile the
> > kernel which greatly reduces the usefulness of the latencytop package.
>
> This costs 1680 or 3360 bytes of non-paged memory for every thread in
> the system (depending on word size), even if the feature is never
> actually used. On my laptop, for example, this would be about a
> megabyte. I really don't think this is a good idea.

I found out that it will need the framepointer stuff which makes the kernel
slightly larger and slower only after writing the bug report.

While I do not care that much about the megabyte given current memory sizes, I
am concerned about the "slightly slower". And then its declared as kernel
hacking feature in the configuration anyway. And for older / embedded machines
1 MiB might be much.

So I can understand your reasoning. Feel free to close as won't fix or
"dependent / waiting for upstream fix" if thats possible.

> It is probably possible to change the way the latency records are kept
> so that this memory is allocated only when needed, but I'm unlikely to
> find the time to do that.

Care to elaborate on that one a bit. I am willing to open a upstream bug
report about that and include your idea and a reference to this debian bug
report.

Thanks,
--
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201206271034.43139.ms@teamix.de">http://lists.debian.org/201206271034.43139.ms@teamix.de
 
Old 06-27-2012, 02:04 PM
Ben Hutchings
 
Default Bug#679094: linux-image-3.4-trunk-amd64: 3.2, 3.3 and 3.4 debian kernels lack latencytop support

On Wed, 2012-06-27 at 10:34 +0200, Martin Steigerwald wrote:
> Am Mittwoch, 27. Juni 2012 schrieb Ben Hutchings:
> > On Tue, 2012-06-26 at 12:46 +0200, Martin Steigerwald wrote:
> > [...]
> >
> > > The current Debian kernels all lack latencytop support:
> > [...]
> >
> > > Please consider activating this support again.
> >
> > What do you mean, 'again'?
>
> I thought this was once working out of the box, but maybe that was at a time
> where I compiled my own kernels and had it enabled.

I think it must have been, as there is no record of this in the
changelog.

> > > Otherwise someone who wants to use latencytop needs to recompile the
> > > kernel which greatly reduces the usefulness of the latencytop package.
> >
> > This costs 1680 or 3360 bytes of non-paged memory for every thread in
> > the system (depending on word size), even if the feature is never
> > actually used. On my laptop, for example, this would be about a
> > megabyte. I really don't think this is a good idea.
>
> I found out that it will need the framepointer stuff which makes the kernel
> slightly larger and slower only after writing the bug report.

I didn't even get as far as that, but yes. This would particularly hurt
i386 which is short of registers.

> While I do not care that much about the megabyte given current memory sizes, I
> am concerned about the "slightly slower". And then its declared as kernel
> hacking feature in the configuration anyway. And for older / embedded machines
> 1 MiB might be much.
>
> So I can understand your reasoning. Feel free to close as won't fix or
> "dependent / waiting for upstream fix" if thats possible.
>
> > It is probably possible to change the way the latency records are kept
> > so that this memory is allocated only when needed, but I'm unlikely to
> > find the time to do that.
>
> Care to elaborate on that one a bit. I am willing to open a upstream bug
> report about that and include your idea and a reference to this debian bug
> report.

The definition of struct task_struct includes:

#ifdef CONFIG_LATENCYTOP
int latency_record_count;
struct latency_record latency_record[LT_SAVECOUNT];
#endif

I was thinking that latency_record could be changed to a pointer, and
the array allocated only when latency tracing is turned on. This should
be easy to do for new tasks; harder if existing tasks should also be
traced.

Ben.

--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
 

Thread Tools




All times are GMT. The time now is 12:35 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org