Opened 2 years ago

Closed 2 years ago

#13567 closed bug (fixed)

hrev51208 x86_64 no USB devices after update

Reported by: vidrep Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86-64

Description

Updated hrev51205 x86_64 to hrev51208 After reboot, no USB mouse or keyboard Rebooting to previous state (hrev51205), all is OK again

Downloaded hrev51207 x86_64 anyboot image Installed to two different PC's (HP 8300 and Dell Optoplex 780) Mouse and keyboard OK with hrev51207 After updating both PC's to hrev51208, no mouse or keyboard on either PC

Syslog attached for fresh install of hrev51207 with update to hrev51208 Syslog attached for reboot of hrev51208

Attachments (3)

syslog_x86_64_hrev51207 (284.2 KB ) - added by vidrep 2 years ago.
syslog_x86_64_hrev51208 (108.5 KB ) - added by vidrep 2 years ago.
07_vs_08.diff (289.6 KB ) - added by waddlesplash 2 years ago.
diff -u of the two files

Download all attachments as: .zip

Change History (9)

by vidrep, 2 years ago

Attachment: syslog_x86_64_hrev51207 added

by vidrep, 2 years ago

Attachment: syslog_x86_64_hrev51208 added

by waddlesplash, 2 years ago

Attachment: 07_vs_08.diff added

diff -u of the two files

comment:1 by waddlesplash, 2 years ago

Attached a diff of the two files for quick comparison. It's not as clean as one might have hoped (mostly due to ASLR it appears?) but there are some pretty substantial differences in there.

comment:2 by vidrep, 2 years ago

Component: - GeneralBuild System
Owner: changed from nobody to bonefish
Platform: Allx86-64

comment:3 by vidrep, 2 years ago

This morning I downloaded the hrev51208 x86_64 anyboot image and installed it to my two PC's. These are working OK. So, it appears that it was only pkgman updates to hrev51208 that were affected.

comment:4 by bonefish, 2 years ago

Component: Build System- General
Owner: changed from bonefish to nobody

Please don't set the component to build system, unless it has something to do with the build system. It isn't a catch-all component.

comment:5 by vidrep, 2 years ago

This appears to have been resolved with latest anyboot image (hrev51227).

comment:6 by vidrep, 2 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.