Home
last modified time | relevance | path

Searched refs:reboot (Results 1 – 164 of 164) sorted by relevance

/linux-4.1.27/Documentation/devicetree/bindings/power/reset/
Dsyscon-reboot.txt6 with the mask defined in the reboot node.
9 - compatible: should contain "syscon-reboot"
11 - offset: offset in the register map for the reboot register (in bytes)
12 - mask: the reset value written to the reboot register (32 bit access)
18 reboot {
19 compatible = "syscon-reboot";
/linux-4.1.27/drivers/power/reset/
DMakefile5 obj-$(CONFIG_POWER_RESET_BRCMSTB) += brcmstb-reboot.o
8 obj-$(CONFIG_POWER_RESET_HISI) += hisi-reboot.o
15 obj-$(CONFIG_POWER_RESET_VERSATILE) += arm-versatile-reboot.o
17 obj-$(CONFIG_POWER_RESET_XGENE) += xgene-reboot.o
19 obj-$(CONFIG_POWER_RESET_SYSCON) += syscon-reboot.o
DKconfig119 bool "ARM Versatile family reboot driver"
/linux-4.1.27/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,brcmstb.txt46 Lastly, nodes that allow for support of SMP initialization and reboot are
77 reboot
82 The string property "brcm,brcmstb-reboot" for 40nm/28nm chips with
83 the new SYS_CTRL interface, or "brcm,bcm7038-reboot" for 65nm
94 reboot {
95 compatible = "brcm,brcmstb-reboot";
/linux-4.1.27/Documentation/watchdog/
Dwdt.txt11 to within a timeout or the machine will reboot. Each write delays the reboot
13 reboot will depend on the state of the machines and interrupts. The hardware
15 will reboot from almost anything.
Dwatchdog-api.txt26 system (causing a reboot) after the timeout occurs.
36 activates as soon as /dev/watchdog is opened and will reboot unless
48 crashes the system will not reboot. Because of this, some of the
52 started. So, if the watchdog daemon crashes, the system will reboot
65 cause a reboot if the watchdog is not re-opened in sufficient time.
131 Get the number of seconds before reboot:
134 before the system will reboot. The WDIOC_GETTIMELEFT is the ioctl
135 that returns the number of seconds before reboot.
144 the reason for the last reboot of the system. The GETSUPPORT ioctl is
185 The last reboot was caused by the watchdog card
[all …]
Dwatchdog-parameters.txt157 testmode: Watchdog test mode (1 = no reboot), default=0
251 soft_noboot: Watchdog action, set to 1 to ignore reboots, 0 to reboot
324 soft_noboot: Softdog action, set to 1 to ignore reboots, 0 to reboot
374 testmode: Watchdog testmode (1 = no reboot), default=0
388 testmode: Watchdog testmode (1 = no reboot), default=0
Dhpwdt.txt54 2. reboot the sever
/linux-4.1.27/arch/arm/mach-zynq/
Dslcr.c99 u32 reboot; in zynq_slcr_system_reset() local
113 zynq_slcr_read(&reboot, SLCR_REBOOT_STATUS_OFFSET); in zynq_slcr_system_reset()
114 zynq_slcr_write(reboot & 0xF0FFFFFF, SLCR_REBOOT_STATUS_OFFSET); in zynq_slcr_system_reset()
/linux-4.1.27/Documentation/devicetree/bindings/arm/hisilicon/
Dhisilicon.txt30 - reboot-offset : offset in sysctrl for system reboot
40 reboot-offset = <0x4>;
61 reboot-offset = <0x4>;
/linux-4.1.27/arch/mips/boot/dts/brcm/
Dbcm6328.dtsi79 reboot {
80 compatible = "syscon-reboot";
Dbcm7125.dtsi104 reboot {
105 compatible = "brcm,bcm7038-reboot";
Dbcm7360.dtsi98 reboot {
99 compatible = "brcm,brcmstb-reboot";
Dbcm7358.dtsi98 reboot {
99 compatible = "brcm,brcmstb-reboot";
Dbcm7362.dtsi104 reboot {
105 compatible = "brcm,brcmstb-reboot";
Dbcm7420.dtsi105 reboot {
106 compatible = "brcm,bcm7038-reboot";
Dbcm7425.dtsi106 reboot {
107 compatible = "brcm,brcmstb-reboot";
Dbcm7346.dtsi104 reboot {
105 compatible = "brcm,brcmstb-reboot";
/linux-4.1.27/Documentation/x86/x86_64/
Dboot-options.txt39 in a reboot. On Intel systems it is enabled by default.
109 reboot=b[ios] | t[riple] | k[bd] | a[cpi] | e[fi] [, [w]arm | [c]old]
110 bios Use the CPU reboot vector for warm reset
111 warm Don't set the cold reboot flag
112 cold Set the cold reboot flag
116 ACPI reset does not work, the reboot path attempts the reset using
119 EFI reset does not work, the reboot path attempts the reset using
125 on reboot so there may be boot problems on some systems.
127 reboot=force
129 Don't stop other CPUs on reboot. This can make reboot more reliable
Duefi.txt38 reboot_type=k turn off EFI reboot runtime service
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dmmc-pwrseq-emmc.txt7 unknown state), and before performing complete system reboot (also in
8 case of emergency reboot call). The latter is needed on boards, which
/linux-4.1.27/kernel/
Dpid_namespace.c265 if (pid_ns->reboot) in zap_pid_ns_processes()
266 current->signal->group_exit_code = pid_ns->reboot; in zap_pid_ns_processes()
316 pid_ns->reboot = SIGHUP; in reboot_pid_ns()
321 pid_ns->reboot = SIGINT; in reboot_pid_ns()
Dreboot.c280 SYSCALL_DEFINE4(reboot, int, magic1, int, magic2, unsigned int, cmd, in SYSCALL_DEFINE4() argument
DMakefile11 notifier.o ksysfs.o cred.o reboot.o \
/linux-4.1.27/Documentation/power/
Ds2ram.txt23 driver that doesn't resume and recompile and reboot).
39 - if it doesn't come back up (which is usually the problem), reboot by
70 survive a reboot.
82 As the clock keeps ticking it is also essential that the reboot is done
Dinterface.txt40 [shutdown] reboot test testproc
46 'reboot'
70 reboot it and run
Dbasic-pm-debugging.txt6 To check if hibernation works, you can try to hibernate in the "reboot" mode:
8 # echo reboot > /sys/power/disk
11 and the system should create a hibernation image, reboot, resume and get back to
16 resuming the system.] Moreover, hibernating in the "reboot" and "shutdown"
19 to hibernate or resume in the "reboot" mode, you should try the "platform" mode:
33 (it is similar to the "reboot" mode, but it requires you to press the power
152 "reboot", "shutdown" and "platform" modes. If that does not work, there
Ddrivers-testing.txt28 b) Load the driver and attempt to hibernate in the "reboot", "shutdown" and
35 in the "reboot", "shutdown" and "platform" modes.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-driver-toshiba_acpi15 a reboot for changes to take effect.
112 Note that toggling this value requires a reboot for changes to
156 Note that toggling this value requires a reboot for changes to
168 Note that toggling this value requires a reboot for changes to
179 Note that toggling this value requires a reboot for changes to
Dsysfs-firmware-gsmi43 a reboot is required for the configuration to be
57 Callers should assume that a reboot is needed
Dsysfs-power51 'reboot' - the memory image will be saved by the kernel and
73 'reboot'
110 the machine, then reboot it and run
Dsysfs-bus-iio1147 since the last reboot while activated. Units after application
1256 since the last reboot while activated.
/linux-4.1.27/arch/m68k/hp300/
DMakefile5 obj-y := config.o time.o reboot.o
/linux-4.1.27/arch/arm/boot/dts/
Dbcm7445.dtsi119 reboot {
120 compatible = "brcm,brcmstb-reboot";
Dhip01.dtsi93 reboot-offset = <0x4>;
Dvfxxx.dtsi46 reboot: syscon-reboot { label
47 compatible = "syscon-reboot";
Dvexpress-v2m-rs1.dtsi430 reboot@0 {
431 compatible = "arm,vexpress-reboot";
Dvexpress-v2m.dtsi429 reboot@0 {
430 compatible = "arm,vexpress-reboot";
Dhisi-x5hd2.dtsi398 reboot {
399 compatible = "syscon-reboot";
Dhi3620.dtsi101 reboot-offset = <0x4>;
/linux-4.1.27/Documentation/s390/
D3270.ChangeLog28 Apr 2002: Fix 3270 console reboot loop
29 * (Belated log entry) Fixed reboot loop if 3270 console,
D3270.txt96 haven't already. Define them before you reboot (reipl):
102 4. Reboot. The reboot process scans hardware devices, including
177 3215 console and then reboot the system.
/linux-4.1.27/Documentation/
Dbasic_profiling.txt35 Configure with CONFIG_PROFILING=y and CONFIG_OPROFILE=y & reboot on new kernel
55 A reset is needed to clear old statistics, which survive a reboot.
Ddell_rbu.txt28 inform the BIOS to enable the update in the next system reboot.
97 code which sends the BIOS update request to the BIOS. So on the next reboot
Dsysrq.txt27 128 = 0x80 - allow reboot/poweroff
68 'b' - Will immediately reboot the system without syncing or unmounting
148 reboot(b) is good when you're unable to shut down. But you should also
161 umount(u), then reboot(b) when my system locks. It's saved me many a fsck.
Dlockup-watchdogs.txt29 to cause the system to reboot automatically after a specified amount
DSAK.txt24 What key sequence should you use? Well, CTRL-ALT-DEL is used to reboot
Dldm.txt23 partitions and filesystems without the need to reboot.
Dramoops.txt115 # reboot -f
Ddebugging-via-ohci1394.txt163 host loaded, reboot the debugged machine, booting the kernel which has
Dcpu-hotplug.txt223 It's said poweroff/reboot may depend on CPU0 on some machines although I haven't
224 seen any poweroff/reboot failure so far after CPU0 is offline on a few tested
Dintel_txt.txt146 attempt to crash the system to gain control on reboot and steal
Drobust-futexes.txt46 In practice, when e.g. yum is kill -9-ed (or segfaults), a system reboot
DIPMI.txt641 gets a pre-action. During a panic or a reboot, the watchdog will
642 start a 120 timer if it is running to make sure the reboot occurs.
D00-INDEX473 - how to auto-reboot Linux if it has "fallen and can't get up". ;-)
Dbcache.txt89 This only has to be done once. The next time you reboot, just reregister all
Dkernel-parameters.txt510 until the next reboot
2459 nonmi_ipi [X86] Disable using NMI IPIs during panic/reboot to
2518 It's said poweroff/reboot may depend on CPU0 on some
2580 Useful together with panic=30 to trigger a reboot.
2594 timeout < 0: reboot immediately
3211 reboot= [KNL]
DDMA-API.txt680 Notice that you can not enable it again at runtime. You have to reboot to do
/linux-4.1.27/drivers/firmware/efi/
DMakefile4 obj-$(CONFIG_EFI) += efi.o vars.o reboot.o
/linux-4.1.27/fs/pstore/
DKconfig29 interface /dev/pmsg0 to log user space messages. On reboot
41 ram buffer that can be decoded and dumped after reboot through
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/4xx/
Dreboot.txt1 Reboot property to control system reboot on PPC4xx systems:
/linux-4.1.27/arch/mips/fw/arc/
Dmisc.c59 ARC_CALL0(reboot); in ArcReboot()
/linux-4.1.27/arch/mips/lantiq/
Dclk.h66 void (*reboot) (struct clk *clk); member
/linux-4.1.27/arch/m68k/
DKconfig100 current kernel, and to start another kernel. It is like a reboot
101 but it is independent of the system firmware. And like a reboot
/linux-4.1.27/include/linux/
Dpid_namespace.h46 int reboot; /* group exit code if this pidns was rebooted */ member
/linux-4.1.27/arch/um/kernel/
DMakefile14 physmem.o process.o ptrace.o reboot.o sigio.o \
/linux-4.1.27/arch/blackfin/kernel/
DMakefile10 fixed_code.o reboot.o bfin_dma.o \
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Dimx-thermal.txt7 is higher than panic threshold, system will auto reboot by SRC module.
/linux-4.1.27/arch/tile/kernel/
DMakefile7 pci-dma.o proc.o process.o ptrace.o reboot.o \
/linux-4.1.27/Documentation/security/
DSELinux.txt17 you are, reboot with selinux disabled
/linux-4.1.27/Documentation/scsi/
Ddpti.txt55 * Enabled hba reset from ioctls (allows a FW flash to reboot and use the new
56 * FW without having to reboot)
Dlpfc.txt36 being removed, a switch rebooting, or a device reboot), the driver could
DBusLogic.txt557 appropriate, and reboot.
/linux-4.1.27/arch/x86/realmode/rm/
DMakefile26 realmode-y += reboot.o
/linux-4.1.27/arch/sh/kernel/
DMakefile18 reboot.o return_address.o \
/linux-4.1.27/arch/arm64/boot/dts/arm/
Drtsm_ve-motherboard.dtsi263 reboot@0 {
264 compatible = "arm,vexpress-reboot";
/linux-4.1.27/drivers/watchdog/
DKconfig16 reboot the machine) and a driver for hardware watchdog boards, which
24 also monitor NFS connections and can reboot the machine when the process
60 A software monitoring watchdog. This will fail to reboot your system
152 ARM Primecell SP805 Watchdog timer. This will reboot your system when
159 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
168 reboot your system when the timeout is reached.
221 Watchdog timer embedded into KS8695 processor. This will reboot your
237 Watchdog timer block in the Samsung SoCs. This will reboot
253 reboot your system when timeout is reached.
523 Watchdog timer embedded into AT32AP700x devices. This will reboot
[all …]
Dcpwd.c79 bool reboot; member
570 p->reboot = (prop_val ? true : false); in cpwd_probe()
/linux-4.1.27/drivers/acpi/
DMakefile21 acpi-y += osl.o utils.o reboot.o
DKconfig87 Controller in a way that a normal reboot is not enough. You then
/linux-4.1.27/Documentation/networking/
Dipv6.txt34 A reboot is required to enable IPv6.
Dde4x5.txt49 reboot sequences). Loadable module support under PCI and EISA has been
76 kernel with the de4x5 configuration turned off and reboot.
Digb.txt74 WoL will be enabled on the system during the next shut down or reboot.
Diphase.txt55 e. Install the new built kernel and modules and reboot.
De100.txt140 WoL will be enabled on the system during the next shut down or reboot. For
DREADME.sb1000139 If you do this to /proc/sys/net/ipv4/conf/default/rp_filter on each reboot
De1000e.txt292 WoL will be enabled on the system during the next shut down or reboot.
Dcxgb.txt110 Making any of the following system changes will only last until you reboot
Darcnet.txt120 messages when you reboot into the new Linux kernel.
507 with "arcnet:" and has shown up since the last reboot) in your mail.
Dixgb.txt249 only last only until the next system reboot.
De1000.txt444 WoL will be enabled on the system during the next shut down or reboot.
/linux-4.1.27/fs/lockd/
Dsvc4proc.c496 PROC(sm_notify, reboot, void, reboot, void, 1),
Dsvcproc.c540 PROC(sm_notify, reboot, void, reboot, void, 1),
/linux-4.1.27/arch/arm/kernel/
DMakefile19 process.o ptrace.o reboot.o return_address.o \
/linux-4.1.27/arch/sparc/kernel/
DMakefile57 obj-$(CONFIG_SPARC64) += reboot.o
/linux-4.1.27/kernel/power/
DKconfig34 system and powers it off; and restores that checkpoint on reboot.
197 reboot. The architecture needs to support this, x86 for
219 machine, reboot it and then run
/linux-4.1.27/tools/testing/ktest/
Dktest.pl100 my $reboot;
248 "REBOOT" => \$reboot,
1326 sub reboot { subroutine
1340 if (run_command $reboot) {
1380 reboot $time;
1899 reboot;
2099 reboot $sleep_time;
/linux-4.1.27/Documentation/device-mapper/
Ddm-log.txt33 will not survive a reboot or crash, but there may be a small boost in
Dsnapshot.txt44 after reboot).
/linux-4.1.27/arch/x86/kernel/
DMakefile57 obj-y += reboot.o
/linux-4.1.27/arch/mips/lantiq/falcon/
Dsysctrl.c181 clk->reboot = sysctl_reboot; in clkdev_add_sys()
/linux-4.1.27/drivers/platform/chrome/
Dcros_ec_sysfs.c244 static DEVICE_ATTR(reboot, S_IWUSR | S_IRUGO, show_ec_reboot, store_ec_reboot);
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dvexpress-sysreg.txt75 "arm,vexpress-reboot"
/linux-4.1.27/fs/proc/
DKconfig54 a recompile of the kernel or reboot of the system. The primary
/linux-4.1.27/Documentation/acpi/
Dinitrd_table_override.txt72 # reboot with increased acpi debug level, e.g. boot params:
Dmethod-customizing.txt16 rebuild/reboot is not needed and test result can be got in minutes.
/linux-4.1.27/arch/x86/boot/
Dheader.S75 # Allow the user to press a key, then reboot
/linux-4.1.27/drivers/staging/unisys/Documentation/
Dproc-entries.txt80 next reboot will launch the installation and recovery tool. If set to
/linux-4.1.27/Documentation/cdrom/
Dpacket-writing.txt7 - Compile and install kernel and modules, reboot.
/linux-4.1.27/lib/
DKconfig.kgdb123 CONFIG_KDB_CONTINUE_CATASTROPHIC == 2. KDB forces a reboot.
DKconfig.debug358 will be able to flush the buffer cache to disk, reboot the system
737 to cause the system to reboot automatically after a
791 to cause the system to reboot automatically after a
830 Set the timeout value (in seconds) until a reboot occurs when the
833 value n < 0 will reboot immediately.
1206 on a single reboot.
/linux-4.1.27/arch/um/
DKconfig.um85 will be able to flush the buffer cache to disk, reboot the system
/linux-4.1.27/arch/mips/include/asm/
Dsgiarcs.h195 LONG reboot; /* Reboot the machine. */ member
/linux-4.1.27/Documentation/powerpc/
Dfirmware-assisted-dump.txt36 unlike kdump, fadump doesn't need a 2nd reboot to get back
213 dump and continue without 2nd reboot.
Deeh-pci-error-recovery.txt17 card to be "rebooted", without also having to reboot the operating
28 the OS the ability to "reboot"/recover individual PCI devices.
Dhvcs.txt523 after a reboot. What happened?
/linux-4.1.27/arch/parisc/kernel/
Dsyscall_table.S164 ENTRY_SAME(reboot)
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfs.txt39 or loss of state during NFS reboot recovery or transparent state migration.
DExporting15 server-reboot (among other things, though these tend to be the most
Dnfs-rdma.txt138 - Build, install, reboot
/linux-4.1.27/arch/powerpc/include/asm/
Dsystbl.h95 SYSCALL(reboot)
/linux-4.1.27/Documentation/ia64/
Defirtc.txt94 i.e. reboot. This is very different from the alarm provided by the legacy
/linux-4.1.27/Documentation/kdump/
Dkdump.txt14 the reboot and is accessible to the dump-capture kernel.
422 described, the system will reboot into the dump-capture kernel if a
453 Before analyzing the dump image, you should reboot into a stable kernel.
/linux-4.1.27/Documentation/sound/oss/
DREADME.modules24 Once you are configured, make zlilo, modules, modules_install; reboot.
/linux-4.1.27/Documentation/hwmon/
Dabituguru-datasheet39 after a reboot uGuru will hold 0x00 here, but if the driver is removed and
310 voltages which proprably safed my computer (after a reboot I managed to
/linux-4.1.27/drivers/md/bcache/
Dsuper.c2097 static struct notifier_block reboot = { variable
2112 unregister_reboot_notifier(&reboot); in bcache_exit()
2125 register_reboot_notifier(&reboot); in bcache_init()
2130 unregister_reboot_notifier(&reboot); in bcache_init()
/linux-4.1.27/arch/ia64/
DKconfig546 current kernel, and to start another kernel. It is like a reboot
547 but it is independent of the system firmware. And like a reboot
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-class-tpm167 cycle. Whether a warm boot (reboot) will clear a TPM chip
/linux-4.1.27/Documentation/blockdev/
Dramdisk.txt19 are erased on reboot.
DREADME.DAC960218 standard kernel, run lilo if appropriate, and reboot.
/linux-4.1.27/drivers/net/ethernet/myricom/myri10ge/
Dmyri10ge.c3555 u32 reboot; in myri10ge_read_reboot() local
3562 pci_read_config_dword(pdev, vs + 0x14, &reboot); in myri10ge_read_reboot()
3563 return reboot; in myri10ge_read_reboot()
3611 u32 reboot, rx_pause_cnt; in myri10ge_watchdog() local
3625 reboot = myri10ge_read_reboot(mgp); in myri10ge_watchdog()
3627 reboot, myri10ge_reset_recover ? "" : " not"); in myri10ge_watchdog()
/linux-4.1.27/arch/s390/kernel/
Dcompat_wrapper.c94 COMPAT_SYSCALL_WRAP4(reboot, int, magic1, int, magic2, unsigned int, cmd, void __user *, arg);
/linux-4.1.27/arch/x86/syscalls/
Dsyscall_64.tbl178 169 common reboot sys_reboot
Dsyscall_32.tbl97 88 i386 reboot sys_reboot
/linux-4.1.27/Documentation/driver-model/
Ddriver.txt171 driver module is being unloaded, during a reboot sequence, or
/linux-4.1.27/arch/sh/
DKconfig607 current kernel, and to start another kernel. It is like a reboot
608 but it is independent of the system firmware. And like a reboot
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt68 - reboot-cmd [ SPARC only ]
254 Nerve Pinch (tm) will be an immediate reboot, without even
718 reboot-cmd: (Sparc only)
/linux-4.1.27/Documentation/sound/alsa/
DCMIPCI.txt43 from front and rear speakers! But.. after reboot, all was gone.
DHD-Audio.txt718 `probe_only=1` option (at best after the cold reboot) and run
/linux-4.1.27/arch/x86/
DKconfig.debug132 would otherwise cause a system to silently reboot. Disabling this
DKconfig1079 bool "Enable X86 board specific fixups for reboot"
1083 in order to get reboot to work correctly. This is only needed on
1085 this config is intended, is when reboot ends with a stalled/hung
1722 current kernel, and to start another kernel. It is like a reboot
1723 but it is independent of the system firmware. And like a reboot
/linux-4.1.27/arch/tile/
DKconfig203 current kernel, and to start another kernel. It is like a reboot
/linux-4.1.27/drivers/char/
DKconfig224 shutdown and reboot by pressing the orange button a number of times.
551 out to lunch past a certain margin. It can reboot the system
/linux-4.1.27/include/uapi/linux/
DKbuild343 header-y += reboot.h
/linux-4.1.27/Documentation/PCI/
Dpcieaer-howto.txt262 After reboot with new kernel or insert the module, a device file named
Dpci-error-recovery.txt178 >>> and prints an error to syslog. A reboot is then required to
Dpci.txt119 the power state of a device before reboot.
/linux-4.1.27/Documentation/usb/
Dgadget_serial.txt124 controller driver. This must be done each time you reboot the gadget
Dproc_usb_info.txt26 to /etc/fstab. This will mount usbfs at each reboot.
/linux-4.1.27/arch/powerpc/
DKconfig418 current kernel, and to start another kernel. It is like a reboot
419 but it is independent of the system firmware. And like a reboot
/linux-4.1.27/drivers/usb/atm/
Dueagle-atm.c2303 static ssize_t reboot(struct device *dev, struct device_attribute *attr, in reboot() function
2320 static DEVICE_ATTR(stat_status, S_IWUSR | S_IRUGO, read_status, reboot);
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt78 10.2 halt and reboot
2247 o halt or reboot the machine
2307 o reboot
2345 10.2. halt and reboot
2973 *** Dropping you to a shell; the system will reboot
3435 *** Dropping you to a shell; the system will reboot
/linux-4.1.27/Documentation/timers/
DNO_HZ.txt308 o A reboot is required to reconfigure both adaptive idle and RCU
/linux-4.1.27/
DREADME312 reboot, and enjoy!
DCREDITS1381 D: /proc/cpuinfo, reboot on panic , kernel pre-patch tester ;)
2047 D: Arc monochrome LCD framebuffer driver, x86 reboot fixups
/linux-4.1.27/arch/arm/
DKconfig1848 look like a DTB header after a reboot if no actual DTB is appended
1957 current kernel, and to start another kernel. It is like a reboot
1958 but it is independent of the system firmware. And like a reboot
/linux-4.1.27/Documentation/input/
Djoystick.txt154 This way, after the next reboot your joystick will remain calibrated. You
/linux-4.1.27/arch/alpha/
DKconfig656 the printing mode to be 0. Then, upon reboot, one could add
/linux-4.1.27/Documentation/filesystems/
Dntfs.txt71 run three times in sequence with each driver (after a reboot) on a 1.4GiB
Dproc.txt1388 reboot the machine once an error has been made.
1412 need to recompile the kernel, or even to reboot the system. The files in the
/linux-4.1.27/arch/mips/
DKconfig2592 current kernel, and to start another kernel. It is like a reboot
2593 but it is independent of the system firmware. And like a reboot
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt960 shutdown/reboot).
1122 (so that volume/mute changes are remembered across shutdown/reboot).
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt528 running. In other words, it is not necessary to reboot the system
959 you reboot, or until you load another keymap.
/linux-4.1.27/Documentation/filesystems/cifs/
DREADME420 unmount or reboot which can confuse some applications,