[opensuse] On my SUSE linux 10.1 kernel: ide: failed opcode was 0xef
Hello,
On my laptop I just started getting this error below about 3 weeks ago. I
have tried to track it down, but I have been unsuccessfule. The message
in the log is...
Dec 6 06:33:35 blg kernel: ide: failed opcode was: 0xef
This is the last message in logs and then I am not able to close any
windows in KDE or write to the HD. The only way to get things to work is
a power off. I have been unable to track down what is causing this
problem. It can happen from an hour to 6 days. That is the longest I
have made it. I have another laptop which is almost exactly the same and
it never happens. Any ideas on how to find the cause? I do notice that
the machine near the right side of the keyboard some times is a bit warm,
but I am not sure if that is the problem. If the machine is hung and I go
to one of my X-terms on the machine I quicly find out that it is hung. An
other symtom is the clock in the lower right conner stops advancing. Also
the repeat on the arrow keys stops functioning.
Thanks,
--
Boyd Gerber
On Thursday 07 December 2006 13:45, Boyd Lynn Gerber wrote:
Hello,
On my laptop I just started getting this error below about 3 weeks ago. I have tried to track it down, but I have been unsuccessfule. The message in the log is...
Dec 6 06:33:35 blg kernel: ide: failed opcode was: 0xef
This is the last message in logs and then I am not able to close any windows in KDE or write to the HD. The only way to get things to work is a power off. I have been unable to track down what is causing this problem. It can happen from an hour to 6 days. That is the longest I have made it. I have another laptop which is almost exactly the same and it never happens. Any ideas on how to find the cause? I do notice that the machine near the right side of the keyboard some times is a bit warm, but I am not sure if that is the problem. If the machine is hung and I go to one of my X-terms on the machine I quicly find out that it is hung. An other symtom is the clock in the lower right conner stops advancing. Also the repeat on the arrow keys stops functioning.
Thanks,
If the drive is SMART capable, it might be an idea to install smartmontools, enable monitoring on the drive and see if the temp. is fluctuating beforehand. You should find lots of info in /var/log/messages.. Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 7 Dec 2006, Pete Connolly wrote:
On Thursday 07 December 2006 13:45, Boyd Lynn Gerber wrote:
On my laptop I just started getting this error below about 3 weeks ago. I have tried to track it down, but I have been unsuccessfule. The message in the log is...
Dec 6 06:33:35 blg kernel: ide: failed opcode was: 0xef
If the drive is SMART capable, it might be an idea to install smartmontools, enable monitoring on the drive and see if the temp. is fluctuating beforehand. You should find lots of info in /var/log/messages..
They are and I do not get any messages there only the one above. That is
why this is so frustrating.
Thanks,
--
Boyd Gerber
On Thursday 07 December 2006 14:21, Boyd Lynn Gerber wrote:
On Thu, 7 Dec 2006, Pete Connolly wrote:
On Thursday 07 December 2006 13:45, Boyd Lynn Gerber wrote:
On my laptop I just started getting this error below about 3 weeks ago. I have tried to track it down, but I have been unsuccessfule. The message in the log is...
Dec 6 06:33:35 blg kernel: ide: failed opcode was: 0xef
If the drive is SMART capable, it might be an idea to install smartmontools, enable monitoring on the drive and see if the temp. is fluctuating beforehand. You should find lots of info in /var/log/messages..
They are and I do not get any messages there only the one above. That is why this is so frustrating.
Thanks,
Very strange. Have you tried just doing a smartctl -H /dev/<drive> to check it's health? Or maybe seeing it capabilities with smartctl -c /dev/<drive>? Just to see if smart can do useful things will it. Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 07 December 2006 09:45, Pete Connolly wrote: <snip>
Very strange. Have you tried just doing a smartctl -H /dev/<drive> to check it's health? Or maybe seeing it capabilities with smartctl -c /dev/<drive>? Just to see if smart can do useful things will it.
Another approach is to check the drive manufacturer's website for downloadable diagnostic tools that can be run from a floppy or CD. Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 7 Dec 2006, Carl Hartung wrote:
On Thursday 07 December 2006 09:45, Pete Connolly wrote: <snip>
Very strange. Have you tried just doing a smartctl -H /dev/<drive> to check it's health? Or maybe seeing it capabilities with smartctl -c /dev/<drive>? Just to see if smart can do useful things will it.
Another approach is to check the drive manufacturer's website for downloadable diagnostic tools that can be run from a floppy or CD.
I have the problem on the same computer with any one of 4 newly purchased
HD's. I can move them to the other lappy's and they never fail. On
yesterday's 6:00-6:30 AM failure I turned off HT support in the BIOS. I
have not tried it this way. This has been going on with 10.1 for 6-8
weeks. When I run the utilites before failure everything works great.
But after the failure when I try to run them the machine just hangs and
the only message it the one posted. Really strange.
Thanks,
--
Boyd Gerber
On Thursday December 7 2006 1:13 pm, Boyd Lynn Gerber wrote:
I have the problem on the same computer with any one of 4 newly purchased HD's. I can move them to the other lappy's and they never fail. On yesterday's 6:00-6:30 AM failure I turned off HT support in the BIOS. I have not tried it this way. This has been going on with 10.1 for 6-8 weeks. When I run the utilites before failure everything works great. But after the failure when I try to run them the machine just hangs and the only message it the one posted. Really strange.
Thanks, Boyd Gerber
Well its either hardware or software... but seriously, I'm hearing symptoms of both from your descriptions. If these drives were working in this machine prior to any updates and are now failing then I'd suspect a kernel update as the culprit. Have you checked for any updated BIOS or firmwares for this system? Is this a different system/chipset than the other laptops? What changed 6-8 weeks ago on this system or drives? Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I had a similar problem with my hard drives and the cpu running wild. Turns out it was a loose connector on the hard drive. I thought the drive was going bad. I just reset the ide cable and everything has been OK. May or may not be related. Terry -- SUSE LINUX 10.1 (i586) -- 2.6.16.21-0.25-default -- Thu 12/07/06 8:50pm up 8 days 0:36, 4 users, load average: 0.42, 0.34, 0.31 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 7 Dec 2006, Terry Eck wrote:
I had a similar problem with my hard drives and the cpu running wild. Turns out it was a loose connector on the hard drive. I thought the drive was going bad. I just reset the ide cable and everything has been OK. May or may not be related. Terry
I ran the memtest for 48 hours no problem. Booted into 10.1 died within
an hour. Powered it off it then ran for 6 days with out a problem. I
have swaped the HD, tried different filesystem, including encrypting the
entire /home partition. Does not seem to matter. I disable HT for the
first time Wed 06 Dec 06 at 06:30 AM MDT. I just thought I should ask as
this has been happening randomly for about 6-8 weeks. I really have no
clue what is causing it. Shortest time was 1 hour longest was 6 days 23
hours and 32 minutes. I will have to wait and see if disabling HT works.
--
Boyd Gerber
Boyd Lynn Gerber wrote:
On my laptop I just started getting this error below about 3 weeks ago. I have tried to track it down, but I have been unsuccessfule. The message in the log is...
Dec 6 06:33:35 blg kernel: ide: failed opcode was: 0xef
This is the last message in logs and then I am not able to close any windows in KDE or write to the HD. The only way to get things to work is a power off. I have been unable to track down what is causing this problem. It can happen from an hour to 6 days. That is the longest I have made it. I have another laptop which is almost exactly the same and it never happens. Any ideas on how to find the cause? I do notice that the machine near the right side of the keyboard some times is a bit warm, but I am not sure if that is the problem. If the machine is hung and I go to one of my X-terms on the machine I quicly find out that it is hung. An other symtom is the clock in the lower right conner stops advancing. Also the repeat on the arrow keys stops functioning.
It might be completely unrelated, but you never know... I have similar problems on one of my laptops running SuSE 10.0. The problems started some weeks ago. Sometimes, I recognise that the "load" starts to increase (xosview is running all the time) - from this point on, I am no longer able to close windows or switch to other desktops. The mouse is still working. If the focus is on a terminal window, I can still enter a command and press "return" but nothing happens. The load is increasing to about 25 and then more or less everything stops working (keyboard no longer responding, etc.). There is no information in /var/log/messages. I've checked memory with memtest86 over night: no problems. I've check the disk with the manufacturer's disk tool (it's a WD disk): no problems. I haven't been able to figure out the trigger for those problems. It might happen any time. The only solution is a power off. Other laptops here (also SuSE 10.0) work without such problems... Cheers, Th. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 7 Dec 2006, Boyd Lynn Gerber wrote:
On my laptop I just started getting this error below about 3 weeks ago. I have tried to track it down, but I have been unsuccessfule. The message in the log is...
Dec 6 06:33:35 blg kernel: ide: failed opcode was: 0xef
This is the last message in logs and then I am not able to close any windows in KDE or write to the HD. The only way to get things to work is a power off. I have been unable to track down what is causing this problem. It can happen from an hour to 6 days. That is the longest I have made it. I have another laptop which is almost exactly the same and it never happens. Any ideas on how to find the cause? I do notice that the machine near the right side of the keyboard some times is a bit warm, but I am not sure if that is the problem. If the machine is hung and I go to one of my X-terms on the machine I quicly find out that it is hung. An other symtom is the clock in the lower right conner stops advancing. Also the repeat on the arrow keys stops functioning.
It appears that disabling HT resolves the issue. I have not had a failure
since.(Knock on Wood)! I think I have now gone longer than the longest
prior lock up. So something in the later Kernel does not like my
processor being in HT mode. I think I will just leave it disabled. I
have to much to do right now to try and chase down the problem. Besides I
am going to move my laptop to 10.2. 10.2 seems to be a much better
release and seems faster.
Thanks to all the responses.
Thanks,
--
Boyd Gerber
participants (6)
-
Boyd Lynn Gerber -
Carl Hartung -
Pete Connolly -
Stan Glasoe -
Terry Eck -
Thomas Hertweck