search for: setting

Hello, syzkaller hit the following crash on 28f50eb20931f32a2ceeb6aba8fa2cd5ca96ad9f git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master compiler: gcc (GCC) 7.1.1 20170620 .config is attached Raw console output is attached. C reproducer is attached syzkaller reproducer is attached. See https://goo.gl/kgGztJ for information about syzkaller reproducers IP: read_pnet

Hello, syzkaller hit the following crash on 28f50eb20931f32a2ceeb6aba8fa2cd5ca96ad9f git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master compiler: gcc (GCC) 7.1.1 20170620 .config is attached Raw console output is attached. C reproducer is attached syzkaller reproducer is attached. See https://goo.gl/kgGztJ for information about syzkaller reproducers IP: read_pnet

On Tue, Oct 24, 2017 at 08:14:01AM -0700, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 28f50eb20931f32a2ceeb6aba8fa2cd5ca96ad9f > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. > C reproducer is attached > syzkaller reproducer is

I have a crash on the current stable kernel. Here is the trace from dmesg:- ---------------------------------------------------------- CPU: 0 PID: 682 Comm: modprobe Not tainted 3.13.0-rc3_exact-293199-g374b105 #379 Hardware name: / , BIOS GB85010A.86A.0063.P14.0107182015 07/18/2001 task: ef5b1a80 ti: ef5d8000 task.ti: ef5d8000 EIP: 0060:[<f0cfe995>] EFLAGS:

Hello, syzkaller hit the following crash on f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master compiler: gcc (GCC) 7.1.1 20170620 .config is attached Raw console output is attached. C reproducer is attached syzkaller reproducer is attached. See https://goo.gl/kgGztJ for information about syzkaller reproducers

Hey! Trying the root disk image http://xm-test.xensource.com/ramdisks/initrd-1.1-i386.img suggested in Documentation/lguest/lguest.txt, I get the follow trace when rebooting the guest. Kernel is 2.6.23-rc2-ge1cf20c1. @%@%> reboot The system is going down NOW !! Sending SIGTERM to all processes. Sending SIGKILL to all processes. Requesting system reboot. [ 7.541027] Restarting system. [

Hey! Trying the root disk image http://xm-test.xensource.com/ramdisks/initrd-1.1-i386.img suggested in Documentation/lguest/lguest.txt, I get the follow trace when rebooting the guest. Kernel is 2.6.23-rc2-ge1cf20c1. @%@%> reboot The system is going down NOW !! Sending SIGTERM to all processes. Sending SIGKILL to all processes. Requesting system reboot. [ 7.541027] Restarting system. [

This patch fixes xen related Kconfigs and add default config file for ia64 xen domU. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> --- arch/ia64/Kconfig | 4 + arch/ia64/configs/xen_domu_defconfig | 1601 ++++++++++++++++++++++++++++++++++ arch/ia64/xen/Kconfig | 3 +- 3 files changed, 1606 insertions(+), 2 deletions(-) create mode

This patch fixes xen related Kconfigs and add default config file for ia64 xen domU. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> --- arch/ia64/Kconfig | 4 + arch/ia64/configs/xen_domu_defconfig | 1601 ++++++++++++++++++++++++++++++++++ arch/ia64/xen/Kconfig | 3 +- 3 files changed, 1606 insertions(+), 2 deletions(-) create mode

Hi, My gateway/firewall/mailserver machine has been running 2.4.13 for a day or so now. Its basically a stock Linus kernel + ext3-0.9.13 patch (for -pre6, with the rej fixed). I'm getting this in /proc/meminfo: total: used: free: shared: buffers: cached: Mem: 130179072 117489664 12689408 0 46854144 69632 Swap: 1073987584 10907648 1063079936 MemTotal: 127128

When I start my domU, I get the infamous and UNINFORMATIVE! error message: "Device 0 (vif) could not be connected. Hotplug scripts not working." What could be the cause? There are strange things occuring. When I boot the host, I can start zero, one or two VM before it happens (most often zero), and then no other VM may be started successfully. It fails the same whether I try to boot

Hello I have serious problem with zhone z-plex 10 the device sometimes get red alarm on some channel and then the device suddenly shutdown. I try to unplugged the power chord and plug again, but the device still didn't up. I have to wait for long time to get this device up again. How can i fix this problem, so i can get this device immediately? Eris Riswanto

I tried booting the paravirt patches on a real machine to see what would happen. It had worked OK under qemu, so I thought it would be worth it. It seems to boot OK, though perhaps fairly slowly, but once it hits usermode it gets into trouble. When starting udevd, the startup script runs MAKEDEV, which seems to get stuck in an infinite loop in userspace. It eventually gets past that part

This is just a rediff and retest - no ext3 changes in this release. http://www.uow.edu.au/~andrewm/linux/ext3/ The latest diff is against linux-2.4.9. The version of ext3 in -ac kernels is current. -ac's ext3 has the "buffer tracing" debug code removed from the non-ext3 files, so the 2.4.9 diff is more useful for bug hunting. I should generate a diff against -ac to enable

Hi! Im currently trying to encrypt my harddrive and plan to boot it of a USB memory stick. Im using loop-aes to do the real work but Im having the hardest time getting syslinux to mount my initrd. Im not sure what information you need but Ill give a bit of it. VFS unable to mount root-fs on unknow-block(1,0) is the error I get. I think there was a Kernel Panic attached somewhere on there as

Is there noone who has any ideas? Ive searched google like crazy but cant find any good information... Any tips on where else I could find information? ----Ursprungligt meddelande---- Fr?n: gabriel.j at telia.com Datum: Apr 12, 2005 2:36:24 PM Till: syslinux at zytor.com ?rende: [syslinux] Syslinux on USB initrd problem Hi! Im currently trying to encrypt my harddrive and plan to boot it of a

...to get the VM to stop when this happens so that I could attach gdb and poke around. Sadly, I was on my way out to dinner when he gave that to me and I subsequently lost the patch to the Debian's paste bin's garbage collection. I have tried debugging without it by booting qemu with `-s -S`, setting break points for the kernel module initialization routines and running the system, but the breakpoints are not triggering. If I could get another copy of the patch that Alexander gave me, I would be able to move forward. Unfortunately, he is not on IRC right now. I cannot debug any further with my...

...to get the VM to stop when this happens so that I could attach gdb and poke around. Sadly, I was on my way out to dinner when he gave that to me and I subsequently lost the patch to the Debian's paste bin's garbage collection. I have tried debugging without it by booting qemu with `-s -S`, setting break points for the kernel module initialization routines and running the system, but the breakpoints are not triggering. If I could get another copy of the patch that Alexander gave me, I would be able to move forward. Unfortunately, he is not on IRC right now. I cannot debug any further with my...

Hello! I`m trying to boot a via sata machine with xen 3.0 with no sucess. It just freezes at this point: ********* ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [LNKB] -> GSI 10 (level,low) -> IRQ 10 sata_via (0000:00:0f.0): routed to hard irq line 10 ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF90 irq 10 ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF98 irq 10 ata1:

Ive done a new initrd but got the exact same error. Should rootfs really be minix? initrd is ext2. ----Ursprungligt meddelande---- Fr?n: jbebel at ncsu.edu Datum: Apr 13, 2005 11:58:26 PM Till: gabriel <gabriel.j at telia.com> ?rende: Re: Sv: Re: Sv: [syslinux] Syslinux on USB initrd problem I've got some really old instructions on creating an initrd up at