Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #162000 > unrolled thread

random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

Started byStaszek <stf.list.other@eisenbits.com>
First post2015-12-22 21:40 +0100
Last post2015-12-24 15:50 +0100
Articles 12 — 6 participants

Back to article view | Back to linux.debian.user

Contents

  random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel  stack trace) Staszek <stf.list.other@eisenbits.com> - 2015-12-22 21:40 +0100
    Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Anders Andersson <pipatron@gmail.com> - 2015-12-22 22:20 +0100
      Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Staszek <stf.list.other@eisenbits.com> - 2015-12-24 14:10 +0100
        Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Neil Roberts <neilr@matrixscience.com> - 2015-12-24 15:00 +0100
        Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Sven Arvidsson <sa@whiz.se> - 2015-12-24 15:10 +0100
          Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Anders Andersson <pipatron@gmail.com> - 2015-12-24 20:30 +0100
          Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Staszek <stf.list.other@eisenbits.com> - 2015-12-25 03:30 +0100
            Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Charlie Kravetz <cjk@teamcharliesangels.com> - 2015-12-25 04:10 +0100
            Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Sven Arvidsson <sa@whiz.se> - 2015-12-25 15:50 +0100
              Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Staszek <stf.list.other@eisenbits.com> - 2016-01-01 00:40 +0100
            Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Patrick Bartek <nemommxiv@gmail.com> - 2015-12-25 19:40 +0100
        Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1)  (kernel stack trace) Charlie Kravetz <cjk@teamcharliesangels.com> - 2015-12-24 15:50 +0100

#162000 — random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromStaszek <stf.list.other@eisenbits.com>
Date2015-12-22 21:40 +0100
Subjectrandom reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qIBSV-e4-3@gated-at.bofh.it>
Hi!

My old Lenovo ThinkPad T61 laptop reboots by itself from time to time.
Usually without a clue, but this time I was able to capture the stack
trace:
http://people.eisenbits.com/~stf/load/20151222-kernel-stack-trace.png .

How to debug it? I've installed linux-image-3.16.0-4-amd64-dbg package:
https://packages.debian.org/jessie/linux-image-3.16.0-4-amd64 , now is
/usr/lib/debug/vmlinux-3.16.0-4-amd64 the vmlinux file matching my
kernel version? What does "ckt20" stand for?
For now I just wanted to follow the stack trace, eg. with addr2line.
Sometimes it prints out some source code address but usually just
"??:0". Why?

Perhaps this is a hardware error, but where? Is this the graphic card?
Or the south bridge maybe?
Is this patchable?

Thanks!

This is the latest Debian Jessie.

-- 
http://people.eisenbits.com/~stf/
http://www.eisenbits.com/

OpenPGP: 9EC2 5620 2355 B1DC 4A8F  8C79 0EC7 C214 E5AE 3B4E

[toc] | [next] | [standalone]

#162002 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromAnders Andersson <pipatron@gmail.com>
Date2015-12-22 22:20 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qICvD-GS-7@gated-at.bofh.it>
In reply to#162000
On Tue, Dec 22, 2015 at 9:27 PM, Staszek <stf.list.other@eisenbits.com> wrote:
> Hi!
>
> My old Lenovo ThinkPad T61 laptop reboots by itself from time to time.
> Usually without a clue, but this time I was able to capture the stack
> trace:
> http://people.eisenbits.com/~stf/load/20151222-kernel-stack-trace.png .
>
> How to debug it? I've installed linux-image-3.16.0-4-amd64-dbg package:
> https://packages.debian.org/jessie/linux-image-3.16.0-4-amd64 , now is
> /usr/lib/debug/vmlinux-3.16.0-4-amd64 the vmlinux file matching my
> kernel version? What does "ckt20" stand for?
> For now I just wanted to follow the stack trace, eg. with addr2line.
> Sometimes it prints out some source code address but usually just
> "??:0". Why?
>
> Perhaps this is a hardware error, but where? Is this the graphic card?
> Or the south bridge maybe?
> Is this patchable?

First thing I do in a case like this is to run memtest86 in some form
on the hardware.

[toc] | [prev] | [next] | [standalone]

#162090 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromStaszek <stf.list.other@eisenbits.com>
Date2015-12-24 14:10 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJdOx-76Q-11@gated-at.bofh.it>
In reply to#162002
On 2015-12-22 22:18, Anders Andersson wrote:
> First thing I do in a case like this is to run memtest86 in some form
> on the hardware.

Good point, but:

1. those stack traces are always nouveau related
2. memtest86+ yields nothing
3. often upon logging into X, before the desktop appears, I am getting
unexpected splash screens; they look like:
http://people.eisenbits.com/~stf/load/20151224-bw-tiling.png , or
sometimes that is a mangled view of what was being displayed before the
crash+reboot.

Perhaps that is a graphics card...

-- 
http://people.eisenbits.com/~stf/
http://www.eisenbits.com/

OpenPGP: 9EC2 5620 2355 B1DC 4A8F  8C79 0EC7 C214 E5AE 3B4E

[toc] | [prev] | [next] | [standalone]

#162091 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromNeil Roberts <neilr@matrixscience.com>
Date2015-12-24 15:00 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJeAW-7mT-19@gated-at.bofh.it>
In reply to#162090
> On 2015-12-22 22:18, Anders Andersson wrote:
>> First thing I do in a case like this is to run memtest86 in some form
>> on the hardware.
> Good point, but:
>
> 1. those stack traces are always nouveau related
> 2. memtest86+ yields nothing
> 3. often upon logging into X, before the desktop appears, I am getting
> unexpected splash screens; they look like:
> http://people.eisenbits.com/~stf/load/20151224-bw-tiling.png , or
> sometimes that is a mangled view of what was being displayed before the
> crash+reboot.
>
> Perhaps that is a graphics card...
>
I had a similar problem on a T520. If you have two graphics cards (ie, 
Intel Optimus)
It will cause crashes when the graphics swaps between the devices.
I resolved it by disabling one of the graphics cards in the bios.

[toc] | [prev] | [next] | [standalone]

#162092 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromSven Arvidsson <sa@whiz.se>
Date2015-12-24 15:10 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJeKB-7HG-7@gated-at.bofh.it>
In reply to#162090

[Multipart message — attachments visible in raw view] — view raw

On Thu, 2015-12-24 at 14:00 +0100, Staszek wrote:
> Perhaps that is a graphics card...

Try disabling nouveau, both in the kernel and the xorg driver, and see
if the crashes stop. 

You might also want to try a later kernel/xorg driver/mesa etc. But
that might open up another can of worms.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5

[toc] | [prev] | [next] | [standalone]

#162097 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromAnders Andersson <pipatron@gmail.com>
Date2015-12-24 20:30 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJjKh-2gc-5@gated-at.bofh.it>
In reply to#162092
On Thu, Dec 24, 2015 at 3:07 PM, Sven Arvidsson <sa@whiz.se> wrote:
> On Thu, 2015-12-24 at 14:00 +0100, Staszek wrote:
>> Perhaps that is a graphics card...
>
> Try disabling nouveau, both in the kernel and the xorg driver, and see
> if the crashes stop.
>
> You might also want to try a later kernel/xorg driver/mesa etc. But
> that might open up another can of worms.

I'm using "the latest" nouveau on Debian Testing. It's horribly
unstable, and been so for the last year. YMMV. :)

[toc] | [prev] | [next] | [standalone]

#162098 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromStaszek <stf.list.other@eisenbits.com>
Date2015-12-25 03:30 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJqiJ-682-5@gated-at.bofh.it>
In reply to#162092
On 2015-12-24 15:07, Sven Arvidsson wrote:
> Try disabling nouveau, both in the kernel and the xorg driver, and see
> if the crashes stop.

Ok, but what other driver shall I use instead?

According to ThinkPad Wiki nv driver works:
http://www.thinkwiki.org/wiki/NVIDIA_Quadro_NVS_140M . Unfortunately it
is not present in Jessie:
https://packages.debian.org/search?keywords=xserver-xorg-video-nv ??...

My graphics card:

# lcpci -vv
[...]
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [Quadro NVS
140M] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Lenovo ThinkPad T61
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 49
	Region 0: Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
	Region 5: I/O ports at 2000 [size=128]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee0300c  Data: 4192
	Capabilities: [78] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency
L0s <512ns, L1 <4us
			ClockPM- Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive-
BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Capabilities: [128 v1] Power Budgeting <?>
	Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1
Len=024 <?>
	Kernel driver in use: nouveau

Shall I compile nv driver from source and install it manually?

-- 
http://people.eisenbits.com/~stf/
http://www.eisenbits.com/

OpenPGP: 9EC2 5620 2355 B1DC 4A8F  8C79 0EC7 C214 E5AE 3B4E

[toc] | [prev] | [next] | [standalone]

#162099 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromCharlie Kravetz <cjk@teamcharliesangels.com>
Date2015-12-25 04:10 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJqVr-6zZ-3@gated-at.bofh.it>
In reply to#162098
On Fri, 25 Dec 2015 03:16:21 +0100
Staszek <stf.list.other@eisenbits.com> wrote:

>On 2015-12-24 15:07, Sven Arvidsson wrote:
>> Try disabling nouveau, both in the kernel and the xorg driver, and see
>> if the crashes stop.
>
>Ok, but what other driver shall I use instead?
>
>According to ThinkPad Wiki nv driver works:
>http://www.thinkwiki.org/wiki/NVIDIA_Quadro_NVS_140M . Unfortunately it
>is not present in Jessie:
>https://packages.debian.org/search?keywords=xserver-xorg-video-nv ??...
>
>My graphics card:
>
># lcpci -vv
>[...]
>01:00.0 VGA compatible controller: NVIDIA Corporation G86M [Quadro NVS
>140M] (rev a1) (prog-if 00 [VGA controller])
>	Subsystem: Lenovo ThinkPad T61
>	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Stepping- SERR+ FastB2B- DisINTx+
>	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
><MAbort- >SERR- <PERR- INTx-
>	Latency: 0, Cache Line Size: 64 bytes
>	Interrupt: pin A routed to IRQ 49
>	Region 0: Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
>	Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
>	Region 3: Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
>	Region 5: I/O ports at 2000 [size=128]
>	Expansion ROM at <unassigned> [disabled]
>	Capabilities: [60] Power Management version 2
>		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
>		Address: 00000000fee0300c  Data: 4192
>	Capabilities: [78] Express (v1) Endpoint, MSI 00
>		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us
>			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
>			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
>			MaxPayload 128 bytes, MaxReadReq 512 bytes
>		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
>		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency
>L0s <512ns, L1 <4us
>			ClockPM- Surprise- LLActRep- BwNot-
>		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- CommClk+
>			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive-
>BWMgmt- ABWMgmt-
>	Capabilities: [100 v1] Virtual Channel
>		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
>		Arb:	Fixed- WRR32- WRR64- WRR128-
>		Ctrl:	ArbSelect=Fixed
>		Status:	InProgress-
>		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
>			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
>			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
>			Status:	NegoPending- InProgress-
>	Capabilities: [128 v1] Power Budgeting <?>
>	Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1
>Len=024 <?>
>	Kernel driver in use: nouveau
>
>Shall I compile nv driver from source and install it manually?
>


I have a Lenovo T520 here, with dual graphics. I found Nouveau did not
work very good for me. I run dual monitors, so I had to make Optimus
work. The best guide I found is
http://www.unixmen.com/how-to-make-nvidia-optimus-technology-work-properly-on-debian/

It makes the setup easy.


-- 
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM.   [http://keepingdreams.com]

[toc] | [prev] | [next] | [standalone]

#162105 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromSven Arvidsson <sa@whiz.se>
Date2015-12-25 15:50 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJBQS-4Ks-1@gated-at.bofh.it>
In reply to#162098

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2015-12-25 at 03:16 +0100, Staszek wrote:
> On 2015-12-24 15:07, Sven Arvidsson wrote:
> > Try disabling nouveau, both in the kernel and the xorg driver, and
> > see
> > if the crashes stop.
> 
> Ok, but what other driver shall I use instead?

The vesa driver would probably be easiest to get up and running. 

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5

[toc] | [prev] | [next] | [standalone]

#162413 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromStaszek <stf.list.other@eisenbits.com>
Date2016-01-01 00:40 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qLUZ4-2rH-7@gated-at.bofh.it>
In reply to#162105
On 2015-12-25 15:42, Sven Arvidsson wrote:
> On Fri, 2015-12-25 at 03:16 +0100, Staszek wrote:
>> On 2015-12-24 15:07, Sven Arvidsson wrote:
>>> Try disabling nouveau, both in the kernel and the xorg driver, and
>>> see
>>> if the crashes stop.
>>
>> Ok, but what other driver shall I use instead?
> 
> The vesa driver would probably be easiest to get up and running. 

I blacklisted nouveau kernel driver (using /etc/modprobe.d/nouveau.conf
and then update-initramfs -u) and removed
/usr/lib/xorg/modules/drivers/nouveau_drv.so , so nouveau is no longer used:

# lsmod | grep -i -E '(video|nouveau|nv)'
nvram                  13034  1 thinkpad_acpi
video                  18096  0
thermal_sys            27642  3 video,thermal,processor

# lspci -v
[...]
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [Quadro NVS
140M] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Lenovo ThinkPad T61
	Flags: bus master, fast devsel, latency 0, IRQ 10
	Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
	I/O ports at 2000 [size=128]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [60] Power Management version 2
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [128] Power Budgeting <?>
	Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>

^^^^ No nouveau here. But why is the kernel driver in use not listed
here anymore?...

X11 now seems to be using vesa driver, no crashes so far, but I am only
having 1024x768 screen resolution (instead of 1680x1050, AFAIR).

$ cat /var/log/Xorg.0.log | grep -i -E '(video|nouveau|nv|vesa)'
[   114.300] 	X.Org Video Driver: 18.0
[   114.636] (==) Matched nouveau as autoconfigured driver 0
[   114.636] (==) Matched nv as autoconfigured driver 1
[   114.636] (==) Matched vesa as autoconfigured driver 4
[   114.636] (II) LoadModule: "nouveau"
[   114.653] (WW) Warning, couldn't open module nouveau
[   114.653] (II) UnloadModule: "nouveau"
[   114.653] (II) Unloading nouveau
[   114.653] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   114.653] (II) LoadModule: "nv"
[   114.654] (WW) Warning, couldn't open module nv
[   114.654] (II) UnloadModule: "nv"
[   114.654] (II) Unloading nv
[   114.654] (EE) Failed to load module "nv" (module does not exist, 0)
[   114.665] 	Module class: X.Org Video Driver
[   114.665] 	ABI class: X.Org Video Driver, version 18.0
[   114.666] 	Module class: X.Org Video Driver
[   114.666] 	ABI class: X.Org Video Driver, version 18.0
[   114.666] (II) LoadModule: "vesa"
[   114.666] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[   114.680] (II) Module vesa: vendor="X.Org Foundation"
[   114.680] 	Module class: X.Org Video Driver
[   114.680] 	ABI class: X.Org Video Driver, version 18.0
[   114.680] (II) VESA: driver for VESA chipsets: vesa
[   114.692] 	ABI class: X.Org Video Driver, version 18.0
[   114.692] 	ABI class: X.Org Video Driver, version 18.0
[   114.699] 	ABI class: X.Org Video Driver, version 18.0
[   114.734] 	ABI class: X.Org Video Driver, version 18.0
[   114.734] (II) VESA(0): initializing int10
[   114.736] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[   114.788] (II) VESA(0): VESA BIOS detected
[   114.788] (II) VESA(0): VESA VBE Version 3.0
[   114.788] (II) VESA(0): VESA VBE Total Mem: 14336 kB
[   114.788] (II) VESA(0): VESA VBE OEM: NVIDIA
[   114.788] (II) VESA(0): VESA VBE OEM Software Rev: 96.134
[   114.788] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
[   114.788] (II) VESA(0): VESA VBE OEM Product: G86 Board - NV_NB8M
[   114.788] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev
[   114.882] (II) VESA(0): Creating default Display subsection in Screen
section
[   114.882] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[   114.882] (==) VESA(0): RGB weight 888
[   114.882] (==) VESA(0): Default visual is TrueColor
[   114.882] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[   114.956] (II) VESA(0): VESA VBE DDC supported
[   114.956] (II) VESA(0): VESA VBE DDC Level none
[   114.956] (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
[   115.219] (II) VESA(0): VESA VBE DDC read failed
[   115.219] (II) VESA(0): Searching for matching VESA mode(s):
[   115.273] (II) VESA(0): Total Memory: 224 64KB banks (14336kB)
[   115.273] (II) VESA(0): <default monitor>: Using default hsync range
of 31.50-48.00 kHz
[   115.273] (II) VESA(0): <default monitor>: Using default vrefresh
range of 50.00-70.00 Hz
[   115.273] (II) VESA(0): <default monitor>: Using default maximum
pixel clock of 65.00 MHz
[   115.273] (WW) VESA(0): Unable to estimate virtual size
[   115.273] (II) VESA(0): Not using built-in mode "1680x1050" (no mode
of this name)
[   115.273] (II) VESA(0): Not using built-in mode "1280x1024" (no mode
of this name)
[   115.273] (II) VESA(0): Not using built-in mode "1280x800" (no mode
of this name)
[   115.273] (II) VESA(0): Not using built-in mode "1024x768" (no mode
of this name)
[   115.273] (II) VESA(0): Not using built-in mode "800x600" (no mode of
this name)
[   115.273] (II) VESA(0): Not using built-in mode "640x480" (no mode of
this name)
[   115.273] (II) VESA(0): Not using built-in mode "640x400" (no mode of
this name)
[   115.273] (II) VESA(0): Not using built-in mode "320x400" (no mode of
this name)
[   115.273] (II) VESA(0): Not using built-in mode "320x240" (no mode of
this name)
[   115.273] (II) VESA(0): Not using built-in mode "320x200" (no mode of
this name)
[   115.274] (WW) VESA(0): No valid modes left. Trying less strict filter...
[   115.274] (II) VESA(0): <default monitor>: Using hsync range of
31.50-48.00 kHz
[   115.274] (II) VESA(0): <default monitor>: Using vrefresh range of
50.00-70.00 Hz
[   115.274] (II) VESA(0): <default monitor>: Using maximum pixel clock
of 65.00 MHz
[   115.274] (WW) VESA(0): Unable to estimate virtual size
[   115.324] (II) VESA(0): Not using built-in mode "1680x1050" (hsync
out of range)
[   115.324] (II) VESA(0): Not using built-in mode "1280x1024" (hsync
out of range)
[   115.324] (II) VESA(0): Not using built-in mode "1280x800" (hsync out
of range)
[   115.324] (II) VESA(0): Not using built-in mode "640x400" (hsync out
of range)
[   115.324] (II) VESA(0): Not using built-in mode "320x400" (hsync out
of range)
[   115.324] (II) VESA(0): Not using built-in mode "320x240" (illegal
horizontal timings)
[   115.324] (II) VESA(0): Not using built-in mode "320x200" (illegal
horizontal timings)
[   115.324] (--) VESA(0): Virtual size is 1024x768 (pitch 1024)
[   115.324] (**) VESA(0): *Built-in mode "1024x768"
[   115.324] (**) VESA(0): *Built-in mode "800x600"
[   115.324] (**) VESA(0): *Built-in mode "640x480"
[   115.324] (==) VESA(0): DPI set to (96, 96)
[   115.324] (II) VESA(0): Attempting to use 60Hz refresh for mode
"1024x768" (118)
[   115.325] (II) VESA(0): Attempting to use 60Hz refresh for mode
"800x600" (115)
[   115.326] (II) VESA(0): Attempting to use 60Hz refresh for mode
"640x480" (112)
[   115.326] (**) VESA(0): Using "Shadow Framebuffer"
[   115.358] 	ABI class: X.Org Video Driver, version 18.0
[   115.358] (II) VESA(0): initializing int10
[   115.358] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[   115.409] (II) VESA(0): VESA BIOS detected
[   115.409] (II) VESA(0): VESA VBE Version 3.0
[   115.409] (II) VESA(0): VESA VBE Total Mem: 14336 kB
[   115.409] (II) VESA(0): VESA VBE OEM: NVIDIA
[   115.409] (II) VESA(0): VESA VBE OEM Software Rev: 96.134
[   115.409] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
[   115.409] (II) VESA(0): VESA VBE OEM Product: G86 Board - NV_NB8M
[   115.409] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev
[   115.409] (II) VESA(0): virtual address = 0x7fb7b4ccc000,
[   115.432] (II) VESA(0): Setting up VESA Mode 0x118 (1024x768)
[   115.773] (==) VESA(0): Default visual is TrueColor
[   115.808] (==) VESA(0): Backing store enabled
[   115.812] (==) VESA(0): DPMS enabled
[   117.700] (II) config/udev: Adding input device Video Bus
(/dev/input/event4)
[   117.700] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[   117.700] (II) Using input driver 'evdev' for 'Video Bus'
[   117.700] (**) Video Bus: always reports core events
[   117.700] (**) evdev: Video Bus: Device: "/dev/input/event4"
[   117.700] (--) evdev: Video Bus: Vendor 0 Product 0x6
[   117.700] (--) evdev: Video Bus: Found keys
[   117.700] (II) evdev: Video Bus: Configuring as keyboard
[   117.700] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:05/LNXVIDEO:01/input/input5/event4"
[   117.700] (II) XINPUT: Adding extended input device "Video Bus"
(type: KEYBOARD, id 7)

"Unable to estimate virtual size" seems to be the problem. Is this a
VESA driver limitation (it will not support my 1680x1050 native
resolution) or how do I configure this?
Some 1680x1050 modes seem to be loaded but then skipped. :/

I would install proprietary nvidia drivers only as the last resort.

-- 
http://people.eisenbits.com/~stf/
http://www.eisenbits.com/

OpenPGP: 9EC2 5620 2355 B1DC 4A8F  8C79 0EC7 C214 E5AE 3B4E

[toc] | [prev] | [next] | [standalone]

#162110 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromPatrick Bartek <nemommxiv@gmail.com>
Date2015-12-25 19:40 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJFrr-72Q-3@gated-at.bofh.it>
In reply to#162098
On Fri, 25 Dec 2015, Staszek wrote:

> On 2015-12-24 15:07, Sven Arvidsson wrote:
> > Try disabling nouveau, both in the kernel and the xorg driver, and
> > see if the crashes stop.
> 
> Ok, but what other driver shall I use instead?
> 
> According to ThinkPad Wiki nv driver works:
> http://www.thinkwiki.org/wiki/NVIDIA_Quadro_NVS_140M . Unfortunately
> it is not present in Jessie:
> https://packages.debian.org/search?keywords=xserver-xorg-video-nv ??..

Have you tried the proprietary nVidia drivers?  I was having
intermittent problems with noveau on my Wheezy system, and installed
nVidia's. Been working great since. Simple install.  Just followed the
instructions.

B

[toc] | [prev] | [next] | [standalone]

#162093 — Re: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)

FromCharlie Kravetz <cjk@teamcharliesangels.com>
Date2015-12-24 15:50 +0100
SubjectRe: random reboots of my Lenovo ThinkPad (3.16.7-ckt20-1+deb8u1) (kernel stack trace)
Message-ID<qJfnk-7Z0-7@gated-at.bofh.it>
In reply to#162090
On Thu, 24 Dec 2015 14:00:15 +0100
Staszek <stf.list.other@eisenbits.com> wrote:

>On 2015-12-22 22:18, Anders Andersson wrote:
>> First thing I do in a case like this is to run memtest86 in some form
>> on the hardware.
>
>Good point, but:
>
>1. those stack traces are always nouveau related
>2. memtest86+ yields nothing
>3. often upon logging into X, before the desktop appears, I am getting
>unexpected splash screens; they look like:
>http://people.eisenbits.com/~stf/load/20151224-bw-tiling.png , or
>sometimes that is a mangled view of what was being displayed before the
>crash+reboot.
>
>Perhaps that is a graphics card...
>

I have a Lenovo T520 here, with dual graphics. I found Nouveau did not
work very good for me. I run dual monitors, so I had to make Optimus
work. The best guide I found is
http://www.unixmen.com/how-to-make-nvidia-optimus-technology-work-properly-on-debian/

It makes the setup easy.


-- 
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM.   [http://keepingdreams.com]

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web