Displaying 2 results from an estimated 2 matches for "invalid_storage_type".
2014 Jun 17
1
[REGRESSION] drm/g94/i2c: add aux channel interrupt driver
...t
[ 41.862815] nouveau D[ DEVICE][0000:01:00.0][0x80000080][ffff880002b39a00] illegal class 0xa06f
[ 41.862824] nouveau D[ PFIFO][0000:01:00.0] reset
[ 41.862827] nouveau D[ PFIFO][0000:01:00.0] 1 PBDMA unit(s)
[ 41.868057] nouveau E[ PFIFO][0000:01:00.0] write fault at 0x0000080000 [INVALID_STORAGE_TYPE] from BAR1/BAR_WRITE on channel 0x3ffffedf000 [unknown]
[ 41.868116] nouveau D[ DEVICE][0000:01:00.0][0x80000080][ffff880002b39a00] illegal class 0xa06f
[ 41.873552] nouveau D[ SW][0000:01:00.0] reset
[ 41.873561] nouveau D[ PFIFO][0000:01:00.0][0xc000906f][ffff88006ed3f180] attached...
2013 Jun 06
1
Lockups ENGT430 (NVc0), failed to unbind.
...: 0x037f0040
Nothing adverse was observed at this time:
Jun 3 19:09:42 one kernel: [194241.366196] [drm] nouveau 0000:06:00.0: gpuobj -28
This was the time of the second lock-up:
Jun 4 20:40:44 one kernel: [285949.704837] [drm] nouveau 0000:06:00.0: PFIFO: write fault at 0x01bcb20000 [INVALID_STORAGE_TYPE] from PGRAPH/GPC0/PROP on channel 0x0000ac8000
Jun 4 20:40:44 one kernel: [285949.704846] [drm] nouveau 0000:06:00.0: PFIFO: unknown status 0x40000000
Some months ago, following advice from this list, I had
successfully restored function by doing these commands via ssh
from another machine:...