similar to: assertion failure

Displaying 20 results from an estimated 5000 matches similar to: "assertion failure"

2001 Dec 20
1
crashing ext3 is easy and reproducible
This is my crash script for 2.4.17-rc1 and rc2 It works exactly as expected first time. Second time your system is toast with an exception error. I think it kills the daemon. I've tried it with varying ram disk sizes, up to 256Mb and in UP and SMP mode. The only thing I've seen was putting two of them into a script with the intention of having a one stop crasher didn't
2010 Jun 29
2
EXTLINUX
I am trying to boot a ramdisk on a usb stick in read-only mode using extlinux. When the system boots all I am getting is a blinking cursor. The stick booted with lilo, but I had some issues with lilo so I am trying extlinux. 1) I partitioned the stick as a linux partition, formated it ext2, and mounted /dev/sda1 on /mnt/flash. 2) I am running extlinux 3.86. 3) excuted "extlinux -i
2012 Mar 25
3
attempt to access beyond end of device and livelock
Hi Dongyang, Yan, When testing BTRFS with RAID 0 metadata on linux-3.3, we see discard ranges exceeding the end of the block device [1], potentially causing dataloss; when this occurs, filesystem writeback becomes catatonic due to continual resubmission. The reproducer is quite simple [2]. Hope this proves useful... Thanks, Daniel --- [1] attempt to access beyond end of device ram0: rw=129,
2004 Jun 30
1
initramfs and kernel 2.6.7
Hi, I 'am trying to launch linux kernel 2.6.7 with initramfs. My pxelinux.cfg/default file looks as follows: default a1 prompt 1 timeout 600 label a1 kernel vmlinuz-2.6.7-1 append initrd=initramfs_data.cpio.gz root=/dev/ram0 init=/linuxrc Kernel image vmlinuz-2.6.7-1 and initramfs_data.cpio.gz was loaded succesfully by pxelinux. Kernel says: checking if image is initramfs... it is but
2011 Apr 14
1
Isolinux 4.02
I am running isolinux 4.02 and ramdisk_size does not seem to have an effect on the ramdisk size. No matter what I set it to in the isolinux.cfg file it seems the limit is 32768. I get the error: ram0: rw=0, want=360456, limit=32768 EXT2-fs error (device ram0): My isolinux.cfg file: LABEL EB KERNEL vmlinuxE APPEND initrd=bos.img root=/dev/ram0 rw ramdisk_size=545000 I am running the 2.6.38.2
2002 Jul 29
4
ISOLINUX
Hello, I have a couple of questions, But first.... Thankyou for creating such an easy to use awesome piece of software. I am wanting to use ISO linux to select two different kernels/configurations and have set up the isolinux.cfg file as follows.... DISPLAY start.msg TIMEOUT 10000 DEFAULT linux LABEL linux KERNEL vmlinuz APPEND root=/dev/ram0 initrd=txtimage.gz LABEL linux-fb KERNEL
2003 Jan 19
1
isolinux/gentoo
Hello, Im a Gentoo kernel maintainer thats trying to fix some bugs on are upcoming 1.4 livecd release that uses IsoLinux. Our isolinux.cfg is pretty standard : ######################################### default gentoo append initrd=initrd acpi=off root=/dev/ram0 init=/linuxrc timeout 300 prompt 1 display boot.msg F1 boot.msg F2 help.msg label livecd kernel gentoo append
2006 Apr 03
2
probs running stuff from initrd
Hello all Now I may be way of whack here, so please forgive me. I''m trying to merge xen with redhat''s config-netboot. The idea being a kinda stateless domU. For those that haven''t seen you share a rootfs and then bind mount all the individual files over then top, and the redhat gui builds all the pxeboot config and stuff for you if you want a diskless client. I
2004 Nov 18
2
use of APPEND in default
Having fought my PXE config and eventually getting it to work (had to comment out the group { } statments ? I now come across another issue I cannot resolve and would appreciate some help. in my /tftpboot/pxelinux.cfg/default file I have cause to use the APPEND statement to pass options to the kernel being used. Unfortunately this line has now become longer than 255 characters and appears to be
2010 Mar 19
3
dom0 - syslinux/isolinux error
Hi,   I am trying to build dom0 iso. I have following in my isolinux.cfg file. I see error: "Invalid or corrupt image file".   --- default 1 prompt 1 timeout 300 display menu.txt label 1   kernel boot/vmlinuz.vm   append boot/xen.gz  ramdisk_size=131072 initrd=boot/ramdisk.gz root=/dev/ram0 ---   The image I check is valid. xen.gz is actually xen-3.4.2.gz: xen.gz: gzip compressed data,
2004 Apr 16
7
pxe linux
Hi, I have setup pxelinux like this, default linux label=linux kernel linux append initrd=rootfs.img ipappend 1 I have my dhcpd.conf like this, allow booting; allow bootp; group{ filename "pxelinux.cfg/pxelinux.0"; host deploy { next-server 192.168.1.254; hardware ethernet 00:0E:A6:22:28:21;
2002 Mar 18
1
Syslinux & DiskonChip 2000 boo error.
Good afternoon. I am trying to make a 32M DiskonChip2000 boot Linux (kernel version 2.2.20) but I'm having difficulty. It begins fine, loading most of the kernel, but halts immediately after the "Freeing unused kernel memory: 52K freed." step. The implication seems to be that my ramdisk is not being mounted/executed properly. My syslinux.cfg file is as follows: timeout=0
2012 Sep 04
1
ifcpu64.c32 not working properly when used in a menu include file
The following is a pxelinux problem, specifically to do with including config files with the menu include directive and the ifcpu64.c32 com module. I have a working ifcpu64.c32 setup that jumps to the label rescue64 in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit kernel and a 64-bit initrd.img. The setup jumps to a label named "rescue32" in the case of a
2005 Jul 07
2
bug(?) in 2.11
Hi! I write this config line: kernel /boot/i386/vmlinuz ro ramdisk=32768 root=/dev/ram0 init=/linuxrc but when I try to boot I got this mesasge: Could not find kernel image: /boot/i.386/ Same symptomes are with slash and backslash too. I think, the parses don't understand the directory separator characters and count as the part of filename. ps Sorry for my english -- Gabor HALASZ
2008 May 15
1
Panic on CPU 0
Hi all, I''m trying to boot XEN. I get the following error though Panic on CPU 0: Early fatal page fault at e008:ff134570 (cr2=fffdf020, ec=0000) Reboot in five seconds... Unknown interrupt (cr2=fffdf020) My system has 2GB of RAM. Has anyone had the same problem and can give an hint? Thanks. In case anyone had done the same I''m doing, I''m actually downloading XEN
2005 Aug 26
2
Could not find kernel image:
I am trying to create a bootable cd from a working LFS 6.1 partition. Thank you in advance for any thoughts on this. This is the error I get: ISOLINUX 3.10 2008-08-24 Copyright (C) 1994-2005 H. Peter Anvin Could not find kernel image: lfskernel-2.6.11.12 boot : _ under /isolinux/ I have these files: isolinux.bin I've tried 3.10 and 3.09 isolinux.cfg: default livecd label livecd
2005 Sep 20
4
standalone bootable usb-stick
hi ya syslinuxerz - i've been slowly working on a making a custom bootable standalone usb-stick with X11 and kde - it's basically builds itself off of a slackware-10.1 server - create a custom initrd.gz ( /dev/ram0 ) http://linux-boot.net/Bootable/InitRD/ - create a custom rootfs.gz ( /dev/loop0 ) http://linux-boot.net/Bootable/RootFS/ - create X11 and kde loopfiles
2002 Jun 17
2
Going Mainstream
Devik, Can you send Htb to Marcello Please? Its only a module, but its about time it went mainstream. Maybe its too late for 2.4.19, but 2.4.20 will come. Same comment for IMQ also. Regards John
2001 Nov 18
2
restoring .journal
Hello, If I made a cpio backup of an ext3 fs. Then created a new fs and restored everything including the .journal file, What would happen?? Regards John
2010 Mar 20
1
Error: ramdisk
  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>