/openbmc/linux/net/mac80211/ |
H A D | Kconfig | 88 bool "Trace all mac80211 debug messages" 93 collect all debugging messages, independent of 96 The overhead in this option is that all the messages 127 many debugging messages. It should not be selected 128 on production systems as some of the messages are 138 debugging messages for the managed-mode MLME. It 140 of the messages are remotely triggerable. 149 debugging messages for station addition/removal. 161 of the messages are remotely triggerable. 170 very verbose OCB debugging messages. It should not [all …]
|
/openbmc/phosphor-power/phosphor-regulators/src/ |
H A D | journal.hpp | 33 * The interface is used to write messages/log entries to the system journal. 47 * Gets the journal messages that have the specified field set to the 50 * The messages in the returned vector are ordered from oldest to newest. 54 * @param max Maximum number of messages to return. Specify 0 to return all 55 * matching messages. 56 * @return matching messages from the journal 70 * Logs debug messages in the system journal. 72 * @param messages messages to log 74 virtual void logDebug(const std::vector<std::string>& messages) = 0; 84 * Logs error messages in the system journal. [all …]
|
H A D | exception_utils.hpp | 48 * Gets the error messages from the specified exception and any nested inner 51 * If the exception contains nested inner exceptions, the messages in the 56 * @return error messages from exceptions 80 * Gets the error messages from the specified exception and any nested inner 83 * Stores the error messages in the specified vector, from innermost exception 87 * @param messages vector where error messages will be stored 89 void getMessages(const std::exception& e, std::vector<std::string>& messages);
|
H A D | exception_utils.cpp | 31 std::vector<std::string> messages{}; in getMessages() local 32 internal::getMessages(e, messages); in getMessages() 33 return messages; in getMessages() 62 void getMessages(const std::exception& e, std::vector<std::string>& messages) in getMessages() argument 64 // If this exception is nested, get messages from inner exception(s) in getMessages() 71 getMessages(inner, messages); in getMessages() 77 messages.emplace_back(e.what()); in getMessages()
|
/openbmc/phosphor-fan-presence/test/ |
H A D | logger_test.cpp | 19 auto messages = logger.getLogs(); in TEST() local 21 ASSERT_EQ(messages.size(), logSize); in TEST() 23 EXPECT_EQ((messages[0][1].get<std::string>()), "Test Message 0"); in TEST() 24 EXPECT_EQ((messages[1][1].get<std::string>()), "Test Message 1"); in TEST() 25 EXPECT_EQ((messages[2][1].get<std::string>()), "Test Message 2"); in TEST() 26 EXPECT_EQ((messages[3][1].get<std::string>()), "Test Message 3"); in TEST() 27 EXPECT_EQ((messages[4][1].get<std::string>()), "Test Message 4"); in TEST() 31 for (const auto& msg : messages) in TEST() 39 messages = logger.getLogs(); in TEST() 40 ASSERT_EQ(messages.size(), logSize); in TEST() [all …]
|
/openbmc/bmcweb/redfish-core/src/utils/ |
H A D | dbus_utils.cpp | 34 messages::insufficientPrivilege(asyncResp->res); in afterSetProperty() 38 messages::resourceNotFound(asyncResp->res, "Set", in afterSetProperty() 50 messages::propertyValueIncorrect( in afterSetProperty() 59 messages::serviceTemporarilyUnavailable(asyncResp->res, "10"); in afterSetProperty() 66 messages::serviceTemporarilyUnavailable(asyncResp->res, "10"); in afterSetProperty() 71 messages::propertyNotWritable(asyncResp->res, in afterSetProperty() 77 messages::resourceInStandby(asyncResp->res); in afterSetProperty() 83 messages::internalError(asyncResp->res); in afterSetProperty() 108 messages::operationFailed(asyncResp->res); in afterSetPropertyAction() 112 messages::actionParameterValueError(asyncResp->res, in afterSetPropertyAction() [all …]
|
/openbmc/phosphor-power/phosphor-regulators/test/ |
H A D | exception_utils_tests.cpp | 113 std::vector<std::string> messages = exception_utils::getMessages(e); in TEST() local 114 EXPECT_EQ(messages.size(), 2); in TEST() 115 EXPECT_EQ(messages[0], "JSON element is not an array"); in TEST() 116 EXPECT_EQ(messages[1], "Unable to parse config file"); in TEST() 250 std::vector<std::string> messages{}; in TEST() local 251 exception_utils::internal::getMessages(e, messages); in TEST() 252 EXPECT_EQ(messages.size(), 1); in TEST() 253 EXPECT_EQ(messages[0], "JSON element is not an array"); in TEST() 279 std::vector<std::string> messages{}; in TEST() local 280 exception_utils::internal::getMessages(e, messages); in TEST() [all …]
|
/openbmc/openpower-hw-diags/util/ |
H A D | ffdc.cpp | 54 * Gather messages from the journal 61 * @param max - Maximum number of messages fetch 68 std::vector<std::string> messages; in sdjGetMessages() local 102 // Store value to messages in sdjGetMessages() 104 messages.insert(messages.begin(), value); in sdjGetMessages() 108 // limit maximum number of messages in sdjGetMessages() 109 if (messages.size() >= max) in sdjGetMessages() 118 return messages; in sdjGetMessages() 161 * Create FDDC files from journal messages of relevant executables 179 // get journal messages in createFFDCTraceFiles() [all …]
|
/openbmc/linux/arch/arm/ |
H A D | Kconfig.debug | 97 bool "Verbose user fault messages" 132 bool "Kernel low-level debugging messages via Alpine UART0" 262 bool "Kernel low-level debugging messages via BCM KONA UART" 294 messages to appear over the UART, select this option. 297 bool "Kernel low-level debugging messages via UART1" 304 bool "Kernel low-level debugging messages via UART2" 327 bool "Kernel low-level debugging messages via footbridge serial port" 334 bool "Kernel low-level debugging messages via Digicolor UA0" 341 bool "Kernel low-level debugging messages via ep93xx UART" 349 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1" [all …]
|
/openbmc/bmcweb/redfish-core/lib/ |
H A D | update_service.hpp | 154 taskData->messages.emplace_back(messages::internalError()); in handleCreateTask() 169 taskData->messages.emplace_back(messages::taskAborted(index)); in handleCreateTask() 176 taskData->messages.emplace_back(messages::taskPaused(index)); in handleCreateTask() 189 taskData->messages.emplace_back(messages::taskCompletedOK(index)); in handleCreateTask() 204 taskData->messages.emplace_back(messages::internalError()); in handleCreateTask() 215 taskData->messages.emplace_back( in handleCreateTask() 216 messages::taskProgressChanged(index, *progress)); in handleCreateTask() 279 messages::internalError(asyncResp->res); in softwareInterfaceAdded() 291 messages::internalError(asyncResp->res); in softwareInterfaceAdded() 333 redfish::messages::internalError(asyncResp->res); in afterAvailbleTimerAsyncWait() [all …]
|
H A D | event_service.hpp | 149 messages::queryParameterOutOfRange( in requestRoutesEventService() 164 messages::queryParameterOutOfRange( in requestRoutesEventService() 214 messages::serviceDisabled(asyncResp->res, in requestRoutesSubmitTestEvent() 236 messages::internalError(asyncResp->res); in doSubscriptionCollection() 247 messages::internalError(asyncResp->res); in doSubscriptionCollection() 313 messages::eventSubscriptionLimitExceeded(asyncResp->res); in requestRoutesEventDestinationCollection() 359 messages::stringValueTooLong(asyncResp->res, "Destination", in requestRoutesEventDestinationCollection() 368 messages::propertyValueConflict( in requestRoutesEventDestinationCollection() 380 messages::propertyValueFormatError(asyncResp->res, destUrl, in requestRoutesEventDestinationCollection() 391 messages::propertyValueFormatError(asyncResp->res, destUrl, in requestRoutesEventDestinationCollection() [all …]
|
H A D | log_services.hpp | 232 messages::internalError(asyncResp->res); in parseDumpEntryFromDbusObject() 249 messages::internalError(asyncResp->res); in parseDumpEntryFromDbusObject() 267 messages::internalError(asyncResp->res); in parseDumpEntryFromDbusObject() 286 messages::internalError(asyncResp->res); in parseDumpEntryFromDbusObject() 298 messages::internalError(asyncResp->res); in parseDumpEntryFromDbusObject() 305 messages::internalError(asyncResp->res); in parseDumpEntryFromDbusObject() 353 messages::internalError(asyncResp->res); in getDumpEntryCollection() 366 messages::internalError(asyncResp->res); in getDumpEntryCollection() 469 messages::internalError(asyncResp->res); in getDumpEntryById() 482 messages::internalError(asyncResp->res); in getDumpEntryById() [all …]
|
H A D | manager_logservices_journal.hpp | 164 messages::resourceNotFound(asyncResp->res, "Manager", managerId); in handleManagersLogServiceJournalGet() 202 messages::internalError(asyncResp->res); in readJournalEntries() 235 messages::internalError(asyncResp->res); in readJournalEntries() 243 messages::internalError(asyncResp->res); in readJournalEntries() 272 messages::resourceNotFound(asyncResp->res, "Manager", managerId); in handleManagersJournalLogEntryCollectionGet() 298 messages::internalError(asyncResp->res); in handleManagersJournalLogEntryCollectionGet() 309 messages::internalError(asyncResp->res); in handleManagersJournalLogEntryCollectionGet() 316 messages::internalError(asyncResp->res); in handleManagersJournalLogEntryCollectionGet() 326 messages::internalError(asyncResp->res); in handleManagersJournalLogEntryCollectionGet() 335 messages::internalError(asyncResp->res); in handleManagersJournalLogEntryCollectionGet() [all …]
|
/openbmc/linux/Documentation/networking/ |
H A D | kcm.rst | 9 can efficiently send and receive application protocol messages over TCP using 45 The multiplexor provides the message steering. In the transmit path, messages 47 Similarly, in the receive path, messages are constructed on each TCP socket 48 (Psock) and complete messages are steered to a KCM socket. 55 messages on receive as well as other connection specific information for KCM. 63 can be used to send and receive messages from the KCM socket. 73 Messages are sent over a TCP stream with some application protocol message 74 format that typically includes a header which frames the messages. The length 102 socket. The BPF program may also enforce a maximum messages size and report an 105 A timeout may be set for assembling messages on a receive socket. The timeout [all …]
|
H A D | netif-msg.rst | 23 to shed the more verbose level messages as they matured. 25 - 0 Minimal messages, only essential information on fatal errors. 26 - 1 Standard messages, initialization status. No run-time messages 27 - 2 Special media selection messages, generally timer-driver. 28 - 3 Interface starts and stops, including normal status messages 29 - 4 Tx and Rx frame error messages, and abnormal driver operation 46 - More selective control over the type of messages emitted. 65 Messages should changes from::
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
H A D | uncore-interconnect.json | 550 "BriefDescription": "Messages sent direct to the Intel UPI", 1984 "BriefDescription": "CBox AD Credits Empty : VNA Messages", 1988 …"PublicDescription": "CBox AD Credits Empty : VNA Messages : No credits available to send to Cbox … 2181 …0 : REQ on AD : VN0 message requested but lost arbitration : Home (REQ) messages on AD. REQ is ge… 2190 …RSP on AD : VN0 message requested but lost arbitration : Response (RSP) messages on AD. RSP packe… 2199 …: SNP on AD : VN0 message requested but lost arbitration : Snoops (SNP) messages on AD. SNP is us… 2208 …0 message requested but lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is ge… 2217 … on BL : VN0 message requested but lost arbitration : Non-Coherent Standard (NCS) messages on BL.", 2226 …RSP on BL : VN0 message requested but lost arbitration : Response (RSP) messages on BL. RSP packet… 2235 …on BL : VN0 message requested but lost arbitration : Data Response (WB) messages on BL. WB is gen… [all …]
|
/openbmc/linux/Documentation/userspace-api/media/cec/ |
H A D | cec-ioc-g-mode.rst | 42 used to initiate messages, i.e. it commands other CEC devices. The 43 follower is the filehandle that receives messages sent to the CEC 60 The CEC framework will process core messages unless requested otherwise 62 case, the CEC framework will pass on most core messages without 63 processing them and the follower will have to implement those messages. 64 There are some messages that the core will always process, regardless of 88 - This is not an initiator, i.e. it cannot transmit CEC messages or 95 it can transmit CEC messages and make changes to the CEC adapter, 102 only one that can transmit CEC messages and make changes to the 129 - This is a follower and it will receive CEC messages unless there [all …]
|
/openbmc/linux/Documentation/virt/hyperv/ |
H A D | vmbus.rst | 56 for passing messages. Most synthetic devices use a single channel, 64 The "in" ring buffer is for messages from the Hyper-V host to the 65 guest, and the "out" ring buffer is for messages from the guest to 105 VMbus messages 107 All VMbus messages have a standard header that includes the message 112 Messages follow one of two patterns: 125 Messages passed between the VSP and VSC are control messages. For 133 ring buffer is minimal. For example, time sync messages from the 140 Three functions exist to send VMbus messages: 142 1. vmbus_sendpacket(): Control-only messages and messages with [all …]
|
/openbmc/bmcweb/redfish-core/include/registries/ |
H A D | openbmc_message_registry.readmefirst.md | 5 Messages in this registry are intended to be generally useful across OpenBMC 6 systems. To that end, there are a number of guidelines needed for messages in 9 1. Messages should not be specific to a piece or type of hardware. Generally 16 2. Messages should not use any proprietary, copyright, or company-specific 17 terms. In general, messages should prefer the industry accepted term. 24 4. Message registry versioning semantics shall be obeyed. Adding new messages 25 require an increment to the subminor revision. Changes to existing messages
|
/openbmc/docs/designs/mctp/ |
H A D | mctp-userspace.md | 21 complete MCTP messages. This daemon is responsible for the packetisation and 22 routing of MCTP messages from external endpoints, and handling the forwarding 23 these messages to and from individual handler applications. This includes 69 messages of a certain type, and would transmit MCTP messages of that same type. 98 MCTP messages should be forwarded to the client. Types must be greater than 101 Subsequent messages sent over the socket are MCTP messages sent/received by the 111 For messages coming from the demux daemon, this indicates the source EID of the 112 outgoing MCTP message. For messages going to the demux daemon, this indicates 125 for passing messages from the core code to application-level handlers. The 135 messages over dbus instead. The reason for the choice of sockets rather than
|
/openbmc/linux/drivers/staging/nvec/ |
H A D | nvec.h | 83 * @node: Messages are part of various lists in a &struct nvec_chip 85 * @size: For TX messages, the number of bytes used in @data 86 * @pos: For RX messages, the current position to write to. For TX messages, 90 * This structure is used to hold outgoing and incoming messages. Outgoing 91 * messages have a different format than incoming messages, and that is not 111 * @notifier_list: Notifiers to be called on received messages, see 113 * @rx_data: Received messages that have to be processed 114 * @tx_data: Messages waiting to be sent to the controller 120 * @msg_pool: A pool of messages for allocation 122 * @tx_scratch: Used for building pseudo messages
|
/openbmc/linux/include/trace/events/ |
H A D | iscsi.h | 19 * Declare event class for iscsi debug messages. 42 * Define event to capture iscsi connection debug messages. 51 * Define event to capture iscsi session debug messages. 60 * Define event to capture iscsi error handling debug messages. 69 * Define event to capture iscsi tcp debug messages. 78 * Define event to capture iscsi sw tcp debug messages. 87 * Define event to capture iscsi transport session debug messages. 96 * Define event to capture iscsi transport connection debug messages.
|
/openbmc/boost-dbus/include/dbus/detail/ |
H A D | queue.hpp | 27 std::deque<message_type> messages; member in dbus::detail::queue 34 : io(m.io), messages(m.messages), handlers(m.handlers) { in queue() 35 // TODO(ed) acquire the lock before copying messages and handlers in queue() 55 messages.push_back(m); in push() 76 if (messages.empty()) { in BOOST_ASIO_INITFN_RESULT_TYPE() 86 message_type m = messages.front(); in BOOST_ASIO_INITFN_RESULT_TYPE() 87 messages.pop_front(); in BOOST_ASIO_INITFN_RESULT_TYPE()
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | dev-kmsg | 8 Injecting messages: 20 is not possible to inject messages from userspace with the 22 the messages can always be reliably determined. 38 Messages in the record ring buffer get overwritten as whole, 39 there are never partial messages received by read(). 41 In case messages get overwritten in the circular buffer while 48 messages, in case the buffer gets overwritten. And they allow 64 or write only whole variable length messages (records) that are 113 interleaved with unrelated messages, but merging the lines in 115 similar logic is used internally when messages are printed to
|
/openbmc/bmcweb/redfish-core/include/ |
H A D | snmp_trap_event_clients.hpp | 33 messages::internalError(asyncResp->res); in afterGetSnmpTrapClientdata() 46 messages::internalError(asyncResp->res); in afterGetSnmpTrapClientdata() 92 messages::internalError(asyncResp->res); in getSnmpTrapClient() 103 messages::internalError(asyncResp->res); in getSnmpTrapClient() 116 messages::resourceNotFound(asyncResp->res, "Subscriptions", id); in getSnmpTrapClient() 138 messages::propertyValueIncorrect(asyncResp->res, "Destination", in afterSnmpClientCreate() 145 messages::propertyValueOutOfRange(asyncResp->res, "SNMPv2c", in afterSnmpClientCreate() 150 messages::internalError(asyncResp->res); in afterSnmpClientCreate() 157 messages::internalError(asyncResp->res); in afterSnmpClientCreate() 166 messages::created(asyncResp->res); in afterSnmpClientCreate() [all …]
|