Linux 2.6.16-rc3
Subsystems (3)
Ok,
it is out there (or in the process of getting mirrored out), so go wild.
And remember - if you get the tar-balls, you can get the patch file as a bonus FOR THE SAME PRICE! Have we got an unbeatable deal for you or what?
Of course, if you get the git repo, you'll get both anyway. And a nifty full log, since I'm just appending the short version here as a teaser.
Most of it is your run-of-the-mill fixes, with some driver updates making it all a bit larger (DVB in particular, but there's a few odd ones elsewhere too).
The most user-visible one (eventually) is the unshare() system call, which glibc wanted. Along with some fixes for fstatat() (use the proper 64-bit interfaces, not the "newer old" one).
MIPS updates to round it up, although other architectures got their regularly scheduled updates too (powerpc, arm, ia64, s390..)
The shortlog gives more details.
Linus
----
Adrian Bunk:
VIDEO_CX88_ALSA must select SND_PCM
V4L/DVB (3428): drivers/media/dvb/ possible cleanups kernel/kprobes.c: fix a warning #ifndef ARCH_SUPPORTS_KRETPROBES don't allow users to set CONFIG_BROKEN=y drivers/serial/jsm/: cleanups
drivers/ide/ide-io.c: make __ide_end_request() static
IDE: always enable CONFIG_PDC202XX_FORCE
OCFS2: __init / __exit problem fs/ocfs2/dlm/dlmrecovery.c must #include <linux/delay.h> Let CDROM_PKTCDVD_WCACHE depend on EXPERIMENTAL
i386: HIGHMEM64G must depend on X86_CMPXCHG64 drivers/base/: proper prototypes
V4L/DVB (3318e): DVB: remove the at76c651/tda80xx frontends drivers/video/Kconfig: remove unused BUS_I2C option
Akinobu Mita:
fix generic_fls64()
Al Viro:
cris: asm-offsets related build failure
remove bogus asm/bug.h includes.
bogus asm/delay.h includes
drive_info removal outside of arch/i386
missing includes in drivers/net/mv643xx_eth.c
fix breakage in ocp.c
restore power-off on sparc32
ppc: last_task_.... is defined only on non-SMP drivers/scsi/mac53c94.c __iomem annotations fallout from ptrace consolidation patch: cris/arch-v10 missing include in ser_a2232
fix __user annotations in fs/select.c
ipv4 NULL noise removal
timer.c NULL noise removal
kernel/sys.c NULL noise removal
dvb NULL noise removal drivers/char/watchdog/sbc_epx_c3.c __user annotations fix __user annotations in drivers/base/memory.c drivers/edac/i82875p_edac.c __user annotations cmm NULL noise removal, __user annotations scsi_transport_iscsi gfp_t annotations
sg gfp_t annotations
eeh_driver NULL noise removal
bogus extern in low_i2c.c
amd64 time.c __iomem annotations
__user annotations of video_spu_palette net/ipv6/mcast.c NULL noise removal arch/x86_64/pci/mmconfig.c NULL noise removal nfsroot port= parameter fix [backport of 2.4 fix] umount_tree() decrements mount count on wrong dentry
arm: fix dependencies for MTD_XIP
mips: namespace pollution - mem_... -> __mem_... in io.h s390x compat __user annotations
powermac pci iomem annotations drivers/media/video __user annotations and fixes powerpc signal __user annotations
sn3 iomem annotations and fixes
compat_ioctl __user annotations
s390 misc __user annotations
fix iomem annotations in dart_iommu
__user annotations in powerpc thread_info synclink_gt is PCI-only
s390 __get_user() bogus warnings removal type-safe min() in prism54
mark HISAX_AMD7930 as broken
m32r_sio iomem annotations
sh: lvalues abuse in arch/sh/boards/renesas/rts7751r2d/io.c
Alan Cox:
SBC EPX does not check/claim I/O ports it uses (2nd Edition) rio cleanups
Fix some ucLinux breakage from the tty updates
ide: set latency when resetting it821x out of firmware mode
Alexey Dobriyan:
dscc4: fix dscc4_init_dummy_skb check include/asm-*/bitops.h: fix more "~0UL >> size" typos
ixj: fix writing silence check
ipmi: mem_{in,out}[bwl] => intf_mem_{in,out}[bwl]
dscc4: fix dscc4_init_dummy_skb check
Alexey Kuznetsov:
[NETLINK]: Fix a severe bug
[NETLINK]: illegal use of pid in rtnetlink
Ananth N Mavinakayanahalli:
Kprobes: Fix deadlock in function-return probes
Andi Kleen:
x86_64: Update defconfig
x86_64: Disallow kprobes on NMI handlers
x86_64: Define pmtmr_ioport to 0 when PM_TIMER is not available
x86_64: Allow to run main time keeping from the local APIC interrupt
x86_64: Automatically enable apicmaintimer on ATI boards
x86_64: Fix swiotlb dma_alloc_coherent fallback
x86_64: Undo the earlier changes to remove unrolled copy/memset functions
x86_64: Remove CONFIG_INIT_DEBUG
x86_64: Remove rogue default y in EDAC Kconfig
x86_64: Clear more state when ignoring empty node in SRAT parsing
x86_64: Do more checking in the SRAT header code
x86_64: Fix zero mcfg entry workaround on x86-64
x86_64: Don't allow kprobes on __switch_to
x86_64: Calibrate APIC timer using PM timer
i386/x86-64: Don't ack the APIC for bad interrupts when the APIC is not enabled
x86_64: Let impossible CPUs point to reference per cpu data
Fix bad apic fix on i386
x86-64: Add sys_unshare
x86_64: GART DMA merging fix
Andreas Gruenbacher:
Fix two ext[23] uninitialized warnings
Fix building external modules on ppc32
Andreas Mohr:
ide Kconfig fixes
Andreas Schwab:
ufs: fix char vs. __s8 clash in ufs
Andrew Morton:
sx.c warning fixes
parport_serial: printk warning fix
quota_v2: printk warning fixes
sx.c printk warning fixes
uninline __sigqueue_free()
ip2main.c warning fixes reiserfs_get_acl() build fix
jbd: fix transaction batching
uli526x warning fix
module: strlen_user() race fix
x86: don't initialise cpu_possible_map to all ones
select: fix returned timeval
tipar fixes
fbdev: video_setup() warning fix
Andrey Panin:
[SERIAL] SIIG 8-port serial boards support
Andy Gospodarek:
r8169: fix forced-mode link settings
Antonino A. Daplas:
nvidiafb: Add support for Geforce4 MX 4000
Arjan van de Ven:
ocfs2: Semaphore to mutex conversion.
Arnaud Giersch:
parport: add parallel port support for SGI O2
parport: fix documentation
parport: remove dead address in MAINTAINERS
Ashok Raj:
x86_64: data/functions wrongly marked as __init with cpu hotplug.
x86_64: Dont record local apic ids when they are disabled in MADT
Atsushi Nemoto:
[SERIAL] initialize spinlock for port failed to setup console
[MIPS] Sparse: Fix some compiler/sparse warnings in ptrace32.c [MIPS] Build blast_cache routines from template
[MIPS] Sparse: Add _MIPS_SZINT and _MIPS_ISA to CHECKFLAGS to fix sparse warnings. [MIPS] Remove wrong __user tags.
[MIPS] ieee754[sd]p_neg workaround
[MIPS] Sparse: Add some __user tags to signal functions.
[MIPS] Fix minor sparse warnings
[MIPS] Fix dump_tlb.c warning and cleanup.
[MIPS] TX49 MFC0 bug workaround
[MIPS] Sparse: Add __user tags to syscall.c
[MIPS] Add 'const' to readb and friends
Becky Bruce:
documentation/powerpc: add bus-frequency property to SOC node
powerpc: Add FSL USB node to documentation
Ben Dooks:
[ARM] 3303/1: S3C24XX - add clock enable usage counting
[ARM] 3306/1: S3C24XX - update defconfig
[ARM] 3299/1: S3C24XX - fix irq range on adc device
[ARM] 3326/1: H1940 - Control latchesBenjamin Herrenschmidt:
Fix uevent buffer overflow in input layer
powerpc: Fix sound driver use of i2c
powerpc: Thermal control for dual core G5s
Bjorn Helgaas:
[IA64] avoid broken SAL_CACHE_FLUSH implementations
ia64: drop arch-specific IDE MAX_HWIFS definition
Carsten Otte:
ext2: print xip mount option in ext2_show_options
Catalin Marinas:
[ARM] 3290/1: Fix the FIFO size detection [ARM] 3313/1: Use OSC4 instead of OSC1 for CLCD
Chen, Kenneth W:
[IA64] remove staled comments in asm/system.h
x86_64: Fix memory policy build without CONFIG_HUGETLBFS [IA64] add syscall entry for *at()
Chris McDermott:
x86-64: Fix HPET timer on x460
Chris Pascoe:
V4L/DVB (3308): Use parallel transport for FusionHDTV Dual Digital USB
Christoph Lameter:
hugetlb: add comment explaining reasons for Bus Errors
hugetlbpage: return VM_FAULT_OOM on oom
Updates for page migration
zone reclaim: do not check references to a page during zone reclaim
vmscan: remove duplicate increment of reclaim_in_progress
vmscan: skip reclaim_mapped determination if we do not swap
Chuck Ebbert:
sched: only print migration_cost once per boot i386 cpu hotplug: don't access freed memory
i386: print kernel version in register dumps
kobject: don't oops on null kobject.name
Cornelia Huck:
s390: fix to_channelpath macro
s390: fix locking in __chp_add() and s390_subchannel_remove_chpid()
Daniel Jacobowitz:
[MIPS] Support /proc/kcore for MIPS
Dave C Boutcher:
powerpc: return correct rtas status from ibm,suspend-me
powerpc: prod all processors after ibm,suspend-me
powerpc: remove useless call to touch_softlockup_watchdog
Dave Jones:
Fix build failure in recent pm_prepare_* changes. EDAC config cleanup
missing license tag in intermodule
V4L/DVB (3318c): fix saa7146 kobject register failure More informative message on umount failure Fix s390 build failure.
Davi Arnaut:
Fix keyctl usage of strnlen_user()
David Binderman:
[IRDA]: out of range array access
David Brownell:
SPI: spi_butterfly, restore lost deltas
David Chinner:
[XFS] Account for the page we just wrote when we detect congestion during
David Gibson:
powerpc: Cleanup, consolidating icache dirtying logic Hugepages need clear_user_highpage() not clear_highpage()
David S. Miller:
[TG3]: Update driver version and release date. [SPARC64]: Add .gitignore file for sparc64 boot images. [SPARC64]: Update defconfig.
[SPARC]: Wire up sys_unshare().
[SPARC64]: Update defconfig.
dean gaudet:
fcntl F_SETFL and read-only IS_APPEND files
Domen Puncer:
drivers/isdn/sc/ioctl.c: copy_from_user() size fix
Eric Dumazet:
percpu data: only iterate over possible CPUs
Eric Paris:
s390: remove one set of brackets in __constant_test_bit()
Eric Sesterhenn:
i2c: Use module_param in i2c-algo-sibyte
Eric Sesterhenn / snakebyte:
BUG_ON() Conversion in fs/ocfs2/
BUG_ON() Conversion in fs/configfs/
Eric W. Biederman:
edac_mc: Remove include of version.h
Evgeniy Dushistov:
ufs: fix oops with `ufs1' type
ufs: fix hang during `rm'
Felix Oxley:
fs/jffs/intrep.c: 255 is unsigned char
Fernando Luis Vazquez Cao:
Compilation of kexec/kdump broken
Francois Romieu:
r8169: prevent excessive busy-waiting
8139too: fix a TX timeout watchdog thread against NAPI softirq race
Geoff Levand:
powerpc: Fix spufs initialization sequence.
George Anzinger:
Normalize timespec for negative values in ns_to_timespec
Grant Grundler:
[PARISC] Remove unnecessary extern declarations from asm/pci.h
Greg Kroah-Hartman:
USB: Fix GPL markings on usb core functions. kobject_add() must have a valid name in order to succeed.
DRM: fix up classdev interface for drm core
IB: fix up major/minor sysfs interface for IB core
Greg Ungerer:
m68knommu: compile fixes for mcfserial.c
m68knommu: need pm_power_off in m68knommu
m68knommu: hardirq.h needs definition of NR_IRQS
m68knommu: use tty_schedule_flip() in 68360serial.c
m68knommu: use tty_schedule_flip() in 68328serial.c
Hans Verkuil:
V4L/DVB (3403): Add probe check for the tda9840.
V4L/DVB (3300): Add standard for South Korean NTSC-M using A2 audio.
Haren Myneni:
kexec: fix in free initrd when overlapped with crashkernel region
Heiko Carstens:
s390: compile fix: missing defines in asm-s390/io.h
s390: fix compat syscall wrapper
[SPARC64]: Fix sys_newfstatat syscall table entry for 64-bit. remove bogus comment from init/main.c
s390: update default configuration
s390: earlier initialization of cpu_possible_map
s390: update maintainers file
s390: fix non smp build of kexec
s390: add support for unshare system call
s390: add #ifdef __KERNEL__ to asm-s390/setup.h
s390: fstatat64 support
Helge Deller:
[PARISC] Use kzalloc and other janitor-style cleanups [PARISC] Drop unused do_check_pgt_cache()
[PARISC] Clean up compiler warning in pci.c [PARISC] Add CONFIG_DEBUG_RODATA to protect read-only data [PARISC] Use DEBUG_KERNEL to catch used-after-free __init data
Herbert Poetzl:
quota: remove unused sync_dquots_dev()
quota: fix error code for ext2_new_inode()
Herbert Xu:
[IPV6]: Don't hold extra ref count in ipv6_ifa_notify [IPV4] multipath_wrandom: Fix softirq-unsafe spin lock usage [IPV6]: Fix illegal dst locking in softirq context. [ICMP]: Fix extra dst release when ip_options_echo fails [PPP]: Fixed hardware RX checksum handling
Hidetoshi Seto:
[IA64] mca_drv: Add minstate validation
Holger Eitzenberger:
[NETFILTER]: ULOG/nfnetlink_log: Use better default value for 'nlbufsiz'
Horms:
[IPV4]: Document icmp_errors_use_inbound_ifaddr sysctl [IPV4]: Remove suprious use of goto out: in icmp_reply
Hugh Dickins:
x86: fix stack trace facility level
Ian Campbell:
[WATCHDOG] sa1100_wdt.c sparse clean (2)
Ian Pickworth:
V4L/DVB (3416): Recognise Hauppauge card #34519
Ingo Molnar:
sem2mutex: drivers/macintosh/windfarm_core.c solve false-positive soft lockup messages during IDE init Fix spinlock debugging delays to not time out too early SLOB=y && SMP=y fix
x86: print out early faults via early_printk()
Ivan Kokshaysky:
alpha: set cpu_possible_map much earlier
J. Bruce Fields:
[OCFS2] Documentation Fix
knfsd: fix nfs4_open lock leak
Jack Steiner:
[IA64-SGI] Update TLB flushing code for SN platform
Jake Moilanen:
powerpc: IOMMU SG paranoia
James Bottomley:
[PARISC] Fix floating point invalid exception trap handler
Jan Beulich:
x86_64: small fix for CFI annotations
x86_64: minor odering correction to dump_pagetable() prevent recursive panic from softlockup watchdog
Jan Glauber:
s390: timer interface visibility
JANAK DESAI:
unshare system call -v5: Documentation file unshare system call -v5: system call handler function unshare system call -v5: unshare filesystem info unshare system call -v5: unshare namespace unshare system call -v5: unshare vm
unshare system call -v5: unshare files
unshare system call -v5: system call registration for i386
powerpc: unshare system call registration
Janak Desai:
[IA64] unshare system call registration for ia64
Jason Gaston:
piix: add Intel ICH8M device IDs
i2c-i801: I2C patch for Intel ICH8
Jay Vosburgh:
bonding: allow bond to use TSO if slaves support it
Jayachandran C:
UDF: Fix issues reported by Coverity in namei.c
IPMI: fix issues reported by Coverity in ipmi_msghandler.c
Jean Delvare:
ide-disk: Restore missing space in log message
I2C: Resurrect i2c_smbus_write_i2c_block_data.
hwmon: Fix negative temperature readings in lm77 driver
hwmon: Inline w83792d register access functions
hwmon: Add f71805f documentation
hwmon: New f71805f driver
hwmon: Fix reboot on it87 driver load
Jeff Dike:
uml: add debug switch for skas mode
uml: close TUN/TAP file descriptors
uml: balance list_add and list_del in the network driver
uml: block SIGWINCH in ptrace tester child
uml: initialize process FP registers properly
uml: remove a dead file
Jeff Garzik:
[libata sata_sil] implement 'slow_down' module parameter [libata sata_mv] do not enable PCI MSI by default
Jeff Mahoney:
ocfs2/dlm: fix compilation on ia64
reiserfs: disable automatic enabling of reiserfs inode attributes
Jeff Moyer:
fix O_DIRECT read of last block in a sparse file
Jens Axboe:
fix ordering on requeued request drainage
cciss: softirq handler needs to save interrupt flags
blk: Fix SG_IO ioctl failure retry looping
Jes Sorensen:
drivers/sn/ must be entered for CONFIG_SGI_IOC3 [IA64-SGI] sn2 housekeeping
[IA64-SGI] include/asm-ia64/sn/intr.h more sn2 housekeeping [IA64] prevent sn2 specific code to be run in generic kernels
Jesper Juhl:
Don't check pointer for NULL before passing it to kfree [arch/powerpc/kernel/rtas_flash.c] wrong firmware location in IPW2100 Kconfig entry
netfilter: fix build error due to missing has_bridge_parent macro
Jesse Allen:
orinoco: support smc2532w
Jesse Brandeburg:
e100: remove init_hw call to fix panic
Jiri Slaby:
V4L/DVB (3439a): media video stradis memory fix
Joel Becker:
o Remove confusing Kconfig text for CONFIGFS_FS.
configfs: Clean up MAINTAINERS entry
configfs: Add permission and ownership to configfs objects.
John Blackwood:
arch/x86_64/kernel/traps.c PTRACE_SINGLESTEP oops
John Heffner:
[TCP]: rcvbuf lock when tcp_moderate_rcvbuf enabled
Jon Mason:
x86_64: IOMMU printk cleanup
Jordan Crouse:
[SERIAL] Fix compile error in 8250_au1x00.c [MMC] Remove extra character in AU1XXX MMC Kconfig entry
KAMBAROV, ZAUR:
coverity: udf/balloc.c null deref fix
KAMEZAWA Hiroyuki:
shmdt cannot detach not-alined shm segment cleanly.
Karsten Keil:
i4l: warning fixes
Keith Owens:
[IA64-SGI] Recursive flags do not work for selective builds Tell kallsyms_lookup_name() to ignore type U entries
Kevin VanMaren:
x86_64: When allocation of merged SG lists fails in the IOMMU don't merge
Kirill Korotaev:
[NETFILTER]: Fix possible overflow in netfilters do_replace()
Kristian Slavov:
[IPV6]: Address autoconfiguration does not work after device down/up cycle
Kumar Gala:
gianfar: Fix sparse warnings
[SERIAL] 8250 serial console update uart_8250_port ier
powerpc: Add CONFIG_DEFAULT_UIMAGE for embedded boards
Kurt Hackel:
ocfs2/dlm: fixes
Kyle McMartin:
[PARISC] Use F_EXTEND() for COMMAND_GLOBAL
[PARISC] atomic64 support
[PARISC] Move pm_power_off export to process.c
[PARISC] Remove obsolete _hlt cruft
[PARISC] Add chassis_power_off routine
[PARISC] Clean up printk in superio.c
[PARISC] Arch-specific compat signals
[PARISC] Simplify DISCONTIGMEM in Kconfig
[PARISC] New syscalls (inotify, *at, pselect6/ppoll, migrate_pages) [IA64] Remove stale comment from ia64/Kconfig
sys_hpux: fix strlen_user() race
Latchesar Ionkov:
v9fs: symlink support fixes
v9fs: v9fs_put_str fix
v9fs: fix corner cases when flushing request
Lennert Buytenhek:
sis900: remove cfgpmcsr I/O space register define
[ARM] 3300/1: make ixdp2x01 co-exist with other ixp2000 machine types [ARM] 3301/1: remove unnecessary clock default from ixdp2801 defconfig [ARM] 3302/1: make pci=firmware the default for ixp2000
Linas Vepstas:
Clean up Documentation/driver-model/overview.txt
Documentation: Updated PCI Error Recovery
Linus Torvalds:
Revert "x86_64: Fix the node cpumask of a cpu going down" mm/slab.c (non-NUMA): Fix compile warning and clean up code
ppc: fix up trivial Kconfig config selection
Revert "kconfig: detect if -lintl is needed when linking conf,mconf" Linux v2.6.16-rc3
Loren M. Lang:
RocketPoint 1520 [hpt366] fails clock stabilization
Lucas Correia Villa Real:
[ARM] 3284/1: S3C2400 - adds support to GPIO
[ARM] 3286/2: S3C2400 - adds to the table of supported CPUs
[ARM] 3283/1: S3C2400 - defines the number of serial ports
[ARM] 3314/1: S3C2400 - adds s3c2400.hLuiz Fernando Capitulino:
bonding: Sparse warnings fix
Manu Abraham:
V4L/DVB (3294): Fix [Bug 5895] to correct snd_87x autodetect
Marcelo Tosatti:
make "struct d_cookie" depend on CONFIG_PROFILING powerpc/8xx: last two 8MB D-TLB entries are incorrectly set
Marcin Rudowski:
V4L/DVB (3266): Fix NICAM buzz on analog sound
Marco Manenti:
V4L/DVB (3297): Add IR support to KWorld DVB-T (cx22702-based)
Marcus Sundberg:
[NETFILTER]: ctnetlink: Fix subsystem used for expectation events
Mark Fasheh:
[OCFS2] Make ip_io_sem a mutex
ocfs2: fix compile warnings
ocfs2: don't wait on recovery when locking journal
Mark Mason:
[MIPS] BCM1125 PCI fixes
[MIPS] BCM1480: Cleanup debug code left behind in the PCI driver. [MIPS] SB1: Add oprofile support.
Mark Maule:
[IA64-SGI] fix smp_affinity redirection when using CONFIG_PCI_MSI [IA64-SGI] disable msi for all altix pci devices
Markus Lidel:
I2O: don't disable PCI device if it is enabled before probing
I2O: fix and workaround for Motorola/Freescale controller Fix i2o_scsi oops on abort
Markus Rechberger:
V4L/DVB (3429): Missing break statement on tuner-core V4L/DVB (3434): changed comment in tuner-core.c
V4L/DVB (3281): Added signal detection support to tvp5150 V4L/DVB (3306): Fixed i2c return value, conversion mdelay to msleep V4L/DVB (3325): Disabled debug on by default in tvp5150
Martin Michlmayr:
Fix compilation errors in maps/dc21285.c
[ARM] 3304/1: Add help descriptions to ARCH config items that don't have one [ARM] 3305/1: Minor typographical and spelling fixes in Konfig
Matt Waddel:
Add wording to m68k .S files to help clarify license info
Matthew Wilcox:
[PARISC] Make flush_tlb_all_local take a void * [PARISC] Update b180_defconfig
[PARISC] Remove {,un}lock_kernel from perf ioctl
Mauro Carvalho Chehab:
V4L/DVB (3406): Added credits for em28xx-video.c
V4L/DVB (3405): Fixes tvp5150a/am1 detection.
V4L/DVB (3453a): Alters MAINTAINERS file to point to newer v4l-dvb email V4L/DVB (3318a): Makes Some symbols static.
Michael Chan:
[TG3]: Flush tg3_reset_task()
Michael Ellerman:
powerpc: Don't allocate zero bytes in finish_device_tree()
powerpc: Make sure we don't create empty lmb regions
powerpc: Refuse to boot a kdump kernel via OF
powerpc: Fix !SMP build of rtas.c
powerpc: Don't overwrite flat device tree with kdump kernel
powerpc: Don't use toc in decrementer_iSeries_masked
Michael Krufky:
V4L/DVB (3392): Add PCI ID for DigitalNow DVB-T Dual, rebranded DViCO FusionHDTV DVB-T Dual.
V4L/DVB (3413): Kill nxt2002 in favor of the nxt200x module
V4L/DVB (3414): rename dvb_pll_tbmv30111in to dvb_pll_samsung_tbmv
V4L/DVB (3417): make VP-3054 Secondary I2C Bus Support a Kconfig option.
V4L/DVB (3431): fixed spelling error, exectuted --> executed.
V4L/DVB (3442): Allow tristate build for cx88-vp3054-i2c
V4L/DVB (3299): Kconfig: DVB_USB_CXUSB depends on DVB_LGDT330X and DVB_MT352
V4L/DVB (3310): Use MT352 parallel transport function for all Bluebird FusionHDTV DVB-T boxes.Michael Neuling:
powerpc: hypervisor check in pseries_kexec_cpu_down
Michael Richardson:
ide: cast arguments to pr_debug() properly
Michal Ostrowski:
Fix RocketPort driver
Mike Isely:
V4L/DVB (3418): Cause tda9887 to use I2C_DRIVERID_TDA9887
Miklos Szeredi:
fuse: fix request_end() vs fuse_reset_request() race
Nathan Lynch:
powerpc: avoid timer interrupt replay effect when onlining cpu
Nathan Scott:
[XFS] Fix missing inode atime update from the utime syscall.
NeilBrown:
md: Handle overflow of mdu_array_info_t->size better
md: Assorted little md fixes
md: Make sure rdev->size gets set for version-1 superblocksNick Piggin:
mm: compound release fix
sched: remove smpnice
Nicolas Pitre:
[ARM] 3293/1: don't invalidate the whole I-cache with xscale_coherent_user_range [ARM] 3294/1: don't invalidate individual BTB entries on ARMv6 [ARM] 3307/1: old ABI compat: mark it experimental
[ARM] 3308/1: old ABI compat: struct sockaddr_un
[ARM] 3309/1: disable the pre-ARMv5 NPTL kernel helper in the non MMU case [ARM] 3310/1: add a comment about the possible __kuser_cmpxchg transient false [ARM] 3311/1: clean up include/asm-arm/mutex.h
OGAWA Hirofumi:
fat: Replace an own implementation with ll_rw_block(SWRITE,) Trivial optimization of ll_rw_block()
fat: Fix truncate() write ordering
Olaf Hering:
powerpc: remove pointer/integer confusion in generic_calibrate_decr
powerpc: restore clock speed in /proc/cpuinfo
powerpc: remove pointer/integer confusion in of_find_node_by_name
powerpc: add refcounting to setup_peg2 and of_get_pci_address
powerpc: fix compile warning in udbg_init_maple_realmode
Oleg Nesterov:
sys_signal: initialize ->sa_mask
do_sigaction: cleanup ->sa_mask manipulationOliver Endriss:
V4L/DVB (3307): Support for Galaxis DVB-S rev1.3
Pablo Neira Ayuso:
[TEXTSEARCH]: Fix broken good shift array calculation in Boyer-Moore [NETFILTER]: ctnetlink: add MODULE_ALIAS for expectation subsystem
Paolo 'Blaisorblade' Giarrusso:
Kbuild menu - hide empty NETDEVICES menu when NET is disabled
Patrick Boettcher:
V4L/DVB (3312): FIX: Multiple usage of VP7045-based devices V4L/DVB (3313): FIX: Check if FW was downloaded or not + new firmware file
Patrick McHardy:
[NETFILTER]: Fix undersized skb allocation in ipt_ULOG/ebt_ulog/nfnetlink_log [NETFILTER]: nfnetlink_queue: fix packet marking over netlink [NETFILTER]: Fix missing src port initialization in tftp expectation mask [NETFILTER]: Check policy length in policy match strict mode [NETFILTER]: Fix ip6t_policy address matching
[NETFILTER]: Prepare {ipt,ip6t}_policy match for x_tables unification [NETFILTER]: Fix check whether dst_entry needs to be released after NAT
Paul E. McKenney:
Fix comment to synchronize_sched()
Paul Fulghum:
new tty buffering locking fix
tty buffering stall fix
Paul Mackerras:
powerpc/64: Fix bug in setting floating-point exception mode
ppc: Use the system call table from arch/powerpc/kernel/systbl.S
Pavel Machek:
Fix Userspace interface breakage in power/state
swsusp: kill unneeded/unbalanced bio_get
Peter Horton:
[MIPS] Fix Cobalt PCI cache line sizes
Peter Missel:
V4L/DVB (3409): Mark Typhoon cards as Lifeview OEM's
Peter Oberparleiter:
s390: fix sclp memory corruption in tty pages list
Peter Osterlund:
pktcdvd: remove version string
pktcdvd: Don't waste kernel memory
Peter Williams:
lib: Fix bug in int_sqrt() for 64 bit longs
Phillip Susi:
pktcdvd: Fix overflow for discs with large packets
pktcdvd: Allow larger packets
Prarit Bhargava:
[IA64-SGI] Hotplug driver related fix in the SN ia64 code. [IA64-SGI] Small cleanup for misuse of list_for_each to list_for_each_safe.
Rafael J. Wysocki:
Fix build failure in recent pm_prepare_* changes.
Ralf Baechle:
[MIPS] Remove stray .set mips3 resulting in 64-bit instruction in 32-bit kernels. [MIPS] Fix C version of ssnop to use the right opcode.
[MIPS] Get rid of unnecessary prototypes. Fixes and optimizations for HZ > 100. [MIPS] RTLX compile fixes.
[MIPS] Revert "mips: add pm_power_off"
[MIPS] Check function pointers are non-zero before calling.
[MIPS] Rename _machine_power_off to pm_power_off so the kernel builds again. [MIPS] Rename include/asm-mips/cobalt to include/asm-mips/mach-cobalt. [MIPS] CPU definitions for Cobalt.
[MIPS] Nevada support for SGI O2.
[MIPS] Bullet proof uaccess.h against 4.0.1 miss-compilation. [MIPS] Get rid of CONFIG_SB1_PASS_1_WORKAROUNDS #ifdef crapola. [MIPS] Sibyte: Make all setup functions __init.
[MIPS] Reformat to 80 columns.
[MIPS] Remove commented out code to add -mmad for Nevada.
[MIPS] local_irq_restore wasn't safe to be used in other macros mode. [MIPS] Cleanup fls implementation.
[MIPS] IP22: Fix serial console detection
[MIPS] Shrink Qemu configuration to the bare minimum that is need and tested. [MIPS] Remove buggy inline version of memscan.
[MIPS] MIPS R2 optimized endianess swapping.
[MIPS] Oprofile: Support for 34K UP kernels.
[MIPS] Fix linker script to work for non-4K page size.
[MIPS] Clear ST0_RE on bootup.
[MIPS] Add support for TIF_RESTORE_SIGMASK.
[MIPS] Make do_signal return void.
[MIPS] Wire up new syscalls.
[SERIAL] ip22zilog: Whitespace cleanup.
Randy Dunlap:
V4L/DVB (3433): Fix printk type warning
parport: fix printk format warning
cpuset: fix sparse warning
edac: use C99 initializers (sparse warnings)
Ravikiran G Thirumalai:
x86_64: Fix the node cpumask of a cpu going down
NUMA slab locking fixes: move color_next to l3
NUMA slab locking fixes: irq disabling from cahep->spinlock to l3 lock NUMA slab locking fixes: fix cpu down and up locking
x86_64: Fix the node cpumask of a cpu going down
slab: Avoid deadlock at kmem_cache_create/kmem_cache_destroy
Richard Purdie:
[ARM] 3291/1: PXA27x: Correct get_clk_frequency_khz turbo flag handling [ARM] 3292/1: Fix memory corruption in asm-arm/checksum.h: ip_fast_csum() stop CompactFlash devices being marked as removable
Robb, Sam:
kconfig: detect if -lintl is needed when linking conf,mconf
Robert Love:
inotify: fix one-shot support
Robin Holt:
[IA64-SGI] Fix XPC code which sleeps with spin_lock_irqsave().
Rudolf Marek:
i2c: Rename i2c-sis96x documentation file
Russ Anderson:
[IA64-SGI] Shub2 BTE address fix
Russ Dill:
[ARM] 3295/1: Fix oprofile init return value
Russell King:
[MMC] Add MMC command type flags
[SERIAL] 8250: limit range of runtime ports
[ARM] Remove ARCH_CAMELOT from at91 defconfigs [SERIAL] uart_port iotype member should use UPIO_* [SERIAL] uart_port flags member should use UPF_* [SERIAL] Remove unnecessary serial.h include
Fix compiler warning in driver core for CONFIG_HOTPLUG=N drivers/base/bus.c warning fixes
[ARM] Experimental config options should have (EXPERIMENTAL) [SERIAL] Remove incorrect code from ioc4 serial driver
Sam Ravnborg:
kconfig: fix /dev/null breakage
kbuild: fix build with O=..
Samir Bellabes:
[NETFILTER]: nf_conntrack: fix incorrect memset() size in FTP helper
Samuel Ortiz:
[IRDA]: Set proper IrLAP device address length
[email protected]:
disable per cpu intr in /proc/stat
Sergei Shtylylov:
[MIPS] TX49x7: Fix timer register #define's [MIPS] Au1xx0: really set KSEG0 to uncached on reboot [MIPS] Au1200: Make KGDB compile
[MIPS] TX49x7: Fix reporting of the CPU name and PCI clock
Shaohua Li:
x86_64: timer resume
x86_64: mark two routines as __cpuinit
Stefan Weinhuber:
s390: dasd extended error reporting module
Steffen Klassert:
3c59x: collision statistic fix
Stephen Hemminger:
[NET] snap: needs hardware checksum fix
[NET]: Add CONFIG_NETDEBUG to suppress bad packet messages.
sky2: power management fix
sky2: pci config space checking
sky2: ethtool rx_coalesce settings fix
sky2: set mac address fix
sky2: clear irq race
sky2: add irq to entropy pool
sky2: support msi interrupt (revised)
sky2: version 0.15 update
[BRIDGE]: fix for RCU and deadlock on device removal [BRIDGE]: netfilter handle RCU during removal [BRIDGE]: fix error handling for add interface to bridge
Stephen Smalley:
SELinux: fix size-128 slab leak MAINTAINERS/CREDITS: Update SELinux contact info
selinux: require SECURITY_NETWORK
selinux: require AUDIT
Steve Langasek:
__cmpxchg() must really always be inlined on alpha
Suzuki:
Fix do_path_lookup() to add the check for error in link_path_walk()
Takashi Iwai:
Fix "value computed is not used" compile warnings with gcc-4.1
Tejun Heo:
block: request_queue->ordcolor must not be flipped on SOFTBARRIER
block: implement elv_insert and use it (fix ordcolor flipping bug)
Thibaut VARENE:
[PARISC] pdc_stable version 0.22
ide: restore support for AEC6280M cards in aec62xx.c
Tobias Klauser:
umem: check pci_set_dma_mask return value correctly
i2c: Use ARRAY_SIZE macro
Tong Li:
OProfile: fixed x86_64 incorrect kernel call graphs
Tony Lindgren:
[ARM] 3279/1: OMAP: 1/3 Fix low-level io init
[ARM] 3280/1: OMAP: 2/3 Fix low-level io init for omap1 boards [ARM] 3278/1: OMAP: 3/3 Fix low-level io init for omap2 boards
Tony Luck:
[IA64] Fix CONFIG_PRINTK_TIME
[IA64] sys32_signal() forgets to initialize ->sa_mask
Trond Myklebust:
VFS: Ensure LOOKUP_CONTINUE flag is preserved by link_path_walk()
Ulrich Drepper:
namei.c: unlock missing in error case
fstatat64 support
V. Ananda Krishnan:
jsm: update for tty buffering revamp
Venkatesh Pallipadi:
x86_64: Only switch to IPI broadcast timer on Intel when C3 is supported
Vincent Hanquez:
debugfs: hard link count wrong
debugfs: trivial comment fix
Vitaly Bordug:
[SERIAL] PPC32 CPM_UART: update to utilize the new TTY flip API
Vitaly Fertman:
someone broke reiserfs V3 mount options, this fixes it
Vlad Yasevich:
[SCTP]: Fix 'fast retransmit' to send a TSN only once.
Wim Van Sebroeck:
[WATCHDOG] pcwd.c add comments + tabs
[WATCHDOG] pcwd.c card_found-- fix.
[WATCHDOG] pcwd.c private data struct patch
[WATCHDOG] pcwd.c Control Status #2 patch
[WATCHDOG] pcwd.c move get_support to pcwd_check_temperature_support [WATCHDOG] pcwd.c show card info patch
[WATCHDOG] pcwd.c - update module version info
Yasuyuki Kozakai:
[NETFILTER]: nf_conntrack: check address family when finding protocol module [NETFILTER]: iptables: fix typos in ipt_connbytes.h
Yoichi Yuasa:
[SERIAL] 8250_pci: add new PCI serial card support
Zach Brown:
list.h: don't evaluate macro args multiple times
x86_64: align per-cpu section to configured cache bytes
Zhang, Yanmin:
Export cpu topology in sysfs
Zou Nan hai:
[IA64] Fix a possible buffer overflow in efi.c [IA64] Fix wrong use of memparse in efi.c
We still have some serious bugs, several of which are in 2.6.15 as well:
- The scsi_cmd leak, which I don't think is fixed.
- The some-x86_64-boxes-use-GFP_DMA-from-bio-layer bug, which causes oom-killings.
- The skbuff_head_cache leak, which has been around since at least 2.6.11. Another box-killer, but is seems very hard to hit. ([email protected], "the dreaded oom-killer (reproducable in 2.6.11 - 2.6.16-rc1) :(")
- http://bugzilla.kernel.org/show_bug.cgi?id=6060: an apparent ACPI regression.
- Nathan's "sysfs-related oops during module unload", which Greg seems to have under control.
- http://bugzilla.kernel.org/show_bug.cgi?id=6049 - another acpi regression. We have the actual offending commit here.
- A couple of random tty-related oopses reported by Jesper Juhl. We don't know why these happened - they appear to not be related to the tty buffering changes.
- http://bugzilla.kernel.org/show_bug.cgi?id=6038, another box-killing acpi regression.
- Various reports similar to
http://bugzilla.kernel.org/show_bug.cgi?id=6011, seemingly related to USB PCI quirk handling.
- "Ben Castricum" <[email protected]> reports that ppp has started exhibiting mysterious failures (again).
- Nasty warnings from scsi about kobject-layer things being called from irq context. James has a push-it-to-process-context patch which sadly assumes kmalloc() is immortal, but no other fix seems to have offered itself.
- In http://bugzilla.kernel.org/show_bug.cgi?id=5989, Sanjoy Mahajan has another regression, but he's off collecting more info.
- Helge Hafting reports a usb printer regression - I don't know if that's still live?
- "Carlo E. Prelz" <[email protected]> has another USB/ehci regression ("ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1").
- Gerrit Bruchhuser <[email protected]> seems to have an aic7xxx regression ("AHA-7850 doesn't detect scanner anymore") but he doesn't say which kernel got it right.
- http://bugzilla.kernel.org/show_bug.cgi?id=5914 - a sata bug (which is quite unremarkable :(), but this one is reported to eat filesystems.
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
- Bjorn Nilsson <[email protected]> has an sk99lin regression ("3COM 3C940, does not work anymore after upgrade to 2.6.15")
- Andrey Borzenkov <[email protected]> has an acpi-cpufreq regression ("cannot unload acpi-cpufreq")
- "P. Christeas" <[email protected]> had an autofs regression ("Regression in Autofs, 2.6.15-git"), whic might be fixed now?
- ghrt <[email protected]> reports an alsa regression ("PROBLEM: SB Live! 5.1 (emu10k1, rev. 0a) doesn't work with 2.6.15")
- jinhong hu <[email protected]> reports what appears to be a qlogic regression ("kernel 2.6.15 scsi problem")
- Benjamin LaHaise <[email protected]> had an NFS problem ("NFS processes gettting stuck in D with currrent git").
These are clear regressions, reported in the last month by people who are willing to test patches. They're almost all in subsystems which have active and professional maintainers.
Quoted 4 lines · Andrew Morton
We still have some serious bugs, several of which are in 2.6.15 as well:
- Benjamin LaHaise <[email protected]> had an NFS problem ("NFS processes gettting stuck in D with currrent git").
...but which was apparently not repeatable:
As of this afternoon's tree (6150c32589d1976ca8a5c987df951088c05a7542) after the more recent set of nfs patches, it seems to be behaving itself. Will keep sysrq enabled to see if it hits again, though.
I've had no news from Ben since then...
Cheers,
Trond
Quoted 11 lines · Trond Myklebust
Quoted 2 lines
- Benjamin LaHaise <[email protected]> had an NFS problem ("NFS processes gettting stuck in D with currrent git").
...but which was apparently not repeatable:
As of this afternoon's tree (
6150c32589d1976ca8a5c987df951088c05a7542) after the more recent set of nfs patches, it seems to be behaving itself. Will keep sysrq enabled to see if it hits again, though.I've had no news from Ben since then...
Confirmed: I've had no problems with NFS since that update, and my test box uses NFS regularly.
-ben
Signature · 2 lines
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here and they've asked us to stop the party." Don't Email: <[email protected]>.
Quoted 2 lines
In http://bugzilla.kernel.org/show_bug.cgi?id=5989, Sanjoy Mahajan has another regression, but he's off collecting more info.
I'm nearly done with bisecting (spent a day on a wild bisect goose chase due to being careless) and I'm 95% sure the problem is introduced by:
commit b8e4d89357fc434618a59c1047cac72641191805
Author: Bob Moore <[email protected]> Date: Fri Jan 27 16:43:00 2006 -0500
[ACPI] ACPICA 20060127
But I will know for sure shortly.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
Quoted 2 lines · Andrew Morton
- http://bugzilla.kernel.org/show_bug.cgi?id=5914 - a sata bug (which is quite unremarkable :(), but this one is reported to eat filesystems.
Issue closed, as the bug notes...
Jeff
Quoted 1 line · Andrew Morton
- The
scsi_cmdleak, which I don't think is fixed.
Erm, you mean the leak caused by flush barriers? That was verified as fixed (albeit accidentally) in 2.6.16-rc1.
James
S3 sleep regression bisected (was Re: Linux 2.6.16-rc3)
In reply to Andrew MortonQuoted 2 lines
In http://bugzilla.kernel.org/show_bug.cgi?id=5989, Sanjoy Mahajan has another regression, but he's off collecting more info.
Now collected. The problematic commit is:
bad: [292dd876ee765c478b27c93cc51e93a558ed58bf] Pull release into acpica branch
The longer story follows (and I'll file it with the bugzilla). The bug is that S3 sleep hangs on the second sleep of my TP 600X, producing an endless loop in the dmesgs (across a serial console):
exregion-0182 [30] ex_system_memory_space: system_memory 0 (32 width) Address=0000000023FDFFC0 exregion-0182 [30] ex_system_memory_space: system_memory 1 (32 width) Address=0000000023FDFFC0 exregion-0287 [30] ex_system_io_space_han: system_iO 1 (8 width) Address=00000000000000B2 exregion-0182 [29] ex_system_memory_space: system_memory 0 (32 width) Address=0000000023FDFFC0
'git bisect' narrowed the problematic commit to:
commit 292dd876ee765c478b27c93cc51e93a558ed58bf
Merge: d4ec6c7cc9a15a7a529719bc3b84f46812f9842e
9fdb62af92c741addbea15545f214a6e89460865
Author: Len Brown <[email protected]>
Date: Fri Jan 27 17:18:29 2006 -0500
Pull release into acpica branch
This commit had a slightly different bug from all the other ones I marked as bad. This one hung on the first S3 sleep, with the same endless loop pattern as the other bad ones (but they hang on the second S3 sleep).
Below is the 'git bisect log', which for fun you can put in some file and feed to 'git bisect replay somefile' :
$ git bisect log git-bisect start # good: [f3bcf72eb85aba88a7bd0a6116dd0b5418590dbe] Linux v2.6.16-rc1 git-bisect good f3bcf72eb85aba88a7bd0a6116dd0b5418590dbe # bad: [e4f9aae0d74cb7d2fd5f0eb315cf9de1118fe260] Linux v2.6.16-rc2 git-bisect bad e4f9aae0d74cb7d2fd5f0eb315cf9de1118fe260 # good: [a6df590dd8b7644c8e298e3b13442bcd6ceeb739] Merge branch 'for-linus' of master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband git-bisect good a6df590dd8b7644c8e298e3b13442bcd6ceeb739 # good: [e0e851cf30f1a9bd2e2a7624e9810378d6a2b072] reiserfs: reiserfs hang and performance fix for data=journal mode git-bisect good e0e851cf30f1a9bd2e2a7624e9810378d6a2b072 # bad: [59ed2f59e4ea6a32f9591e378da7935f713a7000] Merge branch 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 git-bisect bad 59ed2f59e4ea6a32f9591e378da7935f713a7000 # good: [9fdb62af92c741addbea15545f214a6e89460865] [ACPI] merge 3549 4320 4485 4588 4980 5483 5651 acpica asus fops pnpacpi branches into release git-bisect good 9fdb62af92c741addbea15545f214a6e89460865 # good: [61ee9cd5f2e76859222c1d64394ae633f9080163] PowerPC/PCI Hotplug build break git-bisect good 61ee9cd5f2e76859222c1d64394ae633f9080163 # good: [e6da74e1f20ea7822e52a9e4fbd3d25bd907e471] Merge with /pub/scm/linux/kernel/git/torvalds/linux-2.6.git git-bisect good e6da74e1f20ea7822e52a9e4fbd3d25bd907e471 # bad: [b8e4d89357fc434618a59c1047cac72641191805] [ACPI] ACPICA 20060127 git-bisect bad b8e4d89357fc434618a59c1047cac72641191805 # bad: [292dd876ee765c478b27c93cc51e93a558ed58bf] Pull release into acpica branch git-bisect bad 292dd876ee765c478b27c93cc51e93a558ed58bf # good: [d4ec6c7cc9a15a7a529719bc3b84f46812f9842e] [ACPI] remove "Resource isn't an IRQ" warning git-bisect good d4ec6c7cc9a15a7a529719bc3b84f46812f9842e
Quoted 3 lines · Andrew Morton
We still have some serious bugs, several of which are in 2.6.15 as well:
- The
scsi_cmdleak, which I don't think is fixed.
didn't this got nailed down to a 2.6.15 specific queueing bug, fixed in 2.6.16-rc ?
Quoted 4 lines · Andrew Morton
We still have some serious bugs, several of which are in 2.6.15 as well:
- The
scsi_cmdleak, which I don't think is fixed.
It is fixed in 2.6.16-rcX.
Quoted 2 lines
- The some-x86_64-boxes-use-GFP_DMA-from-bio-layer bug, which causes oom-killings.
Still pending.
Signature · 1 line
Jens Axboe
Andrew Morton ha scritto:
Quoted 75 lines
We still have some serious bugs, several of which are in 2.6.15 as well:
- The
scsi_cmdleak, which I don't think is fixed.- The some-x86_64-boxes-use-GFP_DMA-from-bio-layer bug, which causes oom-killings.
- The
skbuff_head_cacheleak, which has been around since at least 2.6.11. Another box-killer, but is seems very hard to hit. ([email protected], "the dreaded oom-killer (reproducable in 2.6.11 - 2.6.16-rc1) :(")- http://bugzilla.kernel.org/show_bug.cgi?id=6060: an apparent ACPI regression.
- Nathan's "sysfs-related oops during module unload", which Greg seems to have under control.
- http://bugzilla.kernel.org/show_bug.cgi?id=6049 - another acpi regression. We have the actual offending commit here.
- A couple of random tty-related oopses reported by Jesper Juhl. We don't know why these happened - they appear to not be related to the tty buffering changes.
- http://bugzilla.kernel.org/show_bug.cgi?id=6038, another box-killing acpi regression.
- Various reports similar to
http://bugzilla.kernel.org/show_bug.cgi?id=6011, seemingly related to USB PCI quirk handling.- "Ben Castricum" <[email protected]> reports that ppp has started exhibiting mysterious failures (again).
- Nasty warnings from scsi about kobject-layer things being called from irq context. James has a push-it-to-process-context patch which sadly assumes
kmalloc()is immortal, but no other fix seems to have offered itself.- In http://bugzilla.kernel.org/show_bug.cgi?id=5989, Sanjoy Mahajan has another regression, but he's off collecting more info.
- Helge Hafting reports a usb printer regression - I don't know if that's still live?
- "Carlo E. Prelz" <[email protected]> has another USB/ehci regression ("ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1").
- Gerrit Bruchhuser <[email protected]> seems to have an aic7xxx regression ("AHA-7850 doesn't detect scanner anymore") but he doesn't say which kernel got it right.
- http://bugzilla.kernel.org/show_bug.cgi?id=5914 - a sata bug (which is quite unremarkable :(), but this one is reported to eat filesystems.
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
- Bjorn Nilsson <[email protected]> has an sk99lin regression ("3COM 3C940, does not work anymore after upgrade to 2.6.15")
- Andrey Borzenkov <[email protected]> has an acpi-cpufreq regression ("cannot unload acpi-cpufreq")
- "P. Christeas" <[email protected]> had an autofs regression ("Regression in Autofs, 2.6.15-git"), whic might be fixed now?
- ghrt <[email protected]> reports an alsa regression ("PROBLEM: SB Live! 5.1 (emu10k1, rev. 0a) doesn't work with 2.6.15")
- jinhong hu <[email protected]> reports what appears to be a qlogic regression ("kernel 2.6.15 scsi problem")
Quoted 10 lines
- Benjamin LaHaise <[email protected]> had an NFS problem ("NFS processes gettting stuck in D with currrent git").
These are clear regressions, reported in the last month by people who are willing to test patches. They're almost all in subsystems which have active and professional maintainers.
Really sad to say, but my Alsa ens1370 regression due to suspend problem is still there.
Only fix is reboot actually. Ready to patch :)
PS.
i have a bug similar to:
http://bugzilla.kernel.org/show_bug.cgi?id=6038 (marked as blocking by Andrew)
on my laptop.
but my dma expiry problem only happens during suspend.
I have a Sis 630 chipset with a 2.5" hitachi drive.
Been there...for ages..i can say: always...never got a working 2.6 kernel. However in my poor opinion it's not blocking on my system, just boring.
Patrizio
Re: Linux 2.6.16-rc3 - x86_64 specific outstanding bugs.
In reply to Andrew MortonAndrew Morton <[email protected]> writes:
[Note to people who find this using google in some archive. This list is for an old kernel and totally obsolete. Don't email me about asking about it. Use a newer kernel.]
Quoted 3 lines
We still have some serious bugs, several of which are in 2.6.15 as well:
From the x86-64 side for 2.6.16:
- Still oopses with mbind in some setups that I need to fix. Problem at least understood now. Should be fixed. Related to GFP_DMA32
- mbind can currently cause a local dos by starting the OOM killer early. Christoph Lameter has patches that should be added.
- Doesn't boot on Opterons with nodes in the middle unpopulated. I can reproduce on SimNow, but still need to fix (unfortunately it completely changes when I add any debugging code)
- kg_crashme causes do_exit be called with interrupts disabled. Need to fix that.
- logical cpu hot replug on multiprocessor opterons hangs the machine. Prime suspect is the powernow-k8 driver.
- Nested kprobes are broken and cause a stack overflow on the int3 stack. Impossible to fix fully, but should support nesting for a few levels at least. The systemtap testsuite triggers this apparently.
- The ATI timer fix using the local APIC timer breaks on many AMD laptops who don't run the APIC timer in C2. Latest plan is to switch to the RTC interrupt on these machines, but still needs to be implemented.
Also some other not well researched timer issue on the usual suspects (mainly nforce3 laptops which seem to have all kind of broken timing), but some of that might be related to the completely different timer code in -mm* which seems to miss all the latest fixes.
-Andi
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 3 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
Quoted 2 lines
- ghrt <[email protected]> reports an alsa regression ("PROBLEM: SB Live! 5.1 (emu10k1, rev. 0a) doesn't work with 2.6.15")
I couldn't find this bugzilla entry...
Takashi
Takashi Iwai ha scritto:
Quoted 7 lines
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 3 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
Quoted 9 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
i wrote "regression" because before (ehm...exactly don't know...about 2.6.14 time)
after suspend i had to restart my distro's mixer values service or i couldn't hear anything.
and...ok..it was boring but worked.
now i get 0x660 errors if i try to restore values and device seems dead, just flood the syslog.
sound apps slow down (like 100% cpu usage) and no sound produced.
only fix is reboot.
Quoted 10 lines
Quoted 3 lines
- ghrt <[email protected]> reports an alsa regression ("PROBLEM: SB Live! 5.1 (emu10k1, rev. 0a) doesn't work with 2.6.15")
I couldn't find this bugzilla entry...
Takashi
At Mon, 13 Feb 2006 13:37:55 +0100,
Quoted 18 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 7 lines
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 3 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
Quoted 9 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
Quoted 5 lines
i wrote "regression" because before (ehm...exactly don't know...about 2.6.14 time)
after suspend i had to restart my distro's mixer values service or i couldn't hear anything.
and...ok..it was boring but worked.
You abused the function which wasn't officially supported :)
Takashi
Takashi Iwai ha scritto:
Quoted 30 lines
At Mon, 13 Feb 2006 13:37:55 +0100,
Quoted 20 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 8 lines
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 4 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
Quoted 10 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
Quoted 6 lines
i wrote "regression" because before (ehm...exactly don't know...about 2.6.14 time)
after suspend i had to restart my distro's mixer values service or i couldn't hear anything.
and...ok..it was boring but worked.
Quoted 6 lines
You abused the function which wasn't officially supported :)
Takashi
nice i'm an abuser! :)
ok, seriously..that's bad, because before it was not implemented, so ok... but now it fails with errors (and make apps not working properly) which is worse.
Patrizio
At Mon, 13 Feb 2006 14:31:23 +0100,
Quoted 35 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 33 lines
At Mon, 13 Feb 2006 13:37:55 +0100,
Quoted 20 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 8 lines
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 4 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
Quoted 10 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
Quoted 6 lines
i wrote "regression" because before (ehm...exactly don't know...about 2.6.14 time)
after suspend i had to restart my distro's mixer values service or i couldn't hear anything.
and...ok..it was boring but worked.You abused the function which wasn't officially supported :)
Quoted 8 lines
Quoted 3 lines
Takashi
nice i'm an abuser! :)
ok, seriously..that's bad, because before it was not implemented, so ok... but now it fails with errors (and make apps not working properly) which is worse.
My rough guess is the initialization order, the resume was called too early.
What about to put sleep between snd_ensoniq_chip_init() and snd_ak4531_resume()? Or put more delay in snd_ak4531_resume()?
Takashi
Takashi Iwai ha scritto:
Quoted 54 lines
At Mon, 13 Feb 2006 14:31:23 +0100,
Quoted 44 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 35 lines
At Mon, 13 Feb 2006 13:37:55 +0100,
Quoted 24 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 10 lines
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 5 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
Quoted 11 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
Quoted 7 lines
i wrote "regression" because before (ehm...exactly don't know...about 2.6.14 time)
after suspend i had to restart my distro's mixer values service or i couldn't hear anything.
and...ok..it was boring but worked.Quoted 7 lines
You abused the function which wasn't officially supported :)
Takashi
Quoted 6 lines
nice i'm an abuser! :)
ok, seriously..that's bad, because before it was not implemented, so ok... but now it fails with errors (and make apps not working properly) which is worse.
Quoted 10 lines
My rough guess is the initialization order, the resume was called too early.
What about to put sleep between
snd_ensoniq_chip_init()andsnd_ak4531_resume()? Or put more delay insnd_ak4531_resume()?Takashi
i'm almost sure the problem is not there (or, at least not only) infact i get 0x660 errors (or better a long flood...) while suspending too.
there may be a bug or problem during suspending, and these problems affect the normal resume.
however sleep is not always trustable...soif you think that's an init problem you may add a
boolean value to check if init is completed or not and poll for TRUE value in the resume function.
but, as i wrote before, i'm not sure the problem is **only** there.
Patrizio
At Mon, 13 Feb 2006 15:34:28 +0100,
Quoted 63 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 61 lines
At Mon, 13 Feb 2006 14:31:23 +0100,
Quoted 44 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 35 lines
At Mon, 13 Feb 2006 13:37:55 +0100,
Quoted 24 lines · Patrizio Bassi
Takashi Iwai ha scritto:
Quoted 10 lines
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 5 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
Quoted 11 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
Quoted 7 lines
i wrote "regression" because before (ehm...exactly don't know...about 2.6.14 time)
after suspend i had to restart my distro's mixer values service or i couldn't hear anything.
and...ok..it was boring but worked.Quoted 7 lines
You abused the function which wasn't officially supported :)
Takashi
Quoted 6 lines
nice i'm an abuser! :)
ok, seriously..that's bad, because before it was not implemented, so ok... but now it fails with errors (and make apps not working properly) which is worse.
My rough guess is the initialization order, the resume was called too early.
What about to put sleep between
snd_ensoniq_chip_init()andsnd_ak4531_resume()? Or put more delay insnd_ak4531_resume()?
Quoted 5 lines
Quoted 3 lines
Takashi
i'm almost sure the problem is not there (or, at least not only) infact i get
0x660errors (or better a long flood...) while suspending too.
IIRC, suspend calls resume callback once to revive the devices back. So, basically you see the same problem here.
Takashi
Quoted 6 lines · Takashi Iwai
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 3 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
Quoted 6 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
That may be related to the fact that modular drivers are not present in memory during resume (just a thought).
Greetings,
Rafael
At Mon, 13 Feb 2006 14:09:51 +0100,
Quoted 11 lines · Rafael J. Wysocki
Quoted 9 lines · Takashi Iwai
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 3 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
Quoted 6 lines
Quoted 3 lines
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
That may be related to the fact that modular drivers are not present in memory during resume (just a thought).
I think the modular drivers are on memory but the order of re-initialization is different.
Takashi
Quoted 17 lines · Takashi Iwai
At Mon, 13 Feb 2006 14:09:51 +0100,
Quoted 15 lines · Rafael J. Wysocki
Quoted 12 lines · Takashi Iwai
At Sun, 12 Feb 2006 19:05:20 -0800,
Quoted 3 lines · Andrew Morton
- Patrizio Bassi <[email protected]> has an alsa suspend regression ("alsa suspend/resume continues to fail for ens1370")
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
About the problem there, I have no idea now what's wrong. The suspend-to-disk works fine if the driver is built as module but not as built-in kernel.
Quoted 5 lines
Quoted 2 lines
That may be related to the fact that modular drivers are not present in memory during resume (just a thought).
I think the modular drivers are on memory but the order of re-initialization is different.
No, they are not (this is the part I'm sure of). software_resume() is called before any modules have a chance to be loaded unless you boot with noresume, load them from an initrd and start the resume manually.
Greetings,
Rafael
Quoted 2 lines · Takashi Iwai
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
btw, PM support in snd-intel8x0 is broken (at least regarding suspending) in 2.6.16-rc2-mm1 on a nforce2 chipset
even if not playing while suspending, ALSA won't resume playing: no more program can play anything strace show that sound programs block on unfinished "futex(0xb7768060, FUTEX_WAIT, 29, NULL..." calls
lspci -vvvv:
00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev b2)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M]
Capabilities: <access denied>
00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:00.3 RAM memory: nVidia Corporation nForce 420 Memory Controller (DDR) (rev b2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev c3)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: <access denied>
00:01.1 SMBus: nVidia Corporation nForce PCI System Management (rev c1)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 5000 [size=16]
Region 1: I/O ports at d000 [size=16]
Region 2: I/O ports at d400 [size=32]
Capabilities: <access denied>
00:02.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) (prog-if 10 [OHCI])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at e0081000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
00:03.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) (prog-if 10 [OHCI])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 3
Region 0: Memory at e0080000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 3000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <access denied>
00:06.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 3
Region 0: I/O ports at d800 [size=256]
Region 1: I/O ports at dc00 [size=128]
Region 2: Memory at e0082000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge (rev c2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: de000000-dfffffff
Prefetchable memory behind bridge: 10000000-100fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
00:09.0 IDE interface: nVidia Corporation nForce IDE (rev c3) (prog-if 8a [Master SecP PriP])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Region 4: I/O ports at e400 [size=16]
Capabilities: <access denied>
00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge (rev b2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: dc000000-ddffffff
Prefetchable memory behind bridge: d0000000-d7ffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B-
01:06.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64)
Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2500ns min, 2500ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at c000 [size=128]
Region 1: Memory at df000000 (32-bit, non-prefetchable) [size=128]
[virtual] Expansion ROM at 10000000 [disabled] [size=128K]
Capabilities: <access denied>
01:07.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: Adaptec Unknown device 0335
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 10500ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 12
Region 0: Memory at df001000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
01:07.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: Adaptec Unknown device 0335
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 10500ns max), Cache Line Size 08
Interrupt: pin B routed to IRQ 11
Region 0: Memory at df002000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
01:07.2 USB Controller: NEC Corporation USB 2.0 (rev 02) (prog-if 20 [EHCI])
Subsystem: Adaptec Unknown device 03e0
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (4000ns min, 8500ns max), Cache Line Size 10
Interrupt: pin C routed to IRQ 11
Region 0: Memory at df003000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
02:00.0 VGA compatible controller: nVidia Corporation NVCrush11 [GeForce2 MX Integrated Graphics] (rev b1) (prog-if 00 [VGA])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 12
Region 0: Memory at dc000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (32-bit, prefetchable) [size=128M]
[virtual] Expansion ROM at dd000000 [disabled] [size=64K]
Capabilities: <access denied>
Quoted 2 lines · Takashi Iwai
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
btw, PM support in snd-intel8x0 is broken (at least regarding suspending) in 2.6.16-rc2-mm1 on a nforce2 chipset
even if not playing while suspending, ALSA won't resume playing: no more program can play anything strace show that sound programs block on unfinished "futex(0xb7768060, FUTEX_WAIT, 29, NULL..." calls
lspci -vvvv:
00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev b2)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M]
Capabilities: <access denied>
00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:00.3 RAM memory: nVidia Corporation nForce 420 Memory Controller (DDR) (rev b2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev c3)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: <access denied>
00:01.1 SMBus: nVidia Corporation nForce PCI System Management (rev c1)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 5000 [size=16]
Region 1: I/O ports at d000 [size=16]
Region 2: I/O ports at d400 [size=32]
Capabilities: <access denied>
00:02.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) (prog-if 10 [OHCI])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at e0081000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
00:03.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) (prog-if 10 [OHCI])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 3
Region 0: Memory at e0080000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 3000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <access denied>
00:06.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2)
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 3
Region 0: I/O ports at d800 [size=256]
Region 1: I/O ports at dc00 [size=128]
Region 2: Memory at e0082000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge (rev c2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: de000000-dfffffff
Prefetchable memory behind bridge: 10000000-100fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
00:09.0 IDE interface: nVidia Corporation nForce IDE (rev c3) (prog-if 8a [Master SecP PriP])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Region 4: I/O ports at e400 [size=16]
Capabilities: <access denied>
00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge (rev b2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: dc000000-ddffffff
Prefetchable memory behind bridge: d0000000-d7ffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B-
01:06.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64)
Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2500ns min, 2500ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at c000 [size=128]
Region 1: Memory at df000000 (32-bit, non-prefetchable) [size=128]
[virtual] Expansion ROM at 10000000 [disabled] [size=128K]
Capabilities: <access denied>
01:07.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: Adaptec Unknown device 0335
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 10500ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 12
Region 0: Memory at df001000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
01:07.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: Adaptec Unknown device 0335
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 10500ns max), Cache Line Size 08
Interrupt: pin B routed to IRQ 11
Region 0: Memory at df002000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
01:07.2 USB Controller: NEC Corporation USB 2.0 (rev 02) (prog-if 20 [EHCI])
Subsystem: Adaptec Unknown device 03e0
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (4000ns min, 8500ns max), Cache Line Size 10
Interrupt: pin C routed to IRQ 11
Region 0: Memory at df003000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
02:00.0 VGA compatible controller: nVidia Corporation NVCrush11 [GeForce2 MX Integrated Graphics] (rev b1) (prog-if 00 [VGA])
Subsystem: ABIT Computer Corp. Unknown device 7105
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 12
Region 0: Memory at dc000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (32-bit, prefetchable) [size=128M]
[virtual] Expansion ROM at dd000000 [disabled] [size=64K]
Capabilities: <access denied>
Quoted 8 lines · Thierry Vignaud
Quoted 2 lines · Takashi Iwai
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
btw, PM support in snd-intel8x0 is broken (at least regarding suspending) in 2.6.16-rc2-mm1 on a nforce2 chipset
Can you identify when this breakage occurred?
Quoted 7 lines · Andrew Morton
Quoted 5 lines
Quoted 2 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
btw, PM support in snd-intel8x0 is broken (at least regarding suspending) in 2.6.16-rc2-mm1 on a nforce2 chipset
Can you identify when this breakage occurred?
i'll try to compile a few older kernels (and/or just older alsa-kernel) if you want but i'm not sure it's a regression (i'll check if it has ever worked before).
i've tried unloading/reloading sound modules after resuming (maybe would it work if unloaded before suspending but of course full PM support would be nicer).
not sure if it can help but while resuming, the snd-intel8x0 printed quite a lot of warnings (due to preempting[1] i guess?) such as:
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
dmesg after resuming (only look at the beginning, the end is only ehci garbage b/c ehci is bugging for monthes (rejecting mass media after writing a few Mo)):
e+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 PCI: Setting latency timer of device 0000:00:08.0 to 64 ohci_hcd 0000:01:07.0: PCI D0, from previous PCI D3 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <c01b5d83> pci_set_power_state+0x127/0x16a <c01b5dd3> pci_enable_device_bars+0xd/0x38 <c01b5e0c> pci_enable_device+0xe/0x2c <cf848a1b> usb_hcd_pci_resume+0x11b/0x1b7 [usbcore] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [LNK4] -> GSI 12 (level, low) -> IRQ 12 ohci_hcd 0000:01:07.1: PCI D0, from previous PCI D3 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <c01b5d83> pci_set_power_state+0x127/0x16a <c01b5dd3> pci_enable_device_bars+0xd/0x38 <c01b5e0c> pci_enable_device+0xe/0x2c <cf848a1b> usb_hcd_pci_resume+0x11b/0x1b7 [usbcore] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 ACPI: PCI Interrupt 0000:01:07.1[B] -> Link [LNK1] -> GSI 11 (level, low) -> IRQ 11 ehci_hcd 0000:01:07.2: PCI D0, from previous PCI D3 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <c01b5d83> pci_set_power_state+0x127/0x16a <c01b5dd3> pci_enable_device_bars+0xd/0x38 <c01b5e0c> pci_enable_device+0xe/0x2c <cf848a1b> usb_hcd_pci_resume+0x11b/0x1b7 [usbcore] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ACPI: PCI Interrupt 0000:01:07.2[C] -> Link [LNK2] -> GSI 11 (level, low) -> IRQ 11 ehci_hcd 0000:01:07.2: lost power, restarting
usb usb5: root hub lost power or was resetehci_hcd 0000:01:07.2: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT ehci_hcd 0000:01:07.2: MWI activeehci_hcd 0000:01:07.2: ...powerdown ports...
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf861ed1> ehci_pci_reinit+0xf6/0xfe [ehci_hcd] <cf86584f> ehci_pci_resume+0xbd/0x10a [ehci_hcd] <cf848a7a> usb_hcd_pci_resume+0x17a/0x1b7 [usbcore] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ehci_hcd 0000:01:07.2: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT ehci_hcd 0000:01:07.2: init command 010009 (park)=0 ithresh=1 period=256 RUN ehci_hcd 0000:01:07.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004 ehci_hcd 0000:01:07.2: ...powerup ports...
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <cf86309c> ehci_run+0x165/0x16f [ehci_hcd] <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf865895> ehci_pci_resume+0x103/0x10a [ehci_hcd] <cf848a7a> usb_hcd_pci_resume+0x17a/0x1b7 [usbcore] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
nvidiafb: your nForce DIMMs are not arranged in optimal banks! i2c_adapter i2c-0: PM: resume from 0, parent 0000:02:00.0 still 1 i2c_adapter i2c-1: PM: resume from 0, parent 0000:02:00.0 still 1 i2c_adapter i2c-2: PM: resume from 0, parent 0000:02:00.0 still 1
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c01af304> vsnprintf+0x45a/0x497 <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5bb> ps2_command+0xdd/0x2ce <c02271bc> atkbd_probe+0x4c/0xe0 <c022842f> atkbd_reconnect+0x97/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6c6> schedule_timeout+0x81/0x95 <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe64f> ps2_command+0x171/0x2ce <c0124c68> autoremove_wake_function+0x0/0x2d <c02271bc> atkbd_probe+0x4c/0xe0 <c022842f> atkbd_reconnect+0x97/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe731> ps2_command+0x253/0x2ce <c0124c68> autoremove_wake_function+0x0/0x2d <c02271bc> atkbd_probe+0x4c/0xe0 <c022842f> atkbd_reconnect+0x97/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5bb> ps2_command+0xdd/0x2ce <c0124c68> autoremove_wake_function+0x0/0x2d <c022736e> atkbd_activate+0x1a/0x69 <c0228455> atkbd_reconnect+0xbd/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5d8> ps2_command+0xfa/0x2ce <c0124c68> autoremove_wake_function+0x0/0x2d <c022736e> atkbd_activate+0x1a/0x69 <c0228455> atkbd_reconnect+0xbd/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5bb> ps2_command+0xdd/0x2ce <c0124c68> autoremove_wake_function+0x0/0x2d <c0227385> atkbd_activate+0x31/0x69 <c0228455> atkbd_reconnect+0xbd/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5d8> ps2_command+0xfa/0x2ce <c0124c68> autoremove_wake_function+0x0/0x2d <c0227385> atkbd_activate+0x31/0x69 <c0228455> atkbd_reconnect+0xbd/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5bb> ps2_command+0xdd/0x2ce <c0124c68> autoremove_wake_function+0x0/0x2d <c0227397> atkbd_activate+0x43/0x69 <c0228455> atkbd_reconnect+0xbd/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5bb> ps2_command+0xdd/0x2ce <c0228465> atkbd_reconnect+0xcd/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c01fe3cb> ps2_sendbyte+0xa1/0xdd <c0124c68> autoremove_wake_function+0x0/0x2d <c01fe5d8> ps2_command+0xfa/0x2ce <c0228465> atkbd_reconnect+0xcd/0xfc <c01fc876> serio_reconnect_driver+0x21/0x34 <c01fc8ba> serio_resume+0xb/0x1a <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c0213851> ide_do_request+0x515/0x730 <c010339a> common_interrupt+0x1a/0x20 <c028c59f> wait_for_completion+0x70/0xc2 <c0112f98> default_wake_function+0x0/0xc <c0213b37> ide_do_drive_cmd+0xcb/0xf0 <c0211301> generic_ide_resume+0x7d/0x88 <c01a84c8> blk_end_sync_rq+0x0/0x1d <c02177f3> task_no_data_intr+0x0/0x63 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c59f> wait_for_completion+0x70/0xc2 <c0112f98> default_wake_function+0x0/0xc <c0213b37> ide_do_drive_cmd+0xcb/0xf0 <c0211301> generic_ide_resume+0x7d/0x88 <c01a84c8> blk_end_sync_rq+0x0/0x1d <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 BUG: warning at drivers/ide/ide-iops.c:1235/ide_wait_not_busy() <c0214b0a> ide_wait_not_busy+0x48/0x92 <c02136d9> ide_do_request+0x39d/0x730 <c01a83bc> freed_request+0x1d/0x37 <c0213cf8> ide_intr+0x19c/0x1d4 <c0219548> ide_dma_intr+0x0/0x8f <c01302f8> handle_IRQ_event+0x21/0x4a <c0130397> __do_IRQ+0x76/0xcf <c0104abe> do_IRQ+0x5e/0x79 ======================= <c010339a> common_interrupt+0x1a/0x20 <c01019bc> default_idle+0x2b/0x53 <c0101a24> cpu_idle+0x40/0x5e <c0322602> start_kernel+0x299/0x29b
usb usb1: finish resumeohci_hcd 0000:00:02.0: lost power
usb usb1: root hub lost power or was resetohci_hcd 0000:00:02.0: resetting from state 'reset', control = 0x600
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c011d0d9> __mod_timer+0x9f/0xa9 <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf828643> ohci_run+0x19e/0x46d [ohci_hcd] <cf8291ba> ohci_bus_resume+0x35e/0x5e4 [ohci_hcd] <cf840c5e> hcd_bus_resume+0x2d/0x7a [usbcore] <cf83d974> hub_resume+0x38/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ohci_hcd 0000:00:02.0: OHCI controller stateohci_hcd 0000:00:02.0: OHCI 1.0, NO legacy support registers ohci_hcd 0000:00:02.0: control 0x683 RWE RWC HCFS=operational CBSR=3 ohci_hcd 0000:00:02.0: cmdstatus 0x00000 SOC=0ohci_hcd 0000:00:02.0: intrstatus 0x00000004 SFohci_hcd 0000:00:02.0: intrenable 0x8000000a MIE RD WDH ohci_hcd 0000:00:02.0: hcca frame #0003ohci_hcd 0000:00:02.0: roothub.a 01000203 POTPGT=1 NPS NDP=3(3) ohci_hcd 0000:00:02.0: roothub.b 00000000 PPCM=0000 DR=0000 ohci_hcd 0000:00:02.0: roothub.status 00008000 DRWE ohci_hcd 0000:00:02.0: roothub.portstatus [0] 0x00000100 PPS ohci_hcd 0000:00:02.0: roothub.portstatus [1] 0x00000100 PPS ohci_hcd 0000:00:02.0: roothub.portstatus [2] 0x00000100 PPS ohci_hcd 0000:00:02.0: restart complete
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf83d9b0> hub_resume+0x74/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS usb usb2: finish resumeohci_hcd 0000:00:03.0: lost power
usb usb2: root hub lost power or was resetohci_hcd 0000:00:03.0: resetting from state 'reset', control = 0x600
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <cf842dc0> usb_start_wait_urb+0x141/0x14b [usbcore] <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf828643> ohci_run+0x19e/0x46d [ohci_hcd] <cf8291ba> ohci_bus_resume+0x35e/0x5e4 [ohci_hcd] <cf840c5e> hcd_bus_resume+0x2d/0x7a [usbcore] <cf83d974> hub_resume+0x38/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ohci_hcd 0000:00:03.0: OHCI controller stateohci_hcd 0000:00:03.0: OHCI 1.0, NO legacy support registers ohci_hcd 0000:00:03.0: control 0x683 RWE RWC HCFS=operational CBSR=3 ohci_hcd 0000:00:03.0: cmdstatus 0x00000 SOC=0ohci_hcd 0000:00:03.0: intrstatus 0x00000004 SFohci_hcd 0000:00:03.0: intrenable 0x8000000a MIE RD WDH ohci_hcd 0000:00:03.0: hcca frame #0003ohci_hcd 0000:00:03.0: roothub.a 01000203 POTPGT=1 NPS NDP=3(3) ohci_hcd 0000:00:03.0: roothub.b 00000000 PPCM=0000 DR=0000 ohci_hcd 0000:00:03.0: roothub.status 00008000 DRWE ohci_hcd 0000:00:03.0: roothub.portstatus [0] 0x00000100 PPS ohci_hcd 0000:00:03.0: roothub.portstatus [1] 0x00000100 PPS ohci_hcd 0000:00:03.0: roothub.portstatus [2] 0x00000100 PPS ohci_hcd 0000:00:03.0: restart complete
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf83d9b0> hub_resume+0x74/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ohci_hcd 0000:00:03.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS usb usb3: finish resumeohci_hcd 0000:01:07.0: lost power
usb usb3: root hub lost power or was resetohci_hcd 0000:01:07.0: resetting from state 'reset', control = 0x0
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <cf842dc0> usb_start_wait_urb+0x141/0x14b [usbcore] <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf828643> ohci_run+0x19e/0x46d [ohci_hcd] <cf8291ba> ohci_bus_resume+0x35e/0x5e4 [ohci_hcd] <cf840c5e> hcd_bus_resume+0x2d/0x7a [usbcore] <cf83d974> hub_resume+0x38/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ohci_hcd 0000:01:07.0: OHCI controller stateohci_hcd 0000:01:07.0: OHCI 1.0, NO legacy support registers ohci_hcd 0000:01:07.0: control 0x083 HCFS=operational CBSR=3 ohci_hcd 0000:01:07.0: cmdstatus 0x00000 SOC=0ohci_hcd 0000:01:07.0: intrstatus 0x00000004 SF ohci_hcd 0000:01:07.0: intrenable 0x8000001a MIE UE RD WDH ohci_hcd 0000:01:07.0: hcca frame #01feohci_hcd 0000:01:07.0: roothub.a ff000203 POTPGT=255 NPS NDP=3(3) ohci_hcd 0000:01:07.0: roothub.b 00000000 PPCM=0000 DR=0000 ohci_hcd 0000:01:07.0: roothub.status 00008000 DRWE ohci_hcd 0000:01:07.0: roothub.portstatus [0] 0x00000100 PPS ohci_hcd 0000:01:07.0: roothub.portstatus [1] 0x00000100 PPS ohci_hcd 0000:01:07.0: roothub.portstatus [2] 0x00000100 PPS ohci_hcd 0000:01:07.0: restart complete
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c011d0d9> __mod_timer+0x9f/0xa9 <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf83d9b0> hub_resume+0x74/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ohci_hcd 0000:01:07.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS usb 3-2: finish resume
usb 3-2: gone after usb resume? status -19
hub 3-0:1.0: resume port 2 --> -19
hub 3-0:1.0: logical disconnect on port 2
usb usb4: finish resumeohci_hcd 0000:01:07.1: lost power
usb usb4: root hub lost power or was resetohci_hcd 0000:01:07.1: resetting from state 'reset', control = 0x0
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <cf842dc0> usb_start_wait_urb+0x141/0x14b [usbcore] <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf828643> ohci_run+0x19e/0x46d [ohci_hcd] <cf8291ba> ohci_bus_resume+0x35e/0x5e4 [ohci_hcd] <cf840c5e> hcd_bus_resume+0x2d/0x7a [usbcore] <cf83d974> hub_resume+0x38/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ohci_hcd 0000:01:07.1: OHCI controller stateohci_hcd 0000:01:07.1: OHCI 1.0, NO legacy support registers ohci_hcd 0000:01:07.1: control 0x083 HCFS=operational CBSR=3 ohci_hcd 0000:01:07.1: cmdstatus 0x00000 SOC=0ohci_hcd 0000:01:07.1: intrstatus 0x00000004 SF ohci_hcd 0000:01:07.1: intrenable 0x8000001a MIE UE RD WDH ohci_hcd 0000:01:07.1: hcca frame #01feohci_hcd 0000:01:07.1: roothub.a ff000202 POTPGT=255 NPS NDP=2(2) ohci_hcd 0000:01:07.1: roothub.b 00000000 PPCM=0000 DR=0000 ohci_hcd 0000:01:07.1: roothub.status 00008000 DRWE ohci_hcd 0000:01:07.1: roothub.portstatus [0] 0x00000100 PPS ohci_hcd 0000:01:07.1: roothub.portstatus [1] 0x00000100 PPS ohci_hcd 0000:01:07.1: restart complete
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c011d0d9> __mod_timer+0x9f/0xa9 <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf83d9b0> hub_resume+0x74/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75 ohci_hcd 0000:01:07.1: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS usb usb5: finish resume BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <c011d16a> msleep+0x17/0x1c <cf83d9b0> hub_resume+0x74/0x17f [usbcore] <cf83c4f7> usb_generic_resume+0x0/0xcf [usbcore] <cf83c56a> usb_generic_resume+0x73/0xcf [usbcore] <cf83d610> finish_device_resume+0x119/0x16a [usbcore] <cf83e46a> usb_resume_device+0x46/0xa1 [usbcore] <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
ehci_hcd 0000:01:07.2: GetStatus port 2 status 001002 POWER sig=se0 CSC ehci_hcd 0000:01:07.2: GetStatus port 3 status 001403 POWER sig=k CSC CONNECT Restarting tasks...<3>BUG: scheduling while atomic: zsh/0x00000001/2196
<c028b93f> schedule+0x43/0x54e <c0112f8f> try_to_wake_up+0xe1/0xea
<c012cea3> thaw_processes+0x97/0xc4 <c012d90e> unprepare_processes+0x25/0x2a
<c012db24> pm_suspend_disk+0xc4/0xc8 <c012cb95> enter_state+0x50/0x16f
<c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f
<c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9
<c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122
<c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0002ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS hub 1-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
done
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c014922a> vfs_write+0xe3/0x122 <c01499df> sys_write+0x3c/0x63 <c0102a3a> work_resched+0x5/0x16 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028be58> io_schedule+0xe/0x16 <c014a963> sync_buffer+0x2b/0x2e <c028c733> __wait_on_bit+0x31/0x56 <c014a938> sync_buffer+0x0/0x2e <c014a938> sync_buffer+0x0/0x2e <c028c7b9> out_of_line_wait_on_bit+0x61/0x69 <c0124d17> wake_bit_function+0x0/0x3c <c014a1b3> __wait_on_buffer+0x1c/0x1f <c017b03e> ext3_bread+0x47/0x61 <c017c4a2> dx_probe+0x3a/0x2af <c017d4e4> ext3_find_entry+0xc2/0x4ed <c01af373> snprintf+0x1b/0x1f <c017dfaa> ext3_lookup+0x1f/0x75 <c0153848> __lookup_hash+0xaa/0xc3 <c0155916> open_namei+0xc9/0x4e5 <c0148839> do_filp_open+0x1c/0x31 <c01af373> snprintf+0x1b/0x1f <c014885d> filp_open+0xf/0x11 <c0151295> do_coredump+0x4e9/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c01a7957> generic_make_request+0x191/0x1c2 <c028be58> io_schedule+0xe/0x16 <c014a963> sync_buffer+0x2b/0x2e <c028c733> __wait_on_bit+0x31/0x56 <c014a938> sync_buffer+0x0/0x2e <c014a938> sync_buffer+0x0/0x2e <c028c7b9> out_of_line_wait_on_bit+0x61/0x69 <c0124d17> wake_bit_function+0x0/0x3c <c014a1b3> __wait_on_buffer+0x1c/0x1f <c017b03e> ext3_bread+0x47/0x61 <c017d571> ext3_find_entry+0x14f/0x4ed <c017dfaa> ext3_lookup+0x1f/0x75 <c0153848> __lookup_hash+0xaa/0xc3 <c0155916> open_namei+0xc9/0x4e5 <c0148839> do_filp_open+0x1c/0x31 <c01af373> snprintf+0x1b/0x1f <c014885d> filp_open+0xf/0x11 <c0151295> do_coredump+0x4e9/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19
hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 hub 2-0:1.0: state 7 ports 3 chg 0000 evt 0002ohci_hcd 0000:00:03.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c01354ed> get_page_from_freelist+0x7d/0x2fb <c01a7957> generic_make_request+0x191/0x1c2 <c028be58> io_schedule+0xe/0x16 <c014a963> sync_buffer+0x2b/0x2e <c028c733> __wait_on_bit+0x31/0x56 <c014a938> sync_buffer+0x0/0x2e <c014a938> sync_buffer+0x0/0x2e <c028c7b9> out_of_line_wait_on_bit+0x61/0x69 <c0124d17> wake_bit_function+0x0/0x3c <c014a1b3> __wait_on_buffer+0x1c/0x1f <c014c575> __bread+0x59/0x6c <c01771b4> read_inode_bitmap+0x28/0x4c <c01779ed> ext3_new_inode+0x3f9/0x824 <c017d188> ext3_create+0x5d/0xc2 <c017d12b> ext3_create+0x0/0xc2 <c0155811> vfs_create+0x5e/0x9a <c0155982> open_namei+0x135/0x4e5 <c0148839> do_filp_open+0x1c/0x31 <c01af373> snprintf+0x1b/0x1f <c014885d> filp_open+0xf/0x11 <c0151295> do_coredump+0x4e9/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 hub 3-0:1.0: state 7 ports 3 chg 0004 evt 0006ohci_hcd 0000:01:07.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS hub 3-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c01354ed> get_page_from_freelist+0x7d/0x2fb <c01a7957> generic_make_request+0x191/0x1c2 <c028be58> io_schedule+0xe/0x16 <c014a963> sync_buffer+0x2b/0x2e <c028c733> __wait_on_bit+0x31/0x56 <c014a938> sync_buffer+0x0/0x2e <c014a938> sync_buffer+0x0/0x2e <c028c7b9> out_of_line_wait_on_bit+0x61/0x69 <c0124d17> wake_bit_function+0x0/0x3c <c014a1b3> __wait_on_buffer+0x1c/0x1f <c0178352> __ext3_get_inode_loc+0x27b/0x2c2 <c017841e> ext3_reserve_inode_write+0x1a/0x7a <c017889b> ext3_mark_inode_dirty+0x11/0x27 <c01858ca> journal_dirty_metadata+0x12e/0x15c <c0177d87> ext3_new_inode+0x793/0x824 <c017d188> ext3_create+0x5d/0xc2 <c017d12b> ext3_create+0x0/0xc2 <c0155811> vfs_create+0x5e/0x9a <c0155982> open_namei+0x135/0x4e5 <c0148839> do_filp_open+0x1c/0x31 <c01af373> snprintf+0x1b/0x1f <c014885d> filp_open+0xf/0x11 <c0151295> do_coredump+0x4e9/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19
hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 ohci_hcd 0000:01:07.0: GetStatus roothub.portstatus [1] = 0x00010100 CSC PPS hub 3-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
usb 3-2: USB disconnect, address 3
usb 3-2: usb_disable_device nuking all URBs
usb 3-2: unregistering interface 3-2:1.0
usb 3-2:1.0: uevent
usb 3-2: unregistering device
usb 3-2: uevent
hub 3-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100 hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0002ohci_hcd 0000:01:07.1: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS hub 4-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c01a7957> generic_make_request+0x191/0x1c2 <c028be58> io_schedule+0xe/0x16 <c014a963> sync_buffer+0x2b/0x2e <c028c733> __wait_on_bit+0x31/0x56 <c014a938> sync_buffer+0x0/0x2e <c014a938> sync_buffer+0x0/0x2e <c028c7b9> out_of_line_wait_on_bit+0x61/0x69 <c0124d17> wake_bit_function+0x0/0x3c <c014a1b3> __wait_on_buffer+0x1c/0x1f <c0178352> __ext3_get_inode_loc+0x27b/0x2c2 <c017841e> ext3_reserve_inode_write+0x1a/0x7a <c017889b> ext3_mark_inode_dirty+0x11/0x27 <c017be7c> add_dirent_to_buf+0x1fa/0x279 <c017c836> ext3_add_entry+0x11f/0x871 <c0177e08> ext3_new_inode+0x814/0x824 <c017cf97> ext3_add_nondir+0xf/0x3a <c017d1b9> ext3_create+0x8e/0xc2 <c017d12b> ext3_create+0x0/0xc2 <c0155811> vfs_create+0x5e/0x9a <c0155982> open_namei+0x135/0x4e5 <c0148839> do_filp_open+0x1c/0x31 <c01af373> snprintf+0x1b/0x1f <c014885d> filp_open+0xf/0x11 <c0151295> do_coredump+0x4e9/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19
hub 4-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 hub 5-0:1.0: state 7 ports 5 chg 0004 evt 000cehci_hcd 0000:01:07.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT hub 5-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
usb 5-2: USB disconnect, address 3
usb 5-2: usb_disable_device nuking all URBs
usb 5-2: unregistering interface 5-2:1.0
usb 5-2:1.0: uevent
usb 5-2: unregistering device
usb 5-2: uevent
hub 5-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c011652c> vprintk+0x23f/0x286 <c01a7957> generic_make_request+0x191/0x1c2 <c028be58> io_schedule+0xe/0x16 <c014a963> sync_buffer+0x2b/0x2e <c028c733> __wait_on_bit+0x31/0x56 <c014a938> sync_buffer+0x0/0x2e <c014a938> sync_buffer+0x0/0x2e <c028c7b9> out_of_line_wait_on_bit+0x61/0x69 <c0124d17> wake_bit_function+0x0/0x3c <c014a1b3> __wait_on_buffer+0x1c/0x1f <c014c575> __bread+0x59/0x6c <c017550e> read_block_bitmap+0x27/0x4a <c0176336> ext3_new_blocks+0x191/0x55d <c01281c3> debug_mutex_add_waiter+0x14/0x25 <c0179dad> ext3_get_blocks_handle+0x12b/0x89d <c0179dad> ext3_get_blocks_handle+0x12b/0x89d <c0179fd5> ext3_get_blocks_handle+0x353/0x89d <c0102a5e> work_notifysig+0x13/0x19 <c011652c> vprintk+0x23f/0x286 <c011652c> vprintk+0x23f/0x286 <c010dc72> smp_apic_timer_interrupt+0x2a/0x2f <c01033bc> apic_timer_interrupt+0x1c/0x24 <c017a5ad> ext3_direct_io_get_blocks+0x8e/0xa8 <c017a5d6> ext3_get_block+0xf/0x12 <c014b904> __block_prepare_write+0x114/0x379 <c014bb7f> block_prepare_write+0x16/0x22 <c017a5c7> ext3_get_block+0x0/0x12 <c01795fc> ext3_prepare_write+0x7f/0x115 <c017a5c7> ext3_get_block+0x0/0x12 <c013216e> generic_file_buffered_write+0x21e/0x52b <c0183f09> journal_stop+0x1c7/0x1d1 <c017ef4f> __ext3_journal_stop+0x19/0x34 <c013353e> __generic_file_aio_write_nolock+0x3a1/0x3de <c013377e> generic_file_aio_write+0x3d/0xa4 <c0133792> generic_file_aio_write+0x51/0xa4 <c017701d> ext3_file_write+0x19/0x83 <c0148df6> do_sync_write+0xb8/0xf3 <c0124c68> autoremove_wake_function+0x0/0x2d <c017ba41> ext3_orphan_del+0x52/0x1b6 <c015d87a> inode_setattr+0x146/0x150 <c01affab> _mmx_memcpy+0x3c/0x136 <c0169540> dump_write+0x10/0x1c <c016b515> elf_core_dump+0x6ad/0xb32 <c015dba3> notify_change+0x20d/0x21d <c01512f1> do_coredump+0x545/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19 ehci_hcd 0000:01:07.2: port 2 high speed ehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT usb 5-2: new high speed USB device using ehci_hcd and address 4 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c01a7957> generic_make_request+0x191/0x1c2 <c028be58> io_schedule+0xe/0x16 <c014a963> sync_buffer+0x2b/0x2e <c028c733> __wait_on_bit+0x31/0x56 <c014a938> sync_buffer+0x0/0x2e <c014a938> sync_buffer+0x0/0x2e <c028c7b9> out_of_line_wait_on_bit+0x61/0x69 <c0124d17> wake_bit_function+0x0/0x3c <c014a1b3> __wait_on_buffer+0x1c/0x1f <c014c575> __bread+0x59/0x6c <c0179c0d> ext3_get_branch+0x6b/0xe0 <c0179d37> ext3_get_blocks_handle+0xb5/0x89d <c0135653> get_page_from_freelist+0x1e3/0x2fb <c01858ef> journal_dirty_metadata+0x153/0x15c <c0178830> ext3_mark_iloc_dirty+0x2d7/0x331 <c017a5ad> ext3_direct_io_get_blocks+0x8e/0xa8 <c017a5d6> ext3_get_block+0xf/0x12 <c0164d2d> do_mpage_readpage+0xe3/0x318 <c0132461> generic_file_buffered_write+0x511/0x52b <c0165787> mpage_readpages+0x8e/0xef <c017a5c7> ext3_get_block+0x0/0x12 <c01357b8> __alloc_pages+0x4d/0x25d <c0177e7e> ext3_readpages+0x0/0x15 <c0136aaf> __do_page_cache_readahead+0x140/0x201 <c017a5c7> ext3_get_block+0x0/0x12 <c013377e> generic_file_aio_write+0x3d/0xa4 <c013379b> generic_file_aio_write+0x5a/0xa4 <c0132a98> filemap_nopage+0x148/0x2e2 <c013bab5> __handle_mm_fault+0x201/0x6a2 <c013c102> get_user_pages+0x1ac/0x25b <c016b7eb> elf_core_dump+0x983/0xb32 <c01512f1> do_coredump+0x545/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19 BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c0177e7e> ext3_readpages+0x0/0x15 <c0136aaf> __do_page_cache_readahead+0x140/0x201 <c017a5c7> ext3_get_block+0x0/0x12 <c028be58> io_schedule+0xe/0x16 <c0131043> sync_page+0x0/0x36 <c0131076> sync_page+0x33/0x36 <c028c7ed> __wait_on_bit_lock+0x2c/0x51 <c0131169> __lock_page+0x50/0x56 <c0124d17> wake_bit_function+0x0/0x3c <c0132b5c> filemap_nopage+0x20c/0x2e2 <c013bab5> __handle_mm_fault+0x201/0x6a2 <c013c102> get_user_pages+0x1ac/0x25b <c016b7eb> elf_core_dump+0x983/0xb32 <c01512f1> do_coredump+0x545/0x59e <c011e84a> __dequeue_signal+0x149/0x154 <c011f777> get_signal_to_deliver+0x3eb/0x418 <c0111230> do_page_fault+0x0/0x4c3 <c0102372> do_notify_resume+0x6f/0x5a1 <c0103463> error_code+0x4f/0x54 <c028dd4a> iret_exc+0x136/0x779 <c01116a3> do_page_fault+0x473/0x4c3 <c0111230> do_page_fault+0x0/0x4c3 <c0102a5e> work_notifysig+0x13/0x19
note: zsh[2196] exited with preempt_count 1
0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0ehci_hcd 0000:01:07.2: Unlink after no-IRQ? Controller is probably using the wrong IRQ. usb 5-2: khubd timed out on ep0in len=8/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
0:0:0:0: rejecting I/O to dead device
usb 5-2: device not accepting address 4, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 5
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0in len=18/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 5, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 6
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 6, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 7
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 7, error -110ehci_hcd 0000:01:07.2: GetStatus port 3 status 001403 POWER sig=k CSC CONNECT
hub 5-0:1.0: port 3, status 0501, change 0001, 480 Mb/s
hub 5-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501ehci_hcd 0000:01:07.2: port 3 low speed --> companionehci_hcd 0000:01:07.2: GetStatus port 3 status 003402 POWER OWNER sig=k CSC
hub 5-0:1.0: state 7 ports 5 chg 0000 evt 0000
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0004ohci_hcd 0000:01:07.0: GetStatus roothub.portstatus [1] = 0x00010301 CSC LSDA PPS CCS hub 3-0:1.0: port 2, status 0301, change 0001, 1.5 Mb/s
0:0:0:0: rejecting I/O to dead device
hub 3-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x301ohci_hcd 0000:01:07.0: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA PPS PES CCS usb 3-2: new low speed USB device using ohci_hcd and address 4ohci_hcd 0000:01:07.0: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA PPS PES CCS usb 3-2: skipped 1 descriptor after interface
usb 3-2: default language 0x0409
usb 3-2: new device found, idVendor=045e, idProduct=0040
usb 3-2: new device strings: Mfr=1, Product=3, SerialNumber=0
usb 3-2: Product: Microsoft 3-Button Mouse with IntelliEye(TM)
usb 3-2: Manufacturer: Microsoft
usb 3-2: uevent
usb 3-2: device is bus-powered
usb 3-2: configuration #1 chosen from 1 choice
usb 3-2: adding 3-2:1.0 (config #1, interface 0)
usb 3-2:1.0: uevent
usbhid 3-2:1.0: usb_probe_interface
usbhid 3-2:1.0: usb_probe_interface - got id
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /class/input/input3
input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:01:07.0-2 drivers/usb/core/inode.c: creating file '004'
hub 3-0:1.0: state 7 ports 3 chg 0000 evt 0004
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
0:0:0:0: rejecting I/O to dead device
hub 5-0:1.0: state 7 ports 5 chg 0000 evt 0004ehci_hcd 0000:01:07.2: GetStatus port 2 status 001002 POWER sig=se0 CSC
hub 5-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
hub 5-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100
hub 5-0:1.0: state 7 ports 5 chg 0000 evt 0004ehci_hcd 0000:01:07.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT
hub 5-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
hub 5-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 9
usb 5-2: khubd timed out on ep0in len=18/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 9, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 10
usb 5-2: khubd timed out on ep0in len=18/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 10, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 11
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 11, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 12
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 12, error -110
hub 5-0:1.0: state 7 ports 5 chg 0000 evt 0004ehci_hcd 0000:01:07.2: GetStatus port 2 status 001002 POWER sig=se0 CSC
hub 5-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
hub 5-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100
hub 5-0:1.0: state 7 ports 5 chg 0000 evt 0004ehci_hcd 0000:01:07.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT
hub 5-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
hub 5-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 13
usb 5-2: khubd timed out on ep0in len=8/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 13, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 14
usb 5-2: khubd timed out on ep0in len=18/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 14, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 15
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 15, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 16
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 16, error -110
hub 5-0:1.0: state 7 ports 5 chg 0000 evt 0004ehci_hcd 0000:01:07.2: GetStatus port 2 status 001002 POWER sig=se0 CSC
hub 5-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
hub 5-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100
hub 5-0:1.0: state 7 ports 5 chg 0000 evt 0004ehci_hcd 0000:01:07.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT
hub 5-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
hub 5-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 17
usb 5-2: khubd timed out on ep0in len=8/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 17, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 18
usb 5-2: khubd timed out on ep0in len=18/64ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 18, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 19
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 19, error -110ehci_hcd 0000:01:07.2: port 2 high speedehci_hcd 0000:01:07.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 5-2: new high speed USB device using ehci_hcd and address 20
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: khubd timed out on ep0out len=0/0
usb 5-2: device not accepting address 20, error -110
while testing suspending with that kernel, the root shell that echoed in /sys/power/state got killed with "note: zsh[2196] exited with preempt_count 1"
Quoted 6 lines · Thierry Vignaud
Quoted 3 lines · Andrew Morton
Quoted 3 lines
Quoted 2 lines
It's not a "regression". PM didn't work with ens1370 at all in the eralier version.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
btw, PM support in snd-intel8x0 is broken (at least regarding suspending) in 2.6.16-rc2-mm1 on a nforce2 chipset
Can you identify when this breakage occurred?
i'll try to compile a few older kernels (and/or just older alsa-kernel) if you want but i'm not sure it's a regression (i'll check if it has ever worked before).
OK, thanks.
Quoted 18 lines
i've tried unloading/reloading sound modules after resuming (maybe would it work if unloaded before suspending but of course full PM support would be nicer).
not sure if it can help but while resuming, the snd-intel8x0 printed quite a lot of warnings (due to preempting[1] i guess?) such as:
BUG: scheduling while atomic: zsh/0x00000001/2196 <c028b93f> schedule+0x43/0x54e <c028c6bf> schedule_timeout+0x7a/0x95 <c011c755> process_timeout+0x0/0x5 <d4938e56> snd_intel8x0_chip_init+0x110/0x39e [snd_intel8x0] <d4939142> intel8x0_resume+0x5e/0x1ba [snd_intel8x0] <c01b6dee> pci_device_resume+0x16/0x43 <c02025d9> resume_device+0x7d/0x96 <c02026a7> dpm_resume+0x58/0x80 <c02026dc> device_resume+0xd/0x16 <c012db1f> pm_suspend_disk+0xbf/0xc8 <c012cb95> enter_state+0x50/0x16f <c012cd37> state_store+0x83/0x8f <c012ccb4> state_store+0x0/0x8f <c0173492> subsys_attr_store+0x1e/0x22 <c0173a1b> sysfs_write_file+0x92/0xb9 <c0173989> sysfs_write_file+0x0/0xb9 <c01491ca> vfs_write+0x83/0x122 <c01499df> sys_write+0x3c/0x63 <c0102973> sysenter_past_esp+0x54/0x75
Quoted 3 lines
dmesg after resuming (only look at the beginning, the end is only ehci garbage b/c ehci is bugging for monthes (rejecting mass media after writing a few Mo)):
That's odd. I don't see what could have elevated preempt_count() on that path. What does `grep PREEMPT .config' say?
Quoted 5 lines · Andrew Morton
...
- Various reports similar to
http://bugzilla.kernel.org/show_bug.cgi?id=6011, seemingly related to USB PCI quirk handling.
...
This bug contains a patch.
What is the status of this patch?
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 10 lines · Adrian Bunk
Quoted 5 lines · Andrew Morton
...
- Various reports similar to
http://bugzilla.kernel.org/show_bug.cgi?id=6011, seemingly related to USB PCI quirk handling.
...This bug contains a patch.
What is the status of this patch?
The patch is in Greg's tree so should see its way to Linus soon. However, it's not the complete fix for the general issue.
Gentoo have had two reports of it. One is fixed by David's patch, the other is not (http://bugs.gentoo.org/122277 - will be re-filed on kernel bugzilla once I have investigated more).
Daniel
Quoted 3 lines · Andrew Morton
- A couple of random tty-related oopses reported by Jesper Juhl. We don't know why these happened - they appear to not be related to the tty buffering changes.
I just posted a patch for this under
[PATCH] tty reference count fix
This is not related to the tty buffering changes.
Signature · 2 lines
Paul Fulghum Microgate Systems, Ltd
Quoted 5 lines · Andrew Morton
We still have some serious bugs, several of which are in 2.6.15 as well:
- Nathan's "sysfs-related oops during module unload", which Greg seems to have under control.
Yes, this isn't a "regression" but has been there for a while. It can also only be triggered by a root user, so it's severity is much lower.
Quoted 3 lines
- Various reports similar to
http://bugzilla.kernel.org/show_bug.cgi?id=6011, seemingly related to USB PCI quirk handling.
I have a patch for this, which will be going to Linus later tonight.
Quoted 4 lines
- Nasty warnings from scsi about kobject-layer things being called from irq context. James has a push-it-to-process-context patch which sadly assumes
kmalloc()is immortal, but no other fix seems to have offered itself.
This has been the case for a long time. I don't really think there is a rush to get this fixed, but I really like James's proposed patch. It's up to him if he feels it is ready for 2.6.16 or not.
Quoted 2 lines
- Helge Hafting reports a usb printer regression - I don't know if that's still live?
He never reported back, and one other person who reported this, figured out that it was bad ram in the system. Replacing that fixed the issue. I've also printed a lot of stuff here (tax time...) and had no problems.
Quoted 3 lines
- "Carlo E. Prelz" <[email protected]> has another USB/ehci regression ("ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1").
Fixed by the previously mentioned EHCI quirk/handoff patch that will be going to Linus.
So, that's it for the USB stuff, thankfully.
thanks,
greg k-h
Quoted 5 lines · Greg KH
Quoted 1 line
- Nasty warnings from scsi about kobject-layer things being called
from
Quoted 1 line
irq context. James has a push-it-to-process-context patch which
sadly
Quoted 1 line
assumes
kmalloc()is immortal, but no other fix seems to have
Quoted 8 lines
offered
Quoted 1 line
itself.
This has been the case for a long time. I don't really think there is a
rush to get this fixed, but I really like James's proposed patch. It's
up to him if he feels it is ready for 2.6.16 or not.
Well, I can't solve the problem that it requires memory allocation from IRQ context to operate. Based on that, it's an unsafe interface. I'm going to put it inside SCSI for 2.6.16, since it's better than what we have now, but I don't think we can export it globally.
James
Quoted 15 lines · James Bottomley
Quoted 5 lines · Greg KH
Quoted 1 line
- Nasty warnings from scsi about kobject-layer things being called
from
Quoted 1 line
irq context. James has a push-it-to-process-context patch which
sadly
Quoted 1 line
assumes
kmalloc()is immortal, but no other fix seems to haveQuoted 8 lines
offered
Quoted 1 line
itself.
This has been the case for a long time. I don't really think there is a
rush to get this fixed, but I really like James's proposed patch. It's
up to him if he feels it is ready for 2.6.16 or not.
Quoted 4 lines
Well, I can't solve the problem that it requires memory allocation from IRQ context to operate. Based on that, it's an unsafe interface. I'm going to put it inside SCSI for 2.6.16, since it's better than what we have now, but I don't think we can export it globally.
Could we perhaps make this safer and more general?
For instance, add to struct device a "pending puts" counter and a list header (both protected by a global spinlock), and have a kernel thread periodically check the list, doing put_device wherever needed. How does that sound?
Alan Stern
Quoted 22 lines · Alan Stern
Quoted 15 lines · James Bottomley
Quoted 5 lines · Greg KH
Quoted 1 line
- Nasty warnings from scsi about kobject-layer things being called
from
Quoted 1 line
irq context. James has a push-it-to-process-context patch which
sadly
Quoted 1 line
assumes
kmalloc()is immortal, but no other fix seems to haveQuoted 8 lines
offered
Quoted 1 line
itself.
This has been the case for a long time. I don't really think there is a
rush to get this fixed, but I really like James's proposed patch. It's
up to him if he feels it is ready for 2.6.16 or not.Quoted 4 lines
Well, I can't solve the problem that it requires memory allocation from IRQ context to operate. Based on that, it's an unsafe interface. I'm going to put it inside SCSI for 2.6.16, since it's better than what we have now, but I don't think we can export it globally.
Quoted 6 lines
Could we perhaps make this safer and more general?
For instance, add to struct device a "pending puts" counter and a list header (both protected by a global spinlock), and have a kernel thread periodically check the list, doing
put_devicewherever needed. How does that sound?
Sounds like a garbage collector :)
Nah, I don't think it's a good idea. James's patch should work just fine.
thanks,
greg k-h
Quoted 3 lines · Greg KH
Nah, I don't think it's a good idea. James's patch should work just fine.
another option is to have a "kill list" which you put the thing on, and then wake up a thread. only 2 pointers in the object ;(
Quoted 7 lines · Arjan van de Ven
Quoted 3 lines · Greg KH
Nah, I don't think it's a good idea. James's patch should work just fine.
another option is to have a "kill list" which you put the thing on, and then wake up a thread. only 2 pointers in the object ;(
Hm, that's almost what James's patch is trying to do. Care to mock up a patch that shows this? It might be a simpler solution.
thanks,
greg k-h
Quoted 11 lines · Greg KH
Quoted 7 lines · Arjan van de Ven
Quoted 3 lines · Greg KH
Nah, I don't think it's a good idea. James's patch should work just fine.
another option is to have a "kill list" which you put the thing on, and then wake up a thread. only 2 pointers in the object ;(
Hm, that's almost what James's patch is trying to do. Care to mock up a patch that shows this? It might be a simpler solution.
It won't work. You might have to do 2 put_device calls on the same structure. That's why I suggested the "pending puts" counter; something can't go on a list more than once.
Alan Stern
Quoted 11 lines · Alan Stern
Quoted 9 lines · Greg KH
Quoted 7 lines · Arjan van de Ven
Quoted 3 lines · Greg KH
Nah, I don't think it's a good idea. James's patch should work just fine.
another option is to have a "kill list" which you put the thing on, and then wake up a thread. only 2 pointers in the object ;(
Quoted 6 lines
Quoted 2 lines
Hm, that's almost what James's patch is trying to do. Care to mock up a patch that shows this? It might be a simpler solution.
It won't work. You might have to do 2
put_devicecalls on the same structure. That's why I suggested the "pending puts" counter; something can't go on a list more than once.
It would only go on the list if the "put" was the last one. Otherwise it would not make any sense to put it on any list.
thanks,
greg k-h
Quoted 15 lines · Greg KH
Quoted 14 lines · Alan Stern
Quoted 11 lines · Greg KH
Quoted 7 lines · Arjan van de Ven
Quoted 3 lines · Greg KH
Nah, I don't think it's a good idea. James's patch should work just fine.
another option is to have a "kill list" which you put the thing on, and then wake up a thread. only 2 pointers in the object ;(
Hm, that's almost what James's patch is trying to do. Care to mock up a patch that shows this? It might be a simpler solution.
Quoted 6 lines
Quoted 3 lines
It won't work. You might have to do 2
put_devicecalls on the same structure. That's why I suggested the "pending puts" counter; something can't go on a list more than once.It would only go on the list if the "put" was the last one. Otherwise it would not make any sense to put it on any list.
There's no way to know whether or not any particular "put" is the last one. So you have to assume they all are.
Alan Stern
Quoted 21 lines · Alan Stern
Quoted 19 lines · Greg KH
Quoted 17 lines · Alan Stern
Quoted 11 lines · Greg KH
Quoted 7 lines · Arjan van de Ven
Quoted 3 lines · Greg KH
Nah, I don't think it's a good idea. James's patch should work just fine.
another option is to have a "kill list" which you put the thing on, and then wake up a thread. only 2 pointers in the object ;(
Hm, that's almost what James's patch is trying to do. Care to mock up a patch that shows this? It might be a simpler solution.
It won't work. You might have to do 2
put_devicecalls on the same structure. That's why I suggested the "pending puts" counter; something can't go on a list more than once.
Quoted 5 lines
Quoted 2 lines
It would only go on the list if the "put" was the last one. Otherwise it would not make any sense to put it on any list.
There's no way to know whether or not any particular "put" is the last one. So you have to assume they all are.
The underlying kobject can "know" that the put was the last one, and handle it differently if needed. Yes, it would not use a kref anymore, but that might be needed here.
thanks,
greg k-h
Quoted 9 lines · Greg KH
Quoted 5 lines
Quoted 2 lines
It would only go on the list if the "put" was the last one. Otherwise it would not make any sense to put it on any list.
There's no way to know whether or not any particular "put" is the last one. So you have to assume they all are.
The underlying kobject can "know" that the put was the last one, and handle it differently if needed. Yes, it would not use a kref anymore, but that might be needed here.
You would need a kref variant, something which would include room for the list header and a pointer to the release routine. Okay, that does involve less time overhead than what I proposed (although the same amount of space overhead).
Alan Stern
James Bottomley
maintainerQuoted 6 lines · Alan Stern
Could we perhaps make this safer and more general?
For instance, add to struct device a "pending puts" counter and a list header (both protected by a global spinlock), and have a kernel thread periodically check the list, doing
put_devicewherever needed. How does that sound?
That's what I've been discussing with Jens elsewhere on this list. However, I think what you're proposing is overly complex. All we really need is for a way of flagging a kobject (or kref) so the final put will be in user context. Then we can use storage within the kobject or device (or something else) for the purpose.
James
Quoted 8 lines · James Bottomley
Quoted 6 lines · Alan Stern
Could we perhaps make this safer and more general?
For instance, add to struct device a "pending puts" counter and a list header (both protected by a global spinlock), and have a kernel thread periodically check the list, doing
put_devicewherever needed. How does that sound?
Quoted 5 lines
That's what I've been discussing with Jens elsewhere on this list. However, I think what you're proposing is overly complex. All we really need is for a way of flagging a kobject (or kref) so the final put will be in user context. Then we can use storage within the kobject or device (or something else) for the purpose.
That's more or less what I was suggesting. The problems are: How do you know which put is the last? (Answer: you don't. So every put has to be done in process context.) And how do you flag the data structure and tell some process thread to do the put? (Answer: by putting the object on a list, as in my suggestion.)
Alan Stern
Quoted 4 lines · James Bottomley
Well, I can't solve the problem that it requires memory allocation from IRQ context to operate. Based on that, it's an unsafe interface. I'm going to put it inside SCSI for 2.6.16, since it's better than what we have now, but I don't think we can export it globally.
OK, this is what I'm proposing as the device model fix. What it does is thread context checking APIs throughout the device subsystem. SCSI can then use it simply via device_put_process_context(). Since we have to supply the kref_work; I'd plan to do that as an additional element in struct scsi_device.
This, by itself, won't solve the SCSI target problem, but I plan to fix that via a device model addition which would have target alloc waiting around for any deleted targets to disappear.
Since this is planned for post 2.6.16, we have plenty of time to argue about it.
James
drivers/base/core.c +3 -3
@@ -338,10 +338,10 @@ struct device * get_device(struct device* put_device - decrement reference count. * @dev: device in question. */ -void put_device (struct device * dev) +void put_device_process_context (struct device * dev,struct kref_work *work) {if (dev) -kobject_put (&dev->kobj); +kobject_put_process_context (&dev->kobj, work); }
@@ -445,7 +445,7 @@ EXPORT_SYMBOL_GPL(device_register);EXPORT_SYMBOL_GPL (device_del);EXPORT_SYMBOL_GPL (device_unregister);EXPORT_SYMBOL_GPL (get_device); -EXPORT_SYMBOL_GPL (put_device); +EXPORT_SYMBOL_GPL (put_device_process_context);EXPORT_SYMBOL_GPL (device_create_file);EXPORT_SYMBOL_GPL (device_remove_file);
include/linux/device.h +7 -1
@@ -396,7 +396,13 @@ extern int (*platform_notify_remove)(str* */ extern struct device *get_device (struct device * dev); -extern void put_device (struct device * dev); +extern void put_device_process_context (struct device * dev, +struct kref_work *work); +static inline void put_device (struct device *dev) +{ +put_device_process_context (dev,NULL ); +} +/* drivers/base/power.c */
include/linux/kobject.h +6 -1
@@ -76,7 +76,12 @@ extern int kobject_register(struct kobjeextern void kobject_unregister (struct kobject *);extern struct kobject *kobject_get (struct kobject *); -extern void kobject_put (struct kobject *); +extern void kobject_put_process_context (struct kobject *,struct kref_work *); + +static inline void kobject_put (struct kobject *kobj) +{ +kobject_put_process_context (kobj,NULL ); +}extern char *kobject_get_path (struct kobject *,gfp_t );
include/linux/kref.h +15 -1
@@ -18,15 +18,29 @@#ifdef __KERNEL__#include <linux/types.h> +#include <linux/workqueue.h> #include <asm/atomic.h> struct kref {atomic_t refcount; }; +struct kref_work { +struct work_struct work; +struct kref *kref; +void (*release)(struct kref *kref); +}; +void kref_init (struct kref *kref);void kref_get (struct kref *kref); -int kref_put (struct kref *kref,void (*release) (struct kref *kref)); +int kref_put_process_context (struct kref *kref, +void (*release) (struct kref *kref), +struct kref_work *work); +static inline int kref_put (struct kref *kref, +void (*release) (struct kref *kref)) +{ +return kref_put_process_context (kref, release,NULL ); +}#endif /* __KERNEL__ */ #endif /* _KREF_H_ */
lib/kobject.c +3 -3
@@ -372,10 +372,10 @@ static void kobject_release(struct kref* * Decrement the refcount, and if 0, call kobject_cleanup(). */ -void kobject_put (struct kobject * kobj) +void kobject_put_process_context (struct kobject * kobj,struct kref_work *work) {if (kobj) -kref_put (&kobj->kref, kobject_release); +kref_put_process_context (&kobj->kref, kobject_release, work); }
@@ -537,7 +537,7 @@ EXPORT_SYMBOL(kobject_init);EXPORT_SYMBOL (kobject_register);EXPORT_SYMBOL (kobject_unregister);EXPORT_SYMBOL (kobject_get); -EXPORT_SYMBOL (kobject_put); +EXPORT_SYMBOL (kobject_put_process_context);EXPORT_SYMBOL (kobject_add);EXPORT_SYMBOL (kobject_del);
lib/kref.c +26 -5
@@ -13,6 +13,7 @@#include <linux/kref.h> #include <linux/module.h> +#include <linux/hardirq.h> /** * kref_init - initialize object.
@@ -33,27 +34,47 @@ void kref_get(struct kref *kref)atomic_inc (&kref->refcount); } +static void kref_release_process_context (void *data) +{ +struct kref_work *work = data; + + work->release (work->kref); +} +/** -* kref_put - decrement refcount for object. +* kref_put_user - decrement refcount for object and put in user context * @kref: object. * @release: pointer to the function that will clean up the object when the * last reference to the object is released. * This pointer is required, and it is not acceptable to pass kfree * in as this function. +* @work: pointer to a kref_work used to take the release through user +* context (may be null) * -* Decrement the refcount, and if 0, call release(). +* Decrement the refcount, and if 0, call release(). If work is not null +* execute release via schedule_work if not in process context. * Return 1 if the object was removed, otherwise return 0. Beware, if this * function returns 0, you still can not count on the kref from remaining in * memory. Only use the return value if you want to see if the kref is now * gone, not present. */ -int kref_put (struct kref *kref,void (*release)(struct kref *kref)) +int kref_put_process_context (struct kref *kref, +void (*release)(struct kref *kref), +struct kref_work *work) {WARN_ON (release ==NULL );WARN_ON (release == (void (*)(struct kref *))kfree);if (atomic_dec_and_test (&kref->refcount)) { -release (kref); +if (!work || !in_interrupt ()) +release (kref); +else { +INIT_WORK (&work->work, kref_release_process_context, + work); +schedule_work (&work->work); + } + +return 1 ; }return 0 ;
@@ -61,4 +82,4 @@ int kref_put(struct kref *kref, void (*rEXPORT_SYMBOL (kref_init);EXPORT_SYMBOL (kref_get); -EXPORT_SYMBOL (kref_put); +EXPORT_SYMBOL (kref_put_process_context);
Quoted 12 lines · James Bottomley
Quoted 4 lines · James Bottomley
Well, I can't solve the problem that it requires memory allocation from IRQ context to operate. Based on that, it's an unsafe interface. I'm going to put it inside SCSI for 2.6.16, since it's better than what we have now, but I don't think we can export it globally.
OK, this is what I'm proposing as the device model fix. What it does is thread context checking APIs throughout the device subsystem. SCSI can then use it simply via
device_put_process_context(). Since we have to supply thekref_work; I'd plan to do that as an additional element in structscsi_device.
Quoted 6 lines
This, by itself, won't solve the SCSI target problem, but I plan to fix that via a device model addition which would have target alloc waiting around for any deleted targets to disappear.
Since this is planned for post 2.6.16, we have plenty of time to argue about it.
This is probably an idiotic question, but if there's something in the scsi release handler can't be called in non-process context, why can't scsi queue up the release processing via the work API itself, rather than having to have this additional code and complexity for everyone?
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
Quoted 1 line · Russell King
On Wed, Feb 15, 2006 at 08:56:00PM -0500, James Bottomley wrote:
[...]
Quoted 3 lines
Quoted 3 lines
OK, this is what I'm proposing as the device model fix. What it does is thread context checking APIs throughout the device subsystem. SCSI can then use it simply via
device_put_process_context().
[...]
Quoted 7 lines
Quoted 2 lines
Since this is planned for post 2.6.16, we have plenty of time to argue about it.
This is probably an idiotic question, but if there's something in the scsi release handler can't be called in non-process context, why can't scsi queue up the release processing via the work API itself, rather than having to have this additional code and complexity for everyone?
Moreover, why are SCSI release handlers called in non-process context in the first place? IMO the fix should be to make sure that SCSI release handlers are always called from process context --- by the respective layers which manage physical devices, i.e. one or more layers beneath SCSI core.
Signature · 3 lines
Stefan Richter -=====-=-==- --=- =---- http://arcgraph.de/sr/
Quoted 4 lines · Russell King
This is probably an idiotic question, but if there's something in the scsi release handler can't be called in non-process context, why can't scsi queue up the release processing via the work API itself, rather than having to have this additional code and complexity for everyone?
It's because, in order to get a guaranteed single allocation for the workqueue to execute in user context, I need to know when the release will be called. The only way to do that is to add the execute in process context directly to kref_put.
James
Quoted 10 lines · James Bottomley
Quoted 4 lines · Russell King
This is probably an idiotic question, but if there's something in the scsi release handler can't be called in non-process context, why can't scsi queue up the release processing via the work API itself, rather than having to have this additional code and complexity for everyone?
It's because, in order to get a guaranteed single allocation for the workqueue to execute in user context, I need to know when the release will be called. The only way to do that is to add the execute in process context directly to
kref_put.
Is there something in the driver model which would prevent something like this?
static void scsi_release_process(void *p)
{
struct my_work *work = p;
struct device *dev = work->dev;
/* destroy dev */
kfree(work);
}static void scsi_release(struct device *dev)
{
struct my_work *work;
work = kmalloc(sizeof(struct my_work), GFP_ATOMIC);
if (work) {
INIT_WORK(&work->work, scsi_release_process, work);
work->dev = dev;
schedule_work(&work->work);
} else {
printk(KERN_ERR ...);
}
}where scsi_release() is the function called by the device model on the last put of a scsi device.
I guess is more or less what you're trying to do invasively via the driver model.
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
Quoted 5 lines · Russell King
where
scsi_release()is the function called by the device model on the last put of a scsi device.I guess is more or less what you're trying to do invasively via the driver model.
Yes ... except I think more than just SCSI has the problem (and we actually have it in more than one release function) so it seems like a good candidate for a general abstraction.
James
Quoted 10 lines · James Bottomley
Quoted 5 lines · Russell King
where
scsi_release()is the function called by the device model on the last put of a scsi device.I guess is more or less what you're trying to do invasively via the driver model.
Yes ... except I think more than just SCSI has the problem (and we actually have it in more than one release function) so it seems like a good candidate for a general abstraction.
Maybe implementing it as a helper function would be the best and simplest solution?
static void scsi_release(struct device *dev)
{
schedule_release_process(dev, scsi_release_process);
}where schedule_release_process() contains more or less what I posted in the previous mailing.
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
Quoted 10 lines · Russell King
Maybe implementing it as a helper function would be the best and simplest solution?
static void
scsi_release(struct device *dev){ schedule_release_process(dev, scsi_release_process); }where
schedule_release_process()contains more or less what I posted in the previous mailing.
That's almost exactly the execute_in_process_context() API that began this discussion (and which Andi NAK'd). However, it could possibly be resurrected with the proviso that the caller has to feed in the workqueue memory. How would people feel about that?
James
Quoted 9 lines · James Bottomley
Quoted 8 lines · Russell King
Maybe implementing it as a helper function would be the best and simplest solution?
static void
scsi_release(struct device *dev){ schedule_release_process(dev, scsi_release_process); }
Quoted 7 lines
Quoted 2 lines
where
schedule_release_process()contains more or less what I posted in the previous mailing.That's almost exactly the
execute_in_process_context()API that began this discussion (and which Andi NAK'd). However, it could possibly be resurrected with the proviso that the caller has to feed in the workqueue memory. How would people feel about that?
That's what I suggested in the first place as well. I still think it's a good idea, fwiw :)
Signature · 1 line
Jens Axboe
Quoted 2 lines · Jens Axboe
That's what I suggested in the first place as well. I still think it's a good idea, fwiw :)
OK smarty pants ... some of us are a bit slower on the uptake. How about this then. It won't solve the target problem, but it will solve the device put.
James
[PATCH] add execute_in_process_context() API
We have several points in the SCSI stack (primarily for our device functions) where we need to guarantee process context, but (given the place where the last reference was released) we cannot guarantee this.
This API gets around the issue by executing the function directly if the caller has process context, but scheduling a workqueue to execute in process context if the caller doesn't have it.
include/linux/workqueue.h +8 -0
@@ -20,6 +20,12 @@struct timer_list timer; }; +struct execute_work { +struct work_struct work; +void (*fn)(void *); +void *data; +}; +#define __WORK_INITIALIZER (n, f, d) { \ .entry = { &(n).entry, &(n).entry }, \ .func = (f), \
@@ -74,6 +80,8 @@void cancel_rearming_delayed_work (struct work_struct *work);void cancel_rearming_delayed_workqueue (struct workqueue_struct *,struct work_struct *); +int execute_in_process_context (void (*fn)(void *),void *, +struct execute_work *);/* * Kill off a pending schedule_delayed_work(). Note that the work callback
kernel/workqueue.c +40 -0
@@ -27,6 +27,7 @@#include <linux/cpu.h> #include <linux/notifier.h> #include <linux/kthread.h> +#include <linux/hardirq.h> /* * The per-CPU workqueue (if single thread, we always use the first
@@ -476,6 +477,45 @@ }EXPORT_SYMBOL (cancel_rearming_delayed_work); +static void execute_in_process_context_work (void *data) +{ +void (*fn)(void *data); +struct execute_work *ew = data; + + fn = ew->fn; + data = ew->data; + +fn (data); +} + +/** +* execute_in_process_context - reliably execute the routine with user context +* @fn: the function to execute +* @data: data to pass to the function +* +* Executes the function immediately if process context is available, +* otherwise schedules the function for delayed execution. +* +* Returns: 0 - function was executed +* 1 - function was scheduled for execution +*/ +int execute_in_process_context (void (*fn)(void *data),void *data, +struct execute_work *ew) +{ +if (!in_interrupt ()) { +fn (data); +return 0 ; + } + +INIT_WORK (&ew->work, execute_in_process_context_work, ew); + ew->fn = fn; + ew->data = data; +schedule_work (&ew->work); + +return 1 ; +} +EXPORT_SYMBOL_GPL (execute_in_process_context); +int keventd_up (void ) {return keventd_wq !=NULL ;
Greg KH
Acked-by Greg Kroah-HartmaQuoted 11 lines · James Bottomley
Quoted 2 lines · Jens Axboe
That's what I suggested in the first place as well. I still think it's a good idea, fwiw :)
OK smarty pants ... some of us are a bit slower on the uptake. How about this then. It won't solve the target problem, but it will solve the device put.
James
[PATCH] add
execute_in_process_context()API
I like it, nice job.
thanks,
greg k-h
Quoted 8 lines
kernel/workqueue.c +8
-0+/** +* execute_in_process_context - reliably execute the routine with user context +* @fn: the function to execute +* @data: data to pass to the function +* +* Executes the function immediately if process context is available, +* otherwise schedules the function for delayed execution. +*
kernel/workqueue.c line 508
Quoted 10 lines
kernel/workqueue.c +10
-0+* Returns: 0 - function was executed +* 1 - function was scheduled for execution +*/ +int execute_in_process_context (void (*fn)(void *data),void *data, +struct execute_work *ew) +{ +if (!in_interrupt ()) { +fn (data); +return 0 ; + }
Is testing in_interrupt() really sufficient to make this work? I seem to remember that (at least) with CONFIG_PREEMPT disabled, there are contexts where it is not safe to sleep but where both in_interrupt() and in_atomic() still return 0.
- R.
Quoted 4 lines · Roland Dreier
Quoted 4 lines
kernel/workqueue.c +4
-0+int execute_in_process_context (void (*fn)(void *data),void *data, +struct execute_work *ew) +{ +if (!in_interrupt ()) {
Quoted 8 lines
kernel/workqueue.c line 508
Quoted 3 lines
kernel/workqueue.c +3
-0+fn (data); +return 0 ; + }Is testing
in_interrupt()really sufficient to make this work? I seem to remember that (at least) withCONFIG_PREEMPTdisabled, there are contexts where it is not safe to sleep but where bothin_interrupt()andin_atomic()still return 0.
That's correct -- in process context, with PREEMPT disabled and a spinlock held, it's unsafe to call this function. It works well for the SCSI usage (where it's called either in interrupt context or in user context with no spinlocks held), but it's not *always* safe.
I think this needs to be documented in the kerneldoc.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
kernel/workqueue.c line 489
Quoted 10 lines · James Bottomley
kernel/workqueue.c +10
-0+static void execute_in_process_context_work (void *data) +{ +void (*fn)(void *data); +struct execute_work *ew = data; + + fn = ew->fn; + data = ew->data; + +fn (data); +}
After removing kfree(), which was here in the initial implementation, this function became a thunk which does nothing useful - we can just stick fn and data directly into work_struct.
Quoted 17 lines
kernel/workqueue.c +17
-0+ +/** +* execute_in_process_context - reliably execute the routine with user context +* @fn: the function to execute +* @data: data to pass to the function +* +* Executes the function immediately if process context is available, +* otherwise schedules the function for delayed execution. +* +* Returns: 0 - function was executed +* 1 - function was scheduled for execution +*/ +int execute_in_process_context (void (*fn)(void *data),void *data, +struct execute_work *ew) +{ +if (!in_interrupt ()) { +fn (data);
kernel/workqueue.c line 516
Quoted 10 lines
kernel/workqueue.c +10
-0+return 0 ; + } + +INIT_WORK (&ew->work, execute_in_process_context_work, ew); + ew->fn = fn; + ew->data = data; +schedule_work (&ew->work); + +return 1 ; +}
Then this becomes:
int execute_in_process_context(void (*fn)(void *data), void *data,
struct work_struct *work)
{
if (!in_interrupt()) {
fn(data);
return 0;
}
INIT_WORK(work, fn, data);
schedule_work(work);
return 1;
}(and struct execute_work is no longer needed).
Quoted 3 lines · Sergey Vlasov
After removing
kfree(), which was here in the initial implementation, this function became a thunk which does nothing useful - we can just stick fn and data directly intowork_struct.
Yes, thanks ... although I think there's still value to wrappering work_struct (a bit like kref wrappers atomic_t).
James
Quoted 2 lines · James Bottomley
Yes, thanks ... although I think there's still value to wrappering
work_struct(a bit like kref wrappersatomic_t).
OK, so how about this?
James
[PATCH] add execute_in_process_context() API
We have several points in the SCSI stack (primarily for our device functions) where we need to guarantee process context, but (given the place where the last reference was released) we cannot guarantee this.
This API gets around the issue by executing the function directly if the caller has process context, but scheduling a workqueue to execute in process context if the caller doesn't have it.
include/linux/workqueue.h +6 -0
@@ -20,6 +20,10 @@struct timer_list timer; }; +struct execute_work { +struct work_struct work; +}; +#define __WORK_INITIALIZER (n, f, d) { \ .entry = { &(n).entry, &(n).entry }, \ .func = (f), \
@@ -74,6 +78,8 @@void cancel_rearming_delayed_work (struct work_struct *work);void cancel_rearming_delayed_workqueue (struct workqueue_struct *,struct work_struct *); +int execute_in_process_context (void (*fn)(void *),void *, +struct execute_work *);/* * Kill off a pending schedule_delayed_work(). Note that the work callback
kernel/workqueue.c +29 -0
@@ -27,6 +27,7 @@#include <linux/cpu.h> #include <linux/notifier.h> #include <linux/kthread.h> +#include <linux/hardirq.h> /* * The per-CPU workqueue (if single thread, we always use the first
@@ -476,6 +477,34 @@ }EXPORT_SYMBOL (cancel_rearming_delayed_work); +/** +* execute_in_process_context - reliably execute the routine with user context +* @fn: the function to execute +* @data: data to pass to the function +* @ew: guaranteed storage for the execute work structure (must +* be available when the work executes) +* +* Executes the function immediately if process context is available, +* otherwise schedules the function for delayed execution. +* +* Returns: 0 - function was executed +* 1 - function was scheduled for execution +*/ +int execute_in_process_context (void (*fn)(void *data),void *data, +struct execute_work *ew) +{ +if (!in_interrupt ()) { +fn (data); +return 0 ; + } + +INIT_WORK (&ew->work, fn, data); +schedule_work (&ew->work); + +return 1 ; +} +EXPORT_SYMBOL_GPL (execute_in_process_context); +int keventd_up (void ) {return keventd_wq !=NULL ;
Quoted 8 lines · James Bottomley
kernel/workqueue.c +8
-0+/** +* execute_in_process_context - reliably execute the routine with user context +* @fn: the function to execute +* @data: data to pass to the function +* +* Executes the function immediately if process context is available, +* otherwise schedules the function for delayed execution. +*
kernel/workqueue.c line 508
Quoted 10 lines
kernel/workqueue.c +10
-0+* Returns: 0 - function was executed +* 1 - function was scheduled for execution +*/ +int execute_in_process_context (void (*fn)(void *data),void *data, +struct execute_work *ew) +{ +if (!in_interrupt ()) { +fn (data); +return 0 ; + }
The test should be in_atomic(), not in_interrupt().
Alan Stern
Quoted 1 line · Alan Stern
The test should be
in_atomic(), notin_interrupt().
There's a long prior discussion of why it has to be in_interrupt()
James
PATCH 1/1 x86: fix oprofile kernel callgraph regression
In reply to Andrew MortonFix x86 oprofile regression introduced by:
commit c34d1b4d165c67b966bca4aba026443d7ff161eb
[PATCH] mm: kill check_user_page_readable
That commit reorganized tests for the userspace stack walking moving all those tests into dump_backtrace(), however, dump_backtrace() was used for both userspace and kernel stalk walking. The result is typically no recorded callgraph information for kernel samples.
Revive the original function as dump_kernel_backtrace() and rename the other to dump_user_backtrace() to avoid future confusion.
--- backtrace.c | 19 ++++++++++++++++--- 1 files changed, 16 insertions(+), 3 deletions(-)
arch/i386/oprofile/backtrace.c +16 -3
@@ -20,7 +20,20 @@ struct frame_head { } __attribute__((packed));static struct frame_head * -dump_backtrace (struct frame_head * head) +dump_kernel_backtrace (struct frame_head * head) +{ +oprofile_add_trace (head->ret); + +/* frame pointers should strictly progress back up the stack +* (towards higher addresses) */ +if (head >= head->ebp) +return NULL ; + +return head->ebp; +} + +static struct frame_head * +dump_user_backtrace (struct frame_head * head) {struct frame_head bufhead[2 ];
@@ -105,10 +118,10 @@ x86_backtrace(struct pt_regs * const regif (!user_mode_vm (regs)) {while (depth-- &&valid_kernel_stack (head, regs)) - head =dump_backtrace (head); + head =dump_kernel_backtrace (head);return ; }while (depth-- && head) - head =dump_backtrace (head); + head =dump_user_backtrace (head); }
Re: [PATCH] x86: fix oprofile kernel callgraph regression
Quoted 9 lines · Gerald Britton
Fix x86 oprofile regression introduced by:
commitc34d1b4d165c67b966bca4aba026443d7ff161eb
[PATCH] mm: killcheck_user_page_readableThat commit reorganized tests for the userspace stack walking moving all those tests into
dump_backtrace(), however,dump_backtrace()was used for both userspace and kernel stalk walking. The result is typically no recorded callgraph information for kernel samples.
Quoted 4 lines
Revive the original function as
dump_kernel_backtrace()and rename the other todump_user_backtrace()to avoid future confusion.Signed-off-by Gerald Britton <[email protected]>
Apology-from: Hugh Dickins <[email protected]>
Quoted 2 lines · Andrew Morton
We still have some serious bugs, several of which are in 2.6.15 as well:
[...]
Quoted 4 lines
- Helge Hafting reports a usb printer regression - I don't know if that's still live?
I tried printing four pages of graphichs with 2.6.16-rc3-mm1 and it worked fine. When I had the problem I couldn't even print three, I had to print the 10 pages I needed one by one.
So I believe the situation has improved.
Helge Hafting
Quoted 5 lines
We still have some serious bugs, several of which are in 2.6.15 as well:
[...]
- "Ben Castricum" <[email protected]> reports that ppp has started exhibiting mysterious failures (again).
I found the time to do some more testing, this time with the latest 2.6.16-rc4 from git and still pppd version 2.4.1.
The problem was very easy to reproduce, within 10 minutes I appeared again. I could narrow the problem down to not being able to _send_ traffic. Ifconfig -a and tcpdump showed traffic coming in, but not going out. I tried stracing the relevant programs (I use pptp to connect to the dsl modem)
root@gateway:~# ps -ef | grep pp root 870 1 0 16:47 ? 00:00:00 /usr/sbin/upnpd ppp0 eth1 root 329 1 0 16:45 ? 00:00:00 /usr/sbin/pptp pptp: call manager for 10.0.0.138 root 323 322 0 16:45 ? 00:00:14 /usr/sbin/pptp pptp: GRE-to-PPP gateway on /dev/ptmx root 322 1 0 16:45 ? 00:00:00 /usr/sbin/pppd call adsl root 3156 2941 0 17:15 pts/2 00:00:00 grep pp
root@gateway:~# strace -p 322 select(4, [0 3], NULL, [0 3], NULL <unfinished ...>
(nothing happening there)
root@gateway:~# strace -p 323
write(4, " \201\210\v\0\0\0\0\0\2\320X", 12) = 12
select(5, [0 4], NULL, NULL, NULL) = 1 (in [4])
read(4, "E\0\0`\36P\0\0@/G\225\n\0\0\212\n\0\0\0010\1\210\v\0@\0"..., 8260) = 96
write(0, "\377\3\0!E\0\0< \211@\0(\6\27\336\310\256\260\215\325T"..., 64) = 64
select(5, [0 4], NULL, NULL, {0, 500000}) = 1 (in [4], left {0, 488000})
read(4, "E\0\0T\36Q\0\0@/G\240\n\0\0\212\n\0\0\0010\1\210\v\000"..., 8260) = 84
write(0, "\377\3\0!E\0\0000_E@\0w\6\320rRH\340\256\325T\313\304\20"..., 52) = 52
select(5, [0 4], NULL, NULL, {0, 0}) = 0 (Timeout)
write(4, " \201\210\v\0\0\0\0\0\2\320Z", 12) = 12
select(5, [0 4], NULL, NULL, NULL) = 1 (in [4])
read(4, "E\0\0T\36R\0\0@/G\237\n\0\0\212\n\0\0\0010\1\210\v\000"..., 8260) = 84
write(0, "\377\3\0!E\0\0000_F@\0w\6\320qRH\340\256\325T\313\304\20"..., 52) = 52
select(5, [0 4], NULL, NULL, {0, 500000}) = 1 (in [4], left {0, 472000})
read(4, "E\0\0T\36S\0\0@/G\236\n\0\0\212\n\0\0\0010\1\210\v\000"..., 8260) = 84
write(0, "\377\3\0!E\0\0000\21\223@\0q\6\205\\P\313\200\364\325T"..., 52) = 52
select(5, [0 4], NULL, NULL, {0, 0}) = 0 (Timeout)
write(4, " \201\210\v\0\0\0\0\0\2\320\\", 12) = 12
select(5, [0 4], NULL, NULL, NULL) = 1 (in [4])
read(4, "E\0\0T\36T\0\0@/G\235\n\0\0\212\n\0\0\0010\1\210\v\000"..., 8260) = 84
write(0, "\377\3\0!E\0\0000C\2@\0h\6\17\233\311\307UJ\325T\313\304"..., 52) = 52
select(5, [0 4], NULL, NULL, {0, 500000}) = 1 (in [4], left {0, 496000})
read(4, "E\0\0`\36U\0\0@/G\220\n\0\0\212\n\0\0\0010\1\210\v\0@\0"..., 8260) = 96
write(0, "\377\3\0!E\0\0<0e@\0003\6\4T\303\200\256i\325T\313\304"..., 64) = 64
select(5, [0 4], NULL, NULL, {0, 0}) = 0 (Timeout)
write(4, " \201\210\v\0\0\0\0\0\2\320^", 12) = 12
select(5, [0 4], NULL, NULL, NULL) = 1 (in [4])
read(4, "E\0\0d\36V\0\0@/G\213\n\0\0\212\n\0\0\0010\1\210\v\0D\0"..., 8260) = 100
write(0, "\377\3\0!E\0\0@:S\0\0003\6\203Y\311\32_\330\325T\313\304"..., 68) = 68
select(5, [0 4], NULL, NULL, {0, 500000}) = 1 (in [4], left {0, 484000})
read(4, "E\0\0`\36W\0\0@/G\216\n\0\0\212\n\0\0\0010\1\210\v\0@\0"..., 8260) = 96
write(0, "\377\3\0!E\0\0<\275\240@\0%\6\24\355\310\320\31E\325T\313"..., 64) = 64
select(5, [0 4], NULL, NULL, {0, 0}) = 0 (Timeout)
write(4, " \201\210\v\0\0\0\0\0\2\320`", 12) = 12
select(5, [0 4], NULL, NULL, NULL) = 1 (in [4])
read(4, "E\0\0d\36X\0\0@/G\211\n\0\0\212\n\0\0\0010\1\210\v\0D\0"..., 8260) = 100
write(0, "\377\3\0!E\0\0@a\264\0\0003\6\250\345\311\374\22\t\325"..., 68) = 68
select(5, [0 4], NULL, NULL, {0, 500000}) = 1 (in [4], left {0, 496000})
read(4, "E\0\0d\36Y\0\0@/G\210\n\0\0\212\n\0\0\0010\1\210\v\0D\0"..., 8260) = 100
write(0, "\377\3\0!E\0\0@j\217\0\0003\6\272\317\310\350\370W\325"..., 68) = 68
select(5, [0 4], NULL, NULL, {0, 0}) = 0 (Timeout)
write(4, " \201\210\v\0\0\0\0\0\2\320b", 12) = 12
select(5, [0 4], NULL, NULL, NULL) = 1 (in [4])
read(4, "E\0\0T\36Z\0\0@/G\227\n\0\0\212\n\0\0\0010\1\210\v\000"..., 8260) = 84
write(0, "\377\3\0!E\0\0000\26\217@\0p\6\375o\310\251\215\6\325T"..., 52) = 52
select(5, [0 4], NULL, NULL, {0, 500000}) = 1 (in [4], left {0, 440000})
read(4, "E\0\0T\36[\0\0@/G\226\n\0\0\212\n\0\0\0010\1\210\v\000"..., 8260) = 84
write(0, "\377\3\0!E\0\0000\3672@\0o\6[-\310\264O\232\325T\313\304"..., 52) = 52
select(5, [0 4], NULL, NULL, {0, 0}) = 0 (Timeout)
write(4, " \201\210\v\0\0\0\0\0\2\320d", 12) = 12
select(5, [0 4], NULL, NULL, NULL <unfinished ...>(and so on...)
root@gateway:~# strace -p 329 select(7, [3 4 6], [], NULL, NULL <unfinished ...>
nothing hapening here either.
checking the iptables setup (I flushed the rules before I started with troubleshooting):
root@gateway:~# iptables-save # Generated by iptables-save v1.2.6a on Wed Feb 22 17:10:44 2006 *filter :INPUT ACCEPT [6204:440626] :FORWARD ACCEPT [8:284] :OUTPUT ACCEPT [18978:2854072] COMMIT # Completed on Wed Feb 22 17:10:44 2006 # Generated by iptables-save v1.2.6a on Wed Feb 22 17:10:44 2006 *nat :PREROUTING ACCEPT [44153:2316103] :POSTROUTING ACCEPT [805:50699] :OUTPUT ACCEPT [2308:153409] COMMIT # Completed on Wed Feb 22 17:10:44 2006
root@gateway:~# iptables-save # Generated by iptables-save v1.2.6a on Wed Feb 22 17:10:48 2006 *filter :INPUT ACCEPT [6721:478137] :FORWARD ACCEPT [8:284] :OUTPUT ACCEPT [20528:3083677] COMMIT # Completed on Wed Feb 22 17:10:48 2006 # Generated by iptables-save v1.2.6a on Wed Feb 22 17:10:48 2006 *nat :PREROUTING ACCEPT [44241:2320941] :POSTROUTING ACCEPT [806:50777] :OUTPUT ACCEPT [2309:153487] COMMIT # Completed on Wed Feb 22 17:10:48 2006
Does this help anything?
Kind regards,
Ben
Quoted 1 line · Linus Torvalds
The most user-visible one (eventually) is the
unshare()system call, which glibc wanted. Along with some fixes forfstatat()(use the proper 64-bit interfaces, not the "newer old" one).
This breaks compilation on 3 archs compared to -rc2:
- mips: broke
AR arch/mips/lib-32/lib.a
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1 arch/mips/kernel/built-in.o(.text+0x9820): In function `einval':
/usr/src/ctest/rc/kernel/arch/mips/kernel/scall32-o32.S: undefined reference to `sys_newfstatat' make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [cdbuilddir] Error 2
Details: http://l4x.org/k/?d=10888
- sparc: broke
SYSMAP System.map
SYSMAP .tmp_System.map
HOSTCC arch/sparc/boot/btfixupprep
BTFIX arch/sparc/boot/btfix.S
AS arch/sparc/boot/btfix.o
LD arch/sparc/boot/image arch/sparc/kernel/built-in.o(.data+0x794): In function `sys_call_table':
: undefined reference to `sys_newfstatat'
make[2]: *** [arch/sparc/boot/image] Error 1
make[1]: *** [image] Error 2
make: *** [cdbuilddir] Error 2
Details: http://l4x.org/k/?d=10897
- sparc64: broke
AR arch/sparc64/lib/lib.a
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1 arch/sparc64/kernel/head.o(.text+0xe78): In function `sys_call_table':
/usr/src/ctest/rc/kernel/arch/sparc64/kernel/head.S: undefined reference to `sys_newfstatat' make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [cdbuilddir] Error 2
Details: http://l4x.org/k/?d=10898
Jan
Hi Jan
Quoted 15 lines · On Mon, 13 Feb 2006 09:46:56 +0100 Jan Dittmer <[email protected]> wrote:
Quoted 3 lines · Linus Torvalds
The most user-visible one (eventually) is the
unshare()system call, which glibc wanted. Along with some fixes forfstatat()(use the proper 64-bit interfaces, not the "newer old" one).This breaks compilation on 3 archs compared to -rc2:
- mips: broke
AR arch/mips/lib-32/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1
Quoted 7 lines
arch/mips/kernel/built-in.o(.text+0x9820): In function `einval':
/usr/src/ctest/rc/kernel/arch/mips/kernel/scall32-o32.S: undefined reference to `sys_newfstatat' make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [cdbuilddir] Error 2Details: http://l4x.org/k/?d=10888
MIPS 32bit machines need fstatat64 support.
Yoichi
arch/mips/kernel/scall32-o32.S +1 -1
@@ -623,7 +623,7 @@ einval: li v0, -EINVAL sys sys_mknodat 4 /* 4290 */ sys sys_fchownat 5 sys sys_futimesat 3 - sys sys_newfstatat 4 + sys sys_fstatat64 4 sys sys_unlinkat 3 sys sys_renameat 4 /* 4295 */ sys sys_linkat 4
Quoted 6 lines · Jan Dittmer
This breaks compilation on 3 archs compared to -rc2:
- mips: broke
- sparc: broke
- sparc64: broke
Should be ok in -git now, pls verify.
Linus
Quoted 12 lines · Linus Torvalds
Quoted 5 lines · Jan Dittmer
This breaks compilation on 3 archs compared to -rc2:
- mips: broke
- sparc: broke
- sparc64: brokeShould be ok in -git now, pls verify.
- mips: fixed
Details: http://l4x.org/k/?d=10915
- sparc: fixed
Details: http://l4x.org/k/?d=10932
- sparc64: fixed
Details: http://l4x.org/k/?d=10933
Good work,
Jan
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 20 lines · Avuton Olrich
Quoted 3 lines · Linus Torvalds
Ok,
it is out there (or in the process of getting mirrored out), so go wild.Hello, I appear to be getting the same issue I had back here:
http://lkml.org/lkml/2006/2/1/121A fix appeared a few messages later:
http://lkml.org/lkml/2006/2/1/129
http://lkml.org/lkml/2006/2/1/131I'm obviously unsure if these were correct fixes or what but they did fix it, and they were or are in -mm afaik.
I am not _sure_ this is the same bug, but the panic messages rings a bell (sorry, I already deleted the old pictures as it appeared to be taken care of in -mm).
Quoted 9 lines
In the case that it's not the same issue here's a new snapshot of the kernel panic:
http://68.111.224.150:8080/~sbh/P1010029.JPG
..and the config:
http://68.111.224.150:8080/~sbh/micromachine.configIf an essential part of the panic is missing please let me know and I will try to remember how I got it shrunk down better last time.
That looks like a different cpufreq bug. Unfortunately the critical first few lines have scrolled away. Please boot with `vga=extended' so we get to see them.
Quoted 3 lines · Andrew Morton
That looks like a different cpufreq bug. Unfortunately the critical first few lines have scrolled away. Please boot with `vga=extended' so we get to see them.
Just as a suggestion, why don't we print oopsen out in the opposite direction so the critical information is in the last few lines and the stacktrace in reverse, or have that as a bootparam option oops=reverse .
Cheers,
Con
Quoted 8 lines · Con Kolivas
Quoted 3 lines · Andrew Morton
That looks like a different cpufreq bug. Unfortunately the critical first few lines have scrolled away. Please boot with `vga=extended' so we get to see them.
Just as a suggestion, why don't we print oopsen out in the opposite direction so the critical information is in the last few lines and the stacktrace in reverse, or have that as a bootparam option oops=reverse .
x86-64 has a one line "executive summary" with the RIP etc. at the end to solve that problem. Might be a good idea for i386 too.
-Andi
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Avuton Olrich
I should have realized that would happen, hopefully here's a better
one. Please let me know anything I can do to help.
Thanks. Yes, it does look like the same bug.
Quoted 9 lines · Andrew Morton
Quoted 5 lines · Avuton Olrich
I should have realized that would happen, hopefully here's a better
one. Please let me know anything I can do to help.Thanks. Yes, it does look like the same bug.
argh. The fix for this oops is still languishing in David's tree.
arch/i386/kernel/timers/timer_tsc.c +5 -0
@@ -272,6 +272,10 @@ time_cpufreq_notifier(struct notifier_blif (val !=CPUFREQ_RESUMECHANGE )write_seqlock_irq (&xtime_lock);if (!ref_freq) { +if (!freq->old){ + ref_freq = freq->new; + goto end; + } ref_freq = freq->old; loops_per_jiffy_ref = cpu_data[freq->cpu].loops_per_jiffy;#ifndef CONFIG_SMP
@@ -297,6 +301,7 @@ time_cpufreq_notifier(struct notifier_bl#endif } +end:if (val !=CPUFREQ_RESUMECHANGE )write_sequnlock_irq (&xtime_lock);
Quoted 4 lines · Andrew Morton
Quoted 3 lines · Andrew Morton
Quoted 1 line · Avuton Olrich
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
I should have realized that would happen, hopefully here's a better
one. Please let me know anything I can do to help.Thanks. Yes, it does look like the same bug.
argh. The fix for this oops is still languishing in David's tree.
I was waiting for it to turn up in an -mm release first to be sure everything was ok.
If you're ok with it going as is, Linus, please pull from master.kernel.org:/pub/scm/linux/kernel/git/davej/cpufreq.git/ to get the changesets below.
Dave
commit 7d5e350fab47f1273bc8b52d5f133ed6e4baeb7f
Author: Dave Jones <[email protected]> Date: Thu Feb 2 17:03:42 2006 -0500
[CPUFREQ] Whitespace/CodingStyle cleanups
commit a85f7bd310dbc9010309bfe70b6b02432a11ef59
Author: Thomas Renninger <[email protected]> Date: Wed Feb 1 11:36:04 2006 +0100
[CPUFREQ] Check whether driver init did not initialize current freq
Check whether driver init did not initialize current freq
commit 9d2725bb815d915fc6c8531097d9e71b579a8763
Author: Thomas Renninger <[email protected]> Date: Wed Feb 1 11:38:37 2006 +0100
[CPUFREQ] Check for not initialized freq on cpufreq changes
Test for old_freq equals 0 to insure not to divide by 0:
______________________________________________
Check for not initialized freq on cpufreq changes
commit e4472cb3706ceea42797ae1dc79d624026986694
Author: Dave Jones <[email protected]> Date: Tue Jan 31 15:53:55 2006 -0800
[CPUFREQ] cpufreq_notify_transition cleanup.
Introduce caching of cpufreq_cpu_data[freqs->cpu], which allows us to make the function a lot more readable, and as a nice side-effect, it now fits in < 80 column displays again.
Quoted 5 lines · Dave Jones
Quoted 2 lines
argh. The fix for this oops is still languishing in David's tree.
I was waiting for it to turn up in an -mm release first to be sure everything was ok.
If we're at -rc<late> and we have a fix in hand and we know we will want that fix in 2.6.x, I don't think there's a lot of point in hanging around - slam it in asap, give it the most exposure possible.
2.6.16-rc3: more regressions
In reply to Linus TorvaldsI have some regressions [1] on my list that weren't metioned by Andrew:
Subject : Xorg freezes 2.6.16-rc1
References : http://lkml.org/lkml/2006/1/26/97
Submitter : Mauro Tassinari <[email protected]>
Status : unknown
Subject : 2.6.16rc1-git4 slab corruption
References : http://lkml.org/lkml/2006/1/31/164
Submitter : Dave Jones <[email protected]>
Status : unknown
Subject : psmouse starts losing sync in 2.6.16-rc2
References : http://lkml.org/lkml/2006/2/5/50
Submitter : Meelis Roos <[email protected]>
Status : unknown
Subject : OCFS2 Filesystem inconsistency across nodes
References : http://lkml.org/lkml/2006/2/10/14
Submitter : Claudio Martins <[email protected]>
Status : unknown
cu
Adrian
[1] "regression" defined as "bug was not present in 2.6.15"
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: 2.6.16-rc3: more regressions
Quoted 4 lines · Adrian Bunk
Subject : 2.6.16rc1-git4 slab corruption
References : http://lkml.org/lkml/2006/1/31/164
Submitter : Dave Jones <[email protected]>
Status : unknown
Haven't seen any instances of this for a few days now with latest -git's.
Dave
Re: 2.6.16-rc3: more regressions
In reply to Adrian BunkQuoted 5 lines · Adrian Bunk
Subject : psmouse starts losing sync in 2.6.16-rc2
References : http://lkml.org/lkml/2006/2/5/50
Submitter : Meelis Roos <[email protected]>
Status : unknown
Working on various manifestations of this one. At worst we will have to disable resync by default before 2.6.16 final is out and continue in 2.6.17 cycle.
--
Dmitry
Re: 2.6.16-rc3: more regressions
In reply to Adrian BunkQuoted 7 lines · Adrian Bunk
I have some regressions [1] on my list that weren't metioned by Andrew:
Subject : Xorg freezes 2.6.16-rc1
References : http://lkml.org/lkml/2006/1/26/97
Submitter : Mauro Tassinari <[email protected]>
Status : unknown
For this one, it would be interesting to see more info about the working setup. Notably
- what modules are loaded by the time X is running
- any differences in 'dmesg' output from 2.6.15 to 16-rc1 (PCI allocation issues should show up there)
I don't see any real differences in the radeonfb driver, for example (there's some trivial cleanup, including things like speeling fixums, but nothing that looks remotely likely).
Of course, in a perfect world, we'd have serial or network console output.. X crashes are nastier than most, if only because the console is mostly gone.
Linus
Re: 2.6.16-rc3: more regressions
Quoted 8 lines · Linus Torvalds
Quoted 4 lines
Subject : Xorg freezes 2.6.16-rc1
References : http://lkml.org/lkml/2006/1/26/97
Submitter : Mauro Tassinari <[email protected]>
Status : unknownFor this one, it would be interesting to see more info about the working setup. Notably
Quoted 7 lines
- what modules are loaded by the time X is running
- any differences in 'dmesg' output from 2.6.15 to 16-rc1 (PCI allocation issues should show up there)Of course, in a perfect world, we'd have serial or network console output.. X crashes are nastier than most, if only because the console is mostly gone.
I think this is the Radeon DRM bug I hit. (rc1 had a big drm update iirc)
Unless I patch with this..
drivers/char/drm/drm_pciids.h 2006-02-09 19:26:56.000000000 -0500 renamed from drivers/char/drm/drm_pciids.h~ 2006-02-09 19:26:06.000000000 -0500 +0 -1
@@ -85,7 +85,6 @@ {0x1002, 0x5969, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100}, \ {0x1002, 0x596A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \ {0x1002, 0x596B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \ - {0x1002, 0x5b60, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \ {0x1002, 0x5c61, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280|CHIP_IS_MOBILITY}, \ {0x1002, 0x5c62, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \ {0x1002, 0x5c63, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280|CHIP_IS_MOBILITY}, \
I get a machine check exception, triple fault, or NMI watchdog lockup.
Dave
Re: 2.6.16-rc3: more regressions
Quoted 2 lines · Dave Jones
I think this is the Radeon DRM bug I hit. (rc1 had a big drm update iirc)
Ahh..
drivers/char/drm/drm_pciids.h 2006-02-09 19:26:56.000000000 -0500 line 88
Quoted 10 lines
Unless I patch with this..
drivers/char/drm/drm_pciids.h 2006-02-09 19:26:56.000000000 -0500 renamed from drivers/char/drm/drm_pciids.h~ 2006-02-09 19:26:06.000000000 -0500 +0
-1@@ -85,7 +85,6 @@ {0x1002, 0x5969, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100}, \ {0x1002, 0x596A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \ {0x1002, 0x596B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \ - {0x1002, 0x5b60, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \ {0x1002, 0x5c61, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280|CHIP_IS_MOBILITY}, \
DaveA, I'll apply this for now. Comments?
Linus
Re: 2.6.16-rc3: more regressions
Quoted 2 lines · Linus Torvalds
DaveA, I'll apply this for now. Comments?
Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly suppresses the ID entirely, but the string seems to match the one that Dave Jones reports) may be unrelated.
DaveJ (or Mauro): since you can test this, can you test having that ID there but _without_ the other changes to drm in -rc1?
Ie was it the addition of that particular ID, or are the other radeon driver changes (which haven't had as much testing) perhaps the culprit?
I realize that without the ID, that card would never have been tested anyway, but the point being that plain 2.6.15 with _just_ that ID added has at least gotten more testing on other (similar) chips. So before I revert that particular ID, it would be nice to know that it was broken even with the previous radeon driver state.
Linus
Re: 2.6.16-rc3: more regressions
Quoted 13 lines · Linus Torvalds
Quoted 2 lines · Linus Torvalds
DaveA, I'll apply this for now. Comments?
Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly suppresses the ID entirely, but the string seems to match the one that Dave Jones reports) may be unrelated.
DaveJ (or Mauro): since you can test this, can you test having that ID there but _without_ the other changes to drm in -rc1?
Quoted 8 lines
Ie was it the addition of that particular ID, or are the other radeon driver changes (which haven't had as much testing) perhaps the culprit?
I realize that without the ID, that card would never have been tested anyway, but the point being that plain 2.6.15 with _just_ that ID added has at least gotten more testing on other (similar) chips. So before I revert that particular ID, it would be nice to know that it was broken even with the previous radeon driver state.
r300 is unlike the other chips though.
Adding that ID on its own doesn't make any sense, as the rest of the radeon driver won't have a clue how to drive the new hardware.
Dave
Re: 2.6.16-rc3: more regressions
Quoted 4 lines · Dave Jones
r300 is unlike the other chips though.
Adding that ID on its own doesn't make any sense, as the rest of the radeon driver won't have a clue how to drive the new hardware.
There were RV350 entries in the drm_pciids file before 2.6.15 as far as I can tell..
Linus
Re: 2.6.16-rc3: more regressions
Quoted 10 lines · Linus Torvalds
Quoted 4 lines · Dave Jones
r300 is unlike the other chips though.
Adding that ID on its own doesn't make any sense, as the rest of the radeon driver won't have a clue how to drive the new hardware.There were RV350 entries in the
drm_pciidsfile before 2.6.15 as far as I can tell..
The entry Dave's patch removes is the only RV350 entry for an RV370.
Quoted 1 line
Linus
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: 2.6.16-rc3: more regressions
In reply to Linus TorvaldsQuoted 9 lines · Linus Torvalds
Quoted 2 lines · Linus Torvalds
DaveA, I'll apply this for now. Comments?
Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly suppresses the ID entirely, but the string seems to match the one that Dave Jones reports) may be unrelated.
Dave's patch removes the entry for the card with the 0x5b60.
According to his bug report, Mauro has a Radeon X300SE that should have the 0x5b70 according to pci.ids from pciutils and that doesn't seem to be claimed by the DRM driver (and the dmesg from the bug report confirms that the radeon DRM driver didn't claim to be responsible for this card).
Quoted 11 lines
DaveJ (or Mauro): since you can test this, can you test having that ID there but _without_ the other changes to drm in -rc1?
Ie was it the addition of that particular ID, or are the other radeon driver changes (which haven't had as much testing) perhaps the culprit?
I realize that without the ID, that card would never have been tested anyway, but the point being that plain 2.6.15 with _just_ that ID added has at least gotten more testing on other (similar) chips. So before I revert that particular ID, it would be nice to know that it was broken even with the previous radeon driver state.
The ID removed by Dave's patch is the only ID listed for an RV370 chips (the other RV370's aren't listed in the radeon DRM driver).
I suspect Dave and Mauro having unrelated problems.
Quoted 1 line
Linus
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: 2.6.16-rc3: more regressions
Quoted 11 lines · Adrian Bunk
Quoted 9 lines · Linus Torvalds
Quoted 2 lines · Linus Torvalds
DaveA, I'll apply this for now. Comments?
Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly suppresses the ID entirely, but the string seems to match the one that Dave Jones reports) may be unrelated.
Quoted 6 lines
Dave's patch removes the entry for the card with the
0x5b60. According to his bug report, Mauro has a Radeon X300SE that should have the0x5b70according to pci.ids from pciutils and that doesn't seem to be claimed by the DRM driver (and the dmesg from the bug report confirms that the radeon DRM driver didn't claim to be responsible for this card).
The X300SE (mine at least) is a dual head card, with a 0x5b60 _and_ a 0x5b70
Dave
Re: 2.6.16-rc3: more regressions
Quoted 12 lines · Dave Jones
Quoted 11 lines · Adrian Bunk
Quoted 9 lines · Linus Torvalds
Quoted 2 lines · Linus Torvalds
DaveA, I'll apply this for now. Comments?
Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly suppresses the ID entirely, but the string seems to match the one that Dave Jones reports) may be unrelated.
Quoted 8 lines
Quoted 6 lines
Dave's patch removes the entry for the card with the
0x5b60. According to his bug report, Mauro has a Radeon X300SE that should have the0x5b70according to pci.ids from pciutils and that doesn't seem to be claimed by the DRM driver (and the dmesg from the bug report confirms that the radeon DRM driver didn't claim to be responsible for this card).The X300SE (mine at least) is a dual head card, with a
0x5b60_and_ a0x5b70
OK, this might explain it.
Then your patch could indeed fix Mauro's problem.
Quoted 1 line
Dave
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: 2.6.16-rc3: more regressions
In reply to Dave JonesQuoted 19 lines · Dave Jones
Quoted 11 lines · Adrian Bunk
Quoted 9 lines · Linus Torvalds
Quoted 2 lines · Linus Torvalds
DaveA, I'll apply this for now. Comments?
Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly suppresses the ID entirely, but the string seems to match the one that Dave Jones reports) may be unrelated.
Quoted 6 lines
Dave's patch removes the entry for the card with the
0x5b60. According to his bug report, Mauro has a Radeon X300SE that should have the0x5b70according to pci.ids from pciutils and that doesn't seem to be claimed by the DRM driver (and the dmesg from the bug report confirms that the radeon DRM driver didn't claim to be responsible for this card).
Quoted 4 lines
The X300SE (mine at least) is a dual head card, with a
0x5b60_and_ a0x5b70Dave
The secondary id is just a place holder for the windows driver so dualhead will work on windows 2000. Neither the drm nor the xorg DDX uses the secondary id.
Alex
Re: 2.6.16-rc3: more regressions
In reply to Adrian BunkQuoted 5 lines · Adrian Bunk
Dave's patch removes the entry for the card with the
0x5b60.According to his bug report, Mauro has a Radeon X300SE that should have the
0x5b70according to pci.ids from pciutils
No. Look closer:
04:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc. Extreme AX300SE-X
That's the 5b60 chip too (yeah, the lspci doesn't show numbers when it has an ascii string, but in this case the ascii string happily has at least that part of the number in it: ".. RV370 5B60 ..", where the 5B60 is just the PCI ID number).
So it _is_ the same chip.
I just worry whether (a) the other added PCI ID's are any good for that core and (b) whether the bug was really introduced with some of the other changes. I admit that (b) is pretty unlikely, but it would be good to test.
Quoted 3 lines
and that doesn't seem to be claimed by the DRM driver (and the dmesg from the bug report confirms that the radeon DRM driver didn't claim to be responsible for this card).
Sadly, that module loading is done by X. So the bootup dmesg stuff wouldn't have had the message.
It might be interesting to see if the hang can be reproduced without starting X at all, by just going a "modprobe radeon" or something. Unlikely, though - while loading the drm modules does _some_ things to the card, it's usually only when X actually starts sending commands to them that things really go downhill..
Linus
Re: 2.6.16-rc3: more regressions
Quoted 6 lines · Linus Torvalds
...
I just worry whether (a) the other added PCI ID's are any good for that core and (b) whether the bug was really introduced with some of the other changes. I admit that (b) is pretty unlikely, but it would be good to test.
...
The one thing I have not yet been proven wrong for is that this PCI id is the only one we have in this driver for an RV370.
Perhaps someone will be able to prove this wrong, too, ;-) but otherwise it would be a good explanation why exactly this one is causing problems.
Quoted 1 line
Linus
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: 2.6.16-rc3: more regressions
Quoted 3 lines · Adrian Bunk
The one thing I have not yet been proven wrong for is that this PCI id is the only one we have in this driver for an RV370.
It definitely is an RV370, you're right in that. I'm too lazy to actually see if the other entries that claim to be RV350's really are RV350's.
So I decided to just remove it. Even if there is some other bug that could make it work again, we can always just re-add it at that time. In the meantime, this should fix both DaveJs and Mauros problems, and is clearly no worse than 2.6.15 (which also didn't recognize the card), so...
Linus
Re: 2.6.16-rc3: more regressions
Quoted 5 lines · Linus Torvalds
So I decided to just remove it. Even if there is some other bug that could make it work again, we can always just re-add it at that time. In the meantime, this should fix both DaveJs and Mauros problems, and is clearly no worse than 2.6.15 (which also didn't recognize the card), so...
Btw, on a totally unrelated tangent, I just wanted to say how much I appreciate people looking for regressions like this, and trying to track them. Andrew does it, but this is absolutely something that should be possible to get more people to do, and it would be a huge boon for kernel development if we had a more aggressive regression tracking system.
Right now it all very easily gets lost in the noise - either on the mailing list or even on bugzilla (where following up on regressions and trying to get details and prodding people to perhaps try to narrow things down a bit more often ends up falling on the floor, because it's a big job).
Linus
Re: 2.6.16-rc3: more regressions
In reply to Linus TorvaldsQuoted 10 lines · Linus Torvalds
Quoted 3 lines · Adrian Bunk
The one thing I have not yet been proven wrong for is that this PCI id is the only one we have in this driver for an RV370.
It definitely is an RV370, you're right in that. I'm too lazy to actually see if the other entries that claim to be RV350's really are RV350's.
Well a while back, I hacked in the pci id for my Xpress 200M (5955), which is basically an RV370 with no dedicated vram. I did the same thing and claimed an RV350, which is the closest model. This allowed the radeon module to load. When I startx'ed and DRI was allowed to load on it, it locked up. So I never sent in the patch. I believe the person who sent this one in originally seemed to indicate that it worked, and I believed it if he had an X300 and my problem was having the IGP version. But now having this reported, I'm pretty sure it is the same problem. RV370 doesn't seem to work as an RV350.
Jesse
Re: 2.6.16-rc3: more regressions
Am Montag, den 13.02.2006, 16:27 -0700 schrieb Jesse Allen:
Quoted 12 lines · Linus Torvalds
Quoted 10 lines · Adrian Bunk
Quoted 3 lines
The one thing I have not yet been proven wrong for is that this PCI id is the only one we have in this driver for an RV370.
It definitely is an RV370, you're right in that. I'm too lazy to actually see if the other entries that claim to be RV350's really are RV350's.
Quoted 9 lines
Well a while back, I hacked in the pci id for my Xpress 200M (5955), which is basically an RV370 with no dedicated vram. I did the same thing and claimed an RV350, which is the closest model. This allowed the radeon module to load. When I startx'ed and DRI was allowed to load on it, it locked up. So I never sent in the patch. I believe the person who sent this one in originally seemed to indicate that it worked, and I believed it if he had an X300 and my problem was having the IGP version. But now having this reported, I'm pretty sure it is the same problem. RV370 doesn't seem to work as an RV350.
The Xpress200 chips have a completely different GART implementation. Thus the driver can't even send commands to the command processor and that's why X locked up on you when DRI was enabled. This has nothing to do with the Xpress200 being (almost) an RV370 or not.
Regards,
Felix
Signature · 2 lines
| Felix Kühling <[email protected]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 |
Re: 2.6.16-rc3: more regressions
Quoted 12 lines · Felix Kühling
Am Montag, den 13.02.2006, 16:27 -0700 schrieb Jesse Allen:
Quoted 10 lines
Well a while back, I hacked in the pci id for my Xpress 200M (5955), which is basically an RV370 with no dedicated vram. I did the same thing and claimed an RV350, which is the closest model. This allowed the radeon module to load. When I startx'ed and DRI was allowed to load on it, it locked up. So I never sent in the patch. I believe the person who sent this one in originally seemed to indicate that it worked, and I believed it if he had an X300 and my problem was having the IGP version. But now having this reported, I'm pretty sure it is the same problem. RV370 doesn't seem to work as an RV350.
Quoted 5 lines
The Xpress200 chips have a completely different GART implementation. Thus the driver can't even send commands to the command processor and that's why X locked up on you when DRI was enabled. This has nothing to do with the Xpress200 being (almost) an RV370 or not.
Well, I did not know about the GART problem. So this means that RV370s and XPRESS will be listed both separately in the driver in the future? They certainly don't function as an RV350 and of course they aren't quite compatable then.
Jesse
Re: 2.6.16-rc3: more regressions
Quoted 5 lines
Well, I did not know about the GART problem. So this means that RV370s and XPRESS will be listed both separately in the driver in the future? They certainly don't function as an RV350 and of course they aren't quite compatable then.
The RV350 and RV370 are more or less programatically the same, I'm not sure there is any difference, the XPRESS chipsets although based on RV370 have a whole different memory controller architecture by virtue of being shared memory..
Dave.
Re: 2.6.16-rc3: more regressions
In reply to Adrian BunkQuoted 43 lines · Adrian Bunk
Date: Mon, 13 Feb 2006 19:34:45 +0100
From: Adrian Bunk <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: Dave Jones <[email protected]>, Andrew Morton <[email protected]>,
Linux Kernel Mailing List <[email protected]>, Mauro Tassinari <[email protected]>, [email protected], [email protected]
Subject: Re: 2.6.16-rc3: more regressionsQuoted 9 lines · Linus Torvalds
Quoted 2 lines · Linus Torvalds
DaveA, I'll apply this for now. Comments?
Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly suppresses the ID entirely, but the string seems to match the one that Dave Jones reports) may be unrelated.
Dave's patch removes the entry for the card with the
0x5b60.According to his bug report, Mauro has a Radeon X300SE that should have the
0x5b70according to pci.ids from pciutils and that doesn't seem to be claimed by the DRM driver (and the dmesg from the bug report confirms that the radeon DRM driver didn't claim to be responsible for this card).Quoted 11 lines
DaveJ (or Mauro): since you can test this, can you test having that ID there but _without_ the other changes to drm in -rc1?
Ie was it the addition of that particular ID, or are the other radeon driver changes (which haven't had as much testing) perhaps the culprit?
I realize that without the ID, that card would never have been tested anyway, but the point being that plain 2.6.15 with _just_ that ID added has at least gotten more testing on other (similar) chips. So before I revert that particular ID, it would be nice to know that it was broken even with the previous radeon driver state.
The ID removed by Dave's patch is the only ID listed for an RV370 chips (the other RV370's aren't listed in the radeon DRM driver).
Quoted 6 lines
I suspect Dave and Mauro having unrelated problems.
Quoted 1 line
Linus
cu
Adrian
The X300 has two pci ids:
0000:05:00.0 0300: 1002:5b60
0000:05:00.1 0380: 1002:5b70
0000:05:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
0000:05:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
Gerhard
--
Gerhard Mack
<>< As a computer I find your faith in technology amusing.
Re: 2.6.16-rc3: more regressions
In reply to Linus TorvaldsQuoted 3 lines
DaveA, I'll apply this for now. Comments?
(sorry - I've been finding my way back home from Xdevconf, just landed)...
I asked DaveJ I believe in one thread to disable Load "dri" in his xorg.conf and report back,
the X.org driver contains problems not the DRM driver, however adding the PCI ID to the DRM driver will cause the X.org driver to enable buggy features..
I cannot fix this from the DRM side, either we enable DRM for these cards at some point or we don't, ideally the X.org driver wouldn't enable DRI by default for r300 class cards..
There may be some other issues however that Ben is currently looking into with the memory manager setup,
I've tested the r300 on the 5460 rv350, and I've heard the rv370 doesn't have any great differences, the Xpress 200 is a mess and I'm not accepting any patches for them until someone with one that knows what they are doing gets it working..
Dave.
Dave.
Re: 2.6.16-rc3: more regressions
Quoted 8 lines · Dave Airlie
Quoted 3 lines
DaveA, I'll apply this for now. Comments?
(sorry - I've been finding my way back home from Xdevconf, just landed)...
I asked DaveJ I believe in one thread to disable Load "dri" in his xorg.conf and report back,
Ah sorry about that. You were just about to go to LCA when that came up, so I figured I'd wait until you had time to look at it again :)
There's a log at http://people.redhat.com/davej/Xorg.0.log
That doesn't have drm disabled, but it is being run on a kernel with the pci id commented out. I'm a bit reluctant to reboot the workstation to try a non-drm enabled X at the moment, until some stuff finishes. Let me know if that log is insufficient or not.
Dave
Re: 2.6.16-rc3: more regressions
nding my way back home from Xdevconf, just landed)...
Quoted 4 lines
Quoted 3 lines
I asked DaveJ I believe in one thread to disable Load "dri" in his xorg.conf and report back,
Quoted 9 lines
Ah sorry about that. You were just about to go to LCA when that came up, so I figured I'd wait until you had time to look at it again :)
There's a log at http://people.redhat.com/davej/Xorg.0.log
That doesn't have drm disabled, but it is being run on a kernel with the pci id commented out. I'm a bit reluctant to reboot the workstation to try a non-drm enabled X at the moment, until some stuff finishes. Let me know if that log is insufficient or not.
Well the things is not having the PCI id is the same things as commenting out Load "dri" in the xorg.conf really, X never tries to initialise the DRM layer on the card, I know this is a bug in the current 7.0 radeon driver and I'm hoping Ben's fixed can fix this however, we will end up never being able to turn on DRM support for r300 cards until X.org 7.1 is widespread or we add some kind of second stage enable that a new X server can work but I'm not really sure that this is possible,
The fix is to not load DRI on old X.org r300 installs...
Dave.
Re: 2.6.16-rc3: more regressions
In reply to Adrian BunkQuoted 5 lines · Adrian Bunk
Subject : OCFS2 Filesystem inconsistency across nodes
References : http://lkml.org/lkml/2006/2/10/14
Submitter : Claudio Martins <[email protected]>Handled-By Mark Fasheh <[email protected]>Status : unknown
Definitely a regression. I think some patch that was merged shortly after OCFS2 is causing this. I'm trying to narrow it down to a single patch right now...
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
[email protected]