similar to: [PATCH] export retained initrd in debugfs

Displaying 20 results from an estimated 100 matches similar to: "[PATCH] export retained initrd in debugfs"

2005 Jun 13
2
[PATCH] fix x86_64 initrd support
Looks like x86_64 never quite handled initrd''s. This brings x86_64 in line with i386 in that it doesn''t check LOADER_TYPE (which will be zero anyway). Now initrd is working fine for me on x86_64. Signed-off-by: Chris Wright <chrisw@osdl.org> ===== linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/setup.c 1.6 vs edited ===== ---
2007 Apr 18
1
[PATCH] fix boot crash when freeing initrd memory
I'm triggering this BUG_ON during boot, which happens while freeing initrd memory: EIP is at free_init_pages+0x37/0xac [<c01143f1>] free_initrd_mem+0x11/0x13 [<c03ce259>] free_initrd+0x13/0x29 [<c03cf647>] populate_rootfs+0xdc/0xe2 [<c01003af>] init+0x42/0x253 [<c0103bbb>] kernel_thread_helper+0x7/0x10 I'm not sure why this memory isn't aligned
2007 Apr 18
1
[PATCH] fix boot crash when freeing initrd memory
I'm triggering this BUG_ON during boot, which happens while freeing initrd memory: EIP is at free_init_pages+0x37/0xac [<c01143f1>] free_initrd_mem+0x11/0x13 [<c03ce259>] free_initrd+0x13/0x29 [<c03cf647>] populate_rootfs+0xdc/0xe2 [<c01003af>] init+0x42/0x253 [<c0103bbb>] kernel_thread_helper+0x7/0x10 I'm not sure why this memory isn't aligned
2010 Nov 18
2
ocfs2: char is not always signed
Commit 1c66b360fe262 (Change some lock status member in ocfs2_lock_res to char.) states that these fields need to be signed due to comparision to -1, but only changed the type from unsigned char to char. However, it is a compiler option if char is a signed or unsigned type. Change these fields to signed char so the code will work with all compilers. Signed-off-by: Milton Miller <miltonm at
2003 Nov 14
1
initramfs gunzip problems.
I've been having an exchange of e-mails with Bryan O'Sullivan regarding this problem. I thought it time to bring it to the list. I've run into a problem where my initramfs archives get this during bootup: checking if image is initramfs...it isn't (ungzip failed); looks like an initrd The same .cpio archive works if I don't gzip it. I stuck a bunch of debug statements into
2006 Jan 30
4
symlinks and initramfs (was klibc-1.2.1: kinit works...)
On Mon Jan 30 08:56:06 PST 2006, H. Peter Anvin wrote: > That being said, there is no reason that you can't run code before it; > to make that simpler, in fact, I'm trying to set it up so that the > default initramfs looks like: > > /dev/console > /dev/zero > /dev/null > /kinit > /init -> /kinit I would request we not put in symlinks. The problem is that
2007 Oct 12
3
extract the initramfs from a kernel
Hello, is there a way to extract an initramfs from a running kernel? and from a kernel lying on a disk? If yes, how? Thanks Eurolines : Voyagez au meilleur prix : http://www.alinto.com/pub/
2006 Jun 26
0
[klibc 06/43] Re-create ROOT_DEV, too many architectures need it.
ROOT_DEV carries a root device number communicated in an architecture- specific way. We now pass it to kinit via the real-root-dev sysctl call. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 0f5a324d655ad582246b6830843114d09835f593 tree fd3a96a69b6d74ee33dcd54a58b8666c02139a3a parent f3e41698e540a7d39658d6590fde1379c0f5bab0 author H. Peter Anvin <hpa at zytor.com> Thu,
2003 Dec 01
0
No subject
Samba mount (from one of our build scripts). We decided to upgrade to RedHat 7.2 (which uses a newer version of Samba -- 2.1.1b IIRC), maybe that fixes the problem. However, I decided to submit this bug report, in the hope that it may help kill some bugs. (Remember -- the only good bug, is a dead bug :)) So, here is the dmesg output: Linux version 2.2.16-22enterprise
2004 Dec 03
2
INITRAMFS: allow no trailer
According to "initramfs buffer format -- third draft" http://lwn.net/2002/0117/a/initramfs-buffer-format.php3 "the cpio "TRAILER!!!" entry (cpio end-of-archive) is optional, but is not ignored" The kernel handling does not follow this spec. If you add null padding after an uncompressed cpio without TRAILER!!! the kernel complains "no cpio magic". In a
2003 Dec 27
0
2 disks boot patch
Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==
2003 Dec 27
0
FW: 2 disks boot patch
Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==
2004 Sep 14
6
initrd / initramfs future
Hello, I would like to know if initrd is here to stay, now that klibc and initramfs are ready. As the multipath-tools maintainer, I'm facing the choice to 1) put the multipath configuration tool in the initrd * dynamic binary is possible * storage hba drivers as modules loaded * no klibc limitations (no mntent for libsysfs ...) 2) put the multipath configuration tool in the initramfs *
2006 Jul 03
0
[PATCH]: klcc typo recognizing .S files
Trying to use klcc to compile an application I was getting gcc: no input files. Tracked it down to filename2lang having and extra space, causing .S files to be labeled "obj". Signed-off-by: Milton Miller <miltonm at bga.com> --- There is probably another bug that we called gcc without any files when we were called with what we parsed as an obj file. ---
2020 Jul 14
0
[PATCH v4 16/75] x86/boot/compressed/64: Don't pre-map memory in KASLR code
From: Joerg Roedel <jroedel at suse.de> With the page-fault handler in place the identity mapping can be built on-demand. So remove the code which manually creates the mappings and unexport/remove the functions used for it. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- arch/x86/boot/compressed/ident_map_64.c | 6 ++---- arch/x86/boot/compressed/kaslr.c | 24
2003 Dec 02
3
How to restart * thru phone "when convenient"
Hi there, here is my attempt to initiate a "restart when convenient" from a software SIP phone. exten => 588,1,Answer exten => 588,2,Wait(1) exten => 588,3,Playback(restart-convenient) exten => 588,4,Wait(1) exten => 588,5,Authenticate(00000) exten => 588,6,System(/usr/sbin/asterisk -rx "restart when convenient") exten => 588,7,Hangup The problem: We
2012 Jul 18
0
Failed Verification - Update Retained (will try again)
I would really like a little clarification for the error in the Subject. 1. If it says "update retained" and I'm doing an --inplace sync, does that mean it did copy over the blocks it found during the initial pass? In other words, can I assume the synced version on the receiving end looks just like the source at the time it was first scanned for changes? I hope so. 2. If #1 is
2015 Nov 25
0
Stereo voice not being retained
Hey Kevin! Once you start dropping under (I think) 32kbps, the codec naturally starts losing stereo separation for the benefit of quality. If you really want perfect stereo at 16kbps CBR (this is horrifically low in my opinion) you might be better off splitting the audio and encoding each part at 8kbps CBR. Or, there may be a magic "enforce 100% stereo" one could pass? (doesn't look
2016 Sep 03
0
hacking grub to control number of retained kernels.
On Fri, Sep 02, 2016 at 10:52:05PM -0400, Fred Smith wrote: > I've recently had this problem on two C7 systems, wherein when doing "yum > update", I get a warning about /boot being low on space. > > both systems were installed using the partition size recommended by > Anaconda, right now "df -h" shows /boot as 494M, with 79M free. > > I don't
2019 Jun 03
2
"WARNING: failed verification -- update retained (will try again)" message
Hi there! On a daily backup script, I am getting a lot of these messages: WARNING: <filename> -- update retained (will try again). I've tried googling, but i can't figure out what these messages exactly mean and how i can solve them. Any hint? Thank you Gabriele -- GPG Key Fingerprint: DAD1 E3E3 C3E9 36FB C570 F405 9B5F 7108 A1D0 2FFF