Displaying 20 results from an estimated 1100 matches similar to: "Problem with RH kernel 2.4.7-6"
2008 May 02
2
serial port in linux
hi,
i have centos 4.2. I have install a PCI card having serial port.
when the os is booted it detects the new hardware ( serial port) .a device is also created /dev/ttyS0. the port works very goog on the same pc in windows XP. but when i connect any serial device to that port in linux it does not work.
in /proc/ioports
there is entry for that port as
0000-001f : dma1
0020-003f :
2006 Oct 23
2
asterisk not detecting hangup
Hi,
Im working with the following versions:
-asterisk-1.2.12.1
-zaptel-1.2.9.1
And with the following card:
00:0d.0 Communication controller: Tiger Jet Network Inc. Tiger3XX
Modem/ISDN interface
Subsystem: Unknown device 8085:0003
Flags: bus master, medium devsel, latency 32, IRQ 201
I/O ports at c800 [size=256]
Memory at fe000000 (32-bit, non-prefetchable)
2004 Mar 05
2
PROBLEM: log abort over RAID5
Several people already reported this at linux-kernel and
elsewhere with no answers, I thought perhaps this would be a more
adequate forum...
[1.] One line summary of the problem:
After I/O, journal is aborted and filesystems made read-only.
[2.] Full description of the problem/report:
One can't anymore write to the affected file systems. Upon
investigation, ext3fs journal was aborted
2007 Jul 13
1
[memdisk] collision between memdisk and emm386 (FreeDOS)
Hi
I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy
disk image 8440kB size. I've put FreeDOS kernel and bootsector into the
floppy. Boot process goes fine with this command:
isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy
The problems begin when I try to run FreeDOS memory manager emm386 from the
floppy image.
my config.sys:
...
2006 Dec 27
5
Problem with ext3 filesystem
Hey,
I've a problem with an ext3 filesystem and don't know how to fix it or
find the failure :(
The Hardware:
Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with
400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and
avm isdn controller.
Couse of the filesystem problems I run memtest and found one bad memory
module which I replaced yet.
The
2004 Apr 14
2
Question about EXT3 error messages in /var/log/messages
Hello list
I've been having the following error messages pop up in my kernel log:
Apr 12 04:08:09 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir:
bad entry in directory #2670595: rec_len %% 4 != 0 - offset=0,
inode=827218527, rec_len=20275, name_len=73
Apr 12 04:08:14 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir:
bad entry in directory #2670596: rec_len %% 4 != 0 -
2002 Jan 06
3
puzzling error message
Hi
RedHat 7.2, ext3 on /, kernel 2.4.18p1.
whilst updatedb was running, i had these messages appear...
Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)):
ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 -
offset=0, inode=1651076143, rec_len=19527, name_len=85
Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)):
ext3_readdir: bad entry in directory
2003 Jul 24
4
filesystem broken / bad entry in directory #248447030
Jul 25 01:41:21 big kernel: EXT3-fs error (device device-mapper(254,16)):
ext3_readdir: bad entry in directory #248447030: rec_len %% 4 != 0 -
offset=0, inode=538976266, rec_len=14637, name_len=49
Jul 25 01:42:53 big kernel: EXT3-fs error (device device-mapper(254,16)):
ext3_readdir: bad entry in directory #248447030: rec_len %% 4 != 0 -
offset=0, inode=538976266, rec_len=14637, name_len=49
2007 Aug 29
1
SATA HardDisk IO error
I got the have install a SATA HardDisk on the machine recently. But
somethings the Disk cannot be accessed. And mesg tells that it is IO error.
Is it a hardware problem or system setting problem.
Here is the message from dmesg.
sd 0:0:0:0: SCSI error: return code = 0x00040000
> end_request: I/O error, dev sda, sector 27099199
> EXT3-fs error (device sda1): ext3_readdir: directory #1687553
2001 Nov 20
1
EXT3-fs error (device ide0(3,9)): ext3_readdir
Hi,
yesterday I upgraded my kernel to 2.4.15-pre6 (after months of using
only ac-kernels) and had my first ext3-error since 0.0.3 .
syslog tells me :
Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device ide0(3,9)):
ext3_readdir: bad entry in directory #47390: inode out of bounds -
offset=0, inode=404363549, rec_len=4096, name_len=23
and the system remounted /usr to ro.
I don't have
2001 Jun 22
2
EXT3-fs error: ext3_readdir: bad entry in directory
Hi. IIRC, I had the same problem with 2.4.3 and ext2, I'm not sure if with the same directory entry, but at the time fsck fixed without any problems. I only know that the error again is with my Mozilla sources.
The Mozilla sources are in another partition. I used lndir from my root fs to symlink everything and build it. At some point c++ segfaulted (happens a lot with my GCC 3.0), and I had
2004 Jun 23
2
Which disk is it?
Which disk is it?
/dev/sda6 or /dev/sdb8 or /dev/sdc6?
>From my log:
Jun 10 21:25:39 postamt1 kernel: attempt to access beyond end of device
Jun 10 21:25:39 postamt1 kernel: 08:06: rw=0, want=1680353324, limit=59954548
Jun 10 21:25:39 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_readdir: directory #3473659 contains a hole at offset 1852399616
$ mount
/dev/sdb6 on / type auto (rw)
2002 Feb 19
1
smbpasswd encryption (2.2.3a - RH 7.2 - kernel 2.4.7-10) Win2k
Hi listmembers,
due to a few very short but good tips from you guys and to much hassle with
my firewall (ipchains) I finally got samba running as a server and client (I
even made an update from source, just with normal ./configure, make, make
install after uninstalling the previous version of course).
With "encrypted passwords = no" everything is working fine (except for some
minor
2001 Dec 11
1
EXT3-fs error..bad entry in directory
Hello ext3-users,
We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25.
I noticed many of these errors in our logs.
EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory
#884828: directory entry across blocks - offset=0, inode=404600689,
rec_len=23080, name_len=59
EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory
#966714: rec_len % 4 != 0 -
2002 Aug 10
3
ext3_readdir error
Hi,
I am getting the following errors on /boot partition on a production
server running 2.4.18 kernel.
-------------
Aug 10 00:19:37 kernel: EXT3-fs error (device sd(8,1)):
ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal -
offset=0, inode=0, rec_len=0, name_len=0
-------------
/boot is not readable at all and attempt to do an ls will return the same
error.
2005 Feb 08
2
Ext3 Journal corruption on hitachi deskstars
I recently came across an enormous cluster of x86 clone machines running
fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE
chipsets.
They frequently experience corrupted journals rendering the ext3 partition
in read-only mode. More important than recovering the filesystem, I am
interested in finding the root of the problem.
The common hardware that all of these
2002 Apr 02
7
ext3 crash
Hi,
One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system.
These are the first errors in the log:
kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in
directory #2424833: rec_len is smaller than minimal - offset=0,
inode=2553887680, rec_len=0, name_len=0
kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in
directory #2424833: rec_len is
2006 Nov 09
2
USB disk dropping out under light load
Hi all,
I'm running a pretty updated CentOS4 x86_64 server (Still on kernel
2.6.9-42.0.2, but appart from that fully up to date against the official
repos) with a USB-disk attached (the USB-disk is a 750G Seagate disk in a
Seagate enclosure) over a USB hub.
I've noticed several times that after longish periods of activity, the disk
drops out (log from last time, below). In this case,
2015 Aug 22
32
[Bug 91722] New: [NVE4] PGRAPH - grctx template channel unload timeout, failed to construct context, init failed, -16
https://bugs.freedesktop.org/show_bug.cgi?id=91722
Bug ID: 91722
Summary: [NVE4] PGRAPH - grctx template channel unload timeout,
failed to construct context, init failed, -16
Product: Mesa
Version: 10.6
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
2013 Feb 06
4
FreeBSD-9.1 would not boot on pentium3 laptop
Hello!
I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it).
FreeBSD 6.3-STABLE was running fine on it, but I decided to update the
machine to 9.1-STABLE.
Well, neither my own custom kernel, nor even the official 9.1-RELEASE
CD1 would boot... In both cases the boot process runs up to detecting
uhub0, then either hangs forever or shuts off after a short while.
Again, I thought I