devel

devel@lists.centos.org

16 participants
4590 discussions

what uses the messages on mqtt.git.centos.org?
by Ken Dreyer 05 Jan '21

05 Jan '21

Hi folks, I was reading about the MQTT broker at mqtt.git.centos.org? (https://wiki.centos.org/Sources) Does anything in CentOS infrastructure consume those messages (for example, to automatically build packages in Koji based on Pagure pushes)? I was also wondering about https://github.com/CentOS/ansible-role-kojihub/commits/master/files/plugins… , does any other tool consume those messages? - Ken

4 3

Re: [CentOS-devel] Vote of Confidence
by Mark Mielke 04 Jan '21

04 Jan '21

On Sat, Jan 2, 2021 at 8:50 AM orkcu via CentOS-devel <centos-devel(a)centos.org> wrote: > I don't think CentOS (or any other clone/rebuild) was ever a Bazaar, it can not be if the goal is to be a good clone/rebuild. > Since the very beginning the control was in a handful of people, very tight, and I remember one crisis when the founder didn't want (was unable/unavailable) to release control of dns domain, sign keys and few other main components that now you complain RedHat don't want to release I think you are right. The original intent, and the announcements and documentation for the project suggested something greater, but the reality turned out to be difficulty in delegation and scale. This is a common problem for volunteer or non-profit organizations. It doesn't matter if you have 3000 people willing to work on your project for free, if you can't effectively assign them work to do. It's worse if you can't even scale beyond a small number like "3", as these 3 eventually move on, and there is no succession plan, resulting in the project failing. For many of us - I think we had a naive trust that this would be figured out, and we would be invited when the time came to invite us. However, it didn't happen, and in 2014, Red Hat offered to take the reins. It's not that Red Hat set out to destroy the community - it is only that Red Hat has a conflict of interest, and it is really difficult for this conflict of interest to not eventually result in favouring certain self-interest outcomes over other non self-interest outcomes, and this is exactly what is happening in 2021. In effect, it was an inevitable conclusion. It was even predicted by several people in 2014. A similar thing is playing out in Rocky right now, however, there is a great deal of accumulated know-how, access to resources, and sober reflection on what went wrong leading up to 2014 and 2020. 3000+ people willing to work for free, but probably only 70 will be able to directly contribute, and initially the number will be a lot fewer as the initial setup takes place. This is why I say that Rocky is what CentOS should have been in 2014. We all know it wasn't. Now there is a chance to fix this. It could be a very good thing. > I don't like CentOS to evolve to Stream, I agree there is a need of a cheap RHEL's quality distribution, and I think all the arguments given so far at the end (in the very bottom) it is about cost (money), from the people complaining about the end because we are losing a very good distro that was free/gratis, from RedHat it is about moving the money to a direction that might provide better benefits for the company. > If RedHat would offer its RHEL with a minimum price (20? 50? 100?) for self support and then charge for a ticket a good amount of money ( like 200? 500?), that might work for a lot of people who are complaining now, I think we all understand that everyone need to have an income to feed its needs, even the small shops that are trying to save in (software) costs as much as possible. If Red Hat had agreed to this in 2016 and 2017 when I was asking for a reasonable solution to our problem, the company I work for would still be a Red Hat only shop. This was an opportunity missed then, and I believe it will be an opportunity missed when the new plans are announced. I don't believe the new subscription plans will be enough to make them an attractive option, and after the stumble with CentOS, even a good subscription plan that might meet some use cases will be frowned upon as a result of this debacle. > Bottom line, I don't think we ever had a community built OS in CentOS, we had people of the community assisting in testing and QA, but not even that was open to the public. I might be wrong but I think even before 2014 we had builders that were not (much) active in mailing list or IRC, and that is OK, each person have different strengths. I don't think you are wrong. Healthy communities need to prioritize delegation and scalability. It means investing specific effort in ensuring that people of different skills and capabilities can successfully contribute to the project. -- Mark Mielke <mark.mielke(a)gmail.com>

7 9

Package AppStreams variants in CentOS Stream?
by Leon Fauster 04 Jan '21

04 Jan '21

Hey, corresponding to CentOS 8 Stream: will ALL package/module versions for the different AppStreams be available? Some appstreams are only available as latest version (maven, nginx, perl, php). Wish you all some nice and healthy Christmas days, Leon

3 4

Vote of Confidence
by redbaronbrowser 03 Jan '21

03 Jan '21

This is an *UNOFFICIAL* non-binding vote to help provide an assessment of the state of the CentOS community and provoke further discussion. On November 11th (7 weeks ago), the CentOS governance board voted to reduce the life span of CentOS 8 from 10 years to 2 years. One board member, Karsten Wade, this is part of Red Hat effort to close the openness gap. He also explained that there is an elephant of which the community has only been shown parts with a flashlight. The CentOS governance page describe the governing board as being like a greenhouse. Why is the greenhouse so darken that it can hide an elephant such that over the last 7 weeks it has never been fully shown in the brightness of day? Part of the problem is the governance board is packed with people that are not active members of the CentOS community and have made no effort to explain the board's actions to the community. Please vote on each of the following items with +1 (in favor), 0 (sustain), -1 (reject). If you vote to reject an item, please explain why. Should Brian Exelbierd be asked to resign from the CentOS governance board? Should Mike McLean be asked to resign from the CentOS governance board? Should Carl Trieloff be asked to resign from the CentOS governance board? Should Rich Bowen be asked to resign from the CentOS governance board? Is obfuscating the CentOS kernel patches consistent with Red Hat attempting to close the openness gap? Are you likely to ever assist with Stream if the CentOS 8 End of Life is December 31, 2021? Would you be more likely to help with Stream if the CentOS 8 End of Life was set to June 30, 2024? Please keep in mind this vote is *UNOFFICIAL* and only for the purpose of promoting discussion. Template for responding: BE resign: [+1|0|-1] [-1 reason] MM resign: [+1|0|-1] [-1 reason] CT resign: [+1|0|-1] [-1 reason] RB resign: [+1|0|-1] [-1 reason] Obfuscation = Openness: [+1|0|-1] [-1 reason] EOL 2021: [+1|0|-1] [-1 reason] EOL 2024: [+1|0|-1] [-1 reason]

7 10

rare but repeating system crash in C7
by Fred 02 Jan '21

02 Jan '21

Hi all, I'm hoping someone can help me figure this out. every now and then (less than monthly, maybe every 2-4 months, or so, I'll walk up to my C7 box (my home PC) in the morning, wiggle the mouse to wake up the screen, and after a second or so, instead of a live screen, the keyboard shift-lock and scroll-lock keys light up. if I wait a few (tens of) second(s) I find it is rebooting, as the BIOS splash screen appears. it boots normally and comes up with everything apparently working fine. Note that I tend to leave myself logged in 24/7/365 since there's nobody here except my wife and myself, and she has her own Linux box. as it happened again this morning, I grabbed some lines from /var/log/messages that show the last few minutes before it rebooted and the first 3 or four statements as it began to reboot: Jan 2 08:50:12 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cb10 trb-start 00000000a9f2cb20 trb-end 00000000a9f2cb20 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:50:13 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:50:13 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164858d0 trb-start 00000000164858e0 trb-end 00000000164858e0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 08:51:12 fcshome dbus[1192]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jan 2 08:51:13 fcshome dbus[1192]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jan 2 08:51:14 fcshome setroubleshoot: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run: sealert -l e4620dcc-6cdc-460d-a8a4-db9ce9624646 Jan 2 08:51:14 fcshome python: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that smbd should be allowed read access on the cups.sock sock_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd#012# semodule -i my-lpqd.pp#012 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485d20 trb-start 0000000016485d30 trb-end 0000000016485d30 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cae0 trb-start 00000000a9f2caf0 trb-end 00000000a9f2caf0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:58:00 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:58:00 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c530 trb-start 00000000a9f2c540 trb-end 00000000a9f2c540 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c340 trb-start 00000000a9f2c350 trb-end 00000000a9f2c350 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cfb0 trb-start 00000000a9f2cfc0 trb-end 00000000a9f2cfc0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:00:02 fcshome systemd: Created slice User Slice of root. Jan 2 09:00:02 fcshome systemd: Started Session 7364 of user root. Jan 2 09:00:02 fcshome systemd: Removed slice User Slice of root. Jan 2 09:00:06 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:06 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cd20 trb-start 00000000a9f2cd30 trb-end 00000000a9f2cd30 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485400 trb-start 0000000016485410 trb-end 0000000016485410 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbc0 trb-start 00000000a9f2cbd0 trb-end 00000000a9f2cbd0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485c00 trb-start 0000000016485c10 trb-end 0000000016485c10 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:01:01 fcshome systemd: Created slice User Slice of root. Jan 2 09:01:01 fcshome systemd: Started Session 7365 of user root. Jan 2 09:01:01 fcshome systemd: Removed slice User Slice of root. Jan 2 09:03:45 fcshome dbus[1192]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jan 2 09:03:46 fcshome dbus[1192]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jan 2 09:03:47 fcshome setroubleshoot: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run: sealert -l e4620dcc-6cdc-460d-a8a4-db9ce9624646 Jan 2 09:03:47 fcshome python: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that smbd should be allowed read access on the cups.sock sock_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd#012# semodule -i my-lpqd.pp#012 Jan 2 09:04:31 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:31 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2ca60 trb-start 00000000a9f2ca70 trb-end 00000000a9f2ca70 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:04:58 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:58 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cd70 trb-start 00000000a9f2cd80 trb-end 00000000a9f2cd80 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b30 trb-start 0000000016485b40 trb-end 0000000016485b40 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164856c0 trb-start 00000000164856d0 trb-end 00000000164856d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:05:03 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:05:03 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164851b0 trb-start 00000000164851c0 trb-end 00000000164851c0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:10:01 fcshome systemd: Created slice User Slice of root. Jan 2 09:10:01 fcshome systemd: Started Session 7366 of user root. Jan 2 09:10:01 fcshome systemd: Removed slice User Slice of root. Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164854c0 trb-start 00000000164854d0 trb-end 00000000164854d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485eb0 trb-start 0000000016485ec0 trb-end 0000000016485ec0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164852c0 trb-start 00000000164852d0 trb-end 00000000164852d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b70 trb-start 0000000016485b80 trb-end 0000000016485b80 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbb0 trb-start 00000000a9f2cbc0 trb-end 00000000a9f2cbc0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164858d0 trb-start 00000000164858e0 trb-end 00000000164858e0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485a00 trb-start 0000000016485a10 trb-end 0000000016485a10 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:14:46 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:14:46 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485450 trb-start 0000000016485460 trb-end 0000000016485460 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c170 trb-start 00000000a9f2c180 trb-end 00000000a9f2c180 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c7a0 trb-start 00000000a9f2c7b0 trb-end 00000000a9f2c7b0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:10 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:10 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485560 trb-start 0000000016485570 trb-end 0000000016485570 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b90 trb-start 0000000016485ba0 trb-end 0000000016485ba0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cf90 trb-start 00000000a9f2cfa0 trb-end 00000000a9f2cfa0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c9e0 trb-start 00000000a9f2c9f0 trb-end 00000000a9f2c9f0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485660 trb-start 0000000016485670 trb-end 0000000016485670 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:23 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:23 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485330 trb-start 0000000016485340 trb-end 0000000016485340 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:24 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:24 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485500 trb-start 0000000016485510 trb-end 0000000016485510 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c400 trb-start 00000000a9f2c410 trb-end 00000000a9f2c410 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164851c0 trb-start 00000000164851d0 trb-end 00000000164851d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485e30 trb-start 0000000016485e40 trb-end 0000000016485e40 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbf0 trb-start 00000000a9f2cc00 trb-end 00000000a9f2cc00 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c000 trb-start 00000000a9f2c010 trb-end 00000000a9f2c010 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:27 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:27 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2ce50 trb-start 00000000a9f2ce60 trb-end 00000000a9f2ce60 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:31 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:31 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c4e0 trb-start 00000000a9f2c4f0 trb-end 00000000a9f2c4f0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:47 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:47 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbb0 trb-start 00000000a9f2cbc0 trb-end 00000000a9f2cbc0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:16:15 fcshome dbus[1192]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jan 2 09:16:16 fcshome dbus[1192]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jan 2 09:16:17 fcshome setroubleshoot: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run: sealert -l e4620dcc-6cdc-460d-a8a4-db9ce9624646 Jan 2 09:16:17 fcshome python: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that smbd should be allowed read access on the cups.sock sock_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd#012# semodule -i my-lpqd.pp#012 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b50 trb-start 0000000016485b60 trb-end 0000000016485b60 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c050 trb-start 00000000a9f2c060 trb-end 00000000a9f2c060 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c680 trb-start 00000000a9f2c690 trb-end 00000000a9f2c690 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cb70 trb-start 00000000a9f2cb80 trb-end 00000000a9f2cb80 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c520 trb-start 00000000a9f2c530 trb-end 00000000a9f2c530 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2ca10 trb-start 00000000a9f2ca20 trb-end 00000000a9f2ca20 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:20:11 fcshome kernel: Initializing cgroup subsys cpuset Jan 2 09:20:11 fcshome kernel: Initializing cgroup subsys cpu Jan 2 09:20:11 fcshome kernel: Initializing cgroup subsys cpuacct Jan 2 09:20:11 fcshome kernel: Linux version 3.10.0-1160.6.1.el7.x86_64 The last four events are the start of reboot and everything above is leading up to the crash. I note that there was a selinux event early in this list of events, but I see those frequently and they normally don't cause a crash. if I scroll upward from this list, I find more of the same above what is shown here. The selinux event seems to be related to a SMB mount. since I have a Synology box on the LAN, and it stays mounted nearly all the time, I suspect the selinux event has something to do with that, but I have no idea why it would cause a crash once every few months. Is that selinux event something I need to fix? I'm further guessing that "xhci_hcd" has something to do with USB, am I right? If so I don't know what it would be... Clues would be greatly appreciated! Thanks in advance! Fred

1 0

Balancing the needs around the CentOS platform
by Karsten Wade 31 Dec '20

31 Dec '20

I wrote a blog post to share with you: https://blog.centos.org/2020/12/balancing-the-needs-around-the-centos-platf… Below is a fair summary of the blog post, but I encourage you to read the whole thing for the context around the "availability gap" and the "openness gap": Summary ======= Letting an outsider take care of the availability gap after the RHL to Fedora/RHEL split meant there was no vehicle for closing the openness gap. Red Hat needed to create or bring-in a solution that was highly available (easy to get) in order to close the gap around openness (easy to contribute to). That was the joining forces with CentOS. And now we think we have something that can cover both the availability and openness gaps, please try it out. All along Red Has been making a Linux OS that we want to be open, to be available, to be stable enough, and to be sustainable. And now we think we have the next evolution in that decades of work, in the form of CentOS Stream. ======= Kind regards, - Karsten -- Karsten Wade [he/him/his]| Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://osci.io https://theopensourceway.org | https://github.com/theopensourceway/guide

19 83

Centos Stream - src.rpms?
by Antal Nemeš 29 Dec '20

29 Dec '20

Hi, Will src.rpm packages be made available for Stream repositories? Currently, I see only empty subdirs for 8-stream at https://vault.centos.org/centos/8-stream/ Regards, Antal

6 9

Before You Get Mad About The CentOS Stream Change, Think About…
by Daniel Comnea 28 Dec '20

28 Dec '20

Hi folks, I am not planning to pour gas over fire, a lot of traffic was generated due to the recent announcement however i thought i should circulate an article [1] i've bumped into today. Please note, i'm not an RH employee nor i know the article's author, i'm just a consumer of CentOS and someone who did a bit of work on PaaS sig for OpenShift in my spare time with no employer sponsorship. As the Xmas time is approaching it would be good to take a step back and analyse from a different perspective what RH did and still does (look at OKD 4.x and the mighty effort did by few passionate RH employees) before throwing rocks. (humanity is very good at judging and snapping in a blink of an eye). Thanks [1] http://crunchtools.com/before-you-get-mad-about-the-centos-stream-change-th…

40 144

What should I do in my cluster? CentOS streams dilemma.
by Pablo Sanz Mercado 27 Dec '20

27 Dec '20

I have been reading a lot about the new CentOS stream "revolution", but now I am trying to understand the dilemma most of "regular" sysadmin have: What should I do? As you know there are a lot of computational centers working with CentOS. Sometimes because it is the best OS sysadmin knows, sometimes because of a low budget problem. Now we have this important change, so we have to decide. We have to choose the OS we are going to install in our servers, moreover we have to decide as quickly as we can, because as you know changes should be done as calm as posible. Could we list pros/cons about using CentOS stream in a computational Center? Are we going to see CentOS stream in the top500 list? Best regards, Pablo Sanz -- Pablo Sanz Mercado Director Técnico Centro de Computación Científica Universidad Autónoma de Madrid

9 23

Re: [CentOS-devel] Before You Get Mad About The CentOS Stream Change, Think About…
by Strahil Nikolov 25 Dec '20

25 Dec '20

В 17:56 +0100 на 23.12.2020 (ср), Daniel Berteaud написа: > ----- Le 23 Déc 20, à 13:24, Mike McGrath <mmcgrath(a)redhat.com> a > écrit : > > > > Hey Mike, > > > > > > Is there a chance to prolong the Stream's life any further ? > > > Maybe with a SIG ? > > > I think that if stream's life was a little bit longer , Stream > > > could have a better adoption . > > > > > > Best Regards, > > > Strahil Nikolov > > > > Low chance but not impossible. We just shook things up and the > > results of that shakeup are a little unclear. The question for a > > longer lifecycle on stream will depend entirely on why one of the > > soon-to-be announced RHEL programs won't work for you. So that's a > > discussion for another time. > > That's the only thing which might prevent me from switching to CentOS > Stream. 5 year is quite shorter than the previous CentOS Linux, and > only two years of overlap between two major versions isn't enough in > a lot of cases. > > Cheers, > Daniel For me it's only 2 1/2 years ... the first 2-3 releases are really unusable and very unstable even on RHEL... Best Regards, Strahil Nikolov

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel