Torstein and list; On Sat, Mar 9, 2013 at 12:00 AM, Torstein Hegge <hegge@xxxxxxxxxxx> wrote: > On Fri, Mar 08, 2013 at 08:23:54AM -0800, chris hermansen wrote: >> As to the outcome, I have two. (blush) (blush) (blush) What an idiot I am! A new kernel snuck into the updates while I wasn't paying attention and so I was testing that which I did not build. (blush) (blush) (blush) Anyway, I booted up the kernel I wished to test and now I get Torstein's messages. So, it seems this Saturday morning was the perfect morning to test things out. I plugged in the Schiit, then with 'sudo aplay -vD plughw:CARD=Interface,DEV=0' I played: 1. a 44.1/16 for ~ 10 seconds - it sounded fine - so I interrupted it 2. a 96/24 - it was staticky / noisy, even though the plughw slave reported it at 96000 - I interrupted it 3. the same 96/24 again - it was fine Here is the stream from /var/log/kern.log, as it all occurred clh@temuko:~/kernel$ tail -f /var/log/kern.log Mar 9 08:29:14 temuko kernel: [ 20.739688] type=1400 audit(1362846554.667:11): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" pid=872 comm="apparmor_parser" Mar 9 08:29:18 temuko kernel: [ 24.377410] wlan0: authenticate with 20:76:00:0d:dd:00 Mar 9 08:29:18 temuko kernel: [ 24.381740] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded Mar 9 08:29:18 temuko kernel: [ 24.381963] wlan0: send auth to 20:76:00:0d:dd:00 (try 1/3) Mar 9 08:29:18 temuko kernel: [ 24.383464] wlan0: authenticated Mar 9 08:29:18 temuko kernel: [ 24.383792] ath5k 0000:02:02.0 wlan0: disabling HT/VHT due to WEP/TKIP use Mar 9 08:29:18 temuko kernel: [ 24.384050] wlan0: associate with 20:76:00:0d:dd:00 (try 1/3) Mar 9 08:29:18 temuko kernel: [ 24.386214] wlan0: RX AssocResp from 20:76:00:0d:dd:00 (capab=0x411 status=0 aid=1) Mar 9 08:29:18 temuko kernel: [ 24.386545] wlan0: associated Mar 9 08:29:18 temuko kernel: [ 24.386606] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 9 08:33:05 temuko kernel: [ 250.380056] usb 1-3: new high-speed USB device number 2 using ehci-pci Mar 9 08:33:05 temuko kernel: [ 250.537896] usb 1-3: config 1 interface 8 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 Mar 9 08:33:05 temuko kernel: [ 250.537909] usb 1-3: config 1 interface 8 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64 Mar 9 08:33:05 temuko kernel: [ 250.540454] usb 1-3: New USB device found, idVendor=0d8c, idProduct=0304 Mar 9 08:33:05 temuko kernel: [ 250.540480] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Mar 9 08:33:05 temuko kernel: [ 250.540490] usb 1-3: Product: Schiit USB Interface Mar 9 08:33:05 temuko kernel: [ 250.540499] usb 1-3: Manufacturer: CMEDIA Mar 9 08:33:05 temuko kernel: [ 250.910794] 2:1: resetting device after change 48000 -> 192000 Mar 9 08:33:05 temuko kernel: [ 250.926921] 2:2: resetting device after change 48000 -> 192000 Mar 9 08:33:05 temuko kernel: [ 250.954813] 2:3: resetting device after change 48000 -> 192000 Mar 9 08:33:05 temuko kernel: [ 250.966681] 2:4: resetting device after change 48000 -> 192000 Mar 9 08:33:05 temuko kernel: [ 250.979809] current rate 48000 is different from the runtime rate 192000 Mar 9 08:33:05 temuko kernel: [ 250.979822] 2:5: resetting device after change -595519488 -> 48000 Mar 9 08:33:05 temuko kernel: [ 250.984816] 2:5:2: clock source 19 is not valid, cannot use Mar 9 08:33:05 temuko kernel: [ 250.985339] cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0x0, type = 4 Mar 9 08:33:05 temuko kernel: [ 250.995007] usbcore: registered new interface driver usbhid Mar 9 08:33:05 temuko kernel: [ 250.995022] usbhid: USB HID core driver Mar 9 08:33:05 temuko kernel: [ 251.012102] usbcore: registered new interface driver snd-usb-audio Mar 9 08:33:05 temuko kernel: [ 251.139444] input: CMEDIA Schiit USB Interface as /devices/pci0000:00/0000:00:13.2/usb1/1-3/1-3:1.6/input/input7 Mar 9 08:33:05 temuko kernel: [ 251.140092] hid-generic 0003:0D8C:0304.0001: input,hidraw0: USB HID v1.00 Device [CMEDIA Schiit USB Interface] on usb-0000:00:13.2-3/input6 Mar 9 08:33:05 temuko kernel: [ 251.252844] 2:4: resetting device after change 192000 -> 44100 Mar 9 08:33:05 temuko kernel: [ 251.276084] 2:1: resetting device after change 192000 -> 44100 Mar 9 08:34:55 temuko kernel: [ 361.220050] current rate 44100 is different from the runtime rate 96000 Mar 9 08:34:55 temuko kernel: [ 361.220066] 2:1: resetting device after change -467349503 -> 44100 Mar 9 08:35:18 temuko kernel: [ 384.140889] 2:1: resetting device after change 44100 -> 96000 ^C clh@temuko:~/kernel$ So that "resetting device after change -467349503 -> 44100" seems a bit odd. I've tried a few more times and this time annotated the output (like this) of the tail -f session as it happened: clh@temuko:~/kernel$ tail -f /var/log/kern.log Mar 9 08:33:05 temuko kernel: [ 250.995007] usbcore: registered new interface driver usbhid Mar 9 08:33:05 temuko kernel: [ 250.995022] usbhid: USB HID core driver Mar 9 08:33:05 temuko kernel: [ 251.012102] usbcore: registered new interface driver snd-usb-audio Mar 9 08:33:05 temuko kernel: [ 251.139444] input: CMEDIA Schiit USB Interface as /devices/pci0000:00/0000:00:13.2/usb1/1-3/1-3:1.6/input/input7 Mar 9 08:33:05 temuko kernel: [ 251.140092] hid-generic 0003:0D8C:0304.0001: input,hidraw0: USB HID v1.00 Device [CMEDIA Schiit USB Interface] on usb-0000:00:13.2-3/input6 Mar 9 08:33:05 temuko kernel: [ 251.252844] 2:4: resetting device after change 192000 -> 44100 Mar 9 08:33:05 temuko kernel: [ 251.276084] 2:1: resetting device after change 192000 -> 44100 Mar 9 08:34:55 temuko kernel: [ 361.220050] current rate 44100 is different from the runtime rate 96000 Mar 9 08:34:55 temuko kernel: [ 361.220066] 2:1: resetting device after change -467349503 -> 44100 Mar 9 08:35:18 temuko kernel: [ 384.140889] 2:1: resetting device after change 44100 -> 96000 (you can see the remnant of the last testing above; below we start this session) (playing 96/24) (sounds fine - interrupting 96/24) (playing 44.1/16) Mar 9 08:49:35 temuko kernel: [ 1241.305358] 2:1: resetting device after change 96000 -> 44100 (sounds fine - interrupting 44.1/16) (playing 96/24) Mar 9 08:50:32 temuko kernel: [ 1297.804486] 2:1:2: cannot get freq (v2) (ok that is weird, it did not play, and the following came out of the aplay:) Playing WAVE '2L50SACD_tr1_96k_stereo.wav' : Signed 24 bit Little Endian in 3bytes, Rate 96000 Hz, Stereo aplay: set_params:1145: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S24_3LE SUBFORMAT: STD SAMPLE_BITS: 24 FRAME_BITS: 48 CHANNELS: 2 RATE: 96000 PERIOD_TIME: 125000 PERIOD_SIZE: 12000 PERIOD_BYTES: 72000 PERIODS: 4 BUFFER_TIME: 500000 BUFFER_SIZE: 48000 BUFFER_BYTES: 288000 TICK_TIME: 0 (trying the 96/24 again) Mar 9 08:52:13 temuko kernel: [ 1399.137610] 2:1: resetting device after change 44100 -> 96000 (that worked fine, sounds fine, interrupting 96/24) (playing 96/24 again) (again fine, interrupting 96/24) (playing 44.1/16) Mar 9 08:53:34 temuko kernel: [ 1479.513636] 2:1: resetting device after change 96000 -> 44100 (that worked fine, sounds fine, interrupting 44.1/16) (trying 96/24 again) Mar 9 08:54:14 temuko kernel: [ 1519.619242] 2:1: resetting device after change 44100 -> 96000 (that worked fine, interrupting) ^C clh@temuko:~/kernel$ (blush) now that I've figured out the kernel thing, any more ideas to test (blush)? -- Chris Hermansen · clhermansen "at" gmail "dot" com C'est ma façon de parler. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
