webcam II & kernel compiling
I have 2 questions. 1) Who is working on the webcam II cpia driver. Under NT I can get 15 to 25 fps, while Linux seems to be limited to 15 max. Is this a hard coded value in the lernel somewhere and is there plans for changing this? (I know that this is an experimental driver, but rebooting to NT is just not what I want to do. 8-) 2) I recently read that when upgrading to a new kernel you should not compile the new kernel in /usr/src/linux . If I upgrade to a new kernel what is the 'proper method' and what other program will I need to recompile to take full advantage of the new kernel? (the more detail the better and please email just me and not the kernel list ) -- Joe Acosta home: [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/
which is it ncr53c810 or ncr53c810a?
Hi, I have been troubleshoting some scsi errors that I have been recieving, and noticed something weird. In my proc/pci my controller card is identified as (I know obsolete). --- Bus 0, device 18, function 0: SCSI storage controller: NCR 53c810 (rev 18). Medium devsel. IRQ 9. Master Capable. Latency=64. Min Gnt=8.Max Lat=64. I/O at 0x6800 [0x6801]. Non-prefetchable 32 bit memory at 0xe400 [0xe400]. --- I then looked in the /proc/scsi/ncr53c8xx/0 file and it said --- General information: Chip NCR53C810a, device id 0x1, revision id 0x12 IO port address 0x6800, IRQ number 9 Using memory mapped IO at virtual address 0xc8902000 Synchronous period factor 25, max commands per lun 32 - So which is it? An 810 or 810A? Also sometimes I get the following error when writing cdr's cdrecord: Input/output error. read track info: scsi sendcmd: retryable error CDB: 52 01 00 00 00 FF 00 00 1C 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 24 00 00 C0 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0 Sense flags: Blk 0 (not valid) error refers to command part, bit ptr 0 (not valid) field ptr 0 The drive is an HP 9200i, any ideas? The drive is terminated and is the only drive on the scsi bus. The strangest thing is that I have set the scsi speed to Fast-5 Mb as fast 10 increases the frequency of this error, and when I do a modprobe -a ncr53c8xx it spits out it is fast-10 and then when I do a modprobe -a sr_mod it detects it is a Fast-5. Is anyone else using the HP 9200i scsi drive? I don't think that it is a scsi termination issue or cabling. -- Joe Acosta home: [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/
patch-2.2.19.gz
I just patched my 2.2.18 kernel. After I did a make dep I got the following message. Any ideas what does this mean? md5sum: WARNING: 11 of 12 computed checksums did NOT match Joe Acosta home: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
bug in float on Pentium
Not sure but I think I found a NEW bug.
I know that there have been some issues with pentiums and floating point
arrithmatic, but this takes the cake...
Linux Lserver.org 2.2.18 #43 SMP Fri Mar 9 14:19:41 EST 2001 i586
unknown
>kgcc --version
egcs-2.91.66
RH 6.2.x / 7.0
try this program
#include
int main() {
char tmpx[100];
char tmpy[100];
double x = 5483.99;
float y = 5483.99;
sprintf (tmpx, "%f",x );
sprintf (tmpy, "%f",y );
printf ("%s\n%s\n", tmpx, tmpy);
return 0;
}
I am getting the following as output
joeja@Lserver$ ./testf
5483.99
5483.990234
what is with the .990234?? it should be .99
any ideas on this??
--
Joe Acosta
home: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
out of swap
Last night I was browsing the web and I came across a page with LOTS of images. There were so many that it drove my swap space to ZERO. I still had 3 Meg of memory, but the system became virtually unusable and SLOW. (there were over 150 x 30k+ images on one page). Is this something that the OOM would fix or is this another issue altogether? The machine has 64Meg of swap space, 128 Meg of RAM, Dual 233MMX, Itis running 2.2.17 and Rh 6.2. Any ideas? thanks Joe __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.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/
out of swap
Last night I was browsing the web and I came across a page with LOTS of images. There were so many that it drove my swap space to ZERO. I still had 3 Meg of memory, but the system became virtually unusable and SLOW. (there were over 150 x 30k+ images on one page). Is this something that the OOM would fix or is this another issue altogether? The machine has 64Meg of swap space, 128 Meg of RAM, Dual 233MMX, Itis running 2.2.17 and Rh 6.2. Any ideas? thanks Joe __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.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/
Re: out of swap
What would I like it to do? Warn me maybe before my swap goes to zero. Kill the program that is doing this possibly. Allow me to set a per process memory / swap limit so that no one process can suck up my system resources. I'd rather not increase swap if possible, as it was only this one page that hosed my system, and other than that, my system doesn't swap that much if at all. > > Last night I was browsing the web and I came across a page with > > LOTS of images. There were so many that it drove my swap space > > to ZERO. I still had 3 Meg of memory, but the system became > > virtually unusable and SLOW. (there were over 150 x 30k+ images > > on one page). > > > > Is this something that the OOM would fix or is this another > > issue altogether? > > > > The machine has > > 64Meg of swap space, 128 Meg of RAM, Dual 233MMX, Itis running > > 2.2.17 and Rh 6.2. > > > > Any ideas? thanks Joe > > Add more swap. What would you like the system to do if it's out of both > memory and swap? It can either kill processes or become slow. > > DS -- Joe Acosta home: [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/
OOM and my .02 cents
Hi all, I read this week in kernelnotes about the OOM killer and thought I'd share a few thoughts that I had on the subject. I know I am maybe considered a 'nobody' here so my opinion may count very little, but this makes sense to me as a user so I though I'd throw in my .02 cents. If you like it use if not delete this email and forget about it. 1) If it does not already do this it should probably start with warnings like printk statements. (I'll hope it does). 2) There should probably be a way to configure OOM (if there is not already). I.E either a % or in bytes before we say we are out of memory. This could default to something like 10% of the remaining memory or 1% or whatever. This would probably have 2 values. Start warning messages at 10% start killing at 5% or something, or one value could be based on the other value. I'd prefer a percent basis, cause you wont know how much memory a system has till the sytem boots and if someone puts in kill at 32Meg and the system has 16 well, you do the math. This could possiblly even be configurable through the /proc interface or a compile time thing or both. With these two bits of info it would be fairly easy to write a user space program that would scan the sys logs for the OOM warnings and pop up a message in X saying that something needs to die. This kind of functionality could be added into X and then if X sees a warning in the sys logs about OOM then X can refuse to start another program. This is assuming the X group wanted to do so. Personally if they did not I'd do it in Gtk or Xaw or something myself. 3) This should probably be capable of being compiled as a module, so that if someone decided to add functionality to it for X it would not make the kernel (bzImage) grow exponentially. The reason I say this is that if you look at the trends in Linux then you'll realize that everything is moving towards X. Even IBM's via voice has a GUI. Do you really know where Linux will have morphed to in 10 years? It's always better to be flexable now then to find yourself screwed in the future. Even if this were a seperate patch it could possiblly in theory be done. Fact is when that code gets on someones system you don't know what there needs are or what they'll do with it. If you look at windows it pops up a message when you try to start a program and you don't have the memory for it, someone or some distribution could do this for Linux if they were so inclined. You know there are some people out there that are into that kind of thing. 4) Lastly, if this is truely an OOM killer it's hueristics, should probably just see which progam(s) are taking up the most memory, and which one(s) were started last. The last program that is taking up the most memory should then be killed. Why? Chances are that the last program that is started that is taking over the most memory is probably your problem. init is # 1 in my process table and the first 5 are kernel related dameons. X starts after that even when xdm/gdm are running. If X had a memory leak and was killed by the OOM most window mangers will catch this and save a users settings. If anyone looses data it is really there fault for not saving every 5 minutes anyway. Lastly the other option rather than killing the program is to restart the program. just my .02 cents. __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.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/
/proc & xml data
I remember hearing about various debates about the /proc structure. I was wondering if anyone had ever considered storing some of the data in xml format rather than its current format? Things like /proc/meminfo and cpuinfo may work good in this format as then it would be easy to write a generic xml parser that could then be used to parse any of the data. "MemTotal: %8lu kB\n" In the case of the meminfo it would be a matter of changing the lines in fs/proc/array.c function get_meminfo(char * buffer) from "MemTotal: %8lu kB\n" to something like "%8lu kB\n" Joe - 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/
Rik's t8sched patch breaks pcmcia
--jho1yZJdad60DJr+ Content-Type: multipart/mixed; boundary*="ansi-x3-4-1968''OgqxwSJOaUobr8KG" Content-Disposition: inline --OgqxwSJOaUobr8KG Content-Type: text/plain; charset*=ansi-x3-4-1968''us-ascii Content-Disposition: inline 1st of all, THANKS RIK!!! Both patches are a godsend. I won't run a kernel w/out them. Your mojo's the best. I've got a Toshiba Satellite 2715 PIII 500 laptop with 128 MB RAM, running linux-2.4.0-test8 with + 2.4.0-t8-vmpatch2 and 2.4.0-t8-sched + reiserfs-3.6.14 Removing the sched patch from the mix makes cardmgr work. With the sched patch in, I get the following: (Attatched is a recorded session with output from lspci, /proc/cpuinfo, and everything that cardmgr spewed to syslog) starting, version is 3.1.20 watching 1 sockets could not adjust resource: IO ports 0xc00-0xcff: Input/output error could not adjust resource: IO ports 0x800-0x8ff: Input/output error could not adjust resource: IO ports 0x100-0x4ff: Input/output error could not adjust resource: memory 0xc-0xf: Input/output error could not adjust resource: memory 0x6000-0x60ff: Input/output error could not adjust resource: memory 0xa000-0xa0ff: Input/output error could not adjust resource: IO ports 0xa00-0xaff: Input/output error could not adjust resource: irq 4: Input/output error could not adjust resource: irq 7: Input/output error could not adjust resource: irq 12: Input/output error initializing socket 0 socket 0: Anonymous Memory executing: 'modprobe memory_cs' + modprobe: Can't locate module memory_cs modprobe exited with status 255 module /lib/modules/2.4.0-test8-t8vmpatch2-reiserfs-t8sched/pcmcia/memory_cs.o not available get dev info on socket 0 failed: Resource temporarily unavailable -Shawn Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise. --OgqxwSJOaUobr8KG Content-Type: text/plain; charset*=ansi-x3-4-1968''us-ascii Content-Disposition: inline; filename*=ansi-x3-4-1968''session%2Etxt Content-Transfer-Encoding: quoted-printable Script started on Fri Sep 15 11:57:16 2000 bash-2.04#=20 bash-2.04#=20 bash-2.04#=20 bash-2.04# ps axf PID TTY STAT TIME COMMAND 1 ?S 0:00 init [S] =20 2 ?SW 0:00 [kapmd] 3 ?SW 0:00 [kswapd] 4 ?SW 0:00 [kreclaimd] 5 ?SW 0:00 [kflushd] 6 ?SW 0:00 [kupdate] 7 ?SW 0:00 [CardBus Watcher] 8 ?SW 0:00 [CardBus Watcher] 9 ?SW 0:00 [khubd] 174 tty1 S 0:00 init [S] =20 175 tty1 S 0:00 \_ /bin/sh 191 tty1 S 0:00 \_ script 192 tty1 S 0:00 \_ script 193 pts/0S 0:00 \_ bash -i 194 pts/0R 0:00 \_ ps axf bash-2.04# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 8 model name : Pentium III (Coppermine) stepping: 1 cpu MHz : 497.561962 cache size : 256 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 sep mtrr pge mca cmov pat pse36= mmx fxsr xmm bogomips: 992.87 bash-2.04# lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (r= ev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev= 03) 00:05.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:05.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:05.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:05.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03) 00:07.0 Communication controller: Lucent Microelectronics 56k WinModem (rev= 01) 00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus= Bridge with ZV Support (rev 20) 00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus= Bridge with ZV Support (rev 20) 00:0c.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev = 10) 01:00.0 VGA compatible controller: Trident Microsystems Cyber 9525 (rev 49) bash-2.04#=20 bash-2.04#=20 bash-2.04#=20 bash-2.04# /etc/rc.d/init.d/pcmcia start Starting PCMCIA services: cardmgr. starting, version is 3.1.20 watching 1 sockets could not adjust resource: IO ports 0xc00-0xcff: Input/output error could not adjust resource: IO ports 0x800-0x8ff: Input/output error could not adjust resource: IO ports 0x100-0x4ff: Input/output error could not adjust resource: memory 0xc-0xf: Input/output error could not adjust resource: memory 0x6000-0x60ff: Input/output error could not adjust resource: memory 0xa000-0xa0ff: Input/output error could n
New features in Linux 2.4 - Wonderful World of Linux 2.4
Hello, This document has already been picked up by some Linux news sites, but it really belongs here. This is my list of new features since Linux 2.2, gathered by reading this list, playing with patches, and getting input from people. Parts of it are non-technical, but there is some good info here. I hope that someone out there finds this list useful. Joe -- Wonderful World of Linux 2.4 Joe Pranevich In the beginning, there was Linus and his 386. For reasons far too complicated to be discussed here, he decided not to use the commonly available operating system of the time and instead decided to write his own. Several years and many thousands of lines of code later, Linux 2.2was released. Linux 2.2 was a milestone in and of itself and I wrote an article about it, which I am quite happy with. Unfortunately for me however (and fortunately for the rest of the world), Linus and company continued to hack away at the Linux OS and the 2.4 release of the Linux kernel is nearing completion. This document describes some of the new features in Linux 2.4. Linux 2.4.0 was released without much fanfare on January 4^th, 2001. Although it has often been criticized for tardiness, the Linux kernel adheres to the Open Source philosophy of releasing code when it is ready. (Development snapshots have been made available weekly for interested parties.) As the kernel is generally only a small piece of a much larger Linux Operating System, the major distribution vendors will likely not be packaging it standard for several months yes. In this document, I have attempted to bring attention to areas where Linux 2.4 is not compatible with Linux 2.2. As this is a major release, the developers have taken this time to refine existing APIs (application programming interfaces) and other structures to make the system more cohesive. This process will almost definitely break any program that relies on an intimate knowledge of the kernel (such as the PPP daemon) but many other programs may be affected. One special item of note is that devfs, the Device Filesystem, will change the names of all device nodes on the system. (A compatibility layer for the old names has been provided.) It will be up to the individual distributions to determine whether or not to implement devfs and to what extent to patch the existing packages. If you would like to experiment with the Linux 2.4 kernel before it is released by a major distribution, please be sure to read the CHANGES document with the kernel and manually upgrade any necessary packages. Joe - [EMAIL PROTECTED] (Home) [EMAIL PROTECTED] (Work) < This work has absolutely nothing to do with Lycos, my employer. The views here are all mine and this article does not constitute an endorsement from Lycos or anything of the sort. Reproduction or translation of this article is fine, with permission. Email me. It's fun.> -- The Many Flavors of Linux In terms of sheer volume of code, the Linux kernel is predominantly made up of drivers. In fact, the size of the Linux core has not increased much over the last several revisions. Some of these drivers are architecture independent, such as the IDE driver. That is, these drivers have been written to work on multiple platforms. Other drivers are dependent on a particular architecture. For example, the ADB (Apple Desktop Bus) mouse driver isn't really applicable on the i386 port and so isn't supported. Linux kernel developers strive to make drivers as general as possible, so as to allow a driver to be reused with relatively little effort on a different platform if a device becomes available. It is convenient to think of the Linux kernel as a single entity, but some features may vary from platform to platform. In order to narrow the scope a bit, this document will mostly stick to Intel hardware as that is the hardware that I use most often at home. While I won't go into the specifics of each individual port, it should be mentioned that Linux 2.4 adds support for three new architectures: ia64 (Itanium, the successor to i386), S/390 (an IBM mainframe), and SuperH (Windows CE hardware). Linux 2.4 also includes support for the newer 64-bit MIPS processors. Of course, some platforms will be more mature than others. In terms of Intel-like hardware, Linux 2.4 is very similar in support to Linux 2.2. All Intel chips since the 386 are still supported, up to the Pentium III. Unlike Linux 2.2 however, Linux 2.4 includes direct support for the newest Pentium IV processors. (Older processors will probably never be supported.) MMX and MMX2 are also supported. Optimizations have been added to speed up Linux on all processors, but especially on the newer processors, such as the Pentium III. Compatible chips, such as those produced
Re: Final Warning [ was: ECN is on! ]
What is ECN? Is it the reason SNORT has started this lately: Active System Attack Alerts =-=-=-=-=-=-=-=-=-=-=-=-=-= May 22 10:11:18 pooh snort: spp_portscan: PORTSCAN DETECTED from 199.183.24.194 (STEALTH) May 22 10:11:22 pooh snort: spp_portscan: portscan status from 199.183.24.194: 1 connections across 1 hosts: TCP(1), UDP(0) STEALTH See ya, Joe Barr On Tue, 22 May 2001 10:57:34 -0400 David Relson <[EMAIL PROTECTED]> wrote: > At 10:18 AM 5/22/01, Steve Modica wrote: > > > >Perhaps it's none of my business, but it doesn't seem very sporting to > >just turn something on that breaks stuff and say "you had fair > >warning". Why not shut it back off, issue a statement saying it works > >now and will be re-enabled on June 10th or something, and everyone must > >do thus and so or they will break on that day? > > > >Vague things like "it'll be turned on real soon now" or ASAP really mean > >"never" since admins always have things with real deadlines at the top > >of their list. > > > I'd suggest something like: > > Final Warning. ECN is being turned on NOW. If your firewall doesn't > support ECN, this will be the last message that gets through to you from us. > > Such a message will have the interesting characteristic of being the last > message received. This will make it obvious why no further messages are > arriving. > > David > > > David Relson Osage Software Systems, Inc. > [EMAIL PROTECTED] Ann Arbor, MI 48103 > www.osagesoftware.com tel: 734.821.8800 > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- #--# | Joe Barr [EMAIL PROTECTED] | | Longears and Linux... nowhere but Texas! | #--# - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
kernel
Sorry about the question to do with visuall gcc. Alot of people seemed to get a intolerable response to my question. The reason I posted it here was a) I am lazy, b) On all the sites to do with Kdevelop the download links are down, and c) I wanted to use the program to compile such files as schedule.c and other scheduling algorithms I create. What do most of you use to comile the kernel, just good ole' command line gcc. - 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/
removable EIDE disks
I am trying to use removable EIDE hard disks on a Red Hat Linux 6.1 machine, for backup / walknet purposes. Issuing a BLKRRPART ioctl call immediately after changing the disk works, but only if the new disk is no larger than the disk present at boot time (smaller and equal capacity disks work OK). How do I get Linux to recognise that the media in /dev/hdc has changed? Bill Nottingham suggested that I ask you, as he is unsure if this is a bug or if there is a technique that I am missing. Thanks Richard Stanton [EMAIL PROTECTED]
filesystems
Does a typical Linux system or Mandrake boot using the ext2 filesystem? Do all filesystems have or use commands such as stat, read, write and chmod. I am trying to figure out without looking through the code how a VFS filesystem works. I am assuming that it does not use the major minor system, for faster access to data? On my system I have: ext2 msdos nodev proc Yes I did a man filesystems, man virtual filesystems, and manVFS. What does the nodev stand for? I have seen other systems containing filesystems such as: ext2 minix msdos vfat nodev proc nodev nfs iso9660 ufs nodev autofs nodev devpts Basically, do you mount a VFS filesystem, does it keep pages in RAM longer than other filesystems. How would a VFS filesystem handle system calls such as "stat" or "open"? I am just looking for something that can easily help me visualize the VFS process. - 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: Trident sound does not work anymore!
Try setting "PNP aware OS" (or something like that) to "NO" in your BIOS. Rene Blokland wrote: > > Hi there, as the subject says the trident sound does not work since > 2.4.0-test9. this messages does dmesg: > Trident 4DWave/SiS 7018/ALi 5451 PCI Audio, version 0.14.6, 12:36:52 Nov 20 2000 > trident: Trident 4DWave DX found at IO 0xd800, IRQ 0 > trident: unable to allocate irq 0 > any ideas? > > - > 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: Trident sound does not work anymore!
At least, that worked for me. I had this same problem on 2.2.17 with my es1371 when I bought a new ASUS P3V4X motherboard. If someone has a better solution I'd love to hear about it! Joe Rouvier wrote: > > Try setting "PNP aware OS" (or something like that) to "NO" in your > BIOS. > > Rene Blokland wrote: > > > > Hi there, as the subject says the trident sound does not work since > > 2.4.0-test9. this messages does dmesg: > > Trident 4DWave/SiS 7018/ALi 5451 PCI Audio, version 0.14.6, 12:36:52 Nov 20 2000 > > trident: Trident 4DWave DX found at IO 0xd800, IRQ 0 > > trident: unable to allocate irq 0 > > any ideas? > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to [EMAIL PROTECTED] > > Please read the FAQ at http://www.tux.org/lkml/ > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linus's include file strategy redux
My solution to this has always been to make a cross compiler environment (even if it is the same processor family). Thusly i386-linux-gcc knows that the target system's include files are in: /usr/local/-tools/i386-linux/include (/linux, /asm) The other advantage to this is that I can switch my host environment (within reason - compatible host glibcs, ok) and not have to change the target compiler. Werner Almesberger wrote: > [EMAIL PROTECTED] wrote: > >> Just out of curiosity, what would happen with redirection if your source >> tree for 'the currently running kernel' version happens to be configured >> for a different 'the currently running kernel', perhaps a machine of a >> foreign arch that you are cross-compiling for? > > > Two choices: > 1) try to find an alternative. If there's none, fail. > 2) make the corresponding asm or asm/arch branch available (non-trivial > and maybe not desirable) > > >> I do this: I use ONE machine to compile kernels for five: four i386 and >> one SUN4C. My other machines don't even HAVE /usr/src/linux, so where does >> this redirection leave them? > > > Depends on your distribution: if it doesn't install any kernel-specific > headers, you wouldn't be able to compile programs requiring anything > beyond what it provided by your libc. Otherwise, there could be a > default location (such as /usr/src/linux is a default location now). > > The main advantage of a script would be that one could easily compile > for multiple kernels, e.g. with > > export TARGET_KERNEL=2.0.4 > make > > Even if your system is running 2.4.13-test1. > > The architecture could be obtained from the tree or the tree could be > picked based on the architecture. This is a policy decision that could > be hidden in the script. > > - Werner -- Joe deBlaquiere Red Hat, Inc. 307 Wynn Drive Huntsville AL, 35805 voice : (256)-704-9200 fax : (256)-837-3839 - 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: Linus's include file strategy redux
Werner Almesberger wrote: > Joe deBlaquiere wrote: > >> My solution to this has always been to make a cross compiler environment > > > ;-))) I think lots of people would really enjoy to have "build a > cross-gcc" added to the prerequisites for installing some driver > module ;-) > > I know, it's not *that* bad. But it still adds quite a few possible > points of failure. Also, it adds a fair amount of overhead to any > directory name change or creation of a new kernel tree. > might be a good newbie filter... but actually the best thing about it is that the compiler people of the work might make generating a proper cross-toolchain less difficult by one or two magnitudes... > >> The other advantage to this is that I can switch my host environment >> (within reason - compatible host glibcs, ok) and not have to change the >> target compiler. > > > Hmm, I don't quite understand what you mean here. > This way I can upgrade my host system from RH6.2 to RH7 and not worry about compiler differences affecting my kernel builds for the various projects I'm working on... including systems based on 2.0, 2.2 and 2.4... If anybody thinks gcc-2.96 messes up a 2.4 kernel, you should see what happens when you compile 2.0.33 ;o). > - Werner -- Joe deBlaquiere Red Hat, Inc. 307 Wynn Drive Huntsville AL, 35805 voice : (256)-704-9200 fax : (256)-837-3839 - 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: Linus's include file strategy redux
Last I recall you have to at least have newlib around to get through the build process of gcc. libgcc doesn't affect the kernel but you can't do 'make install' without building it. BTW : The Linux newlib stuff should go a long way toward solving some of these problems (at least for x86 these days... other arches sure to follow) Peter Samuelson wrote: > [Joe deBlaquiere] > >> might be a good newbie filter... but actually the best thing about it >> is that the compiler people of the work might make generating a >> proper cross-toolchain less difficult by one or two magnitudes... > > > *WHAT*? How much less difficult could it possibly get? This is the > kernel, there is no cross-libc to worry about, so a cross-toolchain is > already down to a pair of CMMIs[1]. > > I do agree that anyone who can't do *that* should probably be using a > distro-packaged kernel > > Peter > > [1] configure-make-make-install -- Joe deBlaquiere Red Hat, Inc. 307 Wynn Drive Huntsville AL, 35805 voice : (256)-704-9200 fax : (256)-837-3839 - 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/
sysmips call and glibc atomic set
I'm working with a vr4181 target and started digging into the atomic
test and set stuff in the kernel and glibc. The first problem I had was
that the glibc code assumes that all mips III targets implement the mips
III ISA (funny assumption, no?) but the vr4181 doesn't include the
miltiprocessor oriented LL/SC operations for atomic test and set.
So I started looking at the glibc code (yes, I know this is the kernel
list... I'm getting there I promise) and notice the following operations:
__asm__ __volatile__
(".set mips2\n\t"
"/* Inline spinlock test & set */\n\t"
"1:\n\t"
"ll %0,%3\n\t"
".set push\n\t"
".set noreorder\n\t"
"bnez %0,2f\n\t"
" li %1,1\n\t"
".set pop\n\t"
"sc %1,%2\n\t"
"beqz %1,1b\n"
"2:\n\t"
"/* End spinlock test & set */"
: "=&r" (ret), "=&r" (temp), "=m" (*spinlock)
: "m" (*spinlock)
: "memory");
The significant code here being the 'll' and 'sc' operations which are
supposed to ensure that the operation is atomic.
QUESTION 1) Will this _ALWAYS_ work from user land? I realize the
operations are temporally close, but isn't there the possibility that an
interrupt occurs in the meantime?
Of course none of this code applies to my case anyway, since the vr4181
doesn't implement these ops. So once I hack^H^H^H^Hadjust glibc to use
the 'mips1' implementation, it uses the sysmips system call. regard :
_test_and_set (int *p, int v) __THROW
{
return sysmips (MIPS_ATOMIC_SET, (int) p, v, 0);
}
So then I looked at the kernel and find the code below. The system I'm
working with is expressedly uniprocessor and doesn't have any swap, so
it looks like the initial caveats are met, but it looks to me like there
could be some confusion if the value of *arg1 at entry looks like
-ENOSYS or something like that.
QUESTION 2) Wouldn't it be better to pass back the initial value of
*arg1 in *arg3 and return zero or negative error code?
case MIPS_ATOMIC_SET: {
/* This is broken in case of page faults and SMP ...
Risc/OS faults after maximum 20 tries with EAGAIN. */
unsigned int tmp;
p = (int *) arg1;
errno = verify_area(VERIFY_WRITE, p, sizeof(*p));
if (errno)
return errno;
errno = 0;
save_and_cli(flags);
errno |= __get_user(tmp, p);
errno |= __put_user(arg2, p);
restore_flags(flags);
if (errno)
return tmp;
return tmp; /* This is broken ... */
}
QUESTION 3) I notice that the code for this particular case of sysmips
has changed recently. The old code looked more like the 'll/sc' version
of glibc above. I would think that the 'll/sc' code would be better on
SMP systems. Is there a good reason why this reverted?
Sorry For the Long Post (tm)! Thanks In Advance! Merry Xmas!
--
Joe deBlaquiere
Red Hat, Inc.
307 Wynn Drive
Huntsville AL, 35805
-
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: sysmips call and glibc atomic set
Ralf, firstly, thank you for the answers :)
Ralf Baechle wrote:
>
> Ok, but since the kernel disables MIPS III you're limited to MIPS II anyway ...
>
This makes sense...
>
>
> Read the ISA manual; sc will fail if the LL-bit in c0_status is cleared
> which will be cleared when the interrupt returns using the eret instruction.
>
I tried to find a MIPSIII manual from mips.com but all I could find was
mips32 and mips64 (which are not the same as MIPSII/MIPSIII/MIPSIV).
>
>
> Not having swap doesn't mean you're safe. Think of any kind of previously
> unmapped page.
>
Is there a reason why it doesn't just force that page to be mapped first?
>
>> QUESTION 2) Wouldn't it be better to pass back the initial value of
>> *arg1 in *arg3 and return zero or negative error code?
>
>
> The semantics of this syscall were previously defined by Risc/OS and later
> on continued to be used by IRIX.
>
>
>> case MIPS_ATOMIC_SET: {
>> /* This is broken in case of page faults and SMP ...
>> Risc/OS faults after maximum 20 tries with EAGAIN. */
>> unsigned int tmp;
>>
>> p = (int *) arg1;
>> errno = verify_area(VERIFY_WRITE, p, sizeof(*p));
>> if (errno)
>> return errno;
>> errno = 0;
>> save_and_cli(flags);
>> errno |= __get_user(tmp, p);
>> errno |= __put_user(arg2, p);
>> restore_flags(flags);
>>
>> if (errno)
>> return tmp;
>>
>> return tmp; /* This is broken ... */
>> }
>>
>> QUESTION 3) I notice that the code for this particular case of sysmips
>> has changed recently. The old code looked more like the 'll/sc' version
>> of glibc above. I would think that the 'll/sc' code would be better on
>> SMP systems.
>
>
> Don't think about SMP without ll/sc. There's algorithems available for
> that but their complexity leaves them a unpractical, theoretical construct.
>
>
>> Is there a good reason why this reverted?
>
Looking at 2.4.0-test5 I see the ll/sc code, but -test12 doesn't use it.
I was just curious at why it was taken out.
>
> Above code will break if the old content of memory has bit 31 set or you take
> pagefaults. The latter problem is a problem even on UP - think multi-
> threading.
>
> Finally, post such things to one of the MIPS-related mailing lists. If
> you're unlucky nobody of the MIPS'ers might see your posting on l-k.
>
> Ralf
--
Joe deBlaquiere
Red Hat, Inc.
307 Wynn Drive
Huntsville AL, 35805
voice : (256)-704-9200
fax : (256)-837-3839
-
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/
RR
When having 5 proceeses {A, B, C, D ,E}, with run times
A = 10
B = 6
C =2
D = 4
E = 8
Why does round robin do A -> E -> B -> D -> C,
why not just use FIFO?
-
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: more on scheduler benchmarks
Maybe I've been off in the hardware lab for too long, but how about 1. using ioperm to give access to the parallel port. 2. have your program write a byte (thread id % 256 ?) constantly to the port during it's other activity 3. capture the results from another computer with an ecp port This way you don't run the risk of altering the scheduler behavior with your logging procedure. Mike Kravetz wrote: > Last week while discussing scheduler benchmarks, Bill Hartner > made a comment something like the following "the benchmark may > not even be invoking the scheduler as you expect". This comment > did not fully sink in until this weekend when I started thinking > about changes made to sched_yield() in 2.4.0. (I'm cc'ing Ingo > Molnar because I think he was involved in the changes). If you > haven't taken a look at sys_sched_yield() in 2.4.0, I suggest > that you do that now. > > A result of new optimizations made to sys_sched_yield() is that > calling sched_yield() does not result in a 'reschedule' if there > are no tasks waiting for CPU resources. Therefore, I would claim > that running 'scheduler benchmarks' which loop doing sched_yield() > seem to have little meaning/value for runs where the number of > looping tasks is less than then number of CPUs in the system. Is > that an accurate statement? > > If the above is accurate, then I am wondering what would be a > good scheduler benchmark for these low task count situations. > I could undo the optimizations in sys_sched_yield() (for testing > purposes only!), and run the existing benchmarks. Can anyone > suggest a better solution? > > Thanks, -- Joe deBlaquiere Red Hat, Inc. 307 Wynn Drive Huntsville AL, 35805 voice : (256)-704-9200 fax : (256)-837-3839 - 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: [OT?] Coding Style
Too bad we can't just do a "Prince" and invent unpronouncable symbols to use as function names... or perhaps just use something from the chinese fonts ;o)... Mike Harrold wrote: >> This message is in MIME format. Since your mail reader does not understand >> this format, some or all of this message may not be legible. >> >> --_=_NextPart_001_01C08552.FFC336D0 >> Content-Type: text/plain; >> charset="ISO-8859-1" >> >> I prefer descriptive variable and function names - like comments, they help >> to make code so much easier to read. >> >> One thing I wonder though... why do people prefer 'some_function_name()' >> over 'SomeFunctionName()'? I personally don't like the underscore character >> - it's an odd character to type when you're trying to get the name typed in, >> and the shifted character, I find, is easier to input. >> > > > For exactly the reverse of that reason. Typing capital letters is a heck > of a lot more difficult that addint an underscore. > > Then there is reasability. > > void ThisIsMyDumbassFunctionName > > if MUCH more difficult to read than > > void this_is_my_clear_and_easy_function_name > > Regards, > > /Mike > > >> Cheers! >> Jon >> >> >>> -Original Message- >>> From: Steve Underwood [mailto:[EMAIL PROTECTED]] >> >> Some people still seem to be living in the age of K&R C, with 6 or 7 >> character variable names that demand some explanation. Maybe some day >> they will awake to the expressive power of long (and well chosen) names. >> >> --_=_NextPart_001_01C08552.FFC336D0 >> Content-Type: text/html; >> charset="ISO-8859-1" >> Content-Transfer-Encoding: quoted-printable >> >> >> >> >> > charset=3DISO-8859-1"> >> > 5.5.2652.35"> >> RE: [OT?] Coding Style >> >> >> >> I prefer descriptive variable and function names - = >> like comments, they help to make code so much easier to read. >> >> >> One thing I wonder though... why do people prefer = >> 'some_function_name()' over 'SomeFunctionName()'? I personally = >> don't like the underscore character - it's an odd character to type = >> when you're trying to get the name typed in, and the shifted character, = >> I find, is easier to input. >> >> Cheers! >> Jon >> >> >> > -Original Message- >> > From: Steve Underwood [> HREF=3D"mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]]= >> >> >> >> Some people still seem to be living in the age of = >> K&R C, with 6 or 7 >> character variable names that demand some = >> explanation. Maybe some day >> they will awake to the expressive power of long (and = >> well chosen) names. >> >> >> >> >> --_=_NextPart_001_01C08552.FFC336D0-- >> - >> 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/ -- Joe deBlaquiere Red Hat, Inc. 307 Wynn Drive Huntsville AL, 35805 voice : (256)-704-9200 fax : (256)-837-3839 - 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/
Is it possible to force don't fragment on a socket?
I'm trying to test a communications path to a remote system and was wondering if I could force the DF bit on some UDP traffic. Does anybody know of a way to do this?? TIA, Joe - 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: kernel boot problems
A few things come to mind: 1. Is your init statically linked or linked with shared libraries? If it's shared, do you have all the shared objects on your disk image in a place where they can be found (/lib, I hope)? You might try linking it statically (but stripped) just to make sure. 2. Is it in the path that the kernel is looking in? check init/main.c to see what your kernel is looking for (it's some educational reading anyway). 3. Even if 'init' isn't found, it should try to run /bin/sh as a last resort. I can't imagine you don't have one of those. 4. Is init executable? 5. "unable to open an initial console" probably means you don't have the necesary device nodes (refer to init/main.c) 6. If this doesn't help, there is a ramdisk FAQ that is well written... Good luck with it! Joe Ryan Hairyes wrote: > Hello all, > > I was wondering if someone might be able to help me. > I have just compiled my kernel and set it up on a floppy > to boot off a disk. I have it then use an image file to uncompress > and get the filesystem off ,etc. Well when it boots it says it has > uncompressed the filesystem image and then gives me this: > Mounted Root (ext2 filesystem) readonly > Freeing unused kernel memory: 212K freed > Warning: unable to open an initial console > Kernel panic: no init found. Try passing init= option to the kernel. > > I know that I have init on the image, so what could I be doing wrong. > It is probably something stupid that I am overlooking, but I thank you in > advance. > > Ryan > > - > 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: [linux-audio-dev] low-latency scheduling patch for 2.4.0
Andrew Morton wrote: > There has been surprisingly little discussion here about the > desirability of a preemptible kernel. > And I think that is a very intersting topic... (certainly more interesting than hotmail's firewalling policy ;o) Alright, so suppose I dream up an application which I think really really needs preemption (linux heart pacemaker project? ;o) I'm just not convinced that linux would ever be the correct codebase to start with. The fundamental design of every driver in the system presumes that there is no preemption. A recent example I came across is in the MTD code which invokes the erase algorithm for CFI memory. This algorithm spews a command sequence to the flash chips followed by a list of sectors to erase. Following each sector adress, the chip will wait for 50usec for another address, after which timeout it begins the erase cycle. With a RTLinux-style approach the driver is eventually going to fail to issue the command in time. There isn't any logic to detect and correct the preemption case, so it just gets confused and thinks the erase failed. Ergo, RTLinux and MTD are mutually exclusive. (I should probably note that I do not intend this as an indictment of RTLinux or MTD, but just an example of why preemption breaks the Linux driver model). So what is the solution in the preemption case? Should we re-write every driver to handle the preemption? Do we need a cli_yes_i_mean_it() for the cases where disabling interrupts is _absolutely_ required? Do we push drivers like MTD down into preemptable-Linux? Do we push all drivers down? In the meantime, fixing the few places where the kernel spends an extended period of time performing a task makes sense to me. If you're going to be busy for a while it is 'courteous' to allow the scheduler a chance to give some time to other threads. Of course it's hard to know when to draw the line. So now I am starting to wonder about what needs to be profiled. Is there a mechanism in place now to measure the time spent with interrupts off, for instance? I know this has to have been quantified to some extent, right? -- Joe deBlaquiere Red Hat, Inc. 307 Wynn Drive Huntsville AL, 35805 voice : (256)-704-9200 fax : (256)-837-3839 - 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: Support for 802.11 cards?
There is a rather informative discussion of wireless support at : http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.html Though possibly a little out of date, the author of this obviously did their research. Kudos! -- Joe Michael H. Warfield wrote: > On Sun, Jan 28, 2001 at 05:07:33PM -0500, John Jasen wrote: > >> On Sun, 28 Jan 2001, Mike Pontillo wrote: > > >>> I was wondering what 802.11 PCI cards anyone knows of that run >>> under Linux-2.4. (or 2.2 for that matter) >> > >> I _think_ a good many of the 802.11 wireless ISA and PCI cards are just >> bus to PCMCIA adapters, so it would be a question of whether or not the >> PCMCIA card is supported and if the bridge is supported. > > > Last I knew (straight from the Lucent people), the ISA bridge > card worked fine and the PCI card did NOT work at all. I've since > confirmed that, first hand, myself (I currently have the ISA bridge in > operation) on the 2.2 kernels. The ISA bridge also works on the 2.4 > kernels but I have not retested the PCI bridge on 2.4. The Lucent > people claim that the Linux pcmcia people are aware of the problem. > > Mike - 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/
e820 Memory Detect Backport Patch
Is it possible to extract *just* the E820 memory detect patch from the 2.2.19-pre1 patch? We recently received a bunch of new Intel server boxes with the STL2 motherboard. However, 2.2.1x refuses to detect more than 64Megs of RAM; I've heard that this patch fixes that problem. (A different solution is to upgrade the BIOS to 1.4 (Build 18), but although the updated Intel docs mention this BIOS revision, it isn't available on the Intel site.) Theorectically, I could extract the patched files myself from the breakdown of the pre-2.2.19-1 patch on linuxhq.com. My main fear would be either missing something, or including a change relating to something else in the patch set that subsquently breaks things. And since these boxes have to go into production relatively quickly, I'd rather not install the complete pre-2.2.19-7 patch set, if I can avoid it. (The higher ups frown heavily on anything that doesn't appear to be "production ready".) I would appreciate any help, either via a list of file patches that I can extract, or through some pointer to a place where I can download just this patch. Thanks. ======= Joe LizziSysAdmin [EMAIL PROTECTED]Advance Internet 201-459-2826 - 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: novatel minstrel on 2.4
Adam Fritzler wrote:
> We've been trying to set up a laptop here to use a Novatel Minstrel PCMCIA
> modem (wireless Richocet network). The card shows up as a serial port
> (ttySx) and accepts AT commands just like a normal modem.
>
I'm in the process of bringing up a Novatel Merlin now (tomorrow morning
actually). I don't know how similar it is, but they do at least use some
common hardware on the Merlin and Sage products.
> It dials fine, PPP connects, gets IPs, etc just as it should. However,
> any packet over about 400 bytes gets dropped on the recieve. Also, the RX
> errors on ppp0 increment occasionally.
>
According to http://people.freebsd.org/~nsayer/ you have to set the mru
to 576 for the Merlin. There is some fairly detailed info on
http://www.mrollins.com/newtmerlin.html about setting it up for (of all
things) a Newton including all the expected commands which implies that
you should adjust the mru setting on the card and then match that with ppp.
> TCP connections connect (because the SYN's are small), but as soon as you
> start trying to do bulk transfers (`ls -la` in an ssh window, or an HTTP
> GET), the connection stalls. Pinging other hosts also works fine, except
> when you do -s with a value larger than 300 or so.
>
> It doesn't work with anything we've tried on 2.4 (changing mtu/mru, serial
> port speed, etc). However, under 2.2.x, we were able to get connections to
> stay running and not stall by setting the MTU on ppp0 to 120 after the ppp
> comes up. As you can imagine, this makes the modem seem even slower than
> it already is.
>
> Not that its relevent, but pppstats shows 0 in the 'vjcomp' fields of
> both rx and tx (as well as 'vjerr'). I've tried starting pppd with and
> without 'novj' just in case. Same result.
>
> Any ideas? The 'rx error' count going up is kind of suspicious. My
> attempts at getting pppd to print more debugging output have been
> futile; aparently the debug and kdebug options no longer work ('debug'
> produces the LCP traffic, yes, but thats working fine).
>
> af
>
> -
> 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/
--
Joe deBlaquiere
Red Hat, Inc.
307 Wynn Drive
Huntsville AL, 35805
voice : (256)-704-9200
fax : (256)-837-3839
-
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: [linux-audio-dev] low-latency scheduling patch for 2.4.0
David Woodhouse wrote: > On Thu, 1 Feb 2001, Pavel Machek wrote: > > >> I thought that Vtech Helio folks already have XIP supported... > > > Plenty of people are doing XIP of the kernel. I'm not aware of anyone > doing XIP of userspace pages. uClinux does XIP (readonly) for userspace programs in the Dragonball port. Of course it's a different executable format than Linux, so there are some hooks for it. -- Joe - 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: Serial device with very large buffer
Hi Alex! I'm a little confused here... why are we overrunning? This thing is running externally at 19200 at best, even if it does all come in as a packet. I would think the flip buffer would never contain more than a few characters. Are you running it at a higher rate internally? Does it buffer up a whole packet if you do this? Wouldn't it be a little easier to drop somthing like "AT#MRU=500\r" to the modem than to change the tty driver? -- Joe Alex Belits wrote: > On Thu, 1 Feb 2001, Alan Cox wrote: > > >>> I also propose to increase the size of flip buffer to 640 bytes (so the >>> flipping won't occur every time in the middle of the full buffer), however >>> I understand that it's a rather drastic change for such a simple goal, and >>> not everyone will agree that it's worth the trouble: >> >> Going to a 1K flip buffer would make sense IMHO for high speed devices too > > > 1K flip buffer makes the tty_struct exceed 4096 bytes, and I don't think, > it's a good idea to change the allocation mechanism for it. - 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: Serial device with very large buffer
Alex Belits wrote: > On Thu, 1 Feb 2001, Joe deBlaquiere wrote: > > >> Hi Alex! >> >> I'm a little confused here... why are we overrunning? This thing is >> running externally at 19200 at best, even if it does all come in as a >> packet. > > > Different Merlin -- original Merlin is 19200, "Merlin for Ricochet" is > 128Kbps (or faster), and uses Metricom/Ricochet network. so can you still limit the mru? -- Joe - 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/
Kernel oopses 2.4.5
Here is a series of oopses. They occured while realplay was running. The sound changed from the dulcit tones of Marvin Gaye to short, static-y bursts. Innocently enough, I thought to bother my sound driver's maintainer, but the problem isn't in his regime; not knowing who else to bother, I'm posting this here. Machine is a Pentium II 350 running Debian testing. Any further info/testing needed, just ask me. Please CC me in any reply, as I am not subscribed to the list. I have not been able to reproduce the problem. Thanks. -- Joe Haas ksymoops 2.4.1 on i686 2.4.5. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.5/ (default) -m /usr/src/linux/System.map (specified) Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(shmem_file_setup) not found in System.map. Ignoring ksyms_base entry Jun 21 07:47:53 lembas kernel: cpu: 0, clocks: 1002294, slice: 501147 Jun 21 07:47:53 lembas kernel: ds: no socket drivers loaded! Jun 21 07:48:14 lembas kernel: ac97_codec: AC97 codec, id: 0x414b:0x4d00 (Asahi Kasei AK4540) Jun 21 11:59:52 lembas kernel: Unable to handle kernel paging request at virtual address 021802c2 Jun 21 11:59:52 lembas kernel: c0114bcf Jun 21 11:59:52 lembas kernel: *pde = Jun 21 11:59:52 lembas kernel: Oops: 0002 Jun 21 11:59:52 lembas kernel: CPU:0 Jun 21 11:59:52 lembas kernel: EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 Jun 21 11:59:52 lembas kernel: EFLAGS: 00010286 Jun 21 11:59:52 lembas kernel: eax: 021802c2 ebx: c549bdc0 ecx: c435e250 edx: c435e250 Jun 21 11:59:52 lembas kernel: esi: c435e000 edi: 021802c2 ebp: bf5ffb24 esp: c435ff90 Jun 21 11:59:52 lembas kernel: ds: 0018 es: 0018 ss: 0018 Jun 21 11:59:52 lembas kernel: Process realplay (pid: 2447, stackpage=c435f000) Jun 21 11:59:52 lembas kernel: Stack: c549bdc0 c435e000 bf5ffb24 bf5ffb24 c01151af 021802c2 c435e000 Jun 21 11:59:52 lembas kernel:bf5ffc00 bf7ffc00 c0115312 c0106a7b 0020 401ad5dc Jun 21 11:59:52 lembas kernel:bf5ffc00 bf7ffc00 bf5ffb24 0001 c010002b 002b 0001 402514ed Jun 21 11:59:52 lembas kernel: Call Trace: [] [] [] [] Jun 21 11:59:52 lembas kernel: Code: ff 0f 0f 94 c0 84 c0 0f 84 9c 00 00 00 8b 57 14 31 ed 31 f6 >>EIP; c0114bcf<= Trace; c01151af Trace; c0115312 Trace; c0106a7b Trace; c010002b Code; c0114bcf <_EIP>: Code; c0114bcf<= 0: ff 0f decl (%edi) <= Code; c0114bd1 2: 0f 94 c0 sete %al Code; c0114bd4 5: 84 c0 test %al,%al Code; c0114bd6 7: 0f 84 9c 00 00 00 je a9 <_EIP+0xa9> c0114c78 Code; c0114bdc d: 8b 57 14 mov0x14(%edi),%edx Code; c0114bdf 10: 31 ed xor%ebp,%ebp Code; c0114be1 12: 31 f6 xor%esi,%esi Jun 21 11:59:52 lembas kernel: Unable to handle kernel paging request at virtual address 078d023e Jun 21 11:59:52 lembas kernel: c01151ca Jun 21 11:59:52 lembas kernel: *pde = Jun 21 11:59:52 lembas kernel: Oops: 0002 Jun 21 11:59:52 lembas kernel: CPU:0 Jun 21 11:59:52 lembas kernel: EIP:0010:[] Jun 21 11:59:52 lembas kernel: EFLAGS: 00010202 Jun 21 11:59:52 lembas kernel: eax: ebx: 078d023e ecx: c435e250 edx: c435e250 Jun 21 11:59:52 lembas kernel: esi: c435e000 edi: 000b ebp: 021802c2 esp: c435fe90 Jun 21 11:59:52 lembas kernel: ds: 0018 es: 0018 ss: 0018 Jun 21 11:59:52 lembas kernel: Process realplay (pid: 2447, stackpage=c435f000) Jun 21 11:59:52 lembas kernel: Stack: 0002 c010fc14 c0106f7e 000b c010ff67 c020d77e c435ff5c Jun 21 11:59:52 lembas kernel:0002 c435e000 0002 c010fc14 bf5ffb24 0046 c435e000 Jun 21 11:59:52 lembas kernel:0046 c25c4000 00030001 c0119f5a c25c4000 0286 0020 c0119fd4 Jun 21 11:59:52 lembas kernel: Call Trace: [] [] [] [] [] [] [] Jun 21 11:59:52 lembas kernel:[] [] [] [] [] [] [] [] Jun 21 11:59:52 lembas kernel: Code: ff 0b 0f 94 c0 84 c0 0f 84 88 00 00 00 8b 43 0c 50 e8 50 7f >>EIP; c01151ca<= Trace; c010fc14 Trace; c0106f7e Trace; c010ff67 Trace; c010fc14 Trace; c0119f5a Trace; c0119fd4 Trace; c011a20d Trace; c011a959 Trace; c0106b98 Trace; c0110018 Trace; c0114bcf Trace; c01151af Trace; c0115312 Trace; c0106a7b Trace; c010002b Code; c01151ca <_EIP>: Code; c01151ca<= 0: ff 0b decl (%ebx) <= Code; c01151cc 2: 0f 94 c0 sete %al Code; c01151cf 5: 84 c0 test %al,%al Code; c01151d1 7: 0f 84 88 00 00 00 je 95 <_EIP+0x95> c011525f Code; c01151d7 d: 8b 43 0c mov0xc(%ebx
