On Fri, 8 Dec 2000, Johannes Erdfelt wrote:
> Actually, looking back at your previous email, enabling bus mastering
> may make this error go away.
>
> Could you give -pre7 a try? Or have you already?
This is pre7
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kern
Here you are two patches:
alpha-mb-2.2.diff add the missing mb() to the cores that still lack it
(against 2.2.18pre25)
alpha-mb-2.4.diff add missing defines from core_t2.h for non generic
kernel (against 2.4.0test11)
Please apply on your trees.
I've also noted that 2.4 uses mb() after read[bw
On Fri, 8 Dec 2000, Alexander Viro wrote:
> On Fri, 8 Dec 2000, Linus Torvalds wrote:
>
> > Looking more at this issue, I suspect that the easiest pretty solution
> > that everybody can probably agree is reasonable is to either pass down the
> > end-of-io callback to ll_rw_block as you suggested
On Sat, 9 Dec 2000, Linus Torvalds wrote:
>
> This is a preliminary patch that I have not compiled and probably breaks,
> but you get the idea. I'm going to sleep, to survive another night with
> three small kids.
Call me stupid [ Chorus: "You're stupid, Linus" ], but I actually compiled
and b
Use of Xconfigurator with the 2.2.18-25 pre-patch causes hard hangs
and lockups on a 4 x PPro server. I am using it with frame buffer
support enabled, AGP enabled, and with the /dev/agpgart device
at maj 10 min 175 set to crw-rw-rw-.
XF86Setup runs fine provided you know what card or chipset y
Hi,
I've seen the e100 udelay/compile problem twice and now I think,
I should release my patch.
I've already send it to Intel but the are not responding.
Please CC: any comments.
cheers, Thomas.
e100-type.patch
e100-mdelay.patch
Here is the .config file section for turning on the console drivers
for 2.2.18-25 that causes the sickness with Xconfigurator.
Jeff
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_MDA_CONSOLE=m
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FB_PM2=y
# CONFIG_FB_PM2_FIFO_DISC
KERNEL VER: 2.4.0-test11
ADD. PATCHES: reiserfs patch
NETWORK CARD: NE2K-PCI Kingston KNE-111TX (P/N: 4460170-001.A00)
10/100BASE-TX
MOBO: MSI BX-Master with 20001013 BIOS update
PROBLEM: Network hangs on all initial outbound traffic.
I need to do a ping in order to get any type of connection.
Hello again
I have performed some tests; and reached the following conclusions
regarding this matter.
As always, UniProcessor kernels have no problems; only SMP ones.
kernel 2.2.17 + idepatches, hde (i.e., on the HPT366) at UDMA(66):
I was unable to cause any corruption despite my best efforts
OK, thanks to Andries Brouwer, who pointed me to IBM's dtla_spw.pdf, I
solved the problem:
The kernel (2.2.18-pre25 + ide.2.2.18-24.all.20001204.patch.bz2) already
has support for unclipping. The problem is that the IBM drive does not
work with the method used when clipped with the jumper. The
This has the missing ide-pci code from 2.2.
It stablized my BP6 on the HPT core.
Cheers,
Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development
diff -urN linux-2.4.0-t12-7-pristine/drivers/ide/cs5530.c
linux-2.4.0-t12-7/drivers/ide/cs5530.c
--- linux-2.
At 21.29 08/12/00 +0100, Rasmus Andersen wrote:
>Hi.
>
>The following patch moves the page_table_lock in mm/* to cover the
>modification of mm->rss in 240-test12-pre7. It was inspired by a
>similar patch from davej(?) which covered too much, AFAIR. The item
>is on Tytso's ToDo list.
[...snip...]
Alexander Viro wrote:
> > It was just an example. Basically, you'd be able to do in with just
> > about any language that has ORBit bindings.
>
> Yeah... "Infinitely extendable API" and all such. Roughly translated
> as "we can't live without API bloat". Frankly, judging by the GNOME
> codebase p
On Sat, 9 Dec 2000, Linus Torvalds wrote:
> This is a preliminary patch that I have not compiled and probably breaks,
> but you get the idea. I'm going to sleep, to survive another night with
> three small kids.
>
> If somebody wants to run with this, please try it out, but realize that
> it's
On Fri, 8 Dec 2000, Matan Ziv-Av wrote:
> Hi,
>
> I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with
> large disks. I use a jumper to clip it to 32GB size, so the bios can
> boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB,
> and not the true size, and even
[Rasmus Andersen]
> -static struct w83977af_ir *dev_self[] = { NULL, NULL, NULL, NULL};
> +static struct w83977af_ir *dev_self[];
How does the compiler know the size of the array?
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Fri, Dec 08, 2000 at 03:31:08PM +0100, Benjamin Herrenschmidt wrote:
> The problem I have (and this is why I don't setup host resources
> properly on multi-host PPCs yet) is that some hosts can have several
> non-contiguous ranges (especially with memory, IO is usually a single
> contiguous ran
On Sat, Dec 09, 2000 at 01:14:00AM +0100, David Härdeman wrote:
> By looking at the windows drivers provided with the card I came to the
> conclusion that the onboard chip was an Oxford Semiconductor OX16PCI954
> which as far as I could understand is documented in
> http://www.oxsemi.com/products
On Sat, 9 Dec 2000, Abramo Bagnara wrote:
>
> Here you are two patches:
>
> alpha-mb-2.2.diff add the missing mb() to the cores that still lack it
> (against 2.2.18pre25)
>
> alpha-mb-2.4.diff add missing defines from core_t2.h for non generic
> kernel (against 2.4.0test11)
>
> Please apply
Hi,
I found a way to reliably OOM test12-pre7 to death. (not my goal;)
1. Start a make -jN bzImage where N is large enough to swap ~hard.
2. Let it ramp up such that oh, say 50mb is in swap and then ^C.
... repeat a few times to verify that all jobs terminate properly,
and that you can do this
Hi,
I noticed a lot of drivers are setting the PCI_CACHE_LINE_SIZE
themselves, some to L1_CACHE_BYTES/sizeof(u32), others
to arbitrary values (4, 8, 16).
Then I spotted that we have a routine in the PCI subsystem
(pdev_enable_device) that sets all these to L1_CACHE_BYTES/sizeof(u32)
Further dig
Gérard Roudier wrote:
>
>
> Based on that, let me claim that most of blind barriers inserted this way
> are useless (thus sob-optimal) and may band-aid useful barriers that are
> missing. The result is subtle bugs, hidden most of the time, that we will
> have to suffer for decades.
>
> The only
[EMAIL PROTECTED] writes:
> 2. Why is pdev_device_enable no longer used ?
It is used from pci_assign_unassigned_resources. iirc, its just that
x86 doesn't call this function.
_
|_| - ---+---+-
| | Russell King[EMAIL
On Sat, Dec 09, 2000 at 04:46:15AM -0600, Peter Samuelson wrote:
>
> [Rasmus Andersen]
> > -static struct w83977af_ir *dev_self[] = { NULL, NULL, NULL, NULL};
> > +static struct w83977af_ir *dev_self[];
>
> How does the compiler know the size of the array?
By reading my mind, I guess :( The fol
On Sat, Dec 09, 2000 at 11:25:09AM +0100, Roberto Fichera wrote:
[...]
> >+ spin_lock(&mm->page_table_lock);
> > mm->rss++;
> >+ spin_unlock(&mm->page_table_lock);
> >
>
> [...snip...]
>
> Why we couldn't use atomic_inc(&mm->rss) here and below, avoiding to wrap
> the inc wit
> The mouse problems have gone away with the 2.2.18-25 pre-patch. I
> am not seeing the problems anymore on the affected systems. I am
I think that is chance. There are no mouse driver changes from -24 to -25 8)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
> Yeah... "Infinitely extendable API" and all such. Roughly translated
> as "we can't live without API bloat". Frankly, judging by the GNOME
> codebase people who designed the thing are culturally incompatible with
> UNIX.
Oh they are definitely unix people, but ORBit is about solving a very
dif
On Sat, Dec 09, 2000 at 11:38:05AM +, Russell King wrote:
> [EMAIL PROTECTED] writes:
> > 2. Why is pdev_device_enable no longer used ?
Right question would be "why is it not used yet?" ;-)
This routine appeared a while ago in one of test12-pre.
> It is used from pci_assign_unassigned_resour
On Sat, 9 Dec 2000, Alan Cox wrote:
> > Yeah... "Infinitely extendable API" and all such. Roughly translated
> > as "we can't live without API bloat". Frankly, judging by the GNOME
> > codebase people who designed the thing
On Sat, 9 Dec 2000, Ivan Kokshaysky wrote:
> > It is used from pci_assign_unassigned_resources. iirc, its just that
> > x86 doesn't call this function.
> Yes, only alpha, arm and mips are using that code.
Ok, thanks Ivan/Russell for clearing this up for me.
If/When x86 (or all?) architectures
Date:Sat, 09 Dec 2000 11:25:09 +0100
From: Roberto Fichera <[EMAIL PROTECTED]>
Why we couldn't use atomic_inc(&mm->rss) here and below, avoiding to wrap
the inc with a spin_lock()/spin_unlock() ?
atomic_t does not guarentee a large enough range necessary for mm->rss
Later,
D
On Sat, Dec 09, 2000 at 11:50:59AM +0200, Matan Ziv-Av wrote:
> I use the attached program, which is a modification of setmax,
Good! So we learned something again.
I merged both versions of setmax.c and added text to the
Large Disk HOWTO. See
http://www.win.tue.nl/~aeb/linux/Large-Disk-1
On Sat, Dec 09, 2000 at 05:40:47AM -0500, Alexander Viro wrote:
> > @@ -1210,7 +1204,6 @@
> [breada()]
> Umm... why do we keep it, in the first place? AFAICS the only
> in-tree user is hpfs_map_sector() and it doesn't look like we really
> need it there. OTOH, trimming the buffer.c down is
> If/When x86 (or all?) architectures use this, will it make sense to
> remove the PCI space cache line setting from drivers ?
> Or is there borked hardware out there that require drivers to say
> "This cacheline size must be xxx bytes, anything else will break" ?
If there is surely the driver ca
On Sat, 9 Dec 2000, Alan Cox wrote:
> > Or is there borked hardware out there that require drivers to say
> > "This cacheline size must be xxx bytes, anything else will break" ?
> If there is surely the driver can override it again before enabling the
> master bit or talking to the device ?
The
On Sat, 9 Dec 2000, Andries Brouwer wrote:
> On Sat, Dec 09, 2000 at 05:40:47AM -0500, Alexander Viro wrote:
>
> > > @@ -1210,7 +1204,6 @@
> > [breada()]
> > Umm... why do we keep it, in the first place? AFAICS the only
> > in-tree user is hpfs_map_sector() and it doesn't look like we real
Well heres my first attempt at kernel debugging
the problem posted yesterday. I some magic sysrq- on the 486 after the
Donald Becker eth0 message displayed. I had to hand write the EIP trace and then
enter it into ksysmoops. Don't know if it will help but I'll try recompiling the
kernel with
On Sat, Dec 09, 2000 at 12:53:46PM +, Alan Cox wrote:
> If there is surely the driver can override it again before enabling the
> master bit or talking to the device ?
It could be done in PCI_FIXUP_FINAL quirks.
Ivan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>>EIP; c0270c21<=
Trace; c01f488e
Trace; ca8578be <[audio]usbout_completed+7e/c0>
Trace; c01ffc3e
Trace; c01ffd49
1. process_urb() obtains the urb_list_lock.
2. Then calls urb->complete() which is audio.c::usbout_complete()
3. Which in turn calls usb_submit_urb()
4. Which calls uhci_s
ftp://ftp..kernel.org/pub/linux/utils/kernel/modutils/v2.3
patch-modutils-2.3.22.gzPatch from modutils 2.3.21 to 2.3.22
modutils-2.3.22.tar.gz Source tarball, includes RPM spec file
modutils-2.3.22-1.src.rpm As above, in SRPM format
modutils-2.3.22-1.i386.rpm Compiled
I wrote:
> Yeah... "Infinitely extendable API" and all such. Roughly translated
> as "we can't live without API bloat". Frankly, judging by the GNOME
> codebase people who designed the thing are culturally incompatible with
> UNIX.
Hrrm. After rereading... I suspect that I wasn't clear en
Mark,
after applying that patch I cut out of an email from Linus the bug continues
to appear but the output of ksymoops looks a little bit shorter.
>I've read Linus' posting and patched my kernel. It's compiling now.
>Nevertheless I attached the output of ksymoops - maybe it'll be still
>help
Date:Sat, 9 Dec 2000 00:45:51 -0800 (PST)
From: Linus Torvalds <[EMAIL PROTECTED]>
out:
-if (nr) {
-ll_rw_block(WRITE, nr, arr);
-} else {
-UnlockPage(page);
-}
+UnlockPage(page);
ClearPageUptodate(page);
Well that didn't work either! I took out APM
from 2.2.17 and the now the system resets immediately following the "Booting
Kernel" message.
Anybody got some good pointers for debugging a
kernel at boot time?
Thanks, Eddy
On Sat, Dec 09, 2000 at 12:41:24AM -0500, Theodore Y. Ts'o wrote:
> In the case of the MegaHertz modem PCMCIA card and the Linksys combo
> PCMCIA card, card registers manage to survive the serial driver's UART
> test (although as a 8250 or 16450, instead of the 16550A that's really
> in those
On Sat, 9 Dec 2000, Abramo Bagnara wrote:
> Gérard Roudier wrote:
> >
> >
> > Based on that, let me claim that most of blind barriers inserted this way
> > are useless (thus sob-optimal) and may band-aid useful barriers that are
> > missing. The result is subtle bugs, hidden most of the time,
At 13.43 09/12/00 +0100, Rasmus Andersen wrote:
>On Sat, Dec 09, 2000 at 11:25:09AM +0100, Roberto Fichera wrote:
>[...]
> > >+ spin_lock(&mm->page_table_lock);
> > > mm->rss++;
> > >+ spin_unlock(&mm->page_table_lock);
> > >
> >
> > [...snip...]
> >
> > Why we couldn't use at
Date: Sat, 09 Dec 2000 15:48:05 +0100
From: Roberto Fichera <[EMAIL PROTECTED]>
>atomic_t does not guarentee a large enough range necessary for mm->rss
If we haven't some atomic_t that can be negative we could define atomic_t
as unsigned long for all arch,
this is sufficient t
On Fri, 8 Dec 2000, Jeff V. Merkey wrote:
> The mouse problems have gone away with the 2.2.18-25 pre-patch. I
> am not seeing the problems anymore on the affected systems. I am
> trying this evening to apply the 2.4 patch sent to me to see if it
> helps with the page cache corruption problem w
Hi!
> I noticed a lot of drivers are setting the PCI_CACHE_LINE_SIZE
> themselves, some to L1_CACHE_BYTES/sizeof(u32), others
> to arbitrary values (4, 8, 16).
>
> Then I spotted that we have a routine in the PCI subsystem
> (pdev_enable_device) that sets all these to L1_CACHE_BYTES/sizeof(u32)
At 06.42 09/12/00 -0800, David S. Miller wrote:
>Date: Sat, 09 Dec 2000 15:48:05 +0100
>From: Roberto Fichera <[EMAIL PROTECTED]>
>
>>atomic_t does not guarentee a large enough range necessary for mm->rss
>
>If we haven't some atomic_t that can be negative we could define atomic_t
Date: Sat, 09 Dec 2000 16:07:03 +0100
From: Roberto Fichera <[EMAIL PROTECTED]>
8 bits for a spinlock ? What kind of use we have here ?
Sparc32 (like some other older architectures) do not have a
word atomic update instruction, but it does have a byte spinlock.
To conserve space and imp
On Fri, 8 Dec 2000, Alexander Viro wrote:
> BTW, what do you think about the following:
> * add_to_page_cache() is not exported and never used. Kill?
I have my eye on that for execute-in-place of romfs from real ROM chips -
making up struct pages for parts of the ROM chips and inserting th
On Sat, 9 Dec 2000, Alan Cox wrote:
> > If/When x86 (or all?) architectures use this, will it make sense to
> > remove the PCI space cache line setting from drivers ?
> > Or is there borked hardware out there that require drivers to say
> > "This cacheline size must be xxx bytes, anything else
Hello all,
Recently, I upgraded my poor Socket7 system from a P166 to a AMD
K6-2 running at 400 MHz.
The only change I made to my kernel config with the upgrade was
to add in MTRR support.
My kernel is a stock 2.2.18pre25, with the addition of the S3
framebuffe
>
> From what I've seen in GNOME it's mostly about avoiding pipes
> religiously and putting everything and a kitchen sink into the same
> process. I'm not saying that it has no valid uses, but it definitely
> had contributed to the bloat in case of GNOME.
>
Please consider to read this articl
/usr/src/linux/include/linux/modules/irmod.ver:139: warning: this is the
location of the previous definition
/usr/src/linux/include/linux/modules/irsyms.ver:145: warning:
`__ver_irda_task_kick' redefined
/usr/src/linux/include/linux/modules/irmod.ver:141: warning: this is the
location of the pr
John Summerfield <[EMAIL PROTECTED]> writes:
> I HAVE built this kernel for another computer. I was having problems with
> this, so I remove the .config, created a new one with "make oldconfig" and the
> customised with make xconfig"
make mrproper
--
MandrakeSoft Inc htt
I'm not sure if this happened w/o reiserfs compiled or not. I didn't leave
it running over night (crash happened about 07:00)
Last thing in the log before this was st being loaded (I have a backup that
starts at 06:00) I don't believe this has anything to do with the crash,
but the machine cras
Linus Torvalds wrote:
> On Sat, 9 Dec 2000, Theodore Y. Ts'o wrote:
> >I didn't have time to do more than just quickly apply the patch and leave
> >in a hurry, but my Vaio certainly recognized the serial port on the combo
> >cardbus card I have with this patch. Everything looked fine -
My apologies for following myself up. Here is slightly more info, if
it will help.
Linux version 2.2.18pre25 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #2 Sat Dec 9 09:39:50 EST 2000
Detected 400915 kHz processor.
Console: colour dummy device 80x25
Calibra
One problem with warnings at compile time is that in many cases, administrators
use kernels provided by friends or collegues that "know linux better than them".
If an admin uses a kernel in which write support has been activated to mount
an NTFS file system without providing any option, he will ge
Hi,
I get this message while doing:
rsync -ac --exclude "/proc" --exclude "/raid" / /raid/
to move all data in the raid1 device. I expected to try the md
autodetect feature, but I am afraid something is wrong...
Know problem ?
--
Jean-Christian
Dec 9 17:33:44 bjork syslogd 1.3-3#33.1: restart.
On Sat, 9 Dec 2000, Alexander Viro wrote:
> Fine
> > - atomic_inc(&bh->b_count);
>
> Why? It's cleaner the old way - why bother postponing that until we
> lock the thing?
I had a rule: we always do the "lock_buffer()" and "b_count increment"
together with setting "b_end_i
Hi,
I've released what will probably be the last blk-xx patch for 2.4, at
least as far as features go. In fact, blk-12 is just minor tweaks and
fixes over the previous version. Highlight of changes:
o Merge elevator merge and insertion scan. This saves an entire linear
queue scan when we can't
Hi,
Stumbled over a small leak.. and some funny looking numbers.
while true; do swapoff -a; swapon -a; done
procs memoryswap io system cpu
r b w swpd free buff cache si sobibo incs us sy id
0 0 0 0 73120 43
=?ISO-8859-1?Q?G=E9rard_Roudier?= writes:
> As a result, in my opinion:
>
> - A device that requires some non zero cache line size value lower than
> the right value for a given system and that actually use MWIs must not be
> supported on that system, unless we know that the bridge does alias MWI
On Sat, 9 Dec 2000, Jens Taprogge wrote:
>
> I have a Megaherz card as well. It has been working fine ever since
> Linus fixed some issues with the ToPIC97 Cardbus controller. It reports
> a 16550A on my machine.
I checked my VAIO's, and they all have a Ricoh cardbus bridge.
Ted claimed he ha
PCI: PCI BIOS revision 2.10 entry at 0xfb240, last bus=1
PCI: Probing PCI hardware
PCI: Using IRQ router VIA [1106/0586] at 00:07.0
..
PCI: Assigned IRQ 11 for device 00:08.0
PCI: The same IRQ used for device 01:00.0
IRQ routing conflict in pirq table! Try 'pci=autoirq'
00:08.1 Input device cont
On Sat, 9 Dec 2000, Martin Mares wrote:
> > Questions:
> > 1. Is there reason for the drivers to be setting this themselves
> >to hardcoded values ?
>
> Definitely not unless the devices are buggy and need a work-around.
Maybe that's the case. The culprits are mostly IDE interfaces. Andre ?
At 07.00 09/12/00 -0800, David S. Miller wrote:
>Date: Sat, 09 Dec 2000 16:07:03 +0100
>From: Roberto Fichera <[EMAIL PROTECTED]>
>
>8 bits for a spinlock ? What kind of use we have here ?
>
>Sparc32 (like some other older architectures) do not have a
>word atomic update instruction,
- stifb doesn't use resource management (yet?), so it must be initialized
later for consistency (as indicated by the comments in fbmem.c)
- Remove superfluous NULL data
--- linux-2.4.0-test12-pre7/drivers/video/fbmem.c.orig Sat Dec 9 14:18:21 2000
+++ linux-2.4.0-test12-pre7/drivers/vi
Linus Torvalds <[EMAIL PROTECTED]> writes:
> > Modulo the comments above - fine with me. However, there is stuff in
> > drivers/md that I don't understand. Ingo, could you comment on the use of
> > ->b_end_io there?
>
> I already sent him mail about it for the same reason.
How about sendi
Hi,
The aforementioned kernel seems to have a minor bug on
(at least) my laptop -- it looks like a potential off-
by-one in the socket handling:
After a clean bootup:
# cardctl status 0
no card
# cardctl status 1
no card
Insert a card in socket 0
# cardctl status 0
no card
# cardctl statu
Alan Cox wrote:
>
> > > wrong with it. I've only seen this under 2.3.x/2.4 SMP kernels. I
> > > would say that this is definitely a kernel problem.=20
> >
> > XFree86 3.9 and XFree86 4 were rock solid for a _long_ time on 2.[34]
> > kernels - even on my BP6=B9. The random crashes started to hap
On Sat, Dec 09, 2000 at 11:55:43AM +, Alan Cox wrote:
> > The mouse problems have gone away with the 2.2.18-25 pre-patch. I
> > am not seeing the problems anymore on the affected systems. I am
>
> I think that is chance. There are no mouse driver changes from -24 to -25 8)
:-) It makes
On Sat, Dec 09, 2000 at 10:05:46AM -0500, Steven N. Hirsch wrote:
> On Fri, 8 Dec 2000, Jeff V. Merkey wrote:
>
> > The mouse problems have gone away with the 2.2.18-25 pre-patch. I
> > am not seeing the problems anymore on the affected systems. I am
> > trying this evening to apply the 2.4 pa
On Sat, Dec 09, 2000 at 05:49:00PM +0100, Willy Tarreau wrote:
> One problem with warnings at compile time is that in many cases, administrators
> use kernels provided by friends or collegues that "know linux better than them".
> If an admin uses a kernel in which write support has been activated
On Sat, 9 Dec 2000, Matthew Vanecek wrote:
> > Have any of the folks seeing it checked if Ben LaHaise's fixes for the page
> > table updating race help ?
> > Alan
>
> Where are his fixes at? I don't seem to see any of his posts in the
> archives.
dwmw2 posted one such patch earlier this week :
Alan/Jens,
Please consider applying, a similar patch is already in 2.4. In
sr_init we don't need zeroing the data allocated with scsi_init_malloc, as
scsi_init_malloc already does this for us.
- Arnaldo
--- linux-2.2.18-pre25/drivers/scsi/sr.cSat Dec 9 15:08:24 2000
+++ linux-2
Alan/Yaroslav,
Please consider applying, a similar patch is already in 2.4.
- Arnaldo
--- linux-2.2.18-pre25/drivers/net/sbni.c Sat Dec 9 15:08:17 2000
+++ linux-2.2.18-pre25.acme/drivers/net/sbni.c Sat Dec 9 17:44:53 2000
@@ -456,6 +456,7 @@
if(dev->priv == NULL)
Alan/Adam,
Please consider applying, a similar patch is already in 2.4.
- Arnaldo
--- linux-2.2.18-pre25/drivers/scsi/3w-.c Tue Sep 5 19:13:35 2000
+++ linux-2.2.18-pre25.acme/drivers/scsi/3w-.c Sat Dec 9 17:59:22 2000
@@ -3,6 +3,8 @@
Written By: Adam Radford <[EM
Hi Linus,
Unfortunately there was a SMP race between ->read() and ->ioctl() routines
(thanks to Mark Hemment for pointing this out!). If one was inside the
->read() after the EOF check and an ioctl requests came in onother CPU
which freed the memory and reset the size then one could panic. The fi
> - A driver that blindly shoe-horns some value for the cache-line size must
> be fixed. Basically, it should not change the value if it is not zero and,
> at least, warn user if it has changed the value because it was zero.
>
> What are the strong reasons that let some POST softwares not fill pr
> > From what I've seen in GNOME it's mostly about avoiding pipes
> > religiously and putting everything and a kitchen sink into the same
> > process. I'm not saying that it has no valid uses, but it definitely
> > had contributed to the bloat in case of GNOME.
> >
>
> Please consider to read t
Hi!
> The following patch removes a 'defined but not used' warning from drivers/
> new/hp100.c when compiling without CONFIG_PCI (240t12p3). It should apply
> cleanly.
I'd say that warning is more acceptable than #ifdef... In cases where
warnings can be eliminating without ifdefs, that's okay, b
Hello,
On Sat, 9 Dec 2000, Victor J. Orlikowski wrote:
> However, in X I get *random* lock-ups (sometimes when gdm
> starts, sometimes when using gmc, etc.)
> Disabling MTRR seems to have cured the problem, for now (I
> haven't *seen* anything random *yet*; I'll
Hi,
It seems that the BUG() at skbuff.c:175 (2.4.0test12pre7)
kills the machine dead; BUG() isn't (or doesn't appear to
be) interrupt safe:
alloc_skb called nonatomically from interrupt c0194b81
kernel BUG at skbuff.c:175!
invalid operand:
[..]
Code: 0f 0b 83 c4 0c 89 f6 83 e7 fe be 20 c5 2
Date: Sat, 9 Dec 2000 21:16:51 + (GMT)
From: Matthew Kirkwood <[EMAIL PROTECTED]>
I guess it should probably be removed (or replace with a
call to something which doesn't try to kill the attached
process.
BUG is supposed to give a backtrace, nothing more.
If it happens to kill
Hi!
It is possible to remove swapfile in use. Great, but how do you swap
off then? Who is to blame?
root@bug:~# swapoff /tmp/swap
swapoff: /tmp/swap: No such file or directory
root@bug:~# > /tmp/swap
root@bug:~# swapoff /tmp/swap
swapoff: /tmp/swap: Invalid argument
root@bug:~#
How do I get out
On Sat, 9 Dec 2000, Matthew Kirkwood wrote:
> I once managed to make it assign a socket 0 card to both sockets
> and completely ignore socket 1, but can't reproduce this now.
Did it again. It seems that if I boot with anything
in socket 0, socket 1 becomes useless.
Matthew.
-
To unsubscribe f
On Sat, 9 Dec 2000, Alexander Viro wrote:
> On Sat, 9 Dec 2000, Andries Brouwer wrote:
>
> > On Sat, Dec 09, 2000 at 05:40:47AM -0500, Alexander Viro wrote:
> >
> > > > @@ -1210,7 +1204,6 @@
> > > [breada()]
> > > Umm... why do we keep it, in the first place? AFAICS the only
> > > in-tree use
This is precisely my problem.
K6-2, model 8, stepping 12.
Thus far, everything is *fine*, as long as MTRR is not compiled into
the kernel.
If MTRR is compiled into the kernel, I get lock-ups in X *only*, and
the entire machine locks.
I have no data on other CPUs; as I said, I previously had a P166
On Sat, 9 Dec 2000, Pavel Machek wrote:
> It is possible to remove swapfile in use. Great, but how do you
> swap off then? Who is to blame?
As usual, root is to blame ;)
> root@bug:~# swapoff /tmp/swap
> swapoff: /tmp/swap: No such file or directory
> root@bug:~# > /tmp/swap
> root@bug:~# swapo
2.2.18-25 with Frame Buffer enabled will frizt and trash LCD displays
on DELL laptop computers when the system kicks into graphics mode,
and attempts to display the penguin images on the screen. It
renders the anaconda installer dead in the water when you attempt
even a text mode install (not
Anyone have a clue on this issue? Even a starting point would be
appreciated.
I want to add a bunch of printfk() to the source so that I can track what
functions are being executed and when in the hope that it may lend a hand in
tracking this down. I'm NOT a coder in any way shape or form so this
On Sat, Dec 09, 2000 at 05:49:00PM +0100, Willy Tarreau wrote:
Alan has spoken. If DANGEROUS doesn't get their attention, what
will?
Jeff
> One problem with warnings at compile time is that in many cases, administrators
> use kernels provided by friends or collegues that "know linux better th
On Sat, 9 Dec 2000, Jeff V. Merkey wrote:
>
>
> 2.2.18-25 with Frame Buffer enabled will frizt and trash LCD displays
> on DELL laptop computers when the system kicks into graphics mode,
> and attempts to display the penguin images on the screen. It
> renders the anaconda installer dead in th
> On Sat, 9 Dec 2000, Pavel Machek wrote:
>
> > It is possible to remove swapfile in use. Great, but how do you
> > swap off then? Who is to blame?
>
> As usual, root is to blame ;)
I do not agree. It is too easy to get to situation like this.
> > root@bug:~# swapoff /tmp/swap
> > swapoff: /tm
On Sat, Dec 09, 2000 at 02:03:08PM -0800, Bob Lorenzini wrote:
> On Sat, 9 Dec 2000, Jeff V. Merkey wrote:
>
> >
> >
> > 2.2.18-25 with Frame Buffer enabled will frizt and trash LCD displays
> > on DELL laptop computers when the system kicks into graphics mode,
> > and attempts to display the p
1 - 100 of 160 matches
Mail list logo
