Searched full:problems (Results 1 – 25 of 1284) sorted by relevance
12345678910>>...52
| /linux-6.12.1/arch/x86/kernel/ |
| D | reboot.c | 184 { /* Handle problems with rebooting on Apple MacBook5 */
192 { /* Handle problems with rebooting on Apple MacBook6,1 */
200 { /* Handle problems with rebooting on Apple MacBookPro5 */
208 { /* Handle problems with rebooting on Apple Macmini3,1 */
216 { /* Handle problems with rebooting on the iMac9,1. */
224 { /* Handle problems with rebooting on the iMac10,1. */
234 { /* Handle problems with rebooting on ASRock Q1900DC-ITX */
244 { /* Handle problems with rebooting on ASUS P4S800 */
252 { /* Handle problems with rebooting on ASUS EeeBook X205TA */
260 { /* Handle problems with rebooting on ASUS EeeBook X205TAW */
[all …]
|
| /linux-6.12.1/Documentation/networking/device_drivers/fddi/ |
| D | skfp.rst | 40 Chapter 4: Describes common problems and solutions.
88 If you run into problems during installation, check those items:
180 Problems fixed:
185 Problems fixed:
202 Problems fixed:
211 Problems fixed:
216 Problems fixed:
227 Problems fixed:
237 Problems fixed:
|
| /linux-6.12.1/Documentation/usb/ |
| D | usb-serial.rst | 53 For any questions or problems with this driver, please contact
98 For any questions or problems with this driver, please contact Greg
150 For any questions or problems with the driver, please contact Ganesh
182 For any questions or problems with this driver, please contact Brian
207 For any questions or problems with this driver, please contact Hugh
221 For any questions or problems with this driver, please contact Bill Ryder.
284 If you have any questions, problems, patches, feature requests, etc. you can
289 (your problems/patches can alternately be submitted to usb-devel)
310 (alborchers@steinerpoint.com) for questions or problems with this
352 For any questions or problems with this driver, please contact William
[all …]
|
| /linux-6.12.1/Documentation/process/ |
| D | 3.Early-stage.rst | 28 the linux-kernel mailing list, where it immediately ran into problems.
89 problems like this before writing the code.
97 doors invariably has problems which are only revealed when the code is
98 released into the community. Sometimes these problems are severe,
112 deadlocks. The late revelation of these problems - and refusal to
181 posted by others. Beyond that, high-level designs often hide problems
187 Unfortunately, you also cannot assume that there are no problems with your
214 problems later. For companies without that sort of in-house expertise, the
222 This kind of review is often enough to avoid serious problems later on
|
| D | 1.Intro.rst | 41 avoid problems at this important stage. Developers are cautioned against
137 mainline solves a large number of distribution and support problems.
161 improved. Often review finds severe bugs and security problems. This is
204 problems, to the point that most kernel developers will not even try. So
218 problems.
258 its owner, or which risks creating copyright-related problems for the
|
| /linux-6.12.1/drivers/net/wireless/ath/ath12k/ |
| D | Kconfig | 25 If unsure, say Y to make it easier to debug problems. But if
34 If unsure, say Y to make it easier to debug problems. But if
43 If unsure, say Y to make it easier to debug problems. But if
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | locks.rst | 24 This should not cause problems for anybody, since everybody using a
31 1.2.1 Typical Problems - Sendmail
35 for example. This gave rise to some other subtle problems if sendmail was
54 fcntl(), with all the problems that implies.
|
| /linux-6.12.1/fs/xfs/libxfs/ |
| D | xfs_health.h | 21 * problems remain at unmount time, we can also request manual intervention by
35 * Evidence of health problems can be sorted into three basic categories:
41 * not themselves problems. These can be forgotten when the primary
42 * health problems are addressed.
100 /* Primary evidence of health problems in a given group. */
137 /* Secondary state related to (but not primary evidence of) health problems. */
143 /* Evidence of health problems elsewhere. */
|
| /linux-6.12.1/Documentation/translations/zh_CN/maintainer/ |
| D | pull-requests.rst | 94 this in a way to successfully neutralize the problems.
96 when needed, so problems should not occur.
99 linux-next releases, and the original problems that it found have
|
| /linux-6.12.1/fs/xfs/ |
| D | xfs_sysctl.h | 26 xfs_sysctl_val_t error_level; /* Degree of reporting for problems */
44 * How much error reporting will be done when internal problems are
45 * encountered. These problems normally return an EFSCORRUPTED to their
|
| /linux-6.12.1/Documentation/virt/kvm/x86/ |
| D | timekeeping.rst | 15 4) Virtualization Problems
27 present some of the problems which arise and solutions available, giving
329 time. In practice, due to a number of problems, it is the most complicated
481 4. Virtualization Problems
491 at any time. This causes problems as the passage of real time, the injection
498 cause similar problems to virtualization makes it a good justification for
499 solving many of these problems on bare metal.
504 One of the most immediate problems that occurs with legacy operating systems
536 many problems unique to its nature as a local, potentially unstable and
582 Migration of a virtual machine raises problems for timekeeping in two ways.
[all …]
|
| /linux-6.12.1/drivers/net/wireless/ath/ath11k/ |
| D | Kconfig | 37 If unsure, say Y to make it easier to debug problems.
45 If unsure, say Y to make it easier to debug problems.
|
| /linux-6.12.1/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 12 those tools incorrectly, but avoiding problems is not actually all that
18 merges would be nearly impossible. Some problems encountered by
153 also obscure problems with the development process in your tree; they can
183 pull request is a good idea. It may alert you to problems that you somehow
197 tree fails to be pulled upstream, whatever problems it had will block the
|
| D | pull-requests.rst | 108 this in a way to successfully neutralize the problems.
110 when needed, so problems should not occur.
113 linux-next releases, and the original problems that it found have
149 firewalls will have problems with https git pulls).
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | vidioc-log-status.rst | 32 debug problems. When this ioctl is called the driver will output the
34 dealing with problems like no sound, no video and incorrectly tuned
|
| /linux-6.12.1/drivers/net/wireless/ath/ath6kl/ |
| D | Kconfig | 43 If unsure, say Y to make it easier to debug problems.
55 If unsure, say Y to make it easier to debug problems.
|
| /linux-6.12.1/drivers/net/wireless/ath/wil6210/ |
| D | Kconfig | 44 If unsure, say Y to make it easier to debug problems.
56 If unsure, say Y to make it easier to debug problems.
|
| /linux-6.12.1/arch/arm/mach-pxa/ |
| D | sleep.S | 66 @ Intel PXA270 Specification Update notes problems sleeping
103 @ Intel PXA255 Specification Update notes problems
159 @ Intel PXA270 Specification Update notes problems performing
|
| /linux-6.12.1/drivers/net/wireless/ath/ath10k/ |
| D | Kconfig | 61 If unsure, say Y to make it easier to debug problems.
69 If unsure, say Y to make it easier to debug problems.
|
| /linux-6.12.1/Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 5 This document contains the information about the problems user
8 Here's the summary. This matrix shows the known problems, that
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | README.rst | 56 contains information about the problems, which may result by upgrading
123 you can just update packages when obvious problems arise during
153 odd problems will turn up if the configuration files are not set up
243 under some circumstances lead to problems: probing for a
255 break bad code to find kernel problems (kmalloc()). Thus you
354 If you have problems that seem to be due to kernel bugs, please follow the
|
| /linux-6.12.1/tools/testing/selftests/proc/ |
| D | proc-2-is-kthread.c | 31 * problems with mandatory module signing, in main()
32 * problems with lockdown mode, in main()
|
| /linux-6.12.1/drivers/net/wireless/realtek/rtw89/ |
| D | Kconfig | 120 If unsure, say Y to simplify debug problems
129 If unsure, say Y to simplify debug problems
|
| /linux-6.12.1/drivers/pcmcia/ |
| D | o2micro.h | 128 * older bridges have problems with both read prefetch and write in o2micro_override()
156 …"O2: enabling read prefetch/write burst. If you experience problems or performance issues, use the… in o2micro_override()
163 …"O2: disabling read prefetch/write burst. If you experience problems or performance issues, use th… in o2micro_override()
|
| /linux-6.12.1/arch/m68k/q40/ |
| D | README | 45 problems. For cards using 16bit io/mem more care is required, like
66 Most problems seem to be caused by fawlty or badly configured io-cards or
130 problems, email me ideally this:
|
12345678910>>...52