mounted
read-only. So I have changed the patch to make umount not abort if
mtab is not writable and "-n" is not specified.
Get the updated patch at:
http://panopticon.csustan.edu/thood/readonly-root.html
--
Thomas Hood
-
To unsubscribe from this list: send the line "unsubscribe linu
for that file too.
util-linux-2.12q-symlinkmtab-10fstab_jdth20050709.patch
--
Thomas Hood
diff -uNr util-linux-2.12p_ORIG/mount/fstab.c util-linux-2.12p/mount/fstab.c
--- util-linux-2.12p_ORIG/mount/fstab.c 2004-12-21 20:09:24.0 +0100
+++ util-linux-2.12p/mount/fstab.c 2005-07-09 11:53
re/dev.c says that this
function should be called "under RTNL semaphore or @dev_base_lock", but
it is actually called under the ipx_interfaces_lock. Is this okay?
__dev_get_by_name() is also called from within ipxitf_ioctl(), seemingly
under no locks at all. Also okay?
Thomas Hood
-
To unsubscri
s I was able
to use IRQ 9 for other things without any obvious problems.
Perhaps this is only because I don't have ACPI support enabled.
Still, if I disable ACPI support then shouldn't I be able to use
IRQ 9 for other things? If so, shouldn't the kernel to refrain
from reserving t
This bug seems to be fixed in 2.4.2-ac16.
Thanks again to Arnaldo Carvalho de Melo.
Thomas
On 21 Feb 2001 I wrote:
> Update on the "unregister_netdevice" bug ...
>
> Arnaldo Carvalho de Melo found one bug but there
> remains another one that makes the dev->refcnt too
> high instead of too l
ic void __init pci_fixup_piix4_acpi(struct pci_dev *d)
< {
< /*
<* PIIX4 ACPI device: hardwired IRQ9
<*/
< d->irq = 9;
< }
What's going on?
Thomas Hood
jdthood_AT_yahoo.co.uk
-
To unsubscribe from this list: send the line "unsubscribe linu
I have seen the same sort of problem in the past.
My conclusion was that there was a problem with dynamic
registering and unregistering of ide interfaces.
Thomas Hood
jdthood_AT_yahoo.co.uk
> I've experienced some disk corruption on my laptop.
>
> Scenario:
> I'm c
created again.
My question is: Is there some better way of blocking
all open() calls to a particular device driver while
processes using it are being killed off?
Thomas Hood
___
Send a cool gift with your E-Card
http://www.bluemountain
d
> change ISA PnP device configurations when it can't do this
> itself? If so, could this perhaps be done by bringing the Hinds
> PnP BIOS driver into the kernel and interfacing isa-pnp to it?
>
> Thomas Hood
> jdthood_AT_yahoo.co.uk <- Change '_AT_' to
tpnp" commands.
Would it not be useful if the isa-pnp driver would fall back
to utilizing the PnP BIOS (if possible) in order to read and
change ISA PnP device configurations when it can't do this
itself? If so, could this perhaps be done by bringing the Hinds
PnP BIOS driver into the k
Update on the "unregister_netdevice" bug ...
Arnaldo Carvalho de Melo found one bug but there
remains another one that makes the dev->refcnt too
high instead of too low.
To be continued ...
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
appens when ipx is used, specifically when
auto_interface=on and auto_primary=on
2) It happens only or especially when using DHCP
3) It happens only to PCMCIA ethernet cards
Thomas Hood
jdthood_AT_yahoo.co.uk
Linux 2.4.1-ac10
/etc/pcmcia/network disabled with an 'exit 0'
command
Sorry, but it turns out that the bug is not completely
fixed by the change that acme made. With the change,
ifup-ing and if-downing eth0 with the ipx module loaded
no longer reduces eth0's refcnt to an indefinitely low
(larger and larger negative) number. However if the ipx
module is loaded firs
This bug was fixed by "acme" in 2.4.1-ac10. :)
The ipx driver now increments refcnt on NETDEV_UP to
match downing the interface on NETDEV_DOWN.
Thanks all.
Thomas
> Okay, I now know the cause of this problem. It's a bug in
> the ipx driver. (This also closes pcmcia-cs bug #126563.)
>
> Thro
> > Here is a patch which may not solve the underlying
>
> This does not. refcnt cannot be <1 at this point.
The refcnt shouldn't be less than 1, but it is in fact
less than 1. (As I'm sure you understand.)
> > assuming that the latter messages aren't serious?
>
> They are fatal. Machine m
gt;if_dev == dev)
__ipxitf_put(i);
i = tmp;
}
spin_unlock_bh(&ipx_interfaces_lock);
return NOTIFY_DONE;
}
--
--
Thomas Hood
Please reply to me at: jdthood_AT_yahoo.co.uk
I wrot
This problem has been resolved (sort of). See the follow up to
"[PATCH] to deal with bad dev->refcnt in unregister_netdevice()"
Thomas Hood
> Here is a patch which may not solve the underlying
> problem but which does prevent the kernel from
> generating an infinite nu
I presume that this change needs to be made.
(All of the drivers/net/pcmcia/*.c need the change.)
// Thomas
jdthood@thanatos:/usr/src/kernel-source-2.4.1-ac3/drivers/net/pcmcia# diff -Naur
xirc2ps_cs.c_ORIG xirc2ps_cs.c
--- xirc2ps_cs.c_ORIG Thu Feb 8 19:11:54 2001
+++ xirc2ps_cs.cTh
void the
"KERNEL: assertion(dev->ip_ptr==NULL)failed at
dev.c(2422):netdev_finish_unregister"
message and the occasional
"Freeing alive device"
message it seems to suffice that I kill the dhclient
process before running "ifdown eth0". Am I right in
assuming that the latter
kernel
usable for me.
I hope the networking gurus can find the real bug.
Thomas Hood
> I have a bit more information about this bug now.
> The message "assertion(yadda) failed ..." occurs only
> if the eth0 interface has been configured using pump
> or dhclient. If the card is
ccurs if the Xircom card is connected to
> the Ethernet (in which case it is configured using DHCP).
> If the card is left unconnected to the network, the problem
> does not occur---the card can be ejected.
>
> Thomas Hood
> Please cc: your replies to me at jdthood_AT_yahoo.co.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
I get this message when shutting down Linux with 2.4.1 kernel,
kernel PCMCIA support compiled as a module.
-
$ cat /proc/ioports
...
03e0-03e1 : i82365
...
$ sudo reboot
(reboot)
$ grep 3e0 /var/log/messages
Feb 4 1
P).
If the card is left unconnected to the network, the problem
does not occur---the card can be ejected.
Thomas Hood
Please cc: your replies to me at jdthood_AT_yahoo.co.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
then 2.4.0 . I have since tested kernel 2.2.17 and see the
same problem. Do I have a hardware problem, or might something
have changed in the kernel that could lead to this behavior?
Thomas Hood
jdthood_AT_yahoo.co.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&qu
g for eth0 to become free. Usage count =
-1"
messages every five seconds or so. "ps -A" reveals that
modprobe is running; it can't be killed even with "kill -9".
The "ifconfig" command locks up.
Thomas Hood
Please cc: your replies to me at jdthood_AT_mail.c
undant,
> since user-level can look at errno to see whether the
> ioctl succeeded.
rtnval is the APM BIOS return code whereas errno
is the ioctl return code.
Thanks
Thomas Hood
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
e would be
to export the address of the APM BIOS so that I
could call it myself from a kernel module.
Thomas Hood
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
27 matches
Mail list logo
