Processed: bug 1027921 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=204769 https://lore.kernel.org/linux-scsi/bug-204769-11...@https.bugzilla.kernel.org%2F/
Processing commands for cont...@bugs.debian.org: > forwarded 1027921 https://bugzilla.kernel.org/show_bug.cgi?id=204769 > https://lore.kernel.org/linux-scsi/bug-204769-11...@https.bugzilla.kernel.org%2F/ Bug #1027921 [src:linux] linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=204769 https://lore.kernel.org/linux-scsi/bug-204769-11...@https.bugzilla.kernel.org%2F/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996839: [PATCH v1] perf script flamegraph: Avoid d3-flame-graph package dependency
Currently flame graph generation requires a d3-flame-graph template to
be installed. Unfortunately this is hard to come by for things like
Debian [1]. If the template isn't installed warn and download it from
jsdelivr CDN. If downloading fails generate a minimal flame graph
again with the javascript coming from jsdelivr CDN.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996839
Signed-off-by: Ian Rogers
---
tools/perf/scripts/python/flamegraph.py | 63 ++---
1 file changed, 45 insertions(+), 18 deletions(-)
diff --git a/tools/perf/scripts/python/flamegraph.py
b/tools/perf/scripts/python/flamegraph.py
index b6af1dd5f816..808b0e1c9be5 100755
--- a/tools/perf/scripts/python/flamegraph.py
+++ b/tools/perf/scripts/python/flamegraph.py
@@ -25,6 +25,27 @@ import io
import argparse
import json
import subprocess
+import urllib.request
+
+minimal_html = """
+ https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/d3-flamegraph.css;>
+
+
+
+ https://d3js.org/d3.v7.js";>
+ https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/d3-flamegraph.min.js";>
+
+ const stacks = [/** @flamegraph_json **/];
+ // Note, options is unused.
+ const options = [/** @options_json **/];
+
+ var chart = flamegraph();
+ d3.select("#chart")
+.datum(stacks[0])
+.call(chart);
+
+
+"""
# pylint: disable=too-few-public-methods
class Node:
@@ -50,15 +71,18 @@ class FlameGraphCLI:
self.args = args
self.stack = Node("all", "root")
-if self.args.format == "html" and \
-not os.path.isfile(self.args.template):
-print("Flame Graph template {} does not exist. Please install "
- "the js-d3-flame-graph (RPM) or libjs-d3-flame-graph (deb) "
- "package, specify an existing flame graph template "
- "(--template PATH) or another output format "
- "(--format FORMAT).".format(self.args.template),
- file=sys.stderr)
-sys.exit(1)
+if self.args.format == "html":
+if os.path.isfile(self.args.template):
+self.template = f"file://{self.args.template}"
+else:
+print(f"""
+Warning: Flame Graph template '{self.args.template}'
+does not exist, a template will be downloaded via http. To avoid this
+please install a package such as the js-d3-flame-graph or
+libjs-d3-flame-graph, specify an existing flame graph template
+(--template PATH) or another output format (--format FORMAT).
+""", file=sys.stderr)
+self.template =
"https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/templates/d3-flamegraph-base.html;
@staticmethod
def get_libtype_from_dso(dso):
@@ -129,15 +153,18 @@ class FlameGraphCLI:
options_json = json.dumps(options)
try:
-with io.open(self.args.template, encoding="utf-8") as template:
-output_str = (
-template.read()
-.replace("/** @options_json **/", options_json)
-.replace("/** @flamegraph_json **/", stacks_json)
-)
-except IOError as err:
-print("Error reading template file: {}".format(err),
file=sys.stderr)
-sys.exit(1)
+with urllib.request.urlopen(self.template) as template:
+output_str = '\n'.join([
+l.decode('utf-8') for l in template.readlines()
+])
+except Exception as err:
+print(f"Error reading template {self.template}: {err}\n"
+ "a minimal flame graph will be generated",
file=sys.stderr)
+output_str = minimal_html
+
+output_str = output_str.replace("/** @options_json **/",
options_json)
+output_str = output_str.replace("/** @flamegraph_json **/",
stacks_json)
+
output_fn = self.args.output or "flamegraph.html"
else:
output_str = stacks_json
--
2.39.0.314.g84b9a713c41-goog
Bug#1027953: src:linux: Enable Intel VSEC, SDSI and PMT drivers
Source: linux Severity: wishlist Tags: patch X-Debbugs-Cc: miguel.bernal.ma...@linux.intel.com, jair.de.jesus.gonzalez.plascen...@intel.com Dear Maintainer, Intel is planing to release the next-generation Xeon products [1] and some of the features are not enabled on Debian. Some of those are described below: # Intel Vendor Specific Extended Capabilities Driver CONFIG_INTEL_VSEC=m This adds support for feature drivers exposed using Intel PCIe VSEC and DVSEC. This feature is used by the Intel PMT and Intel SDSi # Intel Platform Monitoring Technology (PMT) CONFIG_INTEL_PMT_CLASS=m CONFIG_INTEL_PMT_TELEMETRY=m CONFIG_INTEL_PMT_CRASHLOG=m Intel PMT is an architecture for enumerating and accessing hardware monitoring capabilities on a device. With customers increasingly asking for hardware telemetry, engineers not only have to figure out how to measure and collect data, but also how to deliver it and make it discoverable. The latter may be through some device specific method requiring device specific tools to collect the data. PMT provides a solution for discovering and reading telemetry from a device through a hardware agnostic framework that allows for updates to systems without requiring patches to the kernel or software tools. The current capabilities defined by PMT are Telemetry, Watcher, and Crashlog. PMT defines several capabilities to support collecting monitoring data from hardware. All are discoverable as separate instances of the PCIE Designated Vendor extended capability (DVSEC) with the Intel vendor code. # Intel Software Defined Silicon Driver (SDSi) CONFIG_INTEL_SDSI=m Intel Software Defined Silicon (SDSi) is a post manufacturing mechanism for activating additional silicon features. Features are enabled through a license activation process. The SDSi driver provides a per socket, sysfs attribute interface for applications to perform 3 main provisioning functions: 1. Provision an Authentication Key Certificate (AKC), a key written to internal NVRAM that is used to authenticate a capability specific activation payload. 2. Provision a Capability Activation Payload (CAP), a token authenticated using the AKC and applied to the CPU configuration to activate a new feature. 3. Read the SDSi State Certificate, containing the CPU configuration state. The operations perform function specific mailbox commands that forward the requests to SDSi hardware to perform authentication of the payloads and enable the silicon configuration (to be made available after power cycling). The SDSi device itself is enumerated as an auxiliary device from the intel_vsec driver and as such has a build dependency on CONFIG_INTEL_VSEC. Link: https://github.com/intel/intel-sdsi A MR was created for this request: MR: https://salsa.debian.org/kernel-team/linux/-/merge_requests/621 Please let me know if it needs any modification. [1] https://www.intel.com/content/www/us/en/newsroom/news/intel-technology-roadmaps-milestones.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Re: linux-image-6.2.0-rc2: cannot connect via ethernet
Processing control commands: > tag -1 upstream Bug #1027891 [src:linux] linux-image-6.2.0-rc2: cannot connect via ethernet Added tag(s) upstream. > severity -1 normal Bug #1027891 [src:linux] linux-image-6.2.0-rc2: cannot connect via ethernet Severity set to 'normal' from 'important' -- 1027891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027891: linux-image-6.2.0-rc2: cannot connect via ethernet
Control: tag -1 upstream Control: severity -1 normal On Wed, 04 Jan 2023 12:04:52 +0100 xevilstar wrote: > Package: linux-image-6.2.0-rc2 > Version: 6.2.0-rc2-1 > > I am testing linux kernel 6.2-rc2 That is great, but you should report any issues you find to the relevant upstream maintainers. signature.asc Description: This is a digitally signed message part.
Processed: notfixed 1020899 in 0.1.3.0-1, tagging 1023443, tagging 985556, tagging 971640 ..., tagging 1027760 ...
Processing commands for cont...@bugs.debian.org:
> notfixed 1020899 0.1.3.0-1
Bug #1020899 {Done: Ilias Tsitsimpis }
[src:haskell-byte-order] haskell-byte-order: BD-Uninstallable on armel, armhf,
i386, mipsel
No longer marked as fixed in versions 0.1.3.0-1.
> tags 1023443 - sid
Bug #1023443 {Done: Vagrant Cascadian } [src:u-boot]
u-boot: Add colibri_imx6 configuration
Removed tag(s) sid.
> tags 985556 + experimental
Bug #985556 {Done: Simon McVittie } [glib2.0]
flatpak/1.2.5-0+deb10u4 FTBFS on IPv6-only buildds
Added tag(s) experimental.
> tags 971640 + experimental
Bug #971640 {Done: Reiner Herrmann } [firejail] firejail:
Build profile command no longer works
Added tag(s) experimental.
> reassign 1027891 src:linux
Bug #1027891 [linux-image-6.2.0-rc2] linux-image-6.2.0-rc2: cannot connect via
ethernet
Warning: Unknown package 'linux-image-6.2.0-rc2'
Bug reassigned from package 'linux-image-6.2.0-rc2' to 'src:linux'.
No longer marked as found in versions 6.2.0-rc2-1.
Ignoring request to alter fixed versions of bug #1027891 to the same values
previously set
> reassign 794821 src:wxwidgets3.2 3.2.1+dfsg-1
Bug #794821 [libwxbase3.2-0] libwxbase3.0-0: segmentation fault (SIGSEGV) with
gnuplot5
Warning: Unknown package 'libwxbase3.2-0'
Bug reassigned from package 'libwxbase3.2-0' to 'src:wxwidgets3.2'.
No longer marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
Ignoring request to alter fixed versions of bug #794821 to the same values
previously set
Bug #794821 [src:wxwidgets3.2] libwxbase3.0-0: segmentation fault (SIGSEGV)
with gnuplot5
Marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
> reassign 1024147 src:wxwidgets3.2 3.2.1+dfsg-1
Bug #1024147 {Done: Scott Talbert } [libwxgtk3.2-0] Please
build with --disable-glcanvasegl
Warning: Unknown package 'libwxgtk3.2-0'
Bug reassigned from package 'libwxgtk3.2-0' to 'src:wxwidgets3.2'.
No longer marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
No longer marked as fixed in versions wxwidgets3.2/3.2.1+dfsg-2.
Bug #1024147 {Done: Scott Talbert } [src:wxwidgets3.2] Please
build with --disable-glcanvasegl
Marked as found in versions wxwidgets3.2/3.2.1+dfsg-1.
> fixed 1024147 3.2.1+dfsg-2
Bug #1024147 {Done: Scott Talbert } [src:wxwidgets3.2] Please
build with --disable-glcanvasegl
Marked as fixed in versions wxwidgets3.2/3.2.1+dfsg-2.
> found 1026781 1.8.0-7
Bug #1026781 [pkgconf] pkgconf: breaks adequate missing-pkgconfig-dependency
check due to behaviour change in: pkg-config --exists --print-errors
There is no source info for the package 'pkgconf' at version '1.8.0-7' with
architecture ''
Unable to make a source version for version '1.8.0-7'
Marked as found in versions 1.8.0-7.
> found 1027733 4.9.0-3
Bug #1027733 [screen] GNU Screen does not support Unicode 14
Marked as found in versions screen/4.9.0-3.
> tags 1027760 + sid bookworm
Bug #1027760 [src:gortr] gortr appears to be unmaintained
Added tag(s) bookworm and sid.
> tags 1027854 + sid bookworm
Bug #1027854 [kismet-plugins] kismet-plugins: uninstallable due to dependency
on libssl1.1
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020899
1023443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023443
1024147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024147
1026781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026781
1027733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027733
1027760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027760
1027854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027854
1027891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027891
794821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794821
971640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971640
985556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Fwd: Job opportunity for Financial Crimes Data Science Sr. Manager
Hello, Job Title: Financial Crimes Data Science Sr. Manager Position Type: Full Time Remote Client : Key Bank Job description *ABOUT THE JOB (JOB BRIEF)* Reporting to the Director of Financial Crimes Modeling & Analytics that reports to the Chief Modeling and Analytics Officer, the Data Science Senior Manager is primarily responsible for leading a quantitative team in support of financial crime modeling and analytics. This role must establish priorities for the team, assign and define the work to the right resources, and understand the strengths and opportunities of the team to ensure the team meets and exceeds expectations. This role is responsible for owning modeling practices, methods, and techniques as well as for influencing data strategy with a focus on leveraging both current and emerging technologies and applications. The Data Science Senior Manager acts as a leader, strategic advisor and credible thought partner to senior / executive level business partners. This position is also responsible for managing the integration of activities within and across teams as well as effectively manage, coach, develop, and guide a team of professionals to anticipate business needs, recommend solutions that are both effective and efficient, and communicate the right message. *ESSENTIAL JOB FUNCTIONS* - Oversee a small quantitative team (2-4 direct reports) in developing models and conducting analytics to address financial crime compliance needs in AML/BSA/OFAC - Research, compile and evaluate large sets of data to assess quality and determine suitability for model building - Develop/maintain internal models and test/configure vendor solutions to ensure conceptually sound design, proper implementation, and acceptable model performance - Employ innovative techniques to drive continuous improvements in model effectiveness and efficiency, e.g. reducing false positives - Proactively coach and develop the team on building technical skills and business knowledge; promote the team and their capabilities to stakeholders - Effectively collaborate with compliance, technology, and risk partners; guides, advises, challenges, and influences to drive organizational impact - Provide strategic consultation and thought leadership to senior / executive level business partners *REQUIRED QUALIFICATIONS* - Master's degree (or its equivalent) in statistics, mathematics, economics, computer science, data sciences, predictive modeling, or other quantitative disciplines and at least 6 years of relevant experience, preferred in AML/BSA, OFAC, or fraud modeling/analytics - Solid expertise with both traditional and Machine Learning (Client)/Artificial Intelligence (AI) modeling practice and solutions - Hands-on work experience with statistical coding in SAS and/or Python - Knowledge of and ability to leverage traditional databases, cloud-based computing, and distribution computing - In-depth understanding of financial crime regulatory requirements, technology, and data analysis best practices - Demonstrated direct management experience - Excellent verbal, written and visual communication skills; ability to define and communicate key risk metrics, dashboards and analytics for senior management and executive reporting; translate technical observations to a non-technical audience - A credible thought leader that can guide, advise, challenge, and influence at all levels of the organization and drive organizational impact - *What are the 3-4 non-negotiable requirements of this position?* 1. Master's or PhD in statistics, mathematics, economics, computer science, data sciences, predictive modeling, or other quantitative disciplines 2. Minimum 4-6 years of related experience 3. Expertise with both traditional and Machine Learning (Client)/Artificial Intelligence (AI) modeling practice and solutions 4. Hands on coding experience in Python and/or SAS (willing to take weaker SAS experience) 5. Cloud experience (we utilize GCP) If you are qualified, available, interested, planning to make a change, or know of a friend who might have the required qualifications and interest, please call me ASAP at (763) 363-5654, even if we have spoken recently about a different position. If you do respond via e-mail please include a daytime phone number so I can reach you. In considering candidates, time is of the essence, so please respond ASAP. Thank you. Sincerely yours Aditya Pratap Singh Talent Acquisition Specialist ___ Inspiron Systems 5145 Jewel ln North, Plymouth MN 55446 Phone : 1-(855) 722-1029 Direct : 763-373-8285 adi...@inspironsys.com : http://www.inspironsys.com
Bug#1027915: systemd requires /run to be mounted with a minimum size of 20MB
Hi Helmut, On 1/4/23 14:26, Helmut Grohne wrote: On Wed, Jan 04, 2023 at 02:08:00PM +0100, Helge Deller wrote: My suggestion: Please check that the /run mountpoint is mounted with at least 20MB, independend of the installed RAM memory in the machine... Your suggestion makes sense in principle. However, it is /usr/share/initramfs-tools/init that performs the mount, so that's what would need changing. Ah, ok. Thanks Helmut! As a workaround for your situation, I suggest adding a kernel parameter initramfs.runsize=20M. Yes, that should work. Would you be able to provide a patch here? I think that if a runsize is given, it should be honoured, so it would probably work like: if test -z "$RUNSIZE"; then if system_has_at_least_200mb_ram; then RUNSIZE=10% else RUNSIZE=20M fi fi Yes, I'll try to send a patch. I just wonder, what's the best way to get the amount of physical memory? Something like this should work which gives size in kB: mem_kb=$(grep MemTotal /proc/meminfo | (read txt mem txt2; echo $mem)) && echo $mem_kb Is there a better way? I think glibc isn't running in initramfs, so "getconf _PHYS_PAGES" will probably not work? Helge
Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional
On Wednesday, 4 January 2023 15:38:32 CET Tim Düsterhus wrote: > Unfortunately the setting `1` allows direct write access to the devices, > whereas the previous and to my understanding the default setting of `-1` > only allows read access, making this a safer option. > > It appears that aacraid's `expose_physicals=-1` option got broken > somewhere between Linux 4.19 and 5.10. https://git.kernel.org/linus/e3cc268fe4a0ad1cbefbc53cee35c80281e609b8 seems relevant, although I do not fully understand it. One thing that stood out for me is the check `expose_physicals > 0` instead of `expose_physicals != 0`. But that commit exists since 2.6.35 ... This very much looks like an upstream kernel issue and therefor it's better to bring it to the attention of those maintainers. Those are: $ scripts/get_maintainer.pl drivers/scsi/aacraid/aachba.c Adaptec OEM Raid Solutions (supporter:AACRAID SCSI RAID DRIVER) "James E.J. Bottomley" (maintainer:SCSI SUBSYSTEM) "Martin K. Petersen" (maintainer:SCSI SUBSYSTEM) linux-s...@vger.kernel.org (open list:AACRAID SCSI RAID DRIVER) linux-ker...@vger.kernel.org (open list) When you do forward your question, please inform this bug report of the URL. HTH signature.asc Description: This is a digitally signed message part.
Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional
Hi Renato On 1/4/23 16:39, Renato Gallo wrote: 5.10 should be EOL by now According to https://www.kernel.org/category/releases.html, Linux 5.10 is supported until 2026. Whether a fix for this bug qualifies as an "important bugfix" acceptable for a LTS kernel I can't tell. In any case, 5.10 is the stock kernel for Debian Bullseye and thus I wanted to report the issue, if only to ensure it is tracked, even if the/a fix doesn't make the cut for Bullseye. Best regards Tim Düsterhus Developer WoltLab GmbH -- WoltLab GmbH Nedlitzer Str. 27B 14469 Potsdam Tel.: +49 331 96784338 duester...@woltlab.com www.woltlab.com Managing director: Marcel Werk AG Potsdam HRB 26795 P
Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional
On Wednesday, 4 January 2023 16:39:33 CET Renato Gallo wrote: > 5.10 should be EOL by now Please refrain from comments like that. It doesn't help at all and is also plain false. signature.asc Description: This is a digitally signed message part.
Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional
5.10 should be EOL by now
On Wed, Jan 4, 2023 at 3:51 PM Tim Düsterhus wrote:
> Package: src:linux
> Version: 5.10.158-2
> Severity: normal
> X-Debbugs-Cc: duester...@woltlab.com
>
> Dear Maintainer,
>
> after upgrading my server from Debian Buster to Debian Bullseye, I
> noticed that the underlying devices attached to the Adaptec 6405E raid
> controller were no longer exposed via the /dev/sgX devices and thus
> reading the SMART values was no longer possible:
>
> $ lsscsi
> [0:0:0:0]diskAdaptec *redacted* V1.0 /dev/sda
> [0:3:0:0]enclosu ADAPTEC Virtual SGPIO -
>
> Booting into the Linux 4.19 kernel from Debian Buster correctly exposed
> the devices with the new userland, indicating a Kernel issue.
>
> I was able to work around the issue by adding the following
> configuration to /etc/modprobe.d/:
>
> options aacraid expose_physicals=1
>
> After setting this configuration and rebooting the server the devices
> are properly visible as they were before:
>
> $ lsscsi
> [0:0:0:0]diskAdaptec *redacted* V1.0 /dev/sda
> [0:1:0:0]diskATA *redacted* /dev/sdb
> [0:1:1:0]diskATA *redacted* /dev/sdc
> [0:3:0:0]enclosu ADAPTEC Virtual SGPIO -
>
> Unfortunately the setting `1` allows direct write access to the devices,
> whereas the previous and to my understanding the default setting of `-1`
> only allows read access, making this a safer option.
>
> It appears that aacraid's `expose_physicals=-1` option got broken
> somewhere between Linux 4.19 and 5.10.
>
> Best regards
>
>
> -- Package-specific info:
> ** Version:
> Linux version 5.10.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-10
> (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2)
> #1 SMP Debian 5.10.158-2 (2022-12-13)
>
> ** Command line:
> BOOT_IMAGE=/vmlinuz-5.10.0-20-amd64 root=ZFS=rpool/ROOT/debian ro boot=zfs
> swapaccount=1 quiet
>
> ** Tainted: POE (12289)
> * proprietary module was loaded
> * externally-built ("out-of-tree") module was loaded
> * unsigned module was loaded
>
> ** Kernel log:
> Unable to read kernel log; any relevant messages should be attached
>
> ** Model information
> sys_vendor: Supermicro
> product_name: X10SLH-F/X10SLM+-F
> product_version: 0123456789
> chassis_vendor: Supermicro
> chassis_version: 0123456789
> bios_vendor: American Megatrends Inc.
> bios_version: 3.2a
> board_vendor: Supermicro
> board_name: X10SLH-F/X10SLM+-F
> board_version: 1.02
>
> ** Loaded modules:
> nft_reject_inet
> nf_reject_ipv4
> nf_reject_ipv6
> nft_reject
> nft_counter
> intel_rapl_msr
> intel_rapl_common
> ipmi_ssif
> nft_ct
> nf_conntrack
> nf_defrag_ipv6
> nf_defrag_ipv4
> x86_pkg_temp_thermal
> intel_powerclamp
> coretemp
> kvm_intel
> kvm
> ext4
> irqbypass
> ghash_clmulni_intel
> crc16
> mbcache
> jbd2
> aesni_intel
> libaes
> crypto_simd
> cryptd
> ast
> glue_helper
> drm_vram_helper
> drm_ttm_helper
> rapl
> ttm
> intel_cstate
> intel_uncore
> drm_kms_helper
> pcspkr
> joydev
> at24
> intel_pch_thermal
> evdev
> mei_me
> cec
> iTCO_wdt
> mei
> intel_pmc_bxt
> sg
> iTCO_vendor_support
> watchdog
> ie31200_edac
> acpi_ipmi
> ipmi_si
> ipmi_devintf
> ipmi_msghandler
> acpi_pad
> button
> nf_tables
> libcrc32c
> crc32c_generic
> nfnetlink
> drm
> fuse
> configfs
> ip_tables
> x_tables
> autofs4
> hid_generic
> usbhid
> hid
> zfs(POE)
> zunicode(POE)
> zzstd(OE)
> zlua(OE)
> zavl(POE)
> icp(POE)
> zcommon(POE)
> znvpair(POE)
> spl(OE)
> ses
> enclosure
> sd_mod
> scsi_transport_sas
> t10_pi
> crc_t10dif
> crct10dif_generic
> ahci
> libahci
> xhci_pci
> libata
> xhci_hcd
> ehci_pci
> crct10dif_pclmul
> crct10dif_common
> ehci_hcd
> aacraid
> crc32_pclmul
> lpc_ich
> igb
> i2c_i801
> usbcore
> i2c_smbus
> scsi_mod
> crc32c_intel
> i2c_algo_bit
> dca
> ptp
> pps_core
> usb_common
> fan
> video
>
> ** PCI devices:
> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor
> DRAM Controller [8086:0c08] (rev 06)
> Subsystem: Super Micro Computer Inc Xeon E3-1200 v3 Processor DRAM
> Controller [15d9:0803]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> SERR- Latency: 0
> IOMMU group: 0
> Capabilities: [e0] Vendor Specific Information: Len=0c
> Kernel driver in use: ie31200_edac
> Kernel modules: ie31200_edac
>
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core
> Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00
> [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR- Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 25
> IOMMU
Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional
Dear Maintainer, Forgot to include in my initial report that I found the workaround using this (German) thread in the Proxmox Support Forum: https://forum.proxmox.com/threads/adaptec-aacraid-expose_physicals-kernelbug.63256/ The thread is fairly light on details, but it appears to indicate the the issue already existed with Linux 5.3. Best regards Tim Düsterhus Developer WoltLab GmbH -- WoltLab GmbH Nedlitzer Str. 27B 14469 Potsdam Tel.: +49 331 96784338 duester...@woltlab.com www.woltlab.com Managing director: Marcel Werk AG Potsdam HRB 26795 P
Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional
Package: src:linux
Version: 5.10.158-2
Severity: normal
X-Debbugs-Cc: duester...@woltlab.com
Dear Maintainer,
after upgrading my server from Debian Buster to Debian Bullseye, I
noticed that the underlying devices attached to the Adaptec 6405E raid
controller were no longer exposed via the /dev/sgX devices and thus
reading the SMART values was no longer possible:
$ lsscsi
[0:0:0:0]diskAdaptec *redacted* V1.0 /dev/sda
[0:3:0:0]enclosu ADAPTEC Virtual SGPIO -
Booting into the Linux 4.19 kernel from Debian Buster correctly exposed
the devices with the new userland, indicating a Kernel issue.
I was able to work around the issue by adding the following
configuration to /etc/modprobe.d/:
options aacraid expose_physicals=1
After setting this configuration and rebooting the server the devices
are properly visible as they were before:
$ lsscsi
[0:0:0:0]diskAdaptec *redacted* V1.0 /dev/sda
[0:1:0:0]diskATA *redacted* /dev/sdb
[0:1:1:0]diskATA *redacted* /dev/sdc
[0:3:0:0]enclosu ADAPTEC Virtual SGPIO -
Unfortunately the setting `1` allows direct write access to the devices,
whereas the previous and to my understanding the default setting of `-1`
only allows read access, making this a safer option.
It appears that aacraid's `expose_physicals=-1` option got broken
somewhere between Linux 4.19 and 5.10.
Best regards
-- Package-specific info:
** Version:
Linux version 5.10.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP
Debian 5.10.158-2 (2022-12-13)
** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-20-amd64 root=ZFS=rpool/ROOT/debian ro boot=zfs
swapaccount=1 quiet
** Tainted: POE (12289)
* proprietary module was loaded
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: Supermicro
product_name: X10SLH-F/X10SLM+-F
product_version: 0123456789
chassis_vendor: Supermicro
chassis_version: 0123456789
bios_vendor: American Megatrends Inc.
bios_version: 3.2a
board_vendor: Supermicro
board_name: X10SLH-F/X10SLM+-F
board_version: 1.02
** Loaded modules:
nft_reject_inet
nf_reject_ipv4
nf_reject_ipv6
nft_reject
nft_counter
intel_rapl_msr
intel_rapl_common
ipmi_ssif
nft_ct
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
ext4
irqbypass
ghash_clmulni_intel
crc16
mbcache
jbd2
aesni_intel
libaes
crypto_simd
cryptd
ast
glue_helper
drm_vram_helper
drm_ttm_helper
rapl
ttm
intel_cstate
intel_uncore
drm_kms_helper
pcspkr
joydev
at24
intel_pch_thermal
evdev
mei_me
cec
iTCO_wdt
mei
intel_pmc_bxt
sg
iTCO_vendor_support
watchdog
ie31200_edac
acpi_ipmi
ipmi_si
ipmi_devintf
ipmi_msghandler
acpi_pad
button
nf_tables
libcrc32c
crc32c_generic
nfnetlink
drm
fuse
configfs
ip_tables
x_tables
autofs4
hid_generic
usbhid
hid
zfs(POE)
zunicode(POE)
zzstd(OE)
zlua(OE)
zavl(POE)
icp(POE)
zcommon(POE)
znvpair(POE)
spl(OE)
ses
enclosure
sd_mod
scsi_transport_sas
t10_pi
crc_t10dif
crct10dif_generic
ahci
libahci
xhci_pci
libata
xhci_hcd
ehci_pci
crct10dif_pclmul
crct10dif_common
ehci_hcd
aacraid
crc32_pclmul
lpc_ich
igb
i2c_i801
usbcore
i2c_smbus
scsi_mod
crc32c_intel
i2c_algo_bit
dca
ptp
pps_core
usb_common
fan
video
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor DRAM
Controller [8086:0c08] (rev 06)
Subsystem: Super Micro Computer Inc Xeon E3-1200 v3 Processor DRAM
Controller [15d9:0803]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: ie31200_edac
Kernel modules: ie31200_edac
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Super Micro Computer Inc Xeon E3-1200
v3/4th Gen Core Processor PCI Express x16 Controller [15d9:0803]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218 Data:
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256
Processed: Re: Bug#1027915: systemd requires /run to be mounted with a minimum size of 20MB
Processing control commands: > reassign -1 initramfs-tools-core Bug #1027915 [systemd] systemd requires /run to be mounted with a minimum size of 20MB Bug reassigned from package 'systemd' to 'initramfs-tools-core'. No longer marked as found in versions systemd/252.4-1. Ignoring request to alter fixed versions of bug #1027915 to the same values previously set -- 1027915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022126: mpt3sas broken with xen dom0
Hi Taavi, On Mon, Jan 02, 2023 at 03:54:16PM +0200, Taavi Ansper wrote: > Are there any news regarding when the fix would be implemented for bullseye? See https://lore.kernel.org/linux-scsi/181536c494aa39ca78b190396a97072448739411.ca...@suse.com/ for an upstream status. Once the patches land in mainline, they can be picked up for the stable series. Then it will be included as well for bullseye as we follow the stable series and try to rebase at least on each point release. So I would expect we can see the fix in the next update. Regards, Salvatore
Bug#1027861: linux: consider enabling CONFIG_IPV6_RPL_LWTUNNEL
Source: linux Severity: wishlist Tags: ipv6 X-Debbugs-Cc: jerome.pouil...@gmail.com Hi folks, "RPL Source Routing Header" (CONFIG_IPV6_RPL_LWTUNNEL) is currently disabled. It seems it is only an oversight since this option is not explicitly mentioned in debian kernel config file (and features like "Segment Routing Header encapsulation" are enabled while they are very close of "RPL Source Routing Header"). We consider to use RPL Source Routing Header in our implementation of border router for Low-Power and Lossy Networks[1]. So, I would be very glad to see this option enabled on Debian. FYI, I have build a custom kernel with this option enabled without any pain. I could send a patch if you need. Thank you, [1]: https://github.com/SiliconLabs/wisun-br-linux -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.10-custom (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
