Hello,
my Asus M2N Notebook hangs doing the following on 2.6.22-rc3 (from Ubuntu
Gutsy Gibbon Tribe-1):
Setting up standard PCI resources
The non-scrollable output on the full screen can be found here:
http://planck.djpig.de/~mcornils/pci-hang.jpg
Booting with nolapic helps, but makes the SATAized IDE controller buggy
(spontaneous timeouts occuring, which do not happen on OpenBSD or Windows XP
(shiver)).
I'm using the latest BIOS (A208). Now I know it's buggy as hell and I've
already complained to Asus, but to no avail.
There have been other reports of the problem on Asus notebooks. I've collected
some links:
http://bugzilla.kernel.org/show_bug.cgi?id=8278
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/83290
http://bugzilla.kernel.org/show_bug.cgi?id=7906 (maybe related)
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/8012 (maybe
related)
http://lists.debian.org/debian-user-german/2006/12/msg01017.html (german)
I'm willing to provide any needed information (like DSDT table, system
info, ...) and try out almost anything (I do not have a serial console handy
though - the system does not have serial).
Yours,
-Malte
PS: A Cc: is preferred, but not necessary.
> On Thu, 14 Jun 2007 15:05:27 +0200 Malte Cornils <[email protected]> wrote:
> Hello,
>
> my Asus M2N Notebook hangs doing the following on 2.6.22-rc3 (from Ubuntu
> Gutsy Gibbon Tribe-1):
>
> Setting up standard PCI resources
>
> The non-scrollable output on the full screen can be found here:
> http://planck.djpig.de/~mcornils/pci-hang.jpg
>
> Booting with nolapic helps, but makes the SATAized IDE controller buggy
> (spontaneous timeouts occuring, which do not happen on OpenBSD or Windows XP
> (shiver)).
>
> I'm using the latest BIOS (A208). Now I know it's buggy as hell and I've
> already complained to Asus, but to no avail.
>
> There have been other reports of the problem on Asus notebooks. I've collected
> some links:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=8278
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/83290
> http://bugzilla.kernel.org/show_bug.cgi?id=7906 (maybe related)
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/8012 (maybe
> related)
> http://lists.debian.org/debian-user-german/2006/12/msg01017.html (german)
>
> I'm willing to provide any needed information (like DSDT table, system
> info, ...) and try out almost anything (I do not have a serial console handy
> though - the system does not have serial).
>
Are any of these problems new behaviour, or has it always done this?
If there _is_ new behaviour here, are you able to identify which earlier
kernel versions did not exhibit it?
Hello Andrew,
On Thursday, 21. Juni 2007 14:27 Andrew Morton wrote:
> > Booting with nolapic helps, but makes the SATAized IDE controller buggy
> > [...] There have been other reports of the problem on Asus notebooks. I've
> > collected some links:[...]
> Are any of these problems new behaviour, or has it always done this?
>
> If there _is_ new behaviour here, are you able to identify which earlier
> kernel versions did not exhibit it?
The patch causing that behaviour went in between 2.6.18 and 2.6.19rc-1. I have
some 100 patches to go bisecting the bug, but it's slow work due to
difficulties in getting physical access to the machine for extended periods
of time.
I'll be sure to let you know when I have the exact commit. That may be at any
time from tomorrow to beginning of July, I'm not sure yet what my free time
allows.
Yours,
-Malte
> On Fri, 22 Jun 2007 19:43:34 +0200 Malte Cornils <[email protected]> wrote:
> Hello Andrew,
>
> On Thursday, 21. Juni 2007 14:27 Andrew Morton wrote:
> > > Booting with nolapic helps, but makes the SATAized IDE controller buggy
> > > [...] There have been other reports of the problem on Asus notebooks. I've
> > > collected some links:[...]
>
> > Are any of these problems new behaviour, or has it always done this?
> >
> > If there _is_ new behaviour here, are you able to identify which earlier
> > kernel versions did not exhibit it?
>
> The patch causing that behaviour went in between 2.6.18 and 2.6.19rc-1. I have
> some 100 patches to go bisecting the bug, but it's slow work due to
> difficulties in getting physical access to the machine for extended periods
> of time.
>
> I'll be sure to let you know when I have the exact commit. That may be at any
> time from tomorrow to beginning of July, I'm not sure yet what my free time
> allows.
>
OK, thanks. There's no rush but please do persist...
