Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!

2001-07-05 Thread Bob_Tracy
Andrea Arcangeli quoted: > On Thu, Jul 05, 2001 at 11:46:33AM -0400, Arjan van de Ven wrote: > > On Thu, Jul 05, 2001 at 11:32:00PM +0800, Thibaut Laurent wrote: > > > And the winner is... Andrea. Kudos to you, I've just applied these patches, > > > recompiled and it seems to work fine. > > > Too

Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!

2001-07-05 Thread Bob_Tracy
Alan Cox wrote: > > Something I forgot to mention that I didn't see in any of the other > > problem reports. In my case, the panic happens immediately after > > "Calibrating delay loop" appears during the boot sequence. > > Duplicated here. Works fine on a non Cyrix processor with the same kerne

Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!

2001-07-05 Thread Bob_Tracy
Alan Cox wrote: > Intriguing its all Cyrix. That was the first thing that hit me (stood out). > What compiler, what processor choice in the build. compiler: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) processor choice: 586/K5/5x86/6x86/6x86MXCONFIG_M586 > It l

Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!

2001-07-05 Thread Bob_Tracy
Something I forgot to mention that I didn't see in any of the other problem reports. In my case, the panic happens immediately after "Calibrating delay loop" appears during the boot sequence. --Bob - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!

2001-07-05 Thread Bob_Tracy
Alan Cox wrote: > > This bug hits me since 2.4.6-pre5 but nobody answered to my emails... The > > code line is identical (and the softirq.c:206 ofc). > > > > Anyone, any idea? > > None at all. There are odd items in your config - like khttpd which if > involved might explain why there are not m

Re: SCSI Tape Corruption - update

2001-04-12 Thread Bob_Tracy
[EMAIL PROTECTED] wrote: > It seems that the tape is written incorrectly. I wrote some large file > (300MB) > and read it back four time. The read copies are all the same. They differ > from the original only in 32 consecutive bytes (the replaced values SEEM > random). Of course, 32 bytes in 300MB

Cyrix/mtrr fix missing from 2.4.3

2001-04-03 Thread Bob_Tracy
The following fix was omitted from 2.4.3. It corrects a problem where the mtrr code attempts to set up a region twice as large as the user requested. The original message appeared in linux-kernel on 14 Mar 2001. --Bob Tracy - Forwarded message from David Wragg - >From: David Wragg <[EM

Re: Linux Worm (fwd)

2001-03-26 Thread Bob_Tracy
Gregory Maxwell wrote: > On Mon, Mar 26, 2001 at 10:07:22AM -0500, Richard B. Johnson wrote: > [snip] > > I have just received notice that my machines will no longer be > > provided access to "The Internet". > > It's sad that people like the one who sent out messages like that can stay > employed

Re: another Cyrix/mtrr problem?

2001-03-15 Thread Bob_Tracy
David Wragg wrote: > [EMAIL PROTECTED] (Bob_Tracy) writes: > > echo "base=0xd800 size=0x10 type=write-combining" >| /proc/mtrr > > > > I get a 2MB region instead of the 1MB region I expected... > > Oops, it got broken by the MTRR >32-bit suppor

Re: another Cyrix/mtrr problem?

2001-03-13 Thread Bob_Tracy
[EMAIL PROTECTED] wrote: > Normally the answer would be "Closed driver, complain to nVidia", > but just in case.. Glad you were open-minded enough to consider that it *might* be "our" code. > Can you verify that.. > > a. You have MTRR support compiled into the kernel. yes > b. You have a /p

another Cyrix/mtrr problem?

2001-03-13 Thread Bob_Tracy
Since I've seen a few other posts on the subject, I might as well poke my head out of the foxhole long enough to get shot at :-). System is a Tyan S1590S motherboard (Apollo MVP3 chipset) with Cyrix MII 300 processor, NVIDIA GeForce2 MX AGP video card, 2.4.2 kernel, XFree86-4.0.2, and the NVIDIA

ATAPI CD burner with cdrecord > 1.6.1

2001-02-02 Thread Bob_Tracy
Kernel version is 2.4.1. For versions of cdrecord later than 1.6.1 (1.8.1 through the latest 1.10 alpha verified), attempting to burn a CD results in a SCSI error of some kind. Here's some representative output from a "dummy" burn session with cdrecord-1.9: Calling: /usr/local/lib/xcdroast-0.9

Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

2001-01-30 Thread Bob_Tracy
Congratulations to all involved in fixing the subject problem. With the 2.4.1 kernel, I can now actually use agpgart with my GeForce2 MX on a Tyan S1590S motherboard. Just thought someone might appreciate another data point, because prior to 2.4.1 I had to leave out agpgart support :-(. --Bob [

followup: depmod -a and 2.4.0

2001-01-11 Thread Bob_Tracy
Dooh! Please ignore earlier bogus report of module loading "trouble". This was my bad: an old init script was running "modprobe -a". Sigh... -- Bob Tracy[EMAIL PROTECTED] - "We might n

depmod -a and 2.4.0

2001-01-11 Thread Bob_Tracy
Maybe I missed the discussion, but why might "depmod -a" result in every module getting installed? This didn't happen under any of the 2.4.0-testX releases that I recall, and I ran every one of those and the prerelease without this "trouble". Gotta say, the screen output from running "lsmod" wit

Re: ip_defrag is broken (was: Re: test12 lockups -- need feedback)

2000-12-14 Thread Bob_Tracy
Ion Badulescu wrote: > On Thu, 14 Dec 2000 07:15:04 -0500, Mohammad A. Haque <[EMAIL PROTECTED]> wrote: > > Were you connected to a network or receiving/sending anything? > > ip_defrag is broken -- there is an obvious NULL pointer dereference > in it, introduced in test12. It doesn't hit normally

Re: ip_defrag is broken (was: Re: test12 lockups -- need feedback)

2000-12-14 Thread Bob_Tracy
Ion Badulescu wrote: > On Thu, 14 Dec 2000 07:15:04 -0500, Mohammad A. Haque <[EMAIL PROTECTED]> wrote: > > Were you connected to a network or receiving/sending anything? > > ip_defrag is broken -- there is an obvious NULL pointer dereference > in it, introduced in test12. It doesn't hit normally

Re: test12 lockups -- need feedback

2000-12-14 Thread Bob_Tracy
Mohammad A. Haque wrote: > Were you connected to a network or receiving/sending anything? > > dep wrote: > > > > okay. got it here this morning, too. solid lock -- no dumping out of > > x, no changing terminals, no mouse, no keyboard. > > > > k6-2-550 @ 500; 256mb memory, fic 503a mb with via c

followup: 2.4.0-test12 unresolved SCSI symbols

2000-12-12 Thread Bob_Tracy
The quick (not necessarily correct) fix is to back out that portion of the linux/drivers/scsi/Makefile patch that moves "scsi_syms.o" from line 33 to line 126. "It works for me." (tm) -- Bob Tracy[EMAIL PROTECTED] -

2.4.0-test12 unresolved SCSI symbols

2000-12-12 Thread Bob_Tracy
Someone else mentioned the problem in a different context, so this report isn't exactly new... LOTS of unresolved symbols in several SCSI modules. Here's the list for "st.o": scsi_unregister_module scsi_block_when_processing_errors scsi_release_request scsi_do_req scsi_allocate_request print_re

Re: ESS device "1998"

2000-11-02 Thread Bob_Tracy
Mo McKinlay wrote: > 00:0d.0 Multimedia audio controller: ESS Technology: Unknown device 1998 > 00:0d.1 Communication controller: ESS Technology: Unknown device 1999 > > Any hints/clues/etc welcome. Welcome to the "wonderful" world of the Maestro 3i. You'll find the following URL to be of inter

Adaptec 2930U2 followup

2000-09-02 Thread Bob_Tracy
Thought it might be worth a followup report in case anyone was interested. All the problems I was seeing with my 2930U2 went bye-bye when I replaced my bottom-feeder M537 VXpro motherboard with a Tyan S1590S. Current setup is Linux 2.4.0-test7 with the aic7xxx driver compiled in. -- Bob Tracy

www.crucial.com won't talk to 2.4.0-test7 system

2000-08-29 Thread Bob_Tracy
I *thought* I wanted to buy some memory from Crucial :-). Can't get there from here with my 2.4.0-test7 machine, but Win95 seems to be ok, and 2.4.0-test5 worked ok from a different location yesterday. Has anyone else seen this kind of thing that might shed some light on the matter? Here's what