similar to: ext3 oops with 2.4.20

Hi I've got serious troubles - I posted a while back about experiencing ext3 errors using 2.4.18, at the time I put the problems down to harddisk failure, but these problems are occurring more and more - not all of our systems are having this problem but 3 systems have now shown this problem. The hardware is essentially the same, the only difference is disk manufacturers but we've now

Hi, Gettings lots of nasty ext3 errors, as follows: attempt to access beyond end of device 03:06: rw=0, want=1989391900, limit=55167178 EXT3-fs error (device ide0(3,6)): ext3_free_branches: Read failure, inode=10092558, block=-1113264762 - several thousand of these in the course of a few seconds And lots of these: EXT3-fs error (device ide0(3,6)): ext3_free_blocks: Freeing blocks not in

Hi all.. I have found some problems on smbfs module in 2.4.18 kernel. I compiled it by myself (not the very first kernel compilation in my life ;-)) and then I have got it. Looks like it touch smbfs module as when I recompile 2.4.18 modules with smbfs sources changed to sources of smbfs from 2.4.17 problem disappears!! My mainboard is Abit BE6 with Pentium III 450 MHz. I am using SuSE 7.3 with

A brand new system setup with RH 7.3 is still Oopsing after every X hours. The problem started after about 1 week without errors. Sometimes everything is locked, sometimes still messages are written to /var/log/messages. Sometimes other processes keep running (can still ping the machine) I upgraded the kernel to 2.4.18-19.7.x, changed the memory, but still got problems. When I read all sort of

After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel:

Hello list When i'm trying to dial into our pstn the following errors occure: -- Executing Dial("SIP/snomsip-dbd0", "/2100") in new stack Sep 9 10:02:22 WARNING[59409]: channel.c:1901 ast_request: No channel type registered for '' Sep 9 10:02:22 NOTICE[59409]: app_dial.c:715 dial_exec: Unable to create channel of type '' == Everyone is busy/congested

The system stopped responding to ssh but still responded to ping. The logs showed this error: (its long) Feb 4 00:08:08 server1 kernel: gdmgreeter: page allocation failure. order:0, mode:0x50 Feb 4 00:08:08 server1 kernel: [<c014f863>] __alloc_pages+0x28b/0x29d Feb 4 00:08:08 server1 kernel: [<c014b70f>] find_or_create_page+0x39/0x72 Feb 4 00:08:08 server1 kernel:

Hi All, I'm having a bit of a time getting my Tormenta 2 card to actually be seen by the system. Whenever I modprobe, the kernel spits out the following (in addition to the "insmod tor2 failed" messages): Invalid Xilinx 8 bit Base resource Registered Tormenta2 PCI Of course, the module says that its registered a Tormenta2 card, but it unloads the driver and frees related

Hi all, We have been using SuSE7.2 and samba (client and server) without any problems for a few months. Now, we migrated some workstations (samba clients) to SuSE8.0 and we get segfaults while accessing files mounted through samba. The segfault happens on the CLIENT side. Here is our network configuration: - SuSE7.2 server with default samba server package. - Few SuSE7.2 workstations

Steve, 1) go to /etc/asterisk 2) open modules.conf for editing using vi 3) add this line: noload=pbx_wilcalu.so 4) Save the file 5) Restart asterisk Lightup the candles, open the Cabernet Savignon ( or whatever your prefernce) and call your girlfriend. ;) Seshu -----Original Message----- From: asterisk-users-bounces@lists.digium.com

I'm afraid that I am at a loss here. I am new to Asterisk, and have successfully set up SIP. But I cannot get my FXS card working, and I'm not sure what else I can try. # modprobe wcfxo /lib/modules/2.4.21-37.0.1.ELsmp/misc/wcfxo.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may

Hello I am on Athlon 1Gz, kernel 2.4.8. I was running a perl pgm with a lot of disk access, deletions and symlinks creations... Maybe It is due to the kernel version. Could you please inform me if must upgrade to a more recent kernel ? Thanks a lot the kernel logs are : in errors logs Oct 18 17:31:16 tadorne kernel: Assertion failure in journal_revoke_Rb5884a32() at revoke.c:307:

every one,I meet a problem: I used reahat9.0(kernel 2.4.20-8smp,I installed a SCSI RAID Card),and there are always some problems and them the system is dead. is anyone can help me about it? Thanks Crist Below is the error log: Jun 11 22:19:03 mail1 kernel: EXT3-fs error (device sd(8,18)): ext3_free_blocks: Freeing blocks not in datazone - block = 1382828372, count = 1 Jun 11 22:19:03 mail1

This is a 2.2.19 machine with ext3-0.0.7a and quota support running. The symptoms are a particular NFS export hangs (for linux clients but not Solaris clients?) the local filesystem gives the following: EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 2213 EXT3-fs error (device sd(8,49)): ext3_free_blocks: Freeing blocks not in datazone - block = 1563120916,

I recently rebooted one of my machines and was greeted with a message about one of my ext3 partitions having some errors. I dutifully started e2fsck on the partition, but after a few hours of some useful messages about fixing inodes, it then started printing out lists of ascending numbers which I'm not sure how to interpret. The first time I noticed this, these numbers were in the 4000000

Hi, I am struggling to get rid of a conflict on DELL 2800 : PCI Parity error (EB113 on the display) I am learning linux and asterisk as I go along, there might be obvious things I should know, but bear with me. >From demsg below my 2 digium cards installed are listed (no config or connections done to digium cards yet), the conflict is with the TDM400P card, without that card, in any slot, no

On a 2.4.15-pre5 system with a 3ware-Escalade-68000 IDE RAID (mode 1) we had the follwing "dmesg" output today: EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks in system zones - Block = 16, count = 1 EXT3-fs error (device sd(8,38)): ext3_free_blocks: bit already cleared for block 1052672 EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks not in datazone

Hi all, I got a USB-HDD, but it doesn't looked like connect and cannot mount it just after PC boot. But insert and remove a usb cable from PC, it connect (with hotplug?) Is there any good how-to's for getting a usb-HDD to auto connect when It is booted the computer? lsmod is following: [lsmod of just after boot] Module Size Used by Not tainted parport_pc

hiya! i'm currently running 2.4.12-ac1 w/o any further ext3 patches. i've got a dir with some fairly big files (like 15mb/file) in it and while sfv-checking these i got the following errors: Oct 14 21:47:59 srck@trottelkunde attempt to access beyond end of device Oct 14 21:47:59 srck@trottelkunde 16:42: rw=0, want=600889688, limit=12289725 Oct 14 21:47:59 srck@trottelkunde attempt to

Hi, Hi, I have been googling, and can't find anything that will help me: mt -f /dev/st0 status /dev/st0: No such device or address Any suggestion? I am using CentOS 3 [RHEL ES3 without the licenses] The tape drive is recognized at boot [from dmesg] scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec 29160 Ultra160 SCSI adapter> aic7892: