Alan -
Based on your suggestion, I looked again, and found that even though the kernel
sets VRA, the bit is lost when the driver unnecessarily resets the CODEC. The
patch below removes the unnecessary resetting of the CODEC. Nothing seems to be
lost by removing the resetting, and the driver in
On Wed, 3 Jan 2001 04:15:16 +0100,
"J . A . Magallon" <[EMAIL PROTECTED]> wrote:
>I have seen that the CCFOUND stuff has flown away. I have read it
>breaks somthing, and the CROSS_COMPILE in alphas and m68k.
>Perhaps this way could be better : ??
>..
>include arch/$(ARCH)/Makefile
>
>AS :=$(AS)
On Tue, 2 Jan 2001, Linus Torvalds wrote:
> On Wed, 3 Jan 2001, Mike Galbraith wrote:
> >
> > No difference (except more context switching as expected)
>
> What about the current prerelese patch in testing? It doesn't switch to
> bdflush at all, but instead does the buffer cleaning by hand.
On Tue, 2 Jan 2001 19:12:49 +0100,
Matthias Andree <[EMAIL PROTECTED]> wrote:
>There's a problem. depmod should not try to do anything besides giving
>its version when --version is used, should it?
Historical accident. I want to clean that up but it breaks existing
behaviour; somewhere,
On Wed, 3 Jan 2001, Mike Galbraith wrote:
>
> No difference (except more context switching as expected)
What about the current prerelese patch in testing? It doesn't switch to
bdflush at all, but instead does the buffer cleaning by hand.
Linus
-
To unsubscribe from this
On Wed, 3 Jan 2001, Roger Larsson wrote:
> Hi,
>
> I have played around with this code previously.
> This is my current understanding.
> [yield problem?]
Hmm.. this ~could be. I once dove into the VM waters (me=stone)
and changed __alloc_pages() to only yield instead of scheduling.
The
On Tue, 2 Jan 2001, Linus Torvalds wrote:
> On Tue, 2 Jan 2001, Mike Galbraith wrote:
> >
> > Yes and no. I've seen nasty stalls for quite a while now. (I think
> > that there is a wakeup problem lurking)
> >
> > I found the change which triggers my horrid stalls. Nobody is going
> > to
On Wed, 3 Jan 2001, Daniel Phillips wrote:
> Could you try this patch just to see what happens? It uses semaphores
> for the bdflush synchronization instead of banging directly on the task
> wait queues. It's supposed to be a drop-in replacement for the bdflush
> wakeup/waitfor mechanism, but
"Jorge L. deLyra" wrote:
>
> Hi,
>
> I had a K7 booting kernel 2.2.17 OK and mounting an NFS root but that
> doesn't work anymore if I use the 2.2.18 kernel.
>
> Both kernels were compiled with the same configs. I'm also using the same
> lilo and NBI configs, both used to work. In either case
Here's a set of patches that fix compile warnings using gcc 2.97. The first
patch is purely a syntactical change (mainly removing default: statements that
do nothing), the second is a change in code structure that "looks" correct but
was brought on by the same type of warning where the case label
On Saturday December 30, [EMAIL PROTECTED] wrote:
>
> > On Friday December 29, [EMAIL PROTECTED] wrote:
> > > Hi -- could you please CC me if you reply to this mail.
> > >
> > > A: /exports/A - Redhat 7.0
> > > B1/B2: mount /exports/A on /export/A from A
Hi,
Linus Torvalds wrote:
>
> The strange thing is that 0x0100 value, which almost certainly should
> just be NULL. A one-bit error.
>
> Now, I assume this machine has been historically stable, with no history
> of memory corruption problems.. It's entirely possible (and likely) that
> the
On Wed, 3 Jan 2001, Udo A. Steinberg wrote:
>
> Hi Linus et. all
>
> While under massive disk and cpu load, 2.4.0-prerelease produced
> the following oops (decode see below)
> Unable to handle kernel paging request at virtual address 0114
> Code; c01419cc<=
>0: 8b 40 14
On Wed, 3 Jan 2001, Udo A. Steinberg wrote:
>
> While under massive disk and cpu load, 2.4.0-prerelease produced
> the following oops (decode see below)
Hmm.. If I'm not mistaken, this is in dentry_iput() (inline function
called by prune_one_dentry(), which is _also_ an inline function, which
Hi Linus et. all
While under massive disk and cpu load, 2.4.0-prerelease produced
the following oops (decode see below)
Keith, I've read the FAQ about having been bitten by Makefile bugs
with certain symbols and such, yet I still get these symbol warnings
even after a mrproper rebuild. Any
On Tue, 2 Jan 2001, Andreas Dilger wrote:
> This predates me by a while, but I suspect that it is done this way on
> the assumption it is easier to seek forward on the disk while reading
> a file rather than seeking backwards. Also, since with new inodes the
> goal is initially the first
On 2001.01.03 Alan Cox wrote:
> 2.2.19pre5
> o Fix dumpable stuff (Wolfgang Walter)
> o PPA driver update (Tim Waugh)
> o ARM updates (Russell - ptrace.c errored please (Russell King)
> resolve)
> o Fix NFS
Hi Neil,
I thought I'd seen this same bug on 2.4.0-test12 after I applied your patch
but didn't follow up until now. sorry.
Anyway, with 2.4.0-prerelease and an updated loop.c.patch, below the ksymoops
output (your patch updated to 2.4.0-prerelease), I got the following BUG reports.
So it
2.2.19pre5
o Fix dumpable stuff (Wolfgang Walter)
o PPA driver update (Tim Waugh)
o ARM updates (Russell - ptrace.c errored please (Russell King)
resolve)
o Fix NFS data alignment on ARM
Hi,
I have played around with this code previously.
This is my current understanding.
[yield problem?]
On Tuesday 02 January 2001 09:27, Mike Galbraith wrote:
> Hi,
>
> I am seeing (what I believe is;) severe process CPU starvation in
> 2.4.0-prerelease. At first, I attributed it to semaphore
Here's my patch again since Alan didn't get it.
diff -urN linux/drivers/i2c/i2c-pcf8584.h rb/drivers/i2c/i2c-pcf8584.h
--- linux/drivers/i2c/i2c-pcf8584.h Fri Jan 28 22:36:23 2000
+++ rb/drivers/i2c/i2c-pcf8584.hTue Jan 2 16:47:36 2001
@@ -75,4 +75,4 @@
#define I2C_PCF_INTREG
I originally sent this message to Andrea Archelangi, but he felt I
should also send it here. 2.2.19pre3 is great!
Note that I'm not subscribed to the list - please replies to me and the
list if you would? Thanks :)
You may remember me from an earlier e-mail asking where to find
the VM
On Tue, Jan 02, 2001 at 04:15:02PM -0800, Andre Hedrick wrote:
> However each key is to broadcasts its identity for the authorized
> host/application. This every license that uses CPRM is trackable. Since
> the method is exotic enough and you can only get the matrix pillars from
> the LC4
Oh, and adding that option DID fix the lost interrupt problems
(ide1=0x170,0x376,15), so yeah, that fix fixed it.
Thanks for your help. Maybe it should become a config option to enable
that (CONFIG_BLK_DEV_MESSED_UP_VIA_CHIPSET_FIX).
--
| Evan Thompson| ICQ:2233067 |
This oops occurred just a few minutes ago under no particular load.
There were actually two oopsen, but I've included only the first as I've
heard that successive oops really aren't helpful. Nonetheless, if
anyone's interested in seeing it, I have it captured.
These oops were processed
On Tue, Jan 02, 2001 at 10:56:27AM -0800, Linus Torvalds wrote:
> Anyway, I suspect that the "fe"/"ff" values are specified by MS (no way to
> know, as the docs are obviously NDA'd), which means that it would be
> interesting to hear whether the problem is fixed by something like this:
>
> In
Here is a patch that removes more compile warnings from 2.4.0- prerelease. I left out files that have been fixed by Alan or myself in the ac kernels. I'll add more options to my config tomorrow to try to find more of these warnings.
Rich
diff -urN linux/drivers/i2c/i2c-pcf8584.h
On Tue, 2 Jan 2001, Alan Cox wrote:
> > > i2o_block.c:595: warning: #warning "RACE"
> > this is most likely a bad thing, yes.
>
> Yeah its to remind me to fix a small race
If preferred the alternative approach to this:
if (!current->lock_depth)
BUG();
in sleep_on().
hi,
I am using matroxfb with a MGA200 card,
but I find the bootlogo quite annoying.
Is there an easy way to remove it ?
thanks - Jens Nestel -< [EMAIL PROTECTED] >-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please
On Tue, 2 Jan 2001, Keith Owens wrote:
> Some sparc users have a slightly older version of gcc, built shortly
> before 'weak' support was added, which required those symbols to be
> defined. Dave Miller thought the compiler problem was widespread
> enough to justify changing the source to suit
Linus,
In 2.4.0-prerelease, you've changed block_truncate_page() to call
__mark_buffer_dirty instead of mark_buffer_dirty before unlocking the
page, so there is no more possibility of it blocking in bdflush while
holding the page locked, which is good.
But now we don't do balancing anymore
Hi Jes=FAs?=!
On Sat, 30 Dec 2000, Jes=FAs?= Carrete Montaña wrote:
>
> I receive this message very often in console, in every situation: when
> I'm coding and when I'm playing tetrinet. It's quite annoying, mostly
> because it fills my screen of garbage (I'll have to buy a new CTRL and
> L
> "Hakan" == Hakan Lennestal <[EMAIL PROTECTED]> writes:
Hakan> Yes, the problem is the hpt366 (or the sw), not the IBM drives.
Hakan> The IBM drives seem to work well with udma3 on the hpt but not
Hakan> with udma4 or higher.
Is this specific to the 366? My DTLAs on a 370 are working like
On Tue, 2 Jan 2001, Gerold Jury wrote (in a private message, sorry):
> The machine is single CPU no SMP.
> It hangs with or without X when i hangup the ippp0 interface.
> One of the scripts that run when the line is hung up may do a ifconfig
> ippp0 down afterwards which could be the actual
(I'm keeping the CC to l-k, but let's move this to the acpilist, ok?)
acpi_get_battery_info is brand new code. It worked on my box, though ;-) can
you help me narrow down which of the assignments near the end of the
function is to blame? (via printk, I guess)
If you could post your DSDT that
Scott Conway wrote:
>
> Hi, I'm having problems getting anything from
> 2.4.0-test12 onward to get past the IDE detectin phase
> of bootup, and not even 2.4.0-prerelease will work,
> either. At the bottom of this is the output of dmesg,
> on my current kernel (2.4.0-test11), with the spot
>
I will explain later...
However each key is to broadcasts its identity for the authorized
host/application. This every license that uses CPRM is trackable. Since
the method is exotic enough and you can only get the matrix pillars from
the LC4 people, crack will be tough. There is a 1Meg
On 2001.01.02 Giacomo A. Catenazzi wrote:
> Hello!
>
> When working in cpu autoconfiguration I found some problems:
>
> I have to identify this processor:
> Vendor: Intel
> Family: 6
> Model: 8
> Is it a "Pentium III (Coppermine)" (setup.c:1709)
> or a "Celeron (Coppermine)"
On Tue, 2 Jan 2001, David Ford wrote:
> Andre Hedrick wrote:
>
> > On Tue, 2 Jan 2001, dep wrote:
> >
> > > On Tuesday 02 January 2001 06:00 am, Andre Hedrick wrote:
> > > | Doing final tests but it may have come to and end and that deadlock
> > > | may be gone in a few hours after some sleep.
Andre Hedrick wrote:
> On Tue, 2 Jan 2001, dep wrote:
>
> > On Tuesday 02 January 2001 06:00 am, Andre Hedrick wrote:
> > | Doing final tests but it may have come to and end and that deadlock
> > | may be gone in a few hours after some sleep.
How 'bout the lockup on boot at partition checking?
On Tue, 2 Jan 2001, Hakan Lennestal wrote:
> > The IBM DTLA drives aren't in the hpt366 bad_ata66_4 list still.
>
> I second this !
> Until the hpt-problem is solved (if it ever will be)
> we really need the IBM DTLA drives in the bad-list.
> This configuration (IBM DTLA disks on hpt3*
Andre Hedrick wrote:
>
> On Tue, 2 Jan 2001, Rob Landley wrote:
>
> > And we all remember how the pirates got around this, don't we? The easy
> > way: crack the program.
>
> Nope...it is embedded to the vender portion of the media.
My point was that using this kind of thing to protect
On Tue, 2 Jan 2001, Giacomo A. Catenazzi wrote:
> When working in cpu autoconfiguration I found some problems:
> What is the difference between MWINCHIP2 and MWINCHIP3D?
> I don't find differences in the sources
MWINCHIP3D is for the Winchip-2A and above, which have 3dnow!
instructions. Until
It works for me.
With and without the divert module loaded.
Thanks a lot
Gerold
Kai Germaschewski wrote:
> I think I found it. Could everybody who was getting the crash on ISDN line
> hangup try if the following patch fixes the problem?
>
-
To unsubscribe from this list: send the line
Folks, there is a pretty strange detail of the allocation policy -
if cylinder group has no free blocks past the goal ext2 tries very hard to
avoid allocation in the beginning of the group. I.e. order looks so:
* goal
* goal .. (goal+63) & ~63
* goal .. end of
Mike Galbraith wrote:
>
> On Wed, 3 Jan 2001, Anton Blanchard wrote:
> >
> > > I am seeing (what I believe is;) severe process CPU starvation in
> > > 2.4.0-prerelease. At first, I attributed it to semaphore troubles
> > > as when I enable semaphore deadlock detection in IKD and set it to
> > >
On Tue, Jan 02 2001, Dan Hollis wrote:
> On Tue, 2 Jan 2001, Jens Axboe wrote:
> > On Tue, Jan 02 2001, Dan Hollis wrote:
> > > Also, using CDROM on hpt366 is recipe for disaster...
> > ATAPI in general actually, and as I understand it only with DMA.
>
> Nope I can blow it up with PIO also...
Linus Torvalds <[EMAIL PROTECTED]> writes:
> > [...] the drm modules have unresolved symbols:
>
> Does this fix it for you (do a "make clean" before re-building your tree)?
Yep, that works for a modular mga.o (although it also results in
drmlib.a being installed into /lib/modules, which makes
On Tue, 2 Jan 2001, Linus Torvalds wrote:
> Does the Maxtor and/or CDROM problems have anything to do with udma66? Ie
> if you can test, can you please check whether it's ok when they are added
> to the blacklists (or if udma66 is just disabled by default)?
Once I resend you the patches I have
On Tue, 2 Jan 2001, Jens Axboe wrote:
> On Tue, Jan 02 2001, Dan Hollis wrote:
> > Also, using CDROM on hpt366 is recipe for disaster...
> ATAPI in general actually, and as I understand it only with DMA.
Nope I can blow it up with PIO also...
-Dan
-
To unsubscribe from this list: send the line
On Tue, 2 Jan 2001, Linus Torvalds wrote:
> On Tue, 2 Jan 2001, Dan Hollis wrote:
> > Too bad Maxtor is still broken with hpt366...
> > Also, using CDROM on hpt366 is recipe for disaster...
> Does the Maxtor and/or CDROM problems have anything to do with udma66? Ie
> if you can test, can you
On Tue, 2 Jan 2001, Gerold Jury wrote:
> I have reversed the patches part by part, the only thing that makes a
> difference is the diversion services.
> The reason for this remains unknown for me.
I think I found it. Could everybody who was getting the crash on ISDN line
hangup try if the
On Tue, Jan 02 2001, Dan Hollis wrote:
> Also, using CDROM on hpt366 is recipe for disaster...
ATAPI in general actually, and as I understand it only with DMA.
--
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Tue, Jan 02 2001, Kernel Related Emails wrote:
> It appears that DVD calls have been broken in the new prerelease
> kernel. I have been trying to use a DVD application under prerelease that
> worked under test9 with no luck.
>
> Any ideas?
Eh very hard to say, can you say a bit more about
Included it in the rc.local file as you told me but it did not
work. I still had to go to "/dir1/drv" and do "su [password for
root]" and then type "./upload", exit. Maybe some little script that
can do this in the "bash_profile" or
I am not familiar with scripting...
This is a custom
On Tue, 2 Jan 2001, Rob Landley wrote:
> And we all remember how the pirates got around this, don't we? The easy
> way: crack the program.
Nope...it is embedded to the vender portion of the media.
> There's nothing new under the sun, and the "zero day warez" people never
> even broke stride
On Tue, 2 Jan 2001, Dan Hollis wrote:
> On Tue, 2 Jan 2001, David Woodhouse wrote:
> > It's a combination of chipset and drive that causes the problems. I've
> > been using ata66 with the same controller on a different drive
> > (FUJITSU MPE3136AT) for some time now, and it's been rock solid.
On Tue, 2 Jan 2001, David Woodhouse wrote:
> It's a combination of chipset and drive that causes the problems. I've
> been using ata66 with the same controller on a different drive
> (FUJITSU MPE3136AT) for some time now, and it's been rock solid. It's only
> the IBM DTLA drive that's been a
On Tue, 2 Jan 2001, Linus Torvalds wrote:
> So why are the IBM drives picked on? I thought this was a hpt366 problem,
> and possibly has only shown up with IBM drives so far.
>
> It sounds like the proper fix would be to not enable ata66 by default.
It's a combination of chipset and drive that
> Its probably very hard to defeat. It also in its current form means
> you can throw disk defragmenting tools out. Dead, gone. Welcome to
> the United Police State Of America.
Doesn't anybody remember the days of "dongle keys" on the Commodore 64?
Plug a special circuit into the joystick port
On Tue, 2 Jan 2001, Linus Torvalds wrote:
>
> Right now, the automatic balancing only hurts. The stuff that hasn't been
> converted is probably worse off doing balancing when they don't want to,
> than we would be to leave the balancing altogether.
>
> Which is why I don't like it.
Actually,
On Mon, Jan 01, 2001, Heitzso <[EMAIL PROTECTED]> wrote:
> Johannes, I apologize for not getting back to you earlier.
> Holidays, a changing kernel, and work, kept me away from
> the test.
No problem.
> DATA: s10sh 0.1.9 is a program used to access the USB
> bus to get to digital cameras and
>The UPX team owns all copyright in all of UPX and in each part of
> UPX. Therefore, the UPX team may choose which license(s), and has
> chosen two
...
> This permits using UPX to pack a non-GPL executable.
Stupid question time: isn't this what the LGPL was designed to do? The
Library GPL, so
Roman Zippel wrote:
>
> On Tue, 2 Jan 2001, David S. Miller wrote:
>
> >We really can't. We _only_ have load-and-zero. And it has to be
> >16-byte aligned. xchg() is just not something the CPU implements.
> >
> > Oh bugger... you do have real problems.
>
> For 2.5 we could move all
Andrea Arcangeli wrote:
> On Tue, Jan 02, 2001 at 12:09:32PM -0800, J Sloan wrote:
> > # vgscan
> > vgscan: error while loading shared libraries: vgscan: undefined symbol:
> > lvm_remove_recursive
>
> This looks like an userspace compilation/installation problem of the new lvm
> tools. Make sure
On Tue, 2 Jan 2001, Andrea Arcangeli wrote:
>
> > NOTE! I think that throttling writers is fine and good, but as it stands
> > now, the dirty buffer balancing will throttle anybody, not just the
> > writer. That's partly because of the 2.4.x mis-feature of doing the
>
> How can it throttle
> >> distribution? (hint: if it's redhat 7, don't bother).
> >
> > Bzzt, wrong. Red Hat 7 compiles the 2.4 tree beautifully
> > with gcc 2.96 as well. Please grow up.
>
> Huh? Original, bug fix, or both?
I've run kernels built with both with no problems.
-
To unsubscribe from this list: send
On Tue, Jan 02, 2001 at 12:09:32PM -0800, J Sloan wrote:
> # vgscan
> vgscan: error while loading shared libraries: vgscan: undefined symbol:
> lvm_remove_recursive
This looks like an userspace compilation/installation problem of the new lvm
tools. Make sure you removed the old (0.8*) shared
On Tue, Jan 02, 2001 at 08:46:26PM +0100, Giacomo A. Catenazzi wrote:
> When working in cpu autoconfiguration I found some problems:
>
> I have to identify this processor:
> Vendor: Intel
> Family: 6
> Model: 8
> Is it a "Pentium III (Coppermine)" (setup.c:1709)
> or a "Celeron
>> distribution? (hint: if it's redhat 7, don't bother).
>
> Bzzt, wrong. Red Hat 7 compiles the 2.4 tree beautifully
> with gcc 2.96 as well. Please grow up.
Huh? Original, bug fix, or both?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Followup to: <[EMAIL PROTECTED]>
By author:Richard Henderson <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Tue, Jan 02, 2001 at 03:12:37PM -0500, Ghadi Shayban wrote:
> > {standard input}: Assembler messages:
> > {standard input}:139: Error: bad register name `%%mm0'
>
> This
On Tue, Jan 02, 2001 at 01:02:30PM -0800, Linus Torvalds wrote:
>
>
> On Tue, 2 Jan 2001, Andrea Arcangeli wrote:
>
> > On Tue, Jan 02, 2001 at 11:02:41AM -0800, Linus Torvalds wrote:
> > > What does the system feel like if you just change the "sleep for bdflush"
> > > logic in
>
> On Sun, 31 Dec 2000, Linus Torvalds wrote:
>
> > Ok. I didn't make 2.4.0 in 2000. Tough. I tried, but we had some
> > last-minute stuff that needed fixing (ie the dirty page lists etc), and
> > the best I can do is make a prerelease.
>
> I just compiled that one into a 1032 kB kernel, and
Sorry for that stupid mistake.
The patches to the isdn part do not make a difference to the kernel hang
that i experienced lately.
When i reversed the patch for the mentioned files i checked the kernel
configuration and noticed that the "diversion services for isdn" where
on, a feature that i
> haven't finished this work yet. With this new work, however, the
> end-user will still load a single module (e.g., tdfx.o), just like now.
> (Loading a single kernel module is a significant win when dealing with
> end users: there is no possibility of version skew or of having two
> modules
Gregory McLean <[EMAIL PROTECTED]> writes:
> cat /proc/sys/kernel/shmall
> 0
That's your problem. Your limit for overall shm pages is zero. So you
cannot allocate any shm segments.
echo 200 > /proc/sys/kernel/shmall
and check /etc/sysctl.conf or wherever your system stores kernel
On Tue, 2 Jan 2001, Andreas Bombe wrote:
> You're then using the ieee1394.o module object which doesn't include the
> hardware and highlevel drivers. I've sent a patch to Linus already and
> cc'd the mailing list also.
!!! there were heaps of other (not related to ieee1394 stuff )
linking
On Tue 2 Jan 2001 08:32:45 +1100,
Keith Owens <[EMAIL PROTECTED]> wrote:
> On Mon, 1 Jan 2001 09:39:38 -0800 (PST),
> Linus Torvalds <[EMAIL PROTECTED]> wrote:
> >On 1 Jan 2001, Adam Sampson wrote:
> >>
> >> It appears to work (even with the reiserfs patch with the obvious
> >> Makefile
On Tue, 2 Jan 2001, Thorsten Kranzkowski wrote:
> On Tue, Jan 02, 2001 at 03:51:34AM +0100, Gerold Jury wrote:
> > The ISDN changes for the HISAX drivers
> > that came in since test12 have introduced a bug that causes a
> > AIEE-something and a complete kernel hang when i hangup the isdn line.
>
On Tue, Jan 02, 2001 at 03:56:54PM +0200, Elmer Joandi wrote:
>
> compiling everything builtin, (exept RCPCI, which does not compile)
>
> linking errors:
> drivers/ieee1394/ieee1394.a is not made, quick hack to use .o to see other
> errors.
You're then using the ieee1394.o module object which
On Tue, Jan 02, 2001 at 06:43:57AM +0100, Andreas Bombe wrote:
> Now that I've had the time to understand the new kernel makefile
> structure the patch Kai Germaschewski posted is indeed the correct fix
> (move include line up). Furthermore it builds an .o object in the
> static compiled case
On Wed, 20 Dec 2000, Hans-Joachim Baader wrote:
> Then run the program. It should copy the files to the current
> directory. Then run it under gdb. It should hang until you kill
> gdb.
Hello again
(Sorry for the long response time but this really is the busiest time of
the year, or maybe it's
Hi,
I am using Linux 2.2.18 with vm-global-7 and raid-0.90
applied. The system became virtually unresponsive earlier
and after a reboot, I found the following in my logs. By
unresponsive I mean ping would work but telnet for example
would connect and just sit there.
Jan 2 04:36:27 continuum
On Tue, 2 Jan 2001, Andrea Arcangeli wrote:
> On Tue, Jan 02, 2001 at 11:02:41AM -0800, Linus Torvalds wrote:
> > What does the system feel like if you just change the "sleep for bdflush"
> > logic in wakeup_bdflush() to something like
> >
> > wake_up_process(bdflush_tsk);
> >
Hi,
On Tue, 2 Jan 2001, David S. Miller wrote:
>We really can't. We _only_ have load-and-zero. And it has to be
>16-byte aligned. xchg() is just not something the CPU implements.
>
> Oh bugger... you do have real problems.
For 2.5 we could move all the atomic functions from
On Tue, Jan 02, 2001 at 03:12:37PM -0500, Ghadi Shayban wrote:
> {standard input}: Assembler messages:
> {standard input}:139: Error: bad register name `%%mm0'
This is, in fact, a compiler bug. Somehow the "%%" in the
source didn't print as "%" as expected.
r~
-
To unsubscribe from this list:
David,
Sorry for being dense - but I don't see the problem in using
a spinlock to implement xchg(). The example algorithm looks broken.
Or am I missing something obvious here?
"David S. Miller" wrote:
> It is very common to do things like:
>
> producer(elem)
> {
> elem->next =
Upon booting my shiny new Abit VP6 motherboard, I get:
... : IO APIC version: 0011
WARNING: unexpected IO-APIC, please mail
to [EMAIL PROTECTED]
and here is the dmesg, followed by lspci -xx.
Hope it is of some use!
Greetings,
Jurriaan
Linux version 2.2.19pre3 (root@middle)
Perhaps the help text for disk quotas needs to be updated, or at least the
howto for quotas.
The help text for disk quotas says to see the Quota mini-HOWTO. The howto
says to get the quota source from:
ftp://ftp.funet.fi/pub/Linux/PEOPLE/Linus/subsystems/quota/all.tar.gz
That doesn't exist
> I have no idea, but I'm guessing this isn't a gcc bug. Here's where my
> build fails:
> {standard input}: Assembler messages:
> {standard input}:139: Error: bad register name `%%mm0'
Your compiler/binutils are too old
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Perhaps a deadlock with a normal (not irq) spinlock.
Could you enable SysRQ and press ++ ("showPc")
Then write down the EIP values (including the [< >] brackets) and
translate them with ksymoops.
Ksymoops repeats only the EIP values.
But searching through the System.map file has only Labels
I have no idea, but I'm guessing this isn't a gcc bug. Here's where my
build fails:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=athlon -c -o mmx.o mmx.c
{standard input}:
On Tue, Jan 02, 2001 at 11:02:41AM -0800, Linus Torvalds wrote:
> What does the system feel like if you just change the "sleep for bdflush"
> logic in wakeup_bdflush() to something like
>
> wake_up_process(bdflush_tsk);
> __set_current_state(TASK_RUNNING);
> current->policy |=
Hubert Mantel wrote:
>
> Hi,
>
> On Tue, Jan 02, Geert Uytterhoeven wrote:
>
> > This patch fixes two things:
> >
> > - Correct the minor numbers for the frame buffer devices. We have room for
> > 32 frame buffers since about one year, with more room for future expansion
> > to 256.
Hi folks,
I have 2 servers with lvm trouble, one running
Red Hat 6.2, and the other running Red Hat 7.0
plus latest errata.
Both systems had been running lvm-0.8
on 2.4.0-test for awhile with no problems.
After instaling 2.4.0-prerelease and building
the lvm 0_9-1 source rpm on both systems,
Followup to: <[EMAIL PROTECTED]>
By author:"Giacomo A. Catenazzi" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> When working in cpu autoconfiguration I found some problems:
>
> I have to identify this processor:
> Vendor: Intel
> Family: 6
> Model: 8
> Is it a "Pentium III
On Tue, 2 Jan 2001, J Sloan wrote:
> Alan Cox wrote:
>
> > Bzzt, wrong. Red Hat 7 compiles the 2.4 tree beautifully with gcc 2.96 as well.
> > Please grow up.
>
> Yes indeed - on my quad CPU Red Hat 7 server, I accidentally
> forgot to say CC=kgcc during the last kernel build, and ended
> up with
> > It sounds like the proper fix would be to not enable ata66 by default.
>
> LT,
>
> This is one of the evolution timing issues that both the drive guys and
> the chipset guys point fingers, while both attempt to fix the problem in
> their BIOS/Diskware.
Then lets default to ATA33 on the
In article <[EMAIL PROTECTED]>,
Alan Cox <[EMAIL PROTECTED]> wrote:
>> > We really can't. We _only_ have load-and-zero. And it has to be 16-byte
>> > aligned. xchg() is just not something the CPU implements.
>>
>> The network code relies on the reader-xchg semantics David described in
>>
1 - 100 of 381 matches
Mail list logo
