On Mon, 4 Dec 2000 17:31:04 -0500 ,
"Boerner, Brian" <[EMAIL PROTECTED]> wrote:
>The driver
>is generating a segmentation fault and produces and oops. I have included
>Code: 00 00 00 00 00 00 00 00 b8 00 00 00 83 ec 34 68 00 2c 82 c8
That code looks bad. I suspect you are using an old
On Mon, 4 Dec 2000 14:27:10 -0700,
Steven Cole <[EMAIL PROTECTED]> wrote:
>If I have the cs46xx driver compiled either as a module or into
>the kernel, then 2.4.0-test12-pre4 locks up when KDE 2.0
>is started.
>[snip]
>When I say the system freezes, I mean it completely locks up, and
>ALT-SYSRQ-
On Mon, 4 Dec 2000 16:26:42 -0500,
Wakko Warner <[EMAIL PROTECTED]> wrote:
>PCI patches that were added between pre3 and pre4 allow me to boot the
>kernel on my noritake alpha. Once it boots, however, it oops's in the
>swapper. I've tried a few times in the past to use ksymoops on oops's on
On Mon, 4 Dec 2000 16:26:42 -0500,
Wakko Warner [EMAIL PROTECTED] wrote:
PCI patches that were added between pre3 and pre4 allow me to boot the
kernel on my noritake alpha. Once it boots, however, it oops's in the
swapper. I've tried a few times in the past to use ksymoops on oops's on
the
On Mon, 4 Dec 2000 14:27:10 -0700,
Steven Cole [EMAIL PROTECTED] wrote:
If I have the cs46xx driver compiled either as a module or into
the kernel, then 2.4.0-test12-pre4 locks up when KDE 2.0
is started.
[snip]
When I say the system freezes, I mean it completely locks up, and
On Mon, 4 Dec 2000 17:31:04 -0500 ,
"Boerner, Brian" [EMAIL PROTECTED] wrote:
The driver
is generating a segmentation fault and produces and oops. I have included
Code: 00 00 00 00 00 00 00 00 b8 00 00 00 83 ec 34 68 00 2c 82 c8
That code looks bad. I suspect you are using an old modutils on
On Mon, 4 Dec 2000 20:39:29 -0500,
Wakko Warner [EMAIL PROTECTED] wrote:
Keith Owens wrote
Is there any chance of changing arch/alpha/kernel/traps.c to print
registers, trace and _raw_ code, in that order so it is more like other
architectures? You can print the decoded instructions as well
On Mon, 04 Dec 2000 07:29:10 +1100,
Keith Owens <[EMAIL PROTECTED]> wrote:
>On Sun, 3 Dec 2000 07:43:01 -0600 (CST),
>Jeff Garzik <[EMAIL PROTECTED]> wrote:
>>On Sun, 3 Dec 2000, Keith Owens wrote:
>>> If you go down this path, please add a standard performan
On Sun, 3 Dec 2000 07:43:01 -0600 (CST),
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>On Sun, 3 Dec 2000, Keith Owens wrote:
>> If you go down this path, please add a standard performance monitoring
>> method to query the current capacity of an interface.
>Well, ethtool inte
On Sun, 3 Dec 2000 07:43:01 -0600 (CST),
Jeff Garzik [EMAIL PROTECTED] wrote:
On Sun, 3 Dec 2000, Keith Owens wrote:
If you go down this path, please add a standard performance monitoring
method to query the current capacity of an interface.
Well, ethtool interface supports reporting media
On Mon, 04 Dec 2000 07:29:10 +1100,
Keith Owens [EMAIL PROTECTED] wrote:
On Sun, 3 Dec 2000 07:43:01 -0600 (CST),
Jeff Garzik [EMAIL PROTECTED] wrote:
On Sun, 3 Dec 2000, Keith Owens wrote:
If you go down this path, please add a standard performance monitoring
method to query the current
On Sat, 2 Dec 2000 13:07:29 -0600 (CST),
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>If yes, my guess is correct, I think the proper solution is to:
>* create a generic set_config, which does nothing but convert the calls'
>semantics into ethtool semantics, and
>* add ethtool support to the specific
On Sat, 2 Dec 2000 13:07:29 -0600 (CST),
Jeff Garzik [EMAIL PROTECTED] wrote:
If yes, my guess is correct, I think the proper solution is to:
* create a generic set_config, which does nothing but convert the calls'
semantics into ethtool semantics, and
* add ethtool support to the specific
On Fri, 1 Dec 2000 10:52:35 -0800 (PST),
Al Peat <[EMAIL PROTECTED]> wrote:
> I've followed the thread on "Persistent module
>storage" but haven't come across a general explanation
>of the changes to the inter-module symbol stuff
>between 2.4test10 and test11. Anyone care to comment
>on the
On Fri, 01 Dec 2000 09:41:58 -0700,
Roger Crandell <[EMAIL PROTECTED]> wrote:
>Killing interrupt handler
>scheduling in interrupt
>
>The kernel logs nothing and you must reset the machine to bring it back
linux/Documentation/oops-tracing.txt
linux/Documentation/serial-console.txt
-
To
On Fri, 1 Dec 2000 14:52:11 + (GMT),
John Levon <[EMAIL PROTECTED]> wrote:
>Probably you have modversions enabled (CONFIG_MODVERSION=y). Disable that
>and try again, or build as modules. 2.4 fixed this problem in the proper
>way, but I don't know what's going to happen about 2.2 ...
I have
On Fri, 1 Dec 2000 14:52:11 + (GMT),
John Levon [EMAIL PROTECTED] wrote:
Probably you have modversions enabled (CONFIG_MODVERSION=y). Disable that
and try again, or build as modules. 2.4 fixed this problem in the proper
way, but I don't know what's going to happen about 2.2 ...
I have sent
On Fri, 01 Dec 2000 09:41:58 -0700,
Roger Crandell [EMAIL PROTECTED] wrote:
Killing interrupt handler
scheduling in interrupt
The kernel logs nothing and you must reset the machine to bring it back
linux/Documentation/oops-tracing.txt
linux/Documentation/serial-console.txt
-
To unsubscribe
On Fri, 1 Dec 2000 10:52:35 -0800 (PST),
Al Peat [EMAIL PROTECTED] wrote:
I've followed the thread on "Persistent module
storage" but haven't come across a general explanation
of the changes to the inter-module symbol stuff
between 2.4test10 and test11. Anyone care to comment
on the
On Wed, 29 Nov 2000 22:49:29 -0600 (CST),
Dmitri Matrosov <[EMAIL PROTECTED]> wrote:
>i got these modprobing module bttv on linux2.4.0-test11, when loading it
>at startup machine hangs oopsing in endless loop.
grep modutils linux/Documentation/Changes
-
To unsubscribe from this list: send the
Linus, please apply.
The kernel incorrectly defines Elf64_Word and Elf64_Sword as 8 bytes,
they should be 4 bytes, Elf64_Xword and Elf64_Sxword are the 8 byte
versions. The type mismatch between kernel and user space causes field
misalignments if you copy a user space definition into the kernel
Linus, please apply.
The kernel incorrectly defines Elf64_Word and Elf64_Sword as 8 bytes,
they should be 4 bytes, Elf64_Xword and Elf64_Sxword are the 8 byte
versions. The type mismatch between kernel and user space causes field
misalignments if you copy a user space definition into the kernel
On Wed, 29 Nov 2000 01:37:22 +0100,
Kurt Garloff <[EMAIL PROTECTED]> wrote:
>this is a 2.4.0-test11 system;
>rmmod -a (modutils-2.3.21) fails to unload unused autocleanable modules:
Designed behaviour. sys_delete_module only removes autoclean modules
that have been used at least once, either
On Tue, 28 Nov 2000 17:53:48 -0600,
Peter Samuelson <[EMAIL PROTECTED]> wrote:
>Binary patching? If you are binary patching something you need to get
>the exact location, one way or another. Whatever tool you use to
>extract the location of a symbol in an object file, that same tool
>should
On Tue, 28 Nov 2000 20:22:59 +0100,
Kurt Garloff <[EMAIL PROTECTED]> wrote:
>Find attached the modules.dep that caused this: There is a circular
>dependency of pppoe on pppox on pppoe on
The kernel code is broken. Circular dependencies make no sense, the
pppoe maintainer agrees and I
On Tue, 28 Nov 2000 20:22:59 +0100,
Kurt Garloff [EMAIL PROTECTED] wrote:
Find attached the modules.dep that caused this: There is a circular
dependency of pppoe on pppox on pppoe on
The kernel code is broken. Circular dependencies make no sense, the
pppoe maintainer agrees and I thought
On Tue, 28 Nov 2000 17:53:48 -0600,
Peter Samuelson [EMAIL PROTECTED] wrote:
Binary patching? If you are binary patching something you need to get
the exact location, one way or another. Whatever tool you use to
extract the location of a symbol in an object file, that same tool
should tell you
On Wed, 29 Nov 2000 01:37:22 +0100,
Kurt Garloff [EMAIL PROTECTED] wrote:
this is a 2.4.0-test11 system;
rmmod -a (modutils-2.3.21) fails to unload unused autocleanable modules:
Designed behaviour. sys_delete_module only removes autoclean modules
that have been used at least once, either they
On Mon, 27 Nov 2000 16:02:13 -0600,
Peter Samuelson <[EMAIL PROTECTED]> wrote:
>
> [Albert D. Cahalan]
>> > Somebody else posted a reasonable hack for the [<>] problem. His
>> > proposal involved letting multiple values share the same markers,
>> > something like this:
>Me too. (: Keith posed
On Mon, 27 Nov 2000 07:36:22 -0600 (CST),
Chad Schwartz <[EMAIL PROTECTED]> wrote:
>int main(void) {
> printf("Size of an unsigned long is %d bytes\n",sizeof(unsigned long));
> return(0);
>}
>
>That simple program will tell you that an unsigned long is 4 bytes, or 8
>bytes.
>
>It is
On Mon, 27 Nov 2000 07:36:22 -0600 (CST),
Chad Schwartz [EMAIL PROTECTED] wrote:
int main(void) {
printf("Size of an unsigned long is %d bytes\n",sizeof(unsigned long));
return(0);
}
That simple program will tell you that an unsigned long is 4 bytes, or 8
bytes.
It is then a safe
On Mon, 27 Nov 2000 16:02:13 -0600,
Peter Samuelson [EMAIL PROTECTED] wrote:
[Albert D. Cahalan]
Somebody else posted a reasonable hack for the [] problem. His
proposal involved letting multiple values share the same markers,
something like this:
Me too. (: Keith posed two objections:
On Sun, 26 Nov 2000 19:49:43 -0700,
"Jeff V. Merkey" <[EMAIL PROTECTED]> wrote:
>Microsoft drivers have an .INIT code section that is initialization
>ccode that get's chunked after it's loaded. Their model allows
>memory segments to be defined as DISCARDABLE, which tells the loader
>to chunk
On Sun, 26 Nov 2000 17:01:35 -0700,
"Jeff V. Merkey" <[EMAIL PROTECTED]> wrote:
>insmod ppp_deflate (should trigger load of all these modules). I
>know it's works this way if there's a modules.dep file laying
>around, but it would be nice for it to work this way without
>needing the external
On Sun, 26 Nov 2000 16:36:55 -0700,
"Jeff V. Merkey" <[EMAIL PROTECTED]> wrote:
>Keith,
>
>Please consider the attached patch for inclusion in all future versions
>of the modutils depmod program for compatiblity with RedHat and
>RedHat derived Linux distributions.
I have a big problem with
On Sun, 26 Nov 2000 07:30:44 -0800,
"Adam J. Richter" <[EMAIL PROTECTED]> wrote:
> In reading include/linux/init.h, I was surprised to discover
>that __init{,data} expands to nothing when compiling a module.
>I was wondering if anyone is contemplating adding support for
>__init{,data} in
On Sun, 26 Nov 2000 07:30:44 -0800,
"Adam J. Richter" [EMAIL PROTECTED] wrote:
In reading include/linux/init.h, I was surprised to discover
that __init{,data} expands to nothing when compiling a module.
I was wondering if anyone is contemplating adding support for
__init{,data} in module
On Sun, 26 Nov 2000 16:36:55 -0700,
"Jeff V. Merkey" [EMAIL PROTECTED] wrote:
Keith,
Please consider the attached patch for inclusion in all future versions
of the modutils depmod program for compatiblity with RedHat and
RedHat derived Linux distributions.
I have a big problem with Redhat.
On Sun, 26 Nov 2000 17:01:35 -0700,
"Jeff V. Merkey" [EMAIL PROTECTED] wrote:
insmod ppp_deflate (should trigger load of all these modules). I
know it's works this way if there's a modules.dep file laying
around, but it would be nice for it to work this way without
needing the external text
On Sun, 26 Nov 2000 19:49:43 -0700,
"Jeff V. Merkey" [EMAIL PROTECTED] wrote:
Microsoft drivers have an .INIT code section that is initialization
ccode that get's chunked after it's loaded. Their model allows
memory segments to be defined as DISCARDABLE, which tells the loader
to chunk them
On Sat, 25 Nov 2000 21:10:19 -0800 (PST),
Andre Hedrick <[EMAIL PROTECTED]> wrote:
>On Sun, 26 Nov 2000, John Alvord wrote:
>> It also says "I do not know much about the details of the kernel C
>> environment. In particular I do not know that all static variables are
>> initialized to 0 in the
On Sat, 25 Nov 2000 14:20:39 -0800,
"Android" <[EMAIL PROTECTED]> wrote:
>There is a link in /lib/modules/2.4.0.11: build->/usr/src/linux
>created by the Makefile (make modules_install).
>What for? depmod doesn't like this link. It gets confused.
grep modutils Documentation/Changes
-
To
On Sat, 25 Nov 2000 15:59:30 +0200,
Oren Held <[EMAIL PROTECTED]> wrote:
>I patched my test10 directly to test11 (I didn't use the PREs, so I
>can't
Upgrade to modutils 2.3.21.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Sat, 25 Nov 2000 14:18:30 +0100,
"J . A . Magallon" <[EMAIL PROTECTED]> wrote:
>On Sat, 25 Nov 2000 02:58:37 Keith Owens wrote:
>> 2.5 kernel build wish list[1] has a couple of entries for standardising
>> the install targets. My thinking (and I
On Sat, 25 Nov 2000 12:27:24 + (GMT),
Russell King <[EMAIL PROTECTED]> wrote:
>Keith Owens writes:
>> On Sat, 25 Nov 2000 06:10:54 -0500 (EST),
>> [EMAIL PROTECTED] (Steven S. Dick) wrote:
>> >2.4.0-test11-pre1 seems to have broken something.
>> >I h
On Sat, 25 Nov 2000 05:26:20 -0500 (EST),
"Albert D. Cahalan" <[EMAIL PROTECTED]> wrote:
>Somebody else posted a reasonable hack for the [<>] problem.
>His proposal involved letting multiple values share the same
>markers, something like this:
>
>[]
What happens if the line is wrapped before
On Sat, 25 Nov 2000 05:26:20 -0500 (EST),
"Albert D. Cahalan" [EMAIL PROTECTED] wrote:
Somebody else posted a reasonable hack for the [] problem.
His proposal involved letting multiple values share the same
markers, something like this:
[c19a5cb4 c180234c c1801134 c1706550 c1800248 c1603310
On Sat, 25 Nov 2000 12:27:24 + (GMT),
Russell King [EMAIL PROTECTED] wrote:
Keith Owens writes:
On Sat, 25 Nov 2000 06:10:54 -0500 (EST),
[EMAIL PROTECTED] (Steven S. Dick) wrote:
2.4.0-test11-pre1 seems to have broken something.
I have no problems with test10, but test11-pre1 gives
On Sat, 25 Nov 2000 14:18:30 +0100,
"J . A . Magallon" [EMAIL PROTECTED] wrote:
On Sat, 25 Nov 2000 02:58:37 Keith Owens wrote:
2.5 kernel build wish list[1] has a couple of entries for standardising
the install targets. My thinking (and I know that some peopl
On Sat, 25 Nov 2000 15:59:30 +0200,
Oren Held [EMAIL PROTECTED] wrote:
I patched my test10 directly to test11 (I didn't use the PREs, so I
can't
Upgrade to modutils 2.3.21.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Sat, 25 Nov 2000 14:20:39 -0800,
"Android" [EMAIL PROTECTED] wrote:
There is a link in /lib/modules/2.4.0.11: build-/usr/src/linux
created by the Makefile (make modules_install).
What for? depmod doesn't like this link. It gets confused.
grep modutils Documentation/Changes
-
To unsubscribe
On Sat, 25 Nov 2000 21:10:19 -0800 (PST),
Andre Hedrick [EMAIL PROTECTED] wrote:
On Sun, 26 Nov 2000, John Alvord wrote:
It also says "I do not know much about the details of the kernel C
environment. In particular I do not know that all static variables are
initialized to 0 in the kernel
On 24 Nov 2000 16:40:50 -0700,
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
>Peter Samuelson <[EMAIL PROTECTED]> writes:
>
>> [Matt D. Robinson]
>> > Any way we can standardize 'make install' in the kernel? It's
>> > disturbing to have different install mechanisms per platform ...
>> > I can
On Fri, 24 Nov 2000 15:37:33 -0800,
"Adam J. Richter" <[EMAIL PROTECTED]> wrote:
> Note that this is not a "final" version. I plan to go
>through all of the changes and bracket all of these new tables
>with #ifdef MODULE...#endif so they do not result in complaints
>about the table being
On Fri, 24 Nov 2000 10:55:39 +,
Mark Ellis <[EMAIL PROTECTED]> wrote:
>Hi all, consistently getting the following when pppd is terminated. Happens
>in 2.4.0-test11, fine in 2.4.0-test9, don't know about test10. Same happens
>for pppd 2.4.0b4 and 2.4.0, both recompiled for test11. Is this
On Thu, 23 Nov 2000 23:09:18 +0200 (EET),
Pekka Savola <[EMAIL PROTECTED]> wrote:
>EIP:0010:[de4x5:de4x5_probe+24259/37172]
>Note! EIP shows de4x5 for some reason. Please note that de4x5 driver
Because klogd tried to convert the oops and made a complete mess of it.
Always start klogd as
On Thu, 23 Nov 2000 13:36:35 -0500,
Steven Lembark <[EMAIL PROTECTED]> wrote:
>make[1]: Leaving directory `/usr/src/linux-2.4.0-test11/arch/i386/lib'
>cd /lib/modules/2.4.0-test11; \
>mkdir -p pcmcia; \
>find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
>if [ -r
On Thu, 23 Nov 2000 13:36:35 -0500,
Steven Lembark [EMAIL PROTECTED] wrote:
make[1]: Leaving directory `/usr/src/linux-2.4.0-test11/arch/i386/lib'
cd /lib/modules/2.4.0-test11; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ];
On Thu, 23 Nov 2000 23:09:18 +0200 (EET),
Pekka Savola [EMAIL PROTECTED] wrote:
EIP:0010:[de4x5:de4x5_probe+24259/37172]
Note! EIP shows de4x5 for some reason. Please note that de4x5 driver
Because klogd tried to convert the oops and made a complete mess of it.
Always start klogd as "klogd
On Fri, 24 Nov 2000 10:55:39 +,
Mark Ellis [EMAIL PROTECTED] wrote:
Hi all, consistently getting the following when pppd is terminated. Happens
in 2.4.0-test11, fine in 2.4.0-test9, don't know about test10. Same happens
for pppd 2.4.0b4 and 2.4.0, both recompiled for test11. Is this related
On Fri, 24 Nov 2000 15:37:33 -0800,
"Adam J. Richter" [EMAIL PROTECTED] wrote:
Note that this is not a "final" version. I plan to go
through all of the changes and bracket all of these new tables
with #ifdef MODULE...#endif so they do not result in complaints
about the table being
On 24 Nov 2000 16:40:50 -0700,
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
Peter Samuelson [EMAIL PROTECTED] writes:
[Matt D. Robinson]
Any way we can standardize 'make install' in the kernel? It's
disturbing to have different install mechanisms per platform ...
I can make the changes
On Thu, 23 Nov 2000 02:25:33 -0500,
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>Keith Owens wrote:
>> #define PCITBL(v,d,sv,sd) \
>> { PCI_VENDOR_ID_##v, PCI_DEVICE_ID_##d, \
>>PCI_VENDOR_ID_##sv, PCI_DEVICE_ID_##sd }
>
>* your macro fails for the 'AN
[Adam J. Richter]
> +static struct pci_device_id atp870u_pci_tbl[] __initdata = {
> +{vendor: 0x1191, device: 0x8002, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
> +{vendor: 0x1191, device: 0x8010, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
It would make it easier to read and safer to
This patch needs to be reviewed before it goes to Linus.
The ELF 64 bit spec defines
NameSizeAlignment Purpose
Elf64_Addr8 8 Unsigned program address
Elf64_Off 8 8 Unsigned file offset
Elf64_Half2 2
On Wed, 22 Nov 2000 21:54:48 -0500 (EST),
"Albert D. Cahalan" <[EMAIL PROTECTED]> wrote:
>Under NO circumstances should klogd or ksymoops mangle the
>original oops. The raw oops data MUST be completely preserved.
>It is a serious bug that this is not what currently happens.
ksymoops prints the
On Wed, 22 Nov 2000 20:58:28 -0500 (EST),
"Albert D. Cahalan" <[EMAIL PROTECTED]> wrote:
>The infamous LINK_FIRST infrastructure was sort of half-way done.
>
>It would be best to cause drivers with an unspecified link order
>to move around a bit, so that errors may be discovered more quickly.
On Thu, 23 Nov 2000 02:49:27 +0100,
Frank van de Pol <[EMAIL PROTECTED]> wrote:
>After upgrade to 2.4.0-test11 my copy of ALSA 0.6pre1 (cvs version) stopped
>working (causing OOPS on module load of snd-card-sbawe). I reverted back to
>2.4.0-test10 and verified that the problem does not exist in
On Wed, 22 Nov 2000 23:12:25 + (GMT),
Russell King <[EMAIL PROTECTED]> wrote:
>if (copy_from_user(mod+1, mod_user+1, mod->size-sizeof(*mod))) {
Using sizeof(struct module) is a nono in sys_init_module(), the code
has to use the user space size. Does this untested patch fix the
On Wed, 22 Nov 2000 14:42:05 +0100,
Christian Gennerat <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] a écrit :
>
>> I also left something else
>> that always annoyed me: valuable screen space (on a 24x80 vt)
>> is lost by these silly [< >] around addresses in an Oops.
>> They provide no
This is the "never release a security fix in a hurry" release. The
security fixes in modutils 2.3.20 had some side effects on some config
files. Linus knocked back environment variable MOD_SAFEMODE, instead
the kernel propagates the real uid that caused modprobe to be invoked.
On Wed, 22 Nov 2000 09:57:02 +0100,
Christian Gennerat <[EMAIL PROTECTED]> wrote:
>The problem is in modules.conf
>Most users do not use "depfile" and "path" commands
>So they have not seen this problem.
>
>This was true for modutils-2.3.19, and older versions.
>With modutils-2.3.20 the syntax
This is the "never release a security fix in a hurry" release. The
security fixes in modutils 2.3.20 had some side effects on some config
files. Linus knocked back environment variable MOD_SAFEMODE, instead
the kernel propagates the real uid that caused modprobe to be invoked.
On Wed, 22 Nov 2000 23:12:25 + (GMT),
Russell King [EMAIL PROTECTED] wrote:
if (copy_from_user(mod+1, mod_user+1, mod-size-sizeof(*mod))) {
Using sizeof(struct module) is a nono in sys_init_module(), the code
has to use the user space size. Does this untested patch fix the
problem?
On Thu, 23 Nov 2000 02:49:27 +0100,
Frank van de Pol [EMAIL PROTECTED] wrote:
After upgrade to 2.4.0-test11 my copy of ALSA 0.6pre1 (cvs version) stopped
working (causing OOPS on module load of snd-card-sbawe). I reverted back to
2.4.0-test10 and verified that the problem does not exist in that
On Wed, 22 Nov 2000 20:58:28 -0500 (EST),
"Albert D. Cahalan" [EMAIL PROTECTED] wrote:
The infamous LINK_FIRST infrastructure was sort of half-way done.
It would be best to cause drivers with an unspecified link order
to move around a bit, so that errors may be discovered more quickly.
The
On Wed, 22 Nov 2000 21:54:48 -0500 (EST),
"Albert D. Cahalan" [EMAIL PROTECTED] wrote:
Under NO circumstances should klogd or ksymoops mangle the
original oops. The raw oops data MUST be completely preserved.
It is a serious bug that this is not what currently happens.
ksymoops prints the
This patch needs to be reviewed before it goes to Linus.
The ELF 64 bit spec defines
NameSizeAlignment Purpose
Elf64_Addr8 8 Unsigned program address
Elf64_Off 8 8 Unsigned file offset
Elf64_Half2 2
[Adam J. Richter]
+static struct pci_device_id atp870u_pci_tbl[] __initdata = {
+{vendor: 0x1191, device: 0x8002, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
+{vendor: 0x1191, device: 0x8010, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
It would make it easier to read and safer to type
On Thu, 23 Nov 2000 02:25:33 -0500,
Jeff Garzik [EMAIL PROTECTED] wrote:
Keith Owens wrote:
#define PCITBL(v,d,sv,sd) \
{ PCI_VENDOR_ID_##v, PCI_DEVICE_ID_##d, \
PCI_VENDOR_ID_##sv, PCI_DEVICE_ID_##sd }
* your macro fails for the 'ANY' case, because the proper macro is
PCI_ANY_ID
On Wed, 22 Nov 2000 09:57:02 +0100,
Christian Gennerat [EMAIL PROTECTED] wrote:
The problem is in modules.conf
Most users do not use "depfile" and "path" commands
So they have not seen this problem.
This was true for modutils-2.3.19, and older versions.
With modutils-2.3.20 the syntax have
On Tue, 21 Nov 2000 20:17:47 -0700,
"Jeff V. Merkey" <[EMAIL PROTECTED]> wrote:
>Was there a reason we removed the -i and -m options from newer modutils
>and broke backwards caompatibility? I'm re-writing our module build
>scripts for the installer, and I discovered after upgrading to 2.3.20,
On Tue, 21 Nov 2000 20:17:47 -0700,
"Jeff V. Merkey" [EMAIL PROTECTED] wrote:
Was there a reason we removed the -i and -m options from newer modutils
and broke backwards caompatibility? I'm re-writing our module build
scripts for the installer, and I discovered after upgrading to 2.3.20,
that
On Mon, 20 Nov 2000 22:11:04 -0600,
Matthew Vanecek <[EMAIL PROTECTED]> wrote:
>Hi. I see these warnings while compiling modules in 2.4.0-test10. This
>is with RH 7.0's kgcc (why-oh-why did they base their system on
>2.96!!). It doesn't seem to break anything--I'm just curious as to what
>the
On Mon, 20 Nov 2000 22:11:04 -0600,
Matthew Vanecek [EMAIL PROTECTED] wrote:
Hi. I see these warnings while compiling modules in 2.4.0-test10. This
is with RH 7.0's kgcc (why-oh-why did they base their system on
2.96!!). It doesn't seem to break anything--I'm just curious as to what
the
On Sun, 19 Nov 2000 20:03:52 +0100 (CET),
Gerd Knorr <[EMAIL PROTECTED]> wrote:
>On Mon, 20 Nov 2000, Keith Owens wrote:
>> On my list for 2.5. If foo is declared as MODULE_PARM in object bar
>> then you will be able to boot with bar.foo=27 or even foo=27 as long as
>
On Sun, 19 Nov 2000 07:16:52 -0800 (PST),
David Lang <[EMAIL PROTECTED]> wrote:
>there is a rootkit kernel module out there that, if loaded onto your
>system, can make it almost impossible to detect that your system has been
>compramised. with module support disabled this isn't possible.
Wrong.
On 19 Nov 2000 12:56:17 GMT,
[EMAIL PROTECTED] (Gerd Knorr) wrote:
>Some generic way to make module args available as kernel args too
>would be nice. Or at least some simple one-liner I could put next to
>the MODULE_PARM() macro...
On my list for 2.5. If foo is declared as MODULE_PARM in
On Sun, 19 Nov 2000 20:28:39 +1100,
Vincent <[EMAIL PROTECTED]> wrote:
>Nov 19 19:46:47 darkstar kernel: Unable to handle kernel paging request
>at virtual address dfdfdfc4
>Nov 19 19:46:47 darkstar kernel: *pde =
>EIP: 0010:[]
See linux/REPORTING-BUGS.
-
To unsubscribe from this
On Sat, 18 Nov 2000 18:50:00 +0100 (MET),
[EMAIL PROTECTED] (Rogier Wolff) wrote:
>Compile a kernel, marking "sx" and "riscom8" as modules.
>
>Install, modprobe sx, and voila, you'll pull in the riscom because
>its "block_til_ready" static was found to satisfy the block_til_ready
>from
On Sat, 18 Nov 2000 18:50:00 +0100 (MET),
[EMAIL PROTECTED] (Rogier Wolff) wrote:
Compile a kernel, marking "sx" and "riscom8" as modules.
Install, modprobe sx, and voila, you'll pull in the riscom because
its "block_til_ready" static was found to satisfy the block_til_ready
from
On Sun, 19 Nov 2000 20:28:39 +1100,
Vincent [EMAIL PROTECTED] wrote:
Nov 19 19:46:47 darkstar kernel: Unable to handle kernel paging request
at virtual address dfdfdfc4
Nov 19 19:46:47 darkstar kernel: *pde =
EIP: 0010:[c486d5a7]
See linux/REPORTING-BUGS.
-
To unsubscribe from this
On 19 Nov 2000 12:56:17 GMT,
[EMAIL PROTECTED] (Gerd Knorr) wrote:
Some generic way to make module args available as kernel args too
would be nice. Or at least some simple one-liner I could put next to
the MODULE_PARM() macro...
On my list for 2.5. If foo is declared as MODULE_PARM in object
On Sun, 19 Nov 2000 07:16:52 -0800 (PST),
David Lang [EMAIL PROTECTED] wrote:
there is a rootkit kernel module out there that, if loaded onto your
system, can make it almost impossible to detect that your system has been
compramised. with module support disabled this isn't possible.
Wrong.
On Sun, 19 Nov 2000 20:03:52 +0100 (CET),
Gerd Knorr [EMAIL PROTECTED] wrote:
On Mon, 20 Nov 2000, Keith Owens wrote:
On my list for 2.5. If foo is declared as MODULE_PARM in object bar
then you will be able to boot with bar.foo=27 or even foo=27 as long as
variable foo is unique amongst all
On Sat, 18 Nov 2000 03:07:47 -0800 (PST),
Anil Kumar Prasad <[EMAIL PROTECTED]> wrote:
>sorry i didn't ask the question properly. I need to
>know how does kernel modules accept run time arguments
>from user?
MODULE_PARM(variable, type) in the code. It defines which variables
can be set on the
On Sat, 18 Nov 2000 02:10:40 -0800 (PST),
Anil Kumar Prasad <[EMAIL PROTECTED]> wrote:
>can anybody tell how to pass argument to modules?
RTFM. man modprobe. man insmod. man modules.conf.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Sat, 18 Nov 2000 02:10:40 -0800 (PST),
Anil Kumar Prasad [EMAIL PROTECTED] wrote:
can anybody tell how to pass argument to modules?
RTFM. man modprobe. man insmod. man modules.conf.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Sat, 18 Nov 2000 03:07:47 -0800 (PST),
Anil Kumar Prasad [EMAIL PROTECTED] wrote:
sorry i didn't ask the question properly. I need to
know how does kernel modules accept run time arguments
from user?
MODULE_PARM(variable, type) in the code. It defines which variables
can be set on the
On Sat, 18 Nov 2000 00:15:35 -0500,
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>What is the difference between a module that exports no symbols and
>includes EXPORT_NO_SYMBOLS reference, and such a module that lacks
>EXPORT_NO_SYMBOLS?
When modules were first introduced, all symbols were
801 - 900 of 1347 matches
Mail list logo
