Mailinglist Archive: opensuse-bugs (9716 mails)
| < Previous | Next > |
[Bug 335505] System freeze and crash because of pata_pdc202xx_old problems
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Thu, 8 Nov 2007 12:05:34 -0700 (MST)
- Message-id: <20071108190534.C5431245269@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=335505#c8
--- Comment #8 from Thomas Scholz <th.sch@xxxxxxx> 2007-11-08 12:05:34 MST ---
(In reply to comment #5 from Tejun Heo)
Ok. I could reproduce the freeze (in a few sec.) by doing a yes > test.out on
my backup hard disk. So I removed it and got no further system crash up to now.
I did some log file analyses in the past days and discovered that the last 3-4
system crashes was caused by the same (the removed) hard drive. Maybe there are
defect blocks, I can't check the device using the ibm/hitachi drive fitness
test because it is not able to start the tests on it. For other devices it
works without problems and no errors was found, also for one of the disks that
was connected to the Promise controller before I switched it to the onboard VIA
controller. I used it for recording tv shows using mythtv. After a few hours of
recording no write operations can be done but the file system is still mounted
rw (and not full ;) ). I'm not sure if this is a hardware defect or a kernel
issue, I assume that this kind of error will end up in a crash if the device is
connected to the Promise controller.
Because it is not a driver- or kernel task to work around potential broken
hardware I'm not sure how we should proceed. Maybe we can close this bug, on
the other hand I got this problems since I installed suse 10.2, using 10.3 it
is much better.
ATM the system is working fine without problems. At the weekend I will do some
tests again with the Promise Controller.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
--- Comment #8 from Thomas Scholz <th.sch@xxxxxxx> 2007-11-08 12:05:34 MST ---
(In reply to comment #5 from Tejun Heo)
Also, are the errors localized to one drive?
Ok. I could reproduce the freeze (in a few sec.) by doing a yes > test.out on
my backup hard disk. So I removed it and got no further system crash up to now.
I did some log file analyses in the past days and discovered that the last 3-4
system crashes was caused by the same (the removed) hard drive. Maybe there are
defect blocks, I can't check the device using the ibm/hitachi drive fitness
test because it is not able to start the tests on it. For other devices it
works without problems and no errors was found, also for one of the disks that
was connected to the Promise controller before I switched it to the onboard VIA
controller. I used it for recording tv shows using mythtv. After a few hours of
recording no write operations can be done but the file system is still mounted
rw (and not full ;) ). I'm not sure if this is a hardware defect or a kernel
issue, I assume that this kind of error will end up in a crash if the device is
connected to the Promise controller.
Because it is not a driver- or kernel task to work around potential broken
hardware I'm not sure how we should proceed. Maybe we can close this bug, on
the other hand I got this problems since I installed suse 10.2, using 10.3 it
is much better.
ATM the system is working fine without problems. At the weekend I will do some
tests again with the Promise Controller.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |