| Summary: | FreeBSD system locks up with DRI enabled on Radeon RS300 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Yong-Jhen Hong <yongjhen> | ||||||||||
| Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> | ||||||||||
| Status: | RESOLVED INVALID | QA Contact: | |||||||||||
| Severity: | normal | ||||||||||||
| Priority: | high | ||||||||||||
| Version: | DRI git | ||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||
| OS: | FreeBSD | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Yong-Jhen Hong
2006-12-11 00:46:29 UTC
Created attachment 8054 [details]
drm debug message from syslog
Could you also attach your xorg log when it locked up? (In reply to comment #2) > Could you also attach your xorg log when it locked up? Sorry I cannot do it because it is empty. (In reply to comment #3) > (In reply to comment #2) > > Could you also attach your xorg log when it locked up? > > Sorry I cannot do it because it is empty. If that's because of the crash try mounting the partition where it is with the sync option. If it's always empty there is something wrong with your setupl... Created attachment 8069 [details]
X.org server log when system locks up
Finally got the log after tuning off soft-updates and mounting with sync option
to the device.
I can't see anything unusual in the log. Seems to blow up when initializing the cp. Could you provide the drm debug messages when mounted with sync? I think there should be some more. Not sure if it would reveal anything interesting, but it's worth a try. (In reply to comment #6) > I can't see anything unusual in the log. Seems to blow up when initializing the > cp. Could you provide the drm debug messages when mounted with sync? I think > there should be some more. Not sure if it would reveal anything interesting, but > it's worth a try. It it exactly the same from the one I posted earlier, unfortunately. Except for PID and some differences on addresses. After some tracing, I find it hangs on: radeon_dri.c: RADEONDRIKernelInit(): drmCommandWrite(info->drmFD, DRM_RADEON_CP_INIT, &drmInfo, sizeof(drmRadeonInit)) Should I provide all the fields in drmInfo? (In reply to comment #8) > After some tracing, I find it hangs on: > > radeon_dri.c: > RADEONDRIKernelInit(): > drmCommandWrite(info->drmFD, DRM_RADEON_CP_INIT, &drmInfo, sizeof(drmRadeonInit)) yup, that's what I meant with the cp init... (it should cause some more drm messages, maybe syslog doesn't write them instantly to the log file) > Should I provide all the fields in drmInfo? I think it's almost impossible those are wrong. Is this a regression? You could try with an older driver. Some people also had trouble with AGP, so you could try pci mode (Option "BusType" "PCI"). Also, is the ram amount (and width - not sure if this has to match in igp case) correctly detected (should match what you've configured in bios). Could also be an issue with the memory maps - though I think benh really fixed that up... Created attachment 8076 [details]
X.org server log with PCI mode
It works with PCI mode.
Created attachment 8077 [details]
drm syslog with PCI mode
(In reply to comment #10) > It works with PCI mode. Hmm. Another one of those cases. I wonder what's up with that. Could be problem with setting up agp map (seems unlikely), asic bug needing workaround (like forcing AIC clock on), no idea :-(. Hmm, could you try what was suggested here: https://bugs.freedesktop.org/show_bug.cgi?id=9284 (In reply to comment #13) > Hmm, could you try what was suggested here: > https://bugs.freedesktop.org/show_bug.cgi?id=9284 I tried the "AGPMode" option with values 8, 4, 2, and 1, but still got the lock-ups at the same place with no luck. Yong-Jhen Hong Do you still experience this issue with newer soft ? Please check the status of your issue. Hi, Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org. To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default). Sorry about the noise! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.