All of lore.kernel.org
 help / color / mirror / Atom feed
* High latencies on MPC5200 with patch-2.6.24-rc5-rt1
@ 2008-01-08 10:13 Wolfgang Grandegger
  2008-01-08 15:49 ` Robert Schwebel
  0 siblings, 1 reply; 17+ messages in thread
From: Wolfgang Grandegger @ 2008-01-08 10:13 UTC (permalink / raw)
  To: linux-rt-users

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

Hello,

I gave -rt another try on my Icecube-MPC5200 board with
patch-2.6.24-rc5-rt1 and this time I got it working with the attached
little patch fixing an oops in the serial driver. Unfortunately,
cyclictest reports rather high latencies up to 500 us under load:

# ./cyclictest -n -p80 -t1 -i10000
3.55 2.82 1.55 2/45 9971

T: 0 (  922) P:80 I:10000 C: 64228 Min: 28 Act: 71 Avg: 78 Max: 502

Any ideas why the latencies are that high or how to hunt the latency
evils. The nice latency tracer is not available for PowerPC. I have
attached my .config as well.

TIA.

Wolfgang.


[-- Attachment #2: linux-2.6-rt-mpc5200-serial.patch --]
[-- Type: text/x-patch, Size: 419 bytes --]

diff --git a/drivers/serial/mpc52xx_uart.c b/drivers/serial/mpc52xx_uart.c
index ec36ad7..8939405 100644
--- a/drivers/serial/mpc52xx_uart.c
+++ b/drivers/serial/mpc52xx_uart.c
@@ -501,7 +501,9 @@ mpc52xx_uart_int_rx_chars(struct uart_port *port)
 		}
 	}
 
+	spin_unlock(&port->lock);
 	tty_flip_buffer_push(tty);
+	spin_lock(&port->lock);
 
 	return in_be16(&PSC(port)->mpc52xx_psc_status) & MPC52xx_PSC_SR_RXRDY;
 }

[-- Attachment #3: .config --]
[-- Type: text/plain, Size: 21270 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24-rc5-rt1
# Sun Dec 30 21:39:43 2007
#
# CONFIG_PPC64 is not set

#
# Processor support
#
CONFIG_6xx=y
# CONFIG_PPC_85xx is not set
# CONFIG_PPC_8xx is not set
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_E200 is not set
CONFIG_PPC_FPU=y
# CONFIG_ALTIVEC is not set
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_STD_MMU_32=y
# CONFIG_PPC_MM_SLICES is not set
# CONFIG_SMP is not set
CONFIG_PPC32=y
CONFIG_WORD_SIZE=32
CONFIG_PPC_MERGE=y
CONFIG_MMU=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_IRQ_PER_CPU=y
CONFIG_ARCH_HAS_ILOG2_U32=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
# CONFIG_ARCH_NO_VIRT_TO_BUS is not set
CONFIG_PPC=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_NVRAM=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_PPC_OF=y
CONFIG_OF=y
# CONFIG_PPC_UDBG_16550 is not set
# CONFIG_GENERIC_TBSYNC is not set
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
# CONFIG_DEFAULT_UIMAGE is not set
# CONFIG_PPC_DCR_NATIVE is not set
# CONFIG_PPC_DCR_MMIO is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_CGROUPS is not set
# CONFIG_FAIR_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_RADIX_TREE_CONCURRENT is not set
CONFIG_EMBEDDED=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
# CONFIG_EPOLL is not set
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"

#
# Platform support
#
CONFIG_PPC_MULTIPLATFORM=y
# CONFIG_PPC_82xx is not set
# CONFIG_PPC_83xx is not set
# CONFIG_PPC_86xx is not set
CONFIG_CLASSIC32=y
# CONFIG_PPC_CHRP is not set
CONFIG_PPC_MPC52xx=y
CONFIG_PPC_MPC5200=y
CONFIG_PPC_MPC5200_BUGFIX=y
# CONFIG_PPC_EFIKA is not set
CONFIG_PPC_LITE5200=y
# CONFIG_PPC_PMAC is not set
# CONFIG_PPC_CELL is not set
# CONFIG_PPC_CELL_NATIVE is not set
# CONFIG_PQ2ADS is not set
# CONFIG_EMBEDDED6xx is not set
# CONFIG_MPIC is not set
# CONFIG_MPIC_WEIRD is not set
# CONFIG_PPC_I8259 is not set
# CONFIG_PPC_RTAS is not set
# CONFIG_MMIO_NVRAM is not set
# CONFIG_PPC_MPC106 is not set
# CONFIG_PPC_970_NAP is not set
# CONFIG_PPC_INDIRECT_IO is not set
# CONFIG_GENERIC_IOMAP is not set
# CONFIG_CPU_FREQ is not set
# CONFIG_TAU is not set
# CONFIG_CPM2 is not set
# CONFIG_FSL_ULI1575 is not set
CONFIG_PPC_BESTCOMM=y
CONFIG_PPC_BESTCOMM_ATA=y
CONFIG_PPC_BESTCOMM_FEC=y
CONFIG_PPC_BESTCOMM_GEN_BD=y

#
# Kernel options
#
# CONFIG_HIGHMEM is not set
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
# CONFIG_CLASSIC_RCU is not set
CONFIG_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU_BOOST=y
CONFIG_RCU_TRACE=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_ASM_SEMAPHORES=y
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
# CONFIG_KEXEC is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_PROC_DEVICETREE=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_UP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_UP_POSSIBLE=y
# CONFIG_HIBERNATION is not set
CONFIG_SECCOMP=y
CONFIG_WANT_DEVICE_TREE=y
CONFIG_DEVICE_TREE=""
CONFIG_ISA_DMA_API=y

#
# Bus options
#
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
# CONFIG_PPC_INDIRECT_PCI is not set
CONFIG_FSL_SOC=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_SYSCALL=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Advanced setup
#
# CONFIG_ADVANCED_OPTIONS is not set

#
# Default settings for advanced configuration options are used
#
CONFIG_HIGHMEM_START=0xfe000000
CONFIG_LOWMEM_SIZE=0x30000000
CONFIG_KERNEL_START=0xc0000000
CONFIG_TASK_SIZE=0xc0000000
CONFIG_BOOT_LOAD=0x00800000

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set

#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
CONFIG_OF_DEVICE=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=32768
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_MISC_DEVICES=y
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
CONFIG_PATA_MPC52xx=y
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_MD is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_IP1000 is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_FIXED_PHY is not set
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_NET_PCI is not set
# CONFIG_B44 is not set
CONFIG_FEC_MPC52xx=y
CONFIG_FEC_MPC52xx_MDIO=y
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
# CONFIG_INPUT is not set

#
# Hardware I/O ports
#
# CONFIG_SERIO is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
# CONFIG_VT is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_MPC52xx=y
CONFIG_SERIAL_MPC52xx_CONSOLE=y
CONFIG_SERIAL_MPC52xx_CONSOLE_BAUD=9600
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_GEN_RTC is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
CONFIG_RMEM=m
CONFIG_ALLOC_RTSJ_MEM=m
CONFIG_DEVPORT=y
# CONFIG_I2C is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_WATCHDOG is not set

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Sound
#
# CONFIG_SOUND is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
# CONFIG_USB is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set

#
# Userspace I/O
#
# CONFIG_UIO is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_NFSD is not set
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_BIND34 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_NLS is not set
# CONFIG_DLM is not set
# CONFIG_UCC_SLOW is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
# CONFIG_INSTRUMENTATION is not set

#
# Kernel hacking
#
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
CONFIG_PREEMPT_TRACE=y
CONFIG_EVENT_TRACE=y
CONFIG_FUNCTION_TRACE=y
CONFIG_WAKEUP_TIMING=y
# CONFIG_LATENCY_TRACE is not set
# CONFIG_CRITICAL_PREEMPT_TIMING is not set
# CONFIG_CRITICAL_IRQSOFF_TIMING is not set
# CONFIG_WAKEUP_LATENCY_HIST is not set
CONFIG_CRITICAL_TIMING=y
CONFIG_LATENCY_TIMING=y
CONFIG_MCOUNT=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
CONFIG_FRAME_POINTER=y
CONFIG_FORCED_INLINING=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_SAMPLES is not set
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUGGER is not set
# CONFIG_VIRQ_DEBUG is not set
# CONFIG_BDI_SWITCH is not set
# CONFIG_BOOTX_TEXT is not set
# CONFIG_PPC_EARLY_DEBUG is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
# CONFIG_CRYPTO is not set
CONFIG_PPC_CLOCK=y
CONFIG_PPC_LIB_RHEAP=y

^ permalink raw reply related	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-08 10:13 High latencies on MPC5200 with patch-2.6.24-rc5-rt1 Wolfgang Grandegger
@ 2008-01-08 15:49 ` Robert Schwebel
  2008-01-08 16:41   ` Wolfgang Grandegger
  2008-01-09  9:03   ` Robert Schwebel
  0 siblings, 2 replies; 17+ messages in thread
From: Robert Schwebel @ 2008-01-08 15:49 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: linux-rt-users

Hi Wolfgang,

On Tue, Jan 08, 2008 at 11:13:11AM +0100, Wolfgang Grandegger wrote:
> I gave -rt another try on my Icecube-MPC5200 board with
> patch-2.6.24-rc5-rt1

Unfortunately, I only have 2.6.23.1-rt5 for the phyCORE-MPC5200B-tiny (400 MHz)
at the moment, but I can refactor it to match your version.

> and this time I got it working with the attached little patch fixing
> an oops in the serial driver. Unfortunately, cyclictest reports rather
> high latencies up to 500 us under load:

Can you elaborate which load you are using?

> # ./cyclictest -n -p80 -t1 -i10000
> 3.55 2.82 1.55 2/45 9971
> 
> T: 0 (  922) P:80 I:10000 C: 64228 Min: 28 Act: 71 Avg: 78 Max: 502

This is on an idle system:

----------8<----------
root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 64228
1.96 1.85 1.18 1/47 572          

T: 0 (  534) P:80 I:   10000 C:   64228 Min:      21 Act:      39 Avg:      38 Max:      77
----------8<----------

This is under ping -f load:

----------8<----------
root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 64228
2.64 2.25 1.60 1/47 632

T: 0 (  594) P:80 I:   10000 C:   64228 Min:      24 Act:      41 Avg:      44 Max:      82
----------8<----------

And under "(while true; do hackbench 10; done) &" load:

----------8<----------
367.51 329.66 189.94 7/449 4284

T: 0 ( 1439) P:80 I:   10000 C:   64228 Min:      28 Act:      48 Avg:      49 Max:      88
----------8<----------

Doesn't look too bad.

rsc
-- 
 Robert Schwebel              |  http://www.pengutronix.de
 OSADL Testlab @ Pengutronix  |  http://www.osadl.org

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-08 15:49 ` Robert Schwebel
@ 2008-01-08 16:41   ` Wolfgang Grandegger
  2008-01-08 20:40     ` Robert Schwebel
  2008-01-08 21:25     ` Juergen Beisert
  2008-01-09  9:03   ` Robert Schwebel
  1 sibling, 2 replies; 17+ messages in thread
From: Wolfgang Grandegger @ 2008-01-08 16:41 UTC (permalink / raw)
  To: Robert Schwebel; +Cc: linux-rt-users

Robert Schwebel wrote:
> Hi Wolfgang,
> 
> On Tue, Jan 08, 2008 at 11:13:11AM +0100, Wolfgang Grandegger wrote:
>> I gave -rt another try on my Icecube-MPC5200 board with
>> patch-2.6.24-rc5-rt1
> 
> Unfortunately, I only have 2.6.23.1-rt5 for the phyCORE-MPC5200B-tiny (400 MHz)
> at the moment, but I can refactor it to match your version.

You are obviously using a 2.6.23.1 with private patches for MPC5200 as
there is no FEC driver or no clock event support in that version. The
_official_ 2.6.24-rc5 finally builds fine and works for my
Icecube-Eval-Board :-). Yes, it would make sense to add board support
for the phyCORE-MPC5200B-tiny for that version.

>> and this time I got it working with the attached little patch fixing
>> an oops in the serial driver. Unfortunately, cyclictest reports rather
>> high latencies up to 500 us under load:
> 
> Can you elaborate which load you are using?

"while ls; do ls; done" in a telnet window, "ping -f <host-ip>" and the
cache calibrator.

>> # ./cyclictest -n -p80 -t1 -i10000
>> 3.55 2.82 1.55 2/45 9971
>>
>> T: 0 (  922) P:80 I:10000 C: 64228 Min: 28 Act: 71 Avg: 78 Max: 502
> 
> This is on an idle system:
> 
> ----------8<----------
> root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 64228
> 1.96 1.85 1.18 1/47 572          
> 
> T: 0 (  534) P:80 I:   10000 C:   64228 Min:      21 Act:      39 Avg:      38 Max:      77
> ----------8<----------
> 
> This is under ping -f load:
> 
> ----------8<----------
> root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 64228
> 2.64 2.25 1.60 1/47 632
> 
> T: 0 (  594) P:80 I:   10000 C:   64228 Min:      24 Act:      41 Avg:      44 Max:      82
> ----------8<----------
> 
> And under "(while true; do hackbench 10; done) &" load:
> 
> ----------8<----------
> 367.51 329.66 189.94 7/449 4284
> 
> T: 0 ( 1439) P:80 I:   10000 C:   64228 Min:      28 Act:      48 Avg:      49 Max:      88
> ----------8<----------
> 
> Doesn't look too bad.

Some time in the past I also measured much better values and likely
there is a problem with the official version.

Wolfgang.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-08 16:41   ` Wolfgang Grandegger
@ 2008-01-08 20:40     ` Robert Schwebel
  2008-01-08 21:25     ` Juergen Beisert
  1 sibling, 0 replies; 17+ messages in thread
From: Robert Schwebel @ 2008-01-08 20:40 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: linux-rt-users

On Tue, Jan 08, 2008 at 05:41:10PM +0100, Wolfgang Grandegger wrote:
> You are obviously using a 2.6.23.1 with private patches for MPC5200 as
> there is no FEC driver or no clock event support in that version.

Oops, sure, I should have noted. The patches are part of the -6 release
of the BSP:

http://www.pengutronix.de/oselas/bsp/phytec/download/phyCORE-MPC5200B-tiny/

> The _official_ 2.6.24-rc5 finally builds fine and works for my
> Icecube-Eval-Board :-). Yes, it would make sense to add board support
> for the phyCORE-MPC5200B-tiny for that version.

Sure, we'll do soon.

> > Can you elaborate which load you are using?
> 
> "while ls; do ls; done" in a telnet window, "ping -f <host-ip>" and the
> cache calibrator.

We need some well defined default loads for this kind of machines. I'll
post a proposal when we've collected our current ideas.

> Some time in the past I also measured much better values and likely
> there is a problem with the official version.

Yup. We are in the process of setting up an autobuilder for the
phyCORE-MPC5200B. It will hopefully soon find latency regressions in a
more systematic way.

Robert
-- 
 Robert Schwebel              |  http://www.pengutronix.de
 OSADL Testlab @ Pengutronix  |  http://www.osadl.org

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-08 16:41   ` Wolfgang Grandegger
  2008-01-08 20:40     ` Robert Schwebel
@ 2008-01-08 21:25     ` Juergen Beisert
  1 sibling, 0 replies; 17+ messages in thread
From: Juergen Beisert @ 2008-01-08 21:25 UTC (permalink / raw)
  To: linux-rt-users; +Cc: Wolfgang Grandegger

On Tuesday 08 January 2008 17:41, Wolfgang Grandegger wrote:
> Robert Schwebel wrote:
> > Hi Wolfgang,
> >
> > On Tue, Jan 08, 2008 at 11:13:11AM +0100, Wolfgang Grandegger wrote:
> >> I gave -rt another try on my Icecube-MPC5200 board with
> >> patch-2.6.24-rc5-rt1
> >
> > Unfortunately, I only have 2.6.23.1-rt5 for the phyCORE-MPC5200B-tiny
> > (400 MHz) at the moment, but I can refactor it to match your version.
>
> You are obviously using a 2.6.23.1 with private patches for MPC5200 as
> there is no FEC driver or no clock event support in that version. The
> _official_ 2.6.24-rc5 finally builds fine and works for my
> Icecube-Eval-Board :-). Yes, it would make sense to add board support
> for the phyCORE-MPC5200B-tiny for that version.
>
> >> and this time I got it working with the attached little patch fixing
> >> an oops in the serial driver. Unfortunately, cyclictest reports rather
> >> high latencies up to 500 us under load:
> >
> > Can you elaborate which load you are using?
>
> "while ls; do ls; done" in a telnet window, "ping -f <host-ip>" and the
> cache calibrator.
>
> >> # ./cyclictest -n -p80 -t1 -i10000
> >> 3.55 2.82 1.55 2/45 9971
> >>
> >> T: 0 (  922) P:80 I:10000 C: 64228 Min: 28 Act: 71 Avg: 78 Max: 502

Please try to run cyclictest with "-q" (=avoid interrupts on serial or network 
connection) and test if it makes a difference.

Juergen
-- 
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
    Handelsregister: Amtsgericht Hildesheim, HRA 2686
         Vertretung Sued/Muenchen, Germany
   Phone: +49-8766-939 228 |  Fax: +49-5121-206917-9

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-08 15:49 ` Robert Schwebel
  2008-01-08 16:41   ` Wolfgang Grandegger
@ 2008-01-09  9:03   ` Robert Schwebel
  2008-01-09  9:50     ` Wolfgang Grandegger
  2008-01-09 22:51     ` Robert Schwebel
  1 sibling, 2 replies; 17+ messages in thread
From: Robert Schwebel @ 2008-01-09  9:03 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: Thomas Gleixner, linux-rt-users

On Tue, Jan 08, 2008 at 04:49:47PM +0100, Robert Schwebel wrote:
> This is on an idle system:

I've quickly ported the patch stack to 2.6.24-rc5-rt1, and it doesn't
really work:

----------8<----------
root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 1000
0.44 0.35 0.15 1/44 483

T: 0 (  483) P:80 I:   10000 C:     992 Min: -490034 Act: -410032 Avg: -243020 Max:     -10
----------8<----------

Even on an idle system I get negative values and a "running" Act value.

I'll have to clean up the patch stack and check what's going on.

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-09  9:03   ` Robert Schwebel
@ 2008-01-09  9:50     ` Wolfgang Grandegger
  2008-01-09 14:08       ` Robert Schwebel
  2008-01-09 22:51     ` Robert Schwebel
  1 sibling, 1 reply; 17+ messages in thread
From: Wolfgang Grandegger @ 2008-01-09  9:50 UTC (permalink / raw)
  To: Robert Schwebel; +Cc: Thomas Gleixner, linux-rt-users

Robert Schwebel wrote:
> On Tue, Jan 08, 2008 at 04:49:47PM +0100, Robert Schwebel wrote:
>> This is on an idle system:
> 
> I've quickly ported the patch stack to 2.6.24-rc5-rt1, and it doesn't
> really work:
> 
> ----------8<----------
> root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 1000
> 0.44 0.35 0.15 1/44 483
> 
> T: 0 (  483) P:80 I:   10000 C:     992 Min: -490034 Act: -410032 Avg: -243020 Max:     -10
> ----------8<----------
> 
> Even on an idle system I get negative values and a "running" Act value.
> 
> I'll have to clean up the patch stack and check what's going on.

Are the high-res timers enabled? I also need the patch for the serial
driver posted in a previous mail.

Wolfgang.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-09  9:50     ` Wolfgang Grandegger
@ 2008-01-09 14:08       ` Robert Schwebel
  0 siblings, 0 replies; 17+ messages in thread
From: Robert Schwebel @ 2008-01-09 14:08 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: Thomas Gleixner, linux-rt-users

On Wed, Jan 09, 2008 at 10:50:21AM +0100, Wolfgang Grandegger wrote:
> Robert Schwebel wrote:
> > On Tue, Jan 08, 2008 at 04:49:47PM +0100, Robert Schwebel wrote:
> >> This is on an idle system:
> > 
> > I've quickly ported the patch stack to 2.6.24-rc5-rt1, and it doesn't
> > really work:
> > 
> > ----------8<----------
> > root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 1000
> > 0.44 0.35 0.15 1/44 483
> > 
> > T: 0 (  483) P:80 I:   10000 C:     992 Min: -490034 Act: -410032 Avg: -243020 Max:     -10
> > ----------8<----------
> > 
> > Even on an idle system I get negative values and a "running" Act value.
> > 
> > I'll have to clean up the patch stack and check what's going on.
> 
> Are the high-res timers enabled? I also need the patch for the serial
> driver posted in a previous mail.

Nope, I have

CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_HZ_100=y
CONFIG_HZ=100
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
CONFIG_PREEMPT_RCU=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_ASM_SEMAPHORES=y

and your patch was already in, it was proposed by tglx here:

http://marc.info/?l=linux-rt-users&m=118539051805065&w=2

Thomas, can you apply the patch?

Robert
-- 
 Robert Schwebel              |  http://www.pengutronix.de
 OSADL Testlab @ Pengutronix  |  http://www.osadl.org

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-09  9:03   ` Robert Schwebel
  2008-01-09  9:50     ` Wolfgang Grandegger
@ 2008-01-09 22:51     ` Robert Schwebel
  2008-01-10  0:01       ` Robert Schwebel
  1 sibling, 1 reply; 17+ messages in thread
From: Robert Schwebel @ 2008-01-09 22:51 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: Thomas Gleixner, linux-rt-users

On Wed, Jan 09, 2008 at 10:03:45AM +0100, Robert Schwebel wrote:
> ----------8<----------
> root@phyCORE-MPC5200B-tiny:~ cyclictest -n -p80 -t1 -i10000 -l 1000
> 0.44 0.35 0.15 1/44 483
> 
> T: 0 (  483) P:80 I:   10000 C:     992 Min: -490034 Act: -410032 Avg: -243020 Max:     -10
> ----------8<----------

Mainline without -rt doesn't show the effect; I narrowed it down by
disabling patches, starting from the end of the series. Unfortunately,
not all patches can be disabled without breaking the build.

The latencies look normal when I disable these two patches:

	rt-time-starvation-fix.patch
	rt-time-starvation-fix-update.patch

Throwing in the versions from 2.6.23.3-rt5 doesn't help, the effect
stays the same. So I assume it is a side effect.

Robert	
-- 
 Robert Schwebel              |  http://www.pengutronix.de
 OSADL Testlab @ Pengutronix  |  http://www.osadl.org

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-09 22:51     ` Robert Schwebel
@ 2008-01-10  0:01       ` Robert Schwebel
  2008-01-10 13:17         ` Wolfgang Grandegger
  0 siblings, 1 reply; 17+ messages in thread
From: Robert Schwebel @ 2008-01-10  0:01 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: Thomas Gleixner, linux-rt-users, John Stultz

Wolfgang,

On Wed, Jan 09, 2008 at 11:51:07PM +0100, Robert Schwebel wrote:
> Throwing in the versions from 2.6.23.3-rt5 doesn't help, the effect
> stays the same. So I assume it is a side effect.

Can you test the following patch by John Stulz (thanks to John for the quick
help on irc!), which fixes the issues on my board:

----------8<----------
Index: linux-2.6.24-rc5/arch/powerpc/kernel/time.c
===================================================================
--- linux-2.6.24-rc5.orig/arch/powerpc/kernel/time.c
+++ linux-2.6.24-rc5/arch/powerpc/kernel/time.c
@@ -773,7 +773,7 @@ void update_vsyscall(struct timespec *wa
 	stamp_xsec = (u64) xtime.tv_nsec * XSEC_PER_SEC;
 	do_div(stamp_xsec, 1000000000);
 	stamp_xsec += (u64) xtime.tv_sec * XSEC_PER_SEC;
-	update_gtod(clock->cycle_last, stamp_xsec, t2x);
+	update_gtod(clock->cycle_last-clock->cycle_accumulated, stamp_xsec, t2x);
 }
 
 void update_vsyscall_tz(void)
----------8<----------

With this patch ontop of 2.6.24-rc5-rt1 plus the board support patches
for the phyCORE-MPC5200B-tiny, I get this result from cyclictest, again
under "(while true; do hackbench 10; done) &" load:

T: 0 (  867) P:80 I:   10000 C:  105002 Min:      31 Act:      48 Avg:      51 Max:      92

Robert
-- 
 Robert Schwebel              |  http://www.pengutronix.de
 OSADL Testlab @ Pengutronix  |  http://www.osadl.org

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-10  0:01       ` Robert Schwebel
@ 2008-01-10 13:17         ` Wolfgang Grandegger
  2008-01-10 14:35           ` Robert Schwebel
  2008-01-10 15:48           ` Juergen Beisert
  0 siblings, 2 replies; 17+ messages in thread
From: Wolfgang Grandegger @ 2008-01-10 13:17 UTC (permalink / raw)
  To: Robert Schwebel; +Cc: Thomas Gleixner, linux-rt-users, John Stultz

Hi Robert,

Robert Schwebel wrote:
> Wolfgang,
> 
> On Wed, Jan 09, 2008 at 11:51:07PM +0100, Robert Schwebel wrote:
>> Throwing in the versions from 2.6.23.3-rt5 doesn't help, the effect
>> stays the same. So I assume it is a side effect.
> 
> Can you test the following patch by John Stulz (thanks to John for the quick
> help on irc!), which fixes the issues on my board:
> 
> ----------8<----------
> Index: linux-2.6.24-rc5/arch/powerpc/kernel/time.c
> ===================================================================
> --- linux-2.6.24-rc5.orig/arch/powerpc/kernel/time.c
> +++ linux-2.6.24-rc5/arch/powerpc/kernel/time.c
> @@ -773,7 +773,7 @@ void update_vsyscall(struct timespec *wa
>  	stamp_xsec = (u64) xtime.tv_nsec * XSEC_PER_SEC;
>  	do_div(stamp_xsec, 1000000000);
>  	stamp_xsec += (u64) xtime.tv_sec * XSEC_PER_SEC;
> -	update_gtod(clock->cycle_last, stamp_xsec, t2x);
> +	update_gtod(clock->cycle_last-clock->cycle_accumulated, stamp_xsec, t2x);
>  }
>  
>  void update_vsyscall_tz(void)
> ----------8<----------
> 
> With this patch ontop of 2.6.24-rc5-rt1 plus the board support patches
> for the phyCORE-MPC5200B-tiny, I get this result from cyclictest, again
> under "(while true; do hackbench 10; done) &" load:
> 
> T: 0 (  867) P:80 I:   10000 C:  105002 Min:      31 Act:      48 Avg:      51 Max:      92

Unfortunately, it doesn't really help on my Icecube board.

bash-3.00# ./cyclictest -n -p80 -i1000
129.85 93.18 38.05 4/45 6354
130.41 162.23 83.05 3/49 8395
T: 0 ( 4621) P:80 I:1000 C: 477097 Min:     25 Act:   64 Avg:   67 Max:
    286

bash-3.00# ./hackbench 10
Time: 95.402

Could you run your cyclictest much longer?

And hackbench takes ages, already without running cyclictest:

  bash-3.00# time ./hackbench 10
  Time: 83.157
  real    1m23.935s
  user    0m5.692s
  sys     1m18.240s

With a standard non-rt kernel it just takes 10 seconds.

  bash-3.00# time ./hackbench 10
  Time: 9.690
  real    0m10.343s
  user    0m0.404s
  sys     0m9.928s

Is this the normal/expected behavior under -rt?

Wolfgang.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-10 13:17         ` Wolfgang Grandegger
@ 2008-01-10 14:35           ` Robert Schwebel
  2008-01-10 16:23             ` Robert Schwebel
  2008-01-10 15:48           ` Juergen Beisert
  1 sibling, 1 reply; 17+ messages in thread
From: Robert Schwebel @ 2008-01-10 14:35 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: Thomas Gleixner, linux-rt-users, John Stultz

On Thu, Jan 10, 2008 at 02:17:02PM +0100, Wolfgang Grandegger wrote:
> Unfortunately, it doesn't really help on my Icecube board.
> 
> bash-3.00# ./cyclictest -n -p80 -i1000
> 129.85 93.18 38.05 4/45 6354
> 130.41 162.23 83.05 3/49 8395
> T: 0 ( 4621) P:80 I:1000 C: 477097 Min:     25 Act:   64 Avg:   67 Max:
>     286
> 
> bash-3.00# ./hackbench 10
> Time: 95.402
> 
> Could you run your cyclictest much longer?

I'll re-test with your parameters.

> And hackbench takes ages, already without running cyclictest:
> 
>   bash-3.00# time ./hackbench 10
>   Time: 83.157
>   real    1m23.935s
>   user    0m5.692s
>   sys     1m18.240s
> 
> With a standard non-rt kernel it just takes 10 seconds.
> 
>   bash-3.00# time ./hackbench 10
>   Time: 9.690
>   real    0m10.343s
>   user    0m0.404s
>   sys     0m9.928s
> 
> Is this the normal/expected behavior under -rt?

I've no idea where it comes from.

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-10 13:17         ` Wolfgang Grandegger
  2008-01-10 14:35           ` Robert Schwebel
@ 2008-01-10 15:48           ` Juergen Beisert
  2008-01-11  9:22             ` Wolfgang Grandegger
  1 sibling, 1 reply; 17+ messages in thread
From: Juergen Beisert @ 2008-01-10 15:48 UTC (permalink / raw)
  To: linux-rt-users
  Cc: Wolfgang Grandegger, Robert Schwebel, Thomas Gleixner,
	John Stultz

On Thursday 10 January 2008 14:17, Wolfgang Grandegger wrote:
> Hi Robert,
>
> Robert Schwebel wrote:
> > Wolfgang,
> >
> > On Wed, Jan 09, 2008 at 11:51:07PM +0100, Robert Schwebel wrote:
> >> Throwing in the versions from 2.6.23.3-rt5 doesn't help, the effect
> >> stays the same. So I assume it is a side effect.
> >
> > Can you test the following patch by John Stulz (thanks to John for the
> > quick help on irc!), which fixes the issues on my board:
> >
> > ----------8<----------
> > Index: linux-2.6.24-rc5/arch/powerpc/kernel/time.c
> > ===================================================================
> > --- linux-2.6.24-rc5.orig/arch/powerpc/kernel/time.c
> > +++ linux-2.6.24-rc5/arch/powerpc/kernel/time.c
> > @@ -773,7 +773,7 @@ void update_vsyscall(struct timespec *wa
> >  	stamp_xsec = (u64) xtime.tv_nsec * XSEC_PER_SEC;
> >  	do_div(stamp_xsec, 1000000000);
> >  	stamp_xsec += (u64) xtime.tv_sec * XSEC_PER_SEC;
> > -	update_gtod(clock->cycle_last, stamp_xsec, t2x);
> > +	update_gtod(clock->cycle_last-clock->cycle_accumulated, stamp_xsec,
> > t2x); }
> >
> >  void update_vsyscall_tz(void)
> > ----------8<----------
> >
> > With this patch ontop of 2.6.24-rc5-rt1 plus the board support patches
> > for the phyCORE-MPC5200B-tiny, I get this result from cyclictest, again
> > under "(while true; do hackbench 10; done) &" load:
> >
> > T: 0 (  867) P:80 I:   10000 C:  105002 Min:      31 Act:      48 Avg:   
> >   51 Max:      92
>
> Unfortunately, it doesn't really help on my Icecube board.
>
> bash-3.00# ./cyclictest -n -p80 -i1000
> 129.85 93.18 38.05 4/45 6354
> 130.41 162.23 83.05 3/49 8395
> T: 0 ( 4621) P:80 I:1000 C: 477097 Min:     25 Act:   64 Avg:   67 Max:
>     286
>
> bash-3.00# ./hackbench 10
> Time: 95.402
>
> Could you run your cyclictest much longer?
>
> And hackbench takes ages, already without running cyclictest:

Did your read http://lkml.org/lkml/2007/12/7/181 ? Don't know if it is 
relevant here.

Juergen
-- 
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
    Handelsregister: Amtsgericht Hildesheim, HRA 2686
         Vertretung Sued/Muenchen, Germany
   Phone: +49-8766-939 228 |  Fax: +49-5121-206917-9

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-10 14:35           ` Robert Schwebel
@ 2008-01-10 16:23             ` Robert Schwebel
  2008-01-10 21:27               ` Robert Schwebel
  2008-01-10 21:49               ` Wolfgang Grandegger
  0 siblings, 2 replies; 17+ messages in thread
From: Robert Schwebel @ 2008-01-10 16:23 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: Thomas Gleixner, linux-rt-users, John Stultz

On Thu, Jan 10, 2008 at 03:35:27PM +0100, Robert Schwebel wrote:
> > Could you run your cyclictest much longer?
> 
> I'll re-test with your parameters.

Done, here are the results (data and histogram):

http://www.pengutronix.de/software/realtime-preempt/20080110-1-cyclictest/20080110-1-phyCORE-MPC5200B-tiny-data.png
http://www.pengutronix.de/software/realtime-preempt/20080110-1-cyclictest/20080110-1-phyCORE-MPC5200B-tiny-histo.png

Especially the data plot is interesting: it shows that most of the shots
are below 80 us, but there are regular peaks. If you look carefully, you
also see that the peaks are "growing", which usually means that there is
some interference.

Time to activate latency hunting...

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-10 16:23             ` Robert Schwebel
@ 2008-01-10 21:27               ` Robert Schwebel
  2008-01-10 21:49               ` Wolfgang Grandegger
  1 sibling, 0 replies; 17+ messages in thread
From: Robert Schwebel @ 2008-01-10 21:27 UTC (permalink / raw)
  To: Wolfgang Grandegger; +Cc: Thomas Gleixner, linux-rt-users, John Stultz

On Thu, Jan 10, 2008 at 05:23:51PM +0100, Robert Schwebel wrote:
> Done, here are the results (data and histogram):

Here's a better overview now:

http://www.pengutronix.de/oselas/realtime/results/20080110-1-cyclictest_en.html

The second plot series is without net, which proves my assumption that
it is some interference between network interrupt code and cyclictest.
It was taken with 'ifdown eth0', booted from flash and logging into a
ramdisk. The peaks are completely gond, with the maximum below 70 us.

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-10 16:23             ` Robert Schwebel
  2008-01-10 21:27               ` Robert Schwebel
@ 2008-01-10 21:49               ` Wolfgang Grandegger
  1 sibling, 0 replies; 17+ messages in thread
From: Wolfgang Grandegger @ 2008-01-10 21:49 UTC (permalink / raw)
  To: Robert Schwebel; +Cc: Thomas Gleixner, linux-rt-users, John Stultz

Robert Schwebel wrote:
> On Thu, Jan 10, 2008 at 03:35:27PM +0100, Robert Schwebel wrote:
>>> Could you run your cyclictest much longer?
>> I'll re-test with your parameters.
> 
> Done, here are the results (data and histogram):
> 
> http://www.pengutronix.de/software/realtime-preempt/20080110-1-cyclictest/20080110-1-phyCORE-MPC5200B-tiny-data.png
> http://www.pengutronix.de/software/realtime-preempt/20080110-1-cyclictest/20080110-1-phyCORE-MPC5200B-tiny-histo.png
> 
> Especially the data plot is interesting: it shows that most of the shots
> are below 80 us, but there are regular peaks. If you look carefully, you
> also see that the peaks are "growing", which usually means that there is
> some interference.

A latency peak every 16.6 second, hm, interesting.

> Time to activate latency hunting...

Unfortunately, the latency tracer of the -rt kernel is not available for
PowerPC.

Wolfgang.

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
  2008-01-10 15:48           ` Juergen Beisert
@ 2008-01-11  9:22             ` Wolfgang Grandegger
  0 siblings, 0 replies; 17+ messages in thread
From: Wolfgang Grandegger @ 2008-01-11  9:22 UTC (permalink / raw)
  To: Juergen Beisert
  Cc: linux-rt-users, Robert Schwebel, Thomas Gleixner, John Stultz

[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]

Hi Jürgen,

Juergen Beisert wrote:
> On Thursday 10 January 2008 14:17, Wolfgang Grandegger wrote:
>> Hi Robert,
>>
>> Robert Schwebel wrote:
>>> Wolfgang,
>>>
>>> On Wed, Jan 09, 2008 at 11:51:07PM +0100, Robert Schwebel wrote:
>>>> Throwing in the versions from 2.6.23.3-rt5 doesn't help, the effect
>>>> stays the same. So I assume it is a side effect.
>>> Can you test the following patch by John Stulz (thanks to John for the
>>> quick help on irc!), which fixes the issues on my board:
>>>
>>> ----------8<----------
>>> Index: linux-2.6.24-rc5/arch/powerpc/kernel/time.c
>>> ===================================================================
>>> --- linux-2.6.24-rc5.orig/arch/powerpc/kernel/time.c
>>> +++ linux-2.6.24-rc5/arch/powerpc/kernel/time.c
>>> @@ -773,7 +773,7 @@ void update_vsyscall(struct timespec *wa
>>>  	stamp_xsec = (u64) xtime.tv_nsec * XSEC_PER_SEC;
>>>  	do_div(stamp_xsec, 1000000000);
>>>  	stamp_xsec += (u64) xtime.tv_sec * XSEC_PER_SEC;
>>> -	update_gtod(clock->cycle_last, stamp_xsec, t2x);
>>> +	update_gtod(clock->cycle_last-clock->cycle_accumulated, stamp_xsec,
>>> t2x); }
>>>
>>>  void update_vsyscall_tz(void)
>>> ----------8<----------
>>>
>>> With this patch ontop of 2.6.24-rc5-rt1 plus the board support patches
>>> for the phyCORE-MPC5200B-tiny, I get this result from cyclictest, again
>>> under "(while true; do hackbench 10; done) &" load:
>>>
>>> T: 0 (  867) P:80 I:   10000 C:  105002 Min:      31 Act:      48 Avg:   
>>>   51 Max:      92
>> Unfortunately, it doesn't really help on my Icecube board.
>>
>> bash-3.00# ./cyclictest -n -p80 -i1000
>> 129.85 93.18 38.05 4/45 6354
>> 130.41 162.23 83.05 3/49 8395
>> T: 0 ( 4621) P:80 I:1000 C: 477097 Min:     25 Act:   64 Avg:   67 Max:
>>     286
>>
>> bash-3.00# ./hackbench 10
>> Time: 95.402
>>
>> Could you run your cyclictest much longer?
>>
>> And hackbench takes ages, already without running cyclictest:
> 
> Did your read http://lkml.org/lkml/2007/12/7/181 ? Don't know if it is 
> relevant here.

Seems somehow related but my -rt kernel already selects SLAB:

  $ cat init/Kconfig
  ...
  config SLUB
        bool "SLUB (Unqueued Allocator)"
        depends on !PREEMPT_RT

With SLUB re-enabled I get the attached interesting oops.

Wolfgang.


[-- Attachment #2: oops.log --]
[-- Type: text/x-log, Size: 958 bytes --]

[    5.287422] BUG: sleeping function called from invalid context IRQ-192(735) at kernel/rtmutex.c:638
[    5.296678] in_atomic():0 [00000000], irqs_disabled():1
[    5.302009] Call Trace:
[    5.304501] [c39e1e50] [c000919c] show_stack+0x50/0x190 (unreliable)
[    5.311024] [c39e1e80] [c001b3c4] __might_sleep+0xec/0x110
[    5.316652] [c39e1e90] [c0207ad8] __lock_text_start+0x88/0xa0
[    5.322531] [c39e1ea0] [c007c2a8] __slab_alloc+0x3cc/0x644
[    5.328141] [c39e1ed0] [c007cf70] __kmalloc_track_caller+0xdc/0xe4
[    5.334461] [c39e1ef0] [c01803e4] __alloc_skb+0x60/0x120
[    5.339910] [c39e1f10] [c01561c8] mpc52xx_fec_rx_interrupt+0x180/0x308
[    5.346587] [c39e1f40] [c0051620] handle_IRQ_event+0x6c/0x110
[    5.352471] [c39e1f70] [c0051fac] thread_simple_irq+0x88/0x114
[    5.358434] [c39e1f90] [c0052364] do_irqd+0x32c/0x3ac
[    5.363597] [c39e1fd0] [c003ad28] kthread+0x84/0x8c
[    5.368590] [c39e1ff0] [c0010b90] kernel_thread+0x44/0x60

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2008-01-11  9:22 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-08 10:13 High latencies on MPC5200 with patch-2.6.24-rc5-rt1 Wolfgang Grandegger
2008-01-08 15:49 ` Robert Schwebel
2008-01-08 16:41   ` Wolfgang Grandegger
2008-01-08 20:40     ` Robert Schwebel
2008-01-08 21:25     ` Juergen Beisert
2008-01-09  9:03   ` Robert Schwebel
2008-01-09  9:50     ` Wolfgang Grandegger
2008-01-09 14:08       ` Robert Schwebel
2008-01-09 22:51     ` Robert Schwebel
2008-01-10  0:01       ` Robert Schwebel
2008-01-10 13:17         ` Wolfgang Grandegger
2008-01-10 14:35           ` Robert Schwebel
2008-01-10 16:23             ` Robert Schwebel
2008-01-10 21:27               ` Robert Schwebel
2008-01-10 21:49               ` Wolfgang Grandegger
2008-01-10 15:48           ` Juergen Beisert
2008-01-11  9:22             ` Wolfgang Grandegger

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.