similar to: Oops on 2.4.13-pre6 (sparc64)

Ext3 Journal oops & RAID-1 set losing sync. (Sent to both EXT3 and Linux-RAID since both are in use and seem possibly relevant) I have had a number of problems maintaining a software RAID-1 set on an IDE box I maintain; it seems that doing raidhotadd on the drive marked as invalid works each time though. However, I've had both errors about trying to read past the end of the

Hi everybody Just wanted to ask that. pre6 with ext3 work fine for me so far. Bye Tim

An ext3 patch for the latest Linus kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The changes are quite small: - Tided up some code now that quotas in Linus and -ac kernels are synced up. - Fix a race which can cause a null-pointer deref in ext3_writepage(). This bug has been there for a long time, but only manifested in 2.3.13-pre for some reason. I've tested this pretty

Hello everyone. I'm running Red Hat 7.3 with kernel 2.4.18-10 and all errata patches installed. My system has been running for over three years without any problems. All I've done to it in that time is add a mirror set of two 80GB drives, a Promise IDE controller, and upgrade Red Hat through the 7.x series. Right now I have three drives. A 13GB system drive off the motherboard, and

I am having some trouble compiling ext3 for the 2.4.13 kernel. It appears that the journaling source file is corrupted: In file included from sysctl.c:33: /src/linux-2.4.13/include/linux/jbd.h: In function `buffer_jbd': /src/linux-2.4.13/include/linux/jbd.h:241: `BH_JBD' undeclared (first use in this function) /src/linux-2.4.13/include/linux/jbd.h:241: (Each undeclared identifier is

Hello. I found bugs on error handlings in the functions arround the ext3 file system, which cause inadequate completions of synchronous write I/O operations when disk I/O failures occur. Both 2.4 and 2.6 have this problem. I carried out following experiment: 1. Mount a ext3 file system on a SCSI disk with ordered mode. 2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT

Hi, I am getting the following Oops on 2.6.30.1 kernel. The bad part is, it happens rarely (twice in last 1.5 months) and the system is pretty lightly loaded when this happens (no heavy file/disk io). Any insights or patches that I can try? (i searched lkml and ext3 lists but could not find any similar oops/reports). == Oops =================== BUG: unable to handle kernel NULL pointer

I can't get it to run. On launch I get this: dyld: /usr/local/lib/R/bin/R.bin multiple definitions of symbol _PC /sw/lib/libreadline.4.2.dylib(terminal.so) definition of _PC /sw/lib/libncurses.dylib.5(lib_tputs.o) definition of _PC Thanks. Linc Davis -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read

We have here an knfs fileserver running ext3 on 2.4.18 kernel with three filesystems: <CLIP> Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda3 10080520 3609632 6368476 37% / /dev/hda4 16437332 12295408 3974932 76% /home /dev/md1 1024872060 409906136 614441636 41% /fs </CLIP> The /fs filesystem lives on a

Hi Ext3! I'm running about 30 dedicated MySQL machines under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had

Should I be worried? The installation seems to go through fine and apparently nothing is broken. The errors I repeatedly get are like this: g++ -no-cpp-precomp -I/Library/Frameworks/R.framework/Resources/include -I/usr/ local/include -DUNIX -DOPTIM -DNONR -fno-common -g -O2 -c unif.cpp -o unif.o g++ -bundle -flat_namespace -undefined suppress -L/usr/local/lib -o rgenoud.so c hange_order.o

This version cleans up the Ethersel (PCI config probing) changes I have been iterating with Alex Heinz. It's not the same code (so please test, especially Alex), but it should work the same. As before, if you have a machine for which 2.13 worked and 3.0x hasn't worked, please test this version too. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

It seems that at least SYSLINUX 1.73-pre4 and -pre5 had some very serious bugs in it, so here is a SYSLINUX 1.73-pre6 to test out; don't be surprised if there are more in short order... :) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi, just tried 1.73-pre6 pxelinux: - booting linux works - memdisk with 1.44M Dos image works - the 'kbdmap'-parameter fails: [..] Unknown keyword in config file. Missing parameter in config file. boot: - and it doesn't remap any keys. I tried 1.66 with the same config file and it works, it accepts 'kbdmap' and also remaps the keys. Regards, Josef

Hi everyone, I have released SYSLINUX 2.00-pre6. The only difference against -pre5 is that I finally got around to fixing mbr.asm so that it produces a working MBR. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ I will probably try to do a binary-only release of the COM32 port of newlib libc sometime this week. The only reason this will be a binary-only release is that the

Hi, I tested this version and it works all right ! Thanks a lot for the quick fix. Do you still want to see the output in order to check everything is OK, or you don't need it ? --------------------- Sylvain Faivre EdifiXio - AIH Team +33 1 56 90 51 24 www.edifixio.com > -----Message d'origine----- > De : H. Peter Anvin [mailto:hpa at zytor.com] > Envoy? : mardi 18 novembre

This version adds Murali's "onerror" configuration directive. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi all, It looks like the announcement about 2.08-pre6 never went out... it is 2.08-pre5 with Murali's "onerror" command added. -hpa

I have decided to make SYSLINUX 2.10-pre6 a release candidate. Please test it out if you can; if it works OK I will release it as 2.10 some time in the middle of the week. Thanks! -hpa

Hello, While attempting to build syslinux-3.52-pre6 for testing (my SCSI machine won't boot from CD-ROM with 3.51) I hit this problem: nasm -O99 -f bin -DDATE_STR="'3.52-pre6'" -DHEXDATE="0x46c22b21" \ -DMAP=pxelinux.map -l pxelinux.lsr -o pxelinux.bin pxelinux.asm pxelinux.asm:1206: error: short jump is out of range nasm -version NASM version