Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #79667 > unrolled thread
| Started by | AlMa <AlMa0@ro.ru> |
|---|---|
| First post | 2023-07-22 03:10 +0200 |
| Last post | 2023-08-01 01:20 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#1041678: at24 0-005…: supply vcc not found, using dummy regulator AlMa <AlMa0@ro.ru> - 2023-07-22 03:10 +0200
Bug#1041678: marked as done (at24 0-005…: supply vcc not found, using dummy regulator) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-01 01:20 +0200
| From | AlMa <AlMa0@ro.ru> |
|---|---|
| Date | 2023-07-22 03:10 +0200 |
| Subject | Bug#1041678: at24 0-005…: supply vcc not found, using dummy regulator |
| Message-ID | <GU9i9-1R3x-3@gated-at.bofh.it> |
Package: linux-image-6.1.0-10-amd64 Version: 6.1.37-1 Severity: wishlist Control: affects -1 src:linux In my journal I discovered a bunch of orange warnings of the form “at24 0-005…: supply vcc not found, using dummy regulator”: Jul 22 00:07:06 AnonymizedMachineName kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Jul 22 00:07:06 AnonymizedMachineName kernel: input: PC Speaker as /devices/platform/pcspkr/input/input9 Jul 22 00:07:06 AnonymizedMachineName kernel: usbcore: registered new interface driver cdc_mbim Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0050: supply vcc not found, using dummy regulator Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0050: 256 byte spd EEPROM, read-only Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0051: supply vcc not found, using dummy regulator Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0051: 256 byte spd EEPROM, read-only Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0052: supply vcc not found, using dummy regulator Jul 22 00:07:06 AnonymizedMachineName kernel: iTCO_vendor_support: vendor-support=0 Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0052: 256 byte spd EEPROM, read-only Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0053: supply vcc not found, using dummy regulator Jul 22 00:07:06 AnonymizedMachineName kernel: at24 0-0053: 256 byte spd EEPROM, read-only Jul 22 00:07:06 AnonymizedMachineName kernel: mc: Linux media interface: v0.10 First, I asked myself what I am being warned about, and it took me quite some time to find out what “vcc” means. Is actually “Vcc”, the voltage common collector as on http://upload.wikimedia.org/wikipedia/commons/4/4b/Voltage_subscripts.png , meant (where “cc” or “CC” is sometimes typeset as a subscript)? If so, write this way, i.e., “Vcc” (or, as a proper abbreviation, “VCC”). The term “vcc” in small letters means to me, for example, the command-line call of the verifying C compiler; to other folks “vcc” might mean something else. If “vcc” here is NOT the voltage common collector, consider writing the full term instead of the abbreviation. (Similar goes for “spd”: if it's a proper abbreviation and not a typo, consider capitalizing all the letters. Further, even “SPD“ might mean many things, from “Serial Presence Detect” to “Surge Protection Device”, so if the context doesn't make it clear, write the full term instead of the abbreviation.) Second, are these orange messages real warnings (i.e., they foretell potential havoc) or only informational? In the real case, what could go wrong? In the purely informational case, consider making them normal gray-white messages, so that the user is nor really feeling warned or bothered. Gratefully, AlMa
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2023-08-01 01:20 +0200 |
| Subject | Bug#1041678: marked as done (at24 0-005…: supply vcc not found, using dummy regulator) |
| Message-ID | <GXKlb-49LV-13@gated-at.bofh.it> |
| In reply to | #79667 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Tue, 01 Aug 2023 01:09:37 +0200 with message-id <6531216.tM3a2QDmDi@bagend> and subject line Re: Debian's BTS is not for regular user questions has caused the Debian Bug report #1041678, regarding at24 0-005…: supply vcc not found, using dummy regulator to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1041678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041678 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web