Hi,
While trying 2.4.0-test10-pre1 on my Sun4m SparcSystem600, i'm getting an
error during 'make dep' ;((
I don't know anything about assembly, so there I can't help, but here's
the output:
galaxy:/usr/src/kernel-source-2.4-0-test10-pre1# make dep
make -C arch/sparc/kernel check_asm
make[1]: Ent
Kurt Garloff wrote:
> Actually, 2.0e3 did include one rather important fix which solved the
> trouble: Some devices get upset, when the driver tries to negotiate sync
> (or wide) connections, but the device actually does not support it.
> So, the driver now waits for the first INQUIRY result and
On Tue, Oct 10, 2000 at 12:32:50PM -0300, Rik van Riel wrote:
> > So now you can stop arguing about the one and only OOM killer,
> > implement it, provide it as module and get back to the important
> > stuff ;-)
>
> This is definately a cool toy for people who have doubts
> that my OOM killer wil
On Tue, Oct 10, 2000 at 12:30:51PM -0300, Rik van Riel wrote:
> Not killing init when we "should" definately prevents
> embedded systems from auto-rebooting when they should
> do so.
>
> (OTOH, I don't think embedded systems will run into
> this OOM issue too much)
but when they do, they're hard
On Tue, Oct 10, 2000 at 07:21:05AM -0500, Jordan wrote:
> Everything is working great! I can access my hard drive quickly, both
> CD drives are working and I can read and write to my zip as a
> partitioned drive or as a block device for Tar archives. Thanks for all
> of the help.
Great. Thanks
On Tue, 10 Oct 2000, Ingo Oeser wrote:
> before you argue endlessly about the "Right OOM Killer (TM)", I
> did a small patch to allow replacing the OOM killer at runtime.
>
> So now you can stop arguing about the one and only OOM killer,
> implement it, provide it as module and get back to the i
On Tue, 10 Oct 2000, Philipp Rumpf wrote:
> On Tue, Oct 10, 2000 at 12:06:07PM -0300, Rik van Riel wrote:
> > On Tue, 10 Oct 2000, Philipp Rumpf wrote:
> > > > > The algorithm you posted on the list in this thread will kill
> > > > > init if on 4Mbyte machine without swap init is large 3 Mbytes
>
> Doesn't work for all devices. Also since base_addr is truncated to
> 16-bits when passed to ifconfig, this gets even nastier for userspace.
You do the best you can with what's available :)
> ...and noone but the driver can trust this information to be pointing to
> an up-to-date struct netdev
On Tue, Oct 10, 2000 at 12:06:07PM -0300, Rik van Riel wrote:
> On Tue, 10 Oct 2000, Philipp Rumpf wrote:
> > > > The algorithm you posted on the list in this thread will kill
> > > > init if on 4Mbyte machine without swap init is large 3 Mbytes
> > > > and you execute a task that grows over 1M.
>
"Phillips, Mike" wrote:
> Take a look at the olympic driver (drivers/net/tokenring/olympic.c)
> function olympic_proc_info. This is called from a read into the proc
> filesystem. When we get the read we want to print out details on
> all the olympic devices in the system so we have to scan the
> p
On Tue, 10 Oct 2000, Philipp Rumpf wrote:
> > > The algorithm you posted on the list in this thread will kill
> > > init if on 4Mbyte machine without swap init is large 3 Mbytes
> > > and you execute a task that grows over 1M.
> >
> > This sounds suspiciously like the description of a DEAD syste
[OOM killer war]
Hi there,
before you argue endlessly about the "Right OOM Killer (TM)", I
did a small patch to allow replacing the OOM killer at runtime.
You can even use modules, if you are careful (see khttpd on how
to do this without refcouting).
So now you can stop arguing about the one a
Hi...
I _hate_ to do this, but I couldn't find (except for a reference to
"others who have segfaults using glibc") no reference to this problem.
Insmod of i2c, videodev and bttv succeed without problems or any message
in /var/log/debug, messages or syslog.
Also, though I'm surely no expert, I
Hi
I don´t know if it has been fixed in 2.4.0-test10-pre but on alpha
there´s a little mistake in inlude/asm-alpha/fcntl.h:
#define F_LINUX_SPECIFIC_BASE 1024
is missing. This prevents alpha from compiling. I added it till now
everything seems OK.
Do I need do make a patch or can someone fix it
>(There is a second generation drive, ADR-x0, which has a much more advanced
> firmware and does fully comply with SCSI-2 spec, BTW.)
'fully'? Not.
This latter drive has had problems too, but it seems to me that the arrival of
the ADR-50 should preclude the need to support the ADR-30.
-
To
Linus Torvalds wrote:
> Basically, the only thing _I_ think X can do is to really say "oh, please
> don't count my memory, because everything I do I do for my clients, not
> for myself".
>
> THAT is my argument. Basically there is nothing we can reliably account.
>
> So we might as well fall ba
On Tue, Oct 10, 2000 at 09:06:49AM +0200, Helge Hafting wrote:
> If you want init to live - prove that it don't eat too much memory.
I don't see why the machine should be stable only if init is small.
My kernel won't be stable only if init is small since it doesn't cost
anything to handle correct
Hi,
First some explanation. Most cryption algorithms initialize
the cryption process with some init values, called IV (by me :-).
This means that two identical clear messages will give
different encrypted messages, if different IVs are used.
The loop device supports different IVs;
the IVs are in
> I tried the patch, but the result is the same... Uncompressing Linux...,
> now booting the kernel..., NOTHING
> These Winchips need all the help they can get, so if you know something
> else I might try...
Ok, I've narrowed it down to the changes to mtrr.c in test8
Looks like the Cyrix III
Hi Linus, hi Alan,
I'd like to get some driver included into the mainstream kernels.
The driver is a new high-level SCSI driver, which was derived from the
standard st driver. It drives the OnStream tape drives SC-30/50 (SCSI) and
DI-30 (IDE, via ide-scsi) and USB-30 (USB, via usb-storage). The
On Tue, Oct 10, 2000 at 04:38:02AM +0100, Philipp Rumpf wrote:
> Init should never die. If we get to do_exit in init we'll panic which is
> the right thing to do (reboot on critical systems).
If the page fault can fail with OOM on init, init will get a SIGSEGV while
running a signal handler (cop
I have problem with Matrox G400 framebuffer. After turn
on computer, kernel freez durning boot with snow on my monitor.
When I start it with options video=matrox:disbled, and run XFree86
4.0.1 with official drivers from Matrox web page, and reboot my
computer again - everything works fine.
>From
Oops.. sorry for the typo. The server in question is running linux-2.2.16
tarball from ftp.kernel.org instead of 2.2.17 .
Thanks!
- Forwarded message from [EMAIL PROTECTED] -
Date: Tue, 10 Oct 2000 21:28:14 +0800 (SGT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Subject: set_rtc
Hello!
I am currently running the tarball linux-2.2.17 from ftp.kernel.org on a
RedHat Linux 6.2 server. The server is a Dell PowerEdge 4300 with 1GB RAM
, 2 x PIII600 and a DRAC PERC2/SC RAID controller.
The server mainly runs software like MySQL Server, Samba Server, NFS
Server and LDAP Ser
"Jeff V. Merkey" wrote:
>
> "Jeff V. Merkey" wrote:
> >
> > "David S. Miller" wrote:
> > >
> > >Date:Tue, 10 Oct 2000 00:44:58 +0200
> > >From: "Andi Kleen" <[EMAIL PROTECTED]>
> > >
> > >On Mon, Oct 09, 2000 at 11:41:13PM +0100, Alan Cox wrote:
> > >> I dont actually kn
Hi Andrew,
Take a look at the olympic driver (drivers/net/tokenring/olympic.c)
function olympic_proc_info. This is called from a read into the proc
filesystem. When we get the read we want to print out details on
all the olympic devices in the system so we have to scan the
pci tree and find a mat
Andi Kleen wrote:
>
> On Fri, Oct 06, 2000 at 10:00:36PM +1100, Andrew Morton wrote:
> > The little-low-latency patch for test9 is at
> >
> > http://www.uow.edu.au/~andrewm/linux/2.4.0-test9-low-latency.patch
> >
> > Notes:
> >
> > - It now passes Benno's tests with 50% headroom (thanks to
On Mon, 9 Oct 2000, Linus Torvalds wrote:
> On Mon, 9 Oct 2000, Rik van Riel wrote:
> >
> > > I'd prefer just X having a higher "mm nice level" or something.
> >
> > Which it has, because:
> >
> > 1) CAP_RAW_IO
> > 2) p->euid == 0
>
> Oh, I agree, but we might want to generalize this a bit so
Hi There!
1.: SCSI lock-up when scanning with SNAPSCAN1236
2.:
I have an AGFA SNAP-scan 1236S and used it with the kernel
2.2.16 and with the new beta-test-kernel 2.4.0-test9.
The SCSI-Controller is a aha152x and is working fine with
the 2.2.16 kernel except that there is an error message from
[EMAIL PROTECTED] wrote:
>
> 3. Security
>
> * Fix module remove race bug (still to be done: TTY, ldisc, I2C,
>video_device - Al Viro) (Rogier Wolff will handle ATM)
Patch for tty and ldisc is in your inbox...
> ...
>
> 8. Fix Exists But Isnt Merged
>
> ...
> * Many network
On Mon, 9 Oct 2000, Daniel Lange wrote:
> Periodically, I get the following error with the 2.4.0test9 kernel:
>
> spurious 8259A interrupt: IRQ7.
>
[SNIPPED...]
This will sometimes happen with the 8259A and really should not even
be logged. There is a default handler for all interrupts. If thi
"Phillips, Mike" wrote:
>
> >> hi all,
> >> given struct netdevice for any pci network device, is there any way to
> get
> >> corresponding
> >> "struct pci_dev".
>
> > No.
>
> Not directly, but pci_dev knows about netdevice, so you can scan the
> pci_dev's
> to find a match with the required n
Based of my measurement on i386 smp configuration,
If a system has plenty of runnable tasks, schedule() produces
noticable amount of cache misses at runqueue-head traversing and the
goodness calculations.
David S. Miller writes:
> Some of us actually have instrumented it :-) I added a coloring
>> hi all,
>> given struct netdevice for any pci network device, is there any way to
get
>> corresponding
>> "struct pci_dev".
> No.
Not directly, but pci_dev knows about netdevice, so you can scan the
pci_dev's
to find a match with the required netdevice. (Or do a similar match search
on base_a
echo "0" >/proc/sys/net/ipv4/tcp_ecn
Yes, Cisco does know about the bug in their product.
Later,
David S. Miller
[EMAIL PROTECTED]
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Hi!
Ok, that means Andre's patch works. Congrats, Andre! Now, could you send
me 'hdparm -i /dev/hdb' for the ZIP? It seems to be in SWDMA0 mode,
which is interesting, because I thought it can't do that. You probably
have some newer model.
Do all your drives work correctly now?
Thanks for your e
Hello
While working at home without a network card this kernel looked pretty
stable.
However now with network it looks like my SMP BP6 has some serious
locking porblems.
I've got this oops - sorry I don't have really oops message in the log
so only some numbers
with my hand transaltion:
EIP: 001
I am currently booted into a 2.4.0-test10-pre1 kernel with two
modifications, the VIA 3.6 drivers you have provided and the Patch from
Andre that you sent. My IBM is the primary master with the zip as its
slave and the Kenwood is the secondary master with the Plextor as its
slave. Here is my /pr
Andries Brouwer wrote:
>
> On Mon, Oct 09, 2000 at 04:37:38PM +, Zdenek Kabelac wrote:
>
> > I'm having some serious problems with parallel port ZIP with latest
> > 2.4.0-test9 kernel
> > Oct 9 16:57:23 dual kernel: Detected scsi removable disk sda at scsi0,
> > channel
> > Oct 9 16:57:24
On Tue, Oct 10, 2000 at 04:44:40PM +0530, [EMAIL PROTECTED] wrote:
> hi all,
> given struct netdevice for any pci network device, is there any way to get
> corresponding
> "struct pci_dev".
No.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
hi all,
given struct netdevice for any pci network device, is there any way to get
corresponding
"struct pci_dev".
-
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/
I already pointed this out :-). Its not only write caching (dev null doesnt
write at all)
I think its read caching (read ahead)
Cheers
Markus
"Mike A. Harris" wrote:
> On Mon, 9 Oct 2000, blizbor wrote:
>
> >> On Mon, 9 Oct 2000, Andre Tomt wrote:
> >>
> >> The fastest ATA drives out that are n
On Thu, Oct 05, 2000 at 06:01:32AM -0500, Gnea wrote:
> So here's the scoop:
>
> I'm putting together this system for my sister to dual-boot Linux
> (debian) and Windows 98. Originally, I had an IBM 1.7gig ata33 hard
> drive in there, and everything worked fine. Then she decided she
> wanted to
On Tue, Oct 10, 2000 at 11:52:33AM +0200, Matthias Andree wrote:
> On Mon, 02 Oct 2000, Alan Cox announced:
> > 2.2.18pre15
>
> I'd like to know if there are any issues with the current dc390-2.0e or
> 2.0e3 drivers that prevent its inclusion/that prevent Kurt from
> submitting it for inclusion.
On Tue, Oct 10, 2000 at 04:27:04AM -0500, Jordan wrote:
> I have tried moving the Kenwood CDROM and the Zip between channels and
> this works well. I would get rid of the zip if it was a viable option
> but need it to do transfers, and the IBM has a real UDMA 66 cable and
> upto ATA 100 capabilit
On Tue, Oct 10, 2000 at 11:17:31AM +0200, Markus Pfeiffer wrote:
> Vojtech Pavlik wrote:
> >
> > On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
> > Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
> > setup where would be just one drive and a really short, 40-wir
Date:Tue, 10 Oct 2000 10:54:11 +0100 (BST)
From: Alan Cox <[EMAIL PROTECTED]>
Having the stacks aligned also isnt good for the caches. If you are
bored some time instrument the cache lines that wake_up() touches
on a wake. Its very common to see most of them being on the sa
--On 09 October 2000, 17:40 -0300 Rik van Riel <[EMAIL PROTECTED]>
wrote:
> On Mon, 9 Oct 2000, James Sutherland wrote:
>> On Mon, 9 Oct 2000, Ingo Molnar wrote:
>> > On Mon, 9 Oct 2000, Rik van Riel wrote:
>> >
>> > > > so dns helper is killed first, then netscape. (my idea might not
>> > > > ma
Andreas Dilger wrote:
> Having a SIGDANGER handler is good for 2 reasons:
> 1) Lets processes know when memory is short so they can free needless cache.
> 2) Mark process with a SIGDANGER handler as "more important" than those
>without. Most people won't care about this, but init, and X, and
> Linus Torvalds wrote:
> > You can also still do the stack pointer plaything by just using
> > indirection: and when you context switch you switch the pointer around =
> at
> > the base of the per-cpu interrupt stack.
>
> Indirection, =E0 la "current =3D *(stack & ~8191)" might not be a bad ide=
On Mon, 02 Oct 2000, Alan Cox announced:
> 2.2.18pre15
I'd like to know if there are any issues with the current dc390-2.0e or
2.0e3 drivers that prevent its inclusion/that prevent Kurt from
submitting it for inclusion. As per the web page, 2.0e was supposed to
be sent to Linux for 2.4, so it sh
> Alan Cox wrote:
> > - Fix the megaraid (revert if need be)
>
> is this the source of repeated "Blocked mailbox..!!" messages which
> cause lock-ups on three Dell PowerEdge 2450s we have with AMI MegaRaid
> Enterprise 1500 controllers in them?
The current 2.2.18pre does this with certain sp
Albert D. Cahalan wrote:
> X, and any other big friendly processes, could participate in
> memory balancing operations. X could be made to clean out a
> font cache when the kernel signals that memory is low. When
> the situation becomes serious, X could just mmap /dev/zero over
> top of the backgr
> important here (and it could just be a simple configuration error.)
> Still, unless I'm mistaken, isn't an 8259A a UART, which should be related
> to the serial port? Seems odd it would show up on IRQ 7...
8259A is the interrupt controller on a PC. (A pair of them actually). They
raise IRQ 7 if
I've got the above message from 2.4.0-test10-1.
Don't know test9
--
Lorenzo
-
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/
Linus Torvalds wrote:
> You can also still do the stack pointer plaything by just using
> indirection: and when you context switch you switch the pointer around at
> the base of the per-cpu interrupt stack.
Indirection, à la "current = *(stack & ~8191)" might not be a bad idea
in general. As Ral
> Working our way up, Pete noticed that _sparc_free_io() wasn't aligning
> plen properly... problem solved.
>
> While we were there, we noticed a few more problems in the file (misuse
> of a #define, and poor renaming of copied code).
>
> At this point, the dbri driver is properly loadable and
Andi Kleen wrote:
> > 1. Move the error_code block from divide_error to page_fault;
> >this removes one jump from the page_fault path.
>
> It is not clear that it is worth it. You want to align error_code and
> page_fault to 16 or 32 bytes bytes at least, and it would need to execute
> some n
I have tried moving the Kenwood CDROM and the Zip between channels and
this works well. I would get rid of the zip if it was a viable option
but need it to do transfers, and the IBM has a real UDMA 66 cable and
upto ATA 100 capability so I wanted to take advantage of it. Thanks to
all that helpe
Alan Cox wrote:
> - Fix the megaraid (revert if need be)
is this the source of repeated "Blocked mailbox..!!" messages which
cause lock-ups on three Dell PowerEdge 2450s we have with AMI MegaRaid
Enterprise 1500 controllers in them?
Rob
--
Robert Brooks,Systems Manager,
Markus Pfeiffer wrote:
Vojtech Pavlik wrote:
>
> On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
> Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
> setup where would be just one drive and a really short, 40-wire cable
> without problems as well. I've even
On Mon, Oct 09, 2000 at 06:34:29PM -0300, Rik van Riel wrote:
> On Mon, 9 Oct 2000, Ingo Molnar wrote:
> > On Mon, 9 Oct 2000, Rik van Riel wrote:
> >
> > > Would this complexity /really/ be worth it for the twice-yearly OOM
> > > situation?
> >
> > the only reason i suggested this was the init=
Hallo,
I have a few PS2 / POS-Keyboard's (POS = Point of sale).
All the Keyboard have all additional devices, they ar Keylock,
Magnetical Reader, and Display's. All the Devices work
over the pc-Keyboard Controller.
I have written an extention for the pc_keyb.c Modul.
With this modul can I u
> > Still, it would be nice to recover that 4 MB when the system
> > doesn't have any memory left.
> Yup. The X server could give back the memory for some cases like the
> background without too much hackery.
Then Linux only needs to implement SIGDANGER, which has been talked
about for years...
On Tue, Oct 10, 2000 at 01:10:06AM -0700, Andre Hedrick wrote:
> These are two different issues.
> One is host side detection and the other is drive side
> detection/acknowledgement.
>
> ide0=ata66 overrides the host-rules
>
> ivb-byte93 overrides the mixed drive side rules.
>
> The only think
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips:
tda9840,tda9873h,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54
(PV951)
bttv: driver version 0.7.44 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
bttv: Bt8xx card found (0).
bttv0: Bt848 (rev 18) at 00:1
On Tue, 10 Oct 2000, Vojtech Pavlik wrote:
> On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
>
> > Also I need to adjust the rules for "ignore byte93" because the the
> > various methods that are being supported.
>
> Yes, it would be nice if we had some better guesses on whether
On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
> Also I need to adjust the rules for "ignore byte93" because the the
> various methods that are being supported.
Yes, it would be nice if we had some better guesses on whether to think
the 80-wire cable is present. It would also be
Also I need to adjust the rules for "ignore byte93" because the the
various methods that are being supported.
On Tue, 10 Oct 2000, Vojtech Pavlik wrote:
> Try the "ignore byte93" option in the IDE menu. The IBM doesn't try to
> do UDMA66 because the ZIP drive kills its 80-wire cable detection
>
On Tue, Oct 10, 2000 at 12:14:11AM -0700, James Simmons wrote:
> This patch fixes a minor config error for drivers/usb/Config.in. When you
> select USB Human Interface Device (HID) support I assume you should be
> able to select a USB mouse and/or USB keyboard. With the current Config.in
> you ca
On Mon, Oct 09, 2000 at 11:30:50PM +0100, Alan Cox wrote:
> > I think I'll go for the 'current is in a well-known register'
> > approach and see how this goes...
>
> Failing that the 2.0 approach will work, current is a global in uniprocessor
> and a #define to an array indexed by cpu id in smp
Andrea Arcangeli wrote:
>
> On Mon, Oct 09, 2000 at 08:42:26PM +0200, Ingo Molnar wrote:
> > ignoring the kill would just preserve those bugs artificially.
>
> If the oom killer kills a thing like init by mistake or init has a memleak
> you'll notice both problems regardless of having a magic fo
101 - 172 of 172 matches
Mail list logo
