[driverloader] kernel oops on X11 shutdown with stk16 kernel

[Somsak Sriprayoonsakul]

Hi,
   I 'm having similar problem on FC3 (2.6.9-1.667.stk16) too. Also,
I'm using Intel Centrino base Notebook (Dell latitude 500 with Intel
Wireless Proce 2100 MiniPCI) wih latest WindowsXP driver from Dell
(w70n51.inf,sys). I think that Linuxant should posted a pre-compiled
kernel which resolve this kind of problem.

>Hi,
>
>in the 16K stacks kernel we offer on our web site, we have reversed a 
>few patches. We have reversed at least the following patches :
>
>---
>4G/4G layout
>4K stacks
>---
>
>We also added our own 16K stacks patch. We probably also reversed some 
>other less important patches that were now difficult to merge because of 
>the removal of the previous mentioned patches.
>
>You can download the 'kernel-source' package of the 16K stacks kernel we 
>offer from the following page :
>
>http://www.linuxant.com/driverloader/wlan/full/downloads-fc2-kernel-i586.php
>
>With the 'kernel-source' package, you will be able to see which patches 
>where reversed.
>
>Regards,
>
>
>Jonathan
>Technical specialist / Linuxant
>www.linuxant.com
>support at linuxant.com
>
>
>Rich Ibbotson wrote:
>> Hi Jonathan,
>> 
>> That kernel works fine, no strange X11 behavior.  Driverloader works 
>> great, too.  So I guess it's something in one of the 45 patches (yikes, 
>> 45 patches!) included in the FC2 kernel.  I'm a little hesitant about 
>> not using any of those patches, since I'm not sure why they're being 
>> applied.  I can try reversing some of the patches on the FC2 kernel 
>> sources, to see if I can find the problematic one.  Any suggestions on 
>> where to start?  Or maybe a different suggestion altogether?
>> 
>> thanks very much for the help,
>> Rich
>> 
>> Linuxant support (Jonathan) wrote:
>> 
>>> Hi,
>>>
>>> please try with a fresh 2.6.8.1 kernel from 'http://www.kernel.org'. 
>>> Before you compile this kernel, please apply this patch :
>>>
>>> http://www.linuxant.com/driverloader/wlan/full/archive/linux-2.6.8-16kstacks.patch
>>>
>>>
>>> You should make sure that the following configuration option is disabled
>>>
>>> ---
>>> CONFIG_4KSTACKS
>>> ---
>>>
>>> and you should enable the following option
>>>
>>> ---
>>> CONFIG_16KSTACKS
>>> ---
>>>
>>> Since you will now use a custom compiled Linux kernel, you will need 
>>> to use the generic RPM package (if you do not already use it) that we 
>>> offer on the DriverLoader download page at :
>>>
>>> http://www.linuxant.com/driverloader/wlan/full/downloads.php
>>>
>>> Regards,
>>>
>>>
>>> Jonathan
>>> Technical specialist / Linuxant
>>> www.linuxant.com
>>> support at linuxant.com
>>>
>>>
>>> Rich Ibbotson wrote:
>>>
>>>> Thanks, Jonathan.  It looks like that doesn't help for my case (intel 
>>>> centrino with XP drivers).
>>>> I still get messages indicating that I need to use a kernel with >4K 
>>>> stack size.
>>>>
>>>> cheers,
>>>> Rich
>>>>
>>>> Jonathan Baron wrote:
>>>>
>>>>> On 10/03/04 08:00, Rich Ibbotson wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I'm having some difficulties getting driverloader running on my Fedora
>>>>>> Core 2 system.  Actually, it's not the driverloader code that is the
>>>>>> problem, it's the "stk16" kernel that I'm using to get around the 4k
>>>>>> stack restriction in the FC2 kernel.
>>>>>>
>>>>>> The problem:
>>>>>> When I boot using the 2.6.8-1.521.stk16.i686 replacement kernel, 
>>>>>> running
>>>>>> in runlevel 5, all is well until I log out of a kde session.  At that
>>>>>> point, instead of getting a graphical login screen, the X server 
>>>>>> crashes
>>>>>> and I see a kernel oops. I've included the relevant bits of
>>>>>> /var/log/messages and /var/log/Xorg.0.log below.
>>>>>>
>>>>>> Note that I am not sure whether or not this is due to the 4k/16k 
>>>>>> patch.
>>>>>> I've built a kernel from the sources for 2.6.8-1.521 (from Fedora Core
>>>>>> 2) with only the change to disable 4 GB kernel-space/user-space vm
>>>>>> support (no 16k stack patch), and I see slightly different problems -
>>>>>> sometimes an oops at logout, sometimes a system freeze when I log in
>>>>>> graphically, sometimes it works fine.
>>>>>>
>>>>>> Any ideas?  I've tried building a custom kernel starting from the 
>>>>>> stk16
>>>>>> source but re-enabling 4G/4G virtual memory - the resulting kernel
>>>>>> doesn't even boot.  Last thing I see is "Uncompressing Linux... OK,
>>>>>> booting the kernel".
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> With Fedora Core 2 and the 2.6.8-1.521 kernel (the latest),
>>>>> driverloader works for me WITHOUT using a modified kernel (either
>>>>> custom or the stk16 from Linuxant).  You might try that.  I did
>>>>> do the following:
>>>>>
>>>>> dldrconfig --enable-workaround=stack
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> driverloader mailing list
>>>> driverloader at lists.linuxant.com
>>>> https://www.linuxant.com/mailman/listinfo/driverloader
>>>
>>>
>>>
>> 
>> _______________________________________________
>> driverloader mailing list
>> driverloader at lists.linuxant.com
>> https://www.linuxant.com/mailman/listinfo/driverloader
>