2.6.12-rc1-mm3
Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
- Mainly a bunch of fixes relative to 2.6.12-rc1-mm2.
- Again, we'd like people who have had recent DRM and USB resume problems to
test and report, please.
- The bk-ide-dev tree is back after a couple of weeks of difficulties.
- Jeff asks that anyone who has had problems with the Silicon Image SATA
drivers test sata_sil-corruption--lockup-fix.patch, which is included in
this kernel.
Changes since 2.6.12-rc1-mm2:
linus.patch
bk-acpi.patch
bk-agpgart.patch
bk-alsa.patch
bk-arm.patch
bk-audit.patch
bk-cifs.patch
bk-cpufreq.patch
bk-cryptodev.patch
bk-driver-core.patch
bk-driver-core-hang-fix.patch
bk-drm.patch
bk-drm-via.patch
bk-i2c.patch
bk-ia64.patch
bk-ide-dev.patch
bk-ieee1394.patch
bk-input.patch
bk-jfs.patch
bk-kbuild.patch
bk-libata.patch
bk-mtd.patch
bk-net.patch
bk-netdev.patch
bk-nfs.patch
bk-nfs-gcc4-fix.patch
bk-ntfs.patch
bk-pci.patch
bk-scsi.patch
bk-scsi-rc-fixes.patch
bk-serial.patch
bk-usb.patch
bk-watchdog.patch
bk-xfs.patch
Latest versions of sudsystem trees
-fix-agp_backend-usage-in-drm_agp_init.patch
-drm-ioctl-fix.patch
-zd1201-makefile-fix.patch
Merged
-agp-make-some-code-static.patch
Dropped - it broke things.
+powernow-k7recalibrate-cpu_khz.patch
+cpufreq-timers-recalibrate_cpu_khz.patch
cpufreq fixes
+bk-driver-core-hang-fix.patch
Fix for new sysfs/kobject locking code
+sata_sil-corruption--lockup-fix.patch
Silicon Image SATA fixes
+bk-nfs-gcc4-fix.patch
Fix bk-nfs for gcc4
+drivers-pci-hotplug-cpqphp_corec-fix-a-check-after-use.patch
+drivers-usb-misc-usbtestc-fix-a-null-dereference.patch
use-after-free buglets which the compiler was hiding.
+ub-atomicity-fix.patch
Fix sleep-while-atomic in the new usb block driver ub.c
+usb_cdc-build-fix.patch
Compile fix
+freepgt-hugetlb_free_pgd_range-fix-aio-panic-fix.patch
Fix freepgt-hugetlb_free_pgd_range.patch for
ppc64-fix-aio-panic-caused-by-is_hugepage_only_range.patch
+drivers-net-amd8111ec-fix-napi-interrupt-in-poll.patch
net driver NAPI fix
+ipv6-fix-address-interface-handling-according-to-the-scoping-architecture.patch
Fix ipv6 connections to the local address
+drivers-net-wireless-airoc-correct-a-wrong-check.patch
airo fixlet
+ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix.patch
ppc32 build fix
+ppc32-fix-broken-compile-on-sky-computers-hdpu-platform.patch
+ppc32-8xx-typo-fix.patch
ppc32 fixes
+ppc64-fix-lpar-iommu-setup-code-for-p630.patch
ppc64 fix
+mips-update-vr41xx-rtc-support.patch
MIPS fix
-via-irq-fixup-fix-warning-fix.patch
Folded into the new version of x86-via-workaround.patch
-x86_64-separate-amd-cmp-detection-from-hyper-threading.patch
This conflicted with the Intel cpu type detection patches
+x86_64-nop-out-system-call-instruction-in-vsyscall-page-fix.patch
Fix x86_64-nop-out-system-call-instruction-in-vsyscall-page.patch
+x86_64-fix-missing-delay-when-the-tsc-counter-just.patch
x86_64 fix
+x86_64-show_stack-touch_nmi_watchdog.patch
I was having inexplicable soft-lockup-detector timeouts during sysrq-t over
9600 baud serial. Don't know if this fixes it though.
+s390-kernel-faults.patch
+s390-signal-stack-bug.patch
+s390-dasd-preferred-path-support.patch
+s390-qeth-layer2-fixes.patch
+s390-qeth-1920-device-support.patch
+s390-qeth-blkt-tuning.patch
+s390-qeth-tcp-segmentation-offload.patch
+s390-claw-network-device-driver.patch
s/390 updates
+relayfs-properly-handle-oversized-events.patch
relayfs fix
-keys-pass-session-keyring-to-call_usermodehelper-warning-fix.patch
Unneeded
+keys-pass-session-keyring-to-call_usermodehelper-fix.patch
Fix stuff in the new keys-pass-session-keyring-to-call_usermodehelper.patch
+fs-attrc-fix-check-after-use.patch
+fs-smbfs-requestc-fix-null-dereference.patch
More fixlets derived from the Coverity tool (does this thing have a name?)
+sched-uninline-task_timeslice.patch
Uninline a scheduler function.
-wbsd-update.patch
rmk spat this back.
+doc-where-to-find-ldd3.patch
Add a pointer to the Linux Device Drivers book.
+fuse-device-functions-comments-and-documentation.patch
+fuse-device-functions-cleanup.patch
+fuse-mount-options-comments-and-documentation.patch
+fuse-mount-options-fix-cleanup.patch
FUSE fixes and cleanups
+sound-oss-rme96xxc-remove-kernel-22-ifs.patch
+drivers-char-mwave-tp3780ic-remove-kernel-22-ifs.patch
+drivers-net-skfp-cleanups.patch
Little fixes and cleansup
+remove-exports-for-oem-modules.patch
+mm-page_allocc-unexport-nr_swap_pages.patch
+unexport-console_unblank.patch
+mm-swapc-unexport-vm_acct_memory.patch
+mm-swapfilec-unexport-total_swap_pages.patch
+mm-swap_statec-unexport-swapper_space.patch
+unexport-slab_reclaim_pages.patch
+net-atm-resourcesc-remove-__free_atm_dev.patch
unexport some symbols.
number of patches in -mm: 867
number of changesets in external trees: 743
number of patches in -mm only: 834
total patches: 1577
All 867 patches:
linus.patch
pcmcia-properly-bail-out-on-mtd-related-ioctl-invocation.patch
pcmcia: properly bail out on MTD-related ioctl invocation
pcmcia-dont-lock-up-in-rsrc_nonstatic-pcmcia_validate_mem.patch
pcmcia: don't lock up in rsrc_nonstatic pcmcia_validate_mem
pcmcia-dont-send-eject-request-events-to-userspace.patch
pcmcia: don't send eject request events to userspace
ppc64-preliminary-changes-to-of-fixup-functions.patch
ppc64: preliminary changes to OF fixup functions
ppc64-make-of-node-fixup-code-usable-at-runtime.patch
ppc64: make OF node fixup code usable at runtime
ppc64-introduce-pseries_reconfig.patch
ppc64: introduce pSeries_reconfig.[ch]
ppc64-promc-use-pseries-reconfig-notifier.patch
ppc64: prom.c: use pSeries reconfig notifier
ppc64-fix-aio-panic-caused-by-is_hugepage_only_range.patch
ppc64: fix AIO panic on PPC64 caused by is_hugepage_only_range()
handle-multiple-video-cards-on-the-same-bus.patch
handle multiple video cards on the same bus
tty-overrun-time-fix.patch
tty overrun time fix
ia64-msi-warning-fixes.patch
ia64 msi warning fixes
ia64-config_apci_numa-fix.patch
ia64 CONFIG_APCI_NUMA fix
bk-acpi.patch
acpi-ec-warning-fix.patch
acpi ec.c warning fix
acpi-toshiba-failure-handling.patch
acpi: Toshiba failure handling
acpi-video-pointer-size-fix.patch
acpi video pointer size fix
acpi-create_polling_proc-fix.patch
acpi: create_polling_proc() fix
bk-agpgart.patch
agp-fix-for-xen-vmm.patch
AGP fix for Xen VMM
bk-alsa.patch
include-linux-soundcardh-endianness-fix.patch
include/linux/soundcard.h: endianness fix
bk-arm.patch
arm-atomic_sub_and_test.patch
arm atomic_sub_and_test()
bk-audit.patch
bk-cifs.patch
bk-cpufreq.patch
powernow-k7recalibrate-cpu_khz.patch
powernowk7: recalibrate cpu_khz
cpufreq-timers-recalibrate_cpu_khz.patch
cpufreq timers: recalibrate cpu_khz
bk-cryptodev.patch
bk-driver-core.patch
export-platform_add_devices.patch
export platform_add_devices
bk-driver-core-hang-fix.patch
bk-driver-core hang fix
bk-drm.patch
3dfx-drm-depends-on-pci.patch
3dfx DRM depends on PCI
bk-drm-via.patch
bk-i2c.patch
bk-ia64.patch
bk-ide-dev.patch
bk-ieee1394.patch
bk-input.patch
alps-printk-tidy.patch
alps-printk-tidy
bk-jfs.patch
bk-kbuild.patch
uml-make-deb-pkg-build-target-build-a-debian-style-user-mode-linux-package.patch
uml: make deb-pkg build target build a Debian-style user-mode-linux package
uml-restore-proper-descriptions-in-make-deb-pkg-target.patch
UML - Restore proper descriptions in make deb-pkg target
doc-describe-kbuild-pitfall.patch
doc: describe Kbuild pitfall
complete-cpufreq-kconfig-cleanup.patch
complete cpufreq Kconfig cleanup
bk-libata.patch
sata_sil-corruption--lockup-fix.patch
sata_sil corruption / lockup fix
bk-mtd.patch
bk-net.patch
bk-netdev.patch
bk-nfs.patch
bk-nfs-gcc4-fix.patch
nfs4 build fix
nfs4-empty-array-fix.patch
nfs4 empty array fix
bk-ntfs.patch
bk-pci.patch
debug-for-pci-io-mem-allocation.patch
DEBUG for PCI IO & MEM allocation
pci-pci-transparent-bridge-handling-improvements-pci-core.patch
PCI-PCI transparent bridge handling improvements (pci core)
pci-pci-transparent-bridge-handling-improvements-yenta_socket.patch
PCI-PCI transparent bridge handling improvements (yenta_socket)
acpi-bridge-hotadd-acpi-based-root-bridge-hot-add.patch
acpi bridge hotadd: ACPI based root bridge hot-add
acpi-bridge-hotadd-fix-pci_enable_device-for-p2p-bridges.patch
acpi bridge hotadd: Fix pci_enable_device() for p2p bridges
acpi-bridge-hotadd-make-pcibios_fixup_bus-hot-plug-safe.patch
acpi bridge hotadd: Make pcibios_fixup_bus() hot-plug safe
acpi-bridge-hotadd-prevent-duplicate-bus-numbers-when-scanning-pci-bridge.patch
acpi bridge hotadd: Prevent duplicate bus numbers when scanning PCI bridge
acpi-bridge-hotadd-take-the-pci-lock-when-modifying-pci-bus-or-device-lists.patch
acpi bridge hotadd: Take the PCI lock when modifying pci bus or device lists
acpi-bridge-hotadd-link-newly-created-pci-child-bus-to-its-parent-on-creation.patch
acpi bridge hotadd: Link newly created pci child bus to its parent on creation
acpi-bridge-hotadd-make-the-pci-remove-routines-safe-for-failed-hot-plug.patch
acpi bridge hotadd: Make the PCI remove routines safe for failed hot-plug
acpi-bridge-hotadd-remove-hot-plugged-devices-that-could-not-be-allocated-resources.patch
acpi bridge hotadd: Remove hot-plugged devices that could not be allocated resources
acpi-bridge-hotadd-read-bridge-resources-when-fixing-up-the-bus.patch
acpi bridge hotadd: Read bridge resources when fixing up the bus
acpi-bridge-hotadd-allow-acpi-add-and-start-operations-to-be-done-independently.patch
acpi bridge hotadd: Allow ACPI .add and .start operations to be done independently
acpi-bridge-hotadd-export-the-interface-to-get-pci-id-for-an-acpi-handle.patch
acpi bridge hotadd: Export the interface to get PCI id for an ACPI handle
drivers-pci-hotplug-cpqphp_corec-fix-a-check-after-use.patch
drivers/pci/hotplug/cpqphp_core.c: fix a check after use
bk-scsi.patch
megaraid_sas-announcing-new-module-for.patch
megaraid_sas: Announcing new module for LSI Logic's SAS based MegaRAID controllers
open-iscsi-scsi.patch
open-iscsi-scsi
open-iscsi-headers.patch
open-iscsi-headers
open-iscsi-kconfig.patch
open-iscsi-kconfig
open-iscsi-makefile.patch
open-iscsi-makefile
open-iscsi-netlink.patch
open-iscsi-netlink
open-iscsi-doc.patch
open-iscsi-doc
bk-scsi-rc-fixes.patch
add-scsi-changer-driver.patch
add scsi changer driver
scsi-ch-build-fix.patch
scsi ch.c build fix
bk-serial.patch
bk-usb.patch
ub-atomicity-fix.patch
ub: atomicity fix
drivers-usb-misc-usbtestc-fix-a-null-dereference.patch
drivers/usb/misc/usbtest.c: fix a NULL dereference
usb_cdc-build-fix.patch
usb_cdc build fix
usb-resume-fixes.patch
usb resume fixes
usb-suspend-updates-interface-suspend.patch
usb suspend updates (interface suspend)
hcd-suspend-uses-pm_message_t.patch
hcd suspend uses pm_message_t
zd1201-build-fix.patch
zd1201 build fix
usb-support-for-new-ipod-mini-and-possibly-others.patch
usb: support for new ipod mini (and possibly others)
usb-wacom-driver-update.patch
usb: wacom driver update
bk-watchdog.patch
bk-xfs.patch
mm.patch
add -mmN to EXTRAVERSION
fix-help-for-acpi_container.patch
Fix help for ACPI_CONTAINER
swapspace-layout-improvements.patch
swapspace-layout-improvements
/proc/swaps negative Used
bdi-provide-backing-device-capability-information.patch
BDI: Provide backing device capability information [try #3]
cpusets-big-numa-cpu-and-memory-placement-backing_dev-fix.patch
cpusets-big-numa-cpu-and-memory-placement-backing_dev-fix
add-a-clear_pages-function-to-clear-pages-of-higher.patch
add a clear_pages function to clear pages of higher order
slab-kmalloc-cleanups.patch
slab.[ch]: kmalloc() cleanups
slab-64bit-fix.patch
slab: 64-bit fix
vmscan-move-code-to-isolate-lru-pages-into-separate-function.patch
vmscan: move code to isolate LRU pages into separate function
mm-counter-operations-through-macros.patch
mm counter operations through macros
mm-counter-operations-through-macros-tidy.patch
mm-counter-operations-through-macros-tidt
vmscan-notice-slab-shrinking.patch
vmscan: notice slab shrinking
slab-shrinkers-use-vfs_cache_pressure.patch
slab shrinkers: use vfs_cache_pressure
madvise-do-not-split-the-maps.patch
madvise: do not split the maps
madvise-merge-the-maps.patch
madvise: merge the maps
include-cleanup-in-pgalloch.patch
include cleanup in pgalloc.h
fix-mmap-of-dev-kmem.patch
Fix mmap of /dev/kmem
unused-size-assignment-in-filemap_nopage.patch
unused 'size' assignment in filemap_nopage
freepgt-free_pgtables-use-vma-list.patch
freepgt: free_pgtables use vma list
freepgt-remove-mm_vm_sizemm.patch
freepgt: remove MM_VM_SIZE(mm)
freepgt-hugetlb_free_pgd_range.patch
freepgt: hugetlb_free_pgd_range
freepgt-hugetlb_free_pgd_range-fix-aio-panic-fix.patch
ppc64-fix-aio-panic-caused-by-is_hugepage_only_range-ia64-fix
freepgt-remove-arch-pgd_addr_end.patch
freepgt: remove arch pgd_addr_end
freepgt-mpnt-to-vma-cleanup.patch
freepgt: mpnt to vma cleanup
freepgt-hugetlb-area-is-clean.patch
freepgt: hugetlb area is clean
eni155p-error-handling-fix.patch
ENI155P error handling fix
remove-last_rx-update-from-loopback-device.patch
remove last_rx update from loopback device
a-new-10gb-ethernet-driver-by-chelsio-communications.patch
A new 10GB Ethernet Driver by Chelsio Communications
a-new-10gb-ethernet-driver-by-chelsio-communications-update.patch
A new 10GB Ethernet Driver by Chelsio Communications (update)
pcnet32-bug-79c975-fiber-fix.patch
pcnet32 79C975 fiber fix
dm9000-network-driver.patch
DM9000 network driver
null-pointer-bug-in-netpollc.patch
NULL pointer bug in netpoll.c
restore-ports-module-parameter-for-ip_nat_ftp-and-ip_nat_irc.patch
Restore ports module parameter for ip_nat_ftp and ip_nat_irc
e1000-flush-work-queues-on-remove.patch
e1000: flush work queues on remove
ipt-leak-fix.patch
memory leak in net/sched/ipt.c?
drivers-net-amd8111ec-fix-napi-interrupt-in-poll.patch
drivers/net/amd8111e.c: fix NAPI interrupt in poll
ipv6-fix-address-interface-handling-according-to-the-scoping-architecture.patch
ipv6: Fix address/interface handling according to the scoping architecture
drivers-net-wireless-airoc-correct-a-wrong-check.patch
drivers/net/wireless/airo.c: correct a wrong check
selinux-make-code-static-and-remove-unused-code.patch
SELinux: make code static and remove unused code
selinux-allow-mounting-of-filesystems-with-invalid-root-inode-context.patch
SELinux: allow mounting of filesystems with invalid root inode context
selinux-audit-unrecognized-netlink-messages.patch
SELinux: audit unrecognized netlink messages
selinux-add-name_connect-permission-check.patch
SELinux: add name_connect permission check
ppc32-fix-mv64x60-internal-sram-size.patch
ppc32: Fix mv64x60 internal SRAM size
ppc32-move-83xx-85xx-device-and-system-description-files.patch
ppc32: Move 83xx & 85xx device and system description files
ppc32-fix-config_serial_text_debug-support-on-83xx.patch
ppc32: Fix CONFIG_SERIAL_TEXT_DEBUG support on 83xx
ppc32-typo-fix-in-load-store-string-emulation.patch
ppc32: typo fix in load/store string emulation
ppc32-report-chipset-version-in-common-proc-cpuinfo-handling.patch
ppc32: Report chipset version in common /proc/cpuinfo handling
ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix.patch
ppc32-report-chipset-version-in-common-proc-cpuinfo-handling fix
ppc32-dmasound-compilation-fix.patch
ppc32: dmasound compilation fix
ppc32-fix-sandpoint-soft-reboot.patch
ppc32: Fix Sandpoint Soft Reboot
ppc32-64-map-prefetchable-pci-without-guarded-bit.patch
ppc32/64: Map prefetchable PCI without guarded bit
ppc32-fix-broken-compile-on-sky-computers-hdpu-platform.patch
ppc32: fix broken compile on Sky Computers HDPU platform
ppc32-8xx-typo-fix.patch
ppc32: 8xx typo fix
ppc64-pci_dnc-use-pseries-reconfig-notifier.patch
ppc64: pci_dn.c: use pSeries reconfig notifier
ppc64-pseries_iommuc-use-pseries-reconfig-notifier.patch
ppc64: pSeries_iommu.c: use pSeries reconfig notifier
ppc64-fix-gcc4-compile-error-in-pacah.patch
ppc64: fix gcc4 compile error in paca.h
ppc64-fix-compile-error-in-promc.patch
ppc64: fix compile error in prom.c
ppc64-fix-linkage-error-on-g5.patch
ppc64: fix linkage error on G5
ppc64-fix-semtimedop-compat-syscall.patch
ppc64: fix semtimedop compat syscall
ppc64-fix-pseries-hcall-stubs.patch
ppc64: fix pseries hcall stubs
ppc64-make-numa=off-command-line-argument-work-again.patch
ppc64: Make numa=off command line argument work again
ppc64-fix-ethernet-phy-reset-on-imac-g5.patch
ppc64: Fix ethernet PHY reset on iMac G5
ppc64-fix-lpar-iommu-setup-code-for-p630.patch
PPC64: Fix LPAR IOMMU setup code for p630
mips-linkage-fix.patch
mips linkage fix
mips-update-vr41xx-rtc-support.patch
mips: update VR41xx RTC support
x86-reduce-cacheline-bouncing-in-cpu_idle_wait.patch
x86: reduce cacheline bouncing in cpu_idle_wait
x86-cmos-time-update-optimisation.patch
x86: CMOS time update optimisation
x86-cmos-time-update-optimisation-tidy.patch
x86-cmos-time-update-optimisation-tidy
x86-cmos-time-update-optimisation-locking-fix.patch
x86-cmos-time-update-optimisation locking fix
x86-cmos-time-update-optimisation-locking-fix-check.patch
x86-cmos-time-update-optimisation-locking-fix-check
x86-via-workaround.patch
x86: via workaround
apm-fix-interrupts-enabled-in-device_power_up.patch
APM: fix interrupts enabled in device_power_up
rtc_lock-is-irq-safe.patch
rtc_lock is irq-safe
fix-put_user-for-80386.patch
fix put_user for 80386
es7000-legacy-mappings-update.patch
ES7000 Legacy Mappings Update
x86-fix-esp-corruption-cpu-bug-take-2.patch
x86: fix ESP corruption CPU bug (take 2)
x86-fix-esp-corruption-cpu-bug-take-2-fix.patch
x86-fix-esp-corruption-cpu-bug-take-2 fix
es7000-dmi-cleanup.patch
es7000 dmi cleanup
i386-add-kstack=n-option-from-x86_64.patch
i386: add kstack=N option (from x86_64)
reduce-inlined-x86-memcpy-by-2-bytes.patch
x86: reduce inlined memcpy by 2 bytes
rename-fpu_verify_area-to-fpu_access_ok.patch
rename FPU_*verify_area to FPU_*access_ok
x86_64-update-defconfig.patch
x86_64: Update defconfig
x86_64-add-new-amd-cpuid-flags-to-cpuinfo.patch
x86_64: Add new AMD cpuid flags to cpuinfo
x86_64-add-an-64bit-entry-path-for-exec.patch
x86_64: Add an 64bit entry path for exec
x86_64-busses-array-is-only-indexed-with-a-8bit-value.patch
x86_64: Busses array is only indexed with a 8bit value, doesn't make sense
x86_64-fix-compilation-with-config_proc_fs=n.patch
x86_64: Fix compilation with CONFIG_PROC_FS=n
x86_64-move-hpet-selection-into-processor-specific.patch
x86_64: Move HPET selection into processor specific options
x86_64-remove-never-used-obsolete-file.patch
x86_64: Remove never used obsolete file
x86_64-fix-indentation-in-vsyscallc-no-functional.patch
x86_64: Fix indentation in vsyscall.c. No functional changes.
x86_64-nop-out-system-call-instruction-in-vsyscall-page.patch
x86_64: Nop out system call instruction in vsyscall page when not needed
x86_64-nop-out-system-call-instruction-in-vsyscall-page-fix.patch
x86_64: fix vsyscall.c syntax error
x86_64-remove-obsolete-comments-in-vsyscallc-and-fix.patch
x86_64: Remove obsolete comments in vsyscall.c and fix some others.
x86_64-remove-noisy-printk-in-k8-bus-detection-code.patch
x86_64: Remove noisy printk in K8 bus detection code
x86_64-remove-unused-and-broken-code-in-ioh.patch
x86_64: Remove unused and broken code in io.h
x86_64-remove-stale-unused-file.patch
x86_64: Remove stale unused file
x86_64-move-put_user-out-of-line.patch
x86_64: Move put_user out of line
x86_64-give-out-of-line-get_user-better-calling.patch
x86_64: Give out of line get_user better calling conventions
x86_64-work-around-tyan-bios-mtrr-initialization-bug.patch
x86_64: Work around Tyan BIOS MTRR initialization bug.
x86_64-include-pci-express-configuration.patch
x86_64: Include PCI-Express configuration
x86_64-cleanups-in-new-backtrace-code-in-oprofile.patch
x86_64: Cleanups in new backtrace code in oprofile
x86_64-fix-special-isa-case-in-iounmap.patch
x86_64: Fix special ISA case in iounmap()
x86_64-fix-formatting-and-white-space-in-signal-code.patch
x86_64: Fix formatting and white space in signal code
x86_64-mem=xxx-will-now-limit-kernel-memory-to-xxx.patch
x86_64: mem=XXX will now limit kernel memory to XXX instead of XXX+1MB
x86_64-resume-pit-for-x86_64.patch
x86_64: resume PIT for x86_64
x86_64-fix-nmi-rtc-access-race.patch
x86_64: Fix NMI RTC access race
x86_64-minor-fix-to-tlb-flush-ipi.patch
x86_64: Minor fix to TLB flush IPI
x86_64-always-reload-cr3-completely-when-a-lazy-mm.patch
x86_64: Always reload CR3 completely when a lazy MM thread drops a MM.
x86_64-fix-ldt-descriptor.patch
x86_64: Fix LDT descriptor
x86_64-change-the-y2069-bug-in-the-rtc-timer-code-to-be.patch
x86_64: Change the y2069 bug in the RTC timer code to be a y2100 bug.
x86_64-only-free-pmds-and-puds-after-other-cpus-have.patch
x86_64: Only free PMDs and PUDs after other CPUs have been flushed
x86_64-dont-enable-interrupts-in-oopses.patch
x86_64: Don't enable interrupts in oopses unconditionally
x86_64-fix-smp-fallback-to-up.patch
x86_64: Fix SMP fallback to UP
x86_64-fix-config_preempt.patch
x86_64: Fix CONFIG_PREEMPT
x86_64-fix-exception-stack-detection-during-backtraces.patch
x86_64: Fix exception stack detection during backtraces
x86_64-fix-gcc-34-warning-in-bitopsc.patch
x86_64: Fix gcc 3.4 warning in bitops.c
x86_64-fix-missing-delay-when-the-tsc-counter-just.patch
x86_64: Fix missing delay when the TSC counter just overflowed
x86_64-clean-up-the-iommu-initialisation-a-bit.patch
x86_64: Clean up the IOMMU initialisation a bit
x86-64-kconfig-typo-trivial.patch
x86-64: kconfig typo
x86_64-remove-old-decl-trivial.patch
x86_64: remove old decl (trivial)
x86_64-avoid-panic-lockup.patch
x86_64: avoid panic lockup
x86_64-hugetlb-fix.patch
x86_64: hugetlb fix
x86-64-forgot-asmlinkage-on-sys_mmap.patch
x86-64: forgot asmlinkage on sys_mmap
x86_64-reduce-cacheline-bouncing-in-cpu_idle_wait.patch
x86_64: reduce cacheline bouncing in cpu_idle_wait
x86_64-reduce-cacheline-bouncing-in-cpu_idle_wait-warning-fix.patch
x86_64-reduce-cacheline-bouncing-in-cpu_idle_wait-warning-fix
x86-64-kprobes-handle-%rip-relative-addressing-mode.patch
x86-64 kprobes: handle %RIP-relative addressing mode
kernel-parameters-ia-32-x86-64-cleanups.patch
kernel-parameters: IA-32/X86-64 cleanups
x86-x86_64-reading-deterministic-cache-parameters-and-exporting-it-in-sysfs.patch
x86, x86_64: reading deterministic cache parameters and exporting it in /sysfs
x86-x86_64-intel-dual-core-detection.patch
x86, x86_64: Intel dual-core detection
x86-cacheline-alignment-for-cpu-maps.patch
x86: cacheline alignment for cpu maps
x86_64-dump-stack-in-early-exception.patch
x86_64-dump-stack-in-early-exception
x86_64-show_stack-touch_nmi_watchdog.patch
x86_64-show_stack-touch_nmi_watchdog
alpha-spinlockh-update.patch
alpha spinlock.h update
ia64-reduce-cacheline-bouncing-in-cpu_idle_wait.patch
ia64: reduce cacheline bouncing in cpu_idle_wait
ia64-reduce-cacheline-bouncing-in-cpu_idle_wait-fix.patch
ia64-reduce-cacheline-bouncing-in-cpu_idle_wait fix
swsusp-add-missing-refrigerator-calls.patch
swsusp: Add missing refrigerator calls
suspend-to-ram-update-videotxt-with-more-systems.patch
suspend-to-ram: update video.txt with more systems
pm-remove-obsolete-pm_-from-vtc.patch
pm: remove obsolete pm_* from vt.c
swsusp-small-updates.patch
swsusp: small updates
swsusp-1-1-kill-swsusp_restore.patch
swsusp: kill swsusp_restore
m32r-update-mmu-less-support-1.patch
m32r: Update MMU-less support #1
m32r-update-mmu-less-support-2.patch
m32r: Update MMU-less support #2
m32r-update-mmu-less-support-3.patch
m32r: Update MMU-less support #3
m32r-fix-m32102-i-cache-invalidation.patch
m32r: Fix M32102 I-cache invalidation
m32r_sio-driver-update.patch
m32r_sio driver update
m68k-update-signal-delivery-handling.patch
M68k: Update signal delivery handling
m68k-stdma-replace-sleep_on-with-wait_event.patch
M68k/stdma: Replace sleep_on() with wait_event()
zorro-replace-printk-with-pr_info-in-drivers-zorro-zorroc.patch
Zorro: replace printk() with pr_info() in drivers/zorro/zorro.c
mac-ncr5380-scsi-fix-bus-error.patch
Mac NCR5380 SCSI: Fix bus error
m68k-ip-checksum-updates.patch
M68k: IP checksum updates
sun-3-3x-enable-sun-partition-tables-support-by-default.patch
Sun-3/3x: Enable Sun partition tables support by default
m68k-add-missing-pieces-of-thread-info-tif_memdie-support.patch
M68k: Add missing pieces of thread info TIF_MEMDIE support
tpm-depends-on-pci.patch
TPM depends on PCI
uml-cope-with-uml_net-security-fix-2.patch
uml: cope with uml_net security fix
uml-fix-compile.patch
uml: fix compile
uml-cpu_relax-fix.patch
uml: cpu_relax fix
uml-extend-cmd-line-limits.patch
uml: extend cmd line limits
uml-disable-more-hardware-kconfig-opt-and-rename-usermode-to-uml.patch
uml: disable more hardware kconfig opt and rename USERMODE to UML
uml-little-build-fixes.patch
Uml: little build fixes
uml-factor-out-common-code-in-user-obj-handling.patch
uml: factor out common code in user-obj handling
uml-kbuild-link-cmd.patch
uml - kbuild: link cmd
uml-add-kconfig-debug-deps.patch
uml: add kconfig debug deps
uml-real-fix-for-__gcov_init-symbols.patch
uml: real fix for __gcov_init symbols
uml-fix-cond-expr-as-lvalues-warning.patch
Subject: [patch 12/12] uml: fix "cond. expr. as lvalues" warning
s390-swapped-memset-arguments.patch
s390: swapped memset arguments.
s390-kernel-faults.patch
s390: kernel faults
s390-signal-stack-bug.patch
s390: signal stack bug
s390-dasd-preferred-path-support.patch
s390: dasd preferred path support
s390-qeth-layer2-fixes.patch
s390: qeth layer2 fixes
s390-qeth-1920-device-support.patch
s390: qeth 1920 device suppor
s390-qeth-blkt-tuning.patch
s390: qeth blkt tuning
s390-qeth-tcp-segmentation-offload.patch
s390: qeth tcp segmentation offload
s390-claw-network-device-driver.patch
s390: claw network device driver
make-sysrq-f-call-oom_kill.patch
make sysrq-F call oom_kill()
mtrr-size-and-base-debug.patch
mtrr size-and-base debugging
cant-unmount-bad-inode.patch
Can't unmount bad inode
iounmap-debugging.patch
iounmap debugging
detect-soft-lockups.patch
detect soft lockups
detect-soft-lockups-from-touch_nmi_watchdog.patch
detect-soft-lockups: call from touch_nmi_watchdog
areca-raid-linux-scsi-driver.patch
ARECA RAID Linux scsi driver
rt-lsm.patch
RT-LSM
tty-output-lossage-fix.patch
tty output lossage fix
cx24110-conexant-frontend-update.patch
cx24110 Conexant Frontend update
nice-and-rt-prio-rlimits.patch
nice and rt-prio rlimits
relayfs.patch
relayfs
relayfs-properly-handle-oversized-events.patch
relayfs: properly handle oversized events
relayfs-backing_dev-fix.patch
relayfs-backing_dev-fix
cfq-iosched-update-to-time-sliced-design.patch
cfq-iosched: update to time sliced design
cfq-iosched-update-to-time-sliced-design-export-task_nice.patch
cfq-iosched-update-to-time-sliced-design-export-task_nice
cfq-iosched-update-to-time-sliced-design-fix.patch
cfq-iosched-update-to-time-sliced-design fix
cfq-iosched-update-to-time-sliced-design-fix-fix.patch
cfq-iosched-update-to-time-sliced-design-fix-fix
cfq-iosched-update-to-time-sliced-design-use-bio_data_dir.patch
cfq-iosched-update-to-time-sliced-design: use bio_data_dir()
cfq-ioschedc-fix-soft-hang-with-non-fs-requests.patch
cfq-iosched.c: fix soft hang with non-fs requests
keys-discard-key-spinlock-and-use-rcu-for-key-payload.patch
keys: Discard key spinlock and use RCU for key payload
keys-discard-key-spinlock-and-use-rcu-for-key-payload-try-4.patch
keys: Discard key spinlock and use RCU for key payload - try #4
keys-pass-session-keyring-to-call_usermodehelper.patch
Keys: Pass session keyring to call_usermodehelper()
keys-pass-session-keyring-to-call_usermodehelper-fix.patch
keys-pass-session-keyring-to-call_usermodehelper fix
keys-use-rcu-to-manage-session-keyring-pointer.patch
Keys: Use RCU to manage session keyring pointer
keys-make-request-key-create-an-authorisation-key.patch
Keys: Make request-key create an authorisation key
stallion-driver-module-clean-up.patch
Stallion driver module clean up
use-__init-and-__exit-in-pktcdvd.patch
Use __init and __exit in pktcdvd
dvd-ram-support-for-pktcdvd.patch
DVD-RAM support for pktcdvd
break_lock-fix-2.patch
break_lock fix
cdrom-cdu31a-cleanups.patch
cdrom/cdu31a: cleanups
cdrom-cdu31a-locking-fixes.patch
cdrom/cdu31a: locking fixes
cdrom-cdu31a-use-wait_event.patch
cdrom/cdu31a: use wait_event
revert-gconfig-changes.patch
revert recent gconfig changes
revert-gconfig-changes-build-fix.patch
revert-gconfig-changes build fix
enable-gcc-warnings-for-vsprintf-vsnprintf-with-format-attribute.patch
Enable gcc warnings for vsprintf/vsnprintf with "format" attribute
w6692-eliminate-bad-section-references.patch
w6692: eliminate bad section references
teles3-eliminate-bad-section-references.patch
teles3: eliminate bad section references
elsa-eliminate-bad-section-references.patch
elsa eliminate bad section references
hfc_sx-eliminate-bad-section-references.patch
hfc_sx: eliminate bad section references
sedlbauer-eliminate-bad-section-references.patch
sedlbauer: eliminate bad section references
fix-mprotect-with-len=size_t-1-to-return-enomem.patch
fix mprotect() with len=(size_t)(-1) to return -ENOMEM
checkstack-fix-sort-misbehavior-for-long-function-names.patch
checkstack: fix sort misbehavior for long function names
fix-irq_affinity-write-from-proc-for-ia64.patch
Fix irq_affinity write from /proc for ia64
fix-mmap-return-value-to-conform-posix.patch
fix mmap() return value to conform POSIX
fix-mmap-return-value-to-conform-to-posix.patch
fix mmap() return value to conform to POSIX
exports-to-enable-clock-driver-modules.patch
Exports to enable clock driver modules
per-cpu-irq-stat.patch
Per cpu irq stat
kill-drivers-cdrom-mcdc.patch
kill drivers/cdrom/mcd.c
drivers-char-isicomc-gcc4-fix.patch
drivers/char/isicom.c gcc4 fix
infiniband-remove-unsafe-use-of-in_atomic.patch
InfiniBand: remove unsafe use of in_atomic()
new-console-flag-con_boot.patch
New console flag: CON_BOOT
new-console-flag-con_boot-comment.patch
new-console-flag-con_boot-comment
pipe-save-one-pipe-page.patch
pipe: save one pipe page
kprobes-incorrect-spin_unlock_irqrestore-call-in-register_kprobe.patch
kprobes: incorrect spin_unlock_irqrestore() call in register_kprobe()
ext2_make_empty-information-leak.patch
ext2_make_empty information leak fix
missing-set_fs-calls-around-kernel-syscall.patch
Missing set_fs() calls around kernel syscall
cpusets-mems-generation-deadlock-fix.patch
cpusets: mems generation deadlock fix
cpusets-alloc-gfp_wait-sleep-fix.patch
cpusets: alloc GFP_WAIT sleep fix
mtrr-uaccess-range-checking-fix.patch
mtrr: uaccess range checking fix
cciss-range-checking-fix.patch
cciss: range chcking fix
fix-posix-timers-expiring-before-their-scheduled-time.patch
Fix POSIX timers expiring before their scheduled time
fix-oops-when-inserting-ipmi_si-module.patch
Fix oops when inserting ipmi_si module
binfmt_elf-bss-padding-fix.patch
binfmt_elf bss padding fix
posix-cpu-timers-and-cputime_t-divisons.patch
posix-cpu-timers and cputime_t divisons.
timers-prepare-for-del_timer_sync-changes.patch
timers: prepare for del_timer_sync() changes
timers-rework-del_timer_sync.patch
timers: rework del_timer_sync()
timers-serialize-timers.patch
timers: serialize timers
timers-remove-memory-barriers.patch
timers: remove memory barriers
timers-cleanup-kill-__get_base.patch
timers: cleanup, kill __get_base()
timers-enable-irqs-in-__mod_timer.patch
timers: enable irqs in __mod_timer()
timers-enable-irqs-in-__mod_timer-tidy.patch
timers-enable-irqs-in-__mod_timer-tidy
ext2-3-file-limits-to-avoid-overflowing-i_blocks.patch
ext2/3 file limits to avoid overflowing i_blocks
load_elf_library-kfree-fix.patch
load_elf_library kfree fix
futex-queue_me-get_user-ordering-fix.patch
Futex: make futex_wait() atomic again
io_remap_pfn_range-add-for-all-arch-es.patch
io_remap_pfn_range: add for all arch-es
io_remap_pfn_range-add-for-all-arch-es-fix.patch
io_remap_pfn_range-add-for-all-arch-es-fix
io_remap_pfn_range-convert-sparc-callers.patch
io_remap_pfn_range: convert sparc callers
io_remap_pfn_range-fix-some-callers-for-xen.patch
io_remap_pfn_range: fix some callers for XEN
io_remap_pfn_range-convert-last-callers.patch
io_remap_pfn_range: convert last callers
alpha-build-fixes.patch
alpha build fixes
fix-pcmcia-resume-with-card-inserted.patch
Fix PCMCIA resume with card inserted
pcmcia-clean-up-suspend.patch
pcmcia: clean up suspend
small-warning-fix-for-gcc4.patch
small warning fix for gcc4
enable-sig_ign-on-blocked-signals.patch
Enable SIG_IGN on blocked signals
alpha-elimitate-two-warnings-from-gcc4.patch
alpha: elimitate two warnings from gcc4
fat-set-ms_noatime-to-msdos.patch
FAT: set MS_NOATIME to msdos
fat-fix-msdos-datetime.patch
FAT: Fix msdos ->[ac]{date,time}
fix-compile-warning-in-drivers-pnp-resourcec-with-config_pci.patch
Fix compile warning in drivers/pnp/resource.c with !CONFIG_PCI
nlm-fix-f_count-leak.patch
nlm: fix f_count leak
module-parameter-fixes.patch
module parameter fixes
fs-hpfs-fix-hpfs-support-under-64-bit-kernel.patch
fs/hpfs/*: fix HPFS support under 64-bit kernel
arch-hook-for-notifying-changes-in-pte-protections-bits.patch
arch hook for notifying changes in PTE protections bits
serial-digi-neo-driver.patch
serial: Digi Neo driver
netmos-parallel-serial-combo-support.patch
Netmos parallel/serial/combo support
consolidate-asm-ipch.patch
consolidate asm/ipc.h
bt819-array-indexing-fix.patch
bt819 array indexing fix
unified-spinlock-initialization.patch
unified spinlock initialization
drivers-block-dac960c-fix-a-use-after-free.patch
drivers/block/DAC960.c: fix a use after free
drivers-telephony-ixj-fix-a-use-after-free.patch
drivers/telephony/ixj: fix a use after free
fs-attrc-fix-check-after-use.patch
fs/attr.c: fix check after use
fs-smbfs-requestc-fix-null-dereference.patch
fs/smbfs/request.c: fix NULL dereference
hfs-free-page-buffers-in-releasepage.patch
hfs: free page buffers in releasepage
hfs-fix-umask-behaviour.patch
hfs: fix umask behaviour
hfs-more-bnode-error-checks.patch
hfs: more bnode error checks
hfs-fix-sign-problem-in-hfs_ext_keycmp.patch
hfs: fix sign problem in hfs_ext_keycmp
hfs-use-parse-library-for-mount-options.patch
hfs: use parse library for mount options
hfs-add-nls-support.patch
hfs: add nls support
hfs-unicode-decompose-support.patch
hfs: unicode decompose support
inotify-42.patch
inotify #42
dvb-clarify-firmware-upload-messages.patch
dvb: clarify firmware upload messages
dvb-dibcom-frontend-fixes.patch
dvb: dibcom: frontend fixes
dvb-dibusb-misc-fixes.patch
dvb: dibusb: misc. fixes
dvb-skystar2-remove-duplicate-pci_release_region.patch
dvb: skystar2: remove duplicate pci_release_region()
dvb-mt352-pinnacle-300i-comments.patch
dvb: mt352: Pinnacle 300i comments
dvb-support-activy-budget-card.patch
dvb: support Activy Budget card
dvb-skystar2-update-email-address.patch
dvb: skystar2: update email address
dvb-ves1x93-invert_pwm-fix.patch
dvb: ves1x93: invert_pwm fix
dvb-dibusb-readme-update.patch
dvb: dibusb readme update
dvb-dibusb-support-hauppauge-wintv-nova-t-usb2.patch
dvb: dibusb: support Hauppauge WinTV NOVA-T USB2
dvb-nxt2002-qam64-256-support.patch
dvb: nxt2002: QAM64/256 support
dvb-get_dvb_firmware-new-unshield-version.patch
dvb: get_dvb_firmware: new unshield version
dvb-dib3000-corrected-device-naming.patch
dvb: dib3000: corrected device naming
dvb-dibusb-debug-changes.patch
dvb: dibusb: debug changes
dvb-dibusb-increased-the-number-of-urbs-for-usb11-devices.patch
dvb: dibusb: increased the number of urbs for usb1.1 devices
dvb-ttusb_dec-use-alternative-interface-to-save-bandwidth.patch
dvb: ttusb_dec: use alternative interface to save bandwidth
dvb-l64781-email-address-fix.patch
dvb: l64781: email address fix
dvb-skystar2-fix-mac-address-reading.patch
dvb: skystar2: fix MAC address reading
dvb-support-kworld-adstech-instant-dvb-t-usb20.patch
dvb: support KWorld/ADSTech Instant DVB-T USB2.0
dvb-cleanups-make-stuff-static.patch
dvb: cleanups, make stuff static
dvb-refactor-sw-pid-filter-to-drop-redundant-code.patch
dvb: refactor sw pid filter to drop redundant code
dvb-nxt2002-fix-max-frequency.patch
dvb: nxt2002: fix max frequency
dvb-ttusb-budget-s-usb_unlink_urb-usb_kill_urb.patch
dvb: ttusb-budget: s/usb_unlink_urb/usb_kill_urb/
dvb-av7110-fix-oops-when-av7110_ir_init-failed.patch
dvb: av7110: fix Oops when av7110_ir_init() failed
dvb-saa7146-static-initialization.patch
dvb: saa7146: static initialization
dvb-av7110-error-handling-during-attach.patch
dvb: av7110: error handling during attach
dvb-corrected-links-to-firmware-files.patch
dvb: corrected links to firmware files
dvb-support-pchdtv-hd2000.patch
dvb: support pcHDTV HD2000
dvb-dibusb-support-nova-t-usb-ir.patch
dvb: dibusb: support nova-t usb ir
dvb-oren-or51211-or51132_qam-and-or51132_vsb-firmware-download-info.patch
dvb: OREN or51211, or51132_qam and or51132_vsb firmware download info
dvb-ttusb_dec-ir-support.patch
dvb: ttusb_dec: IR support
dvb-dibusb-pll-fix.patch
dvb: dibusb: pll fix
dvb-tda10021-fix-continuity-errors.patch
dvb: tda10021: fix continuity errors
dvb-saa7146-remove-duplicate-setgpio.patch
dvb: saa7146: remove duplicate setgpio
dvb-fix-cams-on-typhoon-dvb-s.patch
dvb: fix CAMs on Typhoon DVB-S
dvb-frontends-kfree-cleanup.patch
dvb: frontends: kfree() cleanup
dvb-clear-up-confusion-between-ids-and-adapters.patch
dvb: clear up confusion between ids and adapters
dvb-dibusb-remove-useless-ifdef.patch
dvb: dibusb: remove useless ifdef
dvb-support-for-technotrend-pci-dvb-t.patch
dvb: support for Technotrend PCI DVB-T
dvb-dibusb-hanftek-umt-010-fixes.patch
dvb: dibusb: HanfTek UMT-010 fixes
dvb-vfree-checking-cleanups.patch
dvb: vfree() checking cleanups
dvb-convert-from-pci_module_init-to-pci_register_driver.patch
dvb: convert from pci_module_init to pci_register_driver
dvb-dibusb-support-dtt200u-yakumo-typhoon-hama-usb20-device.patch
dvb: dibusb: support dtt200u (Yakumo/Typhoon/Hama) USB2.0 device
dvb-sparse-warnings-on-one-bit-bitfields.patch
dvb: sparse warnings on one-bit bitfields
dvb-support-nova-s-rev-22.patch
dvb: support Nova-S rev 2.2
dvb-ttusb_dec-cleanup.patch
dvb: ttusb_dec: cleanup
dvb-gcc-295-compile-fixes.patch
dvb: gcc 2.95 compile fixes
dvb-mt352-cleanups.patch
dvb: mt352: cleanups
ext3-jbd-race-releasing-in-use-journal_heads.patch
ext3/jbd race: releasing in-use journal_heads
ext3-writepages-support-for-writeback-mode.patch
ext3 writepages support for writeback mode
ext3-writeback-nobh-option.patch
ext3 writeback "nobh" option
ext3-fix-journal_unmap_buffer-race.patch
ext3: fix journal_unmap_buffer race
ext3-dynamic-allocating-block-reservation-info.patch
ext3: dynamic allocation of block reservation info
ext3-reservation-info-cleanup-remove-rsv_seqlock.patch
ext3: reservation info cleanup: remove rsv_seqlock
ext3-reservation-info-cleanup-remove-rsv_seqlock-fix.patch
ext3-reservation-info-cleanup-remove-rsv_seqlock fix
ext3-move-goal-logical-block-into-block-allocation-info.patch
ext3: move goal logical block into block allocation info structure
pcmcia-hotplug-event-for-pcmcia-devices.patch
pcmcia: hotplug event for PCMCIA devices
pcmcia-hotplug-event-for-pcmcia-socket-devices.patch
pcmcia: hotplug event for PCMCIA socket devices
pcmcia-device-and-driver-matching.patch
pcmcia: device and driver matching
pcmcia-check-for-invalid-crc32-hashes-in-id_tables.patch
pcmcia: check for invalid crc32 hashes in id_tables
pcmcia-match-for-fake-cis.patch
pcmcia: match for fake CIS
pcmcia-export-cis-in-sysfs.patch
pcmcia: export CIS in sysfs
pcmcia-cis-overrid-via-sysfs.patch
pcmcia: CIS overrid via sysfs
pcmcia-match-anonymous-cards.patch
pcmcia: match "anonymous" cards
pcmcia-allow-function-id-based-match.patch
pcmcia: allow function-ID based match
pcmcia-file2alias.patch
pcmcia: file2alias
pcmcia-request-cis-via-firmware-interface.patch
pcmcia: request CIS via firmware interface
pcmcia-cleanups.patch
pcmcia: cleanups
pcmcia-rescan-bus-always-upon-echoing-into-setup_done.patch
pcmcia: rescan bus always upon echoing into setup_done
pcmcia-id_table-for-serial_cs.patch
pcmcia: id_table for serial_cs
pcmcia-id_table-for-3c574_cs.patch
pcmcia: id_table for 3c574_cs
pcmcia-id_table-for-3c589_cs.patch
pcmcia: id_table for 3c589_cs
pcmcia-id_table-for-aha152x.patch
pcmcia: id_table for aha152x
pcmcia-id_table-for-airo_cs.patch
pcmcia: id_table for airo_cs
pcmcia-id_table-for-axnet_cs.patch
pcmcia: id_table for axnet_cs
pcmcia-id_table-for-fdomain_stub.patch
pcmcia: id_table for fdomain_stub
pcmcia-id_table-for-fmvj18x_cs.patch
pcmcia: id_table for fmvj18x_cs
pcmcia-id_table-for-ibmtr_cs.patch
pcmcia: id_table for ibmtr_cs
pcmcia-id_table-for-netwave_cs.patch
pcmcia: id_table for netwave_cs
pcmcia-id_table-for-nmclan_cs.patch
pcmcia: id_table for nmclan_cs
pcmcia-id_table-for-teles_cs.patch
pcmcia: id_table for teles_cs
pcmcia-id_table-for-ray_cs.patch
pcmcia: id_table for ray_cs
pcmcia-id_table-for-wavelan_cs.patch
pcmcia: id_table for wavelan_cs
pcmcia-id_table-for-sym53c500_csc.patch
pcmcia: id_table for sym53c500_cs.c
pcmcia-id_table-for-qlogic_stubc.patch
pcmcia: id_table for qlogic_stub.c
pcmcia-id_table-for-smc91c92_csc.patch
pcmcia: id_table for smc91c92_cs.c
pcmcia-id_table-for-orinoco_cs.patch
pcmcia: id_table for orinoco_cs
pcmcia-id_table-for-xirc2ps_csc.patch
pcmcia: id_table for xirc2ps_cs.c
pcmcia-id_table-for-ide_csc.patch
pcmcia: id_table for ide_cs.c
pcmcia-id_table-for-parport_csc.patch
pcmcia: id_table for parport_cs.c
pcmcia-id_table-for-pcnet_csc.patch
pcmcia: id_table for pcnet_cs.c
pcmcia-id_table-for-pcmciamtdc.patch
pcmcia: id_table for pcmciamtd.c
pcmcia-id_table-for-vxpocketc.patch
pcmcia: id_table for vxpocket.c
pcmcia-id_table-for-atmel_csc.patch
pcmcia: id_table for atmel_cs.c
pcmcia-id_table-for-avma1_csc.patch
pcmcia: id_table for avma1_cs.c
pcmcia-id_table-for-avm_csc.patch
pcmcia: id_table for avm_cs.c
pcmcia-id_table-for-bluecard_csc.patch
pcmcia: id_table for bluecard_cs.c
pcmcia-id_table-for-bt3c_csc.patch
pcmcia: id_table for bt3c_cs.c
pcmcia-id_table-for-btuart_csc.patch
pcmcia: id_table for btuart_cs.c
pcmcia-id_table-for-com20020_csc.patch
pcmcia: id_table for com20020_cs.c
pcmcia-id_table-for-dtl1_csc.patch
pcmcia: id_table for dtl1_cs.c
pcmcia-id_table-for-elsa_csc.patch
pcmcia: id_table for elsa_cs.c
pcmcia-id_table-for-ixj_pcmciac.patch
pcmcia: id_table for ixj_pcmcia.c
pcmcia-id_table-for-nsp_csc.patch
pcmcia: id_table for nsp_cs.c
pcmcia-id_table-for-sedlbauer_csc.patch
pcmcia: id_table for sedlbauer_cs.c
pcmcia-id_table-for-wl3501_csc.patch
pcmcia: id_table for wl3501_cs.c
pcmcia-id_table-for-pdaudiocfc.patch
pcmcia: id_table for pdaudiocf.c
pcmcia-id_table-for-synclink_csc.patch
pcmcia: id_table for synclink_cs.c
pcmcia-add-some-documentation.patch
pcmcia: add some Documentation
pcmcia-update-resource-database-adjust-routines-to-use-unsigned-long-values.patch
pcmcia: update resource database adjust routines to use unsigned long values
pcmcia-mark-parent-bridge-windows-as-resources-available-for-pcmcia-devices.patch
pcmcia: mark parent bridge windows as resources available for PCMCIA devices
pcmcia-add-a-config-option-for-the-pcmica-ioctl.patch
pcmcia: add a config option for the PCMICA ioctl
pcmcia-move-pcmcia-ioctl-to-a-separate-file.patch
pcmcia: move PCMCIA ioctl to a separate file
pcmcia-clean-up-cs-ds-callback.patch
pcmcia: clean up cs ds callback
pcmcia-clean-up-cs-ds-callback-fix.patch
pcmcia-clean-up-cs-ds-callback-fix
pcmcia-make-pcmcia-status-a-bitfield.patch
pcmcia: make PCMCIA status a bitfield
pcmcia-merge-struct-pcmcia_bus_socket-into-struct-pcmcia_socket.patch
pcmcia: merge struct pcmcia_bus_socket into struct pcmcia_socket
pcmcia-remove-unneeded-includes-in-dsc.patch
pcmcia: remove unneeded includes in ds.c
pcmcia-rename-some-functions.patch
pcmcia: rename some functions
pcmcia-move-pcmcia-resource-handling-out-of-csc.patch
pcmcia: move pcmcia resource handling out of cs.c
pcmcia-csc-cleanup.patch
pcmcia: cs.c cleanup
pcmcia-dsc-cleanup.patch
pcmcia: ds.c cleanup
pcmcia-release_class.patch
pcmcia: release_class
pcmcia-use-request_region-in-i82365.patch
pcmcia: use request_region in i82365
pcmcia-synclink_cs-irq_info2_info-is-gone.patch
pcmcia: synclink_cs IRQ_INFO2_INFO is gone
pcmcia-mod_devicetableh-fix-for-different-sizes-in-kernel-and-userspace.patch
pcmcia: mod_devicetable.h fix for different sizes in kernel- and userspace
pcmcia-select-crc32-in-kconfig-for-pcmcia.patch
pcmcia: select crc32 in Kconfig for PCMCIA
svcrpc-auth_domain-documentation.patch
svcrpc: auth_domain documentation
nfsd4-fix-share-conflict-tests.patch
nfsd4: fix share conflict tests
nfsd4-remove-unneeded-stateowner-arguments.patch
nfsd4: remove unneeded stateowner arguments
nfsd4-fix-use-after-put-in-cb_recall.patch
nfsd4: fix use after put() in cb_recall
nfsd4-allow-read-on-open-for-write.patch
nfsd4: allow read on open for write
nfsd4-factor-out-common-open_truncate-code.patch
nfsd4: factor out common open_truncate code
nfsd4-fix-failure-to-truncate-on-some-opens.patch
nfsd4: fix failure to truncate on some opens
nfsd4_remove_unused_acl_function.patch
nfsd4_remove_unused_acl_function
nfsd4-dont-set-write_owner-in-either-allow-or-deny-bits.patch
nfsd4: don't set WRITE_OWNER in either allow or deny bits
nfsd4-acl-dont-set-named-attrs.patch
nfsd4: acl don't set named attrs
nfsd4-acl-error-fix.patch
nfsd4: acl error fix
nfsd4-rename-release_delegation.patch
nfsd4: rename release_delegation
nfsd4-remove-trailing-whitespace-from-nfs4procc.patch
nfsd4: remove trailing whitespace from nfs4proc.c
nfsd4-fix-open-returns-for-other-claim-types.patch
nfsd4: fix open returns for other claim types
nfsd4-fix-indentation-in-nfsd4_open.patch
nfsd4: fix indentation in nfsd4_open
nfsacl-solaris-nfsacl-workaround.patch
nfsacl: Solaris nfsacl workaround
kgdb-ga.patch
kgdb stub for ia32 (George Anzinger's one)
kgdbL warning fix
kgdb buffer overflow fix
kgdbL warning fix
kgdb: CONFIG_DEBUG_INFO fix
x86_64 fixes
correct kgdb.txt Documentation link (against 2.6.1-rc1-mm2)
kgdb: fix for recent gcc
kgdb warning fixes
THREAD_SIZE fixes for kgdb
Fix stack overflow test for non-8k stacks
kgdb-ga.patch fix for i386 single-step into sysenter
fix TRAP_BAD_SYSCALL_EXITS on i386
add TRAP_BAD_SYSCALL_EXITS config for i386
kgdb-is-incompatible-with-kprobes
kgdb-ga-build-fix
kgdb-ga-fixes
kgdb: kill off highmem_start_page
kgdb documentation fix
kgdb-x86-config_debug_info-fix.patch
kgdb CONFIG_DEBUG_INFO fix
kgdboe-netpoll.patch
kgdb-over-ethernet via netpoll
kgdboe: fix configuration of MAC address
kgdb-x86_64-support.patch
kgdb-x86_64-support.patch for 2.6.2-rc1-mm3
kgdb-x86_64-warning-fixes
kgdb-x86_64-fix
kgdb-x86_64-serial-fix
kprobes exception notifier fix
kgdb-x86_64-config_debug_info-fix.patch
kgdb CONFIG_DEBUG_INFO fix
rock-lindent.patch
rock: lindent it
rock-manual-tidies.patch
rock: manual tidies
rock-remove-CHECK_SP.patch
rock: remove CHECK_SP
rock-remove-CONTINUE_DECLS.patch
rock: remove CONTINUE_DECLS
rock-remove-CHECK_CE.patch
rock: remove CHECK_CE
rock-remove-SETUP_ROCK_RIDGE.patch
rock: remove SETUP_ROCK_RIDGE
rock-remove-MAYBE_CONTINUE.patch
rock: remove MAYBE_CONTINUE
rock-comment-tidies.patch
rock: comment tidies
rock-lindent-rock-h.patch
rock: lindent rock.h
isofs-remove-debug-stuff.patch
isofs: remove debug stuff
rock-handle-corrupted-directories.patch
rock.c: handle corrupted directories
rock-rename-union-members.patch
rock: rename union members
rock-handle-directory-overflows.patch
rock: handle directory overflows
journal_add_journal_head-debug.patch
journal_add_journal_head-debug
list_del-debug.patch
list_del debug check
page-owner-tracking-leak-detector.patch
Page owner tracking leak detector
make-page_owner-handle-non-contiguous-page-ranges.patch
make page_owner handle non-contiguous page ranges
add-gfp_mask-to-page-owner.patch
add gfp_mask to page owner
unplug-can-sleep.patch
unplug functions can sleep
firestream-warnings.patch
firestream warnings
periodically-scan-redzone-entries-and-slab-control-structures.patch
periodically scan redzone entries and slab control structures
slab-leak-detector.patch
slab leak detector
slab-leak-detector-warning-fixes.patch
slab leak detector warning fixes
irqpoll.patch
irqpoll
figure-out-who-is-inserting-bogus-modules.patch
Figure out who is inserting bogus modules
figure-out-who-is-inserting-bogus-modules-warning-fix.patch
Warning fix and be extra careful about array in kernel/module.c
releasing-resources-with-children.patch
Releasing resources with children
perfctr-core.patch
perfctr: core
perfctr: remove bogus perfctr_sample_thread() calls
perfctr-i386.patch
perfctr: i386
perfctr-x86-core-updates.patch
perfctr x86 core updates
perfctr-x86-driver-updates.patch
perfctr x86 driver updates
perfctr-x86-driver-cleanup.patch
perfctr: x86 driver cleanup
perfctr-prescott-fix.patch
Prescott fix for perfctr
perfctr-x86-update-2.patch
perfctr x86 update 2
perfctr-x86_64.patch
perfctr: x86_64
perfctr-x86_64-core-updates.patch
perfctr x86_64 core updates
perfctr-ppc.patch
perfctr: PowerPC
perfctr-ppc32-driver-update.patch
perfctr: ppc32 driver update
perfctr-ppc32-mmcr0-handling-fixes.patch
perfctr ppc32 MMCR0 handling fixes
perfctr-ppc32-update.patch
perfctr ppc32 update
perfctr-ppc32-update-2.patch
perfctr ppc32 update
perfctr-virtualised-counters.patch
perfctr: virtualised counters
perfctr-remap_page_range-fix.patch
virtual-perfctr-illegal-sleep.patch
virtual perfctr illegal sleep
make-perfctr_virtual-default-in-kconfig-match-recommendation.patch
Make PERFCTR_VIRTUAL default in Kconfig match recommendation in help text
perfctr-ifdef-cleanup.patch
perfctr ifdef cleanup
perfctr-update-2-6-kconfig-related-updates.patch
perfctr: Kconfig-related updates
perfctr-virtual-updates.patch
perfctr virtual updates
perfctr-virtual-cleanup.patch
perfctr: virtual cleanup
perfctr-ppc32-preliminary-interrupt-support.patch
perfctr ppc32 preliminary interrupt support
perfctr-update-5-6-reduce-stack-usage.patch
perfctr: reduce stack usage
perfctr-interrupt-support-kconfig-fix.patch
perfctr interrupt_support Kconfig fix
perfctr-low-level-documentation.patch
perfctr low-level documentation
perfctr-inheritance-1-3-driver-updates.patch
perfctr inheritance: driver updates
perfctr-inheritance-2-3-kernel-updates.patch
perfctr inheritance: kernel updates
perfctr-inheritance-3-3-documentation-updates.patch
perfctr inheritance: documentation updates
perfctr-inheritance-locking-fix.patch
perfctr inheritance locking fix
perfctr-api-changes-first-step.patch
perfctr API changes: first step
perfctr-virtual-update.patch
perfctr virtual update
perfctr-x86-64-ia32-emulation-fix.patch
perfctr x86-64 ia32 emulation fix
perfctr-sysfs-update-1-4-core.patch
perfctr sysfs update: core
perfctr-sysfs-update.patch
Perfctr sysfs update
perfctr-sysfs-update-2-4-x86.patch
perfctr sysfs update: x86
perfctr-sysfs-update-3-4-x86-64.patch
perfctr sysfs update: x86-64
perfctr: syscall numbers in x86-64 ia32-emulation
perfctr x86_64 native syscall numbers fix
perfctr-sysfs-update-4-4-ppc32.patch
perfctr sysfs update: ppc32
perfctr-2710-api-update-1-4-common.patch
perfctr-2.7.10 API update 1/4: common
perfctr-2710-api-update-2-4-i386.patch
perfctr-2.7.10 API update 2/4: i386
perfctr-2710-api-update-3-4-x86_64.patch
perfctr-2.7.10 API update 3/4: x86_64
perfctr-2710-api-update-4-4-ppc32.patch
perfctr-2.7.10 API update 4/4: ppc32
perfctr-api-update-1-9-physical-indexing-x86.patch
perfctr API update 1/9: physical indexing, x86
perfctr-api-update-2-9-physical-indexing-ppc32.patch
perfctr API update 2/9: physical indexing, ppc32
perfctr-api-update-3-9-cpu_control_header-x86.patch
perfctr API update 3/9: cpu_control_header, x86
perfctr-api-update-4-9-cpu_control_header-ppc32.patch
perfctr API update 4/9: cpu_control_header, ppc32
perfctr-api-update-5-9-cpu_control_header-common.patch
perfctr API update 5/9: cpu_control_header, common
perfctr-api-update-6-9-cpu_control-access-common.patch
perfctr API update 6/9: cpu_control access, common
perfctr-api-update-7-9-cpu_control-access-x86.patch
perfctr API update 7/9: cpu_control access, x86
perfctr-api-update-8-9-cpu_control-access-ppc32.patch
perfctr API update 8/9: cpu_control access, ppc32
perfctr-api-update-9-9-domain-based-read-write-syscalls.patch
perfctr API update 9/9: domain-based read/write syscalls
perfctr-ia32-syscalls-on-x86-64-fix.patch
perfctr ia32 syscalls on x86-64 fix
perfctr-cleanups-1-3-common.patch
perfctr cleanups: common
perfctr-cleanups-2-3-ppc32.patch
perfctr cleanups: ppc32
perfctr-cleanups-3-3-x86.patch
perfctr cleanups: x86
perfctr-x86-fix-and-cleanups.patch
perfctr: x86 fix and cleanups
perfctr-ppc32-fix-and-cleanups.patch
perfctr: ppc32 fix and cleanups
perfctr-64-bit-values-in-register-descriptors.patch
perfctr: 64-bit values in register descriptors
perfctr-64-bit-values-in-register-descriptors-fix.patch
perfctr-64-bit-values-in-register-descriptors fix
sched2-fix-schedstats-warning.patch
sched: fix schedstats warning
sched2-cleanup-wake_idle.patch
sched: cleanup wake_idle
sched2-improve-load-balancing-pinned-tasks.patch
sched: improve load balancing pinned tasks
sched2-reduce-active-load-balancing.patch
sched: reduce active load balancing
sched2-fix-smt-scheduling-problems.patch
sched: fix SMT scheduling problems
sched2-add-debugging.patch
sched: add debugging
sched2-less-aggressive-idle-balancing.patch
sched: less aggressive idle balancing
sched2-balance-timers.patch
sched: balance timers
sched2-tweak-affine-wakeups.patch
sched: tweak affine wakeups
sched2-no-aggressive-idle-balancing.patch
sched: no aggressive idle balancing
sched2-balance-on-fork.patch
sched: balance on fork
sched2-schedstats-update-for-balance-on-fork.patch
sched: schedstats update for balance on fork
sched2-sched-tuning.patch
sched: sched tuning
sched2-sched-tuning-fix.patch
sched2-sched-tuning-fix
sched2-sched-domain-sysctl.patch
sched: sched domain sysctl
sched-uninline-task_timeslice.patch
sched: uninline task_timeslice
add-do_proc_doulonglongvec_minmax-to-sysctl-functions.patch
Add do_proc_doulonglongvec_minmax to sysctl functions
add-do_proc_doulonglongvec_minmax-to-sysctl-functions-fix
add-do_proc_doulonglongvec_minmax-to-sysctl-functions fix 2
allow-x86_64-to-reenable-interrupts-on-contention.patch
Allow x86_64 to reenable interrupts on contention
i386-cpu-hotplug-updated-for-mm.patch
i386 CPU hotplug updated for -mm
ppc64: fix hotplug cpu
disable-atykb-warning.patch
disable atykb "too many keys pressed" warning
export-file_ra_state_init-again.patch
Export file_ra_state_init() again
cachefs-filesystem.patch
CacheFS filesystem
numa-policies-for-file-mappings-mpol_mf_move-cachefs.patch
numa-policies-for-file-mappings-mpol_mf_move for cachefs
cachefs-release-search-records-lest-they-return-to-haunt-us.patch
CacheFS: release search records lest they return to haunt us
fix-64-bit-problems-in-cachefs.patch
Fix 64-bit problems in cachefs
cachefs-fixed-typos-that-cause-wrong-pointer-to-be-kunmapped.patch
cachefs: fixed typos that cause wrong pointer to be kunmapped
cachefs-return-the-right-error-upon-invalid-mount.patch
CacheFS: return the right error upon invalid mount
fix-cachefs-barrier-handling-and-other-kernel-discrepancies.patch
Fix CacheFS barrier handling and other kernel discrepancies
remove-error-from-linux-cachefsh.patch
Remove #error from linux/cachefs.h
cachefs-warning-fix-2.patch
cachefs warning fix 2
cachefs-linkage-fix-2.patch
cachefs linkage fix
cachefs-build-fix.patch
cachefs build fix
cachefs-documentation.patch
CacheFS documentation
add-page-becoming-writable-notification.patch
Add page becoming writable notification
add-page-becoming-writable-notification-fix.patch
do_wp_page_mk_pte_writable() fix
add-page-becoming-writable-notification-build-fix.patch
add-page-becoming-writable-notification build fix
provide-a-filesystem-specific-syncable-page-bit.patch
Provide a filesystem-specific sync'able page bit
provide-a-filesystem-specific-syncable-page-bit-fix.patch
provide-a-filesystem-specific-syncable-page-bit-fix
provide-a-filesystem-specific-syncable-page-bit-fix-2.patch
provide-a-filesystem-specific-syncable-page-bit-fix-2
make-afs-use-cachefs.patch
Make AFS use CacheFS
afs-cachefs-dependency-fix.patch
afs-cachefs-dependency-fix
split-general-cache-manager-from-cachefs.patch
Split general cache manager from CacheFS
turn-cachefs-into-a-cache-backend.patch
Turn CacheFS into a cache backend
rework-the-cachefs-documentation-to-reflect-fs-cache-split.patch
Rework the CacheFS documentation to reflect FS-Cache split
update-afs-client-to-reflect-cachefs-split.patch
Update AFS client to reflect CacheFS split
fscache-menuconfig-help-fix-documentation-path.patch
fscache-menuconfig-help-fix-documentation-pathc
x86-rename-apic_mode_exint.patch
kexec: x86: rename APIC_MODE_EXINT
x86-local-apic-fix.patch
kexec: x86: local apic fix
x86_64-e820-64bit.patch
kexec: x86_64: e820 64bit fix
x86-i8259-shutdown.patch
kexec: x86: i8259 shutdown: disable interrupts
x86_64-i8259-shutdown.patch
kexec: x86_64: add i8259 shutdown method
x86-apic-virtwire-on-shutdown.patch
kexec: x86: resture apic virtual wire mode on shutdown
x86_64-apic-virtwire-on-shutdown.patch
kexec: x86_64: restore apic virtual wire mode on shutdown
vmlinux-fix-physical-addrs.patch
kexec: vmlinux: fix physical addresses
x86-vmlinux-fix-physical-addrs.patch
kexec: x86: vmlinux: fix physical addresses
x86_64-vmlinux-fix-physical-addrs.patch
kexec: x86_64: vmlinux: fix physical addresses
x86-config-kernel-start.patch
kexec: x86: add CONFIG_PYSICAL_START
kexec-reserve-bootmem-fix-for-booting-nondefault-location-kernel.patch
kexec: reserve Bootmem fix for booting nondefault location kernel
x86_64-config-kernel-start.patch
kexec: x86_64: add CONFIG_PHYSICAL_START
kexec-kexec-generic.patch
kexec: add kexec syscalls
kexec-kexec-generic-kexec-use-unsigned-bitfield.patch
kexec: use unsigned bitfield
x86-machine_shutdown.patch
kexec: x86: factor out apic shutdown code
x86-kexec.patch
kexec: x86 kexec core
x86-crashkernel.patch
crashdump: x86 crashkernel option
x86-crashkernel-fix.patch
kexec: fix for broken kexec on panic
x86_64-machine_shutdown.patch
kexec: x86_64: factor out apic shutdown code
x86_64-kexec.patch
kexec: x86_64 kexec implementation
x86_64-crashkernel.patch
crashdump: x86_64: crashkernel option
kexec-ppc-support.patch
kexec: kexec ppc support
kexec-ppc-fix-noret_type.patch
kexec: ppc: fix NORET_TYPE
x86-crash_shutdown-nmi-shootdown.patch
crashdump: x86: add NMI handler to capture other CPUs
x86-crash_shutdown-snapshot-registers.patch
kexec: x86: snapshot registers during crash shutdown
x86-crash_shutdown-apic-shutdown.patch
kexec: x86 shutdown APICs during crash_shutdown
crashdump-documentation.patch
crashdump: documentation
crashdump-memory-preserving-reboot-using-kexec.patch
crashdump: memory preserving reboot using kexec
crashdump-routines-for-copying-dump-pages.patch
crashdump: routines for copying dump pages
crashdump-routines-for-copying-dump-pages-fixes.patch
crashdump-routines-for-copying-dump-pages-fixes
crashdump-elf-format-dump-file-access.patch
crashdump: elf format dump file access
crashdump-linear-raw-format-dump-file-access.patch
crashdump: linear raw format dump file access
crashdump-linear-raw-format-dump-file-access-coding-style.patch
crashdump-linear-raw-format-dump-file-access-coding-style
kdump-export-crash-notes-section-address-through.patch
Kdump: Export crash notes section address through sysfs
kdump-export-crash-notes-section-address-through-build-fix.patch
kdump-export-crash-notes-section-address-through build fix
kdump-export-crash-notes-section-address-through-x86_64-fix.patch
kdump-export-crash-notes-section-address-through x86_64 fix
reiser4-sb_sync_inodes.patch
reiser4: vfs: add super_operations.sync_inodes()
reiser4-allow-drop_inode-implementation.patch
reiser4: export vfs inode.c symbols
reiser4-truncate_inode_pages_range.patch
reiser4: vfs: add truncate_inode_pages_range()
reiser4-export-remove_from_page_cache.patch
reiser4: export pagecache add/remove functions to modules
reiser4-export-page_cache_readahead.patch
reiser4: export page_cache_readahead to modules
reiser4-reget-page-mapping.patch
reiser4: vfs: re-check page->mapping after calling try_to_release_page()
reiser4-rcu-barrier.patch
reiser4: add rcu_barrier() synchronization point
reiser4-rcu-barrier-license-fix.patch
reiser4-rcu-barrier-license-fix
reiser4-export-inode_lock.patch
reiser4: export inode_lock to modules
reiser4-export-inode_lock-unexport-__iget.patch
reiser4-export-inode_lock-unexport-__iget
reiser4-export-pagevec-funcs.patch
reiser4: export pagevec functions to modules
reiser4-export-radix_tree_preload.patch
reiser4: export radix_tree_preload() to modules
reiser4-export-find_get_pages.patch
reiser4-radix_tree_lookup_slot.patch
reiser4: add radix_tree_lookup_slot()
reiser4-perthread-pages.patch
reiser4: per-thread page pools
reiser4-perthread_pages_alloc-cleanup.patch
perthread_pages_alloc cleanup
reiser4-include-reiser4.patch
reiser4: add to build system
reiser4-doc.patch
reiser4: documentation
reiser4-only.patch
reiser4: main fs
fs-reiser4-possible-cleanups.patch
fs/reiser4/: possible cleanups
reiser4-kconfig-help-cleanup.patch
reiser4 Kconfig help cleanup
reiser4-cleanup-pg_arch_1.patch
reiser4 cleanup (PG_arch_1)
reiser4-build-fix.patch
reiser4 build fix
reiser4-update.patch
reiser4 update
reiser4-only-memory_backed-fix.patch
reiser4-only-memory_backed-fix
add-acpi-based-floppy-controller-enumeration.patch
Add ACPI-based floppy controller enumeration.
possible-dcache-bug-debugging-patch.patch
Possible dcache BUG: debugging patch
serial-add-support-for-non-standard-xtals-to-16c950-driver.patch
serial: add support for non-standard XTALs to 16c950 driver
add-support-for-possio-gcc-aka-pcmcia-siemens-mc45.patch
Add support for Possio GCC AKA PCMCIA Siemens MC45
generic-serial-cli-conversion.patch
generic-serial cli() conversion
specialix-io8-cli-conversion.patch
Specialix/IO8 cli() conversion
sx-cli-conversion.patch
SX cli() conversion
au1x00_uart-deadlock-fix.patch
au1x00_uart deadlock fix
remove-lock_section-from-x86_64-spin_lock-asm.patch
remove LOCK_SECTION from x86_64 spin_lock asm
kfree_skb-dump_stack.patch
kfree_skb-dump_stack
minimal-ide-disk-updates.patch
Minimal ide-disk updates
vt-dont-call-unblank-at-irq-time.patch
vt: don't call unblank at irq time
ppc32-move-powermac-backlight-stuff-to-a-workqueue.patch
ppc32: move powermac backlight stuff to a workqueue
radeonfb-implement-proper-workarounds-for-pll-accesses.patch
radeonfb: Implement proper workarounds for PLL accesses
radeonfb-ddc-i2c-fix.patch
radeonfb: DDC i2c fix
fbdev-nvidia-licensing-clarification.patch
fbdev: mvidia licensing clarification
fbcon-stop-framebuffer-operations-before-hardware-is-properly-initialized.patch
fbcon: Stop framebuffer operations before hardware is properly initialized
nvidiafb-maximize-blit-buffer-capacity.patch
nvidiafb: Maximize blit buffer capacity
pm2fb-x-and-vt-switching-crash-fix.patch
pm2fb: X and VT switching crash fix
nvidiafb-kconfig-help-text-update-for-config-fb_nvidia.patch
nvidiafb: Kconfig help text update for config FB_NVIDIA
fbdev-cleanups-in-drivers-video-part-2.patch
fbdev: Cleanups in drivers/video part 2
fbdev-cleanups-in-drivers-video-part-2-fix.patch
fbdev-cleanups-in-drivers-video-part-2 fix
excessive-atyfb-debug-messages.patch
Excessive atyfb debug messages
atyfb-add-boot-module-option-to-override-composite-sync.patch
atyfb: Add boot/module option to override composite sync
fbdev-kconfig-fix-for-macmodes-and-ppc.patch
fbdev: Kconfig fix for macmodes and PPC
fbdev-convert-drivers-to-pci_register_driver.patch
fbdev: Convert drivers to pci_register_driver
sisfb-trivial-cleanups.patch
sisfb: Trivial cleanups
tridentfb-clean-up-printks.patch
tridentfb: Clean up printk()'s
s1d13xxxfb-add-support-for-epson-s1d13806-fb.patch
s1d13xxxfb: Add support for Epson S1D13806 FB
nvidiafb-process-boot-options-earlier.patch
nvidiafb: Process boot options earlier
fbcon-save-var-rotate-field-in-struct-display.patch
fbcon: Save var rotate field in struct display
fbcon-call-set_par-per-fb_info-once-during-init.patch
fbcon: Call set_par per fb_info once during init
fbcon-do-not-set-palette-if-console-is-not-visible.patch
fbcon: Do not set palette if console is not visible
nvidiafb-delete-i2c-bus-on-driver-unload.patch
nvidiafb: Delete i2c bus on driver unload
neofb-mmio-fixes.patch
neofb: mmio fixes
neofb-set-hwaccel-flags-properly.patch
neofb: Set hwaccel flags properly
remove-redundant-null-checks-before-kfree-in-drivers-video.patch
remove redundant NULL checks before kfree() in drivers/video/
remove-redundant-null-checks-before-kfree-in-drivers-video-fix.patch
remove-redundant-null-checks-before-kfree-in-drivers-video fix
md-merge-md_enter_safemode-into-md_check_recovery.patch
md: merge md_enter_safemode into md_check_recovery
md-improve-locking-on-safemode-and-move-superblock-writes.patch
md: improve locking on 'safemode' and move superblock writes
md-improve-the-interface-to-sync_request.patch
md: improve the interface to sync_request
md-optimised-resync-using-bitmap-based-intent-logging.patch
md: optimised resync using Bitmap based intent logging
md-a-couple-of-tidyups-relating-to-the-bitmap-file.patch
md: a couple of tidyups relating to the bitmap file.
md-call-bitmap_daemon_work-regularly.patch
md: call bitmap_daemon_work regularly
md-print-correct-pid-for-newly-created-bitmap-writeback-daemon.patch
md: print correct pid for newly created bitmap-writeback-daemon.
md-minor-code-rearrangement-in-bitmap_init_from_disk.patch
md: minor code rearrangement in bitmap_init_from_disk
md-make-sure-md-bitmap-is-cleared-on-a-clean-start.patch
md: make sure md bitmap is cleared on a clean start.
md-printk-fix.patch
md printk fix
md-improve-debug-printing-of-bitmap-superblock.patch
md: improve debug-printing of bitmap superblock.
md-check-return-value-of-write_page-rather-than-ignore-it.patch
md: check return value of write_page, rather than ignore it
md-enable-the-bitmap-write-back-daemon-and-wait-for-it.patch
md: enable the bitmap write-back daemon and wait for it.
md-dont-skip-bitmap-pages-due-to-lack-of-bit-that-we-just-cleared.patch
md: don't skip bitmap pages due to lack of bit that we just cleared.
md-optimised-resync-using-bitmap-based-intent-logging-fix.patch
md-optimised-resync-using-bitmap-based-intent-logging fix
md-raid1-support-for-bitmap-intent-logging.patch
md: raid1 support for bitmap intent logging
md-fix-bug-when-raid1-attempts-a-partial-reconstruct.patch
md: fix bug when raid1 attempts a partial reconstruct.
md-raid1-support-for-bitmap-intent-logging-fix.patch
md: initialise sync_blocks in raid1 resync
md-optimise-reconstruction-when-re-adding-a-recently-failed-drive.patch
md: optimise reconstruction when re-adding a recently failed drive.
md-fix-deadlock-due-to-md-thread-processing-delayed-requests.patch
md: fix deadlock due to md thread processing delayed requests.
md-allow-md-intent-bitmap-to-be-stored-near-the-superblock.patch
md: allow md intent bitmap to be stored near the superblock.
md-allow-md-to-update-multiple-superblocks-in-parallel.patch
md: allow md to update multiple superblocks in parallel.
detect-atomic-counter-underflows.patch
detect atomic counter underflows
doc-where-to-find-ldd3.patch
doc: where to find LDD3
post-halloween-doc.patch
post halloween doc
fuse-maintainers-kconfig-and-makefile-changes.patch
FUSE - MAINTAINERS, Kconfig and Makefile changes
fuse-core.patch
FUSE - core
fuse-device-functions.patch
FUSE - device functions
fuse-device-functions-comments-and-documentation.patch
FUSE: comments and documentation
fuse-device-functions-cleanup.patch
FUSE: trivial cleanups
fuse-read-only-operations.patch
FUSE - read-only operations
fuse-read-write-operations.patch
FUSE - read-write operations
fuse-file-operations.patch
FUSE - file operations
fuse-mount-options.patch
FUSE - mount options
fuse-mount-options-fix.patch
fuse: fix busy inodes after unmount
fuse-mount-options-comments-and-documentation.patch
FUSE: comments and documentation
fuse-mount-options-fix-cleanup.patch
FUSE: trivial cleanups
fuse-mount-options-fix-fix.patch
FUSE: fix locking for background list
fuse-extended-attribute-operations.patch
FUSE - extended attribute operations
fuse-readpages-operation.patch
FUSE - readpages operation
fuse-nfs-export.patch
FUSE - NFS export
fuse-direct-i-o.patch
FUSE - direct I/O
fuse-transfer-readdir-data-through-device.patch
fuse: transfer readdir data through device
drivers-isdn-divert-isdn_divertc-make-5-functions-static.patch
drivers/isdn/divert/isdn_divert.c: make 5 functions static
drivers-isdn-capi-make-some-code-static.patch
drivers/isdn/capi/: make some code static
drivers-scsi-pas16c-make-code-static.patch
drivers/scsi/pas16.c: make code static
fix-pm_message_t-in-generic-code.patch
Fix pm_message_t in generic code
fix-u32-vs-pm_message_t-in-usb.patch
Fix u32 vs. pm_message_t in USB
more-pm_message_t-fixes.patch
more pm_message_t fixes
fix-u32-vs-pm_message_t-confusion-in-oss.patch
Fix u32 vs. pm_message_t confusion in OSS
fix-u32-vs-pm_message_t-confusion-in-pcmcia.patch
Fix u32 vs. pm_message_t confusion in PCMCIA
fix-u32-vs-pm_message_t-confusion-in-framebuffers.patch
Fix u32 vs. pm_message_t confusion in framebuffers
fix-u32-vs-pm_message_t-confusion-in-mmc.patch
Fix u32 vs. pm_message_t confusion in MMC
fix-u32-vs-pm_message_t-confusion-in-serials.patch
Fix u32 vs. pm_message_t confusion in serials
fix-u32-vs-pm_message_t-in-macintosh.patch
Fix u32 vs. pm_message_t in macintosh
fix-u32-vs-pm_message_t-confusion-in-agp.patch
Fix u32 vs. pm_message_t confusion in AGP
cyrix-eliminate-bad-section-references.patch
cyrix: eliminate bad section references
drivers-media-video-tvaudioc-make-some-variables-static.patch
drivers/media/video/tvaudio.c: make some variables static
drivers-isdn-sc-possible-cleanups.patch
drivers/isdn/sc/: possible cleanups
drivers-isdn-pcbit-possible-cleanups.patch
drivers/isdn/pcbit/: possible cleanups
drivers-isdn-i4l-possible-cleanups.patch
drivers/isdn/i4l/: possible cleanups
unexport-mca_find_device_by_slot.patch
unexport mca_find_device_by_slot
drivers-isdn-hardware-avm-misc-cleanups.patch
drivers/isdn/hardware/avm/: misc cleanups
drivers-isdn-act2000-capic-if-0-an-unused-function.patch
drivers/isdn/act2000/capi.c: #if 0 an unused function
tpm-fix-gcc-printk-warnings.patch
tpm: fix gcc printk warnings
x86-64-add-memcpy-memset-prototypes.patch
x86-64: add memcpy/memset prototypes
au1100fb-convert-to-c99-inits.patch
au1100fb: convert to C99 inits.
reiserfs-use-null-instead-of-0.patch
reiserfs: use NULL instead of 0
comments-on-locking-of-task-comm.patch
comments on locking of task->comm
riottyc-cleanups-and-warning-fix.patch
riotty.c cleanups and warning fix
fixup-a-comment-still-refering-to-verify_area.patch
fix up a comment still refering to verify_area
char-ds1620-use-msleep-instead-of-schedule_timeout.patch
char/ds1620: use msleep() instead of schedule_timeout()
char-tty_io-replace-schedule_timeout-with-msleep_interruptible.patch
char/tty_io: replace schedule_timeout() with msleep_interruptible()
kernel-timer-fix-msleep_interruptible-comment.patch
kernel/timer: fix msleep_interruptible() comment
ixj-compile-warning-cleanup.patch
ixj* - compile warning cleanup
spelling-cleanups-in-shrinker-code.patch
Spelling cleanups in shrinker code
init-do_mounts_initrdc-fix-sparse-warning.patch
init/do_mounts_initrd.c: fix sparse warning
arch-i386-kernel-trapsc-fix-sparse-warnings.patch
arch/i386/kernel/traps.c: fix sparse warnings
arch-i386-kernel-apmc-fix-sparse-warnings.patch
arch/i386/kernel/apm.c: fix sparse warnings
arch-i386-mm-faultc-fix-sparse-warnings.patch
arch/i386/mm/fault.c: fix sparse warnings
arch-i386-crypto-aesc-fix-sparse-warnings.patch
arch/i386/crypto/aes.c: fix sparse warnings
codingstyle-trivial-whitespace-fixups.patch
CodingStyle: trivial whitespace fixups
small-partitions-msdos-cleanups.patch
small partitions/msdos cleanups
remove-redundant-null-check-before-before-kfree-in.patch
remove redundant NULL check before before kfree() in kernel/sysctl.c
update-ross-biro-bouncing-email-address.patch
update Ross Biro bouncing email address
get-rid-of-redundant-null-checks-before-kfree-in-arch-i386.patch
get rid of redundant NULL checks before kfree() in arch/i386/
remove-redundant-null-checks-before-kfree-in-sound-and.patch
remove redundant NULL checks before kfree() in sound/ and avoid casting pointers about to be kfree()'ed
x86-geode-support-fixes.patch
x86: geode support fixes
drivers-scsi-initioc-cleanups.patch
drivers/scsi/initio.c: cleanups
dont-do-pointless-null-checks-and-casts-before-kfree.patch
selinux: kfree cleanup
drivers-char-isicomc-section-fixes.patch
drivers/char/isicom.c: section fixes
sound-oss-cleanups.patch
sound/oss/: cleanups
sound-oss-rme96xxc-remove-kernel-22-ifs.patch
sound/oss/rme96xx.c: remove kernel 2.2 #if's
drivers-char-mwave-tp3780ic-remove-kernel-22-ifs.patch
drivers/char/mwave/tp3780i.c: remove kernel 2.2 #if's
drivers-net-skfp-cleanups.patch
drivers/net/skfp/: cleanups
net-atm-resourcesc-remove-__free_atm_dev.patch
Subject: [2.6 patch] net/atm/resources.c: remove __free_atm_dev
mm-mmapnommuc-several-unexports.patch
mm/{mmap,nommu}.c: several unexports
unexport-hugetlb_total_pages.patch
unexport hugetlb_total_pages
unexport-clear_page_dirty_for_io.patch
unexport clear_page_dirty_for_io
mm-filemapc-make-sync_page_range_nolock-static.patch
mm/filemap.c: make sync_page_range_nolock static
mm-filemapc-make-generic_file_direct_io-static.patch
mm/filemap.c: make generic_file_direct_IO static
remove-exports-for-oem-modules.patch
remove exports for oem modules
mm-page_allocc-unexport-nr_swap_pages.patch
unexport nr_swap_pages
unexport-console_unblank.patch
unexport console_unblank
mm-swapc-unexport-vm_acct_memory.patch
mm/swap.c: unexport vm_acct_memory
mm-swapfilec-unexport-total_swap_pages.patch
mm/swapfile.c: unexport total_swap_pages
mm-swap_statec-unexport-swapper_space.patch
mm/swap_state.c: unexport swapper_space
unexport-slab_reclaim_pages.patch
unexport slab_reclaim_pages
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Chuck Ebbert
> Latest versions of sudsystem trees
Is that some kind of beer dispenser?
--
Chuck
http://www.counterfeitmini.org
Brice Goglin
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
>
> - Mainly a bunch of fixes relative to 2.6.12-rc1-mm2.
One thing I noticed:
-mm2 did not power off my laptop (Compaq Evo N600c).
I thought I would see something like "ACPI power off" or
USB deregistration messages. But nothing appeared.
It seems to work with -mm3 now.
.config attached.
Regards,
Brice
Rafael J. Wysocki
On Friday, 25 of March 2005 09:21, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
>
> - Mainly a bunch of fixes relative to 2.6.12-rc1-mm2.
First, rmmod works again (thanks ;-)).
> - Again, we'd like people who have had recent DRM and USB resume problems to
> test and report, please.
My box is still hanged solid on resume (swsusp) by the drivers:
ohci_hcd
ehci_hcd
yenta_socket
possibly others, too. To avoid this, I had to revert the following patch from
the Len's tree:
diff -Naru a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
--- a/drivers/acpi/pci_link.c 2005-03-24 04:57:27 -08:00
+++ b/drivers/acpi/pci_link.c 2005-03-24 04:57:27 -08:00
@@ -72,10 +72,12 @@
u8 active; /* Current IRQ */
u8 edge_level; /* All IRQs */
u8 active_high_low; /* All IRQs */
- u8 initialized;
u8 resource_type;
u8 possible_count;
u8 possible[ACPI_PCI_LINK_MAX_POSSIBLE];
+ u8 initialized:1;
+ u8 suspend_resume:1;
+ u8 reserved:6;
};
struct acpi_pci_link {
@@ -530,6 +532,10 @@
ACPI_FUNCTION_TRACE("acpi_pci_link_allocate");
+ if (link->irq.suspend_resume) {
+ acpi_pci_link_set(link, link->irq.active);
+ link->irq.suspend_resume = 0;
+ }
if (link->irq.initialized)
return_VALUE(0);
@@ -713,38 +719,24 @@
return_VALUE(result);
}
-
-static int
-acpi_pci_link_resume (
- struct acpi_pci_link *link)
-{
- ACPI_FUNCTION_TRACE("acpi_pci_link_resume");
-
- if (link->irq.active && link->irq.initialized)
- return_VALUE(acpi_pci_link_set(link, link->irq.active));
- else
- return_VALUE(0);
-}
-
-
static int
-irqrouter_resume(
- struct sys_device *dev)
+irqrouter_suspend(
+ struct sys_device *dev,
+ u32 state)
{
struct list_head *node = NULL;
struct acpi_pci_link *link = NULL;
- ACPI_FUNCTION_TRACE("irqrouter_resume");
+ ACPI_FUNCTION_TRACE("irqrouter_suspend");
list_for_each(node, &acpi_link.entries) {
-
link = list_entry(node, struct acpi_pci_link, node);
if (!link) {
ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Invalid link context\n"));
continue;
}
-
- acpi_pci_link_resume(link);
+ if (link->irq.active && link->irq.initialized)
+ link->irq.suspend_resume = 1;
}
return_VALUE(0);
}
@@ -856,7 +848,7 @@
static struct sysdev_class irqrouter_sysdev_class = {
set_kset_name("irqrouter"),
- .resume = irqrouter_resume,
+ .suspend = irqrouter_suspend,
};
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2005/03/18 16:30:29-05:00 len....@intel.com
# [ACPI] S3 Suspend to RAM: interrupt resume fix
#
# Delete PCI Interrupt Link Device .resume method --
# it is the device driver's job to request interrupts,
# not the Link's job to remember what the devices want.
#
# This addresses the issue of attempting to run
# the ACPI interpreter too early in resume, when
# interrupts are still disabled.
#
# http://bugzilla.kernel.org/show_bug.cgi?id=3469
#
# Signed-off-by: David Shaohua Li <shaoh...@intel.com>
# Signed-off-by: Len Brown <len....@intel.com>
#
# drivers/acpi/pci_link.c
# 2005/03/02 22:23:50-05:00 len....@intel.com +14 -22
# Delete PCI Interrupt Link .resume method
#
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
Li, Shaohua
How about just remove below line:
>+ acpi_pci_link_set(link, link->irq.active);
Thanks,
Shaohua
Rafael J. Wysocki
On Friday, 25 of March 2005 13:54, you wrote:
]--snip--[
You mean apply the patch again and remove just the single
line? No effect (ie hangs).
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
Borislav Petkov
mm3 still not booting on my machine. Boot option 'nmi_watchdog=2' (my cpu is a
dual core pentium 4 HT, 2.60 GHz) gets me a bit further in the boot process
but it blocks there too.
[output retyped from screen]:
kernel: [ 4.109241] PM: Checking swsusp image.
kernel: [ 4.109244] PM: Resume from disk failed.
kernel: [ 4.112220] VFS: Mounted root (ext2 filesystem) readonly.
kernel: [ 4.112465] Freeing unused kernel memory: 188k freed
kernel: [ 4.142002] logips2pp: Detected unknown logitech mouse model 1
kernel: [ 4.274620] input: PS/2 Logitech Mouse on isa0060/serio1
<--- [point of previous blocks without boot option 'nmi_watchdog=2']--->
INIT: version 2.86 booting
Mounting a tmpfs over /dev... done.
Creating initial device nodes... done.
Setting parameters of disc: (none).
Activating swap.
kernel: [ 10.712648] Adding 976744k swap on /dev/hda2. Priority:-1 extents:1
Checking root file system...
fsck 1.36 (05-Feb-2005)
/: clean, 127290/1831424 files, 898566/3662056 blocks
[EOF]
Regards,
Boris.
Barry K. Nathan
> More fixlets derived from the Coverity tool (does this thing have a name?)
AFAICT the name of the tool is "Coverity Prevent". (But I'm not
absolutely 100% sure.)
-Barry K. Nathan <bar...@pobox.com>
Steven Cole
Kernel 2.6.12-rc1 behaves normally:
[root@spc1 steven]# mount /dev/hdc /mnt/cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
[root@spc1 steven]# df -T
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda1 ext3 304M 96M 193M 34% /
/dev/hda9 reiserfs 8.3G 7.2G 1.1G 88% /home
/dev/hda8 ext3 464M 8.1M 432M 2% /tmp
/dev/hda6 ext3 7.4G 1.5G 5.5G 22% /usr
/dev/hda7 ext3 1.9G 96M 1.7G 6% /var
/dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom
[root@spc1 steven]# ls -l /mnt/cdrom
total 37859
-rw-r--r-- 1 501 501 38673949 Mar 25 07:41 linux-2429tar.gz
-rw-r--r-- 1 501 501 92317 Mar 25 07:43 patch-2430-rc1.bz2
[root@spc1 steven]# uname -r
2.6.12-rc1-GX110
Snipped from dmesg:
[ 51.440018] EXT3-fs: mounted filesystem with ordered data mode.
[ 58.585093] PCI: Found IRQ 5 for device 0000:01:0c.0
[ 232.333180] ISO 9660 Extensions: IEEE_P1282
Kernel 2.6.12-rc1-mm3 does not: (same CD left in device)
[root@spc1 steven]# mount /dev/hdc /mnt/cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
[root@spc1 steven]# df -T
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda1 ext3 304M 96M 193M 34% /
/dev/hda9 reiserfs 8.3G 7.2G 1.1G 88% /home
/dev/hda8 ext3 464M 8.1M 432M 2% /tmp
/dev/hda6 ext3 7.4G 1.5G 5.5G 22% /usr
/dev/hda7 ext3 1.9G 96M 1.7G 6% /var
/dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom
[root@spc1 steven]# ls -l /mnt/cdrom
total 0
[root@spc1 steven]# uname -r
2.6.12-rc1-mm3-GX110
Snipped from dmesg:
[ 49.198779] EXT3-fs: mounted filesystem with ordered data mode.
[ 56.310394] PCI: Found IRQ 5 for device 0000:01:0c.0
[ 222.804956] rock: directory entry would overflow storage
[ 222.804978] rock: sig=0x5245, size=8, remaining=0
[ 235.551953] rock: directory entry would overflow storage
[ 235.551969] rock: sig=0x5850, size=36, remaining=34
[ 235.551976] rock: directory entry would overflow storage
[ 235.551981] rock: sig=0x5850, size=36, remaining=34
Sorry, I don't have the time to do further troubleshooting, but I
hope this is enough information. The .config for this machine was
posted earlier in another thread here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=111167720523853&w=2
Steven
Andrew Morton
>
> >
> > [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode.
> > [ 56.310394] PCI: Found IRQ 5 for device 0000:01:0c.0
> > [ 222.804956] rock: directory entry would overflow storage
> > [ 222.804978] rock: sig=0x5245, size=8, remaining=0
> > [ 235.551953] rock: directory entry would overflow storage
> > [ 235.551969] rock: sig=0x5850, size=36, remaining=34
> > [ 235.551976] rock: directory entry would overflow storage
> > [ 235.551981] rock: sig=0x5850, size=36, remaining=34
> >
> > Sorry, I don't have the time to do further troubleshooting, but I
> > hope this is enough information. The .config for this machine was
> > posted earlier in another thread here:
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=111167720523853&w=2
> >
> > Steven
>
> first occured with 2.6.12-rc1-mm2:
>
> 2.6.12-rc1 reads the cd-rom OK as reported earlier
> 2.6.12-rc1-mm1 also reads the cd-rom OK
> 2.6.12-rc1-mm2 broken same as -mm3 described as above
> 2.6.12-rc1-mm3 broken as reported earlier
Are you really really sure about that? -mm3 included both the bk-ide-dev
tree and the isofs changes. 2.6.12-rc1-mm2 had neither.
Steven Cole
I found a few more minutes to test two more kernels. The problem
first occured with 2.6.12-rc1-mm2:
2.6.12-rc1 reads the cd-rom OK as reported earlier
2.6.12-rc1-mm1 also reads the cd-rom OK
2.6.12-rc1-mm2 broken same as -mm3 described as above
2.6.12-rc1-mm3 broken as reported earlier
Steven
Steven Cole
> Steven Cole <elen...@mesatop.com> wrote:
>
>> > [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode.
>> > [ 56.310394] PCI: Found IRQ 5 for device 0000:01:0c.0
>> > [ 222.804956] rock: directory entry would overflow storage
>> > [ 222.804978] rock: sig=0x5245, size=8, remaining=0
>> > [ 235.551953] rock: directory entry would overflow storage
>> > [ 235.551969] rock: sig=0x5850, size=36, remaining=34
>> > [ 235.551976] rock: directory entry would overflow storage
>> > [ 235.551981] rock: sig=0x5850, size=36, remaining=34
>> >
>> > Sorry, I don't have the time to do further troubleshooting, but I
>> > hope this is enough information. The .config for this machine was
>> > posted earlier in another thread here:
>> > http://marc.theaimsgroup.com/?l=linux-kernel&m=111167720523853&w=2
>> >
>> > Steven
>>
>> I found a few more minutes to test two more kernels. The problem
>> first occured with 2.6.12-rc1-mm2:
>>
>> 2.6.12-rc1 reads the cd-rom OK as reported earlier
>> 2.6.12-rc1-mm1 also reads the cd-rom OK
>> 2.6.12-rc1-mm2 broken same as -mm3 described as above
>> 2.6.12-rc1-mm3 broken as reported earlier
>
>
> Are you really really sure about that? -mm3 included both the bk-ide-dev
> tree and the isofs changes. 2.6.12-rc1-mm2 had neither.
>
Just to be really really sure, I repeated the tests. I even checked
that the image/label combination in /etc/lilo.conf was what I intended,
but the uname -r should show what's what.
Same results, -mm2 broken, and -mm1 reads the disk. I even tried
other CD's just to make sure I didn't have something weird. Same results.
[root@spc1 steven]# uname -r
2.6.12-rc1-mm2-GX110
[root@spc1 steven]# mount /dev/hdc /mnt/cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
[root@spc1 steven]# df -T
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda1 ext3 304M 96M 193M 34% /
/dev/hda9 reiserfs 8.3G 7.5G 818M 91% /home
/dev/hda8 ext3 464M 8.1M 432M 2% /tmp
/dev/hda6 ext3 7.4G 1.5G 5.5G 22% /usr
/dev/hda7 ext3 1.9G 96M 1.7G 6% /var
/dev/hdc iso9660 2.9M 2.9M 0 100% /mnt/cdrom
[root@spc1 steven]# ls -l /mnt/cdrom
total 0
[root@spc1 steven]# dmesg | tail
[ 51.205871] EXT3 FS on hda6, internal journal
[ 51.205880] EXT3-fs: mounted filesystem with ordered data mode.
[ 51.234132] kjournald starting. Commit interval 5 seconds
[ 51.234544] EXT3 FS on hda7, internal journal
[ 51.234553] EXT3-fs: mounted filesystem with ordered data mode.
[ 58.357329] PCI: Found IRQ 5 for device 0000:01:0c.0
[ 146.301026] rock: directory entry would overflow storage
[ 146.301044] rock: sig=0x5245, size=8, remaining=0
[ 158.388397] rock: directory entry would overflow storage
[ 158.388415] rock: sig=0x5850, size=36, remaining=34
[root@spc1 steven]#
Machine rebooted here.
[root@spc1 steven]# uname -r
2.6.12-rc1-mm1-GX110
[root@spc1 steven]# mount /dev/hdc /mnt/cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
[root@spc1 steven]# df -T
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda1 ext3 304M 96M 193M 34% /
/dev/hda9 reiserfs 8.3G 7.5G 818M 91% /home
/dev/hda8 ext3 464M 8.1M 432M 2% /tmp
/dev/hda6 ext3 7.4G 1.5G 5.5G 22% /usr
/dev/hda7 ext3 1.9G 96M 1.7G 6% /var
/dev/hdc iso9660 2.9M 2.9M 0 100% /mnt/cdrom
[root@spc1 steven]# ls -l /mnt/cdrom
total 2578
-rw-rw-rw- 1 501 501 2639360 Aug 7 2003 snmp-opc server 30.msi
[root@spc1 steven]# dmesg | tail
[ 50.267382] EXT3 FS on hda8, internal journal
[ 50.267395] EXT3-fs: mounted filesystem with ordered data mode.
[ 50.301423] kjournald starting. Commit interval 5 seconds
[ 50.301763] EXT3 FS on hda6, internal journal
[ 50.301774] EXT3-fs: mounted filesystem with ordered data mode.
[ 50.330087] kjournald starting. Commit interval 5 seconds
[ 50.330503] EXT3 FS on hda7, internal journal
[ 50.330516] EXT3-fs: mounted filesystem with ordered data mode.
[ 57.453061] PCI: Found IRQ 5 for device 0000:01:0c.0
[ 187.450836] ISO 9660 Extensions: IEEE_P1282
[root@spc1 steven]#
Steven
Jason Munro
> Same results, -mm2 broken, and -mm1 reads the disk. I even tried
> other CD's just to make sure I didn't have something weird. Same
> results.
> [root@spc1 steven]# dmesg | tail
> [ 51.205871] EXT3 FS on hda6, internal journal
> [ 51.205880] EXT3-fs: mounted filesystem with ordered data mode.
> [ 51.234132] kjournald starting. Commit interval 5 seconds
> [ 51.234544] EXT3 FS on hda7, internal journal
> [ 51.234553] EXT3-fs: mounted filesystem with ordered data mode.
> [ 58.357329] PCI: Found IRQ 5 for device 0000:01:0c.0
> [ 146.301026] rock: directory entry would overflow storage
> [ 146.301044] rock: sig=0x5245, size=8, remaining=0
> [ 158.388397] rock: directory entry would overflow storage
> [ 158.388415] rock: sig=0x5850, size=36, remaining=34
> [root@spc1 steven]#
Same results with mm3 here, though mm2 will not boot on my machine so I'm
not sure about that. 2.6.12-rc1 works fine, rc1-mm3 successfully mounts the
cdrom device but shows no contents. Releveant dmsesg output:
rock: directory entry would overflow storage
rock: sig=0x4543, size=28, remaining=0
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=27
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=26
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=27
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=26
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=26
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=26
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=27
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=26
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=26
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=26
rock: directory entry would overflow storage
rock: sig=0x5850, size=36, remaining=27
The machine is a Toshiba P35-S609 laptop the cdrom device is:
MATSHITADVD-RAM UJ-820S, ATAPI CD/DVD-ROM drive
Kernel config is attached.
\__ Jason Munro
\__ ja...@stdbev.com
\__ http://hastymail.sourceforge.net/
Andrew Morton
>
> >>
> >> I found a few more minutes to test two more kernels. The problem
> >> first occured with 2.6.12-rc1-mm2:
> >>
> >> 2.6.12-rc1 reads the cd-rom OK as reported earlier
> >> 2.6.12-rc1-mm1 also reads the cd-rom OK
> >> 2.6.12-rc1-mm2 broken same as -mm3 described as above
> >> 2.6.12-rc1-mm3 broken as reported earlier
> >
> >
> > Are you really really sure about that? -mm3 included both the bk-ide-dev
> > tree and the isofs changes. 2.6.12-rc1-mm2 had neither.
> >
>
> Just to be really really sure, I repeated the tests. I even checked
> that the image/label combination in /etc/lilo.conf was what I intended,
> but the uname -r should show what's what.
>
> Same results, -mm2 broken, and -mm1 reads the disk. I even tried
> other CD's just to make sure I didn't have something weird. Same results.
OK, thanks.
It would be interesting to copy a CD to hard disk (under -mm1) and see if
it works OK with the loopback driver.
Also, boot into -mm2 and do a `cmp' of the cdrom with the image which is on
hard-disk.
This should help us work out whether it's isofs, the driver, the VFS or
whatever.
Andrew Morton
(Please dont' edit the cc line. Just do reply-to-all)
"Jason Munro" <ja...@stdbev.com> wrote:
>
> > [ 146.301026] rock: directory entry would overflow storage
> > [ 146.301044] rock: sig=0x5245, size=8, remaining=0
> > [ 158.388397] rock: directory entry would overflow storage
> > [ 158.388415] rock: sig=0x5850, size=36, remaining=34
> > [root@spc1 steven]#
>
>
> Same results with mm3 here, though mm2 will not boot on my machine so I'm
> not sure about that. 2.6.12-rc1 works fine, rc1-mm3 successfully mounts the
> cdrom device but shows no contents. Releveant dmsesg output:
>
> rock: directory entry would overflow storage
> rock: sig=0x4543, size=28, remaining=0
> rock: directory entry would overflow storage
Seems that I am unable to read. It's the new rock-ridge bounds checking.
It worked for me. Is someone able to get an image of a failing filesystem
into my hands?
Andrew Morton
Try this, please?
diff -puN fs/isofs/rock.c~rock-handle-directory-overflows-fix fs/isofs/rock.c
--- 25/fs/isofs/rock.c~rock-handle-directory-overflows-fix Fri Mar 25 14:21:32 2005
+++ 25-akpm/fs/isofs/rock.c Fri Mar 25 14:22:01 2005
@@ -218,12 +218,12 @@ repeat:
if (rr->len < 3)
goto out; /* Something got screwed up here */
sig = isonum_721(rs.chr);
+ if (rock_check_overflow(&rs, sig))
+ goto eio;
rs.chr += rr->len;
rs.len -= rr->len;
if (rs.len < 0)
goto eio; /* corrupted isofs */
- if (rock_check_overflow(&rs, sig))
- goto eio;
switch (sig) {
case SIG('R', 'R'):
@@ -316,12 +316,12 @@ repeat:
if (rr->len < 3)
goto out; /* Something got screwed up here */
sig = isonum_721(rs.chr);
+ if (rock_check_overflow(&rs, sig))
+ goto eio;
rs.chr += rr->len;
rs.len -= rr->len;
if (rs.len < 0)
goto eio; /* corrupted isofs */
- if (rock_check_overflow(&rs, sig))
- goto eio;
switch (sig) {
#ifndef CONFIG_ZISOFS /* No flag for SF or ZF */
@@ -694,12 +694,12 @@ repeat:
if (rr->len < 3)
goto out; /* Something got screwed up here */
sig = isonum_721(rs.chr);
+ if (rock_check_overflow(&rs, sig))
+ goto out;
rs.chr += rr->len;
rs.len -= rr->len;
if (rs.len < 0)
goto out; /* corrupted isofs */
- if (rock_check_overflow(&rs, sig))
- goto out;
switch (sig) {
case SIG('R', 'R'):
_
Chris Wright
>
> (Please dont' edit the cc line. Just do reply-to-all)
>
> "Jason Munro" <ja...@stdbev.com> wrote:
> >
> > > [ 146.301026] rock: directory entry would overflow storage
> > > [ 146.301044] rock: sig=0x5245, size=8, remaining=0
> > > [ 158.388397] rock: directory entry would overflow storage
> > > [ 158.388415] rock: sig=0x5850, size=36, remaining=34
> > > [root@spc1 steven]#
> >
> >
> > Same results with mm3 here, though mm2 will not boot on my machine so I'm
> > not sure about that. 2.6.12-rc1 works fine, rc1-mm3 successfully mounts the
> > cdrom device but shows no contents. Releveant dmsesg output:
> >
> > rock: directory entry would overflow storage
> > rock: sig=0x4543, size=28, remaining=0
> > rock: directory entry would overflow storage
>
> Seems that I am unable to read. It's the new rock-ridge bounds checking.
>
> It worked for me. Is someone able to get an image of a failing filesystem
> into my hands?
I'm interested as well. It should only be the last in the series.
Does reverting it allow the CD to work? (I'm trying to make sure the
other overflow check in the series isn't breaking things, I doubt is,
but...).
ftp.kernel.org:/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/broken-out/rock-handle-directory-overflows.patch
thanks,
-chris
Jason Munro
> On 4:06:54 pm 03/25/05 Andrew Morton <ak...@osdl.org> wrote:
> >
> > (Please dont' edit the cc line. Just do reply-to-all)
>
>
> > "Jason Munro" <ja...@stdbev.com> wrote:
> > >
> > > > [ 146.301026] rock: directory entry would overflow storage
> > > > [ 146.301044] rock: sig=0x5245, size=8, remaining=0
> > > > [ 158.388397] rock: directory entry would overflow storage
> > > > [ 158.388415] rock: sig=0x5850, size=36, remaining=34
> > > > [root@spc1 steven]#
> > >
> > >
> > > Same results with mm3 here, though mm2 will not boot on my
> > > machine so I'm not sure about that. 2.6.12-rc1 works fine,
> > > rc1-mm3 successfully mounts the cdrom device but shows no
> > > contents. Releveant dmsesg output:
> > > rock: directory entry would overflow storage
> > > rock: sig=0x4543, size=28, remaining=0
> > > rock: directory entry would overflow storage
> >
> > Seems that I am unable to read. It's the new rock-ridge bounds
> > checking.
> >
> > It worked for me. Is someone able to get an image of a failing
> > filesystem into my hands?
>
>
> mkdir temp
> touch temp/file1 temp/file2 temp/file3
> mkisofs -R -l temp > test.iso
> mount -o loop /mnt/loop
Of course that should be: mount -o loop test.iso /mnt/loop :)
\__ Jason Munro
\__ ja...@stdbev.com
\__ http://hastymail.sourceforge.net/
-
Jason Munro
Oops, reply-to-all it is.
> "Jason Munro" <ja...@stdbev.com> wrote:
> >
> > > [ 146.301026] rock: directory entry would overflow storage
> > > [ 146.301044] rock: sig=0x5245, size=8, remaining=0
> > > [ 158.388397] rock: directory entry would overflow storage
> > > [ 158.388415] rock: sig=0x5850, size=36, remaining=34
> > > [root@spc1 steven]#
> >
> >
> > Same results with mm3 here, though mm2 will not boot on my machine
> > so I'm not sure about that. 2.6.12-rc1 works fine, rc1-mm3
> > successfully mounts the cdrom device but shows no contents.
> > Releveant dmsesg output:
> > rock: directory entry would overflow storage
> > rock: sig=0x4543, size=28, remaining=0
> > rock: directory entry would overflow storage
>
> Seems that I am unable to read. It's the new rock-ridge bounds
> checking.
>
> It worked for me. Is someone able to get an image of a failing
> filesystem into my hands?
I can reproduce it with the following:
mkdir temp
touch temp/file1 temp/file2 temp/file3
mkisofs -R -l temp > test.iso
mount -o loop /mnt/loop
\__ Jason Munro
\__ ja...@stdbev.com
\__ http://hastymail.sourceforge.net/
-
Steven Cole
> Steven Cole <elen...@mesatop.com> wrote:
>
>>>>I found a few more minutes to test two more kernels. The problem
>>>>first occured with 2.6.12-rc1-mm2:
>>>>
>>>>2.6.12-rc1 reads the cd-rom OK as reported earlier
>>>>2.6.12-rc1-mm1 also reads the cd-rom OK
>>>>2.6.12-rc1-mm2 broken same as -mm3 described as above
>>>>2.6.12-rc1-mm3 broken as reported earlier
>>>
>>>
>>>Are you really really sure about that? -mm3 included both the bk-ide-dev
>>>tree and the isofs changes. 2.6.12-rc1-mm2 had neither.
>>>
>>
>>Just to be really really sure, I repeated the tests. I even checked
>>that the image/label combination in /etc/lilo.conf was what I intended,
>>but the uname -r should show what's what.
>>
>>Same results, -mm2 broken, and -mm1 reads the disk. I even tried
>>other CD's just to make sure I didn't have something weird. Same results.
>
>
> OK, thanks.
>
> It would be interesting to copy a CD to hard disk (under -mm1) and see if
> it works OK with the loopback driver.
>
> Also, boot into -mm2 and do a `cmp' of the cdrom with the image which is on
> hard-disk.
>
> This should help us work out whether it's isofs, the driver, the VFS or
> whatever.
> -
It seems that I've run out of time here today. If this is still an issue
after the weekend, I'll do the above tests.
Until then, Happy Easter.
Steven
Jason Munro
Steven Cole
> Andrew Morton <ak...@osdl.org> wrote:
>
>>It's the new rock-ridge bounds checking.
>
>
> Try this, please?
OK, you caught me just as I was headed out the door. ;)
The patch fixed it for me. Wheee.
[root@spc1 steven]# uname -r
2.6.12-rc1-mm3-GX110
[root@spc1 steven]# mount /dev/hdc /mnt/cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
[root@spc1 steven]# df -T
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda1 ext3 304M 96M 193M 34% /
/dev/hda9 reiserfs 8.3G 7.9G 335M 97% /home
/dev/hda8 ext3 464M 8.1M 432M 2% /tmp
/dev/hda6 ext3 7.4G 1.5G 5.5G 22% /usr
/dev/hda7 ext3 1.9G 97M 1.7G 6% /var
/dev/hdc iso9660 2.9M 2.9M 0 100% /mnt/cdrom
[root@spc1 steven]# ls -l /mnt/cdrom
total 2578
-rw-rw-rw- 1 501 501 2639360 Aug 7 2003 snmp-opc server 30.msi
[root@spc1 steven]# dmesg | tail
[ 49.932278] EXT3 FS on hda8, internal journal
[ 49.932292] EXT3-fs: mounted filesystem with ordered data mode.
[ 49.966250] kjournald starting. Commit interval 5 seconds
[ 49.966659] EXT3 FS on hda6, internal journal
[ 49.966669] EXT3-fs: mounted filesystem with ordered data mode.
[ 49.994929] kjournald starting. Commit interval 5 seconds
[ 49.995334] EXT3 FS on hda7, internal journal
[ 49.995345] EXT3-fs: mounted filesystem with ordered data mode.
[ 57.117794] PCI: Found IRQ 5 for device 0000:01:0c.0
[ 123.944869] ISO 9660 Extensions: IEEE_P1282
Steven
Andrew Morton
>
> This fixes it here.
>
Steven Cole <elen...@mesatop.com> wrote:
>
> The patch fixed it for me. Wheee.
>
OK, thanks guys. You're the best.
Jason Uhlenkott
This doesn't build for SGI sn2:
arch/ia64/kernel/mca.c: In function `ia64_mca_init':
arch/ia64/kernel/mca.c:1394: error: `ACPI_INTERRUPT_CPEI' undeclared (first use in this function)
arch/ia64/kernel/mca.c:1394: error: (Each undeclared identifier is reported only once
arch/ia64/kernel/mca.c:1394: error: for each function it appears in.)
make[1]: *** [arch/ia64/kernel/mca.o] Error 1
make: *** [arch/ia64/kernel] Error 2
This is because we lost CONFIG_ACPI_BOOT -- it now depends on
CONFIG_PM, which we don't have (or want) on sn2. The following fixes
it, but I'm not sure what the original rationale was. Len?
Signed-off-by: Jason Uhlenkott <jaso...@sgi.com>
Index: linux/drivers/acpi/Kconfig
===================================================================
--- linux.orig/drivers/acpi/Kconfig 2005-03-25 12:22:57.909667494 -0800
+++ linux/drivers/acpi/Kconfig 2005-03-25 16:28:35.793588269 -0800
@@ -3,7 +3,6 @@
#
menu "ACPI (Advanced Configuration and Power Interface) Support"
- depends on PM
depends on !X86_VISWS
depends on !IA64_HP_SIM
depends on IA64 || X86
Len Brown
> On Fri, Mar 25, 2005 at 12:21:54AM -0800, Andrew Morton wrote:
> > bk-acpi.patch
>
> This doesn't build for SGI sn2:
>
> arch/ia64/kernel/mca.c: In function `ia64_mca_init':
> arch/ia64/kernel/mca.c:1394: error: `ACPI_INTERRUPT_CPEI' undeclared
> (first use in this function)
> arch/ia64/kernel/mca.c:1394: error: (Each undeclared identifier is
> reported only once
> arch/ia64/kernel/mca.c:1394: error: for each function it appears in.)
> make[1]: *** [arch/ia64/kernel/mca.o] Error 1
> make: *** [arch/ia64/kernel] Error 2
>
> This is because we lost CONFIG_ACPI_BOOT -- it now depends on
> CONFIG_PM, which we don't have (or want) on sn2. The following fixes
> it, but I'm not sure what the original rationale was. Len?
>
> Signed-off-by: Jason Uhlenkott <jaso...@sgi.com>
>
Please send me the .config you'd like to build.
I believe that what we want to do is include CONFIG_PM.
Note also that CONFIG_ACPI_BOOT will be going away --
to be replaced simply by CONFIG_ACPI.
thanks,
-Len
Jason Uhlenkott
> Please send me the .config you'd like to build.
arch/ia64/configs/sn2_defconfig
> I believe that what we want to do is include CONFIG_PM.
At first glance, it looks like that will enable suspend/resume
functionality (which I don't think we want on SGI sn2) for a bunch of
drivers.
Len Brown
> On Fri, Mar 25, 2005 at 08:56:58PM -0500, Len Brown wrote:
> > Please send me the .config you'd like to build.
>
> arch/ia64/configs/sn2_defconfig
> > I believe that what we want to do is include CONFIG_PM.
>
> At first glance, it looks like that will enable suspend/resume
> functionality (which I don't think we want on SGI sn2) for a bunch of
> drivers.
What bad things happen if you define CONFIG_PM on SN2?
Re: CONFIG_ACPI_BOOT
I've got a patch that makes it go away -- this looks like
a good reason for me to dust it off... Looks like
arch/ia64/Kconfig defines ACPI and then pulls in drivers/acpi/Kconfig,
which it should not do - it should look like i386/Kconfig...
-Len
Jason Uhlenkott
> What bad things happen if you define CONFIG_PM on SN2?
None, other than slightly enlarging the kernel with some
suspend/resume stuff we don't care about. It's always been
unavailable for SN2 builds:
depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB
but there doesn't appear to be any particular reason for that other
than us not needing it (and in fact SN2 systems can run IA64_GENERIC
kernels with CONFIG_PM enabled without incident).
> Re: CONFIG_ACPI_BOOT
> I've got a patch that makes it go away -- this looks like
> a good reason for me to dust it off... Looks like
> arch/ia64/Kconfig defines ACPI and then pulls in drivers/acpi/Kconfig,
> which it should not do - it should look like i386/Kconfig...
Sounds good to me. Does that mean everything currently controlled by
CONFIG_ACPI_BOOT will be controlled by CONFIG_ACPI instead?
Jesse Barnes
> On Fri, Mar 25, 2005 at 09:24:21PM -0500, Len Brown wrote:
> > What bad things happen if you define CONFIG_PM on SN2?
>
> None, other than slightly enlarging the kernel with some
> suspend/resume stuff we don't care about. It's always been
> unavailable for SN2 builds:
>
> depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB
>
> but there doesn't appear to be any particular reason for that other
> than us not needing it (and in fact SN2 systems can run IA64_GENERIC
> kernels with CONFIG_PM enabled without incident).
>
> > Re: CONFIG_ACPI_BOOT
> > I've got a patch that makes it go away -- this looks like
> > a good reason for me to dust it off... Looks like
> > arch/ia64/Kconfig defines ACPI and then pulls in drivers/acpi/Kconfig,
> > which it should not do - it should look like i386/Kconfig...
Yeah, I noticed that too. If you've got a patch to clean it up, we should go
ahead and get it sent off to Tony.
I sent this to linux-ia64 the other day to address these issues.
Jesse
Len Brown
> On Fri, Mar 25, 2005 at 09:24:21PM -0500, Len Brown wrote:
> > What bad things happen if you define CONFIG_PM on SN2?
>
> None, other than slightly enlarging the kernel with some
> suspend/resume stuff we don't care about. It's always been
> unavailable for SN2 builds:
>
> depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1 ||
> IA64_HP_ZX1_SWIOTLB
>
> but there doesn't appear to be any particular reason for that other
> than us not needing it (and in fact SN2 systems can run IA64_GENERIC
> kernels with CONFIG_PM enabled without incident).
good.
I realize now I didn't answer your original question.
The reason ACPI now depends on PM is that
it makes it easier for us to do a more orderly shutdown --
acpi registers as a device so it can do some stuff
upon the PM device shutdowns -- before interrupts are disabled.
I think with all the twisty turney passages
related to the suspend states, poweroff, sys-req, and now kexec,
that it is best if we can keep the code paths as
common as possible or some of them will never get the
testing needed to prevent them from getting broken.
Also, it is now common practice to include PM && ACPI together
in the x86 world. Though technically one could have
ACPI w/o PM and you'd have lost only ACPI_SLEEP, virtually
nobody seems to use/depend-on that combination.
Obviously I hadn't considered SN2 or built its config
before that 1-liner. I'll be sure to build it next time.
> > Re: CONFIG_ACPI_BOOT
> > I've got a patch that makes it go away -- this looks like
> > a good reason for me to dust it off... Looks like
> > arch/ia64/Kconfig defines ACPI and then pulls in
> drivers/acpi/Kconfig,
> > which it should not do - it should look like i386/Kconfig...
>
> Sounds good to me. Does that mean everything currently controlled by
> CONFIG_ACPI_BOOT will be controlled by CONFIG_ACPI instead?
yes. this was in -mm a while back, but got pushed onto the back
burner when more pressing things came up.
thanks,
-Len
Paul Blazejowski
Linux version 2.6.12-rc1-mm3 (root@blaze) (gcc version 3.3.4) #2
PREEMPT Fri Mar 25 14:30:56 EST 2005
[snip ...]
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
PCI: nForce2 C1 Halt Disconnect fixup
Boot video device is 0000:03:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Can't get handler for 0000:00:00.1
ACPI: Can't get handler for 0000:00:00.2
ACPI: Can't get handler for 0000:00:00.3
ACPI: Can't get handler for 0000:00:00.4
ACPI: Can't get handler for 0000:00:00.5
ACPI: Can't get handler for 0000:01:0a.0
ACPI: Can't get handler for 0000:01:0b.0
ACPI: Can't get handler for 0000:01:0c.0
ACPI: Can't get handler for 0000:03:00.1
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs *17), disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs *18), disabled.
ACPI: PCI Interrupt Link [APC4] (IRQs *19), disabled.
ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: No ACPI bus support for 00:00
ACPI: No ACPI bus support for 00:01
ACPI: No ACPI bus support for 00:02
ACPI: No ACPI bus support for 00:03
ACPI: No ACPI bus support for 00:04
ACPI: No ACPI bus support for 00:05
ACPI: No ACPI bus support for 00:06
ACPI: No ACPI bus support for 00:07
ACPI: No ACPI bus support for 00:08
ACPI: No ACPI bus support for 00:09
ACPI: No ACPI bus support for 00:0a
ACPI: No ACPI bus support for 00:0b
ACPI: No ACPI bus support for 00:0c
ACPI: No ACPI bus support for 00:0d
pnp: PnP ACPI: found 14 devices
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:00: ioport range 0x1000-0x107f could not be reserved
pnp: 00:00: ioport range 0x1080-0x10ff has been reserved
pnp: 00:00: ioport range 0x1400-0x147f has been reserved
pnp: 00:00: ioport range 0x1480-0x14ff could not be reserved
pnp: 00:00: ioport range 0x1800-0x187f has been reserved
pnp: 00:00: ioport range 0x1880-0x18ff has been reserved
pnp: 00:01: ioport range 0x1c00-0x1c3f has been reserved
pnp: 00:01: ioport range 0x2000-0x203f has been reserved
ACPI: Power Button (FF) [PWRF]
PNP: PS/2 controller doesn't have AUX irq; using default 0xc
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 112
ACPI: No ACPI bus support for i8042
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ACPI: No ACPI bus support for serial8250
ACPI: No ACPI bus support for serio0
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: No ACPI bus support for serio1
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[snip ...]
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ACPI: No ACPI bus support for 0.0
ACPI: No ACPI bus support for 0.1
Probing IDE interface ide1...
hdc: PLEXTOR DVDR PX-716A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ACPI: No ACPI bus support for 1.0
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC3] -> GSI 18 (level,
high) -> IRQ 18
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 29160 Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
(scsi0:A:4): 20.000MB/s transfers (20.000MHz, offset 16)
(scsi0:A:6): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: PLEXTOR Model: CD-R PX-W1210S Rev: 1.06
Type: CD-ROM ANSI SCSI revision: 02
ACPI: No ACPI bus support for 0:0:4:0
Vendor: IBM Model: DDYS-T36950N Rev: S80D
Type: Direct-Access ANSI SCSI revision: 03
scsi0:A:6:0: Tagged Queuing enabled. Depth 32
ACPI: No ACPI bus support for 0:0:6:0
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
ACPI: PCI Interrupt 0000:01:0c.0[A] -> Link [APC2] -> GSI 17 (level,
high) -> IRQ 17
Found Controller: IT8212 UDMA/ATA133 RAID Controller
FindDevices: device 0 is IDE
Channel[0] BM-DMA at 0x9800-0x9807
Channel[1] BM-DMA at 0x9808-0x980F
scsi1 : ITE RAIDExpress133
Vendor: ITE Model: IT8212F Rev: 1.45
Type: Direct-Access ANSI SCSI revision: 00
ACPI: No ACPI bus support for 1:0:0:0
[snip ...]
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1250 $ Ben Collins <bcol...@debian.org>
ACPI: PCI Interrupt Link [APCM] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [APCM] -> GSI 22 (level,
high) -> IRQ 22
PCI: Setting latency timer of device 0000:00:0d.0 to 64
ACPI: No ACPI bus support for fw-host0
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22 (level,
high) -> IRQ 22
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: nVidia Corporation nForce2 USB Controller
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.2: irq 22, io mem 0xee083000
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: park 0
ehci_hcd 0000:00:02.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
ACPI: No ACPI bus support for usb1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ACPI: No ACPI bus support for 1-0:1.0
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level,
high) -> IRQ 21
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: nVidia Corporation nForce2 USB Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 21, io mem 0xee087000
ACPI: No ACPI bus support for usb2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ACPI: No ACPI bus support for 2-0:1.0
ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 20 (level,
high) -> IRQ 20
PCI: Setting latency timer of device 0000:00:02.1 to 64
ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2)
ACPI: No ACPI bus support for 8a1cc7ffff0020ed
ieee1394: Host added: ID:BUS[0-00:1023] GUID[8a1cc7ffff0020ed]
ACPI: No ACPI bus support for 8a1cc7ffff0020ed-0
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:02.1: irq 20, io mem 0xee082000
ACPI: No ACPI bus support for usb3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 3 ports detected
ACPI: No ACPI bus support for 3-0:1.0
eth1394: $Rev: 1247 $ Ben Collins <bcol...@debian.org>
eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
usb 1-3: new high speed USB device using ehci_hcd and address 3
ACPI: No ACPI bus support for 1-3
hub 1-3:1.0: USB hub found
hub 1-3:1.0: 4 ports detected
ACPI: No ACPI bus support for 1-3:1.0
i2c_adapter i2c-4: nForce2 SMBus adapter at 0x1c00
i2c_adapter i2c-5: nForce2 SMBus adapter at 0x2000
eth1: no link during initialization.
usb 2-1: new low speed USB device using ohci_hcd and address 2
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected NVIDIA nForce2 chipset
agpgart: AGP aperture is 128M @ 0xe0000000
ACPI: No ACPI bus support for 2-1
ACPI: No ACPI bus support for 2-1:1.0
usbcore: registered new driver hiddev
[snip ...]
RPC: failed to contact portmap (errno -512).
mount shows
mount -t nfs blazebox:/home/paul /mnt/hd
mount: blazebox:/home/paul: can't read superblock
And the rpcinfo -p on host blazebox [ running FreeBSD 5.3-STABLE ] shows
program vers proto port
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 7 111 portmapper
100000 3 7 111 portmapper
100000 2 7 111 portmapper
100005 1 udp 752 mountd
100005 3 udp 752 mountd
100005 1 tcp 666 mountd
100005 3 tcp 666 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 0 udp 751 nlockmgr
100021 1 udp 751 nlockmgr
100021 3 udp 751 nlockmgr
100021 4 udp 751 nlockmgr
100021 0 tcp 965 nlockmgr
100021 1 tcp 965 nlockmgr
100021 3 tcp 965 nlockmgr
100021 4 tcp 965 nlockmgr
100024 1 udp 879 status
100024 1 tcp 645 status
Trond has helped me before with debugging NFS
--
FreeBSD the Power to Serve!
Jason Uhlenkott
> I realize now I didn't answer your original question.
> The reason ACPI now depends on PM is that
> it makes it easier for us to do a more orderly shutdown --
> acpi registers as a device so it can do some stuff
> upon the PM device shutdowns -- before interrupts are disabled.
>
> I think with all the twisty turney passages
> related to the suspend states, poweroff, sys-req, and now kexec,
> that it is best if we can keep the code paths as
> common as possible or some of them will never get the
> testing needed to prevent them from getting broken.
>
> Also, it is now common practice to include PM && ACPI together
> in the x86 world. Though technically one could have
> ACPI w/o PM and you'd have lost only ACPI_SLEEP, virtually
> nobody seems to use/depend-on that combination.
OK, that makes sense. I see now that Jesse has already sent a patch
to allow CONFIG_PM on sn2, so we'll be fine as soon as that gets
merged.
Jean Delvare
> (...)
> bk-alsa.patch
This one made /proc/asound/card0/id change from "Live" to "Unknown" on
one of my systems, preventing alsatcl from properly restoring my mixer
settings.
I guess this wasn't exactly expected?
00:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
Subsystem: Creative Labs CT4832 SBLive! Value
Flags: bus master, medium devsel, latency 48, IRQ 5
I/O ports at 8800 [size=32]
Class: 0401
Device: 1102:0002
Subsystem: 1102:8027
Thanks,
--
Jean Delvare
Rafael J. Wysocki
On Friday, 25 of March 2005 15:19, Rafael J. Wysocki wrote:
> On Friday, 25 of March 2005 13:54, you wrote:
> ]--snip--[
> > >My box is still hanged solid on resume (swsusp) by the drivers:
> > >
> > >ohci_hcd
> > >ehci_hcd
> > >yenta_socket
> > >
> > >possibly others, too. To avoid this, I had to revert the following
> > patch from the Len's tree:
> > >
> > >diff -Naru a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
> > >--- a/drivers/acpi/pci_link.c 2005-03-24 04:57:27 -08:00
> > >+++ b/drivers/acpi/pci_link.c 2005-03-24 04:57:27 -08:00
> > >@@ -72,10 +72,12 @@
> > > u8 active; /* Current IRQ
> > */
> > > u8 edge_level; /* All IRQs */
> > > u8 active_high_low; /* All IRQs */
> > >- u8 initialized;
> > > u8 resource_type;
> > > u8 possible_count;
> > > u8 possible[ACPI_PCI_LINK_MAX_POSSIBLE];
> > >+ u8 initialized:1;
> > >+ u8 suspend_resume:1;
> > >+ u8 reserved:6;
> > > };
> > >
> > > struct acpi_pci_link {
> > >@@ -530,6 +532,10 @@
> > >
> > > ACPI_FUNCTION_TRACE("acpi_pci_link_allocate");
> > >
> > >+ if (link->irq.suspend_resume) {
> > >+ acpi_pci_link_set(link, link->irq.active);
> > >+ link->irq.suspend_resume = 0;
> > >+ }
> > > if (link->irq.initialized)
> > > return_VALUE(0);
> >
> > How about just remove below line:
> > >+ acpi_pci_link_set(link, link->irq.active);
>
> You mean apply the patch again and remove just the single
> line? No effect (ie hangs).
It looks like removing this line couldn't help.
Apparently, acpi_pci_link_set(link, link->irq.active) must be called
_before_ the call to pci_write_config_word() in
drivers/pci/pci.c:pci_set_power_state(), because the box hangs
otherwise. However, with the patch applied,
acpi_pci_link_set(link, link->irq.active) is only called through
pcibios_enable_irq() in pcibios_enable_device(), which is _after_
the call to pci_set_power_state() in pci_enable_device_bars(),
so it's too late.
Hence, it seems, if you really want to get rid of the
irqrouter_resume(), whatever the reason, the simplest fix
seems to be to change the order of calls to pci_set_power_state()
and pcibios_enable_device() in pci_enable_device_bars():
--- old/drivers/pci/pci.c 2005-03-26 19:10:09.000000000 +0100
+++ linux-2.6.12-rc1-mm2/drivers/pci/pci.c 2005-03-26 19:10:54.000000000 +0100
@@ -442,9 +442,9 @@ pci_enable_device_bars(struct pci_dev *d
{
int err;
- pci_set_power_state(dev, PCI_D0);
if ((err = pcibios_enable_device(dev, bars)) < 0)
return err;
+ pci_set_power_state(dev, PCI_D0);
return 0;
}
though I'm not sure if that's legal.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
Rafael J. Wysocki
Sorry, forget it. It was a good theory that didn't work.
It seems that we have to set all of the PCI links or at least some
of them before we start calling pci_set_power_state().
Sean Neakums
boot with it inserted; however, if I boot with no card inserted,
sleep-resume and insert the card it works fine. Similar with
2.6.12-rc1-mm1; not sure why I didn't notice until now, since I
happily used it for six days or so, PCMCIA and all, although there was
*some* PCMCIA-related issue I failed to note and cannot now recall.
Yenta: CardBus bridge found at 0001:10:13.0 [0000:0000]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0001:10:13.0, mfunc 0x00001002, devctl 0x60
Yenta: ISA IRQ mask 0x0000, PCI irq 53
Socket status: 30000010
pcmcia: I/O behind socket: 0x0 - 0x7fffff
pcmcia: Memory behind socket: 0xf3000000 - 0xf3ffffff
pcmcia: Memory behind socket: 0x80000000 - 0xafffffff
cs: memory probe 0x80000000-0xafffffff:Machine check in kernel mode.
Caused by (from SRR1=149030): Transfer error ack signal
Oops: machine check, sig: 7 [#1]
NIP: F20CEC90 LR: F20CEC64 SP: EF8F3BE0 REGS: ef8f3b30 TRAP: 0200 Not tainted
MSR: 00149030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c12966a0[805] 'modprobe' THREAD: ef8f2000
Last syscall: 128
GPR00: 00000060 EF8F3BE0 C12966A0 F103C000 00000000 EF8F9880 00000002 EF8F3C5A
GPR08: C04B6370 F103D000 00000000 00001000 22002488 1001E284 10017070 00000000
GPR16: 00000000 00000000 00000000 00000000 00000000 C1225D40 30000000 00000000
GPR24: EF8F3C5A 00000021 00000002 C12D282C 00000000 00000000 00000002 EF8F3C5A
NIP [f20cec90] pcmcia_read_cis_mem+0x184/0x1c0 [pcmcia_core]
LR [f20cec64] pcmcia_read_cis_mem+0x158/0x1c0 [pcmcia_core]
Call trace:
[f20cefa0] read_cis_cache+0x144/0x168 [pcmcia_core]
[f20cf668] pccard_get_next_tuple+0x7c/0x2a8 [pcmcia_core]
[f20cf378] pccard_get_first_tuple+0x94/0x144 [pcmcia_core]
[f20d0fb8] pccard_validate_cis+0x94/0x27c [pcmcia_core]
[f106e3c8] readable+0x88/0xa8 [rsrc_nonstatic]
[f106e5a0] cis_readable+0xc8/0xe4 [rsrc_nonstatic]
[f106e860] do_mem_probe+0x1d0/0x1e8 [rsrc_nonstatic]
[f106e8b8] validate_mem+0x40/0x68 [rsrc_nonstatic]
[f106e99c] pcmcia_nonstatic_validate_mem+0xbc/0xc8 [rsrc_nonstatic]
[f20d134c] pcmcia_validate_mem+0x34/0x38 [pcmcia_core]
[f20e39b4] pcmcia_card_add+0x28/0xc0 [pcmcia]
[f20e441c] ds_event+0x8c/0xe4 [pcmcia]
[f20cda3c] send_event+0x70/0xc8 [pcmcia_core]
[f20ce52c] pccard_register_pcmcia+0xac/0xcc [pcmcia_core]
[f20e49b4] pcmcia_bus_add_socket+0xa8/0x104 [pcmcia]
--
Dag vijandelijk luchtschip de huismeester is dood
Dominik Brodowski
> On a PowerBook5.4 I get the below when I insert the PCMCIA card or
> boot with it inserted; however, if I boot with no card inserted,
> sleep-resume and insert the card it works fine. Similar with
> 2.6.12-rc1-mm1; not sure why I didn't notice until now, since I
> happily used it for six days or so, PCMCIA and all, although there was
> *some* PCMCIA-related issue I failed to note and cannot now recall.
If you revert the patch named
pcmcia-mark-parent-bridge-windows-as-resources-available-for-pcmcia-devices.patch
the oops should disappear. However, I had no chance yet to fully debug
what's going on here. So I'd prefer it if you first applied the attached test
patch and sent me (off-list) the dmesg output. Also, it is very strange that
it doesn't trigger if you did a sleep-resume cycle before... Ben, any idea?
Dominik
Li Shaohua
pcibios_enable_device, otherwise enable_device may fail. This is very
strange. In boot time, there also are uninitialized link devices, I'm
wonder why the call of pci_enable_device_bars doesn't fail in boot time.
Did you find the bug only in specific system?
Could you please file a bug in bugzilla? I don't want to lose the
context of thread. And please attach your acpidmp output in the bug.
Thanks,
Shaohua
Reuben Farrelly
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
>
> - Mainly a bunch of fixes relative to 2.6.12-rc1-mm2.
>
> - Again, we'd like people who have had recent DRM and USB resume problems to
> test and report, please.
>
> - The bk-ide-dev tree is back after a couple of weeks of difficulties.
>
> - Jeff asks that anyone who has had problems with the Silicon Image SATA
> drivers test sata_sil-corruption--lockup-fix.patch, which is included in
> this kernel.
I'm repeatably getting this crash on shutdown in -mm3, and a few
releases earlier (but I can't be certain it was the same crash..)
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
ttyS4 at I/O 0xa400 (irq = 16) is a 16550A
ttyS5 at I/O 0xa408 (irq = 16) is a 16550A
This _may_ be the culprit, but I'm not sure:
03:03.0 Serial controller: Timedia Technology Co Ltd PCI2S550 (Dual
16550 UART) (rev 01) (prog-if 02 [16550])
Subsystem: Timedia Technology Co Ltd: Unknown device 0002
Flags: stepping, medium devsel, IRQ 16
I/O ports at a400 [size=32]
The board is an Intel D925XCV.
Shutdown goes like this: (yes, hyperterminal sucks for the ^M
characters, sorry)
INIT: Switching^MINIT: Sending processes the TERM signal
Stopping yum: Disabling nightly yum update: [ OK ]
[ OK ]
Stopping cups-config-daemon: [ OK ]
Stopping HAL daemon: [ OK ]
Stopping system message bus: [ OK ]
Stopping atd: [ OK ]
Stopping cups: [ OK ]
Shutting down xfs: [ OK ]
Shutting down console mouse services: [ OK ]
Unable to handle kernel paging request at virtual address f3a6ce68
printing eip:
c0244109
*pde = 00000000
Oops: 0000 [#1]
SMP DEBUG_PAGEALLOC
Modules linked in: hidp hci_usb sermouse nfsd exportfs md5 ipv6 lp
autofs4 eeprom lm85 i2c_sensor rfcomm l2cap bluetooth nfs lock
d sunrpc usb_storage pwc videodev dm_mod video button battery ac
ohci1394 ieee1394 uhci_hcd ehci_hcd parport_serial parport_pc parp
ort hw_random i2c_i801 i2c_core emu10k1_gp gameport e100 mii floppy ext3
jbd ata_piix libata sd_mod scsi_mod
CPU: 0
EIP: 0060:[<c0244109>] Not tainted VLI
EFLAGS: 00010286 (2.6.12-rc1-mm3)
EIP is at serport_ldisc_write_wakeup+0x9/0x20
eax: f3a6cdf8 ebx: f73d7000 ecx: c038e374 edx: c0244100
esi: f73d700c edi: f73d7000 ebp: c049e900 esp: f7568dc0
ds: 007b es: 007b ss: 0068
Process inputattach (pid: 2932, threadinfo=f7568000 task=f6993ac0)
Stack: c021bb08 00000286 f6c31000 c0245e4a f6c31018 f73d7000 f67c1e88
cbff5c
00000000 c021ceaa 00000000 00000000 00000000 c1e46000 c1e46000
00000000
00000000 c011b739 00000046 c1e46000 00000001 f2c00000 f2c00000
c011b8b4
Call Trace:
^M [<c021bb08>] tty_wakeup+0x48/0x70
^M [<c0245e4a>] uart_close+0xca/0x1e0
^M [<c021ceaa>] release_dev+0x14a/0x750
^M [<c011b739>] change_page_attr+0x29/0x60
^M [<c011b8b4>] kernel_map_pages+0x84/0xa0
^M [<c014cbca>] store_stackinfo+0x5a/0x90
^M [<c01664c8>] __fput+0x108/0x180
^M [<c018b59b>] inotify_inode_queue_event+0x2b/0x40
^M [<c021d97f>] tty_release+0xf/0x20
^M [<c016644a>] __fput+0x8a/0x180
^M [<c0164d7b>] filp_close+0x4b/0x70
^M [<c0125254>] put_files_struct+0x74/0x100
^M [<c012610c>] do_exit+0x11c/0x420
^M [<c012647d>] do_group_exit+0x2d/0xa0
^M [<c012f74c>] get_signal_to_deliver+0x20c/0x310
^M [<c0103deb>] do_signal+0x5b/0x140
^M [<c011ea89>] __wake_up+0x29/0x40
^M [<c021b60c>] tty_ldisc_deref+0x3c/0x70
^M [<c021c267>] tty_read+0xc7/0x130
^M [<c0243fb0>] serport_ldisc_read+0x0/0x100
^M [<c016ecd3>] sys_fstat64+0x23/0x30
^M [<c021c1a0>] tty_read+0x0/0x130
^M [<c0165547>] vfs_read+0x97/0x140
^M [<c016585c>] sys_read+0x3c/0x70
^M [<c0103efa>] do_notify_resume+0x2a/0x40
^M [<c01040be>] work_notifysig+0x13/0x25
^MCode: e8 0f b6 c5 88 4b 4b 31 d2 c1 e9 10 88 43 4a 88 4b 49 89 d0 5b
c3 8d b6 00 00 00 00 8d bf 00 00 00 00 8b 80 a8 09 00 00 8b
40 14 <8b> 50 70 85 d2 74 09 8b 52 10 85 d2 74 02 ff d2 c3 90 90 90 90
^M BUG: atomic counter underflow at:
^M [<c0126386>] do_exit+0x396/0x420
^M [<c01059f6>] die+0x166/0x170
^M [<c011a7a3>] do_page_fault+0x1f3/0x6a1
^M [<c0244109>] serport_ldisc_write_wakeup+0x9/0x20
^M [<c011b36c>] __change_page_attr+0x4c/0x3f0
^M [<c011a5b0>] do_page_fault+0x0/0x6a1
^M [<c010522f>] error_code+0x4f/0x60
^M [<c0244100>] serport_ldisc_write_wakeup+0x0/0x20
^M [<c0244109>] serport_ldisc_write_wakeup+0x9/0x20
^M [<c021bb08>] tty_wakeup+0x48/0x70
^M [<c0245e4a>] uart_close+0xca/0x1e0
^M [<c021ceaa>] release_dev+0x14a/0x750
^M [<c011b739>] change_page_attr+0x29/0x60
^M [<c011b8b4>] kernel_map_pages+0x84/0xa0
^M [<c014cbca>] store_stackinfo+0x5a/0x90
^M [<c01664c8>] __fput+0x108/0x180
^M [<c018b59b>] inotify_inode_queue_event+0x2b/0x40
^M [<c021d97f>] tty_release+0xf/0x20
^M [<c016644a>] __fput+0x8a/0x180
^M [<c0164d7b>] filp_close+0x4b/0x70
^M [<c0125254>] put_files_struct+0x74/0x100
^M [<c012610c>] do_exit+0x11c/0x420
^M [<c012647d>] do_group_exit+0x2d/0xa0
^M [<c012f74c>] get_signal_to_deliver+0x20c/0x310
^M [<c0103deb>] do_signal+0x5b/0x140
^M [<c011ea89>] __wake_up+0x29/0x40
^M [<c021b60c>] tty_ldisc_deref+0x3c/0x70
^M [<c021c267>] tty_read+0xc7/0x130
^M [<c0243fb0>] serport_ldisc_read+0x0/0x100
^M [<c016ecd3>] sys_fstat64+0x23/0x30
^M [<c021c1a0>] tty_read+0x0/0x130
^M [<c0165547>] vfs_read+0x97/0x140
^M [<c016585c>] sys_read+0x3c/0x70
^M [<c0103efa>] do_notify_resume+0x2a/0x40
^M [<c01040be>] work_notifysig+0x13/0x25
^MUnable to handle kernel NULL pointer dereference at virtual address
00000020
^M printing eip:
^Mc0121320
^M*pde = 0041f001
^MOops: 0000 [#2]
^MSMP DEBUG_PAGEALLOC
(there's a bit more, which I can put up online if it's helpful)
Reuben
Russell King
Looks like something in the input layer went bang. The code in
serport_ldisc_write_wakeup is:
0: 8b 80 a8 09 00 00 mov 0x9a8(%eax),%eax
6: 8b 40 14 mov 0x14(%eax),%eax
9: 8b 50 70 mov 0x70(%eax),%edx <====
c: 85 d2 test %edx,%edx
e: 74 09 je 0x19
and the marked line exploded on you. The above instructions correspond
with:
0: struct serport *sp = (struct serport *) tty->disc_data;
6: serio_drv_write_wakeup(sp->serio);
9: if (serio->drv
So, "serio" was this strange 0xf3a6cdf8 value. But why? One for the
input people I think.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
Reuben Farrelly
>
> I'm repeatably getting this crash on shutdown in -mm3, and a few
> releases earlier (but I can't be certain it was the same crash..)
>
> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> ttyS4 at I/O 0xa400 (irq = 16) is a 16550A
> ttyS5 at I/O 0xa408 (irq = 16) is a 16550A
>
> This _may_ be the culprit, but I'm not sure:
>
> 03:03.0 Serial controller: Timedia Technology Co Ltd PCI2S550 (Dual
> 16550 UART) (rev 01) (prog-if 02 [16550])
> Subsystem: Timedia Technology Co Ltd: Unknown device 0002
> Flags: stepping, medium devsel, IRQ 16
> I/O ports at a400 [size=32]
Ugh. I'm an idiot, that will teach me for having two sessions to boxes
running at once.
Wrong info above, but the trace is still valid.
Correct info follows:
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS14 at I/O 0xb400 (irq = 217) is a 16550A
ttyS15 at I/O 0xb000 (irq = 217) is a 16550A
06:02.0 Serial controller: NetMos Technology PCI 9835 Multi-I/O
Controller (rev
01) (prog-if 02 [16550])
Subsystem: LSI Logic / Symbios Logic 2S (16C550 UART)
Flags: medium devsel, IRQ 217
I/O ports at b400 [size=8]
I/O ports at b000 [size=8]
I/O ports at ac00 [size=8]
I/O ports at a800 [size=8]
I/O ports at a400 [size=8]
I/O ports at a000 [size=16]
> The board is an Intel D925XCV.
>
> Shutdown goes like this: (yes, hyperterminal sucks for the ^M
> characters, sorry)
<trace omitted>
reuben
Dmitry Torokhov
> Hi,
>
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
> >
> > - Mainly a bunch of fixes relative to 2.6.12-rc1-mm2.
> >
> > - Again, we'd like people who have had recent DRM and USB resume problems to
> > test and report, please.
> >
> > - The bk-ide-dev tree is back after a couple of weeks of difficulties.
> >
> > - Jeff asks that anyone who has had problems with the Silicon Image SATA
> > drivers test sata_sil-corruption--lockup-fix.patch, which is included in
> > this kernel.
>
> I'm repeatably getting this crash on shutdown in -mm3, and a few
> releases earlier (but I can't be certain it was the same crash..)
>
It would be nice to know when it started breaking... At least point release,
not -rc or -bk.
--
Dmitry
Rafael J. Wysocki
On Monday, 28 of March 2005 03:22, Li Shaohua wrote:
> On Sun, 2005-03-27 at 02:23, Rafael J. Wysocki wrote:
]--snip--[
> Could you please file a bug in bugzilla? I don't want to lose the
> context of thread. And please attach your acpidmp output in the bug.
The bug report is at:
http://bugzilla.kernel.org/show_bug.cgi?id=4416
I've put there all the information related to it that I've already collected.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
Takashi Iwai
Jean Delvare wrote:
>
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
> > (...)
> > bk-alsa.patch
>
> This one made /proc/asound/card0/id change from "Live" to "Unknown" on
> one of my systems, preventing alsatcl from properly restoring my mixer
> settings.
>
> I guess this wasn't exactly expected?
Hmm, perhaps it's a side effect of chip detection patch by James.
But "Unknown" is bad, of course.
How does /proc/asound/cards look?
Takashi
Jean Delvare
> > This one made /proc/asound/card0/id change from "Live" to "Unknown"
> > on one of my systems, preventing alsatcl from properly restoring my
> > mixer settings.
>
> Hmm, perhaps it's a side effect of chip detection patch by James.
> But "Unknown" is bad, of course.
>
> How does /proc/asound/cards look?
0 [Unknown ]: EMU10K1 - SB Live [Unknown]
SB Live [Unknown] (rev.6, serial:0x80271102) at 0x8800, irq 5
With the bk-alsa patch reverted, it looks like:
0 [Live ]: EMU10K1 - Sound Blaster Live!
Sound Blaster Live! (rev.6, serial:0x80271102) at 0x8800, irq 5
Hope that helps. If you need any additional information, just ask.
Thanks,
--
Jean Delvare
Lee Revell
> Hi Takashi,
>
> > > This one made /proc/asound/card0/id change from "Live" to "Unknown"
> > > on one of my systems, preventing alsatcl from properly restoring my
> > > mixer settings.
> >
> > Hmm, perhaps it's a side effect of chip detection patch by James.
> > But "Unknown" is bad, of course.
> >
> > How does /proc/asound/cards look?
>
> 0 [Unknown ]: EMU10K1 - SB Live [Unknown]
> SB Live [Unknown] (rev.6, serial:0x80271102) at 0x8800, irq 5
>
> With the bk-alsa patch reverted, it looks like:
>
> 0 [Live ]: EMU10K1 - Sound Blaster Live!
> Sound Blaster Live! (rev.6, serial:0x80271102) at 0x8800, irq 5
>
> Hope that helps. If you need any additional information, just ask.
I think we just have to add this PCI id to the table. I got the same
result before James added the SBLive! platinum detection.
What is the output of 'lspci -v | grep -1 EMU10k1'?
Lee
Lee Revell
> Hi Lee,
>
> > I think we just have to add this PCI id to the table. I got the same
> > result before James added the SBLive! platinum detection.
> >
> > What is the output of 'lspci -v | grep -1 EMU10k1'?
>
> Subsystem: Creative Labs CT4832 SBLive! Value
>
>
> 00:0d.0 Class 0401: 1102:0002 (rev 06)
> Subsystem: 1102:8027
>
> This made me realize that I could still try to hack it myself. The
> following patch somehow helped:
>
> --- linux-2.6.12-rc1-mm3/sound/pci/emu10k1/emu10k1_main.c.orig 2005-03-29 20:38:12.000000000 +0200
> +++ linux-2.6.12-rc1-mm3/sound/pci/emu10k1/emu10k1_main.c 2005-03-29 22:32:23.000000000 +0200
> @@ -680,6 +680,10 @@
> .driver = "EMU10K1", .name = "E-mu APS [4001]",
> .emu10k1_chip = 1,
> .ecard = 1} ,
> + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102,
> + .driver = "EMU10K1", .name = "SB Live Player 1024",
> + .emu10k1_chip = 1,
> + .ac97_chip = 1} ,
> {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80641102,
> .driver = "EMU10K1", .name = "SB Live 5.1",
> .emu10k1_chip = 1,
>
>
> Now the card will be listed as "S1024" instead of "Unknown" so that's a
> change. Looks like the short name is auto-generated? Unfortunately
> that's still not "Live" as before so my mixer settings are not back yet.
> And I believe that "Live" was a much better name than "S1024" too.
>
Here is the patch (against ALSA CVS) in its preferred format. You will
probably have to apply it by hand. If the mixer settings can't be
restored you'll have to do it manually or edit asound.state by hand.
Lee
Index: alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c,v
retrieving revision 1.49
diff -u -r1.49 emu10k1_main.c
--- alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c 27 Mar 2005 14:00:54 -0000 1.49
+++ alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c 29 Mar 2005 20:51:44 -0000
@@ -693,6 +693,10 @@
.driver = "EMU10K1", .name = "SBLive! Platinum [CT4760P]",
.emu10k1_chip = 1,
.ac97_chip = 1} ,
+ {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102,
+ .driver = "EMU10K1", .name = "SBLive! Value [CT4832]",
+ .emu10k1_chip = 1,
+ .ac97_chip = 1} ,
{.vendor = 0x1102, .device = 0x0002,
.driver = "EMU10K1", .name = "SB Live [Unknown]",
.emu10k1_chip = 1,
Jean Delvare
> I think we just have to add this PCI id to the table. I got the same
> result before James added the SBLive! platinum detection.
>
> What is the output of 'lspci -v | grep -1 EMU10k1'?
00:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
Subsystem: Creative Labs CT4832 SBLive! Value
and the one you didn't ask for:
00:0d.0 Class 0401: 1102:0002 (rev 06)
Subsystem: 1102:8027
This made me realize that I could still try to hack it myself. The
following patch somehow helped:
--- linux-2.6.12-rc1-mm3/sound/pci/emu10k1/emu10k1_main.c.orig 2005-03-29 20:38:12.000000000 +0200
+++ linux-2.6.12-rc1-mm3/sound/pci/emu10k1/emu10k1_main.c 2005-03-29 22:32:23.000000000 +0200
@@ -680,6 +680,10 @@
.driver = "EMU10K1", .name = "E-mu APS [4001]",
.emu10k1_chip = 1,
.ecard = 1} ,
+ {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102,
+ .driver = "EMU10K1", .name = "SB Live Player 1024",
+ .emu10k1_chip = 1,
+ .ac97_chip = 1} ,
{.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80641102,
.driver = "EMU10K1", .name = "SB Live 5.1",
.emu10k1_chip = 1,
Now the card will be listed as "S1024" instead of "Unknown" so that's a
change. Looks like the short name is auto-generated? Unfortunately
that's still not "Live" as before so my mixer settings are not back yet.
And I believe that "Live" was a much better name than "S1024" too.
Thanks,
--
Jean Delvare
Jean Delvare
> Here is the patch (against ALSA CVS) in its preferred format. You
> will probably have to apply it by hand. If the mixer settings can't
> be restored you'll have to do it manually or edit asound.state by
> hand.
>
> Lee
>
> Index: alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c
> ===================================================================
> RCS file: /cvsroot/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c,v
> retrieving revision 1.49
> diff -u -r1.49 emu10k1_main.c
> --- alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c 27 Mar 2005 14:00:54 -0000 1.49
> +++ alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c 29 Mar 2005 20:51:44 -0000
> @@ -693,6 +693,10 @@
> .driver = "EMU10K1", .name = "SBLive! Platinum [CT4760P]",
> .emu10k1_chip = 1,
> .ac97_chip = 1} ,
> + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102,
> + .driver = "EMU10K1", .name = "SBLive! Value [CT4832]",
> + .emu10k1_chip = 1,
> + .ac97_chip = 1} ,
> {.vendor = 0x1102, .device = 0x0002,
> .driver = "EMU10K1", .name = "SB Live [Unknown]",
> .emu10k1_chip = 1,
Unsurprisingly, my card is now named CT4832. I had to edit
/etc/asound.state manually to get my mixer settings back (with some
warnings, but I get some sound).
Not sure I quite see the idea of renaming from "Live", which the user
will understand, to (I suppose) the exact chip name on the card, while
the user has certainly no idea what it is. But heh I'm not an ALSA
developer, there must be a good reason.
Thanks,
--
Jean Delvare
Lee Revell
> > + {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80271102,
> > + .driver = "EMU10K1", .name = "SBLive! Value [CT4832]",
> > + .emu10k1_chip = 1,
> > + .ac97_chip = 1} ,
> /etc/asound.state manually to get my mixer settings back (with some
> warnings, but I get some sound).
>
> Not sure I quite see the idea of renaming from "Live", which the user
> will understand, to (I suppose) the exact chip name on the card, while
> the user has certainly no idea what it is. But heh I'm not an ALSA
> developer, there must be a good reason.
Blame Creative. They have released so many different cards under the
Live! name that it's become meaningless. There are now two separate
classes of cards marketed as Live! (or Audigy) that don't even use the
same driver (ca0106 and emu10k1x), the hardware isn't even similar.
Unsurprisingly, the user confusion is massive.
The model number is the simplest unique identifier. This is also what
the "good" Windows drivers for these devices, http://www.kxproject.com,
use.
Lee
Takashi Iwai
Changing the name to more descriptive one is a good thing, IMO.
But, of course, it's a regression if the system gets (somehow) broken
after the update.
We can add a hack to set id explicitly to be compatible with older
version...
Takashi
Dmitry Torokhov
> Looks like something in the input layer went bang. The code in
> serport_ldisc_write_wakeup is:
>
> 0: 8b 80 a8 09 00 00 mov 0x9a8(%eax),%eax
> 6: 8b 40 14 mov 0x14(%eax),%eax
> 9: 8b 50 70 mov 0x70(%eax),%edx <====
> c: 85 d2 test %edx,%edx
> e: 74 09 je 0x19
>
> and the marked line exploded on you. The above instructions correspond
> with:
>
> 0: struct serport *sp = (struct serport *) tty->disc_data;
> 6: serio_drv_write_wakeup(sp->serio);
> 9: if (serio->drv
>
> So, "serio" was this strange 0xf3a6cdf8 value. But why? One for the
> input people I think.
Reuben, could you please try the patch below? Thanks!
Russell, could you please tell me if ldisc->write_wakeup (tty_wakwup) and
ldisc->read are allowed to be called from an IRQ context? IOW I wonder if
I can use spil_lock_bh instead of spil_lock_irqsave to protect serport
flags.
--
Dmitry
serport.c | 98 +++++++++++++++++++++++++++++++++++++++++++-------------------
1 files changed, 68 insertions(+), 30 deletions(-)
Index: dtor/drivers/input/serio/serport.c
===================================================================
--- dtor.orig/drivers/input/serio/serport.c
+++ dtor/drivers/input/serio/serport.c
@@ -27,11 +27,15 @@ MODULE_LICENSE("GPL");
MODULE_ALIAS_LDISC(N_MOUSE);
#define SERPORT_BUSY 1
+#define SERPORT_ACTIVE 2
+#define SERPORT_DEAD 3
struct serport {
struct tty_struct *tty;
wait_queue_head_t wait;
struct serio *serio;
+ struct serio_device_id id;
+ spinlock_t lock;
unsigned long flags;
};
@@ -45,11 +49,29 @@ static int serport_serio_write(struct se
return -(serport->tty->driver->write(serport->tty, &data, 1) != 1);
}
+static int serport_serio_open(struct serio *serio)
+{
+ struct serport *serport = serio->port_data;
+ unsigned long flags;
+
+ spin_lock_irqsave(&serport->lock, flags);
+ set_bit(SERPORT_ACTIVE, &serport->flags);
+ spin_unlock_irqrestore(&serport->lock, flags);
+
+ return 0;
+}
+
+
static void serport_serio_close(struct serio *serio)
{
struct serport *serport = serio->port_data;
+ unsigned long flags;
+
+ spin_lock_irqsave(&serport->lock, flags);
+ clear_bit(SERPORT_ACTIVE, &serport->flags);
+ set_bit(SERPORT_DEAD, &serport->flags);
+ spin_unlock_irqrestore(&serport->lock, flags);
- serport->serio->id.type = 0;
wake_up_interruptible(&serport->wait);
}
@@ -61,36 +83,21 @@ static void serport_serio_close(struct s
static int serport_ldisc_open(struct tty_struct *tty)
{
struct serport *serport;
- struct serio *serio;
- char name[64];
if (!capable(CAP_SYS_ADMIN))
return -EPERM;
- serport = kmalloc(sizeof(struct serport), GFP_KERNEL);
- serio = kmalloc(sizeof(struct serio), GFP_KERNEL);
- if (unlikely(!serport || !serio)) {
- kfree(serport);
- kfree(serio);
+ serport = kcalloc(1, sizeof(struct serport), GFP_KERNEL);
+ if (!serport)
return -ENOMEM;
- }
- memset(serport, 0, sizeof(struct serport));
- serport->serio = serio;
- set_bit(TTY_DO_WRITE_WAKEUP, &tty->flags);
serport->tty = tty;
- tty->disc_data = serport;
-
- memset(serio, 0, sizeof(struct serio));
- strlcpy(serio->name, "Serial port", sizeof(serio->name));
- snprintf(serio->phys, sizeof(serio->phys), "%s/serio0", tty_name(tty, name));
- serio->id.type = SERIO_RS232;
- serio->write = serport_serio_write;
- serio->close = serport_serio_close;
- serio->port_data = serport;
-
+ spin_lock_init(&serport->lock);
init_waitqueue_head(&serport->wait);
+ tty->disc_data = serport;
+ set_bit(TTY_DO_WRITE_WAKEUP, &tty->flags);
+
return 0;
}
@@ -100,7 +107,8 @@ static int serport_ldisc_open(struct tty
static void serport_ldisc_close(struct tty_struct *tty)
{
- struct serport *serport = (struct serport*) tty->disc_data;
+ struct serport *serport = (struct serport *) tty->disc_data;
+
kfree(serport);
}
@@ -116,9 +124,19 @@ static void serport_ldisc_close(struct t
static void serport_ldisc_receive(struct tty_struct *tty, const unsigned char *cp, char *fp, int count)
{
struct serport *serport = (struct serport*) tty->disc_data;
+ unsigned long flags;
int i;
+
+ spin_lock_irqsave(&serport->lock, flags);
+
+ if (!test_bit(SERPORT_ACTIVE, &serport->flags))
+ goto out;
+
for (i = 0; i < count; i++)
serio_interrupt(serport->serio, cp[i], 0, NULL);
+
+out:
+ spin_unlock_irqrestore(&serport->lock, flags);
}
/*
@@ -141,16 +159,33 @@ static int serport_ldisc_room(struct tty
static ssize_t serport_ldisc_read(struct tty_struct * tty, struct file * file, unsigned char __user * buf, size_t nr)
{
struct serport *serport = (struct serport*) tty->disc_data;
+ struct serio *serio;
char name[64];
if (test_and_set_bit(SERPORT_BUSY, &serport->flags))
return -EBUSY;
+ serport->serio = serio = kcalloc(1, sizeof(struct serio), GFP_KERNEL);
+ if (!serio)
+ return -ENOMEM;
+
+ strlcpy(serio->name, "Serial port", sizeof(serio->name));
+ snprintf(serio->phys, sizeof(serio->phys), "%s/serio0", tty_name(tty, name));
+ serio->id = serport->id;
+ serio->id.type = SERIO_RS232;
+ serio->write = serport_serio_write;
+ serio->open = serport_serio_open;
+ serio->close = serport_serio_close;
+ serio->port_data = serport;
+
serio_register_port(serport->serio);
printk(KERN_INFO "serio: Serial port %s\n", tty_name(tty, name));
- wait_event_interruptible(serport->wait, !serport->serio->id.type);
+
+ wait_event_interruptible(serport->wait, test_bit(SERPORT_DEAD, &serport->flags));
serio_unregister_port(serport->serio);
+ serport->serio = NULL;
+ clear_bit(SERPORT_DEAD, &serport->flags);
clear_bit(SERPORT_BUSY, &serport->flags);
return 0;
@@ -163,16 +198,15 @@ static ssize_t serport_ldisc_read(struct
static int serport_ldisc_ioctl(struct tty_struct * tty, struct file * file, unsigned int cmd, unsigned long arg)
{
struct serport *serport = (struct serport*) tty->disc_data;
- struct serio *serio = serport->serio;
unsigned long type;
if (cmd == SPIOCSTYPE) {
if (get_user(type, (unsigned long __user *) arg))
return -EFAULT;
- serio->id.proto = type & 0x000000ff;
- serio->id.id = (type & 0x0000ff00) >> 8;
- serio->id.extra = (type & 0x00ff0000) >> 16;
+ serport->id.proto = type & 0x000000ff;
+ serport->id.id = (type & 0x0000ff00) >> 8;
+ serport->id.extra = (type & 0x00ff0000) >> 16;
return 0;
}
@@ -182,9 +216,13 @@ static int serport_ldisc_ioctl(struct tt
static void serport_ldisc_write_wakeup(struct tty_struct * tty)
{
- struct serport *sp = (struct serport *) tty->disc_data;
+ struct serport *serport = (struct serport *) tty->disc_data;
+ unsigned long flags;
- serio_drv_write_wakeup(sp->serio);
+ spin_lock_irqsave(&serport->lock, flags);
+ if (test_bit(SERPORT_ACTIVE, &serport->flags))
+ serio_drv_write_wakeup(serport->serio);
+ spin_unlock_irqrestore(&serport->lock, flags);
}
/*
Borislav Petkov
> Hi Andrew,
>
> mm3 still not booting on my machine. Boot option 'nmi_watchdog=2' (my cpu
> is a dual core pentium 4 HT, 2.60 GHz) gets me a bit further in the boot
> process but it blocks there too.
>
> [output retyped from screen]:
> kernel: [ 4.109241] PM: Checking swsusp image.
> kernel: [ 4.109244] PM: Resume from disk failed.
> kernel: [ 4.112220] VFS: Mounted root (ext2 filesystem) readonly.
> kernel: [ 4.112465] Freeing unused kernel memory: 188k freed
> kernel: [ 4.142002] logips2pp: Detected unknown logitech mouse model 1
> kernel: [ 4.274620] input: PS/2 Logitech Mouse on isa0060/serio1
> <--- [point of previous blocks without boot option 'nmi_watchdog=2']--->
> INIT: version 2.86 booting
> Mounting a tmpfs over /dev... done.
> Creating initial device nodes... done.
> Setting parameters of disc: (none).
> Activating swap.
> kernel: [ 10.712648] Adding 976744k swap on /dev/hda2. Priority:-1
> extents:1 Checking root file system...
> fsck 1.36 (05-Feb-2005)
> /: clean, 127290/1831424 files, 898566/3662056 blocks
> [EOF]
Hi Andrew,
i finally got to run kdb within mm3 and I got a bit further but am not sure
whether I'm debugging in the right direction:
After booting with "kdb=early" I found out that the kernel blocks with the
partial message:
kmem_cache_create: Early error in slab task_struct
kernel BUG at mm/slab.c:1215
invalid operand: 0000 [#1]
PREEMPT SMP
and here all dies. After singlestepping through the code, I found out that
start_kernel calls at offset 0x14d fork_init, which calls at offset 0x39
kmem_cache_create. kmem_cache_create performs some initial checks:
1205 /*
1206 * Sanity checks... these are all serious usage bugs.
1207 */
1208 if ((!name) ||
1209 in_interrupt() ||
1210 (size < BYTES_PER_WORD) ||
1211 (size > (1<<MAX_OBJ_ORDER)*PAGE_SIZE) ||
1212 (dtor && !ctor)) {
1213 printk(KERN_ERR "%s: Early error in slab %s\n",
1214 __FUNCTION__, name);
1215 BUG();
1216 }
And after singlestepping a little bit more, I found out that the
in_interrupt() check returns true and printk is executed. Here's the
disassembled code:
00000b10 <kmem_cache_create>:
kmem_cache_create():
mm/slab.c:1201
b10: 55 push %ebp
b11: 89 e5 mov %esp,%ebp
b13: 57 push %edi
b14: 56 push %esi
b15: 53 push %ebx
b16: 83 ec 3c sub $0x3c,%esp
mm/slab.c:1208
b19: 8b 55 08 mov 0x8(%ebp),%edx
b1c: 85 d2 test %edx,%edx
b1e: 0f 84 01 08 00 00 je 1325 <kmem_cache_create+0x815>
include/asm/thread_info.h:91
b24: b8 00 f0 ff ff mov $0xfffff000,%eax
b29: 21 e0 and %esp,%eax
include/asm/thread_info.h:89
b2b: f7 40 14 00 ff ff 0f testl $0xfffff00,0x14(%eax)
b32: 0f 85 ed 07 00 00 jne 1325 <kmem_cache_create+0x815> <---
this jump here executes and line 0x1325 is:
mm/slab.c:1213
1325: c7 04 24 40 02 00 00 movl $0x240,(%esp)
132c: 8b 45 08 mov 0x8(%ebp),%eax
132f: 89 44 24 08 mov %eax,0x8(%esp)
1333: b8 0d 00 00 00 mov $0xd,%eax
1338: 89 44 24 04 mov %eax,0x4(%esp)
133c: e8 fc ff ff ff call 133d <kmem_cache_create+0x82d>
mm/slab.c:1215
1341: 0f 0b ud2a
1343: bf 04 00 00 00 mov $0x4,%edi
1348: 00 e9 add %ch,%cl
134a: 13 f8 adc %eax,%edi
134c: ff (bad)
134d: ff c7 inc %edi
and BUG() is called.
Any suggestions or corrections will be greatly appreciated.
Regards,
Boris.
Andrew Morton
Beats me. Where did the kdb patch come from?
It sounds like kdb for some reason is leaving the calling task in
in_interrupt() state when it shouldn't. You could try removing the
in_interrupt() test, but things will probably die later on.
It might be worth disabling preempt, although a bug there won't cause
in_interrupt() to return true.
Did you send me your .config?
Borislav Petkov
> It sounds like kdb for some reason is leaving the calling task in
> in_interrupt() state when it shouldn't. You could try removing the
> in_interrupt() test, but things will probably die later on.
is without the kdb patch.
> It might be worth disabling preempt, although a bug there won't cause
> in_interrupt() to return true.
disabling preempt doesn't change that either. I'll run more kdb sessions
tomorrow to see what's going on.
> Did you send me your .config?
yes, in some of the previous mails but here you go again.
Regards,
Boris.
Reuben Farrelly
I've done some testing this afternoon and it seems that this patch
fixes the problem in -mm4. I don't even have a serial
mouse/keyboard, but do have a serial PCI card onboard. The box has a
USB connection to a Belkin KVM instead of directly attached input devices.
I also note that it is occurring on kernel-smp-2.6.11-1.1219_FC4 - so
it is probably a problem in mainline as well as -mm.
Now I'm crashing a bit further through the shutdown, here's the stacktrace:
INIT: Sending processes the TERM signal
Stopping yum: Disabling nightly yum update: [ OK ]
[ OK ]
Stopping cups-config-daemon: [ OK ]
Stopping HAL daemon: [ OK ]
Stopping system message bus: [ OK ]
Stopping atd: [ OK ]
Stopping cups: [ OK ]
Shutting down xfs: [ OK ]
[ OK ] down console mouse services: [ OK ]
Shutting down NFS mountd: [ OK ]
Shutting down NFS daemon: nfsd: last server has exited
nfsd: unexporting all filesystems
RPC: error 5 connecting to server localhost
RPC: failed to contact portmap (errno -5).
Unable to handle kernel paging request at virtual address f2826d2c
printing eip:
c01337a9
*pde = 00000000
Oops: 0000 [#1]
SMP DEBUG_PAGEALLOC
Modules linked in: nfsd exportfs md5 ipv6 lp snd_usb_audio
snd_usb_lib pwc video
dev usb_storage autofs4 eeprom lm85 i2c_sensor rfcomm l2cap bluetooth nfs lockd
sunrpc dm_mod video button battery ac ohci1394 ieee1394 uhci_hcd
ehci_hcd parpor
t_serial parport_pc parport hw_random i2c_i801 i2c_core emu10k1_gp
gameport snd_
emu10k1 snd_rawmidi snd_seq_device snd_ac97_codec snd_pcm_oss
snd_mixer_oss snd_
pcm snd_timer snd_page_alloc snd_util_mem snd_hwdep snd soundcore
e100 mii flopp
y ext3 jbd ata_piix libata sd_mod scsi_mod
CPU: 0
EIP: 0060:[<c01337a9>] Not tainted VLI
EFLAGS: 00010087 (2.6.12-rc1-mm4)
EIP is at worker_thread+0x149/0x230
eax: 00000001 ebx: 00000212 ecx: f7eb4018 edx: f2826d20
esi: f2826d24 edi: f7eb4000 ebp: 00000000 esp: f7e83f7c
ds: 007b es: 007b ss: 0068
Process events/0 (pid: 8, threadinfo=f7e83000 task=f7fefad0)
Stack: f7eb4028 f7eb4010 f7eb4018 f7e83000 f2826d20 c014f4b0 00000001 00000000
000f41fa 00010000 00000000 00000000 f7fefad0 c011ea50 00100100 00200200
ffffffff ffffffff fffffffc f7e46f54 f7eb4000 c0133660 c0137694 ffffffff
Call Trace:
[<c014f4b0>] cache_reap+0x0/0x240
[<c011ea50>] default_wake_function+0x0/0x10
[<c0133660>] worker_thread+0x0/0x230
[<c0137694>] kthread+0x94/0xa0
[<c0137600>] kthread+0x0/0xa0
[<c01023f5>] kernel_thread_helper+0x5/0x10
Code: 00 00 89 f8 e8 19 e3 1e 00 89 c3 8b 47 40 40 89 47 40 83 f8 03
0f 8f bd 00
00 00 8b 77 10 3b 74 24 04 74 71 8d 56 fc 89 54 24 10 <8b> 42 0c 89
44 24 14 8b
6a 10 8b 46 04 8b 16 89 10 89 36 89 42
[ OK ]
Shutting down NFS quotas: [FAILED]
Shutting down NFS services: [ OK ]
Stopping sshd: [ OK ]
Stopping postfix: Shutting down postfix: <3>BUG: soft lockup
detected on CPU#0!
Pid: 3413, comm: rpc.rquotad
EIP: 0060:[<c0321ac0>] CPU: 0
EIP is at _spin_lock_irqsave+0x20/0x50
EFLAGS: 00000286 Not tainted (2.6.12-rc1-mm4)
EAX: f7eb4000 EBX: 00000246 ECX: f7eb4000 EDX: c22021a0
ESI: f7eb4000 EDI: c22021a0 EBP: c01335b0 DS: 007b ES: 007b
CR0: 8005003b CR2: 800147fc CR3: 37256d20 CR4: 000006e0
[<c013350c>] __queue_work+0xc/0x50
[<c012cc17>] run_timer_softirq+0xd7/0x1c0
[<c0128950>] __do_softirq+0x80/0x100
[<c0106adb>] do_softirq+0x4b/0x50
=======================
[<c010511c>] apic_timer_interrupt+0x1c/0x30
[<c02b7ed8>] kfree_skbmem+0x8/0x20
[<c02b007b>] cpufreq_governor+0x3b/0x50
[<c014eed2>] kfree+0x62/0x90
[<c02b7ed8>] kfree_skbmem+0x8/0x20
[<c02b7fcc>] __kfree_skb+0xdc/0x1a0
[<c02d2501>] netlink_recvmsg+0xf1/0x230
[<c02b422a>] sock_recvmsg+0xfa/0x120
[<c02b40d2>] sock_sendmsg+0xe2/0x110
[<c0137b20>] autoremove_wake_function+0x0/0x30
[<c0149d32>] __alloc_pages+0x122/0x440
[<c01d94a2>] copy_from_user+0x42/0x80
[<c02b5ba9>] sys_recvmsg+0x109/0x1e0
[<c01d94a2>] copy_from_user+0x42/0x80
[<c02b553e>] sys_sendto+0xfe/0x140
[<c011a863>] do_page_fault+0x253/0x6a1
[<c017c6a1>] d_alloc+0x141/0x1a0
[<c01648d1>] fd_install+0x21/0x50
[<c02b3e57>] sock_map_fd+0xf7/0x130
[<c032068d>] schedule+0x97d/0xc10
[<c02b5e67>] sys_socketcall+0x1e7/0x200
[<c0103fbb>] sysenter_past_esp+0x54/0x79
System is an up to date FC4- devel box with a 2.8 Ghz SMP Intel processor.
reuben
Andrew Morton
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
> >
> > - Mainly a bunch of fixes relative to 2.6.12-rc1-mm2.
>
>
> > - Again, we'd like people who have had recent DRM and USB resume problems to
> > test and report, please.
>
>
> ohci_hcd
> ehci_hcd
> yenta_socket
>
> possibly others, too. To avoid this, I had to revert the following patch from
> the Len's tree:
Rafael, does this problem still exist in latest -mm?
I think it does...
> diff -Naru a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
> --- a/drivers/acpi/pci_link.c 2005-03-24 04:57:27 -08:00
> +++ b/drivers/acpi/pci_link.c 2005-03-24 04:57:27 -08:00
> @@ -72,10 +72,12 @@
> u8 active; /* Current IRQ */
> u8 edge_level; /* All IRQs */
> u8 active_high_low; /* All IRQs */
> - u8 initialized;
> u8 resource_type;
> u8 possible_count;
> u8 possible[ACPI_PCI_LINK_MAX_POSSIBLE];
> + u8 initialized:1;
> + u8 suspend_resume:1;
> + u8 reserved:6;
> };
>
> struct acpi_pci_link {
> @@ -530,6 +532,10 @@
>
> ACPI_FUNCTION_TRACE("acpi_pci_link_allocate");
>
> + if (link->irq.suspend_resume) {
> + acpi_pci_link_set(link, link->irq.active);
> + link->irq.suspend_resume = 0;
> + }
> if (link->irq.initialized)
> return_VALUE(0);
>
> @@ -713,38 +719,24 @@
> return_VALUE(result);
> }
>
> -
> -static int
> -acpi_pci_link_resume (
> - struct acpi_pci_link *link)
> -{
> - ACPI_FUNCTION_TRACE("acpi_pci_link_resume");
> -
> - if (link->irq.active && link->irq.initialized)
> - return_VALUE(acpi_pci_link_set(link, link->irq.active));
> - else
> - return_VALUE(0);
> -}
> -
> -
> static int
> -irqrouter_resume(
> - struct sys_device *dev)
> +irqrouter_suspend(
> + struct sys_device *dev,
> + u32 state)
> {
> struct list_head *node = NULL;
> struct acpi_pci_link *link = NULL;
>
> - ACPI_FUNCTION_TRACE("irqrouter_resume");
> + ACPI_FUNCTION_TRACE("irqrouter_suspend");
>
> list_for_each(node, &acpi_link.entries) {
> -
> link = list_entry(node, struct acpi_pci_link, node);
> if (!link) {
> ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Invalid link context\n"));
> continue;
> }
> -
> - acpi_pci_link_resume(link);
> + if (link->irq.active && link->irq.initialized)
> + link->irq.suspend_resume = 1;
> }
> return_VALUE(0);
> }
> @@ -856,7 +848,7 @@
>
> static struct sysdev_class irqrouter_sysdev_class = {
> set_kset_name("irqrouter"),
> - .resume = irqrouter_resume,
> + .suspend = irqrouter_suspend,
> };
>
>
> # This is a BitKeeper generated diff -Nru style patch.
> #
> # ChangeSet
> # 2005/03/18 16:30:29-05:00 len....@intel.com
> # [ACPI] S3 Suspend to RAM: interrupt resume fix
> #
> # Delete PCI Interrupt Link Device .resume method --
> # it is the device driver's job to request interrupts,
> # not the Link's job to remember what the devices want.
> #
> # This addresses the issue of attempting to run
> # the ACPI interpreter too early in resume, when
> # interrupts are still disabled.
> #
> # http://bugzilla.kernel.org/show_bug.cgi?id=3469
> #
> # Signed-off-by: David Shaohua Li <shaoh...@intel.com>
> # Signed-off-by: Len Brown <len....@intel.com>
> #
> # drivers/acpi/pci_link.c
> # 2005/03/02 22:23:50-05:00 len....@intel.com +14 -22
> # Delete PCI Interrupt Link .resume method
> #
>
> Greets,
> Rafael
>
>
> --
> - Would you tell me, please, which way I ought to go from here?
> - That depends a good deal on where you want to get to.
> -- Lewis Carroll "Alice's Adventures in Wonderland"
Rafael J. Wysocki
On Tuesday, 3 of May 2005 00:54, Andrew Morton wrote:
> "Rafael J. Wysocki" <r...@sisk.pl> wrote:
> >
> > Hi,
> >
> > On Friday, 25 of March 2005 09:21, Andrew Morton wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm3/
> > >
> > > - Mainly a bunch of fixes relative to 2.6.12-rc1-mm2.
> >
> > First, rmmod works again (thanks ;-)).
> >
> > > - Again, we'd like people who have had recent DRM and USB resume problems to
> > > test and report, please.
> >
> > My box is still hanged solid on resume (swsusp) by the drivers:
> >
> > ohci_hcd
> > ehci_hcd
> > yenta_socket
> >
> > possibly others, too. To avoid this, I had to revert the following patch from
> > the Len's tree:
>
> Rafael, does this problem still exist in latest -mm?
Yes, it does. I've already updated its bugzilla entry
(http://bugzilla.kernel.org/show_bug.cgi?id=4416).
Andrew Morton
>
> >
> >Reuben, could you please try the patch below? Thanks!
> >
> >Russell, could you please tell me if ldisc->write_wakeup (tty_wakwup) and
> >ldisc->read are allowed to be called from an IRQ context? IOW I wonder if
> >I can use spil_lock_bh instead of spil_lock_irqsave to protect serport
> >flags.
> >
> >--
> >Dmitry
> >
> > serport.c | 98
> > +++++++++++++++++++++++++++++++++++++++++++-------------------
> > 1 files changed, 68 insertions(+), 30 deletions(-)
> >
> >Index: dtor/drivers/input/serio/serport.c
> >===================================================================
> >--- dtor.orig/drivers/input/serio/serport.c
> >+++ dtor/drivers/input/serio/serport.c
> >@@ -27,11 +27,15 @@ MODULE_LICENSE("GPL");
> > MODULE_ALIAS_LDISC(N_MOUSE);
>
>
> I've done some testing this afternoon and it seems that this patch
> fixes the problem in -mm4. I don't even have a serial
> mouse/keyboard, but do have a serial PCI card onboard. The box has a
> USB connection to a Belkin KVM instead of directly attached input devices.
>
> I also note that it is occurring on kernel-smp-2.6.11-1.1219_FC4 - so
> it is probably a problem in mainline as well as -mm.
Can you please confirm that the above fix is present in 2.6.12-rc5 and that
2.6.12-rc5 is working OK?
>
> Now I'm crashing a bit further through the shutdown, here's the stacktrace:
Is this still occurring in either 2.6.12-rc5 or 2.6.12-rc5-mm1?
Reuben Farrelly
The fix is definitely in -rc5 (thanks), and without doubt fixed the problem I
was seeing (thanks Dmitry). I haven't tested on a vanilla 2.6.12-rc5, but I
can confirm that 2.6.12-rc4-mm* releases have not had the problem. The patch
was of course in -rc4-mm* and possibly earlier?
> >>Now I'm crashing a bit further through the shutdown, here's the stacktrace:
>
>
> Is this still occurring in either 2.6.12-rc5 or 2.6.12-rc5-mm1?
2.6.12-rc4-mm* releases have been stable, I haven't seen any oopses for a few
weeks now.
If confirmation is required in -rc5 then I'm happy to attempt this, but I
don't think it's at all likely given I haven't seen any oopses at all since
that patch was included in -mm, and the patch is now in upstream.
Btw, I didn't see a lkml-announce message about -rc5-mm1 being released :( No
big deal really...