Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Fri, Oct 15, 2004 at 11:40:30AM -0400, Jon Smirl wrote: On Fri, 15 Oct 2004 15:19:41 +0100, José Fonseca [EMAIL PROTECTED] wrote: It doesn't say nothing and I found (partially) why: the dynamic lynking is failing, so the call to drm_init(pci_driver, pciidlist, driver) never reaches a single line of code there (no debug message, *nothing*). Could it be symbol versioning? I've diffed my two machines kernel config files and symbol versioning was one of the suspicious differences indeed, but I only managed to get everything working as expected after disabling some of those kernel hacking options too. Things behave weirdly if you have an old drm module loaded and load the new ones too. You should at least get a sign on: [drm] Initialized drm 1.0.0 20040925 Yes, this message always appeared when loading drm.ko. That the very first thing the drm module does. If you sync from CVS you need to use... insmod ./drm.ko drm_debug=1 Thanks for your help. This issue is finally closed. Regards, José Fonseca --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Mon, Oct 11, 2004 at 10:52:40AM -0400, Jon Smirl wrote: What does dmesg say? There should be some debugging data in the log. drm loads right? which personality is failing? It doesn't say nothing and I found (partially) why: the dynamic lynking is failing, so the call to drm_init(pci_driver, pciidlist, driver) never reaches a single line of code there (no debug message, *nothing*). I still don't know how this can be (the kernel configuration, or software setup, maybe), but I'm more inclined toward a problem on my end, rather than in *-core code. I'll still try sorting this out, so that I can move on to more interesting things. José Fonseca --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Fri, 15 Oct 2004 15:19:41 +0100, José Fonseca [EMAIL PROTECTED] wrote: It doesn't say nothing and I found (partially) why: the dynamic lynking is failing, so the call to drm_init(pci_driver, pciidlist, driver) never reaches a single line of code there (no debug message, *nothing*). Could it be symbol versioning? Things behave weirdly if you have an old drm module loaded and load the new ones too. You should at least get a sign on: [drm] Initialized drm 1.0.0 20040925 That the very first thing the drm module does. If you sync from CVS you need to use... insmod ./drm.ko drm_debug=1 -- Jon Smirl [EMAIL PROTECTED] --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Wed, Oct 06, 2004 at 05:51:41PM -0400, Jon Smirl wrote: For debug info: insmod ./drm.ko drm_opts=debug:on insmod ./radeon.ko drm_opts=debug:on I haven't fully writen the code for the new parameters yet. When it is finished the message will disappear. Make sure you don't have any old DRM drivers loaded by accident or compiled into your kernel. If you do the symbols will be all messed up and who know where the code will jump. Sometimes the drm/radeon pair will still load even if an old version is in memory. Try a sequence like this: [EMAIL PROTECTED] linux-core]# insmod ./drm.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# rmmod drm [EMAIL PROTECTED] linux-core]# This runs for me without errors. This still fails on me. I've checked on another machine, with the same kernel but different hardware and kernel configuration, and it does works fint. I don't suppose any processor-specific assembly was added to the *-core, so I'm inclined towards any conflict with this machine kernel's configuration. FYI it's an AMD K6. I'll try to backtrack in the *-core to determine when the problem happened. Any other hints to hunt this bug down? José Fonseca --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Mon, 11 Oct 2004 11:56:27 +0100, José Fonseca [EMAIL PROTECTED] wrote: I've checked on another machine, with the same kernel but different hardware and kernel configuration, and it does works fint. I don't suppose any processor-specific assembly was added to the *-core, so I'm inclined towards any conflict with this machine kernel's configuration. FYI it's an AMD K6. I'll try to backtrack in the *-core to determine when the problem happened. Any other hints to hunt this bug down? What does dmesg say? There should be some debugging data in the log. drm loads right? which personality is failing? -- Jon Smirl [EMAIL PROTECTED] --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Code status (Was: New DRM driver model - gets rid of DRM() macros!)
Jon, I was trying to build and test the linux-core - I really like what you've been doing there - but I get endless kernel oops after insmod'ing any of the driver modules (not the common drm one though), regardless the specific chip is present or not. Before I search deeper into this could you let me know whether the code in *-core is not runnable yet, or if there must be something wrong on my side? Regards, José Fonseca --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Wed, 6 Oct 2004, [iso-8859-15] José Fonseca wrote: Jon, I was trying to build and test the linux-core - I really like what you've been doing there - but I get endless kernel oops after insmod'ing any of the driver modules (not the common drm one though), regardless the specific chip is present or not. Before I search deeper into this could you let me know whether the code in *-core is not runnable yet, or if there must be something wrong on my side? Just as a data point I was able to insert radeon module just fine on 2.6.9rc3. This was yesterday. Maybe a fresh checkout will help ? best Vladimir Dergachev Regards, José Fonseca --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Wed, Oct 06, 2004 at 09:53:51AM -0400, Vladimir Dergachev wrote: On Wed, 6 Oct 2004, [iso-8859-15] José Fonseca wrote: Jon, I was trying to build and test the linux-core - I really like what you've been doing there - but I get endless kernel oops after insmod'ing any of the driver modules (not the common drm one though), regardless the specific chip is present or not. Before I search deeper into this could you let me know whether the code in *-core is not runnable yet, or if there must be something wrong on my side? Just as a data point I was able to insert radeon module just fine on 2.6.9rc3. This was yesterday. Maybe a fresh checkout will help ? Inserting mga worked on 2.6.7 for me. Unfortunately actually using the module failed. The problem is with get_order() in drm_bufs.c. After I replaced get_order() with the original drm order function things started to work. -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
I'll revert these to the old DRM(order). One of the kernel developers wanted this changed and now I see these functions aren't identical. -- Jon Smirl [EMAIL PROTECTED] --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Wed, 6 Oct 2004 12:14:05 -0400, Jon Smirl [EMAIL PROTECTED] wrote: I'll revert these to the old DRM(order). One of the kernel developers wanted this changed and now I see these functions aren't identical. This is checked in now. -- Jon Smirl [EMAIL PROTECTED] --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Wed, 6 Oct 2004 14:37:14 +0100, José Fonseca [EMAIL PROTECTED] wrote: Jon, I was trying to build and test the linux-core - I really like what you've been doing there - but I get endless kernel oops after insmod'ing any of the driver modules (not the common drm one though), regardless the specific chip is present or not. Before I search deeper into this could you let me know whether the code in *-core is not runnable yet, or if there must be something wrong on my side? What kernel version? What is the OOPs? Be sure and try with the current CVS. Bugs are getting fixed as fast as people are reporting them. -- Jon Smirl [EMAIL PROTECTED] --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
On Wed, Oct 06, 2004 at 12:30:01PM -0400, Jon Smirl wrote: On Wed, 6 Oct 2004 14:37:14 +0100, José Fonseca [EMAIL PROTECTED] wrote: Jon, I was trying to build and test the linux-core - I really like what you've been doing there - but I get endless kernel oops after insmod'ing any of the driver modules (not the common drm one though), regardless the specific chip is present or not. Before I search deeper into this could you let me know whether the code in *-core is not runnable yet, or if there must be something wrong on my side? What kernel version? kernel version 2.6.8, from debian unstable. What is the OOPs? They are not reproducible, i.e., they are always different every run, on a different entry point. They happen one after the other so fast that they're never recorded on /proc/kmsg. I got a screenshot (literaly, with a digital camera) on http://jrfonseca.dyndns.org/misc/bugs/radeon-core.jpg after insmod'ing radeon. It's likely that the first oops is within the loaded module, but all the others oops trash it away... I also add that insmod'ing mach64 or radeon from the linux-2.6 works just fine, so it must be some regression in linux-core. Be sure and try with the current CVS. Bugs are getting fixed as fast as people are reporting them. On Wed, Oct 06, 2004 at 09:53:51AM -0400, Vladimir Dergachev wrote: Just as a data point I was able to insert radeon module just fine on 2.6.9rc3. This was yesterday. Maybe a fresh checkout will help ? best Vladimir Dergachev I've tracking the CVS closely for the last 2 days, but nothing changed so far. I'll try with 2.6.9 too see if it changes anything. I noticed the Ignoring new-style parameters in presence of obsolete ones warnings. What is the de-facto way to enable extra debugging info in linux-core modules? José Fonseca --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Code status (Was: New DRM driver model - gets rid of DRM() macros!)
For debug info: insmod ./drm.ko drm_opts=debug:on insmod ./radeon.ko drm_opts=debug:on I haven't fully writen the code for the new parameters yet. When it is finished the message will disappear. Make sure you don't have any old DRM drivers loaded by accident or compiled into your kernel. If you do the symbols will be all messed up and who know where the code will jump. Sometimes the drm/radeon pair will still load even if an old version is in memory. Try a sequence like this: [EMAIL PROTECTED] linux-core]# insmod ./drm.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# insmod ./radeon.ko drm_opts=debug:on [EMAIL PROTECTED] linux-core]# rmmod radeon [EMAIL PROTECTED] linux-core]# rmmod drm [EMAIL PROTECTED] linux-core]# This runs for me without errors. -- Jon Smirl [EMAIL PROTECTED] --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
