Re: ext3 and Software RAID

2000-10-07 Thread Andreas Dilger

Matt Stegman writes:
> A few weeks ago Alan Cox mentioned, in reply to someone asking about
> building an enourmous RAID array,
> 
> "Right now 2.2 doesnt support journalling over software raid so that would
> stop you using reiserfs and ext3."
> 
> http://kernelnotes.org/lnxlists/linux-kernel/lk_0008_05/msg9.html
> 
> Is this still true? I was going to use 2.2.17, with ext3-0.0.3b, and Ingo
> Molnar's 2.2.17 RAID patch:

This was just discussed on l-k last week.  Basically, no it still doesn't
work (not for 2.2 at least).  The problem is with RAID doing buffer cache
snooping and causing data to be written out-of-order to disk (on 2.2).
This is fixed in 2.4, but there _may_ still be a problem in 2.4 when
rebuilding the array (on disk failure) in 2.4...  I'm not too sure of
the latter though...

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/   -- Dogbert
-
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: ack number in a connection-refused RST

2000-10-07 Thread David Wagner

David S. Miller wrote:
>   From: [EMAIL PROTECTED] (David Wagner)
>
>   How could it be for another connection, if it has source and
>   destination port numbers?
>
>Consider previously existing connections with the same src/dst/ports
>and the effects of massive packet reordering and other transmission
>delays.

Good point.  Ok, I see your point.  I stand corrected.

Thanks for catching that.
-
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: will ip 6 in ip4 tunnelling be fixed anytime soon ?

2000-10-07 Thread Bernd Eckenfels

In article <[EMAIL PROTECTED]> you wrote:
> Is there an ETA on having ip6 in ip4 tunnelling working with the latest
> net-utils??

what is the problem? Do u have a bug or do u mean general IPv6 Support?
There are a lot of unoficial IPv6 Packages, Debian has a good Collection,
and we are trying to get them back into the Upstream.

For net-tools, everything should be ok with 1.57

Greetings
Bernd
-
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: User-mode linux stack overflow: could be generic problem

2000-10-07 Thread Jeff Dike

Thank you!

I've been waiting for someone to send me that stack.  There aren't any real 
smoking guns there.  I'm guessing that the difference between your laptop and 
the machine it works on is that your laptop is running a fairly recent kernel 
(2.4.0-testx) and the other isn't.  The sigcontext struct greatly increased in 
size (to ~800 bytes IIRC) to accomodate the MMX registers or something.  There 
are three signals on your stack, so those frames by themselves are taking up 
half the stack page.

Anyway, the patch below removes 256 bytes from the set_signals frame.  It 
ought to alleviate things a bit.  I'll be looking for other things I can do, 
as well. Let me know how it works for you.

Jeff

--- arch/um/kernel/signal_user.c~   Thu Sep 14 17:00:08 2000
+++ arch/um/kernel/signal_user.cSun Oct  8 00:21:29 2000
@@ -45,26 +45,29 @@
 
 int set_signals(int enable)
 {
-   sigset_t mask, unmask, old;
+   sigset_t mask;
+   int ret;
 
check_stack_overflow();
+   sigprocmask(SIG_BLOCK, NULL, );
+   ret = enable_mask();
sigemptyset();
-   sigemptyset();
-   if(enable & (1 << SIGIO_BIT)) sigaddset(, SIGIO);
-   else sigaddset(, SIGIO);
+   if(enable & (1 << SIGIO_BIT)) sigaddset(, SIGIO);
if(enable & (1 << SIGVTALRM_BIT)){
-   sigaddset(, SIGVTALRM);
-   sigaddset(, SIGALRM);
+   sigaddset(, SIGVTALRM);
+   sigaddset(, SIGALRM);
}
-   else {
+   if(sigprocmask(SIG_UNBLOCK, , NULL) < 0)
+   panic("Failed to enable signals");
+   sigemptyset();
+   if((enable & (1 << SIGIO_BIT)) == 0) sigaddset(, SIGIO);
+   if((enable & (1 << SIGVTALRM_BIT)) == 0){
sigaddset(, SIGVTALRM);
sigaddset(, SIGALRM);
}
-   if(sigprocmask(SIG_BLOCK, , ) < 0)
-   panic("Failed to change signal mask");
-   if(sigprocmask(SIG_UNBLOCK, , NULL) < 0)
-   panic("Failed to change signal mask");
-   return(enable_mask());
+   if(sigprocmask(SIG_BLOCK, , NULL) < 0)
+   panic("Failed to block signals");
+   return(ret);
 }
 
 /*


-
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: SoundFusion/Cirrus Logic CS4630 sound chipset support

2000-10-07 Thread David Ford

David Ford wrote:

> Jeff Garzik wrote:
>
> > On Sat, 7 Oct 2000, David Ford wrote:
> > > Does anyone have any driver for this, or does anyone have a driver that
> > > has been started?
> >
> > What's the PCI id?  Does drivers/sound/cs46xx.c work after adding your
> > PCI id?
>
> The ID is already in the file but the kernel doesn't print any init messages
> or show anything in /dev/sound.

disregard, it must have been operator error.  i rebuilt it as a module and it's
working fine albeit it seems to have pretty weak sound output and degenerates
to garble when the volume is turned up.

i think i may take this card back, even tho i got it due to it's numerous
inputs.

-d

--
  "There is a natural aristocracy among men. The grounds of this are
  virtue and talents", Thomas Jefferson [1742-1826], 3rd US President



-
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: Blocked processes <=> Elevator starvation?

2000-10-07 Thread Rik van Riel

On Sun, 8 Oct 2000, Rui Sousa wrote:

> After starting 2 processes that scan a lot of files (diff, find,
> slocate, ...) it's impossible to run any other processes that
> touch the disk, they will stall until one of the first two stop.
> Could this be a sign of starvation in the elevator code?

It could well be. I've seen this problem too and don't
really have another explanation for this phenomenon.

OTOH, maybe there is another reason for it that hasn't
been found yet ;)

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
   -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/   http://www.surriel.com/

-
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/



ext3 and Software RAID

2000-10-07 Thread Matt Stegman

Hello,

  I've been using ext3 for some time now on an NFS server, with excellent
results (it's crashed once, and I didn't have to wait for fsck! yay!).  
I'm also wanting to upgrade to RAID (in software, since I'm short on
cash).

A few weeks ago Alan Cox mentioned, in reply to someone asking about
building an enourmous RAID array,

"Right now 2.2 doesnt support journalling over software raid so that would
stop you using reiserfs and ext3."

http://kernelnotes.org/lnxlists/linux-kernel/lk_0008_05/msg9.html

Is this still true? I was going to use 2.2.17, with ext3-0.0.3b, and Ingo
Molnar's 2.2.17 RAID patch:
http://people.redhat.com/mingo/raid-patches/raid-2.2.17-A0

  -Matt Stegman

-
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: SoundFusion/Cirrus Logic CS4630 sound chipset support

2000-10-07 Thread David Ford

Jeff Garzik wrote:

> On Sat, 7 Oct 2000, David Ford wrote:
> > Does anyone have any driver for this, or does anyone have a driver that
> > has been started?
>
> What's the PCI id?  Does drivers/sound/cs46xx.c work after adding your
> PCI id?

The ID is already in the file but the kernel doesn't print any init messages
or show anything in /dev/sound.

-d

--
  "There is a natural aristocracy among men. The grounds of this are
  virtue and talents", Thomas Jefferson [1742-1826], 3rd US President



-
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/



Blocked processes <=> Elevator starvation?

2000-10-07 Thread Rui Sousa

Hi,

I reported this problem before but didn't get any answers so I'm posting
again.

After starting 2 processes that scan a lot of files (diff, find,
slocate, ...) it's impossible to run any other processes that touch 
the disk, they will stall until one of the first two stop. Could this be
a sign of starvation in the elevator code?

This is a UP machine, 64 Mb, IDE disks, kernel 2.4.0-test9 (final). If I
can help with further details just ask.


Rui Sousa

-
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/



Будьте бдительны!

2000-10-07 Thread Vladimir

÷ÎÉÍÁÎÉÅ!
ëÔÏ-ÔÏ ÒÁÓÓÙÌÁÅÔ ÏÞÅÎØ "ÈÏÒÏÛÕÀ" ÜËÒÁÎÎÕÀ ÚÁÓÔÁ×ËÕ, Budweiser Frogs
"BUDDYLST.ZIP". åÓÌÉ ÷Ù ÅÅ ÚÁÇÒÕÚÉÔÅ, ÷Ù ÐÏÔÅÒÑÅÔÅ ×ÓÅ!!! ÷ÁÛ ÖÅÓÔËÉÊ ÄÉÓË 
ÂÕÄÅÔ ÐÏ×ÒÅÖÄÅÎ É ÌÀÂÏÊ ÐÏÌÕÞÉÔ ÉÍÑ É ÐÁÒÏÌØ ×ÁÛÅÇÏ ÜËÒÁÎÁ ÉÚ éÎÔÅÒÎÅÔÁ.îå 
úáçòõöáêôå åçï îé ðòé ëáëéè ïâóôïñôåìøóô÷áè!!! ïÎ ÐÏÓÔÕÐÉÌ × ÏÂÒÁÝÅÎÉÅ 
×ÞÅÒÁ, ÎÁÓËÏÌØËÏ ÍÙ ÍÏÖÅÍ ÓÕÄÉÔØ. ðÏÖÁÌÕÊÓÔÁ, ÒÁÚÏÛÌÉÔÅ ÜÔÏ ÓÏÏÂÝÅÎÉÅ. üÔÏ 
ÎÏ×ÙÊ, ÏÞÅÎØ "×ÒÅÄÎÙÊ" ×ÉÒÕÓ É ÎÅÍÎÏÇÉÅ Ï ÎÅÍ ÚÎÁÀÔ. üÔÁ ÉÎÆÏÒÍÁÃÉÑ 
ÐÏÓÔÕÐÉÌÁ ×ÞÅÒÁ ÕÔÒÏÍ ÏÔ ËÏÍÐÁÎÉÉ Microsoft. ðÏÖÁÌÕÊÓÔÁ, ÐÏÄÅÌÉÔÅÓØ 
üÔÏÊ ÉÎÆÏÒÍÁÃÉÅÊ ÓÏ ×ÓÅÍÉ, ËÔÏ ÉÍÅÅÔ ÄÏÓÔÕÐ × éÎÔÅÒÎÅÔ. é ÅÝÅ ÒÁÚ, 
ðÅÒÅÄÁÊÔÅ ÜÔÕ ÉÎÆÏÒÍÁÃÉÀ ×ÓÅÍ ËÔÏ ÎÁÈÏÄÉÔÓÑ × ×ÁÛÅÍ ÓÐÉÓËÅ ÁÄÒÅÓÏ× ÄÌÑ 
ÔÏÇÏ,þÔÏÂÙ ÐÒÅÄÏÔ×ÒÁÔÉÔØ ÎÅÖÅÌÁÔÅÌØÎÏÅ. AOL ÇÏ×ÏÒÉÔ, ÞÔÏ ÜÔÏ ÏÞÅÎØ ÏÐÁÓÎÙÊ 
×ÉÒÕÓ É îå ÓÕÝÅÓÔ×ÕÅÔ ÓÒÅÄÓÔ× ÚÁÝÉÔÙ ÏÔ ÎÅÇÏ × ÄÁÎÎÙÊ ÐÅÒÉÏÄ ×ÒÅÍÅÎÉ. 
ðÏÖÁÌÕÊÓÔÁ, ÐÒÅÄÐÒÉÍÉÔÅ ×ÓÅ ÐÒÅÄÏÓÔÅÒÅÇÁÀÝÉÅ ÍÅÒÙ É ÐÅÒÅÛÌÉÔÅ ÜÔÏ ÓÏÏÂÝÅÎÉÅ 
×ÓÅÍ ×ÁÛÉÍ ÄÒÕÚØÑÍ, Ó ËÏÔÏÒÙÍÉ ×Ù ÐÏÄÄÅÒÖÉ×ÁÅÔÅ Ó×ÑÚØ × on-line. åÓÌÉ ×Ù 
ÐÏÌÕÞÉÔÅ email, ÏÚÁÇÌÁ×ÌÅÎÎÙÊ "It Takes Guts to Say Jesus", ÎÅ ÏÔËÒÙ×ÁÊÔÅ 
ÅÇÏ. ÏÎ ÓÏÔÒÅÔ ×ÓÀ ÉÎÆÏÒÍÁÃÉÀ ÎÁ ÖÅÓÔËÏÍ ÄÉÓËÅ. ðÅÒÅÛÌÉÔÅ ÜÔÏ ÐÉÓØÍÏ ËÁË 
ÍÏÖÎÏ ÂÏÌØÛÅÍÕ ËÏÌÉÞÅÓÔ×Õ ÌÀÄÅÊ. 


-- 
Best regards,
 Vladimir http://webmoney.bos.ru
 
*
 èÏÔÉÔÅ ÉÍÅÔØ ÓÔÁÂÉÌØÎÙÊ ÅÖÅÍÅÓÑÞÎÙÊ ÚÁÒÁÂÏÔÏË?

ëÌÕ "òÅÇÉÓÔÒÁÔÏÒ" - ÌÕÞÛÅÅ ÐÒÅÄÌÏÖÅÎÉÅ ÎÁ ÓÅÇÏÄÎÑÛÎÉÊ ÄÅÎØ.
òÅÇÉÓÔÒÉÒÕÑÓØ × ÒÁÚÌÉÞÎÙÈ ÐÒÏÇÒÁÍÍÁÈ, ×Ù ÓÍÏÖÅÔÅ ÚÁÒÁÂÁÔÙ×ÁÔØ $5-$15 ×
ÞÁÓ.  õÄÅÌÑÑ  ÜÔÏÍÕ  ÚÁÎÑÔÉÀ  ×ÓÅÇÏ  ÌÉÛØ  1  ÞÁÓ  × ÄÅÎØ - ×Ù ÓÍÏÖÅÔÅ
ÚÁÒÁÂÁÔÙ×ÁÔØ $200 - $300 × ÍÅÓÑÃ!
îÏ  ÜÔÏ  ÎÅ  ÐÒÅÄÅÌ.  îÉËÔÏ  ×ÁÍ  ÎÅ  ÚÁÐÒÅÝÁÅÔ  ÒÁÂÏÔÁÔØ  ÂÏÌØÛÅÉ
ÓÏÏÔ×ÅÔÓÔ×ÅÎÎÏ ÐÏÌÕÞÁÔØ ÚÁ ÜÔÏ.

÷ÁÍ  ÂÕÄÕÔ ÐÌÁÔÉÔØ ÎÅ ÞÅËÉ, Á × WebMoney ËÏÛÅÌ£Ë, ÏÂÎÁÌÉÞÉÔØ ÄÅÎØÇÉ ÉÚ
ËÏÔÏÒÏÇÏ ÍÏÖÎÏ × ÔÅÞÅÎÉÉ 4-5 ÄÎÅÊ ÂÁÎËÏ×ÓËÉÍ ÉÌÉ ÐÏÞÔÏ×ÙÍ ÐÅÒÅ×ÏÄÏÍ.
 
üÔÏ  ÒÅÁÌØÎÙÊ  ÐÒÏÅËÔ,  É ÔÏ ÞÔÏ ÏÎ ÒÁÂÏÔÁÅÔ É ×ÙÐÌÁÔÙ ÉÄÕÔ ÓÔÁÂÉÌØÎÏ
ÇÏ×ÏÒÉÔ  ÓËÒÉÎÛÏÔ  ÍÏÅÇÏ  ËÏÛÅÌØËÁ,  ×Ù×ÅÛÅÎÎÙÊ  ÎÁ ÓÔÒÁÎÉÃÅ. ñ ÌÉÞÎÏ
ÐÏÌÕÞÁÌ ÄÅÎØÇÉ ÕÖÅ 2 ÒÁÚÁ.
 
 ðÏÓÍÏÔÒÅÔØ  ÎÁ  cËÒÉÎÛÏÔ  ËÏÛÅÌØËÁ  É ÐÏÚÎÁËÏÍÉÔØÓÑ Ó ÄÁÎÎÙÍ ÐÒÏÅËÔÏÍ
 ÐÏÄÒÏÂÎÅÊ ÍÏÖÎÏ ÚÄÅÓØ: http://webmoney.bos.ru

úÁÒÅÇÉÓÔÒÉÒÏ×Á×ÛÉÓØ × ËÌÕÂÅ, ×Ù ÔÁË ÖÅ ÐÏÌÕÞÉÔÅ ÌÀÂÕÀ ÐÏÓÉÌØÎÕÀ ÐÏÍÏÝØ
É ÔÅÈÎÉÞÅÓËÕÀ ÐÏÄÄÅÒÖËÕ.


-
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/



User-mode linux stack overflow: could be generic problem

2000-10-07 Thread Jeremy Fitzhardinge

Hi,

I've been playing with user-mode linux (2.4.0-pre9).  It works well on
one machine, but on my laptop I'm consistently getting stack overflows
just as init is started.

The backtrace (from a breakpoint at panic()):

(gdb) bt
#0  panic (fmt=0x10112e00 "Stack overflowed onto current_task page")
at panic.c:54
#1  0x100a244d in check_stack_overflow (ptr=0x5015ccc8) at process_kern.c:715
#2  0x1009ddc9 in set_signals (enable=0) at signal_user.c:50
#3  0x100050b0 in __wake_up (q=0x5014afc8, mode=35) at sched.c:714
#4  0x10020ea5 in end_buffer_io_sync (bh=0x5014af80, uptodate=1)
at /home/jeremy/uml/2.3/include/linux/locks.h:34
#5  0x100607a4 in end_that_request_first (req=0x500e8f00, uptodate=1, 
name=0x1011390d "User-mode block device") at ll_rw_blk.c:1000
#6  0x100a3d48 in ubd_finish () at /home/jeremy/uml/2.3/include/linux/blk.h:396
#7  0x100a3dd5 in ubd_handler () at ubd.c:222
#8  0x100a3e00 in ubd_intr (irq=3, dev=0x1012c0a0, unused=0x5015cd88)
at ubd.c:229
#9  0x1009c6bf in handle_IRQ_event (irq=3, regs=0x5015cd88, action=0x500573c0)
at irq.c:148
#10 0x1009c85f in do_IRQ (irq=3, user_mode=0) at irq.c:313
#11 0x1009cf8d in sigio_handler (sig=29) at irq_user.c:53
#12 0x100a7318 in __restore ()
at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
#13 0x1009de50 in set_signals (enable=3) at signal_user.c:65
#14 0x1005fb46 in generic_unplug_device (data=0x10160650) at ll_rw_blk.c:364
#15 0x100204ab in __wait_on_buffer (bh=0x5014af80)
at /home/jeremy/uml/2.3/include/linux/tqueue.h:120
#16 0x100212be in bread (dev=25088, block=92508, size=1024)
at /home/jeremy/uml/2.3/include/linux/locks.h:20
#17 0x10041a40 in ext2_get_block (inode=0x5013c0a0, iblock=288, 
bh_result=0x5014ae00, create=0) at inode.c:250
#18 0x10021edd in block_read_full_page (page=0x50008b74, 
get_block=0x10041978 ) at buffer.c:1613
#19 0x10042014 in ext2_readpage (file=0x500de1e0, page=0x50008b74)
at inode.c:659
#20 0x10013eb1 in read_cluster_nonblocking (file=0x500de1e0, offset=77, 
filesize=78) at filemap.c:440
#21 0x1001525c in filemap_nopage (area=0x500d2c60, address=134832128, 
no_share=2) at filemap.c:1391
#22 0x1001209d in do_no_page (mm=0x500d41c0, vma=0x500d2c60, 
address=134832392, write_access=2, page_table=0x50159258) at memory.c:1150
#23 0x100121d4 in handle_mm_fault (mm=0x500d41c0, vma=0x500d2c60, 
address=134832392, write_access=2) at memory.c:1207
#24 0x100a01b3 in segv (address=134832392, ip=268665530, is_write=2, is_user=0)
at trap_kern.c:89
#25 0x100a0902 in segv_handler (sig=11) at trap_user.c:258
#26 0x100a7318 in __restore ()
at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
#27 0x100397d4 in load_elf_binary (bprm=0x5015db24, regs=0x0)
at binfmt_elf.c:714
#28 0x100287e8 in search_binary_handler (bprm=0x5015db24, regs=0x0)
at exec.c:809
#29 0x10038226 in load_script (bprm=0x5015db24, regs=0x0) at binfmt_script.c:92
#30 0x100287e8 in search_binary_handler (bprm=0x5015db24, regs=0x0)
at exec.c:809
#31 0x100289cd in do_execve (filename=0x500df000 "/etc/rc.d/rc.sysinit", 
argv=0xbf7ffb14, envp=0x804f2c0, regs=0x0) at exec.c:902
#32 0x1009c3fc in execve1 (file=0x500df000 "/etc/rc.d/rc.sysinit", 
argv=0xbf7ffb14, env=0x804f2c0) at exec_kern.c:77
#33 0x1009c474 in sys_execve (file=0xbf7ffa88 "", argv=0xbf7ffb14, 
env=0x804f2c0) at exec_kern.c:101
#34 0x1009eab7 in execute_syscall (syscall=11, args=0x5015dcf8)
at syscall_kern.c:340
#35 0x1009eeb8 in syscall_handler (unused=0) at syscall_user.c:113
#36 0x1009bf03 in fork_handler (sig=10) at process.c:96
#37 0x100a7318 in __restore ()
at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127

This is a pretty deep stack, but there's nothing unexpected there.
I would guess that some kind of very fast disk drive would also cause
this kind of deep stack on real hardware, if it can complete the
I/O and interrupt before the reschedule.

I tried adding some inlines to make the stack use a little shallower, but
it didn't help.

Any suggestions on how to get this working? 

Thanks,
J

 PGP signature


Hard lock with Raid 0.90 on buslogic flashpoint SCSI card

2000-10-07 Thread Diamon


I hope this is going to the right list/group/etc, as I got this email
address from someone on #kernelnewbies...

Attempting to mkraid /dev/md0 a raid5 array using a Buslogic Flashpoint
fast SCSI PCI card will always hard lock the system at exactly 2% complete.
There is no oops or log, and it's a total lockup.  I can't even switch
virtual terminals when it locks.  Using an AHA-2940UW in place of the
buslogic works perfectly.

This is using kernel 2.2.17 with the raid 0.90 B0 patch which applied
cleanly.  I was wondering if it was raid, but since the 2940 worked, I
started to wonder about the Buslogic card driver maybe.

root@userhost:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5]
read_ahead 1024 sectors
md0 : active raid5 sdd1[2] sdc1[1] sdb1[0] 4185856 blocks level 5, 4k chunk,
alg
orithm 0 [3/3] [UUU] resync=68% finish=17.8min
unused devices: 
root@userhost:~#

A cut-and-paste of the rebuild in progress.  It completed normally and
was usable after that on the 2940.  I will test any other variations of
tests I can think of and give the results.

Any information on even how I can troubleshoot this further would be
appreciated!

For replies (If this is a mailing list), please cc: me as well, as I am
not on the mailing list.

Diamon

-
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: [KBUILD] Re: Adding vendor drivers...

2000-10-07 Thread Peter Samuelson


[Philipp Rumpf <[EMAIL PROTECTED]>]
> The idea isn't bad, but I'm not sure magic comments are really the
> way to go.  special macros should work just as well, shouldn't they ?

To be defined where?  Do we assume everyone will #include
 or something?  Or #include ?  It
seems a little absurd, since the whole file would be something like

  #define MAKEFILE_LINE(foo...)
  #define CONFIG_LINE(foo...)
  #define CONFIG_HELP_LINE(foo...)

(Of course you'd probably use something other than CONFIG_LINE because
that would needlessly confuse mkdep.c and checkconfig.pl.)

Peter
-
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?

2000-10-07 Thread Kai Henningsen

[EMAIL PROTECTED] (Matthew Hawkins)  wrote on 03.10.00 in 
<[EMAIL PROTECTED]>:

> One reason I stopped running and recommending Redhat was the inferior
> quality of their packages.  They'd ship half-complete, half-assed
> packages and it was concerned end-users who'd have to make their own
> RPMS and kindly make them available to the world, to fix the irritating
> stupid bugs in the default Redhat ones.  Of course, some enlightened
> Redhat employee will no doubt tell me I should register bug reports
> about their packages through official channels blah blah blah which is
> no use when you do that and the bug reports are ignored for over six
> months while Redhat are off promoting themselves at one conference or
> another, arse-kissing for more shareholders while at the other end
> screwing over the people that put them into the position they could IPO
> in in the first place.  There's noone responsible for a package, unlike
> Debian (the other extreme) where each package has a maintainer who is
> responsible for making sure that package is reliable, security-conscious
> and integrates well into the rest of the system.  With RH you just
> submit bug reports to some tracking system and three revisions down the
> track somebody will get back from self-promotion at whatever conference
> and go "damn, there's a lot of bug reports, I might look at one or two
> then delete the rest" and maybe your bug is one of the lucky two, so you
> and the millions of other Redhat users don't have to manually fix it
> next time.

Nice rant.

Unfortunately, a lot of it is equally applicable to Debian. Well, not the  
IPO stuff, of course, but Debian does have some bugs in the bug tracking  
system that are several years old (as is easy to verify for anyone who  
cares at http://bugs.debian.org/). There's a reason we're talking abou how  
it would be nice to get from 10,000 bugs down to 8,000 for the next  
release.

> That might not be quite how it works now (and for their sake, I hope
> not), but it sure looks that way from the outside, from the eyes of a
> former loyal customer.

Well, one difference with Debian is that most of our dirty underwear is  
publicly available, so instead of dreaming up scenarios about how we all  
go around self-promoting on conferences to look good for the next IPO, you  
can see how we spend the time insulting each other for not caring about  
.

MfG Kai
[EMAIL PROTECTED]
-
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: Adding vendor drivers...

2000-10-07 Thread Philipp Rumpf

On Fri, Oct 06, 2000 at 11:39:53PM +0200, Pavel Machek wrote:
> Well, having .in and .mak files with single lines in them seems ugly
> to me. What about make dep scanning for
> 
> /* Makefile:  obj-$(CONFIG_MY_DRIVER) += mydriver.o */
> /* Config.in: bool CONFIG_MY_DRIVER */
> 
> in .c files?

The idea isn't bad, but I'm not sure magic comments are really the way to
go.  special macros should work just as well, shouldn't they ?

Also you're missing a very important item here: Documentation for the
config option.

Philipp Rumpf
-
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: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Jeff V. Merkey


Oct  7 18:48:01 manos PAM_pwdb[727]: (login) session opened for user root by 
LOGIN(uid=0)
Oct  7 18:48:08 manos kernel: scsi1 : SCSI host adapter emulation for IDE ATAPI 
devices 
Oct  7 18:48:08 manos kernel: scsi : 2 hosts. 
Oct  7 18:49:32 manos PAM_pwdb[728]: (login) session opened for user root by 
LOGIN(uid=0)
Oct  7 19:04:34 manos modprobe: modprobe: Can't locate module block-major-11
Oct  7 19:04:34 manos modprobe: modprobe: Can't locate module block-major-11
Oct  7 19:04:41 manos kernel: hdd: packet command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:04:41 manos kernel: hdd: packet command error: error=0x54 
Oct  7 19:04:41 manos kernel: ATAPI device hdd: 
Oct  7 19:04:41 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:04:41 manos kernel:   Invalid field in command packet -- (asc=0x24, 
ascq=0x00) 
Oct  7 19:04:41 manos kernel:   The failed "Read TOC" packet command was:  
Oct  7 19:04:41 manos kernel:   "43 02 00 00 00 00 00 00 04 00 00 00 " 
Oct  7 19:04:41 manos kernel: hdd: command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:04:41 manos kernel: hdd: command error: error=0x54 
Oct  7 19:04:41 manos kernel: end_request: I/O error, dev 16:40 (hdd), sector 2 
Oct  7 19:04:41 manos kernel: ATAPI device hdd: 
Oct  7 19:04:41 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:04:41 manos kernel:   Logical block address out of range -- (asc=0x21, 
ascq=0x00) 
Oct  7 19:04:41 manos kernel: hdd: packet command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:04:41 manos kernel: hdd: packet command error: error=0x54 
Oct  7 19:04:41 manos kernel: ATAPI device hdd: 
Oct  7 19:04:41 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:04:41 manos kernel:   Invalid field in command packet -- (asc=0x24, 
ascq=0x00) 
Oct  7 19:04:41 manos kernel:   The failed "Read TOC" packet command was:  
Oct  7 19:04:41 manos kernel:   "43 02 00 00 00 00 00 00 04 00 00 00 " 
Oct  7 19:04:41 manos kernel: hdd: command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:04:41 manos kernel: hdd: command error: error=0x54 
Oct  7 19:04:41 manos kernel: end_request: I/O error, dev 16:40 (hdd), sector 2 
Oct  7 19:04:41 manos kernel: ATAPI device hdd: 
Oct  7 19:04:41 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:04:41 manos kernel:   Logical block address out of range -- (asc=0x21, 
ascq=0x00) 
Oct  7 19:04:41 manos kernel: hdd: packet command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:04:41 manos kernel: hdd: packet command error: error=0x54 
Oct  7 19:04:41 manos kernel: ATAPI device hdd: 
Oct  7 19:04:41 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:04:41 manos kernel:   Invalid field in command packet -- (asc=0x24, 
ascq=0x00) 
Oct  7 19:04:41 manos kernel:   The failed "Read TOC" packet command was:  
Oct  7 19:04:41 manos kernel:   "43 02 00 00 00 00 00 00 04 00 00 00 " 
Oct  7 19:04:41 manos kernel: hdd: command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:04:41 manos kernel: hdd: command error: error=0x54 
Oct  7 19:04:41 manos kernel: end_request: I/O error, dev 16:40 (hdd), sector 0 
Oct  7 19:04:41 manos kernel: FAT bread failed 
Oct  7 19:04:41 manos kernel: ATAPI device hdd: 
Oct  7 19:04:41 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:04:41 manos kernel:   Logical block address out of range -- (asc=0x21, 
ascq=0x00) 
Oct  7 19:05:01 manos kernel: hdd: packet command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:05:01 manos kernel: hdd: packet command error: error=0x54 
Oct  7 19:05:01 manos kernel: ATAPI device hdd: 
Oct  7 19:05:01 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:05:01 manos kernel:   Invalid field in command packet -- (asc=0x24, 
ascq=0x00) 
Oct  7 19:05:01 manos kernel:   The failed "Read TOC" packet command was:  
Oct  7 19:05:01 manos kernel:   "43 02 00 00 00 00 00 00 04 00 00 00 " 
Oct  7 19:05:01 manos kernel: hdd: packet command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:05:01 manos kernel: hdd: packet command error: error=0x54 
Oct  7 19:05:01 manos kernel: ATAPI device hdd: 
Oct  7 19:05:01 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:05:01 manos kernel:   Invalid field in command packet -- (asc=0x24, 
ascq=0x00) 
Oct  7 19:05:01 manos kernel:   The failed "Read TOC" packet command was:  
Oct  7 19:05:01 manos kernel:   "43 02 00 00 00 00 00 00 04 00 00 00 " 
Oct  7 19:05:01 manos kernel: hdd: command error: status=0x51 { DriveReady 
SeekComplete Error } 
Oct  7 19:05:01 manos kernel: hdd: command error: error=0x54 
Oct  7 19:05:01 manos kernel: end_request: I/O error, dev 16:40 (hdd), sector 64 
Oct  7 19:05:01 manos kernel: ATAPI device hdd: 
Oct  7 19:05:01 manos kernel:   Error: Illegal request -- (Sense key=0x05) 
Oct  7 19:05:01 manos kernel:   

Re: [KBUILD] Re: Adding vendor drivers...

2000-10-07 Thread Jeff Garzik

Pavel Machek wrote:
> 
> Hi!
> 
> > So, when a vendor has to add a new driver, especially with the new-style
> > makefiles, you have a one-line patch to a makefile, a one-line patch to
> > a Config.in, and a patch which adds the driver to the tree.
> >
> > It would make adding new drivers to vendor kernel packages a whole lot
> > easier and more modular if you could add a driver simply by doing:
> >
> >   cp driver.c driver.config.in driver.mak linux/extras
> >
> > ...and then the makefile and config system automatically slurps this
> > data.  extras/Makefile could look something like:
> >
> >   ...new style init..
> >   include *.mak
> >   ...new style obj-x handling...
> >   include Rules.make
> >
> > Something similar would have to be worked out for Config.in.
> >
> > Of course, for anything complex, patching is still an option.
> >
> > Comments?  Suggested implementation?  :)
> 
> Well, having .in and .mak files with single lines in them seems ugly
> to me. What about make dep scanning for
> 
> /* Makefile:obj-$(CONFIG_MY_DRIVER) += mydriver.o */
> /* Config.in:   bool CONFIG_MY_DRIVER */
> 
> in .c files?

Don Becker has a similar solution in his newer net drivers.  For
single-c-file drivers it is wholly sufficient.  For anything remotely
complex, like a multi-file driver in its own directory, makefile
fragments of some sort are necessary..
-
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: Newer motherboards / CPU's / hardware with Linux

2000-10-07 Thread David Rees

On Sat, Oct 07, 2000 at 02:10:31PM -0400, Mark Hahn wrote:
> > kernel proper and working.  If it *IS* ready now, what sort of
> > Athlon hardware is recommended for a developmental machine?
> 
> I HIGHLY recommend duron/thunderbird, KT133, PC133, UDMA machines;
> they work very well with modern (2.4) kernels.  K6-2 machines are 
> not anywhere close to the same performance, and even low-end Durons
> embarass FSB100-overclocked Celeron machines quite neatly.
> a Duron/600 makes a great development workstation; 
> I haven't seen a reason to pay extra for a thunderbird.

Agreed.  The only difficulty I had was while attempting to set up a recent
system was getting the ATA100 chipset to work on a Asus A7V, but all that
required was a patch with Andre's IDE patches to 2.2.17 and things the
Promise ATA100 chipset was detected fine.  We're using the Via controller,
though, our disk is only a ATA33 drive.

The Durons are GREAT values, we did a few benchmarks on a Duron 600 system
vs an Athlon 700 (slot, not TBird), and in most cases it was about 10-15%
slower, but while timing how long it took to unpack the kernel sources, it
was something like 5-10% FASTER!

Now if they made Durons in the higher clock speeds, I wouldn't hesitate to
pick one of those up over a TBird, but if you want something over 700Mhz,
you're stuck.

Keep in mind that AMD will be significantly dropping prices around the end
of the month, so you may want to wait a bit before picking one up.

-Dave
-
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: Tux 2 patents

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 10:56:51PM +0200, Daniel Phillips wrote:
> > I would appreciate you not bouncing off the walls...
> 
> The main goal is to encourage NetApp management to do the right thing. 
> If refraining from making inflamatory remarks about burning down the
> USTPO helps advance that purpose then that's exactly what I'll do.

Whatever happens, so long as we are doing the right thing, we'll be ok.

:-)

Jeff

> 
> Incidently, the continuing controversy seems to have resulted in a
> steady stream of very well qualified and helpful subscribers to the
> tux2-dev list.  This suggests that when I do post the code sometime next
> month, development will proceed more rapidly than I had previously
> hoped.  So something good has already come of this.
> 
> --
> Daniel
> 
> http://innominate.org/mailman/listinfo/tux2-dev <- read the archives and
> sign up here
> -
> 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/



Quantum lct08 & Ultra66 on GA-BX2000+

2000-10-07 Thread Mikhail Vladimirov


In Original Message
From: "Andre Hedrick" <[EMAIL PROTECTED]>
To: "Mikhail Vladimirov" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, October 07, 2000 9:16 PM
Subject: Re: Quantum lct08 & Ultra66 on GigaByte GA-BX2000+
You wrote me literally:

>
> Read the source code and put the complete drive name in the quirk list for
> that chipset.
>

Ops! I did it...
Generally speaking "complete drive name" is ALREADY IN quirklist about a
month at least...
but it does not help me the same way as if it has been written on a fence
:-)
For any case I send you little attachment to check it.
("QUANTUM FIREBALLlct08 08" - that's what we are talking about)

I suspect there is some fundamental lowlevel drawback somewhere,
or there is some specific in my hardware set which makes imposible to use
2.4.0-kernel in the future at all :-)
For instance I have found that version of my Ultra66 BIOS is 1.15
while you design everything (as far as I can get it) with expectation of
ver.1.11

Sorry I'm not sure I can update BIOS ver.1.15 of my onboard
Ultra66-controller up to ver.1.29,
I never  read anything about such possibility at least.

Regards,
Mike




 pdc202xx.c


bttv driver sometimes oopses

2000-10-07 Thread Koos Vriezen

Hi,

Since i2c was added to the kernel, I have sometimes trouble with my bttv
card. Before that, I never had any trouble with bttv since kernel 2.2.0.
The modules are loaded when I start X with vidmode extension turned on. When
everything goes well I see the following in my syslog:

 kernel: Linux video capture interface: v1.00
 kernel: i2c-core.o: i2c core module
 kernel: i2c-algo-bit.o: i2c bit algorithm module
 kernel: bttv: driver version 0.7.38 loaded
 kernel: bttv: using 2 buffers with 1040k (2080k total) for capture
 kernel: bttv: Bt8xx card found (0).
 kernel: bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 80, irq: 9, memory:
0xe700.
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 1 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o:3 scl: 0  sda: 1
 kernel: i2c-algo-bit.o:4 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 passed test.
 kernel: bttv0: i2c: checking for eeprom @ 0xa0... found
 kernel: bttv0: card id: Hauppauge WinTV (0x13eb0070) => card=10
 kernel: bttv0: model: BT878(Hauppauge new (bt878)) [insmod option]
 kernel: bttv0: Hauppauge eeprom: tuner=Philips FM1216 (5)
 kernel: bttv0: Hauppauge msp34xx: reset line init
 kernel: bttv0: i2c: checking for MSP34xx @ 0x80... found
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 1 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o:3 scl: 0  sda: 1
 kernel: i2c-algo-bit.o:4 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 passed test.
 kernel: bttv0: i2c: checking for MSP34xx @ 0x80... found
 kernel: msp3400: init: chip=MSP3410D-B4, has NICAM support
 kernel: msp3410: daemon started
 kernel: bttv0: i2c attach [MSP3410D-B4]
 kernel: bttv0: i2c: checking for TDA8425 @ 0x82... not found
 kernel: bttv0: i2c: checking for TDA985x @ 0xb6... not found
 kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found
 kernel: tuner: chip found @ 0x61
 kernel: bttv0: i2c attach [Philips PAL]
 modprobe: modprobe: Can't locate module char-major-81-1
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0

Except that I don't know which aliases to use for the tvmixer. What are they?
Anyway, when it goes wrong I see:

 kernel: Linux video capture interface: v1.00
 kernel: i2c-core.o: i2c core module
 kernel: i2c-algo-bit.o: i2c bit algorithm module
 kernel: bttv: driver version 0.7.38 loaded
 kernel: bttv: using 2 buffers with 1040k (2080k total) for capture
 kernel: bttv: Bt8xx card found (0).
 kernel: bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 80, irq: 9, memory:
0xe700.
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 0 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 SDA stuck low!
 kernel: bttv0: model: BT878(Hauppauge new (bt878)) [insmod option]
 kernel: bttv: readee error
 kernel: bttv0: Hauppauge eeprom: tuner= (4)
 kernel: bttv0: Hauppauge msp34xx: reset line init
 kernel: i2c-core.o: unregister_adapter adap [bt848 #0] not found.
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 1 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o:3 scl: 0  sda: 1
 kernel: i2c-algo-bit.o:4 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 passed test.
 kernel: tuner: chip found @ 0x61
 kernel: bttv0: i2c attach [Philips PAL]
 modprobe: modprobe: Can't locate module char-major-81-1
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0

I can fix this by manually removing the bttv module, before starting XawTV.
But when I don't do that, next will happen:

 kernel: Unable to handle kernel paging request at virtual address c48a5a98
 kernel:  printing eip:
 kernel: c4893594
 kernel: *pde = 03dd7063
 kernel: *pte = 
 kernel: Oops: 
 kernel: CPU:0
 kernel: EIP:0010:[]
 kernel: EFLAGS: 00010246
 kernel: eax: c48a5a98   ebx: c48bd000   ecx: c48bfde0   edx: c48a5a98
 kernel: esi: c48bb000   edi: c48a5a40   ebp:    esp: c3aa3f68
 kernel: ds: 0018   es: 0018   ss: 0018
 kernel: Process rmmod (pid: 1839, stackpage=c3aa3000)
 kernel: Stack: c48bd000 c48bb000 c48bd000 bfffedf8 c4895e88 c48a5a98
c4895e9c 0001
 kernel:0001 c48bed0a c48bfde0 c0116213 c48bd000 c48bb000
 bfffedf8
 kernel:c011572e c48bd000 0001 c3aa2000 0061 bfffedf8
c0108d23 
 kernel: Call Trace: [] [] [] []
[] [] []
 kernel:[] [free_module+23/152] [] []
[sys_delete_module+378/448] [] [system_call+51/64]
 kernel: Code: 8b 1c aa 85 db 74 37 8b 4c 24 28 39 4b 30 75 2e 83 3d 80 5d

$ 

RE: Adding vendor drivers...

2000-10-07 Thread Paul Fulghum


>Well, having .in and .mak files with single lines in them seems ugly
>to me. What about make dep scanning for
>
>/* Makefile:   obj-$(CONFIG_MY_DRIVER) += mydriver.o */
>/* Config.in:  bool CONFIG_MY_DRIVER */
>
>in .c files?
>   Pavel

I love this idea. Everything in one neat, drop-in package.

1. As person working for a hardware vendor, this would make
things much easier for me and my customers.

2. I think it would also make it easier to move things
around when restructuring the source directories is necessary.

3. And it might reduce the instances of a driver accidentally
being removed when a Makefile is reworked (which just happened
to a driver of ours in the 2.4.0-test kernels).

This may not be appropriate for all add-ons, but for simple drivers
like ours this would be great.

Maybe even add another tag to add the config help text.

This has my vote of support.

Paul Fulghum
[EMAIL PROTECTED]
 
-
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: Tux 2 patents

2000-10-07 Thread Daniel Phillips

> I would appreciate you not bouncing off the walls...

The main goal is to encourage NetApp management to do the right thing. 
If refraining from making inflamatory remarks about burning down the
USTPO helps advance that purpose then that's exactly what I'll do.

Incidently, the continuing controversy seems to have resulted in a
steady stream of very well qualified and helpful subscribers to the
tux2-dev list.  This suggests that when I do post the code sometime next
month, development will proceed more rapidly than I had previously
hoped.  So something good has already come of this.

--
Daniel

http://innominate.org/mailman/listinfo/tux2-dev <- read the archives and
sign up here
-
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: [PATCH] VM fix for 2.4.0-test9 & OOM handler

2000-10-07 Thread Rik van Riel

On Sat, 7 Oct 2000, James Lewis Nance wrote:
> On Fri, Oct 06, 2000 at 03:59:48PM -0300, Rik van Riel wrote:
> > the following patch contains 2 fixes and one addition
> > to the VM layer:
> 
> This kernel is working well for me.  I have been off the net
> for about a week and a half, so I did not get to try any of the
> latter test9-preX kernels, but all the early ones would lock up
> on me if I tried to build mozilla with mem=48M.  This one works
> just fine.

Yes, we seem to have things under control now ...  ;)

My 2 main TODO items at the moment are getting the OOM
killer to kick in at exactly the right moment and trying
to make swap-over-nbd work...

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
   -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/   http://www.surriel.com/

-
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/



[BENCH] Linux kernel benchmarked..

2000-10-07 Thread Luuk van der Duim

Hi Kernelfolks,

 I know kernelcompiling is not the only useful thing we do within Linux but
it is one of the longer lasting tasks.
Therefore I timed Linux kernel 2.2.16-pre9, 2.4.0-test6, 2.4.0-test9-pre7
and 2.4.0-test9 compiling bzImage.

 System: Linux mandrake 7.1 UP Pentium2 266@300

 2.4.0-t9  867,72 s.   512,37 s.  503,66 s. 500,97 s.
2.4.0-t9-p7891,64 s.   513,27 s.  506,00 s.  501,04 s.
2.4.0-t6   1.002,50 s.   511,44 s. 502,27  s. 500,04 s.
2.2.16-pre9 1.302,98 s.   506,50 s.  498,66 s. 496,67 s.

16 MB 32 MB 64 MB 128 MB

 My Gnumeric does not make graphs.. Therefore I've added an excell
sheet..(sorry)
Most useful to you might be the textfile testresults in which the pagefaults
are also mentioned.

 Greetings,

 Luuk van der Duim



begin 666 Kernelbench.pdf
M)5!$1BTQ+C(*)TLP?I"E-Z$("@?Q^Y%G/K%=3AC8LBX>W;^7W+/E-`/2A??KZ<'2O[M7C
MC"W+P]'?3N[+#VG ],NA/\R_^DQ>JOCI>'7_^_'Q#:^G9_=U\G?*>'+1O^OZ
M3;_/+E,`2EYRXK8>':]MBY?;9B\2@=O&2,5_OVT;$T-*BKT[+]ZJ0@R7R*,$$J7
MCX!THN%-T.-/6O^&]:&6C0-DVX".##=$9\S87)!_"@EJS-)@1PFYW2S1*H
M^L-;]6S8LQ'0:6R8LQ'0`@`$P`,0`B`+0``) !``#\"0%(`&4`; !V`&4`= !I`&,`
M80`Q`"(`M ``D $``/P)`4@`90!L`'8`90!T``8P!A`#$`&@#(
M_W^0`0``_ 4!00!R``80!L`#$`&@#(_W^0`0``_ 4!
M00!R``80!L`#$`&@#P``$`_W^\`@``_ 4!00!R``80!L`#$`&@#(
M``$`_W^\`@``_ 4!00!R``80!L`!X$( `%`!L``")F;")<(",L(R,P
M7RT[(F9L(EP@(RPC(S!<+1X$)0`&`" ``")F;")<(",L(R,P7RT[6U)E9%TB
M9FPB7" C+",C,%PM'@0F``<`(0``(F9L(EP@(RPC(S N,#!?+3LB9FPB7" C
M+",C,"XP,%PM'@0K``@`)@``(F9L(EP@(RPC(S N,#!?+3M;4F5D72)F;")<
M(",L(R,P+C P7"T>!#X`*@`Y``!?+2)F;")<("H@(RPC(S!?+3M?+2)F;")<
M("H@(RPC(S!<+3M?+2)F;")<("H@(BTB7RT[7RU 7RT>!"P`*0`G``!?+2H@
M(RPC(S!?+3M?+2H@(RPC(S!<+3M?+2H@(BTB7RT[7RU 7RT>!$8`+ !!``!?
M+2)F;")<("H@(RPC(S N,#!?+3M?+2)F;")<("H@(RPC(S N,#!<+3M?+2)F
M;")<("H@(BTB/S]?+3M?+4!?+1X$- `K`"\``%\M*B C+",C,"XP,%\M.U\M
M*B C+",C,"XP,%PM.U\M*B B+2(_/U\M.U\M0%\M'@0:`*0`%0``7"0C+",C
M,%\I.UPH7"0C+",C,%PI'@0?`*4`&@``7"0C+",C,%\I.UM2961=7"A<)",L
M(R,P7"D>!" `I@`;``!<)",L(R,P+C P7RD[7"A<)",L(R,P+C P7"D>!"4`
MIP`@``!<)",L(R,P+C P7RD[6U)E9%U<*%PD(RPC(S N,#!<*1X$- "H`"\`
M`%\H7"0J(",L(R,P7RD[7RA<)"H@7"@C+",C,%PI.U\H7"0J("(M(E\I.U\H
M0%\I'@0N`*D`*0``7R@J(",L(R,P7RD[7R@J(%PH(RPC(S!<*3M?*"H@(BTB
M7RD[7RA 7RD>!#P`J@`W``!?*%PD*B C+",C,"XP,%\I.U\H7"0J(%PH(RPC
M(S N,#!<*3M?*%PD*B B+2(_/U\I.U\H0%\I'@0V`*L`,0``7R@J(",L(R,P
M+C P7RD[7R@J(%PH(RPC(S N,#!<*3M?*"H@(BTB/S]?*3M?*$!?*> `% ``
M]?\@``# (. `% `!]?\@``#T``# (. `
M% `!]?\@``#T``# (. `% `"]?\@``#T``# 
M(. `% `"]?\@``#T``# (. `% ``]?\@``#T
M``# (. `% ``]?\@``#T``# (. `% ``]?\@``#T
M``# (. `% ``]?\@``#T``# (. `% ``]?\@``#T
M``# (. `% ``]?\@``#T``# (. `% ``]?\@
M``#T``# (. `% ``]?\@``#T``# (. `% ``
M]?\@``#T``# (. `% ``]?\@``#T``# (. `% ``
M`0`@``# (. `% `!`*L`]?\@``#X``# (. `
M% `!`*D`]?\@``#X``# (. `% `!``D`]?\@``#X``# 
M(. `% `!`*H`]?\@``#X``# (. `% `!`*@`]?\@``#X
M``# (. `% `!``0``0`B```<``" (. `% `!`0`B```8
M``" (),"! `0@ /_DP($`!& !O^3`@0`$H %_Y,"! ``@ #_DP($`!. 
M!/^3`@0`%( '_Y(`X@`X``#___\`_P#_`/\`__\``/\`_P``
M__\`@ " `( `@( ``( `@ ``@( `P,# `(" @ "9F?\`F3-F`/__
MS #,__\`9@!F`/^ @ ``9LP`S,S_@ #_`/\`__\```#__P" `( `@ ``
M``" @ ```/\``,S_`,S__P#,_\P`__^9`)G,_P#_FC `(36 !R &,``0>
MC !\L0\P$ "1`,@!C `(`(<``-RY8@`(%P```/RY8@`@'HP`*+IB
M`)1S$# @NF(`" @```#(N6(`^+P#,-"Y8@!D.HP`% $*"0@0```&
M( `<#LP'0084%0```(,``@```(0``@```*$`(@#_`0`!
M``$`! " X#\```#@/\P`,P`"``,`8! *`$ XSB+(
M!0!@$ H`0#C.(L@``0`&`& 0"@! .,XB\ <`8! *`$ XSB+(``$`" `!
M$ ("$! ```"@<-<"D*/$`3,0``"@``0`,0`R`&00" $`
M```!``,0# `#``$`! `$``$S$ ``41 (```!#1 :"P$R
M`"X`- `N`# `( !T`&4`/___XH`
M`+$`30`@$ ``,Q ``$\0% `"``(``"80
M`@`%`%$0" ```0```#00```D$ (``P`E$" ``@(!``!XB@``
ML0!-`" 0```S$ ``3Q 4``(``@``
M)A "``8`41 (```!-! ``$80`@`!`$$0$@```"L```"D`0``9@T`
M`+<-```S$ ``3Q 4``(``@`KI $``&8-``"W#0``'1 2
M`#,0```@$ @``0`!``$``0!B$!(```$!
M`.\`'A >``(``0$``",`30```"$0`@`#``<0
M# " @( `%P`*$! `P,# ```!%@!/`#00```=$!(``0``
M,Q ``!\0*@``
M'P$>$!X``@`#`0``
M(P!-(1 "``$`!Q ,`/__"0!-`"$0`@`#``<0# ``
M``#__PD`30`*$! ``/___P`!``$`30!.`#00```=$!(``@``
M,Q ``" 0" $``0```!X0'@`"``$!
M```K`$T`6@`T$ ``)1 @``("`0``ZP,``-$)``#JG@``
M`($`30``,Q ``$\0% `"``(V%P```"80`@`(`%$0
M" ```0T0$ 

Re: [PATCH] VM fix for 2.4.0-test9 & OOM handler

2000-10-07 Thread James Lewis Nance

On Fri, Oct 06, 2000 at 03:59:48PM -0300, Rik van Riel wrote:
> the following patch contains 2 fixes and one addition
> to the VM layer:

Rik,
This kernel is working well for me.  I have been off the net for about
a week and a half, so I did not get to try any of the latter test9-preX
kernels, but all the early ones would lock up on me if I tried to build
mozilla with mem=48M.  This one works just fine.

Thanks,

Jim
-
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: Adding vendor drivers...

2000-10-07 Thread Sven Koch

On Fri, 6 Oct 2000, Pavel Machek wrote:

> Well, having .in and .mak files with single lines in them seems ugly
> to me. What about make dep scanning for
> 
> /* Makefile:  obj-$(CONFIG_MY_DRIVER) += mydriver.o */
> /* Config.in: bool CONFIG_MY_DRIVER */
> 
> in .c files?

Isn't "make dep" normaly only done after configuring the kernel?
(and scanning every .c-file seems really slow to me)

c'ya
sven

-- 

The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)

-
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: RedHat 7.0 anaconda installer doesn't support devfs

2000-10-07 Thread Tom Rini

On Fri, Oct 06, 2000 at 09:19:45PM -0400, Joseph Fannin wrote:
> Jeff Merkey wrote:
> 
> >On Sat, Oct 07, 2000 at 12:31:05AM -0400, jeff millar wrote: 
> >> Redhat support got back to me today and said 7.0 doesnt support
> >> upgrades to systems running devfs. But I thought sure than Linus
> >> blessed it! :-) 
> >> Does anyone have a fix? 
> >
> >Good question. I noticed this as well. 
> 
> 
>  I couldn't run devfs on a fresh install of RedHat 7 either; the
> use of labels in fstab to identify partitions seems to preclude this.

Eh?  That doesn't make sense.  I've used devfs & LABELs in my fstab before
fine.  That really shouldn't be the problem.  Your root gets mounted, yes?
Then /proc and /proc is needed (I don't know the file) for the LABEL/UUID->
device stuff.

>  Well, I *could* have hacked all the necessary scripts if I knew what
> they were, I guess.

The rawhide scripts used to start devfs all by themselves.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
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: Bug in "ide-pci.c"

2000-10-07 Thread David Woodhouse

On Fri, 6 Oct 2000, Andre Hedrick wrote:

> void go_take_a_dump (float load)
> {
>   if (pull_down_pants() && purge_bowles() && wipe_anus() && pull_up_pants())
>  flush(load);
>   else
>  wear(load);
> }

But here you make another classic mistake. Consider the case where
purge_bowels() fails (-EWOULDBLOCK?). 

In that case, you don't actually execute the subsequent two procedure
calls, which I'm sure we all agree is a suboptimal state of affairs.

-- 
dwmw2


-
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: [OOPS] unloading ns558 driver in Linux 2.4.0-test9

2000-10-07 Thread Forever shall I be.

On Sat, Oct 07, 2000 at 12:42:16PM -0400, Brian Gerst wrote:
> "Forever shall I be." wrote:
> > 
> > I got this OOPS while unloading the ns558 module.. I don't think it did
> > this in 2.4.0-test8, but I don't recall ever unloading it in test8..
> > 
> > I've attached the ksymoops output..
> What kind of game port do you have?
> 
> -- 
>   Brian Gerst

Whatever kind of game port there is on the Diamond Sonic Impact s70..
It works fine with the driver -- It just oops'd when I unloaded it :/

It should be noted here that i have to enable it with the following:
setpci -v -d 125d:1968 0x40.W=0x107f

-- 
Zinx Verituse(See headers for gpg/pgp key info)
-
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: one-line umount patch needed for am-utils

2000-10-07 Thread Pavel Machek

Hi!

> > It's kind of silly and an abuse of the VFS, I agree. Unfortunately, it's
> > been around for a while, it works on other systems and real people are
> > using it. And they get a nasty surprise when they try it on Linux: the
> > amd-provided NFS filesystems cannot be unmounted, because the VFS umount
> > code follows the root symlink.
> 
> So fix amd and teach it not to do that.

This is kernel bug. It allows root to (easily) get into situation when
he can't unmount filesystem. 
While we allow root to shoot into his foot (-:), this is much too
easy.

Pavel
-- 
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
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: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 11:16:30AM -0700, Andre Hedrick wrote:
> On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
> 
> > append "hdd=ide-scsi"

Am I doing this wrong?  It seems to work.  

:-)

Jeff

> 
> append "hdd=scsi" is better.
> 
> Andre Hedrick
> The Linux ATA/IDE guy
> 
-
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: Tux 2 patents

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 08:13:45PM +0200, Daniel Phillips wrote:
> On Sat, 07 Oct 2000, Jeff V. Merkey wrote:
> > On Sat, Oct 07, 2000 at 06:45:38PM +0200, Daniel Phillips wrote:
> 
> You are right of course.  I'm open to suggestions on exactly how best to
> behave.  The object is to make the most forward progress.

Thank you.  Lawyers can be really straight and narrow, particularly 
patent lawyers.  To date, you have not disclosed the specific methods
that will comprise the claims of you invention, just a high level 
description, which is ok.  Until the provisional application has 
been issued a docket number, you need to not describe the actual 
methods publically other than in high level designs.  Malinkrodt has
your email address, and I expect next week, they will begin their 
dialouge with you.  It only takes a few days to slap a provisional
application together.  

> But how did we get from a state where algorithms were not patentable to one
> where they are?  Surely at least that can be undone.

The spirit of the USPTO is to protect inventors rights and balance 
this with those things which are "essential facilities" of the 
affected area.  The USPTO is not the utlimate authority on what is
or is not patentable, the Judges sitting in the Federal Courts of
the US are.  There are many patents ruled to be invalidate, and 
vis-a-vis the other way in infringement claims.  The controlling
law here is what's described in the Consitution, and the rights
of an inventor to enjoy the profits of his invention for a 
limited period of time.  People always assume it's these big,
evil companies behind all the patent issues in the US.  The fact
is that the system in the US recognizes individual inventors.  These
inventors have to assign their patents to a corporation in order 
for a corporation to own it.  These laws in the US were originally 
intended to protect individual inventors, BTW.

> obviously with a view to learning the truth.  I'm also not sure whether you're
> also objecting to the idea of trying to fence in closed-source software sellers,
> are you?  Or is it just that it seems like an inflamatory idea?

It's not so black and white.  In the US, we have a concept of 
"courts of equity".  This means folks are basically free to step 
on each others rights, including the right to develop new ways of 
writing software.  At times, the system has no other recourse than
to resort to one side or the other litigating before a sitting 
Judge to expand the meaning and application of these laws, such as
the laws regulating patents.  Much of the USPTO's current policies
are based on this case law from the US District Courts.  I agree 
that the legal system in the US is "tecnology ignorant" but it 
is getting better.  

:-)

Jeff


> 
> --
> Daniel
-
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: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Andre Hedrick

On Sat, 7 Oct 2000, Jeff V. Merkey wrote:

> append "hdd=ide-scsi"

append "hdd=scsi" is better.

Andre Hedrick
The Linux ATA/IDE guy

-
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: Adding vendor drivers...

2000-10-07 Thread Pavel Machek

Hi!

> So, when a vendor has to add a new driver, especially with the new-style
> makefiles, you have a one-line patch to a makefile, a one-line patch to
> a Config.in, and a patch which adds the driver to the tree.
> 
> It would make adding new drivers to vendor kernel packages a whole lot
> easier and more modular if you could add a driver simply by doing:
> 
>   cp driver.c driver.config.in driver.mak linux/extras
> 
> ...and then the makefile and config system automatically slurps this
> data.  extras/Makefile could look something like:
> 
>   ...new style init..
>   include *.mak
>   ...new style obj-x handling...
>   include Rules.make
> 
> Something similar would have to be worked out for Config.in.
> 
> Of course, for anything complex, patching is still an option.
> 
> Comments?  Suggested implementation?  :)

Well, having .in and .mak files with single lines in them seems ugly
to me. What about make dep scanning for

/* Makefile:obj-$(CONFIG_MY_DRIVER) += mydriver.o */
/* Config.in:   bool CONFIG_MY_DRIVER */

in .c files?
Pavel
-- 
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
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: Newer motherboards / CPU's / hardware with Linux

2000-10-07 Thread Mark Hahn

> kernel proper and working.  If it *IS* ready now, what sort of
> Athlon hardware is recommended for a developmental machine?

I HIGHLY recommend duron/thunderbird, KT133, PC133, UDMA machines;
they work very well with modern (2.4) kernels.  K6-2 machines are 
not anywhere close to the same performance, and even low-end Durons
embarass FSB100-overclocked Celeron machines quite neatly.
a Duron/600 makes a great development workstation; 
I haven't seen a reason to pay extra for a thunderbird.

-
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: 2.4.0-test9 boot failure (Linux/Alpha, EIDE CMD646)

2000-10-07 Thread Richard Henderson

On Sat, Oct 07, 2000 at 06:38:00PM +0100, Dave Gilbert wrote:
>   It looses interrupts in the IDE probes; it is a CMD646 controller and
> what appears to be happening is that it is getting the wrong IRQs...

This was a generic ide problem in test9.


r~
-
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/



2.4.0-test9 boot failure (Linux/Alpha, EIDE CMD646)

2000-10-07 Thread Dave Gilbert

Hi,
  2.4.0-test9 failed to boot on my LX164 Alpha system; 2.4.0-test8 works
fine.

  It looses interrupts in the IDE probes; it is a CMD646 controller and
what appears to be happening is that it is getting the wrong IRQs; under
2.4.0-test8 we see:

Oct  7 18:19:57 tardis kernel: CMD646: IDE controller on PCI bus 00 dev 58
Oct  7 18:19:57 tardis kernel: CMD646: chipset revision 1
Oct  7 18:19:57 tardis kernel: CMD646: not 100% native mode: will probe
irqs later
Oct  7 18:19:57 tardis kernel: CMD646: chipset revision 0x01, MultiWord
DMA Limited, IRQ workaround enabled
Oct  7 18:19:57 tardis kernel: ide0: BM-DMA at 0x8000-0x8007, BIOS
settings: hda:pio, hdb:DMA
Oct  7 18:19:57 tardis kernel: ide1: BM-DMA at 0x8008-0x800f, BIOS
settings: hdc:DMA, hdd:DMA
Oct  7 18:19:57 tardis kernel: hdb: , ATAPI CDROM drive
Oct  7 18:19:57 tardis kernel: ide: Assuming 33MHz system bus speed for
PIO modes; override with idebus=xx
Oct  7 18:19:57 tardis kernel: hdc: IBM-DPTA-373420, ATA DISK drive
Oct  7 18:19:57 tardis kernel: hdd: MATSHITADVD-ROM SR-8582, ATAPI CDROM
drive
Oct  7 18:19:57 tardis kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct  7 18:19:57 tardis kernel: ide1 at 0x170-0x177,0x376 on irq 15

On 2.4.0-test9 I can't easily get a log saved; however it looks like its
saying that both ide0 and ide1 are on irq 21 and then complains that it is
loosing them.

It is not unusual for PCI devices on Alpha to have IRQs > 16 (indeed my
ether is on 17).

.config on request for anyone interested.

Dave

-- 
  Have a happy GNU millennium! --   
/ Dr. David Alan Gilbert  | Running GNU/Linux on   |  Happy  \ 
\   gro.gilbert @ treblig.org |  Alpha, x86, ARM and SPARC |  In Hex /
 |___ http://www.treblig.org  |/

-
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: Tux 2 patents

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 06:45:38PM +0200, Daniel Phillips wrote:
> Marty Fouts wrote:
> > 
> Well, I like your version more than Jeff's because if you're right then
> I still have time to make a whitehat patent application for my better
> atomic commit method.  What's a whitehat patent?  It's one that helps
> fence in companies who want to use patented algorithms in closed source
> software.  Whitehat patents will help convince the blackhats that it's
> in their interest to disallow algorithm patents and put things back the
> way they were before.


Daniel,

Do you want me to continue the patent attorney's analysis or not?  If I'm
spending money to help you here, I would appreciate you not bouncing off the
walls.  I am also having this guy put togther a provisional patent application
for your stuff, if you want to obtain a patent.  You are not going to 
change the USPTO, that's the system here, and like it or not, we all
just have to live with it.  The USPTO's authority is consitutional in 
it's basis regarding the rights of inventors (section 113), and unless
Congress and the Senate ammend the constitution, the USPTO and the rights
of inventors in the US will be protected. 

The list lurker non-lawyer technocrats waiving web pages around don't 
change the system, or provide the resources to help you.
 
Jeff

> 
> --
> Daniel
> -
> 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: Quantum lct08 & Ultra66 on GigaByte GA-BX2000+

2000-10-07 Thread Andre Hedrick


Read the source code and put the complete drive name in the quirk list for
that chipset.

On Sat, 7 Oct 2000, Mikhail Vladimirov wrote:

> Hi, people!
> Here I am :-)
> I just want to remember: It's already test9 but... :-(
> All what I certainly have is kernel panic at FS mounting point.
> Nothing was changed in other words
> Think everybody may have my experience, trying to install 2.4.0 to Quantum lct08 
>UDMA66 drive
> attached as a slave to primary Promise Ultra66 controller.
> 
> So, I am still forced to load my poor linux from diskette with kernel 2.2.5-15
> And nobody can help me!
> I'm crying :(
> God knows even Windows95 works fine with both of my HDD
> 2.4.0 still does not!
> 
> Regards,
> Mike
> 
> P.S.
> Everything you need (details I mean, and if you Really need it of course) you can 
>find
> in my previous messages which (I hope) have been stored in archive
> 
> 

Andre Hedrick
The Linux ATA/IDE guy

-
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: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 10:03:34AM +0200, Jens Axboe wrote:
> On Sat, Oct 07 2000, Dax Kelson wrote:
> > > BTW, how did your testing of the speed=4 problem with ide-scsi turn
> > > out.  We are still seeing the speed=2 problem on 2.4.0-pre9.  I cannot
> > > get the drive to burn clean unless the speed setting is cranked down to
> > > speed=2.
> > > 
> > > Jeff 
> > 
> > I just burned Red Hat 7.0 disk1 iso image at on a SCSI 4x burner without
> > any problems.  I have an IDE Plextor 12x burner at work, Monday I'll try a
> > burn under 2.4.0-test9.
> 
> [snip]
> 
> I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
> problems (this is on two different atapi writers). This could be an
> ide-scsi bug on some models. The folks who are seeing corruption, could
> they try and narrow it down? Is it random data getting written, or
> data from other locations?

I think it's related to the drive type in some way.  What we are seeing
is the CD burner hang on the first write to track 0.  Once it starts
burning, it seems to work fine, and we have even got some clean burns
at speed=4, however, when it's set this way, we occasionally see cdrecord
hang when it attempts to write the first track of a CD.  It ruins the 
CD in the burner, BTW when this happens.  I also see an I/O error message
from the ide-scsi driver about a timeout and data error 
(but I did not write it down -- sorry).  

I will burn some more CD's today, and will try to get more info.  Config 
is:

in lilo.conf:

append "hdd=ide-scsi"

and the CDROM device is mapped to:

/dev/scd0

and I load the ide-scsi module:

insmod ide-scsi

and:

cdrecord -scanbus.

Then we use the system to burn CD's all day.

Jeff


> 
> -- 
> * Jens Axboe <[EMAIL PROTECTED]>
> * SuSE Labs
-
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: Tux 2 patents

2000-10-07 Thread Jeff V. Merkey

On Fri, Oct 06, 2000 at 09:11:44PM -0700, Marty Fouts wrote:
> I don't know a lawyer I would trust who would give free legal advice on a
> mailing list without the usual disclaimers.

You should go back and read the start of this thread.  I've hired an 
IP Patent attorney to handle the Tux 2 Patent issue, and will be posting 
his analysis back to this community.  I have forwarded Daniel's 
designs and the specific patents and we are performing an infringement 
analysis. 

I think it's great that the USPTO has a website, but it's no subsitute
for "real" legal help to folks on this list.

Jeff


> 
> And I don't care what you've done elsewhere, you have, here, been misleading
> about patent law. I stand by my recommendation that people who are
> interested should read the Nolo Press book and then, if they have specific
> issues, consult an IP lawyer on those particular issues.
> 
> In addition to the Nolo press, by the way, the US Patent Office now has a
> web site with good general information for those people who are interested
> in US patent issues.  (http://www.uspto.gov/) I suppose there is a similar
> web site for people interested in EU patent specifics as well.  One of the
> serveral ways in which you were mistaken in your assertions is that you've
> neglected to clarify where US Patent Law differs from Patent Law in other
> jurisdictions.  You may be in Utah, but not everyone on this mailing list
> is.
> 
> 
> 
> 
> > -Original Message-
> > From: Jeff V. Merkey [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, October 06, 2000 3:40 PM
> > To: Marty Fouts
> > Cc: 'jesse'; [EMAIL PROTECTED]
> > Subject: Re: Tux 2 patents
> > 
> > 
> > 
> > 
> > Marty Fouts wrote:
> > > 
> > > I don't do pissing matches, Jeff, and won't compare the 
> > quality of the IP
> > > experts I have access to to the quality of those you have access to.
> > > 
> > > I will say that you are wrong about disclosure because you 
> > have overly
> > > simplified, and again recommend that people who care should 
> > discuss their
> > > specific cases with real lawyers, which neither you no or I are.
> > 
> > Excuse me -- I was one of the attorneys on the Novell/TRG lawsuit --
> > check my motions
> > and filings.  In fact, check the 4th District Court in general for my
> > filings in other cases.  You can check the Texas courts for 1980's as
> > well.  Just because I have been a software 
> > engineer for the past 20 years does not mean I did something else in a
> > previous life. 
> > 
> > Since all my friends are lawyers and TRG runs a law firm out of here
> > should say something.
-
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/



Newer motherboards / CPU's / hardware with Linux

2000-10-07 Thread Mike A. Harris

I've been considering a possible upgrade now for quite a while,
but wanted to wait until just the right time to do so.  The
purpose of an upgrade of course to get more performance out of
the system.

I got a freebie loaner upgrade recently from a K6-200 to a
K62-350.  I had to clock the chip to 300 for reliable operation
however.  After that, I noticed my hard drives were running at
half the speed as they did previously.  (5M/s instead of 10M/s)
That is with identical hdparm settings and no DMA.

I got Andre's latest IDE patches and applied, etc. and got my
disks back to speed (VIA MVP3 chipset), but not to the speed I
would have expected.  Nonetheless it is much much better now, and
a definite improvement over the last board/CPU I was using.

After the problems I experienced though, I wondered just how many
problems would I be in for if I bought a brand new Athlon 800
system?  Would it run like a P100 due to lack of Linux hardware
support?  After reading stuff on lkml here, I'm starting to think
that such an upgrade would be a waste of money until maybe 2.4.10
or so.

So the question is basically:  Is the upgrade worthwhile?  Is
2.2.x or 2.4.x compatible with Athlon CPU's or are there problems
at all still?  What about Athlon motherboards and chipset
hardware?  Can I expect the IDE chipset to work?  Applying IDE
patches is ok, but I just want to know that I'm going to get more
than 10M/s out of the drives, and not fry them.  Those are my
main concerns, but I'd just like to know what the average
developer thinks of the idea of forking out cash for a highend
system right now and wether or not it is worth it yet.

If not, I'd rather wait until things are integrated with the
kernel proper and working.  If it *IS* ready now, what sort of
Athlon hardware is recommended for a developmental machine?

TIA



--
  Mike A. Harris  -  Linux advocate  -  Open source advocate
  Computer Consultant - Capslock Consulting
 Copyright 2000 all rights reserved
--

Need general help or technical support with Red Hat Linux 6.2?  Join the user 
support mailing list by sending a message to "[EMAIL PROTECTED]"
with the word "subscribe" on the subject line.

-
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: [OOPS] unloading ns558 driver in Linux 2.4.0-test9

2000-10-07 Thread Brian Gerst

"Forever shall I be." wrote:
> 
> I got this OOPS while unloading the ns558 module.. I don't think it did
> this in 2.4.0-test8, but I don't recall ever unloading it in test8..
> 
> I've attached the ksymoops output..
> 
> --
> Zinx Verituse(See headers for gpg/pgp key info)
> 
>   
> 
>oops.outName: oops.out
>Type: Plain Text (text/plain)

What kind of game port do you have?

-- 

Brian Gerst
-
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: Tux 2 patents

2000-10-07 Thread Daniel Phillips

Marty Fouts wrote:
> 
> I don't know a lawyer I would trust who would give free legal advice on a
> mailing list without the usual disclaimers.

You mean 'I am a lawyer but this is not legal advice'.  Hmm, I think the
fact that it's on a mailing list and doesn't say 'here's my advice'
should be disclaimer enough.  Of course IANAL, so I may be attempting to
lead you into a legal deathtrap ;-)

> And I don't care what you've done elsewhere, you have, here, been misleading
> about patent law. I stand by my recommendation that people who are
> interested should read the Nolo Press book and then, if they have specific
> issues, consult an IP lawyer on those particular issues.

Well, I like your version more than Jeff's because if you're right then
I still have time to make a whitehat patent application for my better
atomic commit method.  What's a whitehat patent?  It's one that helps
fence in companies who want to use patented algorithms in closed source
software.  Whitehat patents will help convince the blackhats that it's
in their interest to disallow algorithm patents and put things back the
way they were before.

Have I said publicly that I'm waiting to hear from NetApp about whether
they're going to write a GPL-compatible license for the patents in
question?  And thus remove all doubt about whether they conflict with my
work.  I'm not sure I said that - I'm saying it now.  So far, not a word
out of NetApp management, though I know they're well aware of the
issue.  My idea is that by waiting patiently and not accusing them of
being turds that they will find it a lot easier to take a deep breath
and do the right thing.

> In addition to the Nolo press, by the way, the US Patent Office now has a
> web site with good general information for those people who are interested
> in US patent issues.  (http://www.uspto.gov/) I suppose there is a similar
> web site for people interested in EU patent specifics as well.  One of the
> serveral ways in which you were mistaken in your assertions is that you've
> neglected to clarify where US Patent Law differs from Patent Law in other
> jurisdictions.  You may be in Utah, but not everyone on this mailing list
> is.

Yes, it's thoughtful of the USPTO to give us free access to documents
that state in precise terms exactly how we are being screwed.  What I
really want to see on the site is "patents on software are no longer
allowed, and we have invalidated all the ones that we granted in error".

--
Daniel
-
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/



Quantum lct08 & Ultra66 on GigaByte GA-BX2000+

2000-10-07 Thread Mikhail Vladimirov



Hi, people!
Here I am :-)
I just want to remember: It's already test9 but... 
:-(
All what I certainly have is kernel panic at FS 
mounting point.
Nothing was changed in other words
Think everybody may have my experience, trying to 
install 2.4.0 to Quantum lct08 UDMA66 drive
attached as a slave to primary Promise Ultra66 
controller.
 
So, I am still forced to load my poor linux from 
diskette with kernel 2.2.5-15
And nobody can help me!
I'm crying :(
God knows even Windows95 works fine with both of my 
HDD
2.4.0 still does not!
 
Regards,
Mike
 

P.S.
Everything you need (details I mean, and if you 
Really need it of course) you can find
in my previous messages which (I hope) have been stored in archive
 


"hdx=bswap" doesn't work in 2.4.0-test9

2000-10-07 Thread Chris Adams

I'm trying to read an IDE drive from a different architecture on my x86
PC, and "hda=bswap" doesn't seem to work anymore.  The option is
recognized (because I get "ide_setup: hda=bswap" in the boot output) but
it does not appear to have any effect.
-- 
Chris Adams <[EMAIL PROTECTED]>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
-
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/



[OOPS] unloading ns558 driver in Linux 2.4.0-test9

2000-10-07 Thread Forever shall I be.

I got this OOPS while unloading the ns558 module.. I don't think it did
this in 2.4.0-test8, but I don't recall ever unloading it in test8..

I've attached the ksymoops output..

-- 
Zinx Verituse(See headers for gpg/pgp key info)

ksymoops 2.3.4 on i686 2.4.0-test9.  Options used
 -V (default)
 -k /proc/ksyms (default)
 -l /proc/modules (default)
 -o /lib/modules/2.4.0-test9/ (default)
 -m /usr/src/linux/System.map (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.

Warning (compare_ksyms_lsmod): module ns558 is in lsmod but not in ksyms, probably no 
symbols exported
Unable to handle kernel NULL pointer dereference at virtual address 0004
 c01dbaa7
 *pde = 
 Oops: 0002
 CPU:0
 EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
 EFLAGS: 00010246
 eax:    ebx:    ecx: cf799000   edx: 
 esi: d0820a20   edi: d082   ebp: bfffe7cc   esp: ccce7f80
 ds: 0018   es: 0018   ss: 0018
 Process modprobe (pid: 13294, stackpage=ccce7000)
 Stack:  fff0 d0820696 d0820a20 d082 c011afd3 d082 fff0
c507 bfffe7cc c011a477 d082  ccce6000  bb15
c010a32f bb15 bb15   bb15 bfffe7cc 0081
 Call Trace: [] [] [] [] [] 
[] []
 []
 Code: 89 50 04 89 02 8b 1d c8 c2 2a c0 81 fb c8 c2 2a c0 74 29 8d

>>EIP; c01dbaa7<=
Trace; d0820696 <[joydev]__module_device+2253/dc11>
Trace; d0820a20 <[joydev]__module_device+25dd/dc11>
Trace; d082 <[joydev]__module_device+1bbd/dc11>
Trace; c011afd3 
Trace; d082 <[joydev]__module_device+1bbd/dc11>
Trace; c011a477 
Trace; d082 <[joydev]__module_device+1bbd/dc11>
Trace; c010a32f 
Code;  c01dbaa7 
 <_EIP>:
Code;  c01dbaa7<=
   0:   89 50 04  mov%edx,0x4(%eax)   <=
Code;  c01dbaaa 
   3:   89 02 mov%eax,(%edx)
Code;  c01dbaac 
   5:   8b 1d c8 c2 2a c0 mov0xc02ac2c8,%ebx
Code;  c01dbab2 
   b:   81 fb c8 c2 2a c0 cmp$0xc02ac2c8,%ebx
Code;  c01dbab8 
  11:   74 29 je 3c <_EIP+0x3c> c01dbae3 

Code;  c01dbaba 
  13:   8d 00 lea(%eax),%eax


2 warnings issued.  Results may not be reliable.



Re: ack number in a connection-refused RST

2000-10-07 Thread kuznet

Hello!

> namely, it only happens with probability 1/2^32 (you hope).

This can happen with probability close to 1 or even exactly 1,
depending on sequence number selection algorithm.

Alexey
-
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: Why does everyone hate gcc 2.95?

2000-10-07 Thread Kim Shepherd

Maybe some of us don't use white Xterms.. -bg black (can't remember if
that's exact, but it's something like that) isn't hard to do :)

- Original Message -
From: Henning P. Schmiedehausen <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 08, 2000 12:51 AM
Subject: Re: Why does everyone hate gcc 2.95?


> [EMAIL PROTECTED] (Jamie Lokier) writes:
>
> >Alexander Viro wrote:
> >> ITYM "cute". As in "cute dancing paperclip". As colourized ls.
>
> >Hey, colour ls is _useful_!
>
> Use white background Xterm. Come again?
>
> First thing I do on _all_ RH installations is "rm /etc/profile.d/colorls*"
>
> One of the biggest mistakes RH ever did was happily jumping off _that_
> cliff to follow SuSE.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen   -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
>
> Am Schwabachgrund 22  Fon.: 09131 / 50654-0   [EMAIL PROTECTED]
> D-91054 Buckenhof Fax.: 09131 / 50654-20
> -
> 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: Why does everyone hate gcc 2.95?

2000-10-07 Thread Henning P. Schmiedehausen

[EMAIL PROTECTED] (Jamie Lokier) writes:

>Alexander Viro wrote:
>> ITYM "cute". As in "cute dancing paperclip". As colourized ls.

>Hey, colour ls is _useful_!

Use white background Xterm. Come again?

First thing I do on _all_ RH installations is "rm /etc/profile.d/colorls*"

One of the biggest mistakes RH ever did was happily jumping off _that_
cliff to follow SuSE.

Regards
Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen   -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20   
-
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: Crashing 2.2.17 and 2.4.0-test* series on SMP Celeron.

2000-10-07 Thread David S. Miller

   From: Rienk de Vries <[EMAIL PROTECTED]>
   Date:Sat, 7 Oct 2000 12:49:56 +0200

   NMI watchdog detected LOCKUP CPU0
   CPU: 0
   EIP: 0010 : [}
   EFLAGS: 0086
   A lot of other figures I didnt jot down
   cconsole shuts up

You have to write down all the figures and either:

1) find the matching symbols by hand in your System.map

or

2) send your System.map along with the full set of "figures"

before anyone can try and work on this bug.

Later,
David S. Miller
[EMAIL PROTECTED]
-
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: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Andre Hedrick

> Something like this?

Close but now there is no select.

--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c   Sat Sep 23
01:04:46 2000
+++ drivers/scsi/ide-scsi.c Sat Oct  7 10:52:13 2000
@@ -435,7 +435,6 @@
+   SELECT_DRIVE(HWIF(drive), drive);
if (IDE_CONTROL_REG)
OUT_BYTE (drive->ctl,IDE_CONTROL_REG);
OUT_BYTE (dma_ok,IDE_FEATURE_REG);
OUT_BYTE (bcount >> 8,IDE_BCOUNTH_REG);
OUT_BYTE (bcount & 0xff,IDE_BCOUNTL_REG);
-   OUT_BYTE (drive->select.all,IDE_SELECT_REG);

if (dma_ok) {
set_bit (PC_DMA_IN_PROGRESS, >flags);

It is a macro issue and ordering task-registers.

Cheers,

Andre Hedrick
The Linux ATA/IDE guy

-
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/



Crashing 2.2.17 and 2.4.0-test* series on SMP Celeron.

2000-10-07 Thread Rienk de Vries

Hi,

With 2.2.16 My dual Celeron300A (FSB 66MHz) works flawlessly, merrily cracking
away with RC5DES for weeks on end,
But, when trying to upgrade to 2.4.0-test9, or 2.2.17, shit happens...

NMI watchdog detected LOCKUP CPU0
CPU: 0
EIP: 0010 : [}
EFLAGS: 0086
A lot of other figures I didnt jot down
cconsole shuts up

This doesn't even make it to the logs. it only gives this message with the 240
kernel. with 2217 it just freezes, (no messages) though I can than still
emergency sync and reboot.

But the network seems to stay up, the leds on my cablemodem keep on flashing
normally. Also booting in single user mode (init 1) works normally.
I switched off every "experimental option" (had to convert my filesystems back
to ext2 (from ReiserFS) to do that...), switched off the framebuffer stuff, to
no avail.

Output of ver_linux script:
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux knurkl 2.4.0-test9 #3 SMP do okt 5 10:35:45 CEST 2000 i686 unknown
Kernel modules 2.3.15
Gnu C  2.95.2
Gnu Make   3.77
Binutils   2.9.5.0.16
Linux C Library2.1.2
Dynamic linker ldd (GNU libc) 2.1.2
Procps 2.0.6
Mount  2.10o
Net-tools  1.53
Console-tools  0.2.2
Sh-utils   2.0
Modules Loaded nls_cp437 nls_iso8859-15 tlan

cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no  
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr
bogomips: 599.65

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr 
 
bogomips: 601.29

modules:
nls_cp437   4352   3 (autoclean)
nls_iso8859-15  3388   3
tlan   22332   0 (unused) 

When building a non SMP kernel, things started working normally again.. 
The above output was made when running a non-SMP-2.4.0-test9.


Thanks for having a look at this..


-- 
Met vriendelijke groet,
Rienk

rdv@.chello.nl
rvries.6@.hccnet.nl
ICQ 49322958
Homepage:  http://www.penguinpowered.com/~rienk 
-
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/



Crashing 2.2.17 and 2.4.0-test* series on SMP Celeron.

2000-10-07 Thread Rienk de Vries

Hi,

With 2.2.16 My dual Celeron300A (FSB 66MHz) works flawlessly, merrily cracking
away with RC5DES for weeks on end,
But, when trying to upgrade to 2.4.0-test9, or 2.2.17, shit happens...

NMI watchdog detected LOCKUP CPU0
CPU: 0
EIP: 0010 : [}
EFLAGS: 0086
A lot of other figures I didnt jot down
cconsole shuts up

This doesn't even make it to the logs. it only gives this message with the 240
kernel. with 2217 it just freezes, (no messages) though I can than still
emergency sync and reboot.

But the network seems to stay up, the leds on my cablemodem keep on flashing
normally. Also booting in single user mode (init 1) works normally.
I switched off every "experimental option" (had to convert my filesystems back
to ext2 (from ReiserFS) to do that...), switched off the framebuffer stuff, to
no avail.

Output of ver_linux script:
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux knurkl 2.4.0-test9 #3 SMP do okt 5 10:35:45 CEST 2000 i686 unknown
Kernel modules 2.3.15
Gnu C  2.95.2
Gnu Make   3.77
Binutils   2.9.5.0.16
Linux C Library2.1.2
Dynamic linker ldd (GNU libc) 2.1.2
Procps 2.0.6
Mount  2.10o
Net-tools  1.53
Console-tools  0.2.2
Sh-utils   2.0
Modules Loaded nls_cp437 nls_iso8859-15 tlan

cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no  
 sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr
bogomips: 599.65

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr 
 
bogomips: 601.29

modules:
nls_cp437   4352   3 (autoclean)
nls_iso8859-15  3388   3
tlan   22332   0 (unused) 

When building a non SMP kernel, things started working normally again.. 
The above output was made when running a non-SMP-2.4.0-test9.


Thanks for having a look at this..



-- 
Met vriendelijke groet,
Rienk

rdv@.chello.nl
rvries.6@.hccnet.nl
ICQ 49322958
Homepage:  http://www.penguinpowered.com/~rienk 
-
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: SoundFusion/Cirrus Logic CS4630 sound chipset support

2000-10-07 Thread Jeff Garzik

On Sat, 7 Oct 2000, David Ford wrote:
> Does anyone have any driver for this, or does anyone have a driver that
> has been started?

What's the PCI id?  Does drivers/sound/cs46xx.c work after adding your
PCI id?

Jeff





-
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: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Jens Axboe

On Sat, Oct 07 2000, Andre Hedrick wrote:
> > I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
> > problems (this is on two different atapi writers). This could be an
> > ide-scsi bug on some models. The folks who are seeing corruption, could
> > they try and narrow it down? Is it random data getting written, or
> > data from other locations?
> 
> If it is ide-scsi then it is device select bug that is know but never made
> it in the kernel.  I have the fix.
> 
> Plextor is one on the list that fails without it.

Something like this?

-- 
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs


--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c   Sat Sep 23 01:04:46 
2000
+++ drivers/scsi/ide-scsi.c Sat Oct  7 10:52:13 2000
@@ -435,7 +435,6 @@
OUT_BYTE (dma_ok,IDE_FEATURE_REG);
OUT_BYTE (bcount >> 8,IDE_BCOUNTH_REG);
OUT_BYTE (bcount & 0xff,IDE_BCOUNTL_REG);
-   OUT_BYTE (drive->select.all,IDE_SELECT_REG);
 
if (dma_ok) {
set_bit (PC_DMA_IN_PROGRESS, >flags);



Re: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Andre Hedrick

On Sat, 7 Oct 2000, Jens Axboe wrote:

> I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
> problems (this is on two different atapi writers). This could be an
> ide-scsi bug on some models. The folks who are seeing corruption, could
> they try and narrow it down? Is it random data getting written, or
> data from other locations?

If it is ide-scsi then it is device select bug that is know but never made
it in the kernel.  I have the fix.

Plextor is one on the list that fails without it.

Cheers,

Andre Hedrick
The Linux ATA/IDE guy

-
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: No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Jens Axboe

On Sat, Oct 07 2000, Dax Kelson wrote:
> > BTW, how did your testing of the speed=4 problem with ide-scsi turn
> > out.  We are still seeing the speed=2 problem on 2.4.0-pre9.  I cannot
> > get the drive to burn clean unless the speed setting is cranked down to
> > speed=2.
> > 
> > Jeff 
> 
> I just burned Red Hat 7.0 disk1 iso image at on a SCSI 4x burner without
> any problems.  I have an IDE Plextor 12x burner at work, Monday I'll try a
> burn under 2.4.0-test9.

[snip]

I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
problems (this is on two different atapi writers). This could be an
ide-scsi bug on some models. The folks who are seeing corruption, could
they try and narrow it down? Is it random data getting written, or
data from other locations?

-- 
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs
-
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/



SoundFusion/Cirrus Logic CS4630 sound chipset support

2000-10-07 Thread David Ford

Does anyone have any driver for this, or does anyone have a driver that
has been started?

-d

--
  "There is a natural aristocracy among men. The grounds of this are
  virtue and talents", Thomas Jefferson [1742-1826], 3rd US President



-
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/



2.4.0-test9 kernel problems (was 2.4 kernel problems on 386)

2000-10-07 Thread johna

I had problems loading a variant of this kernel on a 386. The problems
are now more obvious, as I've tried to operate this kernel, compiled for
a 386, on my pentium pro.

In this case, the kernel starts up, but has no communication with the
screen. No messages are logged to the screen. However, the messages are
logged to the disk. A message : Cannot find map file, and also :
Warning: unable to open an initial console. appear on the log, I can
forward more detail to anyone who is interested.

When I run the kernel on a 386, as far as I can tell, the machine just
plain halts and does nothing. If the kernel is compiled using gcc version 
2.95.2, then it reboots on a 386. On the Pentium Pro, the behaviour is
the same.

Seems a bit odd that what would be a standard patch seems to be causing
this problem. Could be that a file or device is expected on the filesystem,
but it is not obvious from the logs.

There could indeed be a triple fault, as a previous participant suggested -
but I would not know. Getting the kernel to at least print on my pentium
pro would be a start.

Any ideas ?

I'm not on the list, so please copy me in correspondence.

Thanks,

-- 
John August

Some of us are paying for sins we have committed.
Others are paying for sins we still have to commit.
-
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/



No SCSI burning problem (was: Bug in "ide-pci.c")

2000-10-07 Thread Dax Kelson

Jeff V. Merkey said once upon a time (Fri, 6 Oct 2000):

> 
> Andre,
> 
> BTW, how did your testing of the speed=4 problem with ide-scsi turn
> out.  We are still seeing the speed=2 problem on 2.4.0-pre9.  I cannot
> get the drive to burn clean unless the speed setting is cranked down to
> speed=2.
> 
> Jeff 

I just burned Red Hat 7.0 disk1 iso image at on a SCSI 4x burner without
any problems.  I have an IDE Plextor 12x burner at work, Monday I'll try a
burn under 2.4.0-test9.

distro: Red Hat 7.0
kernel: 2.4.0-test9-pre8
Cdrecord 1.9
True SCSI Yamaha 4x burner

(scsi0)  found at PCI 0/16/0
(scsi0:0:4:0) Synchronous at 8.0 Mbyte/sec, offset 15.
  Vendor: YAMAHAModel: CRW4416S  Rev: 1.0j
  Type:   CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0
Uniform CD-ROM driver Revision: 3.11
sr1: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray


[root@localhost burn]# md5sum redhat-7.0-disc1.iso 
626b7d18033e320c27c8cd58cc37a288  redhat-7.0-disc1.iso

[did a 4x burn]

[root@localhost dkelson]# md5sum /dev/scd1
626b7d18033e320c27c8cd58cc37a288  /dev/scd1


-
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/



No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Dax Kelson

Jeff V. Merkey said once upon a time (Fri, 6 Oct 2000):

 
 Andre,
 
 BTW, how did your testing of the speed=4 problem with ide-scsi turn
 out.  We are still seeing the speed=2 problem on 2.4.0-pre9.  I cannot
 get the drive to burn clean unless the speed setting is cranked down to
 speed=2.
 
 Jeff 

I just burned Red Hat 7.0 disk1 iso image at on a SCSI 4x burner without
any problems.  I have an IDE Plextor 12x burner at work, Monday I'll try a
burn under 2.4.0-test9.

distro: Red Hat 7.0
kernel: 2.4.0-test9-pre8
Cdrecord 1.9
True SCSI Yamaha 4x burner

(scsi0) Adaptec AHA-2940UW Pro Ultra SCSI host adapter found at PCI 0/16/0
(scsi0:0:4:0) Synchronous at 8.0 Mbyte/sec, offset 15.
  Vendor: YAMAHAModel: CRW4416S  Rev: 1.0j
  Type:   CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0
Uniform CD-ROM driver Revision: 3.11
sr1: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray


[root@localhost burn]# md5sum redhat-7.0-disc1.iso 
626b7d18033e320c27c8cd58cc37a288  redhat-7.0-disc1.iso

[did a 4x burn]

[root@localhost dkelson]# md5sum /dev/scd1
626b7d18033e320c27c8cd58cc37a288  /dev/scd1


-
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/



2.4.0-test9 kernel problems (was 2.4 kernel problems on 386)

2000-10-07 Thread johna

I had problems loading a variant of this kernel on a 386. The problems
are now more obvious, as I've tried to operate this kernel, compiled for
a 386, on my pentium pro.

In this case, the kernel starts up, but has no communication with the
screen. No messages are logged to the screen. However, the messages are
logged to the disk. A message : Cannot find map file, and also :
Warning: unable to open an initial console. appear on the log, I can
forward more detail to anyone who is interested.

When I run the kernel on a 386, as far as I can tell, the machine just
plain halts and does nothing. If the kernel is compiled using gcc version 
2.95.2, then it reboots on a 386. On the Pentium Pro, the behaviour is
the same.

Seems a bit odd that what would be a standard patch seems to be causing
this problem. Could be that a file or device is expected on the filesystem,
but it is not obvious from the logs.

There could indeed be a triple fault, as a previous participant suggested -
but I would not know. Getting the kernel to at least print on my pentium
pro would be a start.

Any ideas ?

I'm not on the list, so please copy me in correspondence.

Thanks,

-- 
John August

Some of us are paying for sins we have committed.
Others are paying for sins we still have to commit.
-
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/



SoundFusion/Cirrus Logic CS4630 sound chipset support

2000-10-07 Thread David Ford

Does anyone have any driver for this, or does anyone have a driver that
has been started?

-d

--
  "There is a natural aristocracy among men. The grounds of this are
  virtue and talents", Thomas Jefferson [1742-1826], 3rd US President



-
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: No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Jens Axboe

On Sat, Oct 07 2000, Dax Kelson wrote:
  BTW, how did your testing of the speed=4 problem with ide-scsi turn
  out.  We are still seeing the speed=2 problem on 2.4.0-pre9.  I cannot
  get the drive to burn clean unless the speed setting is cranked down to
  speed=2.
  
  Jeff 
 
 I just burned Red Hat 7.0 disk1 iso image at on a SCSI 4x burner without
 any problems.  I have an IDE Plextor 12x burner at work, Monday I'll try a
 burn under 2.4.0-test9.

[snip]

I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
problems (this is on two different atapi writers). This could be an
ide-scsi bug on some models. The folks who are seeing corruption, could
they try and narrow it down? Is it random data getting written, or
data from other locations?

-- 
* Jens Axboe [EMAIL PROTECTED]
* SuSE Labs
-
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: No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Andre Hedrick

On Sat, 7 Oct 2000, Jens Axboe wrote:

 I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
 problems (this is on two different atapi writers). This could be an
 ide-scsi bug on some models. The folks who are seeing corruption, could
 they try and narrow it down? Is it random data getting written, or
 data from other locations?

If it is ide-scsi then it is device select bug that is know but never made
it in the kernel.  I have the fix.

Plextor is one on the list that fails without it.

Cheers,

Andre Hedrick
The Linux ATA/IDE guy

-
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: No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Jens Axboe

On Sat, Oct 07 2000, Andre Hedrick wrote:
  I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
  problems (this is on two different atapi writers). This could be an
  ide-scsi bug on some models. The folks who are seeing corruption, could
  they try and narrow it down? Is it random data getting written, or
  data from other locations?
 
 If it is ide-scsi then it is device select bug that is know but never made
 it in the kernel.  I have the fix.
 
 Plextor is one on the list that fails without it.

Something like this?

-- 
* Jens Axboe [EMAIL PROTECTED]
* SuSE Labs


--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c   Sat Sep 23 01:04:46 
2000
+++ drivers/scsi/ide-scsi.c Sat Oct  7 10:52:13 2000
@@ -435,7 +435,6 @@
OUT_BYTE (dma_ok,IDE_FEATURE_REG);
OUT_BYTE (bcount  8,IDE_BCOUNTH_REG);
OUT_BYTE (bcount  0xff,IDE_BCOUNTL_REG);
-   OUT_BYTE (drive-select.all,IDE_SELECT_REG);
 
if (dma_ok) {
set_bit (PC_DMA_IN_PROGRESS, pc-flags);



Re: SoundFusion/Cirrus Logic CS4630 sound chipset support

2000-10-07 Thread Jeff Garzik

On Sat, 7 Oct 2000, David Ford wrote:
 Does anyone have any driver for this, or does anyone have a driver that
 has been started?

What's the PCI id?  Does drivers/sound/cs46xx.c work after adding your
PCI id?

Jeff





-
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/



Crashing 2.2.17 and 2.4.0-test* series on SMP Celeron.

2000-10-07 Thread Rienk de Vries

Hi,

With 2.2.16 My dual Celeron300A (FSB 66MHz) works flawlessly, merrily cracking
away with RC5DES for weeks on end,
But, when trying to upgrade to 2.4.0-test9, or 2.2.17, shit happens...

NMI watchdog detected LOCKUP CPU0
CPU: 0
EIP: 0010 : [c88272f8}
EFLAGS: 0086
A lot of other figures I didnt jot down
cconsole shuts up

This doesn't even make it to the logs. it only gives this message with the 240
kernel. with 2217 it just freezes, (no messages) though I can than still
emergency sync and reboot.

But the network seems to stay up, the leds on my cablemodem keep on flashing
normally. Also booting in single user mode (init 1) works normally.
I switched off every "experimental option" (had to convert my filesystems back
to ext2 (from ReiserFS) to do that...), switched off the framebuffer stuff, to
no avail.

Output of ver_linux script:
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux knurkl 2.4.0-test9 #3 SMP do okt 5 10:35:45 CEST 2000 i686 unknown
Kernel modules 2.3.15
Gnu C  2.95.2
Gnu Make   3.77
Binutils   2.9.5.0.16
Linux C Library2.1.2
Dynamic linker ldd (GNU libc) 2.1.2
Procps 2.0.6
Mount  2.10o
Net-tools  1.53
Console-tools  0.2.2
Sh-utils   2.0
Modules Loaded nls_cp437 nls_iso8859-15 tlan

cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no  
 sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr
bogomips: 599.65

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr 
 
bogomips: 601.29

modules:
nls_cp437   4352   3 (autoclean)
nls_iso8859-15  3388   3
tlan   22332   0 (unused) 

When building a non SMP kernel, things started working normally again.. 
The above output was made when running a non-SMP-2.4.0-test9.


Thanks for having a look at this..



-- 
Met vriendelijke groet,
Rienk

rdv@.chello.nl
rvries.6@.hccnet.nl
ICQ 49322958
Homepage:  http://www.penguinpowered.com/~rienk 
-
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/



Crashing 2.2.17 and 2.4.0-test* series on SMP Celeron.

2000-10-07 Thread Rienk de Vries

Hi,

With 2.2.16 My dual Celeron300A (FSB 66MHz) works flawlessly, merrily cracking
away with RC5DES for weeks on end,
But, when trying to upgrade to 2.4.0-test9, or 2.2.17, shit happens...

NMI watchdog detected LOCKUP CPU0
CPU: 0
EIP: 0010 : [c88272f8}
EFLAGS: 0086
A lot of other figures I didnt jot down
cconsole shuts up

This doesn't even make it to the logs. it only gives this message with the 240
kernel. with 2217 it just freezes, (no messages) though I can than still
emergency sync and reboot.

But the network seems to stay up, the leds on my cablemodem keep on flashing
normally. Also booting in single user mode (init 1) works normally.
I switched off every "experimental option" (had to convert my filesystems back
to ext2 (from ReiserFS) to do that...), switched off the framebuffer stuff, to
no avail.

Output of ver_linux script:
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux knurkl 2.4.0-test9 #3 SMP do okt 5 10:35:45 CEST 2000 i686 unknown
Kernel modules 2.3.15
Gnu C  2.95.2
Gnu Make   3.77
Binutils   2.9.5.0.16
Linux C Library2.1.2
Dynamic linker ldd (GNU libc) 2.1.2
Procps 2.0.6
Mount  2.10o
Net-tools  1.53
Console-tools  0.2.2
Sh-utils   2.0
Modules Loaded nls_cp437 nls_iso8859-15 tlan

cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no  
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr
bogomips: 599.65

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 6
model name  : Celeron (Mendocino)
stepping: 5
cpu MHz : 300.000683
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 mmx fxsr 
 
bogomips: 601.29

modules:
nls_cp437   4352   3 (autoclean)
nls_iso8859-15  3388   3
tlan   22332   0 (unused) 

When building a non SMP kernel, things started working normally again.. 
The above output was made when running a non-SMP-2.4.0-test9.


Thanks for having a look at this..


-- 
Met vriendelijke groet,
Rienk

rdv@.chello.nl
rvries.6@.hccnet.nl
ICQ 49322958
Homepage:  http://www.penguinpowered.com/~rienk 
-
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: No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Andre Hedrick

 Something like this?

Close but now there is no select.

--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c   Sat Sep 23
01:04:46 2000
+++ drivers/scsi/ide-scsi.c Sat Oct  7 10:52:13 2000
@@ -435,7 +435,6 @@
+   SELECT_DRIVE(HWIF(drive), drive);
if (IDE_CONTROL_REG)
OUT_BYTE (drive-ctl,IDE_CONTROL_REG);
OUT_BYTE (dma_ok,IDE_FEATURE_REG);
OUT_BYTE (bcount  8,IDE_BCOUNTH_REG);
OUT_BYTE (bcount  0xff,IDE_BCOUNTL_REG);
-   OUT_BYTE (drive-select.all,IDE_SELECT_REG);

if (dma_ok) {
set_bit (PC_DMA_IN_PROGRESS, pc-flags);

It is a macro issue and ordering task-registers.

Cheers,

Andre Hedrick
The Linux ATA/IDE guy

-
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: Crashing 2.2.17 and 2.4.0-test* series on SMP Celeron.

2000-10-07 Thread David S. Miller

   From: Rienk de Vries [EMAIL PROTECTED]
   Date:Sat, 7 Oct 2000 12:49:56 +0200

   NMI watchdog detected LOCKUP CPU0
   CPU: 0
   EIP: 0010 : [c88272f8}
   EFLAGS: 0086
   A lot of other figures I didnt jot down
   cconsole shuts up

You have to write down all the figures and either:

1) find the matching symbols by hand in your System.map

or

2) send your System.map along with the full set of "figures"

before anyone can try and work on this bug.

Later,
David S. Miller
[EMAIL PROTECTED]
-
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: Why does everyone hate gcc 2.95?

2000-10-07 Thread Henning P. Schmiedehausen

[EMAIL PROTECTED] (Jamie Lokier) writes:

Alexander Viro wrote:
 ITYM "cute". As in "cute dancing paperclip". As colourized ls.

Hey, colour ls is _useful_!

Use white background Xterm. Come again?

First thing I do on _all_ RH installations is "rm /etc/profile.d/colorls*"

One of the biggest mistakes RH ever did was happily jumping off _that_
cliff to follow SuSE.

Regards
Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen   -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20   
-
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: Why does everyone hate gcc 2.95?

2000-10-07 Thread Kim Shepherd

Maybe some of us don't use white Xterms.. -bg black (can't remember if
that's exact, but it's something like that) isn't hard to do :)

- Original Message -
From: Henning P. Schmiedehausen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 08, 2000 12:51 AM
Subject: Re: Why does everyone hate gcc 2.95?


 [EMAIL PROTECTED] (Jamie Lokier) writes:

 Alexander Viro wrote:
  ITYM "cute". As in "cute dancing paperclip". As colourized ls.

 Hey, colour ls is _useful_!

 Use white background Xterm. Come again?

 First thing I do on _all_ RH installations is "rm /etc/profile.d/colorls*"

 One of the biggest mistakes RH ever did was happily jumping off _that_
 cliff to follow SuSE.

 Regards
 Henning

 --
 Dipl.-Inf. (Univ.) Henning P. Schmiedehausen   -- Geschaeftsfuehrer
 INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]

 Am Schwabachgrund 22  Fon.: 09131 / 50654-0   [EMAIL PROTECTED]
 D-91054 Buckenhof Fax.: 09131 / 50654-20
 -
 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: ack number in a connection-refused RST

2000-10-07 Thread kuznet

Hello!

 namely, it only happens with probability 1/2^32 (you hope).

This can happen with probability close to 1 or even exactly 1,
depending on sequence number selection algorithm.

Alexey
-
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/



[OOPS] unloading ns558 driver in Linux 2.4.0-test9

2000-10-07 Thread Forever shall I be.

I got this OOPS while unloading the ns558 module.. I don't think it did
this in 2.4.0-test8, but I don't recall ever unloading it in test8..

I've attached the ksymoops output..

-- 
Zinx Verituse(See headers for gpg/pgp key info)

ksymoops 2.3.4 on i686 2.4.0-test9.  Options used
 -V (default)
 -k /proc/ksyms (default)
 -l /proc/modules (default)
 -o /lib/modules/2.4.0-test9/ (default)
 -m /usr/src/linux/System.map (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.

Warning (compare_ksyms_lsmod): module ns558 is in lsmod but not in ksyms, probably no 
symbols exported
Unable to handle kernel NULL pointer dereference at virtual address 0004
 c01dbaa7
 *pde = 
 Oops: 0002
 CPU:0
 EIP:0010:[c01dbaa7]
Using defaults from ksymoops -t elf32-i386 -a i386
 EFLAGS: 00010246
 eax:    ebx:    ecx: cf799000   edx: 
 esi: d0820a20   edi: d082   ebp: bfffe7cc   esp: ccce7f80
 ds: 0018   es: 0018   ss: 0018
 Process modprobe (pid: 13294, stackpage=ccce7000)
 Stack:  fff0 d0820696 d0820a20 d082 c011afd3 d082 fff0
c507 bfffe7cc c011a477 d082  ccce6000  bb15
c010a32f bb15 bb15   bb15 bfffe7cc 0081
 Call Trace: [d0820696] [d0820a20] [d082] [c011afd3] [d082] 
[c011a477] [d082]
 [c010a32f]
 Code: 89 50 04 89 02 8b 1d c8 c2 2a c0 81 fb c8 c2 2a c0 74 29 8d

EIP; c01dbaa7 pci_unregister_driver+b/4c   =
Trace; d0820696 [joydev]__module_device+2253/dc11
Trace; d0820a20 [joydev]__module_device+25dd/dc11
Trace; d082 [joydev]__module_device+1bbd/dc11
Trace; c011afd3 free_module+17/98
Trace; d082 [joydev]__module_device+1bbd/dc11
Trace; c011a477 sys_delete_module+103/1c0
Trace; d082 [joydev]__module_device+1bbd/dc11
Trace; c010a32f system_call+33/38
Code;  c01dbaa7 pci_unregister_driver+b/4c
 _EIP:
Code;  c01dbaa7 pci_unregister_driver+b/4c   =
   0:   89 50 04  mov%edx,0x4(%eax)   =
Code;  c01dbaaa pci_unregister_driver+e/4c
   3:   89 02 mov%eax,(%edx)
Code;  c01dbaac pci_unregister_driver+10/4c
   5:   8b 1d c8 c2 2a c0 mov0xc02ac2c8,%ebx
Code;  c01dbab2 pci_unregister_driver+16/4c
   b:   81 fb c8 c2 2a c0 cmp$0xc02ac2c8,%ebx
Code;  c01dbab8 pci_unregister_driver+1c/4c
  11:   74 29 je 3c _EIP+0x3c c01dbae3 
pci_unregister_driver+47/4c
Code;  c01dbaba pci_unregister_driver+1e/4c
  13:   8d 00 lea(%eax),%eax


2 warnings issued.  Results may not be reliable.



hdx=bswap doesn't work in 2.4.0-test9

2000-10-07 Thread Chris Adams

I'm trying to read an IDE drive from a different architecture on my x86
PC, and "hda=bswap" doesn't seem to work anymore.  The option is
recognized (because I get "ide_setup: hda=bswap" in the boot output) but
it does not appear to have any effect.
-- 
Chris Adams [EMAIL PROTECTED]
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
-
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/



Quantum lct08 Ultra66 on GigaByte GA-BX2000+

2000-10-07 Thread Mikhail Vladimirov



Hi, people!
Here I am :-)
I just want to remember: It's already test9 but... 
:-(
All what I certainly have is kernel panic at FS 
mounting point.
Nothing was changed in other words
Think everybody may have my experience, trying to 
install 2.4.0 to Quantum lct08 UDMA66 drive
attached as a slave to primary Promise Ultra66 
controller.

So, I am still forced to load my poor linux from 
diskette with kernel 2.2.5-15
And nobody can help me!
I'm crying :(
God knows even Windows95 works fine with both of my 
HDD
2.4.0 still does not!

Regards,
Mike


P.S.
Everything you need (details I mean, and if you 
Really need it of course) you can find
in my previous messages which (I hope) have been stored in archive



Re: Tux 2 patents

2000-10-07 Thread Daniel Phillips

Marty Fouts wrote:
 
 I don't know a lawyer I would trust who would give free legal advice on a
 mailing list without the usual disclaimers.

You mean 'I am a lawyer but this is not legal advice'.  Hmm, I think the
fact that it's on a mailing list and doesn't say 'here's my advice'
should be disclaimer enough.  Of course IANAL, so I may be attempting to
lead you into a legal deathtrap ;-)

 And I don't care what you've done elsewhere, you have, here, been misleading
 about patent law. I stand by my recommendation that people who are
 interested should read the Nolo Press book and then, if they have specific
 issues, consult an IP lawyer on those particular issues.

Well, I like your version more than Jeff's because if you're right then
I still have time to make a whitehat patent application for my better
atomic commit method.  What's a whitehat patent?  It's one that helps
fence in companies who want to use patented algorithms in closed source
software.  Whitehat patents will help convince the blackhats that it's
in their interest to disallow algorithm patents and put things back the
way they were before.

Have I said publicly that I'm waiting to hear from NetApp about whether
they're going to write a GPL-compatible license for the patents in
question?  And thus remove all doubt about whether they conflict with my
work.  I'm not sure I said that - I'm saying it now.  So far, not a word
out of NetApp management, though I know they're well aware of the
issue.  My idea is that by waiting patiently and not accusing them of
being turds that they will find it a lot easier to take a deep breath
and do the right thing.

 In addition to the Nolo press, by the way, the US Patent Office now has a
 web site with good general information for those people who are interested
 in US patent issues.  (http://www.uspto.gov/) I suppose there is a similar
 web site for people interested in EU patent specifics as well.  One of the
 serveral ways in which you were mistaken in your assertions is that you've
 neglected to clarify where US Patent Law differs from Patent Law in other
 jurisdictions.  You may be in Utah, but not everyone on this mailing list
 is.

Yes, it's thoughtful of the USPTO to give us free access to documents
that state in precise terms exactly how we are being screwed.  What I
really want to see on the site is "patents on software are no longer
allowed, and we have invalidated all the ones that we granted in error".

--
Daniel
-
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/



Newer motherboards / CPU's / hardware with Linux

2000-10-07 Thread Mike A. Harris

I've been considering a possible upgrade now for quite a while,
but wanted to wait until just the right time to do so.  The
purpose of an upgrade of course to get more performance out of
the system.

I got a freebie loaner upgrade recently from a K6-200 to a
K62-350.  I had to clock the chip to 300 for reliable operation
however.  After that, I noticed my hard drives were running at
half the speed as they did previously.  (5M/s instead of 10M/s)
That is with identical hdparm settings and no DMA.

I got Andre's latest IDE patches and applied, etc. and got my
disks back to speed (VIA MVP3 chipset), but not to the speed I
would have expected.  Nonetheless it is much much better now, and
a definite improvement over the last board/CPU I was using.

After the problems I experienced though, I wondered just how many
problems would I be in for if I bought a brand new Athlon 800
system?  Would it run like a P100 due to lack of Linux hardware
support?  After reading stuff on lkml here, I'm starting to think
that such an upgrade would be a waste of money until maybe 2.4.10
or so.

So the question is basically:  Is the upgrade worthwhile?  Is
2.2.x or 2.4.x compatible with Athlon CPU's or are there problems
at all still?  What about Athlon motherboards and chipset
hardware?  Can I expect the IDE chipset to work?  Applying IDE
patches is ok, but I just want to know that I'm going to get more
than 10M/s out of the drives, and not fry them.  Those are my
main concerns, but I'd just like to know what the average
developer thinks of the idea of forking out cash for a highend
system right now and wether or not it is worth it yet.

If not, I'd rather wait until things are integrated with the
kernel proper and working.  If it *IS* ready now, what sort of
Athlon hardware is recommended for a developmental machine?

TIA



--
  Mike A. Harris  -  Linux advocate  -  Open source advocate
  Computer Consultant - Capslock Consulting
 Copyright 2000 all rights reserved
--

Need general help or technical support with Red Hat Linux 6.2?  Join the user 
support mailing list by sending a message to "[EMAIL PROTECTED]"
with the word "subscribe" on the subject line.

-
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: [OOPS] unloading ns558 driver in Linux 2.4.0-test9

2000-10-07 Thread Brian Gerst

"Forever shall I be." wrote:
 
 I got this OOPS while unloading the ns558 module.. I don't think it did
 this in 2.4.0-test8, but I don't recall ever unloading it in test8..
 
 I've attached the ksymoops output..
 
 --
 Zinx Verituse(See headers for gpg/pgp key info)
 
   
 
oops.outName: oops.out
Type: Plain Text (text/plain)

What kind of game port do you have?

-- 

Brian Gerst
-
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: Tux 2 patents

2000-10-07 Thread Jeff V. Merkey

On Fri, Oct 06, 2000 at 09:11:44PM -0700, Marty Fouts wrote:
 I don't know a lawyer I would trust who would give free legal advice on a
 mailing list without the usual disclaimers.

You should go back and read the start of this thread.  I've hired an 
IP Patent attorney to handle the Tux 2 Patent issue, and will be posting 
his analysis back to this community.  I have forwarded Daniel's 
designs and the specific patents and we are performing an infringement 
analysis. 

I think it's great that the USPTO has a website, but it's no subsitute
for "real" legal help to folks on this list.

Jeff


 
 And I don't care what you've done elsewhere, you have, here, been misleading
 about patent law. I stand by my recommendation that people who are
 interested should read the Nolo Press book and then, if they have specific
 issues, consult an IP lawyer on those particular issues.
 
 In addition to the Nolo press, by the way, the US Patent Office now has a
 web site with good general information for those people who are interested
 in US patent issues.  (http://www.uspto.gov/) I suppose there is a similar
 web site for people interested in EU patent specifics as well.  One of the
 serveral ways in which you were mistaken in your assertions is that you've
 neglected to clarify where US Patent Law differs from Patent Law in other
 jurisdictions.  You may be in Utah, but not everyone on this mailing list
 is.
 
 
 
 
  -Original Message-
  From: Jeff V. Merkey [mailto:[EMAIL PROTECTED]]
  Sent: Friday, October 06, 2000 3:40 PM
  To: Marty Fouts
  Cc: 'jesse'; [EMAIL PROTECTED]
  Subject: Re: Tux 2 patents
  
  
  
  
  Marty Fouts wrote:
   
   I don't do pissing matches, Jeff, and won't compare the 
  quality of the IP
   experts I have access to to the quality of those you have access to.
   
   I will say that you are wrong about disclosure because you 
  have overly
   simplified, and again recommend that people who care should 
  discuss their
   specific cases with real lawyers, which neither you no or I are.
  
  Excuse me -- I was one of the attorneys on the Novell/TRG lawsuit --
  check my motions
  and filings.  In fact, check the 4th District Court in general for my
  filings in other cases.  You can check the Texas courts for 1980's as
  well.  Just because I have been a software 
  engineer for the past 20 years does not mean I did something else in a
  previous life. 
  
  Since all my friends are lawyers and TRG runs a law firm out of here
  should say something.
-
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: No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 10:03:34AM +0200, Jens Axboe wrote:
 On Sat, Oct 07 2000, Dax Kelson wrote:
   BTW, how did your testing of the speed=4 problem with ide-scsi turn
   out.  We are still seeing the speed=2 problem on 2.4.0-pre9.  I cannot
   get the drive to burn clean unless the speed setting is cranked down to
   speed=2.
   
   Jeff 
  
  I just burned Red Hat 7.0 disk1 iso image at on a SCSI 4x burner without
  any problems.  I have an IDE Plextor 12x burner at work, Monday I'll try a
  burn under 2.4.0-test9.
 
 [snip]
 
 I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
 problems (this is on two different atapi writers). This could be an
 ide-scsi bug on some models. The folks who are seeing corruption, could
 they try and narrow it down? Is it random data getting written, or
 data from other locations?

I think it's related to the drive type in some way.  What we are seeing
is the CD burner hang on the first write to track 0.  Once it starts
burning, it seems to work fine, and we have even got some clean burns
at speed=4, however, when it's set this way, we occasionally see cdrecord
hang when it attempts to write the first track of a CD.  It ruins the 
CD in the burner, BTW when this happens.  I also see an I/O error message
from the ide-scsi driver about a timeout and data error 
(but I did not write it down -- sorry).  

I will burn some more CD's today, and will try to get more info.  Config 
is:

in lilo.conf:

append "hdd=ide-scsi"

and the CDROM device is mapped to:

/dev/scd0

and I load the ide-scsi module:

insmod ide-scsi

and:

cdrecord -scanbus.

Then we use the system to burn CD's all day.

Jeff


 
 -- 
 * Jens Axboe [EMAIL PROTECTED]
 * SuSE Labs
-
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: Quantum lct08 Ultra66 on GigaByte GA-BX2000+

2000-10-07 Thread Andre Hedrick


Read the source code and put the complete drive name in the quirk list for
that chipset.

On Sat, 7 Oct 2000, Mikhail Vladimirov wrote:

 Hi, people!
 Here I am :-)
 I just want to remember: It's already test9 but... :-(
 All what I certainly have is kernel panic at FS mounting point.
 Nothing was changed in other words
 Think everybody may have my experience, trying to install 2.4.0 to Quantum lct08 
UDMA66 drive
 attached as a slave to primary Promise Ultra66 controller.
 
 So, I am still forced to load my poor linux from diskette with kernel 2.2.5-15
 And nobody can help me!
 I'm crying :(
 God knows even Windows95 works fine with both of my HDD
 2.4.0 still does not!
 
 Regards,
 Mike
 
 P.S.
 Everything you need (details I mean, and if you Really need it of course) you can 
find
 in my previous messages which (I hope) have been stored in archive
 
 

Andre Hedrick
The Linux ATA/IDE guy

-
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: Tux 2 patents

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 06:45:38PM +0200, Daniel Phillips wrote:
 Marty Fouts wrote:
  
 Well, I like your version more than Jeff's because if you're right then
 I still have time to make a whitehat patent application for my better
 atomic commit method.  What's a whitehat patent?  It's one that helps
 fence in companies who want to use patented algorithms in closed source
 software.  Whitehat patents will help convince the blackhats that it's
 in their interest to disallow algorithm patents and put things back the
 way they were before.


Daniel,

Do you want me to continue the patent attorney's analysis or not?  If I'm
spending money to help you here, I would appreciate you not bouncing off the
walls.  I am also having this guy put togther a provisional patent application
for your stuff, if you want to obtain a patent.  You are not going to 
change the USPTO, that's the system here, and like it or not, we all
just have to live with it.  The USPTO's authority is consitutional in 
it's basis regarding the rights of inventors (section 113), and unless
Congress and the Senate ammend the constitution, the USPTO and the rights
of inventors in the US will be protected. 

The list lurker non-lawyer technocrats waiving web pages around don't 
change the system, or provide the resources to help you.
 
Jeff

 
 --
 Daniel
 -
 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/



2.4.0-test9 boot failure (Linux/Alpha, EIDE CMD646)

2000-10-07 Thread Dave Gilbert

Hi,
  2.4.0-test9 failed to boot on my LX164 Alpha system; 2.4.0-test8 works
fine.

  It looses interrupts in the IDE probes; it is a CMD646 controller and
what appears to be happening is that it is getting the wrong IRQs; under
2.4.0-test8 we see:

Oct  7 18:19:57 tardis kernel: CMD646: IDE controller on PCI bus 00 dev 58
Oct  7 18:19:57 tardis kernel: CMD646: chipset revision 1
Oct  7 18:19:57 tardis kernel: CMD646: not 100% native mode: will probe
irqs later
Oct  7 18:19:57 tardis kernel: CMD646: chipset revision 0x01, MultiWord
DMA Limited, IRQ workaround enabled
Oct  7 18:19:57 tardis kernel: ide0: BM-DMA at 0x8000-0x8007, BIOS
settings: hda:pio, hdb:DMA
Oct  7 18:19:57 tardis kernel: ide1: BM-DMA at 0x8008-0x800f, BIOS
settings: hdc:DMA, hdd:DMA
Oct  7 18:19:57 tardis kernel: hdb: , ATAPI CDROM drive
Oct  7 18:19:57 tardis kernel: ide: Assuming 33MHz system bus speed for
PIO modes; override with idebus=xx
Oct  7 18:19:57 tardis kernel: hdc: IBM-DPTA-373420, ATA DISK drive
Oct  7 18:19:57 tardis kernel: hdd: MATSHITADVD-ROM SR-8582, ATAPI CDROM
drive
Oct  7 18:19:57 tardis kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct  7 18:19:57 tardis kernel: ide1 at 0x170-0x177,0x376 on irq 15

On 2.4.0-test9 I can't easily get a log saved; however it looks like its
saying that both ide0 and ide1 are on irq 21 and then complains that it is
loosing them.

It is not unusual for PCI devices on Alpha to have IRQs  16 (indeed my
ether is on 17).

.config on request for anyone interested.

Dave

-- 
  Have a happy GNU millennium! --   
/ Dr. David Alan Gilbert  | Running GNU/Linux on   |  Happy  \ 
\   gro.gilbert @ treblig.org |  Alpha, x86, ARM and SPARC |  In Hex /
 |___ http://www.treblig.org  |/

-
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: 2.4.0-test9 boot failure (Linux/Alpha, EIDE CMD646)

2000-10-07 Thread Richard Henderson

On Sat, Oct 07, 2000 at 06:38:00PM +0100, Dave Gilbert wrote:
   It looses interrupts in the IDE probes; it is a CMD646 controller and
 what appears to be happening is that it is getting the wrong IRQs...

This was a generic ide problem in test9.


r~
-
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: Adding vendor drivers...

2000-10-07 Thread Pavel Machek

Hi!

 So, when a vendor has to add a new driver, especially with the new-style
 makefiles, you have a one-line patch to a makefile, a one-line patch to
 a Config.in, and a patch which adds the driver to the tree.
 
 It would make adding new drivers to vendor kernel packages a whole lot
 easier and more modular if you could add a driver simply by doing:
 
   cp driver.c driver.config.in driver.mak linux/extras
 
 ...and then the makefile and config system automatically slurps this
 data.  extras/Makefile could look something like:
 
   ...new style init..
   include *.mak
   ...new style obj-x handling...
   include Rules.make
 
 Something similar would have to be worked out for Config.in.
 
 Of course, for anything complex, patching is still an option.
 
 Comments?  Suggested implementation?  :)

Well, having .in and .mak files with single lines in them seems ugly
to me. What about make dep scanning for

/* Makefile:obj-$(CONFIG_MY_DRIVER) += mydriver.o */
/* Config.in:   bool CONFIG_MY_DRIVER */

in .c files?
Pavel
-- 
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
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: Newer motherboards / CPU's / hardware with Linux

2000-10-07 Thread Mark Hahn

 kernel proper and working.  If it *IS* ready now, what sort of
 Athlon hardware is recommended for a developmental machine?

I HIGHLY recommend duron/thunderbird, KT133, PC133, UDMA machines;
they work very well with modern (2.4) kernels.  K6-2 machines are 
not anywhere close to the same performance, and even low-end Durons
embarass FSB100-overclocked Celeron machines quite neatly.
a Duron/600 makes a great development workstation; 
I haven't seen a reason to pay extra for a thunderbird.

-
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: No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Andre Hedrick

On Sat, 7 Oct 2000, Jeff V. Merkey wrote:

 append "hdd=ide-scsi"

append "hdd=scsi" is better.

Andre Hedrick
The Linux ATA/IDE guy

-
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: Tux 2 patents

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 08:13:45PM +0200, Daniel Phillips wrote:
 On Sat, 07 Oct 2000, Jeff V. Merkey wrote:
  On Sat, Oct 07, 2000 at 06:45:38PM +0200, Daniel Phillips wrote:
 
 You are right of course.  I'm open to suggestions on exactly how best to
 behave.  The object is to make the most forward progress.

Thank you.  Lawyers can be really straight and narrow, particularly 
patent lawyers.  To date, you have not disclosed the specific methods
that will comprise the claims of you invention, just a high level 
description, which is ok.  Until the provisional application has 
been issued a docket number, you need to not describe the actual 
methods publically other than in high level designs.  Malinkrodt has
your email address, and I expect next week, they will begin their 
dialouge with you.  It only takes a few days to slap a provisional
application together.  

 But how did we get from a state where algorithms were not patentable to one
 where they are?  Surely at least that can be undone.

The spirit of the USPTO is to protect inventors rights and balance 
this with those things which are "essential facilities" of the 
affected area.  The USPTO is not the utlimate authority on what is
or is not patentable, the Judges sitting in the Federal Courts of
the US are.  There are many patents ruled to be invalidate, and 
vis-a-vis the other way in infringement claims.  The controlling
law here is what's described in the Consitution, and the rights
of an inventor to enjoy the profits of his invention for a 
limited period of time.  People always assume it's these big,
evil companies behind all the patent issues in the US.  The fact
is that the system in the US recognizes individual inventors.  These
inventors have to assign their patents to a corporation in order 
for a corporation to own it.  These laws in the US were originally 
intended to protect individual inventors, BTW.

 obviously with a view to learning the truth.  I'm also not sure whether you're
 also objecting to the idea of trying to fence in closed-source software sellers,
 are you?  Or is it just that it seems like an inflamatory idea?

It's not so black and white.  In the US, we have a concept of 
"courts of equity".  This means folks are basically free to step 
on each others rights, including the right to develop new ways of 
writing software.  At times, the system has no other recourse than
to resort to one side or the other litigating before a sitting 
Judge to expand the meaning and application of these laws, such as
the laws regulating patents.  Much of the USPTO's current policies
are based on this case law from the US District Courts.  I agree 
that the legal system in the US is "tecnology ignorant" but it 
is getting better.  

:-)

Jeff


 
 --
 Daniel
-
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: No SCSI burning problem (was: Bug in ide-pci.c)

2000-10-07 Thread Jeff V. Merkey

On Sat, Oct 07, 2000 at 11:16:30AM -0700, Andre Hedrick wrote:
 On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
 
  append "hdd=ide-scsi"

Am I doing this wrong?  It seems to work.  

:-)

Jeff

 
 append "hdd=scsi" is better.
 
 Andre Hedrick
 The Linux ATA/IDE guy
 
-
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: one-line umount patch needed for am-utils

2000-10-07 Thread Pavel Machek

Hi!

  It's kind of silly and an abuse of the VFS, I agree. Unfortunately, it's
  been around for a while, it works on other systems and real people are
  using it. And they get a nasty surprise when they try it on Linux: the
  amd-provided NFS filesystems cannot be unmounted, because the VFS umount
  code follows the root symlink.
 
 So fix amd and teach it not to do that.

This is kernel bug. It allows root to (easily) get into situation when
he can't unmount filesystem. 
While we allow root to shoot into his foot (-:), this is much too
easy.

Pavel
-- 
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
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: [OOPS] unloading ns558 driver in Linux 2.4.0-test9

2000-10-07 Thread Forever shall I be.

On Sat, Oct 07, 2000 at 12:42:16PM -0400, Brian Gerst wrote:
 "Forever shall I be." wrote:
  
  I got this OOPS while unloading the ns558 module.. I don't think it did
  this in 2.4.0-test8, but I don't recall ever unloading it in test8..
  
  I've attached the ksymoops output..
 What kind of game port do you have?
 
 -- 
   Brian Gerst

Whatever kind of game port there is on the Diamond Sonic Impact s70..
It works fine with the driver -- It just oops'd when I unloaded it :/

It should be noted here that i have to enable it with the following:
setpci -v -d 125d:1968 0x40.W=0x107f

-- 
Zinx Verituse(See headers for gpg/pgp key info)
-
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: Bug in ide-pci.c

2000-10-07 Thread David Woodhouse

On Fri, 6 Oct 2000, Andre Hedrick wrote:

 void go_take_a_dump (float load)
 {
   if (pull_down_pants()  purge_bowles()  wipe_anus()  pull_up_pants())
  flush(load);
   else
  wear(load);
 }

But here you make another classic mistake. Consider the case where
purge_bowels() fails (-EWOULDBLOCK?). 

In that case, you don't actually execute the subsequent two procedure
calls, which I'm sure we all agree is a suboptimal state of affairs.

-- 
dwmw2


-
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: RedHat 7.0 anaconda installer doesn't support devfs

2000-10-07 Thread Tom Rini

On Fri, Oct 06, 2000 at 09:19:45PM -0400, Joseph Fannin wrote:
 Jeff Merkey wrote:
 
 On Sat, Oct 07, 2000 at 12:31:05AM -0400, jeff millar wrote: 
  Redhat support got back to me today and said 7.0 doesnt support
  upgrades to systems running devfs. But I thought sure than Linus
  blessed it! :-) 
  Does anyone have a fix? 
 
 Good question. I noticed this as well. 
 
 
  I couldn't run devfs on a fresh install of RedHat 7 either; the
 use of labels in fstab to identify partitions seems to preclude this.

Eh?  That doesn't make sense.  I've used devfs  LABELs in my fstab before
fine.  That really shouldn't be the problem.  Your root gets mounted, yes?
Then /proc and /proc is needed (I don't know the file) for the LABEL/UUID-
device stuff.

  Well, I *could* have hacked all the necessary scripts if I knew what
 they were, I guess.

The rawhide scripts used to start devfs all by themselves.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
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: Adding vendor drivers...

2000-10-07 Thread Sven Koch

On Fri, 6 Oct 2000, Pavel Machek wrote:

 Well, having .in and .mak files with single lines in them seems ugly
 to me. What about make dep scanning for
 
 /* Makefile:  obj-$(CONFIG_MY_DRIVER) += mydriver.o */
 /* Config.in: bool CONFIG_MY_DRIVER */
 
 in .c files?

Isn't "make dep" normaly only done after configuring the kernel?
(and scanning every .c-file seems really slow to me)

c'ya
sven

-- 

The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)

-
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/



[BENCH] Linux kernel benchmarked..

2000-10-07 Thread Luuk van der Duim

Hi Kernelfolks,

 I know kernelcompiling is not the only useful thing we do within Linux but
it is one of the longer lasting tasks.
Therefore I timed Linux kernel 2.2.16-pre9, 2.4.0-test6, 2.4.0-test9-pre7
and 2.4.0-test9 compiling bzImage.

 System: Linux mandrake 7.1 UP Pentium2 266@300

 2.4.0-t9  867,72 s.   512,37 s.  503,66 s. 500,97 s.
2.4.0-t9-p7891,64 s.   513,27 s.  506,00 s.  501,04 s.
2.4.0-t6   1.002,50 s.   511,44 s. 502,27  s. 500,04 s.
2.2.16-pre9 1.302,98 s.   506,50 s.  498,66 s. 496,67 s.

16 MB 32 MB 64 MB 128 MB

 My Gnumeric does not make graphs.. Therefore I've added an excell
sheet..(sorry)
Most useful to you might be the textfile testresults in which the pagefaults
are also mentioned.

 Greetings,

 Luuk van der Duim



begin 666 Kernelbench.pdf
M)5!$1BTQ+C(*)?LCZ(*-" P(]B:@H\/"],96YG=@@-2 P(%(O1FEL=5R
M("];%T941E8V]D93X^"G-TF5A;0IXG)U5P6H,0R]^RM\3""K6I(MV]= 
M+X4TLP?I"E-Z$("@?Q^Y%G/K%=3AC8LBXW;^7W+/E-`/2A??KZ'2O[M7C
MC"W+P]'?3N[+#VG ],NA/\R_^DQJOCI'7_^_'Q#:^G9_=U\G?*'+1O^OZ
M3;_/+E,`2EYRXK8':J(_+'W]MBY?;9B\2@=O2,5_OVT;$T-*BKT[+FI
M^9E^7J40H:?`D*(,XV 1L-,0'%=.:%Z*/*DKSZ6'2G6HSNCC3=%ON[NTTI
MR9SI1AMI0496%1RO2MR,ABKH:U( ,+LQ[,!6M%1A:%8E@+\A_]"_.AKTVL
MD/7_L4!I?92X;6,`"6L;42TC0(A[+:1@+*VL2A]T\88[?AUY-/RF4]CR+0O
M'U6N3B'J;GE//B+$.-M,82.?BIVOCGQ:/N;3Z:/LRB^20]ZJ0@R7R*,$$J7
MCX!THN%-T.-/6O^]:6C0-DVX".##=$9\S87)!_"@EJS-J)@1PFYW2S1*H
M^L-;]O#X25W4US/+8DG4YTDRB9 .;Q4ZRH5ZVI!QG38LL8,V90R3FPU#)
MY,68#F6S8LQ'0:6R8LQ'XLFQ=C.@PLDQ=[CO]I7(YGU02),_SN^7\6KES
M'QFM6+%E;F1S=')E86T*96YD;V)J"C4@,"!O8FH*-#W"F5N9]B:@HS(# @
M;V)J"CP\"B]47!E("]086=E"B]-961I84)O"!;," P(#8Q,B W.3)="B]0
M87)E;G0@,B P(%(*+U)EV]UF-ER \/" O4')O8U-E="!;+U!$1B O55X
M=%T*+T9O;G0@/#P*+U(W(#@,"!2"B]2-B V(# @4@H^/@H^/@HO0V]N=5N
M=',@-" P(%(*/CX*96YD;V)J"C@,"!O8FH*/#PO5'EP92];VYT+TYA;64O
M4CO4W5B='EP92]47!E,2]"87-E1F]N="]4:6UERU";VQD/CX*96YD;V)J
M"C8@,"!O8FH*/#PO5'EP92];VYT+TYA;64O4C8O4W5B='EP92]47!E,2]"
M87-E1F]N="]4:6UERU2;VUA;CX^"F5N9]B:@HR(# @;V)J"CP\("]47!E
M("]086=ER O2VEDR!;"C,@,"!2"ET@+T-O=6YT(#$*/CX*96YD;V)J"C$@
M,"!O8FH*/#P@+U1Y4@+T-A=%L;V@+U!A9V5S(#(@,"!2"CX^"F5N9]B
M:@HX(# @;V)J"CP\("]#F5A=EO;D1A=4@*$0Z,C P,#$P,#Q.#$X-#I
M"B]0F]D=6-EB H1TY5($=H;W-TV-R:7!T(#4N-3 I"CX^"F5N9]B:@IX
MF5F"C @.0HP,# P,# P,# P(#8U-3,U(8@"C P,# P,# Y-#,@,# P,# @
M;B *,# P,# P,#@X-" P,# P,"!N( HP,# P,# P-3@Q(# P,# P(X@"C P
M,# P,# P,34@,# P,# @;B *,# P,# P,#4V,B P,# P,"!N( HP,# P,# P
M.#$Q(# P,# P(X@"C P,# P,# W,SD@,# P,# @;B *,# P,# P,#DY,B P
M,# P,"!N( ITF%I;5R"CP\("]3:7IE(#D@+U)O;W0@,2 P(%(@+TEN9F\@
." P(%(*/CX*W1AG1XF5F"C$P-SD*)25%3T8*
`
end

begin 666 Kernelbench.xls
MT,\1X*QN$`/@`#`/[_"0!
M+0``$ ``_O___P#^`"P```#_
M
M
M
M
M
M
M
M
M
M__\)"! ```8%`!P.S =!!@```.$``@"P!,$`
M`@```.(```!`' `$0``3'5U:R!V86X@95R($1U:6T@(" @(" @(" @(" @
M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @
M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @($(``@"P!$!`@`!
M`#T!! `"``$`G `"``X`0`"$@`"$P`"KP$"O $"
M/0`2``"7.X(C. ```0!8`D ``@```(T``@```"(``@X``@`!
M`+!`@```-H``@```#$`(@"T``"0`0``_ D!2 !E`P`=@!E`'0`
M:0!C`$`,0`L`-P``) !``#\#@%5`%(`5P`@`$,`: !A`X`8P!E
M`'(`0`@`$P`,0`B`+0``) !``#\"0%(`4`; !V`4`= !I`,`
M80`Q`"(`M ``D $``/P)`4@`90!L`'8`90!T`D`8P!A`#$`@#(
M_W^0`0``_ 4!00!R`D`80!L`#$`@#(_W^0`0``_ 4!
M00!R`D`80!L`#$`@#P``$`_W^\`@``_ 4!00!R`D`80!L`#$`@#(
M``$`_W^\`@``_ 4!00!R`D`80!L`!X$( `%`!L``")F;")(",L(R,P
M7RT[(F9L(EP@(RPC(S!+1X$)0``" ``")F;")(",L(R,P7RT[6U)E9%TB
M9FPB7" C+",C,%PM'@0F```(0``(F9L(EP@(RPC(S N,#!?+3LB9FPB7" C
M+",C,"XP,%PM'@0K``@`)@``(F9L(EP@(RPC(S N,#!?+3M;4F5D72)F;")
M(",L(R,P+C P7"T!#X`*@`Y``!?+2)F;")("H@(RPC(S!?+3M?+2)F;")
M("H@(RPC(S!+3M?+2)F;")("H@(BTB7RT[7RU 7RT!"P`*0`G``!?+2H@
M(RPC(S!?+3M?+2H@(RPC(S!+3M?+2H@(BTB7RT[7RU 7RT!$8`+ !!``!?
M+2)F;")("H@(RPC(S N,#!?+3M?+2)F;")("H@(RPC(S N,#!+3M?+2)F
M;")("H@(BTB/S]?+3M?+4!?+1X$- `K`"\``%\M*B C+",C,"XP,%\M.U\M
M*B C+",C,"XP,%PM.U\M*B B+2(_/U\M.U\M0%\M'@0:`*0`%0``7"0C+",C
M,%\I.UPH7"0C+",C,%PI'@0?`*4`@``7"0C+",C,%\I.UM2961=7"A)",L
M(R,P7"D!" `I@`;``!)",L(R,P+C P7RD[7"A)",L(R,P+C P7"D!"4`
MIP`@``!)",L(R,P+C P7RD[6U)E9%U*%PD(RPC(S N,#!*1X$- "H`"\`
M`%\H7"0J(",L(R,P7RD[7RA)"H@7"@C+",C,%PI.U\H7"0J("(M(E\I.U\H
M0%\I'@0N`*D`*0``7R@J(",L(R,P7RD[7R@J(%PH(RPC(S!*3M?*"H@(BTB
M7RD[7RA 

Re: [PATCH] VM fix for 2.4.0-test9 OOM handler

2000-10-07 Thread Rik van Riel

On Sat, 7 Oct 2000, James Lewis Nance wrote:
 On Fri, Oct 06, 2000 at 03:59:48PM -0300, Rik van Riel wrote:
  the following patch contains 2 fixes and one addition
  to the VM layer:
 
 This kernel is working well for me.  I have been off the net
 for about a week and a half, so I did not get to try any of the
 latter test9-preX kernels, but all the early ones would lock up
 on me if I tried to build mozilla with mem=48M.  This one works
 just fine.

Yes, we seem to have things under control now ...  ;)

My 2 main TODO items at the moment are getting the OOM
killer to kick in at exactly the right moment and trying
to make swap-over-nbd work...

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
   -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/   http://www.surriel.com/

-
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/



  1   2   >