Re: [CentOS] 7.2 kernel panic on boot
On 04/12/2015 12:03, Karanbir Singh wrote: On 03/12/15 16:47, Duncan Brown wrote: Did you rebuild initrd after removing the kmod packages? Yes, and no change is it possible to get a bug report at bugs.centos.org with as much detail as possible, so we can try to reproduce ( and atleast document and manage it that way ). thanks I'm seeing if I can get a decent copy of the kernel panic Would the bug report be much use without it? thanks ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 04/12/2015 19:17, Marcelo Ricardo Leitner wrote: Em 03-12-2015 14:46, Duncan Brown escreveu: Here is a couple of pictures, http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? Of some. It's failing on ftrace initialization while allocating memory, but can't know the real reason. It can be just lack of memory or any other bug. Probably by that stage of the boot, framebuffer is already loaded. Use vga=0x317 boot option to get a bigger resolution and more lines on it, then send another pic. I hope it fits this time. If not, pick 0x31A, if your monitor allows. (kernel src, Documentation/fb/vesafb.txt) | 640x480 800x600 1024x768 1280x1024 +- 256 | 0x3010x3030x3050x307 32k | 0x3100x3130x3160x319 64k | 0x3110x3140x3170x31A 16M | 0x3120x3150x3180x31B Marcelo ___ Hi Marcelo Thanks for the suggestion I've worked through a decent selection and cant get any to show a higher resolution than it's currently at, in fact most just leave me with a blank screen Note I can change the resolution all I want if I boot via the previous kernel cheers Duncan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
Em 03-12-2015 14:46, Duncan Brown escreveu: Here is a couple of pictures, http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png Any use? Of some. It's failing on ftrace initialization while allocating memory, but can't know the real reason. It can be just lack of memory or any other bug. Probably by that stage of the boot, framebuffer is already loaded. Use vga=0x317 boot option to get a bigger resolution and more lines on it, then send another pic. I hope it fits this time. If not, pick 0x31A, if your monitor allows. (kernel src, Documentation/fb/vesafb.txt) | 640x480 800x600 1024x768 1280x1024 +- 256 | 0x3010x3030x3050x307 32k | 0x3100x3130x3160x319 64k | 0x3110x3140x3170x31A 16M | 0x3120x3150x3180x31B Marcelo ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On Fri, Dec 04, 2015 at 12:06:14PM +, Karanbir Singh wrote: > i dont see it being dropped, on my completely updated machine i still > see the fully qualified numbering in /etc/centos-release ( as an example ) ? I know this is a big, confused thread, but the main complaint is that the website has dropped the fully qualified numbering: https://www.google.com/#q=%227.1.1503%27+site:centos.org vs https://www.google.com/#q=%227+1503%27+site:centos.org The first is "7.1.1503" and has 895 results, and they aren't html pages, they're things like directories containing that string. The second is strings like "7 (1503)", and has 1,700+ results, and they are the html pages. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 12/04/2015 08:02 AM, mark wrote: No, *you* don't understand what we're saying: pre-systemd, if the o/p saw that one stmt before the panic, they could look at what the system was doing *sequentially*, and so have an idea what it was failing on. With systemd's parallelism, we have no clue, other than what it's done, and no idea what's happening that's failing. It has never been true that a kernel panic was necessarily caused by the immediately preceding step in a sequential init. I ran into one instance (back in 4.x days, incidentally, where 'x' was 1 or 2) where a panic was caused by the tg3 driver, but it wasn't tickled until a variable number of packets passed the interface, and it didn't happen very often. Typically, when it happened it happened during ssh startup (almost every time it occurred, in fact). But the root cause was the tg3 driver module, not sshd. So having the last line before the panic being the ssh startup was actually a hindrance rather than a help in that case; I would have been looking for an sshd problem that didn't actually exist. I don't think that's an isolated instance, either. You need the module information from the panic more than information on what was started immediately prior to the panic. This was fixed without me having to file a bug report, incidentally, and so there is no BZ # to point you to that I recall, and a quick search of bugzilla doesn't show one for that particular issue that I had. I ended up seeing that it was a tg3 problem after setting up a serial console and grabbing the panic output from that. By the time I got to that point, the next update rollup for CentOS 4 was coming down, and that was the end of that problem. I keep thinking I'll track down the panic I saw a few months ago with CentOS 7 and gkrellm on my hardware, but by the time I get enough 'round toits' to do the troubleshooting the kernel has been updated, and I have to wait on the debuginfo.lather, rinse, repeat. Eventually I'll get my timing right and see what is (or maybe is not) happening. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firewalld zone conflict
On 04/12/15 15:01, James Hogarth wrote: >> In CentOS7 I have added two zones using firewall-cmd, each for >> different ports/services and interfaces when I try to --add-source to >> the second zone with an IP that is already in the first I am getting an >> 'Error: ZONE_CONFLICT' message. Am I trying to do something illogical or >> is this a feature? >> >> >> > By design a source network can only belong to a single zone... > > You'll have to create N zones to cover each network and add the service to > each... > > You may be interested in reading https://www.hogarthuk.com/?q=node/9 if > you are doing some firewalld stuff. OK thanks, I see the error of my reasoning now. Colin. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7.2 - no GUI login after upgrade
On Fri, 2015-12-04 at 09:41 +, John Hodrien wrote: > On Fri, 4 Dec 2015, Leon Fauster wrote: > > >> Any pointers on how to get the login screen? > > > > What about the gstreamer1 stuff, are all necessary > > libraries (linkage) in place? Especially for the EPEL > > stuff. > > You *need* to upgrade the gstreamer libraries or you break gnome (which breaks > gdm). Uninstall whatever is clashing from epel, upgrade gstreamer, all will > be well. > > There's a missing dependency there in the RPMs, but to be honest that's not at > all uncommon. I'd never recommend a partial update over a point release. > > jh > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos Thank Leon and John, Removed the gstreamer that was installed from epel repo and I used the packages that are from base and I am now able to login to the laptop. Thanks again guys. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firewalld zone conflict
On 4 December 2015 at 14:18, Colin Coles wrote: > Hi, > In CentOS7 I have added two zones using firewall-cmd, each for > different ports/services and interfaces when I try to --add-source to > the second zone with an IP that is already in the first I am getting an > 'Error: ZONE_CONFLICT' message. Am I trying to do something illogical or > is this a feature? > > > By design a source network can only belong to a single zone... You'll have to create N zones to cover each network and add the service to each... You may be interested in reading https://www.hogarthuk.com/?q=node/9 if you are doing some firewalld stuff. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Firewalld zone conflict
Hi, In CentOS7 I have added two zones using firewall-cmd, each for different ports/services and interfaces when I try to --add-source to the second zone with an IP that is already in the first I am getting an 'Error: ZONE_CONFLICT' message. Am I trying to do something illogical or is this a feature? Cheers, Colin. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On Thu, December 3, 2015 14:50, m.r...@5-cent.us wrote: > Valeri Galtsev wrote: . . . >> That is my main complaint about parallelized boot. My brain is >> only capable to deal with serial sequence of events, and which >> next event is deterministically predictable from previous. As >> with fatal things like kernel panic, it is the previous before >> the fatalstep is the one that you still can see... >> >> It there some way to tell systemd kick in components serially? >> >> Severs aside (you can not have everything), this (CentOS 7) is a >> great system for laptops, the best I saw so far. Like machintosh. >> Only better. > > For laptops, great. For anything else, not so much. For example, > it's supposed to be an *ENTERPRISE* o/s... why does it > automatically, without ever asking, install anything wifi? I'm > still trying to figure out how to tell a *wired* CentOS 7 > workstation to stop even thinking about wifi or wimax, and stop > cluttering the logs with debugging garbage. > The short answer: Because RHEL is based on Fedora development. The long answer: Because RH believes/believed that the laptop environment is/was a key part of its growth strategy. The recent phenomenon of the widespread adoption of smart phones and tablets in place of laptops may bring that into question now, but the move to laptops was a deliberate business choice in my opinion. It remains to be seen whether or not RH can have its cake and eat it too. Sysadmins tend to be rather prickly people when it comes to people and things that appear to waste their time. It seems to me a strategy of dubious worth aggravating ones installed based chasing a chimera. However that may be, the world moves on and we perforce move with it or are left behind. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On Fri, Dec 04, 2015 at 08:02:28AM -0500, mark wrote: > No, *you* don't understand what we're saying: pre-systemd, if the o/p saw > that one stmt before the panic, they could look at what the system was doing > *sequentially*, and so have an idea what it was failing on. With systemd's > parallelism, we have no clue, other than what it's done, and no idea what's > happening that's failing. Sadly, in this case, no init system would help with the fact that the kernel panic is more lines than are shown on a VGA screen. So, no help there. Also, while the systemd init system is loaded very early, judging from the call trace, it happened before or during the pivot from the initrd to the root filesystem. There's little that can be done to address this kind of panic, no matter what init system you're running, you basically just need to have a logging console somewhere. However, if you have a journald writing into memory, its very possible that if it doesn't panic enough to kill the journal you might have a copy of what *was* running. It's not the case here, but this is something that you get from having a journal -- you have real logs of what was happening, what processes were running and what emitted the error. With Upstart and SysVinit, you were stuck watching the output on the console and hoping whatever generated the error was good enough to say what program it was. Sure, you could make guesses based on the serial startup (although Upstart also supported parallel startup, although the CentOS init system rarely used it). For what its worth, you could always crank up systemd.log_level=debug on boot and you'll see what's going on when it panics. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 12/03/15 20:54, Jonathan Billings wrote: On Dec 3, 2015, at 2:33 PM, Valeri Galtsev wrote: That is my main complaint about parallelized boot. My brain is only capable to deal with serial sequence of events, and which next event is deterministically predictable from previous. As with fatal things like kernel panic, it is the previous before the fatalstep is the one that you still can see... This has nothing to do with systemd or a parallelized boot. The kernel panic is happening during the initial load of the kernel and initialization of hardware. I know you love to blame every problem on systemd, but c’mon, this problem is going to happen with *EVERY* init system. No, *you* don't understand what we're saying: pre-systemd, if the o/p saw that one stmt before the panic, they could look at what the system was doing *sequentially*, and so have an idea what it was failing on. With systemd's parallelism, we have no clue, other than what it's done, and no idea what's happening that's failing. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/15 13:58, Greg Bailey wrote: > Those who care about the upstream version knew that this was derived > from RHEL 7.0. Those who don't care about upstream versions but want to > track monthly rebuilds of cloud images, etc., could distinguish between > "1406" and (for example) "1407". But somewhere along the line for 7.1, > the "component that maps to the upstream release" was dropped, and we > got just 7 (1503). I don't recall seeing where or how that decision was > made; is there a link someone can provide to the relevant discussion in > centos-devel? i dont see it being dropped, on my completely updated machine i still see the fully qualified numbering in /etc/centos-release ( as an example ) ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2 kernel panic on boot
On 03/12/15 16:47, Duncan Brown wrote: >> Did you rebuild initrd after removing the kmod packages? >> > Yes, and no change is it possible to get a bug report at bugs.centos.org with as much detail as possible, so we can try to reproduce ( and atleast document and manage it that way ). thanks -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7.2 - no GUI login after upgrade
On Fri, 4 Dec 2015, Leon Fauster wrote: Any pointers on how to get the login screen? What about the gstreamer1 stuff, are all necessary libraries (linkage) in place? Especially for the EPEL stuff. You *need* to upgrade the gstreamer libraries or you break gnome (which breaks gdm). Uninstall whatever is clashing from epel, upgrade gstreamer, all will be well. There's a missing dependency there in the RPMs, but to be honest that's not at all uncommon. I'd never recommend a partial update over a point release. jh ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7.2 - no GUI login after upgrade
Am 04.12.2015 um 03:12 schrieb Earl A Ramirez : > After installing and enabling the centos-release-cr repo on my CentOS 7.1 > laptop; I ran yum clean all and yum update. Yum complained about gstreamer1 > dependencies that is caused by epel repo; therefore, I excluded it from the > epel repo and run yum update one more time and it went through. > > After the update was completed I rebooted the laptop and I will just get > the splash screen but will never get to the actual login screen; I have > experienced this in the past from CentOS 7.0 to 7.1 upgrade and at that > time it was caused by SELinux relabeling some of the configuration files; > e.g. /etc/passwd and /etc/shadow. This was discovered after I went into > single user mode and checked the journal. > > I booted in the previous successful kernel that loaded and I experienced > the same behavior; therefore I went into single user mode from the latest > kernel that came with CentOS 7.2 and the previous kernel, checked the > journal and there were no errors that give me a hint of what is going > wrong. There are no SELinux relabeling but I left the laptop on for a few > hours because I was modifying a few directories to accommodate docker and > KVM storage from the default setup. > > Any pointers on how to get the login screen? What about the gstreamer1 stuff, are all necessary libraries (linkage) in place? Especially for the EPEL stuff. -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
