[Kernel-packages] [Bug 1953199] Re: 0-byte files created in overlay filesystem

2021-12-06 Thread Pete Woods 
So what we're saying here is that:

1. 
https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be
2. 
https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc

need backporting to Ubuntu 18.04's 5.4 series Kernel?

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

Title:
  0-byte files created in overlay filesystem

Status in linux-base package in Ubuntu:
  New

Bug description:
  Copied from
  
https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/:

  A number of users have reported that under certain conditions using
  the overlay filesystem, copy_file_range() can unexpectedly create a
  0-byte file. [0]

  This bug can cause significant problems because applications that copy
  files expect the target file to match the source immediately after the
  copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based
  CI tests started failing due to this bug, since Ruby's IO.copy_stream
  uses this system call. We have worked around the problem by touching
  the target file before using it, but this shouldn't be necessary.
  Other projects, such as Rust, have added similar workarounds. [1]

  As discussed in the linux-fsdevel mailing list [2], the bug appears to
  be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be
  able to cherry-pick the following upstream patches to fix this. Could
  you cherry-pick them to 5.10.x stable? I've confirmed that these
  patches, applied from top to bottom to that branch, pass the
  reproduction test [3]:

  82a763e61e2b601309d696d4fa514c77d64ee1be
  9b91b6b019fda817eb52f728eb9c79b3579760bc

  The diffstat:

   fs/overlayfs/file.c | 59
  +++
   1 file changed, 31 insertions(+), 28 deletions(-)

  Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable.

  [0] https://github.com/docker/for-linux/issues/1015
  [1] 
https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569
  [2] https://marc.info/?l=linux-fsdevel&m=163847383311699&w=2
  [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668

  ---

  I reproduced this bug in Ubuntu 18.04:

  ```
  # bash test.sh
  Sending build context to Docker daemon  43.05kB
  Step 1/2 : FROM debian:10.8-slim
   ---> 115566c891d1
  Step 2/2 : RUN apt update && apt install -y gcc strace
   ---> Using cache
   ---> 0dfb7ffcd427
  Successfully built 0dfb7ffcd427
  Successfully tagged strace:latest

  Local:
  OK

  Docker - mounted:
  Copy failed

  Docker - copied:
  OK
  ```

  ```
  root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04
  root@stanhu-ubuntu-18:/home/stanhu# uname -r
  5.4.0-1057-gcp
  ```

  Per [the latest update on the kernel stable mailing
  list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the
  kernel backport fix for 5.10 has been queued for review and should
  land in the [`stable-5.10.y`
  
branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y)
  soon.

  To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now,
  unless you backport the two patches below:

  1. 
https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be
  1. 
https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc

  I've confirmed that 5.5.19 does NOT have this bug, and it was
  introduced in 5.6.0 via
  
https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+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 1970586] [NEW] No sound support on Linux AWS kernel (but supported on GCP)

2022-04-27 Thread Pete Woods 
Public bug reported:

In GCP images it is possible to create virtual MIDI devices and
generally do stuff like audio routing, etc.

At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
our customers use this functionality to test audio equipment in their CI
runs.

Unfortunately they cannot run their tests on our AWS based VMs, as there
is no sound support compiled into the kernel on the AWS kernel and
images.

See the package listings for the other kernels for, e.g. the loopback driver:
```
linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
```

We would love to be able to install the sound drivers (especially snd-
aloop) with the linux-modules-extra-aws package, but currently cannot,
and obviously do not want to start running our own kernels, as then we
lose the immediacy of kernel patches provided upstream by Canonical.

You can see the difference in the GCP:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

and AWS kernel:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

again there. The reasoning for the removal appears to be in this commit from 
2016:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
- See the package listings for, e.g. the loopback driver:
+ See the package listings for the other kernels for, e.g. the loopback driver:
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
  See the package listings for the other kernels for, e.g. the loopback driver:
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.
+ 
+ You can see the difference in the GCP:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884
+ 
+ and AWS kernel:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu
+ 
+ again there. The reasoning for the removal appears to be in this commit:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they canno

[Kernel-packages] [Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

2022-04-27 Thread Pete Woods 
** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.
  
  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884
  
  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu
  
- again there. The reasoning for the removal appears to be in this commit:
+ again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

2022-04-27 Thread Pete Woods 
Thankyou for doing this so quickly - let me see if I can get one of the
customers setup to work with this kernel.

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

2022-04-28 Thread Pete Woods 
I have asked the customer if they can provide a script so I get verify
if their virtual MIDI devices will work on this new kernel (rather than
guess at their needs).

I think they'll need at least:

CONFIG_SND_RAWMIDI=m

CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DEVICE=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_SEQ_MIDI=m
CONFIG_SND_SEQ_MIDI_EMUL=m
CONFIG_SND_SEQ_MIDI_EVENT=m
CONFIG_SND_SEQ_VIRMIDI=m

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

2022-05-16 Thread Pete Woods 
With input from our customer, I have created a very simple NPM project
to test out the sound / virtual MIDI support:

https://github.com/CircleCI-Public/midi-test

I'm getting the expected failures with it on the latest 22.04 AMI, so
I'll try the new kernel next.

$ node .
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file 
or directory

MidiOutAlsa::initialize: error creating ALSA sequencer client object.

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory

MidiInAlsa::initialize: error creating ALSA sequencer client object.

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory

MidiOutAlsa::initialize: error creating ALSA sequencer client object.

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory

MidiInAlsa::initialize: error creating ALSA sequencer client object.

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

2022-05-18 Thread Pete Woods 
This appears to work with my simple script, and now pass the tests in
the customer's MIDI library.

Thanks very much for your time here!


> mocha test/unit/*.js && node test/virtual-loopback-test-automated.js


  midi.Input
✔ should raise when not called with new
✔ should be an emitter
.getPortCount
  ✔ .getPortCoun should return an integer
.getPortName
  ✔ requires an argument
  ✔ requires an integer

MidiInAlsa::getPortName: error looking for port name!

  ✔ returns an empty string for unknown port
.openPort
  ✔ requires an argument
  ✔ requires an integer
  ✔ requires a valid port
.openVirtualPort
  ✔ requires an argument
  ✔ requires a string
.on('message')
  ✔ allows promises to resolve

  midi.Output
✔ should raise when not called with new
✔ should not be an emitter
.getPortCount
  ✔ should return an integer
.getPortName
  ✔ requires an argument
  ✔ requires an integer

MidiOutAlsa::getPortName: error looking for port name!

  ✔ returns an empty string for unknown port
.openPort
  ✔ requires an argument
  ✔ requires an integer
  ✔ requires a valid port
.openVirtualPort
  ✔ requires an argument
  ✔ requires a string
.closePort
  ✔ allows you to close a port that was not opened
.send
  ✔ should require an array argument
.sendMessage
  ✔ should require an array argument


  26 passing (61ms)

Enumerating inputs
Input found: Midi Through:Midi Through Port-0 14:0
Input found: RtMidi Output Client:node-midi Virtual Output 128:0
Enumerating outputs
Output found: Midi Through:Midi Through Port-0 14:0
Output found: RtMidi Output Client:node-midi Virtual Output 128:0
Sending message
Sending message
Sending message
Sending message

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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 1970586] Re: No sound support on Linux AWS/Azure kernels (but supported on GCP)

2022-05-28 Thread Pete Woods 
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  No sound support on Linux AWS/Azure kernels (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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