linux-kernel - Re: Syba 8-Port Serial Card Unidentified By Kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 22 Oct 2007 19:33:23 +0400
From:	Andrey Panin <pazke@...pac.ru>
To:	Chris Bergeron <chris@...urn.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Syba 8-Port Serial Card Unidentified By Kernel

On 291, 10 18, 2007 at 01:00:06 -0400, Chris Bergeron wrote:
> Andrey Panin wrote:
>> On 290, 10 17, 2007 at 06:16:58 -0400, Chris Bergeron wrote:
>>   
>>> Andrey Panin wrote:
>>>     
>>>> Is it possible to connect two ports and run getty on one port and 
>>>> minicom on
>>>> another ? We should check that UARTs are really working.
>>>>
>>>>         
>>> I used the on-board serial port as a known working control (after getting 
>>> it to work with the other onboard serial port) to try and connect over to 
>>> one of the Syba card ports (using Cutecom & getty).  The lines light up, 
>>> but there's nothing getting sent from the 8-port as far as I can see.
>>>     
>>
>> Oh crap... I missed this fscking "Disabling IRQ #17" line in your dmesg.
>> Can you try with firewire controller disabled somehow ?
>>
>>   
> Ah, I forgot to make note of that.  I did actually turn off Firewire in the 
> BIOS.  Assuming that worked (and it looks like it did) the following 
> section probably contains the relevant bits.  Still getting the IRQ 17 
> error.
>
> -- Chris
>
> PCI: Setting latency timer of device 0000:00:05.0 to 64
> NET: Registered protocol family 17
> eth0: no IPv6 routers present
> irq 17: nobody cared (try booting with the "irqpoll" option)
> [<c0104f45>] show_trace_log_lvl+0x1a/0x2f
> [<c0105939>] show_trace+0x12/0x14
> [<c0105951>] dump_stack+0x16/0x18
> [<c0152f90>] __report_bad_irq+0x39/0x79
> [<c01531af>] note_interrupt+0x1df/0x218
> [<c0153754>] handle_fasteoi_irq+0x91/0xb6
> [<c0105fef>] do_IRQ+0x7c/0x95
> [<c0104946>] common_interrupt+0x2e/0x34
> [<c010233a>] cpu_idle+0x1c/0xc2
> [<c02deed9>] rest_init+0x4d/0x4f
> [<c03e7979>] start_kernel+0x32a/0x332
> [<00000000>] 0x0
> =======================
> handlers:
> [<c023ecae>] (serial8250_interrupt+0x0/0x115)
> Disabling IRQ #17
> hda: DMA timeout retry
>
>
> full dmesg output at 
> http://pcburn.com/files/Syba_serial_controller/dmesg_with_1394_disabled.txt

So the card probably generates screaming interrupt... that's bad.
I found some docs for IT887x chips, according to these docs  IT887x
have simple interrupt controller inside. Further investigation is needed.

Can you post output of lspci -xxx ?

-- 
Andrey Panin		| Linux and UNIX system administrator
pazke@...pac.ru		| PGP key: wwwkeys.pgp.net

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)