|Subject:||Re: module loading on 64-bit kernel|
|From:||"Stephen P. Becker" <firstname.lastname@example.org>|
|Date:||Tue, 19 Jul 2005 18:30:30 -0400|
|User-agent:||Mozilla Thunderbird 1.0.5 (X11/20050719)|
This seems to be a bug which crept in for (at least) 64bit Indy kernels in IIRC 2.6.12-rc3.
I'm fairly certain it happened with the initial 2.6.11-rc1 import. I'd have to go back and double check to be 100% on that.
It happens with every module. If I'd need other tools these messages are confusing. I didn't try "vmalloc=..." as I think module loading wouldn't be "disabled" in such a way by default...It happens also for any significant memory pressure.
...including significant use of dd, mounting of ricerfs partitions, mounting of swap, etc.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: bal instruction in gcc 3.x, Pete Popov|
|Next by Date:||Re: Updating RTC with date command, Jan-Benedict Glaw|
|Previous by Thread:||Re: module loading on 64-bit kernel, Thiemo Seufer|
|Next by Thread:||Re: module loading on 64-bit kernel, Ralf Baechle|
|Indexes:||[Date] [Thread] [Top] [All Lists]|