Re: HEADSUP!!! USB MFC committed..
[sorry for the late followup. also, my address is ipv6-only; drop it and I'll catch up from the archives after some time] > On Sun, 29 Feb 2004, Julian Elischer wrote: > > The USB code in RELENG_4 has been updated to match that in -current. > > Please test any USB devices that are critical to you BEFORE we release > > 4.10 :-) > p.s. there are some more MFCs to come but they are minor > (except for what looks like a major rewrite of parts of umass) Would it be possible to merge in the umass parts of -current that enable all slots of a 6/8/whetever-in-1 USB card reader/writer thingies to be detected? In source updated around 30.mar, building the umass -stable kernel module only finds the CF slot. I've added a few dozen lines to the -current umass code and built a module from that which appears to work as needed (meaning, I have not had major problems, but I haven't stress-tested it) with the -stable usb code and kernel I'm using. This gives me all sorts of da* devices (see below). Unfortunately, adding EHCI support to the usb.ko module causes panics with such a umass.ko module; adding an EBUSY line to match -stable seems to make things better, but not perfect (from what I can remember). The below result is with only uhci/ohci support. My added-lines hack is not based on knowing what I'm doing, but rather based on what appears superficially to work and is probably horribly wrong. I believe the code to add support for the card readers was added to -current something like a year ago, and may possibly be found in a patch mentioned around that time by Bernd Walter -- as I have not been online, I haven't been able to download it and check. The -current diff appears to be between 1.79 and 1.80, but when massaged into -stable, I don't get all the devices (can be my fault). My world/kernel/modules on the machine in question are a horrible mongrel mix spanning the last couple of years and originate from both -stable and adopted out of -current, so I hesitate to make a fool of myself by publicly posting the added lines to umass.c from -current to make it operate with my mostly-stable. (Actually, it looks like all I did was to un-re-implement cam_calc_geometry() back to what was in -stable, and to say that I don't have a ZIP_100 so I could junk that portion of the code just to get it to compile quietly, rather than to make it work.) thanks barry bouwsma Preloaded elf module "usb_NEW.ko" at 0xc042f600. Preloaded elf module "ums_NEW.ko" at 0xc042f6a0. Preloaded elf module "ugen_NEW.ko" at 0xc042f740. Preloaded elf module "umass_CURRENT.ko" at 0xc042f7e0. [...] umass1: OTi USB 7-in-1 Card Reader, rev 2.00/2.00, addr 4 umass1:1:1:-1: Attached to scbus1 [...] umass2: SMSC 223 USB97C223, rev 2.00/1.95, addr 7 umass2:2:2:-1: Attached to scbus2 [...] Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 Creating DISK da4 Creating DISK da5 Creating DISK da6 Creating DISK da7 Creating DISK da8 [snipping for brevity] da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: Serial Number A80A06AE da0: 1.000MB/s transfers da0: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) da1 at umass-sim1 bus 1 target 0 lun 0 da1: Removable Direct Access SCSI-0 device [Serial Number lines from this umass device are a control-underscore] da1: 1.000MB/s transfers da5 at umass-sim2 bus 2 target 0 lun 0 da5: Removable Direct Access SCSI-0 device da5: Serial Number da5: 1.000MB/s transfers da2 at umass-sim1 bus 1 target 0 lun 1 da2: Removable Direct Access SCSI-0 device da2: 1.000MB/s transfers da3 at umass-sim1 bus 1 target 0 lun 2 da3: Removable Direct Access SCSI-0 device da3: 1.000MB/s transfers da3: 60MB (124160 512 byte sectors: 64H 32S/T 60C) da6 at umass-sim2 bus 2 target 0 lun 1 da6: Removable Direct Access SCSI-0 device da6: Serial Number da6: 1.000MB/s transfers da4 at umass-sim1 bus 1 target 0 lun 3 da4: Removable Direct Access SCSI-0 device da4: 1.000MB/s transfers da7 at umass-sim2 bus 2 target 0 lun 2 da7: Removable Direct Access SCSI-0 device da7: Serial Number da7: 1.000MB/s transfers da8 at umass-sim2 bus 2 target 0 lun 3 da8: Removable Direct Access SCSI-0 device da8: Serial Number da8: 1.000MB/s transfers da8: 243MB (498176 512 byte sectors: 64H 32S/T 243C) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
let me have your patches.. 4.10 goes into code freeze tomorrow so I need them asap. I can get a pass from release engineering to put in fixes pas teh freeze if it's soon. On Wed, 7 Apr 2004, Barry Bouwsma wrote: > [sorry for the late followup. also, my address is ipv6-only; drop it and > I'll catch up from the archives after some time] > > > > On Sun, 29 Feb 2004, Julian Elischer wrote: > > > > The USB code in RELENG_4 has been updated to match that in -current. > > > Please test any USB devices that are critical to you BEFORE we release > > > 4.10 :-) > > > p.s. there are some more MFCs to come but they are minor > > (except for what looks like a major rewrite of parts of umass) > > Would it be possible to merge in the umass parts of -current that > enable all slots of a 6/8/whetever-in-1 USB card reader/writer > thingies to be detected? > > In source updated around 30.mar, building the umass -stable kernel > module only finds the CF slot. > > I've added a few dozen lines to the -current umass code and built > a module from that which appears to work as needed (meaning, I have > not had major problems, but I haven't stress-tested it) with the > -stable usb code and kernel I'm using. This gives me all sorts of > da* devices (see below). Unfortunately, adding EHCI support to the > usb.ko module causes panics with such a umass.ko module; adding an > EBUSY line to match -stable seems to make things better, but not > perfect (from what I can remember). The below result is with only > uhci/ohci support. > > My added-lines hack is not based on knowing what I'm doing, but rather > based on what appears superficially to work and is probably horribly > wrong. I believe the code to add support for the card readers was > added to -current something like a year ago, and may possibly be > found in a patch mentioned around that time by Bernd Walter -- as I > have not been online, I haven't been able to download it and check. > The -current diff appears to be between 1.79 and 1.80, but when > massaged into -stable, I don't get all the devices (can be my fault). > > My world/kernel/modules on the machine in question are a horrible > mongrel mix spanning the last couple of years and originate from > both -stable and adopted out of -current, so I hesitate to make a > fool of myself by publicly posting the added lines to umass.c from > -current to make it operate with my mostly-stable. > > (Actually, it looks like all I did was to un-re-implement > cam_calc_geometry() back to what was in -stable, and to say that > I don't have a ZIP_100 so I could junk that portion of the code > just to get it to compile quietly, rather than to make it work.) > > > thanks > barry bouwsma > > Preloaded elf module "usb_NEW.ko" at 0xc042f600. > Preloaded elf module "ums_NEW.ko" at 0xc042f6a0. > Preloaded elf module "ugen_NEW.ko" at 0xc042f740. > Preloaded elf module "umass_CURRENT.ko" at 0xc042f7e0. > [...] > umass1: OTi USB 7-in-1 Card Reader, rev 2.00/2.00, addr 4 > umass1:1:1:-1: Attached to scbus1 > [...] > umass2: SMSC 223 USB97C223, rev 2.00/1.95, addr 7 > umass2:2:2:-1: Attached to scbus2 > [...] > Creating DISK da0 > Creating DISK da1 > Creating DISK da2 > Creating DISK da3 > Creating DISK da4 > Creating DISK da5 > Creating DISK da6 > Creating DISK da7 > Creating DISK da8 > [snipping for brevity] > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: Serial Number A80A06AE > da0: 1.000MB/s transfers > da0: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) > > da1 at umass-sim1 bus 1 target 0 lun 0 > da1: Removable Direct Access SCSI-0 device > [Serial Number lines from this umass device are a control-underscore] > da1: 1.000MB/s transfers > > da5 at umass-sim2 bus 2 target 0 lun 0 > da5: Removable Direct Access SCSI-0 device > da5: Serial Number > da5: 1.000MB/s transfers > > da2 at umass-sim1 bus 1 target 0 lun 1 > da2: Removable Direct Access SCSI-0 device > da2: 1.000MB/s transfers > > da3 at umass-sim1 bus 1 target 0 lun 2 > da3: Removable Direct Access SCSI-0 device > da3: 1.000MB/s transfers > da3: 60MB (124160 512 byte sectors: 64H 32S/T 60C) > > da6 at umass-sim2 bus 2 target 0 lun 1 > da6: Removable Direct Access SCSI-0 device > da6: Serial Number > da6: 1.000MB/s transfers > > da4 at umass-sim1 bus 1 target 0 lun 3 > da4: Removable Direct Access SCSI-0 device > da4: 1.000MB/s transfers > > da7 at umass-sim2 bus 2 target 0 lun 2 > da7: Removable Direct Access SCSI-0 device > da7: Serial Number > da7: 1.000MB/s transfers > > da8 at umass-sim2 bus 2 target 0 lun 3 > da8: Removable Direct Access SCSI-0 device > da8: Serial Number > da8: 1.000MB/s transfers > da8: 243MB (498176 512 byte sectors: 64H 32S/T 243C) > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
Hi akiyama san, unfortunately, It couldn't help me. With KMODDEPS, DDB said: Stopped at usbd_get_string+0x15: movl 0(%eax), %eax) db> trace usbd_get_string(.) usbd_devinfo_vp(.) usbd_devinfo(.) ugen_attach(.) DEVICE_ATTACH(.) device_probe_and_attach(.) at ... usbd_probe_and_attach(.) at ... usbd_new_device(.) at ... (snip) Without KMODEPS, I had been seen: Stopped at usbd_get_interface_descriptor+0x6: movl 0x4(%eax),%eax db> trace usbd_get_interface_descriptor(1,6,) at usbd_get_interface_descriptor+0x6 umodem_match(.) at umodem_match+0x24 DEVICE_PROBE(.) at DEVICE_PROBE+0x2e device_probe_child(.) at ... device_probe_and_attach(.) at ... usbd_probe_and_attach(.) at ... usbd_new_device(.) at ... (snip) I don't know what is different between two above situation. By the way, I found it would always panic with latter panic message when I load kernel-without-usb + usb.ko + ucom.ko + umodem.ko then boot although I didn't plugged any umodem devices. akiyama san wrote: > Hi, Sarumaru-san. > > At Mon, 8 Mar 2004 01:38:07 +0900, > Yoshihiko Sarumaru wrote: > > > I report you about a USB problem that would be occur with my > > laptop after you MFC'ed USB stuff. > > > > With GENERIC kernel, it is fine and there are no changes from > > before, but with no usb kernel + usb.ko + umass.ko, it would be > > panic everytime on boot. > > > > It is not depend on umass. The panic would be happen when I > > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > > (PHS phone). > > I reproduced this panic, and tracked this down. > This is a kernel module dependency problem. > > Please try attached patch, and let me know the result. > If this patch fix your problem, I'll commit this. > -- > Shunsuke Akiyama > [EMAIL PROTECTED] > [EMAIL PROTECTED] -- Yoshihiko Sarumaru mail: [EMAIL PROTECTED] web: http://www.imasy.or.jp/~mistral/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
On Fri, 12 Mar 2004, Shunsuke Akiyama wrote: > At Wed, 10 Mar 2004 22:18:05 +0900, > Shunsuke Akiyama wrote: > > > At Mon, 8 Mar 2004 01:38:07 +0900, > > Yoshihiko Sarumaru wrote: > > > > > I report you about a USB problem that would be occur with my > > > laptop after you MFC'ed USB stuff. > > > > > > With GENERIC kernel, it is fine and there are no changes from > > > before, but with no usb kernel + usb.ko + umass.ko, it would be > > > panic everytime on boot. > > > > > > It is not depend on umass. The panic would be happen when I > > > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > > > (PHS phone). > > > > I reproduced this panic, and tracked this down. > > This is a kernel module dependency problem. > > > > Please try attached patch, and let me know the result. > > If this patch fix your problem, I'll commit this. > > Grrr, my patch makes another problem about loading kernel module. > > I tried to load umodem.ko by hand with kernel which have compiled-in > uhci and usb drivers. Then I got an error like following. > > # kldload umodem > module_register: module usb/uhub already exists! > linker_file_sysinit "usb.ko" failed to register! 17 > kldload: can't load umodem: Exec format error > > Hum, this is different from CURRENT's behavior. > I think in-kernel loader/linker should be fixed first. On the other hand teh netgraph autoloading workd better in 4.x than it did in 5.x. (last time I checked about 6 months ago) > -- > Shunsuke Akiyama > [EMAIL PROTECTED] > [EMAIL PROTECTED] > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
At Wed, 10 Mar 2004 22:18:05 +0900, Shunsuke Akiyama wrote: > At Mon, 8 Mar 2004 01:38:07 +0900, > Yoshihiko Sarumaru wrote: > > > I report you about a USB problem that would be occur with my > > laptop after you MFC'ed USB stuff. > > > > With GENERIC kernel, it is fine and there are no changes from > > before, but with no usb kernel + usb.ko + umass.ko, it would be > > panic everytime on boot. > > > > It is not depend on umass. The panic would be happen when I > > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > > (PHS phone). > > I reproduced this panic, and tracked this down. > This is a kernel module dependency problem. > > Please try attached patch, and let me know the result. > If this patch fix your problem, I'll commit this. Grrr, my patch makes another problem about loading kernel module. I tried to load umodem.ko by hand with kernel which have compiled-in uhci and usb drivers. Then I got an error like following. # kldload umodem module_register: module usb/uhub already exists! linker_file_sysinit "usb.ko" failed to register! 17 kldload: can't load umodem: Exec format error Hum, this is different from CURRENT's behavior. I think in-kernel loader/linker should be fixed first. -- Shunsuke Akiyama [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
On Wed, 10 Mar 2004, Shunsuke Akiyama wrote: > Hi, Sarumaru-san. > > At Mon, 8 Mar 2004 01:38:07 +0900, > Yoshihiko Sarumaru wrote: > > > I report you about a USB problem that would be occur with my > > laptop after you MFC'ed USB stuff. > > > > With GENERIC kernel, it is fine and there are no changes from > > before, but with no usb kernel + usb.ko + umass.ko, it would be > > panic everytime on boot. > > > > It is not depend on umass. The panic would be happen when I > > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > > (PHS phone). > you are just ahead of me I was looking at the dependencies but had not yet worked it out :-) > I reproduced this panic, and tracked this down. > This is a kernel module dependency problem. > > Please try attached patch, and let me know the result. > If this patch fix your problem, I'll commit this. > -- > Shunsuke Akiyama > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
Hi, Sarumaru-san. At Mon, 8 Mar 2004 01:38:07 +0900, Yoshihiko Sarumaru wrote: > I report you about a USB problem that would be occur with my > laptop after you MFC'ed USB stuff. > > With GENERIC kernel, it is fine and there are no changes from > before, but with no usb kernel + usb.ko + umass.ko, it would be > panic everytime on boot. > > It is not depend on umass. The panic would be happen when I > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > (PHS phone). I reproduced this panic, and tracked this down. This is a kernel module dependency problem. Please try attached patch, and let me know the result. If this patch fix your problem, I'll commit this. -- Shunsuke Akiyama [EMAIL PROTECTED] [EMAIL PROTECTED] moddepfix.diffs Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
Hello, julian wrote: > > With GENERIC kernel, it is fine and there are no changes from > > before, but with no usb kernel + usb.ko + umass.ko, it would be > > panic everytime on boot. > > > > It is not depend on umass. The panic would be happen when I > > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > > (PHS phone). > > do you need a usb device plugged in for the panic? > I can not duplicate this.. Because of my laptop has MemoryStick reader inside, I can't boot without a USB device. But when I boot without umass.ko, it wouldn't panic at all. Off cource in that case, load umodem and plug USB modem causes panic (load umodem but not plug USB modem doesn't cause panic). So maybe the answer for you question is yes. -- Yoshihiko Sarumaru mail: [EMAIL PROTECTED] web: http://www.imasy.or.jp/~mistral/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
On Mon, 8 Mar 2004, Yoshihiko Sarumaru wrote: > Hello Julian, > > I report you about a USB problem that would be occur with my > laptop after you MFC'ed USB stuff. > > With GENERIC kernel, it is fine and there are no changes from > before, but with no usb kernel + usb.ko + umass.ko, it would be > panic everytime on boot. > > It is not depend on umass. The panic would be happen when I > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > (PHS phone). do you need a usb device plugged in for the panic? I can not duplicate this.. see below: ok load /k2 /k2 text=0x17a2ae data=0x1f40c+0x1d064 syms=[0x4+0x25990+0x4+0x2c7a0] ok load /modules/usb.ko /modules/usb.ko text=0x18c40 data=0x3e14+0x60 syms=[0x4+0x24d0+0x4+0x2697] ok load /modules/umass.ko /modules/umass.ko text=0x5280 data=0x108+0x8 syms=[0x4+0x7e0+0x4+0x6af] ok boot -s Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-STABLE #5: Tue Mar 9 00:47:27 GMT 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/REF1 Timecounter "i8254" frequency 1193182 Hz CPU: Intel Pentium III (863.87-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 267124736 (260864K bytes) sio1: gdb debugging port avail memory = 256868352 (250848K bytes) Preloaded elf kernel "k2" at 0xc0336000. Preloaded elf module "usb.ko" at 0xc03360a4. Preloaded elf module "umass.ko" at 0xc0336140. ... ohci0: mem 0xff8fd000-0xff8fdfff irq 11 at device 10.0 on pci1 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xff8fe000-0xff8fefff irq 9 at device 10.1 on pci1 usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci1: at 10.2 irq 6 ... uhci0: port 0xef40-0xef5f irq 10 at device 31.2 on pci0 usb2: on uhci0 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2443) at 31.3 irq 6 uhci1: port 0xef80-0xef9f irq 9 at device 31.4 on pci0 usb3: on uhci1 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ... acd0: CDROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a Enter full pathname of shell or RETURN for /bin/sh: ... though I notice that my EHCI controller was not seen.. (something to look at) > > | Preloaded elf kernel "kernel.nousb" at 0xc042b000. > | Preloaded elf module "usb.ko" at 0xc042b0b0. > | Preloaded elf module "umass.ko" at 0xc042b14c. > | ... > | ata0: at 0x1f0 irq 14 on atapci0 > | ata1: at 0x170 irq 15 on atapci0 > | uhci0: port 0xfca0-0xfcbf irq 9 at dev > | ice 7.2 on pci0 > | usb0: on uhci0 > | usb0: USB revision 1.0 > | uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > | uhub0: 2 ports with 2 removable, self powered > | uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 > | uhub1: 3 ports with 3 removable, self powered > | > | > | Fatal trap 12: page fault while in kernel mode > | fault virtual address = 0x38 > | fault code = supervisor read, page not present > | instruction pointer = 0x8:0xc0424323 > | stack pointer = 0x10:0xc044d91c > | frame pointer = 0x10:0xc044d928 > | code segment= base 0x0, limit 0xf, type 0x1b > | = DPL 0, pres 1, def32 1, gran 1 > | processor eflags= interrupt enabled, resume, IOPL = 0 > | current process = 0 (swapper) > | interrupt mask = net tty bio cam > > With USB built-in kernel, it will be like this: > | Preloaded elf kernel "kernel.withusb" at 0xc0434000. > | Preloaded elf module "ucom.ko" at 0xc043409c. > | Preloaded elf module "umodem.ko" at 0xc0434138. > | ... > | ata0: at 0x1f0 irq 14 on atapci0 > | ata1: at 0x170 irq 15 on atapci0 > | uhci0: port 0xfca0-0xfcbf irq 9 at dev > | ice 7.2 on pci0 > | usb0: on uhci0 > | usb0: USB revision 1.0 > | uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > | uhub0: 2 ports with 2 removable, self powered > | uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 > | uhub1: 3 ports with 3 removable, self powered > | umass0: Sony USB Memory Stick Slot, rev 1.10/1.31, addr 3, UFI over CBI > | umass0:0:0:-1: Attached to scbus0 as device 0 > > Thanks, > - Yoshihiko > > [EMAIL PROTECTED] wrote: > > > > > The USB code in RELENG_4 has been updated to match that in -current. > > Please test any USB devices that are critical to you BEFORE we release > > 4.10 :-) > > > > > > thanks > > > > Julian > > > > > > ___ > > [EMAIL PROTECTED]
Re: HEADSUP!!! USB MFC committed..
Hello Julian, I report you about a USB problem that would be occur with my laptop after you MFC'ed USB stuff. With GENERIC kernel, it is fine and there are no changes from before, but with no usb kernel + usb.ko + umass.ko, it would be panic everytime on boot. It is not depend on umass. The panic would be happen when I didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem (PHS phone). | Preloaded elf kernel "kernel.nousb" at 0xc042b000. | Preloaded elf module "usb.ko" at 0xc042b0b0. | Preloaded elf module "umass.ko" at 0xc042b14c. | ... | ata0: at 0x1f0 irq 14 on atapci0 | ata1: at 0x170 irq 15 on atapci0 | uhci0: port 0xfca0-0xfcbf irq 9 at dev | ice 7.2 on pci0 | usb0: on uhci0 | usb0: USB revision 1.0 | uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 | uhub0: 2 ports with 2 removable, self powered | uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 | uhub1: 3 ports with 3 removable, self powered | | | Fatal trap 12: page fault while in kernel mode | fault virtual address = 0x38 | fault code = supervisor read, page not present | instruction pointer = 0x8:0xc0424323 | stack pointer = 0x10:0xc044d91c | frame pointer = 0x10:0xc044d928 | code segment= base 0x0, limit 0xf, type 0x1b | = DPL 0, pres 1, def32 1, gran 1 | processor eflags= interrupt enabled, resume, IOPL = 0 | current process = 0 (swapper) | interrupt mask = net tty bio cam With USB built-in kernel, it will be like this: | Preloaded elf kernel "kernel.withusb" at 0xc0434000. | Preloaded elf module "ucom.ko" at 0xc043409c. | Preloaded elf module "umodem.ko" at 0xc0434138. | ... | ata0: at 0x1f0 irq 14 on atapci0 | ata1: at 0x170 irq 15 on atapci0 | uhci0: port 0xfca0-0xfcbf irq 9 at dev | ice 7.2 on pci0 | usb0: on uhci0 | usb0: USB revision 1.0 | uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 | uhub0: 2 ports with 2 removable, self powered | uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 | uhub1: 3 ports with 3 removable, self powered | umass0: Sony USB Memory Stick Slot, rev 1.10/1.31, addr 3, UFI over CBI | umass0:0:0:-1: Attached to scbus0 as device 0 Thanks, - Yoshihiko [EMAIL PROTECTED] wrote: > > The USB code in RELENG_4 has been updated to match that in -current. > Please test any USB devices that are critical to you BEFORE we release > 4.10 :-) > > > thanks > > Julian > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Yoshihiko Sarumaru mail: [EMAIL PROTECTED] web: http://www.imasy.or.jp/~mistral/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
On Mon, 8 Mar 2004, Yoshihiko Sarumaru wrote: > Hello Julian, > > I report you about a USB problem that would be occur with my > laptop after you MFC'ed USB stuff. thankyou. > > With GENERIC kernel, it is fine and there are no changes from > before, but with no usb kernel + usb.ko + umass.ko, it would be > panic everytime on boot. intersting.. I will investigate. > > It is not depend on umass. The panic would be happen when I > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem > (PHS phone). > > | Preloaded elf kernel "kernel.nousb" at 0xc042b000. > | Preloaded elf module "usb.ko" at 0xc042b0b0. > | Preloaded elf module "umass.ko" at 0xc042b14c. > | ... > | ata0: at 0x1f0 irq 14 on atapci0 > | ata1: at 0x170 irq 15 on atapci0 > | uhci0: port 0xfca0-0xfcbf irq 9 at dev > | ice 7.2 on pci0 > | usb0: on uhci0 > | usb0: USB revision 1.0 > | uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > | uhub0: 2 ports with 2 removable, self powered > | uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 > | uhub1: 3 ports with 3 removable, self powered > | > | > | Fatal trap 12: page fault while in kernel mode > | fault virtual address = 0x38 > | fault code = supervisor read, page not present > | instruction pointer = 0x8:0xc0424323 > | stack pointer = 0x10:0xc044d91c > | frame pointer = 0x10:0xc044d928 > | code segment= base 0x0, limit 0xf, type 0x1b > | = DPL 0, pres 1, def32 1, gran 1 > | processor eflags= interrupt enabled, resume, IOPL = 0 > | current process = 0 (swapper) > | interrupt mask = net tty bio cam > > With USB built-in kernel, it will be like this: > | Preloaded elf kernel "kernel.withusb" at 0xc0434000. > | Preloaded elf module "ucom.ko" at 0xc043409c. > | Preloaded elf module "umodem.ko" at 0xc0434138. > | ... > | ata0: at 0x1f0 irq 14 on atapci0 > | ata1: at 0x170 irq 15 on atapci0 > | uhci0: port 0xfca0-0xfcbf irq 9 at dev > | ice 7.2 on pci0 > | usb0: on uhci0 > | usb0: USB revision 1.0 > | uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > | uhub0: 2 ports with 2 removable, self powered > | uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 > | uhub1: 3 ports with 3 removable, self powered > | umass0: Sony USB Memory Stick Slot, rev 1.10/1.31, addr 3, UFI over CBI > | umass0:0:0:-1: Attached to scbus0 as device 0 > > Thanks, > - Yoshihiko > > [EMAIL PROTECTED] wrote: > > > > > The USB code in RELENG_4 has been updated to match that in -current. > > Please test any USB devices that are critical to you BEFORE we release > > 4.10 :-) > > > > > > thanks > > > > Julian > > > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > -- > Yoshihiko Sarumaru > mail: [EMAIL PROTECTED] web: http://www.imasy.or.jp/~mistral/ > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
On Sun, 29 Feb 2004, Julian Elischer wrote: > > The USB code in RELENG_4 has been updated to match that in -current. > Please test any USB devices that are critical to you BEFORE we release > 4.10 :-) p.s. there are some more MFCs to come but they are minor (except for what looks like a major rewrite of parts of umass) > > > thanks > > Julian > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HEADSUP!!! USB MFC committed..
The USB code in RELENG_4 has been updated to match that in -current. Please test any USB devices that are critical to you BEFORE we release 4.10 :-) thanks Julian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
