[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1108271356450.3459@fry.nucleusys.com>
Date: Sat, 27 Aug 2011 14:05:52 +0300 (EEST)
From: Petko Manolov <petkan@...leusys.com>
To: Alan Stern <stern@...land.harvard.edu>
cc: Andrew Morton <akpm@...ux-foundation.org>, netdev@...r.kernel.org,
USB list <linux-usb@...r.kernel.org>,
bugme-daemon@...zilla.kernel.org,
Petko Manolov <petkan@...rs.sourceforge.net>,
csanyipal@...il.com, jmm@...ian.org
Subject: Re: [Bugme-new] [Bug 40372] New: Driver pegasus freeze networking
very often so one must reboot to get it to work again
On Fri, 26 Aug 2011, Alan Stern wrote:
> On Fri, 26 Aug 2011, Andrew Morton wrote:
>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=40372
>>>
>>> Summary: Driver pegasus freeze networking very often so one
>>> must reboot to get it to work again
>
>>> Hi,
>>>
>>> the driver pegasus freezes networking often so one must to reboot to get
>>> networking work again.
>>>
>>> At reboot the system hang.
>>>
>>> At this point one must press the Reset button of the PC Box because
>>> the system hangs forever. I can't see any messages on the console screen when I
>>> want to reboot at point when system freezes.
>
> How do you know the pegasus driver is responsible for this problem?
>
> Do any error messages show up if you want a few minutes before
> rebooting? What does the dmesg log say?
The list of loaded modules is rather impressive. Could you please reduce
their number as much as possible and test again?
Without the kernel panic screen there's no easy way to determine what
actually happened and which module caused the hang-up, so we'll need that
as well.
Petko
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists