| 2010-12-22 22:33:35 |
Nelson Elhage |
bug |
|
|
added bug |
| 2010-12-22 22:34:50 |
Nelson Elhage |
description |
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
[ 1437.041829] INFO: task rmmod:1608 blocked for more than 120 seconds.
[ 1437.044653] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1437.048064] rmmod D 0000000000000000 0 1608 1440 0x00000000
[ 1437.051240] ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
[ 1437.054695] ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
[ 1437.058218] 0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
[ 1437.061226] Call Trace:
[ 1437.061922] [<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[ 1437.063485] [<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[ 1437.064883] [<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[ 1437.066447] [<ffffffff8154178b>] wait_for_common+0xdb/0x180
[ 1437.067957] [<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[ 1437.069610] [<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[ 1437.071214] [<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[ 1437.072789] [<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[ 1437.074748] [<ffffffff81080754>] flush_workqueue+0x54/0x80
[ 1437.076234] [<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[ 1437.077732] [<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[ 1437.079286] [<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[ 1437.080721] [<ffffffff8109cbd4>] ? find_module+0x34/0x70
[ 1437.082188] [<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[ 1437.083784] [<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue
work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't
appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I can reproduce this bug on Karmic's kernel, but it does not seem to be present
in Maverick.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-25-generic 2.6.32-25.45
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: ksplice_1lie9lm5 ksplice_u18q23m7_vmlinux_new ksplice_u18q23m7 ksplice_63erbnhk_vmlinux_new ksplice_63erbnhk ksplice_3ttzyhci ksplice_8fdd0eeb_xfs_new ksplice_8fdd0eeb ksplice_zelykc16_vmlinux_new ksplice_zelykc16 ksplice_x6zz8imw ksplice_usjf73re ksplice_8wm26sii ksplice_w4khq8o9 ksplice_im08wyhr ksplice_1ndthrri ksplice_wniswd30 ksplice_pn1puy67 ksplice_gm6xc1gu ksplice_1uajjecp ksplice_hm5sowqz_vmlinux_new ksplice_hm5sowqz ksplice_mjex9nuz_vmlinux_new ksplice_mjex9nuz ksplice_2wopjp26_vmlinux_new ksplice_2wopjp26 openafs nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: nelhage 2858 F.... pulseaudio
/dev/snd/pcmC0D0p: nelhage 2858 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 22'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,18490890,00100101'
Controls : 38
Simple ctrls : 22
Date: Wed Dec 22 17:22:52 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic root=/dev/mapper/vg-root ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.2
RfKill:
SourcePackage: linux
dmi.bios.date: 11/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: X58 Extreme
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/06/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M. |
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
[ 1437.041829] INFO: task rmmod:1608 blocked for more than 120 seconds.
[ 1437.044653] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1437.048064] rmmod D 0000000000000000 0 1608 1440 0x00000000
[ 1437.051240] ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
[ 1437.054695] ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
[ 1437.058218] 0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
[ 1437.061226] Call Trace:
[ 1437.061922] [<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[ 1437.063485] [<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[ 1437.064883] [<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[ 1437.066447] [<ffffffff8154178b>] wait_for_common+0xdb/0x180
[ 1437.067957] [<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[ 1437.069610] [<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[ 1437.071214] [<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[ 1437.072789] [<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[ 1437.074748] [<ffffffff81080754>] flush_workqueue+0x54/0x80
[ 1437.076234] [<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[ 1437.077732] [<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[ 1437.079286] [<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[ 1437.080721] [<ffffffff8109cbd4>] ? find_module+0x34/0x70
[ 1437.082188] [<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[ 1437.083784] [<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I can reproduce this bug on Karmic's kernel, but it does not seem to be present in Maverick.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-25-generic 2.6.32-25.45
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: ksplice_1lie9lm5 ksplice_u18q23m7_vmlinux_new ksplice_u18q23m7 ksplice_63erbnhk_vmlinux_new ksplice_63erbnhk ksplice_3ttzyhci ksplice_8fdd0eeb_xfs_new ksplice_8fdd0eeb ksplice_zelykc16_vmlinux_new ksplice_zelykc16 ksplice_x6zz8imw ksplice_usjf73re ksplice_8wm26sii ksplice_w4khq8o9 ksplice_im08wyhr ksplice_1ndthrri ksplice_wniswd30 ksplice_pn1puy67 ksplice_gm6xc1gu ksplice_1uajjecp ksplice_hm5sowqz_vmlinux_new ksplice_hm5sowqz ksplice_mjex9nuz_vmlinux_new ksplice_mjex9nuz ksplice_2wopjp26_vmlinux_new ksplice_2wopjp26 openafs nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: nelhage 2858 F.... pulseaudio
/dev/snd/pcmC0D0p: nelhage 2858 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 22'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,18490890,00100101'
Controls : 38
Simple ctrls : 22
Date: Wed Dec 22 17:22:52 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic root=/dev/mapper/vg-root ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.2
RfKill:
SourcePackage: linux
dmi.bios.date: 11/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: X58 Extreme
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/06/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
|
|
| 2010-12-22 22:36:09 |
Nelson Elhage |
description |
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
[ 1437.041829] INFO: task rmmod:1608 blocked for more than 120 seconds.
[ 1437.044653] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1437.048064] rmmod D 0000000000000000 0 1608 1440 0x00000000
[ 1437.051240] ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
[ 1437.054695] ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
[ 1437.058218] 0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
[ 1437.061226] Call Trace:
[ 1437.061922] [<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[ 1437.063485] [<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[ 1437.064883] [<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[ 1437.066447] [<ffffffff8154178b>] wait_for_common+0xdb/0x180
[ 1437.067957] [<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[ 1437.069610] [<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[ 1437.071214] [<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[ 1437.072789] [<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[ 1437.074748] [<ffffffff81080754>] flush_workqueue+0x54/0x80
[ 1437.076234] [<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[ 1437.077732] [<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[ 1437.079286] [<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[ 1437.080721] [<ffffffff8109cbd4>] ? find_module+0x34/0x70
[ 1437.082188] [<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[ 1437.083784] [<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I can reproduce this bug on Karmic's kernel, but it does not seem to be present in Maverick.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-25-generic 2.6.32-25.45
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: ksplice_1lie9lm5 ksplice_u18q23m7_vmlinux_new ksplice_u18q23m7 ksplice_63erbnhk_vmlinux_new ksplice_63erbnhk ksplice_3ttzyhci ksplice_8fdd0eeb_xfs_new ksplice_8fdd0eeb ksplice_zelykc16_vmlinux_new ksplice_zelykc16 ksplice_x6zz8imw ksplice_usjf73re ksplice_8wm26sii ksplice_w4khq8o9 ksplice_im08wyhr ksplice_1ndthrri ksplice_wniswd30 ksplice_pn1puy67 ksplice_gm6xc1gu ksplice_1uajjecp ksplice_hm5sowqz_vmlinux_new ksplice_hm5sowqz ksplice_mjex9nuz_vmlinux_new ksplice_mjex9nuz ksplice_2wopjp26_vmlinux_new ksplice_2wopjp26 openafs nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: nelhage 2858 F.... pulseaudio
/dev/snd/pcmC0D0p: nelhage 2858 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 22'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,18490890,00100101'
Controls : 38
Simple ctrls : 22
Date: Wed Dec 22 17:22:52 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic root=/dev/mapper/vg-root ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.2
RfKill:
SourcePackage: linux
dmi.bios.date: 11/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: X58 Extreme
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/06/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
|
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
INFO: task rmmod:1608 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rmmod D 0000000000000000 0 1608 1440 0x00000000
ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
Call Trace:
[<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[<ffffffff8154178b>] wait_for_common+0xdb/0x180
[<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[<ffffffff81080754>] flush_workqueue+0x54/0x80
[<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[<ffffffff8109cbd4>] ? find_module+0x34/0x70
[<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I can reproduce this bug on Karmic's kernel, but it does not seem to be present in Maverick.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-25-generic 2.6.32-25.45
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: ksplice_1lie9lm5 ksplice_u18q23m7_vmlinux_new ksplice_u18q23m7 ksplice_63erbnhk_vmlinux_new ksplice_63erbnhk ksplice_3ttzyhci ksplice_8fdd0eeb_xfs_new ksplice_8fdd0eeb ksplice_zelykc16_vmlinux_new ksplice_zelykc16 ksplice_x6zz8imw ksplice_usjf73re ksplice_8wm26sii ksplice_w4khq8o9 ksplice_im08wyhr ksplice_1ndthrri ksplice_wniswd30 ksplice_pn1puy67 ksplice_gm6xc1gu ksplice_1uajjecp ksplice_hm5sowqz_vmlinux_new ksplice_hm5sowqz ksplice_mjex9nuz_vmlinux_new ksplice_mjex9nuz ksplice_2wopjp26_vmlinux_new ksplice_2wopjp26 openafs nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: nelhage 2858 F.... pulseaudio
/dev/snd/pcmC0D0p: nelhage 2858 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 22'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,18490890,00100101'
Controls : 38
Simple ctrls : 22
Date: Wed Dec 22 17:22:52 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic root=/dev/mapper/vg-root ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.2
RfKill:
SourcePackage: linux
dmi.bios.date: 11/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: X58 Extreme
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/06/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
|
|
| 2010-12-22 22:37:15 |
Nelson Elhage |
description |
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
INFO: task rmmod:1608 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rmmod D 0000000000000000 0 1608 1440 0x00000000
ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
Call Trace:
[<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[<ffffffff8154178b>] wait_for_common+0xdb/0x180
[<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[<ffffffff81080754>] flush_workqueue+0x54/0x80
[<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[<ffffffff8109cbd4>] ? find_module+0x34/0x70
[<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I can reproduce this bug on Karmic's kernel, but it does not seem to be present in Maverick.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-25-generic 2.6.32-25.45
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: ksplice_1lie9lm5 ksplice_u18q23m7_vmlinux_new ksplice_u18q23m7 ksplice_63erbnhk_vmlinux_new ksplice_63erbnhk ksplice_3ttzyhci ksplice_8fdd0eeb_xfs_new ksplice_8fdd0eeb ksplice_zelykc16_vmlinux_new ksplice_zelykc16 ksplice_x6zz8imw ksplice_usjf73re ksplice_8wm26sii ksplice_w4khq8o9 ksplice_im08wyhr ksplice_1ndthrri ksplice_wniswd30 ksplice_pn1puy67 ksplice_gm6xc1gu ksplice_1uajjecp ksplice_hm5sowqz_vmlinux_new ksplice_hm5sowqz ksplice_mjex9nuz_vmlinux_new ksplice_mjex9nuz ksplice_2wopjp26_vmlinux_new ksplice_2wopjp26 openafs nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: nelhage 2858 F.... pulseaudio
/dev/snd/pcmC0D0p: nelhage 2858 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 22'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,18490890,00100101'
Controls : 38
Simple ctrls : 22
Date: Wed Dec 22 17:22:52 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic root=/dev/mapper/vg-root ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.2
RfKill:
SourcePackage: linux
dmi.bios.date: 11/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: X58 Extreme
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/06/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
|
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
INFO: task rmmod:1608 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rmmod D 0000000000000000 0 1608 1440 0x00000000
ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
Call Trace:
[<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[<ffffffff8154178b>] wait_for_common+0xdb/0x180
[<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[<ffffffff81080754>] flush_workqueue+0x54/0x80
[<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[<ffffffff8109cbd4>] ? find_module+0x34/0x70
[<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I can reproduce this bug on Karmic's kernel, but it does not seem to be present in Maverick.
[deleting all the apport crap because I can reproduce this on a stock LiveCD, so it's just noise]
|
|
| 2011-01-05 15:05:33 |
Nelson Elhage |
affects |
linux (Ubuntu) |
libcgroup (Ubuntu) |
|
| 2011-01-05 15:05:54 |
Nelson Elhage |
summary |
rmmod hangs if cgroup-bin is installed |
cgroup-bin should not move kthreadd into a default cgroup |
|
| 2011-01-05 15:07:11 |
Nelson Elhage |
description |
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
INFO: task rmmod:1608 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rmmod D 0000000000000000 0 1608 1440 0x00000000
ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
Call Trace:
[<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[<ffffffff8154178b>] wait_for_common+0xdb/0x180
[<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[<ffffffff81080754>] flush_workqueue+0x54/0x80
[<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[<ffffffff8109cbd4>] ? find_module+0x34/0x70
[<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I can reproduce this bug on Karmic's kernel, but it does not seem to be present in Maverick.
[deleting all the apport crap because I can reproduce this on a stock LiveCD, so it's just noise]
|
Steps to reproduce:
1. Install cgroup-bin from universe on a stock Lucid machine (I've only tested amd64, but I suspect it shouldn't matter)
2. Load an arbitrary module (e.g. modprobe rds)
3. Unload the module loaded in (2) (e.g. rmmod rds)
The 'rmmod' process will hang unkillably in the kernel.
Here's an example `dmesg` output from the hung-task watchdog for rmmod:
INFO: task rmmod:1608 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rmmod D 0000000000000000 0 1608 1440 0x00000000
ffff880014245c78 0000000000000082 0000000000015bc0 0000000000015bc0
ffff880014804890 ffff880014245fd8 0000000000015bc0 ffff8800148044d0
0000000000015bc0 ffff880014245fd8 0000000000015bc0 ffff880014804890
Call Trace:
[<ffffffff81541b6d>] schedule_timeout+0x22d/0x300
[<ffffffff812b8716>] ? rb_erase+0xd6/0x160
[<ffffffff81052a10>] ? __dequeue_entity+0x30/0x50
[<ffffffff8154178b>] wait_for_common+0xdb/0x180
[<ffffffff8105a220>] ? default_wake_function+0x0/0x20
[<ffffffff815418ed>] wait_for_completion+0x1d/0x20
[<ffffffff8107fe55>] flush_cpu_workqueue+0x65/0xa0
[<ffffffff8107ff10>] ? wq_barrier_func+0x0/0x20
[<ffffffff81080754>] flush_workqueue+0x54/0x80
[<ffffffff810b5b24>] __stop_machine+0xf4/0x120
[<ffffffff8109d8c0>] ? __try_stop_module+0x0/0x50
[<ffffffff810b5d7e>] stop_machine+0x3e/0x60
[<ffffffff8109cbd4>] ? find_module+0x34/0x70
[<ffffffff8109e1ee>] sys_delete_module+0x17e/0x270
[<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
The process is waiting on kstop/0 to wake up and service the stop_cpu workqueue work item that it has queued. kstop/0 is marked as TASK_RUNNABLE, but doesn't appear to ever be getting scheduled:
$ ps -f 1609
UID PID PPID C STIME TTY STAT TIME CMD
root 1609 2 0 14:47 ? R 0:00 [kstop/0]
$ cat /proc/1609/stack
[<ffffffff8107fb6a>] worker_thread+0xda/0x110
[<ffffffff81084206>] kthread+0x96/0xa0
[<ffffffff810131ea>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
I tracked this behavior down and reported it to the upstream kernel, but they say it's not a bug and that it's libcgroup's fault for moving kthreadd into a cgroup without RT privs: https://lkml.org/lkml/2011/1/5/53
|
|
| 2011-04-22 17:21:53 |
Serge Hallyn |
libcgroup (Ubuntu): status |
New |
Confirmed |
|
| 2011-04-22 17:21:57 |
Serge Hallyn |
libcgroup (Ubuntu): importance |
Undecided |
High |
|
| 2011-04-25 13:03:50 |
Serge Hallyn |
libcgroup (Ubuntu): assignee |
|
Jon Bernard (jbernard) |
|
| 2011-10-11 13:40:03 |
Walter Richards |
bug |
|
|
added subscriber Walter Richards |
| 2012-05-14 15:50:56 |
SaveTheRbtz |
bug |
|
|
added subscriber SaveTheRbtz |
| 2013-01-17 04:07:07 |
Tomofumi |
bug |
|
|
added subscriber Tomofumi |
| 2013-02-12 18:19:48 |
Ayke |
bug |
|
|
added subscriber Ayke van Laethem |
| 2013-10-31 00:08:22 |
Jon Bernard |
libcgroup (Ubuntu): assignee |
Jon Bernard (jbernard) |
|
|
| 2017-08-08 22:53:17 |
SaveTheRbtz |
removed subscriber SaveTheRbtz |
|
|
|
