runaway modprobe loop

[Grant Edwards <grante@visi.com>]

I compiled 2.2.20 with VESA frame buffer support enabled, and
now I have a runaway modprobe loop:

apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13)
apm: disabled on user request.                        
 hdd: hdd1                    
  hdd: hdd1
  VFS: Mounted root (ext2 filesystem) readonly.
  Freeing unused kernel memory: 164k freed     
  INIT: version 2.84 booting              
  kmod: runaway modprobe loop assumed and stopped
  insmod: modprobekmod: runaway modprobe loop assumed and stopped
  : cannot create kmod: runaway modprobe loop assumed and stopped
  /var/log/ksymoopkmod: runaway modprobe loop assumed and stopped
  s/20020410.log Read-only file system                           
  insmod: /lib/modules/2.2.20/misc/unix.o: cannot create /var/log/ksymoops/20020410135256.ksyms Read-only file system
insmod: /lib/modules/2.2.20/misc/unix.o: insmod net-pf-1 failed
insmod: /lib/modules/2.2.20/misc/unix.o: cannot create /var/log/ksymoops/20020410.log Read-only file system
insmod: modprobe: cannot create /var/log/ksymoops/20020410.log Read-only file system

[the last few lines repeat forever]

I'm going to try again with unix and pf_packet compiled into
the kernel, but I can't figure out why enabling VESA FB support
caused this.  Any hints?

-- 
Grant Edwards
grante@visi.com


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org