| /linux-4.4.14/arch/powerpc/platforms/cell/spufs/ |
| D | hw_ops.c | 40 struct spu_problem __iomem *prob = spu->problem; in spu_hw_mbox_read()
56 return in_be32(&ctx->spu->problem->mb_stat_R); in spu_hw_mbox_stat_read()
67 stat = in_be32(&spu->problem->mb_stat_R); in spu_hw_mbox_stat_poll()
99 struct spu_problem __iomem *prob = spu->problem; in spu_hw_ibox_read()
120 struct spu_problem __iomem *prob = spu->problem; in spu_hw_wbox_write()
140 out_be32(&ctx->spu->problem->signal_notify1, data); in spu_hw_signal1_write()
145 out_be32(&ctx->spu->problem->signal_notify2, data); in spu_hw_signal2_write()
192 return in_be32(&ctx->spu->problem->spu_npc_RW); in spu_hw_npc_read()
197 out_be32(&ctx->spu->problem->spu_npc_RW, val); in spu_hw_npc_write()
202 return in_be32(&ctx->spu->problem->spu_status_R); in spu_hw_status_read()
[all …]
|
| D | switch.c | 97 struct spu_problem __iomem *prob = spu->problem; in check_spu_isolate()
217 struct spu_problem __iomem *prob = spu->problem; in save_spu_runcntl()
236 struct spu_problem __iomem *prob = spu->problem; in save_spu_status()
310 struct spu_problem __iomem *prob = spu->problem; in do_mfc_mssync()
382 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querymask()
393 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querytype()
404 struct spu_problem __iomem *prob = spu->problem; in save_ppu_tagstatus()
517 struct spu_problem __iomem *prob = spu->problem; in save_spu_npc()
601 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb_stat()
611 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb()
[all …]
|
| /linux-4.4.14/Documentation/zh_CN/ |
| D | SecurityBugs | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | stable_kernel_rules.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | IRQ.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | stable_api_nonsense.txt | 4 original document maintainer directly. However, if you have problem
7 is problem with translation.
|
| D | basic_profiling.txt | 4 However, if you have problem communicating in English you can also ask the
6 translation is outdated or there is problem with translation.
|
| D | io_ordering.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | sparse.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | volatile-considered-harmful.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | SubmittingDrivers | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | email-clients.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | oops-tracing.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | SubmittingPatches | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | gpio.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | magic-number.txt | 4 However, if you have problem communicating in English you can also ask the
6 translation is outdated or there is problem with translation.
|
| D | HOWTO | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | CodingStyle | 4 However, if you have problem communicating in English you can also ask the
6 translation is outdated or there is problem with translation.
|
| /linux-4.4.14/Documentation/zh_CN/arm64/ |
| D | tagged-pointers.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | legacy_instructions.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | memory.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | booting.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /linux-4.4.14/Documentation/networking/ |
| D | vortex.txt | 198 decision. If you think that Tx checksums are causing a problem, you
217 "Variables to work-around the Compaq PCI BIOS32 problem"....
320 On a side note, adding HAS_NWAY seems to share a problem with the
335 If autonegotiation is a problem, you may need to specify "speed
345 Maintainers find that accurate and complete problem reports are
348 the bottom of the problem.
350 If you believe you have a driver problem here are some of the
353 - Is it really a driver problem?
359 - OK, it's a driver problem.
366 problem. If it's a kernel crash then you should refer to the
[all …]
|
| D | skfp.txt | 90 is not there, then you may have a hardware problem or PCI
95 Some COMPAQ machines have a problem with PCI under
104 forwarding or there is a problem with the routing table
108 If your problem is not listed here, please contact our
217 document for details about this problem.
|
| D | 6pack.txt | 146 or more subsequent packets. I have been told that this is due to a problem
147 with the serial driver of 2.0.3x kernels. I don't know yet if the problem
153 running, even if that IP connection is already closed. The problem does not
155 this is a problem of the 6pack driver or something else in the kernel.
|
| D | vxlan.txt | 5 problem of limited VLAN IDs (4096) in IEEE 802.1q. With VXLAN the
|
| D | cxgb.txt | 204 is provided as a workaround to the problem. In some cases, this problem is
277 AMD's provides three workarounds for this problem, however, Chelsio
294 and duplicate the problem before submitting a bug or asking for support.
|
| D | z8530drv.txt | 334 and start your NOS and attach /dev/ptys0 there. The problem is that
336 (disastrous on a DAMA controlled channel). To solve this problem,
607 A very common problem is that the PTT locks until the maxkeyup timer
637 If you cannot solve a problem, send me
639 - a description of the problem,
|
| D | de4x5.txt | 126 share the same interrupt as the DECchip based cards. The problem occurs
138 Finally, I think I have really fixed the module loading problem with
|
| D | 3c509.txt | 141 have an interrupt line problem. Check /proc/interrupts to verify that the
147 you have a routing problem.
|
| D | tcp.txt | 48 Good TCP congestion control is a complex problem because the algorithm
|
| D | generic-hdlc.txt | 122 If you have a problem with N2, C101 or PLX200SYN card, you can issue the
|
| D | README.sb1000 | 120 problem lies.
152 Solution -- There's a problem with later versions of isapnp using the "(CHECK)"
|
| D | decnet.txt | 176 - Which client caused the problem ?
179 - How can the problem be reproduced ?
|
| D | spider_net.txt | 115 the hardware can fill them, there is no problem. If, for some reason,
140 problem. A typical print when the network is hung shows the following:
|
| D | rds.txt | 136 This isn't a trivial problem, but applications can deal with
200 to ack messages that have been received. The problem is that IB
|
| /linux-4.4.14/arch/powerpc/platforms/ps3/ |
| D | spu.c | 136 unsigned long problem, unsigned long ls, unsigned long shadow, in _dump_areas() argument
141 pr_debug("%s:%d: problem: %lxh\n", func, line, problem); in _dump_areas()
190 iounmap(spu->problem); in spu_unmap()
227 spu->problem = ioremap(spu->problem_phys, in setup_areas()
230 if (!spu->problem) { in setup_areas()
247 (unsigned long)spu->problem, (unsigned long)spu->local_store, in setup_areas()
|
| /linux-4.4.14/arch/powerpc/platforms/cell/ |
| D | spu_manage.c | 75 iounmap(spu->problem); in spu_unmap()
155 spu->problem = spu_map_prop_old(spu, node, "problem"); in spu_map_device_old()
156 if (!spu->problem) in spu_map_device_old()
247 ret = spu_map_resource(spu, 1, (void __iomem**)&spu->problem, in spu_map_device()
272 spu->problem_phys, spu->problem); in spu_map_device()
354 spu->local_store, spu->problem, spu->priv1, in of_create_spu()
|
| D | spu_base.c | 707 in_be32(&spu->problem->spu_runcntl_RW); in crash_kexec_stop_spus()
709 in_be32(&spu->problem->spu_status_R); in crash_kexec_stop_spus()
711 in_be32(&spu->problem->spu_npc_RW); in crash_kexec_stop_spus()
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 29 # But that is a problem, because this means that in order to determine
37 # obvious that an easy to solution to this problem should just be the removal
43 # CORE also consist of a solution to this recursive problem.
|
| D | Kconfig.recursion-issue-02 | 43 # problem consisted on matching semantics with newly introduced features.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 3.Early-stage | 13 clear description of the problem to be solved. In some cases, this step is
15 example. In others, though, it is tempting to confuse the real problem
27 immediate problem. To the wider kernel community, though, it was seen as a
49 the right solution to the problem than they were with a specific module.
50 The moral of the story is to focus on the problem - not a specific solution
57 - What, exactly, is the problem which needs to be solved?
59 - Who are the users affected by this problem? Which use cases should the
62 - How does the kernel fall short in addressing that problem now?
73 - It may well be that the problem is addressed by the kernel in ways which
87 problem; they may have ideas for a better solution, and may be willing
[all …]
|
| D | 6.Followthrough | 61 suggested change, describe it and justify your solution to the problem. If
65 be easy to become blinded by your own solution to a problem to the point
67 you're not even solving the right problem.
199 developer posts a different solution to your problem. At that point,
203 really only one way to respond: be pleased that your problem got solved and
|
| D | 5.Posting | 17 completely "ready." For simple patches, that is not a problem. If the
116 finger the last patch as the one which caused the problem, even though
159 hunters wondering whether the patch is responsible for a problem they are
169 and the title when citing commits). If a problem is associated with
171 searching for a solution to the same problem. If the change is meant to
216 - Reported-by: names a user who reported a problem which is fixed by this
|
| D | 4.Coding | 151 corporate doors. But one large problem in particular was that it was not
212 automated way. Any problem caught by the computer is a problem which will
262 occasion, deadlock. This kind of problem can be painful (for both
320 changelog. Log entries should describe the problem being solved, the form
|
| /linux-4.4.14/Documentation/power/ |
| D | basic-pm-debugging.txt | 104 that there is a problem with the tasks freezer subsystem that should be
119 make sure to report the problem with the driver.
127 If the "platform" test fails, there is a problem with the handling of the
133 work (of course, this only may be an issue on SMP systems) and the problem
140 the problem is most probably hardware-related and serious, so it should be
145 indicates a serious problem that very well may be related to the hardware, but
153 probably is a problem with a driver statically compiled into the kernel and you
155 individually. Otherwise, there is a problem with a modular driver and you can
165 before hibernation, and please report the problem with it(them).
172 techniques to find the problem. First, if there is a serial port in your box,
|
| D | s2ram.txt | 10 video.txt. Perhaps problem is as simple as broken module, and
39 - if it doesn't come back up (which is usually the problem), reboot by
|
| D | swsusp-and-swap-files.txt | 9 holds it. From the swsusp's point of view (1) is not a problem, because it is
|
| D | video.txt | 13 This is not problem for swsusp, because during swsusp resume, BIOS is
15 problem for S1 standby, because hardware should retain its state over
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | mwave | 9 OK, first thing - the IRQ problem IS a problem, whether the test is bypassed or
10 not. It is NOT a Linux problem, but an MWAVE problem that is fixed with the
169 problem with the SB1.5 (CD sound) or SBPRO (Mixers) settings. No one knows why
|
| D | VIBRA16 | 18 So, the big problem still remains, because the sb module wants a
|
| D | Opti | 173 companded samples works well. Apparently this problem is not common
175 have this problem.
|
| D | Introduction | 278 is a PnP problem.... If anyone has any luck doing this, please
279 send me an E-MAIL. PCI sound cards should not have this problem.a
331 (my Toshiba T8000 PII/366 sometimes has this problem).
|
| D | README.modules | 84 problem is to allocate the DMA buffers during module load and deallocate
|
| /linux-4.4.14/Documentation/zh_CN/arm/ |
| D | Booting | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | kernel_user_helpers.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | NOTES | 1 There seems to be a problem with exp(double) and our emulator. I haven't
22 This code will cause this problem:
|
| D | README | 41 attempting to isolate the problem. Please report them, but don't
42 expect quick action. Bugs still exist. The problem remains in isolating
44 problem are a godsend.
|
| /linux-4.4.14/fs/exofs/ |
| D | BUGS | 1 - Out-of-space may cause a severe problem if the object (and directory entry)
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 7 The problem. Network devices show up in sysfs and with the network
11 To avoid that problem and allow existing applications in network
|
| D | ufs.txt | 12 The problem are differences among implementations. Features of
|
| D | inotify.txt | 16 This solves the primary problem with dnotify: keeping the file open pins
70 A: The poor user-space interface is the second biggest problem with dnotify.
|
| D | hpfs.txt | 154 You encounter this problem only if you have many directories so that
234 Fixed a possible problem with disks > 64G (but I don't have one, so I can't
257 Fixed possible problem on large disks
266 1.99 Corrected a possible problem when there's not enough space while deleting
272 2.01 Fixed problem with directory listing over NFS
|
| D | autofs4-mount-control.txt | 5 The problem
8 There is a problem with active restarts in autofs (that is to say
28 The actual problem with autofs is that it can't reconnect to existing
93 problem, except for people with a large number of offsets in map entries.
99 similarly for expiring them which resolves the above problem. There is
101 sake of the problem explanation. The one important detail is that these
|
| D | dnotify.txt | 48 the problem of hard links to files has been ignored. So if a file (x)
|
| D | xfs-self-describing-metadata.txt | 7 The largest scalability problem facing XFS is not one of algorithmic
11 is this very scalability that causes the verification problem.
22 determine the root cause of a corruption problem, but it is still mainly a
110 determine the scope of the problem.
|
| D | dax.txt | 93 those pages. This problem is being worked on. That means that O_DIRECT
|
| D | f2fs.txt | 50 also updated recursively. This problem is called as wandering tree problem [1],
434 tree problem, F2FS is able to cut off the propagation of node updates caused by
573 log block thrashing problem in the greedy algorithm. F2FS adopts the greedy
|
| /linux-4.4.14/Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 3 * 1.01 Nov 2, 1994 -- Fixed problem with starting request in
24 * Aztech drives, which seem to have the same problem.
84 * Work around sporadic Sony55e audio play problem.
86 * problem with "hde=cdrom" with no drive present. -ml
241 * - Fixed a problem with WPI CDS-32X drive - it
255 * - Fix small problem with ide_cdrom_capacity
257 * 4.59 Aug 11, 2000 - Fix changer problem in cdrom_read_toc, we weren't
|
| D | ChangeLog.ide-floppy.1996-2002 | 57 * fix a lost interrupt problem. It appears the busy
|
| /linux-4.4.14/drivers/infiniband/hw/nes/ |
| D | Kconfig | 16 driver. Select this if you are diagnosing a problem.
|
| /linux-4.4.14/drivers/staging/rdma/amso1100/ |
| D | Kconfig | 15 or trying to diagnose a problem.
|
| /linux-4.4.14/Documentation/fb/ |
| D | tgafb.txt | 64 refreshed. This is an X server problem, not a tgafb problem, and is fixed in
|
| D | sstfb.txt | 144 problem with XFree86-4. Apparently recent Xfree86-4.x solve this
145 problem.
|
| D | matroxfb.txt | 102 problem and not mine, but I'm not sure.
378 + secondary head shares videomemory with primary head. It is not problem
399 + secondary head shares videomemory with primary head. It is not problem
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-arch.txt | 9 locked. This is usually not a problem unless switch_to may need to
40 4a. Common problem with this type of sleep appears to be:
|
| D | sched-rt-group.txt | 9 1.1 The problem
39 1.1 The problem
|
| D | completion.txt | 11 race-free solution to this problem. Semantically they are somewhat like a
151 A common problem that occurs is to have unclean assignment of return types,
|
| /linux-4.4.14/drivers/i2c/ |
| D | Kconfig | 128 problem with I2C support and want to see more of what is going on.
135 a problem with I2C support and want to see more of what is going
144 a problem with I2C support and want to see more of what is going
|
| /linux-4.4.14/Documentation/usb/ |
| D | rio.txt | 26 It seems that the Rio has a problem when sending .mp3 with low batteries.
30 know if that's normal or not; it could simply be a problem with the flash
36 problem. Do NOT allow your batteries to wear down to nothing before
|
| D | error-codes.txt | 58 problem that could not be worked around.
150 to some problem that could not be worked around,
|
| D | iuu_phoenix.txt | 14 I never had any problem with it, but I'm not a real
|
| D | persist.txt | 8 What is the problem?
51 you can convince the BIOS supplier to fix the problem (lots of luck!).
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Procfile.txt | 9 found in this tree. When you encounter a problem and need debugging,
208 When the problem is related with PCM, first try to turn on xrun_debug
217 when it's a PCM problem,
222 when it's a mixer problem,
|
| D | HD-Audio.txt | 12 problem is broken BIOS, and the rest is the driver implementation.
51 The most common problem of the controller is the inaccurate DMA
69 the above. If you get a problem of repeated sounds, this option might
88 A less often but a more severe problem is the codec probing. When
148 The most common problem regarding the HD-audio driver is the
227 Another related problem is the automatic mute of speaker output by
231 In anyway, try a different model option if you have such a problem.
236 If you are masochistic enough to debug the driver problem, note the
854 HD-audio pin control for jack retasking. If you have a problem about
|
| D | Channel-Mapping-API.txt | 18 The problem, so far, was that we had no standard channel map
|
| /linux-4.4.14/Documentation/zh_CN/video4linux/ |
| D | omap3isp.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | v4l2-framework.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /linux-4.4.14/drivers/infiniband/hw/cxgb3/ |
| D | Kconfig | 27 the driver or trying to diagnose a problem.
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | GPIO.txt | 58 3) s3c2410_gpio_pullup() changes have the problem that whilst the
66 which may be required if this becomes a problem.
81 numberspace, so there is no problem with converting the gpio numbering
|
| /linux-4.4.14/include/scsi/ |
| D | sg.h | 119 char problem; /* 0 -> no problem detected, 1 -> error to report */ member
|
| /linux-4.4.14/ |
| D | REPORTING-BUGS | 108 [1.] One line summary of the problem:
109 [2.] Full description of the problem/report:
118 problem (if possible)
126 [8.7.] Other information that might be relevant to the problem
|
| D | README | 331 how to duplicate the problem, and what your setup is (use your common
332 sense). If the problem is new, tell me so, and if the problem is
349 help debugging the problem. The text above the dump is also
385 "context" in your problem report, giving a few lines around the
|
| /linux-4.4.14/Documentation/ko_KR/ |
| D | stable_api_nonsense.txt | 6 a problem with the translation, please contact the maintainer of this file.
|
| D | HOWTO | 5 a problem with the translation, please contact the maintainer of this file.
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | README.freeze | 9 has a few hints how you can help to pin down the problem.
65 the problem without.
|
| D | PROBLEMS | 8 XFree-3.2A! This solved the problem for most people.
|
| /linux-4.4.14/Documentation/vm/ |
| D | balance | 33 doing fine even with the presence of this problem. In 2.3, due to
34 HIGHMEM, this problem is aggravated.
48 balancing problem, and stays as close to 2.2 behavior as possible. Also,
|
| D | slub.txt | 186 1. Description of the problem encountered
210 Shows a few bytes before the object where the problem was detected.
240 4. Report on how the problem was dealt with in order to ensure the continued
|
| D | page_owner.txt | 49 kernel memory problem.
|
| /linux-4.4.14/Documentation/ |
| D | percpu-rw-semaphore.txt | 7 The problem with traditional read-write semaphores is that when multiple
|
| D | cpu-load.txt | 27 kind/state. The problem with this is that the system could have
|
| D | stable_api_nonsense.txt | 135 reworked to prevent the security problem from occurring. When this
137 same time, ensuring that the security problem was fixed and could not
139 were not allowed to change, fixing this kind of security problem and
|
| D | stable_kernel_rules.txt | 10 problem..." type thing).
11 - It must fix a problem that causes a build error (but not for things
|
| D | highuid.txt | 18 architectures, this should not be a problem.
|
| D | assoc_array.txt | 58 problem, the iterator should lock against modification. Objects will not
316 this is a problem, then modification should be locked against. The
357 Poor scattering isn't too much of a problem as there are shortcuts and nodes
542 problem as we've passed the anchoring pointer and won't switch onto the
566 However, when we're changing a shortcut into a node this isn't a problem
|
| D | debugging-via-ohci1394.txt | 26 of physical address space. This can be a problem on IA64 machines where
27 memory is located mostly above that limit, but it is rarely a problem on
|
| D | SAK.txt | 74 Vixie cron also seems to have this problem, and needs the same treatment.
|
| D | cachetlb.txt | 231 The biggest problem is that of virtual aliasing in the data cache
237 physical address from existing at once, you have this problem.
239 If your D-cache has this problem, first define asm/shmparam.h SHMLBA
255 aliasing problem has the potential to exist since the kernel already
|
| D | SubmittingPatches | 109 Describe your problem. Whether your patch is a one-line bug fix or
110 5000 lines of a new feature, there must be an underlying problem that
112 problem worth fixing and that it makes sense for them to read past the
117 problem was spotted during code review, describe the impact you think
133 Once the problem is established, describe what you are actually doing
142 Solve only one problem per patch. If your description starts to get
225 series. Developers using "git bisect" to track down a problem can end up
464 make him endorse your bugs. To solve this problem, it is recommended that
|
| D | Intel-IOMMU.txt | 59 If this fixes anything, please ensure you file a bug reporting the problem.
|
| D | coccinelle.txt | 86 description of the problem being checked by the semantic patch, and
212 When the 'patch' mode is available, it proposes a fix for each problem
|
| D | ManagementStyle | 151 The problem with #1 is that it's very easy to do, since you can say
160 To solve this problem, you really only have two options:
245 ends up going overboard and hiding the problem, and as they say, "On the
|
| D | kmemcheck.txt | 91 debugging a problem. This option is not mandatory, however, because it slows
111 If you are using kmemcheck to actively debug a problem, then you
120 problem you were interested in.
123 enable kmemcheck in case of some problem, it might be a good idea to
155 error is detected to help the debugging of a particular problem.
|
| D | robust-futexes.txt | 38 There is a big conceptual problem with futex based mutexes though: it is
50 To solve this problem, the traditional approach was to extend the vma
|
| D | email-clients.txt | 294 although tab2space problem can be solved with external editor.
296 Another problem is that Gmail will base64-encode any message that has a
|
| D | flexible-arrays.txt | 6 Kernel programmers will sometimes respond to this problem by allocating
|
| /linux-4.4.14/arch/metag/ |
| D | Kconfig.debug | 31 problem with catch buffer handling much more apparent.
|
| /linux-4.4.14/drivers/usb/wusbcore/ |
| D | Kconfig | 37 to the system log. Select this if you are having a problem with
|
| /linux-4.4.14/Documentation/w1/masters/ |
| D | ds2490 | 65 reattaching would clear the problem. usbmon output in the guest and
66 host did not explain the problem. My guess is a bug in either qemu
|
| /linux-4.4.14/fs/befs/ |
| D | ChangeLog | 7 * Fixed module makefile problem. It was not compiling all the correct
35 a workaround for this problem (compatibility.h) [WD]
111 node. This is the cleaner solution to Brent Miszalaski's problem. [WD]
140 hanging disk io problem. It turns out you need to have the sync_pages
244 * Fixed a problem with reading the superblock on devices with large sector
339 * Fixed the problem with statfs where it would always claim the disk was
|
| /linux-4.4.14/drivers/staging/slicoss/ |
| D | TODO | 30 at problem
|
| /linux-4.4.14/Documentation/ja_JP/ |
| D | stable_kernel_rules.txt | 5 If you find difference with original file or problem in translation,
|
| D | stable_api_nonsense.txt | 6 or a problem with the translation,
|
| D | SubmitChecklist | 6 or a problem with the translation,
|
| D | HOWTO | 6 or a problem with the translation,
|
| D | SubmittingPatches | 6 or a problem with the translation,
|
| /linux-4.4.14/drivers/pps/ |
| D | Kconfig | 30 problem with PPS support and want to see more of what is going on.
|
| /linux-4.4.14/fs/xfs/ |
| D | Kconfig | 84 are debugging a particular problem.
95 not useful unless you are debugging a particular problem.
|
| /linux-4.4.14/Documentation/zh_CN/filesystems/ |
| D | sysfs.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /linux-4.4.14/Documentation/security/ |
| D | IMA-templates.txt | 15 However, the main problem to introduce this feature is that, each time
20 The proposed solution solves this problem by separating the template
|
| D | Yama.txt | 21 This is not a theoretical problem. SSH session hijacking
|
| D | keys-trusted-encrypted.txt | 127 compromised by a user level problem, and when sealed to specific boot PCR
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 8 Fix append problem to Samba servers (files opened with O_APPEND could
9 have duplicated data). Fix oops in cifs_lookup. Workaround problem
81 top of the share. Fix problem in 2.6.28 resolving DFS paths to
157 cifs_request_buffers pool. Fix problem with POSIX Open/Mkdir on
233 (fixes FC problem). Return error in rename 2nd attempt retry (ie report
247 problem (instantiate inodes/dentries in right order for readdir).
332 to be more accurate. Fix big endian problem with mapchars mount option,
370 Fix caching problem, in which readdir of directory containing a file
454 Fix internationalization problem in cifs readdir with filenames that map to
538 for each mounted share (new menuconfig option). Fix endianness problem in
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos-mic.txt | 5 solves this problem by compressing the frame data by 1/2 before it is
|
| /linux-4.4.14/scripts/coccinelle/free/ |
| D | devm_free.cocci | 7 /// A difficulty of detecting this problem is that the standard freeing
|
| /linux-4.4.14/drivers/scsi/osd/ |
| D | Kconfig | 48 track the problem (see also MAINTAINERS). Setting this will also
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 352 Several hardware limitations make the problem worse - if it is not possible to
417 this problem.
460 challenges arise. The most obvious problem is that time is now shared between
470 This same problem can occur on native hardware to a degree, as SMM mode may
481 or the RTC, but the problem is the same: the host virtualization engine may not
487 There are three approaches to solving this problem; first, it may be possible
494 solution to the problem has risen: the guest may need to become aware of lost
502 rate (ed: is it 18.2 Hz?) however that it has not yet been a problem in
542 This problem is particularly pronounced with an internal time source in Linux,
564 advancing faster than usual. A slower clock is less of a problem, as it can
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.pcbit | 32 the manufacturer in order to solve this problem.
|
| D | syncPPP.FAQ | 14 Q11: I can't connect. How can I check where the problem is.
193 Q11: I can't connect. How can I check where the problem is.
|
| D | README.sc | 164 Upon testing, the following problem was noted, the driver would load without
167 of this problem, change the BIOS settings so that the interrupts in question are
277 in a segmentation fault when 'insmod'ed. This problem was created when one of
|
| /linux-4.4.14/arch/powerpc/xmon/ |
| D | xmon.c | 3139 in_be32(&spu->problem->spu_runcntl_RW); in stop_spus()
3184 out_be32(&spu->problem->spu_runcntl_RW, in restart_spus()
3245 DUMP_FIELD(spu, "0x%p", problem); in dump_spu_fields()
3246 DUMP_VALUE("0x%x", problem->spu_runcntl_RW, in dump_spu_fields()
3247 in_be32(&spu->problem->spu_runcntl_RW)); in dump_spu_fields()
3248 DUMP_VALUE("0x%x", problem->spu_status_R, in dump_spu_fields()
3249 in_be32(&spu->problem->spu_status_R)); in dump_spu_fields()
3250 DUMP_VALUE("0x%x", problem->spu_npc_RW, in dump_spu_fields()
3251 in_be32(&spu->problem->spu_npc_RW)); in dump_spu_fields()
|
| /linux-4.4.14/arch/ia64/ |
| D | Kconfig.debug | 48 from step B3 or later don't have this problem. If you're unsure,
|
| /linux-4.4.14/Documentation/RCU/ |
| D | arrayRCU.txt | 16 case is -not- supported. The problem with RCU-protected indexes into
152 One way to avoid this problem is to assign a seqlock for
|
| D | rcubarrier.txt | 287 Much later, yours truly hit the RCU module-unload problem when
289 this problem as well.
317 problem. However, when the -rt RCU eventually does have per-CPU
|
| D | lockdep-splat.txt | 10 This problem can therefore be serious: it might result in random memory
|
| D | listRCU.txt | 225 additional RCU-induced staleness is normally not a problem.
313 "deleted" flag. If processing stale data really is a problem,
|
| D | rculist_nulls.txt | 7 to solve following problem :
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.saa7134 | 41 forget to tell me what it changes / which problem it fixes / whatever
|
| D | pxa_camera.txt | 134 would be a problem if the following sequence is encountered :
|
| /linux-4.4.14/arch/arm/mach-sa1100/ |
| D | sleep.S | 54 @ fixes resume problem on high speed SA1110
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | freezer-subsystem.txt | 26 demonstrate this problem using nested bash shells:
45 have a problem with this method of stopping and resuming tasks.
|
| /linux-4.4.14/Documentation/locking/ |
| D | ww-mutex-design.txt | 15 mutex for it to become available, this presents a problem because
19 makes. Which results in the potential for deadlock. The problem gets
24 simplified understanding of the problem you can ignore this.
27 this problem is quite simple. For each group of buffers (execbuf) that need
|
| /linux-4.4.14/drivers/rapidio/ |
| D | Kconfig | 45 problem with the RapidIO subsystem and want to see more of what is
|
| /linux-4.4.14/Documentation/scsi/ |
| D | sym53c8xx_2.txt | 48 11. SCSI problem troubleshooting
212 All I can say is that I never have had problem with tagged queuing using
267 driver notifies by default this problem to user by indicating the actual
566 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
574 15. SCSI problem troubleshooting
596 If it still fails, then you can send your problem description to
619 problem, as follows:
639 BF (0x20), then the cause may be likely due to a PCI BUS problem.
658 BUS problem is likely the cause of these errors.
|
| D | scsi-changer.txt | 43 and each CD-ROM) and 2 transport arms. No problem to handle.
110 logfiles). If you email me some question because of a problem with the
|
| D | in2000.txt | 8 compiled for SMP. I've fixed that problem, and after
142 252, because higher speeds may be a problem with poor quality
|
| D | qlogicfas.txt | 55 any problem worse.
|
| D | ChangeLog.ips | 84 4.00.02 - Fix problem with PT DCDB with no buffer
|
| D | FlashPoint.txt | 85 After this problem was identified, BusLogic contacted its major OEM
90 overall problem of FlashPoint support for Linux users. It did nothing to
|
| D | ChangeLog.megaraid | 82 Fix: MegaRAID F/W has fixed the problem and being process of release,
118 > We confirmed this patch fix the problem by IA64 server.
156 problem. I had to increase the loop counter to 0xFFFFFF. (6 F's)
211 problem had been a new warning showing up in sparse output on alpha
|
| D | ncr53c8xx.txt | 70 15. SCSI problem troubleshooting
296 driver notifies by default this problem to user by indicating the actual
999 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1169 other problem that may appear is timeouts. The only way to avoid
1201 This problem is described in SYMBIOS DEL 397, Part Number 69-039241, ITEM 4.
1233 15. SCSI problem troubleshooting
1255 If it still fails, then you can send your problem description to
1293 problem, as follows:
1313 BF (0x20), then the cause may be likely due to a PCI BUS problem.
1332 BUS problem is likely the cause of these errors.
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 33 user space to solve the problem. In future, we may
|
| /linux-4.4.14/drivers/net/wireless/ipw2x00/ |
| D | Kconfig | 37 this driver into your kernel image, you can avoid this problem by
99 this driver into your kernel image, you can avoid this problem by
|
| /linux-4.4.14/tools/testing/selftests/futex/ |
| D | README | 55 problem as we intend to write multiple tests which collide in this namespace.
|
| /linux-4.4.14/lib/ |
| D | Kconfig.kmemcheck | 73 error is detected to help the debugging of a particular problem.
|
| /linux-4.4.14/net/netlink/ |
| D | genetlink.c | 1086 goto problem; in genl_init()
1090 goto problem; in genl_init()
1094 problem: in genl_init()
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-dev-attrs.txt | 45 the card wait. This is not a problem if the whole card
|
| /linux-4.4.14/Documentation/s390/ |
| D | 3270.txt | 159 messages? Ha! There's your problem.
164 problem!
172 problem!
|
| /linux-4.4.14/Documentation/arm/ |
| D | README | 53 the problem, what you were doing, etc.
148 could be a bit of a problem! Suggestions on the correct way to do this
|
| /linux-4.4.14/Documentation/pps/ |
| D | pps.txt | 45 problem:
58 The problem can be simply solved if you consider that a PPS source is
|
| /linux-4.4.14/drivers/pci/ |
| D | Kconfig | 35 problem with PCI support and want to see more of what is going on.
|
| /linux-4.4.14/net/l2tp/ |
| D | Kconfig | 41 used to dump internal state of the l2tp drivers for problem
|
| /linux-4.4.14/arch/powerpc/platforms/pseries/ |
| D | Kconfig | 91 problem with the pseries core and want to see more of what is
|
| /linux-4.4.14/arch/blackfin/ |
| D | Kconfig.debug | 12 explaining what the problem was. This debugging information is
190 the hardware trace may indicate that the problem lies in kernel
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | ide-cd | 262 The most notorious of these is the CMD640B chip. This problem can
288 OK, and the problem is at the filesystem level (i.e., the CDROM is
323 upgrade, you can probably work around the problem by specifying a
335 as a command line parameter may work around the problem, at the
|
| /linux-4.4.14/Documentation/trace/ |
| D | stm.txt | 23 To solve this mapping problem, stm class provides a policy management
|
| /linux-4.4.14/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 124 get a BUG() very early in boot, this might fix the problem. For
|
| /linux-4.4.14/Documentation/dvb/ |
| D | README.dvb-usb | 102 2004-07-08 - firmware-extraction-2.422-problem solved, driver is now working
178 problem, if you only want to watch TV (this does not apply for HDTV),
|
| /linux-4.4.14/Documentation/nvmem/ |
| D | nvmem.txt | 18 This was also a problem as far as other in-kernel users were involved, since
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | adm1021 | 62 the oldest; it has the problem that it is not very well detectable. The
|
| D | zl6100 | 101 appears to be sufficient and has not caused any problems in testing. The problem
|
| D | submitting-patches | 20 warning helps hiding a real problem. If you don't like the kernel coding
|
| /linux-4.4.14/Documentation/parisc/ |
| D | registers | 108 that should not cause a problem for the calling routine.
|
| /linux-4.4.14/fs/ncpfs/ |
| D | Kconfig | 80 This option does not solve the problem that filenames appear
|
| /linux-4.4.14/Documentation/x86/i386/ |
| D | IO-APIC.txt | 33 Some interrupts are still listed as 'XT PIC', but this is not a problem;
|
| /linux-4.4.14/arch/cris/arch-v32/mm/ |
| D | mmu.S | 73 ; the TLB contents. The problem and workaround were verified
|
| /linux-4.4.14/Documentation/ia64/ |
| D | mca.txt | 56 monarch is entered. The monarch now tries to diagnose the problem
117 it is a difficult problem because of the asynchronous nature of these
|
| /linux-4.4.14/drivers/net/wireless/b43/ |
| D | Kconfig | 187 Only say Y, if you are debugging a problem in the b43 driver sourcecode.
|
| /linux-4.4.14/arch/powerpc/kvm/ |
| D | Kconfig | 104 guest in user mode (problem state) and emulating all
|
| /linux-4.4.14/drivers/base/ |
| D | Kconfig | 198 problem with the driver core and want to see more of what is
209 you are having a problem with devres or want to debug
|
| /linux-4.4.14/Documentation/i2c/ |
| D | fault-codes | 74 specific than ENXIO, implying the problem isn't with the
|
| /linux-4.4.14/Documentation/input/ |
| D | yealink.txt | 31 Q: Module yealink compiled and installed without any problem but phone
|
| /linux-4.4.14/Documentation/timers/ |
| D | highres.txt | 81 The clock events subsystem tries to address this problem by providing a generic
160 state. A workaround is available as an idea, but the problem has not been
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 577 recognized the IP datagram is discarded and an ICMP "parameter problem"
613 unrecognized tag type MUST be treated as a "parameter problem" and
630 discarded and an ICMP "parameter problem" (type 12) is generated and
690 generated due to a problem associated with the original CIPSO label then the
|
| /linux-4.4.14/drivers/net/can/ |
| D | Kconfig | 173 a problem with CAN support and want to see more of what is going
|
| /linux-4.4.14/drivers/s390/char/ |
| D | Kconfig | 111 problem reporting queue the call home records should be sent to.
|
| /linux-4.4.14/tools/perf/config/ |
| D | utilities.mak | 113 # This function avoids the problem by producing a string
|
| /linux-4.4.14/arch/m68k/q40/ |
| D | README | 137 classic configuration problem - don't send me anything in this case
|
| /linux-4.4.14/arch/powerpc/include/asm/ |
| D | spu.h | 126 struct spu_problem __iomem *problem; member
|