issues (full) in projects: linux-6.15 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:issues (Results 1 – 25 of 1545) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...62

/linux-6.15/Documentation/process/
D	embargoed-hardware-issues.rst	3 Embargoed hardware issues 9 Hardware issues which result in security problems are a different category 13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated 17 issues, software mitigations can depend on microcode or firmware updates, 29 issues. Reports of pure software security bugs in the Linux kernel are not 46 While hardware security issues are often handled by the affected silicon 79 is aware of the sensitive nature of such issues and offers a Memorandum of 87 keep hardware security issues under embargo for coordination between 91 issues in the past and has the necessary mechanisms in place to allow 95 initial contact, which oversees the process of handling such issues under [all …]
D	cve.rst	`17 potential Linux kernel security issues. This assignment is independent 31 potentially security issues are identified by the developers responsible 47 security issues should be sent to this alias, it is ONLY for assignment 53 No CVEs will be automatically assigned for unfixed security issues in 118 assigned to all fixes for all issues, but sometimes we will fail to`
D	stable-api-nonsense.rst	`45 First off, I'm not going to address any legal issues about closed 50 the technical issues here (not to make light of the legal issues, they 84 Now a number of these issues can be addressed by simply compiling your 120 issues: 146 Security issues are also very important for Linux. When a`
D	maintainer-soc-clean-dts.rst	`19 results of issues in an included DTSI file, are considered existing, not new 25 issues shall be fixed in reasonable time (e.g. within one release) or the`
/linux-6.15/Documentation/networking/diagnostic/
D	twisted_pair_layer1_diagnostics.rst	12 Ethernet issues, this guide provides a practical, step-by-step 15 or mysterious network issues, jump right into the step-by-step guide and 33 The guide is designed to help users diagnose physical layer (Layer 1) issues on 38 partner and will focus on diagnosing issues locally. 44 there are issues with data transmission, refer to the OSI Layer 2 48 indicate potential issues at the hardware or physical layer. 88 detected, indicating potential Layer 1 issues like a cable fault, 106 troubleshoot potential physical layer issues. 122 checking Layer 2 configurations (such as VLANs or MAC address issues), 137 duplex issues, and link instability. [all …]
/linux-6.15/Documentation/admin-guide/
D	reporting-issues.rst	4 Reporting issues 40 If you are facing multiple issues with the Linux kernel at once, report each 51 Step-by-step guide how to report issues to the kernel maintainers 54 The above TL;DR outlines roughly how to report issues to the Linux kernel 56 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For 72 will often be needed anyway to hunt down and fix issues. 80 issue, or a really severe problem: those are 'issues of high priority' that 96 issues at once, create separate notes for each of them and make sure they 107 time this won't be bugzilla.kernel.org, as issues typically need to be sent 129 up there, scroll down to the instructions for issues only happening with [all …]
D	reporting-regressions.rst	24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst, 57 behavior with a newer kernel version; such issues can be caused by changes in 77 Documentation/admin-guide/reporting-issues.rst, it already describes the 146 a lot of issues only occur in a particular environment outside the developer's 158 Documentation/admin-guide/reporting-issues.rst and described in more detail by 184 issues, or other problematic aspects already fixed in later versions 254 In extremely rare situations security issues can't be fixed without causing 258 issues without causing regressions. 389 What kind of issues are supposed to be tracked by regzbot? 393 regular issues. But it's okay for the Linux kernel's regression tracker if you [all …]
/linux-6.15/Documentation/gpu/amdgpu/display/
D	display-contributing.rst	`10 This page summarizes some of the issues you can help with; keep in mind that 16 Gitlab issues 19 Users can report issues associated with AMD GPUs at: 24 filter issues. If you can reproduce any problem, you could help by adding more 50 issues on the display side. 54 Fix compilation issues when using um architecture 59 from the test perspective. We currently have some compilation issues in this`
D	dc-debug.rst	7 procedures to help you identify if some issues are related to display code. 9 Narrow down display issues 13 reporting issues as a display when another component causes the problem. This 22 looking for the issues associated with amdgpu, remember that each component of 139 the display should not be ignored since this could be a DPM issues. From the 169 issues. 173 indication of Sub-Viewport issues; after the users identified the target DCN, 257 When reporting issues, it is important to have the firmware information since
/linux-6.15/tools/perf/pmu-events/arch/arm64/arm/neoverse-v3/
D	metrics.json	15 …tage of total cycles stalled in the backend due to memory access latency issues caused by level 1 … 22 …tage of total cycles stalled in the backend due to memory access latency issues caused by level 2 … 29 …ckend core resource constraints not related to instruction fetch latency issues caused by memory a… 43 …ue to backend core resource constraints related to memory access latency issues caused by memory a… 50 … percentage of total cycles stalled in the backend due to memory latency issues caused by data cac… 64 …tage of total cycles stalled in the backend due to memory access latency issues caused by data TLB… 184 …age of total cycles stalled in the frontend due to memory access latency issues caused by level 1 … 191 …age of total cycles stalled in the frontend due to memory access latency issues caused by level 2 … 198 …ntend core resource constraints not related to instruction fetch latency issues caused by memory a… 219 …ntend core resource constraints related to the instruction fetch latency issues caused by memory a… [all …]
/linux-6.15/tools/perf/pmu-events/arch/arm64/arm/neoverse-n3/
D	metrics.json	15 …tage of total cycles stalled in the backend due to memory access latency issues caused by level 1 … 22 …tage of total cycles stalled in the backend due to memory access latency issues caused by level 2 … 29 …ckend core resource constraints not related to instruction fetch latency issues caused by memory a… 43 …ue to backend core resource constraints related to memory access latency issues caused by memory a… 50 … percentage of total cycles stalled in the backend due to memory latency issues caused by data cac… 64 …tage of total cycles stalled in the backend due to memory access latency issues caused by data TLB… 184 …age of total cycles stalled in the frontend due to memory access latency issues caused by level 1 … 191 …age of total cycles stalled in the frontend due to memory access latency issues caused by level 2 … 198 …ntend core resource constraints not related to instruction fetch latency issues caused by memory a… 219 …ntend core resource constraints related to the instruction fetch latency issues caused by memory a… [all …]
/linux-6.15/drivers/media/pci/tw5864/
D	tw5864-core.c	33 * BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY 43 * There is a workaround for both issues: avoid P-frames by setting GOP size 48 * These issues are not decoding errors; all produced H.264 streams are decoded 50 * analog-to-digital conversion issues nor internal memory errors; we conclude 51 * it's internal H.264 encoder issues. 53 * worked properly at all in our development environment. So these issues may 299 dev_info(&pci_dev->dev, "Note: there are known video quality issues. For details\n"); in tw5864_initdev()
/linux-6.15/tools/testing/selftests/rseq/
D	compiler.h	`21 * https://github.com/llvm/llvm-project/issues/52735 23 * Work around these issues by adding a volatile inline asm with 26 * issues are found in the future.`
/linux-6.15/drivers/gpu/drm/xe/
D	Kconfig.debug	`27 performance but will catch some internal issues. 93 Choose this option when debugging guc issues. 94 Buffer should be large enough for complex issues.`
/linux-6.15/Documentation/process/debugging/
D	driver_development_debugging_guide.rst	`13 debugging issues and behavior. 47 - Can cause delays in the execution of the code (which can cause issues to be 60 delays into the code execution, causing issues to be flaky or hidden.) 62 If the processing of this still causes timing issues then you can try 182 behavior. It is designed to find a variety of issues, including signed integer 193 and other locking-related issues in the kernel.`
/linux-6.15/drivers/gpu/drm/i915/
D	Kconfig.debug	`67 performance but will catch some internal issues. 160 performance but will catch some internal issues. 172 performance but will catch some internal issues. 185 performance but will help resolve GuC related issues.`
/linux-6.15/Documentation/gpu/
D	automated_testing.rst	`85 amdgpu driver: https://gitlab.freedesktop.org/drm/amd/-/issues 86 i915 driver: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues 87 msm driver: https://gitlab.freedesktop.org/drm/msm/-/issues 88 xe driver: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues 132 issues, for example), you can remove tests from the flakes and/or skips lists,`
/linux-6.15/Documentation/usb/
D	ehci.rst	`51 used on PPC hardware so big/little endianness issues should be gone. 53 systems with interesting DMA mapping issues. 84 There are some issues with power management; suspend/resume doesn't 156 but aggregate throughput is also affected by issues like delays between 224 Interrupt and ISO transfer performance issues. Those periodic`
/linux-6.15/drivers/gpu/drm/amd/display/
D	Kconfig	`14 # !CC_IS_CLANG: https://github.com/ClangBuiltLinux/linux/issues/1752 26 https://github.com/llvm/llvm-project/issues/41896.`
/linux-6.15/drivers/gpu/drm/ci/xfails/
D	msm-sc7180-trogdor-kingoftown-flakes.txt	`23 # Bug Report: https://gitlab.freedesktop.org/drm/msm/-/issues/68 30 # Bug Report: https://gitlab.freedesktop.org/drm/msm/-/issues/69`
D	amdgpu-stoney-flakes.txt	`23 # Bug Report: https://gitlab.freedesktop.org/drm/amd/-/issues/3835 30 # Bug Report: https://gitlab.freedesktop.org/drm/amd/-/issues/3836`
/linux-6.15/drivers/gpu/drm/panfrost/
D	panfrost_gpu.c	`181 u64 issues; member 184 u64 issues; member 193 .issues = hw_issues_##_name, \ 200 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \ 315 hw_issues \|= model->issues; in panfrost_gpu_init_features() 325 hw_issues \|= model->revs[best].issues; in panfrost_gpu_init_features() 335 dev_info(pfdev->dev, "features: %64pb, issues: %64pb", in panfrost_gpu_init_features()`
/linux-6.15/Documentation/kbuild/
D	llvm.rst	141 will build or work without any issues. Below is a general summary of 145 it or there are known issues. Using the latest stable version of LLVM or 198 - `Issue Tracker <https://github.com/ClangBuiltLinux/linux/issues>`_ 202 - `Beginner Bugs <https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%2…
/linux-6.15/Documentation/dev-tools/
D	testing-overview.rst	`89 detect classes of issues when they occur in a running kernel. These typically 91 concurrency issues such as data races, or other undefined behaviour like 103 * KFENCE is a low-overhead detector of memory issues, which is much faster than 137 etc. Smatch also has tests against more serious issues such as integer`
/linux-6.15/tools/perf/tests/shell/
D	stat_all_metrics.sh	`59 echo "FP issues" 68 echo "Optane memory issues"`

12 3 4 5 6 7 8 9 10 >>...62