Laptop crashes after running for a week (NTFS?)

Bug #187893 reported by Pete MacKay on 2008-01-31
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

I've been running Ubuntu 7.10 on a HP/Compaq nc6320 laptop with Intel CoreDuo (2x T2400 @ 1.83 GHz), 1 GB memory, and SATA drive with ext3, swap, FAT32, and NTFS partitions, as it's a dual-boot with Win XP sp2. During the work-week I typically run Thunderbird (with FAT32 profile shared with Windows), Firefox, gedit and various GNU cross tools (I'm an embedded systems developer), and sometimes stream MP3 with vlc and/or Amarok from the NTFS partition. The laptop runs 24/7, but after a few days crashes with both CPUs pegged. At first I assumed it was one of the music players leaking memory, so I stopped using them, but now I've discovered the problem happens consistently as long as I have an NTFS partition mounted. When I don't mount any NTFS partitions (which I also have on two USB hard drives I occasionally use) I don't have the problem. Memory seems to increase over time, but the crash doesn't seem caused by a memory leak, as there's plenty of free memory when it happens. It's only after I've had NTFS mounted and probably have read some files (I never write to NTFS, at least not intentionally). dmesg and the logs don't seem to indicate anything going awry when the mouse starts having a hard time moving around, which is my indication the crash is on its way.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

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.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers