LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Hang on triggering udev events- is there a buildup of events? (http://www.linuxquestions.org/questions/slackware-14/hang-on-triggering-udev-events-is-there-a-buildup-of-events-649392/)

sonichedgehog 06-15-2008 05:56 AM

Hang on triggering udev events- is there a buildup of events?
 
My 1999 microstar + pIII has a history of slow progress after a particular point in the boot process and I am questioning whether there is an "event" that is blocking my system?

I have read
http://www.linuxquestions.org/questi...%2Fudevtrigger

and

http://www.linuxquestions.org/questi...lation-645586/
Which are very helpful, but before I try again (which requires systemrescuecd so can be time consuming) I want to ask whether there is some other issue?

Full details of what I believe to be a related problem with this computer on another distro are on
http://www.linuxquestions.org/questi...rboard-640144/
All seemed OK until I needed an upgrade to experimental for particular application, then problem returned. I have since changed the power supply, no difference.

I am raising this as a separate issue from the excellent thread quoted above because, firstly, the problem with Debian was a hang beginning with
Code:

waiting for /dev to become fully populated...
which in my layman's thanking looks a bit like the hang I have in slackware, starting with
Code:

triggering udev events: /sbin/udevtrigger
and later on
Code:

triggering udev events: /sbin/udevtrigger  --retry-failed
and secondly, the first second and third boots on my new slackware 12.1 installation were fine. I had a resolution issue (noted on earlier thread, I am thinking on it) and modified field depth on xorg.config from 24 to 16 ( a quick fix that has worked for me before, and did in this case).

Straight after that, I experienced the "triggering udev events: /sbin/udevtrigger" delay and the system has never returned to normal speed.

I don't rule out hardware trouble, but ultimatebootcd says that all is well, and anyway the first few successful boots suggest a software problem.

Is there a list of "udev events" that I can either post here or perhaps clear? I can experiment without risk as all data is on another partition and it isn't my main computer. Thank you.

sonichedgehog 06-20-2008 07:28 PM

Having tried change to generic kernel in http://www.linuxquestions.org/questi...d-disk-650281/ problem not solved.
I'm hanging in there because there's never a problem using a live cd or loading a distro, m$ used to work, and the hdd in the comp at present was tried & tested on a reliable old mainboard.

More on udev: I've tried udevadm settle --timeout=10 and udevadm control --stop_events_queue, but that didn't help (& no doubt reverts back on next reboot unless configuration file is changed?) The first delay occurred at "Triggering udev events" straight after a xorg.config change, I'm sure something is happening in udev that keeps my processor permanently busy (when in slack, ksysguard shows cpu>95%)

Recalling that I had this on Debian prior to HDD change, and again recently with the present HDD, have to question whether, hardware fault or not, this mainboard is viable for a modern OS?

sonichedgehog 06-21-2008 12:45 PM

Have now loaded using huge.s on a spare partition with ext2 file system, and result is the same as generic kernel+ ext3. Observations:
Checking ps -e there were numerous instances of artsd running at one time, later a knotify message with option to close it down, which I did, still very slow.
ps result after multiple artsd problem ended:
Code:

UID        PID  PPID  C STIME TTY          TIME CMD
root        1    0  0 09:03 ?        00:00:03 init [3] 
root        2    0  0 09:03 ?        00:00:00 [kthreadd]
root        3    2  0 09:03 ?        00:00:00 [migration/0]
root        4    2  0 09:03 ?        00:00:00 [ksoftirqd/0]
root        5    2  0 09:03 ?        00:00:00 [events/0]
root        6    2  0 09:03 ?        00:00:00 [khelper]
root        98    2  0 09:03 ?        00:00:00 [kblockd/0]
root      105    2  0 09:03 ?        00:00:00 [ata/0]
root      106    2  0 09:03 ?        00:00:00 [ata_aux]
root      107    2  0 09:03 ?        00:00:00 [ksuspend_usbd]
root      113    2  0 09:03 ?        00:00:00 [khubd]
root      116    2  0 09:03 ?        00:00:00 [kseriod]
root      161    2  0 09:03 ?        00:00:00 [pdflush]
root      162    2  0 09:03 ?        00:00:00 [pdflush]
root      163    2  0 09:03 ?        00:00:00 [kswapd0]
root      205    2  0 09:03 ?        00:00:00 [aio/0]
root      229    2  0 09:03 ?        00:00:00 [jfsIO]
root      230    2  0 09:03 ?        00:00:00 [jfsCommit]
root      231    2  0 09:03 ?        00:00:00 [jfsSync]
root      233    2  0 09:03 ?        00:00:00 [xfslogd/0]
root      234    2  0 09:03 ?        00:00:00 [xfsdatad/0]
root      238    2  0 09:03 ?        00:00:00 [xfs_mru_cache]
root      243    2  0 09:03 ?        00:00:19 [gfs2_scand]
root      244    2  0 09:03 ?        00:00:00 [glock_workqueue]
root      919    2  0 09:03 ?        00:00:00 [scsi_tgtd/0]
root      996    2  0 09:03 ?        00:00:00 [exec-osm/0]
root      1002    2  0 09:03 ?        00:00:00 [block-osm/0]
root      1009    2  0 09:03 ?        00:00:00 [khpsbpkt]
root      1063    2  0 09:03 ?        00:00:00 [ksnapd]
root      1068    2  0 09:03 ?        00:00:00 [rpciod/0]
root      1124    1  0 09:03 ?        00:00:53 /sbin/udevd --daemon
root      2091    2  0 09:07 ?        00:00:00 [kpsmoused]
root      2301    1  0 09:10 ?        00:00:00 /usr/sbin/syslogd
root      2305    1  0 09:10 ?        00:00:00 /usr/sbin/klogd -c 3 -x
root      2440    1  0 09:12 ?        00:00:00 /usr/sbin/inetd
root      2452    1  0 09:13 ?        00:00:00 /usr/sbin/sshd
81        2468    1  0 09:13 ?        00:00:01 /usr/bin/dbus-daemon --system
82        2474    1  0 09:13 ?        00:00:03 /usr/sbin/hald --daemon=yes
root      2475  2474  0 09:13 ?        00:00:00 hald-runner
root      2482  2475  0 09:13 ?        00:00:00 hald-addon-input: Listening on /dev/input/event1
root      2492  2475  0 09:13 ?        00:00:07 hald-addon-storage: polling /dev/hdc (every 2 sec)
root      2498    1  0 09:13 ?        00:00:00 /usr/sbin/crond -l10
daemon    2500    1  0 09:13 ?        00:00:00 /usr/sbin/atd -b 15 -l 1
root      2538    1  0 09:14 ?        00:00:00 /usr/sbin/gpm -m /dev/mouse -t imps2
root      2540    1  0 09:14 tty1    00:00:01 -bash
root      2541    1  0 09:14 tty2    00:00:00 /sbin/agetty 38400 tty2 linux
root      2542    1  0 09:14 tty3    00:00:00 /sbin/agetty 38400 tty3 linux
root      2543    1  0 09:14 tty4    00:00:00 /sbin/agetty 38400 tty4 linux
root      2544    1  0 09:14 tty5    00:00:00 /sbin/agetty 38400 tty5 linux
root      2545    1  0 09:14 tty6    00:00:00 /sbin/agetty 38400 tty6 linux
root      2571    1  0 09:23 ?        00:00:00 kdm
root      2573  2571  1 09:23 tty7    00:07:58 /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-UaGJde
root      3331    2  0 15:40 ?        00:00:00 [scsi_eh_5]
root      3332    2  0 15:40 ?        00:00:00 [usb-storage]
root      3365  2475  0 15:41 ?        00:00:00 hald-addon-storage: polling /dev/sda (every 2 sec)
root      3685  2571  0 16:18 ?        00:00:00 -:0
root      3696  3685  0 16:19 ?        00:00:00 /bin/sh /usr/bin/startkde
root      3742    1  0 16:20 ?        00:00:00 start_kdeinit --new-startup +kcminit_startup
root      3743    1  0 16:21 ?        00:00:05 kdeinit Running...                                         
root      3746    1  0 16:21 ?        00:00:00 dcopserver [kdeinit] --nosid                               
root      3748  3743  0 16:22 ?        00:00:02 klauncher [kdeinit] --new-startup                         
root      3750    1  3 16:22 ?        00:00:41 kded [kdeinit] --new-startup                               
root      3752    1  0 16:22 ?        00:00:00 /usr/libexec/gam_server
root      3757  3696  0 16:22 ?        00:00:00 kwrapper ksmserver
root      3759    1  0 16:22 ?        00:00:03 ksmserver [kdeinit]                                       
root      3760  3743  1 16:22 ?        00:00:13 kwin [kdeinit] -session 10dfdd6762000121404731800000028420 
root      3762    1  3 16:22 ?        00:00:33 kdesktop [kdeinit]                                         
root      3764  3743  0 16:23 ?        00:00:02 kio_file [kdeinit] file /tmp/ksocket-root/klauncherALdT7b. 
root      3765    1  2 16:23 ?        00:00:23 kicker [kdeinit]                                           
root      3775    1  0 16:26 ?        00:00:03 knotify [kdeinit]                                         
root      3778    1  0 16:26 ?        00:00:03 klipper [kdeinit]                                         
root      3780    1  0 16:26 ?        00:00:03 kaccess [kdeinit]                                         
root      3781    1  1 16:27 ?        00:00:08 korgac --miniicon korganizer
root      3811  3743 14 16:33 ?        00:01:08 konqueror [kdeinit] --silent                               
root      3813  3743  4 16:33 ?        00:00:20 konsole [kdeinit] --ls                                     
root      3814  3813  0 16:34 pts/1    00:00:00 -bash
root      3852  3814  0 16:41 pts/1    00:00:00 ps -e -f

dmesg result:
Code:

Linux version 2.6.24.5-smp (root@midas) (gcc version 4.2.3) #1 SMP Wed Apr 30 13:18:13 CDT 2008
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000fee0000 (usable)
 BIOS-e820: 000000000fee0000 - 000000000fef0000 (ACPI data)
 BIOS-e820: 000000000fef0000 - 000000000ff00000 (ACPI NVS)
 BIOS-e820: 000000000ff00000 - 0000000010000000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
254MB LOWMEM available.
Entering add_active_range(0, 0, 65248) 0 entries of 256 used
Zone PFN ranges:
  DMA            0 ->    4096
  Normal      4096 ->    65248
  HighMem    65248 ->    65248
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->    65248
On node 0 totalpages: 65248
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 477 pages used for memmap
  Normal zone: 60675 pages, LIFO batch:15
  HighMem zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
DMI 2.3 present.
Allocating PCI resources starting at 20000000 (gap: 10000000:eff80000)
swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000e0000
swsusp: Registered nosave memory region: 00000000000e0000 - 0000000000100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64739
Kernel command line: BOOT_IMAGE=Slack-12.1 ro root=301 vt.default_utf8=0 acpi=off noapic
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffb000 (0120c000)
Enabling fast FPU save and restore... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Detected 501.155 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 252840k/260992k available (2781k kernel code, 7700k reserved, 1093k data, 260k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xffe15000 - 0xfffff000  (1960 kB)
    pkmap  : 0xff800000 - 0xffc00000  (4096 kB)
    vmalloc : 0xd0800000 - 0xff7fe000  ( 751 MB)
    lowmem  : 0xc0000000 - 0xcfee0000  ( 254 MB)
      .init : 0xc04d0000 - 0xc0511000  ( 260 kB)
      .data : 0xc03b7686 - 0xc04c8ce4  (1093 kB)
      .text : 0xc0100000 - 0xc03b7686  (2781 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
Calibrating delay using timer specific routine.. 1003.49 BogoMIPS (lpj=2006998)
Security Framework initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0183f9ff 00000000 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0183f9ff 00000000 00000000 00000040 00000000 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 13k freed
CPU0: Intel Celeron (Mendocino) stepping 05
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
net_namespace: 64 bytes
xor: measuring software checksum speed
  8regs    :  913.000 MB/sec
  8regs_prefetch:  777.000 MB/sec
  32regs    :  435.000 MB/sec
  32regs_prefetch:  443.000 MB/sec
  pII_mmx  :  1304.000 MB/sec
  p5_mmx    :  1358.000 MB/sec
xor: using function: p5_mmx (1358.000 MB/sec)
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0480-04bf claimed by ICH4 GPIO
PCI: Transparent bridge - 0000:00:1e.0
PCI: Using IRQ router PIIX/ICH [8086/2410] at 0000:00:1f.0
PCI: Bridge: 0000:00:1e.0
  IO window: a000-afff
  MEM window: efd00000-efdfffff
  PREFETCH window: e7b00000-e7bfffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
Time: tsc clocksource has been installed.
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 865k freed
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
async_tx: api initialized (async)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Boot video device is 0000:00:01.0
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
PCI: setting IRQ 11 as level-triggered
PCI: Found IRQ 11 for device 0000:00:1f.6
PCI: Sharing IRQ 11 with 0000:00:1f.5
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: module loaded
input: Macintosh mouse button emulation as /devices/virtual/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH: IDE controller (0x8086:0x2411 rev 0x02) at  PCI slot 0000:00:1f.1
ICH: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: ExcelStor Technology J240, ATA DISK drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
hda: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: GENERIC CRD-BP1500P, ATAPI CD/DVD-ROM drive
hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hdc: MWDMA2 mode selected
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 80418240 sectors (41174 MB) w/1863KiB Cache, CHS=65535/16/63
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
usbmon: debugfs is not available
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1    142 MB/s
raid6: int32x2    149 MB/s
raid6: int32x4    129 MB/s
raid6: int32x8    128 MB/s
raid6: mmxx1      408 MB/s
raid6: mmxx2      483 MB/s
raid6: using algorithm mmxx2 (483 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
md: multipath personality registered for level -4
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
Freeing unused kernel memory: 260k freed
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 489972k swap on /dev/hda2.  Priority:-1 extents:1 across:489972k
Linux agpgart interface v0.102
Intel 82802 RNG detected
agpgart: Detected an Intel i810 Chipset.
agpgart: AGP aperture is 64M @ 0xe8000000
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware
iTCO_wdt: No card detected
USB Universal Host Controller Interface driver v3.0
PCI: setting IRQ 10 as level-triggered
PCI: Found IRQ 10 for device 0000:00:1f.2
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: UHCI Host Controller
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 10, io base 0x0000cc00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
uhci_hcd 0000:01:01.0: UHCI Host Controller
uhci_hcd 0000:01:01.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:01:01.0: irq 11, io base 0x0000a400
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:01:01.1: UHCI Host Controller
uhci_hcd 0000:01:01.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:01:01.1: irq 5, io base 0x0000a800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input2
i810_smbus 0000:00:01.0: i810/i815 i2c device found.
fuse init (API version 7.9)
PCI: Found IRQ 11 for device 0000:00:1f.5
PCI: Sharing IRQ 11 with 0000:00:1f.6
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 54504 usecs
intel8x0: clocking to 48000
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
EXT3 FS on hda1, internal journal
Linux Tulip driver version 1.1.15 (Feb 27, 2007)
tulip0:  MII transceiver #1 config 1000 status 7849 advertising 05e1.
eth0: ADMtek Comet rev 17 at MMIO 0xefdffc00, 00:50:bf:99:a7:f7, IRQ 9.
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
ehci_hcd 0000:01:01.2: EHCI Host Controller
ehci_hcd 0000:01:01.2: new USB bus registered, assigned bus number 4
ehci_hcd 0000:01:01.2: irq 10, io mem 0xefdffb00
ehci_hcd 0000:01:01.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 4 ports detected
lp0: using parport0 (polling).
lp0: console ready
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
0000:01:00.0: tulip_stop_rxtx() failed (CSR5 0xfc06c012 CSR6 0xff970111)
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
0000:01:00.0: tulip_stop_rxtx() failed (CSR5 0xfc06c012 CSR6 0xff970111)
0000:01:00.0: tulip_stop_rxtx() failed (CSR5 0xfc06c012 CSR6 0xff970111)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
usb 2-1: new full speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 0:0:0:0: Direct-Access    USB      Flash Drive      1.89 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 64000 512-byte hardware sectors (33 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 64000 512-byte hardware sectors (33 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
usb-storage: device scan complete
sd 0:0:0:0: Attached scsi generic sg0 type 0


C-Sniper 06-21-2008 03:56 PM

triggering udev events: /sbin/udevtrigger --retry-failed,

That is just loading all the Kernel modules that were not in use at the start (due to the device not being initialized yet) so it can take a while depending on the way the machine is set up. (i believe that is what it is if i am not please correct me)

sonichedgehog 06-22-2008 06:49 AM

I don't know exactly- I thought it was the same as populating /dev with the hardware as in the the Debian bootup. A duff HDD is the obvious culprit, but not here as this HDD works in another machine, so either there is a module working in a permanent loop and this continues even when the boot is concluded, CPU at >85% all the time (has to be a specific incompatibility with this mainboard as older ones have worked fine for me...)
or the mainboard is itself defective and the tool to which your final para refers is appropriate!

T3slider 06-22-2008 07:12 AM

Is this relevant?
Quote:

Originally Posted by CHANGES_AND_HINTS.TXT
If you notice extremely long wait times when formatting partitions in the
installer, and you're installing on a Thinkpad that has a SATA drive, it's
possible that the wrong driver is being used, which disables DMA on the drive
(and could happen on other machines). A bit more detail about it is here:
http://www.thinkwiki.org/wiki/Proble...stem_hard_disk
Try passing "hda=noprobe" to the kernel when booting the installer, and it
should use the correct libata driver.

It looks partially relevant, but I can't be sure. Do you happen to know if your drive is SATA or PATA? (It is currently being recognized as PATA)

shadowsnipes 06-22-2008 01:19 PM

Quote:

Originally Posted by sonichedgehog (Post 3190742)
Again thank you. Result of
Code:

hdparm -d /dev/hda
is dma=1. However, with nothing to lose, I tried Alien's instructions. Booting from the cd, with
Code:

hugesmp.s hda=noprobe
produced a strange result- none of my partitions were loaded on /dev, either as hda1,2 etc or sda1,sda2... I went through /dev and checked whether my partitions had appeared as anything else, they didn't.

Seeing as how dma was on, that is not problem. The problem is your drive is taking too long to be detected properly. You may have to specify the correct module to use or blacklist a particular module.

Quote:

Originally Posted by sonichedgehog (Post 3190742)
I have also tried appending hda-noprobe in lilo and making the suggested changes in lilo.conf & fstab. Not accepted in lilo as sda doesn't exist.

Right. You can't run lilo with those changes unless sda corresponds to the correct drive. You would have to boot with hda=noprobe on the install cd, mount your root partition, cd into, chroot, edit lilo (change the hda's to sda's and add the noprobe option), and then run lilo. You would have to do a similar procedure to change it back.

I think your drive really is PATA, though, so you shouldn't need to do this.

Quote:

Originally Posted by C-Sniper (Post 3191300)
triggering udev events: /sbin/udevtrigger --retry-failed,

That is just loading all the Kernel modules that were not in use at the start (due to the device not being initialized yet) so it can take a while depending on the way the machine is set up. (i believe that is what it is if i am not please correct me)

It sounds like you need to specify the module that needs to be loaded (in rc.modules*) so probing isn't necessary for that hardware. Turning off probing might be needed as well, but it looks like it won't work unless you tell the kernel what you need. The big thing is to make sure that the right module is actually used. Hopefully it isn't something odd that isn't already built for the kernel (that would mean you would have to build a custom kernel).

sonichedgehog 06-23-2008 04:40 AM

Quote:

The problem is your drive is taking too long to be detected properly. You may have to specify the correct module to use or blacklist a particular module.
OK! I like the idea of turning off the module that's hanging the boot up & killing performance & can envisage a solution that involves disabling some of the detection by commenting lines out, and re-enabling if & when there has been a hardware change.

What should I be looking for in rc.modules? I expect to have to try suppressing a number of modules one at a time and noting the effect, but if I went in right now it would be almost random.

Quote:

Hopefully it isn't something odd that isn't already built for the kernel (that would mean you would have to build a custom kernel).
Could be worthwhile, this may be anecdotal but I know of several comps like mine- which were excellent with W98- that were discarded due to software issues. Well, if it comes to building a custom kernel, I'll try anything once but there might be a month before I post again. I know there's lost of material out there and a recommendation for a beginner will be most helpful!

Thanks T3slider, but I have seen this before, probably when checking out

http://www.linuxquestions.org/questi...6/#post3169143

as suggested. There was a lot of investigation into markluocanada's HDD, but I think, as shadowsnipes suggests, noting that I have DMA, I don't need to look further into this.

shadowsnipes 06-23-2008 09:29 AM

The first thing you need to do is to properly identify your hardware. In particular, since we suspect your hard disk is taking a while to probe, we are interested in your disc controller(s).
Show us the output of
Code:

lspci -v
. Also, if you dual boot with Windows you can check under its hardware interface. Finally, it would be a good idea to see if there is any wiki or forum for your particular machine. Try searching around for it. At a minimum there should be a site that details the specs of your machine (ie. the manufacturer's site). There might be other good information there as well.

After the hardware is identified then you will need to look through the kernel docs to see how to support it. You could grep the docs for your device or make menuconfig and search through the disc controller options (there are help files you can read as well in there). You could also check which modules are loaded after your system is booted up.
Show us the output of
Code:

lsmod
. One of those might be the one that we need to specify. Once the module(s) that is needed is identified then you just add a modprobe line for it in rc.modules*. If we find there is a conflicting module then we will need to blacklist it.

sonichedgehog 06-25-2008 06:59 PM

Result of lspci:
Code:

00:00.0 Host bridge: Intel Corporation 82810 GMCH (Graphics Memory Controller Hub) (rev 03)
        Subsystem: Intel Corporation 82810 GMCH (Graphics Memory Controller Hub)
        Flags: bus master, fast devsel, latency 0
        Kernel driver in use: agpgart-intel
        Kernel modules: intel-agp

00:01.0 VGA compatible controller: Intel Corporation 82810 (CGC) Chipset Graphics Controller (rev 03) (prog-if 00 [VGA controller])
        Subsystem: Intel Corporation Unknown device 0200
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 9
        Memory at e8000000 (32-bit, prefetchable) [size=64M]
        Memory at eff80000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [dc] Power Management version 1
        Kernel driver in use: i810_smbus
        Kernel modules: i2c-i810

00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
        I/O behind bridge: 0000a000-0000afff
        Memory behind bridge: efd00000-efdfffff
        Prefetchable memory behind bridge: e7b00000-e7bfffff
        Kernel modules: shpchp

00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02)
        Flags: bus master, medium devsel, latency 0
        Kernel modules: iTCO_wdt, intel-rng

00:1f.1 IDE interface: Intel Corporation 82801AA IDE Controller (rev 02) (prog-if 80 [Master])
        Subsystem: Intel Corporation 82801AA IDE Controller
        Flags: bus master, medium devsel, latency 0
        [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
        [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
        [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
        [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
        I/O ports at ffa0 [size=16]
        Kernel driver in use: PIIX_IDE

00:1f.2 USB Controller: Intel Corporation 82801AA USB Controller (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801AA USB Controller
        Flags: bus master, medium devsel, latency 0, IRQ 10
        I/O ports at cc00 [size=32]
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci-hcd

00:1f.5 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 02)
        Subsystem: Intel Corporation Unknown device 4001
        Flags: bus master, medium devsel, latency 0, IRQ 11
        I/O ports at d400 [size=256]
        I/O ports at d000 [size=64]
        Kernel driver in use: Intel ICH
        Kernel modules: snd-intel8x0

00:1f.6 Modem: Intel Corporation 82801AA AC'97 Modem Controller (rev 02) (prog-if 00 [Generic])
        Subsystem: Intel Corporation 82801AA AC'97 Modem Controller
        Flags: medium devsel, IRQ 11
        I/O ports at dc00 [size=256]
        I/O ports at d800 [size=128]
        Kernel modules: snd-intel8x0m

01:00.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)
        Subsystem: SiteCom Europe BV Unknown device 0020
        Flags: bus master, medium devsel, latency 64, IRQ 9
        I/O ports at ac00 [size=256]
        Memory at efdffc00 (32-bit, non-prefetchable) [size=1K]
        Expansion ROM at e7b00000 [disabled] [size=128K]
        Capabilities: [c0] Power Management version 2
        Kernel driver in use: tulip
        Kernel modules: tulip

Result of lsmod:
Code:

Module                  Size  Used by
nls_iso8859_1          7808  1
nls_cp437              9472  1
vfat                  14592  1
fat                    49692  1 vfat
sg                    30224  0
usb_storage            84288  1
snd_seq_dummy          6660  0
snd_seq_oss            32896  0
snd_seq_midi_event    10112  1 snd_seq_oss
snd_seq                50256  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device        10380  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            40352  0
snd_mixer_oss          17920  1 snd_pcm_oss
ipv6                  234724  10
pcmcia                35884  0
pcmcia_core            35988  1 pcmcia
lp                    13348  0
parport_pc            27556  1
parport                34632  2 lp,parport_pc
fuse                  45588  1
tulip                  52256  0
snd_intel8x0          31900  0
snd_ac97_codec        98724  1 snd_intel8x0
ac97_bus                5760  1 snd_ac97_codec
snd_pcm                72068  3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              22532  2 snd_seq,snd_pcm
snd                    47716  9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
serio_raw              9092  0
soundcore              9824  1 snd
snd_page_alloc        11528  2 snd_intel8x0,snd_pcm
evdev                  12672  1
psmouse                40336  0
i2c_i810                8068  0
shpchp                32788  0
uhci_hcd              25996  0
i2c_algo_bit            9476  1 i2c_i810
iTCO_wdt              13988  0
iTCO_vendor_support    7044  1 iTCO_wdt
intel_agp              25236  1
i2c_core              22528  2 i2c_i810,i2c_algo_bit
agpgart                30664  1 intel_agp
intel_rng              8448  0
ext3                  124808  2
jbd                    43924  1 ext3
mbcache                10496  1 ext3
ata_generic            8836  0
pata_acpi              8832  0

Meanwhile, I have tried some further experiments & research.

The comp is Tiny 1999 with Excelstor J240 40gB HDD salvaged from a later Tiny (2002). Following Tiny's demise there is AFAICT nothing of technical value on the net relating to Tiny, so I have concentrated on the mainboard. I had access to the manual (typed MS6178 on search engine) before starting this thread, it is useful for hardware building but I didn't find anything relevant to the current problem.

If necessary I could get a M$ ghost image that I previously saved back on the comp, then reinstall slack as dual boot, but haven't done so yet. (I only dual boot with M$ on my latest comp because vista was provided and it's foolish to lose it)


The /udev delay has, according to several sources, been associated with usb devices. I tried removing the usb2.0 card (the mainboard has 2 built in usb1's) and the next boot was fast, into a fully effective system. On reboot, however, the system hung at /udev. Replacing the card made no difference.

I then did the same with the modem card- and the result was identical. The next boot was fast. I used the os for a while and am satisfied that it is fully effective if the boot has proceeded normally. The following boot was slow, and I could not "provoke" a normal boot by fiddling with bits of hardware.


So, is the udev daemon working effectively only on the first occasion after a hardware change? If so it is not consistent.

The following is slightly worrying.

http://www.coreboot.org/News#2007.2F..._now_supported

http://www.coreboot.org/MSI_MS-6178_Build_Tutorial

In summary, it is stated that Linux had never worked with the MS 6178 mainboard, and the above provides a bios flash utility to overcome this.

I would question the indication that Linux and the MS6178 with original bios are incompatible- my system is almost working. I have checked LQ for coreboot discussion & found nothing directly relevant to this case.

I have the source from svn, and the howto insists that the bios saviour is essential- I can see why. No serious risk here as this is an ex-work mainboard of little value, but the procedure seems troublesome and I think flawed- I am sure you need your linux os up and running in order to use the software. But I have probably missed something.

Maybe your suggestion of suppressing/enabling relevant modules will work? I don't know where to go with the checking of pci & module info against kernel docs, would welcome further guidance.

Many thanks _ Phil

shadowsnipes 06-26-2008 11:10 PM

I just remembered something I meant to mention before. Why don't you try to increase the verbosity of the udev events and then recheck your logs?

Try changing /etc/udev/udev.conf's udev_log to "info" or even "debug".

Also, in /etc/rc.d/rc.udev, try modifying this line
Code:

        /sbin/udevtrigger $OPT && /sbin/udevsettle --timeout=120
Adding --verbose to the udevtrigger (and the other verbosity change) might help you really determine where the sticking point is.

You could also shorten the timeout dramatically, but you may have to manually load the modules that don't "settle". You already have a list of modules that get loaded, so any that are missing probably need to be manually loaded if the timeout is not long enough.

sonichedgehog 06-30-2008 07:19 AM

Of the extemely "verbose" output following the suggested changes, I identified the following:

Code:

Jun 29 13:36:17 localhost kernel: Intel ISA PCIC probe: not found.
Jun 29 13:36:17 localhost kernel: Databook TCIC-2 PCMCIA probe: not found.

Working on this, I find http://ubuntuforums.org/showthread.php?t=286827

http://random.openminds.be/2007/02/1...obe-not-found/

and

http://www.linuxquestions.org/questi...aviour-492115/

However, the suggested changes did not work. The message related to PCIC & PCMCIA disappeared but otherwise no difference. So, I restored the affected files.

From the messages log, I can see that, straight after a modprobe that detected my mainboard, the hang began and went to my new timeout (set at 30 seconds).

AFter that, there is a message:

Jun 30 07:38:38 localhost udevd-event[2185]: run_program: '/sbin/modprobe' (stderr) 'FATAL: Module pci:v00008086d00002416sv00008086sd00002416bc07sc03i00 not found.'

That, I regret, is as far as I can go, and I have to ask for some help in interpreting the rest. I can see that the processor is locked into a long operation, but don't know how to address it.

I have posted the files at http://cid-110ecf7e446877f7.skydrive...se.aspx/Public (they are too long to post here)

If you have time (and I realize this is becoming a messy, time consuming task- thank you!) please take a look at the messages 30 june log (my comments in red with <<>>). 29 june shows result of pcmcia changes, now reversed. The other files are there is case they prove useful.

-Phil

shadowsnipes 06-30-2008 09:27 AM

Quote:

Originally Posted by sonichedgehog (Post 3199187)
Of the extemely "verbose" output following the suggested changes, I identified the following:

Code:

Jun 29 13:36:17 localhost kernel: Intel ISA PCIC probe: not found.
Jun 29 13:36:17 localhost kernel: Databook TCIC-2 PCMCIA probe: not found.

Working on this, I find http://ubuntuforums.org/showthread.php?t=286827

http://random.openminds.be/2007/02/1...obe-not-found/

and

http://www.linuxquestions.org/questi...aviour-492115/

However, the suggested changes did not work. The message related to PCIC & PCMCIA disappeared but otherwise no difference. So, I restored the affected files.

Are you using a Cardbus or other type of PCMCI device? If this isn't a laptop then the answer is likely to be no, so you can safely just take away the execute perms on /etc/rc.d/rc.pcmcia.

Quote:

Originally Posted by sonichedgehog (Post 3199187)
From the messages log, I can see that, straight after a modprobe that detected my mainboard, the hang began and went to my new timeout (set at 30 seconds).

Ah, now we are finding what we were looking for! This is good news, but it is bad news that the problem is with your mainboard. I haven't looked at all the files (much less really read through them), but it sounds like this is the real problem area as you mentioned.

Code:

Jun 30 07:36:49 localhost udevd-event[2194]: run_program: '/sbin/modprobe dmi:bvnAmericanMegatrendsInc.:bvr62710:bd05/20/99:svnMicro-StarInc.:pnMS-6178:pvr1.0:rvnMicro-StarInc.:rnMS-6178:rvr1.0:cvnINTELString:ct3:cvr0000000:'
Jun 30 07:36:49 localhost udevd-event[2196]: run_program: '/sbin/modprobe input:b0017v0001p0001e0100-e0,1,2,k110,111,112,r0,1,amlsfw'
Jun 30 07:37:20 localhost udevsettle[2179]: udevsettle: timeout waiting for queue

If you take away the verbose and debug options (leaving the timeout at 30) does your system boot faster or slower than before (with default timeout of 120)? Use a stopwatch. If your system actually takes longer to boot with a shorter timeout try increasing the timeout to 60 and then compare (again versus timeout of 120).

Since the problem, as you suspected previously, appears to be your mainboard you can try a few things. First, try using the non-smp huge kernel. Second, poke around your BIOS and see if there is anything useful you can change. You might even need to update your BIOS (version 2.1 looks like the latest). Here is the Micro-Star page for your MS-6178. You can find the BIOS updates there.

I wouldn't worry about the coreboot pages you were looking at earlier, by the way. Just look at the description of the project:
Quote:

Originally Posted by Coreboot homepage
coreboot (formerly known as LinuxBIOS) is a Free Software project aimed at replacing the proprietary BIOS (firmware) you can find in most of today's computers.


sonichedgehog 06-30-2008 06:38 PM

I'd like to go straight for the BIOS- kill or cure!

Thanks for the safer suggestions:

Quote:

...you can safely just take away the execute perms on /etc/rc.d/rc.pcmcia.
No, not a laptop. I suspected it made no difference either way, but I restored the execute perms to ensure that I hadn't introduced a new problem before posting the log on my webspace.

Quote:

try using the non-smp huge kernel. Second, poke around your BIOS and see if there is anything useful you can change.
I have huge.s kernel (is that the correct one to try?) on another partition, I haven't examined the logs but it is behaving exactly the same. I have also looked at the BIOS and fiddled around (some time ago). There's not much that can be changed, compared to, for example, my trusty MS-5168. No luck there.

On the timing, it's not just the long boot- the system is "preoccupied" all the time.

I'll take your advice and leave corebios alone so...

Thanks for the Microstar link. I didn't see it previously because I went straight to the manual. Even at first glance, it all looks very microsoft, so -am I right? - I should swallow my pride, restore my XP image for now, and use the .zip's and .exe's in the traditional way.

Anyway, I'm very grateful for all your help. I'm sensing that the end of the quest is near- although whether through a successful outcome or a trashed bios remains to be seen!

shadowsnipes 06-30-2008 10:03 PM

Quote:

Originally Posted by sonichedgehog (Post 3199745)
I have huge.s kernel (is that the correct one to try?) on another partition, I haven't examined the logs but it is behaving exactly the same. I have also looked at the BIOS and fiddled around (some time ago). There's not much that can be changed, compared to, for example, my trusty MS-5168. No luck there.

I was talking about using /boot/vmlinuz-huge-* instead of vmlinuz-huge-smp-* or the generic kernel (for now). According to the logs you posted it looked like you were still using the smp kernel and it complained. Usually this does not matter, but with some older machines it can make a big difference, so I thought it was worth a quick check.

Quote:

Originally Posted by sonichedgehog (Post 3199745)
On the timing, it's not just the long boot- the system is "preoccupied" all the time.

Good to know that. I don't think you mentioned this before. That could mean that the hardware isn't just slow to detect, but that it never got detected/loaded properly.

Quote:

Originally Posted by sonichedgehog (Post 3199745)
Thanks for the Microstar link. I didn't see it previously because I went straight to the manual. Even at first glance, it all looks very microsoft, so -am I right? - I should swallow my pride, restore my XP image for now, and use the .zip's and .exe's in the traditional way.

Anyway, I'm very grateful for all your help. I'm sensing that the end of the quest is near- although whether through a successful outcome or a trashed bios remains to be seen!

Do you even need a BIOS update? What version do you have? As I said in my last post version 2.1 is the latest. And, no you should not need anything M$ to use a BIOS update. Most of the time you just extract the zip files into a formatted bootable floppy and then boot into it. Read any readme.txt's first. You should be able to get the boot floppy set up just fine in Linux.

It might also be worth a shot to try the Online customer support that MSI has. They might be of no help, but then again it shouldn't take long to find out, and they might be able to at least point you in the right direction.

Has any *nix OS worked properly on this machine recently? If not, you may want to try a LiveCD (or a couple) with good hardware detection like Knoppix or something similar. If it appears to work fine then take a look at its logs and the modules that get loaded.

Oh, and if your BIOS has a QuickBoot, try turning it off.


All times are GMT -5. The time now is 02:49 AM.