similar to: xen-3.0.4-rc1: undefined reference to `remove_siblinginfo''

Wanted to pass this error by you and get your feedback ... I tried building a debug kernel with spinlock related debug info. The tree was pulled when the Xen-305 first rc was announced (and has not been updated since) make -C /root/src/mercurial/xen-3.0.5-testing.hg/linux-2.6.18-xen O=/root/src/mercurial/xen-3.0.5-testing.hg/build-linux-2.6.18-xen_x86_64 vmlinuz Using

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

Hi I just tried to install Xen (3.0.4) from source. The Installation process finished without any errors. Then after booting the XEN-Image (without initrd) I got a Kernel Panic. My machine said it was unuable to mount root fs from Sda1 or unknown-block(0,0) After some research on google, I built the SCSI and SATA drivers in the XEN-kernel and now this kernel Panic occurs: Kernel Panic-not

On Sat, 17 Oct 2020, Joe Perches wrote: > On Sat, 2020-10-17 at 09:09 -0700, trix at redhat.com wrote: > > From: Tom Rix <trix at redhat.com> > > > > This is a upcoming change to clean up a new warning treewide. > > I am wondering if the change could be one mega patch (see below) or > > normal patch per file about 100 patches or somewhere half way by

On Sat, 17 Oct 2020, Joe Perches wrote: > On Sat, 2020-10-17 at 09:09 -0700, trix at redhat.com wrote: > > From: Tom Rix <trix at redhat.com> > > > > This is a upcoming change to clean up a new warning treewide. > > I am wondering if the change could be one mega patch (see below) or > > normal patch per file about 100 patches or somewhere half way by

On Sat, 2020-10-17 at 09:09 -0700, trix at redhat.com wrote: > From: Tom Rix <trix at redhat.com> > > This is a upcoming change to clean up a new warning treewide. > I am wondering if the change could be one mega patch (see below) or > normal patch per file about 100 patches or somewhere half way by collecting > early acks. > > clang has a number of useful, new

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 *

Hi List, I encountered some problems with PCI pass to PVM using 2.6.18.8 kernel. When I try to pass an USB bus I get: usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:1d.1 (0000 -> 0001) uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus

Hi List, I encountered some problems with PCI pass to PVM using 2.6.18.8 kernel. When I try to pass an USB bus I get: usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:1d.1 (0000 -> 0001) uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus

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

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

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

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

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

Hi all, This series aims to fix almost all remaining fall-through warnings in order to enable -Wimplicit-fallthrough for Clang. In preparation to enable -Wimplicit-fallthrough for Clang, explicitly add multiple break/goto/return/fallthrough statements instead of just letting the code fall through to the next case. Notice that in order to enable -Wimplicit-fallthrough for Clang, this change[1]

Hi all, This series aims to fix almost all remaining fall-through warnings in order to enable -Wimplicit-fallthrough for Clang. In preparation to enable -Wimplicit-fallthrough for Clang, explicitly add multiple break/goto/return/fallthrough statements instead of just letting the code fall through to the next case. Notice that in order to enable -Wimplicit-fallthrough for Clang, this change[1]

Hi all, This series aims to fix almost all remaining fall-through warnings in order to enable -Wimplicit-fallthrough for Clang. In preparation to enable -Wimplicit-fallthrough for Clang, explicitly add multiple break/goto/return/fallthrough statements instead of just letting the code fall through to the next case. Notice that in order to enable -Wimplicit-fallthrough for Clang, this change[1]

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:

My kernel crashes every time I shut down dom0 This crash was not happening before I installed the Xen hypervisor Any ideas? (XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi at debian.org) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: com1=9600,8n1 console=com1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods:

From: Tom Rix <trix at redhat.com> This is a upcoming change to clean up a new warning treewide. I am wondering if the change could be one mega patch (see below) or normal patch per file about 100 patches or somewhere half way by collecting early acks. clang has a number of useful, new warnings see