Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
thanks, the patch works great! would be nice if it could be send to the stable team as well (I think a number of distributions want to use 2.6.22 as base for there next release, and I would be happy if users had the patch in it). sorry for creating confusion: initially I thought MODALIAS had been removed, as I looked at the event with DEVICE and in 2.6.21 it has MODALIAS= and in 2.6.22 it doesn't. that was wrong, I should have looked at the MODALIAS event to find out that DEVICE, TYPE and PRODUCT where missing. sorry again. > Andreas, do I read this right, you miss: > DEVICE, PRODUCT, TYPE > in the usb-interface event, and they only exist in the usb-device event? yes, in 2.6.21 two events have DEVICE (one of them has also MODALIAS), in 2.6.22 one event has DEVICE and PRODUCT and TYPE, the other one MODALIAS, no event has both. your patch fixes this, thanks! > +#ifdef CONFIG_USB_DEVICEFS does this depend on USB_CLASS_DEVICE? i.e. will it break if USB_CLASS_DEVICE is turned off? a migration plan / what shall I do so my code still works when that is done, would be very nice. and enough time so I can get new versions out to the users. so far the kernel was faster and I got bug reports about openct not working with 2.6.22 :( Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Dienstag, 21. August 2007 schrieb Kay Sievers: > The subject says MODALIAS was removed, but I don't think that it ever > was there for a usb-device event. And sure, it's still there for a > usb-interface event. > > Andreas, do I read this right, you miss: > DEVICE, PRODUCT, TYPE > in the usb-interface event, and they only exist in the usb-device event? > > And MODALIAS is not what you miss, and the subject of the mail is > misleading? I'm coming from a different side, as I know not much about the kernel internals. but if I run "udevmonitor --kernel --environment" and then plug in some usb device (e.g. my smart card reader): - on 2.6.21 there are two events with DEVICE and the second has DEVICE and MODALIAS set. thats what I need. - on 2.6.22 there are two events: one has DEVICE and one has MODALIAS, but neither has both. this breaks openct. PRODUCT and TYPE are also missing from the event that has MODALIAS in 2.6.22. > Note: > DEVICE only exists when USB_DEVICE_CLASS=y, yes, I tested with 2.6.22 with that turned on. if setting this to no breaks openct, then we should not easily deprecate it. instead we first need a migration plan, than we need enough time to get a new version of openct to every user that works with the new and the old kernel, and only after that is done we can deprecate it, suggest to turn it of, and even later remove it. please keep such a timing, many other parts of the kernel follow these rules too. Documentation/feature-removal-schedule.txt should be updated to contain exact information how long we can count on USB_DEVICE_CLASS=y etc. > because it unfortunately is > prefixed with the /proc mount path, which doesn't exist when the /proc > device node support is not compiled in I'm fine with that. people have used that one for years, and they still should have it. if you suggest people should use /dev/bus/usb instead, we need the same plan: migration plan first, enough time to adjust the software and get it to the users, then deprecation plan and later a removeal. maybe add an entry to feature-removal-schedule.txt too? even if only to let everyone incl. distribution makers know, that /dev/bus/usb is not an instant replacement for /proc/bus/usb, even if it seems so for some software. > so nothing should depend on the existence of DEVICE. well, first I need the migration plan: so far I could depend on it, please give me the new thing that I can depend on. it needs to work with old kernels too (something like a 6month to 2year window of kernel, we shouldn't force people to upgrade and downgrade kernel and other apps unless it is absolutely necessary). all discussions I remember ended nowhere: there is no alternative for the combination of DEVICE and MODALIAS. I tried /dev/bus/usb and sysfs, but it didn't work out because of timing and race conditions and other problems you summed up as "there is no sane way" ... but maybe I got this wrong, so I'm asking once more: DEVICE plus MODALIAS is working fine for me, but I'm happy to migrate. what is the plan, what shall I do instead? and what is the minimum kernel and udev etc. required for this alternative to work? and how long can I count on the old style still to work? > Most of the recent distros don't mount or configure > usbfs anymore, but use /dev/bus/usb/ device nodes, which can handle > access control lists for local users. that would be a huge problem, as I know no alternative to DEVICE with /proc/bus/usb. the kernel tells me about new /proc/bus/usb devices, but who tells me about any /dev/bus/usb device? as far as I know: no one. please correct me if I'm wrong, I would be real happy to migrate to a working new solution, if it fixes the problem and gives me time for new adventures. > Is this patch fixing your problem? will give it a try and respond later. thanks! Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Dienstag, 21. August 2007 schrieb Greg KH:
> On Fri, Aug 17, 2007 at 04:22:04PM +0200, Andreas Jellinghaus [c] wrote:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit
> >diff;h=9f8b17e643fe6aa505629658445849397bda4e4f
> >
> > removes MODALIAS from one of the events,
>
> Which event?
here is the event with kernel 2.6.21:
UEVENT[1187683991.583384]
add /devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0
SUBSYSTEM=usb
SEQNUM=3070
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/002/006
PRODUCT=8e6/3438/100
TYPE=0/0/0
INTERFACE=11/0/0
MODALIAS=usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00
note: it has both - MODALIAS and DEVICE.
here is the event with kernel 2.6.22 (with CONFIG_USB_DEVICE_CLASS):
UEVENT[1187684539.588975]
add /devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0
SUBSYSTEM=usb
SEQNUM=3029
DEVTYPE=usb_interface
PHYSDEVBUS=usb
INTERFACE=11/0/0
MODALIAS=usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00
you see, it is missing DEVICE and PRODUCT and TYPE
and here is the event with kernel 2.6.22 with alans patch and
CONFIG_USB_DEVICE_CLASS:
UEVENT[1187684125.860105]
add /devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0
SUBSYSTEM=usb
SEQNUM=3029
DEVTYPE=usb_interface
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/002/006
BUSNUM=002
DEVNUM=006
INTERFACE=11/0/0
MODALIAS=usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00
it still misses PRODUCT and TYPE, for real compatibility those should be added
too. (I can work around that, as the PRODUCT information is part of MODALIAS
and I don't use TYPE.)
> If you enable CONFIG_USB_DEVICE_CLASS, does everything work the same
> again?
both with CONFIG_USB_DEVICE_CLASS. would it change anything here?
> What specific udev rule are you matching against here that is now
> broken?
still trying to get it to work, so far I try:
SUBSYSTEM!="usb", GOTO="openct_usb_rules_end"
ACTION!="add", GOTO="openct_usb_rules_end"
ENV{MODALIAS}=="usb:v0973p0001*", RUN+="/lib/udev/openct_usb"
ENV{MODALIAS}=="usb:*ic0Bisc00*", RUN+="/lib/udev/openct_usb"
LABEL="openct_usb_rules_end"
this should work?
> > The text does not mention MODALIAS nor the reason for it's removal.
>
> The reason is we don't need the usb_device class anymore, but we still
> provide for the compatibility if you have an old distro with old udev
> rules that is expecting it (only rule we ran into was the one for the
> usbfs /dev nodes, but there might be more.)
I'm no udev expert, but old kernels provide an event with all three
informations I care about: MODALIAS, DEVICE and PRODUCT. this is changed,
and I don't understand what it has to do with usb_device class.
but I can say that without any event that has all three (or at least the first
two - I can create PRODUCT from MODALIAS i think), I would need to redesign
how openct finds out if new devices are plugged in. long term I might need
to do so anyway, but right now people complain "it doesn't work" to me, and
the culprit seems to be the kernel to me - 2.6.21 works, 2.6.22 does not.
Now I'm working on getting openct udev rules and handling script fixed so
they work at least with alans patch and work around missing PRODUCT.
Regards, Andreas
-
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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Montag, 20. August 2007 schrieb Alan Stern: > I could, but I don't know whether any of this would be accepted for > 2.6.22.stable. It might not be too late to get into 2.6.23... even without it is a first step. I hope it gets accepted into both, as 2.6.22 broke kernel<->user space interfaces and those should never change (or only after a long time with announcement, time for switching to a new one etc). Thanks for your work! Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Montag, 20. August 2007 schrieb Alan Stern: I could, but I don't know whether any of this would be accepted for 2.6.22.stable. It might not be too late to get into 2.6.23... even without it is a first step. I hope it gets accepted into both, as 2.6.22 broke kernel-user space interfaces and those should never change (or only after a long time with announcement, time for switching to a new one etc). Thanks for your work! Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Dienstag, 21. August 2007 schrieb Greg KH:
On Fri, Aug 17, 2007 at 04:22:04PM +0200, Andreas Jellinghaus [c] wrote:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit
diff;h=9f8b17e643fe6aa505629658445849397bda4e4f
removes MODALIAS from one of the events,
Which event?
here is the event with kernel 2.6.21:
UEVENT[1187683991.583384]
add /devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0
SUBSYSTEM=usb
SEQNUM=3070
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/002/006
PRODUCT=8e6/3438/100
TYPE=0/0/0
INTERFACE=11/0/0
MODALIAS=usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00
note: it has both - MODALIAS and DEVICE.
here is the event with kernel 2.6.22 (with CONFIG_USB_DEVICE_CLASS):
UEVENT[1187684539.588975]
add /devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0
SUBSYSTEM=usb
SEQNUM=3029
DEVTYPE=usb_interface
PHYSDEVBUS=usb
INTERFACE=11/0/0
MODALIAS=usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00
you see, it is missing DEVICE and PRODUCT and TYPE
and here is the event with kernel 2.6.22 with alans patch and
CONFIG_USB_DEVICE_CLASS:
UEVENT[1187684125.860105]
add /devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci:00/:00:1d.1/usb2/2-1/2-1.7/2-1.7:1.0
SUBSYSTEM=usb
SEQNUM=3029
DEVTYPE=usb_interface
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/002/006
BUSNUM=002
DEVNUM=006
INTERFACE=11/0/0
MODALIAS=usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00
it still misses PRODUCT and TYPE, for real compatibility those should be added
too. (I can work around that, as the PRODUCT information is part of MODALIAS
and I don't use TYPE.)
If you enable CONFIG_USB_DEVICE_CLASS, does everything work the same
again?
both with CONFIG_USB_DEVICE_CLASS. would it change anything here?
What specific udev rule are you matching against here that is now
broken?
still trying to get it to work, so far I try:
SUBSYSTEM!=usb, GOTO=openct_usb_rules_end
ACTION!=add, GOTO=openct_usb_rules_end
ENV{MODALIAS}==usb:v0973p0001*, RUN+=/lib/udev/openct_usb
ENV{MODALIAS}==usb:*ic0Bisc00*, RUN+=/lib/udev/openct_usb
LABEL=openct_usb_rules_end
this should work?
The text does not mention MODALIAS nor the reason for it's removal.
The reason is we don't need the usb_device class anymore, but we still
provide for the compatibility if you have an old distro with old udev
rules that is expecting it (only rule we ran into was the one for the
usbfs /dev nodes, but there might be more.)
I'm no udev expert, but old kernels provide an event with all three
informations I care about: MODALIAS, DEVICE and PRODUCT. this is changed,
and I don't understand what it has to do with usb_device class.
but I can say that without any event that has all three (or at least the first
two - I can create PRODUCT from MODALIAS i think), I would need to redesign
how openct finds out if new devices are plugged in. long term I might need
to do so anyway, but right now people complain it doesn't work to me, and
the culprit seems to be the kernel to me - 2.6.21 works, 2.6.22 does not.
Now I'm working on getting openct udev rules and handling script fixed so
they work at least with alans patch and work around missing PRODUCT.
Regards, Andreas
-
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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Dienstag, 21. August 2007 schrieb Kay Sievers: The subject says MODALIAS was removed, but I don't think that it ever was there for a usb-device event. And sure, it's still there for a usb-interface event. Andreas, do I read this right, you miss: DEVICE, PRODUCT, TYPE in the usb-interface event, and they only exist in the usb-device event? And MODALIAS is not what you miss, and the subject of the mail is misleading? I'm coming from a different side, as I know not much about the kernel internals. but if I run udevmonitor --kernel --environment and then plug in some usb device (e.g. my smart card reader): - on 2.6.21 there are two events with DEVICE and the second has DEVICE and MODALIAS set. thats what I need. - on 2.6.22 there are two events: one has DEVICE and one has MODALIAS, but neither has both. this breaks openct. PRODUCT and TYPE are also missing from the event that has MODALIAS in 2.6.22. Note: DEVICE only exists when USB_DEVICE_CLASS=y, yes, I tested with 2.6.22 with that turned on. if setting this to no breaks openct, then we should not easily deprecate it. instead we first need a migration plan, than we need enough time to get a new version of openct to every user that works with the new and the old kernel, and only after that is done we can deprecate it, suggest to turn it of, and even later remove it. please keep such a timing, many other parts of the kernel follow these rules too. Documentation/feature-removal-schedule.txt should be updated to contain exact information how long we can count on USB_DEVICE_CLASS=y etc. because it unfortunately is prefixed with the /proc mount path, which doesn't exist when the /proc device node support is not compiled in I'm fine with that. people have used that one for years, and they still should have it. if you suggest people should use /dev/bus/usb instead, we need the same plan: migration plan first, enough time to adjust the software and get it to the users, then deprecation plan and later a removeal. maybe add an entry to feature-removal-schedule.txt too? even if only to let everyone incl. distribution makers know, that /dev/bus/usb is not an instant replacement for /proc/bus/usb, even if it seems so for some software. so nothing should depend on the existence of DEVICE. well, first I need the migration plan: so far I could depend on it, please give me the new thing that I can depend on. it needs to work with old kernels too (something like a 6month to 2year window of kernel, we shouldn't force people to upgrade and downgrade kernel and other apps unless it is absolutely necessary). all discussions I remember ended nowhere: there is no alternative for the combination of DEVICE and MODALIAS. I tried /dev/bus/usb and sysfs, but it didn't work out because of timing and race conditions and other problems you summed up as there is no sane way ... but maybe I got this wrong, so I'm asking once more: DEVICE plus MODALIAS is working fine for me, but I'm happy to migrate. what is the plan, what shall I do instead? and what is the minimum kernel and udev etc. required for this alternative to work? and how long can I count on the old style still to work? Most of the recent distros don't mount or configure usbfs anymore, but use /dev/bus/usb/ device nodes, which can handle access control lists for local users. that would be a huge problem, as I know no alternative to DEVICE with /proc/bus/usb. the kernel tells me about new /proc/bus/usb devices, but who tells me about any /dev/bus/usb device? as far as I know: no one. please correct me if I'm wrong, I would be real happy to migrate to a working new solution, if it fixes the problem and gives me time for new adventures. Is this patch fixing your problem? will give it a try and respond later. thanks! Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
thanks, the patch works great! would be nice if it could be send to the stable team as well (I think a number of distributions want to use 2.6.22 as base for there next release, and I would be happy if users had the patch in it). sorry for creating confusion: initially I thought MODALIAS had been removed, as I looked at the event with DEVICE and in 2.6.21 it has MODALIAS= and in 2.6.22 it doesn't. that was wrong, I should have looked at the MODALIAS event to find out that DEVICE, TYPE and PRODUCT where missing. sorry again. Andreas, do I read this right, you miss: DEVICE, PRODUCT, TYPE in the usb-interface event, and they only exist in the usb-device event? yes, in 2.6.21 two events have DEVICE (one of them has also MODALIAS), in 2.6.22 one event has DEVICE and PRODUCT and TYPE, the other one MODALIAS, no event has both. your patch fixes this, thanks! +#ifdef CONFIG_USB_DEVICEFS does this depend on USB_CLASS_DEVICE? i.e. will it break if USB_CLASS_DEVICE is turned off? a migration plan / what shall I do so my code still works when that is done, would be very nice. and enough time so I can get new versions out to the users. so far the kernel was faster and I got bug reports about openct not working with 2.6.22 :( Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Freitag, 17. August 2007 schrieben Sie: > On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote: > > I need some kernel event that has both DEVICE and MODALIAS set. > > up to including kernel 2.6.21 this seems to come from > > drivers/usb/core/driver.c if I read the code correctly, and then > > it was removed. > > > > udevmonitor --kernel --environment shows one event with both on 2.6.21 > > plain, but not on 2.6.22 plain. > > Does this patch improve matters? yes, thanks, it does. can you add PRODUCT as well? remembered too late that my scripts at least use it too. but that one is no big issue, MODALIAS has the same information so I could use that information. but other people might use it. Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Freitag, 17. August 2007 schrieben Sie: On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote: I need some kernel event that has both DEVICE and MODALIAS set. up to including kernel 2.6.21 this seems to come from drivers/usb/core/driver.c if I read the code correctly, and then it was removed. udevmonitor --kernel --environment shows one event with both on 2.6.21 plain, but not on 2.6.22 plain. Does this patch improve matters? yes, thanks, it does. can you add PRODUCT as well? remembered too late that my scripts at least use it too. but that one is no big issue, MODALIAS has the same information so I could use that information. but other people might use it. Regards, Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Freitag, 17. August 2007 schrieb Alan Stern: > On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote: > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit > >diff;h=9f8b17e643fe6aa505629658445849397bda4e4f > > > > removes MODALIAS from one of the events, this breaks user space > > applications like openct - everything that depends on getting an event > > that has both the DEVICE= path to the usb device and any information on > > the interface, so it can check if the device is something it supports (in > > case of openct: smart card reader, i.e. bInterfaceClass 0b). > > There is no MODALIAS for these events because there are no drivers for > the devices they report. Perhaps you should be looking at > usb_if_uevent() in drivers/usb/core/message.c instead. Is the problem > that this routine doesn't set DEVICE, BUSNUM, or DEVNUM? I need some kernel event that has both DEVICE and MODALIAS set. up to including kernel 2.6.21 this seems to come from drivers/usb/core/driver.c if I read the code correctly, and then it was removed. udevmonitor --kernel --environment shows one event with both on 2.6.21 plain, but not on 2.6.22 plain. Regards, Andreas - 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/
why was MODALIAS removed from usb kernel events? [u]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9f8b17e643fe6aa505629658445849397bda4e4f removes MODALIAS from one of the events, this breaks user space applications like openct - everything that depends on getting an event that has both the DEVICE= path to the usb device and any information on the interface, so it can check if the device is something it supports (in case of openct: smart card reader, i.e. bInterfaceClass 0b). The text does not mention MODALIAS nor the reason for it's removal. sorry for being late, this problem shows up with 2.6.21 -> 2.6.22 changes. Andreas - 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/
why was MODALIAS removed from usb kernel events? [u]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9f8b17e643fe6aa505629658445849397bda4e4f removes MODALIAS from one of the events, this breaks user space applications like openct - everything that depends on getting an event that has both the DEVICE= path to the usb device and any information on the interface, so it can check if the device is something it supports (in case of openct: smart card reader, i.e. bInterfaceClass 0b). The text does not mention MODALIAS nor the reason for it's removal. sorry for being late, this problem shows up with 2.6.21 - 2.6.22 changes. Andreas - 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/
Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]
Am Freitag, 17. August 2007 schrieb Alan Stern: On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit diff;h=9f8b17e643fe6aa505629658445849397bda4e4f removes MODALIAS from one of the events, this breaks user space applications like openct - everything that depends on getting an event that has both the DEVICE= path to the usb device and any information on the interface, so it can check if the device is something it supports (in case of openct: smart card reader, i.e. bInterfaceClass 0b). There is no MODALIAS for these events because there are no drivers for the devices they report. Perhaps you should be looking at usb_if_uevent() in drivers/usb/core/message.c instead. Is the problem that this routine doesn't set DEVICE, BUSNUM, or DEVNUM? I need some kernel event that has both DEVICE and MODALIAS set. up to including kernel 2.6.21 this seems to come from drivers/usb/core/driver.c if I read the code correctly, and then it was removed. udevmonitor --kernel --environment shows one event with both on 2.6.21 plain, but not on 2.6.22 plain. Regards, Andreas - 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/
Re: rsdl 30 on 2.6.20.2 breaks user space usb
Serge Belyshev wrote: > Andreas Jellinghaus <[EMAIL PROTECTED]> writes: > >> with plain 2.6.20.2 I get events / called from udev for /proc/bus/usb >> devices. with rsdl 0.30 added to the kernel I no longer get called for >> those devices (but I do get called for the new /dev/usbdev devices - >> except that I can't use them). >> >> any idea why and what to do? might be related to a race condition. > > sounds like http://bugzilla.kernel.org/show_bug.cgi?id=8166#c32 further debugging shows at least udev->openct is missing an event: udev events on 2.6.20.2 (without rsdl): ( "$ACTION - $DEVICE - $DEVNAME - $PRODUCT - $$ - $PPID") add - /proc/bus/usb/002/016 - - 8e6/3438/100 - 6071 - 6065 add - - /dev/usbdev2.16_ep02 - - 6116 - 6113 add - - /dev/usbdev2.16_ep82 - - 6118 - 6114 add - - /dev/usbdev2.16_ep81 - - 6120 - 6115 udev events on 2.6.20.2 (with rsdl): ( "$ACTION - $DEVICE - $DEVNAME - $PRODUCT - $$ - $PPID") add - - /dev/usbdev2.8_ep02 - - 5287 - 5286 add - - /dev/usbdev2.8_ep82 - - 5290 - 5288 add - - /dev/usbdev2.8_ep81 - - 5291 - 5289 the /proc event is missing. in both cases /proc/ was mounted. syslog with udev on debugging (only the /proc event from the kernel w/o rsdl): Mar 15 11:19:06 localhost udevd[2622]: udev_event_run: seq 2869 forked, pid [6065], 'add' 'usb', 0 seconds old Mar 15 11:19:06 localhost udevd-event[6065]: wait_for_sysfs: file '/sys/devices/pci:00/:00:1d.1/usb2/2-1/2-1.5/2-1.5:1.0/bus' appeared after 0 loops Mar 15 11:19:06 localhost udevd-event[6065]: run_program: '/lib/udev/openct_usb' Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/lib/udev/openct_usb' returned with status 0 Mar 15 11:19:07 localhost udevd-event[6065]: pass_env_to_socket: passed 338 bytes to socket '/org/freedesktop/hal/udev_event', Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/sbin/modprobe -Q usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00' Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/sbin/modprobe' returned with status 1 Mar 15 11:19:07 localhost udevd-event[6065]: pass_env_to_socket: passed -1 bytes to socket '/org/kernel/udev/monitor', Mar 15 11:19:07 localhost udevd-event[6065]: udev_event_run: seq 2869 finished Mar 15 11:19:07 localhost udevd[2622]: udev_done: seq 2869, pid [6065] exit with 1, 1 seconds old there is something similar in syslog (on the rsdl kernel): Mar 15 11:24:32 localhost udevd[2607]: udev_event_run: seq 2717 forked, pid [5284], 'add' 'usb', 0 seconds old Mar 15 11:24:32 localhost udevd-event[5284]: wait_for_sysfs: file '/sys/devices/pci:00/:00:1d.1/usb2/2-1/2-1.5/2-1.5:1.0/bus' appeared after 0 loops Mar 15 11:24:32 localhost udevd-event[5284]: pass_env_to_socket: passed 338 bytes to socket '/org/freedesktop/hal/udev_event', Mar 15 11:24:32 localhost udevd-event[5284]: run_program: '/sbin/modprobe -Q usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00' Mar 15 11:24:32 localhost udevd-event[5284]: run_program: '/sbin/modprobe' returned with status 1 Mar 15 11:24:32 localhost udevd-event[5284]: pass_env_to_socket: passed -1 bytes to socket '/org/kernel/udev/monitor', Mar 15 11:24:32 localhost udevd-event[5284]: udev_event_run: seq 2717 finished Mar 15 11:24:32 localhost udevd[2607]: udev_done: seq 2717, pid [5284] exit with 1, 0 seconds old so I guess it might be a udev bug, as it wait_for_sysfs in both cases, but doesn't trigger openct if the kernel has rsdl. as the hardware is the same and the openct rules for udev didn't change. Thanks, I'm taking the issue to the hotplug mailing list. Regards, Andreas - 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/
rsdl 30 on 2.6.20.2 breaks user space usb
with plain 2.6.20.2 I get events / called from udev for /proc/bus/usb devices. with rsdl 0.30 added to the kernel I no longer get called for those devices (but I do get called for the new /dev/usbdev devices - except that I can't use them). any idea why and what to do? might be related to a race condition. I can also provide kernel config, dmesg, etc. whatever. system is x86 with ubuntu edgy installed. I noticed the problem with openct - the udev helper doesn't get spawned with the rsdl kernel, while it does get spawned with the normal kernel. Regards, Andreas - 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/
rsdl 30 on 2.6.20.2 breaks user space usb
with plain 2.6.20.2 I get events / called from udev for /proc/bus/usb devices. with rsdl 0.30 added to the kernel I no longer get called for those devices (but I do get called for the new /dev/usbdev devices - except that I can't use them). any idea why and what to do? might be related to a race condition. I can also provide kernel config, dmesg, etc. whatever. system is x86 with ubuntu edgy installed. I noticed the problem with openct - the udev helper doesn't get spawned with the rsdl kernel, while it does get spawned with the normal kernel. Regards, Andreas - 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/
Re: rsdl 30 on 2.6.20.2 breaks user space usb
Serge Belyshev wrote: Andreas Jellinghaus [EMAIL PROTECTED] writes: with plain 2.6.20.2 I get events / called from udev for /proc/bus/usb devices. with rsdl 0.30 added to the kernel I no longer get called for those devices (but I do get called for the new /dev/usbdev devices - except that I can't use them). any idea why and what to do? might be related to a race condition. sounds like http://bugzilla.kernel.org/show_bug.cgi?id=8166#c32 further debugging shows at least udev-openct is missing an event: udev events on 2.6.20.2 (without rsdl): ( $ACTION - $DEVICE - $DEVNAME - $PRODUCT - $$ - $PPID) add - /proc/bus/usb/002/016 - - 8e6/3438/100 - 6071 - 6065 add - - /dev/usbdev2.16_ep02 - - 6116 - 6113 add - - /dev/usbdev2.16_ep82 - - 6118 - 6114 add - - /dev/usbdev2.16_ep81 - - 6120 - 6115 udev events on 2.6.20.2 (with rsdl): ( $ACTION - $DEVICE - $DEVNAME - $PRODUCT - $$ - $PPID) add - - /dev/usbdev2.8_ep02 - - 5287 - 5286 add - - /dev/usbdev2.8_ep82 - - 5290 - 5288 add - - /dev/usbdev2.8_ep81 - - 5291 - 5289 the /proc event is missing. in both cases /proc/ was mounted. syslog with udev on debugging (only the /proc event from the kernel w/o rsdl): Mar 15 11:19:06 localhost udevd[2622]: udev_event_run: seq 2869 forked, pid [6065], 'add' 'usb', 0 seconds old Mar 15 11:19:06 localhost udevd-event[6065]: wait_for_sysfs: file '/sys/devices/pci:00/:00:1d.1/usb2/2-1/2-1.5/2-1.5:1.0/bus' appeared after 0 loops Mar 15 11:19:06 localhost udevd-event[6065]: run_program: '/lib/udev/openct_usb' Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/lib/udev/openct_usb' returned with status 0 Mar 15 11:19:07 localhost udevd-event[6065]: pass_env_to_socket: passed 338 bytes to socket '/org/freedesktop/hal/udev_event', Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/sbin/modprobe -Q usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00' Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/sbin/modprobe' returned with status 1 Mar 15 11:19:07 localhost udevd-event[6065]: pass_env_to_socket: passed -1 bytes to socket '/org/kernel/udev/monitor', Mar 15 11:19:07 localhost udevd-event[6065]: udev_event_run: seq 2869 finished Mar 15 11:19:07 localhost udevd[2622]: udev_done: seq 2869, pid [6065] exit with 1, 1 seconds old there is something similar in syslog (on the rsdl kernel): Mar 15 11:24:32 localhost udevd[2607]: udev_event_run: seq 2717 forked, pid [5284], 'add' 'usb', 0 seconds old Mar 15 11:24:32 localhost udevd-event[5284]: wait_for_sysfs: file '/sys/devices/pci:00/:00:1d.1/usb2/2-1/2-1.5/2-1.5:1.0/bus' appeared after 0 loops Mar 15 11:24:32 localhost udevd-event[5284]: pass_env_to_socket: passed 338 bytes to socket '/org/freedesktop/hal/udev_event', Mar 15 11:24:32 localhost udevd-event[5284]: run_program: '/sbin/modprobe -Q usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00' Mar 15 11:24:32 localhost udevd-event[5284]: run_program: '/sbin/modprobe' returned with status 1 Mar 15 11:24:32 localhost udevd-event[5284]: pass_env_to_socket: passed -1 bytes to socket '/org/kernel/udev/monitor', Mar 15 11:24:32 localhost udevd-event[5284]: udev_event_run: seq 2717 finished Mar 15 11:24:32 localhost udevd[2607]: udev_done: seq 2717, pid [5284] exit with 1, 0 seconds old so I guess it might be a udev bug, as it wait_for_sysfs in both cases, but doesn't trigger openct if the kernel has rsdl. as the hardware is the same and the openct rules for udev didn't change. Thanks, I'm taking the issue to the hotplug mailing list. Regards, Andreas - 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/
Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Evgeniy Polyakov wrote: You can change it in async_provider in compilation time or I can create module version. There is an item in related todo list to use crypto contexts, they were created exactly for such kind of things (actually for hardware devices which do not support realtime key changes). ok, what do I need to change to get aes-cbc-essiv:sha256 support so I can use acrypto with my current dm-crypt'ed partitions? would be nice to track those issues, so people testing your patch are aware of the situation. I will change acrypto software crypto provider, but right now, yes, software crypto only supports one mode. ok, thanks. Regards, Andreas - 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/
Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Evgeniy Polyakov wrote: You can change it in async_provider in compilation time or I can create module version. There is an item in related todo list to use crypto contexts, they were created exactly for such kind of things (actually for hardware devices which do not support realtime key changes). ok, what do I need to change to get aes-cbc-essiv:sha256 support so I can use acrypto with my current dm-crypt'ed partitions? would be nice to track those issues, so people testing your patch are aware of the situation. I will change acrypto software crypto provider, but right now, yes, software crypto only supports one mode. ok, thanks. Regards, Andreas - 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/
Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Evgeniy Polyakov wrote: Actually I do not recall what is 'size retrictions' - if you talk about possibility to use software crypto provider, which supports one cipher in a time, then yes, but it is intended to be used with hardware though. Otherwise I do not recall any problems pointed to me. sorry, "size restriction" was the wrong term. acrypto only supports "sync provider only supports AES-128 in CBC mode, so if you try different ciphers, there can be some problems." and I'm using dm-crypto with aes-cbc-essiv:sha256 and your acrypto patch breaks this setup - not only acrypto doesn't provide crypto capability for my setup, but with this patch it is not offered by the old mechanism either, so my system has no way to decrypt the root partition. note: that was with the 2.6.18 patch, no idea if it is different now. so while the patch adds new features, it also removes some features - not sure if always (via patch) or via compile option or via module load. also I'm not sure if acrypto can be disabled via kernel command line to get the old behaviour (including aes-cbc-essiv:sha256 support for dm-crypt). would be nice to track those issues, so people testing your patch are aware of the situation. Regards, Andreas - 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/
Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Evgeniy Polyakov wrote: Actually I do not recall what is 'size retrictions' - if you talk about possibility to use software crypto provider, which supports one cipher in a time, then yes, but it is intended to be used with hardware though. Otherwise I do not recall any problems pointed to me. sorry, size restriction was the wrong term. acrypto only supports sync provider only supports AES-128 in CBC mode, so if you try different ciphers, there can be some problems. and I'm using dm-crypto with aes-cbc-essiv:sha256 and your acrypto patch breaks this setup - not only acrypto doesn't provide crypto capability for my setup, but with this patch it is not offered by the old mechanism either, so my system has no way to decrypt the root partition. note: that was with the 2.6.18 patch, no idea if it is different now. so while the patch adds new features, it also removes some features - not sure if always (via patch) or via compile option or via module load. also I'm not sure if acrypto can be disabled via kernel command line to get the old behaviour (including aes-cbc-essiv:sha256 support for dm-crypt). would be nice to track those issues, so people testing your patch are aware of the situation. Regards, Andreas - 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/
Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Does acrypto still have the same size restrictions I ran into with the last release? Thanks, Andreas - 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/
Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Does acrypto still have the same size restrictions I ran into with the last release? Thanks, Andreas - 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/
Re: linux 2.6.19 still crashing
Sergio Monteiro Basto wrote:
Hi,
1st you should put this information on http://bugzilla.kernel.org/
ok, thanks.
your bug kept me the attention because on bad interrupts you have :
21: 10 IO-APIC-fasteoi ohci1394
Exactly oops on 10 interrupts, I had seen this before .
I have my bug on http://bugzilla.kernel.org/show_bug.cgi?id=6419
which one of the bugs looks like similar to yours.
So, You are saying with kernel 2.6.16.31 with xen 3.0.2, you don't have
this problem , I like to try it, how or where you build this Xenified
kernel ?
The package source were available at , but they no longer are :(
http://debian.thoughtcrime.co.nz/ubuntu/
I can send you my copies (either parts or all), if you don't mind
getting big emails
-rw-r--r-- 1 aj aj 342068 2006-04-19 12:14 libxen3.0_3.0.2-2r7_amd64.deb
-rw-r--r-- 1 aj aj 106440 2006-04-19 12:14 libxen-dev_3.0.2-2r7_amd64.deb
-rw-r--r-- 1 aj aj 155186 2006-04-19 12:14
libxen-python_3.0.2-2r7_amd64.deb
-rw-r--r-- 1 aj aj 620946 2006-04-19 12:14
linux-patch-xen_3.0.2-2r7_amd64.deb
drwxr-xr-x 10 aj aj4096 2006-04-19 12:14 xen-3.0.2
-rw-r--r-- 1 aj aj 12926 2006-04-19 12:14 xen_3.0.2-2r7_amd64.deb
-rw-r--r-- 1 aj aj 656745 2006-04-19 12:12 xen_3.0.2-2r7.diff.gz
-rw-r--r-- 1 aj aj 645 2006-04-19 12:12 xen_3.0.2-2r7.dsc
-rw-r--r-- 1 aj aj 0 2006-04-19 12:14 xen_3.0.2-2r7.dsc.asc
-rw-r--r-- 1 aj aj 4933621 2006-04-19 11:36 xen_3.0.2.orig.tar.gz
-rw-r--r-- 1 aj aj 531232 2006-04-19 12:14 xen-docs_3.0.2-2r7_all.deb
-rw-r--r-- 1 aj aj 1479866 2006-04-19 12:14
xen-hypervisor-3.0_3.0.2-2r7_amd64.deb
-rw-r--r-- 1 aj aj 180526 2006-04-19 12:14
xen-utils-3.0_3.0.2-2r7_amd64.deb
only *dsc *diff.gz and *orig.tar.gz are needed, then you can recompile
the rest yourself ("dpkg-source -x *dsc; cd xen-*/; dpkg-buildpackage
-rfakeroot").
or I can send you the kernel patch as file and the xen hypervisor:
-rw-r--r-- 1 root root 244694 2006-04-19 12:14 /boot/xen-3.0.2-2.gz
-rw-r--r-- 1 root root 604942 2006-04-19 12:14
/usr/src/kernel-patches/diffs/xen/linux-2.6.16-xen.patch.gz
it applies clean against 2.6.16, but if with 2.6.16.31 I had
to manually fix two rejects.
Regards, Andreas
-
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/
Re: linux 2.6.19 still crashing
Sergio Monteiro Basto wrote: Hi, 1st you should put this information on http://bugzilla.kernel.org/ ok, thanks. your bug kept me the attention because on bad interrupts you have : 21: 10 IO-APIC-fasteoi ohci1394 Exactly oops on 10 interrupts, I had seen this before . I have my bug on http://bugzilla.kernel.org/show_bug.cgi?id=6419 which one of the bugs looks like similar to yours. So, You are saying with kernel 2.6.16.31 with xen 3.0.2, you don't have this problem , I like to try it, how or where you build this Xenified kernel ? The package source were available at , but they no longer are :( http://debian.thoughtcrime.co.nz/ubuntu/ I can send you my copies (either parts or all), if you don't mind getting big emails -rw-r--r-- 1 aj aj 342068 2006-04-19 12:14 libxen3.0_3.0.2-2r7_amd64.deb -rw-r--r-- 1 aj aj 106440 2006-04-19 12:14 libxen-dev_3.0.2-2r7_amd64.deb -rw-r--r-- 1 aj aj 155186 2006-04-19 12:14 libxen-python_3.0.2-2r7_amd64.deb -rw-r--r-- 1 aj aj 620946 2006-04-19 12:14 linux-patch-xen_3.0.2-2r7_amd64.deb drwxr-xr-x 10 aj aj4096 2006-04-19 12:14 xen-3.0.2 -rw-r--r-- 1 aj aj 12926 2006-04-19 12:14 xen_3.0.2-2r7_amd64.deb -rw-r--r-- 1 aj aj 656745 2006-04-19 12:12 xen_3.0.2-2r7.diff.gz -rw-r--r-- 1 aj aj 645 2006-04-19 12:12 xen_3.0.2-2r7.dsc -rw-r--r-- 1 aj aj 0 2006-04-19 12:14 xen_3.0.2-2r7.dsc.asc -rw-r--r-- 1 aj aj 4933621 2006-04-19 11:36 xen_3.0.2.orig.tar.gz -rw-r--r-- 1 aj aj 531232 2006-04-19 12:14 xen-docs_3.0.2-2r7_all.deb -rw-r--r-- 1 aj aj 1479866 2006-04-19 12:14 xen-hypervisor-3.0_3.0.2-2r7_amd64.deb -rw-r--r-- 1 aj aj 180526 2006-04-19 12:14 xen-utils-3.0_3.0.2-2r7_amd64.deb only *dsc *diff.gz and *orig.tar.gz are needed, then you can recompile the rest yourself (dpkg-source -x *dsc; cd xen-*/; dpkg-buildpackage -rfakeroot). or I can send you the kernel patch as file and the xen hypervisor: -rw-r--r-- 1 root root 244694 2006-04-19 12:14 /boot/xen-3.0.2-2.gz -rw-r--r-- 1 root root 604942 2006-04-19 12:14 /usr/src/kernel-patches/diffs/xen/linux-2.6.16-xen.patch.gz it applies clean against 2.6.16, but if with 2.6.16.31 I had to manually fix two rejects. Regards, Andreas - 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/
linux 2.6.19 still crashing
my msi s270 laptop. but all vanilla kernel I ever tried do that, also the debian and ubuntu kernel are instable too. But: xen 3.0.2 plus xen'ified linux 2.6.16.31 are rock solid. any idea what the issue could be? I'm running 64bit kernel, 64bit userland (plus some 32bit apps), and the cpu is a turion mt-40 (sempron users seem to not have this problem). I documented all details, config files, dmesg, /proc/interrupts, lspci -vvv and xorg log file at http://www.megawiki.org/wiki/S270Crashing I can also mail you all those files (didn't want to spam linux-kernel with a huge mail), and provide any other information that can help, try patches or command line options, or different compile options or whatever you can suggest. Thanks for your help! Regards, Andreas - 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/
linux 2.6.19 still crashing
my msi s270 laptop. but all vanilla kernel I ever tried do that, also the debian and ubuntu kernel are instable too. But: xen 3.0.2 plus xen'ified linux 2.6.16.31 are rock solid. any idea what the issue could be? I'm running 64bit kernel, 64bit userland (plus some 32bit apps), and the cpu is a turion mt-40 (sempron users seem to not have this problem). I documented all details, config files, dmesg, /proc/interrupts, lspci -vvv and xorg log file at http://www.megawiki.org/wiki/S270Crashing I can also mail you all those files (didn't want to spam linux-kernel with a huge mail), and provide any other information that can help, try patches or command line options, or different compile options or whatever you can suggest. Thanks for your help! Regards, Andreas - 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/
Re: O2micro smartcard reader driver.
maybe post once more, and make clear whether you are looking for: - smart card reader support. (smart card as in "digital signature card".) o2micro creates such readers, they are usualy usb devices, conform to the ccid standard and work fine (e.g. pcsc-lite plus ccid driver or openct). - smart media card / multi media card reader support (those small memory cards used by mobile phones, cameras and so on). o2micro creates those too, they are also build in by some vendors, but I'm not sure about their situation. also o2micro might also create pcmcia card readers for either. maybe let us know what kind of device you exactly have and how it is connected (if build in... lspci / lsusb would see pci or usb devices, pcmcia devices are found by the kernel I think). Regards, Andreas - 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/
Re: O2micro smartcard reader driver.
maybe post once more, and make clear whether you are looking for: - smart card reader support. (smart card as in digital signature card.) o2micro creates such readers, they are usualy usb devices, conform to the ccid standard and work fine (e.g. pcsc-lite plus ccid driver or openct). - smart media card / multi media card reader support (those small memory cards used by mobile phones, cameras and so on). o2micro creates those too, they are also build in by some vendors, but I'm not sure about their situation. also o2micro might also create pcmcia card readers for either. maybe let us know what kind of device you exactly have and how it is connected (if build in... lspci / lsusb would see pci or usb devices, pcmcia devices are found by the kernel I think). Regards, Andreas - 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/
Re: initramfs [u]
Jacek Jab?o?ski wrote: > Do You know any tool to create initramfs (not initrd)? that is very easy: create a directory tree with everything you want in it (for example ld.so, a libc, some applications and config files and scripts and device files and whatever) and then use cpio to pack the files and directories into a cpio archive. gzip if you want. cpio has several formats, be sure to choose the right one. more information in Documentation/early-userspace/* btw: most people want initrd/initramfs etc. with some small libc (klibc, dietlibc etc.). But normal libcs works very fine as well. I have some initramfs that are build from a few dozend debian packages. the result is a few hundred mb big (uncompressed), but that is ok as I can load and boot it via network and it works great and has all the normal linux tools in it. also see the klibc mailing list, there have been several discussions about initramfs and I posted example code there I think. so look at the archives, too. Regards, Andreas - 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/
Re: initramfs [u]
Jacek Jab?o?ski wrote: Do You know any tool to create initramfs (not initrd)? that is very easy: create a directory tree with everything you want in it (for example ld.so, a libc, some applications and config files and scripts and device files and whatever) and then use cpio to pack the files and directories into a cpio archive. gzip if you want. cpio has several formats, be sure to choose the right one. more information in Documentation/early-userspace/* btw: most people want initrd/initramfs etc. with some small libc (klibc, dietlibc etc.). But normal libcs works very fine as well. I have some initramfs that are build from a few dozend debian packages. the result is a few hundred mb big (uncompressed), but that is ok as I can load and boot it via network and it works great and has all the normal linux tools in it. also see the klibc mailing list, there have been several discussions about initramfs and I posted example code there I think. so look at the archives, too. Regards, Andreas - 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/
Re: INITRAMFS: junk in compressed archive
On Fri, 25 Mar 2005 14:51:07 +, Bernhard Schauer wrote: > other question: > > Is there any size-limit on initramfs image? I found out that after > reducing the image size it is loaded & /init executed as expected... compressed size plus uncompressed size have be less than the total ram available. maybe a few checks a remissing? I get a kernel panic. it would be nice if the kernel dropped the initrd, and then did the usual no root fs -> kernel panic code. Andreas - 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/
Re: INITRAMFS: junk in compressed archive
On Fri, 25 Mar 2005 14:51:07 +, Bernhard Schauer wrote: other question: Is there any size-limit on initramfs image? I found out that after reducing the image size it is loaded /init executed as expected... compressed size plus uncompressed size have be less than the total ram available. maybe a few checks a remissing? I get a kernel panic. it would be nice if the kernel dropped the initrd, and then did the usual no root fs - kernel panic code. Andreas - 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/
Re: swsusp: allow resume from initramfs
On Fri, 04 Mar 2005 11:35:12 +, Andrew Morton wrote: > I don't understand how this can be affected by the modularness of the > kernel. Can you explain a little more? > > Would it not be simpler to just add "resume=03:02" to the boot command line? initramfs can also be used to ask for a passphrase, hash it, and setup some (de)cryption dm tables. Andreas - 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/
Re: swsusp: allow resume from initramfs
Great, with this patch I can setup an encrypted swap partition, and resume from it (after the initramfs asked for the password and set up the dm-crypt table). But wait, I'm using swapfiles. swap is fine with files. what about swsuspend? and if it works with files, too, what about this resume interface? Andreas - 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/
Re: swsusp: allow resume from initramfs
Great, with this patch I can setup an encrypted swap partition, and resume from it (after the initramfs asked for the password and set up the dm-crypt table). But wait, I'm using swapfiles. swap is fine with files. what about swsuspend? and if it works with files, too, what about this resume interface? Andreas - 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/
Re: swsusp: allow resume from initramfs
On Fri, 04 Mar 2005 11:35:12 +, Andrew Morton wrote: I don't understand how this can be affected by the modularness of the kernel. Can you explain a little more? Would it not be simpler to just add resume=03:02 to the boot command line? initramfs can also be used to ask for a passphrase, hash it, and setup some (de)cryption dm tables. Andreas - 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/
Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts
it looks like yaird does use pivot_root. however pivot_root and initramfs cause a kernel crash (once you unmount /initrd in the real system). use run-init from klibc instead and you are fine. Andreas - 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/
Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts
it looks like yaird does use pivot_root. however pivot_root and initramfs cause a kernel crash (once you unmount /initrd in the real system). use run-init from klibc instead and you are fine. Andreas - 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/
Re: Announce loop-AES-v3.0b file/swap crypto package
On Mon, 17 Jan 2005 15:11:18 +, Jari Ruusu wrote: > Mainline folks are just too much in love with their backdoored device > crypto implementations [1]. If you want strong device crypto in mainline > kernel, maybe you should take a look at FreeBSD gbde. what about dm-crypt? I lost track, whether it is fixed or not. (Or rather: whether secure modes where added, and which modes are considered secure). also my key is 32 random bytes and not a hash. will I have any issue? dictionary attacks will not work with that. Thanks for your help. Regards, Andreas - 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/
Re: Announce loop-AES-v3.0b file/swap crypto package
On Mon, 17 Jan 2005 15:11:18 +, Jari Ruusu wrote: Mainline folks are just too much in love with their backdoored device crypto implementations [1]. If you want strong device crypto in mainline kernel, maybe you should take a look at FreeBSD gbde. what about dm-crypt? I lost track, whether it is fixed or not. (Or rather: whether secure modes where added, and which modes are considered secure). also my key is 32 random bytes and not a hash. will I have any issue? dictionary attacks will not work with that. Thanks for your help. Regards, Andreas - 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/
partition table: chs question
hi. for partitions not in the first 8gb of a harddisk, what should the c/h/s start and end value be ? most fdisks seem to set start and end to 255/63/1023. but partition magic creates partitions with start set to 0/1/1023 and end set to 255/63/1023, and detects a problem if start is set to 255/63/1023. so, how should a partition table look like ? regards, andreas - 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/
partition table: chs question
hi. for partitions not in the first 8gb of a harddisk, what should the c/h/s start and end value be ? most fdisks seem to set start and end to 255/63/1023. but partition magic creates partitions with start set to 0/1/1023 and end set to 255/63/1023, and detects a problem if start is set to 255/63/1023. so, how should a partition table look like ? regards, andreas - 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/
2.4.0-ac10 crashed
hi. this morning i found my home server crashed. a full screen of [<%8lx>], no idea what was above that. Aieee, killing in interrupt handler! In Interrupt handler - not syncing. Code 80 78 0E 00 75 04 C6 40 0e 30 31 c0 88 d8 50 56 e8 5f 1D 00 dmesg after reboot: Linux version 2.4.0-ac10 (root@dream) (gcc version 2.95.3 20010111 (prerelease)) #1 Sat Jan 20 09:21:52 CET 2001 BIOS-provided physical RAM map: BIOS-e820: 000a @ (usable) BIOS-e820: 00018000 @ 000e8000 (reserved) BIOS-e820: 03f0 @ 0010 (usable) BIOS-e820: 0002 @ fffe (reserved) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. Scan SMP from c000 for 4096 bytes. On node 0 totalpages: 16384 zone(0): 4096 pages. zone(1): 12288 pages. zone(2): 0 pages. APIC turned off by hardware. mapped APIC to e000 (01112000) Kernel command line: mem=65536K root=/dev/sda3 readonly hisax=3,2,10,0xd80,0,HiSax HiSax_setup: argc(5) str(HiSax) Initializing CPU#0 Detected 119.754 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 238.38 BogoMIPS Memory: 61996k/65536k available (1175k kernel code, 3152k reserved, 441k data, 212k init, 0k highmem) Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) VFS: Diskquotas version dquot_6.5.0 initialized CPU: Before vendor init, caps: 01bf , vendor = 0 Intel Pentium with F0 0F bug - workaround enabled. CPU: After vendor init, caps: 01bf CPU: After generic, caps: 01bf CPU: Common caps: 01bf CPU: Intel Pentium 75 - 200 stepping 05 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.10 entry at 0xfbcd0, last bus=0 PCI: Using configuration type 1 PCI: Probing PCI hardware Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket IA-32 Microcode Update Driver: v1.08 <[EMAIL PROTECTED]> Starting kswapd v1.8 parport0: PC-style at 0x378 [PCSPP,EPP] parport0: cpp_daisy: aa5500ff(00) parport0: assign_addrs: aa5500ff(00) parport0: No more nibble data (0 bytes) parport0: cpp_daisy: aa5500ff(00) parport0: assign_addrs: aa5500ff(00) parport0: Legacy device pty: 256 Unix98 ptys configured lp0: using parport0 (polling). ISDN subsystem Rev: 1.114/1.94/1.140.6.1/1.85/1.21/1.5 HiSax: Linux Driver for passive ISDN cards HiSax: Version 3.5 (kernel) HiSax: Layer1 Revision 2.41.6.1 HiSax: Layer2 Revision 2.25 HiSax: TeiMgr Revision 2.17 HiSax: Layer3 Revision 2.17 HiSax: LinkLayer Revision 2.51 HiSax: Approval certification failed because of HiSax: unauthorized source code changes HiSax: Total 1 card defined HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) HiSax: Teles IO driver Rev. 2.17 HiSax: Teles 16.3 config irq:10 isac:0x980 cfg:0xD80 HiSax: hscx A:0x180 hscx B:0x580 Teles3: ISAC version (0): 2086/2186 V1.1 Teles3: HSCX version A: A3 B: A3 Teles 16.3: IRQ 10 count 0 Teles 16.3: IRQ 10 count 3 HiSax: DSS1 Rev. 2.30 HiSax: 2 channels added HiSax: MAX_WAITING_CALLS added block: queued sectors max/low 40733kB/30550kB, 128 slots per queue loop: enabling 8 loop devices Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ DETECT_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker http://www.scyld.com/network/ne2k-pci.html eth0: Winbond 89C940 found at 0xe400, IRQ 15, 48:54:E8:28:85:5F. SCSI subsystem driver Revision: 1.00 scsi: * BusLogic SCSI Driver Version 2.1.15 of 17 August 1998 * scsi: Copyright 1995-1998 by Leonard N. Zubkoff <[EMAIL PROTECTED]> scsi0: Configuring BusLogic Model BT-950 PCI Wide Ultra SCSI Host Adapter scsi0: Firmware Version: 5.02, I/O Address: 0xE000, IRQ Channel: 15/Level scsi0: PCI Bus: 0, Device: 10, Address: 0xFBFD, Host Adapter SCSI ID: 7 scsi0: Parity Checking: Enabled, Extended Translation: Enabled scsi0: Synchronous Negotiation: UFFUFFF#, Wide Negotiation: YYYNYYY# scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled scsi0: Driver Queue Depth: 255, Scatter/Gather Limit: 128 segments scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3 scsi0: Error Recovery Strategy: Default, SCSI Bus Reset: Enabled scsi0: SCSI Bus Termination: High Enabled, SCAM: Disabled scsi0: *** BusLogic BT-950 Initialized Successfully *** scsi0 : BusLogic BT-950 Vendor: IBM Model: DCAS-34330W Rev: S65A Type: Direct-Access ANSI SCSI revision: 02 Vendor:
2.4.0-ac10 crashed
hi. this morning i found my home server crashed. a full screen of [%8lx], no idea what was above that. Aieee, killing in interrupt handler! In Interrupt handler - not syncing. Code 80 78 0E 00 75 04 C6 40 0e 30 31 c0 88 d8 50 56 e8 5f 1D 00 dmesg after reboot: Linux version 2.4.0-ac10 (root@dream) (gcc version 2.95.3 20010111 (prerelease)) #1 Sat Jan 20 09:21:52 CET 2001 BIOS-provided physical RAM map: BIOS-e820: 000a @ (usable) BIOS-e820: 00018000 @ 000e8000 (reserved) BIOS-e820: 03f0 @ 0010 (usable) BIOS-e820: 0002 @ fffe (reserved) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. Scan SMP from c000 for 4096 bytes. On node 0 totalpages: 16384 zone(0): 4096 pages. zone(1): 12288 pages. zone(2): 0 pages. APIC turned off by hardware. mapped APIC to e000 (01112000) Kernel command line: mem=65536K root=/dev/sda3 readonly hisax=3,2,10,0xd80,0,HiSax HiSax_setup: argc(5) str(HiSax) Initializing CPU#0 Detected 119.754 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 238.38 BogoMIPS Memory: 61996k/65536k available (1175k kernel code, 3152k reserved, 441k data, 212k init, 0k highmem) Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) VFS: Diskquotas version dquot_6.5.0 initialized CPU: Before vendor init, caps: 01bf , vendor = 0 Intel Pentium with F0 0F bug - workaround enabled. CPU: After vendor init, caps: 01bf CPU: After generic, caps: 01bf CPU: Common caps: 01bf CPU: Intel Pentium 75 - 200 stepping 05 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.10 entry at 0xfbcd0, last bus=0 PCI: Using configuration type 1 PCI: Probing PCI hardware Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket IA-32 Microcode Update Driver: v1.08 [EMAIL PROTECTED] Starting kswapd v1.8 parport0: PC-style at 0x378 [PCSPP,EPP] parport0: cpp_daisy: aa5500ff(00) parport0: assign_addrs: aa5500ff(00) parport0: No more nibble data (0 bytes) parport0: cpp_daisy: aa5500ff(00) parport0: assign_addrs: aa5500ff(00) parport0: Legacy device pty: 256 Unix98 ptys configured lp0: using parport0 (polling). ISDN subsystem Rev: 1.114/1.94/1.140.6.1/1.85/1.21/1.5 HiSax: Linux Driver for passive ISDN cards HiSax: Version 3.5 (kernel) HiSax: Layer1 Revision 2.41.6.1 HiSax: Layer2 Revision 2.25 HiSax: TeiMgr Revision 2.17 HiSax: Layer3 Revision 2.17 HiSax: LinkLayer Revision 2.51 HiSax: Approval certification failed because of HiSax: unauthorized source code changes HiSax: Total 1 card defined HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) HiSax: Teles IO driver Rev. 2.17 HiSax: Teles 16.3 config irq:10 isac:0x980 cfg:0xD80 HiSax: hscx A:0x180 hscx B:0x580 Teles3: ISAC version (0): 2086/2186 V1.1 Teles3: HSCX version A: A3 B: A3 Teles 16.3: IRQ 10 count 0 Teles 16.3: IRQ 10 count 3 HiSax: DSS1 Rev. 2.30 HiSax: 2 channels added HiSax: MAX_WAITING_CALLS added block: queued sectors max/low 40733kB/30550kB, 128 slots per queue loop: enabling 8 loop devices Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ DETECT_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker http://www.scyld.com/network/ne2k-pci.html eth0: Winbond 89C940 found at 0xe400, IRQ 15, 48:54:E8:28:85:5F. SCSI subsystem driver Revision: 1.00 scsi: * BusLogic SCSI Driver Version 2.1.15 of 17 August 1998 * scsi: Copyright 1995-1998 by Leonard N. Zubkoff [EMAIL PROTECTED] scsi0: Configuring BusLogic Model BT-950 PCI Wide Ultra SCSI Host Adapter scsi0: Firmware Version: 5.02, I/O Address: 0xE000, IRQ Channel: 15/Level scsi0: PCI Bus: 0, Device: 10, Address: 0xFBFD, Host Adapter SCSI ID: 7 scsi0: Parity Checking: Enabled, Extended Translation: Enabled scsi0: Synchronous Negotiation: UFFUFFF#, Wide Negotiation: YYYNYYY# scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled scsi0: Driver Queue Depth: 255, Scatter/Gather Limit: 128 segments scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3 scsi0: Error Recovery Strategy: Default, SCSI Bus Reset: Enabled scsi0: SCSI Bus Termination: High Enabled, SCAM: Disabled scsi0: *** BusLogic BT-950 Initialized Successfully *** scsi0 : BusLogic BT-950 Vendor: IBM Model: DCAS-34330W Rev: S65A Type: Direct-Access ANSI SCSI revision: 02 Vendor: YAMAHA
[2.4.0-rerelease] driver/net/Makefile bug (pcmcia)
modules for pcmcia network cards are not build by the kernel. subdir-$(CONFIG_PCMCIA) += pcmcia should be ifeq ($(CONFIG_PCMCIA),y) subdir-y += pcmcia subdir-m += pcmcia endif because CONFIG_PCMCIA=y but CONFIG_PCMCIA_SOMENETWORKDRIVER=m maybe even bett is useing CONFIG_NET_PCMCIA instead of CONFIG_PCMCIA. regards, andreas - 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/
[2.4.0-rerelease] driver/net/Makefile bug (pcmcia)
modules for pcmcia network cards are not build by the kernel. subdir-$(CONFIG_PCMCIA) += pcmcia should be ifeq ($(CONFIG_PCMCIA),y) subdir-y += pcmcia subdir-m += pcmcia endif because CONFIG_PCMCIA=y but CONFIG_PCMCIA_SOMENETWORKDRIVER=m maybe even bett is useing CONFIG_NET_PCMCIA instead of CONFIG_PCMCIA. regards, andreas - 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/
2.2.18 ipc problem
lotus domino server dies with deleting all semaphores, shared memory ... with ipcrm/ipcs does not help, only a reboot does. any idea what could be wrong ? i have no idea if this is a bug in linux or domino, but under linux usualy you don't need a to reboot a server. are there known issues with ipc / kernel 2.2.18 ? or with domino or other apps. the machine is a smp dual i386 machine (ibm netfinity 5500). regards, andreas - 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/
2.2.18 ipc problem
lotus domino server dies with deleting all semaphores, shared memory ... with ipcrm/ipcs does not help, only a reboot does. any idea what could be wrong ? i have no idea if this is a bug in linux or domino, but under linux usualy you don't need a to reboot a server. are there known issues with ipc / kernel 2.2.18 ? or with domino or other apps. the machine is a smp dual i386 machine (ibm netfinity 5500). regards, andreas - 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/
