On Tue, Dec 12, 2000, Andrey Savochkin <[EMAIL PROTECTED]> wrote:
; To answer your question in short, yet, we hope to fix the problem sooner or
; later.
I added the print out of the message to see in what state was the card
being left after it was wedged.
The card seems to be locking up with un
Hello,
On Mon, Dec 11, 2000 at 10:52:19AM -0800, Tom Murphy wrote:
>Also, regarding the eepro100 driver, are there any plans to fix
> support for the following chipset (given by lspci):
>
[snip]
> I have one of these at work and I will get the following messages:
>
> Dec 11 10:46:13 morph
Hello all,
test12-pre7 seems to randomly just power off my machine.
CONFIG_APM=y and CONFIG_APM_REAL_MODE_POWER_OFF=y as well. Could this
be what is
making it power off the machine randomly? Has it been fixed in pre8?
I wasn't doing much on the machine at the time.. it just happens
sporadi
Hi there,
For a long time, I experienced Oops with 2.4.0-testxx-prexx. I've reported
several Oops. With every patch, the system crashes with a Oops and is frozen.
The attached Oops was recorded by hand. Even the 'magic keys' are not working.
After booting the sytem, the filesystem is corrupted w
My mail client thought it would be amusing to wrap my text at 80
columns.
Useful at times, I'll give it that; but it chewed on my patch a little.
Reasoning / excuses in my earlier post with the similar subject line...
Good Night and Happy Hacking
Gerard Sharp
Two Penguins at 1024x768
#diff -du
FWIW, I got the following oops while trying to play an mpeg stream
from a loop-back mounted iso9660 file system:
ksymoops 0.7c on i586 2.4.0-test12.pre7.1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test12.pre7.1/ (defa
Hello
I just upgraded to both of the above (from .21 and and test11-ac4
respectively); and 8139too.o and ntfs.o both failled to insmod;
insmod: /lib/modules/2.4.0-test12/kernel/fs/ntfs/ntfs.o
: symbol for parameter ntdebug not found
the problem in both cases appears to be a MODULE_PARM refering
This message showed up when running lilo on an ext2 image, mounted via
a loopback mount. Line 827 in fs/buffer.c is a call to UnlockPage().
The complete message from /var/log/messages:
Dec 9 18:24:51 tampere kernel: kernel BUG at buffer.c:827!
Dec 9 18:24:51 tampere kernel: invalid operand: 00
anic. The fix is
trivial -- just down the semaphore inside ->read() a bit earlier.
This patch is cumulative again since you have not accepted yet all the
previous fixes.
Tested under 2.4.0-test12-pre7 of course.
Regards,
Tigran
diff -urN -X dontdiff linux/CREDITS ucode/CREDITS
--- linux/CREDI
> However when I then suspended the machine and resumed it sound no longer
> worked. In fact the mpg123 that I used to test it after the resume is
> now just sitting there.
The driver does not currently support power management. In fact whoever
hacked on the include files went and put __init in
Hi,
On Wed, Dec 06, 2000 at 05:29:14PM -0800, Linus Torvalds wrote:
> - test7:
> - Kai Germaschewski: ymfpci cleanups and resource leak fixes
> - pre5:
> - Jaroslav Kysela: ymfpci driver
Just tried this out on my laptop and it played and didn't give strange
messages that Pete's driver
I have noticed that Linux 2.4.0-test12-pre7 still comes with .8final. Is
there a plan to have .9 incorporated at some future time into the stock
2.4 kernels? Will this happen before 2.4 comes out?
Also is there a transition path between .8final and .9? (short of save
everything to tape and
ew days.
Tested thoroughly under 2.4.0-test12-pre7. I have also backported most of
the fixes to 2.2.
Regards,
Tigran
diff -urN -X dontdiff linux/CREDITS ucode/CREDITS
--- linux/CREDITS Thu Dec 7 08:41:55 2000
+++ ucode/CREDITS Fri Dec 8 11:01:27 2000
@@ -41,7 +41,7 @@
E: [EMAIL PRO
On Thu, Dec 07, 2000 at 08:01:13PM +0100, Kai Germaschewski wrote:
> Maybe I'm stating something which is obvious to everybody, but note
> that pci_assign_unassigned_resources is only called from
Possibly, but I don't know either. :)
> ./arch/alpha/kernel/pci.c: pci_assign_unassigned_resources
Linus Torvalds wrote:
> probably vote for getting rid of the device enables in
> pci_assign_unassigned_resources() (for all the reasons already mentioned
> by others - scribbling over memory due to not being quiescent etc). But
> it's not worth breaking now. 2.5.x material. Most PCI drivers may a
On Thu, 7 Dec 2000, Russell King wrote:
> Linus Torvalds writes:
> > - me: UHCI drivers really need to enable bus mastering.
>
> But it'll already be turned on if pci_assign_unassigned_resources() is
> called. This calls pdev_enable_device for every single device, which
> turns on the bus
On Thu, 7 Dec 2000, Russell King wrote:
>
> Is it intentional that pci_assign_unassigned_resources should:
> 1. enable all devices?
> 2. enable bus master on all devices?
Probably intentional, but probably for all the wrong reasons.
The device enabling is still required for all drivers that a
> I think that Linus's patch is correct and that
> pci/setup_res.c::pdev_enable_device() shouldn't be doing this:
>
> /* ??? Always turn on bus mastering. If the device doesn't support
> it, the bit will go into the bucket. */
> cmd |= PCI_COMMAND_MASTER;
>
> First, the ???
> From: Russell King [mailto:[EMAIL PROTECTED]]
>
> Linus Torvalds writes:
> > - me: UHCI drivers really need to enable bus mastering.
>
> But it'll already be turned on if pci_assign_unassigned_resources() is
> called. This calls pdev_enable_device for every single device, which
> turns on
Linus Torvalds writes:
> - me: UHCI drivers really need to enable bus mastering.
But it'll already be turned on if pci_assign_unassigned_resources() is
called. This calls pdev_enable_device for every single device, which
turns on the bus master bit in the PCI command register.
Is it intenti
The only reason for this pre7 is to resolve some warring patches in the
cs46xx driver.
Linus
---
- test7:
- Kai Germaschewski: ymfpci cleanups and resource leak fixes
- me: UHCI drivers really need to enable bus mastering.
- Trond Myklebust: fix up nfs_writepage_sy
21 matches
Mail list logo
