similar to: pxelinux (2.08 or later) on VMware

Folks, When I run syslinux on my Sandisk Cruzer (512MB) USB flash RAM with the "syslinux /dev/sda" , it corrupts the partition table that I had already created on my USB device. It attempts to boot but eventually fails trying to load the kernel. If I try "syslinux /dev/sda1", the USB device fail to boot at all. I would think that /dev/sda would be the correct device to use if

Hi, [I sent this mail again because my previous mail was rejected by ML for some reason] This topic is originally from etherboot ML. When we specify "localboot" for pxelinux loaded from etherboot, this option doesn't work( it doesn't boot from local harddrive ). pxelinux returns to PXE with localboot return code but etherboot doesn't check it. I was trying to change

Hi. I've ever wondered how nuch timeis left to timeout while waiting at the boot prompt, so I've writen this small patch to show it. This add a configuration command 'showtimeout'. If you like the patch I could improve it (for example to show the timeout in decimal because now it uses the writehex functions) Regards. -- ______ ________ / / \/ /___ ) I N T E G

Hi all, While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a number of splats in the block layer: * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in jbd2_trans_will_send_data_barrier * BUG: sleeping function called from invalid context at mm/mempool.c:320 * WARNING: CPU: 0 PID: 0 at block/blk.h:297 generic_make_request_checks+0x670/0x750 ... I've included the

Hi all, While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a number of splats in the block layer: * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in jbd2_trans_will_send_data_barrier * BUG: sleeping function called from invalid context at mm/mempool.c:320 * WARNING: CPU: 0 PID: 0 at block/blk.h:297 generic_make_request_checks+0x670/0x750 ... I've included the

Hi all, I am wondering about the following suggested change: In isolinux.asm, line 50 (at least in my Debian patched version), add the line "hlt" inside the "DO_IDLE" macro. Explanation: When running isolinux on a vmware box, the boot menu takes up all available CPU. This change seems to solve this problem. I have read elsewhere that such a change will not go in, as the

Hi, (this is a topic from etherboot ML). When we specify "localboot" for pxelinux loaded from etherboot, this option doesn't work( it doesn't boot from local harddrive ). I was trying to change etherboot side but it was not easy to me. So I simply replaced pxelinux local_boot: with isolinux's one with little modification. It may be better that pxelinux.cfg also allows to

>I found a problem with pxelinux in 2.08 and 2.09pre13 when working with >vmware 4.5.1 (the latest with builtin support fpr pxe-boot). With 2.07 and >2.01 it works without problems. But when trying the later versions there is >trouble. I reach pxeboot.msg >and it shows fine but when I try to choose an image it dosent give keyboard >feedback (first I thought it had hanged) but

I found a problem with pxelinux in 2.08 and 2.09pre13 when working with vmware 4.5.1 (the latest with builtin support fpr pxe-boot). With 2.07 and 2.01 it works without problems. But when trying the later versions there is trouble. I reach pxeboot.msg and it shows fine but when I try to choose an image it dosent give keyboard feedback (first I thought it had hanged) but after some testing it

On Wed 2023-01-25 10:57:30, Seth Forshee wrote: > On Wed, Jan 25, 2023 at 12:34:26PM +0100, Petr Mladek wrote: > > On Tue 2023-01-24 11:21:39, Seth Forshee wrote: > > > On Tue, Jan 24, 2023 at 03:17:43PM +0100, Petr Mladek wrote: > > > > On Fri 2023-01-20 16:12:22, Seth Forshee (DigitalOcean) wrote: > > > > > Livepatch relies on stack checking of

On Fri 23-02-18 15:47:36, Mark Rutland wrote: > Hi all, > > While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a > number of splats in the block layer: > > * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in > jbd2_trans_will_send_data_barrier > > * BUG: sleeping function called from invalid context at mm/mempool.c:320 > > * WARNING:

Tim Legge has passed the following message on to me: hpa wrote: > Quinn wrote: > > Now it seems I have found a bug in PXELINUX with regards to etherboot. > > Up until 2.07 pxelinux was responsive to the keyboard. From 2.08 and > > up the keyboard is locked at the boot prompt when pxelinux is loaded > > via etherboot 5.3.14. > > That would not be a PXELINUX bug,

Hello everyone, I have pushed out SYSLINUX 3.08. It's identical in all but version number to 3.08-pre11. Sorry for everything that probably should have been done that didn't make it, but I simply haven't had time :( :( :( However, given several bugs fixed in 3.08, this seemed important... Changes in 3.08: * SYSLINUX: Fix performance regression (-s mode always

On 28.12.2018 03:26, Wei Wang wrote: > Some vqs don't need to be allocated when the related feature bits are > disabled. Callers notice the vq allocation layer by setting the related > names[i] to be NULL. > > This patch series fixes the find_vqs implementations to handle this case. So the random crashes during boot are gone. What still does not work is actually using the

From: Yang Zhang <yang.zhang.wz at gmail.com> Implement a generic idle poll which resembles the functionality found in arch/. Provide weak arch_cpu_idle_poll function which can be overridden by the architecture code if needed. Interrupts arrive which may not cause a reschedule in idle loops. In KVM guest, this costs several VM-exit/VM-entry cycles, VM-entry for interrupts and VM-exit

On Thu, Jul 5, 2018 at 6:59 AM, syzbot <syzbot+4e955f82549d361ed655 at syzkaller.appspotmail.com> wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: 2bdea157b999 Merge branch 'sctp-fully-support-for-dscp-and.. > git tree: bpf-next > console output: https://syzkaller.appspot.com/x/log.txt?x=178c5e68400000 > kernel config:

https://bugzilla.netfilter.org/show_bug.cgi?id=1141 Bug ID: 1141 Summary: trace aborts using pkttype on ingress Product: nftables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: major Priority: P5 Component: kernel Assignee: pablo at netfilter.org

https://bugs.freedesktop.org/show_bug.cgi?id=100691 Bug ID: 100691 Summary: [4.10] BUG: KASAN: use-after-free in drm_calc_vbltimestamp_from_scanoutpos+0x625/0x740 Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

It's pretty much the same as 2.08-pre11. 2.08 mostly a collection of minor enhancements. Changes in 2.08: * Add new configuration command "ontimeout" to allow timeout to have a different action than just pressing Enter. * Add new configuration command "onerror" to allow a custom command to be executed in case the kernel image is not

I have released SYSLINUX 2.08-pre11. It is the same as 2.08-pre10 except I have added logical partition support to the chainbooting module (still no partition hiding or anything like that.) Unfortunately I have no way to test this at the moment, so I thought I'd release a -pre11 and see if someone was willing to take it for a spin.