ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
- autofs4 mounting remains busted.
- CONFIG_BLOCK=n doesn't (quite) work. Will fix later.
- CONFIG_MSI=y is probably broken - try disabling it before reporting
interrupt-related oopses. Then please report it whether or not that fixed
it.
- Could I point out the fifth bullet-point in the "Boilerplate" section,
below?
- git-cryptodev.patch is dropped due to my continuing inability to pull a
clean git diff (there is hope, but more work is needed)
- Ditto git-sas.patch
- And git-audit-master.patch (I think).
Things will improve around the 2.6.19-rc1 timeframe.
- 1,915 patches breaks the previous record by ~200.
- This kernel includes the patch to sort the PCI devices breadth-first.
This might cause strange things to happen (particular devices get assigned
to different /dev nodes, for example). If this is suspected, please try
reverting gregkh-pci-pci-sort-device-lists-breadth-first.patch then send a
report.
Boilerplate:
- See the `hot-fixes' directory for any important updates to this patchset.
- To fetch an -mm tree using git, use (for example)
git fetch git://git.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git v2.6.16-rc2-mm1
- -mm kernel commit activity can be reviewed by subscribing to the
mm-commits mailing list.
echo "subscribe mm-commits" | mail [email protected]
- If you hit a bug in -mm and it is not obvious which patch caused it, it is
most valuable if you can perform a bisection search to identify which patch
introduced the bug. Instructions for this process are at
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
But beware that this process takes some time (around ten rebuilds and
reboots), so consider reporting the bug first and if we cannot immediately
identify the faulty patch, then perform the bisection search.
- When reporting bugs, please try to Cc: the relevant maintainer and mailing
list on any email.
- When reporting bugs in this kernel via email, please also rewrite the
email Subject: in some manner to reflect the nature of the bug. Some
developers filter by Subject: when looking for messages to read.
- Semi-daily snapshots of the -mm lineup are uploaded to
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/ and are announced on
the mm-commits list.
Changes since 2.6.18-rc6-mm1:
origin.patch
git-acpi.patch
git-alsa.patch
git-agpgart.patch
git-block.patch
git-cifs.patch
git-cpufreq.patch
git-drm.patch
git-dvb.patch
git-geode.patch
git-gfs2.patch
git-ia64.patch
git-ieee1394.patch
git-infiniband.patch
git-input.patch
git-intelfb.patch
git-kbuild.patch
git-libata-all.patch
git-lxdialog.patch
git-mtd.patch
git-netdev-all.patch
git-net.patch
git-nfs.patch
git-ocfs2.patch
git-parisc.patch
git-pcmcia.patch
git-powerpc.patch
git-r8169.patch
git-s390.patch
git-scsi-misc.patch
git-scsi-rc-fixes.patch
git-scsi-target.patch
git-watchdog.patch
git-xfs.patch
git trees
-use-the-correct-restart-option-for-futex_lock_pi.patch
-optical-proc-ide-media.patch
-sh-fix-fpn_start-typo.patch
-sis5513-add-sis-south-bridge-id-0x966.patch
-ext3_getblk-should-handle-hole-correctly.patch
-invalidate_complete_page-race-fix.patch
-nfs-large-non-page-aligned-direct-i-o-clobbers-memory.patch
-input-i8042-get-rid-of-polling-timer.patch
-asus-mv-device-ids.patch
-gregkh-usb-usb-hid-core.c-fix-duplicate-usb_device_id_gtco_404.patch
-gregkh-usb-usb-support-for-usb20svga-wh-usb20svga-dg.patch
-gregkh-usb-usb-new-device-id-for-ftdi_sio-usb-serial-driver.patch
-gregkh-usb-usb-usbtouchscreen-fix-itm-data-reading.patch
-gregkh-usb-usb-must_check-fixes.patch
-x86_64-mm-module-locks-raw-spinlock.patch
Merged into mainline or a subsystem tree.
+libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
+lockdep-double-the-number-of-stack-trace-entries.patch
+we-can-not-allow-anonymous-contributions-to-the-kernel.patch
+alim15x3c-m5229-rev-c8-support-for-dma-cd-writer.patch
+scsi-lockdep-annotation-in-scsi_send_eh_cmnd.patch
+rcu_do_batch-make-qlen-decrement-irq-safe.patch
+x86-reserve-a-boot-loader-id-number-for-xen.patch
+headers_check-improve-include-regexp.patch
+headers_check-clarify-error-message.patch
+headers_check-reduce-user-visible-noise-in-linux-nfs_fsh.patch
+headers_check-remove-asm-timexh-from-user-export.patch
+headers_check-move-inclusion-of-linux-linkageh-in.patch
+headers_check-move-kernel-only-includes-within-asm-i386-elfh.patch
+headers_check-dont-expose-pfn-stuff-to-userspace-in.patch
+headers_check-fix-userspace-build-of-asm-mips-pageh.patch
+cciss-version-update-new-hw.patch
2.6.18 queue (already sent to Linus)
+usbserial-reference-leak.patch
USB fix (probably for 2.6.18)
+jbd-fix-commit-of-ordered-data-buffers.patch
JBD fix (for 2.6.19 and 2.6.18.x)
+fix-incorrect-handling-of-pci-express-root-bridge-_hid.patch
PCI fix
+maintainers-updates-to-ieee-1394-subsystem.patch
1394 maintainers update
+revert-libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
Make git-libata-all.patch apply.
+redo-libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
Reapply this fix after git-libata-all.patch.
+git-libata-all-ata_piix-build-fix.patch
Fix git-libata-all.patch.
+rtnetlink-fix-netdevice-name-corruption.patch
Fix the net-device-names-go-bad bug.
+gregkh-pci-pci-sort-device-lists-breadth-first.patch
PCI tree update.
+gregkh-usb-usb-ub-let-cdrecord-to-see-a-device-with-media-absent.patch
+gregkh-usb-usb-core-must_check.patch
+gregkh-usb-usb-misc-must_check.patch
+gregkh-usb-usb-atm-must_check.patch
+gregkh-usb-usb-class-must_check.patch
+gregkh-usb-usb-input-must_check.patch
+gregkh-usb-usb-host-must_check.patch
+gregkh-usb-usb-serial-must_check-fixes.patch
USB tree updates.
+watchdog-use-enotty-instead-of-enoioctlcmd-in-ioctl.patch
Watchdog driver fixes.
+hostap_cs-added-support-for-proxim-harmony-pci-w-lan.patch
Wireless device support.
+x86_64-mm-lockdep-stacktrace-no-recursion.patch
+x86_64-mm-compat-pselect-must-check.patch
+x86_64-mm-compat-uname-must-check.patch
+x86_64-mm-pda-noreturn.patch
+x86_64-mm-fix-idle-notifiers.patch
+x86_64-mm-pci-probe-type1-first.patch
+x86_64-mm-i386-acpi-mcfg-check.patch
+x86_64-mm-acpi-mcfg-check.patch
+x86_64-mm-remove-mcfg-dmi.patch
+x86_64-mm-insert-gart-region-into-resource-map.patch
+x86_64-mm-mcfg-resource.patch
+x86_64-mm-i386-mcfg-resource.patch
+x86_64-mm-i386-pack-descriptor.patch
+x86_64-mm-i386-multiline-oops.patch
x86_64 tree updates.
+xfs-rename-uio_read.patch
Rename a function in XFS to avoid a clash.
+numa-add-zone_to_nid-function-update.patch
Improve numa-add-zone_to_nid-function.patch
+vm-add-per-zone-writeout-counter.patch
Add new counter to /proc/vmstat: counts number of pages written out via the
vm scanner.
+own-header-file-for-struct-page.patch
+convert-s390-page-handling-macros-to-functions.patch
+convert-s390-page-handling-macros-to-functions-fix.patch
MM header file cleanups.
+frv-improve-frvs-use-of-generic-irq-handling.patch
+frv-permit-__do_irq-to-be-dispensed-with.patch
FRV update.
+avr32-rename-at32stk100x-atstk100x.patch
AVR32 update
+nommu-move-the-fallback-arch_vma_name-to-a-sensible-place-fix.patch
Fix nommu-move-the-fallback-arch_vma_name-to-a-sensible-place.patch
+uml-tty-locking.patch
TTY locking fix
-lockdep-core-add-enable-disable_irq_irqsave-irqrestore-apis-frv-fix.patch
Folded into
lockdep-core-add-enable-disable_irq_irqsave-irqrestore-apis.patch (I think)
+linux-kernel-dump-test-module-fixes.patch
Fix linux-kernel-dump-test-module.patch
+ext3-more-whitespace-cleanups.patch
+ext3-fix-sparse-warnings.patch
+submittingpatches-add-a-note-about-format=flowed-when-sending-patches.patch
+kmemdup-introduce.patch
+kmemdup-some-users.patch
+linux-magich-for-magic-numbers.patch
+linux-magich-for-magic-numbers-sparc-fix.patch
+cpuset-fix-obscure-attach_task-vs-exiting-race.patch
+create-fs-utimesc.patch
+cciss-support-for-2tb-logical-volumes.patch
Misc updates.
+add-genetlink-utilities-for-payload-length-calculation.patch
+fix-taskstats-size-calculation-use-the-new-genetlink-utility-functions.patch
+fix-getdelaysc-cpumask-length-and-error-reporting.patch
taskstats fixes for the Comprehensive System Accounting patches in -mm.
-vt-update-spawnpid-to-be-a-struct-pid_t.patch
-vt-update-spawnpid-to-be-a-struct-pid_t-tidy.patch
+vt-rework-the-console-spawning-variables.patch
+vt-make-vt_pid-a-struct-pid-making-it-pid-wrap-around-safe.patch
Updated.
+update-mq_notify-to-use-a-struct-pid.patch
+file-add-locking-to-f_getown.patch
+usb-fixup-usb-so-it-uses-struct-pid.patch
More pid management updates.
+proc-convert-task_sig-to-use-lock_task_sighand.patch
+proc-convert-do_task_stat-to-use-lock_task_sighand.patch
+proc-drop-tasklist-lock-in-task_state.patch
+proc-properly-compute-tgid_offset.patch
+proc-remove-trailing-blank-entry-from-pid_entry-arrays.patch
+proc-remove-the-useless-smp-safe-comments-from-proc.patch
+proc-comment-what-proc_fill_cache-does.patch
+introduce-get_task_pid-to-fix-unsafe-get_pid.patch
More /porc core updates.
+allow-ide_generic_all-to-be-used-modular-and-built-in.patch
IDE fix.
+savagefb-use-generic-ddc-reading-fix.patch
Fix savagefb-use-generic-ddc-reading.patch
+rcu-simplify-improve-batch-tuning.patch
RCU tuneup.
+pr_debug-aio-use-size_t-length-modifier-in-pr_debug-format-arguments.patch
+pr_debug-configfs-use-size_t-length-modifier-in-pr_debug-format-argument.patch
+pr_debug-sysfs-use-size_t-length-modifier-in-pr_debug-format-arguments.patch
+pr_debug-umem-repair-nonexistant-bh-pr_debug-reference.patch
+pr_debug-tipar-repair-nonexistant-pr_debug-argument-use.patch
+pr_debug-dell_rbu-fix-pr_debug-argument-warnings.patch
+pr_debug-ifb-replace-missing-comma-to-separate-pr_debug-arguments.patch
+pr_debug-trident-use-size_t-length-modifier-in-pr_debug-format-arguments.patch
+pr_debug-check-pr_debug-arguments.patch
+isdn-debug-build-fix.patch
+isdn-more-pr_debug-fixes.patch
Make pr_debug() check its arguments even if !defined(DEBUG). Plus fixes
arising from this.
All 1915 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/patch-list
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
> - autofs4 mounting remains busted.
>
> - CONFIG_BLOCK=n doesn't (quite) work. Will fix later.
>
> - CONFIG_MSI=y is probably broken - try disabling it before reporting
> interrupt-related oopses. Then please report it whether or not that fixed
> it.
>
> - Could I point out the fifth bullet-point in the "Boilerplate" section,
> below?
>
> - git-cryptodev.patch is dropped due to my continuing inability to pull a
> clean git diff (there is hope, but more work is needed)
>
> - Ditto git-sas.patch
>
> - And git-audit-master.patch (I think).
>
> Things will improve around the 2.6.19-rc1 timeframe.
>
> - 1,915 patches breaks the previous record by ~200.
>
> - This kernel includes the patch to sort the PCI devices breadth-first.
> This might cause strange things to happen (particular devices get assigned
> to different /dev nodes, for example). If this is suspected, please try
> reverting gregkh-pci-pci-sort-device-lists-breadth-first.patch then send a
> report.
>
>
>
> Boilerplate:
>
> - See the `hot-fixes' directory for any important updates to this patchset.
>
> - To fetch an -mm tree using git, use (for example)
>
> git fetch git://git.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git v2.6.16-rc2-mm1
>
> - -mm kernel commit activity can be reviewed by subscribing to the
> mm-commits mailing list.
>
> echo "subscribe mm-commits" | mail [email protected]
>
> - If you hit a bug in -mm and it is not obvious which patch caused it, it is
> most valuable if you can perform a bisection search to identify which patch
> introduced the bug. Instructions for this process are at
>
> http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
>
> But beware that this process takes some time (around ten rebuilds and
> reboots), so consider reporting the bug first and if we cannot immediately
> identify the faulty patch, then perform the bisection search.
>
> - When reporting bugs, please try to Cc: the relevant maintainer and mailing
> list on any email.
>
> - When reporting bugs in this kernel via email, please also rewrite the
> email Subject: in some manner to reflect the nature of the bug. Some
> developers filter by Subject: when looking for messages to read.
>
> - Semi-daily snapshots of the -mm lineup are uploaded to
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/ and are announced on
> the mm-commits list.
>
>
>
>
> Changes since 2.6.18-rc6-mm1:
>
>
> origin.patch
> git-acpi.patch
> git-alsa.patch
> git-agpgart.patch
> git-block.patch
> git-cifs.patch
> git-cpufreq.patch
> git-drm.patch
> git-dvb.patch
> git-geode.patch
> git-gfs2.patch
> git-ia64.patch
> git-ieee1394.patch
> git-infiniband.patch
> git-input.patch
> git-intelfb.patch
> git-kbuild.patch
> git-libata-all.patch
> git-lxdialog.patch
> git-mtd.patch
> git-netdev-all.patch
> git-net.patch
> git-nfs.patch
> git-ocfs2.patch
> git-parisc.patch
> git-pcmcia.patch
> git-powerpc.patch
> git-r8169.patch
> git-s390.patch
> git-scsi-misc.patch
Seems that the module unload bug in scsi.c (details below) is still
there... I'll follow up with the work around patch I am using.
-apw
Seems that -mm fails to compile when CONFIG_MODULES is set but
CONFIG_MODULE_UNLOAD is not.
LD .tmp_vmlinux1
drivers/built-in.o(.text+0x47724): In function `scsi_device_put':
drivers/scsi/scsi.c:887: undefined reference to `module_refcount'
Config fragment:
CONFIG_MODULES=y
# CONFIG_MODULE_UNLOAD is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
This seems to be caused by changes in the scsi-misc git tree, from the
changes in the two commits below:
[SCSI] sd: fix cache flushing on module removal
(and individual device removal)
[SCSI] fix up non-modular SCSI
85b6c720b0931101c8bcc3a5abdc2b8514b0fb4b
f479ab87936563a286b8aa0e39003c40fa31c6da
It looks very much like module_refcount is really not meant to be an
external interface, cirtainly its not available in all module
'load/unload modes'.
Hi,
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
This patch removes delated files from headers_install target.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
Signed-off-by: Michal Piotrowski <[email protected]>
diff -uprN -X linux-mm/Documentation/dontdiff linux-mm-clean/include/linux/Kbuild linux-mm/include/linux/Kbuild
--- linux-mm-clean/include/linux/Kbuild 2006-09-12 11:19:46.000000000 +0200
+++ linux-mm/include/linux/Kbuild 2006-09-12 11:16:14.000000000 +0200
@@ -2,7 +2,7 @@ header-y := byteorder/ dvb/ hdlc/ isdn/
netfilter/ netfilter_arp/ netfilter_bridge/ netfilter_ipv4/ \
netfilter_ipv6/
-header-y += affs_fs.h affs_hardblocks.h aio_abi.h a.out.h arcfb.h \
+header-y += affs_hardblocks.h aio_abi.h a.out.h arcfb.h \
atmapi.h atmbr2684.h atmclip.h atm_eni.h atm_he.h \
atm_idt77105.h atmioc.h atmlec.h atmmpc.h atm_nicstar.h \
atmppp.h atmsap.h atmsvc.h atm_zatm.h auto_fs4.h auxvec.h \
@@ -12,7 +12,7 @@ header-y += affs_fs.h affs_hardblocks.h
dqblk_v2.h dqblk_xfs.h efs_fs_sb.h elf-fdpic.h elf.h elf-em.h \
fadvise.h fd.h fdreg.h ftape-header-segment.h ftape-vendors.h \
fuse.h futex.h genetlink.h gen_stats.h gigaset_dev.h hdsmart.h \
- hpfs_fs.h hysdn_if.h i2c-dev.h i8k.h icmp.h \
+ hysdn_if.h i2c-dev.h i8k.h icmp.h \
if_arcnet.h if_arp.h if_bonding.h if_cablemodem.h if_fc.h \
if_fddi.h if.h if_hippi.h if_infiniband.h if_packet.h \
if_plip.h if_ppp.h if_slip.h if_strip.h if_tunnel.h in6.h \
@@ -21,7 +21,7 @@ header-y += affs_fs.h affs_hardblocks.h
jffs2.h keyctl.h limits.h lock_dlm_plock.h major.h matroxfb.h \
meye.h minix_fs.h mmtimer.h mqueue.h mtio.h ncp_no.h \
netfilter_arp.h netrom.h nfs2.h nfs4_mount.h nfs_mount.h \
- openprom_fs.h param.h pci_ids.h pci_regs.h personality.h \
+ param.h pci_ids.h pci_regs.h personality.h \
pfkeyv2.h pg.h pkt_cls.h pkt_sched.h posix_types.h ppdev.h \
prctl.h ps2esdi.h qic117.h qnxtypes.h quotaio_v1.h quotaio_v2.h \
radeonfb.h raw.h resource.h rose.h sctp.h smbno.h snmp.h \
On 12/09/06, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
I get this while umounting jfs (umount segfaulted).
BUG: unable to handle kernel paging request at virtual address 6b6b6c4f
printing eip:
c013a612
*pde = 00000000
Oops: 0002 [#1]
4K_STACKS PREEMPT SMP
last sysfs file: /devices/platform/i2c-9191/9191-0290/temp2_input
Modules linked in: jfs nls_base xfs reiser4 reiserfs ext2 loop ipv6
w83627hf hwmon_vid hwmon i2c_isa af_packet ip_conntrack_netbios_ns
ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter
ip_tables x_tables cpufreq_userspace p4_clockmod speedstep_lib
binfmt_misc thermal processor fan container evdev snd_intel8x0
snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss
snd_pcm sk98lin snd_timer skge snd soundcore snd_page_alloc intel_agp
agpgart ide_cd i2c_i801 iTCO_wdt cdrom rtc unix
CPU: 1
EIP: 0060:[<c013a612>] Not tainted VLI
EFLAGS: 00010046 (2.6.18-rc6-mm2 #120)
EIP is at __lock_acquire+0x35e/0xae8
eax: 00000000 ebx: 6b6b6b6b ecx: c036b3d8 edx: 00000000
esi: 00000002 edi: f1620030 ebp: f158be7c esp: f158be48
ds: 007b es: 007b ss: 0068
Process umount (pid: 19719, ti=f158b000 task=f1620030 task.ti=f158b000)
Stack: 000007bf 00000000 00000000 f173fd4c f1620030 f2543874 00000002 00000000
00000078 c02f980b f16205b8 00000002 f1620030 f158beb0 c013ae74 00000000
00000002 00000000 fdcfc85b c02f7e43 00000003 f1620590 00000004 f1620608
Call Trace:
[<c013ae74>] lock_release_non_nested+0xd8/0x143
[<c013b291>] lock_release+0x178/0x19f
[<c02f7dc5>] __mutex_unlock_slowpath+0xbb/0x131
[<c02f7e43>] mutex_unlock+0x8/0xa
[<c017655f>] generic_shutdown_super+0x9c/0xd9
[<c01765bc>] kill_block_super+0x20/0x32
[<c017667c>] deactivate_super+0x5d/0x6f
[<c01892bc>] mntput_no_expire+0x52/0x85
[<c017b2c9>] path_release_on_umount+0x15/0x18
[<c018a469>] sys_umount+0x1e1/0x215
[<c018a4aa>] sys_oldumount+0xd/0xf
[<c0103156>] sysenter_past_esp+0x5f/0x99
DWARF2 unwinder stuck at sysenter_past_esp+0x5f/0x99
Leftover inexact backtrace:
=======================
Code: 68 0b e6 2f c0 68 e7 04 00 00 68 e9 f4 31 c0 68 f4 84 31 c0 e8
7f 7b fe ff e8 3d a4 fc ff 83 c4 10 eb 08 85 db 0f 84 6d 07 00 00 <f0>
ff 83 e4 00 00 00 8b 55 dc 8b 92 5c 05 00 00 89 55 e4 83 fa
EIP: [<c013a612>] __lock_acquire+0x35e/0xae8 SS:ESP 0068:f158be48
<3>BUG: sleeping function called from invalid context at
/usr/src/linux-mm/mm/slab.c:2985
in_atomic():0, irqs_disabled():1
[<c01041ba>] dump_trace+0x63/0x1ca
[<c0104333>] show_trace_log_lvl+0x12/0x25
[<c0104993>] show_trace+0xd/0x10
[<c0104a58>] dump_stack+0x16/0x18
[<c011a8b7>] __might_sleep+0x8d/0x95
[<c01709f7>] kmem_cache_zalloc+0x28/0xe3
[<c0152dae>] taskstats_exit_alloc+0x2e/0x6c
[<c01246e4>] do_exit+0x1b6/0x9fe
[<c01048a3>] die+0x2ae/0x2d4
[<c0118b0c>] do_page_fault+0x4a4/0x584
[<c02f9b4f>] error_code+0x3f/0x44
DWARF2 unwinder stuck at error_code+0x3f/0x44
Leftover inexact backtrace:
[<c013ae74>] lock_release_non_nested+0xd8/0x143
[<c013b291>] lock_release+0x178/0x19f
[<c02f7dc5>] __mutex_unlock_slowpath+0xbb/0x131
[<c02f7e43>] mutex_unlock+0x8/0xa
[<c017655f>] generic_shutdown_super+0x9c/0xd9
[<c01765bc>] kill_block_super+0x20/0x32
[<c017667c>] deactivate_super+0x5d/0x6f
[<c01892bc>] mntput_no_expire+0x52/0x85
[<c017b2c9>] path_release_on_umount+0x15/0x18
[<c018a469>] sys_umount+0x1e1/0x215
[<c018a4aa>] sys_oldumount+0xd/0xf
[<c0103156>] sysenter_past_esp+0x5f/0x99
=======================
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-config1
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On 12/09/06, Michal Piotrowski <[email protected]> wrote:
> On 12/09/06, Andrew Morton <[email protected]> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> >
>
> I get this while umounting jfs (umount segfaulted).
s/jfs/xfs
/home/michal/bin/test_mount_fs.sh: line 22: 2354 Segmentation fault
sudo umount /mnt/fs-farm/xfs/
>
> BUG: unable to handle kernel paging request at virtual address 6b6b6c4f
> printing eip:
> c013a612
> *pde = 00000000
> Oops: 0002 [#1]
> 4K_STACKS PREEMPT SMP
> last sysfs file: /devices/platform/i2c-9191/9191-0290/temp2_input
> Modules linked in: jfs nls_base xfs reiser4 reiserfs ext2 loop ipv6
> w83627hf hwmon_vid hwmon i2c_isa af_packet ip_conntrack_netbios_ns
> ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter
> ip_tables x_tables cpufreq_userspace p4_clockmod speedstep_lib
> binfmt_misc thermal processor fan container evdev snd_intel8x0
> snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
> snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss
> snd_pcm sk98lin snd_timer skge snd soundcore snd_page_alloc intel_agp
> agpgart ide_cd i2c_i801 iTCO_wdt cdrom rtc unix
> CPU: 1
> EIP: 0060:[<c013a612>] Not tainted VLI
> EFLAGS: 00010046 (2.6.18-rc6-mm2 #120)
> EIP is at __lock_acquire+0x35e/0xae8
> eax: 00000000 ebx: 6b6b6b6b ecx: c036b3d8 edx: 00000000
> esi: 00000002 edi: f1620030 ebp: f158be7c esp: f158be48
> ds: 007b es: 007b ss: 0068
> Process umount (pid: 19719, ti=f158b000 task=f1620030 task.ti=f158b000)
> Stack: 000007bf 00000000 00000000 f173fd4c f1620030 f2543874 00000002 00000000
> 00000078 c02f980b f16205b8 00000002 f1620030 f158beb0 c013ae74 00000000
> 00000002 00000000 fdcfc85b c02f7e43 00000003 f1620590 00000004 f1620608
> Call Trace:
> [<c013ae74>] lock_release_non_nested+0xd8/0x143
> [<c013b291>] lock_release+0x178/0x19f
> [<c02f7dc5>] __mutex_unlock_slowpath+0xbb/0x131
> [<c02f7e43>] mutex_unlock+0x8/0xa
> [<c017655f>] generic_shutdown_super+0x9c/0xd9
> [<c01765bc>] kill_block_super+0x20/0x32
> [<c017667c>] deactivate_super+0x5d/0x6f
> [<c01892bc>] mntput_no_expire+0x52/0x85
> [<c017b2c9>] path_release_on_umount+0x15/0x18
> [<c018a469>] sys_umount+0x1e1/0x215
> [<c018a4aa>] sys_oldumount+0xd/0xf
> [<c0103156>] sysenter_past_esp+0x5f/0x99
> DWARF2 unwinder stuck at sysenter_past_esp+0x5f/0x99
>
> Leftover inexact backtrace:
>
> =======================
> Code: 68 0b e6 2f c0 68 e7 04 00 00 68 e9 f4 31 c0 68 f4 84 31 c0 e8
> 7f 7b fe ff e8 3d a4 fc ff 83 c4 10 eb 08 85 db 0f 84 6d 07 00 00 <f0>
> ff 83 e4 00 00 00 8b 55 dc 8b 92 5c 05 00 00 89 55 e4 83 fa
> EIP: [<c013a612>] __lock_acquire+0x35e/0xae8 SS:ESP 0068:f158be48
> <3>BUG: sleeping function called from invalid context at
> /usr/src/linux-mm/mm/slab.c:2985
> in_atomic():0, irqs_disabled():1
> [<c01041ba>] dump_trace+0x63/0x1ca
> [<c0104333>] show_trace_log_lvl+0x12/0x25
> [<c0104993>] show_trace+0xd/0x10
> [<c0104a58>] dump_stack+0x16/0x18
> [<c011a8b7>] __might_sleep+0x8d/0x95
> [<c01709f7>] kmem_cache_zalloc+0x28/0xe3
> [<c0152dae>] taskstats_exit_alloc+0x2e/0x6c
> [<c01246e4>] do_exit+0x1b6/0x9fe
> [<c01048a3>] die+0x2ae/0x2d4
> [<c0118b0c>] do_page_fault+0x4a4/0x584
> [<c02f9b4f>] error_code+0x3f/0x44
> DWARF2 unwinder stuck at error_code+0x3f/0x44
> Leftover inexact backtrace:
>
> [<c013ae74>] lock_release_non_nested+0xd8/0x143
> [<c013b291>] lock_release+0x178/0x19f
> [<c02f7dc5>] __mutex_unlock_slowpath+0xbb/0x131
> [<c02f7e43>] mutex_unlock+0x8/0xa
> [<c017655f>] generic_shutdown_super+0x9c/0xd9
> [<c01765bc>] kill_block_super+0x20/0x32
> [<c017667c>] deactivate_super+0x5d/0x6f
> [<c01892bc>] mntput_no_expire+0x52/0x85
> [<c017b2c9>] path_release_on_umount+0x15/0x18
> [<c018a469>] sys_umount+0x1e1/0x215
> [<c018a4aa>] sys_oldumount+0xd/0xf
> [<c0103156>] sysenter_past_esp+0x5f/0x99
> =======================
>
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-config1
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Tue, Sep 12, 2006 at 12:06:18AM -0700, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
Hi,
It looks like Zach Brown's patch pr_debug-check-pr_debug-arguments
worked as inteded. That is, it doesn't "allow completely incorrect code
to build." :).
The arm build fails with the following message:
CC arch/arm/vfp/vfpsingle.o
arch/arm/vfp/vfpsingle.c: In function `__vfp_single_normaliseround':
arch/arm/vfp/vfpsingle.c:201: error: `func' undeclared (first use in
this function)
arch/arm/vfp/vfpsingle.c:201: error: (Each undeclared identifier is
reported only once
arch/arm/vfp/vfpsingle.c:201: error: for each function it appears in.)
make[1]: *** [arch/arm/vfp/vfpsingle.o] Error 1
make: *** [arch/arm/vfp] Error 2
The following patch fixes the issue by using func only when DEBUG is
defined.
Regards,
Frederik
Signed-off-by: Frederik Deweerdt <[email protected]>
--- 2.6.18-rc6-mm2/arch/arm/vfp/vfpsingle.c~ 2006-09-12 19:57:50 +0000
+++ 2.6.18-rc6-mm2/arch/arm/vfp/vfpsingle.c 2006-09-12 19:58:07 +0000
@@ -198,8 +198,10 @@ u32 vfp_single_normaliseround(int sd, st
vfp_single_dump("pack: final", vs);
{
s32 d = vfp_single_pack(vs);
+#ifdef DEBUG
pr_debug("VFP: %s: d(s%d)=%08x exceptions=%08x\n", func,
sd, d, exceptions);
+#endif
vfp_put_float(d, sd);
}
Frederik Deweerdt wrote:
> On Tue, Sep 12, 2006 at 12:06:18AM -0700, Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>>
> Hi,
>
> It looks like Zach Brown's patch pr_debug-check-pr_debug-arguments
> worked as inteded.
:). I should really take the time to get some cross compilers going.
> arch/arm/vfp/vfpsingle.c:201: error: `func' undeclared (first use in
> this function)
Does changing 'func' to '__func__' in the arguments fix it?
- z
On Tue, Sep 12, 2006 at 11:27:57AM -0700, Zach Brown wrote:
> Frederik Deweerdt wrote:
> > On Tue, Sep 12, 2006 at 12:06:18AM -0700, Andrew Morton wrote:
> >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> >>
> > Hi,
> >
> > It looks like Zach Brown's patch pr_debug-check-pr_debug-arguments
> > worked as inteded.
>
> :). I should really take the time to get some cross compilers going.
>
> > arch/arm/vfp/vfpsingle.c:201: error: `func' undeclared (first use in
> > this function)
>
> Does changing 'func' to '__func__' in the arguments fix it?
Yes it does, but the intended use of 'func' (or so I understood) is to
print the calling function name, not the current function's, isn't it?
Frederik
>
> - z
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> Yes it does, but the intended use of 'func' (or so I understood) is to
> print the calling function name, not the current function's, isn't it?
Dunno, I took it to mean the current function from the context of that
patch. I could be wrong, of course.
- z
On 12/09/06, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
My FC6T2 bug appeared in -mm
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202223
Any ideas about this?
echo shutdown > /sys/power/disk; echo disk > /sys/power/state
CPU 1 is now offline
lockdep: not fixing up alternatives.
=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.18-rc6-mm2 #120
-------------------------------------------------------
bash/1961 is trying to acquire lock:
((cpu_chain).rwsem){----}, at: [<c012e289>]
blocking_notifier_call_chain+0x11/0x2d
but task is already holding lock:
(workqueue_mutex){--..}, at: [<c02f8156>] mutex_lock+0x1c/0x1f
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (workqueue_mutex){--..}:
[<c0138b97>] add_lock_to_list+0x5c/0x7a
[<c013aca0>] __lock_acquire+0x9ec/0xae8
[<c013b0fc>] lock_acquire+0x6b/0x88
[<c02f7f1b>] __mutex_lock_slowpath+0xd6/0x2f5
[<c02f8156>] mutex_lock+0x1c/0x1f
[<c01312de>] workqueue_cpu_callback+0x109/0x1ff
[<c012de43>] notifier_call_chain+0x20/0x31
[<c012e295>] blocking_notifier_call_chain+0x1d/0x2d
[<c013f867>] _cpu_down+0x48/0x207
[<c013fbf8>] disable_nonboot_cpus+0x98/0x12c
[<c01451d6>] prepare_processes+0xe/0x41
[<c014539e>] pm_suspend_disk+0x9/0xe2
[<c0144635>] enter_state+0x53/0x177
[<c01447df>] state_store+0x86/0x9c
[<c01abde4>] subsys_attr_store+0x20/0x25
[<c01abee3>] sysfs_write_file+0xa6/0xcc
[<c0174d60>] vfs_write+0xcd/0x174
[<c01753fa>] sys_write+0x3b/0x71
[<c0103156>] sysenter_past_esp+0x5f/0x99
[<ffffffff>] 0xffffffff
-> #0 ((cpu_chain).rwsem){----}:
[<c013a280>] print_circular_bug_tail+0x2e/0x62
[<c013abd7>] __lock_acquire+0x923/0xae8
[<c013b0fc>] lock_acquire+0x6b/0x88
[<c0136e60>] down_read+0x28/0x3b
[<c012e289>] blocking_notifier_call_chain+0x11/0x2d
[<c013f98e>] _cpu_down+0x16f/0x207
[<c013fbf8>] disable_nonboot_cpus+0x98/0x12c
[<c01451d6>] prepare_processes+0xe/0x41
[<c014539e>] pm_suspend_disk+0x9/0xe2
[<c0144635>] enter_state+0x53/0x177
[<c01447df>] state_store+0x86/0x9c
[<c01abde4>] subsys_attr_store+0x20/0x25
[<c01abee3>] sysfs_write_file+0xa6/0xcc
[<c0174d60>] vfs_write+0xcd/0x174
[<c01753fa>] sys_write+0x3b/0x71
[<c0103156>] sysenter_past_esp+0x5f/0x99
[<ffffffff>] 0xffffffff
other info that might help us debug this:
2 locks held by bash/1961:
#0: (cpu_add_remove_lock){--..}, at: [<c02f8156>] mutex_lock+0x1c/0x1f
#1: (workqueue_mutex){--..}, at: [<c02f8156>] mutex_lock+0x1c/0x1f
stack backtrace:
[<c01041ba>] dump_trace+0x63/0x1ca
[<c0104333>] show_trace_log_lvl+0x12/0x25
[<c0104993>] show_trace+0xd/0x10
[<c0104a58>] dump_stack+0x16/0x18
[<c013a2a9>] print_circular_bug_tail+0x57/0x62
[<c013abd7>] __lock_acquire+0x923/0xae8
[<c013b0fc>] lock_acquire+0x6b/0x88
[<c0136e60>] down_read+0x28/0x3b
[<c012e289>] blocking_notifier_call_chain+0x11/0x2d
[<c013f98e>] _cpu_down+0x16f/0x207
[<c013fbf8>] disable_nonboot_cpus+0x98/0x12c
[<c01451d6>] prepare_processes+0xe/0x41
[<c014539e>] pm_suspend_disk+0x9/0xe2
[<c0144635>] enter_state+0x53/0x177
[<c01447df>] state_store+0x86/0x9c
[<c01abde4>] subsys_attr_store+0x20/0x25
[<c01abee3>] sysfs_write_file+0xa6/0xcc
[<c0174d60>] vfs_write+0xcd/0x174
[<c01753fa>] sys_write+0x3b/0x71
[<c0103156>] sysenter_past_esp+0x5f/0x99
DWARF2 unwinder stuck at sysenter_past_esp+0x5f/0x99
Leftover inexact backtrace:
l *blocking_notifier_call_chain+0x11/0x2d
0xc012e278 is in blocking_notifier_call_chain
(/usr/src/linux-mm/kernel/sys.c:324).
319 * of the last notifier function called.
320 */
321
322 int blocking_notifier_call_chain(struct blocking_notifier_head *nh,
323 unsigned long val, void *v)
324 {
325 int ret;
326
327 down_read(&nh->rwsem);
328 ret = notifier_call_chain(&nh->head, val, v);
l *mutex_lock+0x1c/0x1f
0xc02f813a is in mutex_lock (/usr/src/linux-mm/kernel/mutex.c:85).
80 * deadlock debugging. )
81 *
82 * This function is similar to (but not equivalent to) down().
83 */
84 void inline fastcall __sched mutex_lock(struct mutex *lock)
85 {
86 might_sleep();
87 /*
88 * The locking fastpath is the 1->0 transition from
89 * 'unlocked' into 'locked' state.
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg2
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-config1
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Tue, Sep 12, 2006 at 12:07:35PM -0700, Zach Brown wrote:
>
> > Yes it does, but the intended use of 'func' (or so I understood) is to
> > print the calling function name, not the current function's, isn't it?
>
> Dunno, I took it to mean the current function from the context of that
> patch. I could be wrong, of course.
I've just checked, this are some of the callers of
vfp_single_normaliseround (last argument is 'func'):
in vfp_single_fuito:
vfp_single_normaliseround(sd, &vs, fpscr, 0, "fuito");
in vfp_single_fsito:
vfp_single_normaliseround(sd, &vs, fpscr, 0, "fsito");
in vfp_single_fnmul:
vfp_single_normaliseround(sd, &vsd, fpscr, exceptions, "fnmul");
It definitely looks like we want the calling function to be printed
here.
Regards,
Frederik
>
> - z
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Michal Piotrowski wrote:
> On 12/09/06, Andrew Morton <[email protected]> wrote:
>>
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>>
>>
>
> My FC6T2 bug appeared in -mm
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202223
>
> Any ideas about this?
Hi,
this is known:
http://lkml.org/lkml/2006/9/8/56
> echo shutdown > /sys/power/disk; echo disk > /sys/power/state
>
> CPU 1 is now offline
> lockdep: not fixing up alternatives.
>
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 2.6.18-rc6-mm2 #120
> -------------------------------------------------------
> bash/1961 is trying to acquire lock:
> ((cpu_chain).rwsem){----}, at: [<c012e289>]
> blocking_notifier_call_chain+0x11/0x2d
>
> but task is already holding lock:
> (workqueue_mutex){--..}, at: [<c02f8156>] mutex_lock+0x1c/0x1f
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
> -> #1 (workqueue_mutex){--..}:
> [<c0138b97>] add_lock_to_list+0x5c/0x7a
> [<c013aca0>] __lock_acquire+0x9ec/0xae8
> [<c013b0fc>] lock_acquire+0x6b/0x88
> [<c02f7f1b>] __mutex_lock_slowpath+0xd6/0x2f5
> [<c02f8156>] mutex_lock+0x1c/0x1f
> [<c01312de>] workqueue_cpu_callback+0x109/0x1ff
> [<c012de43>] notifier_call_chain+0x20/0x31
> [<c012e295>] blocking_notifier_call_chain+0x1d/0x2d
> [<c013f867>] _cpu_down+0x48/0x207
> [<c013fbf8>] disable_nonboot_cpus+0x98/0x12c
> [<c01451d6>] prepare_processes+0xe/0x41
> [<c014539e>] pm_suspend_disk+0x9/0xe2
> [<c0144635>] enter_state+0x53/0x177
> [<c01447df>] state_store+0x86/0x9c
> [<c01abde4>] subsys_attr_store+0x20/0x25
> [<c01abee3>] sysfs_write_file+0xa6/0xcc
> [<c0174d60>] vfs_write+0xcd/0x174
> [<c01753fa>] sys_write+0x3b/0x71
> [<c0103156>] sysenter_past_esp+0x5f/0x99
> [<ffffffff>] 0xffffffff
> -> #0 ((cpu_chain).rwsem){----}:
> [<c013a280>] print_circular_bug_tail+0x2e/0x62
> [<c013abd7>] __lock_acquire+0x923/0xae8
> [<c013b0fc>] lock_acquire+0x6b/0x88
> [<c0136e60>] down_read+0x28/0x3b
> [<c012e289>] blocking_notifier_call_chain+0x11/0x2d
> [<c013f98e>] _cpu_down+0x16f/0x207
> [<c013fbf8>] disable_nonboot_cpus+0x98/0x12c
> [<c01451d6>] prepare_processes+0xe/0x41
> [<c014539e>] pm_suspend_disk+0x9/0xe2
> [<c0144635>] enter_state+0x53/0x177
> [<c01447df>] state_store+0x86/0x9c
> [<c01abde4>] subsys_attr_store+0x20/0x25
> [<c01abee3>] sysfs_write_file+0xa6/0xcc
> [<c0174d60>] vfs_write+0xcd/0x174
> [<c01753fa>] sys_write+0x3b/0x71
> [<c0103156>] sysenter_past_esp+0x5f/0x99
> [<ffffffff>] 0xffffffff
>
> other info that might help us debug this:
>
> 2 locks held by bash/1961:
> #0: (cpu_add_remove_lock){--..}, at: [<c02f8156>] mutex_lock+0x1c/0x1f
> #1: (workqueue_mutex){--..}, at: [<c02f8156>] mutex_lock+0x1c/0x1f
>
> stack backtrace:
> [<c01041ba>] dump_trace+0x63/0x1ca
> [<c0104333>] show_trace_log_lvl+0x12/0x25
> [<c0104993>] show_trace+0xd/0x10
> [<c0104a58>] dump_stack+0x16/0x18
> [<c013a2a9>] print_circular_bug_tail+0x57/0x62
> [<c013abd7>] __lock_acquire+0x923/0xae8
> [<c013b0fc>] lock_acquire+0x6b/0x88
> [<c0136e60>] down_read+0x28/0x3b
> [<c012e289>] blocking_notifier_call_chain+0x11/0x2d
> [<c013f98e>] _cpu_down+0x16f/0x207
> [<c013fbf8>] disable_nonboot_cpus+0x98/0x12c
> [<c01451d6>] prepare_processes+0xe/0x41
> [<c014539e>] pm_suspend_disk+0x9/0xe2
> [<c0144635>] enter_state+0x53/0x177
> [<c01447df>] state_store+0x86/0x9c
> [<c01abde4>] subsys_attr_store+0x20/0x25
> [<c01abee3>] sysfs_write_file+0xa6/0xcc
> [<c0174d60>] vfs_write+0xcd/0x174
> [<c01753fa>] sys_write+0x3b/0x71
> [<c0103156>] sysenter_past_esp+0x5f/0x99
> DWARF2 unwinder stuck at sysenter_past_esp+0x5f/0x99
>
> Leftover inexact backtrace:
>
> l *blocking_notifier_call_chain+0x11/0x2d
> 0xc012e278 is in blocking_notifier_call_chain
> (/usr/src/linux-mm/kernel/sys.c:324).
> 319 * of the last notifier function called.
> 320 */
> 321
> 322 int blocking_notifier_call_chain(struct blocking_notifier_head *nh,
> 323 unsigned long val, void *v)
> 324 {
> 325 int ret;
> 326
> 327 down_read(&nh->rwsem);
> 328 ret = notifier_call_chain(&nh->head, val, v);
>
> l *mutex_lock+0x1c/0x1f
> 0xc02f813a is in mutex_lock (/usr/src/linux-mm/kernel/mutex.c:85).
> 80 * deadlock debugging. )
> 81 *
> 82 * This function is similar to (but not equivalent to) down().
> 83 */
> 84 void inline fastcall __sched mutex_lock(struct mutex *lock)
> 85 {
> 86 might_sleep();
> 87 /*
> 88 * The locking fastpath is the 1->0 transition from
> 89 * 'unlocked' into 'locked' state.
>
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg2
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-config1
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
Jiri Slaby wrote:
> Michal Piotrowski wrote:
>> On 12/09/06, Andrew Morton <[email protected]> wrote:
>>>
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>>>
>>>
>>
>> My FC6T2 bug appeared in -mm
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202223
>>
>> Any ideas about this?
>
> Hi,
> this is known:
> http://lkml.org/lkml/2006/9/8/56
Of course, you know it, there is a link to the redhat bugzilla in the root post
of this...
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
On Tue, 12 Sep 2006 17:42:10 +0200
"Michal Piotrowski" <[email protected]> wrote:
> On 12/09/06, Michal Piotrowski <[email protected]> wrote:
> > On 12/09/06, Andrew Morton <[email protected]> wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> > >
> >
> > I get this while umounting jfs (umount segfaulted).
>
> s/jfs/xfs
Do you mean that both JFS and XFS exhibit this bug, or only XFS?
> /home/michal/bin/test_mount_fs.sh: line 22: 2354 Segmentation fault
> sudo umount /mnt/fs-farm/xfs/
>
On 13/09/06, Andrew Morton <[email protected]> wrote:
> On Tue, 12 Sep 2006 17:42:10 +0200
> "Michal Piotrowski" <[email protected]> wrote:
>
> > On 12/09/06, Michal Piotrowski <[email protected]> wrote:
> > > On 12/09/06, Andrew Morton <[email protected]> wrote:
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> > > >
> > >
> > > I get this while umounting jfs (umount segfaulted).
> >
> > s/jfs/xfs
>
> Do you mean that both JFS and XFS exhibit this bug, or only XFS?
Only XFS. (s/jfs/xfs - "Thinking in s/c++/sed :)")
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Wed, 13 Sep 2006 01:34:34 +0200
"Michal Piotrowski" <[email protected]> wrote:
> On 13/09/06, Andrew Morton <[email protected]> wrote:
> > On Tue, 12 Sep 2006 17:42:10 +0200
> > "Michal Piotrowski" <[email protected]> wrote:
> >
> > > On 12/09/06, Michal Piotrowski <[email protected]> wrote:
> > > > On 12/09/06, Andrew Morton <[email protected]> wrote:
> > > > >
> > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> > > > >
> > > >
> > > > I get this while umounting jfs (umount segfaulted).
> > >
> > > s/jfs/xfs
> >
> > Do you mean that both JFS and XFS exhibit this bug, or only XFS?
>
> Only XFS. (s/jfs/xfs - "Thinking in s/c++/sed :)")
>
OK, thanks. Let us rub the xfs-masters lamp and see what emerges.
On Tue, Sep 12, 2006 at 04:37:49PM -0700, Andrew Morton wrote:
> On Wed, 13 Sep 2006 01:34:34 +0200
> "Michal Piotrowski" <[email protected]> wrote:
>
> > On 13/09/06, Andrew Morton <[email protected]> wrote:
> > > On Tue, 12 Sep 2006 17:42:10 +0200
> > > "Michal Piotrowski" <[email protected]> wrote:
> > >
> > > > On 12/09/06, Michal Piotrowski <[email protected]> wrote:
> > > > > On 12/09/06, Andrew Morton <[email protected]> wrote:
> > > > > >
> > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> > > > > >
> > > > >
> > > > > I get this while umounting jfs (umount segfaulted).
> > > >
> > > > s/jfs/xfs
> > >
> > > Do you mean that both JFS and XFS exhibit this bug, or only XFS?
> >
> > Only XFS. (s/jfs/xfs - "Thinking in s/c++/sed :)")
>
> OK, thanks. Let us rub the xfs-masters lamp and see what emerges.
Just for XFs list folks:
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-config1
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1
Call Trace:
[<c013ae74>] lock_release_non_nested+0xd8/0x143
[<c013b291>] lock_release+0x178/0x19f
[<c02f7dc5>] __mutex_unlock_slowpath+0xbb/0x131
[<c02f7e43>] mutex_unlock+0x8/0xa
[<c017655f>] generic_shutdown_super+0x9c/0xd9
[<c01765bc>] kill_block_super+0x20/0x32
[<c017667c>] deactivate_super+0x5d/0x6f
[<c01892bc>] mntput_no_expire+0x52/0x85
[<c017b2c9>] path_release_on_umount+0x15/0x18
[<c018a469>] sys_umount+0x1e1/0x215
[<c018a4aa>] sys_oldumount+0xd/0xf
[<c0103156>] sysenter_past_esp+0x5f/0x99
I'm not sure why XFS would cause this - the crash is outside XFS releasing
a mutex (sb->s_lock) that XFS code has never touched. I doubt anyone
in the XFS team has done any testing on this -mm kernel...
What is the test case, Michal? Can you post the script you used?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
On Wed, Sep 13, 2006 at 11:58:50AM +1000, David Chinner wrote:
> Call Trace:
> [<c013ae74>] lock_release_non_nested+0xd8/0x143
> [<c013b291>] lock_release+0x178/0x19f
> [<c02f7dc5>] __mutex_unlock_slowpath+0xbb/0x131
> [<c02f7e43>] mutex_unlock+0x8/0xa
> [<c017655f>] generic_shutdown_super+0x9c/0xd9
> [<c01765bc>] kill_block_super+0x20/0x32
> [<c017667c>] deactivate_super+0x5d/0x6f
> [<c01892bc>] mntput_no_expire+0x52/0x85
> [<c017b2c9>] path_release_on_umount+0x15/0x18
> [<c018a469>] sys_umount+0x1e1/0x215
> [<c018a4aa>] sys_oldumount+0xd/0xf
> [<c0103156>] sysenter_past_esp+0x5f/0x99
>
> I'm not sure why XFS would cause this - the crash is outside XFS releasing
> a mutex (sb->s_lock) that XFS code has never touched. I doubt anyone
> in the XFS team has done any testing on this -mm kernel...
>
> What is the test case, Michal? Can you post the script you used?
I've booted 2.6.18-rc6-mm2 and mounted and unmounted several xfs
filesystems. I'm currently running xfsqa on it, and I haven't seen
any failures on unmount yet.
That test case would be really handy, Michal.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
On 13/09/06, David Chinner <[email protected]> wrote:
> On Wed, Sep 13, 2006 at 11:58:50AM +1000, David Chinner wrote:
> > Call Trace:
> > [<c013ae74>] lock_release_non_nested+0xd8/0x143
> > [<c013b291>] lock_release+0x178/0x19f
> > [<c02f7dc5>] __mutex_unlock_slowpath+0xbb/0x131
> > [<c02f7e43>] mutex_unlock+0x8/0xa
> > [<c017655f>] generic_shutdown_super+0x9c/0xd9
> > [<c01765bc>] kill_block_super+0x20/0x32
> > [<c017667c>] deactivate_super+0x5d/0x6f
> > [<c01892bc>] mntput_no_expire+0x52/0x85
> > [<c017b2c9>] path_release_on_umount+0x15/0x18
> > [<c018a469>] sys_umount+0x1e1/0x215
> > [<c018a4aa>] sys_oldumount+0xd/0xf
> > [<c0103156>] sysenter_past_esp+0x5f/0x99
> >
> > I'm not sure why XFS would cause this - the crash is outside XFS releasing
> > a mutex (sb->s_lock) that XFS code has never touched. I doubt anyone
> > in the XFS team has done any testing on this -mm kernel...
> >
> > What is the test case, Michal? Can you post the script you used?
>
> I've booted 2.6.18-rc6-mm2 and mounted and unmounted several xfs
> filesystems. I'm currently running xfsqa on it, and I haven't seen
> any failures on unmount yet.
>
> That test case would be really handy, Michal.
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/test_mount_fs.sh
ls -hs /home/fs-farm/
total 3.6G
513M ext2.img 513M ext4.img 513M reiser3.img 513M xfs.img
513M ext3.img 513M jfs.img 513M reiser4.img
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> Principal Engineer
> SGI Australian Software Group
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Tuesday, 12 September 2006 09:06, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
'rmmod ohci_hcd' causes the following oops to appear on my HPC 6325 every
time (happens also on -rc6-mm1, does not happen on -rc7):
Unable to handle kernel NULL pointer dereference at 0000000000000274 RIP:
[<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
PGD 35ca9067 PUD 369a4067 PMD 0
Oops: 0000 [1] SMP
last sysfs file: /devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
CPU 0
Modules linked in: netconsole cpufreq_ondemand cpufreq_userspace cpufreq_powersa
ve powernow_k8 freq_table button af_packet edd battery snd_pcm_oss snd_mixer_oss
snd_seq snd_seq_device ac ip6t_REJECT xt_tcpudp ipt_REJECT xt_state iptable_man
gle iptable_nat ip_nat iptable_filter ip6table_mangle ip_conntrack nfnetlink ip_
tables ip6table_filter ip6_tables x_tables ipv6 loop dm_mod usbhid ff_memless hc
i_usb bluetooth snd_hda_intel snd_hda_codec bcm43xx ohci1394 ohci_hcd shpchp pci
_hotplug pcmcia ehci_hcd i2c_piix4 ieee1394 firmware_class ieee80211softmac usbc
ore tg3 sdhci ieee80211 ieee80211_crypt mmc_core ide_cd k8temp yenta_socket rsrc
_nonstatic pcmcia_core i2c_core hwmon snd_pcm snd_timer snd soundcore snd_page_a
lloc cdrom ext3 jbd fan thermal processor atiixp ide_disk ide_core sg
Pid: 3667, comm: rmmod Tainted: G M 2.6.18-rc6-mm2 #19
RIP: 0010:[<ffffffff8822c185>] [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_d
ata+0x25/0x27b
RSP: 0018:ffffffff805c7e18 EFLAGS: 00010296
RAX: 0000000000000000 RBX: ffff81003485c508 RCX: 0000000000000000
RDX: 0000000000000064 RSI: ffffffff805c7e68 RDI: ffff81003485c640
RBP: ffffffff805c7e58 R08: 0000000000000000 R09: ffff810037438138
R10: ffffffff80701c40 R11: ffff81003263bc88 R12: ffff81003485c640
R13: ffffffff805c7e68 R14: ffffc2000003c000 R15: ffff81003485c508
FS: 00002ba0d06fa6d0(0000) GS:ffffffff8066f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000274 CR3: 000000002f153000 CR4: 00000000000006e0
Process rmmod (pid: 3667, threadinfo ffff81003263a000, task ffff81003697c810)
Stack: ffffffff802813b0 ffffffff805c7e40 ffffffff80281258 ffff81003485c508
ffff81003485c508 ffff81003485c508 ffffc2000003c000 ffffffff805c7e68
ffffffff805c7ea8 ffffffff8818e03f 003d09e3f5998950 ffffffff80509860
Call Trace:
[<ffffffff8818e03f>] :usbcore:usb_hcd_poll_rh_status+0x40/0x13b
[<ffffffff8822c01b>] :ohci_hcd:ohci_irq+0xcb/0x210
[<ffffffff8818e78b>] :usbcore:usb_hcd_irq+0x2f/0x5f
[<ffffffff8020ef13>] handle_IRQ_event+0x33/0x66
[<ffffffff802af5f8>] handle_fasteoi_irq+0x9d/0xe3
[<ffffffff80267c85>] do_IRQ+0x104/0x11f
[<ffffffff80259621>] ret_from_intr+0x0/0xa
DWARF2 unwinder stuck at ret_from_intr+0x0/0xa
Leftover inexact backtrace:
<IRQ> <EOI> [<ffffffff802ee4ac>] sysfs_hash_and_remove+0x9/0x137
[<ffffffff802eed13>] sysfs_remove_file+0x10/0x12
[<ffffffff8038baf7>] class_device_remove_file+0x12/0x14
[<ffffffff8822aa02>] :ohci_hcd:ohci_stop+0xf5/0x17b
[<ffffffff8818d9d2>] :usbcore:usb_remove_hcd+0xdc/0x114
[<ffffffff8040f8eb>] klist_release+0x0/0x82
[<ffffffff88197f45>] :usbcore:usb_hcd_pci_remove+0x1e/0x7d
[<ffffffff803204d8>] pci_device_remove+0x25/0x3c
[<ffffffff8038b1b5>] __device_release_driver+0x80/0x9c
[<ffffffff8038b617>] driver_detach+0xac/0xee
[<ffffffff8038ad92>] bus_remove_driver+0x75/0x98
[<ffffffff8038b696>] driver_unregister+0x15/0x21
[<ffffffff80320686>] pci_unregister_driver+0x13/0x8e
[<ffffffff8822cd1c>] :ohci_hcd:ohci_hcd_pci_cleanup+0x10/0x12
[<ffffffff8029b281>] sys_delete_module+0x1b5/0x1e6
[<ffffffff8025910e>] system_call+0x7e/0x83
Code: 8a 98 74 02 00 00 e8 d6 3b 03 f8 48 89 45 d0 41 8b 84 24 e4
RIP [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
RSP <ffffffff805c7e18>
CR2: 0000000000000274
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
where
(gdb) l *ohci_hub_status_data+0x25
0x4185 is in ohci_hub_status_data (drivers/usb/host/ohci-hub.c:316).
311 struct ohci_hcd *ohci = hcd_to_ohci (hcd);
312 int i, changed = 0, length = 1;
313 int can_suspend;
314 unsigned long flags;
315
316 can_suspend = device_may_wakeup(&hcd->self.root_hub->dev);
317 spin_lock_irqsave (&ohci->lock, flags);
318
319 /* handle autosuspended root: finish resuming before
320 * letting khubd or root hub timer see state changes.
I guess it may be related to the suspend issues?
On Wednesday, 13 September 2006 15:58, Rafael J. Wysocki wrote:
> On Tuesday, 12 September 2006 09:06, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
> 'rmmod ohci_hcd' causes the following oops to appear on my HPC 6325 every
> time (happens also on -rc6-mm1, does not happen on -rc7):
So far, I have verified that the problem already happened on -rc5-mm1.
Greetings,
Rafael
> Unable to handle kernel NULL pointer dereference at 0000000000000274 RIP:
> [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
> PGD 35ca9067 PUD 369a4067 PMD 0
> Oops: 0000 [1] SMP
> last sysfs file: /devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
> CPU 0
> Modules linked in: netconsole cpufreq_ondemand cpufreq_userspace cpufreq_powersa
> ve powernow_k8 freq_table button af_packet edd battery snd_pcm_oss snd_mixer_oss
> snd_seq snd_seq_device ac ip6t_REJECT xt_tcpudp ipt_REJECT xt_state iptable_man
> gle iptable_nat ip_nat iptable_filter ip6table_mangle ip_conntrack nfnetlink ip_
> tables ip6table_filter ip6_tables x_tables ipv6 loop dm_mod usbhid ff_memless hc
> i_usb bluetooth snd_hda_intel snd_hda_codec bcm43xx ohci1394 ohci_hcd shpchp pci
> _hotplug pcmcia ehci_hcd i2c_piix4 ieee1394 firmware_class ieee80211softmac usbc
> ore tg3 sdhci ieee80211 ieee80211_crypt mmc_core ide_cd k8temp yenta_socket rsrc
> _nonstatic pcmcia_core i2c_core hwmon snd_pcm snd_timer snd soundcore snd_page_a
> lloc cdrom ext3 jbd fan thermal processor atiixp ide_disk ide_core sg
> Pid: 3667, comm: rmmod Tainted: G M 2.6.18-rc6-mm2 #19
> RIP: 0010:[<ffffffff8822c185>] [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_d
> ata+0x25/0x27b
> RSP: 0018:ffffffff805c7e18 EFLAGS: 00010296
> RAX: 0000000000000000 RBX: ffff81003485c508 RCX: 0000000000000000
> RDX: 0000000000000064 RSI: ffffffff805c7e68 RDI: ffff81003485c640
> RBP: ffffffff805c7e58 R08: 0000000000000000 R09: ffff810037438138
> R10: ffffffff80701c40 R11: ffff81003263bc88 R12: ffff81003485c640
> R13: ffffffff805c7e68 R14: ffffc2000003c000 R15: ffff81003485c508
> FS: 00002ba0d06fa6d0(0000) GS:ffffffff8066f000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000000274 CR3: 000000002f153000 CR4: 00000000000006e0
> Process rmmod (pid: 3667, threadinfo ffff81003263a000, task ffff81003697c810)
> Stack: ffffffff802813b0 ffffffff805c7e40 ffffffff80281258 ffff81003485c508
> ffff81003485c508 ffff81003485c508 ffffc2000003c000 ffffffff805c7e68
> ffffffff805c7ea8 ffffffff8818e03f 003d09e3f5998950 ffffffff80509860
> Call Trace:
> [<ffffffff8818e03f>] :usbcore:usb_hcd_poll_rh_status+0x40/0x13b
> [<ffffffff8822c01b>] :ohci_hcd:ohci_irq+0xcb/0x210
> [<ffffffff8818e78b>] :usbcore:usb_hcd_irq+0x2f/0x5f
> [<ffffffff8020ef13>] handle_IRQ_event+0x33/0x66
> [<ffffffff802af5f8>] handle_fasteoi_irq+0x9d/0xe3
> [<ffffffff80267c85>] do_IRQ+0x104/0x11f
> [<ffffffff80259621>] ret_from_intr+0x0/0xa
> DWARF2 unwinder stuck at ret_from_intr+0x0/0xa
>
> Leftover inexact backtrace:
>
> <IRQ> <EOI> [<ffffffff802ee4ac>] sysfs_hash_and_remove+0x9/0x137
> [<ffffffff802eed13>] sysfs_remove_file+0x10/0x12
> [<ffffffff8038baf7>] class_device_remove_file+0x12/0x14
> [<ffffffff8822aa02>] :ohci_hcd:ohci_stop+0xf5/0x17b
> [<ffffffff8818d9d2>] :usbcore:usb_remove_hcd+0xdc/0x114
> [<ffffffff8040f8eb>] klist_release+0x0/0x82
> [<ffffffff88197f45>] :usbcore:usb_hcd_pci_remove+0x1e/0x7d
> [<ffffffff803204d8>] pci_device_remove+0x25/0x3c
> [<ffffffff8038b1b5>] __device_release_driver+0x80/0x9c
> [<ffffffff8038b617>] driver_detach+0xac/0xee
> [<ffffffff8038ad92>] bus_remove_driver+0x75/0x98
> [<ffffffff8038b696>] driver_unregister+0x15/0x21
> [<ffffffff80320686>] pci_unregister_driver+0x13/0x8e
> [<ffffffff8822cd1c>] :ohci_hcd:ohci_hcd_pci_cleanup+0x10/0x12
> [<ffffffff8029b281>] sys_delete_module+0x1b5/0x1e6
> [<ffffffff8025910e>] system_call+0x7e/0x83
>
>
> Code: 8a 98 74 02 00 00 e8 d6 3b 03 f8 48 89 45 d0 41 8b 84 24 e4
> RIP [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
> RSP <ffffffff805c7e18>
> CR2: 0000000000000274
> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>
> where
>
> (gdb) l *ohci_hub_status_data+0x25
> 0x4185 is in ohci_hub_status_data (drivers/usb/host/ohci-hub.c:316).
> 311 struct ohci_hcd *ohci = hcd_to_ohci (hcd);
> 312 int i, changed = 0, length = 1;
> 313 int can_suspend;
> 314 unsigned long flags;
> 315
> 316 can_suspend = device_may_wakeup(&hcd->self.root_hub->dev);
> 317 spin_lock_irqsave (&ohci->lock, flags);
> 318
> 319 /* handle autosuspended root: finish resuming before
> 320 * letting khubd or root hub timer see state changes.
On Wed, 13 Sep 2006, Rafael J. Wysocki wrote:
> 'rmmod ohci_hcd' causes the following oops to appear on my HPC 6325 every
> time (happens also on -rc6-mm1, does not happen on -rc7):
>
> Unable to handle kernel NULL pointer dereference at 0000000000000274 RIP:
> [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
> PGD 35ca9067 PUD 369a4067 PMD 0
> Call Trace:
> [<ffffffff8818e03f>] :usbcore:usb_hcd_poll_rh_status+0x40/0x13b
> [<ffffffff8822c01b>] :ohci_hcd:ohci_irq+0xcb/0x210
> [<ffffffff8818e78b>] :usbcore:usb_hcd_irq+0x2f/0x5f
> [<ffffffff8020ef13>] handle_IRQ_event+0x33/0x66
> [<ffffffff802af5f8>] handle_fasteoi_irq+0x9d/0xe3
> [<ffffffff80267c85>] do_IRQ+0x104/0x11f
> [<ffffffff80259621>] ret_from_intr+0x0/0xa
> DWARF2 unwinder stuck at ret_from_intr+0x0/0xa
>
> Leftover inexact backtrace:
>
> <IRQ> <EOI> [<ffffffff802ee4ac>] sysfs_hash_and_remove+0x9/0x137
> [<ffffffff802eed13>] sysfs_remove_file+0x10/0x12
> [<ffffffff8038baf7>] class_device_remove_file+0x12/0x14
> [<ffffffff8822aa02>] :ohci_hcd:ohci_stop+0xf5/0x17b
> [<ffffffff8818d9d2>] :usbcore:usb_remove_hcd+0xdc/0x114
> [<ffffffff8040f8eb>] klist_release+0x0/0x82
> [<ffffffff88197f45>] :usbcore:usb_hcd_pci_remove+0x1e/0x7d
> [<ffffffff803204d8>] pci_device_remove+0x25/0x3c
> [<ffffffff8038b1b5>] __device_release_driver+0x80/0x9c
> [<ffffffff8038b617>] driver_detach+0xac/0xee
> [<ffffffff8038ad92>] bus_remove_driver+0x75/0x98
> [<ffffffff8038b696>] driver_unregister+0x15/0x21
> [<ffffffff80320686>] pci_unregister_driver+0x13/0x8e
> [<ffffffff8822cd1c>] :ohci_hcd:ohci_hcd_pci_cleanup+0x10/0x12
> [<ffffffff8029b281>] sys_delete_module+0x1b5/0x1e6
> [<ffffffff8025910e>] system_call+0x7e/0x83
>
>
> Code: 8a 98 74 02 00 00 e8 d6 3b 03 f8 48 89 45 d0 41 8b 84 24 e4
> RIP [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
> RSP <ffffffff805c7e18>
> CR2: 0000000000000274
> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>
> where
>
> (gdb) l *ohci_hub_status_data+0x25
> 0x4185 is in ohci_hub_status_data (drivers/usb/host/ohci-hub.c:316).
> 311 struct ohci_hcd *ohci = hcd_to_ohci (hcd);
> 312 int i, changed = 0, length = 1;
> 313 int can_suspend;
> 314 unsigned long flags;
> 315
> 316 can_suspend = device_may_wakeup(&hcd->self.root_hub->dev);
> 317 spin_lock_irqsave (&ohci->lock, flags);
> 318
> 319 /* handle autosuspended root: finish resuming before
> 320 * letting khubd or root hub timer see state changes.
>
> I guess it may be related to the suspend issues?
No, this is completely separate. The suspend issue involved ehci-hcd, not
ohci-hcd.
This problem has already been identified by Pete Zaitcev in this thread:
http://marc.theaimsgroup.com/?t=115769512800001&r=1&w=2
Perhaps Pete has an updated patch to fix the problem. If not, I could
write one.
Alan Stern
On Wednesday, 13 September 2006 20:44, Alan Stern wrote:
> On Wed, 13 Sep 2006, Rafael J. Wysocki wrote:
>
> > 'rmmod ohci_hcd' causes the following oops to appear on my HPC 6325 every
> > time (happens also on -rc6-mm1, does not happen on -rc7):
> >
> > Unable to handle kernel NULL pointer dereference at 0000000000000274 RIP:
> > [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
> > PGD 35ca9067 PUD 369a4067 PMD 0
>
> > Call Trace:
> > [<ffffffff8818e03f>] :usbcore:usb_hcd_poll_rh_status+0x40/0x13b
> > [<ffffffff8822c01b>] :ohci_hcd:ohci_irq+0xcb/0x210
> > [<ffffffff8818e78b>] :usbcore:usb_hcd_irq+0x2f/0x5f
> > [<ffffffff8020ef13>] handle_IRQ_event+0x33/0x66
> > [<ffffffff802af5f8>] handle_fasteoi_irq+0x9d/0xe3
> > [<ffffffff80267c85>] do_IRQ+0x104/0x11f
> > [<ffffffff80259621>] ret_from_intr+0x0/0xa
> > DWARF2 unwinder stuck at ret_from_intr+0x0/0xa
> >
> > Leftover inexact backtrace:
> >
> > <IRQ> <EOI> [<ffffffff802ee4ac>] sysfs_hash_and_remove+0x9/0x137
> > [<ffffffff802eed13>] sysfs_remove_file+0x10/0x12
> > [<ffffffff8038baf7>] class_device_remove_file+0x12/0x14
> > [<ffffffff8822aa02>] :ohci_hcd:ohci_stop+0xf5/0x17b
> > [<ffffffff8818d9d2>] :usbcore:usb_remove_hcd+0xdc/0x114
> > [<ffffffff8040f8eb>] klist_release+0x0/0x82
> > [<ffffffff88197f45>] :usbcore:usb_hcd_pci_remove+0x1e/0x7d
> > [<ffffffff803204d8>] pci_device_remove+0x25/0x3c
> > [<ffffffff8038b1b5>] __device_release_driver+0x80/0x9c
> > [<ffffffff8038b617>] driver_detach+0xac/0xee
> > [<ffffffff8038ad92>] bus_remove_driver+0x75/0x98
> > [<ffffffff8038b696>] driver_unregister+0x15/0x21
> > [<ffffffff80320686>] pci_unregister_driver+0x13/0x8e
> > [<ffffffff8822cd1c>] :ohci_hcd:ohci_hcd_pci_cleanup+0x10/0x12
> > [<ffffffff8029b281>] sys_delete_module+0x1b5/0x1e6
> > [<ffffffff8025910e>] system_call+0x7e/0x83
> >
> >
> > Code: 8a 98 74 02 00 00 e8 d6 3b 03 f8 48 89 45 d0 41 8b 84 24 e4
> > RIP [<ffffffff8822c185>] :ohci_hcd:ohci_hub_status_data+0x25/0x27b
> > RSP <ffffffff805c7e18>
> > CR2: 0000000000000274
> > <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
> >
> > where
> >
> > (gdb) l *ohci_hub_status_data+0x25
> > 0x4185 is in ohci_hub_status_data (drivers/usb/host/ohci-hub.c:316).
> > 311 struct ohci_hcd *ohci = hcd_to_ohci (hcd);
> > 312 int i, changed = 0, length = 1;
> > 313 int can_suspend;
> > 314 unsigned long flags;
> > 315
> > 316 can_suspend = device_may_wakeup(&hcd->self.root_hub->dev);
> > 317 spin_lock_irqsave (&ohci->lock, flags);
> > 318
> > 319 /* handle autosuspended root: finish resuming before
> > 320 * letting khubd or root hub timer see state changes.
> >
> > I guess it may be related to the suspend issues?
>
> No, this is completely separate. The suspend issue involved ehci-hcd, not
> ohci-hcd.
Well, on my box it's ohci-hcd too.
> This problem has already been identified by Pete Zaitcev in this thread:
>
> http://marc.theaimsgroup.com/?t=115769512800001&r=1&w=2
Ah, thanks.
> Perhaps Pete has an updated patch to fix the problem. If not, I could
> write one.
For now I can use the original Pete's patch, but it would be nice to have a
fix in -mm. ;-)
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Wed, 13 Sep 2006 14:44:48 -0400 (EDT), Alan Stern <[email protected]> wrote:
> This problem has already been identified by Pete Zaitcev in this thread:
>
> http://marc.theaimsgroup.com/?t=115769512800001&r=1&w=2
>
> Perhaps Pete has an updated patch to fix the problem. If not, I could
> write one.
No, not yet. I am working on getting David's approach with irq = -1
tested at Stratus. Since it was the only reproducer known to me, I wanted
to test. Now that Rafael has a fault case, I'll expedite.
-- Pete
On Wed, Sep 13, 2006 at 11:43:32AM +0200, Michal Piotrowski wrote:
> On 13/09/06, David Chinner <[email protected]> wrote:
> >
> >I've booted 2.6.18-rc6-mm2 and mounted and unmounted several xfs
> >filesystems. I'm currently running xfsqa on it, and I haven't seen
> >any failures on unmount yet.
> >
> >That test case would be really handy, Michal.
>
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/test_mount_fs.sh
>
> ls -hs /home/fs-farm/
> total 3.6G
> 513M ext2.img 513M ext4.img 513M reiser3.img 513M xfs.img
> 513M ext3.img 513M jfs.img 513M reiser4.img
Ok, so you're using loopback and mounting one of each filesystem, then
unmounting them in the same order. I have mounted and unmounted an
XFS filesystem in isolation in exactly the same way you have been, but
I haven't seen any failures.
Can you rerun the test with just XFS in your script and see if you
see any failures? If you don't see any failures, can you add each
filesystem back in one at a time until you see failures again?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
Seeing a problem with suspend-to-RAM or suspend-to-disk on my laptop. If
I suspend (either way) once it is fine. If I suspend again the EHCI
controller fails to suspend and the suspend is aborted.
Here is the dmesg from one suspend to RAM (successful) and then suspend
to disk (failed):
Linux version 2.6.18-rc6-mm2 ([email protected]) (gcc version
4.1.1 20060525 (Red Hat 4.1.1-1)) #1 Wed Sep 13 22:34:20 CST 2006
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end:
000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end:
00000000000a0000 type: 2
copy_e820_map() start: 00000000000e0000 size: 0000000000020000 end:
0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000001fed0000 end:
000000001ffd0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000001ffd0000 size: 0000000000020c00 end:
000000001fff0c00 type: 2
copy_e820_map() start: 000000001fff0c00 size: 000000000000b400 end:
000000001fffc000 type: 4
copy_e820_map() start: 000000001fffc000 size: 0000000000004000 end:
0000000020000000 type: 2
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001ffd0000 (usable)
BIOS-e820: 000000001ffd0000 - 000000001fff0c00 (reserved)
BIOS-e820: 000000001fff0c00 - 000000001fffc000 (ACPI NVS)
BIOS-e820: 000000001fffc000 - 0000000020000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
Entering add_active_range(0, 0, 131024) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 131024
HighMem 131024 -> 131024
early_node_map[1] active PFN ranges
0: 0 -> 131024
On node 0 totalpages: 131024
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 991 pages used for memmap
Normal zone: 125937 pages, LIFO batch:31
HighMem zone: 0 pages used for memmap
DMI 2.3 present.
ACPI: RSDP (v000 COMPAQ ) @ 0x000f6560
ACPI: RSDT (v001 HP CPQ0860 0x14070520 CPQ 0x00000001) @ 0x1fff0c84
ACPI: FADT (v002 HP CPQ0860 0x00000002 CPQ 0x00000001) @ 0x1fff0c00
ACPI: SSDT (v001 COMPAQ CPQGysr 0x00001001 MSFT 0x0100000e) @ 0x1fff5c3c
ACPI: DSDT (v001 HP nx7000 0x00010000 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x1008
Allocating PCI resources starting at 30000000 (gap: 20000000:e0000000)
Detected 1694.559 MHz processor.
Built 1 zonelists. Total pages: 130001
Kernel command line: ro root=/dev/VolGroup00/LogVol00
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01404000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
cpu 0 current c0369480
Initializing CPU#0
CPU 0 irqstacks, hard=c0462000 soft=c0461000
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 513424k/524096k available (2036k kernel code, 10076k reserved,
822k data, 228k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfff9c000 - 0xfffff000 ( 396 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xe0800000 - 0xff7fe000 ( 495 MB)
lowmem : 0xc0000000 - 0xdffd0000 ( 511 MB)
.init : 0xc0423000 - 0xc045c000 ( 228 kB)
.data : 0xc02fd14d - 0xc03cab14 ( 822 kB)
.text : 0xc0100000 - 0xc02fd14d (2036 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3390.77 BogoMIPS
(lpj=16953877)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: afe9f9bf 00000000 00000000 00000000
00000180 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: After all inits, caps: afe9f9bf 00000000 00000000 00000040 00000180
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) M processor 1.70GHz stepping 06
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0c20)
checking if image is initramfs... it is
Freeing initrd memory: 1669k freed
PM: Adding info for No Bus:platform
NET: Registered protocol family 16
PM: Adding info for No Bus:virtual
PM: Adding info for No Bus:vtconsole
PM: Adding info for No Bus:vtcon0
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf031f, last bus=3
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
PM: Adding info for acpi:acpi
ACPI: PCI Root Bridge [C046] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.C046] bus is 0
PM: Adding info for No Bus:pci0000:00
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1100-113f claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#03) (try
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.C046._PRT]
PM: Adding info for pci:0000:00:00.0
PM: Adding info for pci:0000:00:01.0
PM: Adding info for pci:0000:00:1d.0
PM: Adding info for pci:0000:00:1d.1
PM: Adding info for pci:0000:00:1d.2
PM: Adding info for pci:0000:00:1d.7
PM: Adding info for pci:0000:00:1e.0
PM: Adding info for pci:0000:00:1f.0
PM: Adding info for pci:0000:00:1f.1
PM: Adding info for pci:0000:00:1f.3
PM: Adding info for pci:0000:00:1f.5
PM: Adding info for pci:0000:00:1f.6
PM: Adding info for pci:0000:01:00.0
PM: Adding info for pci:0000:02:00.0
PM: Adding info for pci:0000:02:01.0
PM: Adding info for pci:0000:02:02.0
PM: Adding info for pci:0000:02:04.0
ACPI: PCI Interrupt Routing Table [\_SB_.C046.C047._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.C046.C058._PRT]
ACPI: Embedded Controller [C0EA] (gpe 28) interrupt mode.
ACPI: Power Resource [C18D] (on)
ACPI: Power Resource [C195] (on)
ACPI: Power Resource [C19C] (on)
ACPI: Power Resource [C1A6] (on)
ACPI: PCI Interrupt Link [C0C2] (IRQs 5 *10)
ACPI: PCI Interrupt Link [C0C3] (IRQs 5 *10)
ACPI: PCI Interrupt Link [C0C4] (IRQs *5 10)
ACPI: PCI Interrupt Link [C0C5] (IRQs *5 10)
ACPI: PCI Interrupt Link [C0C6] (IRQs 5 10) *0, disabled.
ACPI: PCI Interrupt Link [C0C7] (IRQs 5 10) *11
ACPI: PCI Interrupt Link [C0C8] (IRQs 5 10) *0, disabled.
ACPI: PCI Interrupt Link [C0C9] (IRQs *5 10)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
PM: Adding info for No Bus:pnp0
PM: Adding info for pnp:00:00
PM: Adding info for pnp:00:01
PM: Adding info for pnp:00:02
PM: Adding info for pnp:00:03
PM: Adding info for pnp:00:04
PM: Adding info for pnp:00:05
PM: Adding info for pnp:00:06
PM: Adding info for pnp:00:07
PM: Adding info for pnp:00:08
PM: Adding info for pnp:00:09
PM: Adding info for pnp:00:0a
PM: Adding info for pnp:00:0b
PM: Adding info for pnp:00:0c
PM: Adding info for pnp:00:0d
PM: Adding info for pnp:00:0e
pnp: PnP ACPI: found 15 devices
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
pnp: 00:0d: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:0d: ioport range 0x1000-0x107f could not be reserved
pnp: 00:0d: ioport range 0x1100-0x113f has been reserved
pnp: 00:0d: ioport range 0x1200-0x121f has been reserved
PCI: Bridge: 0000:00:01.0
IO window: 3000-3fff
MEM window: 90400000-904fffff
PREFETCH window: 98000000-9fffffff
PCI: Bus 3, cardbus bridge: 0000:02:04.0
IO window: 00002800-000028ff
IO window: 00002c00-00002cff
PREFETCH window: 30000000-31ffffff
MEM window: 34000000-35ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 2000-2fff
MEM window: 90000000-903fffff
PREFETCH window: 30000000-31ffffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI: PCI Interrupt Link [C0C4] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [C0C4] -> GSI 5 (level, low)
-> IRQ 5
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
PM: Adding info for platform:pcspkr
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
PM: Adding info for No Bus:misc
PM: Adding info for No Bus:snapshot
audit: initializing netlink socket (disabled)
audit(1158188552.800:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
PM: Adding info for platform:vesafb.0
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
PM: Adding info for No Bus:pnp1
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PM: Adding info for No Bus:vc
PM: Adding info for No Bus:vcs
PM: Adding info for No Bus:vcsa
PM: Adding info for No Bus:rtc
Real Time Clock Driver v1.12ac
PM: Adding info for No Bus:hpet
PM: Adding info for No Bus:nvram
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 855PM Chipset.
PM: Adding info for No Bus:agpgart
agpgart: AGP aperture is 256M @ 0xb0000000
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
PM: Adding info for platform:serial8250
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS2 at I/O 0x3e8 (irq = 3) is a 16550A
00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt Link [C0C3] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PM: Adding info for No Bus:isa
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
libata version 2.00 loaded.
ata_piix 0000:00:1f.1: version 2.00ac7
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [C0C4] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1f.1 to 64
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x4C40 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x4C48 irq 15
scsi0 : ata_piix
PM: Adding info for No Bus:host0
ata1.00: ATA-7, max UDMA/100, 156368016 sectors: LBA48
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : ata_piix
PM: Adding info for No Bus:host1
ata2.00: ATAPI, max UDMA/33
ata2.00: configured for UDMA/33
PM: Adding info for No Bus:target0:0:0
scsi 0:0:0:0: Direct-Access ATA SAMSUNG MP0804H UE20 PQ: 0 ANSI: 5
PM: Adding info for scsi:0:0:0:0
SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda
PM: Adding info for No Bus:target1:0:0
scsi 1:0:0:0: CD-ROM QSI CDRW/DVD SBW-241 VH04 PQ: 0 ANSI: 5
PM: Adding info for scsi:1:0:0:0
sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
Yenta: CardBus bridge found at 0000:02:04.0 [0e11:0860]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:04.0, mfunc 0x001c1112, devctl 0x44
Yenta: ISA IRQ mask 0x08d8, PCI irq 5
Socket status: 30000006
Yenta: Raising subordinate bus# of parent bus (#02) from #03 to #06
pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff
cs: IO port probe 0x2000-0x2fff: clean.
pcmcia: parent PCI bridge Memory window: 0x90000000 - 0x903fffff
pcmcia: parent PCI bridge Memory window: 0x30000000 - 0x31ffffff
usbcore: registered new interface driver libusual
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:C1A3,PNP0f13:C1A4] at 0x60,0x64 irq 1,12
PM: Adding info for platform:i8042
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
PM: Adding info for serio:serio0
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
PM: Adding info for serio:serio1
PM: Adding info for serio:serio2
Using IPI Shortcut mode
PM: Adding info for serio:serio3
ACPI: (supports S0 S3 S4 S5)
Freeing unused kernel memory: 228k freed
Write protecting the kernel read-only data: 422k
Time: tsc clocksource has been installed.
PM: Adding info for No Bus:vcs1
PM: Adding info for serio:serio4
PM: Adding info for No Bus:vcsa1
Time: acpi_pm clocksource has been installed.
input: AT Translated Set 2 keyboard as /class/input/input0
PM: Adding info for No Bus:device-mapper
device-mapper: ioctl: 4.8.0-ioctl (2006-06-24) initialised:
[email protected]
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x236eb3, caps: 0x904713/0x10008
input: SynPS/2 Synaptics TouchPad as /class/input/input1
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
audit(1158188556.189:2): enforcing=1 old_enforcing=0 auid=4294967295
security: 3 users, 6 roles, 1481 types, 152 bools, 1 sens, 256 cats
security: 58 classes, 43474 rules
SELinux: Completing initialization.
SELinux: Setting up existing superblocks.
SELinux: initialized (dev dm-0, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses task SIDs
SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
audit(1158188556.529:3): policy loaded auid=4294967295
PM: Removing info for No Bus:vcs1
PM: Removing info for No Bus:vcsa1
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
warning: process `date' used the removed sysctl system call
warning: process `touch' used the removed sysctl system call
input: PC Speaker as /class/input/input2
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.00 (30-Jul-2006)
PM: Adding info for platform:iTCO_wdt
iTCO_wdt: Found a ICH4-M TCO device (Version=1, TCOBASE=0x1060)
PM: Adding info for No Bus:watchdog
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PM: Adding info for No Bus:i2c-0
Floppy drive(s): fd0 is 1.44M
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
eth0: RTL-8139C+ at 0xe08ec000, 00:02:3f:65:4d:74, IRQ 10
intel_rng: FWH not detected
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<[email protected]>
ACPI: PCI Interrupt Link [C0C9] enabled at IRQ 5
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [C0C9] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 5, io mem 0xa0000000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.18-rc6-mm2 ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
PM: Adding info for usb:usb1
PM: Adding info for No Bus:usbdev1.1_ep00
usb usb1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-0:1.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
USB Universal Host Controller Interface driver v3.0
PM: Adding info for No Bus:usbdev1.1_ep81
PM: Adding info for No Bus:usbdev1.1
ACPI: PCI Interrupt Link [C0C2] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [C0C2] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 10, io base 0x000048c0
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.18-rc6-mm2 uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
PM: Adding info for usb:usb2
PM: Adding info for No Bus:usbdev2.1_ep00
usb usb2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-0:1.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ieee1394: Initialized config rom entry `ip1394'
PM: Adding info for No Bus:usbdev2.1_ep81
PM: Adding info for No Bus:usbdev2.1
ACPI: PCI Interrupt Link [C0C5] enabled at IRQ 5
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [C0C5] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 5, io base 0x000048e0
usb usb3: new device found, idVendor=0000, idProduct=0000
usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.18-rc6-mm2 uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
PM: Adding info for usb:usb3
PM: Adding info for No Bus:usbdev3.1_ep00
usb usb3: configuration #1 chosen from 1 choice
PM: Adding info for usb:3-0:1.0
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.4kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
PM: Adding info for No Bus:usbdev3.1_ep81
PM: Adding info for No Bus:usbdev3.1
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [C0C4] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 5, io base 0x00004c00
usb usb4: new device found, idVendor=0000, idProduct=0000
usb usb4: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.18-rc6-mm2 uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
PM: Adding info for usb:usb4
PM: Adding info for No Bus:usbdev4.1_ep00
usb usb4: configuration #1 chosen from 1 choice
PM: Adding info for usb:4-0:1.0
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
cs: IO port probe 0x100-0x3af: excluding 0x140-0x14f 0x200-0x20f 0x370-0x37f
cs: IO port probe 0x3e0-0x4ff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
PM: Adding info for No Bus:usbdev4.1_ep81
PM: Adding info for No Bus:usbdev4.1
ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [C0C5] -> GSI 5 (level, low)
-> IRQ 5
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 1:0:0:0: Attached scsi generic sg1 type 5
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [C0C2] -> GSI 10 (level,
low) -> IRQ 10
PM: Adding info for ieee1394:fw-host0
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10]
MMIO=[90200000-902007ff] Max Packet=[2048] IR/IT contexts=[4/8]
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
intel8x0_measure_ac97_clock: measured 59429 usecs
intel8x0: clocking to 48000
PM: Adding info for ac97:0-0:AD1981B
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.6 to 64
PM: Adding info for ac97:1-1:Si3036,8
PM: Adding info for ieee1394:00023f383800c298
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f383800c298]
PM: Adding info for ieee1394:00023f383800c298-0
floppy0: no floppy controllers found
warning: process `salsa' used the removed sysctl system call
warning: process `salsa' used the removed sysctl system call
warning: process `salsa' used the removed sysctl system call
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
lp0: console ready
ACPI: AC Adapter [C134] (on-line)
ACPI: Battery Slot [C11F] (battery present)
bay: Unknown symbol is_dock_device
bay: Unknown symbol register_hotplug_dock_device
bay: Unknown symbol unregister_hotplug_dock_device
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [C1BE]
ACPI: Lid Switch [C136]
ibm_acpi: ec object not found
ACPI: Video Device [C0D0] (multi-head: yes rom: no post: no)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev sda2, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
NTFS driver 2.1.27 [Flags: R/W MODULE].
NTFS volume version 3.1.
NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
flags 0x4000 encountered.
NTFS-fs error (device sda1): load_system_files(): Volume has unsupported
flags set. Mounting read-only. Run chkdsk and mount in Windows.
SELinux: initialized (dev sda1, type ntfs), uses genfs_contexts
Adding 1048568k swap on /dev/VolGroup00/LogVol01. Priority:-1 extents:1
across:1048568k
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses
genfs_contexts
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (4094 buckets, 32752 max) - 224 bytes per conntrack
eth0: link down
Bluetooth: Core ver 2.10
PM: Adding info for platform:bluetooth
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
wbsd: Winbond W83L51xD SD/MMC card interface driver, 1.6
wbsd: Copyright(c) Pierre Ossman
pnp: Device 00:02 activated.
mmc0: W83L51xD id 7112 at 0x248 irq 6 dma 0 PnP
PM: Adding info for No Bus:vcs2
PM: Adding info for No Bus:vcsa2
PM: Removing info for No Bus:vcs2
PM: Removing info for No Bus:vcsa2
PM: Adding info for No Bus:vcs3
PM: Adding info for No Bus:vcsa3
PM: Removing info for No Bus:vcs3
PM: Removing info for No Bus:vcsa3
PM: Adding info for No Bus:vcs4
PM: Adding info for No Bus:vcsa4
PM: Removing info for No Bus:vcs4
PM: Removing info for No Bus:vcsa4
PM: Adding info for No Bus:vcs5
PM: Adding info for No Bus:vcsa5
PM: Removing info for No Bus:vcs5
PM: Removing info for No Bus:vcsa5
PM: Adding info for No Bus:vcs6
PM: Adding info for No Bus:vcsa6
PM: Removing info for No Bus:vcs6
PM: Removing info for No Bus:vcsa6
PM: Adding info for No Bus:vcs7
PM: Adding info for No Bus:vcsa7
PM: Removing info for No Bus:vcs7
PM: Removing info for No Bus:vcsa7
[drm] Initialized drm 1.0.1 20051102
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0C2] -> GSI 10 (level,
low) -> IRQ 10
[drm] Initialized radeon 1.25.0 20060524 on minor 0
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Setting GART location based on new memory map
[drm] Loading R200 Microcode
[drm] writeback test succeeded in 1 usecs
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
ieee80211_crypt: registered algorithm 'CCMP'
eth1: no IPv6 routers present
ADDRCONF(NETDEV_UP): eth1: link is not ready
PM: Preparing system for mem sleep
Stopping tasks:
====================================================================================================|
Suspending device bluetooth
platform bluetooth: suspend
Suspending device 00023f383800c298-0
Suspending device 00023f383800c298
Suspending device 1-1:Si3036,8
ac97 1-1:Si3036,8: suspend
Suspending device 0-0:AD1981B
ac97 0-0:AD1981B: suspend
Suspending device fw-host0
Suspending device usbdev4.1
Suspending device usbdev4.1_ep81
Suspending device 4-0:1.0
hub 4-0:1.0: suspend
Suspending device usbdev4.1_ep00
Suspending device usb4
usb usb4: suspend, may wakeup
Suspending device usbdev3.1
Suspending device usbdev3.1_ep81
Suspending device 3-0:1.0
hub 3-0:1.0: suspend
Suspending device usbdev3.1_ep00
Suspending device usb3
usb usb3: suspend, may wakeup
Suspending device usbdev2.1
Suspending device usbdev2.1_ep81
Suspending device 2-0:1.0
hub 2-0:1.0: suspend
Suspending device usbdev2.1_ep00
Suspending device usb2
usb usb2: suspend, may wakeup
Suspending device usbdev1.1
Suspending device usbdev1.1_ep81
Suspending device 1-0:1.0
hub 1-0:1.0: suspend
Suspending device usbdev1.1_ep00
Suspending device usb1
usb usb1: suspend, may wakeup
Suspending device i2c-0
Suspending device watchdog
Suspending device iTCO_wdt
iTCO_wdt iTCO_wdt: suspend
Suspending device device-mapper
Suspending device serio4
Suspending device serio3
Suspending device serio2
Suspending device serio1
Suspending device serio0
Suspending device i8042
i8042 i8042: suspend
Suspending device 1:0:0:0
sr 1:0:0:0: suspend
Suspending device target1:0:0
Suspending device 0:0:0:0
sd 0:0:0:0: suspend
Suspending device target0:0:0
Suspending device host1
Suspending device host0
Suspending device isa
Suspending device serial8250
serial8250 serial8250: suspend
Suspending device agpgart
Suspending device nvram
Suspending device hpet
Suspending device rtc
Suspending device vcsa
Suspending device vcs
Suspending device vc
Suspending device pnp1
Suspending device vesafb.0
platform vesafb.0: suspend
Suspending device snapshot
Suspending device misc
Suspending device pcspkr
pcspkr pcspkr: suspend
Suspending device 00:0e
system 00:0e: suspend
Suspending device 00:0d
system 00:0d: suspend
Suspending device 00:0c
system 00:0c: suspend
Suspending device 00:0b
i8042 aux 00:0b: suspend
Suspending device 00:0a
i8042 kbd 00:0a: suspend
Suspending device 00:09
pnp 00:09: suspend
Suspending device 00:08
pnp 00:08: suspend
Suspending device 00:07
pnp 00:07: suspend
Suspending device 00:06
pnp 00:06: suspend
Suspending device 00:05
parport_pc 00:05: suspend
pnp: Device 00:05 disabled.
Suspending device 00:04
pnp 00:04: suspend
Suspending device 00:03
serial 00:03: suspend
pnp: Device 00:03 disabled.
Suspending device 00:02
wbsd 00:02: suspend
pnp: Device 00:02 disabled.
Suspending device 00:01
pnp 00:01: suspend
Suspending device 00:00
system 00:00: suspend
Suspending device pnp0
Suspending device 0000:02:04.0
yenta_cardbus 0000:02:04.0: suspend
Suspending device 0000:02:02.0
ipw2200 0000:02:02.0: suspend
eth1: Going into suspend...
Suspending device 0000:02:01.0
8139cp 0000:02:01.0: suspend
Suspending device 0000:02:00.0
ohci1394 0000:02:00.0: suspend
Suspending device 0000:01:00.0
pci 0000:01:00.0: suspend
Suspending device 0000:00:1f.6
Intel ICH Modem 0000:00:1f.6: suspend
Suspending device 0000:00:1f.5
Intel ICH 0000:00:1f.5: suspend
codec_write 0: semaphore is not ready for register 0x26
Suspending device 0000:00:1f.3
i801_smbus 0000:00:1f.3: suspend
Suspending device 0000:00:1f.1
ata_piix 0000:00:1f.1: suspend
pci_set_power_state(): 0000:00:1f.1: state=3, current state=5
Suspending device 0000:00:1f.0
pci 0000:00:1f.0: suspend
Suspending device 0000:00:1e.0
pci 0000:00:1e.0: suspend
Suspending device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: suspend, may wakeup
Suspending device 0000:00:1d.2
uhci_hcd 0000:00:1d.2: suspend
Suspending device 0000:00:1d.1
uhci_hcd 0000:00:1d.1: suspend
Suspending device 0000:00:1d.0
uhci_hcd 0000:00:1d.0: suspend
Suspending device 0000:00:01.0
pci 0000:00:01.0: suspend
Suspending device 0000:00:00.0
agpgart-intel 0000:00:00.0: suspend
Suspending device pci0000:00
Suspending device acpi
acpi acpi: suspend
Suspending device vtcon0
Suspending device vtconsole
Suspending device virtual
Suspending device platform
PM: Entering mem sleep
platform bluetooth: LATE suspend
iTCO_wdt iTCO_wdt: LATE suspend
i8042 i8042: LATE suspend
serial8250 serial8250: LATE suspend
platform vesafb.0: LATE suspend
pcspkr pcspkr: LATE suspend
yenta_cardbus 0000:02:04.0: LATE suspend
ipw2200 0000:02:02.0: LATE suspend
8139cp 0000:02:01.0: LATE suspend
ohci1394 0000:02:00.0: LATE suspend
pci 0000:01:00.0: LATE suspend
Intel ICH Modem 0000:00:1f.6: LATE suspend
Intel ICH 0000:00:1f.5: LATE suspend
i801_smbus 0000:00:1f.3: LATE suspend
pci 0000:00:1f.0: LATE suspend
pci 0000:00:1e.0: LATE suspend
pci 0000:00:01.0: LATE suspend
agpgart-intel 0000:00:00.0: LATE suspend
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Back to C!
agpgart-intel 0000:00:00.0: EARLY resume
pci 0000:00:01.0: EARLY resume
uhci_hcd 0000:00:1d.0: EARLY resume
uhci_hcd 0000:00:1d.1: EARLY resume
uhci_hcd 0000:00:1d.2: EARLY resume
ehci_hcd 0000:00:1d.7: EARLY resume
pci 0000:00:1e.0: EARLY resume
pci 0000:00:1f.0: EARLY resume
ata_piix 0000:00:1f.1: EARLY resume
i801_smbus 0000:00:1f.3: EARLY resume
Intel ICH 0000:00:1f.5: EARLY resume
Intel ICH Modem 0000:00:1f.6: EARLY resume
pci 0000:01:00.0: EARLY resume
ohci1394 0000:02:00.0: EARLY resume
8139cp 0000:02:01.0: EARLY resume
ipw2200 0000:02:02.0: EARLY resume
yenta_cardbus 0000:02:04.0: EARLY resume
pcspkr pcspkr: EARLY resume
platform vesafb.0: EARLY resume
serial8250 serial8250: EARLY resume
i8042 i8042: EARLY resume
iTCO_wdt iTCO_wdt: EARLY resume
platform bluetooth: EARLY resume
PM: Finishing wakeup.
acpi acpi: resuming
agpgart-intel 0000:00:00.0: resuming
pci 0000:00:01.0: resuming
uhci_hcd 0000:00:1d.0: resuming
PCI: Enabling device 0000:00:1d.0 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [C0C2] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PM: Writing back config space on device 0000:00:1d.0 at offset f (was
100, writing 10a)
PM: Writing back config space on device 0000:00:1d.0 at offset 8 (was 1,
writing 48c1)
usb usb2: root hub lost power or was reset
uhci_hcd 0000:00:1d.1: resuming
PCI: Enabling device 0000:00:1d.1 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [C0C5] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.1 to 64
PM: Writing back config space on device 0000:00:1d.1 at offset f (was
200, writing 205)
PM: Writing back config space on device 0000:00:1d.1 at offset 8 (was 1,
writing 48e1)
usb usb3: root hub lost power or was reset
uhci_hcd 0000:00:1d.2: resuming
PCI: Enabling device 0000:00:1d.2 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [C0C4] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.2 to 64
PM: Writing back config space on device 0000:00:1d.2 at offset f (was
300, writing 305)
PM: Writing back config space on device 0000:00:1d.2 at offset 8 (was 1,
writing 4c01)
usb usb4: root hub lost power or was reset
ehci_hcd 0000:00:1d.7: resuming
PCI: Enabling device 0000:00:1d.7 (0000 -> 0002)
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [C0C9] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.7 to 64
PM: Writing back config space on device 0000:00:1d.7 at offset f (was
400, writing 405)
PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0,
writing a0000000)
usb usb1: root hub lost power or was reset
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
pci 0000:00:1e.0: resuming
PM: Writing back config space on device 0000:00:1e.0 at offset 9 (was
fff0, writing 31f03000)
PM: Writing back config space on device 0000:00:1e.0 at offset 7 (was
22802020, writing 2802020)
PCI: Setting latency timer of device 0000:00:1e.0 to 64
pci 0000:00:1f.0: resuming
ata_piix 0000:00:1f.1: resuming
PM: Writing back config space on device 0000:00:1f.1 at offset f (was
100, writing 105)
PM: Writing back config space on device 0000:00:1f.1 at offset 9 (was 0,
writing 32000000)
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [C0C4] -> GSI 5 (level, low)
-> IRQ 5
PCI: Setting latency timer of device 0000:00:1f.1 to 64
i801_smbus 0000:00:1f.3: resuming
Intel ICH 0000:00:1f.5: resuming
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
Intel ICH Modem 0000:00:1f.6: resuming
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.6 to 64
pci 0000:01:00.0: resuming
PM: Writing back config space on device 0000:01:00.0 at offset 6 (was 0,
writing 90400000)
PM: Writing back config space on device 0000:01:00.0 at offset 3 (was 0,
writing 8008)
ohci1394 0000:02:00.0: resuming
PM: Writing back config space on device 0000:02:00.0 at offset f (was
20000100, writing 2000010a)
PM: Writing back config space on device 0000:02:00.0 at offset 5 (was 1,
writing 2401)
PM: Writing back config space on device 0000:02:00.0 at offset 4 (was 0,
writing 90200000)
PM: Writing back config space on device 0000:02:00.0 at offset 3 (was 0,
writing 8008)
PM: Writing back config space on device 0000:02:00.0 at offset 1 (was
2100080, writing 2100007)
8139cp 0000:02:01.0: resuming
ipw2200 0000:02:02.0: resuming
eth1: Coming out of suspend...
PCI: Enabling device 0000:02:02.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [C0C5] -> GSI 5 (level, low)
-> IRQ 5
PM: Writing back config space on device 0000:02:02.0 at offset f (was
18030100, writing 1803010b)
PM: Writing back config space on device 0000:02:02.0 at offset 4 (was 0,
writing 90000000)
PM: Writing back config space on device 0000:02:02.0 at offset 3 (was 0,
writing 8008)
PM: Writing back config space on device 0000:02:02.0 at offset 1 (was
2900002, writing 2900006)
yenta_cardbus 0000:02:04.0: resuming
PM: Writing back config space on device 0000:02:04.0 at offset f (was
34001ff, writing 5c00105)
PM: Writing back config space on device 0000:02:04.0 at offset e (was 0,
writing 2cfc)
PM: Writing back config space on device 0000:02:04.0 at offset d (was 0,
writing 2c00)
PM: Writing back config space on device 0000:02:04.0 at offset c (was 0,
writing 28fc)
PM: Writing back config space on device 0000:02:04.0 at offset b (was 0,
writing 2800)
PM: Writing back config space on device 0000:02:04.0 at offset a (was 0,
writing 35fff000)
PM: Writing back config space on device 0000:02:04.0 at offset 9 (was 0,
writing 34000000)
PM: Writing back config space on device 0000:02:04.0 at offset 8 (was 0,
writing 31fff000)
PM: Writing back config space on device 0000:02:04.0 at offset 7 (was 0,
writing 30000000)
PM: Writing back config space on device 0000:02:04.0 at offset 6 (was 0,
writing b0060302)
PM: Writing back config space on device 0000:02:04.0 at offset 4 (was 0,
writing 90100000)
PM: Writing back config space on device 0000:02:04.0 at offset 3 (was
20000, writing 2a820)
PM: Writing back config space on device 0000:02:04.0 at offset 1 (was
2100000, writing 2100007)
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [C0C4] -> GSI 5 (level, low)
-> IRQ 5
system 00:00: resuming
pnp 00:01: resuming
wbsd 00:02: resuming
pnp: Device 00:02 activated.
serial 00:03: resuming
pnp: Device 00:03 activated.
pnp 00:04: resuming
parport_pc 00:05: resuming
pnp: Device 00:05 activated.
pnp 00:06: resuming
pnp 00:07: resuming
pnp 00:08: resuming
pnp 00:09: resuming
i8042 kbd 00:0a: resuming
pnp: Device 00:0a does not support activation.
i8042 aux 00:0b: resuming
pnp: Device 00:0b does not support activation.
system 00:0c: resuming
system 00:0d: resuming
system 00:0e: resuming
pcspkr pcspkr: resuming
platform vesafb.0: resuming
serial8250 serial8250: resuming
sd 0:0:0:0: resuming
sr 1:0:0:0: resuming
ata2: soft resetting port
i8042 i8042: resuming
atkbd serio0: resuming
serio serio1: resuming
serio serio2: resuming
serio serio3: resuming
psmouse serio4: resuming
ata2.00: configured for UDMA/33
ata2: EH complete
iTCO_wdt iTCO_wdt: resuming
usb usb1: resuming
usbdev1.1_ep00: PM: resume from 0, parent usb1 still 2
hub 1-0:1.0: PM: resume from 0, parent usb1 still 2
hub 1-0:1.0: resuming
usbdev1.1: PM: resume from 0, parent usb1 still 2
usb usb2: resuming
ata1: EH pending after completion, repeating EH (cnt=4)
ata1: soft resetting port
usbdev2.1_ep00: PM: resume from 0, parent usb2 still 2
hub 2-0:1.0: PM: resume from 0, parent usb2 still 2
hub 2-0:1.0: resuming
usbdev2.1: PM: resume from 0, parent usb2 still 2
usb usb3: resuming
usbdev3.1_ep00: PM: resume from 0, parent usb3 still 2
hub 3-0:1.0: PM: resume from 0, parent usb3 still 2
hub 3-0:1.0: resuming
usbdev3.1: PM: resume from 0, parent usb3 still 2
usb usb4: resuming
usbdev4.1_ep00: PM: resume from 0, parent usb4 still 2
hub 4-0:1.0: PM: resume from 0, parent usb4 still 2
hub 4-0:1.0: resuming
usbdev4.1: PM: resume from 0, parent usb4 still 2
ac97 0-0:AD1981B: resuming
ac97 1-1:Si3036,8: resuming
platform bluetooth: resuming
Restarting tasks... done
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [C1BE]
ACPI: Lid Switch [C136]
PM: Adding info for No Bus:vcs63
PM: Adding info for No Bus:vcsa63
PM: Removing info for No Bus:vcs63
PM: Removing info for No Bus:vcsa63
PM: Adding info for No Bus:vcs8
PM: Adding info for No Bus:vcsa8
PM: Removing info for No Bus:vcs8
PM: Removing info for No Bus:vcsa8
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Loading R200 Microcode
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
PM: suspend-to-disk mode set to 'platform'
Stopping tasks:
===================================================================================================|
Shrinking memory... -\|/done (56066 pages freed)
Suspending device bluetooth
platform bluetooth: freeze
Suspending device 00023f383800c298-0
Suspending device 00023f383800c298
Suspending device 1-1:Si3036,8
ac97 1-1:Si3036,8: freeze
Suspending device 0-0:AD1981B
ac97 0-0:AD1981B: freeze
Suspending device fw-host0
Suspending device usbdev4.1
usbdev4.1: PM: suspend 0->1, parent usb4 already 2
Suspending device usbdev4.1_ep81
Suspending device 4-0:1.0
hub 4-0:1.0: PM: suspend 0->1, parent usb4 already 2
hub 4-0:1.0: freeze
Suspending device usbdev4.1_ep00
usbdev4.1_ep00: PM: suspend 0->1, parent usb4 already 2
Suspending device usb4
usb usb4: PM: suspend 2-->1
Suspending device usbdev3.1
usbdev3.1: PM: suspend 0->1, parent usb3 already 2
Suspending device usbdev3.1_ep81
Suspending device 3-0:1.0
hub 3-0:1.0: PM: suspend 0->1, parent usb3 already 2
hub 3-0:1.0: freeze
Suspending device usbdev3.1_ep00
usbdev3.1_ep00: PM: suspend 0->1, parent usb3 already 2
Suspending device usb3
usb usb3: PM: suspend 2-->1
Suspending device usbdev2.1
usbdev2.1: PM: suspend 0->1, parent usb2 already 2
Suspending device usbdev2.1_ep81
Suspending device 2-0:1.0
hub 2-0:1.0: PM: suspend 0->1, parent usb2 already 2
hub 2-0:1.0: freeze
Suspending device usbdev2.1_ep00
usbdev2.1_ep00: PM: suspend 0->1, parent usb2 already 2
Suspending device usb2
usb usb2: PM: suspend 2-->1
Suspending device usbdev1.1
usbdev1.1: PM: suspend 0->1, parent usb1 already 2
Suspending device usbdev1.1_ep81
Suspending device 1-0:1.0
hub 1-0:1.0: PM: suspend 0->1, parent usb1 already 2
hub 1-0:1.0: freeze
Suspending device usbdev1.1_ep00
usbdev1.1_ep00: PM: suspend 0->1, parent usb1 already 2
Suspending device usb1
usb usb1: PM: suspend 2-->1
Suspending device i2c-0
Suspending device watchdog
Suspending device iTCO_wdt
iTCO_wdt iTCO_wdt: freeze
Suspending device device-mapper
Suspending device serio4
Suspending device serio3
Suspending device serio2
Suspending device serio1
Suspending device serio0
Suspending device i8042
i8042 i8042: freeze
Suspending device 1:0:0:0
sr 1:0:0:0: freeze
Suspending device target1:0:0
Suspending device 0:0:0:0
sd 0:0:0:0: freeze
Suspending device target0:0:0
Suspending device host1
Suspending device host0
Suspending device isa
Suspending device serial8250
serial8250 serial8250: freeze
Suspending device agpgart
Suspending device nvram
Suspending device hpet
Suspending device rtc
Suspending device vcsa
Suspending device vcs
Suspending device vc
Suspending device pnp1
Suspending device vesafb.0
platform vesafb.0: freeze
Suspending device snapshot
Suspending device misc
Suspending device pcspkr
pcspkr pcspkr: freeze
Suspending device 00:0e
system 00:0e: freeze
Suspending device 00:0d
system 00:0d: freeze
Suspending device 00:0c
system 00:0c: freeze
Suspending device 00:0b
i8042 aux 00:0b: freeze
Suspending device 00:0a
i8042 kbd 00:0a: freeze
Suspending device 00:09
pnp 00:09: freeze
Suspending device 00:08
pnp 00:08: freeze
Suspending device 00:07
pnp 00:07: freeze
Suspending device 00:06
pnp 00:06: freeze
Suspending device 00:05
parport_pc 00:05: freeze
pnp: Device 00:05 disabled.
Suspending device 00:04
pnp 00:04: freeze
Suspending device 00:03
serial 00:03: freeze
pnp: Device 00:03 disabled.
Suspending device 00:02
wbsd 00:02: freeze
pnp: Device 00:02 disabled.
Suspending device 00:01
pnp 00:01: freeze
Suspending device 00:00
system 00:00: freeze
Suspending device pnp0
Suspending device 0000:02:04.0
yenta_cardbus 0000:02:04.0: freeze
Suspending device 0000:02:02.0
ipw2200 0000:02:02.0: freeze
eth1: Going into suspend...
Suspending device 0000:02:01.0
8139cp 0000:02:01.0: freeze
Suspending device 0000:02:00.0
ohci1394 0000:02:00.0: freeze
Suspending device 0000:01:00.0
pci 0000:01:00.0: freeze
Suspending device 0000:00:1f.6
Intel ICH Modem 0000:00:1f.6: freeze
Suspending device 0000:00:1f.5
Intel ICH 0000:00:1f.5: freeze
codec_write 0: semaphore is not ready for register 0x26
Suspending device 0000:00:1f.3
i801_smbus 0000:00:1f.3: freeze
Suspending device 0000:00:1f.1
ata_piix 0000:00:1f.1: freeze
Suspending device 0000:00:1f.0
pci 0000:00:1f.0: freeze
Suspending device 0000:00:1e.0
pci 0000:00:1e.0: freeze
Suspending device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: freeze
usb_hcd_pci_suspend(): ehci_pci_suspend+0x0/0x84 [ehci_hcd]() returns -22
pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x13d() returns -22
suspend_device(): pci_device_suspend+0x0/0x34() returns -22
Could not suspend device 0000:00:1d.7: error -22
pci 0000:00:1e.0: resuming
PCI: Setting latency timer of device 0000:00:1e.0 to 64
pci 0000:00:1f.0: resuming
ata_piix 0000:00:1f.1: resuming
PCI: Setting latency timer of device 0000:00:1f.1 to 64
i801_smbus 0000:00:1f.3: resuming
Intel ICH 0000:00:1f.5: resuming
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
Intel ICH Modem 0000:00:1f.6: resuming
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [C0C3] -> GSI 10 (level,
low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.6 to 64
pci 0000:01:00.0: resuming
ohci1394 0000:02:00.0: resuming
8139cp 0000:02:01.0: resuming
ipw2200 0000:02:02.0: resuming
eth1: Coming out of suspend...
PCI: Enabling device 0000:02:02.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [C0C5] -> GSI 5 (level, low)
-> IRQ 5
PM: Writing back config space on device 0000:02:02.0 at offset f (was
18030100, writing 1803010b)
PM: Writing back config space on device 0000:02:02.0 at offset 4 (was 0,
writing 90000000)
PM: Writing back config space on device 0000:02:02.0 at offset 3 (was 0,
writing 8008)
PM: Writing back config space on device 0000:02:02.0 at offset 1 (was
2900002, writing 2900006)
yenta_cardbus 0000:02:04.0: resuming
PM: Writing back config space on device 0000:02:04.0 at offset 1 (was
2100003, writing 2100007)
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [C0C4] -> GSI 5 (level, low)
-> IRQ 5
system 00:00: resuming
pnp 00:01: resuming
wbsd 00:02: resuming
pnp: Device 00:02 activated.
serial 00:03: resuming
pnp: Device 00:03 activated.
pnp 00:04: resuming
parport_pc 00:05: resuming
pnp: Device 00:05 activated.
pnp 00:06: resuming
pnp 00:07: resuming
pnp 00:08: resuming
pnp 00:09: resuming
i8042 kbd 00:0a: resuming
pnp: Device 00:0a does not support activation.
i8042 aux 00:0b: resuming
pnp: Device 00:0b does not support activation.
system 00:0c: resuming
system 00:0d: resuming
system 00:0e: resuming
pcspkr pcspkr: resuming
platform vesafb.0: resuming
serial8250 serial8250: resuming
sd 0:0:0:0: resuming
ata1: EH complete
sr 1:0:0:0: resuming
ata2: EH complete
i8042 i8042: resuming
atkbd serio0: resuming
serio serio1: resuming
serio serio2: resuming
serio serio3: resuming
psmouse serio4: resuming
iTCO_wdt iTCO_wdt: resuming
usbdev1.1_ep00: PM: resume from 0, parent usb1 still 2
hub 1-0:1.0: PM: resume from 0, parent usb1 still 2
hub 1-0:1.0: resuming
usbdev1.1: PM: resume from 0, parent usb1 still 2
usbdev2.1_ep00: PM: resume from 0, parent usb2 still 2
hub 2-0:1.0: PM: resume from 0, parent usb2 still 2
hub 2-0:1.0: resuming
usbdev2.1: PM: resume from 0, parent usb2 still 2
usbdev3.1_ep00: PM: resume from 0, parent usb3 still 2
hub 3-0:1.0: PM: resume from 0, parent usb3 still 2
hub 3-0:1.0: resuming
usbdev3.1: PM: resume from 0, parent usb3 still 2
usbdev4.1_ep00: PM: resume from 0, parent usb4 still 2
hub 4-0:1.0: PM: resume from 0, parent usb4 still 2
hub 4-0:1.0: resuming
usbdev4.1: PM: resume from 0, parent usb4 still 2
ac97 0-0:AD1981B: resuming
ac97 1-1:Si3036,8: resuming
platform bluetooth: resuming
Some devices failed to suspend
Restarting tasks... done
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [C1BE]
ACPI: Lid Switch [C136]
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Loading R200 Microcode
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
David Chinner wrote:
> On Wed, Sep 13, 2006 at 11:43:32AM +0200, Michal Piotrowski wrote:
>> On 13/09/06, David Chinner <[email protected]> wrote:
>>> I've booted 2.6.18-rc6-mm2 and mounted and unmounted several xfs
>>> filesystems. I'm currently running xfsqa on it, and I haven't seen
>>> any failures on unmount yet.
>>>
>>> That test case would be really handy, Michal.
>> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/test_mount_fs.sh
>>
>> ls -hs /home/fs-farm/
>> total 3.6G
>> 513M ext2.img 513M ext4.img 513M reiser3.img 513M xfs.img
>> 513M ext3.img 513M jfs.img 513M reiser4.img
>
> Ok, so you're using loopback and mounting one of each filesystem, then
> unmounting them in the same order. I have mounted and unmounted an
> XFS filesystem in isolation in exactly the same way you have been, but
> I haven't seen any failures.
>
> Can you rerun the test with just XFS in your script and see if you
> see any failures? If you don't see any failures, can you add each
> filesystem back in one at a time until you see failures again?
I still get an oops (with xfs only). Maybe it's file system image problem.
xfs_info /mnt/fs-farm/xfs/
meta-data=/dev/loop1 isize=256 agcount=8, agsize=16384 blks
= sectsz=512
data = bsize=4096 blocks=131072, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=1200, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
>
> Cheers,
>
> Dave.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> David Chinner wrote:
> > On Wed, Sep 13, 2006 at 11:43:32AM +0200, Michal Piotrowski wrote:
> >> On 13/09/06, David Chinner <[email protected]> wrote:
> >>> I've booted 2.6.18-rc6-mm2 and mounted and unmounted several xfs
> >>> filesystems. I'm currently running xfsqa on it, and I haven't seen
> >>> any failures on unmount yet.
> >>>
> >>> That test case would be really handy, Michal.
> >> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/test_mount_fs.sh
> >>
> >> ls -hs /home/fs-farm/
> >> total 3.6G
> >> 513M ext2.img 513M ext4.img 513M reiser3.img 513M xfs.img
> >> 513M ext3.img 513M jfs.img 513M reiser4.img
> >
> > Ok, so you're using loopback and mounting one of each filesystem, then
> > unmounting them in the same order. I have mounted and unmounted an
> > XFS filesystem in isolation in exactly the same way you have been, but
> > I haven't seen any failures.
> >
> > Can you rerun the test with just XFS in your script and see if you
> > see any failures? If you don't see any failures, can you add each
> > filesystem back in one at a time until you see failures again?
>
>
> I still get an oops (with xfs only). Maybe it's file system image problem.
>
> xfs_info /mnt/fs-farm/xfs/
> meta-data=/dev/loop1 isize=256 agcount=8, agsize=16384 blks
> = sectsz=512
> data = bsize=4096 blocks=131072, imaxpct=25
> = sunit=0 swidth=0 blks, unwritten=1
> naming =version 2 bsize=4096
> log =internal bsize=4096 blocks=1200, version=1
> = sectsz=512 sunit=0 blks
> realtime =none extsz=65536 blocks=0, rtextents=0
Can I send to you this fs image? It's only 246KB bz2 file.
>
> >
> > Cheers,
> >
> > Dave.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> Can I send to you this fs image? It's only 246KB bz2 file.
I have uploaded this on my http.
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/xfs.img.bz2
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Thu, Sep 14, 2006 at 10:50:42AM +0200, Michal Piotrowski wrote:
> On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> >David Chinner wrote:
> >> On Wed, Sep 13, 2006 at 11:43:32AM +0200, Michal Piotrowski wrote:
> >>> On 13/09/06, David Chinner <[email protected]> wrote:
> >>>> I've booted 2.6.18-rc6-mm2 and mounted and unmounted several xfs
> >>>> filesystems. I'm currently running xfsqa on it, and I haven't seen
> >>>> any failures on unmount yet.
> >>>>
> >>>> That test case would be really handy, Michal.
> >>> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/test_mount_fs.sh
> >>>
> >>> ls -hs /home/fs-farm/
> >>> total 3.6G
> >>> 513M ext2.img 513M ext4.img 513M reiser3.img 513M xfs.img
> >>> 513M ext3.img 513M jfs.img 513M reiser4.img
> >>
> >> Ok, so you're using loopback and mounting one of each filesystem, then
> >> unmounting them in the same order. I have mounted and unmounted an
> >> XFS filesystem in isolation in exactly the same way you have been, but
> >> I haven't seen any failures.
> >>
> >> Can you rerun the test with just XFS in your script and see if you
> >> see any failures? If you don't see any failures, can you add each
> >> filesystem back in one at a time until you see failures again?
> >
> >
> >I still get an oops (with xfs only). Maybe it's file system image problem.
> >
> >xfs_info /mnt/fs-farm/xfs/
> >meta-data=/dev/loop1 isize=256 agcount=8, agsize=16384 blks
> > = sectsz=512
> >data = bsize=4096 blocks=131072, imaxpct=25
> > = sunit=0 swidth=0 blks, unwritten=1
> >naming =version 2 bsize=4096
> >log =internal bsize=4096 blocks=1200, version=1
> > = sectsz=512 sunit=0 blks
> >realtime =none extsz=65536 blocks=0, rtextents=0
>
> Can I send to you this fs image? It's only 246KB bz2 file.
I've downloaded it, and I don't see a panic on that fs at all.
I've got it sitting in a tight loop mounting and unmounting the
image you sent me, and nothing has gone wrong. I don't think it's
a corrupted filesystem problem - it seems more like a memory corruption
problem to me.
What arch are you running on and what compiler are you using?
Can you try 2.6.18-rc6 and see if it panics like this on your
machine? there is little difference in xfs between -rc6 and -rc6-mm2
so it would be good to know if this is a problem isolated to
the -mm tree or not....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
On 14/09/06, David Chinner <[email protected]> wrote:
> On Thu, Sep 14, 2006 at 10:50:42AM +0200, Michal Piotrowski wrote:
> > On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> > >David Chinner wrote:
> > >> On Wed, Sep 13, 2006 at 11:43:32AM +0200, Michal Piotrowski wrote:
> > >>> On 13/09/06, David Chinner <[email protected]> wrote:
> > >>>> I've booted 2.6.18-rc6-mm2 and mounted and unmounted several xfs
> > >>>> filesystems. I'm currently running xfsqa on it, and I haven't seen
> > >>>> any failures on unmount yet.
> > >>>>
> > >>>> That test case would be really handy, Michal.
> > >>> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/test_mount_fs.sh
> > >>>
> > >>> ls -hs /home/fs-farm/
> > >>> total 3.6G
> > >>> 513M ext2.img 513M ext4.img 513M reiser3.img 513M xfs.img
> > >>> 513M ext3.img 513M jfs.img 513M reiser4.img
> > >>
> > >> Ok, so you're using loopback and mounting one of each filesystem, then
> > >> unmounting them in the same order. I have mounted and unmounted an
> > >> XFS filesystem in isolation in exactly the same way you have been, but
> > >> I haven't seen any failures.
> > >>
> > >> Can you rerun the test with just XFS in your script and see if you
> > >> see any failures? If you don't see any failures, can you add each
> > >> filesystem back in one at a time until you see failures again?
> > >
> > >
> > >I still get an oops (with xfs only). Maybe it's file system image problem.
> > >
> > >xfs_info /mnt/fs-farm/xfs/
> > >meta-data=/dev/loop1 isize=256 agcount=8, agsize=16384 blks
> > > = sectsz=512
> > >data = bsize=4096 blocks=131072, imaxpct=25
> > > = sunit=0 swidth=0 blks, unwritten=1
> > >naming =version 2 bsize=4096
> > >log =internal bsize=4096 blocks=1200, version=1
> > > = sectsz=512 sunit=0 blks
> > >realtime =none extsz=65536 blocks=0, rtextents=0
> >
> > Can I send to you this fs image? It's only 246KB bz2 file.
>
> I've downloaded it, and I don't see a panic on that fs at all.
> I've got it sitting in a tight loop mounting and unmounting the
> image you sent me, and nothing has gone wrong. I don't think it's
> a corrupted filesystem problem - it seems more like a memory corruption
> problem to me.
I'm checking memory from time to time with memtest86.
>
> What arch are you running on and what compiler are you using?
gcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-libgcj-multifile
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
I'll build system with gcc 3.4
> Can you try 2.6.18-rc6 and see if it panics like this on your
> machine?
2.6.18-rc7 works fine.
> there is little difference in xfs between -rc6 and -rc6-mm2
> so it would be good to know if this is a problem isolated to
> the -mm tree or not....
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> Principal Engineer
> SGI Australian Software Group
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> On 14/09/06, David Chinner <[email protected]> wrote:
> >
> > What arch are you running on and what compiler are you using?
>
> gcc -v
> Using built-in specs.
> Target: i386-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-libgcj-multifile
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --with-cpu=generic --host=i386-redhat-linux
> Thread model: posix
> gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
>
> I'll build system with gcc 3.4
It's not a compiler issue.
Binary search should solve this mystery.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On 12/09/06, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
Kernel 2.6.18-rc6-mm2 - xfs-rename-uio_read.patch
Built with gcc 3.4
Reading specs from /usr/local/bin/../lib/gcc/i686-pc-linux-gnu/3.4.6/specs
Configured with: ./configure --prefix=/usr/local/ --disable-nls
--enable-shared --enable-languages=c --program-suffix=-3.4
Thread model: posix
gcc version 3.4.6
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
BUG: unable to handle kernel paging request at virtual address 5a5a5aaa
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
printing eip:
c01f596a
*pde = 00000000
Oops: 0000 [#1]
4K_STACKS PREEMPT SMP
last sysfs file:
Modules linked in:
CPU: 0
EIP: 0060:[<c01f596a>] Not tainted VLI
EFLAGS: 00010202 (2.6.18-rc6-mm2 #122)
EIP is at kref_get+0x7/0x55
eax: 5a5a5aaa ebx: 5a5a5aaa ecx: c75cfe54 edx: c75cfe54
esi: c033152f edi: c75cfe5e ebp: c755be20 esp: c755be18
ds: 007b es: 007b ss: 0068
Process usb-probe-<NULL (pid: 291, ti=c755b000 task=c759aab0 task.ti=c755b000)
Stack: 5a5a5a92 c033152f c755be2c c01f529b c75cfe80 c755be50 c01b1513 c755be50
fffffff4 c75bd51c 5a5a5a92 c75b8eec c0331525 5a5a5a92 c755be68 c01b15ca
ffffffef c75cfeac c752e044 c752e044 c755be80 c025d2ff c752e12c c75cfeac
Call Trace:
[<c01f529b>] kobject_get+0x12/0x17
[<c01b1513>] sysfs_add_link+0x5f/0xa3
[<c01b15ca>] sysfs_create_link+0x73/0x8c
[<c025d2ff>] device_add_class_symlinks+0x2f/0x111
[<c025d5f4>] device_add+0x181/0x2ea
[<c025d76f>] device_register+0x12/0x15
[<c02936b2>] usb_create_ep_files+0xaf/0x146
[<c0293013>] usb_create_sysfs_dev_files+0x80/0xbb
[<c0296402>] generic_probe+0xc/0x55
[<c0290e54>] usb_probe_device+0x35/0x3b
[<c025f1eb>] really_probe+0x3a/0xbb
[<c025f31e>] driver_probe_device+0x99/0xa5
[<c025f332>] __device_attach+0x8/0xa
[<c025e828>] bus_for_each_drv+0x38/0x5d
[<c025f384>] device_attach+0x50/0x67
[<c025e9fe>] bus_attach_device+0x1a/0x35
[<c025d65e>] device_add+0x1eb/0x2ea
[<c028c182>] __usb_new_device+0x102/0x134
[<c0134b3d>] kthread+0x79/0xa1
[<c0103e53>] kernel_thread_helper+0x7/0x10
=======================
Code: 40 89 06 3b 45 18 5e 7f 04 ff 07 31 db 8d 65 f4 89 d8 5b 5e 5f
5d c3 90 90 55 c7 00 01 00 00 00 89 e5 5d c3 55 89 e5 56 53 89 c3 <8b>
00 85 c0 0f 94 c0 0f b6 f0 b8 38 b9 38 c0 89 f2 e8 f4 0f 01
Sep 14 12:58:09 euridica kernel: EIP: [<c01f596a>] kref_get+0x7/0x55
SS:ESP 0068:c755be18
Sep 14 12:58:09 euridica kernel: <7>PCI: Setting latency timer of
device 0000:00:1d.2 to 64
l *0xc01f596a
0xc01f596a is in kref_get (/usr/src/linux-mm/lib/kref.c:32).
27 * kref_get - increment refcount for object.
28 * @kref: object.
29 */
30 void kref_get(struct kref *kref)
31 {
32 WARN_ON(!atomic_read(&kref->refcount));
33 atomic_inc(&kref->refcount);
34 }
35
36 /**
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-config1
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Thursday, 14 September 2006 07:16, Robert Hancock wrote:
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
>
> Seeing a problem with suspend-to-RAM or suspend-to-disk on my laptop. If
> I suspend (either way) once it is fine. If I suspend again the EHCI
> controller fails to suspend and the suspend is aborted.
This one is being worked on now (see the thread starting from
http://marc.theaimsgroup.com/?l=linux-kernel&m=115815146907713&w=2).
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Thursday, 14 September 2006 00:31, Pete Zaitcev wrote:
> On Wed, 13 Sep 2006 14:44:48 -0400 (EDT), Alan Stern <[email protected]> wrote:
>
> > This problem has already been identified by Pete Zaitcev in this thread:
> >
> > http://marc.theaimsgroup.com/?t=115769512800001&r=1&w=2
> >
> > Perhaps Pete has an updated patch to fix the problem. If not, I could
> > write one.
>
> No, not yet. I am working on getting David's approach with irq = -1
> tested at Stratus. Since it was the only reproducer known to me, I wanted
> to test. Now that Rafael has a fault case, I'll expedite.
In fact I can reproduce it on two different boxes now.
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
(Added linux-usb-devel)
On Thu, 14 Sep 2006 13:11:49 +0200
"Michal Piotrowski" <[email protected]> wrote:
> On 12/09/06, Andrew Morton <[email protected]> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> >
>
> Kernel 2.6.18-rc6-mm2 - xfs-rename-uio_read.patch
> Built with gcc 3.4
> Reading specs from /usr/local/bin/../lib/gcc/i686-pc-linux-gnu/3.4.6/specs
> Configured with: ./configure --prefix=/usr/local/ --disable-nls
> --enable-shared --enable-languages=c --program-suffix=-3.4
> Thread model: posix
> gcc version 3.4.6
>
> ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
> BUG: unable to handle kernel paging request at virtual address 5a5a5aaa
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> printing eip:
> c01f596a
> *pde = 00000000
> Oops: 0000 [#1]
> 4K_STACKS PREEMPT SMP
> last sysfs file:
> Modules linked in:
> CPU: 0
> EIP: 0060:[<c01f596a>] Not tainted VLI
> EFLAGS: 00010202 (2.6.18-rc6-mm2 #122)
> EIP is at kref_get+0x7/0x55
> eax: 5a5a5aaa ebx: 5a5a5aaa ecx: c75cfe54 edx: c75cfe54
> esi: c033152f edi: c75cfe5e ebp: c755be20 esp: c755be18
> ds: 007b es: 007b ss: 0068
> Process usb-probe-<NULL (pid: 291, ti=c755b000 task=c759aab0 task.ti=c755b000)
That's an interesting process name..
> Stack: 5a5a5a92 c033152f c755be2c c01f529b c75cfe80 c755be50 c01b1513 c755be50
> fffffff4 c75bd51c 5a5a5a92 c75b8eec c0331525 5a5a5a92 c755be68 c01b15ca
> ffffffef c75cfeac c752e044 c752e044 c755be80 c025d2ff c752e12c c75cfeac
> Call Trace:
> [<c01f529b>] kobject_get+0x12/0x17
> [<c01b1513>] sysfs_add_link+0x5f/0xa3
> [<c01b15ca>] sysfs_create_link+0x73/0x8c
> [<c025d2ff>] device_add_class_symlinks+0x2f/0x111
> [<c025d5f4>] device_add+0x181/0x2ea
> [<c025d76f>] device_register+0x12/0x15
> [<c02936b2>] usb_create_ep_files+0xaf/0x146
> [<c0293013>] usb_create_sysfs_dev_files+0x80/0xbb
> [<c0296402>] generic_probe+0xc/0x55
> [<c0290e54>] usb_probe_device+0x35/0x3b
> [<c025f1eb>] really_probe+0x3a/0xbb
> [<c025f31e>] driver_probe_device+0x99/0xa5
> [<c025f332>] __device_attach+0x8/0xa
> [<c025e828>] bus_for_each_drv+0x38/0x5d
> [<c025f384>] device_attach+0x50/0x67
> [<c025e9fe>] bus_attach_device+0x1a/0x35
> [<c025d65e>] device_add+0x1eb/0x2ea
> [<c028c182>] __usb_new_device+0x102/0x134
> [<c0134b3d>] kthread+0x79/0xa1
> [<c0103e53>] kernel_thread_helper+0x7/0x10
> =======================
> Code: 40 89 06 3b 45 18 5e 7f 04 ff 07 31 db 8d 65 f4 89 d8 5b 5e 5f
> 5d c3 90 90 55 c7 00 01 00 00 00 89 e5 5d c3 55 89 e5 56 53 89 c3 <8b>
> 00 85 c0 0f 94 c0 0f b6 f0 b8 38 b9 38 c0 89 f2 e8 f4 0f 01
> Sep 14 12:58:09 euridica kernel: EIP: [<c01f596a>] kref_get+0x7/0x55
> SS:ESP 0068:c755be18
> Sep 14 12:58:09 euridica kernel: <7>PCI: Setting latency timer of
> device 0000:00:1d.2 to 64
>
> l *0xc01f596a
> 0xc01f596a is in kref_get (/usr/src/linux-mm/lib/kref.c:32).
> 27 * kref_get - increment refcount for object.
> 28 * @kref: object.
> 29 */
> 30 void kref_get(struct kref *kref)
> 31 {
> 32 WARN_ON(!atomic_read(&kref->refcount));
> 33 atomic_inc(&kref->refcount);
> 34 }
> 35
> 36 /**
>
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-config1
>
> Regards,
> Michal
>
> --
> Michal K. K. Piotrowski
> LTG - Linux Testers Group
> (http://www.stardust.webpages.pl/ltg/)
On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> On 14/09/06, Michal Piotrowski <[email protected]> wrote:
> > On 14/09/06, David Chinner <[email protected]> wrote:
> > >
> > > What arch are you running on and what compiler are you using?
> >
> > gcc -v
> > Using built-in specs.
> > Target: i386-redhat-linux
> > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> > --infodir=/usr/share/info --enable-shared --enable-threads=posix
> > --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> > --disable-libunwind-exceptions --enable-libgcj-multifile
> > --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> > --enable-java-awt=gtk --disable-dssi
> > --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> > --with-cpu=generic --host=i386-redhat-linux
> > Thread model: posix
> > gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
> >
> > I'll build system with gcc 3.4
>
> It's not a compiler issue.
>
> Binary search should solve this mystery.
I was wrong - it's in vanilla tree
(http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1).
cat hunt | head -n 3
origin.patch
BAD
libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
I can reproduce this bug with all CONFIG_DEBUG_*=y.
(only
CONFIG_DEBUG_SYNCHRO_TEST=m
CONFIG_RCU_TORTURE_TEST=m
as modules)
I have checked memory
http://www.stardust.webpages.pl/files/crap/memtest.jpg and everything
seems to be fine.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Thu, Sep 14, 2006 at 01:11:49PM +0200, Michal Piotrowski wrote:
> On 12/09/06, Andrew Morton <[email protected]> wrote:
> >
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> >
>
> Kernel 2.6.18-rc6-mm2 - xfs-rename-uio_read.patch
> Built with gcc 3.4
> Reading specs from /usr/local/bin/../lib/gcc/i686-pc-linux-gnu/3.4.6/specs
> Configured with: ./configure --prefix=/usr/local/ --disable-nls
> --enable-shared --enable-languages=c --program-suffix=-3.4
> Thread model: posix
> gcc version 3.4.6
>
> ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
> BUG: unable to handle kernel paging request at virtual address 5a5a5aaa
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> printing eip:
> c01f596a
> *pde = 00000000
> Oops: 0000 [#1]
> 4K_STACKS PREEMPT SMP
> last sysfs file:
> Modules linked in:
> CPU: 0
> EIP: 0060:[<c01f596a>] Not tainted VLI
> EFLAGS: 00010202 (2.6.18-rc6-mm2 #122)
> EIP is at kref_get+0x7/0x55
> eax: 5a5a5aaa ebx: 5a5a5aaa ecx: c75cfe54 edx: c75cfe54
> esi: c033152f edi: c75cfe5e ebp: c755be20 esp: c755be18
> ds: 007b es: 007b ss: 0068
> Process usb-probe-<NULL (pid: 291, ti=c755b000 task=c759aab0
> task.ti=c755b000)
You have the USB multi-threaded device probing config option
(CONFIG_USB_MULTITHREAD_PROBE) enabled, right?
Does disabling it fix this problem?
That option has been reworked by Alan Stern, and I need to intregate it
into my tree soon. This is the first report of a problem with the
current stuff, I wonder why.
Can you send the output of /sys/proc/bus/usb/devices with the same
devices plugged in on a different, no oopsing kernel?
thanks,
greg k-h
On 14/09/06, Greg KH <[email protected]> wrote:
> On Thu, Sep 14, 2006 at 01:11:49PM +0200, Michal Piotrowski wrote:
> > On 12/09/06, Andrew Morton <[email protected]> wrote:
> > >
> > >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> > >
> >
> > Kernel 2.6.18-rc6-mm2 - xfs-rename-uio_read.patch
> > Built with gcc 3.4
> > Reading specs from /usr/local/bin/../lib/gcc/i686-pc-linux-gnu/3.4.6/specs
> > Configured with: ./configure --prefix=/usr/local/ --disable-nls
> > --enable-shared --enable-languages=c --program-suffix=-3.4
> > Thread model: posix
> > gcc version 3.4.6
> >
> > ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
> > BUG: unable to handle kernel paging request at virtual address 5a5a5aaa
> > usb usb2: configuration #1 chosen from 1 choice
> > hub 2-0:1.0: USB hub found
> > printing eip:
> > c01f596a
> > *pde = 00000000
> > Oops: 0000 [#1]
> > 4K_STACKS PREEMPT SMP
> > last sysfs file:
> > Modules linked in:
> > CPU: 0
> > EIP: 0060:[<c01f596a>] Not tainted VLI
> > EFLAGS: 00010202 (2.6.18-rc6-mm2 #122)
> > EIP is at kref_get+0x7/0x55
> > eax: 5a5a5aaa ebx: 5a5a5aaa ecx: c75cfe54 edx: c75cfe54
> > esi: c033152f edi: c75cfe5e ebp: c755be20 esp: c755be18
> > ds: 007b es: 007b ss: 0068
> > Process usb-probe-<NULL (pid: 291, ti=c755b000 task=c759aab0
> > task.ti=c755b000)
>
> You have the USB multi-threaded device probing config option
> (CONFIG_USB_MULTITHREAD_PROBE) enabled, right?
Yes, I have.
>
> Does disabling it fix this problem?
I'll disable it and try to reproduce the problem.
> That option has been reworked by Alan Stern, and I need to intregate it
> into my tree soon. This is the first report of a problem with the
> current stuff, I wonder why.
>
> Can you send the output of /sys/proc/bus/usb/devices with the same
> devices plugged in on a different, no oopsing kernel?
cat /proc/bus/usb/devices
T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18-rc7-g63b98080 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18-rc7-g63b98080 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc=118/900 us (13%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18-rc7-g63b98080 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=04d9 ProdID=0499 Rev= 2.90
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18-rc7-g63b98080 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18-rc7-g63b98080 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
>
> thanks,
>
> greg k-h
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Fri, Sep 15, 2006 at 12:17:33AM +0200, Michal Piotrowski wrote:
> On 14/09/06, Greg KH <[email protected]> wrote:
> >On Thu, Sep 14, 2006 at 01:11:49PM +0200, Michal Piotrowski wrote:
> >> On 12/09/06, Andrew Morton <[email protected]> wrote:
> >> >
> >>
> >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> >> >
> >>
> >> Kernel 2.6.18-rc6-mm2 - xfs-rename-uio_read.patch
> >> Built with gcc 3.4
> >> Reading specs from
> >/usr/local/bin/../lib/gcc/i686-pc-linux-gnu/3.4.6/specs
> >> Configured with: ./configure --prefix=/usr/local/ --disable-nls
> >> --enable-shared --enable-languages=c --program-suffix=-3.4
> >> Thread model: posix
> >> gcc version 3.4.6
> >>
> >> ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
> >> BUG: unable to handle kernel paging request at virtual address 5a5a5aaa
> >> usb usb2: configuration #1 chosen from 1 choice
> >> hub 2-0:1.0: USB hub found
> >> printing eip:
> >> c01f596a
> >> *pde = 00000000
> >> Oops: 0000 [#1]
> >> 4K_STACKS PREEMPT SMP
> >> last sysfs file:
> >> Modules linked in:
> >> CPU: 0
> >> EIP: 0060:[<c01f596a>] Not tainted VLI
> >> EFLAGS: 00010202 (2.6.18-rc6-mm2 #122)
> >> EIP is at kref_get+0x7/0x55
> >> eax: 5a5a5aaa ebx: 5a5a5aaa ecx: c75cfe54 edx: c75cfe54
> >> esi: c033152f edi: c75cfe5e ebp: c755be20 esp: c755be18
> >> ds: 007b es: 007b ss: 0068
> >> Process usb-probe-<NULL (pid: 291, ti=c755b000 task=c759aab0
> >> task.ti=c755b000)
> >
> >You have the USB multi-threaded device probing config option
> >(CONFIG_USB_MULTITHREAD_PROBE) enabled, right?
>
> Yes, I have.
>
> >
> >Does disabling it fix this problem?
>
> I'll disable it and try to reproduce the problem.
Great, please let us know. Your device list looks simple, I don't see
why this would happen (no confusing devices). In fact, this is getting
triggered by the root hub, which Alan's update specifically addresses by
not making that be multithreaded, as it's not needed.
I'll work on intergrating that patch update.
thanks,
greg k-h
On Thu, Sep 14, 2006 at 07:01:38PM +0200, Michal Piotrowski wrote:
> >>
> >> I'll build system with gcc 3.4
> >
> >It's not a compiler issue.
> >
> >Binary search should solve this mystery.
>
> I was wrong - it's in vanilla tree
> (http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1).
>
> cat hunt | head -n 3
> origin.patch
> BAD
> libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
Not sure what this means....
> I can reproduce this bug with all CONFIG_DEBUG_*=y.
> (only
> CONFIG_DEBUG_SYNCHRO_TEST=m
> CONFIG_RCU_TORTURE_TEST=m
> as modules)
I notice you're running i386 with 4k stacks - I wonder if you're blowing the
stack by running xfs on loopback. I've been testing on x86_64 and ia64
which don't have those issues. Can you try with 8K stacks instead of
4k stacks?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
On Fri, 15 Sep 2006 12:57:45 +1000
David Chinner <[email protected]> wrote:
> On Thu, Sep 14, 2006 at 07:01:38PM +0200, Michal Piotrowski wrote:
> > >>
> > >> I'll build system with gcc 3.4
> > >
> > >It's not a compiler issue.
> > >
> > >Binary search should solve this mystery.
> >
> > I was wrong - it's in vanilla tree
> > (http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1).
> >
> > cat hunt | head -n 3
> > origin.patch
> > BAD
> > libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
>
> Not sure what this means....
"BAD" is a bisection point, as per
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt. So
just 2.6.18-rc6+origin.patch exhibits the failure. That is mainline.
> > I can reproduce this bug with all CONFIG_DEBUG_*=y.
> > (only
> > CONFIG_DEBUG_SYNCHRO_TEST=m
> > CONFIG_RCU_TORTURE_TEST=m
> > as modules)
>
> I notice you're running i386 with 4k stacks - I wonder if you're blowing the
> stack by running xfs on loopback. I've been testing on x86_64 and ia64
> which don't have those issues. Can you try with 8K stacks instead of
> 4k stacks?
hm, that wouldn't be good.
Enabling CONFIG_DEBUG_STACK_USAGE will make the fourth column in the
sysrq-T output display the minimum-ever free stack space for each task.
sleep S ffff810100f0bea8 0 18893 22372 (NOTLB)
^ this number.
On Thu, Sep 14, 2006 at 08:48:01PM -0700, Andrew Morton wrote:
> On Fri, 15 Sep 2006 12:57:45 +1000
> David Chinner <[email protected]> wrote:
>
> > On Thu, Sep 14, 2006 at 07:01:38PM +0200, Michal Piotrowski wrote:
> > > >>
> > > >> I'll build system with gcc 3.4
> > > >
> > > >It's not a compiler issue.
> > > >
> > > >Binary search should solve this mystery.
> > >
> > > I was wrong - it's in vanilla tree
> > > (http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1).
> > >
> > > cat hunt | head -n 3
> > > origin.patch
> > > BAD
> > > libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
> >
> > Not sure what this means....
>
> "BAD" is a bisection point, as per
> http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt. So
> just 2.6.18-rc6+origin.patch exhibits the failure. That is mainline.
Ah - thanks for explaining that for me, Andrew.
Michal, there were several XFS fixes (4, I think) that went into -rc7. If
-rc6 fails and -rc7 doesn't then we need to check if one of those fixes is
responsible. The crash doesn't match any of the symptoms we've seen from them,
but it's worth checking.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
On 15/09/06, David Chinner <[email protected]> wrote:
> On Thu, Sep 14, 2006 at 08:48:01PM -0700, Andrew Morton wrote:
> > "BAD" is a bisection point, as per
> > http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt. So
> > just 2.6.18-rc6+origin.patch exhibits the failure. That is mainline.
>
> Ah - thanks for explaining that for me, Andrew.
>
> Michal, there were several XFS fixes (4, I think) that went into -rc7. If
> -rc6 fails and -rc7 doesn't then we need to check if one of those fixes is
> responsible.
As I said before "I was wrong" (I use lockdep only with -mm kernels).
> The crash doesn't match any of the symptoms we've seen from them,
> but it's worth checking.
http://www.ussg.iu.edu/hypermail/linux/kernel/0608.1/1202.html
The problem with this bug is "bad interaction" between lockdep and
XFS. (I forgot about this probably because lockdep was broken for me
in 2.6.18-rc5-mm* - and previous bug appeared while mounting XFS, not
umounting).
2006-07-03 locdep was merged
2006-07-28 - 2006-08-10 a few XFS fixes
So I guess that binary search won't solve this mystery.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> Principal Engineer
> SGI Australian Software Group
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On 15/09/06, Greg KH <[email protected]> wrote:
> On Fri, Sep 15, 2006 at 12:17:33AM +0200, Michal Piotrowski wrote:
> > On 14/09/06, Greg KH <[email protected]> wrote:
> > >On Thu, Sep 14, 2006 at 01:11:49PM +0200, Michal Piotrowski wrote:
> > >> On 12/09/06, Andrew Morton <[email protected]> wrote:
> > >> >
> > >>
> > >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm2/
> > >> >
> > >>
> > >> Kernel 2.6.18-rc6-mm2 - xfs-rename-uio_read.patch
> > >> Built with gcc 3.4
> > >> Reading specs from
> > >/usr/local/bin/../lib/gcc/i686-pc-linux-gnu/3.4.6/specs
> > >> Configured with: ./configure --prefix=/usr/local/ --disable-nls
> > >> --enable-shared --enable-languages=c --program-suffix=-3.4
> > >> Thread model: posix
> > >> gcc version 3.4.6
> > >>
> > >> ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
> > >> BUG: unable to handle kernel paging request at virtual address 5a5a5aaa
> > >> usb usb2: configuration #1 chosen from 1 choice
> > >> hub 2-0:1.0: USB hub found
> > >> printing eip:
> > >> c01f596a
> > >> *pde = 00000000
> > >> Oops: 0000 [#1]
> > >> 4K_STACKS PREEMPT SMP
> > >> last sysfs file:
> > >> Modules linked in:
> > >> CPU: 0
> > >> EIP: 0060:[<c01f596a>] Not tainted VLI
> > >> EFLAGS: 00010202 (2.6.18-rc6-mm2 #122)
> > >> EIP is at kref_get+0x7/0x55
> > >> eax: 5a5a5aaa ebx: 5a5a5aaa ecx: c75cfe54 edx: c75cfe54
> > >> esi: c033152f edi: c75cfe5e ebp: c755be20 esp: c755be18
> > >> ds: 007b es: 007b ss: 0068
> > >> Process usb-probe-<NULL (pid: 291, ti=c755b000 task=c759aab0
> > >> task.ti=c755b000)
> > >
> > >You have the USB multi-threaded device probing config option
> > >(CONFIG_USB_MULTITHREAD_PROBE) enabled, right?
> >
> > Yes, I have.
> >
> > >
> > >Does disabling it fix this problem?
> >
> > I'll disable it and try to reproduce the problem.
>
> Great, please let us know.
Good news, I can't reproduce this bug with CONFIG_USB_MULTITHREAD_PROBE=n.
BTW. This might be a problem with CONFIG_PCI_MULTITHREAD_PROBE=y
http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/bug.jpg
> Your device list looks simple, I don't see
> why this would happen (no confusing devices). In fact, this is getting
> triggered by the root hub, which Alan's update specifically addresses by
> not making that be multithreaded, as it's not needed.
>
> I'll work on intergrating that patch update.
>
> thanks,
>
> greg k-h
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Fri, Sep 15, 2006 at 10:35:37PM +0200, Michal Piotrowski wrote:
> Good news, I can't reproduce this bug with CONFIG_USB_MULTITHREAD_PROBE=n.
Great, thanks for letting me know.
> BTW. This might be a problem with CONFIG_PCI_MULTITHREAD_PROBE=y
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/bug.jpg
That looks odd. What device is your root partition on? And what is the
"switchroot" stuff being printed out, is that in an initramfs?
thanks,
greg k-h
On Thu, 14 Sep 2006 13:19:53 +0200, "Rafael J. Wysocki" <[email protected]> wrote:
> In fact I can reproduce it on two different boxes now.
How about the attached?
-- Pete
diff -urp -X dontdiff linux-2.6.18-rc6/drivers/usb/host/ohci-hcd.c linux-2.6.18-rc6-lem/drivers/usb/host/ohci-hcd.c
--- linux-2.6.18-rc6/drivers/usb/host/ohci-hcd.c 2006-09-06 21:56:32.000000000 -0700
+++ linux-2.6.18-rc6-lem/drivers/usb/host/ohci-hcd.c 2006-09-14 22:48:15.000000000 -0700
@@ -775,7 +775,9 @@ static void ohci_stop (struct usb_hcd *h
ohci_usb_reset (ohci);
ohci_writel (ohci, OHCI_INTR_MIE, &ohci->regs->intrdisable);
-
+ free_irq(hcd->irq, hcd);
+ hcd->irq = -1;
+
remove_debug_files (ohci);
unregister_reboot_notifier (&ohci->reboot_notifier);
ohci_mem_cleanup (ohci);
On 15/09/06, Greg KH <[email protected]> wrote:
> On Fri, Sep 15, 2006 at 10:35:37PM +0200, Michal Piotrowski wrote:
> > Good news, I can't reproduce this bug with CONFIG_USB_MULTITHREAD_PROBE=n.
>
> Great, thanks for letting me know.
>
> > BTW. This might be a problem with CONFIG_PCI_MULTITHREAD_PROBE=y
> > http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/bug.jpg
>
> That looks odd. What device is your root partition on?
SATA HDD.
> And what is the
> "switchroot" stuff being printed out, is that in an initramfs?
Yes, it's initrd generated by new-kernel-pkg (Fedora).
>
> thanks,
>
> greg k-h
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
On Saturday, 16 September 2006 00:45, Pete Zaitcev wrote:
> On Thu, 14 Sep 2006 13:19:53 +0200, "Rafael J. Wysocki" <[email protected]> wrote:
>
> > In fact I can reproduce it on two different boxes now.
>
> How about the attached?
Apparently works. :-)
Thanks,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
Hello,
I could not find this anywhere reported, so here it goes:
when is enabled, gcc-4.0.3 (ubuntu/dapper, x86_64) gives:
fs/built-in.o: In function `init_nfs_fs':inode.c:(.init.text+0x16a9): undefined reference to `__fscache_register_netfs'
:inode.c:(.init.text+0x1757): undefined reference to `__fscache_unregister_netfs'
see the full error here:
http://nerdbynature.de/bits/2.6.18-rc6-mm2/make.log
I suspect a missing "#include <linux/fscache.h>" but could not find out
where yet :(
Thanks,
Christian.
--
BOFH excuse #96:
Vendor no longer supports the product
On Sun, 17 Sep 2006, Christian Kujau wrote:
> when is enabled, gcc-4.0.3 (ubuntu/dapper, x86_64) gives:
------^ uh, that should read:
"when CONFIG_NFS_FSCACHE is enabled..."
The diff to the old-and-working-config is here:
http://nerdbynature.de/bits/2.6.18-rc6-mm2/config.diff
Christian.
--
BOFH excuse #50:
Change in Earth's rotational speed
On Fri, Sep 15, 2006 at 10:06:48AM +0200, Michal Piotrowski wrote:
> On 15/09/06, David Chinner <[email protected]> wrote:
> >On Thu, Sep 14, 2006 at 08:48:01PM -0700, Andrew Morton wrote:
> >> "BAD" is a bisection point, as per
> >> http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt.
> >So
> >> just 2.6.18-rc6+origin.patch exhibits the failure. That is mainline.
> >
> >Ah - thanks for explaining that for me, Andrew.
> >
> >Michal, there were several XFS fixes (4, I think) that went into -rc7. If
> >-rc6 fails and -rc7 doesn't then we need to check if one of those fixes is
> >responsible.
>
> As I said before "I was wrong" (I use lockdep only with -mm kernels).
>
> >The crash doesn't match any of the symptoms we've seen from them,
> >but it's worth checking.
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0608.1/1202.html
>
> The problem with this bug is "bad interaction" between lockdep and
> XFS. (I forgot about this probably because lockdep was broken for me
> in 2.6.18-rc5-mm* - and previous bug appeared while mounting XFS, not
> umounting).
According to the above link, unmount was the problem as well.
I know little about lockdep, but if this really is the superblock
lock that we are oopsing on then I cannot see how XFS is involved
at all seeing as it does not ever touch the superblock lock.
I'd say the first step is to get a lockdep expert to explain why
we are oopsing here....
> 2006-07-03 locdep was merged
> 2006-07-28 - 2006-08-10 a few XFS fixes
>
> So I guess that binary search won't solve this mystery.
Don't use lockdep with XFS yet. XFS hasn't been instrumented
with lockdep notations, so nothing good will come from using
it right now. There is work in progress to fix this, but it's not
ready yet.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
On Sat, Sep 16, 2006 at 02:14:52PM +0200, Michal Piotrowski wrote:
> On 15/09/06, Greg KH <[email protected]> wrote:
> >On Fri, Sep 15, 2006 at 10:35:37PM +0200, Michal Piotrowski wrote:
> >> Good news, I can't reproduce this bug with
> >CONFIG_USB_MULTITHREAD_PROBE=n.
> >
> >Great, thanks for letting me know.
> >
> >> BTW. This might be a problem with CONFIG_PCI_MULTITHREAD_PROBE=y
> >> http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/bug.jpg
> >
> >That looks odd. What device is your root partition on?
>
> SATA HDD.
Which type of SATA device? Is it ata_piix perhaps?
If so, you need the hack below to enable these devices to work properly.
I can't vouch for any problems that might happen with the patch, but
I've been using it successfully for quite a while.
thanks,
greg k-h
---------------------
Subject: Driver: multi-threaded hacks
- Fix "issue" with ata_piix doing multi-threaded boot
Use at your own risk.
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/scsi/ata_piix.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- gregkh-2.6.orig/drivers/scsi/ata_piix.c
+++ gregkh-2.6/drivers/scsi/ata_piix.c
@@ -1024,7 +1024,7 @@ static int __init piix_init(void)
if (rc)
return rc;
- in_module_init = 0;
+// in_module_init = 0; multi-threaded probe doesn't like this...
DPRINTK("done\n");
return 0;
On Friday 15 September 2006 3:45 pm, Pete Zaitcev wrote:
> On Thu, 14 Sep 2006 13:19:53 +0200, "Rafael J. Wysocki" <[email protected]> wrote:
>
> > In fact I can reproduce it on two different boxes now.
>
> How about the attached?
>
> -- Pete
Signed-off-by: David Brownell <[email protected]>
> diff -urp -X dontdiff linux-2.6.18-rc6/drivers/usb/host/ohci-hcd.c linux-2.6.18-rc6-lem/drivers/usb/host/ohci-hcd.c
> --- linux-2.6.18-rc6/drivers/usb/host/ohci-hcd.c 2006-09-06 21:56:32.000000000 -0700
> +++ linux-2.6.18-rc6-lem/drivers/usb/host/ohci-hcd.c 2006-09-14 22:48:15.000000000 -0700
> @@ -775,7 +775,9 @@ static void ohci_stop (struct usb_hcd *h
>
> ohci_usb_reset (ohci);
> ohci_writel (ohci, OHCI_INTR_MIE, &ohci->regs->intrdisable);
> -
> + free_irq(hcd->irq, hcd);
> + hcd->irq = -1;
> +
> remove_debug_files (ohci);
> unregister_reboot_notifier (&ohci->reboot_notifier);
> ohci_mem_cleanup (ohci);
>
Christian Kujau <[email protected]> wrote:
> I could not find this anywhere reported, so here it goes:
>
> when is enabled, gcc-4.0.3 (ubuntu/dapper, x86_64) gives:
>
> fs/built-in.o: In function `init_nfs_fs':inode.c:(.init.text+0x16a9): undefined reference to `__fscache_register_netfs'
> :inode.c:(.init.text+0x1757): undefined reference to `__fscache_unregister_netfs'
It looks like your build failed to build the fscache facility or built it as a
module but build NFS directly into the kernel. What's your full configuration?
David
Hmmm... It looks like a configurator problem:
warthog>grep 'NFS\|CACHE' .config
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_INTERNODE_CACHE_BYTES=128
# CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set
CONFIG_IRDA_CACHE_LAST_LSAP=y
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_FS_MBCACHE=y
---> CONFIG_FSCACHE=m
# CONFIG_CACHEFILES is not set
---> CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_FSCACHE=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_NCPFS_NFS_NS=y
I'm not sure what I can do about that. NFS_FS doesn't depend on FSCACHE, and
so isn't forced to become a module when FSCACHE is. The dependency is through
one of NFS's configuation options.
David
Hello David,
On Fri, 22 Sep 2006, David Howells wrote:
> ---> CONFIG_FSCACHE=m
> # CONFIG_CACHEFILES is not set
> ---> CONFIG_NFS_FS=y
[...]
> I'm not sure what I can do about that. NFS_FS doesn't depend on FSCACHE, and
> so isn't forced to become a module when FSCACHE is. The dependency is through
> one of NFS's configuation options.
I'll try to build with different settings (CONFIG_FSCACHE=y and will
look at the Kconfig for this one again, only my (faster) build-machine
is offline right now...
Thanks,
Christian.
--
BOFH excuse #378:
Operators killed by year 2000 bug bite.
for the record (and to make the archives happy): the compile error
went away with the latest -mm version (same config, make oldconfig).
Thanks,
Christian.
--
BOFH excuse #11:
magnetic interference from money/credit cards
