Re: goodbye
[EMAIL PROTECTED] wrote: > > Joseph Carter <[EMAIL PROTECTED]> wrote: > > >Let's see, ORBS takes out the ISP route, DUL takes out the direct one. Is > >it any wonder people are hostile toward those two lists? > > Exactly. I hate spam, but I hate ORBS and DUL even more. If I'm going to get > the shaft, I'd rather it be from the "bad guys" (spammers) than from > self-appointed net.cops. > > Wayne > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ Amen!!! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: goodbye
[EMAIL PROTECTED] wrote: Joseph Carter [EMAIL PROTECTED] wrote: Let's see, ORBS takes out the ISP route, DUL takes out the direct one. Is it any wonder people are hostile toward those two lists? Exactly. I hate spam, but I hate ORBS and DUL even more. If I'm going to get the shaft, I'd rather it be from the "bad guys" (spammers) than from self-appointed net.cops. Wayne - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ Amen!!! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: uninteruptable sleep
That happened to me with 2.4.2-ac28 when I tried using DRM. I also got the following messages in syslog. /var/log/messages.1:Mar 31 12:15:04 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:04 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:15 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:15 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:16 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:40 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:18 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:31 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:32 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:45 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:45 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:48 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:49 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed!/ So I turned off DRI in X 4.0.3 HTH Steve Trevor Nichols wrote: > > Hi all, > > Since upgrading to the latest stable (2.4.3) kernel, I've noticed that > randomly some processes are going into an uninteruptable sleep and not > waking up at all. > > It's happened to nautilus and today just happened to mozilla also. > Another common related problem is the load averages go up to n + "normal" > where n is the number of processes that have gone uninteruptable sleep. > This is making me think it's a kernel related problem. > > I had one time where nautilus with 9 [presumably forked] processes of > itself go this way, causing load averages to go 9+, however the system > doesn't appear to be straining or strugling under that much load. > > The previous kernel version that I was using (2.4.1) did not have this > problem. > > One last thing, if this turns out to be a non-kernel problem, the > processes that *do* get stuck, are unkillable - even by root with SIGKILL. > Is there any way for it to be able to? :) So far I have to reboot each > time it happens. > > Best regards, > Trevor Nichols. > > ps please CC replies to my address. thanks. > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: uninteruptable sleep
That happened to me with 2.4.2-ac28 when I tried using DRM. I also got the following messages in syslog. /var/log/messages.1:Mar 31 12:15:04 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:04 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:15 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:15 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:16 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:15:40 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:18 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:31 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:32 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:45 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:45 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:48 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! /var/log/messages.1:Mar 31 12:16:49 joker kernel: [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed!/ So I turned off DRI in X 4.0.3 HTH Steve Trevor Nichols wrote: Hi all, Since upgrading to the latest stable (2.4.3) kernel, I've noticed that randomly some processes are going into an uninteruptable sleep and not waking up at all. It's happened to nautilus and today just happened to mozilla also. Another common related problem is the load averages go up to n + "normal" where n is the number of processes that have gone uninteruptable sleep. This is making me think it's a kernel related problem. I had one time where nautilus with 9 [presumably forked] processes of itself go this way, causing load averages to go 9+, however the system doesn't appear to be straining or strugling under that much load. The previous kernel version that I was using (2.4.1) did not have this problem. One last thing, if this turns out to be a non-kernel problem, the processes that *do* get stuck, are unkillable - even by root with SIGKILL. Is there any way for it to be able to? :) So far I have to reboot each time it happens. Best regards, Trevor Nichols. ps please CC replies to my address. thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
MTRR on AMD THUNDERBIRD
Anyone know the status of mtrr the AMD Thunderbird? It does not seem to work for me anymore. cat /proc/mtrr reg00: base=0x ( 0MB), size=16711936MB: write-back, count=1 joker:/ # echo "base=0xd400 size=0x200 type=write-combining" >| /proc/mtrr joker:/ # cat /proc/mtrr reg00: base=0x ( 0MB), size=16711936MB: write-back, count=1 Linux version 2.4.2-ac18 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #5 Mon Mar 19 17:42:56 EST 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 0001 @ 000f (reserved) BIOS-e820: 0fef @ 0010 (usable) BIOS-e820: 3000 @ 0fff (ACPI NVS) BIOS-e820: d000 @ 0fff3000 (ACPI data) BIOS-e820: 0001 @ (reserved) On node 0 totalpages: 65536 zone(0): 4096 pages. zone(1): 61440 pages. zone(2): 0 pages. Kernel command line: auto BOOT_IMAGE=l-2.4.2ac18pnp ro root=1601 ramdisk=0 mem=256M Initializing CPU#0 Detected 800.056 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 1595.80 BogoMIPS Memory: 255176k/262144k available (1327k kernel code, 6580k reserved, 422k data, 224k init, 0k highmem) Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes) Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) VFS: Diskquotas version dquot_6.5.0 initialized CPU: Before vendor init, caps: 0183f9ff c1c7f9ff , vendor = 2 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After vendor init, caps: 0183f9ff c1c7f9ff CPU: After generic, caps: 0183f9ff c1c7f9ff CPU: Common caps: 0183f9ff c1c7f9ff CPU: AMD Athlon(tm) Processor stepping 02 Enabling fast FPU save and restore... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel PCI: PCI BIOS revision 2.10 entry at 0xfb430, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Bus master Pipeline request disabled PCI: Disabled enhanced CPU to PCI writes PCI: Bursting cornercase bug worked around PCI: Post Write Fail set to Retry PCI: Using IRQ router VIA [1106/0686] at 00:07.0 isapnp: Scanning for PnP cards... isapnp: Card 'SMC EtherEZ (8416)' isapnp: 1 Plug & Play card detected total Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd v1.8 parport_pc: Strange, can't probe Via 686A parallel port: io=0x378, irq=7, dma=-1parport0: PC-style at 0x378 [PCSPP(,...)] also *** any ideas about the above message * i2c-core.o: i2c core module i2c-dev.o: i2c /dev entries driver module i2c-core.o: driver i2c-dev dummy driver registered. i2c-algo-bit.o: i2c bit algorithm module pty: 256 Unix98 ptys configured lp0: using parport0 (polling). block: queued sectors max/low 169546kB/56515kB, 512 slots per queue Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 16 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1 ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA hda: JTS CORPORATION CHAMPION MODEL C3200-2A, ATA DISK drive hdb: Maxtor 91366U4, ATA DISK drive hdc: Maxtor 53073H4, ATA DISK drive hdd: ATAPI 52X CDROM, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: 6306048 sectors (3229 MB) w/512KiB Cache, CHS=6256/16/63, DMA hdb: 26684784 sectors (13663 MB) w/2048KiB Cache, CHS=1661/255/63, UDMA(66) hdc: 60030432 sectors (30736 MB) w/2048KiB Cache, CHS=59554/16/63, UDMA(66) hdd: ATAPI 48X CD-ROM drive, 128kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.12 Partition check: hda: hda1 hda2 hda3 hda4 hdb: hdb1 hdb2 hdb3 hdc: hdc1 hdc2 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 smc-ultra.c: ISAPnP reports SMC EtherEZ (8416) at i/o 0x240, irq 5. smc-ultra.c:v2.02 2/3/98 Donald Becker ([EMAIL PROTECTED]) eth0: SMC EtherEZ at 0x240, 00 E0 29 03 E5 92,assigned IRQ 5 memory 0xc8000-0xc9fff. SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256). loop: loaded (max 8 devices) Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a
MTRR on AMD THUNDERBIRD
Anyone know the status of mtrr the AMD Thunderbird? It does not seem to work for me anymore. cat /proc/mtrr reg00: base=0x ( 0MB), size=16711936MB: write-back, count=1 joker:/ # echo "base=0xd400 size=0x200 type=write-combining" | /proc/mtrr joker:/ # cat /proc/mtrr reg00: base=0x ( 0MB), size=16711936MB: write-back, count=1 Linux version 2.4.2-ac18 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #5 Mon Mar 19 17:42:56 EST 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 0001 @ 000f (reserved) BIOS-e820: 0fef @ 0010 (usable) BIOS-e820: 3000 @ 0fff (ACPI NVS) BIOS-e820: d000 @ 0fff3000 (ACPI data) BIOS-e820: 0001 @ (reserved) On node 0 totalpages: 65536 zone(0): 4096 pages. zone(1): 61440 pages. zone(2): 0 pages. Kernel command line: auto BOOT_IMAGE=l-2.4.2ac18pnp ro root=1601 ramdisk=0 mem=256M Initializing CPU#0 Detected 800.056 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 1595.80 BogoMIPS Memory: 255176k/262144k available (1327k kernel code, 6580k reserved, 422k data, 224k init, 0k highmem) Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes) Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) VFS: Diskquotas version dquot_6.5.0 initialized CPU: Before vendor init, caps: 0183f9ff c1c7f9ff , vendor = 2 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After vendor init, caps: 0183f9ff c1c7f9ff CPU: After generic, caps: 0183f9ff c1c7f9ff CPU: Common caps: 0183f9ff c1c7f9ff CPU: AMD Athlon(tm) Processor stepping 02 Enabling fast FPU save and restore... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel PCI: PCI BIOS revision 2.10 entry at 0xfb430, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Bus master Pipeline request disabled PCI: Disabled enhanced CPU to PCI writes PCI: Bursting cornercase bug worked around PCI: Post Write Fail set to Retry PCI: Using IRQ router VIA [1106/0686] at 00:07.0 isapnp: Scanning for PnP cards... isapnp: Card 'SMC EtherEZ (8416)' isapnp: 1 Plug Play card detected total Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd v1.8 parport_pc: Strange, can't probe Via 686A parallel port: io=0x378, irq=7, dma=-1parport0: PC-style at 0x378 [PCSPP(,...)] also *** any ideas about the above message * i2c-core.o: i2c core module i2c-dev.o: i2c /dev entries driver module i2c-core.o: driver i2c-dev dummy driver registered. i2c-algo-bit.o: i2c bit algorithm module pty: 256 Unix98 ptys configured lp0: using parport0 (polling). block: queued sectors max/low 169546kB/56515kB, 512 slots per queue Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 16 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1 ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA hda: JTS CORPORATION CHAMPION MODEL C3200-2A, ATA DISK drive hdb: Maxtor 91366U4, ATA DISK drive hdc: Maxtor 53073H4, ATA DISK drive hdd: ATAPI 52X CDROM, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: 6306048 sectors (3229 MB) w/512KiB Cache, CHS=6256/16/63, DMA hdb: 26684784 sectors (13663 MB) w/2048KiB Cache, CHS=1661/255/63, UDMA(66) hdc: 60030432 sectors (30736 MB) w/2048KiB Cache, CHS=59554/16/63, UDMA(66) hdd: ATAPI 48X CD-ROM drive, 128kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.12 Partition check: hda: hda1 hda2 hda3 hda4 hdb: hdb1 hdb2 hdb3 hdc: hdc1 hdc2 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 smc-ultra.c: ISAPnP reports SMC EtherEZ (8416) at i/o 0x240, irq 5. smc-ultra.c:v2.02 2/3/98 Donald Becker ([EMAIL PROTECTED]) eth0: SMC EtherEZ at 0x240, 00 E0 29 03 E5 92,assigned IRQ 5 memory 0xc8000-0xc9fff. SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256). loop: loaded (max 8 devices) Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a
Re: [PATCH] Prevent OOM from killing init
Alan Cox wrote: > > > You don't beleve me if I tell you: DOS extender and JVM (Java Virtual > > Machine) > > The JVM doesnt actually. The JVM will itself spontaenously explode in real > life when out of memory. Maybe the JVM on a DOS extender 8) > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ Back in the early nineties I was working with 18 developers on a Data General Aviion running DGUX. The system had only 16mb of memory and 600mb of disk. We were all continuously going thru the edit, compile, debug steps developing as large Computer Aided Dispatch System. Never did this system with its limited resources crash, or randomly start killing user or system processes. My $.02. Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RTNL assert
Andrew Morton wrote: > > "Stephen E. Clark" wrote: > > > > When I configure in Tunneling I get the following error message. Is this > > normal? This with 2.4test9pre5 > > > > GRE over IPv4 tunneling driver > > RTNL: assertion failed at devinet.c(775):inetdev_event > > The rtnetlink lock needs to be taken around > register_netdevice(). There should be a function > which does these three common steps, but there isn't. > > --- linux-2.4.0-test10-pre5/net/ipv4/ip_gre.c Sat Sep 9 16:19:30 2000 > +++ linux-akpm/net/ipv4/ip_gre.cSat Oct 28 21:44:23 2000 > @@ -1266,7 +1266,9 @@ > #ifdef MODULE > register_netdev(_fb_tunnel_dev); > #else > + rtnl_lock(); > register_netdevice(_fb_tunnel_dev); > + rtnl_unlock(); > #endif > > inet_add_protocol(_protocol); > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ Thanks Andrew, I also get the same error if I try to configure in normal IPV4 tunneling. I guess it needs the same kind of patch. Oct 27 14:46:59 joker kernel: IPv4 over IPv4 tunneling driver Oct 27 14:46:59 joker kernel: RTNL: assertion failed at devinet.c(775):inetdev_event Oct 27 14:46:59 joker kernel: GRE over IPv4 tunneling driver Oct 27 14:46:59 joker kernel: RTNL: assertion failed at devinet.c(775):inetdev_event Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RTNL assert
When I configure in Tunneling I get the following error message. Is this normal? This with 2.4test9pre5 GRE over IPv4 tunneling driver RTNL: assertion failed at devinet.c(775):inetdev_event - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RTNL assert
When I configure in Tunneling I get the following error message. Is this normal? GRE over IPv4 tunneling driver RTNL: assertion failed at devinet.c(775):inetdev_event - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RTNL assert
When I configure in Tunneling I get the following error message. Is this normal? GRE over IPv4 tunneling driver RTNL: assertion failed at devinet.c(775):inetdev_event - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RTNL assert
When I configure in Tunneling I get the following error message. Is this normal? This with 2.4test9pre5 GRE over IPv4 tunneling driver RTNL: assertion failed at devinet.c(775):inetdev_event - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: What is up with Redhat 7.0?
Maybe this thread should be on the redhat list not the kernel list. Alec Smith wrote: > > Date: Fri, 29 Sep 2000 16:58:22 -0400 (EDT) > From: Alec Smith <[EMAIL PROTECTED]> > To: David M. Rector <[EMAIL PROTECTED]> > Subject: Re: What is up with Redhat 7.0? > > Congratulations, you got further than I did. I couldn't even get that > disaster known as RH7.0 to even install. It died with some error about not > being able to detect free disk space after formatting the paritions... Or > something like that. RedHack 6.2 installed fine on the same machine. > > I'll stick to Debian -- It might be a bit outdated at times, but Debian > "just works." Maybe RedHat could take some hints from the Debian guys. > > On Fri, 29 Sep 2000, David M. Rector wrote: > > > > > Has anyone tried Redhat 7.0 yet? What a mess. > > > > 1) It would not compile stock kernels out of the box. (ends at > > compress.S) with a fatal error. > > > > 2) Trying to compile the kernel source for 2.2.16 that comes with the > > redhat disk (which is very different than the stock 2.2.16) causes my > > system come to a screeching halt, no messages, no errors, crashed solid. > > > > I have a Supermicro PIIIDME motherboard with a GeForce2 graphics card, > > adaptec 2940UW scsi and seagate UW 9 gig scsi drive. > > > > Dave Rector > > *:^) > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to [EMAIL PROTECTED] > > Please read the FAQ at http://www.tux.org/lkml/ > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: What is up with Redhat 7.0?
Maybe this thread should be on the redhat list not the kernel list. Alec Smith wrote: Date: Fri, 29 Sep 2000 16:58:22 -0400 (EDT) From: Alec Smith [EMAIL PROTECTED] To: David M. Rector [EMAIL PROTECTED] Subject: Re: What is up with Redhat 7.0? Congratulations, you got further than I did. I couldn't even get that disaster known as RH7.0 to even install. It died with some error about not being able to detect free disk space after formatting the paritions... Or something like that. RedHack 6.2 installed fine on the same machine. I'll stick to Debian -- It might be a bit outdated at times, but Debian "just works." Maybe RedHat could take some hints from the Debian guys. On Fri, 29 Sep 2000, David M. Rector wrote: Has anyone tried Redhat 7.0 yet? What a mess. 1) It would not compile stock kernels out of the box. (ends at compress.S) with a fatal error. 2) Trying to compile the kernel source for 2.2.16 that comes with the redhat disk (which is very different than the stock 2.2.16) causes my system come to a screeching halt, no messages, no errors, crashed solid. I have a Supermicro PIIIDME motherboard with a GeForce2 graphics card, adaptec 2940UW scsi and seagate UW 9 gig scsi drive. Dave Rector *:^) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ip forwarding/tunneling for WIN PPTP broken in 2.2.18pre9?
Alan, Sorry for the noise I must be getting senile in my old age. I forgot I has patched 2.2.14 to support the vpn masquerading. Thanks for your indulgence and response. Steve Alan Cox wrote: > > > I had been using 2.2.14pre16 to forward Win PPTP from my winblows > > machine to our Corp Business network. > > With some kind of PPTP package on top of Linux ? > > > I upgraded to 2.2.18pre9 and used make oldconfig using my .config file > > from my 2.2.14 directory. > > I can no longer log into our Corp network using my Linux system as > > ip-forwarder for my winblows machine using VPN. > > > > I rebooted 2.2.14 and things worked fine. > > > > Am I missing something? Is there anything special I need to do for > > 2.2.18? > > There shouldnt be - do 2.2.16 or 2.2.17 work ? > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ip forwarding/tunneling for WIN PPTP broken in 2.2.18pre9?
Juan, I had been using 2.2.14pre16 to forward Win PPTP from my winblows machine to our Corp Business network. I upgraded to 2.2.18pre9 and used make oldconfig using my .config file from my 2.2.14 directory. I can no longer log into our Corp network using my Linux system as ip-forwarder for my winblows machine using VPN. I rebooted 2.2.14 and things worked fine. Am I missing something? Is there anything special I need to do for 2.2.18? Any help would be greatly appreciated. Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ip forwarding/tunneling for WIN PPTP broken in 2.2.18pre9?
Alan, Sorry for the noise I must be getting senile in my old age. I forgot I has patched 2.2.14 to support the vpn masquerading. Thanks for your indulgence and response. Steve Alan Cox wrote: I had been using 2.2.14pre16 to forward Win PPTP from my winblows machine to our Corp Business network. With some kind of PPTP package on top of Linux ? I upgraded to 2.2.18pre9 and used make oldconfig using my .config file from my 2.2.14 directory. I can no longer log into our Corp network using my Linux system as ip-forwarder for my winblows machine using VPN. I rebooted 2.2.14 and things worked fine. Am I missing something? Is there anything special I need to do for 2.2.18? There shouldnt be - do 2.2.16 or 2.2.17 work ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ip forwarding/tunneling for WIN PPTP broken in 2.2.18pre9?
Linux kernel, I had been using 2.2.14pre16 to forward Win PPTP from my winblows machine to our Corp Business network. I upgraded to 2.2.18pre9 and used make oldconfig using my .config file from my 2.2.14 directory. I can no longer log into our Corp network using my Linux system as ip-forwarder for my winblows machine using VPN. I rebooted 2.2.14 and things worked fine. Am I missing something? Is there anything special I need to do for 2.2.18? Any help would be greatly appreciated. Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ip forwarding/tunneling for WIN PPTP broken in 2.2.18pre9?
Linux kernel, I had been using 2.2.14pre16 to forward Win PPTP from my winblows machine to our Corp Business network. I upgraded to 2.2.18pre9 and used make oldconfig using my .config file from my 2.2.14 directory. I can no longer log into our Corp network using my Linux system as ip-forwarder for my winblows machine using VPN. I rebooted 2.2.14 and things worked fine. Am I missing something? Is there anything special I need to do for 2.2.18? Any help would be greatly appreciated. Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
attempt to access beyond end of device
Help. I am getting the above error when trying to build an Oracle Database. I have tried 2.2.14 and 2.2.18pre8 with the same results. I am putting the DB on /usr8 which from the df -m command should have plenty of room. Is this a kernel problem or a problem on my part? Below is part of my /var/log/messages file which shows my configuration as well as the errors. How do I relate dev 08:02 to my actual physical devices. I have 2 ide drives and 3 scsi drives. At the end of /var/log/messages I have appended my /etc/fstab, the output from a df -m comand and fdisk output for each drive. Any help in pointing to the problem would be greatly appreciated. Thanks Steve excerpts from /var/log/messages: Sep 15 19:01:54 joker syslogd 1.3-3: restart. Sep 15 19:01:55 joker syslog: syslogd startup succeeded Sep 15 19:01:55 joker syslog: klogd startup succeeded Sep 15 19:01:55 joker kernel: klogd 1.3-3, log source = /proc/kmsg started. Sep 15 19:01:55 joker kernel: Inspecting /boot/System.map-2.2.18pre8 Sep 15 19:01:55 joker kernel: Loaded 8573 symbols from /boot/System.map-2.2.18pre8. Sep 15 19:01:55 joker kernel: Symbols match kernel version 2.2.18. Sep 15 19:01:55 joker kernel: No module symbols loaded. Sep 15 19:01:55 joker kernel: Linux version 2.2.18pre8 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 Fri Sep 15 22:55:43 EDT 2000 Sep 15 19:01:55 joker kernel: Detected 451030 kHz processor. Sep 15 19:01:55 joker kernel: Console: colour VGA+ 80x25 Sep 15 19:01:55 joker kernel: Calibrating delay loop... 897.84 BogoMIPS Sep 15 19:01:55 joker kernel: Memory: 127452k/131072k available (1464k kernel code, 412k reserved, 1680k data, 64k init) Sep 15 19:01:55 joker kernel: Dentry hash table entries: 16384 (order 5, 128k) Sep 15 19:01:55 joker kernel: Buffer cache hash table entries: 131072 (order 7, 512k) Sep 15 19:01:55 joker kernel: Page cache hash table entries: 32768 (order 5, 128k) Sep 15 19:01:55 joker kernel: VFS: Diskquotas version dquot_6.4.0 initialized Sep 15 19:01:55 joker kernel: CPU: L1 I Cache: 32K L1 D Cache: 32K Sep 15 19:01:55 joker kernel: CPU: AMD-K6(tm) 3D processor stepping 0c Sep 15 19:01:55 joker kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Sep 15 19:01:55 joker kernel: Checking 'hlt' instruction... OK. Sep 15 19:01:55 joker kernel: POSIX conformance testing by UNIFIX Sep 15 19:01:55 joker kernel: mtrr: v1.35a (19990819) Richard Gooch ([EMAIL PROTECTED]) Sep 15 19:01:55 joker kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb220 Sep 15 19:01:55 joker kernel: PCI: Using configuration type 1 Sep 15 19:01:55 joker kernel: PCI: Probing PCI hardware Sep 15 19:01:55 joker kernel: PCI: 00:38 [1106/0586]: Work around ISA DMA hangs (00) Sep 15 19:01:55 joker kernel: Activating ISA DMA hang workarounds. Sep 15 19:01:55 joker kernel: Linux NET4.0 for Linux 2.2 Sep 15 19:01:55 joker kernel: Based upon Swansea University Computer Society NET3.039 Sep 15 19:01:55 joker kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. Sep 15 19:01:55 joker kernel: NET4: Linux TCP/IP 1.0 for NET4.0 Sep 15 19:01:55 joker kernel: IP Protocols: ICMP, UDP, TCP, IGMP Sep 15 19:01:55 joker kernel: TCP: Hash tables configured (ehash 131072 bhash 65536) Sep 15 19:01:55 joker kernel: IPv4 over IPv4 tunneling driver Sep 15 19:01:55 joker kernel: early initialization of device tunl0 is deferred Sep 15 19:01:55 joker kernel: GRE over IPv4 tunneling driver Sep 15 19:01:55 joker kernel: early initialization of device gre0 is deferred Sep 15 19:01:55 joker kernel: Initializing RT netlink socket Sep 15 19:01:55 joker kernel: Starting kswapd v 1.5 Sep 15 19:01:55 joker kernel: parport0: PC-style at 0x378 [SPP,PS2] Sep 15 19:01:55 joker kernel: Detected PS/2 Mouse Port. Sep 15 19:01:55 joker kernel: Serial driver version 4.27 with no serial options enabled Sep 15 19:01:55 joker kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A Sep 15 19:01:55 joker kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A Sep 15 19:01:55 joker kernel: pty: 256 Unix98 ptys configured Sep 15 19:01:55 joker kernel: lp0: using parport0 (polling). Sep 15 19:01:55 joker kernel: Real Time Clock Driver v1.09 Sep 15 19:01:55 joker kernel: RAM disk driver initialized: 16 RAM disks of 0K size Sep 15 19:01:55 joker kernel: loop: registered device at major 7 Sep 15 19:01:55 joker kernel: VP_IDE: IDE controller on PCI bus 00 dev 39 Sep 15 19:01:55 joker kernel: VP_IDE: not 100% native mode: will probe irqs later Sep 15 19:01:55 joker kernel: ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA Sep 15 19:01:55 joker kernel: ide0: VIA Bus-Master (U)DMA Timing Config Success Sep 15 19:01:55 joker kernel: ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio Sep 15 19:01:55 joker kernel: ide1: VIA Bus-Master (U)DMA Timing Config Success Sep 15 19:01:55 joker kernel: hda: JTS CORPORATION CHAMPION MODEL C3200-2A, ATA DISK drive Sep 15
attempt to access beyond end of device
Help. I am getting the above error when trying to build an Oracle Database. I have tried 2.2.14 and 2.2.18pre8 with the same results. I am putting the DB on /usr8 which from the df -m command should have plenty of room. Is this a kernel problem or a problem on my part? Below is part of my /var/log/messages file which shows my configuration as well as the errors. How do I relate dev 08:02 to my actual physical devices. I have 2 ide drives and 3 scsi drives. At the end of /var/log/messages I have appended my /etc/fstab, the output from a df -m comand and fdisk output for each drive. Any help in pointing to the problem would be greatly appreciated. Thanks Steve excerpts from /var/log/messages: Sep 15 19:01:54 joker syslogd 1.3-3: restart. Sep 15 19:01:55 joker syslog: syslogd startup succeeded Sep 15 19:01:55 joker syslog: klogd startup succeeded Sep 15 19:01:55 joker kernel: klogd 1.3-3, log source = /proc/kmsg started. Sep 15 19:01:55 joker kernel: Inspecting /boot/System.map-2.2.18pre8 Sep 15 19:01:55 joker kernel: Loaded 8573 symbols from /boot/System.map-2.2.18pre8. Sep 15 19:01:55 joker kernel: Symbols match kernel version 2.2.18. Sep 15 19:01:55 joker kernel: No module symbols loaded. Sep 15 19:01:55 joker kernel: Linux version 2.2.18pre8 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 Fri Sep 15 22:55:43 EDT 2000 Sep 15 19:01:55 joker kernel: Detected 451030 kHz processor. Sep 15 19:01:55 joker kernel: Console: colour VGA+ 80x25 Sep 15 19:01:55 joker kernel: Calibrating delay loop... 897.84 BogoMIPS Sep 15 19:01:55 joker kernel: Memory: 127452k/131072k available (1464k kernel code, 412k reserved, 1680k data, 64k init) Sep 15 19:01:55 joker kernel: Dentry hash table entries: 16384 (order 5, 128k) Sep 15 19:01:55 joker kernel: Buffer cache hash table entries: 131072 (order 7, 512k) Sep 15 19:01:55 joker kernel: Page cache hash table entries: 32768 (order 5, 128k) Sep 15 19:01:55 joker kernel: VFS: Diskquotas version dquot_6.4.0 initialized Sep 15 19:01:55 joker kernel: CPU: L1 I Cache: 32K L1 D Cache: 32K Sep 15 19:01:55 joker kernel: CPU: AMD-K6(tm) 3D processor stepping 0c Sep 15 19:01:55 joker kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Sep 15 19:01:55 joker kernel: Checking 'hlt' instruction... OK. Sep 15 19:01:55 joker kernel: POSIX conformance testing by UNIFIX Sep 15 19:01:55 joker kernel: mtrr: v1.35a (19990819) Richard Gooch ([EMAIL PROTECTED]) Sep 15 19:01:55 joker kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb220 Sep 15 19:01:55 joker kernel: PCI: Using configuration type 1 Sep 15 19:01:55 joker kernel: PCI: Probing PCI hardware Sep 15 19:01:55 joker kernel: PCI: 00:38 [1106/0586]: Work around ISA DMA hangs (00) Sep 15 19:01:55 joker kernel: Activating ISA DMA hang workarounds. Sep 15 19:01:55 joker kernel: Linux NET4.0 for Linux 2.2 Sep 15 19:01:55 joker kernel: Based upon Swansea University Computer Society NET3.039 Sep 15 19:01:55 joker kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. Sep 15 19:01:55 joker kernel: NET4: Linux TCP/IP 1.0 for NET4.0 Sep 15 19:01:55 joker kernel: IP Protocols: ICMP, UDP, TCP, IGMP Sep 15 19:01:55 joker kernel: TCP: Hash tables configured (ehash 131072 bhash 65536) Sep 15 19:01:55 joker kernel: IPv4 over IPv4 tunneling driver Sep 15 19:01:55 joker kernel: early initialization of device tunl0 is deferred Sep 15 19:01:55 joker kernel: GRE over IPv4 tunneling driver Sep 15 19:01:55 joker kernel: early initialization of device gre0 is deferred Sep 15 19:01:55 joker kernel: Initializing RT netlink socket Sep 15 19:01:55 joker kernel: Starting kswapd v 1.5 Sep 15 19:01:55 joker kernel: parport0: PC-style at 0x378 [SPP,PS2] Sep 15 19:01:55 joker kernel: Detected PS/2 Mouse Port. Sep 15 19:01:55 joker kernel: Serial driver version 4.27 with no serial options enabled Sep 15 19:01:55 joker kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A Sep 15 19:01:55 joker kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A Sep 15 19:01:55 joker kernel: pty: 256 Unix98 ptys configured Sep 15 19:01:55 joker kernel: lp0: using parport0 (polling). Sep 15 19:01:55 joker kernel: Real Time Clock Driver v1.09 Sep 15 19:01:55 joker kernel: RAM disk driver initialized: 16 RAM disks of 0K size Sep 15 19:01:55 joker kernel: loop: registered device at major 7 Sep 15 19:01:55 joker kernel: VP_IDE: IDE controller on PCI bus 00 dev 39 Sep 15 19:01:55 joker kernel: VP_IDE: not 100% native mode: will probe irqs later Sep 15 19:01:55 joker kernel: ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA Sep 15 19:01:55 joker kernel: ide0: VIA Bus-Master (U)DMA Timing Config Success Sep 15 19:01:55 joker kernel: ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio Sep 15 19:01:55 joker kernel: ide1: VIA Bus-Master (U)DMA Timing Config Success Sep 15 19:01:55 joker kernel: hda: JTS CORPORATION CHAMPION MODEL C3200-2A, ATA DISK drive Sep 15
Re: Availability of kdb
Linus Torvalds wrote: > > On Sat, 9 Sep 2000, Oliver Xymoron wrote: > > > > Tools are tools. They don't make better code. They make better code easier > > if used properly. > > I think you missed the point of my original reply completely. > > The _technical_ side of the tool in question is completely secondary. > > The social engineering side is very real, and immediate. ... > Linus > Then why don't we get rid of the compilers and assemblers and go back to the old way of doing it all - coding on the bare metal. Believe it or not at one time it was done this way. Imagine where we would be if everyone had said lets not invent tools to make ourselves more productive. My $.02 Steve Clark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Availability of kdb
Linus Torvalds wrote: On Sat, 9 Sep 2000, Oliver Xymoron wrote: Tools are tools. They don't make better code. They make better code easier if used properly. I think you missed the point of my original reply completely. The _technical_ side of the tool in question is completely secondary. The social engineering side is very real, and immediate. ... Linus Then why don't we get rid of the compilers and assemblers and go back to the old way of doing it all - coding on the bare metal. Believe it or not at one time it was done this way. Imagine where we would be if everyone had said lets not invent tools to make ourselves more productive. My $.02 Steve Clark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
