Lines Matching refs:something
74 something else. These steps thus help to ensure the time you invest in this
111 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
144 that hear about it for the first time. And if you learned something in this
182 face one of those if something breaks when updating from 5.10.4 to 5.10.5 (a
398 You deal with a 'regression' if something that worked with an older version of
416 An issue is a 'really severe problem' when something totally unacceptably bad
451 * When dealing with a regression, make sure it's not something else that
456 something in the BIOS Setup can also lead to problems that on look a lot
500 The kernel marks itself with a 'taint' flag when something happens that might
593 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
596 Regression within a stable and longterm kernel version line are something the
601 regressions with newer kernel version line (say something broke when switching
632 code it builds upon, but unless you suspect something like that stick to the
633 driver. If it's really something else, the driver's developers will get the
643 [user@something ~]$ lspci -k
654 interface, which might be something like 'wlp58s0'. This name can be used like
657 …[user@something ~]$ realpath --relative-to=/sys/module/ /sys/class/net/wlp58s0/device/driver/module
669 MAINTAINERS file, as then you might find something like this::
769 regular internet search engine and add something like
844 to that if you're dealing with something that shouldn't wait. In that case
932 something happens that can lead to follow-up errors that look totally
962 that hear about it for the first time. And if you learned something in this
993 …[user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux
1000 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
1040 get something quickly fixed. But for that to happen the change that's causing
1060 introduced the regression. If something for example breaks when switching from
1073 the kernel and not by something else, as outlined above already.
1159 report. Ideally use something where the files stay available for years, as
1210 Don't worry too much about forgetting something, as developers will ask for
1220 something like 'The detailed description:' before the part you just wrote and
1329 * Someone tells you to send something privately.
1331 * You were told to send something, but noticed it contains sensitive
1337 process someone might tell you to do something that requires a skill you might
1358 should wait a week at maximum (or just two days if it's something urgent)
1378 idea, but only report your results if something relevant changed or if you are
1379 writing something anyway.
1400 **Inquiries for data**: Often you will be asked to test something or provide
1423 your report arrived or had something more important to take care of. When
1471 together that mentions how many you are and why this is something that in your
1533 a recheck. Say something broke when you updated from 5.10.4-vendor.42 to
1560 try to find that version using vanilla kernels. Lets assume something broke when
1715 Maybe their test hardware broke, got replaced by something more fancy, or is so
1716 old that it's something you don't find much outside of computer museums
1718 something different in their life became way more important. In some cases
1729 much time and energy in maintaining a Linux kernel driver for something they