similar to: linux-next: Tree for Jan 23 (hvc and virtio_console)

Displaying 20 results from an estimated 100000 matches similar to: "linux-next: Tree for Jan 23 (hvc and virtio_console)"

2020 Jan 16
0
linux-next: Tree for Jan 16 (drivers/gpu/drm/nouveau/nvkm/subdev/ltc/gp10b.c)
On 1/16/20 1:17 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20200115: > > New tree: zonefs > > The sound-asoc tree lost its build failure. > > The net-next tree gained a build failure for which I reverted a commit. > > The keys tree still had build failures so I used the version from > next-20191211. > on i386 or x86_64:
2018 Feb 02
0
[fw_cfg] c8bf448ff3: kernel_BUG_at_arch/x86/mm/physaddr.c
FYI, we noticed the following commit (built with gcc-7): commit: c8bf448ff3899860de51fbae61a43619c912ddf2 ("fw_cfg: do DMA read operation") https://git.kernel.org/cgit/linux/kernel/git/mst/vhost.git vhost in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
2020 Apr 15
2
linux-next: Tree for Apr 15 (vdpa)
On 4/14/20 10:22 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20200414: > on x86_64: ERROR: modpost: "vringh_set_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! ERROR: modpost: "vringh_init_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! ERROR: modpost: "vringh_iov_push_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! ERROR:
2020 Apr 15
2
linux-next: Tree for Apr 15 (vdpa)
On 4/14/20 10:22 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20200414: > on x86_64: ERROR: modpost: "vringh_set_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! ERROR: modpost: "vringh_init_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! ERROR: modpost: "vringh_iov_push_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! ERROR:
2013 Feb 13
2
linux-next: Tree for Feb 13 (virtio_console)
On 02/13/13 00:35, Stephen Rothwell wrote: > Hi all, > > Changes since 20130212: > on i386: drivers/built-in.o: In function `in_intr': virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' drivers/built-in.o: In function `resize_console': virtio_console.c:(.text+0x2e26f): undefined
2013 Feb 13
2
linux-next: Tree for Feb 13 (virtio_console)
On 02/13/13 00:35, Stephen Rothwell wrote: > Hi all, > > Changes since 20130212: > on i386: drivers/built-in.o: In function `in_intr': virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' drivers/built-in.o: In function `resize_console': virtio_console.c:(.text+0x2e26f): undefined
2013 Jun 03
0
[virtio_blk] BUG: unable to handle kernel paging request at ff7f5784
Greetings, I got the below dmesg and the first bad commit is commit b70aa55ec9532d5f5d3e367e4cad8997b1135f86 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk> [ 277.857736] blk-mq: CPU -> queue map [ 277.871142] CPU 0
2013 Jun 03
0
[virtio_blk] BUG: unable to handle kernel paging request at ff7f5784
Greetings, I got the below dmesg and the first bad commit is commit b70aa55ec9532d5f5d3e367e4cad8997b1135f86 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk> [ 277.857736] blk-mq: CPU -> queue map [ 277.871142] CPU 0
2020 Jan 22
0
mmotm 2020-01-21-13-28 uploaded (nouveau)
On 1/21/20 1:29 PM, akpm at linux-foundation.org wrote: > The mm-of-the-moment snapshot 2020-01-21-13-28 has been uploaded to > > http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my -mm patch queue. Uploaded at random hopefully > more than once
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to
2017 Oct 05
0
24e700e291 ("Merge branch 'x86-apic-for-linus' of .."): WARNING: kernel stack regs at 979f9f70 in kworker/u4:1:648 has bad 'bp' value (null)
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 24e700e291d52bd200212487e2b654c0aa3f07a2 Merge: f57091767add2 c6ef89421e236 Author: Linus Torvalds <torvalds at linux-foundation.org> AuthorDate: Mon Sep 4 17:43:56 2017 -0700 Commit: Linus Torvalds <torvalds at
2017 Oct 05
0
24e700e291 ("Merge branch 'x86-apic-for-linus' of .."): WARNING: kernel stack regs at 979f9f70 in kworker/u4:1:648 has bad 'bp' value (null)
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 24e700e291d52bd200212487e2b654c0aa3f07a2 Merge: f57091767add2 c6ef89421e236 Author: Linus Torvalds <torvalds at linux-foundation.org> AuthorDate: Mon Sep 4 17:43:56 2017 -0700 Commit: Linus Torvalds <torvalds at
2006 Dec 14
1
xen-3.0.4-rc1: undefined reference to `remove_siblinginfo''
Hello, On my x86_64 box, when compiling the xen-3.0.4-rc1, if CONFIG_HOTPLUG_CPU is not set it produces an undefined reference to ''remove_siblinginfo'' that is used in arch/x86_64/kernel/smpboot.c drivers/built-in.o: In function `__cpu_up'': (.text+0x54c10): undefined reference to `remove_siblinginfo'' If CONFIG_HOTPLUG_CPU is set the compilation works fine.
2008 Apr 30
1
btrfs v0.14: kernel BUG at /home/trey/btrfs-0.14/volumes.c:1453
Hi, Kernel crash when i tried to mount btrfs: -- Machine: HP Proliant DL 380 G4 -- Ubuntu 8.04 Hardy Server root at btrfs:/home/trey# uname -a Linux btrfs 2.6.24-16-server #1 SMP Thu Apr 10 13:15:38 UTC 2008 x86_64 GNU/Linux -- root at btrfs:/home/trey# fdisk -l Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes 255 heads, 63 sectors/track, 17848 cylinders Units = cylinders of 16065 *
2005 Dec 10
1
[BUG 2.6.15-rc5] EXT3-fs error and soft lockup detected
Hello, I got this message when exiting qemu: [11266.262154] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318015 [11266.276897] Aborting journal on device hda. [11266.283815] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318016 [11266.293567] EXT3-fs error (device hda): ext3_free_blocks_sb: bit already cleared for block 318017
2019 Sep 23
2
[PATCH trivial 1/3] treewide: drivers: Fix Kconfig indentation
Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like: $ sed -e 's/^ /\t/' -i */Kconfig Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> --- drivers/acpi/Kconfig | 8 +- drivers/ata/Kconfig | 12 +-- drivers/auxdisplay/Kconfig | 14 +--