Problem: When pressing maximize button in KDE4 Konsole - the system hangs. After a remote login nvidia-bugreport.sh have been called, but it hangs too. Attaching partial log file.
Bug can be reproduced on two different machines - a MSI notebook with GF8600 card (attached log file from this notebook), and on a desktop machine with GF250 GTS.
Both computers running x86_64 kernel 2.6.38.2. and Xorg 1.10.0
Also this can be found in syslog after bug reproducing (taken from desktop machine)
Code:
Apr 7 10:05:26 DIT021 kernel: [ 20.679799] ioremap error for 0xdfbe2000-0xdfbe3000, requested 0x10, got 0x0
Apr 7 10:06:32 DIT021 kernel: [ 86.457512] NVRM: Xid (0000:01:00): 13, 0001 00000000 00005097 000015e0 00000000 00000100
Apr 7 10:08:13 DIT021 kernel: [ 187.300587] NVRM: Xid (0000:01:00): 13, 0002 00000000 0000502d 00000250 ffffffff 0000000c
Apr 7 10:08:13 DIT021 kernel: [ 187.326980] NVRM: Xid (0000:01:00): 13, 0002 00000000 0000502d 00000220 ffffffff 0000000c
Apr 7 10:08:13 DIT021 kernel: [ 187.339337] NVRM: Xid (0000:01:00): 1, Channel 00000001 Method 00000060 Data 0100cb1a
Apr 7 10:08:15 DIT021 kernel: [ 189.337344] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:17 DIT021 kernel: [ 191.335084] NVRM: Xid (0000:01:00): 1, Channel 00000001 Method 00000060 Data 0100cb1a
Apr 7 10:08:19 DIT021 kernel: [ 193.333307] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:21 DIT021 kernel: [ 195.330691] NVRM: Xid (0000:01:00): 1, Channel 00000001 Method 00000060 Data 0100cb1a
Apr 7 10:08:22 DIT021 kernel: [ 195.336038] NVRM: Xid (0000:01:00): 1, Channel 00000001 Method 00000060 Data 0100cb1a
Apr 7 10:08:23 DIT021 kernel: [ 197.334111] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:25 DIT021 kernel: [ 199.331466] NVRM: Xid (0000:01:00): 1, Channel 00000001 Method 00000060 Data 0100cb1a
Apr 7 10:08:27 DIT021 kernel: [ 201.329725] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:31 DIT021 kernel: [ 205.327061] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:35 DIT021 kernel: [ 209.333134] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:39 DIT021 kernel: [ 213.328806] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:43 DIT021 kernel: [ 217.324170] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:47 DIT021 kernel: [ 221.319732] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:51 DIT021 kernel: [ 225.331306] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:55 DIT021 kernel: [ 229.328311] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:08:59 DIT021 kernel: [ 233.324044] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:09:03 DIT021 kernel: [ 237.319884] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:09:07 DIT021 kernel: [ 241.316659] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:09:11 DIT021 kernel: [ 245.312201] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Apr 7 10:09:15 DIT021 kernel: [ 249.307582] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context