[Kernel-packages] [Bug 1545330] Re: [wily][regression] systemtap script compilation broken by new kernels
By the way, a simple diagnostic for whether any particular version of
systemtap has been ported to a kernel is to run
% stap -V
Systemtap translator/driver (version 4.1/0.174, rpm
4.1-0.20190327git2ede4cecb20c.fc28)
Copyright (C) 2005-2019 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.18 ... 5.0-rc3
enabled features: AVAHI BOOST_STRING_REF DYNINST BPF JAVA PYTHON2 PYTHON3
LIBRPM LIBSQLITE3 LIBVIRT LIBXML2 NLS NSS READLINE
Note the "tested kernel versions" line. If your kernel is newer than
that, you'll need to switch to a fresher upstream systemtap version.
--
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/1545330
Title:
[wily][regression] systemtap script compilation broken by new kernels
Status in linux package in Ubuntu:
Fix Released
Status in systemtap package in Ubuntu:
Fix Released
Status in linux source package in Wily:
Fix Released
Status in systemtap source package in Wily:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in systemtap source package in Xenial:
Fix Released
Status in systemtap package in Fedora:
Fix Released
Bug description:
The following errors appear when compiling any systemtap script:
In file included from include/linux/mutex.h:15:0,
from
/tmp/stapbdpxn3/stap_a0ec17f995e8f89d672d8c2eb7fe7c24_1693_src.c:25:
include/linux/spinlock_types.h:55:14: error: ‘__ARCH_SPIN_LOCK_UNLOCKED’
undeclared here (not in a function)
.raw_lock = __ARCH_SPIN_LOCK_UNLOCKED, \
^
include/linux/spinlock_types.h:79:15: note: in expansion of macro
‘__RAW_SPIN_LOCK_INITIALIZER’
{ { .rlock = __RAW_SPIN_LOCK_INITIALIZER(lockname) } }
^
include/linux/spinlock_types.h:82:16: note: in expansion of macro
‘__SPIN_LOCK_INITIALIZER’
(spinlock_t ) __SPIN_LOCK_INITIALIZER(lockname)
^
include/linux/mutex.h:111:18: note: in expansion of macro
‘__SPIN_LOCK_UNLOCKED’
, .wait_lock = __SPIN_LOCK_UNLOCKED(lockname.wait_lock) \
^
include/linux/mutex.h:117:27: note: in expansion of macro
‘__MUTEX_INITIALIZER’
struct mutex mutexname = __MUTEX_INITIALIZER(mutexname)
Upstream fix:
https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=320e1ecb16427b5769f0f5a097d80823ee1fb765
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545330/+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 1325713] [NEW] need vdso*.so images installed under /lib/modules for systemtap etc.
Public bug reported:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship
these .so's in the same location.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124377/+files/ProcCpuinfo.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] Re: need vdso*.so images installed under /lib/modules for systemtap etc.
apport information
** Tags added: apport-collected trusty
** Description changed:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
- Please make the change to have the linux-image deb preserve & ship these
- .so's in the same location.
+ Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
+ crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
+ InstallationDate: Installed on 2014-04-22 (41 days ago)
+ InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
+ IwConfig:
+ eth0 no wireless extensions.
+
+ lono wireless extensions.
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
+ MachineType: Bochs Bochs
+ Package: linux (not installed)
+ PciMultimedia:
+
+ ProcFB: 0 cirrusdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
+ ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
+ RelatedPackageVersions:
+ linux-restricted-modules-3.13.0-24-generic N/A
+ linux-backports-modules-3.13.0-24-generic N/A
+ linux-firmware 1.127.2
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: trusty
+ Uname: Linux 3.13.0-24-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/01/2011
+ dmi.bios.vendor: Bochs
+ dmi.bios.version: Bochs
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Bochs
+ dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
+ dmi.product.name: Bochs
+ dmi.sys.vendor: Bochs
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124374/+files/BootDmesg.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
[Kernel-packages] [Bug 1325713] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124376/+files/Lspci.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124375/+files/CurrentDmesg.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124380/+files/ProcModules.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124379/+files/ProcInterrupts.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] UdevLog.txt
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124382/+files/UdevLog.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124378/+files/ProcEnviron.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124381/+files/UdevDb.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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 1325713] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1325713/+attachment/4124383/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1325713
Title:
need vdso*.so images installed under /lib/modules for systemtap etc.
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The vdso* files are built into the kernel for loading into userspace
binaries to accelerate various kernel-related operations. These files
do not need to be packaged & installed for the system to operate, and
indeed they aren't part of the linux-image* deb's in Ubuntu. However,
tools such as systemtap (and possibly perf and oprofile;
https://bugs.launchpad.net/ubuntu/+source/oprofile/+bug/295975) need
them, in order to unwind user-space stacks.
In Fedora, these vdso.so's are installed with:
[...]
%{make} -s ARCH=$Arch INSTALL_MOD_PATH=$RPM_BUILD_ROOT vdso_install
KERNELRELEASE=$KernelVer
[...]
so they show up under /usr/lib/modules/`uname -r`/vdso/.
Please make the change to have the linux-image deb preserve & ship these
.so's in the same location.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 2 14:54 seq
crw-rw 1 root audio 116, 33 Jun 2 14:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/vm--ubuntu14--vg-swap_1
InstallationDate: Installed on 2014-04-22 (41 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic
root=/dev/mapper/vm--ubuntu14--vg-root ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare stapdev stapusr sudo
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713/+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 320638] Re: hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device mapper on top => data corruption (bio too big device md0 (248 > 240))
The resolution of "fix released" is incorrect: the kernel bug is still present. The debian bug was closed due to age rather due to being fixed. -- 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/320638 Title: hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device mapper on top => data corruption (bio too big device md0 (248 > 240)) Status in The Linux Kernel: Fix Released Status in mdadm - Tool for managing linux software RAID arrays.: Confirmed Status in “debian-installer” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Won't Fix Status in “mdadm” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Invalid Bug description: Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the device mapper and filesystem layer on top of the raid can not (always?) cope with that. Observations: * "bio too big device mdX (248 > 240)" messages in the syslog * read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.) Expected: Adding and removing members to running raids (hotplugging) should not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present. Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices). Fix: Upsteam has no formal bug tracking, but a mailing list. The response was that finally this needs to be "fixed [outside of mdadm] by cleaning up the bio path so that big bios are split by the device that needs the split, not be the fs sending the bio." However, in the meantime mdadm needs to saveguard against the date corruption: > > [The mdadm] fix is to reject the added device [if] its limits are > > too low. > > Good Idea to avoid the data corruption. MD could save the > max_sectors default limit for arrays. If the array is modified and the new > limit gets smaller, postpone the sync until the next assembe/restart. > > And of course print a message if postponing, that explains when --force would be save. > What ever that would be: no block device abstraction layer (device mapper, lvm, luks,...) > between an unmounted? ext, fat?, ...? filesystem and md? As upsteam does not do public bug tracking, the status and rememberence of this need remains unsure though. --- This is on a MSI Wind U100 and I've got the following stack running: HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser Whenever I remove the HDD from the Raid1 > mdadm /dev/md0 --fail /dev/sda2 > mdadm /dev/md0 --remove /dev/sda2) for powersaving reasons, I cannot run any apt related tools. > sudo apt-get update [...] Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources Reading package lists... Error! E: Read error - read (5 Input/output error) E: The package lists or status file could not be parsed or opened. Taking a look at the kernel log shows (and many more above): > dmesg|tail [ 9479.330550] bio too big device md0 (248 > 240) [ 9479.331375] bio too big device md0 (248 > 240) [ 9479.332182] bio too big device md0 (248 > 240) [ 9611.980294] bio too big device md0 (248 > 240) [ 9742.929761] bio too big device md0 (248 > 240) [ 9852.932001] bio too big device md0 (248 > 240) [ 9852.935395] bio too big device md0 (248 > 240) [ 9852.938064] bio too big device md0 (248 > 240) [ 9853.081046] bio too big device md0 (248 > 240) [ 9853.081688] bio too big device md0 (248 > 240) $ sudo mdadm --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Tue Jan 13 11:25:57 2009 Raid Level : raid1 Array Size : 3871552 (3.69 GiB 3.96 GB) Used Dev Size : 3871552 (3.69 GiB 3.96 GB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 0 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Fri Jan 23 21:47:35 2009 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain) Events : 0.8767 Number Major Minor RaidDevice State 0 000 removed 1 8 171
