hi

i use suse 9.1 i have many warning and error when i boot...
i can see it in /var/log/message


hi

i use suse 9.1 and when i boot i get this error in /var/log/messages

WARNING in Function ACPI_Interface; line 26: could not set battery alarm, you may need to force polling mode.

linux [powersaved][2331]: resmgr: server response code 200
linux [powersave_proxy][2407]: WARNING: hdparm returned error 5

linux kernel: Symbols match kernel version 2.6.5.
linux kernel: No module symbols loaded - kernel modules not enabled.

linux kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
linux kernel: hda: drive_cmd: error=0x04 { DriveStatusError }

via_ircc: unsupported module, tainting kernel.

linux ifup: No configuration found for sit0

linux kernel: sym0: SCSI parity error detected: SCR1=132 DBC=50000000 SBCL=0
linux kernel: Non-volatile memory driver v1.2
linux kernel: end_request: I/O error, dev fd0, sector 0
linux kernel: end_request: I/O error, dev fd0, sector 0
linux kernel: sym0: SCSI parity error detected: SCR1=132 DBC=2440a04 SBCL=0

linux /etc/hotplug/block.agent[3357]: grep: /sys/class/scsi_host/ide1/proc_name: No such file or directory
Sep 13 23:07:34 linux /etc/hotplug/block.agent[3357]: grep: /sys/class/scsi_host/ide1/proc_name: No such file or directory

linux /etc/hotplug/block.agent[3357]: new block device /block/hdc
linux kernel: sym0: SCSI parity error detected: SCR1=132 DBC=2440a04 SBCL=0
linux kernel: eth0: no IPv6 routers present
linux kernel: sym0: SCSI parity error detected: SCR1=132 DBC=2440a04 SBCL=0
linux kernel: sym0:0: ERROR (81:0) (a-0-0) (f/9d/0) @ (mem d136a328:ffffffff).
linux kernel: sym0: regdump: da 00 40 9d 47 0f 00 0e 00 0a 80 00 80 00 0f 0a 30 30 71 1f 02 ff ff ff.
linux kernel: sym0: SCSI BUS reset detected.
linux kernel: sym0: SCSI BUS has been reset.
linux kernel: st: Version 20040318, fixed bufsize 32768, s/g segs 256
linux kernel: sym0:4: FAST-20 SCSI 20.0 MB/s ST (50.0 ns, offset 16)
linux kernel: sr0: scsi-1 drive
linux kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
linux kernel: sym0:6: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 15)
linux kernel: sr1: scsi-1 drive
linux kernel: Attached scsi CD-ROM sr1 at scsi0, channel 0, id 6, lun 0
linux kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,type 0
linux kernel: Attached scsi generic sg1 at scsi0, channel 0, id 4, lun 0,type 5
linux kernel: Attached scsi generic sg2 at scsi0, channel 0, id 6, lun 0,type 5
linux kernel: BIOS EDD facility v0.13 2004-Mar-09, 2 devices found
linux /etc/hotplug/block.agent[3498]: 0:0:4:0: sg_io failed status 0x0 0x0 0x0 0x2

linux /etc/hotplug/block.agent[3498]: 0:0:4:0: sense key 0x5 ASC 0x24 ASCQ 0x0
linux /etc/hotplug/scsi_generic.agent[3587]: 0:0:4:0: sg_io failed status 0x0 0x0 0x0 0x2
linux /etc/hotplug/scsi_generic.agent[3587]: 0:0:4:0: sense key 0x5 ASC 0x24 ASCQ 0x0
linux /etc/hotplug/block.agent[3498]: new block device /block/sr0
linux kernel: sym0: SCSI parity error detected: SCR1=132 DBC=50000000 SBCL=0
linux kernel: sym0:4:0: ABORT operation started.
linux kernel: sym0:4:0: ABORT operation timed-out.
linux kernel: sym0:6:0: ABORT operation started.
linux kernel: sym0:6:0: ABORT operation timed-out.
linux kernel: sym0:4:0: DEVICE RESET operation started.
linux kernel: sym0:4:0: DEVICE RESET operation timed-out.
linux kernel: sym0:6:0: DEVICE RESET operation started.
linux kernel: sym0:6:0: DEVICE RESET operation timed-out.
linux kernel: sym0:4:0: BUS RESET operation started.
linux kernel: sym0: SCSI BUS reset detected.
linux kernel: sym0: SCSI BUS has been reset.
linux kernel: sym0:4:0: BUS RESET operation complete.

any idea to resolve any of theses problem?

thanks

I don't know that much about the kernel, but seeing that no one has responded to this in 4 days, I'll throw some wild guesses at it.

The first error has to do with power saving features, do you own a laptop? Does it boot up all the way? If it does, have you noticed any other symptoms? Has it always done this, or did it start suddenly? Have you recompiled your kernel yourself (something may have gone wrong with the compile/module install)?

Your system may not be correctly detecting hardware. I have seen other threads describing kernel parameters to use different hardware detection schemes. a portion of your kernel or a module may be corrupted.

If I knew as much as I wish (and will) know then I could be of more help. I hope I've thought of something that you haven't already checked (assuming I'm not completely out to lunch.)