On Friday 06 January 2006 01:47, Andrew Morton wrote:
> Alexander Gran <[email protected]> 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
It means submit_bio(WRITE_BARRIER, bio) fails and reiser4 falls back to
synchronous write in the transaction commit code.
Ext3, reiserfs do similar checks in their code and all issue warnings if those
checks fail. But only ext3, it seems, has write barrier support disabled by
default.
> 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
--
Alex.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
