2004-04-26 08:42:04

by Andrew Morton

[permalink] [raw]
Subject: 2.6.6-rc2-mm2


ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc2/2.6.6-rc2-mm2/

- Largeish reiserfs feature update. The biggest change is probably the new
block allocation algorithm. See the changelog inside
reiserfs-group-alloc-9.patch for details.

- Added the ia64 CPU hotplug support patch

- More work against the ext3 block allocator.

- Several more framebuffer driver update, some quite substantial.

- Lots of fixes, mostly minor.




Changes since 2.6.6-rc2-mm1:


linus.patch
bk-acpi.patch
bk-agpgart.patch
bk-alsa.patch
bk-cifs.patch
bk-cpufreq.patch
bk-drm.patch
bk-input.patch
bk-libata.patch
bk-netdev.patch
bk-scsi.patch
bk-usb.patch

Latest versions of various external trees

-fix-nfsroot-option-parsing.patch
-aic7xxx-deadlock-fix.patch
-pcmcia-netdev-ordering-fixes.patch
-3ware-update.patch
-jgarzik-warnings.patch
-aic7xxx-unload-fix.patch
-rndis-fix.patch
-ext3-data-leak-fix.patch
-populate-rootfs-later.patch
-remove-amd7saucy_tco.patch
-ehci-oops-fix.patch
-lockfs-vfs-bits.patch
-lockfs-reiserfs-fix.patch
-lockfs-xfs-bits.patch
-lockfs-dm-bits.patch
-lockfs-dm-bits-2.patch
-i4l-compat-ioctls.patch
-selinux-change-context_to_sid-handling-for-no-policy-case.patch
-selinux-add-runtime-disable.patch
-selinux-remove-hardcoded-policy-assumption-from-get_user_sids-logic.patch
-i810_dma-range-check.patch
-fb_ioctl-usercopy-fix.patch
-writeback-livelock-fix.patch
-new-set-of-input-patches-lkkbd-whitespace.patch
-new-set-of-input-patches-lkkbd-simplify-checks.patch
-i386-hugetlb-tlb-correction.patch
-loop_set_fd-sendfile-check-fix.patch

Merged

-create_singlethread_workqueue-fix.patch

Folded into create_singlethread_workqueue.patch

-use-workqueue-for-call_usermodehelper-fix.patch

Folded into use-workqueue-for-call_usermodehelper.patch

+1-1-reiserfs-ignore-prepared-and-locked-buffers.patch

reiserfs fix

+frame-pointer-based-stack-dumps.patch

Use the frame pointer to generate nicer stack traces on x86.

Turns out that enabling framepointers makes basically no difference to code
size at all.

-compute-creds-race-fix.patch
-compute-creds-race-fix-fix.patch
-compute-creds-race-fix-fix-fix.patch
+credentials-locking-fix.patch

Re-fix locking around credential checks.

+ext3-journalled-quota-locking-fix.patch

Fix some ext3 locking

+bigger-quota-hashtable.patch

Quotas speedup

+per-sb-dquot-dirty-lists.patch

More quota speedups

+minor-fixes-in-journalled-quota.patch

Journalled quota fixlets

+ppc64-split-promc-into-pre-reloc-and-post-reloc-functions.patch
+ppc64-rearrage-finish_device_tree-and-its-functions-in-c.patch
+ppc64-rearrage-copy_device_tree-and-its-functions-in-c.patch
+ppc64-rearrage-interpret_funcs-in-c-order.patch
+ppc64-rearrage-rest-of-promc-in-c-order.patch
+ppc64-make-finish_device_tree-use-lmb_alloc-not-klimit.patch
+ppc64-make_room-macro-for-ppc64-promc.patch
+ppc64-fix-promc-to-boot-on-g5-after-make_room-fix.patch
+ppc64-clean-up-prom-functions-in-promc.patch
+ppc64-initrd-cleanup.patch
+ppc64-move-initrd.patch
+ppc64-remove-duplicated-mb-and-comment-from-__cpu_up.patch

PPC64 update

+acpi-build-fix.patch

Fix build prob in bk-acpi.patch

+i_shared_lock-fix-1.patch
+i_shared_lock-fix-2.patch
+i_shared_lock-mremap-fix.patch

Various fixes for the i_shared_sem->i_shared_lock conversion

+hotplug-cpu-sched_balance_exec-fix.patch

Fix deadlock with CPU hotplug and the CPU scheduler changes

+cond_resched-might-sleep.patch

Add a debug check

-warn-on-mdelay-in-irq-handlers.patch

This seems to have done its job.

+aic7xxx-deadlock-fix.patch
+aic7xxx-section-fix.patch

More adaptec driver fixes.

-numa-api-core-i_shared_sem.patch

Dropped, not needed any more.

+numa-api-docs-policy_vma-fix.patch
+include-linux-gfph-cleanup-for-numa-api.patch

NUMA API fixes

-ext3-reservation-regression-fix.patch
-ext3_rsv_mount.patch
-ext3_rsv_dw.patch

Folded into ext3_rsv_base.patch

+4-autofs4-260-expire-20040405-fix-fix.patch

Fix the autofs4 update

+new-set-of-input-patches-serio-whitespace.patch
+new-set-of-input-patches-serio-open-close-optional.patch
+psmouse-fix-mouse-hotplugging.patch

Input driver rework

+bssprot.patch
+bssprot-sparc-fix.patch
+bssprot-cleanup.patch
+bssprot-more-fixes.patch

Fix vma permissions for ELF PT_LOAD segments

+slab-alignment-fixes.patch

Slab object alignment changes

+neomagic-driver-update.patch

Update this fbdev driver

+kernel_ppc8xx_misc.patch

PPC32 build fixes

+prune_dcache-comment-fix.patch

Fix buggy comment

+m68k-superfluous-whitespace.patch
+amiga-a2065-ethernet-kern.patch
+m68k-bitops.patch

68k stuff

+efivars-remove-from-ia64.patch
+efivars-add-to-drivers-firmware.patch
+efivars-remove-x86-references.patch

EFI driver updates

+s390-9-9-no-timer-interrupts-in-idle.patch

Tickless mode for S390.

+task_lock-comment-update.patch

Fix a comment

+dio_bio_reap-retval-fix.patch

Fix a return value

+crypto_null-autoload.patch

Fix module loading

+remove-bootsect_helper-and-a-comment-fix-iii.patch

Remove unneeded code

+fix-config_sysfs=n-compile-warning.patch

Warning fix

+isofs-default-nls-charset-not-used-fix.patch

Use CONFIG_NLS_DEFAULT rather than hard-coding it.

+fixes-to-mvme5100-support-in-265.patch

PPC32 stuff

+fealnx-mac-address-and-other-issues.patch

Fix this net driver a bit.

+remove-some-unused-variables-in-s2io.patch

Cleanup for this net driver

+new-version-of-early-cpu-detect.patch
+new-version-of-early-cpu-detect-fix.patch

Bring back the very-early detection of the x86 CPU type

+slab-order-0-for-vfs-caches.patch

Prevent slab from ever using higher-order allocations for VFS caches: it's
deadlocky.

+radeon-garbled-screen-fix.patch

Radeon fix

+smb_writepage-retval-fix.patch

->writepage() return 0 or -errno. It should _not_ return the
number-of-bytes-written. Unless you want it to perform like crap, that is.

+writepage-retval-warning.patch

Runtime check for filesystem which wish to perform like crap.

+shrink_slab-handle-GFP_NOFS.patch

Fiddle with slab-vs-pagecache reclaim balancing

+simplify-put_page.patch

Require that compound pages have a destructor.

+hugepage-fixes.patch
+hugepage-fixes-fix.patch

Consolidate up a few hugetlbpage helpers

+26-isdn-eicon-driver-remove-call-to-trap-usermode-helper.patch

ISDN cleanup

+tips-for-s3-resume-on-radeon-cards.patch

Power management documentation update

+fix-3c59xc-to-allow-3c905c-100bt-fd.patch

3c59x MII programming fix

+ppc32-fix-head_44xs-copyrights.patch

PPC32 assembly code copyright corrections

+proc-array-old-gcc-fix.patch

Work around problems with older gcc's

+use-dos_extended_partition.patch

Use the provided enums rather than magic constants.

+blkdevh-functions-no-longer-inline.patch

Make declarations match implementations

+reiserfs-acl-mknod.patch
+reiserfs-xattrs-04.patch
+reiserfs-acl-02.patch
+reiserfs-trusted-02.patch
+reiserfs-selinux-02.patch
+reiserfs-xattr-locking-02.patch
+reiserfs-quota.patch
+reiserfs-permission.patch
+reiserfs-warning.patch
+reiserfs-group-alloc-9.patch
+reiserfs-group-alloc-9-build-fix.patch
+reiserfs-search_reada-5.patch

reiserfs update

+nfs_writepages-retval-fix.patch

The nfs_writepages() return value is fishy as well.

+ext3-reservation-ifdef-cleanup-patch.patch
+ext3-reservation-max-window-size-check-patch.patch
+ext3-reservation-file-ioctl-fix.patch
+ext3-lazy-discard-reservation-window-patch.patch
+ext3-discard-reservation-in-last-iput-fix-patch.patch
+ext3-discard-reservation-in-last-iput-fix-patch-fix.patch

Reservation-based ext3 block allocator updates

+include-asm-ppc-dma-mappingh-dma_unmap_page.patch

Fix ppc32's dma_unmap_page()

+nfs_writepage-retval-fix.patch

As is the nfs_writepage() return value.

+problems-with-atkbd_command--atkbd_interrupt-interaction.patch

AT keyboard fix

+fix-fs-proc-task_nommuc-compile.patch

NOMMU build fix

+remove-documentation-docbook-parportbooktmpl.patch

Remove documentation which has an inappropriate license.

+set-module-license-in-mcheck-non-fatalc.patch

Add a MODULE_LICENSE()

+submittingpatches-diffing-update.patch

Fix wording in SubmittingPatches

+mptfusion-depends-on-scsi.patch

Kconfig dependency fix

+fix-null-ptr-dereference-in-pm2fb_probe-2.patch

Fix an oops

+mark-config_mac_serial-drivers-macintosh-macserialc-as-broken.patch

This serial driver doesn't work. Mark it as broken.

+fix-warning-in-prefetch_range.patch

Fix a compile warning (I'm suspecting gcc breakage)

+virtual-fbdev-updates.patch
+vesa-fbdev-update.patch
+vesa-fbdev-update-fix.patch

fbdev updates

+ia64-cpu-hotplug-core_kernel_init.patch
+ia64-cpu-hotplug-init_removal_ia64.patch
+ia64-cpu-hotplug-sysfs_ia64.patch
+ia64-cpu-hotplug-hotcpu_ia64.patch
+ia64-cpu-hotplug-ia64_palinfo.patch
+ia64-cpu-hotplug-cpu_present.patch
+ia64-cpu-hotplug-migrate_irq.patch

Impement CPU hotplug for ia64

+promc-fix-for-config_blk_dev_initrd=n.patch

Build fix

+parport-pnp-detection-fix.patch

Maybe fix recent SuperIO parport breakage.

+scsi_disk_release-warning-fix.patch

SCSI warning fix

+8139too-suspend-fix.patch

Fix power management in this net driver

+sata_sx4-warning-fix.patch
+cifssmb-warning-fix.patch

Fix a couple of warnings.





All 308 patches


linus.patch

create_singlethread_workqueue.patch
reate_singlethread_workqueue()
create_singlethread_workqueue fix

use-workqueue-for-call_usermodehelper.patch
Use workqueue for call_usermodehelper
use-workqueue-for-call_usermodehelper fix

1-1-reiserfs-ignore-prepared-and-locked-buffers.patch
Subject: [PATCH] 1/1 reiserfs: ignore prepared and locked buffers

mc.patch
Add -mcN to EXTRAVERSION

bk-acpi.patch

bk-agpgart.patch

bk-alsa.patch

bk-cifs.patch

bk-cpufreq.patch

bk-drm.patch

bk-input.patch

bk-libata.patch

bk-netdev.patch

bk-scsi.patch

bk-usb.patch

mm.patch
add -mmN to EXTRAVERSION

frame-pointer-based-stack-dumps.patch
x86: stack dumps using frame pointers

credentials-locking-fix.patch
credentials locking fix

ext3-journalled-quota-locking-fix.patch
ext3 journalled quota locking fix

bigger-quota-hashtable.patch
Bigger quota hashtable

per-sb-dquot-dirty-lists.patch
From: Jan Kara <[email protected]>
Subject: [PATCH] Per-sb dquot dirty lists

minor-fixes-in-journalled-quota.patch
Minor fixes for ext3 journalled quotas

ppc64-split-promc-into-pre-reloc-and-post-reloc-functions.patch
ppc64: Split prom.c Into pre-reloc and post-reloc Functions

ppc64-rearrage-finish_device_tree-and-its-functions-in-c.patch
ppc64: Rearrage finish_device_tree() and its functions in C Order

ppc64-rearrage-copy_device_tree-and-its-functions-in-c.patch
ppc64: Rearrage copy_device_tree() and its functions in C Order

ppc64-rearrage-interpret_funcs-in-c-order.patch
ppc64: Rearrage interpret_funcs in C Order

ppc64-rearrage-rest-of-promc-in-c-order.patch
ppc64: Rearrage Rest of prom.c in C Order

ppc64-make-finish_device_tree-use-lmb_alloc-not-klimit.patch
ppc64: Make finish_device_tree use lmb_alloc, not klimit

ppc64-make_room-macro-for-ppc64-promc.patch
ppc64: make_room macro for ppc64 prom.c

ppc64-fix-promc-to-boot-on-g5-after-make_room-fix.patch
ppc64: Fix prom.c to boot on G5 after make_room fix

ppc64-clean-up-prom-functions-in-promc.patch
ppc64: Clean up prom functions in prom.c

ppc64-initrd-cleanup.patch
ppc64: Initrd Cleanup

ppc64-move-initrd.patch
ppc64: Move Initrd

acpi-build-fix.patch
acpi build fix

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

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

rmap-7-object-based-rmap.patch
rmap 7 object-based rmap

ia64-rmap-build-fix.patch
ia64 rmap build fix

rmap-8-unmap-nonlinear.patch
rmap 8 unmap nonlinear

slab-panic.patch
slab: consolidate panic code

rmap-9-remove-pte_chains.patch
rmap 9 remove pte_chains

rmap-10-add-anonmm-rmap.patch
rmap 10 add anonmm rmap

rmap-11-mremap-moves.patch
rmap 11 mremap moves

rmap-12-pgtable-remove-rmap.patch
rmap 12 pgtable remove rmap

rmap-13-include-asm-deletions.patch
rmap 13 include/asm deletions

i_shared_lock.patch
Convert i_shared_sem back to a spinlock

i_shared_lock-fix-1.patch
i_shared_lock fix 1

i_shared_lock-fix-2.patch
i_shared_lock fix 2

i_shared_lock-mremap-fix.patch
i_shared_lock mremap fix

must-fix.patch
must fix lists update
must fix list update
mustfix update

must-fix-update-5.patch
must-fix update

ppc64-reloc_hide.patch

invalidate_inodes-speedup.patch
invalidate_inodes speedup
more invalidate_inodes speedup fixes

config_spinline.patch
uninline spinlocks for profiling accuracy.

pdflush-diag.patch

get_user_pages-handle-VM_IO.patch
fix get_user_pages() against mappings of /dev/mem

pci_set_power_state-might-sleep.patch

CONFIG_STANDALONE-default-to-n.patch
Make CONFIG_STANDALONE default to N

selinux-inode-race-trap.patch
Try to diagnose Bug 2153

slab-leak-detector.patch
slab leak detector
mm/slab.c warning in cache_alloc_debugcheck_after

local_bh_enable-warning-fix.patch

Move-saved_command_line-to-init-mainc.patch
Move saved_command_line to init/main.c

sched-run_list-cleanup.patch
small scheduler cleanup

sched-find_busiest_node-resolution-fix.patch
sched: improved resolution in find_busiest_node

sched-domains.patch
sched: scheduler domain support
sched: fix for NR_CPUS > BITS_PER_LONG
sched: clarify find_busiest_group
sched: find_busiest_group arithmetic fix

sched-find-busiest-fix.patch
sched-find-busiest-fix

sched-sibling-map-to-cpumask.patch
sched: cpu_sibling_map to cpu_mask
p4-clockmod sibling_map fix
p4-clockmod: handle more than two siblings

sched-domains-i386-ht.patch
sched: implement domains for i386 HT
sched: Fix CONFIG_SMT oops on UP
sched: fix SMT + NUMA bug
Change arch_init_sched_domains to use cpu_online_map
Fix build with NR_CPUS > BITS_PER_LONG

sched-no-drop-balance.patch
sched: handle inter-CPU jiffies skew

sched-directed-migration.patch
sched_balance_exec(): don't fiddle with the cpus_allowed mask

sched-domain-debugging.patch
sched_domain debugging

sched-domain-balancing-improvements.patch
scheduler domain balancing improvements

sched-group-power.patch
sched-group-power
sched-group-power warning fixes

sched-domains-use-cpu_possible_map.patch
sched_domains: use cpu_possible_map

sched-smt-nice-handling.patch
sched: SMT niceness handling

sched-local-load.patch
sched: add local load metrics

process-migration-speedup.patch
Reduce TLB flushing during process migration

sched-trivial.patch
sched: trivial fixes, cleanups

sched-misc-fixes.patch
sched: misc fixes

hotplug-cpu-sched_balance_exec-fix.patch
Hotplug CPU sched_balance_exec Fix

sched-wakebalance-fixes.patch
sched: wakeup balancing fixes

sched-imbalance-fix.patch
sched: fix imbalance calculations

sched-altix-tune1.patch
sched: altix tuning

sched-fix-activelb.patch
sched: oops fix

ppc64-sched-domain-support.patch
ppc64: sched-domain support

sched-domain-setup-lock.patch
sched: fix setup races

ppc64-sched_domains-fix.patch
ppc64-sched_domains-fix

sched-domain-setup-lock-ppc64-fix.patch

sched-minor-cleanups.patch
sched: minor cleanups

sched-inline-removals.patch
sched: uninlinings

sched-move-cold-task.patch
sched: move cold task in mysteriouis ways

sched-migrate-shortcut.patch
sched: add migration shortcut

sched-more-sync-wakeups.patch
sched: extend sync wakeups

sched-boot-fix.patch
sched: lock cpu_attach_domain for hotplug

sched-cleanups.patch
sched: cleanups

sched-damp-passive-balance.patch
sched: passive balancing damping

sched-cpu-load-cleanup.patch
sched: cpu load management cleanup

sched-balance-context.patch
sched: balance-on-clone

sched-less-idle.patch
sched: reduce idle time

sched-wake_up-speedup.patch
sched: micro-optimisation for wake_up

ppc64-smt-sched-stuff.patch
ppc64: SMT scheduler support

schedstats.patch
sched: scheduler statistics

cond_resched-might-sleep.patch
cond_resched() might sleep

fa311-mac-address-fix.patch
wrong mac address with netgear FA311 ethernet card

pid_max-fix.patch
Bug when setting pid_max > 32k

use-soft-float.patch
Use -msoft-float

non-readable-binaries.patch
Handle non-readable binfmt_misc executables

binfmt_misc-credentials.patch
binfmt_misc: improve calaulation of interpreter's credentials

poll-select-longer-timeouts.patch
poll()/select(): support longer timeouts

poll-select-range-check-fix.patch
poll()/select() range checking fix

poll-select-handle-large-timeouts.patch
poll()/select(): handle long timeouts

add-a-slab-for-ethernet.patch
Add a kmalloc slab for ethernet packets

siimage-update.patch
ide: update for siimage driver

nmi_watchdog-local-apic-fix.patch
Fix nmi_watchdog=2 and P4 HT

nmi-1-hz-2.patch
reduce NMI watchdog call frequency with local APIC.

shm-do_munmap-check.patch

stack-overflow-test-fix.patch
Fix stack overflow test for non-8k stacks

jbd-remove-livelock-avoidance.patch
JBD: remove livelock avoidance code in journal_dirty_data()

logitech-keyboard-fix.patch
2.6.5-rc2 keyboard breakage

stack-reductions-nfsread.patch
stack reductions: nfs read

speed-up-sata.patch
speed up SATA

advansys-fix.patch
advansys check_region() fix

journal_add_journal_head-debug.patch
journal_add_journal_head-debug

nfs-O_DIRECT-fixes.patch
NFS: O_DIRECT fixes

nfs-direct-warning-fix.patch
nfs/direct.c warning fix

aic7xxx-deadlock-fix.patch
aic7xxx deadlock fix

aic7xxx-swsusp-support.patch
support swsusp for aic7xxx
aic79xx_osm.c build fix

aic7xxx-section-fix.patch
aic7...: Fix bad __exit reference

xfs-laptop-mode.patch
Laptop mode support for XFS

xfs-laptop-mode-syncd-synchronization.patch
Synchronize XFS sync daemon with laptop mode syncs.

list_del-debug.patch
list_del debug check

oops-dump-preceding-code.patch
i386 oops output: dump preceding code

lockmeter.patch
lockmeter
ia64 CONFIG_LOCKMETER fix

cciss-logical-device-queues.patch
cciss: per logical device queues

numa-api-x86_64.patch
numa api: -64 support

numa-api-bitmap-fix.patch
numa api: Bitmap bugfix

numa-api-i386.patch
numa api: Add i386 support

numa-api-ia64.patch
numa api: Add IA64 support

numa-api-core.patch
numa api: Core NUMA API code

numa-api-docs-policy_vma-fix.patch
numa api: docs and policy_vma() locking fix

include-linux-gfph-cleanup-for-numa-api.patch
From: Matthew Dobson <[email protected]>
Subject: [PATCH] include/linux/gfp.h cleanup for NUMA API

mpol-in-copy_vma.patch
mpol in copy_vma

numa-api-core-slab-panic.patch
numa-api-core-slab-panic

numa-api-core-tweaks.patch
numa-api-core-tweaks

numa-api-fixes.patch
Some fixes for NUMA API

numa-api-statistics-2.patch
Re-add NUMA API statistics

numa-api-core-bitmap_clear-fixes.patch
numa-api-core bitmap_clear fixes

numa-api-vma-policy-hooks.patch
numa api: Add VMA hooks for policy

numa-api-vma-policy-hooks-fix.patch
numa-api-vma-policy-hooks fix

numa-api-shared-memory-support.patch
numa api: Add shared memory support

numa-api-shared-memory-support-tweaks.patch
numa-api-shared-memory-support-tweaks

numa-api-statistics.patch
numa api: Add statistics

numa-api-anon-memory-policy.patch
numa api: Add policy support to anonymous memory

sk98lin-buggy-vpd-workaround.patch
net/sk98lin: correct buggy VPD in ASUS MB
skvpd-build-fix

unplug-can-sleep.patch
unplug functions can sleep

firestream-warnings.patch
firestream warnings

fix-acer-travelmate-360-interrupt-routing.patch
fix Acer TravelMate 360 interrupt routing

ext3_rsv_cleanup.patch
ext3 block reservation patch set -- ext3 preallocation cleanup

ext3_rsv_base.patch
ext3 block reservation patch set -- ext3 block reservation
ext3 reservations: fix performance regression
ext3 block reservation patch set -- mount and ioctl feature
ext3 block reservation patch set -- dynamically increase reservation window

ext3-reservation-default-on.patch
ext3 reservation: default to on

sched-in_sched_functions.patch
sched: in_sched_functions() cleanup

sysfs-d_fsdata-race-fix-2.patch
kobject/sysfs race fix

0-autofs4-2.6.0-signal-20040405.patch
autofs: dnotify + autofs may create signal/restart syscall loop

add-omitted-autofs4-super-block-field.patch
add omitted autofs4 super block field

1-autofs4-2.6.4-cleanup-20040405.patch
autofs: printk cleanups

2-autofs4-2.6.4-fill_super-20040405.patch

3-autofs4-2.6.0-bkl-20040405.patch
autofs: locking rework

4-autofs4-2.6.0-expire-20040405.patch
autofs: expiry refcount fixes

4-autofs4-260-expire-20040405-fix.patch
4-autofs4-2.6.0-expire-20040405 locking fix

4-autofs4-260-expire-20040405-fix-fix.patch
autofs expiry fix

5-autofs4-2.6.0-readdir-20040405.patch
autofs: readdir fixes

umount-after-bad-chdir.patch
fix umount after bad chdir

autofs4-fix-handling-of-chdir-and-chroot.patch
autofs4: fix handling of chdir and chroot

6-autofs4-2.6.0-may_umount-20040405.patch
autofs: add ioctl to query unmountability

7-autofs4-2.6.0-extra-20040405.patch
autofs: readdir futureproofing

lindent-rwsem.patch
cleanup lib/rwsem.c lib/rwsem-spinlock.c

de-racify-rwsem-take-2.patch
de-racify rwsem take 2

as-increase-batch-expiry.patch
AS: increase batch expiry intervals

consolidate-sys32_readv-and-sys32_writev.patch
Consolidate sys32_readv and sys32_writev

consolidate-do_execve32.patch
Consolidate do_execve32

consolidate-sys32_select.patch
Consolidate sys32_select

consolidate-sys32_nfsservctl.patch
Consolidate sys32_nfsservctl

intel8x0-resume-fix.patch
intel8x0 suspend/resume fix

clean-up-asm-pgalloch-include.patch
Clean up asm/pgalloc.h include

clean-up-asm-pgalloch-include-2.patch
Clean up asm/pgalloc.h include

clean-up-asm-pgalloch-include-3.patch
Clean up asm/pgalloc.h include 3

ppc64-uninline-__pte_free_tlb.patch
ppc64: uninline __pte_free_tlb()

radeon-fb-screen-corruption-fix.patch
radeonfb display corruption fix

es7000-subarch-update-2.patch
es7000 subarch update

tridentfbc-warning-fix.patch
video/tridentfb.c warning fix

hgafbc-warning-fix.patch
video/hgafb.c warning fix

imsttfbc-warning-fix.patch
video/imsttfb.c. warning fix

dquot-unneeded-test.patch
dquot: remove unneeded test

fbdev-logo-handling-fix.patch
fbdev: clean up logo handling

fbdev-redundant-prows-calculation-removal.patch
fbdev: remove redundant p->vrows calculation

fbdev-remove-redundant-local.patch
fbdev: remove redundant local

fbdev-access_align-default.patch
fbdev: set a default access_align value

kbuild-improved-external-module-support.patch
kbuild: Improved external module support

input-tsdev-fixes.patch
tsdev.c fixes

fix-scancode-keycode-scancode-conversion-for-265.patch
Fix scancode->keycode->scancode conversion

use-less-stack-in-ide_unregister.patch
use less stack in ide_unregister

string_h-needs-compiler_h.patch
string.h needs compiler.h

new-set-of-input-patches-synaptics-cleanup.patch
input: synaptics cleanup

new-set-of-input-patches-synaptics-middle-button-support.patch
input: synaptics middle button support

new-set-of-input-patches-dont-change-max-proto.patch
input: dont change max proto

new-set-of-input-patches-atkbd-soften-accusation.patch
input: atkbd soften accusation

new-set-of-input-patches-atkbd-trailing-whitespace.patch
input: atkbd trailing whitespace

new-set-of-input-patches-atkbd-use-bitfields.patch
input: atkbd - use bitfields

new-set-of-input-patches-atkbd-timeout-complaints.patch
input: atkbd timeout complaints

new-set-of-input-patches-psmouse-rescan-on-hotplug.patch
input: psmouse rescan on hotplug

new-set-of-input-patches-psmouse-reconnect-after-error.patch
input: psmouse reconnect after error

new-set-of-input-patches-psmouse-add-protocol_handler.patch
input: psmouse add protocol_handler

new-set-of-input-patches-psmouse-sliced-commands.patch
input: psmouse sliced commands

new-set-of-input-patches-atkbd-reconnect-probe.patch
input: atkbd reconnect probe

new-set-of-input-patches-allow-disabling-psaux.patch
input: allow disabling psaux

new-set-of-input-patches-serio-whitespace.patch
input: serio whitespace

new-set-of-input-patches-serio-open-close-optional.patch
input: serio open/close optional

psmouse-fix-mouse-hotplugging.patch
psmouse: fix mouse hotplugging

bssprot.patch
binfmt_elf.c: allow .bss with no access

bssprot-sparc-fix.patch
bssprot sparc64 fix

bssprot-cleanup.patch
bssprot cleanup

bssprot-more-fixes.patch
bssprot: more fixes

slab-alignment-fixes.patch
slab alignment fixes

neomagic-driver-update.patch
Neomagic driver update.

kernel_ppc8xx_misc.patch
ppc32: ppc8xx build fixes

prune_dcache-comment-fix.patch
prune_dcache comment fix

m68k-superfluous-whitespace.patch
M68k superfluous whitespace

amiga-a2065-ethernet-kern.patch
m68k: Amiga A2065 Ethernet KERN_*

m68k-bitops.patch
m68k bitops

efivars-remove-from-ia64.patch
efivars: remove from arch/ia64

efivars-add-to-drivers-firmware.patch
efivars: add to drivers/firmware

efivars-remove-x86-references.patch
efivars: remove x86 references

s390-9-9-no-timer-interrupts-in-idle.patch
s390: no timer interrupts in idle.

task_lock-comment-update.patch
task_lock() comment update

dio_bio_reap-retval-fix.patch
dio_bio_reap() return value fix

crypto_null-autoload.patch
crypto_null autoload

remove-bootsect_helper-and-a-comment-fix-iii.patch
Remove bootsect_helper and a comment fix

fix-config_sysfs=n-compile-warning.patch
fix CONFIG_SYSFS=n compile warning

isofs-default-nls-charset-not-used-fix.patch
isofs "default NLS charset not used" fix

fixes-to-mvme5100-support-in-265.patch
Fixes to MVME5100 support

fealnx-mac-address-and-other-issues.patch
Fealnx. Mac address and other issues

remove-some-unused-variables-in-s2io.patch
remove some unused variables in s2io

new-version-of-early-cpu-detect.patch
New version of early CPU detect

new-version-of-early-cpu-detect-fix.patch
new-version-of-early-cpu-detect-fix

slab-order-0-for-vfs-caches.patch
slab: use order 0 for vfs caches

radeon-garbled-screen-fix.patch
radeonfb: fix garbled screen

smb_writepage-retval-fix.patch
smb_writepage retval fix

writepage-retval-warning.patch
writepage-retval-warning

shrink_slab-handle-GFP_NOFS.patch
shrink_slab: improved handling of GFP_NOFS allocations

simplify-put_page.patch
simplify put_page()

hugepage-fixes.patch
hugepage fixes

hugepage-fixes-fix.patch
hugepage-fixes-fix

26-isdn-eicon-driver-remove-call-to-trap-usermode-helper.patch
ISDN Eicon driver: remove call to trap usermode helper

tips-for-s3-resume-on-radeon-cards.patch
Tips for S3 resume on radeon cards

fix-3c59xc-to-allow-3c905c-100bt-fd.patch
fix 3c59x.c to allow 3c905c 100bT-FD

ppc32-fix-head_44xs-copyrights.patch
ppc32: fix head_44x.S copyrights

proc-array-old-gcc-fix.patch
fs/proc/array.c: workaround for gcc-2.96

use-dos_extended_partition.patch
partitioning cleanup: use DOS_EXTENDED_PARTITION

blkdevh-functions-no-longer-inline.patch
blkdev.h: functions no longer inline

reiserfs-acl-mknod.patch
reiserfs: acl device node initialization

reiserfs-xattrs-04.patch
reiserfs: xattr support

reiserfs-acl-02.patch
reiserfs: ACL support

reiserfs-trusted-02.patch
reiserfs: support trusted xattrs

reiserfs-selinux-02.patch
reiserfs: selinux support

reiserfs-xattr-locking-02.patch
reiserfs: xattr locking fixes

reiserfs-quota.patch
reiserfs: quota support

reiserfs-permission.patch
reiserfs: xattr permission fix

reiserfs-warning.patch
reiserfs: add device info to diagnostic messages

reiserfs-group-alloc-9.patch
reiserfs: block allocator optimizations

reiserfs-group-alloc-9-build-fix.patch
reiserfs-group-alloc-9 build fix

reiserfs-search_reada-5.patch
reiserfs: btree readahead

nfs_writepages-retval-fix.patch
nfw_writepages() return value fix

ext3-reservation-ifdef-cleanup-patch.patch
ext3 reservation ifdef cleanup patch

ext3-reservation-max-window-size-check-patch.patch
ext3 reservation max window size check patch

ext3-reservation-file-ioctl-fix.patch
ext3 reservation file ioctl fix

ext3-lazy-discard-reservation-window-patch.patch
ext3 lazy discard reservation window patch

ext3-discard-reservation-in-last-iput-fix-patch.patch
ext3 discard reservation in last iput fix patch

ext3-discard-reservation-in-last-iput-fix-patch-fix.patch
Fix lazy reservation discard

include-asm-ppc-dma-mappingh-dma_unmap_page.patch
ppc32: dma_unmap_page() fix

nfs_writepage-retval-fix.patch
nfs_write-apge-retval-fix

problems-with-atkbd_command--atkbd_interrupt-interaction.patch
Problems with atkbd_command & atkbd_interrupt interaction

fix-fs-proc-task_nommuc-compile.patch
fix fs/proc/task_nommu.c compile

remove-documentation-docbook-parportbooktmpl.patch
remove Documentation/DocBook/parportbook.tmpl

set-module-license-in-mcheck-non-fatalc.patch
Set module license in mcheck/non-fatal.c

submittingpatches-diffing-update.patch
SubmittingPatches diffing update.

mptfusion-depends-on-scsi.patch
mptfusion depends on scsi

fix-null-ptr-dereference-in-pm2fb_probe-2.patch
Fix NULL-ptr dereference in pm2fb_probe

mark-config_mac_serial-drivers-macintosh-macserialc-as-broken.patch
Mark CONFIG_MAC_SERIAL (drivers/macintosh/macserial.c) as broken

fix-warning-in-prefetch_range.patch
Fix warning in prefetch_range

virtual-fbdev-updates.patch
Virtual fbdev updates

vesa-fbdev-update.patch
Vesa Fbdev update

vesa-fbdev-update-fix.patch
Vesa Fbdev update fix

ia64-cpu-hotplug-core_kernel_init.patch
IA64 hotplug: core kernel initialisation

ia64-cpu-hotplug-init_removal_ia64.patch
IA64 hotplug: init section changes

ia64-cpu-hotplug-sysfs_ia64.patch
IA64 hotplug: add sysfs entries

ia64-cpu-hotplug-hotcpu_ia64.patch
IA64 hotplug: core ia64 hotplug CPU support

ia64-cpu-hotplug-ia64_palinfo.patch
IA64 hotplug: create /proc entries in hotplug callbacks

ia64-cpu-hotplug-cpu_present.patch
IA64 hotplug: add cpu_present iterators

ia64-cpu-hotplug-migrate_irq.patch
IA64 hotplug: IRQ migration for hotplug

promc-fix-for-config_blk_dev_initrd=n.patch
prom.c fix for CONFIG_BLK_DEV_INITRD=n

ppc64-remove-duplicated-mb-and-comment-from-__cpu_up.patch
ppc64: remove duplicated mb() and comment from __cpu_up

parport-pnp-detection-fix.patch
parport pnp detection fix

scsi_disk_release-warning-fix.patch
scsi_disk_release() warning fix

8139too-suspend-fix.patch
8139too not running s3 suspend/resume pci fix

sata_sx4-warning-fix.patch
sata_sx4.c warning fix

cifssmb-warning-fix.patch
cifssmb.c warning fix




2004-04-26 16:56:18

by Zwane Mwaikambo

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

The directory is all setup on k.o but the actual file appears to have not
been compressed which confused a few scripts.

--12:24:26--
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc2/2.6.6-rc2-mm2/2.6.6-rc2-mm2.bz2
=> `/build/patches/2.6.6-rc2-mm2.bz2.partial'
Resolving http://www.kernel.org... done.
Connecting to http://www.kernel.org[204.152.189.116]:80... connected.
HTTP request sent, awaiting response... 404 Not Found

2004-04-26 17:09:19

by Ian Kent

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2


Patch to sync 2.6.6-rc2-mm2 with the result of my discussion with
Christoph Hellwig.

Difference is that Christoph realised that merging may_umount_tree and
may_umount was not worth it. They are now seperate functions.

diff -Nur linux-2.6.6-rc2-mm2.orig/fs/namespace.c linux-2.6.6-rc2-mm2/fs/namespace.c
--- linux-2.6.6-rc2-mm2.orig/fs/namespace.c 2004-04-27 00:51:36.000000000 +0800
+++ linux-2.6.6-rc2-mm2/fs/namespace.c 2004-04-27 00:43:32.000000000 +0800
@@ -260,7 +260,15 @@
.show = show_vfsmnt
};

-static int __may_umount_tree(struct vfsmount *mnt, int root_mnt_only)
+/**
+ * may_umount_tree - check if a mount tree is busy
+ * @mnt: root of mount tree
+ *
+ * This is called to check if a tree of mounts has any
+ * open files, pwds, chroots or sub mounts that are
+ * busy.
+ */
+int may_umount_tree(struct vfsmount *mnt)
{
struct list_head *next;
struct vfsmount *this_parent = mnt;
@@ -270,14 +278,6 @@
spin_lock(&vfsmount_lock);
actual_refs = atomic_read(&mnt->mnt_count);
minimum_refs = 2;
-
- if (root_mnt_only) {
- spin_unlock(&vfsmount_lock);
- if (actual_refs > minimum_refs)
- return -EBUSY;
- return 0;
- }
-
repeat:
next = this_parent->mnt_mounts.next;
resume:
@@ -308,19 +308,6 @@
return 0;
}

-/**
- * may_umount_tree - check if a mount tree is busy
- * @mnt: root of mount tree
- *
- * This is called to check if a tree of mounts has any
- * open files, pwds, chroots or sub mounts that are
- * busy.
- */
-int may_umount_tree(struct vfsmount *mnt)
-{
- return __may_umount_tree(mnt, 0);
-}
-
EXPORT_SYMBOL(may_umount_tree);

/**
@@ -338,7 +325,9 @@
*/
int may_umount(struct vfsmount *mnt)
{
- return __may_umount_tree(mnt, 1);
+ if (atomic_read(&mnt->mnt_count) > 2)
+ return -EBUSY;
+ return 0;
}

EXPORT_SYMBOL(may_umount);

2004-04-26 17:37:47

by Grzegorz Kulewski

[permalink] [raw]
Subject: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)

Hi,

I was experiencing strange problem with mm tree since at least 2.6.4-mm?.
My Gentoo startup scripts can mount root filesystem and all virtual
filesystems (procfs, sysfs, tmpfs, usbfs, devpts) but nothing more. Mount
fails for all other disk filesystems (ext3, vfat, ntfs) with EBUSY (or
-EBUSY if you like). Everything is working perfectly on 2.4, late 2.5 and
early 2.6 kernels (both mm or no). But it seems that changes in mm that
broke things for me were incorporated in mainline 2.6 somewhere between
2.6.5 and 2.6.6, because I recently tried 2.6.6-rc2-bk3 and got the same
error. This way I am still using "ancient" 2.6.2-rc2-mm? with some
additional patches...

I attached my .config file.

Could you help me (and tell me what I am doing wrong)?


Grzegorz Kulewski


Attachments:
.config (28.31 kB)

2004-04-26 18:19:40

by Linus Torvalds

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)



On Mon, 26 Apr 2004, Grzegorz Kulewski wrote:
>
> I was experiencing strange problem with mm tree since at least 2.6.4-mm?.
> My Gentoo startup scripts can mount root filesystem and all virtual
> filesystems (procfs, sysfs, tmpfs, usbfs, devpts) but nothing more. Mount
> fails for all other disk filesystems (ext3, vfat, ntfs) with EBUSY (or
> -EBUSY if you like).

Sounds like something is keeping the block device busy with an exclusive
open. But it would be easier to guess if you can specify a but more
closely on exactly when this changed:

> But it seems that changes in mm that
> broke things for me were incorporated in mainline 2.6 somewhere between
> 2.6.5 and 2.6.6, because I recently tried 2.6.6-rc2-bk3 and got the same
> error.

So 2.6.5 works, and 2.6.6-rc2-bk3 does not?

Can you check rc1/rc2 and then pinpoint it to a particular day?

Linus

2004-04-26 18:53:10

by Frédéric L. W. Meunier

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

On Mon, 26 Apr 2004, Andrew Morton wrote:

> - Several more framebuffer driver update, some quite
> substantial.

Still broken for me, as reported at
http://marc.theaimsgroup.com/?l=linux-kernel&m=108269975708471&w=2

I tried manually, and it happens after con2fb /dev/fb0
/dev/tty1.

Maybe framebuffer as modules is broken, who knows...

CONFIG_FB=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_G450=y
CONFIG_FB_MATROX_G100=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_CLUT224=y

--
http://www.pervalidus.net/contact.html

2004-04-26 22:13:30

by Linus Torvalds

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)



On Tue, 27 Apr 2004, Grzegorz Kulewski wrote:
>
> Have you any ideas what could cause the problem and what options should I
> add from not working to working config or should I start binary search?
> (On my machine kernel compiles painfully slow, so I will be glad to hear
> you have an idea where should I look...)

Try turning off MD first. Then quota, and if neither of those matters,
start tuning off the individual filesystem drivers (reiser, xfs).

Linus

2004-04-26 22:09:59

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)

On Mon, 26 Apr 2004, Linus Torvalds wrote:
> On Mon, 26 Apr 2004, Grzegorz Kulewski wrote:
> >
> > I was experiencing strange problem with mm tree since at least 2.6.4-mm?.
> > My Gentoo startup scripts can mount root filesystem and all virtual
> > filesystems (procfs, sysfs, tmpfs, usbfs, devpts) but nothing more. Mount
> > fails for all other disk filesystems (ext3, vfat, ntfs) with EBUSY (or
> > -EBUSY if you like).
>
> Sounds like something is keeping the block device busy with an exclusive
> open. But it would be easier to guess if you can specify a but more
> closely on exactly when this changed:

Ok, I tested more and found that config files used by me to compile 2.6.5
and 2.6.6-rc2-bk3 were different. This is normal, because I usually
generate them by hand (with menuconfig) for each kernel. Config for 2.6.5
was minimal (after sad experiences with newest mm...) setup that I need.
Config for 2.6.6-rc2-bk3 was much richer. So I used 2.6.5 config to
compile 2.6.6-rc2-bk3 and it was working. Next I started adding options to
it. Now I have two configs for 2.6.6-rc2-bk3. The first does work and the
second does not. I attached them and diff between (to save you typing :))

Have you any ideas what could cause the problem and what options should I
add from not working to working config or should I start binary search?
(On my machine kernel compiles painfully slow, so I will be glad to hear
you have an idea where should I look...)


thanks for anwser and waiting for more

Grzegorz Kulewski


Attachments:
diff.patch (1.41 kB)
config-not-working (23.51 kB)
config-working (23.07 kB)
Download all attachments

2004-04-26 22:38:58

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)

On Mon, 26 Apr 2004, Linus Torvalds wrote:
> Try turning off MD first. Then quota, and if neither of those matters,
> start tuning off the individual filesystem drivers (reiser, xfs).

Yes, when I turned off MD and DM it started to work. Thanks. Can I help
more to track the problem down? (I currently have no MD or DM volumes in
my system - I just wanted to start experimenting with them...)


Grzegorz Kulewski

2004-04-26 22:56:22

by Al Viro

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)

On Tue, Apr 27, 2004 at 12:38:53AM +0200, Grzegorz Kulewski wrote:
> On Mon, 26 Apr 2004, Linus Torvalds wrote:
> > Try turning off MD first. Then quota, and if neither of those matters,
> > start tuning off the individual filesystem drivers (reiser, xfs).
>
> Yes, when I turned off MD and DM it started to work. Thanks. Can I help
> more to track the problem down? (I currently have no MD or DM volumes in
> my system - I just wanted to start experimenting with them...)

Add
printk("claim: %d:%d %p -> %d\n",
MAJOR(bdev->bd_dev), MINOR(bdev->bd_dev), holder, res);
in the very end of fs/block_dev.c::bd_claim() (just before return) and
printk("release: %d:%d\n",
MAJOR(bdev->bd_dev), MINOR(bdev->bd_dev));
in bd_release() (same file).

2004-04-26 23:06:57

by John Cherry

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2 (compile stats)

For the following warning (which results in some errors as well),
the function ignore_timer_override() should be behind the
CONFIG_ACPI_BOOT
define.

CC arch/i386/kernel/dmi_scan.o
arch/i386/kernel/dmi_scan.c:569: warning: `ignore_timer_override'
defined but
not used

-----------------------------------------------------------------------

Linux 2.6 (mm tree) Compile Statistics (gcc 3.2.2)
Warnings/Errors Summary

Kernel bzImage bzImage bzImage modules bzImage modules
(defconfig) (allno) (allyes) (allyes) (allmod) (allmod)
--------------- ---------- -------- -------- -------- -------- --------
2.6.6-rc1-mm2 0w/0e 1w/5e 118w/ 0e 8w/0e 3w/0e 118w/0e
2.6.6-rc1-mm1 0w/0e 0w/7e 122w/ 0e 7w/0e 4w/0e 122w/0e
2.6.5-mm6 0w/0e 0w/0e 123w/ 0e 7w/0e 4w/0e 124w/0e
2.6.5-mm5 0w/0e 0w/0e 119w/ 0e 7w/0e 4w/0e 120w/0e
2.6.5-mm4 0w/0e 0w/0e 120w/ 0e 7w/0e 4w/0e 121w/0e
2.6.5-mm3 0w/0e 1w/0e 121w/12e 7w/0e 3w/0e 123w/0e
2.6.5-mm2 0w/0e 0w/0e 128w/12e 7w/0e 3w/0e 134w/0e
2.6.5-mm1 0w/0e 5w/0e 122w/ 0e 7w/0e 3w/0e 124w/0e
2.6.5-rc3-mm4 0w/0e 0w/0e 124w/ 0e 8w/0e 4w/0e 126w/0e
2.6.5-rc3-mm3 0w/0e 5w/0e 129w/14e 8w/0e 4w/0e 129w/6e
2.6.5-rc3-mm2 0w/0e 5w/0e 130w/14e 8w/0e 4w/0e 129w/6e
2.6.5-rc3-mm1 0w/0e 5w/0e 129w/ 0e 8w/0e 4w/0e 129w/0e
2.6.5-rc2-mm5 0w/0e 5w/0e 130w/ 0e 8w/0e 4w/0e 129w/0e
2.6.5-rc2-mm4 0w/0e 5w/0e 134w/ 0e 8w/0e 3w/0e 133w/0e
2.6.5-rc2-mm3 0w/0e 5w/0e 134w/ 0e 8w/0e 3w/0e 133w/0e
2.6.5-rc2-mm2 0w/0e 5w/0e 137w/ 0e 8w/0e 3w/0e 134w/0e
2.6.5-rc2-mm1 0w/0e 5w/0e 136w/ 0e 8w/0e 3w/0e 134w/0e
2.6.5-rc1-mm2 0w/0e 5w/0e 135w/ 5e 8w/0e 3w/0e 133w/0e
2.6.5-rc1-mm1 0w/0e 5w/0e 135w/ 5e 8w/0e 3w/0e 133w/0e
2.6.4-mm2 1w/2e 5w/2e 144w/10e 8w/0e 3w/2e 144w/0e
2.6.4-mm1 1w/0e 5w/0e 146w/ 5e 8w/0e 3w/0e 144w/0e
2.6.4-rc2-mm1 1w/0e 5w/0e 146w/12e 11w/0e 3w/0e 147w/2e
2.6.4-rc1-mm2 1w/0e 5w/0e 144w/ 0e 11w/0e 3w/0e 145w/0e
2.6.4-rc1-mm1 1w/0e 5w/0e 147w/ 5e 11w/0e 3w/0e 147w/0e
2.6.3-mm4 1w/0e 5w/0e 146w/ 0e 7w/0e 3w/0e 142w/0e
2.6.3-mm3 1w/2e 5w/2e 146w/15e 7w/0e 3w/2e 144w/5e
2.6.3-mm2 1w/8e 5w/0e 140w/ 0e 7w/0e 3w/0e 138w/0e
2.6.3-mm1 1w/0e 5w/0e 143w/ 5e 7w/0e 3w/0e 141w/0e
2.6.3-rc3-mm1 1w/0e 0w/0e 144w/13e 7w/0e 3w/0e 142w/3e
2.6.3-rc2-mm1 1w/0e 0w/265e 144w/ 5e 7w/0e 3w/0e 145w/0e
2.6.3-rc1-mm1 1w/0e 0w/265e 141w/ 5e 7w/0e 3w/0e 143w/0e
2.6.2-mm1 2w/0e 0w/264e 147w/ 5e 7w/0e 3w/0e 173w/0e
2.6.2-rc3-mm1 2w/0e 0w/265e 146w/ 5e 7w/0e 3w/0e 172w/0e
2.6.2-rc2-mm2 0w/0e 0w/264e 145w/ 5e 7w/0e 3w/0e 171w/0e
2.6.2-rc2-mm1 0w/0e 0w/264e 146w/ 5e 7w/0e 3w/0e 172w/0e
2.6.2-rc1-mm3 0w/0e 0w/265e 144w/ 8e 7w/0e 3w/0e 169w/0e
2.6.2-rc1-mm2 0w/0e 0w/264e 144w/ 5e 10w/0e 3w/0e 171w/0e
2.6.2-rc1-mm1 0w/0e 0w/264e 144w/ 5e 10w/0e 3w/0e 171w/0e
2.6.1-mm5 2w/5e 0w/264e 153w/11e 10w/0e 3w/0e 180w/0e
2.6.1-mm4 0w/821e 0w/264e 154w/ 5e 8w/1e 5w/0e 179w/0e
2.6.1-mm3 0w/0e 0w/0e 151w/ 5e 10w/0e 3w/0e 177w/0e
2.6.1-mm2 0w/0e 0w/0e 143w/ 5e 12w/0e 3w/0e 171w/0e
2.6.1-mm1 0w/0e 0w/0e 146w/ 9e 12w/0e 6w/0e 171w/0e
2.6.1-rc2-mm1 0w/0e 0w/0e 149w/ 0e 12w/0e 6w/0e 171w/4e
2.6.1-rc1-mm2 0w/0e 0w/0e 157w/15e 12w/0e 3w/0e 185w/4e
2.6.1-rc1-mm1 0w/0e 0w/0e 156w/10e 12w/0e 3w/0e 184w/2e
2.6.0-mm2 0w/0e 0w/0e 161w/ 0e 12w/0e 3w/0e 189w/0e
2.6.0-mm1 0w/0e 0w/0e 173w/ 0e 12w/0e 3w/0e 212w/0e

Web page with links to complete details:
http://developer.osdl.org/cherry/compile/

John


2004-04-27 00:05:36

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)

On Mon, 26 Apr 2004 [email protected] wrote:
> On Tue, Apr 27, 2004 at 12:38:53AM +0200, Grzegorz Kulewski wrote:
> > On Mon, 26 Apr 2004, Linus Torvalds wrote:
> > > Try turning off MD first. Then quota, and if neither of those matters,
> > > start tuning off the individual filesystem drivers (reiser, xfs).
> >
> > Yes, when I turned off MD and DM it started to work. Thanks. Can I help
> > more to track the problem down? (I currently have no MD or DM volumes in
> > my system - I just wanted to start experimenting with them...)
>
> Add
> printk("claim: %d:%d %p -> %d\n",
> MAJOR(bdev->bd_dev), MINOR(bdev->bd_dev), holder, res);
> in the very end of fs/block_dev.c::bd_claim() (just before return) and
> printk("release: %d:%d\n",
> MAJOR(bdev->bd_dev), MINOR(bdev->bd_dev));
> in bd_release() (same file).

Here is what I got:

Apr 27 01:49:23 polb01 syslog-ng[9702]: syslog-ng version 1.6.2 starting
Apr 27 01:49:23 polb01 syslog-ng[9702]: Changing permissions on special
file /dev/tty12
Apr 27 01:49:23 polb01 Linux version 2.6.6-rc2-bk3 (root@polb01) (gcc
version 3.3.3 20040217 (Gentoo Linux 3.3.3, propolice-3.3-7)) #4 Tue Apr
27 01:43:01 CEST 2004
Apr 27 01:49:23 polb01 BIOS-provided physical RAM map:
Apr 27 01:49:23 polb01 BIOS-e820: 0000000000000000 - 000000000009fc00
(usable)
Apr 27 01:49:23 polb01 BIOS-e820: 000000000009fc00 - 00000000000a0000
(reserved)
Apr 27 01:49:23 polb01 BIOS-e820: 00000000000f0000 - 0000000000100000
(reserved)
Apr 27 01:49:23 polb01 BIOS-e820: 0000000000100000 - 000000001fff0000
(usable)
Apr 27 01:49:23 polb01 BIOS-e820: 000000001fff0000 - 000000001fff3000
(ACPI NVS)
Apr 27 01:49:23 polb01 BIOS-e820: 000000001fff3000 - 0000000020000000
(ACPI data)
Apr 27 01:49:23 polb01 BIOS-e820: 00000000ffff0000 - 0000000100000000
(reserved)
Apr 27 01:49:23 polb01 511MB LOWMEM available.
Apr 27 01:49:23 polb01 On node 0 totalpages: 131056
Apr 27 01:49:23 polb01 DMA zone: 4096 pages, LIFO batch:1
Apr 27 01:49:23 polb01 Normal zone: 126960 pages, LIFO batch:16
Apr 27 01:49:23 polb01 HighMem zone: 0 pages, LIFO batch:1
Apr 27 01:49:23 polb01 DMI 2.2 present.
Apr 27 01:49:23 polb01 ACPI: RSDP (v000 761686
) @ 0x000f6810
Apr 27 01:49:23 polb01 ACPI: RSDT (v001 761686 AWRDACPI 0x42302e31 AWRD
0x00000000) @ 0x1fff3000
Apr 27 01:49:23 polb01 ACPI: FADT (v001 761686 AWRDACPI 0x42302e31 AWRD
0x00000000) @ 0x1fff3040
Apr 27 01:49:23 polb01 ACPI: DSDT (v001 761686 AWRDACPI 0x00001000 MSFT
0x0100000c) @ 0x00000000
Apr 27 01:49:23 polb01 ACPI: PM-Timer IO Port: 0x4008
Apr 27 01:49:23 polb01 Built 1 zonelists
Apr 27 01:49:23 polb01 Kernel command line: ro root=/dev/hdd4
Apr 27 01:49:23 polb01 Local APIC disabled by BIOS -- reenabling.
Apr 27 01:49:23 polb01 Found and enabled local APIC!
Apr 27 01:49:23 polb01 Initializing CPU#0
Apr 27 01:49:23 polb01 PID hash table entries: 2048 (order 11: 16384
bytes)
Apr 27 01:49:23 polb01 Detected 1001.762 MHz processor.
Apr 27 01:49:23 polb01 Using pmtmr for high-res timesource
Apr 27 01:49:23 polb01 Console: colour VGA+ 80x25
Apr 27 01:49:23 polb01 Memory: 515000k/524224k available (2788k kernel
code, 8472k reserved, 567k data, 132k init, 0k highmem)
Apr 27 01:49:23 polb01 Checking if this processor honours the WP bit even
in supervisor mode... Ok.
Apr 27 01:49:23 polb01 Calibrating delay loop... 1982.46 BogoMIPS
Apr 27 01:49:23 polb01 Dentry cache hash table entries: 65536 (order: 6,
262144 bytes)
Apr 27 01:49:23 polb01 Inode-cache hash table entries: 32768 (order: 5,
131072 bytes)
Apr 27 01:49:23 polb01 Mount-cache hash table entries: 512 (order: 0, 4096
bytes)
Apr 27 01:49:23 polb01 CPU: After generic identify, caps: 0183fbff
c1c7fbff 00000000 00000000
Apr 27 01:49:23 polb01 CPU: After vendor identify, caps: 0183fbff
c1c7fbff 00000000 00000000
Apr 27 01:49:23 polb01 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K
(64 bytes/line)
Apr 27 01:49:23 polb01 CPU: L2 Cache: 256K (64 bytes/line)
Apr 27 01:49:23 polb01 CPU: After all inits, caps: 0183fbf7 c1c7fbff
00000000 00000020
Apr 27 01:49:23 polb01 Intel machine check architecture supported.
Apr 27 01:49:23 polb01 Intel machine check reporting enabled on CPU#0.
Apr 27 01:49:23 polb01 CPU: AMD Athlon(tm) processor stepping 02
Apr 27 01:49:23 polb01 Enabling fast FPU save and restore... done.
Apr 27 01:49:23 polb01 Checking 'hlt' instruction... OK.
Apr 27 01:49:23 polb01 POSIX conformance testing by UNIFIX
Apr 27 01:49:23 polb01 enabled ExtINT on CPU#0
Apr 27 01:49:23 polb01 ESR value before enabling vector: 00000000
Apr 27 01:49:23 polb01 ESR value after enabling vector: 00000000
Apr 27 01:49:23 polb01 Using local APIC timer interrupts.
Apr 27 01:49:23 polb01 calibrating APIC timer ...
Apr 27 01:49:23 polb01 ..... CPU clock speed is 1001.0108 MHz.
Apr 27 01:49:23 polb01 ..... host bus clock speed is 266.0962 MHz.
Apr 27 01:49:23 polb01 NET: Registered protocol family 16
Apr 27 01:49:23 polb01 PCI: PCI BIOS revision 2.10 entry at 0xfb5e0, last
bus=1
Apr 27 01:49:23 polb01 PCI: Using configuration type 1
Apr 27 01:49:23 polb01 mtrr: v2.0 (20020519)
Apr 27 01:49:23 polb01 ACPI: Subsystem revision 20040326
Apr 27 01:49:23 polb01 ACPI: IRQ11 SCI: Level Trigger.
Apr 27 01:49:23 polb01 spurious 8259A interrupt: IRQ7.
Apr 27 01:49:23 polb01 ACPI: Interpreter enabled
Apr 27 01:49:23 polb01 ACPI: Using PIC for interrupt routing
Apr 27 01:49:23 polb01 ACPI: PCI Root Bridge [PCI0] (00:00)
Apr 27 01:49:23 polb01 PCI: Probing PCI hardware (bus 00)
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7
*10 11 12 14 15)
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7
10 11 12 14 15)
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7
10 11 12 14 15)
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7
10 *11 12 14 15)
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 9
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
Apr 27 01:49:23 polb01 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
Apr 27 01:49:23 polb01 PCI: Using ACPI for IRQ routing
Apr 27 01:49:23 polb01 PCI: if you experience problems, try using option
'pci=noacpi' or even 'acpi=off'
Apr 27 01:49:23 polb01 ikconfig 0.7 with /proc/config*
Apr 27 01:49:23 polb01 Total HugeTLB memory allocated, 0
Apr 27 01:49:23 polb01 VFS: Disk quotas dquot_6.5.1
Apr 27 01:49:23 polb01 SGI XFS with ACLs, security attributes, realtime,
no debug enabled
Apr 27 01:49:23 polb01 SGI XFS Quota Management subsystem
Apr 27 01:49:23 polb01 Initializing Cryptographic API
Apr 27 01:49:23 polb01 Serial: 8250/16550 driver $Revision: 1.90 $ 8
ports, IRQ sharing disabled
Apr 27 01:49:23 polb01 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Apr 27 01:49:23 polb01 ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Apr 27 01:49:23 polb01 8139too Fast Ethernet driver 0.9.27
Apr 27 01:49:23 polb01 eth0: RealTek RTL8139 at 0xe000, 00:06:4f:00:73:8b,
IRQ 11
Apr 27 01:49:23 polb01 eth0: Identified 8139 chip type 'RTL-8139C'
Apr 27 01:49:23 polb01 Uniform Multi-Platform E-IDE driver Revision:
7.00alpha2
Apr 27 01:49:23 polb01 ide: Assuming 33MHz system bus speed for PIO modes;
override with idebus=xx
Apr 27 01:49:23 polb01 VP_IDE: IDE controller at PCI slot 0000:00:07.1
Apr 27 01:49:23 polb01 VP_IDE: chipset revision 6
Apr 27 01:49:23 polb01 VP_IDE: not 100% native mode: will probe irqs later
Apr 27 01:49:23 polb01 VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100
controller on pci0000:00:07.1
Apr 27 01:49:23 polb01 ide0: BM-DMA at 0xd400-0xd407, BIOS settings:
hda:DMA, hdb:pio
Apr 27 01:49:23 polb01 ide1: BM-DMA at 0xd408-0xd40f, BIOS settings:
hdc:DMA, hdd:DMA
Apr 27 01:49:23 polb01 hda: SAMSUNG SV6004H, ATA DISK drive
Apr 27 01:49:23 polb01 Using anticipatory io scheduler
Apr 27 01:49:23 polb01 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Apr 27 01:49:23 polb01 hdc: PIONEER DVD-ROM DVD-115, ATAPI CD/DVD-ROM
drive
Apr 27 01:49:23 polb01 hdd: SAMSUNG SV3063H, ATA DISK drive
Apr 27 01:49:23 polb01 ide1 at 0x170-0x177,0x376 on irq 15
Apr 27 01:49:23 polb01 hda: max request size: 128KiB
Apr 27 01:49:23 polb01 hda: 117306000 sectors (60060 MB) w/468KiB Cache,
CHS=65535/16/63, UDMA(100)
Apr 27 01:49:23 polb01 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
Apr 27 01:49:23 polb01 hdd: max request size: 128KiB
Apr 27 01:49:23 polb01 hdd: 59797584 sectors (30616 MB) w/426KiB Cache,
CHS=59323/16/63, UDMA(100)
Apr 27 01:49:23 polb01 hdd: hdd1 hdd2 hdd3 hdd4
Apr 27 01:49:23 polb01 mice: PS/2 mouse device common for all mice
Apr 27 01:49:23 polb01 serio: i8042 AUX port at 0x60,0x64 irq 12
Apr 27 01:49:23 polb01 input: PS/2 Generic Mouse on isa0060/serio1
Apr 27 01:49:23 polb01 serio: i8042 KBD port at 0x60,0x64 irq 1
Apr 27 01:49:23 polb01 input: AT Translated Set 2 keyboard on
isa0060/serio0
Apr 27 01:49:23 polb01 NET: Registered protocol family 2
Apr 27 01:49:23 polb01 IP: routing cache hash table of 1024 buckets,
32Kbytes
Apr 27 01:49:23 polb01 TCP: Hash tables configured (established 32768 bind
9362)
Apr 27 01:49:23 polb01 ACPI: (supports S0 S1 S4 S5)
Apr 27 01:49:23 polb01 claim: 22:68 c0407320 -> 0
Apr 27 01:49:23 polb01 release: 22:68
Apr 27 01:49:23 polb01 claim: 22:68 c0407aa0 -> 0
Apr 27 01:49:23 polb01 kjournald starting. Commit interval 5 seconds
Apr 27 01:49:23 polb01 EXT3-fs: mounted filesystem with ordered data mode.
Apr 27 01:49:23 polb01 VFS: Mounted root (ext3 filesystem) readonly.
Apr 27 01:49:23 polb01 Freeing unused kernel memory: 132k freed
Apr 27 01:49:23 polb01 NET: Registered protocol family 1
Apr 27 01:49:23 polb01 EXT3 FS on hdd4, internal journal
Apr 27 01:49:23 polb01 CSLIP: code copyright 1989 Regents of the
University of California
Apr 27 01:49:23 polb01 PPP generic driver version 2.4.2
Apr 27 01:49:23 polb01 PPP Deflate Compression module registered
Apr 27 01:49:23 polb01 NET: Registered protocol family 8
Apr 27 01:49:23 polb01 NET: Registered protocol family 20
Apr 27 01:49:23 polb01 ACPI: Power Button (FF) [PWRF]
Apr 27 01:49:23 polb01 ACPI: Sleep Button (CM) [SLPB]
Apr 27 01:49:23 polb01 ACPI: Processor [CPU0] (supports C1, 2 throttling
states)
Apr 27 01:49:23 polb01 input: PC Speaker
Apr 27 01:49:23 polb01 inserting floppy driver for 2.6.6-rc2-bk3
Apr 27 01:49:23 polb01 Floppy drive(s): fd0 is 1.44M
Apr 27 01:49:23 polb01 FDC 0 is a post-1991 82077
Apr 27 01:49:23 polb01 loop: loaded (max 8 devices)
Apr 27 01:49:23 polb01 Non-volatile memory driver v1.2
Apr 27 01:49:23 polb01 BIOS EDD facility v0.13 2004-Mar-09, 2 devices
found
Apr 27 01:49:23 polb01 Please report your BIOS at
http://linux.dell.com/edd/results.html
Apr 27 01:49:23 polb01 device-mapper: 4.1.0-ioctl (2003-12-10)
initialised: [email protected]
Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 01:49:23 polb01
Apr 27 01:49:23 polb01 device-mapper: error adding target to table
Apr 27 01:49:23 polb01 claim: 3:5 c0407aa0 -> -16
Apr 27 01:49:23 polb01 claim: 3:2 e0947800 -> -16
Apr 27 01:49:23 polb01 NTFS driver 2.1.6 [Flags: R/O MODULE].
Apr 27 01:49:23 polb01 claim: 3:3 e09176c0 -> -16
Apr 27 01:49:23 polb01 usbcore: registered new driver usbfs
Apr 27 01:49:23 polb01 usbcore: registered new driver hub
Apr 27 01:49:23 polb01 Real Time Clock Driver v1.12
Apr 27 01:49:23 polb01 parport_pc: Strange, can't probe Via 686A parallel
port: io=0x378, irq=-1, dma=-1
Apr 27 01:49:23 polb01 USB Universal Host Controller Interface driver v2.2
Apr 27 01:49:23 polb01 uhci_hcd 0000:00:07.2: UHCI Host Controller
Apr 27 01:49:23 polb01 uhci_hcd 0000:00:07.2: irq 11, io base 0000d800
Apr 27 01:49:23 polb01 uhci_hcd 0000:00:07.2: new USB bus registered,
assigned bus number 1
Apr 27 01:49:23 polb01 hub 1-0:1.0: USB hub found
Apr 27 01:49:23 polb01 hub 1-0:1.0: 2 ports detected
Apr 27 01:49:23 polb01 uhci_hcd 0000:00:07.3: UHCI Host Controller
Apr 27 01:49:23 polb01 uhci_hcd 0000:00:07.3: irq 11, io base 0000dc00
Apr 27 01:49:23 polb01 uhci_hcd 0000:00:07.3: new USB bus registered,
assigned bus number 2
Apr 27 01:49:23 polb01 hub 2-0:1.0: USB hub found
Apr 27 01:49:23 polb01 hub 2-0:1.0: 2 ports detected
Apr 27 01:49:23 polb01 usb 1-1: new full speed USB device using address 2
Apr 27 01:49:23 polb01 usbcore: registered new driver speedtch
Apr 27 01:49:23 polb01 usb 1-2: new full speed USB device using address 3
Apr 27 01:49:23 polb01 gameport: pci0000:00:09.1 speed 1242 kHz
Apr 27 01:49:23 polb01 usb 1-1: usbfs: interface 1 claimed while
'modem_run' sets config #1
Apr 27 01:49:23 polb01 usb 1-1: usbfs: interface 2 claimed while
'modem_run' sets config #1
Apr 27 01:49:23 polb01 eth0: link down
Apr 27 01:49:23 polb01 usb 1-1: usbfs: interface 0 claimed while
'modem_run' sets config #1
Apr 27 01:49:23 polb01 usb 1-1: usbfs: interface 1 claimed while
'modem_run' sets config #1
Apr 27 01:49:23 polb01 usb 1-1: usbfs: interface 2 claimed while
'modem_run' sets config #1
Apr 27 01:49:25 polb01 named[9892]: starting BIND 9.2.2-P1 -u named -n 1
Apr 27 01:49:25 polb01 named[9892]: using 1 CPU
Apr 27 01:49:25 polb01 named[9892]: loading configuration from
'/etc/bind/named.conf'
Apr 27 01:49:25 polb01 named[9892]: listening on IPv4 interface lo,
127.0.0.1#53
Apr 27 01:49:25 polb01 process `named' is using obsolete setsockopt
SO_BSDCOMPAT
Apr 27 01:49:25 polb01 init: Activating demand-procedures for 'A'
Apr 27 01:49:25 polb01 named[9892]: command channel listening on
127.0.0.1#953
Apr 27 01:49:25 polb01 named[9892]: zone 127.in-addr.arpa/IN: loaded
serial 2002081601
Apr 27 01:49:25 polb01 named[9892]: zone localhost/IN: loaded serial
2002081601
Apr 27 01:49:25 polb01 named[9892]: running
Apr 27 01:49:34 polb01 gdm[10087]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 01:49:35 polb01 modem_run[9364]: [monitoring report] ADSL link went
up
Apr 27 01:49:36 polb01 gdm[10233]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 01:49:42 polb01 gdm[10371]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 01:49:47 polb01 gdm[10515]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 01:49:47 polb01 gdm[10085]: deal_with_x_crashes: Uruchamianie
skryptu XKeepsCrashing
Apr 27 01:49:51 polb01 modem_run[8122]: ADSL synchronization has been
obtained
Apr 27 01:49:51 polb01 modem_run[8122]: ADSL line is up (640 kbit/s down |
160 kbit/s up)
Apr 27 01:49:51 polb01 modem_run[9364]: Error reading interrupts
Apr 27 01:49:51 polb01 modem_run[9364]: [monitoring report] ADSL link went
down
Apr 27 01:49:52 polb01 modem_run[9364]: Device disconnected, shutting down
Apr 27 01:49:52 polb01 login(pam_unix)[9972]: session opened for user root
by (uid=0)
Apr 27 01:49:52 polb01 pppd[10731]: Plugin /usr/lib/pppoatm.so loaded.
Apr 27 01:49:52 polb01 pppd[10731]: PPPoATM plugin_init
Apr 27 01:49:52 polb01 pppd[10731]: PPPoATM setdevname - remove unwanted
options
Apr 27 01:49:52 polb01 pppd[10731]: PPPoATM setdevname_pppoatm -
SUCCESS:0.35
Apr 27 01:49:52 polb01 pppd[10736]: pppd 2.4.2 started by root, uid 0
Apr 27 01:49:52 polb01 pppd[10736]: Using interface ppp0
Apr 27 01:49:52 polb01 pppd[10736]: Connect: ppp0 <--> 0.35
Apr 27 01:50:02 polb01 pppd[10736]: LCP: timeout sending Config-Requests
Apr 27 01:50:02 polb01 pppd[10736]: Connection terminated.
Apr 27 01:50:03 polb01 claim: 3:5 c0407aa0 -> -16
Apr 27 01:50:06 polb01 pppd[10736]: connect(0.35): Address already in use
Apr 27 01:50:06 polb01 pppd[10736]: Exit.
Apr 27 01:50:15 polb01 pppd[10875]: Plugin /usr/lib/pppoatm.so loaded.
Apr 27 01:50:15 polb01 pppd[10875]: PPPoATM plugin_init
Apr 27 01:50:15 polb01 pppd[10875]: PPPoATM setdevname - remove unwanted
options
Apr 27 01:50:15 polb01 pppd[10875]: PPPoATM setdevname_pppoatm -
SUCCESS:0.35
Apr 27 01:50:15 polb01 pppd[10876]: pppd 2.4.2 started by root, uid 0
Apr 27 01:50:15 polb01 pppd[10876]: Using interface ppp0
Apr 27 01:50:15 polb01 pppd[10876]: Connect: ppp0 <--> 0.35
Apr 27 01:50:22 polb01 pppd[10876]: CHAP authentication succeeded
Apr 27 01:50:22 polb01 PPP BSD Compression module registered
Apr 27 01:50:22 polb01 pppd[10876]: local IP address 83.31.85.169
Apr 27 01:50:22 polb01 pppd[10876]: remote IP address 213.25.2.31
Apr 27 01:50:24 polb01 claim: 3:5 c0407aa0 -> -16
Apr 27 01:50:24 polb01 claim: 3:2 e0947800 -> -16
Apr 27 01:50:24 polb01 claim: 3:3 e09176c0 -> -16
Apr 27 01:50:45 polb01 init: Switching to runlevel: 6
Apr 27 01:50:48 polb01 SysRq : Emergency Sync
Apr 27 01:50:48 polb01 Emergency Sync complete
Apr 27 01:50:49 polb01 SysRq : Emergency Sync
Apr 27 01:50:49 polb01 Emergency Sync complete
Apr 27 01:50:49 polb01 SysRq : Emergency Sync
Apr 27 01:50:49 polb01 Emergency Sync complete
Apr 27 01:50:49 polb01 SysRq : Emergency Sync
Apr 27 01:50:49 polb01 Emergency Sync complete
Apr 27 01:50:59 polb01 named[9892]: shutting down
Apr 27 01:50:59 polb01 named[9892]: stopping command channel on
127.0.0.1#953
Apr 27 01:50:59 polb01 named[9892]: no longer listening on 127.0.0.1#53
Apr 27 01:50:59 polb01 named[9892]: exiting
Apr 27 01:51:02 polb01 sshd[9558]: Received signal 15; terminating.
Apr 27 01:51:04 polb01 syslog-ng[9702]: syslog-ng version 1.6.2 going down


And here is my /etc/fstab:

/dev/hdd4 / ext3 noatime
0 0
/dev/hda5 /mnt/old ext3 noatime
0 0
/dev/hda6 /mnt/old/home ext3 noatime
0 0
/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,ro,user
0 0
/dev/hda2 /mnt/fat vfat
defaults,dmask=0000,fmask=0111,noexec 0 0
/dev/hda3 /mnt/win ntfs
defaults,dmask=0222,fmask=0111,noexec,ro 0 0


I am going down now! (It is after 2am in Warsaw.) Goodnight.
But I will probably be accessible in the morning...


Grzegorz Kulewski

2004-04-27 00:23:28

by Al Viro

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)

On Tue, Apr 27, 2004 at 02:04:40AM +0200, Grzegorz Kulewski wrote:
> Apr 27 01:49:23 polb01 claim: 22:68 c0407320 -> 0
> Apr 27 01:49:23 polb01 release: 22:68

grabbed and released hdd4

> Apr 27 01:49:23 polb01 claim: 22:68 c0407aa0 -> 0

grabbed hdd4

> Apr 27 01:49:23 polb01 kjournald starting. Commit interval 5 seconds
> Apr 27 01:49:23 polb01 EXT3-fs: mounted filesystem with ordered data mode.
> Apr 27 01:49:23 polb01 VFS: Mounted root (ext3 filesystem) readonly.
> Apr 27 01:49:23 polb01 Freeing unused kernel memory: 132k freed
> Apr 27 01:49:23 polb01 NET: Registered protocol family 1
> Apr 27 01:49:23 polb01 EXT3 FS on hdd4, internal journal

... and that was apparently done by mount()

> Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
> Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
> Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
> Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
> Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
> Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0

whee... 6 claims of hda - all by the same owner.

> Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16
> Apr 27 01:49:23 polb01 device-mapper: : dm-linear: Device lookup failed
> Apr 27 01:49:23 polb01
> Apr 27 01:49:23 polb01 device-mapper: error adding target to table
> Apr 27 01:49:23 polb01 claim: 22:64 e08e223e -> -16

[several times]

a bunch of attempts to claim hdd for the same guy - failed since hdd4 is
claimed already.

> Apr 27 01:49:23 polb01 claim: 3:5 c0407aa0 -> -16
> Apr 27 01:49:23 polb01 claim: 3:2 e0947800 -> -16

... and failing attempts to claim hda5 and hda2, since hda had been claimed and
never released.


IOW, dm.c doesn't release what it'd claimed, even after it gives up on probing.

2004-04-27 00:43:41

by Al Viro

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)

BTW, why on the earth had the damn thing tried to grab hda 6
times? It was _not_ touching partitions - all claims (i.e. open_dev()
calls in dm-table.c) had been for dev == MKDEV(3.0).

What userland tools do you have and how are they invoked? Having
a leak like that (it looks like we have a struct dm_dev leaking there,
so destructor is never called) is a bug in any case, but I really wonder
what had triggered these opens in the first place.

2004-04-27 01:00:30

by Linus Torvalds

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?)



On Tue, 27 Apr 2004 [email protected] wrote:
> > Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
>
> whee... 6 claims of hda - all by the same owner.

Would it make sense to add a "dump_stack()" and to print out the name of
the binary that causes this too? Ie add something like

printk("dumping stack for %s:\n", current->comm);
dump_stack();

to the bd_claim() debugging thing...

It will fill the logs, but I don't think it happens often enough to be a
bother...

Linus

2004-04-27 01:07:51

by Al Viro

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Mon, Apr 26, 2004 at 06:00:12PM -0700, Linus Torvalds wrote:
>
>
> On Tue, 27 Apr 2004 [email protected] wrote:
> > > Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
> >
> > whee... 6 claims of hda - all by the same owner.
>
> Would it make sense to add a "dump_stack()" and to print out the name of
> the binary that causes this too? Ie add something like
>
> printk("dumping stack for %s:\n", current->comm);
> dump_stack();
>
> to the bd_claim() debugging thing...
>
> It will fill the logs, but I don't think it happens often enough to be a
> bother...

I'd put it in drivers/md/dm-table.c::open_dev() - it's practically certain
candidate for that crap (note the subsequent failing claims of hdd - they
are definitely from dm code).

2004-04-27 09:13:55

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Tue, 27 Apr 2004 [email protected] wrote:
> On Mon, Apr 26, 2004 at 06:00:12PM -0700, Linus Torvalds wrote:
> > On Tue, 27 Apr 2004 [email protected] wrote:
> > > > Apr 27 01:49:23 polb01 claim: 3:0 e08e223e -> 0
> > >
> > > whee... 6 claims of hda - all by the same owner.
> >
> > Would it make sense to add a "dump_stack()" and to print out the name of
> > the binary that causes this too?

Ok, here it goes:

Apr 27 10:59:50 polb01 syslog-ng[9786]: syslog-ng version 1.6.2 starting
Apr 27 10:59:50 polb01 syslog-ng[9786]: Changing permissions on special
file /dev/tty12
Apr 27 10:59:50 polb01 Linux version 2.6.6-rc2-bk3 (root@polb01) (gcc
version 3.3.3 20040217 (Gentoo Linux 3.3.3, propolice-3.3-7)) #5 Tue Apr
27 10:49:36 CEST 2004
Apr 27 10:59:50 polb01 BIOS-provided physical RAM map:
Apr 27 10:59:50 polb01 BIOS-e820: 0000000000000000 - 000000000009fc00
(usable)
Apr 27 10:59:50 polb01 BIOS-e820: 000000000009fc00 - 00000000000a0000
(reserved)
Apr 27 10:59:50 polb01 BIOS-e820: 00000000000f0000 - 0000000000100000
(reserved)
Apr 27 10:59:50 polb01 BIOS-e820: 0000000000100000 - 000000001fff0000
(usable)
Apr 27 10:59:50 polb01 BIOS-e820: 000000001fff0000 - 000000001fff3000
(ACPI NVS)
Apr 27 10:59:50 polb01 BIOS-e820: 000000001fff3000 - 0000000020000000
(ACPI data)
Apr 27 10:59:50 polb01 BIOS-e820: 00000000ffff0000 - 0000000100000000
(reserved)
Apr 27 10:59:50 polb01 511MB LOWMEM available.
Apr 27 10:59:50 polb01 On node 0 totalpages: 131056
Apr 27 10:59:50 polb01 DMA zone: 4096 pages, LIFO batch:1
Apr 27 10:59:50 polb01 Normal zone: 126960 pages, LIFO batch:16
Apr 27 10:59:50 polb01 HighMem zone: 0 pages, LIFO batch:1
Apr 27 10:59:50 polb01 DMI 2.2 present.
Apr 27 10:59:50 polb01 ACPI: RSDP (v000 761686
) @ 0x000f6810
Apr 27 10:59:50 polb01 ACPI: RSDT (v001 761686 AWRDACPI 0x42302e31 AWRD
0x00000000) @ 0x1fff3000
Apr 27 10:59:50 polb01 ACPI: FADT (v001 761686 AWRDACPI 0x42302e31 AWRD
0x00000000) @ 0x1fff3040
Apr 27 10:59:50 polb01 ACPI: DSDT (v001 761686 AWRDACPI 0x00001000 MSFT
0x0100000c) @ 0x00000000
Apr 27 10:59:50 polb01 ACPI: PM-Timer IO Port: 0x4008
Apr 27 10:59:50 polb01 Built 1 zonelists
Apr 27 10:59:50 polb01 Kernel command line: ro root=/dev/hdd4
Apr 27 10:59:50 polb01 Local APIC disabled by BIOS -- reenabling.
Apr 27 10:59:50 polb01 Found and enabled local APIC!
Apr 27 10:59:50 polb01 Initializing CPU#0
Apr 27 10:59:50 polb01 PID hash table entries: 2048 (order 11: 16384
bytes)
Apr 27 10:59:50 polb01 Detected 1001.762 MHz processor.
Apr 27 10:59:50 polb01 Using pmtmr for high-res timesource
Apr 27 10:59:50 polb01 Console: colour VGA+ 80x25
Apr 27 10:59:50 polb01 Memory: 515000k/524224k available (2788k kernel
code, 8472k reserved, 567k data, 132k init, 0k highmem)
Apr 27 10:59:50 polb01 Checking if this processor honours the WP bit even
in supervisor mode... Ok.
Apr 27 10:59:50 polb01 Calibrating delay loop... 1982.46 BogoMIPS
Apr 27 10:59:50 polb01 Dentry cache hash table entries: 65536 (order: 6,
262144 bytes)
Apr 27 10:59:50 polb01 Inode-cache hash table entries: 32768 (order: 5,
131072 bytes)
Apr 27 10:59:50 polb01 Mount-cache hash table entries: 512 (order: 0, 4096
bytes)
Apr 27 10:59:50 polb01 CPU: After generic identify, caps: 0183fbff
c1c7fbff 00000000 00000000
Apr 27 10:59:50 polb01 CPU: After vendor identify, caps: 0183fbff
c1c7fbff 00000000 00000000
Apr 27 10:59:50 polb01 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K
(64 bytes/line)
Apr 27 10:59:50 polb01 CPU: L2 Cache: 256K (64 bytes/line)
Apr 27 10:59:50 polb01 CPU: After all inits, caps: 0183fbf7 c1c7fbff
00000000 00000020
Apr 27 10:59:50 polb01 Intel machine check architecture supported.
Apr 27 10:59:50 polb01 Intel machine check reporting enabled on CPU#0.
Apr 27 10:59:50 polb01 CPU: AMD Athlon(tm) processor stepping 02
Apr 27 10:59:50 polb01 Enabling fast FPU save and restore... done.
Apr 27 10:59:50 polb01 Checking 'hlt' instruction... OK.
Apr 27 10:59:50 polb01 POSIX conformance testing by UNIFIX
Apr 27 10:59:50 polb01 enabled ExtINT on CPU#0
Apr 27 10:59:50 polb01 ESR value before enabling vector: 00000000
Apr 27 10:59:50 polb01 ESR value after enabling vector: 00000000
Apr 27 10:59:50 polb01 Using local APIC timer interrupts.
Apr 27 10:59:50 polb01 calibrating APIC timer ...
Apr 27 10:59:50 polb01 ..... CPU clock speed is 1001.0108 MHz.
Apr 27 10:59:50 polb01 ..... host bus clock speed is 266.0962 MHz.
Apr 27 10:59:50 polb01 NET: Registered protocol family 16
Apr 27 10:59:50 polb01 PCI: PCI BIOS revision 2.10 entry at 0xfb5e0, last
bus=1
Apr 27 10:59:50 polb01 PCI: Using configuration type 1
Apr 27 10:59:50 polb01 mtrr: v2.0 (20020519)
Apr 27 10:59:50 polb01 ACPI: Subsystem revision 20040326
Apr 27 10:59:50 polb01 ACPI: IRQ11 SCI: Level Trigger.
Apr 27 10:59:50 polb01 spurious 8259A interrupt: IRQ7.
Apr 27 10:59:50 polb01 ACPI: Interpreter enabled
Apr 27 10:59:50 polb01 ACPI: Using PIC for interrupt routing
Apr 27 10:59:50 polb01 ACPI: PCI Root Bridge [PCI0] (00:00)
Apr 27 10:59:50 polb01 PCI: Probing PCI hardware (bus 00)
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7
*10 11 12 14 15)
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7
10 11 12 14 15)
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7
10 11 12 14 15)
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7
10 *11 12 14 15)
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 9
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
Apr 27 10:59:50 polb01 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
Apr 27 10:59:50 polb01 PCI: Using ACPI for IRQ routing
Apr 27 10:59:50 polb01 PCI: if you experience problems, try using option
'pci=noacpi' or even 'acpi=off'
Apr 27 10:59:50 polb01 ikconfig 0.7 with /proc/config*
Apr 27 10:59:50 polb01 Total HugeTLB memory allocated, 0
Apr 27 10:59:50 polb01 VFS: Disk quotas dquot_6.5.1
Apr 27 10:59:50 polb01 SGI XFS with ACLs, security attributes, realtime,
no debug enabled
Apr 27 10:59:50 polb01 SGI XFS Quota Management subsystem
Apr 27 10:59:50 polb01 Initializing Cryptographic API
Apr 27 10:59:50 polb01 Serial: 8250/16550 driver $Revision: 1.90 $ 8
ports, IRQ sharing disabled
Apr 27 10:59:50 polb01 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Apr 27 10:59:50 polb01 ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Apr 27 10:59:50 polb01 8139too Fast Ethernet driver 0.9.27
Apr 27 10:59:50 polb01 eth0: RealTek RTL8139 at 0xe000, 00:06:4f:00:73:8b,
IRQ 11
Apr 27 10:59:50 polb01 eth0: Identified 8139 chip type 'RTL-8139C'
Apr 27 10:59:50 polb01 Uniform Multi-Platform E-IDE driver Revision:
7.00alpha2
Apr 27 10:59:50 polb01 ide: Assuming 33MHz system bus speed for PIO modes;
override with idebus=xx
Apr 27 10:59:50 polb01 VP_IDE: IDE controller at PCI slot 0000:00:07.1
Apr 27 10:59:50 polb01 VP_IDE: chipset revision 6
Apr 27 10:59:50 polb01 VP_IDE: not 100% native mode: will probe irqs later
Apr 27 10:59:50 polb01 VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100
controller on pci0000:00:07.1
Apr 27 10:59:50 polb01 ide0: BM-DMA at 0xd400-0xd407, BIOS settings:
hda:DMA, hdb:pio
Apr 27 10:59:50 polb01 ide1: BM-DMA at 0xd408-0xd40f, BIOS settings:
hdc:DMA, hdd:DMA
Apr 27 10:59:50 polb01 hda: SAMSUNG SV6004H, ATA DISK drive
Apr 27 10:59:50 polb01 Using anticipatory io scheduler
Apr 27 10:59:50 polb01 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Apr 27 10:59:50 polb01 hdc: PIONEER DVD-ROM DVD-115, ATAPI CD/DVD-ROM
drive
Apr 27 10:59:50 polb01 hdd: SAMSUNG SV3063H, ATA DISK drive
Apr 27 10:59:50 polb01 ide1 at 0x170-0x177,0x376 on irq 15
Apr 27 10:59:50 polb01 hda: max request size: 128KiB
Apr 27 10:59:50 polb01 hda: 117306000 sectors (60060 MB) w/468KiB Cache,
CHS=65535/16/63, UDMA(100)
Apr 27 10:59:50 polb01 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
Apr 27 10:59:50 polb01 hdd: max request size: 128KiB
Apr 27 10:59:50 polb01 hdd: 59797584 sectors (30616 MB) w/426KiB Cache,
CHS=59323/16/63, UDMA(100)
Apr 27 10:59:50 polb01 hdd: hdd1 hdd2 hdd3 hdd4
Apr 27 10:59:50 polb01 mice: PS/2 mouse device common for all mice
Apr 27 10:59:50 polb01 serio: i8042 AUX port at 0x60,0x64 irq 12
Apr 27 10:59:50 polb01 input: PS/2 Generic Mouse on isa0060/serio1
Apr 27 10:59:50 polb01 serio: i8042 KBD port at 0x60,0x64 irq 1
Apr 27 10:59:50 polb01 input: AT Translated Set 2 keyboard on
isa0060/serio0
Apr 27 10:59:50 polb01 NET: Registered protocol family 2
Apr 27 10:59:50 polb01 IP: routing cache hash table of 1024 buckets,
32Kbytes
Apr 27 10:59:50 polb01 TCP: Hash tables configured (established 32768 bind
9362)
Apr 27 10:59:50 polb01 ACPI: (supports S0 S1 S4 S5)
Apr 27 10:59:50 polb01 claim: 22:68 c0407320 -> 0
Apr 27 10:59:50 polb01 dumping stack for swapper:
Apr 27 10:59:50 polb01 Call Trace:
Apr 27 10:59:50 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:50 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 10:59:50 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 10:59:50 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 10:59:50 polb01 [<c01e04be>] get_super_block+0x2e/0x30
Apr 27 10:59:50 polb01 [<c01dfd30>] reiserfs_fill_super+0x0/0x710
Apr 27 10:59:50 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 10:59:50 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 10:59:50 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 10:59:50 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 10:59:50 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 10:59:50 polb01 [<c044afee>] do_mount_root+0x2e/0xa0
Apr 27 10:59:50 polb01 [<c044b0b2>] mount_block_root+0x52/0x120
Apr 27 10:59:50 polb01 [<c016d5e7>] sys_access+0x87/0x140
Apr 27 10:59:50 polb01 [<c044b1e0>] mount_root+0x60/0x70
Apr 27 10:59:50 polb01 [<c044b20d>] prepare_namespace+0x1d/0xd0
Apr 27 10:59:50 polb01 [<c044bf58>] populate_rootfs+0x28/0x50
Apr 27 10:59:50 polb01 [<c01005b8>] init+0x248/0x2d0
Apr 27 10:59:50 polb01 [<c0100370>] init+0x0/0x2d0
Apr 27 10:59:50 polb01 [<c01032b1>] kernel_thread_helper+0x5/0x14
Apr 27 10:59:50 polb01
Apr 27 10:59:50 polb01 release: 22:68
Apr 27 10:59:50 polb01 dumping stack for swapper:
Apr 27 10:59:50 polb01 Call Trace:
Apr 27 10:59:50 polb01 [<c017c8a4>] close_bdev_excl+0x14/0x20
Apr 27 10:59:50 polb01 [<c0177271>] deactivate_super+0xd1/0x2b0
Apr 27 10:59:50 polb01 [<c017a4c4>] sb_set_blocksize+0x24/0x50
Apr 27 10:59:50 polb01 [<c0179f19>] get_sb_bdev+0x159/0x160
Apr 27 10:59:50 polb01 [<c01e04be>] get_super_block+0x2e/0x30
Apr 27 10:59:50 polb01 [<c01dfd30>] reiserfs_fill_super+0x0/0x710
Apr 27 10:59:50 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 10:59:50 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 10:59:50 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 10:59:50 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 10:59:50 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 10:59:50 polb01 [<c044afee>] do_mount_root+0x2e/0xa0
Apr 27 10:59:50 polb01 [<c044b0b2>] mount_block_root+0x52/0x120
Apr 27 10:59:50 polb01 [<c016d5e7>] sys_access+0x87/0x140
Apr 27 10:59:50 polb01 [<c044b1e0>] mount_root+0x60/0x70
Apr 27 10:59:50 polb01 [<c044b20d>] prepare_namespace+0x1d/0xd0
Apr 27 10:59:50 polb01 [<c044bf58>] populate_rootfs+0x28/0x50
Apr 27 10:59:50 polb01 [<c01005b8>] init+0x248/0x2d0
Apr 27 10:59:50 polb01 [<c0100370>] init+0x0/0x2d0
Apr 27 10:59:50 polb01 [<c01032b1>] kernel_thread_helper+0x5/0x14
Apr 27 10:59:50 polb01
Apr 27 10:59:50 polb01 claim: 22:68 c0407aa0 -> 0
Apr 27 10:59:50 polb01 dumping stack for swapper:
Apr 27 10:59:50 polb01 Call Trace:
Apr 27 10:59:50 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:50 polb01 [<c01773ab>] deactivate_super+0x20b/0x2b0
Apr 27 10:59:50 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 10:59:50 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 10:59:50 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 10:59:50 polb01 [<c0204d4e>] ext3_get_sb+0x2e/0x30
Apr 27 10:59:50 polb01 [<c0203210>] ext3_fill_super+0x0/0xb90
Apr 27 10:59:50 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 10:59:50 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 10:59:50 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 10:59:50 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 10:59:50 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 10:59:50 polb01 [<c044afee>] do_mount_root+0x2e/0xa0
Apr 27 10:59:50 polb01 [<c044b0b2>] mount_block_root+0x52/0x120
Apr 27 10:59:50 polb01 [<c016d5e7>] sys_access+0x87/0x140
Apr 27 10:59:50 polb01 [<c044b1e0>] mount_root+0x60/0x70
Apr 27 10:59:50 polb01 [<c044b20d>] prepare_namespace+0x1d/0xd0
Apr 27 10:59:50 polb01 [<c044bf58>] populate_rootfs+0x28/0x50
Apr 27 10:59:50 polb01 [<c01005b8>] init+0x248/0x2d0
Apr 27 10:59:50 polb01 [<c0100370>] init+0x0/0x2d0
Apr 27 10:59:50 polb01 [<c01032b1>] kernel_thread_helper+0x5/0x14
Apr 27 10:59:50 polb01
Apr 27 10:59:50 polb01 kjournald starting. Commit interval 5 seconds
Apr 27 10:59:50 polb01 EXT3-fs: hdd4: orphan cleanup on readonly fs
Apr 27 10:59:50 polb01 ext3_orphan_cleanup: deleting unreferenced inode
1194323
Apr 27 10:59:50 polb01 EXT3-fs: hdd4: 1 orphan inode deleted
Apr 27 10:59:50 polb01 EXT3-fs: recovery complete.
Apr 27 10:59:50 polb01 EXT3-fs: mounted filesystem with ordered data mode.
Apr 27 10:59:50 polb01 VFS: Mounted root (ext3 filesystem) readonly.
Apr 27 10:59:50 polb01 Freeing unused kernel memory: 132k freed
Apr 27 10:59:50 polb01 NET: Registered protocol family 1
Apr 27 10:59:50 polb01 EXT3 FS on hdd4, internal journal
Apr 27 10:59:50 polb01 CSLIP: code copyright 1989 Regents of the
University of California
Apr 27 10:59:50 polb01 PPP generic driver version 2.4.2
Apr 27 10:59:50 polb01 PPP Deflate Compression module registered
Apr 27 10:59:50 polb01 NET: Registered protocol family 8
Apr 27 10:59:50 polb01 NET: Registered protocol family 20
Apr 27 10:59:50 polb01 ACPI: Power Button (FF) [PWRF]
Apr 27 10:59:50 polb01 ACPI: Sleep Button (CM) [SLPB]
Apr 27 10:59:50 polb01 ACPI: Processor [CPU0] (supports C1, 2 throttling
states)
Apr 27 10:59:50 polb01 input: PC Speaker
Apr 27 10:59:50 polb01 inserting floppy driver for 2.6.6-rc2-bk3
Apr 27 10:59:50 polb01 Floppy drive(s): fd0 is 1.44M
Apr 27 10:59:50 polb01 FDC 0 is a post-1991 82077
Apr 27 10:59:50 polb01 loop: loaded (max 8 devices)
Apr 27 10:59:50 polb01 Non-volatile memory driver v1.2
Apr 27 10:59:50 polb01 BIOS EDD facility v0.13 2004-Mar-09, 2 devices
found
Apr 27 10:59:50 polb01 Please report your BIOS at
http://linux.dell.com/edd/results.html
Apr 27 10:59:50 polb01 device-mapper: 4.1.0-ioctl (2003-12-10)
initialised: [email protected]
Apr 27 10:59:50 polb01 claim: 3:0 e08e223e -> 0
Apr 27 10:59:50 polb01 dumping stack for evms_activate:
Apr 27 10:59:50 polb01 Call Trace:
Apr 27 10:59:50 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:50 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:50 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:50 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:50 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:50 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:50 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:50 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:50 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:50 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:50 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:50 polb01
Apr 27 10:59:50 polb01 claim: 3:0 e08e223e -> 0
Apr 27 10:59:50 polb01 dumping stack for evms_activate:
Apr 27 10:59:50 polb01 Call Trace:
Apr 27 10:59:50 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:50 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:50 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:50 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:50 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:50 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:50 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:50 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:50 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:50 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:50 polb01
Apr 27 10:59:50 polb01 claim: 3:0 e08e223e -> 0
Apr 27 10:59:50 polb01 dumping stack for evms_activate:
Apr 27 10:59:50 polb01 Call Trace:
Apr 27 10:59:50 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:50 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:50 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:50 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:50 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:50 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:50 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:50 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:50 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:50 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:50 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:50 polb01
Apr 27 10:59:50 polb01 claim: 3:0 e08e223e -> 0
Apr 27 10:59:50 polb01 dumping stack for evms_activate:
Apr 27 10:59:50 polb01 Call Trace:
Apr 27 10:59:50 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:50 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 claim: 3:0 e08e223e -> 0
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 claim: 3:0 e08e223e -> 0
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c012212e>] profile_hook+0x2e/0x46
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 22:64 e08e223e -> -16
Apr 27 10:59:51 polb01 dumping stack for evms_activate:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<e08de458>] open_dev+0x58/0x70 [dm_mod]
Apr 27 10:59:51 polb01 [<e08de681>] __table_get_device+0x121/0x1a0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08de73d>] dm_get_device+0x3d/0x190 [dm_mod]
Apr 27 10:59:51 polb01 [<c02e02ef>] sscanf+0x1f/0x24
Apr 27 10:59:51 polb01 [<e08df93f>] linear_ctr+0x7f/0xd0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08dec57>] dm_table_add_target+0x107/0x1b0
[dm_mod]
Apr 27 10:59:51 polb01 [<e08e1560>] populate_table+0x80/0xe0 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e161e>] table_load+0x5e/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e1e3e>] ctl_ioctl+0xde/0x140 [dm_mod]
Apr 27 10:59:51 polb01 [<e08e15c0>] table_load+0x0/0x130 [dm_mod]
Apr 27 10:59:51 polb01 [<c0189415>] sys_ioctl+0x205/0x3f0
Apr 27 10:59:51 polb01 [<c016f539>] sys_write+0x59/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: : dm-linear: Device lookup failed
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 device-mapper: error adding target to table
Apr 27 10:59:51 polb01 claim: 3:5 c0407aa0 -> -16
Apr 27 10:59:51 polb01 dumping stack for mount:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 10:59:51 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 10:59:51 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 10:59:51 polb01 [<c0204d4e>] ext3_get_sb+0x2e/0x30
Apr 27 10:59:51 polb01 [<c0203210>] ext3_fill_super+0x0/0xb90
Apr 27 10:59:51 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 10:59:51 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 10:59:51 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 10:59:51 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 10:59:51 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 claim: 3:2 e0947800 -> -16
Apr 27 10:59:51 polb01 dumping stack for mount:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 10:59:51 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 10:59:51 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 10:59:51 polb01 [<e0945b0e>] vfat_get_sb+0x2e/0x30 [vfat]
Apr 27 10:59:51 polb01 [<e0945a80>] vfat_fill_super+0x0/0x60 [vfat]
Apr 27 10:59:51 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 10:59:51 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 10:59:51 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 10:59:51 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 10:59:51 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 10:59:51 polb01 [<c016f51f>] sys_write+0x3f/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 NTFS driver 2.1.6 [Flags: R/O MODULE].
Apr 27 10:59:51 polb01 claim: 3:3 e09176c0 -> -16
Apr 27 10:59:51 polb01 dumping stack for mount:
Apr 27 10:59:51 polb01 Call Trace:
Apr 27 10:59:51 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 10:59:51 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 10:59:51 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 10:59:51 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 10:59:51 polb01 [<e090f51e>] ntfs_get_sb+0x2e/0x30 [ntfs]
Apr 27 10:59:51 polb01 [<e090ed30>] ntfs_fill_super+0x0/0x7a0 [ntfs]
Apr 27 10:59:51 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 10:59:51 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 10:59:51 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 10:59:51 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 10:59:51 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 10:59:51 polb01 [<c016f51f>] sys_write+0x3f/0x60
Apr 27 10:59:51 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 10:59:51 polb01
Apr 27 10:59:51 polb01 usbcore: registered new driver usbfs
Apr 27 10:59:51 polb01 usbcore: registered new driver hub
Apr 27 10:59:51 polb01 Real Time Clock Driver v1.12
Apr 27 10:59:51 polb01 parport_pc: Strange, can't probe Via 686A parallel
port: io=0x378, irq=-1, dma=-1
Apr 27 10:59:51 polb01 USB Universal Host Controller Interface driver v2.2
Apr 27 10:59:51 polb01 uhci_hcd 0000:00:07.2: UHCI Host Controller
Apr 27 10:59:51 polb01 uhci_hcd 0000:00:07.2: irq 11, io base 0000d800
Apr 27 10:59:51 polb01 uhci_hcd 0000:00:07.2: new USB bus registered,
assigned bus number 1
Apr 27 10:59:51 polb01 hub 1-0:1.0: USB hub found
Apr 27 10:59:51 polb01 hub 1-0:1.0: 2 ports detected
Apr 27 10:59:51 polb01 uhci_hcd 0000:00:07.3: UHCI Host Controller
Apr 27 10:59:51 polb01 uhci_hcd 0000:00:07.3: irq 11, io base 0000dc00
Apr 27 10:59:51 polb01 uhci_hcd 0000:00:07.3: new USB bus registered,
assigned bus number 2
Apr 27 10:59:51 polb01 hub 2-0:1.0: USB hub found
Apr 27 10:59:51 polb01 hub 2-0:1.0: 2 ports detected
Apr 27 10:59:51 polb01 usb 1-1: new full speed USB device using address 2
Apr 27 10:59:51 polb01 usbcore: registered new driver speedtch
Apr 27 10:59:51 polb01 usb 1-2: new full speed USB device using address 3
Apr 27 10:59:51 polb01 gameport: pci0000:00:09.1 speed 1242 kHz
Apr 27 10:59:51 polb01 usb 1-1: usbfs: interface 1 claimed while
'modem_run' sets config #1
Apr 27 10:59:51 polb01 usb 1-1: usbfs: interface 2 claimed while
'modem_run' sets config #1
Apr 27 10:59:51 polb01 eth0: link down
Apr 27 10:59:51 polb01 usb 1-1: usbfs: interface 0 claimed while
'modem_run' sets config #1
Apr 27 10:59:51 polb01 usb 1-1: usbfs: interface 1 claimed while
'modem_run' sets config #1
Apr 27 10:59:51 polb01 usb 1-1: usbfs: interface 2 claimed while
'modem_run' sets config #1
Apr 27 10:59:52 polb01 named[9970]: starting BIND 9.2.2-P1 -u named -n 1
Apr 27 10:59:52 polb01 named[9970]: using 1 CPU
Apr 27 10:59:52 polb01 named[9970]: loading configuration from
'/etc/bind/named.conf'
Apr 27 10:59:52 polb01 named[9970]: listening on IPv4 interface lo,
127.0.0.1#53
Apr 27 10:59:52 polb01 process `named' is using obsolete setsockopt
SO_BSDCOMPAT
Apr 27 10:59:53 polb01 init: Activating demand-procedures for 'A'
Apr 27 10:59:53 polb01 named[9970]: command channel listening on
127.0.0.1#953
Apr 27 10:59:53 polb01 named[9970]: zone 127.in-addr.arpa/IN: loaded
serial 2002081601
Apr 27 10:59:53 polb01 named[9970]: zone localhost/IN: loaded serial
2002081601
Apr 27 10:59:53 polb01 named[9970]: running
Apr 27 11:00:01 polb01 modem_run[9361]: [monitoring report] ADSL link went
up
Apr 27 11:00:02 polb01 gdm[10165]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 11:00:05 polb01 gdm[10313]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 11:00:08 polb01 login(pam_unix)[10052]: session opened for user
root by (uid=0)
Apr 27 11:00:10 polb01 gdm[10453]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 11:00:15 polb01 gdm[10599]: gdm_slave_xioerror_handler: Powany bd X
- restartowanie :0
Apr 27 11:00:15 polb01 gdm[10163]: deal_with_x_crashes: Uruchamianie
skryptu XKeepsCrashing
Apr 27 11:00:15 polb01 claim: 3:5 c0407aa0 -> -16
Apr 27 11:00:15 polb01 dumping stack for mount:
Apr 27 11:00:15 polb01 Call Trace:
Apr 27 11:00:15 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 11:00:15 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 11:00:15 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 11:00:15 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 11:00:15 polb01 [<c0204d4e>] ext3_get_sb+0x2e/0x30
Apr 27 11:00:15 polb01 [<c0203210>] ext3_fill_super+0x0/0xb90
Apr 27 11:00:15 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 11:00:15 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 11:00:15 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 11:00:15 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 11:00:15 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 11:00:15 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 11:00:15 polb01
Apr 27 11:00:18 polb01 modem_run[8152]: ADSL synchronization has been
obtained
Apr 27 11:00:18 polb01 modem_run[8152]: ADSL line is up (640 kbit/s down |
160 kbit/s up)
Apr 27 11:00:18 polb01 modem_run[9361]: Error reading interrupts
Apr 27 11:00:18 polb01 modem_run[9361]: [monitoring report] ADSL link went
down
Apr 27 11:00:19 polb01 modem_run[9361]: Device disconnected, shutting down
Apr 27 11:00:19 polb01 pppd[10812]: Plugin /usr/lib/pppoatm.so loaded.
Apr 27 11:00:19 polb01 pppd[10812]: PPPoATM plugin_init
Apr 27 11:00:19 polb01 pppd[10812]: PPPoATM setdevname - remove unwanted
options
Apr 27 11:00:19 polb01 pppd[10812]: PPPoATM setdevname_pppoatm -
SUCCESS:0.35
Apr 27 11:00:20 polb01 pppd[10813]: pppd 2.4.2 started by root, uid 0
Apr 27 11:00:20 polb01 pppd[10813]: Using interface ppp0
Apr 27 11:00:20 polb01 pppd[10813]: Connect: ppp0 <--> 0.35
Apr 27 11:00:23 polb01 pppd[10813]: CHAP authentication succeeded
Apr 27 11:00:23 polb01 PPP BSD Compression module registered
Apr 27 11:00:23 polb01 pppd[10813]: local IP address 83.31.101.12
Apr 27 11:00:23 polb01 pppd[10813]: remote IP address 213.25.2.31
Apr 27 11:00:25 polb01 claim: 3:5 c0407aa0 -> -16
Apr 27 11:00:25 polb01 dumping stack for mount:
Apr 27 11:00:25 polb01 Call Trace:
Apr 27 11:00:25 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 11:00:25 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 11:00:25 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 11:00:25 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 11:00:25 polb01 [<c0204d4e>] ext3_get_sb+0x2e/0x30
Apr 27 11:00:25 polb01 [<c0203210>] ext3_fill_super+0x0/0xb90
Apr 27 11:00:25 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 11:00:25 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 11:00:25 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 11:00:25 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 11:00:25 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 11:00:25 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 11:00:25 polb01
Apr 27 11:00:25 polb01 claim: 3:2 e0947800 -> -16
Apr 27 11:00:25 polb01 dumping stack for mount:
Apr 27 11:00:25 polb01 Call Trace:
Apr 27 11:00:25 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 11:00:25 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 11:00:25 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 11:00:25 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 11:00:25 polb01 [<e0945b0e>] vfat_get_sb+0x2e/0x30 [vfat]
Apr 27 11:00:25 polb01 [<e0945a80>] vfat_fill_super+0x0/0x60 [vfat]
Apr 27 11:00:25 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 11:00:25 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 11:00:25 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 11:00:25 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 11:00:25 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 11:00:25 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 11:00:25 polb01
Apr 27 11:00:25 polb01 claim: 3:3 e09176c0 -> -16
Apr 27 11:00:25 polb01 dumping stack for mount:
Apr 27 11:00:25 polb01 Call Trace:
Apr 27 11:00:25 polb01 [<c017b72b>] bd_claim+0x16b/0x210
Apr 27 11:00:25 polb01 [<c017c865>] open_bdev_excl+0x75/0xa0
Apr 27 11:00:25 polb01 [<c0179de8>] get_sb_bdev+0x28/0x160
Apr 27 11:00:25 polb01 [<c015032c>] __kmalloc+0x19c/0x250
Apr 27 11:00:25 polb01 [<e090f51e>] ntfs_get_sb+0x2e/0x30 [ntfs]
Apr 27 11:00:25 polb01 [<e090ed30>] ntfs_fill_super+0x0/0x7a0 [ntfs]
Apr 27 11:00:25 polb01 [<c017a116>] do_kern_mount+0x56/0xd0
Apr 27 11:00:25 polb01 [<c019c6ab>] do_add_mount+0x7b/0x1a0
Apr 27 11:00:25 polb01 [<c019c9b0>] do_mount+0x130/0x180
Apr 27 11:00:25 polb01 [<c019c82d>] copy_mount_options+0x5d/0xb0
Apr 27 11:00:25 polb01 [<c019cf9d>] sys_mount+0x11d/0x270
Apr 27 11:00:25 polb01 [<c016f51f>] sys_write+0x3f/0x60
Apr 27 11:00:25 polb01 [<c010593d>] sysenter_past_esp+0x52/0x71
Apr 27 11:00:25 polb01
Apr 27 11:00:35 polb01 SysRq : Emergency Sync
Apr 27 11:00:35 polb01 Emergency Sync complete
Apr 27 11:00:35 polb01 SysRq : Emergency Sync
Apr 27 11:00:35 polb01 Emergency Sync complete
Apr 27 11:00:35 polb01 SysRq : Emergency Sync
Apr 27 11:00:35 polb01 Emergency Sync complete
Apr 27 11:00:35 polb01 SysRq : Emergency Sync
Apr 27 11:00:35 polb01 Emergency Sync complete
Apr 27 11:00:35 polb01 SysRq : Emergency Sync
Apr 27 11:00:35 polb01 Emergency Sync complete
Apr 27 11:00:36 polb01 SysRq : Emergency Sync
Apr 27 11:00:36 polb01 Emergency Sync complete
Apr 27 11:00:36 polb01 SysRq : Emergency Sync
Apr 27 11:00:36 polb01 Emergency Sync complete
Apr 27 11:00:36 polb01 SysRq : Emergency Sync
Apr 27 11:00:36 polb01 Emergency Sync complete
Apr 27 11:00:36 polb01 SysRq : Emergency Sync
Apr 27 11:00:36 polb01 Emergency Sync complete
Apr 27 11:00:39 polb01 init: Switching to runlevel: 6
Apr 27 11:00:53 polb01 named[9970]: shutting down
Apr 27 11:00:53 polb01 named[9970]: stopping command channel on
127.0.0.1#953
Apr 27 11:00:53 polb01 named[9970]: no longer listening on 127.0.0.1#53
Apr 27 11:00:53 polb01 named[9970]: exiting
Apr 27 11:00:56 polb01 sshd[9635]: Received signal 15; terminating.
Apr 27 11:00:58 polb01 syslog-ng[9786]: syslog-ng version 1.6.2 going down

uff...

evms_activate is called blindly from startup scripts in case important
filesystems (/usr, /var) reside on it.


Grzegorz Kulewski

2004-04-27 12:50:55

by Chris Mason

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Tue, 2004-04-27 at 05:12, Grzegorz Kulewski wrote:

> uff...
>
> evms_activate is called blindly from startup scripts in case important
> filesystems (/usr, /var) reside on it.
>

Oh, it's evms

http://evms.sourceforge.net/install/kernel.html#bdclaim

EVMS 2.3.1 might work better for you.

-chris


2004-04-27 13:07:31

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Tue, 27 Apr 2004, Chris Mason wrote:
> On Tue, 2004-04-27 at 05:12, Grzegorz Kulewski wrote:
> > evms_activate is called blindly from startup scripts in case important
> > filesystems (/usr, /var) reside on it.
>
> Oh, it's evms
>
> http://evms.sourceforge.net/install/kernel.html#bdclaim
>
> EVMS 2.3.1 might work better for you.

Thanks!

But it is strange that I need kernel patch even if I have no evms
or dm volumes in my system. Can not it be solved in mainstream kernels?
Maybe there should be warning in config help temporaily? Maybe even note
after option name?


But thanks anyway,

Grzegorz Kulewski

2004-04-27 14:05:42

by Paul Komkoff

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

Replying to Grzegorz Kulewski:
> But it is strange that I need kernel patch even if I have no evms
> or dm volumes in my system. Can not it be solved in mainstream kernels?
> Maybe there should be warning in config help temporaily? Maybe even note
> after option name?

This defect grew up off a disagreement between bdclaim authors and
evms authors, but as gentoo is topmost in this pyramid I consider it's
guilty :)

just exclude yours partitioned drivers out of evms scan
(/etc/evms.conf)
-or-
mount it thru evms nodes (/dev/evms/*)

--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head

2004-04-27 18:34:18

by Al Viro

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Tue, Apr 27, 2004 at 06:05:34PM +0400, Paul P Komkoff Jr wrote:
> Replying to Grzegorz Kulewski:
> > But it is strange that I need kernel patch even if I have no evms
> > or dm volumes in my system. Can not it be solved in mainstream kernels?
> > Maybe there should be warning in config help temporaily? Maybe even note
> > after option name?
>
> This defect grew up off a disagreement between bdclaim authors and
> evms authors

Excuse me? The damn thing had found nothing. However, it didn't care
to release the devices it had claimed - hadn't even closed them, as the
matter of fact. That's a clear and obvious bug, regardless of any
disagreements.

Speaking of the proposed "solutions", how about #4: figure out what,
when and for how long do they really want to claim and take care to
release what they don't end up using?

WTF is going on there?

2004-04-27 20:06:30

by Paul Komkoff

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

Replying to [email protected]:
> On Tue, Apr 27, 2004 at 06:05:34PM +0400, Paul P Komkoff Jr wrote:
> > Replying to Grzegorz Kulewski:
> > > But it is strange that I need kernel patch even if I have no evms
> > > or dm volumes in my system. Can not it be solved in mainstream kernels?
> > > Maybe there should be warning in config help temporaily? Maybe even note
> > > after option name?
> >
> > This defect grew up off a disagreement between bdclaim authors and
> > evms authors
>
> Excuse me? The damn thing had found nothing. However, it didn't care
> to release the devices it had claimed - hadn't even closed them, as the
> matter of fact. That's a clear and obvious bug, regardless of any
> disagreements.

As far as I can see from here, evms parsed partition table, called
dmsetup several times and created corresponding nodes in /dev/evms.

Thus we allowed to mount /dev/evms/hda1 but /dev/hda1 stopped working.
That's why it did not released hda - because it has active devmapper
on top.

> Speaking of the proposed "solutions", how about #4: figure out what,
> when and for how long do they really want to claim and take care to
> release what they don't end up using?

Logic is easy - evms trying to concentrate block device management
into its own hands, but we have in-kernel partitioning code to
consider ...

> WTF is going on there?

:(

--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head

2004-04-27 20:28:17

by Al Viro

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Wed, Apr 28, 2004 at 12:04:59AM +0400, Paul P Komkoff Jr wrote:
> > Excuse me? The damn thing had found nothing. However, it didn't care
> > to release the devices it had claimed - hadn't even closed them, as the
> > matter of fact. That's a clear and obvious bug, regardless of any
> > disagreements.
>
> As far as I can see from here, evms parsed partition table, called
> dmsetup several times and created corresponding nodes in /dev/evms.

... without saying anything?

> Logic is easy - evms trying to concentrate block device management
> into its own hands, but we have in-kernel partitioning code to
> consider ...

How nice of them.

Well, AFAICS that means
a) either kernel side of the things or the userland tools should
printk/syslog - at least that evms device had been set up
b) any distribution that runs this from initrd/init scripts would
better take care of having sane fstab.
c) nobody sane should put that as default. Oh, wait, it's gentoo
we are talking about? Nevermind, then.

2004-04-27 20:39:17

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Tue, 27 Apr 2004 [email protected] wrote:

> On Wed, Apr 28, 2004 at 12:04:59AM +0400, Paul P Komkoff Jr wrote:
> > > Excuse me? The damn thing had found nothing. However, it didn't care
> > > to release the devices it had claimed - hadn't even closed them, as the
> > > matter of fact. That's a clear and obvious bug, regardless of any
> > > disagreements.
> >
> > As far as I can see from here, evms parsed partition table, called
> > dmsetup several times and created corresponding nodes in /dev/evms.
>
> ... without saying anything?
>
> > Logic is easy - evms trying to concentrate block device management
> > into its own hands, but we have in-kernel partitioning code to
> > consider ...
>
> How nice of them.
>
> Well, AFAICS that means
> a) either kernel side of the things or the userland tools should
> printk/syslog - at least that evms device had been set up
> b) any distribution that runs this from initrd/init scripts would
> better take care of having sane fstab.
> c) nobody sane should put that as default. Oh, wait, it's gentoo
> we are talking about? Nevermind, then.

But what default? Gentoo just calls evms_activate before mounting
filesystems to check if there are evms volumes (because filesystems can
reside on it). And, according to man page, this is the right usage of
evms_activate. And Gentoo could not know easily that I have no evms
volumes in the system. And I possibly could insert some and boot Gentoo
(and for example have label not device in fstab to specify fs to mount). I
really think that evms_activate should not take the device that is not for
it. And I think Gentoo is right. (And it is the best distro I ever tried.)


Grzegorz Kulewski

2004-04-27 21:37:04

by Al Viro

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Tue, Apr 27, 2004 at 10:39:09PM +0200, Grzegorz Kulewski wrote:
> > c) nobody sane should put that as default. Oh, wait, it's gentoo
> > we are talking about? Nevermind, then.
>
> But what default? Gentoo just calls evms_activate before mounting
> filesystems to check if there are evms volumes (because filesystems can
> reside on it). And, according to man page, this is the right usage of
> evms_activate.

And that usage of evms_activate takes over all normally partitioned devices
and shoves equivalents of partitions under /dev/evms, right? So in which
universe would that be the right thing to do without a big fat warning and
update of /etc/fstab?

2004-04-27 21:59:38

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

On Tue, 27 Apr 2004 [email protected] wrote:
> On Tue, Apr 27, 2004 at 10:39:09PM +0200, Grzegorz Kulewski wrote:
> > > c) nobody sane should put that as default. Oh, wait, it's gentoo
> > > we are talking about? Nevermind, then.
> >
> > But what default? Gentoo just calls evms_activate before mounting
> > filesystems to check if there are evms volumes (because filesystems can
> > reside on it). And, according to man page, this is the right usage of
> > evms_activate.
>
> And that usage of evms_activate takes over all normally partitioned devices
> and shoves equivalents of partitions under /dev/evms, right? So in which
> universe would that be the right thing to do without a big fat warning and
> update of /etc/fstab?


>From evms_activate man page:

DESCRIPTION
The evms_activate command discovers all EVMS volumes and
activates kernel devices for all volumes
that are not yet active. The command should be run at boot time so
the file systems that reside on
the volumes can be mounted. If EVMS volumes are listed in the
/etc/fstab, evms_activate should be run
before /etc/fstab is processed (which is distribution specific). If
the root file system is on an
EVMS volume, evms_activate should be run from the init-ramdisk.


And where is the big fat warning that you can not use your normal devices
anymore?

And I still do not understand why my old device names that every script /
program on the Eartch uses cannot be used anymore... And if I really can
not use them why their device files in dev do not disappear? (I am using
udev.)

And can I use fdisk to modify and then reload partition table in this new
approach? And will mount that is searching for filesystem with specified
label find it on new device? And should not the kernel warn in case
someone is touching the old device?


Grzegorz Kulewski

2004-04-28 09:37:55

by William Lee Irwin III

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

On Mon, Apr 26, 2004 at 01:39:44AM -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc2/2.6.6-rc2-mm2/
> - Largeish reiserfs feature update. The biggest change is probably the new
> block allocation algorithm. See the changelog inside
> reiserfs-group-alloc-9.patch for details.
> - Added the ia64 CPU hotplug support patch
> - More work against the ext3 block allocator.
> - Several more framebuffer driver update, some quite substantial.
> - Lots of fixes, mostly minor.

arch/i386/kernel/built-in.o(.init.text+0x1efe): In function `ignore_timer_override':
arch/i386/kernel/entry.S:307: undefined reference to `acpi_skip_timer_override'
make[1]: *** [.tmp_vmlinux1] Error 1

ignore_timer_override() is only usable #if defined(CONFIG_ACPI_BOOT)
anyway, so:


-- wli


Index: local/wli-2.6.6-rc2-mm2/arch/i386/kernel/dmi_scan.c
===================================================================
--- local.orig/wli-2.6.6-rc2-mm2/arch/i386/kernel/dmi_scan.c 2004-04-28 01:22:29.000000000 -0700
+++ local/wli-2.6.6-rc2-mm2/arch/i386/kernel/dmi_scan.c 2004-04-28 02:31:59.000000000 -0700
@@ -565,6 +565,7 @@
* early nForce2 reference BIOS shipped with a
* bogus ACPI IRQ0 -> pin2 interrupt override -- ignore it
*/
+#ifdef CONFIG_ACPI_BOOT
static __init int ignore_timer_override(struct dmi_blacklist *d)
{
extern int acpi_skip_timer_override;
@@ -574,6 +575,7 @@
acpi_skip_timer_override = 1;
return 0;
}
+#endif
/*
* Process the DMI blacklists
*/

2004-04-28 10:20:00

by Paul Komkoff

[permalink] [raw]
Subject: Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?

Replying to [email protected]:
> ... without saying anything?

Actually, it puts corresponding messages into /var/log/evms-engine.log
>
> Well, AFAICS that means
> a) either kernel side of the things or the userland tools should
> printk/syslog - at least that evms device had been set up
> b) any distribution that runs this from initrd/init scripts would
> better take care of having sane fstab.
> c) nobody sane should put that as default. Oh, wait, it's gentoo
> we are talking about? Nevermind, then.

I think it is a really minor problem, comparing to others we sometimes
have. It has many solutions, for example, we can create
native device nodes in /dev/evms (or map on top of partitions).

There's a reason why this problem never arised before in such manner.
Traditional evms audience is server admins, and most of them configure
their boxes that disks other than with they /dev/root are
"evms-native" in some manner, and excluding their /dev/sda from evms
scan.

So for now, correct solution would be correct exclude device list, and
maybe distributions shipping evms will do this.

--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head

2004-04-29 18:41:33

by William Lee Irwin III

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

On Mon, Apr 26, 2004 at 01:39:44AM -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc2/2.6.6-rc2-mm2/
> - Largeish reiserfs feature update. The biggest change is probably the new
> block allocation algorithm. See the changelog inside
> reiserfs-group-alloc-9.patch for details.
> - Added the ia64 CPU hotplug support patch
> - More work against the ext3 block allocator.
> - Several more framebuffer driver update, some quite substantial.
> - Lots of fixes, mostly minor.

I missed -mm1; both this and -mm1 appear to be unable to detect Adaptec
39160 HBA's. I'm in the midst of bisecting this. Thus far I have the
last known-working as virgin 2.6.6-rc2, and first known broken is patch
#36 out of 308 i.e. it's probably in one of the external bk trees or
linus.patch, though linus.patch doesn't seem to have anything related.


-- wli

2004-04-29 21:08:00

by Andrew Morton

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

William Lee Irwin III <[email protected]> wrote:
>
> On Mon, Apr 26, 2004 at 01:39:44AM -0700, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc2/2.6.6-rc2-mm2/
> > - Largeish reiserfs feature update. The biggest change is probably the new
> > block allocation algorithm. See the changelog inside
> > reiserfs-group-alloc-9.patch for details.
> > - Added the ia64 CPU hotplug support patch
> > - More work against the ext3 block allocator.
> > - Several more framebuffer driver update, some quite substantial.
> > - Lots of fixes, mostly minor.
>
> I missed -mm1; both this and -mm1 appear to be unable to detect Adaptec
> 39160 HBA's. I'm in the midst of bisecting this. Thus far I have the
> last known-working as virgin 2.6.6-rc2, and first known broken is patch
> #36 out of 308 i.e. it's probably in one of the external bk trees or
> linus.patch, though linus.patch doesn't seem to have anything related.

bk-scsi.patch will be the one to try.

2004-04-29 21:24:03

by William Lee Irwin III

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

William Lee Irwin III <[email protected]> wrote:
>> I missed -mm1; both this and -mm1 appear to be unable to detect Adaptec
>> 39160 HBA's. I'm in the midst of bisecting this. Thus far I have the
>> last known-working as virgin 2.6.6-rc2, and first known broken is patch
>> #36 out of 308 i.e. it's probably in one of the external bk trees or
>> linus.patch, though linus.patch doesn't seem to have anything related.

On Thu, Apr 29, 2004 at 01:45:46PM -0700, Andrew Morton wrote:
> bk-scsi.patch will be the one to try.

Is there a split-up version of that anywhere I can do bisection search on?


-- wli

2004-04-30 00:25:00

by William Lee Irwin III

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

On Thu, Apr 29, 2004 at 01:45:46PM -0700, Andrew Morton wrote:
>> bk-scsi.patch will be the one to try.

On Thu, Apr 29, 2004 at 02:18:25PM -0700, William Lee Irwin III wrote:
> Is there a split-up version of that anywhere I can do bisection search on?

I finished bisecting. It was this:

$ head -80 patches/bk-scsi.patch | tail -5 | egrep -v '^#[ ]+$'
# ChangeSet
# 2004/04/25 09:10:30-05:00 [email protected]
# [PATCH] aic7xxx: fix oops whe hardware is not present
# From: Herbert Xu <[email protected]>


-- wli

2004-04-30 02:05:38

by James Bottomley

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

On Thu, 2004-04-29 at 19:24, William Lee Irwin III wrote:
> # ChangeSet
> # 2004/04/25 09:10:30-05:00 [email protected]
> # [PATCH] aic7xxx: fix oops whe hardware is not present
> # From: Herbert Xu <[email protected]>

OK, well, on inspection that patch is fairly comprehensively incorrect.

Can you try out the attached? I've compiled it but have nothing to test
installation with.

Thanks,

James

===== aic7770_osm.c 1.5 vs edited =====
--- 1.5/drivers/scsi/aic7xxx/aic7770_osm.c Tue Apr 6 23:09:31 2004
+++ edited/aic7770_osm.c Thu Apr 29 20:07:39 2004
@@ -159,10 +159,10 @@
void
ahc_linux_eisa_exit(void)
{
-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,5,0)
- eisa_driver_unregister(&aic7770_driver);
- free(aic7770_driver.id_table, M_DEVBUF);
-#endif
+ if(aic7xxx_probe_eisa_vl != 0 && aic7770_driver.id_table != NULL) {
+ eisa_driver_unregister(&aic7770_driver);
+ free(aic7770_driver.id_table, M_DEVBUF);
+ }
}

static int
===== aic7xxx_osm.c 1.51 vs edited =====
--- 1.51/drivers/scsi/aic7xxx/aic7xxx_osm.c Sun Apr 25 09:11:53 2004
+++ edited/aic7xxx_osm.c Thu Apr 29 20:32:32 2004
@@ -843,7 +843,8 @@
ahc_linux_detect(Scsi_Host_Template *template)
{
struct ahc_softc *ahc;
- int found;
+ int found = 0;
+ int eisa_err, pci_err;

#if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0)
/*
@@ -891,21 +892,12 @@
*/
ahc_list_lockinit();

-#ifdef CONFIG_PCI
- found = ahc_linux_pci_init();
- if (found)
- goto out;
-#endif
+ pci_err = ahc_linux_pci_init();
+ eisa_err = ahc_linux_eisa_init();

-#ifdef CONFIG_EISA
- found = ahc_linux_eisa_init();
- if (found) {
-#ifdef CONFIG_PCI
- ahc_linux_pci_exit();
-#endif
+ if(pci_err && eisa_err)
goto out;
- }
-#endif
+

/*
* Register with the SCSI layer all
@@ -916,12 +908,13 @@
if (ahc_linux_register_host(ahc, template) == 0)
found++;
}
+out:
+
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0)
spin_lock_irq(&io_request_lock);
#endif
aic7xxx_detect_complete++;

-out:
return (found);
}

@@ -5078,7 +5071,7 @@
}
}

-static void __exit ahc_linux_exit(void);
+static void ahc_linux_exit(void);

static int __init
ahc_linux_init(void)
@@ -5101,7 +5094,7 @@
#endif
}

-static void __exit
+static void
ahc_linux_exit(void)
{
struct ahc_softc *ahc;
@@ -5128,12 +5121,8 @@
*/
scsi_unregister_module(MODULE_SCSI_HA, &aic7xxx_driver_template);
#endif
-#ifdef CONFIG_PCI
ahc_linux_pci_exit();
-#endif
-#ifdef CONFIG_EISA
ahc_linux_eisa_exit();
-#endif
}

module_init(ahc_linux_init);
===== aic7xxx_osm.h 1.52 vs edited =====
--- 1.52/drivers/scsi/aic7xxx/aic7xxx_osm.h Tue Apr 6 23:09:31 2004
+++ edited/aic7xxx_osm.h Thu Apr 29 20:39:50 2004
@@ -845,6 +845,12 @@
int aic7770_map_registers(struct ahc_softc *ahc,
u_int port);
int aic7770_map_int(struct ahc_softc *ahc, u_int irq);
+#else
+static inline int ahc_linux_eisa_init(void) {
+ return -ENODEV;
+}
+static inline void ahc_linux_eisa_exit(void) {
+}
#endif

/******************************* PCI Routines *********************************/
@@ -931,6 +937,12 @@
ahc_get_pci_bus(ahc_dev_softc_t pci)
{
return (pci->bus->number);
+}
+#else
+static inline int ahc_linux_pci_init(void) {
+ return -ENODEV;
+}
+static inline void ahc_linux_pci_exit(void) {
}
#endif


2004-04-30 02:25:07

by William Lee Irwin III

[permalink] [raw]
Subject: Re: 2.6.6-rc2-mm2

On Thu, 2004-04-29 at 19:24, William Lee Irwin III wrote:
>> # ChangeSet
>> # 2004/04/25 09:10:30-05:00 [email protected]
>> # [PATCH] aic7xxx: fix oops whe hardware is not present
>> # From: Herbert Xu <[email protected]>

On Thu, Apr 29, 2004 at 09:05:06PM -0500, James Bottomley wrote:
> OK, well, on inspection that patch is fairly comprehensively incorrect.
> Can you try out the attached? I've compiled it but have nothing to test
> installation with.

I'll give it a whirl. I've got a slow turnaround time (>= 1hr) for the
moment, so please be patient.


-- wli

2004-06-19 17:17:19

by Grzegorz Kulewski

[permalink] [raw]
Subject: Memory and rsync problem with vanilla 2.6.7

Hi,

I have very strange problem. I am using Gentoo Linux and I use rsync to
refresh its ebuilds list about once a day. Since 2.6.7 the system started
to be very slow during this operation and Gentoo rsync servers started to
drop connstions to me because of timeout. So I looked at top and found
that I am very short on memmory and that mainly kswapd runs on my system.
I have 512 MB of memmory and about 768 MB of swap. I was running
only GNOME, two gnome terminals and rsync but all my RAM was used and 86
MB of swap too. This never happened before. I looked further and found
that buffers were about 4 MB and cache was only 2 MB. But the most memmory
consuming process (rsync) had only about 15 MB. But because it was under X
(with nvidia module) and the kernel was 2.6.7-ck1 I double checked with
untainted vanilla 2.6.7 without X. And it was more or less the same (but
less swap was used probably because there were no X and GNOME - only
about 400 KB).

Is this bug or feature? Is there some wreid memmory leak? Where is my RAM?

My config and output from meminfo and slabinfo after rsync stopped (from
vanilla 2.6.7) attached.


Thanks,

Grzegorz Kulewski


Attachments:
config-2.6.7 (29.76 kB)
bad5 (27.20 kB)
Download all attachments

2004-06-19 17:50:32

by Linus Torvalds

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7



On Sat, 19 Jun 2004, Grzegorz Kulewski wrote:
>
> Is this bug or feature? Is there some wreid memmory leak? Where is my RAM?

Your memory is apparently in dentry and inode memory:

ext3_inode_cache 62553 62553 4096 (244MB)
dentry_cache 48768 48768 4096 (190MB)

and it really looks like you have enabled CONFIG_DEBUG_PAGEALLOC, which
just eats memory like mad (a dentry is normally ~200 bytes, but then when
it is rounded up to page-size, it takes 20 times the memory).

So don't enable DEBUG_PAGEALLOC unless you really want to debug some
strange problem.

That said, there might be a memory balancing problem too, and
DEBUG_PAGEALLOC just makes it more obvious. Nick Piggin reports that an
"obvious fix" by Andrew potentially causes problems, and if you're a BK
user, you could try just backing out this cset:

[email protected], 2004-06-03 07:58:03-07:00, [email protected]
[PATCH] shrink_all_memory() fixes

....

(check with "bk changes" what the revision is in your tree, and do a

bk cset -xX.XXX.XX.X

to try reverting it. Quite possibly that fix makes the VM much less likely
to throw out the VM caches, which would make the debug problem much
worse).

Linus

2004-06-20 03:48:05

by Nick Piggin

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

Linus Torvalds wrote:
>
> On Sat, 19 Jun 2004, Grzegorz Kulewski wrote:
>
>>Is this bug or feature? Is there some wreid memmory leak? Where is my RAM?
>
>
> Your memory is apparently in dentry and inode memory:
>
> ext3_inode_cache 62553 62553 4096 (244MB)
> dentry_cache 48768 48768 4096 (190MB)
>
> and it really looks like you have enabled CONFIG_DEBUG_PAGEALLOC, which
> just eats memory like mad (a dentry is normally ~200 bytes, but then when
> it is rounded up to page-size, it takes 20 times the memory).
>
> So don't enable DEBUG_PAGEALLOC unless you really want to debug some
> strange problem.
>

This could be it. But can you check whether your previous well-behaving
kernel also has CONFIG_DEBUG_PAGEALLOC on? If so, then it is possible
that VM behaviour has regressed.

Of course, DEBUG_PAGEALLOC is the wrong target to attempt to tune for:
without it, those above two items would take up a combined 40 megs.

> That said, there might be a memory balancing problem too, and
> DEBUG_PAGEALLOC just makes it more obvious. Nick Piggin reports that an
> "obvious fix" by Andrew potentially causes problems, and if you're a BK
> user, you could try just backing out this cset:
>
> [email protected], 2004-06-03 07:58:03-07:00, [email protected]
> [PATCH] shrink_all_memory() fixes
>
> ....
>
> (check with "bk changes" what the revision is in your tree, and do a
>
> bk cset -xX.XXX.XX.X
>
> to try reverting it. Quite possibly that fix makes the VM much less likely
> to throw out the VM caches, which would make the debug problem much
> worse).
>

Well it doesn't seem to have caused too much trouble as yet... But it
is the obvious candidate if your problems continue. If you are not a
bk user, the attached patch will also revert that change.


Attachments:
vm-revert-fix.patch (998.00 B)

2004-06-20 13:25:09

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

On Sat, 19 Jun 2004, Linus Torvalds wrote:

> On Sat, 19 Jun 2004, Grzegorz Kulewski wrote:
> >
> > Is this bug or feature? Is there some wreid memmory leak? Where is my RAM?
>
> Your memory is apparently in dentry and inode memory:
>
> ext3_inode_cache 62553 62553 4096 (244MB)
> dentry_cache 48768 48768 4096 (190MB)
>
> and it really looks like you have enabled CONFIG_DEBUG_PAGEALLOC, which
> just eats memory like mad (a dentry is normally ~200 bytes, but then when
> it is rounded up to page-size, it takes 20 times the memory).
>
> So don't enable DEBUG_PAGEALLOC unless you really want to debug some
> strange problem.
>
> That said, there might be a memory balancing problem too, and
> DEBUG_PAGEALLOC just makes it more obvious. Nick Piggin reports that an
> "obvious fix" by Andrew potentially causes problems, and if you're a BK
> user, you could try just backing out this cset:
>
> [email protected], 2004-06-03 07:58:03-07:00, [email protected]
> [PATCH] shrink_all_memory() fixes
>
> ....
>
> (check with "bk changes" what the revision is in your tree, and do a
>
> bk cset -xX.XXX.XX.X
>
> to try reverting it. Quite possibly that fix makes the VM much less likely
> to throw out the VM caches, which would make the debug problem much
> worse).

Yes, you are right. But something was changed (probably) between 2.6.6 and
2.7 because I always test new kernels with every debug enabled, just in
case :). It was slower but never caused such problems.

No, I am currently not bk user (but I will probably learn it during
holidays). Is there any easy way to produce patch from that changeset?
I want to test it to check if it really is the cause of the problem.


Thanks,

Grzegorz Kulewski

2004-06-20 13:53:04

by Sam Ravnborg

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

On Sun, Jun 20, 2004 at 03:24:56PM +0200, Grzegorz Kulewski wrote:
>
> No, I am currently not bk user (but I will probably learn it during
> holidays). Is there any easy way to produce patch from that changeset?

Goto: http://linus.bkbits.net:8080/linux-2.5/[email protected]

Here there is a link to:
http://linus.bkbits.net:8080/linux-2.5/gnupatch@40bf3c7byPSs7WNObejgoMcVAD9p5g

Note: The first link may change since ChangeSet numbers are not fixed.
The latter is always valid.

Sam

2004-06-20 14:18:23

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

On Sun, 20 Jun 2004, Nick Piggin wrote:

> Linus Torvalds wrote:
> >
> > On Sat, 19 Jun 2004, Grzegorz Kulewski wrote:
> >
> >>Is this bug or feature? Is there some wreid memmory leak? Where is my RAM?
> >
> >
> > Your memory is apparently in dentry and inode memory:
> >
> > ext3_inode_cache 62553 62553 4096 (244MB)
> > dentry_cache 48768 48768 4096 (190MB)
> >
> > and it really looks like you have enabled CONFIG_DEBUG_PAGEALLOC, which
> > just eats memory like mad (a dentry is normally ~200 bytes, but then when
> > it is rounded up to page-size, it takes 20 times the memory).
> >
> > So don't enable DEBUG_PAGEALLOC unless you really want to debug some
> > strange problem.
> >
>
> This could be it. But can you check whether your previous well-behaving
> kernel also has CONFIG_DEBUG_PAGEALLOC on? If so, then it is possible
> that VM behaviour has regressed.

I always test new kernels with all debug enabled just in case. If
everything is ok I recompile them without debuging. And sometimes I use
rsync before I recompile and I never experienced such problems so I think
something was changed.


> Of course, DEBUG_PAGEALLOC is the wrong target to attempt to tune for:
> without it, those above two items would take up a combined 40 megs.

Yes, of course. Maybe there should be bigger warning in make config about
this option? Btw. many debug options have very short help (if any) not
saying how bad they interract with speed and memory. Maybe there should be
some submenu with "mad" debug options only for insane people :)?


> > That said, there might be a memory balancing problem too, and
> > DEBUG_PAGEALLOC just makes it more obvious. Nick Piggin reports that an
> > "obvious fix" by Andrew potentially causes problems, and if you're a BK
> > user, you could try just backing out this cset:
> >
> > [email protected], 2004-06-03 07:58:03-07:00, [email protected]
> > [PATCH] shrink_all_memory() fixes
> >
> > ....
> >
> > (check with "bk changes" what the revision is in your tree, and do a
> >
> > bk cset -xX.XXX.XX.X
> >
> > to try reverting it. Quite possibly that fix makes the VM much less likely
> > to throw out the VM caches, which would make the debug problem much
> > worse).
>
> Well it doesn't seem to have caused too much trouble as yet... But it
> is the obvious candidate if your problems continue. If you are not a
> bk user, the attached patch will also revert that change.

Thanks, I will test it soon and I will report results. But I am not saying
it is a bug - maybe it is simply change that can lead to problems with
insane debug options but itself is good?


Thanks,

Grzegorz Kulewski

2004-06-20 14:41:15

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

> > Well it doesn't seem to have caused too much trouble as yet... But it
> > is the obvious candidate if your problems continue. If you are not a
> > bk user, the attached patch will also revert that change.
>
> Thanks, I will test it soon and I will report results. But I am not saying
> it is a bug - maybe it is simply change that can lead to problems with
> insane debug options but itself is good?

Are you sure that this is good patch against vanilla 2.6.7? It gives me
2 failed hunks (both normal and -R)... Should I merge it manually?


Thanks,

Grzegorz Kulewski

2004-06-20 14:47:15

by Nick Piggin

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

Grzegorz Kulewski wrote:
>>>Well it doesn't seem to have caused too much trouble as yet... But it
>>>is the obvious candidate if your problems continue. If you are not a
>>>bk user, the attached patch will also revert that change.
>>
>>Thanks, I will test it soon and I will report results. But I am not saying
>>it is a bug - maybe it is simply change that can lead to problems with
>>insane debug options but itself is good?
>
>
> Are you sure that this is good patch against vanilla 2.6.7? It gives me
> 2 failed hunks (both normal and -R)... Should I merge it manually?
>

You're right here's the correct one.


Attachments:
vm-revert-fix.patch (983.00 B)

2004-06-20 20:34:10

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

On Mon, 21 Jun 2004, Nick Piggin wrote:

> Grzegorz Kulewski wrote:
> >>>Well it doesn't seem to have caused too much trouble as yet... But it
> >>>is the obvious candidate if your problems continue. If you are not a
> >>>bk user, the attached patch will also revert that change.
> >>
> >>Thanks, I will test it soon and I will report results. But I am not saying
> >>it is a bug - maybe it is simply change that can lead to problems with
> >>insane debug options but itself is good?
> >
> >
> > Are you sure that this is good patch against vanilla 2.6.7? It gives me
> > 2 failed hunks (both normal and -R)... Should I merge it manually?
>
> You're right here's the correct one.

No, it is not. GCC complains about priority undeclared. It should be
probably sc->priority (I changed it this way). Looks like you do not know
how to code in C ;-).


Thanks,

Grzegorz Kulewski

2004-06-21 16:22:11

by Grzegorz Kulewski

[permalink] [raw]
Subject: Re: Memory and rsync problem with vanilla 2.6.7

On Mon, 21 Jun 2004, Nick Piggin wrote:

> Grzegorz Kulewski wrote:
> >>>Well it doesn't seem to have caused too much trouble as yet... But it
> >>>is the obvious candidate if your problems continue. If you are not a
> >>>bk user, the attached patch will also revert that change.
> >>
> >>Thanks, I will test it soon and I will report results. But I am not saying
> >>it is a bug - maybe it is simply change that can lead to problems with
> >>insane debug options but itself is good?

It maybe helps but very little. I can sync now one time. The second time I
always get timeouts. Without this patch I nearly never can do this one
time.

Why the kernel keeps inodes and dentries even if it completly runs out of
memory?


Thanks,

Grzegorz Kulewski

2004-06-21 18:37:20

by Grzegorz Kulewski

[permalink] [raw]
Subject: network related(?) kernel panic (2.6.7-bk4)

Hi,

I am testing 2.6.7-bk4 + timer fix + vesafb-tng patch. This time without
debuging compiled in. Everything worked perfectly before I got:

bad: scheduling while atomic!
schedule+0x466/0x470
do_page_fault+0x104/0x4c1
ip_route_output_flow+0x22/0x70
sys_sched_yield+0x3f/0x50
coredump_wait+0x31/0xa0
do_coredump+0xf1/0x1af
sockfd_lookup+0x16/0x80
do_page_fault+0x0/0x4c1
error_code+0x2d/0x38
__dequeue_signal+0xc6/0x160
dequeue_signal+0x23/0x80
get_signal_to_deriver+0x246/0x330
do_signal+0x85/0x100
__sock_create+0x191/0x260
sys_send+0x37/0x40
sys_socketcall+0x12f/0x250
copy_to_user+0x32/0x50
do_page_fault+0x0/0x4c1
do_notify_resume+0x35/0x38
work_notifysig+0x13/0x15
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

(sorry for any mistakes - I copied it by hand).

The kernel was not tainted. I can reproduce the same every time I want to
connect to the network. I use speedtouch kernel driver. I have script that
first executes modem_run then pppd then wget to change DNS entries to new
IP adress. This happens after pppd setups connection and gets IP. I think
that this happens in wget. This works with 2.6.7, so some recent bk change
is probably the cause.

Can you help me?


Thanks,

Grzegorz Kulewski