PDA

View Full Version : Problem with 2.6.19-1.2895.fc6xen #1 SMP



Reisswolf
31st January 2007, 08:33 AM
Hi,

I know there is another thread about problems with 2.6.19-1.2895.fc6xen #1 SMP, but since my problem appears to be a bit different, I thought I would start a new thread. If I am doing something improper, feel free to let me know.

Yesterday I reinstalled Core 6 from the original CDs. Then I configured the livna repository and ran "yum update."

But now, when I boot, I get strange error messages when the HAL daemon tries to start up. I am pasting a portion of the output from dmesg below:



eth0: no IPv6 routers present
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 04 41 62 00 00 01 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 1115528
Buffer I/O error on device hdc, logical block 278882
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 04 41 63 00 00 01 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 1115532
Buffer I/O error on device hdc, logical block 278883
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 04 41 62 00 00 02 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 1115528
Buffer I/O error on device hdc, logical block 278882
Buffer I/O error on device hdc, logical block 278883
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 04 41 62 00 00 02 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 1115528
Buffer I/O error on device hdc, logical block 278882
Buffer I/O error on device hdc, logical block 278883
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 04 41 64 00 00 04 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 1115536
Buffer I/O error on device hdc, logical block 278884
Buffer I/O error on device hdc, logical block 278885
Buffer I/O error on device hdc, logical block 278886
Buffer I/O error on device hdc, logical block 278887
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 04 41 64 00 00 02 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 1115536
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 04 41 62 00 00 02 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 1115528
Bridge firewalling registered
device vif0.0 entered promiscuous mode
xenbr0: port 1(vif0.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
peth0: link up, 100Mbps, full-duplex, lpa 0x45E1
device peth0 entered promiscuous mode
xenbr0: port 2(peth0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 2(peth0) entering forwarding state
[drm] Initialized drm 1.0.1 20051102
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
[drm] Initialized i915 1.5.0 20060119 on minor 0
eth0: no IPv6 routers present
printk: 4 messages suppressed.
4gb seg fixup, process mono (pid 3765), cs:ip 73:081186b8
4gb seg fixup, process mono (pid 3765), cs:ip 73:00119e6f
4gb seg fixup, process mono (pid 3765), cs:ip 73:08118601
4gb seg fixup, process mono (pid 3765), cs:ip 73:001178a7
4gb seg fixup, process mono (pid 3765), cs:ip 73:08118601
4gb seg fixup, process mono (pid 3765), cs:ip 73:001178a7
4gb seg fixup, process mono (pid 3765), cs:ip 73:08118601
4gb seg fixup, process mono (pid 3765), cs:ip 73:001178a7
4gb seg fixup, process mono (pid 3765), cs:ip 73:08118601
4gb seg fixup, process mono (pid 3765), cs:ip 73:001178a7
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
printk: 77825 messages suppressed.
4gb seg fixup, process beagled (pid 3765), cs:ip 73:0811853f
printk: 69161 messages suppressed.
4gb seg fixup, process beagled (pid 3765), cs:ip 73:0811853f
printk: 9 messages suppressed.
4gb seg fixup, process beagled (pid 3765), cs:ip 73:0811853f
4gb seg fixup, process beagled (pid 3765), cs:ip 73:001178a7
4gb seg fixup, process beagled (pid 3765), cs:ip 73:08118601
4gb seg fixup, process beagled (pid 3765), cs:ip 73:00118464
4gb seg fixup, process beagled (pid 3765), cs:ip 73:0811853f
4gb seg fixup, process beagled (pid 3765), cs:ip 73:00117357
4gb seg fixup, process beagled (pid 3765), cs:ip 73:08118601
4gb seg fixup, process beagled (pid 3765), cs:ip 73:00118464
4gb seg fixup, process beagled (pid 3765), cs:ip 73:08118601
4gb seg fixup, process beagled (pid 3765), cs:ip 73:081198a0
printk: 338 messages suppressed.
4gb seg fixup, process mono (pid 4043), cs:ip 73:081186b8
4gb seg fixup, process mono (pid 4043), cs:ip 73:081186b8
4gb seg fixup, process mono (pid 4043), cs:ip 73:081186b8
4gb seg fixup, process mono (pid 4043), cs:ip 73:081186b8
4gb seg fixup, process mono (pid 4043), cs:ip 73:081186b8
printk: 147111 messages suppressed.
4gb seg fixup, process beagled (pid 4043), cs:ip 73:0811853f
printk: 7 messages suppressed.
4gb seg fixup, process beagled (pid 4043), cs:ip 73:0811853f
4gb seg fixup, process beagled (pid 4043), cs:ip 73:0012e8a7
4gb seg fixup, process beagled (pid 4043), cs:ip 73:08118601
4gb seg fixup, process beagled (pid 4043), cs:ip 73:0012f464
4gb seg fixup, process beagled (pid 4043), cs:ip 73:0811853f

This never happened before. Does anyone know what might be causing the error?

Thanks in advance for your help.

Reisswolf
31st January 2007, 09:11 AM
Just a quick update. I tried booting kernel 2795 Xen, which is the one that is packaged with my CDs--and the only other one I have besides this latest kernel--and the problem still exists. So I guess the problem is not one with the kernel.

But when what could be causing it? I had installed from those same CDs before, on this very computer, and I had never faced this problem. I wonder why all of a sudden this is happening.

If anyone has any pointers, I would be extremely grateful. The boot process goes well--until it tries to start HAL. That is when all the error messages start to show up.

Reisswolf
31st January 2007, 03:32 PM
I have a quick question for the oracles here. If it appears that the computer is functioning well in spite of those error messages, should I be worried about something?

Reisswolf
31st January 2007, 10:10 PM
I am actually embarrassed about writing this particular post. I thought long and hard about whether or not I should show my face here again, but I thought that there might be someone in this wide world who can benefit from my stupidity.

The problem was occurring because I had left a movie in the DVD drive. As soon as I took out the disc, the error messages went away.

I would like to apologise to those who read my original post and pondered over the problem for at least a little while.

Seve
31st January 2007, 10:26 PM
Hello:
No need to feel bad .... sheesh everyone goes through the same thing at one time or another. :) Or many times like me. :eek:
I was just about to ask you what device /hdc was, but I guess I know the answer now

Seve

Ninja_Unmatched
10th March 2007, 05:54 AM
Hello I have a similar if not same issue. When I updated and after reboot my hal daemon started acting crazy getting all kinds of errors. Only with mine they were more like Lost Interrupt. It looks like it keeps trying then goes to the other drives and fails on those too. What is all that about? I have an ATI X1600, pentium 4 3.0E HT. Using Livna ATI kmod driver. What is up with that new kernel? Or is it the kernel at all
I'm not having much luck in fedora world on my compuiter with its ASUS P4S800 board, SIS chipset with onboard audio and NIC. Not to mention all the video issues I have to jump hurdles to get through to finally get somewhere then updating blows everything out of the water... I hope more people respond to this. Might be the best idea to just do the first set of updates and then after that watch carfullt after that what it is updating (only update cetain things and leave the major updates alone until time passes)

Ninja_Unmatched
10th March 2007, 05:56 AM
There is not much in this Hal issue either. No one seems to know anything about it

Ninja_Unmatched
10th March 2007, 05:57 AM
Also why is it I can only get Fedora 6 to boot up with no freezes only when I install Xen???????????