search for: read_intr

...ines for this sort of thing. There are two machines with identical hardware, both running Red Hat 7.3's stock SMP kernel (required due to third party software). Both have come down with the same symptoms after having run fine for a number of months. The initial errors were these: kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=54666719, high=3, low=4335071, sector=61720 kernel: end_request: I/O error, dev 03:09 (hda), sector 61720 kernel: journal_bmap_Rsmp_41b34d97: journal block not found at offs...

...[<d081ca48>] [<d081cfa6>] [<d081ca48>] [<c01265c8>] [<d081aa7b>] [<c0130ec9>] [<d081aa5c>] [<d080f777>] [<d081ab0f>] [<c0130fe1>] [<c0106dd3>] Code: 0f 0b 5b 5e 8b 54 24 24 f6 42 10 04 bb e2 ff ff ff b8 01 00 hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854, sector=163854 end_request: I/O error, dev 03:02 (hda), sector 163854 EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=20100, block=81927 hd...

All, Trying to figure out how to deal with, I assume, a dying disk that's unfortunately on / (ext3). Getting errors similar to: Dec 31 20:44:30 mybox kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 31 20:44:30 mybox kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=163423, high=0, low=163423, sector=163360 Dec 31 20:44:30 mybox kernel: end_request:

Any unpriveledged user can abuse the syslog facility in an interesting way. The following example is a good one that can put misleading information in the logs. ------------------------------- #include <syslog.h> void main(void){ const char *mesg1 = "hda: read_intr: status=0x59 { SeekComplete DataRequest Error } { UncorrectableError }, CHS=157/2/9, sector=2826\0"; const char *mesg2 ="end_request: I/O error, dev 03:00, sector 2826\0"; const char *mesg3 = "EXT2-fs: group descriptors corrupted !\0"; openlog("kernel", LOG_CO...

Hi, yesterday my linux machine gave me some smartd errors so i checked the disk in another machine and it had defective sectors, I installed a new hard disk on the original machine. Today this is being reported in logwatch. I have a Maxtor (200gig) as hda, a cdrom as hdc and another hard disk that is used for storage as hdd. All plain IDE (not sata) --------------------- Kernel Begin

Hi, I'm trying to setup a small BRI ISDN <-> voip gateway. The ISDN card is based on Cologne chipset, so I try set it up with zaphfc. The versions i'm running: kernel-2.4.27 Asterisk 1.0.7-BRIstuffed-0.2.0-RC8e zaptel modules 1.0.7 zaphfc is from bristuff-0.2.0-RC8e When I'm doing the insmod on zaptel, zaphfc, zaprtc: Zapata Telephony Interface Registered on major 196 PCI: