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


Groups > linux.debian.kernel > #55641 > unrolled thread

Bug#842971: loading nouveau causes screen to become unresponsive

Started byMathieu Malaterre <malat@debian.org>
First post2016-11-04 08:10 +0100
Last post2016-11-06 20:40 +0100
Articles 2 — 2 participants

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#842971: loading nouveau causes screen to become unresponsive Mathieu Malaterre <malat@debian.org> - 2016-11-04 08:10 +0100
    Bug#842971: loading nouveau causes screen to become unresponsive Karl-Philipp Richter <krichter@posteo.de> - 2016-11-06 20:40 +0100

#55641 — Bug#842971: loading nouveau causes screen to become unresponsive

FromMathieu Malaterre <malat@debian.org>
Date2016-11-04 08:10 +0100
SubjectBug#842971: loading nouveau causes screen to become unresponsive
Message-ID<szGNr-6VD-1@gated-at.bofh.it>
hi,

On Thu, Nov 3, 2016 at 9:06 PM, Karl-Philipp Richter <krichter@posteo.de> wrote:
>
>
> Am 03.11.2016 um 12:15 schrieb Mathieu Malaterre:
>> Why src:linux and not simply the binary package: xserver-xorg-video-nouveau ?
> I already did at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806684 and have been
> requested to file this against the kernel.

I see.

>> Are you able to reproduce that directly from one of the virtual tty so
>> as to copy/paste the actual error log.
> Since there's nothing I can do after `modprobe nouveau` because the
> screen is all white and changing tty doesn't work as described, I don't
> know how to provide the error logs. I assumed that `reportbug` would
> include them. I'm happy to add them if you assist me.

Here is what I would do:

#1. Have an ssh connection ready. Right after doing your `modprobe
nouveau`, run `dmesg` from the ssh connection and copy/paste.

#2. All logs are stored in /var/log/syslog. Then they are archived in
gz form. So you should be able to do something like `zgrep nouveau
/var/log/syslog*.gz`. It may be more difficult to search through this,
so I would suggest #1 first if you can.

[toc] | [next] | [standalone]


#55658

FromKarl-Philipp Richter <krichter@posteo.de>
Date2016-11-06 20:40 +0100
Message-ID<sABsl-186-1@gated-at.bofh.it>
In reply to#55641

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

Hi,

Am 04.11.2016 um 08:04 schrieb Mathieu Malaterre:
> Here is what I would do:
> 
> #1. Have an ssh connection ready. Right after doing your `modprobe
> nouveau`, run `dmesg` from the ssh connection and copy/paste.
> 
> #2. All logs are stored in /var/log/syslog. Then they are archived in
> gz form. So you should be able to do something like `zgrep nouveau
> /var/log/syslog*.gz`. It may be more difficult to search through this,
> so I would suggest #1 first if you can.

The changes in `/var/log/syslog` after `modprobe nouveau` (are the same
as in `dmesg`):

    Nov  6 20:24:41 debian kernel: [  132.889027] [drm] Initialized drm
1.1.0 20060810
    Nov  6 20:24:42 debian kernel: [  133.287204] checking generic
(98004000 c0000) vs hw (98000000 8000000)
    Nov  6 20:24:42 debian kernel: [  133.287226] fb: switching to
nouveaufb from OFfb NVDA,NVMac
    Nov  6 20:24:42 debian kernel: [  133.287498] Console: switching to
colour dummy device 80x25
    Nov  6 20:24:42 debian kernel: [  133.291700] nouveau 0000:00:10.0:
NVIDIA NV11 (011000b2)
    Nov  6 20:24:42 debian kernel: [  133.303059] nouveau 0000:00:10.0:
bios: version 03.11.00.15.00
    Nov  6 20:24:42 debian kernel: [  133.303102] nouveau 0000:00:10.0:
bios: DCB table not found
    Nov  6 20:24:42 debian kernel: [  133.315098] nouveau 0000:00:10.0:
bios: DCB table not found
    Nov  6 20:24:42 debian kernel: [  133.316476] nouveau 0000:00:10.0:
bios: DCB table not found
    Nov  6 20:24:42 debian kernel: [  133.316501] nouveau 0000:00:10.0:
bios: DCB table not found
    Nov  6 20:24:42 debian kernel: [  133.316555] nouveau 0000:00:10.0:
bios: DCB table not found
    Nov  6 20:24:42 debian kernel: [  133.505732] nouveau 0000:00:10.0:
tmr: unknown input clock freq
    Nov  6 20:24:42 debian kernel: [  133.506519] nouveau 0000:00:10.0:
fb: 64 MiB DDR1
    Nov  6 20:24:42 debian kernel: [  133.512136] [TTM] Zone  kernel:
Available graphics memory: 125276 kiB
    Nov  6 20:24:42 debian kernel: [  133.512159] [TTM] Initializing
pool allocator
    Nov  6 20:24:42 debian kernel: [  133.512245] nouveau 0000:00:10.0:
DRM: VRAM: 63 MiB
    Nov  6 20:24:42 debian kernel: [  133.512253] nouveau 0000:00:10.0:
DRM: GART: 128 MiB
    Nov  6 20:24:42 debian kernel: [  133.512267] nouveau 0000:00:10.0:
DRM: BMP version 5.16
    Nov  6 20:24:42 debian kernel: [  133.512278] nouveau 0000:00:10.0:
DRM: No DCB data found in VBIOS
    Nov  6 20:24:42 debian kernel: [  133.517274] nouveau 0000:00:10.0:
DRM: Adaptor not initialised, running VBIOS init tables.
    Nov  6 20:24:42 debian kernel: [  133.519035] nouveau 0000:00:10.0:
DRM: Saving VGA fonts
    Nov  6 20:24:42 debian kernel: [  133.571915] nouveau 0000:00:10.0:
DRM: No DCB data found in VBIOS
    Nov  6 20:24:42 debian kernel: [  133.578176] [drm] Supports vblank
timestamp caching Rev 2 (21.10.2013).
    Nov  6 20:24:42 debian kernel: [  133.578198] [drm] Driver supports
precise vblank timestamp query.
    Nov  6 20:24:42 debian kernel: [  133.586305] nouveau 0000:00:10.0:
DRM: MM: using M2MF for buffer copies
    Nov  6 20:24:42 debian kernel: [  133.640067] nouveau 0000:00:10.0:
fifo: DMA_PUSHER - ch 0 [DRM] get 80086078 put 0000016c state c000016c
(err: MEM_FAULT) push 00000000
    Nov  6 20:24:42 debian kernel: [  133.640093] nouveau 0000:00:10.0:
fifo: intr 00010000
    Nov  6 20:24:42 debian kernel: [  133.640123] nouveau 0000:00:10.0:
DRM: allocated 1024x768 fb: 0x8000, bo cc340000
    Nov  6 20:24:42 debian kernel: [  133.647447] Console: switching to
colour frame buffer device 128x48
    Nov  6 20:24:42 debian kernel: [  133.647500] nouveau 0000:00:10.0:
fb0: nouveaufb frame buffer device
    Nov  6 20:24:42 debian kernel: [  133.647539] [drm] Initialized
nouveau 1.3.1 20120801 for 0000:00:10.0 on minor 0
    Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Service
hold-off time over, scheduling restart.
    Nov  6 20:24:45 debian systemd[1]: Stopped Bumblebee C Daemon.
    Nov  6 20:24:45 debian systemd[1]: Started Bumblebee C Daemon.
    Nov  6 20:24:45 debian bumblebeed[1105]: [  136.560197] [ERROR]No
integrated video card found, quitting.
    Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Main process
exited, code=exited, status=1/FAILURE
    Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Unit entered
failed state.
    Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Failed with
result 'exit-code'.

Thanks for your suggestions.

-Kalle

[toc] | [prev] | [standalone]


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


csiph-web