headers
Florian Schmitt | 1 Dec 2002 08:02
Picon

Re: module loading 2.5.50 + nvidia patch


> With
> insmod, I can load modules, but I'd like that the kernel do it
> automatically such as in 2.4. In kernel config, the neccessary options
> for this are set. What am I missing, or how has the kernel configuration
> changed? 

I ran into the same problem yesterday. If I remember correctly (I don't have 
access to that computer right now), Rusty's new modutils look for 
/etc/modutils.conf instead of /etc/modules.conf... A softlink to modules.conf 
fixed that for me.

Regards,
  Flo
Permalink | Reply | 0 comments |
headers
Sander Smeenk | 1 Dec 2002 01:00

2.5.50 results

Hi,

After a little struggle with 2.5.50 and it's new modules system I got
things running on my Toshiba laptop.

Now there's a couple of things:

1) I get these messages while typing just normal stuff on my keyboard:
| Dec  1 00:28:00 misery kernel: atkbd.c: Unknown key (set 2, scancode 0x96, on isa0060/serio0) pressed.
| Dec  1 00:28:10 misery kernel: atkbd.c: Unknown key (set 2, scancode 0xae, on isa0060/serio0) pressed.
| Dec  1 00:28:13 misery kernel: atkbd.c: Unknown key (set 2, scancode 0x91, on isa0060/serio0) pressed.
| Dec  1 00:28:23 misery kernel: atkbd.c: Unknown key (set 2, scancode 0xa3, on isa0060/serio0) pressed.
| Dec  1 00:28:38 misery kernel: atkbd.c: Unknown key (set 2, scancode 0xa6, on isa0060/serio0) pressed.
I'm not doing anything funny at that moment, just typing commands.
Messaged appear at a random interval and at random keys.

2) Apparently when one boots 2.5.50 without having the newest
module-init-tools, the kernel panics while doing a shutdown.
Unfortunately I can't give much more information, because now I have the
new module-init-tools, and when it happened, all I could see was the
last bit of the panic.

Lastly, while loading modules:

| [0:57] [root <at> misery:~] # modprobe trident
| WARNING: Error inserting ac97_codec
| (/lib/modules/2.5.50/kernel/ac97_codec.o): Invalid module format
| FATAL: Error inserting trident (/lib/modules/2.5.50/kernel/trident.o):
| Unknown symbol in module
| zsh: 456 exit 1     modprobe trident
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matt Reppert | 1 Dec 2002 01:12

[PATCH] Unsafe MODULE_ usage in crc32.c

Hi,

Okay, I know, it's just a library module, doesn't need to ever be unloaded
anyway. But error noise in dmesg annoys me, hence this patch.

Matt

  Convert CRC32 to try_module_get; fixes an unsafe usage that
  prevents unloading.

 lib/crc32.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletion(-)

--- linux-2.5.50/lib/crc32.c~crc32-unsafe	2002-11-30 05:31:19.000000000 -0600
+++ linux-2.5.50-arashi/lib/crc32.c	2002-11-30 05:36:17.000000000 -0600
 <at>  <at>  -551,7 +551,10  <at>  <at>  static int __init init_crc32(void)
 	rc1 = crc32init_le();
 	rc2 = crc32init_be();
 	rc = rc1 || rc2;
-	if (!rc) MOD_INC_USE_COUNT;
+	if (!rc) {
+		if (!try_module_get(THIS_MODULE))
+			rc = -1;
+	}
 	return rc;
 }

[patch ends]
Permalink | Reply | 3 comments |
headers
Thorbjørn Lind | 1 Dec 2002 01:13

quirk_via_ioapic

Performs the following code when io_apic is enabled.

tmp = 0x1f;
pci_write_config_byte (dev, 0x58, tmp);

Which happens to be a bad idea(tm) on my Tyan Tiger 230T (Via 691+686 chipset) because it will cause
one of the upper IRQ lines (>15) to trigger about 10M times / minute. In this case it's the ide
controller, but is seen on other devices too.

Things sortof work w/o the quirk.
What is going on here ? :)

leeloo:~# cat /proc/interrupts...
 17:          0   IO-APIC-level  Ensoniq AudioPCI
 19:         12   IO-APIC-level  ide2
...

Pretending to use the quirk....
leeloo:~# pcitweak -w 0:7:0 -b 0x58 0x1f

And just a few seconds later...
leeloo:~# cat /proc/interrupts
...
 17:          0   IO-APIC-level  Ensoniq AudioPCI
 19:    2007685   IO-APIC-level  ide2
Permalink | Reply | 0 comments |
headers
Petr Vandrovec | 1 Dec 2002 01:25
Picon
Picon

Re: [PATCH] Unsafe MODULE_ usage in crc32.c

On Sat, Nov 30, 2002 at 06:12:24PM -0600, Matt Reppert wrote:
> Hi,
> 
> Okay, I know, it's just a library module, doesn't need to ever be unloaded
> anyway. But error noise in dmesg annoys me, hence this patch.

Better asking Rusty, why module cannot call MOD_INC_USE_COUNT on itself
during its own init... I'm pretty sure that crc32 module knows that nobody
can unload it at this point: it is executing its own code, isn't it?
					Petr Vandrovec
					vandrove <at> vc.cvut.cz

> Matt
> 
>   Convert CRC32 to try_module_get; fixes an unsafe usage that
>   prevents unloading.
> 
> 
>  lib/crc32.c |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletion(-)
> 
> --- linux-2.5.50/lib/crc32.c~crc32-unsafe	2002-11-30 05:31:19.000000000 -0600
> +++ linux-2.5.50-arashi/lib/crc32.c	2002-11-30 05:36:17.000000000 -0600
>  <at>  <at>  -551,7 +551,10  <at>  <at>  static int __init init_crc32(void)
>  	rc1 = crc32init_le();
>  	rc2 = crc32init_be();
>  	rc = rc1 || rc2;
> -	if (!rc) MOD_INC_USE_COUNT;
> +	if (!rc) {
> +		if (!try_module_get(THIS_MODULE))
(Continue reading)

Permalink | Reply | 0 comments |
headers
Zwane Mwaikambo | 1 Dec 2002 01:45

Re: [CFT] Serial double initialisation

On Sat, 30 Nov 2002, Russell King wrote:

> A while ago, Alan reported to me a double-initialisation bug between the
> ISA init and PNP initialisation of serial ports.
>
> Since then, Alan integrated a patch I sent him into -ac, and as yet I
> haven't heard any feedback.  Since I don't have the PNP hardware to be
> able to test this, I'm not putting it into Linus' tree until I hear some
> success.
>
> So, if people are using 2.5.50 with PNP support enabled, and if you are
> seeing two "ttyS0" lines during the kernel boot messages, please apply
> this patch and confirm to me that it correctly reports one ttyS0 message.

Thanks for checking this out, the double init only comes when you have
CONFIG_PNPBIOS enabled, but CONFIG_ISAPNP alone is fine. I tested the
patch with both and it does indeed fix the problem.

Cheers,
	Zwane

--

-- 
function.linuxpower.ca
Permalink | Reply | 0 comments |
headers
Sander Smeenk | 1 Dec 2002 01:51

Re: 2.5.50 results

Quoting Sander Smeenk (ssmeenk <at> freshdot.net):

I have FUP'ing to myself, but sometimes you just have to.

> 1) I get these messages while typing just normal stuff on my keyboard:
> | Dec  1 00:28:00 misery kernel: atkbd.c: Unknown key (set 2, scancode 0x96, on isa0060/serio0) pressed.
> | Dec  1 00:28:10 misery kernel: atkbd.c: Unknown key (set 2, scancode 0xae, on isa0060/serio0) pressed.
> | Dec  1 00:28:13 misery kernel: atkbd.c: Unknown key (set 2, scancode 0x91, on isa0060/serio0) pressed.
> | Dec  1 00:28:23 misery kernel: atkbd.c: Unknown key (set 2, scancode 0xa3, on isa0060/serio0) pressed.
> | Dec  1 00:28:38 misery kernel: atkbd.c: Unknown key (set 2, scancode 0xa6, on isa0060/serio0) pressed.
> I'm not doing anything funny at that moment, just typing commands.
> Messaged appear at a random interval and at random keys.

It seems this only occurs when I type "real fast". If I do 2 keys a second
the messages won't appear. Maybe this might have to do with Toshiba's
key-repeat rate problem, as discussed with Linus, Alan, various X11
coders and this list as a whole earlier. (More info -> google news ->
'toshiba repeating keys')

> 2) Apparently when one boots 2.5.50 without having the newest
> module-init-tools, the kernel panics while doing a shutdown.
> Unfortunately I can't give much more information, because now I have the
> new module-init-tools, and when it happened, all I could see was the
> last bit of the panic.

Ok, just happened again after I tried shutdown -r'ing my laptop.
This time there's more information on the screen, and I Hope This Helps:

<typeovermode>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dave Jones | 1 Dec 2002 01:59
Picon
Favicon

Re: Linux 2.4.20-ac1

On Sat, Nov 30, 2002 at 02:47:16AM +0200, Jarno Paananen wrote:

 > > Linux 2.4.20-ac1
 > > o	VIA KT400 AGP support				(Nicolas Mailhot)
 > This doesn't seem to work on my setup, dmesg says:
 > agpgart: unable to determine aperture size.
 > My machine has A7V8X motherboard with KT400 chipset and Radeon 9700
 > Pro running AGP 8X with sidebanding and fast-writes in Windows XP
 > so the setup itself should be ok.
 > I checked the code out a bit and the register supposed to be
 > containing the aperture size contains 0x1b while the values in the
 > array it is tested against are 0, 128, 192, 224, 240, 248 and 252
 > (192 being 64 megs)... Could this be caused by AGP 3.0 or something
 > that VIA handles differently than before? Anything else I could
 > test or help get it to work?

I hadn't realised that was an AGP 3.0 chip. Its likely that we'll
need to change things to use different routines than the generic
ones if this is the case.  If it is the case, then it shouldn't be too
hard to figure out what to change, as long as VIA have the specs
available.. I'll dig around when I get back on Monday.

		Dave

--

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs
Permalink | Reply | 0 comments |
headers
J.A. Magallon | 1 Dec 2002 02:55
Picon

Re: [PATCHSET] Linux 2.4.20-jam0


On 2002.11.30 Andrea Arcangeli wrote:
>On Sat, Nov 30, 2002 at 12:38:07AM +0100, J.A. Magallon wrote:
>> - reverted the fast-pte part of -aa. Still have to try again
>>   to see if it is more stable now.
>
>AFIK this was reproduced by Srihari on nohighmem so it must be that
>somebody is calling pgd_free_fast on a pgd that cannot be re-used.
>Can you try this patch on top of 2.4.20rc2aa1? (or jam0 after backing
>out the fast-pte removal that would otherwise forbid the debugging check
>to trigger)
>

I suppose this will be useless (tainted ;))
BTW, what does mean the symbol address mismatch ?

ksymoops 2.4.8 on i686 2.4.20-jam1.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.20-jam1/ (default)
     -m /boot/System.map-2.4.20-jam1 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alan Cox | 1 Dec 2002 03:01
Picon
Favicon

Re: Linux 2.4.20-ac1

> >  	drive->using_dma = 1;
> >  	ide_toggle_bounce(drive, 1);
> > +	printk(KERN_INFO "%s: DMA enabled\n", drive->name);
> >  	return HWIF(drive)->ide_dma_host_on(drive);
> >  }
> 
> with the above applied:

Better I think that via drivers turn DMA off -quietly-
Permalink | Reply | 1 comment |

Gmane