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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44FE8EBA.4060104@jordet.net>
Date:	Wed, 06 Sep 2006 11:02:50 +0200
From:	Stian Jordet <liste@...det.net>
To:	Daniel Drake <dsd@...too.org>
CC:	akpm@...l.org, sergio@...giomb.no-ip.org, jeff@...zik.org,
	greg@...ah.com, cw@...f.org, bjorn.helgaas@...com,
	linux-kernel@...r.kernel.org, alan@...rguk.ukuu.org.uk,
	harmon@....edu, len.brown@...el.com, vsu@...linux.ru
Subject: Re: [NEW PATCH] VIA IRQ quirk behaviour change

Daniel Drake wrote:
> Stian Jordet: You're on CC due to a discussion linked to from above where
> it appeared that you needed Bjorn's patch. Please test this patch against
> unmodified 2.6.17 or 2.6.18-rc and let us know if there are any problems.
> 
No more usb for me with this patch :P

When usb is loaded I get this in dmesg:

irq 9: nobody cared (try booting with the "irqpoll" option)
  [<c01302d3>] __report_bad_irq+0x2b/0x69
  [<c01304bd>] note_interrupt+0x1ac/0x1e3
  [<c0246175>] acpi_irq+0xb/0x14
  [<c012fadb>] handle_IRQ_event+0x23/0x49
  [<c012fbb3>] __do_IRQ+0xb2/0xe6
  [<c0104b3d>] do_IRQ+0x43/0x52
  [<c01031ea>] common_interrupt+0x1a/0x20
  [<c0101620>] default_idle+0x0/0x59
  [<c0101651>] default_idle+0x31/0x59
  [<c01016d7>] cpu_idle+0x5e/0x74
  [<c053d6d7>] start_kernel+0x353/0x35a
handlers:
[<c024616a>] (acpi_irq+0x0/0x14)
Disabling IRQ #9

and while USB has the same irq in /proc/interrupts now as earlier, usb 
doesn't work (or sometimes it does, just dog slow!). Acpi is of course 
disabled, so no acpi events neither.

I have to admit, that this computer have some weird behaviour - see 
http://bugzilla.kernel.org/show_bug.cgi?id=2874 - but still, it's been 
working well for many years now, before this patch. While I do 
understand that I seem to be the only one affected by this bug, I hope 
someone will help me look into another way to solve my problems if this 
patch get applied.

Thanks.

-Stian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ