[BUG?] vtund broken by tun driver changes in 2.4.6
I recently upgraded a server running vtund 2.4 (4/18/01) to stock 2.4.6 kernel. It seems the changes to the tun driver have broken vtund. Now my syslog gets filled with the following messages when a client attempts to connect: Jul 5 10:15:53 mackman vtund[4011]: Session mackman-vpn[64.169.117.25:2359] opened Jul 5 10:15:53 mackman vtund[4011]: Can't allocate tun device. File descriptor in bad state(77) Jul 5 10:15:53 mackman vtund[4011]: Session mackman-vpn closed Jul 5 10:16:04 mackman vtund[4014]: Session mackman-vpn[64.169.117.25:2360] opened Jul 5 10:16:04 mackman vtund[4014]: Can't allocate tun device. File descriptor in bad state(77) Jul 5 10:16:04 mackman vtund[4014]: Session mackman-vpn closed Eventually the client gives up. Do you have any suggestions or know of any fixes? Thanks, Ryan Mack - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[BUG?] vtund broken by tun driver changes in 2.4.6
I recently upgraded a server running vtund 2.4 (4/18/01) to stock 2.4.6 kernel. It seems the changes to the tun driver have broken vtund. Now my syslog gets filled with the following messages when a client attempts to connect: Jul 5 10:15:53 mackman vtund[4011]: Session mackman-vpn[64.169.117.25:2359] opened Jul 5 10:15:53 mackman vtund[4011]: Can't allocate tun device. File descriptor in bad state(77) Jul 5 10:15:53 mackman vtund[4011]: Session mackman-vpn closed Jul 5 10:16:04 mackman vtund[4014]: Session mackman-vpn[64.169.117.25:2360] opened Jul 5 10:16:04 mackman vtund[4014]: Can't allocate tun device. File descriptor in bad state(77) Jul 5 10:16:04 mackman vtund[4014]: Session mackman-vpn closed Eventually the client gives up. Do you have any suggestions or know of any fixes? Thanks, Ryan Mack - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
SCSI errors using USB mass storage device
Hello, I'm running unmodified 2.4.5 on a Red Hat 7.1 system and have an IBM DiskOnKey (a USB not-so-mass storage device). When mounting the device, the SCSI layer responds with the error: SCSI error: host 1 id 0 lun 0 return code = 802 Sense class 7, sense error 0, extended sense 0 The device seems to work fine, and I have experienced no data corruption or other problems. I was wondering what the cause of this error was and if it should be taken as a warning of potential data loss. Thanks, Ryan Mack - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
SCSI errors using USB mass storage device
Hello, I'm running unmodified 2.4.5 on a Red Hat 7.1 system and have an IBM DiskOnKey (a USB not-so-mass storage device). When mounting the device, the SCSI layer responds with the error: SCSI error: host 1 id 0 lun 0 return code = 802 Sense class 7, sense error 0, extended sense 0 The device seems to work fine, and I have experienced no data corruption or other problems. I was wondering what the cause of this error was and if it should be taken as a warning of potential data loss. Thanks, Ryan Mack - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA
I have a 3c595 CardBus card and a Lucent Orinoco card under pcmcia-cs I used the following drivers: pcmcia_core, ds, and (I think) cs for low level stuff, i82365 for the controller, cb_enabler and 3c595_cb for the 3c595, and wvlan_cs for the Orinoco under the kernel pcmcia support, I use: pcmcia_core and ds for low level stuff, yenta_socket for the controller, 3c59x (same driver as PCI) for the 3c595, and hermes and orinoco_cs for the Orinoco Now after awhile I figured out what new drivers I should start using, but I have a few things about the change that still confuse me... First, why have I stopped needing cs and cb_enabler? Second, why is yenta_socket only compiled if I enable CardBus support in the kernel? I'm running an Orinoco card on another machine, and since I don't think it's CardBus (am I wrong?), I didn't enable CB in the kernel. The i82365 driver is the only one compiled, but it seems to work fine on that machine. Should I enable CardBus support and use yenta_socket instead? Third, on the first machine with both cards, neither card works if I use i82365 instead of yenta_socket, why? The Orinoco gets Tx timeouts on every packet, and inserting the 3c595 causes the controller (socket) to time out waiting for reset and it doesn't recognize the 3c595. Despite the confusion of changing systems, I must say that the orinoco driver works much better than wvlan_cs for me, as the two Orinoco cards in IBSS Ad-Hoc mode would get intermittent Tx timeouts with the wvlan_cs driver. It's also nice not to have to rebuild pcmcia-cs when I upgrade my kernel anymore. Keep up the good work! Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA
I have a 3c595 CardBus card and a Lucent Orinoco card under pcmcia-cs I used the following drivers: pcmcia_core, ds, and (I think) cs for low level stuff, i82365 for the controller, cb_enabler and 3c595_cb for the 3c595, and wvlan_cs for the Orinoco under the kernel pcmcia support, I use: pcmcia_core and ds for low level stuff, yenta_socket for the controller, 3c59x (same driver as PCI) for the 3c595, and hermes and orinoco_cs for the Orinoco Now after awhile I figured out what new drivers I should start using, but I have a few things about the change that still confuse me... First, why have I stopped needing cs and cb_enabler? Second, why is yenta_socket only compiled if I enable CardBus support in the kernel? I'm running an Orinoco card on another machine, and since I don't think it's CardBus (am I wrong?), I didn't enable CB in the kernel. The i82365 driver is the only one compiled, but it seems to work fine on that machine. Should I enable CardBus support and use yenta_socket instead? Third, on the first machine with both cards, neither card works if I use i82365 instead of yenta_socket, why? The Orinoco gets Tx timeouts on every packet, and inserting the 3c595 causes the controller (socket) to time out waiting for reset and it doesn't recognize the 3c595. Despite the confusion of changing systems, I must say that the orinoco driver works much better than wvlan_cs for me, as the two Orinoco cards in IBSS Ad-Hoc mode would get intermittent Tx timeouts with the wvlan_cs driver. It's also nice not to have to rebuild pcmcia-cs when I upgrade my kernel anymore. Keep up the good work! Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[QUESTION] 2.4.3: hotplug_path unresolved in usbcore?
Sorry for such a stupid question, but I'm stumped (it doesn't take much). modprobe reports that hotplug_path is unresolved when it processes usbcore. CONFIG_HOTPLUG is defined, so it seems that hotplug_path is defined and EXPORTed in kernel/kmod.c, so I'm unsure what the problem is. Thanks, Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[QUESTION] 2.4.3: hotplug_path unresolved in usbcore?
Sorry for such a stupid question, but I'm stumped (it doesn't take much). modprobe reports that hotplug_path is unresolved when it processes usbcore. CONFIG_HOTPLUG is defined, so it seems that hotplug_path is defined and EXPORTed in kernel/kmod.c, so I'm unsure what the problem is. Thanks, Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
