[PATCH] new bug report script

2001-01-06 Thread Matthias Juchem
d from /proc +# - runs the oops through ksymoops +# +# For notes view bottom of file + +use strict; +use FileHandle; +use IPC::Open2; + +# variables ########## + +# bug report +my $summary; my $description; my $keywords; +my $oops;

Re: Can I submit a bug report on this mailing list?

2001-01-05 Thread Rik van Riel
On Thu, 4 Jan 2001, Evan Thompson wrote: > I hear about the 2.4.0 release. I have, in my mailbox, many > messages titled "Re: And oh, btw...", BUT NO ORIGINAL MESSAGE! > What happened? Is my stupid mailserver selective or something? > > Anyways. My bug report is

Can I submit a bug report on this mailing list?

2001-01-04 Thread Evan Thompson
Alright. I hear about the 2.4.0 release. I have, in my mailbox, many messages titled "Re: And oh, btw...", BUT NO ORIGINAL MESSAGE! What happened? Is my stupid mailserver selective or something? Anyways. My bug report is: "[EMAIL PROTECTED] does not send me important mails tha

bug report in kernel-2.2.18: kernel cannot start

2001-01-01 Thread François Dupoux
this text is printed and make an infinite loop. Maybe I made an error, then I don't want to write to alan cox for the moment. But if this is a real important bug, I hope I can help to fix it by sumbitting this bug report. I think this is a bug from the kernel, because it work when I compil

Re: Bug Report : make modules_install seems to do a wrong call to depmod, using an unknow option "-F".

2000-12-05 Thread Mohammad A. Haque
Are you using the latest version of modutils? Delaporte Frédéric wrote: > > Hello. > > make modules_install seems to do a wrong call to depmod, using an unknow > option "-F". -- = Mohammad A. Haque

Bug Report : make modules_install seems to do a wrong call to depmod, using an unknow option "-F".

2000-12-05 Thread Delaporte Frédéric
Hello. make modules_install seems to do a wrong call to depmod, using an unknow option "-F". The line concerned in the Makefile is the 376th, colonne 47, character 44. Replacing "-F" by "-m" seems to solve the trouble (I've trust the depmod's man page). Here is this line : if [ -r System.ma

Re: BUG Report 2.4.0-test11-pre3: NMI Watchdoch detected LOCKUP atCPU[01]

2000-11-15 Thread James M
Gert Wollny wrote: > > Hello, > > i think it got it nailed, please try the attached patch (it is against > 11-pre4, but it should work against all test11). > > Explanation: > with test7-pre6 in the imm-module the new scsi - code was enabled (see > imm.h). > This causes the locking of the io_re

Re: BUG Report 2.4.0-test11-pre3: NMI Watchdoch detected LOCKUP atCPU[01]

2000-11-15 Thread Gert Wollny
Hello, i think it got it nailed, please try the attached patch (it is against 11-pre4, but it should work against all test11). Explanation: with test7-pre6 in the imm-module the new scsi - code was enabled (see imm.h). This causes the locking of the io_request_lock in scsi_register_host (scsi

Re: Bug-report: menuconfig

2000-11-13 Thread Peter Samuelson
Note for future reference: please report configuration and build bugs to [EMAIL PROTECTED] Speaking for myself, I am much more likely to notice it there, as the volume is a lot lower than l-k. (: [Stefan Sassenberg] > When I set CONFIG_MD_BOOT to 'y' and then set neither > CONFIG_MD_LINEAR nor

BUG Report 2.4.0-test11-pre3: NMI Watchdoch detected LOCKUP atCPU[01] (fwd)

2000-11-13 Thread Gert Wollny
A bug i had with kernel version 2.4.0-test9 is still there, but there are additional information: When parport_pc is compiled as module, and not already loaded "modprobe imm" yields the LOCKUP message (subject). The iomega-drive is usable after the modprobe and despite of the lockup. If parpo

Bug-report: menuconfig

2000-11-13 Thread Stefan Sassenberg
Hi, I think I detected a bug in Makefile's target "menuconfig". When I set CONFIG_MD_BOOT to 'y' and then set neither CONFIG_MD_LINEAR nor CONFIG_MD_STRIPED to 'y' then although CONFIG_MD_BOOT is not changeable anymore it is always set. This leads to an error when linking the kernel because of a

Re: [BUG REPORT] TCP/IP weirdness in 2.2.15

2000-11-06 Thread Thomas Pollinger
Hi Stephen >Let me see if I understand this correct: > > Client Router Server > > Linux Linux HPUXBad > WinNT Linux HPUXGood > HPUXLinux HPUXGood > >With all Linux box

Re: [BUG REPORT] TCP/IP weirdness in 2.2.15

2000-11-06 Thread Stephen Landamore
Hi Thomas, On Fri, 3 Nov 2000, Thomas Pollinger wrote: > Running a 'cvs get' on the Linux clients of a larger source tree > eventually hangs the client in the middle of the get process. The > hang is *always* reproduceable (however it does not always hang at > the same place, sometimes after 1',

Re: [BUG REPORT] TCP/IP weirdness in 2.2.15

2000-11-03 Thread Thomas Pollinger
Hi Stephen I've been experiencing similar problems with what would seem at first a completely unrelated problem. To make things short: I have the following configuration: - CVS server (vers. 1.10.4) running on HPUX B.11.00 - different CVS clients (running different cvs client versions: 1.10.4/7

Re: [BUG REPORT] Conflict between Tulip driver w/ LinkSys 100LNE and EEPro

2000-10-19 Thread Ian Stirling
> The problem: I can't have the Tulip and EEPro drivers loaded at the same > time. If I have the Tulip driver loaded, and I load the EEPro driver, the > self check fails with 0x and complains that I don't have the card in > a bus master slot. If I have the EEPro driver loaded and the eth

[BUG REPORT] Conflict between Tulip driver w/ LinkSys 100LNE and EEPro driver w/ Intel PCI EtherExpress Pro100 82557

2000-10-19 Thread Dylan Griffiths
The problem: I can't have the Tulip and EEPro drivers loaded at the same time. If I have the Tulip driver loaded, and I load the EEPro driver, the self check fails with 0x and complains that I don't have the card in a bus master slot. If I have the EEPro driver loaded and the ether teste

Repeatable with gcc 2.7.2.3 [was BUG Report 2.4.0-test9: NMI Watchdochdetected LOCKUP ...]

2000-10-15 Thread wollny
Hello, I was told that I should see if the bug is repeatable with a vanilla gcc (and not pgcc). /proc/version is now: Linux version 2.4.0-test9-my-fb ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #26 SMP Son Okt 15 18:50:40 CEST 2000 The other information stays the same. bye Gert PS: Pleas CC

BUG Report 2.4.0-test9: NMI Watchdoch detected LOCKUP at CPU[01]

2000-10-13 Thread wollny
Hello, Here is the bug report When doing "modprobe imm" I get message LOCKUP detected the trace looks like this: 0: ?? (assume spin_lock_irqsave in blk_get_queue but printed EIP seems to be sensless - area with no code according to the map file) 1: ll_rw_

Another VM bug report.

2000-09-22 Thread Rui Sousa
Hi, I had another system lock up using 2.4.0-test9pre5 + vmfixes-2.4.0-test9-A1 (by Ingo Molnar). This time I manage to sample the functions where the kernel was looping using SysReq + P. Here is the list: swap_out swap_out_vma try_to_swap_out find_vma __wake_up It probably doesn't help much

Re: bug report

2000-09-20 Thread Tigran Aivazian
On Wed, 20 Sep 2000, frank wrote: > ok: > switch(parity) { > case 'o': case 'O': > cflag |= PARODD; > cflag |= PARENB; can't you just do (PARODD|PARENB) instead? Also, producing diff -ur output makes it a lot easier to

bug report

2000-09-19 Thread frank
hi all, I hope it is the right mailing list! Kernel version 2.2.5-15 and 2.2.10 (no other available) The problem: A consol-terminal connected to /dev/ttyS? cannot work with parity = odd. error is in: /usr/src/linux/drivers/serial.c error resolving: In fuction : __initfunc(static int seri

Re: [bug report] pcmcia in kernel 2.4.0-test8

2000-09-15 Thread David Ford
Alessandro Suardi wrote: > Kernel pcmcia code works fine with 2.4.0-test8 and my Xircom RBEM56G100TX, > in fact I am writing from my laptop connected through it. See lsmod output > and relevant part of .config. > > [asuardi@princess asuardi]$ lsmod > Module Size Used by > seri

Re: [bug report] pcmcia in kernel 2.4.0-test8

2000-09-15 Thread Alessandro Suardi
David Ford wrote: > > Summary: > > Kernel pcmcia code doesn't work. > DHinds pcmcia code works only if kernel pcmcia code is completely disabled. > USB Pegasus driver fails when kernel pcmcia code is enabled. > Kernel pcmcia code works fine with 2.4.0-test8 and my Xircom RBEM56G100TX, in fact

[bug report] pcmcia in kernel 2.4.0-test8

2000-09-15 Thread David Ford
Summary: Kernel pcmcia code doesn't work. DHinds pcmcia code works only if kernel pcmcia code is completely disabled. USB Pegasus driver fails when kernel pcmcia code is enabled. Attached is a text writeup of several tests. -d -- "The difference between 'involvement' and 'commitment' is like a

Re: Bug Report: Kernel 2.4.0-test7 - Floppy Drive?

2000-09-06 Thread Mike A. Harris
On Wed, 6 Sep 2000, S.J. Black wrote: >Of all the bugs i've run into, this is one of the oddest. Hopefully, >i've a) got all the req'd information here and b)a hope of finding a >solution/workaround/a facsimile thereof to the problem. > >System Spec's: K6-2/500 > 64 MB RAM >

Re: Bug Report: Kernel 2.4.0-test7 - Floppy Drive?

2000-09-06 Thread S.J. Black
Greetings... Of all the bugs i've run into, this is one of the oddest. Hopefully, i've a) got all the req'd information here and b)a hope of finding a solution/workaround/a facsimile thereof to the problem. System Spec's: K6-2/500 64 MB RAM 9.2 Quantum HD

<    2   3   4   5   6   7