| 2007-12-07 18:35:28 |
Montana Harkin |
bug |
|
|
added bug |
| 2007-12-07 18:36:49 |
Montana Harkin |
bug |
|
|
added attachment 'resize2fs_kernel_panic.txt' (resize2fs_kernel_panic.txt) |
| 2007-12-07 18:37:14 |
Montana Harkin |
bug |
|
|
added attachment 'resize2fs_kernel_panic_messages.txt' (resize2fs_kernel_panic_messages.txt) |
| 2008-08-25 22:30:16 |
Theodore Ts'o |
bug |
|
|
assigned to linux (Ubuntu) |
| 2008-08-25 22:32:56 |
Theodore Ts'o |
e2fsprogs: status |
New |
Invalid |
|
| 2008-08-25 22:32:56 |
Theodore Ts'o |
e2fsprogs: statusexplanation |
|
By definition a kernel panic is a linux kernel problem and not a userspace bug. There should be nothing that a user program can do that should be able to trigger a kernel panic, without a kernel bug. In this case, the bug isn't even in any ext3 filesystem code, but rather a kernel soft lockup while doing some block device I/O. 2.6.20 is a rather old kernel, so it would be interesting to see if the problem can be reproduced on a more modern kernel.
|
|
| 2008-08-26 09:51:36 |
Marcus Asshauer |
linux: status |
New |
Invalid |
|
| 2008-08-26 09:51:36 |
Marcus Asshauer |
linux: statusexplanation |
|
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find. |
|
