| 2007-06-17 17:40:17 |
Chris Lin |
bug |
|
|
added bug |
| 2007-06-18 17:22:01 |
Brian Murray |
None: status |
Unconfirmed |
Needs Info |
|
| 2007-06-18 17:22:01 |
Brian Murray |
None: assignee |
|
brian-murray |
|
| 2007-06-18 17:22:01 |
Brian Murray |
None: statusexplanation |
|
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Your kernel messages log file '/var/log/messages' may also be helpful so please attach it to your bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance! |
|
| 2007-06-18 19:15:52 |
Chris Lin |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2007-06-18 19:16:42 |
Chris Lin |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2007-06-18 19:17:25 |
Chris Lin |
bug |
|
|
added attachment 'messages' (messages) |
| 2007-06-18 20:14:13 |
Brian Murray |
description |
Ubuntu 7.04 Feisty Fawn will lock up completely within 2-30 minutes of using it. I have done numerous searches on Google, forums, etc. and while many people have posted solutions, none of them have worked for my computer (noapic, changing CPU scaling, different kernels, etc.). When it freezes I cannot do anything (no ctrl-alt-backspace, no ctrl-alt-F1, etc.) so I have to press the power button to turn the computer off and back on again. Interestingly, using the default 'ati' driver I cannot do anything but using the propietary fglrx drivers lets me move the mouse cursor around, but nothing responds.
It is definitely not an overheating issue as I've watched the system temp before it crashes and it remains cool.
Here are my system specs, I'm running a dual-boot with Windows XP
P4 2.6 Ghz (tried it with hyper threading enabled and disabled)
ABIT IS-7 Motherboard (using the onboard ethernet)
1024 MB RAM (memtest checks out)
ATI Radeon 9700 Pro (ati drivers and fglrx drivers)
Soundblaster Audigy 2
2 Western Digital Hard Drives, one with a dual NTFS/ext3 partition |
Ubuntu 7.04 Feisty Fawn will lock up completely within 2-30 minutes of using it. I have done numerous searches on Google, forums, etc. and while many people have posted solutions, none of them have worked for my computer (noapic, changing CPU scaling, different kernels, etc.). When it freezes I cannot do anything (no ctrl-alt-backspace, no ctrl-alt-F1, etc.) so I have to press the power button to turn the computer off and back on again. Interestingly, using the default 'ati' driver I cannot do anything but using the propietary fglrx drivers lets me move the mouse cursor around, but nothing responds.
It is definitely not an overheating issue as I've watched the system temp before it crashes and it remains cool.
Here are my system specs, I'm running a dual-boot with Windows XP
P4 2.6 Ghz (tried it with hyper threading enabled and disabled)
ABIT IS-7 Motherboard (using the onboard ethernet)
1024 MB RAM (memtest checks out)
ATI Radeon 9700 Pro (ati drivers and fglrx drivers)
Soundblaster Audigy 2
2 Western Digital Hard Drives, one with a dual NTFS/ext3 partition
Found in dmesg.log:
ATA: abnormal status 0x7F on port 0x0001c807 |
|
| 2007-06-18 20:14:27 |
Brian Murray |
linux-source-2.6.20: status |
Needs Info |
Confirmed |
|
| 2007-06-18 20:14:27 |
Brian Murray |
linux-source-2.6.20: importance |
Undecided |
Medium |
|
| 2007-06-18 20:14:27 |
Brian Murray |
linux-source-2.6.20: statusexplanation |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Your kernel messages log file '/var/log/messages' may also be helpful so please attach it to your bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance! |
|
|
| 2007-06-18 20:14:27 |
Brian Murray |
linux-source-2.6.20: assignee |
brian-murray |
ubuntu-kernel-team |
|
| 2008-08-29 11:04:21 |
Leann Ogasawara |
bug |
|
|
added subscriber Leann Ogasawara |
| 2009-09-11 06:24:29 |
Keng-Yu Lin |
linux (Ubuntu): status |
Incomplete |
Won't Fix |
|
