public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wink Saville <wink@saville.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Matthias Hentges <oe@hentges.net>, linux-kernel@vger.kernel.org
Subject: Hang in fb_notifier_call_chain with nvidia framebuffer
Date: Wed, 04 Oct 2006 09:26:04 -0700	[thread overview]
Message-ID: <4523E09C.9000609@saville.com> (raw)
In-Reply-To: <1159882225.2891.525.camel@laptopd505.fenrus.org>

[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]

Arjan van de Ven wrote:
> 
> please please remove "quiet"... that removes any kind of useful debug
> output! It also makes you point at the wrong party for blaming hangs
> on ;)
> 
> 

Arjan,

Attached in the zip file is:

log-hang1.txt	-> log showing hang
cfg-hang1	-> config file for hang condition
cfg-ok		-> config file that works
fbmem.c		-> Modifications to register_framebuffer

To possibly assist I turned on debugging in nvidia.c and found that it 
hung in the call to register_framebuffer. I then added some additional 
debug in that routine and it appears the hang occurs in the call to 
fb_notifier_call_chain.

Please let me know what else maybe needed.

Cheers,

Wink

My hardware is a Asus P5W DH Deluxe with Intel Core 2 Duo, Intel 
975X/ICH7R chip set & e-GeForce nvidia 7600 GT KO video card with 2GB of 
ram.

Other info when using config-ok:

wink@winkc2d1:~$ uname -a
Linux winkc2d1 2.6.18-w6 #7 SMP Wed Oct 4 09:13:10 PDT 2006 x86_64 GNU/Linux
wink@winkc2d1:~$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
stepping        : 6
cpu MHz         : 2404.168
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall 
nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips        : 4811.86
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
stepping        : 6
cpu MHz         : 2404.168
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall 
nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips        : 6934.66
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

wink@winkc2d1:~$ cat /proc/meminfo
MemTotal:      2058588 kB
MemFree:       1935192 kB
Buffers:          3496 kB
Cached:          53176 kB
SwapCached:          0 kB
Active:          52032 kB
Inactive:        36804 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:            1544 kB
Writeback:           0 kB
AnonPages:       32240 kB
Mapped:          14568 kB
Slab:            16012 kB
SReclaimable:     7432 kB
SUnreclaim:       8580 kB
PageTables:       2000 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   1029292 kB
Committed_AS:    54388 kB
VmallocTotal: 34359738367 kB
VmallocUsed:      6180 kB
VmallocChunk: 34359732163 kB


[-- Attachment #2: nvidiafb-hang1.zip --]
[-- Type: application/x-zip-compressed, Size: 33845 bytes --]

  parent reply	other threads:[~2006-10-04 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02  1:12 PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved with 2.6.18 kernel Wink Saville
2006-10-02  9:54 ` Andi Kleen
2006-10-02 15:10   ` Wink Saville
2006-10-02 15:22     ` Andi Kleen
2006-10-02 16:08       ` Wink Saville
2006-10-02 17:00 ` Matthias Hentges
2006-10-03  4:12   ` Wink Saville
2006-10-03 12:23     ` Matthias Hentges
2006-10-03 16:33       ` Wink Saville
2006-10-03 13:30     ` Arjan van de Ven
2006-10-03 16:37       ` Wink Saville
2006-10-04 16:26       ` Wink Saville [this message]
2006-10-08  6:01         ` Hang in fb_notifier_call_chain with nvidia framebuffer Andrew Morton
2006-10-08  8:14           ` Wink Saville
2006-10-08  9:07             ` Andrew Morton
2006-10-08 18:06               ` Wink Saville
2006-10-05  6:28       ` 2.6.18 Hang in fb_notifier_call_chain while booting " Wink Saville

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4523E09C.9000609@saville.com \
    --to=wink@saville.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe@hentges.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox