Opened 6 years ago

Closed 5 years ago

Last modified 4 years ago

#14593 closed bug (fixed)

[ati] attempting to clone non-user-clonable kernel area

Reported by: AlienSoldier Owned by: waddlesplash
Priority: normal Milestone: R1/beta2
Component: Drivers/Graphics/ati Version: R1/beta1
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Talked a bit about this on IRC with waddlesplash. Updated that PC again with latest nighlty last weekend and it was still going it. The linked picture of the KDL is from the first occurence that said (that one was an update that jumped from march 2018).

Attachments (1)

IMG_0415.JPG (1.5 MB ) - added by AlienSoldier 6 years ago.

Download all attachments as: .zip

Change History (8)

by AlienSoldier, 6 years ago

Attachment: IMG_0415.JPG added

comment:1 by waddlesplash, 6 years ago

Please retest with a newer build; it will give more information about the area.

comment:2 by diver, 6 years ago

Component: - GeneralDrivers/Graphics/ati
Owner: changed from nobody to korli
Status: newassigned
Summary: My P4 KDL at boot[ati] SMAP violation

comment:3 by diver, 6 years ago

Owner: changed from korli to diver
Summary: [ati] SMAP violation[ati] attempting to clone non-user-clonable kernel area

comment:4 by AlienSoldier, 6 years ago

Will only be able to test again when i am physically with my P4 in december.

comment:5 by diver, 6 years ago

Owner: changed from diver to waddlesplash

comment:6 by waddlesplash, 5 years ago

Resolution: fixed
Status: assignedclosed

Should have been fixed by korli's mass driver change.

comment:7 by nielx, 4 years ago

Milestone: UnscheduledR1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.