Re: 4.20.1: BUG: unable to handle kernel paging request at 0000100000000008
Hi Pavel, On 3/7/19 12:10 AM, Pavel Machek wrote: On Tue 2019-01-22 11:15:39, Harald Dunkel wrote: Is this the wrong list to report this problem? I haven't found a "mem" mailing list on vger. Right list, ugly looking problem. How reproducible is it? By now this was just a single incident. The server runs 24/7, but I try to keep the kernel up-to-date, so it is rebootet frequently. You may want to look at MAINTAINERS file, cc x86 and memory management people...? I have created a bug report. https://bugzilla.kernel.org/show_bug.cgi?id=202257 Please ignore the hijacker. Regards Harri
Re: 4.20.1: BUG: unable to handle kernel paging request at 0000100000000008
Is this the wrong list to report this problem? I haven't found a "mem" mailing list on vger. Regards Harri - On 1/14/19 2:01 PM, Harald Dunkel wrote: Hi folks, my server stumbled over this last night: Jan 13 19:03:15 sylvester kernel: [272280.820190] BUG: unable to handle kernel paging request at 1008 Jan 13 19:03:15 sylvester kernel: [272280.820198] PGD 0 P4D 0 Jan 13 19:03:15 sylvester kernel: [272280.820203] Oops: [#1] PREEMPT SMP PTI Jan 13 19:03:15 sylvester kernel: [272280.820207] CPU: 3 PID: 46 Comm: kswapd0 Not tainted 4.20.1-raw #1 Jan 13 19:03:15 sylvester kernel: [272280.820211] Hardware name: /DH67CF, BIOS BLH6710H.86A.0125.2011.0705.1517 07/05/2011 Jan 13 19:03:15 sylvester kernel: [272280.820219] RIP: 0010:find_get_entries+0xed/0x240 Jan 13 19:03:15 sylvester kernel: [272280.820223] Code: 4e 4e 00 48 89 c2 48 85 d2 0f 84 91 00 00 00 48 81 fa 02 04 00 00 0f 84 a3 00 00 00 48 81 fa 06 04 00 00 74 ca f6 Jan 13 19:03:15 sylvester kernel: [272280.820230] RSP: 0018:c9fdb9c8 EFLAGS: 00010246 Jan 13 19:03:15 sylvester kernel: [272280.820234] RAX: 1000 RBX: 000f RCX: Jan 13 19:03:15 sylvester kernel: [272280.820238] RDX: 1000 RSI: 0680 RDI: ffc0 Jan 13 19:03:15 sylvester kernel: [272280.820242] RBP: 0002 R08: 8880a98b7d80 R09: Jan 13 19:03:15 sylvester kernel: [272280.820246] R10: 004b R11: c9fdb9c8 R12: Jan 13 19:03:15 sylvester kernel: [272280.820250] R13: c9fdbae0 R14: c9fdba60 R15: Jan 13 19:03:15 sylvester kernel: [272280.820255] FS: () GS:88821798() knlGS: Jan 13 19:03:15 sylvester kernel: [272280.820259] CS: 0010 DS: ES: CR0: 80050033 Jan 13 19:03:15 sylvester kernel: [272280.820263] CR2: 1008 CR3: 0200a003 CR4: 000606e0 Jan 13 19:03:15 sylvester kernel: [272280.820268] Call Trace: Jan 13 19:03:15 sylvester kernel: [272280.820276] pagevec_lookup_entries+0x15/0x20 Jan 13 19:03:15 sylvester kernel: [272280.820280] truncate_inode_pages_range+0xc5/0x810 Jan 13 19:03:15 sylvester kernel: [272280.820289] ? ___cache_free+0x2c/0x2f0 Jan 13 19:03:15 sylvester kernel: [272280.820296] ? jbd2_journal_release_jbd_inode+0x105/0x130 [jbd2] Jan 13 19:03:15 sylvester kernel: [272280.820301] ? iput+0x1e9/0x210 Jan 13 19:03:15 sylvester kernel: [272280.820305] ? __inode_wait_for_writeback+0x7a/0xe0 Jan 13 19:03:15 sylvester kernel: [272280.820319] ext4_evict_inode+0x52/0x5d0 [ext4] Jan 13 19:03:15 sylvester kernel: [272280.820325] evict+0xbf/0x190 Jan 13 19:03:15 sylvester kernel: [272280.820328] dispose_list+0x30/0x40 Jan 13 19:03:15 sylvester kernel: [272280.820332] prune_icache_sb+0x4d/0x70 Jan 13 19:03:15 sylvester kernel: [272280.820337] super_cache_scan+0x121/0x1a0 Jan 13 19:03:15 sylvester kernel: [272280.820342] do_shrink_slab+0x136/0x2d0 Jan 13 19:03:15 sylvester kernel: [272280.820346] shrink_slab+0x22a/0x290 Jan 13 19:03:15 sylvester kernel: [272280.820351] ? __mod_node_page_state+0x64/0xa0 Jan 13 19:03:15 sylvester kernel: [272280.820354] shrink_node+0xe1/0x450 Jan 13 19:03:15 sylvester kernel: [272280.820358] kswapd+0x3f9/0x740 Jan 13 19:03:15 sylvester kernel: [272280.820362] ? mem_cgroup_shrink_node+0x1b0/0x1b0 Jan 13 19:03:15 sylvester kernel: [272280.820367] kthread+0x111/0x130 Jan 13 19:03:15 sylvester kernel: [272280.820371] ? kthread_create_worker_on_cpu+0x60/0x60 Jan 13 19:03:15 sylvester kernel: [272280.820376] ret_from_fork+0x35/0x40 Jan 13 19:03:15 sylvester kernel: [272280.820380] Modules linked in: cpuid fuse btrfs xor zstd_compress raid6_pq zstd_decompress xxhash ufs hfsplus ntfs vfat msdos fat j Jan 13 19:03:15 sylvester kernel: [272280.820423] scsi_mod mfd_core usbcore e1000e Jan 13 19:03:15 sylvester kernel: [272280.820452] CR2: 1008 Jan 13 19:03:15 sylvester kernel: [272280.820456] ---[ end trace b383b200f5d976a9 ]--- Jan 13 19:03:15 sylvester kernel: [272280.820461] RIP: 0010:find_get_entries+0xed/0x240 Jan 13 19:03:15 sylvester kernel: [272280.820465] Code: 4e 4e 00 48 89 c2 48 85 d2 0f 84 91 00 00 00 48 81 fa 02 04 00 00 0f 84 a3 00 00 00 48 81 fa 06 04 00 00 74 ca f6 Jan 13 19:03:15 sylvester kernel: [272280.820472] RSP: 0018:c9fdb9c8 EFLAGS: 00010246 I have opened https://bugzilla.kernel.org/show_bug.cgi?id=202257, providing kernel.log and config file. Is there anything else I could do to help tracking down this problem? Regards Harri
4.20.1: BUG: unable to handle kernel paging request at 0000100000000008
Hi folks, my server stumbled over this last night: Jan 13 19:03:15 sylvester kernel: [272280.820190] BUG: unable to handle kernel paging request at 1008 Jan 13 19:03:15 sylvester kernel: [272280.820198] PGD 0 P4D 0 Jan 13 19:03:15 sylvester kernel: [272280.820203] Oops: [#1] PREEMPT SMP PTI Jan 13 19:03:15 sylvester kernel: [272280.820207] CPU: 3 PID: 46 Comm: kswapd0 Not tainted 4.20.1-raw #1 Jan 13 19:03:15 sylvester kernel: [272280.820211] Hardware name: /DH67CF, BIOS BLH6710H.86A.0125.2011.0705.1517 07/05/2011 Jan 13 19:03:15 sylvester kernel: [272280.820219] RIP: 0010:find_get_entries+0xed/0x240 Jan 13 19:03:15 sylvester kernel: [272280.820223] Code: 4e 4e 00 48 89 c2 48 85 d2 0f 84 91 00 00 00 48 81 fa 02 04 00 00 0f 84 a3 00 00 00 48 81 fa 06 04 00 00 74 ca f6 Jan 13 19:03:15 sylvester kernel: [272280.820230] RSP: 0018:c9fdb9c8 EFLAGS: 00010246 Jan 13 19:03:15 sylvester kernel: [272280.820234] RAX: 1000 RBX: 000f RCX: Jan 13 19:03:15 sylvester kernel: [272280.820238] RDX: 1000 RSI: 0680 RDI: ffc0 Jan 13 19:03:15 sylvester kernel: [272280.820242] RBP: 0002 R08: 8880a98b7d80 R09: Jan 13 19:03:15 sylvester kernel: [272280.820246] R10: 004b R11: c9fdb9c8 R12: Jan 13 19:03:15 sylvester kernel: [272280.820250] R13: c9fdbae0 R14: c9fdba60 R15: Jan 13 19:03:15 sylvester kernel: [272280.820255] FS: () GS:88821798() knlGS: Jan 13 19:03:15 sylvester kernel: [272280.820259] CS: 0010 DS: ES: CR0: 80050033 Jan 13 19:03:15 sylvester kernel: [272280.820263] CR2: 1008 CR3: 0200a003 CR4: 000606e0 Jan 13 19:03:15 sylvester kernel: [272280.820268] Call Trace: Jan 13 19:03:15 sylvester kernel: [272280.820276] pagevec_lookup_entries+0x15/0x20 Jan 13 19:03:15 sylvester kernel: [272280.820280] truncate_inode_pages_range+0xc5/0x810 Jan 13 19:03:15 sylvester kernel: [272280.820289] ? ___cache_free+0x2c/0x2f0 Jan 13 19:03:15 sylvester kernel: [272280.820296] ? jbd2_journal_release_jbd_inode+0x105/0x130 [jbd2] Jan 13 19:03:15 sylvester kernel: [272280.820301] ? iput+0x1e9/0x210 Jan 13 19:03:15 sylvester kernel: [272280.820305] ? __inode_wait_for_writeback+0x7a/0xe0 Jan 13 19:03:15 sylvester kernel: [272280.820319] ext4_evict_inode+0x52/0x5d0 [ext4] Jan 13 19:03:15 sylvester kernel: [272280.820325] evict+0xbf/0x190 Jan 13 19:03:15 sylvester kernel: [272280.820328] dispose_list+0x30/0x40 Jan 13 19:03:15 sylvester kernel: [272280.820332] prune_icache_sb+0x4d/0x70 Jan 13 19:03:15 sylvester kernel: [272280.820337] super_cache_scan+0x121/0x1a0 Jan 13 19:03:15 sylvester kernel: [272280.820342] do_shrink_slab+0x136/0x2d0 Jan 13 19:03:15 sylvester kernel: [272280.820346] shrink_slab+0x22a/0x290 Jan 13 19:03:15 sylvester kernel: [272280.820351] ? __mod_node_page_state+0x64/0xa0 Jan 13 19:03:15 sylvester kernel: [272280.820354] shrink_node+0xe1/0x450 Jan 13 19:03:15 sylvester kernel: [272280.820358] kswapd+0x3f9/0x740 Jan 13 19:03:15 sylvester kernel: [272280.820362] ? mem_cgroup_shrink_node+0x1b0/0x1b0 Jan 13 19:03:15 sylvester kernel: [272280.820367] kthread+0x111/0x130 Jan 13 19:03:15 sylvester kernel: [272280.820371] ? kthread_create_worker_on_cpu+0x60/0x60 Jan 13 19:03:15 sylvester kernel: [272280.820376] ret_from_fork+0x35/0x40 Jan 13 19:03:15 sylvester kernel: [272280.820380] Modules linked in: cpuid fuse btrfs xor zstd_compress raid6_pq zstd_decompress xxhash ufs hfsplus ntfs vfat msdos fat j Jan 13 19:03:15 sylvester kernel: [272280.820423] scsi_mod mfd_core usbcore e1000e Jan 13 19:03:15 sylvester kernel: [272280.820452] CR2: 1008 Jan 13 19:03:15 sylvester kernel: [272280.820456] ---[ end trace b383b200f5d976a9 ]--- Jan 13 19:03:15 sylvester kernel: [272280.820461] RIP: 0010:find_get_entries+0xed/0x240 Jan 13 19:03:15 sylvester kernel: [272280.820465] Code: 4e 4e 00 48 89 c2 48 85 d2 0f 84 91 00 00 00 48 81 fa 02 04 00 00 0f 84 a3 00 00 00 48 81 fa 06 04 00 00 74 ca f6 Jan 13 19:03:15 sylvester kernel: [272280.820472] RSP: 0018:c9fdb9c8 EFLAGS: 00010246 I have opened https://bugzilla.kernel.org/show_bug.cgi?id=202257, providing kernel.log and config file. Is there anything else I could do to help tracking down this problem? Regards Harri
Re: 4.6.4, 3w_sas: timeout too small?
Hi Adam, thanx very much for your detailed analysis. Regards Harri
4.6.4, 3w_sas: timeout too small?
Hi folks, Question about the reset timeout of the 3w_sas: For an unknown reason my 3ware 9750 RAID controller became unresponsive. kernel.log: Oct 16 06:30:42 nasl003b kernel: [4902556.775272] 3w-sas: scsi0: AEN: INFO (0x04:0x002B): Verify completed:unit=1. Oct 16 06:38:29 nasl003b kernel: [4903023.388357] 3w-sas: scsi0: AEN: INFO (0x04:0x002B): Verify completed:unit=2. Oct 16 06:41:33 nasl003b kernel: [4903207.577484] 3w-sas: scsi0: ERROR: (0x06:0x000D): Microcontroller Error: clearing. Oct 16 06:42:11 nasl003b kernel: [4903245.701070] TMR Opcode TARGET_WARM_RESET authorization failed for Initiator Node: iqn.2014-01.com.example.ac.srva001 Oct 16 06:42:11 nasl003b kernel: [4903245.706778] TMR Opcode TARGET_WARM_RESET authorization failed for Initiator Node: iqn.2014-01.com.example.ac.srva001 Oct 16 06:42:15 nasl003b kernel: [4903249.298778] TMR Opcode TARGET_WARM_RESET authorization failed for Initiator Node: iqn.2014-01.com.example.ac.srva002 Oct 16 06:42:15 nasl003b kernel: [4903249.304369] TMR Opcode TARGET_WARM_RESET authorization failed for Initiator Node: iqn.2014-01.com.example.ac.srva002 Oct 16 06:42:15 nasl003b kernel: [4903249.318734] TMR Opcode TARGET_WARM_RESET authorization failed for Initiator Node: iqn.2014-01.com.example.ac.srva003 Oct 16 06:42:15 nasl003b kernel: [4903249.324122] TMR Opcode TARGET_WARM_RESET authorization failed for Initiator Node: iqn.2014-01.com.example.ac.srva003 Oct 16 06:42:41 nasl003b kernel: [4903275.739327] 3w-sas: scsi0: WARNING: (0x06:0x0006): Character ioctl (0x108) timed out, resetting card. Oct 16 06:42:41 nasl003b kernel: [4903275.739402] sd 0:0:0:0: WARNING: (0x06:0x002C): Command (0x2a) timed out, resetting card. Oct 16 06:43:36 nasl003b kernel: [4903330.757153] iSCSI Login timeout on Network Portal 172.19.96.217:3260 Oct 16 06:43:36 nasl003b kernel: [4903330.762124] iSCSI Login negotiation failed. Oct 16 06:43:42 nasl003b kernel: [4903336.720892] 3w-sas: scsi0: ERROR: (0x06:0x0011): Controller not ready during reset sequence. Oct 16 06:43:51 nasl003b kernel: [4903345.796529] iSCSI Login timeout on Network Portal 172.19.96.217:3260 Oct 16 06:43:51 nasl003b kernel: [4903345.801462] iSCSI Login negotiation failed. Oct 16 06:44:06 nasl003b kernel: [4903360.835920] iSCSI Login timeout on Network Portal 172.19.96.217:3260 Oct 16 06:44:06 nasl003b kernel: [4903360.840843] iSCSI Login negotiation failed. Oct 16 06:44:13 nasl003b kernel: [4903367.919662] INFO: task jbd2/sda1-8:235 blocked for more than 120 seconds. Oct 16 06:44:13 nasl003b kernel: [4903367.924633] Tainted: GE 4.6.0-0.bpo.1-amd64 #1 Oct 16 06:44:13 nasl003b kernel: [4903367.929624] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 16 06:44:13 nasl003b kernel: [4903367.934751] jbd2/sda1-8 D 88042d896000 0 235 2 0x Oct 16 06:44:13 nasl003b kernel: [4903367.934756] 880424c2c440 88042b43a140 8804249e 8804249dfbc0 Oct 16 06:44:13 nasl003b kernel: [4903367.934760] 7fff 815c50a0 8804249dfc40 8804000daf00 Oct 16 06:44:13 nasl003b kernel: [4903367.934763] 815c4821 815c785f 7fff Oct 16 06:44:13 nasl003b kernel: [4903367.934766] Call Trace: Oct 16 06:44:13 nasl003b kernel: [4903367.934783] [] ? bit_wait_timeout+0xa0/0xa0 Oct 16 06:44:13 nasl003b kernel: [4903367.934786] [] ? schedule+0x31/0x80 Oct 16 06:44:13 nasl003b kernel: [4903367.934789] [] ? schedule_timeout+0x22f/0x2c0 Oct 16 06:44:13 nasl003b kernel: [4903367.934794] [] ? blk_peek_request+0x4d/0x280 Oct 16 06:44:13 nasl003b kernel: [4903367.934797] [] ? bit_wait_timeout+0xa0/0xa0 : : The interesting point is that apparently the reset didn't succeed. "Controller not ready during reset sequence" at 06:43:42. The 3ware web interface says the controller was busy to write the cache to disk: Oct 16, 2016 06:45:03AM (0x04:0x005E): Cache synchronization completed: unit=0 I have the impression that the timeout (60 secs?) in the driver is insufficient. Do you think the status check in twl_reset_sequence() could be improved? There were no disk failures, of course. Every helpful comment is highly appreciated. Harri
bcache vs bcachefs
Hi folks, I am pretty hesitant replacing the rock-solid ext4 by bcachefs on my servers. Meaning no offense, but surely I would prefer to have ext4 with a thin "SSD caching layer" over a completely different filesystem, potentially with alot of teething troubles. Question: Is bcache EOL or can I rely on it for the next 5 to 10 years? Regards Harri
non-rotational USB stick?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi folks, Is there some way to make the kernel automatically recognize a USB stick as a non-rotational device? (My hope is that the CFQ IOPS mode patch might improve performance of a USB stick as well :-) Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVdRWGAAoJEAqeKp5m04HLxLYH/AuECvumy3UkdNwRA7yOUHKo 3GyRC95iv+AzIVk2Iceqgcza6RV3uYnS22SDpWIz0/Y+ArdqzrMpWCdvnExLAQBR PZg+wmDSpE7DFamAakGM6g0ca5LPXMqklLJx7TMMPQ3rIBqRdqOHJiLA6r+Qw8iI ZqTfWDQILmv4j2O9FAzvV6ksoYAxUBSGivtaXirkWFPaCTH1hyUbFh3cPJl5x7r/ yfg04k68bevPVdYc/2ItplDpA0xVoYTg1gejKNla0v7cV8jL7RC7pZoWtyXFUjFi X3+MOtCXDFJ8701Vt/J++t4t4jEsgXQZ2vemXw51RMwzFnMD12HeqP7itnkQzqg= =ZPwG -END PGP SIGNATURE- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
strange kernel log messages
Hi folks, I get a lot of strange messages in /var/log/kern.log: : Dec 26 08:01:58 dpcl082 kernel: <>[1862186]xc_c 000:00 RO oro ne ig<>1862143]hb5110 ciae->-23862114]xc_c 000:00 RO oro ne ig<>1862186]hb5110 ciae->-231862075]xc_c 000:00 RO oro ne ig<>1862140]hb5110 ciae->-2<>[1872078]xc_c 000:00 RO oro ne ig<>1872074]xc_c 000:00 RO oro ne ig<>1872031]hb5110 ciae->-2<>1872064]xc_c 000:00 RO oro ne ig<>1872039]hb5110 ciae->-2<>1881965]xc_c 000:00 RO oro ne ig<>1882033]hb5110 ciae->-23[794.753 hihd00:60.:ERRn omo prn Dec 26 08:03:58 dpcl082 kernel: <>1881961]xc_c 000:00 RO oro ne ig<3>[1789871.993215]hb5110 ciae->-2<>1891961]xc_c 000:00 RO oro ne ig<>1891927]hb5110 ciae->-2<>1891957]xc_c 000:00 RO oro ne ig<>1891929]hb5110 ciae->-2<>[1796.954 hihd00:60.:ERRn omo prn Dec 26 08:03:58 dpcl082 kernel: 3[796.330 u -:.:atvt - 1 Dec 26 08:04:28 dpcl082 kernel: <>[799.730 hihd00:60.:ERRn omo prn Dec 26 08:04:28 dpcl082 kernel: 3[799.116 u -:.:atvt - 1 Dec 26 08:05:58 dpcl082 kernel: <>1901890]xc_c 000:00 RO oro ne ig<>1901862]hb5110 ciae->-2<>1901847]xc_c 000:00 RO oro ne ig<>1901810]hb5110 ciae->-23[708.173 hihd00:60.:ERRn omo prn Dec 26 08:05:58 dpcl082 kernel: 3[708.553 u -:.:atvt - 1 Dec 26 08:06:58 dpcl082 kernel: <>1911747]xc_c 000:00 RO oro ne ig<>1911817]hb5110 ciae->-2<3>[1790141.774230] xhci_hcd :06:00.0: ERROR no room on ep ring Dec 26 08:07:58 dpcl082 kernel: 3[700.770 u -:.:atvt - 1 Dec 26 08:11:28 dpcl082 kernel: 3[701.224 u -:.:atvt - 1 : What is it trying to tell me? Sorry for asking, but Google did not help. Kernel is 3.2.0-0.bpo.4-amd64 from Squeeze backports. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
strange behavior on multimedia eject button for cdrom
Hi folks, My laptop (Dell XPS M1330) has some multimedia keys added to the keyboard, including an eject button for the cdrom drive, instead of a "regular" eject button built into the drive itself. When I press it to eject a CD, then Linux becomes pretty mad: The audio device gets stuck somehow, playing the same tune over and over again, the network connection is frozen, etc. Once the CD is out it is back to normal, as it seems. I would guess that the eject button triggers some bios functionality, outside of the control of the kernel. But is it? How comes that Linux seems to loose control in this case? Kernel is 2.6.24.2 (amd64). AFAICS this eject button has no keycode. The other multimedia keys have. Any helpful idea would be very welcome. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc8: iwl3945 gets stuck
Jeff suggested to post this on [EMAIL PROTECTED] I hope this is OK? Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.24-rc8: iwl3945 gets stuck
Hi folks, If I put some heavy load on the iwl3945, then the network connection gets stuck after a some time. To fix it I have to reload the module. AFAICS this problem was a topic on lkml almost 3 months ago. Any news about this? I would be glad to help to track this down, but I have no idea how to change the scaling algorithm to iwl-3945-rs . Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Takashi Iwai wrote: Linus, please revert the commit 57a04513cb3 as now. The life can go well without this patch. hda_intel.c works for me in rc8. Many thanx to all Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Dear Takashi-san, Takashi Iwai wrote: The "regression" was your original problem, no sound on rc7, which was fixed by reverting the patch. Now I'd like to know that my new patch doesn't break after reverting the broken patch. Seems that there was some misunderstanding: I thought your patch for sigmatel.c was supposed to fix the "missing sound" problem, too. In short, try my patch on the latest Linus git tree. Check whether the sound still works. It does. rc7 plus the big "clean-up" patch for sigmatel.c plus hda_intel.c taken from rc6 worked, too. Seems that I missed to mention it in a previous EMail. It's simply a delay. Basically Ingo's patch changed msleep() to udelay() to reduce *unneeded* delays. The function waits until the all pending commands are processed. The delay is simply to reduce the system load. And, now, changing this delay causes a problem surprisingly. I am glad to help, but could you please do me a favour? If I am supposed to try some new version, then please create a complete(!) patch using rc7 on kernel.org as the base, and send it as an attachment using a unique filename. Very likely you have a much better overview about the most recent kernel changes, but some statements like "new patch" or "Ingo's patch" don't mean very much to me. The "reverted" patch is a new patch, too, and AFAIK Ingo reverted it, so maybe you can imagine that this is highly confusing. >> AFAICS I did use the mm branch. The command to grab the sources was >> >> git-clone git://git.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git mm >> >> Is this correct? > > No. You'd better to clone Linus git tree, then pull from alsa.git mm > branch. > > % git-clone $LINUS/linux-2.6.git > % cd linux-2.6 > % git-pull $ALSA/alsa.git mm > AFAICS there shouldn't be a difference to my one-liner, unless Linus' and Alsa's git trees are out of sync. Is this correct? Sorry, I am more familiar with ClearCase and Accurev than with Git. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Takashi Iwai wrote: At Thu, 10 Jan 2008 23:02:53 +0100, Harald Dunkel wrote: Takashi Iwai wrote: Hm... Just to be sure, try the patch below. It's a clean up patch that I'd like to apply later. Sorry, no sound. OK, but I'd like to know whether this makes no regression to rc6. Could you check? Also, what exactly did you test? "No sound" means that no sound from the headphone / line-out or from the speaker? One interesting test would be to increase the value of udelay() in the reverted patch. What happens if it's set to 500? There is no udelay() in the reverted patch. If I replace "udelay(10)" by "udelay(500)" in the original rc7, then there is still no sound. This is like fishing in the dark. We've got a working version. Why not keep it? Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Takashi Iwai wrote: At Thu, 10 Jan 2008 23:02:53 +0100, Harald Dunkel wrote: Takashi Iwai wrote: Hm... Just to be sure, try the patch below. It's a clean up patch that I'd like to apply later. Sorry, no sound. OK, but I'd like to know whether this makes no regression to rc6. Could you check? "Regression" sounds like a test suite to me, verifying that the old problems didn't come back. Maybe you could send me a pointer? Of course I didn't try that much yet. The kernel booted as expected, I saw XWindow running, the mouse pointer was moving, etc. There was just no sound, as before with rc7. Also, what exactly did you test? "No sound" means that no sound from the headphone / line-out or from the speaker? Speaker and first headphone are the same on this laptop. If I plugin the headphone, then the tiny speakers are disconnected. But for the last tests no headphone was plugged in. I tested it by running gnome-alsamixer. I tried to switch off and on the mute buttons, change the volume and other sliders, etc. One interesting test would be to increase the value of udelay() in the reverted patch. What happens if it's set to 500? I will try tomorrow. What exactly is this delay good for? The perex/alsa.git mm branch on kernel.org has many fixes. Could you give it a try, too? This version seems to work. But AFAICS it just reverts hda_intel.c back to rc6 again, so this is no surprise. Use mm branch. The main branch is just an old Linus tree. AFAICS I did use the mm branch. The command to grab the sources was git-clone git://git.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git mm Is this correct? Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Takashi Iwai wrote: Hm... Just to be sure, try the patch below. It's a clean up patch that I'd like to apply later. Sorry, no sound. The perex/alsa.git mm branch on kernel.org has many fixes. Could you give it a try, too? This version seems to work. But AFAICS it just reverts hda_intel.c back to rc6 again, so this is no surprise. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Takashi Iwai wrote: Thanks. Then the possible reason might be the registers that don't appear in this proc output, such as GPIO. Could you try the patch below with the latency patch (you reverted) in rc7? Using rc7: hda_intel.c(rc6) + patch for sigmatel.c: sound works hda_intel.c(rc7) + patch for sigmatel.c: sound does not work Sorry to say, but AFAICS the patch for sigmatel.c doesn't fix the problem. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Takashi Iwai wrote: Did you enable CONFIG_SND_HDA_POWER_SAVE feature? And which hardware (laptop, product name, whatever) exactly? CONFIG_SND_HDA_POWER_SAVE is not set. Hardware is a Dell XPS M1330. CPU is Core2 Duo T7500, 2.20GHz, 2 GByte RAM. lspci: 00:00.0 Host bridge: Intel Corporation Mobile Memory Controller Hub (rev 0c) 00:01.0 PCI bridge: Intel Corporation Mobile PCI Express Root Port (rev 0c) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 02) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02) 00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2) 00:1f.0 ISA bridge: Intel Corporation Mobile LPC Interface Controller (rev 02) 00:1f.1 IDE interface: Intel Corporation Mobile IDE Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0427 (rev a1) 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 (rev 05) 03:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 03:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 03:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) 09:00.0 Ethernet controller: Broadcom Corporation Unknown device 1713 (rev 02) 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) Also, please show the contents of /proc/asound/card0/codec#* files. Do you see difference in these files between with and without the patch? See below. There is no difference between both. Regards Harri Codec: SigmaTel STAC9228 Address: 0 Vendor Id: 0x83847616 Subsystem Id: 0x10280209 Revision Id: 0x100201 No Modem Function Group found Default PCM: rates [0x7e0]: 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: ofs=0x00, nsteps=0x0e, stepsize=0x05, mute=0 Default Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x02, mute=1 Node 0x02 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out Amp-Out caps: N/A Amp-Out vals: [0x7f 0x7f] Power: 0x0 Node 0x03 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Power: 0x0 Node 0x04 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Power: 0x0 Node 0x05 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Power: 0x0 Node 0x06 [Vendor Defined Widget] wcaps 0xfd0c05: Stereo Amp-Out Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Power: 0x0 Node 0x07 [Audio Input] wcaps 0x1d0541: Stereo Power: 0x0 Connection: 1 0x1b Node 0x08 [Audio Input] wcaps 0x1d0541: Stereo Power: 0x0 Connection: 1 0x1c Node 0x09 [Audio Input] wcaps 0x1d0541: Stereo Power: 0x0 Connection: 1 0x1d Node 0x0a [Pin Complex] wcaps 0x400181: Stereo Pincap 0x08173f: IN OUT HP Detect Pin Default 0x02214020: [Jack] HP Out at Ext Front Conn = 1/8, Color = Green Pin-ctls: 0xc0: OUT HP Connection: 2 0x02* 0x03 Node 0x0b [Pin Complex] wcaps 0x400181: Stereo Pincap 0x08173f: IN OUT HP Detect Pin Default 0x02a19080: [Jack] Mic at Ext Front Conn = 1/8, Color = Pink Pin-ctls: 0x24: IN Connection: 2 0x02 0x03* Node 0x0c [Pin Complex] wcaps 0x400181: Stereo Pincap 0x081737: IN OUT Detect Pin Default 0x0181304e: [Jack] Line In at Ext Rear Conn = 1/8, Color = Blue Pin-ctls: 0x20: IN Connection: 1 0x03 Node 0x0d [Pin Complex] wcaps 0x400181: Stereo Pincap 0x08173f: IN OUT HP Detect Pin Default 0x01014010: [Jack] Line Out at Ext Rear Conn = 1/8, Color = Green Pin-ctls: 0x40: OUT Connection: 1 0x02 Node 0x0e [Pin Complex] wcaps 0x400181: Stereo Pincap 0x081737: IN OUT Detect Pin Default 0x01a19040: [Jack] Mic at Ext Rear Conn = 1/8, Color = Pink Pin-ctls: 0x24: IN
Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Dear Takashi-san, Takashi Iwai wrote: Could you revert it and check whether the problem still exists? I did, and sound is back :-). Please mail, if you need the .config file. BTW, I missed to send the output of uname. Here is: Linux daffy 2.6.24-rc7 #1 SMP Tue Jan 8 07:17:39 CET 2008 x86_64 GNU/Linux Its 64bit. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.24-rc7, intel audio: alsa doesn't say a beep
Hi folks,
Upgrading from 2.6.24-rc6 to rc7 Alsa stopped working for me. I still
can access /dev/dsp, change the volume and so on, but the speakers
are quiet. Moving back to rc6 there is no such problem.
Of course the config files are the same (except for some new
CONFIG_SLABINFO variable).
lspci says:
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
00:1b.0 0403: 8086:284b (rev 02)
% aplay -l
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
The only difference between rc6 and rc7 in sound/pci/hda/hda_intel.c is
this:
diff -ur linux-2.6.24-rc6/sound/pci/hda/hda_intel.c
linux-2.6.24-rc7/sound/pci/hda/hda_intel.c
--- linux-2.6.24-rc6/sound/pci/hda/hda_intel.c 2007-12-21 02:25:48.0
+0100
+++ linux-2.6.24-rc7/sound/pci/hda/hda_intel.c 2008-01-06 22:45:38.0
+0100
@@ -555,7 +555,8 @@
}
if (!chip->rirb.cmds)
return chip->rirb.res; /* the last value */
- schedule_timeout_uninterruptible(1);
+ udelay(10);
+ cond_resched();
} while (time_after_eq(timeout, jiffies));
if (chip->msi) {
Do you think this could be related to the problem?
Any hint would be highly appreciated. Please mail if I can help to
track this down.
Regards
Harri
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
2.6.24-rc6: ricoh_mmc woes
Hi folks, I've got a problem with a Ricoh mmc reader. As soon as I insert a sd card I get tons of I/O errors. syslog says: Jan 5 21:19:12 daffy kernel: ricoh-mmc: Ricoh MMC Controller disabling driver Jan 5 21:19:12 daffy kernel: ricoh-mmc: Copyright(c) Philip Langdale Jan 5 21:19:12 daffy kernel: ricoh-mmc: Ricoh MMC controller found at :03:01.2 [1180:0843] (rev 12) Jan 5 21:19:12 daffy kernel: ricoh-mmc: Controller is now disabled. Jan 5 21:19:25 daffy kernel: mmc0: new high speed SD card at address 1234 Jan 5 21:19:25 daffy kernel: mmcblk0: mmc0:1234 SD01G 995328KiB Jan 5 21:19:25 daffy kernel: mmcblk0:<3>mmcblk0: error -84 transferring data Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0 Jan 5 21:19:25 daffy kernel: printk: 32 messages suppressed. Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0 Jan 5 21:19:25 daffy kernel: mmcblk0: error -84 transferring data Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0 Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0 Jan 5 21:19:25 daffy kernel: mmcblk0: error -84 transferring data Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0 Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0 Jan 5 21:19:25 daffy kernel: mmcblk0: error -84 transferring data Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0 Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0 Jan 5 21:19:26 daffy kernel: mmcblk0: error -84 transferring data Jan 5 21:19:26 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0 Jan 5 21:19:26 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0 Jan 5 21:19:26 daffy kernel: ldm_validate_partition_table(): Disk read failed. Jan 5 21:19:26 daffy kernel: mmcblk0: error -84 transferring data Jan 5 21:19:26 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0 : : The ricoh_mmc disabler module is installed as a module. udev loads it at boot time. But AFAICS I get the same errors if ricoh_mmc is removed. lspci says # lspci | grep -i ricoh 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 (rev 05) 03:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 03:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 12) 03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) # lspci -n | grep 03:01 03:01.0 0c00: 1180:0832 (rev 05) 03:01.1 0805: 1180:0822 (rev 22) 03:01.2 0880: 1180:0843 (rev 12) 03:01.3 0880: 1180:0592 (rev 12) 03:01.4 0880: 1180:0852 (rev ff) Of course the SD card works fine in another PC. Any idea how to track this down? Please mail Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.24-r6: README.iwlwifi lost?
Hi folks, The help for iwl3945 suggests to read some Documentation/networking/\ README.iwlwifi, but obviously this file is not there. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
howto get a melodic system beep?
Hi folks, Is there a way to replace the system beep by something more melodic? I remember some 10 years ago there was a patch for the kernel to call an external "beep daemon" playing an audio file instead (no kidding). But it never worked very well. Sometimes there was a huge delay, and some programs were not very nice to the system beep. My X-mas wish would be to get an improvement here. Regards Harri -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23.8, ondemand scaling governor: "BUG: soft lockup detected on CPU#0!"
Pallipadi, Venkatesh wrote: This looks like TSC related issue. Ingo's patch commit id a3b13c23f186ecb57204580cc1f2dbe9c284953a http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.g it;a=commit;h=a3b13c23f186ecb57204580cc1f2dbe9c284953a should help. Yes, after applying this patch the problem seems to be gone. Many thanx Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23.8, ondemand scaling governor: "BUG: soft lockup detected on CPU#0!"
Pallipadi, Venkatesh wrote: Can you try switching to powersave governor (which should always run CPU at 400MHz) and see whether you see similar error? Yes, if I move from performance to powersave, then I see a similar error: Nov 20 09:06:48 bugs kernel: BUG: soft lockup detected on CPU#0! Nov 20 09:06:48 bugs kernel: [] softlockup_tick+0x91/0xa6 Nov 20 09:06:48 bugs kernel: [] update_process_times+0x3a/0x5d Nov 20 09:06:48 bugs kernel: [] tick_sched_timer+0x115/0x164 Nov 20 09:06:48 bugs kernel: [] hrtimer_interrupt+0x102/0x191 Nov 20 09:06:48 bugs kernel: [] timer_interrupt+0x2e/0x34 Nov 20 09:06:48 bugs kernel: [] handle_IRQ_event+0x1a/0x3f Nov 20 09:06:48 bugs kernel: [] handle_level_irq+0xa8/0xb7 Nov 20 09:06:48 bugs kernel: [] do_IRQ+0x53/0x6c Nov 20 09:06:48 bugs kernel: [] common_interrupt+0x23/0x28 Nov 20 09:06:48 bugs kernel: === Please mail. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.23.8, ondemand scaling governor: "BUG: soft lockup detected on CPU#0!"
Hi folks, using the ondemand scaling governour I see some error messages in kern.log, e.g.: Nov 20 01:00:46 bugs kernel: BUG: soft lockup detected on CPU#0! Nov 20 01:00:46 bugs kernel: [] softlockup_tick+0x91/0xa6 Nov 20 01:00:46 bugs kernel: [] update_process_times+0x3a/0x5d Nov 20 01:00:46 bugs kernel: [] tick_sched_timer+0x115/0x164 Nov 20 01:00:46 bugs kernel: [] hrtimer_interrupt+0x102/0x191 Nov 20 01:00:46 bugs kernel: [] timer_interrupt+0x2e/0x34 Nov 20 01:00:46 bugs kernel: [] handle_IRQ_event+0x1a/0x3f Nov 20 01:00:46 bugs kernel: [] handle_level_irq+0xa8/0xb7 Nov 20 01:00:46 bugs kernel: [] do_IRQ+0x53/0x6c Nov 20 01:00:46 bugs kernel: [] common_interrupt+0x23/0x28 Nov 20 01:00:46 bugs kernel: [] smp_apic_timer_interrupt+0x1a/0x70 Nov 20 01:00:46 bugs kernel: [] default_idle+0x27/0x39 Nov 20 01:00:46 bugs kernel: [] cpu_idle+0x46/0x68 Nov 20 01:00:46 bugs kernel: [] start_kernel+0x24d/0x252 Nov 20 01:00:46 bugs kernel: [] unknown_bootoption+0x0/0x196 Nov 20 01:00:46 bugs kernel: === This seems to happen when the load drops below the threshold and the ondemand governor changes the CPU from 2GHz to 400MHz. If I use the "performance" governor instead, then there is no such message. If I set it back to "ondemand", then the message is printed immediately. # uname -a Linux bugs 2.6.23.8 #1 PREEMPT Sun Nov 18 09:14:13 CET 2007 i686 GNU/Linux # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Pentium(R) M processor 2.00GHz stepping: 8 cpu MHz : 400.000 cache size : 2048 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx bts est tm2 bogomips: 798.34 clflush size: 64 Please mail if I can help to track this down. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.24-rc1: usb problem?
Hi folks, I found this call trace in /var/kern.log: : : Oct 30 14:59:36 pluto kernel: usb 1-2: config 1 descriptor has 1 excess byte, ignoring Oct 30 14:59:36 pluto kernel: usb 1-2: configuration #1 chosen from 1 choice Oct 30 14:59:36 pluto kernel: usb 1-3: new high speed USB device using ehci_hcd and address 4 Oct 30 14:59:36 pluto kernel: usb 1-3: configuration #1 chosen from 1 choice Oct 30 14:59:36 pluto kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 30 14:59:36 pluto kernel: ata3.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7 Oct 30 14:59:36 pluto kernel: ata3.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32) Oct 30 14:59:36 pluto kernel: ata3.00: configured for UDMA/100 Oct 30 14:59:36 pluto kernel: usb 1-5: new high speed USB device using ehci_hcd and address 5 Oct 30 14:59:36 pluto kernel: usb 1-5: configuration #1 chosen from 1 choice Oct 30 14:59:36 pluto kernel: usb 1-1.1: new high speed USB device using ehci_hcd and address 6 Oct 30 14:59:36 pluto kernel: usb 1-1.1: configuration #1 chosen from 1 choice Oct 30 14:59:36 pluto kernel: hub 1-1.1:1.0: USB hub found Oct 30 14:59:36 pluto kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 30 14:59:36 pluto kernel: hub 1-1.1:1.0: 4 ports detected Oct 30 14:59:36 pluto kernel: sysfs: duplicate filename 'bInterfaceNumber' can not be created Oct 30 14:59:36 pluto kernel: WARNING: at fs/sysfs/dir.c:424 sysfs_add_one() Oct 30 14:59:36 pluto kernel: Oct 30 14:59:36 pluto kernel: Call Trace: Oct 30 14:59:36 pluto kernel: [] sysfs_add_one+0xae/0xe0 Oct 30 14:59:36 pluto kernel: [] sysfs_add_file+0x5f/0xb0 Oct 30 14:59:36 pluto kernel: [] sysfs_create_group+0x6c/0x120 Oct 30 14:59:36 pluto kernel: [] :usbcore:usb_create_sysfs_intf_files+0x46/0x100 Oct 30 14:59:36 pluto kernel: [] :usbcore:usb_set_configuration+0x336/0x5f0 Oct 30 14:59:36 pluto kernel: [] :usbcore:generic_probe+0x7c/0xb0 Oct 30 14:59:36 pluto kernel: [] driver_probe_device+0x9b/0x1c0 Oct 30 14:59:36 pluto kernel: [] __device_attach+0x0/0x10 Oct 30 14:59:36 pluto kernel: [] bus_for_each_drv+0x58/0x80 Oct 30 14:59:36 pluto kernel: [] device_attach+0x88/0x90 Oct 30 14:59:36 pluto kernel: [] bus_attach_device+0x55/0xa0 Oct 30 14:59:36 pluto kernel: [] device_add+0x528/0x690 Oct 30 14:59:36 pluto kernel: [] :usbcore:usb_new_device+0x55/0xa0 Oct 30 14:59:36 pluto kernel: [] :usbcore:hub_thread+0x749/0xe10 Oct 30 14:59:36 pluto kernel: [] set_next_entity+0x23/0x50 Oct 30 14:59:36 pluto kernel: [] autoremove_wake_function+0x0/0x30 Oct 30 14:59:36 pluto kernel: [] :usbcore:hub_thread+0x0/0xe10 Oct 30 14:59:36 pluto kernel: [] kthread+0x4b/0x80 Oct 30 14:59:36 pluto kernel: [] child_rip+0xa/0x12 Oct 30 14:59:36 pluto kernel: [] kthread+0x0/0x80 Oct 30 14:59:36 pluto kernel: [] child_rip+0x0/0x12 Oct 30 14:59:36 pluto kernel: Oct 30 14:59:36 pluto kernel: ata4.00: ATAPI: TSSTcorpCD/DVDW SH-S183A, SB02, max UDMA/33 Oct 30 14:59:36 pluto kernel: ata4.00: applying bridge limits Oct 30 14:59:36 pluto kernel: ata4.00: configured for UDMA/33 Oct 30 14:59:36 pluto kernel: scsi 2:0:0:0: Direct-Access ATA SAMSUNG SP2504C VT10 PQ: 0 ANSI: 5 Oct 30 14:59:36 pluto kernel: usb 1-1.1.1: new high speed USB device using ehci_hcd and address 7 Oct 30 14:59:36 pluto kernel: scsi 3:0:0:0: CD-ROMTSSTcorp CD/DVDW SH-S183A SB02 PQ: 0 ANSI: 5 Oct 30 14:59:36 pluto kernel: ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18 Oct 30 14:59:36 pluto kernel: ACPI: PCI Interrupt :01:06.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18 : : uname says: Linux pluto 2.6.24-rc1 #1 PREEMPT Sat Oct 27 22:56:02 CEST 2007 x86_64 GNU/Linux Is this anything to worry about? Please mail if I can help to track this down. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.19.1, sata_sil: sata dvd writer doesn't work
Hi Tejun, Tejun Heo wrote: > > Okay, I just tested a number of dvds on x86-64 and x86. The error > pattern is really interesting. It doesn't matter whether you're on > x86-64 or x86, 2.6.18 or 2.6.20-rc5. The problem occurs when a dvd > which doesn't match dvd's region mask is played. > > MMC command 0xa4 (READ KEY) is the one which always fails. After the > failure, the odd goes into strange state and usually won't respond to > commands. Interestingly, if you pull the power plug or reset the > machine while the READ KEY command is in progress and then reconnect it, > you can play the DVD after that. I've checked this multiple times and > no, dvdcss key caching isn't the cause, crossed checked it multiple times. > > Once you played a dvd this way, the drive seems to remember the dvd and > successfully plays it afterwards. I've checked this multiple times > using completely separate OS installation (one x86, the other x86-64). > How comes that there is no such problem if I connect the drive via an USB SATA adapter? > This almost looks like new defense method against CSS-workaround. Can't > understand why the drive remembers successfully played dvds tho. > I would have the option to return it (playing no DVDs is surely a defect), but this would be a shame. It was lightning fast on writing, a little bit noisy, though, but I was really glad to get rid of that clumsy parallel cable. Do you think it would be reasonable to send a bug report to Samsung, and see what they say? I would need some documentation about these MMC commands, though. Is this part of some "Red Book" standard, or so? Regards Harri signature.asc Description: OpenPGP digital signature
Re: 2.6.19.1, sata_sil: sata dvd writer doesn't work
Hi Tejun, Tejun Heo wrote: > Hello, > > Please do the following and post the result. > > # strace mplayer -v dvd:// > out 2>&1 > I had sent this out last week. Any news about this? Regards Harri signature.asc Description: OpenPGP digital signature
Re: 2.6.19.1, sata_sil: sata dvd writer doesn't work
Hi Tejun, Tejun Heo wrote: > > Please do the following and post the result. > > # strace mplayer -v dvd:// > out 2>&1 > See attachment. I was lucky: On the first run with strace mplayer could play the DVD (still using Tron). But this was not reproducible. Both strace files are attached. Hope this helps. I noticed something else: If I run regionset to report the supported region, then it returns on 64bit: % regionset regionset version 0.1 -- reads/sets region code on DVD drives Current Region Code settings: RPC Phase: Unknown (I) type: NONE vendor resets available: 0 user controlled changes resets available: 0 drive plays discs from region(s): 1 2 3 4 5 6 7 8, mask=0x00 I am pretty sure that this drive is not region-free. On 32bit (booting grml-0.9 from CD on a 2nd drive) I get the expected "region 2 only". Of course I used the same 32bit executable. Regards Harri strace.out.bad.gz Description: Unix tar archive strace.out.good.gz Description: Unix tar archive log.regionset.gz Description: Unix tar archive signature.asc Description: OpenPGP digital signature
Re: 2.6.19.1, sata_sil: sata dvd writer doesn't work
Hi Tejun, After the patch was applied (using 2.6.19.1 instead of 2.6.19, hope you don't mind) I could play a DVD once. Unfortunately this was not reproducible, using the same DVD. I have attached the requested log files for the good and the last bad session. Hope this helps. Which version of the SATA DVD writer have you received? The label on my writer says H/W:A Ver:A September 2006 I hope I don't break any netiquette by posting large log files. Do I? Many thanx Harri out.good.gz Description: Unix tar archive kern.log.good.gz Description: Unix tar archive out.bad.gz Description: Unix tar archive kern.log.bad.gz Description: Unix tar archive signature.asc Description: OpenPGP digital signature
Re: 2.6.19.1, sata_sil: sata dvd writer doesn't work
Harald Dunkel wrote: > Hi folks, > > I've got a problem with a Samsung SATA dvd writer: It > doesn't play video DVDs. If I connect the same drive > via an adapter to USB, then there is no such problem. > PS: To make sure that its not a hardware problem I have tried this drive in another PC, using ata_piix for sata. Same kernel, but 32bit. There was no problem here. Regards Harri signature.asc Description: OpenPGP digital signature
Re: 2.6.19.1, sata_sil: sata dvd writer doesn't work
Hi Tejun, Tejun Heo wrote: > * dmesg is truncated, please post the content of file /var/log/boot.msg. > > * Please post the result of 'lspci -nnvvv' > > * Please try the attached patch and see if it makes any difference and > post the result of 'dmesg' after trying to play a problematic dvd. > It still doesn't work, but the dmesg output looks less weird. See attachments. Hope this helps. Please mail. Regards Harri kern.log.gz Description: Unix tar archive lspci.txt.gz Description: Unix tar archive kern.log.patched.gz Description: Unix tar archive signature.asc Description: OpenPGP digital signature
Re: 2.6.19.1, sata_sil: sata dvd writer doesn't work
Hi Tejun, Tejun Heo wrote: > Harald Dunkel wrote: >> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen >> ata2.00: (BMDMA stat 0x1) >> ata2.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout) >> ata2: soft resetting port >> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) >> ata2.00: model number mismatch 'TSSTcorpCD/DVDW SH-S183A' != 'ÑÅÌhõ³Nõ > > This is really fishy. Something really went wrong there. Please post > full dmesg and does the drive work at all? - eg. data dvd or cd. I haven't tried writing CDs yet, but the last backup on DVD went fine. And it is really fast: It starts writing DVDs with 8X and goes up to 18X (Verbatim DVD-R 16X). I don't see a DMA problem. > How > reproducible is the problem? Always. I tried 5 different commercial video DVD by now. All showed this problem. The video DVDs I created in a Philips DVD recorder (DVD-R) play fine. BTW, region code has been set to 2 (Europe) using regionset. There was no error message, AFAIR. > What program did you use to play dvd? xine, mplayer. > If > mplayer, please run it with -v and post what it says (usb case too). > See attachments. Hope this helps. Please mail if you need more info, or if there is something to try. Regards Harri log.dmesg.gz Description: Unix tar archive log.mplayer.gz Description: Unix tar archive log.mplayer.usb.gz Description: Unix tar archive signature.asc Description: OpenPGP digital signature
2.6.19.1, sata_sil: sata dvd writer doesn't work
Hi folks, I've got a problem with a Samsung SATA dvd writer: It doesn't play video DVDs. If I connect the same drive via an adapter to USB, then there is no such problem. dmesg says: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (BMDMA stat 0x1) ata2.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout) ata2: soft resetting port ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata2.00: model number mismatch 'TSSTcorpCD/DVDW SH-S183A' != 'ÑÅÌhõ³Nõ This is reproducible. lspci: 01:07.0 RAID bus controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01) 01:07.0 0104: 1095:3512 (rev 01) /proc/scsi/scsi: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: TSSTcorp Model: CD/DVDW SH-S183A Rev: SB01 Type: CD-ROM ANSI SCSI revision: 05 I already asked Samsung's hotline for a firmware update, but there is none available. They haven't heard of this problem before, either. My wild guess would be that this is a driver problem. Kernels tried: 2.6.19.1, 2.6.18.3 What would be your suggestion to track down this problem? Regards Harri signature.asc Description: OpenPGP digital signature
2.6.18.3, sata dvd writer: can't watch dvd
Hi folks, I've got a shiny new sata dvd writer: A Samsung SH-183A, most recent firmware SB01. Writing data DVDs is _lightning_ fast, but I cannot watch my css-encrypted movie DVDs, even with libdvdcss installed. If I try, then it becomes unresponsive. dmesg says: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (BMDMA stat 0x1) ata2.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout) ata2: soft resetting port ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata2.00: failed to IDENTIFY (device reports illegal type, err_mask=0x0) ata2.00: revalidation failed (errno=-22) ata2.00: disabled ata2: EH complete Buffer I/O error on device sr0, logical block 0 Buffer I/O error on device sr0, logical block 1 Buffer I/O error on device sr0, logical block 2 Buffer I/O error on device sr0, logical block 3 Buffer I/O error on device sr0, logical block 4 Buffer I/O error on device sr0, logical block 5 Buffer I/O error on device sr0, logical block 6 Buffer I/O error on device sr0, logical block 7 Buffer I/O error on device sr0, logical block 0 Buffer I/O error on device sr0, logical block 1 After that the DVD drive is dead, waiting for a reset. I tried this with 4 DVDs by now. Watching my own DVD-Rs (created in a Philips HD recorder), or commercial DVDs without CSS (e.g. "True Lies") is no problem. The region code is set (2), of course. Any idea? Unfortunately I cannot verify the drive in a proprietary runtime environment. Many thanx in advance. Regards Harri signature.asc Description: OpenPGP digital signature
Re: 2.6.12.5: psmouse mouse detection doesn't work
Hi Mike, Michael Krufky wrote: > Harri- > > I was having problems with my psmouse also. Try the kernel boot option > "usb-handoff", see if that helps. This is just a suggestion. I have > nothing to do with the development of that driver. > It helps. Thanx very much Harri signature.asc Description: OpenPGP digital signature
2.6.12.5: psmouse mouse detection doesn't work
Hi folks, At boot time my Logitech mouse is detected as I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name="PS/2 Generic Mouse" P: Phys=isa0060/serio1/input0 H: Handlers=event1 ts0 mouse0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 After manually reloading psmouse I get the expected I: Bus=0011 Vendor=0002 Product=0002 Version=0049 N: Name="PS2++ Logitech Mouse" P: Phys=isa0060/serio1/input0 H: Handlers=event1 ts0 mouse0 B: EV=7 B: KEY=f 0 0 0 0 B: REL=3 Using psmouse_noext=1 at boot time does not help. How comes that this doesn't work on the first run? I asked this more than a year ago, and somebody posted a fix, but obviously it wasn't accepted. What needs to be done to fix this? Regards Harri signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCE] hotplug-ng 001 release
Greg KH wrote: On Sat, Feb 12, 2005 at 09:30:54AM +0100, Harald Dunkel wrote: If it is not possible to use klibc together with a non-Linux system (e.g. FreeBSD or Mach), then I would suggest to make klibc an optional kernel patch and drop it from udev and hotplug. But it is not possible to use udev or hotplug-ng on a non-Linux system, right? Thats not the point. The point is to remove the copy of the klibc sources from packages like udev and hotplug-ng and to use the existing klibc sources or binaries on the target system instead. Just to keep it modular. As far as "optional kernel patch"? What do you mean? People are working on adding klibc to the main kernel tree, nothing optional about that. I do not know the internals of klibc that much. Is it possible to use klibc on non-Linux systems, e.g. on Mach or FreeBSD? Maybe by adding some #ifdefs to klibc's kernel interface? If yes, then making klibc an integrated part of the Linux kernel source tree and dropping the independent development tree would be a restriction to the use of klibc. AFAIK the plan for initramfs is to move as much functionality as possible from kernel to user space. Why not do the same thing for the sources? Everything that is supposed to be run in user space could be removed from the kernel source tree and managed seperately, either in a set of userspace modules like klibc, hotplug, udev, initramfs, etc., or in a monolithic "userspace-tools" source tree. Surely klibc belongs to the user space. Regards Harri signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCE] hotplug-ng 001 release
Greg KH wrote: Because we don't have an easy way yet to build against a copy of klibc on a system? For right now, it's the simplest way to ensure that it works for everyone, once klibc moves into the kernel tree I can remove it from udev and hotplug-ng. If it is not possible to use klibc together with a non-Linux system (e.g. FreeBSD or Mach), then I would suggest to make klibc an optional kernel patch and drop it from udev and hotplug. Is it causing problems for you? Some months ago I had contributed a patch to add an install target to the klibc Makefiles. I just wonder why it has been ignored. Regards Harri signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCE] hotplug-ng 001 release
Greg KH wrote: I'd like to announce, yet-another-hotplug based userspace project: linux-ng. This collection of code replaces the existing linux-hotplug package with very tiny, compiled executable programs, instead of the existing bash scripts. cpio is running to setup a test partition. But one question: This is yet another package with its own private copy of klibc. Whats the reason behind this non-modular approach? Regards Harri signature.asc Description: OpenPGP digital signature
2.4.5: SCSI devices are mixed up?
Hi folks, It took me quite some time to recognize what has changed between 2.4.4 and 2.4.5 and why my CD drives were not accessable: Somehow the sequence of SCSI devices has been changed. For 2.4.4 the IDE SCSI emulation was scsibus0, my Adaptec 39160 was scsibus1 and scsibus2. Suddenly with 2.4.5 the IDE SCSI stuff is scsibus2. The Adaptec devices moved down one step. You can imagine that this mixed up a lot of things. Fortunately my boot disk wasn't affected. My question is: How can I specify the sequence of the SCSI devices? I would like to make sure that this doesn't happen again. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Overkeen CDROM disk-change messages
Maybe thats related to the problems with my CDROM drives (SCSI or IDE SCSI emulation). I cannot mount any CD with 2.4.5. kern.log says: May 26 15:31:17 bilbo kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 2, lun 0 May 26 15:31:17 bilbo kernel: Detected scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0 May 26 15:31:17 bilbo kernel: Detected scsi CD-ROM sr2 at scsi2, channel 0, id 0, lun 0 May 26 15:31:17 bilbo kernel: sr0: scsi3-mmc drive: 0x/0x cd/rw xa/form2 cdda tray May 26 15:31:17 bilbo kernel: Uniform CD-ROM driver Revision: 3.12 May 26 15:31:17 bilbo kernel: sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray May 26 15:31:17 bilbo kernel: sr2: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray May 26 15:31:17 bilbo kernel: VFS: Disk change detected on device sr(11,1) May 26 15:31:17 bilbo last message repeated 3 times May 26 15:31:17 bilbo kernel: Device 0b:01 not ready. May 26 15:31:17 bilbo kernel: I/O error: dev 0b:01, sector 1024 Of course I did _not_ change the CD 4 times within 1 second. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5: 'mount /cdrom' doesn't work
Jens Axboe wrote: > > On Sat, May 26 2001, Harald Dunkel wrote: > > Hi folks, > > > > With 2.4.5 my CD and DVD drives have become unaccessable. > > > > Can you reproduce this problem? > > Any kernel messages? And please show what happens. > Currently I am back to 2.4.4, but AFAIR I got a message 'no medium found' or something like that on the command line. I have found this in kern.log: May 26 15:31:17 bilbo kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 2, lun 0 May 26 15:31:17 bilbo kernel: Detected scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0 May 26 15:31:17 bilbo kernel: Detected scsi CD-ROM sr2 at scsi2, channel 0, id 0, lun 0 May 26 15:31:17 bilbo kernel: sr0: scsi3-mmc drive: 0x/0x cd/rw xa/form2 cdda tray May 26 15:31:17 bilbo kernel: Uniform CD-ROM driver Revision: 3.12 May 26 15:31:17 bilbo kernel: sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray May 26 15:31:17 bilbo kernel: sr2: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray May 26 15:31:17 bilbo kernel: VFS: Disk change detected on device sr(11,1) May 26 15:31:17 bilbo last message repeated 3 times May 26 15:31:17 bilbo kernel: Device 0b:01 not ready. May 26 15:31:17 bilbo kernel: I/O error: dev 0b:01, sector 1024 Using 2.4.4 the same CD works in the same drive. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5: 'mount /cdrom' doesn't work
Jens Axboe wrote: > > > The only changes that could matter would be SCSI driver changes. You > wouldn't happen to use the new aic7xxx driver? > I had the same problem with the IDE CD writer (using SCSI emulation). Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5: 'mount /cdrom' doesn't work
Hi folks, With 2.4.5 my CD and DVD drives have become unaccessable. Can you reproduce this problem? Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Giant disk on 2.2.17: Any concerns?
"Mohammad A. Haque" wrote: > > > I've used a 250GB and 400GB RAID array with 2.2.x kernels w/o any > problems. We have several thousands of ~1 MB > and >100 MB files. > Many thanx for your fast answer. What kind of controller did you use? Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Giant disk on 2.2.17: Any concerns?
Hi folks, For running some kind of database application (ClearCase 4.1) I would like to attach an external RAID array with 6*30GByte to a RedHat 6.2 machine, using kernel 2.2.17. I don't expect huge files (maximum file size should be about 250MByte), but a lot of middle size files and millions of tiny files. Will this work? Do you expect any problems with the partition table? Many thanx in advance Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 sluggish under fork load
Peter Osterlund wrote: > > I have noticed that 2.4.4 feels a lot less responsive than 2.4.3 under > fork load. This is caused by the "run child first after fork" patch. I > have tested on two different UP x86 systems running redhat 7.0. > > For example, when running the gcc configure script, the X mouse pointer is > very jerky. The configure script itself runs approximately as fast as in > 2.4.3. > That explains why xtoolwait did not work anymore. After applying the patch everything is OK again. Many thanx Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA 82C686 Audio Codec: Clicks
Jani Monoses wrote: > > You could try the ALSA driver if you're certain it is not a hw problem.It > works better here than the one in the kernel. > Now, _this_ is an improvement! I tried the 0.9.0beta3 version of Alsa. No more clicks! Amazing. Many thanx for your help Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ReiserFS? How reliable is it? Is this the future?
Hi folks, If I get the DVD stuff working, then I won't need NT anymore, i.e. I will have an empty disk. What is your impression about ReiserFS? Does it work? Is it stable enough for my daily work, or is it something to try out and watch carefully? Do you use ReiserFS for your boot partition? Or should I try ext3 instead? Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
VIA 82C686 Audio Codec: Clicks
Hi folks, Has anybody an idea how to get rid of the annoying clicks of the VIA 82C686 audio codec? Using xmms (just as an example) I get a click with each new track, when I move and release the track slider, etc. Even this echo -n "" >/dev/dsp produces a click. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
aic7xxx of 2.4.2: 'cdrecord -scanbus' complains about DVD
Hi folks, When I run 'cdrecord -scanbus', then cdrecord complains about my DVD: # cdrecord -scanbus Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling Linux sg driver version: 3.1.17 Using libscg version 'schily-0.1' scsibus0: 0,0,0 0) * 0,1,0 1) * cdrecord: Warning: controller returns wrong size for CD capabilities page. 0,2,0 2) 'PIONEER ' 'DVD-ROM DVD-303 ' '1.09' Removable CD-ROM 0,3,0 3) * 0,4,0 4) 'PIONEER ' 'CD-ROM DR-U16S ' '1.01' Removable CD-ROM 0,5,0 5) * [snip] Is this warning correct? Or is this a problem of cdrecord? Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
svc: unknown program 100227 (me 100003)
Hi folks, Maybe a stupid question, but it would be nice to know what this message means: fright kernel: svc: unknown program 100227 (me 13) 'fright' is the name of the machine in question (2.4.0-test6, x86). I get this about 40 times per day. Many thanx Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: What is up with Redhat 7.0?
Richard Henderson wrote: > The reasons are the following: > > : > (2) C++ in 2.95 is already ABI incompatible with egcs 1.1 and gcc 3.0, > so clearly (to my mind anyway) it didn't matter whether we > shipped 2.95 or a snapshot, we would still be incompatible with > Red Hat 6 and Red Hat 8. > It seems that you are ignoring other major distros (Slackware, Suse, Debian, etc.) as well as commercial software. By providing an incompatible binary interface RedHat splits the Linux community into 2 parts. I am *very* concerned about this. I guess that RedHat (as the owner of Cygnus and working very closely with the FSF) would have had sufficient arguments to get an official(!) gcc 2.96 before release date of RedHat 7.0. Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ISAPnP + Soundblaster doesn't work without 'multiple=0'
Hi Paul, Thanx very much for your patch for sb_card.c. I have tested it with 2.4.0-test9-pre6. The Oops is gone. Have a nice weekend Harri -- Harald Dunkel | [EMAIL PROTECTED] | If your operating system seems to Synopsys GmbH | Kaiserstr. 100 | be made by Dr. Frankenstein, then 52134 Herzogenrath, Germany| it is time for a change. +49 2407 9558 (fax? 44: 0) |Try Linux! --- Paul Laufer wrote: > > Here is the patch that I sent to Linus, but he hasn't applied it yet. > This bug, my bug, has been present since 2.4.0-test7. > > Paul Laufer > > > > >sb_card.c.2.4.0-test9-pre2.patchName: sb_card.c.2.4.0-test9-pre2.patch >Type: Plain Text (text/plain) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ISAPnP + Soundblaster doesn't work without 'multiple=0'
Hi folks, According to Documentation/sound/Soundblaster I have to report that I had to set the option 'multiple=0' to make my Soundblaster16 work. Without this option I get the following message at boot time: : : Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 SB 4.13 detected OK (220) sb: I/O region in use. Sound: Hmm, DMA1 was left allocated - fixed Sound: Hmm, DMA6 was left allocated - fixed Unable to handle kernel paging request at virtual address c8866060 printing eip: c885844d *pde = 012d8063 *pte = Oops: CPU:0 EIP:0010:[] EFLAGS: 00010286 eax: c8866060 ebx: c120cd20 ecx: edx: esi: c1282660 edi: ebp: esp: c7c95f08 ds: 0018 es: 0018 ss: 0018 Process aumix (pid: 65, stackpage=c7c95000) Stack: c1282660 c7d06500 c128e660 c1282660 c7d06500 c128e660 72616863 6a616d2d 312d726f c1280034 ffeb c0128394 c7d06500 c1282660 c1282660 c7d06500 c01276a9 c7d06500 c1282660 0002 0804ddb4 Call Trace: [] [] [] [] [] Code: 8b 10 85 d2 74 1d 52 e8 cf cc 8b f7 83 c4 04 85 c0 74 14 8b : : This is the output of ksymoops: ksymoops 2.3.4 on i586 2.4.0-test8. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.0-test8/ (default) -m /usr/src/linux/System.map (specified) Unable to handle kernel paging request at virtual address c8866060 c885844d *pde = 012d8063 Oops: CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010286 eax: c8866060 ebx: c120cd20 ecx: edx: esi: c1282660 edi: ebp: esp: c7c95f08 ds: 0018 es: 0018 ss: 0018 Process aumix (pid: 65, stackpage=c7c95000) Stack: c1282660 c7d06500 c128e660 c1282660 c7d06500 c128e660 72616863 6a616d2d 312d726f c1280034 ffeb c0128394 c7d06500 c1282660 c1282660 c7d06500 c01276a9 c7d06500 c1282660 0002 0804ddb4 Call Trace: [] [] [] [] [] Code: 8b 10 85 d2 74 1d 52 e8 cf cc 8b f7 83 c4 04 85 c0 74 14 8b >>EIP; c885844d <[soundcore]soundcore_open+49/184> <= Trace; c0128394 Trace; c01276a9 Trace; c01275e3 Trace; c01278d9 Trace; c0108d23 Code; c885844d <[soundcore]soundcore_open+49/184> <_EIP>: Code; c885844d <[soundcore]soundcore_open+49/184> <= 0: 8b 10 mov(%eax),%edx <= Code; c885844f <[soundcore]soundcore_open+4b/184> 2: 85 d2 test %edx,%edx Code; c8858451 <[soundcore]soundcore_open+4d/184> 4: 74 1d je 23 <_EIP+0x23> c8858470 <[soundcore]sou ndcore_open+6c/184> Code; c8858453 <[soundcore]soundcore_open+4f/184> 6: 52push %edx Code; c8858454 <[soundcore]soundcore_open+50/184> 7: e8 cf cc 8b f7call f78bccdb <_EIP+0xf78bccdb> c0115128 Code; c8858459 <[soundcore]soundcore_open+55/184> c: 83 c4 04 add$0x4,%esp Code; c885845c <[soundcore]soundcore_open+58/184> f: 85 c0 test %eax,%eax Code; c885845e <[soundcore]soundcore_open+5a/184> 11: 74 14 je 27 <_EIP+0x27> c8858474 <[soundcore]sou ndcore_open+70/184> Code; c8858460 <[soundcore]soundcore_open+5c/184> 13: 8b 00 mov(%eax),%eax This problem seems to be in since 2.4.0-test7. Please mail me if I can help to fix the problem. Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | If your operating system seems to Synopsys GmbH | Kaiserstr. 100 | be made by Dr. Frankenstein, then 52134 Herzogenrath, Germany| it is time for a change. +49 2407 9558 (fax? 44: 0) |Try Linux! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Update Linux 2.4 Status/TODO list
Hi folks, How can I submit a bug report to be added to this list? Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0-test8: Ooops in soundcore
Alexander Viro wrote: > > On Sat, 9 Sep 2000, Harald Dunkel wrote: > > > Hi folks, > > > > I still experience problems with the most recent kernels. It seems > > to be related to soundcore. > > Funny... s->unit_fops pointing to bogus place in soundcore_open(). > What soundcard are you using? Soundblaster 16, but I have configured multiple soundcards, cause I am managing several machines with different hardware. This is the soundcard section in .config: # # Sound # CONFIG_SOUND=m # CONFIG_SOUND_CMPCI is not set CONFIG_SOUND_EMU10K1=m # CONFIG_SOUND_FUSION is not set # CONFIG_SOUND_ES1370 is not set CONFIG_SOUND_ES1371=m # CONFIG_SOUND_ESSSOLO1 is not set # CONFIG_SOUND_MAESTRO is not set # CONFIG_SOUND_SONICVIBES is not set # CONFIG_SOUND_TRIDENT is not set # CONFIG_SOUND_MSNDCLAS is not set # CONFIG_SOUND_MSNDPIN is not set # CONFIG_SOUND_VIA82CXXX is not set CONFIG_SOUND_OSS=m # CONFIG_SOUND_TRACEINIT is not set # CONFIG_SOUND_DMAP is not set # CONFIG_SOUND_AD1816 is not set # CONFIG_SOUND_SGALAXY is not set # CONFIG_SOUND_ADLIB is not set # CONFIG_SOUND_ACI_MIXER is not set CONFIG_SOUND_CS4232=m # CONFIG_SOUND_SSCAPE is not set # CONFIG_SOUND_GUS is not set # CONFIG_SOUND_ICH is not set # CONFIG_SOUND_VMIDI is not set # CONFIG_SOUND_TRIX is not set # CONFIG_SOUND_MSS is not set # CONFIG_SOUND_MPU401 is not set # CONFIG_SOUND_NM256 is not set # CONFIG_SOUND_MAD16 is not set # CONFIG_SOUND_PAS is not set # CONFIG_PAS_JOYSTICK is not set # CONFIG_SOUND_PSS is not set # CONFIG_SOUND_SOFTOSS is not set CONFIG_SOUND_SB=m # CONFIG_SOUND_AWE32_SYNTH is not set # CONFIG_SOUND_WAVEFRONT is not set # CONFIG_SOUND_MAUI is not set # CONFIG_SOUND_YM3812 is not set # CONFIG_SOUND_OPL3SA1 is not set # CONFIG_SOUND_OPL3SA2 is not set # CONFIG_SOUND_YMPCI is not set # CONFIG_SOUND_UART6850 is not set # CONFIG_SOUND_AEDSP16 is not set # CONFIG_SOUND_TVMIXER is not set Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | If your operating system seems to Synopsys GmbH | Kaiserstr. 100 | be made by Dr. Frankenstein, then 52134 Herzogenrath, Germany| it is time for a change. +49 2407 9558 (fax? 44: 0) |Try Linux! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
2.4.0-test8: Ooops in soundcore
Hi folks, I still experience problems with the most recent kernels. It seems to be related to soundcore. Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | If your operating system seems to Synopsys GmbH | Kaiserstr. 100 | be made by Dr. Frankenstein, then 52134 Herzogenrath, Germany| it is time for a change. +49 2407 9558 (fax? 44: 0) |Try Linux! ksymoops 2.3.4 on i586 2.4.0-test8. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.0-test8/ (default) -m /usr/src/linux/System.map (specified) ds: no socket drivers loaded! Unable to handle kernel paging request at virtual address c8866060 c885844d *pde = 012d9063 Oops: CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010286 eax: c8866060 ebx: c125dd20 ecx: edx: esi: c1283660 edi: ebp: esp: c7e75f08 ds: 0018 es: 0018 ss: 0018 Process aumix (pid: 65, stackpage=c7e75000) Stack: c1283660 c7c89e00 c128f660 c1283660 c7c89e00 c128f660 72616863 6a616d2d 312d726f c1280034 ffeb c0128394 c7c89e00 c1283660 c1283660 c7c89e00 c01276a9 c7c89e00 c1283660 0002 0804ddb4 Call Trace: [] [] [] [] [] Code: 8b 10 85 d2 74 1d 52 e8 cf cc 8b f7 83 c4 04 85 c0 74 14 8b >>EIP; c885844d <[soundcore]soundcore_open+49/184> <= Trace; c0128394 Trace; c01276a9 Trace; c01275e3 Trace; c01278d9 Trace; c0108d23 Code; c885844d <[soundcore]soundcore_open+49/184> <_EIP>: Code; c885844d <[soundcore]soundcore_open+49/184> <= 0: 8b 10 mov(%eax),%edx <= Code; c885844f <[soundcore]soundcore_open+4b/184> 2: 85 d2 test %edx,%edx Code; c8858451 <[soundcore]soundcore_open+4d/184> 4: 74 1d je 23 <_EIP+0x23> c8858470 <[soundcore]soundcore_open+6c/184> Code; c8858453 <[soundcore]soundcore_open+4f/184> 6: 52push %edx Code; c8858454 <[soundcore]soundcore_open+50/184> 7: e8 cf cc 8b f7call f78bccdb <_EIP+0xf78bccdb> c0115128 Code; c8858459 <[soundcore]soundcore_open+55/184> c: 83 c4 04 add$0x4,%esp Code; c885845c <[soundcore]soundcore_open+58/184> f: 85 c0 test %eax,%eax Code; c885845e <[soundcore]soundcore_open+5a/184> 11: 74 14 je 27 <_EIP+0x27> c8858474 <[soundcore]soundcore_open+70/184> Code; c8858460 <[soundcore]soundcore_open+5c/184> 13: 8b 00 mov(%eax),%eax Unable to handle kernel paging request at virtual address 24748b14 c0115135 *pde = Oops: CPU:0 EIP:0010:[] EFLAGS: 00010206 eax: 0001 ebx: c125dd40 ecx: 0003 edx: 24748b00 esi: c7597c20 edi: 0003 ebp: 0003 esp: c7255f00 ds: 0018 es: 0018 ss: 0018 Process au (pid: 232, stackpage=c7255000) Stack: c8858459 24748b00 c7597c20 c72af500 c128f660 c7597c20 c72af500 c128f660 080495a0 0001 c72d5d60 c7fe1005 ffeb c0128394 c72af500 c7597c20 c7597c20 c72af500 c01276a9 c72af500 c7597c20 Call Trace: [] [] [] [] [] [] Code: f6 42 14 02 74 05 31 c0 c3 89 f6 ff 42 10 80 4a 14 18 c3 b8 >>EIP; c0115135<= Trace; c8858459 <[soundcore]soundcore_open+55/184> Trace; c0128394 Trace; c01276a9 Trace; c01275e3 Trace; c01278d9 Trace; c0108d23 Code; c0115135 <_EIP>: Code; c0115135<= 0: f6 42 14 02 testb $0x2,0x14(%edx) <= Code; c0115139 4: 74 05 je b <_EIP+0xb> c0115140 Code; c011513b 6: 31 c0 xor%eax,%eax Code; c011513d 8: c3ret Code; c011513e 9: 89 f6 mov%esi,%esi Code; c0115140 b: ff 42 10 incl 0x10(%edx) Code; c0115143 e: 80 4a 14 18 orb$0x18,0x14(%edx) Code; c0115147 12: c3ret Code; c0115148 13: b8 00 00 00 00mov$0x0,%eax Unable to handle kernel paging request at virtual address 24748b14 c0115135 *pde = Oops: CPU:0 EIP:0010:[] EFLAGS: 00010206 eax: 0001 ebx: c125dd40 ecx: 0003 edx: 24748b00 esi: c72103c0 edi: 0003 ebp: 0003 esp: c7223f00 ds: 0018 es: 0018 ss: 0018 Process rplayd (pid: 243, stackpage=c7223000) Stack: c8858459 24748b00 c72103c0 c72af500 c128f660 c72103c0 c72af500 c128f660 0001 0001 c0130e9c 001d ffeb c0128394 c72af500 c72103c0 c72103c0 c72af500 c01276a9 c72af500 c72103c0 Call Trace: [] [] [] [] [] [] [] Code: f6 42 14 02 74 05 31
test8-pre4: Ooops at boot time
10244c8d c7360900 c777d0c0 c128e6e0 c7360900 c777d0c0 c128e6e0 0001 0001 c0130dac 001d ffeb c0128344 c777d0c0 c7360900 c7360900 c777d0c0 c0127659 c777d0c0 c7360900 Call Trace: [] [] [] [] [] [] [] Code: f6 42 14 02 74 05 31 c0 c3 89 f6 ff 42 10 80 4a 14 18 c3 b8 >>EIP; c0115135<= Trace; c8858459 <[soundcore]soundcore_open+55/184> Trace; c0130dac Trace; c0128344 Trace; c0127659 Trace; c0127593 Trace; c0127889 Trace; c0108d13 <__rwsem_wake+1077/22cc> Code; c0115135 <_EIP>: Code; c0115135<= 0: f6 42 14 02 testb $0x2,0x14(%edx) <= Code; c0115139 4: 74 05 je b <_EIP+0xb> c0115140 Code; c011513b 6: 31 c0 xor%eax,%eax Code; c011513d 8: c3ret Code; c011513e 9: 89 f6 mov%esi,%esi Code; c0115140 b: ff 42 10 incl 0x10(%edx) Code; c0115143 e: 80 4a 14 18 orb$0x18,0x14(%edx) Code; c0115147 12: c3ret Code; c0115148 13: b8 00 00 00 00mov $0x0,%eax 1 warning and 1 error issued. Results may not be reliable. All these problems seem to be related to loadable module support. modutils is 2.3.14. CONFIG_MODVERSIONS is not set. Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | If your operating system seems to Synopsys GmbH | Kaiserstr. 100 | be made by Dr. Frankenstein, then 52134 Herzogenrath, Germany| it is time for a change. +49 2407 9558 (fax? 44: 0) |Try Linux! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
test8-pre2: Boot problems
_walk+532/1912] [fput+12/24] [sys_vhangup+5/60] [filp_close+3/92] [sys_read+41/168] [tracesys+3/35] Code: f6 42 14 02 74 05 31 c0 c3 89 f6 ff 42 10 80 4a 14 18 c3 b8 OPEN: 146.225.224.201 -> 146.225.224.69 UDP, port: 123 -> 123 ippp0: dialing 1 0xx... It seems that all problems are related to loadable module support. modutils is 2.3.14. CONFIG_MODVERSIONS is not set. How can I help to fix this problem? I am not quite sure about the kernel bug report policy, so please forgive me if something is wrong or missing. Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | If your operating system seems to Synopsys GmbH | Kaiserstr. 100 | be made by Dr. Frankenstein, then 52134 Herzogenrath, Germany| it is time for a change. +49 2407 9558 (fax? 44: 0) |Try Linux! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
