LinuxQuestions.org - USB devises crash system

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - USB devises crash system (https://www.linuxquestions.org/questions/linux-newbie-8/usb-devises-crash-system-407285/)

USB devises crash system

OK please bare with me, although I'm not totally new to the whole Linux thing this is the first time I have chosen to ditch windows and do a full install.

I have just installed Slackware 10.2 and after getting every thing else working (Wi-Fi cards etc) I came to plugging in my USB GPS, that caused the system to freeze. The only way that I can restart the system is to remove the battery. (laptop)

Now the same thing happens when I plug in any USB device either before or after boot up. If someone could give me a few pointers as to how to fix this it would be very much appreciated.

BTW: The laptop is a Medion Sim2000, 1.3 Celeron m processor, 768MB of ram, Im not quite sure of the motherboard but most of the stuff on it (including USB) is SIS.

Gah, that's weird. Can you have a look through /var/log/kernel and see if there are any errors that you can see? It might help to cause the system to crash out and then reboot and immediately check the log file as there shouldn't be too much between the end of the file and the crash data (if any).

Quote:

Originally Posted by cs-cam

Mmmmm, Well I get as far as /var/log but kernel doesn't seem to exist. Should it be there? Or is it created in the event of a system failure?

OK, it's getting worse now after a reboot there seems to be a force check of the root file system that gives me, /dev/hda1: UNEXPECTED INCONSISTANCY; RUN fsck MANUALLY

It could be /var/log/messages, varies depending on the logger daemon you're using. System crashed create havoc in filesystems, if you're using ext2 I suggest running fsck on it then mkefs -j /dev/hda1 to convert it to ext3 (no data loss) which uses a journal to help protect against the damage hard resets can cause.

OK, I have now installed v10.1 to see if that made any difference, it didnt. Reinstalled v10.2 and am back to where I started from .:cry:

The log from /var/log/messages is:

Code:

Jan 24 18:48:16 lappy kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5

Jan 24 18:48:16 lappy kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5

Jan 24 18:48:16 lappy kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5

Jan 24 18:48:16 lappy kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4

Jan 24 18:48:16 lappy kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5

Jan 24 18:48:16 lappy kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5

Jan 24 18:48:16 lappy kernel: uhci.c: USB Universal Host Controller Interface driver v1.1

Jan 24 18:48:16 lappy kernel: usb-uhci.c: $Revision: 1.275 $ time 18:53:41 Jun  5 2005

Jan 24 18:48:16 lappy kernel: usb-uhci.c: High bandwidth mode enabled

Jan 24 18:48:16 lappy kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver

Jan 24 18:48:27 lappy logger: /etc/rc.d/rc.hotplug start (exiting script)

Jan 24 18:48:45 lappy sshd[2749]: Server listening on 0.0.0.0 port 22.

Jan 24 18:52:11 lappy syslogd 1.4.1: restart.

Jan 24 18:52:12 lappy kernel: klogd 1.4.1, log source = /proc/kmsg started.

Jan 24 18:52:12 lappy kernel: kmod: failed to exec /sbin/modprobe -s -k parport_lowlevel, errno = 2

Jan 24 18:52:12 lappy kernel: loop: loaded (max 8 devices)

Jan 24 18:52:12 lappy kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4

Jan 24 18:52:12 lappy kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx

Jan 24 18:52:12 lappy kernel: SIS5513: IDE controller at PCI slot 00:02.5

Jan 24 18:52:12 lappy kernel: SIS5513: chipset revision 0

Jan 24 18:52:12 lappy kernel: SIS5513: not 100%% native mode: will probe irqs later

Jan 24 18:52:12 lappy kernel: SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller

Jan 24 18:52:12 lappy kernel:    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA

Jan 24 18:52:12 lappy kernel:    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA

Jan 24 18:52:12 lappy kernel: hda: 78140160 sectors (40008 MB), CHS=4864/255/63, UDMA(33)

Jan 24 18:52:12 lappy kernel: hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)

Jan 24 18:52:12 lappy kernel: Uniform CD-ROM driver Revision: 3.12

The USB device was inserted at 18:51 so as far as I can see it has not been logged.

Sorry, tag me out. I've got no idea :( Never heard of that happening before. If you're not on dial-up I'd suggest downloading Knoppix and see if you experience the problems under that. It could be that Slack is incorrectly detecting your motherboard and loading the wrong modules for it that are crapping out or something :confused:

I had a similar issue on a barebones system I built up. Plug something into the front USB ports, INSTANT POWERDOWN! A very ungraceful shutdown. Plug it into one of the rear ports, everything worked fine.

It turned out that the barebones system was shipped to me with a jumper incorrectly set on the motherboard. I checked all the jumpers before initially powering on the system, but obviously missed this one.

Probably not an issue for your laptop however. I doubt you built the thing yourself. Did USB work when you used to have Windows installed on this same laptop?

Quote:

Originally Posted by haertig

Probably not an issue for your laptop however. I doubt you built the thing yourself. Did USB work when you used to have Windows installed on this same laptop?

Yep, and just to confuse things even more they work on the Whoppix live CD and every other live CD I have tried. (there have been a few)

Just to confuse things a bit more I have installed Debian and they work in that. But I refuse to give up and want to use Slackware.:scratch: I'm sure that there is an incompatible module or driver loading its self somewhere, now it's just a case of finding what one. Any ideas anyone?

have you tried plugging it in and turning the computer on? see if it will boot up? then maybe take a look at dmesg

Quote:

Originally Posted by bosewicht

have you tried plugging it in and turning the computer on? see if it will boot up? then maybe take a look at dmesg

Yep, if I do that it will not boot past the hardware detection stage.

It sounds like hotplug is loading an incorrect module. just outta curiosity. open up /etc/hotplug/blacklist and add hw_random to blacklist and try rebooting with the unit plugged in.

Still crashing in the same place. Im guessing that I have entered it in the right place.

Code:

# uhci ... usb-uhci handles the same pci class, so one of the two

# needs to be listed below.

usb-uhci

hw_random

# usbcore ... module is loaded implicitly, ignore it otherwise

usbcore

hw_random

# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices

de4x5



# At least 2.4.3 and later xircom_tulip doesn't have that conflict

# xircom_tulip_cb

dmfe

ok, I doubted if that would work, it was a stab in the dark. that module has given a lot of people probs before. You have it in the right place. Another thing to try is disable hotplug. boot the computer up with the unit plugged in. After its booted up. run hotplug. I don't know for sure in slack where it would be either /etc/init.d/hotplug start or /etc/rc.d/hotplug start. you get the point. Now if the unit is plugged in, it should lock your computer up. Thats ok, then maybe you can see what module hotplug is trying to load when it freezes and add that one to the blacklist.

Edit:
actually you could have just stopped hotplug and plugged it in then started hotplug...oh well

I like the way you are thinking, but when I run /etc/rc.d/rc.hotpulg I get a system beep and every thing freezes. (Damm I'm getting quick at pulling the battery out.)

now check the logs see what was the last module to load or the module that was loading when it froze.