On Sunday July 8, [EMAIL PROTECTED] wrote:
>
> Could well be. ext3 will happily feed 2,000 buffers into submit_bh()
> prior to running tq_disk. Everything else is happy with this, so I blame
> nfsd and raid5 :) Rapid fsyncs will break this up, however.
>
raid5 is definately happy with large
Hello to all.
I'm sorry if this is the wrong list to post this question to, but I
did 4 days ago, and haven't seen anything concerning my problem.
I have a Ricoh mp7120a cdrw drive. Since it is a atapi drive, i must
use ide-scsi and sg to use it with cdrecord. However there is a
strange
> Moreover, when swap is of, the hard disk
> goes crazy as if it where using swap, when in fact it isn't). Is this
> expected behaviour ?
Yes, it's recovering memory by dropping program text pages (memory
mapped from elf files) so those have to be reloaded when the program
executes them again.
The pci_device_id tables in linux-2.4.7-pre3/drivers/char/sonypi.c
claims that the driver wants to be loaded on all computers that have
an that have a PCI device with vendor id PCI_VENDOR_ID_INTEL and
a device ID of either PCI_DEVICE_ID_INTEL_82371AB_3 (0x7110) or
Neil Brown wrote:
>
> On Saturday July 7, [EMAIL PROTECTED] wrote:
> > An update of the ext3 journalling filesystem for 2.4 kernels
> > is available at
> >
> > http://www.uow.edu.au/~andrewm/linux/ext3/
> >
> > Patches are against 2.4.6-ac1 and 2.4.6.
>
> I thought it was time to try out
Solved with new ppp. Thanks, and sorry.
---
My modems (Courier 28.8 external, Actiontec PCI call waiting non-winmodem)
connect to the Internet fine with 2.4.0, and broke around 2.4.1. What
happens is they dial out, make those sounds, and just as they seem to be
Hi, all,
I am new to linux device driver. I do not know
how to change a module to a character device driver.
I have a module by hand, I want to modify it
to a character device driver. Then I can make it
in linux kernel, and do not need modutils rpm.
If someone knows, please help me. Thanks!
i was digging around for info on TCP_DEFER_ACCEPT and found this claim in
the thttpd mailing list archive:
> Alexey Kuznestov mentioned to me that on SMP servers, this option may
> not be desired as it creates a new contention point
is this still the case?
i haven't played with it yet, but i
On 08 Jul 2001 00:40:51 +, José Luis Domingo López wrote:
>
> Another interesting thing I noted is the fact (as shown by Robert Love's
> message) that oom_kill() seems to kill processes without taking into
> account whether the selected process is a full application or just one
> of more
On Saturday, 07 July 2001, at 18:00:08 -0400,
Robert Love wrote:
> i thought it would be nice to finally hear something good about the OOM
> killer.
> [...]
> kernel showed:
> Out of Memory: Killed process 1296 (evolution-mail).
> [...]
> Out of Memory: Killed process 1307 (evolution-mail).
>
I mailed the list about similar problems with 2.4.5. Since it's
still happening now that 2.4.6 is out I decided to send another
report.
The following will crash my 128 meg x86 running 2.4.6.
mke2fs /dev/ram0 8
mount /dev/ram0 /mnt
dd if=/dev/zero of=/mnt/junk bs=1024000 count=60
I poked
[EMAIL PROTECTED] wrote:
> >> Would it be possible to use a cramfs image in vmlinux (i.e. real
> >> filesystem image, not an in-kernel-structures fs like ramfs), and map
> >> it directly from the kernel image (it would have to be suitably aligned,
> >> of course)?
>
> > Yes that would work, and
On 7-Jul-01 at 20:42, Alan Cox ([EMAIL PROTECTED]) wrote:
> > I have Casio Fiva 102 which is a mini notebook based on Cyrix MediaGX
> > (clone) chipset. 2.4.5 runs like a charm, but 2.4.6, immediately
> > after starting, displays this:
>
> 2.4.7pre3 should fix that one
It works, thanks.
Mike Touloumtzis wrote:
> > Yes that would work, and it would work on machines with less RAM too.
> > You would want to remove the cramfs filesystem code when you're done though.
>
> Some of the files in the boot time FS would need to
> be kept around, such as the ACPI code, right?
Perhaps.
On Saturday July 7, [EMAIL PROTECTED] wrote:
> An update of the ext3 journalling filesystem for 2.4 kernels
> is available at
>
> http://www.uow.edu.au/~andrewm/linux/ext3/
>
> Patches are against 2.4.6-ac1 and 2.4.6.
I thought it was time to try out ext3 between nfsd and raid5, so I
On Sat, Jul 07, 2001 at 11:53:29PM +0200, Jamie Lokier wrote:
> Mike Touloumtzis wrote:
> >
> > Would it be possible to use a cramfs image in vmlinux (i.e. real
> > filesystem image, not an in-kernel-structures fs like ramfs), and map
> > it directly from the kernel image (it would have to be
In article <[EMAIL PROTECTED]> you wrote:
>> Would it be possible to use a cramfs image in vmlinux (i.e. real
>> filesystem image, not an in-kernel-structures fs like ramfs), and map
>> it directly from the kernel image (it would have to be suitably aligned,
>> of course)?
> Yes that would work,
i thought it would be nice to finally hear something good about the OOM
killer.
i am testing Evolution (Ximian's GNOME emailer/groupware app), and the
latest Evolution cvs-snapshot went crazy when trying to copy a mail
folder. my load averaged spiked, swap filled, and then i ran out of
memory.
Mike Touloumtzis wrote:
> > > Doesn't the approach "treat a chunk of data built into bzImage as
> > > populated ramfs" look cleaner? No need to fiddle with tar format,
> > > no copying data from place to place.
> >
> > So tell me, how do you populate ramfs without a format which tells you
> >
Jamie Lokier writes:
> (tar has a silly pad-to-multiple-of-512-byte per file rule, which is
> inappropriate for this).
If you remember that 'tar' means "tape archiver", and that at the time
it was written the standard tape block size was 512 bytes, the rule
isn't silly at all, although it may
On Sat, 7 Jul 2001, Alan Cox wrote:
> > > Its certainly misleading. I got Jeff to try making oom return
> > > 4999 out of 5000 times regardless.
> >
> > In that case, he _is_ OOM. ;)
>
> Hardly
>
> > 1) (almost) no free memory
> > 2) no free swap
> > 3) very little pagecache + buffer cache
>
>
> > Its certainly misleading. I got Jeff to try making oom return
> > 4999 out of 5000 times regardless.
>
> In that case, he _is_ OOM. ;)
Hardly
> 1) (almost) no free memory
> 2) no free swap
> 3) very little pagecache + buffer cache
Large amounts of cache, which went away when the OOM code
On Sat, Jul 07, 2001 at 07:34:38AM -0400, Jeff Garzik wrote:
> Eugene Crosser wrote:
> >
> > Doesn't the approach "treat a chunk of data built into bzImage as
> > populated ramfs" look cleaner? No need to fiddle with tar format,
> > no copying data from place to place.
>
> So tell me, how do
> I was running 2.4.6-stable in SMP mode on a dual P3-1GHz machine (VIA 694D
> Chipset / MSI-6321 M/B + ) and the following message popped up after which
> the system hardlocked (no SysRQ input). What does this message mean?
>
> CPU 1: Machine Check Exception: 0004
> Bank 1:
Rik van Riel wrote:
>
> On Sat, 7 Jul 2001, Alan Cox wrote:
>
> > > instead. That way the vmstat output might be more useful, although vmstat
> > > obviously won't know about the new "SwapCache:" field..
> > >
> > > Can you try that, and see if something else stands out once the misleading
> >
Daniel Phillips wrote:
> > Reading a tarball is the distillation of what you describe into
> > efficient form :)
>
> /me downloads tar file definition
>
> Um, gnu tar or posix tar? or some new, improved tar?
I suggest cpio, which is more compact and in some ways more standard.
(tar has a silly
> But neutering the OOM killer like Alan suggested may be a rather valid
> approach anyway. Delaying the killing sounds valid: if we're truly
> livelocked on the VM, we'll be calling down to the OOM killer so much that
> it's probably quite valid to say "only return 1 after X iterations".
Its
On Sat, 7 Jul 2001, Alan Cox wrote:
> > instead. That way the vmstat output might be more useful, although vmstat
> > obviously won't know about the new "SwapCache:" field..
> >
> > Can you try that, and see if something else stands out once the misleading
> > accounting is taken care of?
>
>
> instead. That way the vmstat output might be more useful, although vmstat
> obviously won't know about the new "SwapCache:" field..
>
> Can you try that, and see if something else stands out once the misleading
> accounting is taken care of?
Its certainly misleading. I got Jeff to try making
depmod: *** Unresolved symbols in
/lib/modules/2.4.6-ac2/kernel/drivers/net/dl2k.o
depmod: __ucmpdi2
-
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
kernels:
Linux pepsi 2.4.6-pre1-packet #1 SMP Tue Jun 12 02:12:32 EDT 2001 i686
Linux eax 2.2.20pre6 #1 Wed Jun 27 10:39:14 EST 2001 i586
I have a program which does :
flags = MSG_WAITALL;
rawsock = socket(PF_INET,SOCK_RAW,IPPROTO_TCP);
bytesread =
Followup to: <[EMAIL PROTECTED]>
By author:"Vibol Hou" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Hi,
>
> I was running 2.4.6-stable in SMP mode on a dual P3-1GHz machine (VIA 694D
> Chipset / MSI-6321 M/B + ) and the following message popped up after which
> the system
On Sat, 7 Jul 2001, Jim Roland wrote:
> but it's possible that the kernel is making a BIOS call,
Not really ...
Rik
--
Executive summary of a recent Microsoft press release:
"we are concerned about the GNU General Public License (GPL)"
http://www.surriel.com/
- Original Message -
From: "M.H.VanLeeuwen" <[EMAIL PROTECTED]>
To: "Jim Roland" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 07, 2001 8:47 AM
Subject: Re: Does kernel require IDE enabled in BIOS to access HD, FS
errors?
> Jim,
>
> Thanks for the info, comments
Hi,
I was running 2.4.6-stable in SMP mode on a dual P3-1GHz machine (VIA 694D
Chipset / MSI-6321 M/B + ) and the following message popped up after which
the system hardlocked (no SysRQ input). What does this message mean?
CPU 1: Machine Check Exception: 0004
Bank 1:
Just to follow up to myself, after futher testing, it looks like it's an
SMP-related problem. I'm not yet sure if it's an SMP-Via chipset
problem or just an SMP problem. I've heard from two people with this
same problem. I think one of them has a Via chipset and I'm not sure
about the other
My modems (Courier 28.8 external, Actiontec PCI call waiting non-winmodem)
connect to the Internet fine with 2.4.0, and broke around 2.4.1. What
happens is they dial out, make those sounds, and just as they seem to be
about to connect, they disconnect. I'm pretty sure both kernels are
configured
On Sat, 7 Jul 2001, Linus Torvalds wrote:
> In fact, I do not see any part of the whole path that sets the
> page age at all, so we're basically using a completely
> uninitialized field here (it's been initialized way back when
> the page was allocated, but because it hasn't been part of the
>
On Sat, 7 Jul 2001, Rik van Riel wrote:
>
> Not at all. Note that try_to_swap_out() will happily
> create swap cache pages with a very high page->age,
> pages which are in absolutely no danger of being
> evicted from memory...
That seems to be a bug in "add_to_swap_cache()".
In fact, I do not
Hi,
maybe we'll want to end the confusion and split the cached
and swap-cached statistics ...
Rik
--
Executive summary of a recent Microsoft press release:
"we are concerned about the GNU General Public License (GPL)"
http://www.surriel.com/
http://www.conectiva.com/
On Sat, 7 Jul 2001, Paul Mackerras wrote:
>
> The patch below does this (and makes a similar correction for I/O
> space). With this patch applied, the pcmcia stuff works fine on my
> powerbook, and I end up with something like this in /proc/iomem:
This is wrong.
The reason it currently uses
On Sat, 7 Jul 2001, Jeff Garzik wrote:
> Sigh. since I am a VM ignoramus I doubt my opinion matters much
> at all here... but it would be nice if oddball configurations
> like 384MB with 50MB swap could be supported.
It would be fun if we had 48 hours in a day, too ;)
This particular thing
On Fri, 6 Jul 2001, Jeff Garzik wrote:
> Rik van Riel wrote:
> > + cache_mem = atomic_read(_cache_size);
> > + cache_mem += atomic_read(_pages);
> > + cache_mem -= swapper_space.nrpages;
> > + limit = (page_cache.min_percent + buffer_mem.min_percent);
>
> Don't you need
Linus Torvalds wrote:
>
> On Sat, 7 Jul 2001, Jeff Garzik wrote:
> > Linus Torvalds wrote:
> > >
> > > Now, the fact that the system appears unusable does obviously mean that
> > > something is wrong. But you're barking up the wrong tree.
> >
> > Two more additional data points,
> >
> > 1)
On Sat, 7 Jul 2001, Jeff Garzik wrote:
> 2) I agree that 200MB into swap and 200MB into cache isn't bad
> per se, but when it triggers the OOM killer it is bad.
Please read my patch for the OOM killer. It substracts the
swap cache from the cache figure you quote and ONLY goes
into oom_kill() if
On Sat, 7 Jul 2001, Jeff Garzik wrote:
> Linus Torvalds wrote:
> >
> > Now, the fact that the system appears unusable does obviously mean that
> > something is wrong. But you're barking up the wrong tree.
>
> Two more additional data points,
>
> 1) partially kernel-unrelated. MDK's "make" macro
Linus Torvalds wrote:
>
> On Sat, 7 Jul 2001, Jeff Garzik wrote:
> >
> > When building gcc-2.96 RPM using gcc-2.96 under kernel 2.4.7 on alpha,
> > the system goes --deeply-- into swap. Not pretty at all. The system
> > will be 200MB+ into swap, with 200MB+ in cache! I presume this affects
>
On Sat, 7 Jul 2001, Jeff Garzik wrote:
>
> When building gcc-2.96 RPM using gcc-2.96 under kernel 2.4.7 on alpha,
> the system goes --deeply-- into swap. Not pretty at all. The system
> will be 200MB+ into swap, with 200MB+ in cache! I presume this affects
> 2.4.7-release also.
Note that
In article <[EMAIL PROTECTED]> you wrote:
> Since you can make any file into a block device using loop,
> is there any value to supporting swap files in 2.5?
> swap files seem like a special case that is no longer necessary...
loop is always tricky re near-OOM deadlocks. It'll survive now, by
On Saturday 07 July 2001 15:50, Jeff Garzik wrote:
> Eugene Crosser wrote:
> > In article
> > <[EMAIL PROTECTED]>,
> >
> > Alexander Viro <[EMAIL PROTECTED]> writes:
> > >> Doesn't the approach "treat a chunk of data built into bzImage
> > >> as populated ramfs" look cleaner? No need to
On Thu, Jul 05, 2001 at 09:49:08PM -0400, Michael Gold wrote:
> In kernel 2.4.4, a change was made to gamecon.c that causes problems
> with Super Nintendo controllers. The directional pad no longer works
> correctly - only the up and left directions work. The following patch
> fixes the problem
Diff between 2.4.7pre2aa1 and 2.4.7pre3aa1:
-
Only in 2.4.7pre2aa1: 00_3c59x-zerocopy-1
Only in 2.4.7pre3aa1: 00_3c59x-zerocopy-2
Right fix for enabling zerocopy on highmem kernels.
(nice to have)
Only in 2.4.7pre3aa1:
On Sat, Jul 07, 2001 at 06:30:33PM +0400, Oleg Drokin wrote:
> Hmm
> (examining Makefile...)
> I see. So there cannot be usual targets before including Rules.make,
> and my copy of the tree have these. And if I move them after inclusion,
> everything builds just fine.
> Perhaps it should be
Recompile your VTUND daemon with the new kernel headers (and also updated to
2.5 vtund, it has some small patches) and you will be fine.
- Original Message -
From: "Ryan Mack" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 07, 2001 1:02 AM
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
2.4.6-ac2
o Merge Linus 2.4.7pre1
o Drop out various bits that are 2.5 stuff
AS/400 etc
o Merge Linus
> I have Casio Fiva 102 which is a mini notebook based on Cyrix MediaGX
> (clone) chipset. 2.4.5 runs like a charm, but 2.4.6, immediately
> after starting, displays this:
2.4.7pre3 should fix that one
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
I have Casio Fiva 102 which is a mini notebook based on Cyrix MediaGX
(clone) chipset. 2.4.5 runs like a charm, but 2.4.6, immediately
after starting, displays this:
zone(0): 4096 pages.
zone(1): 11648 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=linux ro root=304 sb=0x220,5,1,5
Hi,
Every once in a while, my system gets unbelievable slow. So slow that I
almost can't do anything anymore. This happens only once in a few months.
I think it has to do with sound, because when I start using sound, it happens.
"top" gives me then about 90% idle time, and "top" is using this
> And i have a NCR 3525 with MCA bus and 8 processors and 512MB RAM , i
> tried Suse 6.4 and Red Hat 7.1 , but nome detected my MCA bus , the 8
> processors and more than 64MB ... i tried kernel parameter mem=512m ,
> but no results... only 64MB i recompiled the kernel (2.4.2) with
> MCA=y
Since you can make any file into a block device using loop,
is there any value to supporting swap files in 2.5?
swap files seem like a special case that is no longer necessary...
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024| can cause malaise in
Kernel 2.4.7-pre3 on alpha.
The initial phase of an RPM build is unpacking a tarball and applying
patches, which is a bunch of writes followed by a update of read/write
updates. A lot of write activity, basically. RPM build is running at
normal priority as a normal user.
In another xterm,
hello,
I have a serious problem since 2.4.5 kernel, the timer go crazy (about
10 time normal speed)
I can't login because the 60 secondes timeout get only a few second in
real life.
Same thing about harddrive timeout error.
The motherboard is a dual pentium-mmx 200
Oleg Drokin wrote:
> arm-linux-ld -p -X -T arch/arm/vmlinux.lds arch/arm/kernel/head-armv.o
>arch/arm/kernel/init_task.o init/main.o init/version.o \
> --start-group \
> arch/arm/kernel/kernel.o arch/arm/mm/mm.o arch/arm/mach-sa1100/sa1100.o
> kernel/kernel.o mm/mm.o fs/fs.o
Hello!
>> Seems like its something that appeared between 2.4.5 and 2.4.6. Anyone
>> know the correct fix, other than reversing the change?
KG> It should be fine.
It is not.
>> Since all net cards are modules, object list for pcmcia_net.o is empty and
>> kernel can't be linked.
KG> Could you
Hello!
>> Seems like its something that appeared between 2.4.5 and 2.4.6. Anyone
>> know the correct fix, other than reversing the change?
AC> I build with all pcmcia network drivers modular on my test builds, what
AC> am I missing here ?
Well. As you might have noticed - this is build for
this is a test
-
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/
Jeff Garzik wrote:
>
> Oh this is a fun one :)
>
> When building gcc-2.96 RPM using gcc-2.96 under kernel 2.4.7 on alpha,
> the system goes --deeply-- into swap. Not pretty at all. The system
> will be 200MB+ into swap, with 200MB+ in cache! I presume this affects
> 2.4.7-release also.
>
>
[EMAIL PROTECTED] wrote:
>
> In article <[EMAIL PROTECTED]> you
>wrote:
> > Dear Kernel People,
> > A friend of mine has a new PC with an ASUS CUV4X-D motherboard
> > and dual 1GHZ PIII's.
...
> For several people the following works:
> 1) Upgrade to the latest bios
> 2) Change the "MPS"
Eugene Crosser wrote:
>
> In article <[EMAIL PROTECTED]>,
> Alexander Viro <[EMAIL PROTECTED]> writes:
>
> >> Doesn't the approach "treat a chunk of data built into bzImage as
> >> populated ramfs" look cleaner? No need to fiddle with tar format,
> >> no copying data from place to
Oh this is a fun one :)
When building gcc-2.96 RPM using gcc-2.96 under kernel 2.4.7 on alpha,
the system goes --deeply-- into swap. Not pretty at all. The system
will be 200MB+ into swap, with 200MB+ in cache! I presume this affects
2.4.7-release also.
System has 256MB of swap, and 384MB of
In article <[EMAIL PROTECTED]>,
Alexander Viro <[EMAIL PROTECTED]> writes:
>> Doesn't the approach "treat a chunk of data built into bzImage as
>> populated ramfs" look cleaner? No need to fiddle with tar format,
>> no copying data from place to place.
>
> What the hell _is_ "populated
Jim,
Thanks for the info, comments interleaved below
Thanks
Martin
Jim Roland wrote:
>
> Activating an IDE drive in an older BIOS (newer ones have a SCSI option in
> the "A/C/CDROM" options) will always force an IDE drive boot with older
> BIOSes. Older BIOSes are written to stop looking for
On Sat, 7 Jul 2001, Russell King wrote:
> Seems like its something that appeared between 2.4.5 and 2.4.6. Anyone
> know the correct fix, other than reversing the change?
It should be fine.
> Since all net cards are modules, object list for pcmcia_net.o is empty and
> kernel can't be linked.
hi,
> did you boot with ip=bootp or ip=dhcp or ip=rarp?
no, i didn't - it seems to be that this is required for kernels >2.2.17.
-> now it works - thanks a lot!
greets,
albert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Activating an IDE drive in an older BIOS (newer ones have a SCSI option in
the "A/C/CDROM" options) will always force an IDE drive boot with older
BIOSes. Older BIOSes are written to stop looking for a boot device once it
has found one, and it's own IDE is where it says "Ok, I have boot
Albert Weichselbraun wrote:
>
> On 2001-07-07 at 08:26:49 -0400, Jeff Garzik wrote:
> > Can you try 2.4.6 please?
> done.
> - sorry, but 2.4.6 doesn't work either.
>
>
> ...
> 8139too Fast Ethernet driver 0.9.18-pre4
> PCI: Found IRQ 10 for device 00:09.0
> eth0: RealTek RTL8139 Fast Ethernet
On 2001-07-07 at 08:26:49 -0400, Jeff Garzik wrote:
> Can you try 2.4.6 please?
done.
- sorry, but 2.4.6 doesn't work either.
...
8139too Fast Ethernet driver 0.9.18-pre4
PCI: Found IRQ 10 for device 00:09.0
eth0: RealTek RTL8139 Fast Ethernet at 0xe080, 00:00:21:fa:20:ce, IRQ 10
NET4:
hi,
i'm experiencing problems using dhcp-autoconfiguration with rtl8139-network
cards and kernels >2.2.17.
- it seems to be, that the kernel tries to mount the nfs-root-directory,
before fetching the nodes-ip-address via dhcp (the logs from dhcpd
indicate, that the node doesn't even try to
> I'm interested if there is an explanation of the MK7 specific code in mmx.c and
> whether that could really be the source of the problem. I would like to get
> to the bottom of this.
As far as we can tell the problem is 'using a VIA chipset'. The code itself
is a fast copying loop using
> Seems like its something that appeared between 2.4.5 and 2.4.6. Anyone
> know the correct fix, other than reversing the change?
I build with all pcmcia network drivers modular on my test builds, what
am I missing here ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> Can anyone let me know the steps for making/submitting
> a linux kernel patch ? What is the difference between
man diff
Use the diff -u options
> an unofficial patch and an official patch ?
I guess it depends who made it, who likes it and who you trust 8)
-
To unsubscribe from this list:
>A friend of mine has a new PC with an ASUS CUV4X-D motherboard
> and dual 1GHZ PIII's. We have installed RedHat 7.1. The original
> RedHat SMP kernel (2.4.2) did not boot; it froze with some complaints
You need at least bios rev 1007 I believe
-
To unsubscribe from this list: send the
> I am wondering who maintains drivers/ide/sl82c105.c, and who sent in
> the recent changes to it. We now have, at around line 278, this code:
>
> unsigned int pci_init_sl82c105(struct pci_dev *dev, const char *msg)
> {
> return ide_special_settings(dev, msg);
> }
>
> The call to
Paul Mackerras wrote:
> In drivers/pcmcia/rsrc_mgr.c, there is code that check whether a given
> range of PCI memory addresses are available for the pcmcia code to
> use. This code uses a macro, check_mem_resource(), to check whether a
> particular region is available, defined like this:
>
>
In drivers/pcmcia/rsrc_mgr.c, there is code that check whether a given
range of PCI memory addresses are available for the pcmcia code to
use. This code uses a macro, check_mem_resource(), to check whether a
particular region is available, defined like this:
#define check_mem_resource(b,n)
On Fri, Jul 06, 2001 at 11:28:35PM -0700, Satish Kumar wrote:
> Can anyone let me know the steps for making/submitting
> a linux kernel patch ? What is the difference between
> an unofficial patch and an official patch ?
See Documentation/SubmittingPatches in your kernel tree.
Erik
--
J.A.K.
Eugene Crosser wrote:
>
> In article <[EMAIL PROTECTED]>,
> Linus Torvalds <[EMAIL PROTECTED]> writes:
>
> > I don't like the current initrd very much myself, I have to admit. I'm not
> > going to accept a "you have to have a ramdisk" approach - I think the
> > ramdisks are really
On 7 Jul 2001, Eugene Crosser wrote:
> Doesn't the approach "treat a chunk of data built into bzImage as
> populated ramfs" look cleaner? No need to fiddle with tar format,
> no copying data from place to place.
What the hell _is_ "populated ramfs"? The thing doesn't live in array
of blocks.
On Tue, 3 Jul 2001, David Howells wrote:
> > The question I think being ignored here is. Why not leave things as is. The
> > multiple bus stuff is a port specific detail hidden behind readb() and
> > friends.
>
> This isn't so much for the case where the address generation is done by a
> simple
On Tue, 3 Jul 2001, David Howells wrote:
> * It should make drivers easier to write: they don't have to worry about
>whether a resource refers to memory or to I/O or to something more exotic.
>
> * It makes some drivers more flexible. For example, the ne2k-pci driver has
>to be set at
>I think what we are seeing is XBoot rather than yaboot and we tried just
>about all conceivable "kernel options", as exposed by Xboot. When Xboot
>comes up it shows a ramdisk_size=8192 as the only default parameter.
>Rapidly growing to hate the non-intuitive nature of the MAC OS we are
>not
In article <[EMAIL PROTECTED]>,
Linus Torvalds <[EMAIL PROTECTED]> writes:
> I don't like the current initrd very much myself, I have to admit. I'm not
> going to accept a "you have to have a ramdisk" approach - I think the
> ramdisks are really broken.
>
> But I've seen a "populate
On Sat, Jul 07 2001, gopi krishna wrote:
> Why do we need a dummy req for plugging.
> As i understood only thing plugging does is to, on arrival of new req if
> the dev queue is empty, puts a dummy req on the queue, and schedules the
> unplug routine on tq_disk, which on being scheduled calls the
Henry wrote:
>
> >
> > I wonder why it only affects you. Is the drive which holds
> > your swap partition running in PIO mode? `hdparm' will tell
> > you. If it is, then that could easily cause the page to come
> > unlocked before brw_page() has finished touching the buffer
> > ring. Then
>
> I wonder why it only affects you. Is the drive which holds
> your swap partition running in PIO mode? `hdparm' will tell
> you. If it is, then that could easily cause the page to come
> unlocked before brw_page() has finished touching the buffer
> ring. Then all it takes is a parallel
Seems like its something that appeared between 2.4.5 and 2.4.6. Anyone
know the correct fix, other than reversing the change?
- Forwarded message from Nicolas Pitre <[EMAIL PROTECTED]> -
-- Forwarded message --
Date: Fri, 6 Jul 2001 12:17:54 +0400
From: Oleg Drokin
In article <[EMAIL PROTECTED]> you wrote:
> Dear Kernel People,
> A friend of mine has a new PC with an ASUS CUV4X-D motherboard
> and dual 1GHZ PIII's. We have installed RedHat 7.1. The original
> RedHat SMP kernel (2.4.2) did not boot; it froze with some complaints
> about APIC. The backup
On Sat, Jul 07, 2001 at 09:10:46AM -0800, Richard Chan wrote:
> Athlon oops saga continues - I consistently get Athlon kernels oopsing
> during the boot up process either in rc.sysinit or loading of usb modules
> (this is a RedHat system 7.1). These kernels can boot to a shell init=/bin/sh
> but
Henry wrote:
>
> ...
> So far, so good. There has not been a single oops on the two principle
> servers I patched.
>
> uptime1:8:04am up 18:22, 1 user, load average: 0.09, 0.15, 0.11
> uptime2:8:04am up 18:25, 1 user, load average: 0.15, 0.20, 0.15
OK,
I recently upgraded a server running vtund 2.4 (4/18/01) to stock 2.4.6
kernel. It seems the changes to the tun driver have broken vtund. Now my
syslog gets filled with the following messages when a client attempts to
connect:
Jul 5 10:15:53 mackman vtund[4011]: Session
1 - 100 of 206 matches
Mail list logo
