Bug 120034 - [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 G memory, works with 512 M
Summary: [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 G memory, works with 512 M
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-27 10:40 UTC by Kenneth Freidank
Modified: 2017-12-31 22:37 UTC (History)
0 users

See Also:


Attachments
dmesg_0.5G (6.95 KB, application/octet-stream)
2008-01-27 19:12 UTC, Kenneth Freidank
no flags Details
dmesg_1.0G (6.95 KB, application/octet-stream)
2008-01-27 19:12 UTC, Kenneth Freidank
no flags Details
dmesg_1.5G_nousb (5.10 KB, application/octet-stream)
2008-01-27 19:12 UTC, Kenneth Freidank
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Freidank 2008-01-27 10:40:02 UTC
Running 6.3 release from .iso disk image.  No modifications to kernel.
At 512 M of DDR2 memory, everything runs great.
..
ohci0: <ATI SB400 USB Controller> irq 19 at device 19.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: <ATI SB400 USB Controller> on ohci0
usb0: USB revision 1.0
..

Then I add 1 G of DDR2 memory so I have a total of 1.5 G of memory.  XP
runs great (dual boot with each OS on its own disk).  I even swapped the
location of the memory cards, i.e. 1G in one slot, and 512M in the other
slot.  XP still ran fine.  When I try FreeBSD, swapped or not, it hangs
on boot up.  ..
ohci0: <ATI SB400 USB Controller> irq 19 at device 19.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 0.0
usb0: unsupported OHCI revision
ohci0: USB init failed
device_attach: ohci0 attach returned 5
..the machine is hung at this point...

Fix: 

Remove the 1G chip.
How-To-Repeat: Leave in the 1G chip.
Also tried booting from the 6.2 release .iso image as well as booting off
the 6.3 release .iso image -- install kernel hung both times with the 1G
chip added for a total of 1.5 G.
Comment 1 Remko Lodder freebsd_committer 2008-01-27 10:44:21 UTC
Kenneth Freidank wrote:

Could you disable USB support in the bios and see where that leads
up to? could it be that the additional memory kicks in the USB
controller? and/or perhaps any other region?

You did not provide a full boot dmesg btw; just giving parts of
it makes it very hard to see what might be going on, in addition
it could be interesting to start the freebsd installation without
acpi support, and doing a boot verbose (that's 2 additional things
we might like to see).

Thanks,
remko

-- 
/"\   Best regards,                      | remko@FreeBSD.org
\ /   Remko Lodder                       | remko@EFnet
  X    http://www.evilcoder.org/          |
/ \   ASCII Ribbon Campaign              | Against HTML Mail and News
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2008-01-27 11:31:11 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-usb

reclassify.
Comment 3 Kenneth Freidank 2008-01-27 19:12:20 UTC
OK..more info.

Seems like disabling USB when 1.5G is plugged in works, but then I loose my working USB which I use for my working memory stick and floppy drive.

Enabling and disableing ACPI had no effect.

When I enable usb, dmesg is the same up to the point of hanging with the exception of the mem and iomem fields in the "atapci0" and "atapci1" lines.  With 1.5G and usb enabled, my hung kernel says:
atapci0: ...mem 0x80207600 - 0x802077ff... the port locations are the same
atapci1: ...mem 0x80207400 - 0x802075ff... the port locations are the same

Attached are full dmesg outputs of configurations that work, i.e. no hang:
"dmesg_0.5G" - 0.5G memory, full usb, full ACPI (6.3 .iso kernel)
"dmesg_1.0G" - 1.0G memory, full usb, full ACPI (6.3 .iso kernel)
"dmesg_1.5G_nousb" - 1.5G memory, no usb, full ACPI (6.3 .iso kernel)

I also tried 6.2 .iso kernel from the install CD and it still hangs with 1.5G.

I do not know how I can provide you with a full dmesg when the system hangs.  Can you tell me how I can log output of a boot sequence that hangs for later analysis?  I have no shells in which to run dmesg.  Extended logging does not help as I still do not know how to log it.



-----Original Message-----
>From: Remko Lodder <remko@FreeBSD.org>
>Sent: Jan 27, 2008 5:44 AM
>To: Kenneth Freidank <kennethcf@earthlink.net>
>Cc: freebsd-gnats-submit@FreeBSD.org
>Subject: Re: kern/120034: 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 G memory, works with 512 M
>
>Kenneth Freidank wrote:
>
>Could you disable USB support in the bios and see where that leads
>up to? could it be that the additional memory kicks in the USB
>controller? and/or perhaps any other region?
>
>You did not provide a full boot dmesg btw; just giving parts of
>it makes it very hard to see what might be going on, in addition
>it could be interesting to start the freebsd installation without
>acpi support, and doing a boot verbose (that's 2 additional things
>we might like to see).
>
>Thanks,
>remko
>
>-- 
>/"\   Best regards,                      | remko@FreeBSD.org
>\ /   Remko Lodder                       | remko@EFnet
>  X    http://www.evilcoder.org/          |
>/ \   ASCII Ribbon Campaign              | Against HTML Mail and News
Comment 4 Kenneth Freidank 2008-01-27 19:32:56 UTC
I forgot to mention my hardware:
emachines T5048
Intel Grant County 2 motherboard:  D102GGC2
BIOS: GC11020M.86A.1087.2007.0130.1451
- Pentium 4 524 Hyperthreaded, 3.06 GHz, 533 MHz FSB, 1 MB L2
- ATI Radeon XPRESS 200 Northbridge
- ATI IXP 450 Southbridge
- 4 Mbit Firmware Hub (FWH)
- Memory is 1.0 G DDR2 (slot 0), and 0.5 G DDR2 (slot 1)
- XP works

Intel Product Guide:  d4798502_en.pdf
Technical Spec:  d4427801us.pdf
Technical Spec Update:  d5947403us.pdf




-----Original Message-----
>From: Remko Lodder <remko@FreeBSD.org>
>Sent: Jan 27, 2008 5:44 AM
>To: Kenneth Freidank <kennethcf@earthlink.net>
>Cc: freebsd-gnats-submit@FreeBSD.org
>Subject: Re: kern/120034: 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 G memory, works with 512 M
>
>Kenneth Freidank wrote:
>
>Could you disable USB support in the bios and see where that leads
>up to? could it be that the additional memory kicks in the USB
>controller? and/or perhaps any other region?
>
>You did not provide a full boot dmesg btw; just giving parts of
>it makes it very hard to see what might be going on, in addition
>it could be interesting to start the freebsd installation without
>acpi support, and doing a boot verbose (that's 2 additional things
>we might like to see).
>
>Thanks,
>remko
>
>-- 
>/"\   Best regards,                      | remko@FreeBSD.org
>\ /   Remko Lodder                       | remko@EFnet
>  X    http://www.evilcoder.org/          |
>/ \   ASCII Ribbon Campaign              | Against HTML Mail and News
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:33 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped