NetBSD Problem Report #47080

From www@NetBSD.org  Mon Oct 15 13:55:13 2012
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id D064263E4E6
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 15 Oct 2012 13:55:13 +0000 (UTC)
Message-Id: <20121015135511.AD6C363E059@www.NetBSD.org>
Date: Mon, 15 Oct 2012 13:55:11 +0000 (UTC)
From: ishit@oak.dti.ne.jp
Reply-To: ishit@oak.dti.ne.jp
To: gnats-bugs@NetBSD.org
Subject: E-mobile D02HW is not attached to uhmodem driver
X-Send-Pr-Version: www-1.0

>Number:         47080
>Category:       kern
>Synopsis:       E-mobile D02HW is not attached to uhmodem driver
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 15 14:00:01 +0000 2012
>Last-Modified:  Sun Oct 13 10:35:00 +0000 2013
>Originator:     ISIHARA Takanori
>Release:        NetBSD 6.0
>Organization:
Nagoya *BSD Users' Group :-)
>Environment:
NetBSD ishitPc9.home 6.0 NetBSD 6.0 (GENERIC) #0: Mon Oct 15 10:36:39 JST 2012  sysbuild@ishitPc9.home:/opt/sysbuild/netbsd-6/obj/i386/sys/arch/i386/compile/GENERIC i386

>Description:
uhmodem(4) man page said,

  HARDWARE
       The uhmodem driver supports the following adapters:

             Huawei E220
             E-mobile D01HW
             E-mobile D02HW
             NTT DoCoMo a2502


My E-mobile D02HW modem is not attached to uhmodem(4) driver.
My modem is attached to u3g(4) driver, and it works fine.

Is this a problem ?


PC:

My PC is MSI Wind Notebook U100.
Wifi card is Intel PRO/Wireless 3945ABG.
Memory is 2GB.


dmesg:

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 6.0 (GENERIC) #0: Mon Oct 15 10:36:39 JST 2012
	sysbuild@ishitPc9.home:/opt/sysbuild/netbsd-6/obj/i386/sys/arch/i386/compile/GENERIC
total memory = 2037 MB
avail memory = 1990 MB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
MICRO-STAR INTERNATIONAL CO., LTD U-100 (Ver.001)
mainbus0 (root)
ACPI Warning: 32/64X FACS address mismatch in FADT - 0x7F611E40/0x000000007F611D40, using 32 (20110623/tbfadt-517)
cpu0 at mainbus0 apid 0: Intel(R) Atom(TM) CPU N270   @ 1.60GHz, id 0x106c2
cpu1 at mainbus0 apid 1: Intel(R) Atom(TM) CPU N270   @ 1.60GHz, id 0x106c2
ioapic0 at mainbus0 apid 2: pa 0xfec00000, version 20, 24 pins
acpi0 at mainbus0: Intel ACPICA 20110623
acpi0: X/RSDT: OemId <MSI_NB,MEGABOOK,06222004>, AslId <MSFT,00010013>
ACPI Error: No handler for Region [EC__] (0xc35ba134) [EmbeddedControl] (20110623/evregion-421)
ACPI Error: Region EmbeddedControl (ID=3) has no handler (20110623/exfldio-310)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc35bbb24), AE_NOT_EXIST (20110623/psparse-560)
ACPI Error: Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc35bbb24), AE_NOT_EXIST (20110623/uteval-114)
ACPI Error: No handler for Region [EC__] (0xc35ba134) [EmbeddedControl] (20110623/evregion-421)
ACPI Error: Region EmbeddedControl (ID=3) has no handler (20110623/exfldio-310)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc35bbb24), AE_NOT_EXIST (20110623/psparse-560)
ACPI Error: Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc35bbb24), AE_NOT_EXIST (20110623/uteval-114)
acpi0: SCI interrupting at int 9
timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900
ACPI Error: No handler for Region [EC__] (0xc35ba134) [EmbeddedControl] (20110623/evregion-421)
ACPI Error: Region EmbeddedControl (ID=3) has no handler (20110623/exfldio-310)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc35bbb24), AE_NOT_EXIST (20110623/psparse-560)
ACPI Error: Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc35bbb24), AE_NOT_EXIST (20110623/uteval-114)
acpiec0 at acpi0 (EC, PNP0C09): io 0x62,0x66
MCH (PNP0C01) at acpi0 not configured
pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
midi0 at pcppi1: PC speaker
sysbeep0 at pcppi1
attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0
RMSC (PNP0C02) at acpi0 not configured
npx1 at acpi0 (COPR, PNP0C04): io 0xf0-0xff irq 13
npx1: reported by CPUID; using exception 16
pckbc1 at acpi0 (PS2K, PNP0303) (kbd port): io 0x60,0x64 irq 1
pckbc2 at acpi0 (PS2M, PNP0F03) (aux port): irq 12
acpiacad0 at acpi0 (ADP1, ACPI0003): ACPI AC Adapter
acpibat0 at acpi0 (BAT1, PNP0C0A-1): ACPI Battery
acpibat0: 
 LION
 rechargeable battery
acpibat0: granularity: low->warn 0.001 Ah, warn->full 0.001 Ah
acpilid0 at acpi0 (LID0, PNP0C0D): ACPI Lid Switch
acpiwmi0 at acpi0 (SCM0, PNP0C14-0): ACPI WMI Interface
acpiwmibus at acpiwmi0 not configured
ICH7 (PNP0C01) at acpi0 not configured
acpivga0 at acpi0 (IGD): ACPI Display Adapter
acpiout0 at acpivga0 (CRT, 0x0100): ACPI Display Output Device
acpiout1 at acpivga0 (LCD, 0x0410): ACPI Display Output Device
acpiout1: brightness levels: 20 30 40 50 60 70 80 90 100
acpivga0: connected output devices:
acpivga0:   0x0100 (acpiout0): Ext. Monitor, head 0, bios detect
acpivga0:   0x0410 (acpiout1): Unknown Output Device, head 0, bios detect
hpet0 at acpi0 (HPET, PNP0103): high precision event timer (mem 0xfed03000-0xfed03400)
timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button
acpibut1 at acpi0 (SLPB, PNP0C0E): ACPI Sleep Button
RMEM (PNP0C01) at acpi0 not configured
acpitz0 at acpi0 (THRM)
acpitz0: levels: critical 100.0 C, passive cooling
OMSC (PNP0C02) at acpi0 not configured
apm0 at acpi0: Power Management spec V1.2
attimer1: attached to pcppi1
pckbd0 at pckbc1 (kbd slot)
pckbc1: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pms0 at pckbc1 (aux slot)
pckbc1: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: vendor 0x8086 product 0x27ac (rev. 0x03)
agp0 at pchb0: detected 7932k stolen memory
agp0: aperture at 0xc0000000, size 0x10000000
vga1 at pci0 dev 2 function 0: vendor 0x8086 product 0x27ae (rev. 0x03)
wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
i915drm0 at vga1: Intel i945GME
i915drm0: AGP at 0xc0000000 256MB
i915drm0: Initialized i915 1.6.0 20080730
vendor 0x8086 product 0x27a6 (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured
hdaudio0 at pci0 dev 27 function 0: HD Audio Controller
hdaudio0: interrupting at ioapic0 pin 16
hdafg0 at hdaudio0: Realtek ALC888
hdafg0: DAC00 2ch: Speaker [Built-In], HP Out [Jack]
hdafg0: ADC01 2ch: Mic In [Jack] [Built-In]
hdafg0: 2ch/2ch 44100Hz 48000Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3
audio0 at hdafg0: full duplex, playback, capture, independent
ppb0 at pci0 dev 28 function 0: vendor 0x8086 product 0x27d0 (rev. 0x02)
ppb0: PCI Express 1.0 <Root Port of PCI-E Root Complex>
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
re0 at pci1 dev 0 function 0: RealTek 8100E/8101E/8102E/8102EL PCIe 10/100BaseTX (rev. 0x02)
re0: interrupting at ioapic0 pin 16
re0: Ethernet address 00:21:85:53:6e:05
re0: using 256 tx descriptors
rlphy0 at re0 phy 7: RTL8201L 10/100 media interface, rev. 1
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ppb1 at pci0 dev 28 function 1: vendor 0x8086 product 0x27d2 (rev. 0x02)
ppb1: PCI Express 1.0 <Root Port of PCI-E Root Complex>
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
wpi0 at pci2 dev 0 function 0: vendor 0x8086 product 0x4222 (rev. 0x02)
wpi0: interrupting at ioapic0 pin 17
wpi0: MoW2, address 00:1f:3c:07:6e:ad
wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
uhci0 at pci0 dev 29 function 0: vendor 0x8086 product 0x27c8 (rev. 0x02)
uhci0: interrupting at ioapic0 pin 23
usb0 at uhci0: USB revision 1.0
uhci1 at pci0 dev 29 function 1: vendor 0x8086 product 0x27c9 (rev. 0x02)
uhci1: interrupting at ioapic0 pin 19
usb1 at uhci1: USB revision 1.0
uhci2 at pci0 dev 29 function 2: vendor 0x8086 product 0x27ca (rev. 0x02)
uhci2: interrupting at ioapic0 pin 18
usb2 at uhci2: USB revision 1.0
uhci3 at pci0 dev 29 function 3: vendor 0x8086 product 0x27cb (rev. 0x02)
uhci3: interrupting at ioapic0 pin 16
usb3 at uhci3: USB revision 1.0
ehci0 at pci0 dev 29 function 7: vendor 0x8086 product 0x27cc (rev. 0x02)
ehci0: interrupting at ioapic0 pin 23
ehci0: EHCI version 1.0
ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2 uhci3
usb4 at ehci0: USB revision 2.0
ppb2 at pci0 dev 30 function 0: vendor 0x8086 product 0x2448 (rev. 0xe2)
pci3 at ppb2 bus 3
pci3: i/o space, memory space enabled
ichlpcib0 at pci0 dev 31 function 0: vendor 0x8086 product 0x27b9 (rev. 0x02)
timecounter: Timecounter "ichlpcib0" frequency 3579545 Hz quality 1000
ichlpcib0: 24-bit timer
ichlpcib0: TCO (watchdog) timer configured.
gpio0 at ichlpcib0: 64 pins
piixide0 at pci0 dev 31 function 2: Intel 82801GBM/GHM Serial ATA Controller (ICH7) (rev. 0x02)
piixide0: bus-master DMA support present
piixide0: primary channel wired to compatibility mode
piixide0: primary channel interrupting at ioapic0 pin 14
atabus0 at piixide0 channel 0
piixide0: secondary channel wired to compatibility mode
piixide0: secondary channel interrupting at ioapic0 pin 15
atabus1 at piixide0 channel 1
ichsmb0 at pci0 dev 31 function 3: vendor 0x8086 product 0x27da (rev. 0x02)
ichsmb0: interrupting at ioapic0 pin 19
iic0 at ichsmb0: I2C bus
isa0 at ichlpcib0
acpicpu0 at cpu0: ACPI CPU
acpicpu0: C1: FFH, lat   1 us, pow  1000 mW
acpicpu0: C2: FFH, lat  20 us, pow   500 mW
acpicpu0: C3: FFH, lat 100 us, pow   100 mW, bus master check
acpicpu0: P0: FFH, lat  10 us, pow  2000 mW, 1600 MHz
acpicpu0: P1: FFH, lat  10 us, pow  1533 mW, 1333 MHz
acpicpu0: P2: FFH, lat  10 us, pow  1066 mW, 1067 MHz
acpicpu0: P3: FFH, lat  10 us, pow   600 mW,  800 MHz
acpicpu0: T0: FFH, lat   1 us, pow   600 mW, 100 %
acpicpu0: T1: FFH, lat   1 us, pow   525 mW,  88 %
acpicpu0: T2: FFH, lat   1 us, pow   450 mW,  75 %
acpicpu0: T3: FFH, lat   1 us, pow   375 mW,  63 %
acpicpu0: T4: FFH, lat   1 us, pow   300 mW,  50 %
acpicpu0: T5: FFH, lat   1 us, pow   225 mW,  38 %
acpicpu0: T6: FFH, lat   1 us, pow   150 mW,  25 %
acpicpu0: T7: FFH, lat   1 us, pow    75 mW,  13 %
coretemp0 at cpu0: thermal sensor, 1 C resolution
acpicpu1 at cpu1: ACPI CPU
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
acpiacad0: AC adapter online.
uhub0 at usb0: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub1 at usb1: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub2 at usb2: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhub3 at usb3: vendor 0x8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
uhub4 at usb4: vendor 0x8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
umass0 at uhub4 port 6 configuration 1 interface 0
umass0: Generic USB2.0-CRW, rev 2.00/58.87, addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <Generic-, Multi-Card, 1.00> disk removable
sd0: drive offline
sd0: unable to open device, error = 19
wd0 at atabus0 drive 0
wd0: <WDC WD800BEVT-22ZCT0>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 76319 MB, 155061 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
Kernelized RAIDframe activated
u3g0 at uhub0 port 1 configuration 1 interface 0
ucom0 at u3g0 portno 0: 3G Modem
u3g1 at uhub0 port 1 configuration 1 interface 1
ucom1 at u3g1 portno 1: 3G Modem
umass1 at uhub0 port 1 configuration 1 interface 2
umass1: HUAWEI Technologies HUAWEI Mobile, rev 1.10/0.00, addr 2
umass1: using SCSI over Bulk-Only
scsibus1 at umass1: 2 targets, 1 lun per target
cd0 at scsibus1 target 0 lun 0: <HUAWEI, Mass Storage, 2.31> cdrom removable
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)
umass1: BBB reset failed, STALLED
cd0(umass1:0:0:0): generic HBA error
i915drm0: interrupting at ioapic0 pin 16

>How-To-Repeat:
You use E-mobile D02HW & NetBSD/i386 6.0.

>Fix:

>Audit-Trail:
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/47080: E-mobile D02HW is not attached to uhmodem driver
Date: Mon, 7 Oct 2013 06:49:32 +0000

 (not sent to gnats)

    ------

 From: Pierre Pronchery <khorben@defora.org>
 To: netbsd-bugs@netbsd.org
 Subject: Re: kern/47080: E-mobile D02HW is not attached to uhmodem driver
 Date: Mon, 15 Oct 2012 20:09:31 +0200

 			Hi,

 On 15/10/2012 16:00, ishit@oak.dti.ne.jp wrote:
 > 
 > My E-mobile D02HW modem is not attached to uhmodem(4) driver.
 > My modem is attached to u3g(4) driver, and it works fine.

 AFAICT the u3g(4) obsoletes the (rather crashy) uhmodem(4) driver, and
 it is expected that your USB modem attaches to u3g(4) only. Does it work
 properly?

 HTH,
 -- 
 khorben

From: ishit <ishit@oak.dti.ne.jp>
To: khorben@defora.org, gnats-bugs@NetBSD.org, netbsd-bugs@netbsd.org,
        dholland-bugs@netbsd.org
Cc: 
Subject: Re: kern/47080: E-mobile D02HW is not attached to uhmodem driver
Date: Sun, 13 Oct 2013 05:52:31 +0900

 >  From: Pierre Pronchery <khorben@defora.org>
 >  To: netbsd-bugs@netbsd.org
 >  Subject: Re: kern/47080: E-mobile D02HW is not attached to uhmodem driver
 >  Date: Mon, 15 Oct 2012 20:09:31 +0200
 >  
 >  			Hi,
 >  
 >  On 15/10/2012 16:00, ishit@oak.dti.ne.jp wrote:
 >  > 
 >  > My E-mobile D02HW modem is not attached to uhmodem(4) driver.
 >  > My modem is attached to u3g(4) driver, and it works fine.
 >  
 >  AFAICT the u3g(4) obsoletes the (rather crashy) uhmodem(4) driver, and
 >  it is expected that your USB modem attaches to u3g(4) only. Does it work
 >  properly?
 >  
 >  HTH,
 >  khorben

 My E-mobile D02HW modem is attached to u3g(4) driver only, and it works properly.

 Thank you.

 ISIHARA,Takanori

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/47080: E-mobile D02HW is not attached to uhmodem driver
Date: Sun, 13 Oct 2013 04:41:42 +0000

 On Sat, Oct 12, 2013 at 10:05:01PM +0000, ishit wrote:
  > > > My E-mobile D02HW modem is not attached to uhmodem(4) driver.
  > > > My modem is attached to u3g(4) driver, and it works fine.
  > >  
  > >  AFAICT the u3g(4) obsoletes the (rather crashy) uhmodem(4) driver, and
  > >  it is expected that your USB modem attaches to u3g(4) only. Does it work
  > >  properly?
  > >  
  > >  HTH,
  > >  khorben
  >  
  > My E-mobile D02HW modem is attached to u3g(4) driver only, and it
  > works properly.

 I guess we should update the man pages. Should all the models listed
 in uhmodem(4) be shifted to u3g(4)? And should uhmodem(4) note that
 it's deprecated in favor of u3g(4)?

 -- 
 David A. Holland
 dholland@netbsd.org

From: ishit <ishit@oak.dti.ne.jp>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/47080: E-mobile D02HW is not attached to uhmodem driver
Date: Sun, 13 Oct 2013 18:25:15 +0900

 At Sun, 13 Oct 2013 04:45:00 +0000 (UTC), David Holland wrote:
 >   > >  AFAICT the u3g(4) obsoletes the (rather crashy) uhmodem(4) driver, and
 >   > >  it is expected that your USB modem attaches to u3g(4) only. Does it work
 >   > >  properly?
 >   > >  
 >   > >  HTH,
 >   > >  khorben
 >   >  
 >   > My E-mobile D02HW modem is attached to u3g(4) driver only, and it
 >   > works properly.
 >  
 >  I guess we should update the man pages. Should all the models listed
 >  in uhmodem(4) be shifted to u3g(4)? And should uhmodem(4) note that
 >  it's deprecated in favor of u3g(4)?

   I have a E-mobile D02HW only.
   I do not have other models.
   Probably, D01HW will run by u3g(4) as well as D02HW.

   I have no idea whether it should be shifted of all or not. 

   I agree about annotating to manuals of uhmodem(4) and u3g(4).

 # Like azalia(4) and hdaudio(4) ?

 Regards
 -- 
 ISIHARA,Takanori

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.