[Kernel-packages] [Bug 1879161] Re: Building linux-image-unsigned with existing .config fails

2020-05-17 Thread Shakthi Kannan
This is on a private instance and I cannot run apport-collect. I am
changing the bug status to 'Confirmed'. Please let me know if you need
any more information. Thanks!

** Changed in: linux (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879161

Title:
  Building linux-image-unsigned with existing .config fails

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Objective: For a working 4.15.0-99-generic (x86_64) on Ubuntu 18.04.4
  LTS (Bionic Beaver), re-build the Linux kernel sources with
  CONFIG_NO_HZ_FULL=y.

  Steps followed:

  Uncomment deb-src in /etc/apt/sources.list, so that we can obtain the
  Linux kernel sources, and run "apt-get update".

$ sudo apt-get build-dep linux-image-4.15.0-99-generic
$ sudo apt-get install libncurses5-dev flex bison openssl libssl-dev dkms 
libelf-dev \
libudev-dev libpci-dev libiberty-dev autoconf

$ mkdir code/kernel; cd code/kernel
$ apt source linux-image-unsigned-4.15.0-99-generic
$ cd linux-4.15.0
$ chmod a+x debian/rules
$ chmod a+x debian/scripts/*
$ chmod a+x debian/scripts/misc*
$ fakeroot debian/rules clean
$ cp /boot/config-4.15.0-99-generic .config

$ fakeroot debian/rules startnewrelease
  dh_testdir
  Creating new changelog set 4.15.0-100.101...

$ fakeroot debian/rules editconfigs

  Edit amd64/config.flavour.generic, set CONFIG_NO_HZ_FULL and save
  config to .config.

$ fakeroot debian/rules binary

  The outputs are in the attached files: binary-build-output.txt and
  binary-build-error.txt.

  In order to handle ABI, I touched an ignore file in
  debian.master/abi/4.15.0-97.98/amd64/ignore and the relevant output
  files are binary-build-output-no-abi.txt and binary-build-error-no-
  abi.txt.

  The linux-image...deb file did not get created. The following files were 
created:
linux-cloud-tools-common_4.15.0-99.100_all.deb
linux-doc_4.15.0-99.100_all.deb
linux-headers-4.15.0-99_4.15.0-99.100_all.deb
linux-source-4.15.0_4.15.0-99.100_all.deb
linux-tools-common_4.15.0-99.100_all.deb
linux-tools-host_4.15.0-99.100_all.deb

  I used the following documents for reference:

  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

  https://ahelpme.com/linux/ubuntu/rebuild-the-official-ubuntu-kernel-
  ubuntu-16-04-lts/

  https://help.ubuntu.com/community/Kernel/Compile

  Most of the documentation seem outdated or do not work as expected.

  Questions:

  1. Can you please provide a tutorial on how to re-build a Ubuntu
  specific kernel with a working .config successfully?

  2. Should we use apt source "linux" instead of using a specific kernel
  version?

  3. From 'dpkg -l | grep linux-image', I see:

  ii  linux-image-4.15.0-99-generic 4.15.0-99.100  amd64  Signed
  kernel image generic

  What is the meaning of the naming (4.15.0-99-generic and
  4.15.0-99.100) convention used here?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879161/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1879161] Re: Building linux-image-unsigned with existing .config fails

2020-05-17 Thread Shakthi Kannan
** Attachment added: "binary-build-output-no-abi.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879161/+attachment/5372938/+files/binary-build-output-no-abi.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879161

Title:
  Building linux-image-unsigned with existing .config fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Objective: For a working 4.15.0-99-generic (x86_64) on Ubuntu 18.04.4
  LTS (Bionic Beaver), re-build the Linux kernel sources with
  CONFIG_NO_HZ_FULL=y.

  Steps followed:

  Uncomment deb-src in /etc/apt/sources.list, so that we can obtain the
  Linux kernel sources, and run "apt-get update".

$ sudo apt-get build-dep linux-image-4.15.0-99-generic
$ sudo apt-get install libncurses5-dev flex bison openssl libssl-dev dkms 
libelf-dev \
libudev-dev libpci-dev libiberty-dev autoconf

$ mkdir code/kernel; cd code/kernel
$ apt source linux-image-unsigned-4.15.0-99-generic
$ cd linux-4.15.0
$ chmod a+x debian/rules
$ chmod a+x debian/scripts/*
$ chmod a+x debian/scripts/misc*
$ fakeroot debian/rules clean
$ cp /boot/config-4.15.0-99-generic .config

$ fakeroot debian/rules startnewrelease
  dh_testdir
  Creating new changelog set 4.15.0-100.101...

$ fakeroot debian/rules editconfigs

  Edit amd64/config.flavour.generic, set CONFIG_NO_HZ_FULL and save
  config to .config.

$ fakeroot debian/rules binary

  The outputs are in the attached files: binary-build-output.txt and
  binary-build-error.txt.

  In order to handle ABI, I touched an ignore file in
  debian.master/abi/4.15.0-97.98/amd64/ignore and the relevant output
  files are binary-build-output-no-abi.txt and binary-build-error-no-
  abi.txt.

  The linux-image...deb file did not get created. The following files were 
created:
linux-cloud-tools-common_4.15.0-99.100_all.deb
linux-doc_4.15.0-99.100_all.deb
linux-headers-4.15.0-99_4.15.0-99.100_all.deb
linux-source-4.15.0_4.15.0-99.100_all.deb
linux-tools-common_4.15.0-99.100_all.deb
linux-tools-host_4.15.0-99.100_all.deb

  I used the following documents for reference:

  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

  https://ahelpme.com/linux/ubuntu/rebuild-the-official-ubuntu-kernel-
  ubuntu-16-04-lts/

  https://help.ubuntu.com/community/Kernel/Compile

  Most of the documentation seem outdated or do not work as expected.

  Questions:

  1. Can you please provide a tutorial on how to re-build a Ubuntu
  specific kernel with a working .config successfully?

  2. Should we use apt source "linux" instead of using a specific kernel
  version?

  3. From 'dpkg -l | grep linux-image', I see:

  ii  linux-image-4.15.0-99-generic 4.15.0-99.100  amd64  Signed
  kernel image generic

  What is the meaning of the naming (4.15.0-99-generic and
  4.15.0-99.100) convention used here?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879161/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1879161] Re: Building linux-image-unsigned with existing .config fails

2020-05-17 Thread Shakthi Kannan
** Attachment added: "binary-build-error.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879161/+attachment/5372937/+files/binary-build-error.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879161

Title:
  Building linux-image-unsigned with existing .config fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Objective: For a working 4.15.0-99-generic (x86_64) on Ubuntu 18.04.4
  LTS (Bionic Beaver), re-build the Linux kernel sources with
  CONFIG_NO_HZ_FULL=y.

  Steps followed:

  Uncomment deb-src in /etc/apt/sources.list, so that we can obtain the
  Linux kernel sources, and run "apt-get update".

$ sudo apt-get build-dep linux-image-4.15.0-99-generic
$ sudo apt-get install libncurses5-dev flex bison openssl libssl-dev dkms 
libelf-dev \
libudev-dev libpci-dev libiberty-dev autoconf

$ mkdir code/kernel; cd code/kernel
$ apt source linux-image-unsigned-4.15.0-99-generic
$ cd linux-4.15.0
$ chmod a+x debian/rules
$ chmod a+x debian/scripts/*
$ chmod a+x debian/scripts/misc*
$ fakeroot debian/rules clean
$ cp /boot/config-4.15.0-99-generic .config

$ fakeroot debian/rules startnewrelease
  dh_testdir
  Creating new changelog set 4.15.0-100.101...

$ fakeroot debian/rules editconfigs

  Edit amd64/config.flavour.generic, set CONFIG_NO_HZ_FULL and save
  config to .config.

$ fakeroot debian/rules binary

  The outputs are in the attached files: binary-build-output.txt and
  binary-build-error.txt.

  In order to handle ABI, I touched an ignore file in
  debian.master/abi/4.15.0-97.98/amd64/ignore and the relevant output
  files are binary-build-output-no-abi.txt and binary-build-error-no-
  abi.txt.

  The linux-image...deb file did not get created. The following files were 
created:
linux-cloud-tools-common_4.15.0-99.100_all.deb
linux-doc_4.15.0-99.100_all.deb
linux-headers-4.15.0-99_4.15.0-99.100_all.deb
linux-source-4.15.0_4.15.0-99.100_all.deb
linux-tools-common_4.15.0-99.100_all.deb
linux-tools-host_4.15.0-99.100_all.deb

  I used the following documents for reference:

  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

  https://ahelpme.com/linux/ubuntu/rebuild-the-official-ubuntu-kernel-
  ubuntu-16-04-lts/

  https://help.ubuntu.com/community/Kernel/Compile

  Most of the documentation seem outdated or do not work as expected.

  Questions:

  1. Can you please provide a tutorial on how to re-build a Ubuntu
  specific kernel with a working .config successfully?

  2. Should we use apt source "linux" instead of using a specific kernel
  version?

  3. From 'dpkg -l | grep linux-image', I see:

  ii  linux-image-4.15.0-99-generic 4.15.0-99.100  amd64  Signed
  kernel image generic

  What is the meaning of the naming (4.15.0-99-generic and
  4.15.0-99.100) convention used here?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879161/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1879161] [NEW] Building linux-image-unsigned with existing .config fails

2020-05-17 Thread Shakthi Kannan
Public bug reported:

Objective: For a working 4.15.0-99-generic (x86_64) on Ubuntu 18.04.4
LTS (Bionic Beaver), re-build the Linux kernel sources with
CONFIG_NO_HZ_FULL=y.

Steps followed:

Uncomment deb-src in /etc/apt/sources.list, so that we can obtain the
Linux kernel sources, and run "apt-get update".

  $ sudo apt-get build-dep linux-image-4.15.0-99-generic
  $ sudo apt-get install libncurses5-dev flex bison openssl libssl-dev dkms 
libelf-dev \
  libudev-dev libpci-dev libiberty-dev autoconf

  $ mkdir code/kernel; cd code/kernel
  $ apt source linux-image-unsigned-4.15.0-99-generic
  $ cd linux-4.15.0
  $ chmod a+x debian/rules
  $ chmod a+x debian/scripts/*
  $ chmod a+x debian/scripts/misc*
  $ fakeroot debian/rules clean
  $ cp /boot/config-4.15.0-99-generic .config

  $ fakeroot debian/rules startnewrelease
dh_testdir
Creating new changelog set 4.15.0-100.101...

  $ fakeroot debian/rules editconfigs

Edit amd64/config.flavour.generic, set CONFIG_NO_HZ_FULL and save config
to .config.

  $ fakeroot debian/rules binary

The outputs are in the attached files: binary-build-output.txt and
binary-build-error.txt.

In order to handle ABI, I touched an ignore file in
debian.master/abi/4.15.0-97.98/amd64/ignore and the relevant output
files are binary-build-output-no-abi.txt and binary-build-error-no-
abi.txt.

The linux-image...deb file did not get created. The following files were 
created:
  linux-cloud-tools-common_4.15.0-99.100_all.deb
  linux-doc_4.15.0-99.100_all.deb
  linux-headers-4.15.0-99_4.15.0-99.100_all.deb
  linux-source-4.15.0_4.15.0-99.100_all.deb
  linux-tools-common_4.15.0-99.100_all.deb
  linux-tools-host_4.15.0-99.100_all.deb

I used the following documents for reference:

https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

https://ahelpme.com/linux/ubuntu/rebuild-the-official-ubuntu-kernel-
ubuntu-16-04-lts/

https://help.ubuntu.com/community/Kernel/Compile

Most of the documentation seem outdated or do not work as expected.

Questions:

1. Can you please provide a tutorial on how to re-build a Ubuntu
specific kernel with a working .config successfully?

2. Should we use apt source "linux" instead of using a specific kernel
version?

3. From 'dpkg -l | grep linux-image', I see:

ii  linux-image-4.15.0-99-generic 4.15.0-99.100  amd64  Signed
kernel image generic

What is the meaning of the naming (4.15.0-99-generic and 4.15.0-99.100)
convention used here?

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: bionic

** Attachment added: "binary-build-output.txt"
   
https://bugs.launchpad.net/bugs/1879161/+attachment/5372936/+files/binary-build-output.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879161

Title:
  Building linux-image-unsigned with existing .config fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Objective: For a working 4.15.0-99-generic (x86_64) on Ubuntu 18.04.4
  LTS (Bionic Beaver), re-build the Linux kernel sources with
  CONFIG_NO_HZ_FULL=y.

  Steps followed:

  Uncomment deb-src in /etc/apt/sources.list, so that we can obtain the
  Linux kernel sources, and run "apt-get update".

$ sudo apt-get build-dep linux-image-4.15.0-99-generic
$ sudo apt-get install libncurses5-dev flex bison openssl libssl-dev dkms 
libelf-dev \
libudev-dev libpci-dev libiberty-dev autoconf

$ mkdir code/kernel; cd code/kernel
$ apt source linux-image-unsigned-4.15.0-99-generic
$ cd linux-4.15.0
$ chmod a+x debian/rules
$ chmod a+x debian/scripts/*
$ chmod a+x debian/scripts/misc*
$ fakeroot debian/rules clean
$ cp /boot/config-4.15.0-99-generic .config

$ fakeroot debian/rules startnewrelease
  dh_testdir
  Creating new changelog set 4.15.0-100.101...

$ fakeroot debian/rules editconfigs

  Edit amd64/config.flavour.generic, set CONFIG_NO_HZ_FULL and save
  config to .config.

$ fakeroot debian/rules binary

  The outputs are in the attached files: binary-build-output.txt and
  binary-build-error.txt.

  In order to handle ABI, I touched an ignore file in
  debian.master/abi/4.15.0-97.98/amd64/ignore and the relevant output
  files are binary-build-output-no-abi.txt and binary-build-error-no-
  abi.txt.

  The linux-image...deb file did not get created. The following files were 
created:
linux-cloud-tools-common_4.15.0-99.100_all.deb
linux-doc_4.15.0-99.100_all.deb
linux-headers-4.15.0-99_4.15.0-99.100_all.deb
linux-source-4.15.0_4.15.0-99.100_all.deb
linux-tools-common_4.15.0-99.100_all.deb
linux-tools-host_4.15.0-99.100_all.deb

  I used the following documents for reference:

  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

  https://ahelpme.com/linux/ubuntu/rebuild-the-official-ubuntu-kernel-
  ubuntu-16-04-lts/

  https://help.ubuntu.com/community/Kernel/Compile

  Most of the documentati

[Kernel-packages] [Bug 1879161] Re: Building linux-image-unsigned with existing .config fails

2020-05-17 Thread Shakthi Kannan
** Attachment added: "binary-build-error-no-abi.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879161/+attachment/5372939/+files/binary-build-error-no-abi.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879161

Title:
  Building linux-image-unsigned with existing .config fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Objective: For a working 4.15.0-99-generic (x86_64) on Ubuntu 18.04.4
  LTS (Bionic Beaver), re-build the Linux kernel sources with
  CONFIG_NO_HZ_FULL=y.

  Steps followed:

  Uncomment deb-src in /etc/apt/sources.list, so that we can obtain the
  Linux kernel sources, and run "apt-get update".

$ sudo apt-get build-dep linux-image-4.15.0-99-generic
$ sudo apt-get install libncurses5-dev flex bison openssl libssl-dev dkms 
libelf-dev \
libudev-dev libpci-dev libiberty-dev autoconf

$ mkdir code/kernel; cd code/kernel
$ apt source linux-image-unsigned-4.15.0-99-generic
$ cd linux-4.15.0
$ chmod a+x debian/rules
$ chmod a+x debian/scripts/*
$ chmod a+x debian/scripts/misc*
$ fakeroot debian/rules clean
$ cp /boot/config-4.15.0-99-generic .config

$ fakeroot debian/rules startnewrelease
  dh_testdir
  Creating new changelog set 4.15.0-100.101...

$ fakeroot debian/rules editconfigs

  Edit amd64/config.flavour.generic, set CONFIG_NO_HZ_FULL and save
  config to .config.

$ fakeroot debian/rules binary

  The outputs are in the attached files: binary-build-output.txt and
  binary-build-error.txt.

  In order to handle ABI, I touched an ignore file in
  debian.master/abi/4.15.0-97.98/amd64/ignore and the relevant output
  files are binary-build-output-no-abi.txt and binary-build-error-no-
  abi.txt.

  The linux-image...deb file did not get created. The following files were 
created:
linux-cloud-tools-common_4.15.0-99.100_all.deb
linux-doc_4.15.0-99.100_all.deb
linux-headers-4.15.0-99_4.15.0-99.100_all.deb
linux-source-4.15.0_4.15.0-99.100_all.deb
linux-tools-common_4.15.0-99.100_all.deb
linux-tools-host_4.15.0-99.100_all.deb

  I used the following documents for reference:

  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

  https://ahelpme.com/linux/ubuntu/rebuild-the-official-ubuntu-kernel-
  ubuntu-16-04-lts/

  https://help.ubuntu.com/community/Kernel/Compile

  Most of the documentation seem outdated or do not work as expected.

  Questions:

  1. Can you please provide a tutorial on how to re-build a Ubuntu
  specific kernel with a working .config successfully?

  2. Should we use apt source "linux" instead of using a specific kernel
  version?

  3. From 'dpkg -l | grep linux-image', I see:

  ii  linux-image-4.15.0-99-generic 4.15.0-99.100  amd64  Signed
  kernel image generic

  What is the meaning of the naming (4.15.0-99-generic and
  4.15.0-99.100) convention used here?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879161/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp