> Changes since 2.6.13-rc2-mm1: I'm seeing this oops with 2.6.13-rc2-mm2: *pde 00000000 Oops: 0000 [#1] last sysfs file: Modules linked in: dm_snapshot dm_mirror ext3 mbcache jbd dm_mod CPU: 0 EIP: 0060:[<e081e681>] Not tainted VLI EFLAGS: 00010246 (2.6.13-rc2mm2) EIP is at suspend_targets+0x6/0x47 [dm_mod] eax: 00000000 ebx: dfdee400 ecx: e0827108 edx: 00000000 esi: dfdee400 edi: c1620000 ebp: 00000000 esp: c1621efc ds: 007b es: 007b ss:0068 Process lvm (pid: 236, threadinfo=c1620000 task=dfee1a70) Stack: dfdee400 dfdee400 c1620000 00000000 e081d15b 00000000 00000000 dfee1a70 c0115680 00000000 00000000 dfded680 dfdee400 e0826bc0 e082c000 e08201f0 00000000 dfded680 c1620000 00000000 00000006 e082023d e08211b8 00000001 Call Trace: [<e081d15b>] dm_suspend+0x89/0x185 [dm_mod] [<c0115680>] default_wake_function+0x0/0xc [<e08201f0>] do_resume+0x149/0x196 [dm_mod] [<e082023d>] dev_suspend+0x0/0x10 [dm_mod] [<e08211b8>] ctl_ioctl+0xce/0x10a [dm_mod] [<e08210ea>] ctl_ioctl+0x0/0x10a [dm_mod] [<c015fdc1>] do_ioctl+0x51/0x55 [<c015feb7>] vfs_ioctl+0x50/0x1aa [<c016006e>] sys_ioctl+0x5d/0x6b [<c0102c85>] syscall_call+0x7/0xb Code: 00 00 8b 83 b0 00 00 00 89 86 4c 01 00 00 5b 5e c3 8b 80 88 00 00 00 c3 05 9c 00 00 00 c3 8b 80 98 00 00 00 c3 44 57 56 53 89 d5 <8b> b8 88 00 00 00 8b 98 94 00 00 00 85 ff 74 1e 31 f6 85 ed 74 ERROR: /bin/lvm exited abnormally with value 0 ! (pid 236) Doesn't happen with 2.6.13-rc2-mm1, however. Any ideas?
Attachment:
config-2.6.13-rc2mm2
Description: Binary data
- Follow-Ups:
- Re: 2.6.13-rc2-mm2
- From: Alasdair G Kergon <[email protected]>
- Re: 2.6.13-rc2-mm2
- References:
- 2.6.13-rc2-mm2
- From: Andrew Morton <[email protected]>
- 2.6.13-rc2-mm2
- Prev by Date: Re: 2.6.12.2 acpi_register_gsi() patch causes problems on Asus A7V333 motherboard
- Next by Date: Re: [PATCH -rc2-mm2] BUG FIX - v4l broken hybrid dvb inclusion
- Previous by thread: Re: 2.6.13-rc2-mm2
- Next by thread: Re: 2.6.13-rc2-mm2
- Index(es):