LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-29-2013, 10:07 AM   #76
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,077

Rep: Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787

With:
Code:
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
and (the rebuilt) 3.2.45 kernel, all is well on Dell Optiplex 780 and Dell Inspiron 1750 if that matters.

[OOPS]
Forgot to include the Insipron 1750:
Code:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Writing this on that (obviously working fine).
[/OOPS]

Hope this helps some.

Last edited by tronayne; 05-29-2013 at 11:52 AM.
 
Old 05-29-2013, 11:24 AM   #77
PrinceCruise
Member
 
Registered: Aug 2009
Location: /Universe/Earth/India/Pune
Distribution: Slackware64 14.1/Current, CentOS 6.5/7.0
Posts: 773

Rep: Reputation: Disabled
Well I've got these specs :-
Quote:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Will try the second rebuild and see how does it go.

Thanks and regards.
 
Old 05-30-2013, 03:35 PM   #78
csking
LQ Newbie
 
Registered: May 2013
Posts: 3

Rep: Reputation: Disabled
Quote:
Originally Posted by volkerdi View Post
Is this with Intel graphics again?

I've been pointed to another suspicious commit and might be forced to do a third build. Giving much credit to whether a kernel series is designated LTS isn't looking like it matters as much as we may have thought. If 3.2.x had been dead, we'd have patched the CVE and had it right the first time.
I'm still seeing crashes with the second build, on an Intel DQ67SW with Core i7 2600 (HD 2000 Graphics) unless I append nomodeset.
 
Old 05-30-2013, 04:00 PM   #79
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 874

Rep: Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812Reputation: 1812
Quote:
Originally Posted by csking View Post
I'm still seeing crashes with the second build, on an Intel DQ67SW with Core i7 2600 (HD 2000 Graphics) unless I append nomodeset.
This might be the cause:

https://git.kernel.org/cgit/linux/ke...dc11b95adc339c

I'm considering doing a third build. If anyone who is running into problems still could revert this patch and rebuild to see if it fixes the issue, then I'd do it for sure. The only Intel graphics I have here are the trusty GM945, and there's no problem there.
 
3 members found this post helpful.
Old 05-30-2013, 05:11 PM   #80
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Well I have the following card:

Code:
# lspci -v -s $(lspci | awk '/VGA/{print $1}')
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Samsung Electronics Co Ltd Device c0b3
        Flags: bus master, fast devsel, latency 0, IRQ 49
        Memory at c0000000 (64-bit, non-prefetchable) [size=4M]
        Memory at b0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 3000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915
and I was having issues with X freezing when using 3.2.45 (both the first and the second package), prior to switching to the 3.8.13 kernel from -current. However to help out with confirmation I'll revert this patch and compile 3.2.45 locally and try again.

Might be a few hours delay in giving you a response though. It is almost midnight here and I need to get some sleep as I expect my 1 year old to wake me during the night (my wife is away so it is just me looking after the little one). Let's see how long it takes to compile. If it is quick I'll let you know soon. Otherwise in the morning my local time.

Last edited by ruario; 05-30-2013 at 05:16 PM. Reason: Clarified my wording
 
Old 05-30-2013, 05:43 PM   #81
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Ok, well I am done compiling (I actually started compilation some time before I submitted my previous message). I have now rebooted and am now using 3.2.45 with that patch reverted. So far so good. No hangs at all. It has only been a few minutes but then that is all it took previously before the issue showed up. It was very consistent.

I will leave the machine running overnight and have a look at it again tomorrow if you want a longer test. Anyway, thanks for the effort in tracking this down. Your hard work is very much appreciated (even though I am likely to go back to 3.8.13 when all is said and done. ).

Last edited by ruario; 05-30-2013 at 05:55 PM. Reason: s/ ery/ very/
 
1 members found this post helpful.
Old 05-30-2013, 07:45 PM   #82
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware{,-current}, FreeBSD
Posts: 198

Rep: Reputation: 106Reputation: 106
Quote:
Originally Posted by volkerdi View Post
I'm considering doing a third build. If anyone who is running into problems still could revert this patch and rebuild to see if it fixes the issue, then I'd do it for sure. The only Intel graphics I have here are the trusty GM945, and there's no problem there.
Same as ruario here. I reverted the patch, rebuilt the kernel, reinstalled modules, rebuilt initrd, run lilo. After rebooting I didn't have any issues so far, so you probably fixed it. I didn't use the patch command to revert, but I tracked the lines below in drivers/gpu/drm/i915/intel_ringbuffer.c and deleted them manually.

Code:
/* Required for the hardware to program scanline values for waiting */
if (INTEL_INFO(dev)->gen == 6)
I915_WRITE(GFX_MODE,
GFX_MODE_ENABLE(GFX_TLB_INVALIDATE_ALWAYS));
The hardware here is an H67 mini-ITX Intel board with Celeron G530 (HD 2000).

Code:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Intel Corporation Device 2000
	Flags: bus master, fast devsel, latency 0, IRQ 49
	Memory at fe000000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
Now I'll leave the machine running and see tomorrow if it's still fine as it seem to be now.

Thanks for following this thread, Patrick!

Best regards,
Philip

Last edited by Philip Lacroix; 05-30-2013 at 07:49 PM.
 
2 members found this post helpful.
Old 05-30-2013, 11:06 PM   #83
rpeter
LQ Newbie
 
Registered: Jan 2008
Location: Hungary
Distribution: Slackware
Posts: 7

Rep: Reputation: 0
Quote:
Originally Posted by ecoslacker View Post
Sometimes the graphical session in KDE gets frozen and sometimes I cannot enter to graphical session even, with the new rebuild 3.2.45 kernel.

Little help: How can I install back the old 3.2.29 kernel?

Thanks
I used the command upgradepkg oldpackage%newpackage, because I do not have much free space on hard drive, but I think that command installpkg may be appropriate as well. The modified packages were kernel-modules*, kernel-huge* and kernel-generic*.
If you use the generic kernel, then you should make a new mkinitrd and then use the command lilo, assuming you boot with lilo.
Interesting however, that slackpkg does not perceive the change.
 
Old 05-31-2013, 12:01 AM   #84
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Quote:
Originally Posted by ruario View Post
I will leave the machine running overnight and have a look at it again tomorrow if you want a longer test.
Still fine, reverting that patch has fixed the issue for me.
 
Old 05-31-2013, 12:02 AM   #85
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Quote:
Originally Posted by rpeter View Post
I used the command upgradepkg oldpackage%newpackage, because I do not have much free space on hard drive, but I think that command installpkg may be appropriate as well.
No need for oldpackage%newpackage in this case as the pkgtools will accept a downgrade without question (which is a feature, not a bug, I might add). And yep you can just installpkg new kernel packages, rather than upgradepkg allowing you to have both installed.

Quote:
Originally Posted by ecoslacker View Post
Little help: How can I install back the old 3.2.29 kernel?
If you are up to it try reverting the commit that volkerdi highlighted and build your own copy of the 3.2.45 kernel. Or wait, it seems likely that volkerdi will be issuing updated kernels.

If you can't (or won't) compile your own and cannot wait for a new kernel to be issued, then the 3.2.29 SMP kernel packages for Slackware 14.0 can be found here: kernel-generic-smp-3.2.29_smp-i686-1.txz, kernel-huge-smp-3.2.29_smp-i686-1.txz, kernel-modules-smp-3.2.29_smp-i686-1.txz, kernel-headers-3.2.29_smp-x86-1.txz and kernel-source-3.2.29_smp-noarch-1.txz.

If you have a 64-Bit install then the 3.2.29 kernel packages for Slackware64 14.0 can be found here: kernel-generic-3.2.29-x86_64-1.txz, kernel-huge-3.2.29-x86_64-1.txz, kernel-modules-3.2.29-x86_64-1.txz, kernel-headers-3.2.29-x86-1.txz and kernel-source-3.2.29-noarch-1.txz

Install them with either upgradepkg or installpkg. upgradepkg will replace the 3.2.45 kernel packages with these. installpkg will install them alongside.

Last edited by ruario; 05-31-2013 at 02:54 AM. Reason: Provided feedback to ecoslacker as well
 
Old 05-31-2013, 04:51 AM   #86
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware{,-current}, FreeBSD
Posts: 198

Rep: Reputation: 106Reputation: 106
Thumbs up

Quote:
Originally Posted by Philip Lacroix View Post
Now I'll leave the machine running and see tomorrow if it's still fine as it seem to be now.
It is, still running smoothly and without issues: reverting that patch fixed the problem for me too.
 
Old 05-31-2013, 08:35 AM   #87
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware{,-current}, FreeBSD
Posts: 198

Rep: Reputation: 106Reputation: 106
Linux 3.2.46 available, but...

Ok, Linux 3.2.46 is now available on kernel.org, however the patch doesn't revert the lines discussed above. I decided to try it anyway, so I updated the original 3.2.45 sources with today's 3.2.46 incremental patch, rebuilt the kernel, modules, initrd and so on, and the previous issues are here again. Just FYI

Philip

Last edited by Philip Lacroix; 05-31-2013 at 01:27 PM. Reason: Fixed link :)
 
Old 05-31-2013, 01:16 PM   #88
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Yeah the 3.2.46 ChangeLog makes no reference to either of the troublesome commits (e12a2d53ae45a69aea499b64f75e7222cca0f12f and 393143615d9f2f581d87387268dc11b95adc339c). Additionally a lot of new stuff has gone in, which considering the problems thus far could mean further regressions. If we are gonna get another kernel update, I'm pretty sure Pat is gonna stick with 3.2.45 and just revert that one further problematic fix. Taking 3.2.46 is not worth the risk.

Last edited by ruario; 05-31-2013 at 03:48 PM.
 
1 members found this post helpful.
Old 06-01-2013, 01:30 PM   #89
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Yet another thread on this issue.

Pat, there was also this thread (in case you missed it).

Last edited by ruario; 06-01-2013 at 01:35 PM. Reason: Added second sentence
 
Old 06-01-2013, 02:23 PM   #90
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,866

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
SalixOS uses the kernel's shipped by Slackware and also had a thread about CVE 2013-1763 - Linux Kernel local root exploit. One of the comments shows another user with this issue after the 3.2.45 kernel update:

Quote:
Originally Posted by laprjns
I upgraded to the new kernel on my Dell laptop with these specs:
Code:
root[rich]# inxi -C -G
CPU:       Dual core Intel Core i3-2330M CPU (-HT-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) 
           Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz 3: 800.00 MHz 4: 800.00 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller 
           X.org: 1.12.4 drivers: intel (unloaded: vesa) tty size: 133x38 Advanced Data: N/A for root
It booted into x and the desktop ok, but then completely locked up. I could move the mouse pointer, but no response to clicks or keyboard entries. I reverted back to the old kernel.
 
  


Reply

Tags
black screen, kernel, slackware 14, upgrade


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Laptop with via chrome9 slackware black screen on boot splintercdo Linux - Laptop and Netbook 14 02-05-2011 08:07 AM
Activated desktop effects in Ubuntu and resulted in black screen Mooney Linux - Newbie 1 05-23-2008 11:25 AM
PC failed to boot with a dark screen resulted satimis Linux - Hardware 9 05-16-2007 08:59 PM
Slackware 9.1 new kernel compile displays black screen on boot. Krenn Slackware 3 03-29-2004 02:33 PM
Black screen during boot up after new 2.6.1 kernel cjdock Slackware 17 02-01-2004 03:36 PM


All times are GMT -5. The time now is 11:41 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration