From: Andrew Morton <akpm@osdl.org>
To: Alexander Gran <alex@zodiac.dnsalias.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, "Brown,
Len" <len.brown@intel.com>, Adam Belay <ambx1@neo.rr.com>,
reiserfs-dev@namesys.com, Dave Airlie <airlied@linux.ie>,
"Vladimir V. Saveliev" <vs@namesys.com>
Subject: Re: Re. 2.6.15-mm1
Date: Thu, 5 Jan 2006 14:47:20 -0800 [thread overview]
Message-ID: <20060105144720.25085afa.akpm@osdl.org> (raw)
In-Reply-To: <200601051801.29007@zodiac.zodiac.dnsalias.org>
Alexander Gran <alex@zodiac.dnsalias.org> wrote:
>
> Hi,
>
> just tried 2.6.15-mm1 on my thinkpad. Various aspects that didn't work / look
> good:
Thanks. A few people have some work to do before they are ready to merge to 2.6.16.
> Jan 5 16:22:38 t40 kernel: pnp: PnP ACPI init
> Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
> Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
> Jan 5 16:22:39 t40 last message repeated 10 times
> Jan 5 16:22:39 t40 kernel: pnp: PnP ACPI: found 0 devices
pnpacpi is unhappy.
> All over the place logs like this:
> Jan 5 16:22:43 t40 kernel: **** SET: Misaligned resource pointer: f7db5502
> Type 07 Len 0
> Unknown to me so far..
acpi is unhappy.
> When X startet, the laptops crashed:
> Jan 5 16:22:43 t40 kernel: <4>reiser4[syslogd(2729)]: disable_write_barrier
> (fs/reiser4/wander.c:233)[zam-1055]:
> Jan 5 16:22:43 t40 kernel: WARNING: disabling write barrier
Vladimir, is that expected?
> Jan 5 16:22:43 t40 kernel:
> Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
> 0xe0000000,0x4000000
> Jan 5 16:22:48 t40 last message repeated 2 times
Is that new?
> Jan 5 16:22:48 t40 kernel: agpgart: Found an AGP 2.0 compliant device at
> 0000:00:00.0.
> Jan 5 16:22:48 t40 kernel: c028b7cf
> Jan 5 16:22:48 t40 kernel: Modules linked in: irtty_sir sir_dev cfq_iosched
> ehci_hcd uhci_hcd
> Jan 5 16:22:48 t40 kernel: EIP: 0060:[<c028b7cf>] Not tainted VLI
> Jan 5 16:22:48 t40 kernel: EFLAGS: 00013202 (2.6.15-mm1)
> Jan 5 16:22:48 t40 kernel: <0>c028b9e9 f762ff08 00000002 00000000
> c19720ec 00000000 1f000217 c1a79400
> Jan 5 16:22:48 t40 kernel: <0>00000032 00000001 c028bfb5 c0297262
> c1a79400 c02972af 1f000207 c029727f
hm, it's not clear what oopsed. Can you get a cleaner copy of this?
> Jan 5 16:22:48 t40 kernel: <3>[drm:drm_release] *ERROR* Device busy: 1 0
drm is unhappy
next prev parent reply other threads:[~2006-01-05 22:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 17:01 Alexander Gran
2006-01-05 22:47 ` Andrew Morton [this message]
2006-01-05 23:33 ` Alexander Gran
2006-01-06 0:21 ` Andrew Morton
2006-01-06 0:28 ` Dave Airlie
2006-01-06 0:38 ` Dave Jones
2006-01-06 9:30 ` Hans Reiser
2006-01-06 18:29 ` Alexander Zarochentsev
2006-01-05 23:31 Etienne Lorrain
2006-01-06 0:15 ` Andrew Morton
2006-01-06 0:36 ` Linus Torvalds
2006-01-06 10:04 ` Etienne Lorrain
2006-01-06 2:05 Seth, Rohit
2006-01-06 5:36 Brown, Len
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060105144720.25085afa.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=airlied@linux.ie \
--cc=alex@zodiac.dnsalias.org \
--cc=ambx1@neo.rr.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=vs@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®