search for: v3.10

Displaying 20 results from an estimated 52 matches for "v3.10".

Did you mean: v3.11
2013 Jul 08
0
Linux v3.10 and a new config option that is not enabled by default ... CONFIG_HYPERVISOR_GUEST=y
If you compiled your kernel and booted under Xen and got: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x9db000 (XEN) elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xa30f0 (XEN) elf_parse_binary: phdr: paddr=0x1aa4000 memsz=0x13c00 (XEN) elf_parse_binary: phdr: paddr=0x1ab8000 memsz=0x206000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x1cbe000 (XEN)
2005 Aug 24
2
MEMDISK bug in Syslinux 3.10
MEMDISK included in the freshly released Syslinux v3.10 is unfortunately broken. v3.09 works properly. Scenario: Isolinux --> MEMDISK --> FDBOOT.IMG (FreeDOS 360KB diskette image). Then try to access drive B: , which normally is your first diskette drive with driveletter A:. However, in this case MEMDISK occupies A:, and real diskdrive becomes B: Bug: when accessing B:, you're asked
2013 Apr 19
2
[GIT PULL) xen (stable/for-linus-3.10-rc0-tag) for v3.10 merge window.
Hey Linus, I am heading out for a week of vacation but would hate to have missed the merge window. Hence sending it out early in anticipation that you will release v3.9 on Sunday. With that said, please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.10-rc0-tag which has just a couple of features and mostly bug-fixes. Here is the
2013 Jun 04
2
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
Hello, Hit this right after killing trinity with Ctrl-C. Was fuzzing v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. Tommi [29175] Random reseed: 3970521611 [29175] Random reseed: 202886419 [29175] Random reseed: 2930978521 [179904.099501] binder: 29175:2539 ioctl 4010630e fff returned -22 [29175] Random reseed: 2776471322 [29175] Random reseed: 3086119361 child 2606 exiting
2013 Jun 04
2
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
Hello, Hit this right after killing trinity with Ctrl-C. Was fuzzing v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. Tommi [29175] Random reseed: 3970521611 [29175] Random reseed: 202886419 [29175] Random reseed: 2930978521 [179904.099501] binder: 29175:2539 ioctl 4010630e fff returned -22 [29175] Random reseed: 2776471322 [29175] Random reseed: 3086119361 child 2606 exiting
2018 Apr 25
2
RDMA Client Hang Problem
Dear Gluster-Users, I am experiencing RDMA problems. I have installed Ubuntu 16.04.4 running with 4.15.0-13-generic kernel, MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64 to 4 different servers. All of them has Mellanox ConnectX-4 LX dual port NICs. These four servers are connected via Mellanox SN2100 Switch. I have installed GlusterFS Server v3.10 (from Ubuntu PPA) to 3 servers. These 3
2013 Jun 05
1
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
2013/6/5 Michael S. Tsirkin <mst at redhat.com>: > On Tue, Jun 04, 2013 at 09:50:59PM +0300, Tommi Rantala wrote: >> Hello, >> >> Hit this right after killing trinity with Ctrl-C. Was fuzzing >> v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. >> >> Tommi > > Thanks a lot for the report. If found some bugs when looking > at
2013 Jun 05
1
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
2013/6/5 Michael S. Tsirkin <mst at redhat.com>: > On Tue, Jun 04, 2013 at 09:50:59PM +0300, Tommi Rantala wrote: >> Hello, >> >> Hit this right after killing trinity with Ctrl-C. Was fuzzing >> v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. >> >> Tommi > > Thanks a lot for the report. If found some bugs when looking > at
2018 Apr 25
0
RDMA Client Hang Problem
Is infiniband itself working fine? You can run tools like ibv_rc_pingpong to find out. On Wed, Apr 25, 2018 at 12:23 PM, Necati E. SISECI <siseci at gmail.com> wrote: > Dear Gluster-Users, > > I am experiencing RDMA problems. > > I have installed Ubuntu 16.04.4 running with 4.15.0-13-generic kernel, > MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64 to 4 different servers.
2013 Mar 22
6
[PATCH V4 0/2] tcm_vhost hotplug
Asias He (2): tcm_vhost: Introduce tcm_vhost_check_feature() tcm_vhost: Add hotplug/hotunplug support drivers/vhost/tcm_vhost.c | 224 ++++++++++++++++++++++++++++++++++++++++++++-- drivers/vhost/tcm_vhost.h | 10 +++ 2 files changed, 229 insertions(+), 5 deletions(-) -- 1.8.1.4
2013 Mar 22
6
[PATCH V4 0/2] tcm_vhost hotplug
Asias He (2): tcm_vhost: Introduce tcm_vhost_check_feature() tcm_vhost: Add hotplug/hotunplug support drivers/vhost/tcm_vhost.c | 224 ++++++++++++++++++++++++++++++++++++++++++++-- drivers/vhost/tcm_vhost.h | 10 +++ 2 files changed, 229 insertions(+), 5 deletions(-) -- 1.8.1.4
2018 Apr 25
1
RDMA Client Hang Problem
Thank you for your mail. ibv_rc_pingpong seems working between servers and client. Also udaddy, ucmatose, rping etc are working. root at gluster1:~# ibv_rc_pingpong -d mlx5_0 -g 0 ? local address:? LID 0x0000, QPN 0x0001e4, PSN 0x10090e, GID fe80::ee0d:9aff:fec0:1dc8 ? remote address: LID 0x0000, QPN 0x00014c, PSN 0x09402b, GID fe80::ee0d:9aff:fec0:1b14 8192000 bytes in 0.01 seconds =
2013 Sep 03
2
[PATCH] drm/nouveau: avoid null deref on bad arguments to nouveau_vma_getmap
Op 03-09-13 16:20, Pasi K?rkk?inen schreef: > On Wed, Aug 28, 2013 at 09:44:15AM +0200, Maarten Lankhorst wrote: >> Op 28-08-13 08:29, Pasi K?rkk?inen schreef: >>> On Fri, Aug 23, 2013 at 11:20:42PM +0300, Pasi K?rkk?inen wrote: >>>> On Thu, Aug 22, 2013 at 09:12:40AM +0200, Maarten Lankhorst wrote: >>>>> Op 22-08-13 02:10, Ilia Mirkin schreef:
2013 Aug 24
5
[Bug 847] New: Owner matching fails on listening socket
https://bugzilla.netfilter.org/show_bug.cgi?id=847 Summary: Owner matching fails on listening socket Product: netfilter/iptables Version: unspecified Platform: x86_64 OS/Version: Debian GNU/Linux Status: NEW Severity: enhancement Priority: P5 Component: ip_tables (kernel) AssignedTo:
2009 Jun 05
3
R: Re: R: Re: PXEbooting very slow
I made other tests. It's not a matter of Win98 versus WinXP, things change passing from tftpd32 v310beta to v3.33. This version seems to work fine, but the logs show problems. Here is the complete log with pxelinux 3.82-pre4: Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:1E: 68:A6:9E:A9 [05/06 18:24:43.816] DHCP: proposed address 192.168.1.20 [05/06 18:24:43.816] 1356 Request 2 not
2013 Sep 24
11
[Bug 69768] New: not able to do a suspend
https://bugs.freedesktop.org/show_bug.cgi?id=69768 Priority: medium Bug ID: 69768 Assignee: nouveau at lists.freedesktop.org Summary: not able to do a suspend QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: marccollin7379 at gmail.com Hardware:
2013 Aug 27
4
Is: Xen 4.2 and using 'xl' to save/restore is buggy with PVHVM Linux guests (v3.10 and v3.11 and presumarily earlier as well). Works with Xen 4.3 and Xen 4.4. Was:Re: FAILURE 3.11.0-rc7upstream(x86_64) 3.11.0-rc7upstream(i386)\: 2013-08-26 (tst001)
Hey, I have a nighly build/test system that boots various machines with upstream Linux and randomly selects Xen 4.1, Xen 4.2, Xen 4.3 and unstable. After a bit of digging I found out that Xen 4.2 ''xl'' (but not ''xm'') has some badness in it. When "migrating" (''xl'' save followed by ''xl'' restore'') the PVHVM
2015 Mar 05
0
"Machine Check Exception: 4 Bank 0: 9000000020000003" when boot CentOS 7, with Intel CPU E3845, and BIOS option "EIST" enable.
My hardware is: CPU: Intel(R) Atom(TM) CPU E3845 @ 1.91GHz and it supports EIST(Enhanced Intel SpeedStep Technology). OS: CentOS 7(kernel-3.10) When I set the BIOS options "CPU configuration >> EIST" to "enable", it appears a kernel panic when the system is starting up. Here is what I am seeing: ...... Fast TSC calibration failed. [Hardware Error] CPU 3: Machine Check
2013 Jun 10
0
[GIT PULL] (xen) stable/for-linus-3.10-rc5-tag
Hey Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.10-rc5-tag which has two fixes for regressions that occured in v3.10. The signed tag has more details so replicating it here: <tag> Bug-fixes for regressions: - xen/tmem stopped working after a certain combination of modprobe/swapon was used - cpu
2014 Apr 10
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #14 from Lubosz Sarnecki <lubosz at gmail.com> --- I am only bisecting the nouveau directory, like so: git bisect start v3.14 v3.10 -- drivers/gpu/drm/nouveau -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: