frozen issues in gigabyte motherboard ga-8s648fxm2 bluetooth ohci

Bug #164816 reported by Juan Pedro Paredes
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6-686

First I have to install kubunto 7.10 using another mother board, cause install kubuntu in 7.10 now is impossible.
It hangs the computer without dump logs,panics, without the possibility of SysReq dumps, etc. Really strange, sure.
I decided to follow the thread to see what is really happened. I decide to debug the boot of the ga-8s648fxm2.

First, the MB always was frozen when I have some usb devices connected

Bus 003 Device 003: ID 050d:0121 Belkin Components F5D5050 100Mbps Ethernet
this is a bluetooth device and I solve his troubleshooting with blacklisting the pegasus module that has have the same USB ID
Bus 002 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Bus 002 Device 003: ID 06b9:4061 Alcatel Telecom SpeedTouch ISDN or ADSL Modem
ADSL modem
Bus 004 Device 002: ID 03f0:4d11 Hewlett-Packard
Printer
Bus 001 Device 006: ID 058f:6362 Alcor Micro Corp.
SD MMC reader

I remove
Bus 003 Device 003: ID 050d:0121 Belkin Components F5D5050 100Mbps Ethernet
Bus 002 Device 003: ID 06b9:4061 Alcatel Telecom SpeedTouch ISDN or ADSL Modem
Bus 004 Device 002: ID 03f0:4d11 Hewlett-Packard
Bus 001 Device 006: ID 058f:6362 Alcor Micro Corp.

Well, I obtain some steps in the booting process, later it appears to be frozen in the /etc/init.d/bluetooth script
Then I disable the /etc/init.d/bluetooth setting exit 0 in the second line of the script.

Now is the time i see the light, cause i attain to boot completely
Now i think in ohci as a target, an think than debian, the ancient distro installed in this computer, don't have this kind of problems.

i got a git repository of 2.6.23 kernel and a config used in debian, boot well, i activate bluetooth
boot well too, later the usb devices plugged, as expected it boots

I got the same git but using config-2.6.22-14-generic of ubuntu, and the problematic was the same as described

Now I have 2 config files, one god an one worse, an i need some ideas an help to debug this

Revision history for this message
Juan Pedro Paredes (juampe) wrote :
Revision history for this message
Juan Pedro Paredes (juampe) wrote :

2.6.23 config good

Revision history for this message
Ricardo L. Febrero (rlfebrero) wrote :

I dont's know if it has something to do with this, but I have the same USB adapter and a Gigabyte Ma-69G-3H motherboard, and I have the same lockup when plugging a SD Card, only if SD. It happens a while after inserting it. I'm going to debug it.

Revision history for this message
Ricardo L. Febrero (rlfebrero) wrote :

Sorry, here's my lsusb:

Bus 006 Device 007: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
(same as yours)
Bus 006 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 004: ID 062a:0000 Creative Labs Optical mouse
Bus 001 Device 003: ID 04a9:1094 Canon, Inc. PIXMA iP3000x Printer
Bus 001 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 002 Device 003: ID 05d8:4002 Ultima Electronics Corp. Artec Ultima 2000 (GT6801 based)/Lifetec LT9385/ScanMagic 1200 UB Plus Scanner
Bus 002 Device 002: ID 04d9:0461 Holtek Semiconductor, Inc.
Bus 002 Device 001: ID 0000:0000

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in linux-meta:
status: New → Incomplete
Revision history for this message
Juan Pedro Paredes (juampe) wrote : Re: [Bug 164816] Re: frozen issues in gigabyte motherboard ga-8s648fxm2 bluetooth ohci

Daniel T Chen escribió:
> Is this symptom still reproducible in 8.10?
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: linux-meta => linux
> Status: New => Incomplete
>
>
Sorry, actually my ga-8s648fxm2 were defunct, R.I.P.
I can't offer more information.
Regards.

Revision history for this message
Andy Whitcroft (apw) wrote :

The reporter indicates that they no longer have the hardware to test. Therefore moving this Won't FIx. If you have the issue indicated and hardware to test with please reopen this bug by moving it to New. Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.