On a "5.9.0-1-powerpc64" system with PAGE_SIZE 64 KiB, the attempt to read
a zisofs compressed file with zisofs block size 32 KiB yields a kernel
Oops if the file contains sparse blocks of 32 KiB all zeros.
BUG: Unable to handle kernel data access on read at 0xfff01417f3f9800
Le dim. 19 avr. 2020 à 19:08, Dennis Clarke a écrit :
> I have a dedicated Intel i7 based machine
Mine being Xeon the frequency are likely lower, and the storage is
spinning rust (a ZFS mirrored pool on a couple of old SAS drive). So
you should be at least as fast, if not perceptively faster...
On 4/19/20 2:14 PM, Romain Dolbeau wrote:
Le ven. 17 avr. 2020 à 02:30, Dennis Clarke a écrit :
I have no idea how that works.
Normally it's the default, quoting the doc: "The default is to enable
multi-threading where both the back-end and front-ends support it and
no incompatible TCG featur
Le ven. 17 avr. 2020 à 02:30, Dennis Clarke a écrit :
> I have no idea how that works.
Normally it's the default, quoting the doc: "The default is to enable
multi-threading where both the back-end and front-ends support it and
no incompatible TCG features have been enabled (e.g. icount/replay)."
On 4/16/20 5:46 AM, Romain Dolbeau wrote:
Le jeu. 16 avr. 2020 à 01:07, Dennis Clarke a écrit :
With luck I can run multiple POWER9 cpus and get better performance
Multithreaded TCG works fine, so yes '-smp 12' does give me better
performance for multi-threaded/multi-programmed workload in
Le jeu. 16 avr. 2020 à 01:07, Dennis Clarke a écrit :
> With luck I can run multiple POWER9 cpus and get better performance
Multithreaded TCG works fine, so yes '-smp 12' does give me better
performance for multi-threaded/multi-programmed workload in the VM
(e.g., compiling).
> I may give Debia
On 4/15/20 1:26 PM, Romain Dolbeau wrote:
Le mer. 15 avr. 2020 à 15:08, Dennis Clarke a écrit :
This is inside a qemu ppc64 instance wherein attempting to use POWER9
or the POWER8 cpu types. Seems to result in a kernel panic repeatedly :
I have a QEMU PPC64EL image running Debian Buster, and
Le mer. 15 avr. 2020 à 15:08, Dennis Clarke a écrit :
> This is inside a qemu ppc64 instance wherein attempting to use POWER9
> or the POWER8 cpu types. Seems to result in a kernel panic repeatedly :
I have a QEMU PPC64EL image running Debian Buster, and it has been
rock-solid for my usage (I che
This is inside a qemu ppc64 instance wherein attempting to use POWER9
or the POWER8 cpu types. Seems to result in a kernel panic repeatedly :
Debian GNU/Linux bullseye/sid enceladus hvc0
enceladus login: [ 1881.112289] Oops: Exception in kernel mode, sig: 4 [#1]
[ 1881.113655] BE PAGE_SIZE
On Tue, May 26, 2015 at 5:21 PM, Daniel Kahn Gillmor
wrote:
> On Tue 2015-05-26 04:54:47 -0400 about https://bugs.debian.org/692324,
> Mathieu Malaterre wrote:
>> Any update with more recent kernel ?
>
> Sorry, i don't have easy access to this machine ("colddeadhands") right
> now. I know it was
On Sep 18, 2008, at 3:55 AM, maximilian attems wrote:
On Wed, Sep 17, 2008 at 11:54:01PM -0400, Rick Thomas wrote:
Well...
I did another dist-upgrade tonite, and the problem went away. Go
figure...
Some one of the following list of upgrades (extracted from /var/log/
dpkg.log) fixed it.
200
On Wed, Sep 17, 2008 at 11:54:01PM -0400, Rick Thomas wrote:
> Well...
>
> I did another dist-upgrade tonite, and the problem went away. Go
> figure...
>
> Some one of the following list of upgrades (extracted from /var/log/
> dpkg.log) fixed it.
>
> 2008-09-17 22:57:42 upgrade initramfs-too
Well...
I did another dist-upgrade tonite, and the problem went away. Go
figure...
Some one of the following list of upgrades (extracted from /var/log/
dpkg.log) fixed it.
2008-09-17 22:57:17 upgrade ncurses-bin 5.6+20080907-1 5.6+20080913-1
2008-09-17 22:57:23 upgrade libncurses5 5.6+200
On Sep 17, 2008, at 4:02 AM, Rick Thomas wrote:
I have another system running Sid. I haven't done a dist-upgrade
on it yet. So I'll see what happens there.
I did the dist-upgrade on my other G4 running Sid, and the oops
doesn't happen.
Looking at the syslog extracts
s the whole system
PowerPC (G4 Macintosh) running sid.
Ran nightly dist-upgrade which updated initramfs-tools.
Now the system crashes with a kernel oops.
I restored the old initrd.img...bak and it now boots OK.
curiously, after gunzip-ing and un-cpio-ing the two initrd.img files,
the only differen
On 2008-05-26 01:21:04 +0200, Vincent Lefevre wrote:
> Note: When I start vlc from bash or pdksh, I do not have this problem.
> So, if you want to try to reproduce it, use zsh to start vlc (even
> "zsh -f" to make sure rc files do not change anything important).
Eventually I could reproduce it wit
Everything is described on
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482346
(see the full discussion). Here's a summary:
When I start vlc from zsh and interrupt it with Ctrl-C several times,
it segfaults, the kernel oops whilst trying to page in memory to write
the coredump, an
On Mon, 2006-07-03 at 12:33 -0500, James Stallings II wrote:
> DOH!!
>
> Mea Culpa, mea Culpa...
>
>
> Not only was the adaptec not integrated on the mainboard, its one I
> put in myself a year ago.
>
> Oh well, I pulled it but still get the kernel oops in the scsi_
DOH!!
Mea Culpa, mea Culpa...
Not only was the adaptec not integrated on the mainboard, its one I
put in myself a year ago.
Oh well, I pulled it but still get the kernel oops in the scsi_mod...
unfortunately much of the oops output scrolls off the screen. How can
I page back to the beginning
On Mon, 2006-07-03 at 06:38 -0500, James Stallings II wrote:
> Greetings All,
>
> I've recently attempted to install debian on my Mac - and it all goes
> quite well until the reboot after installation. It would appear that
> there is an unused adaptec SCSI Host controller integrated into the
> mai
Greetings All,
I've recently attempted to install debian on my Mac - and it all goes
quite well until the reboot after installation. It would appear that
there is an unused adaptec SCSI Host controller integrated into the
mainboard, which currently has no application on my system (except for
bork
On Sat, 01 Jul 2006 the mental interface of
Kel Modderman told:
> Elimar Riesebieter wrote:
> >On Thu, 15 Jun 2006 the mental interface of
> >Elimar Riesebieter told:
> >
> >
> >>Package: madwifi-source
> >>Version: 0.svnr1644.0.9.0-1
> >>Severity: important
> >>
> >[...]
> >
> >There are no
etup DMA (and UDMA for IDE devices) works without any data
corruption. I tested this with around 500 MD5 checksum tests of three
different files with a file size of at least 100 MB. But when I view a DVD
for example (without HIGHMEM support), the system crashes with the following
kernel oops:
Ma
Le Dimanche 23 Avril 2006 14:39, Filippo Giunchedi a écrit :
> this has been reported before, try loading i2c-powermac before
> snd-powermac, i.e. add i2c-powermac to /etc/modules and before
> snd-powermac
Done that, heard sound, thank you !
--
feth
On Sun, 23 Apr 2006 14:21:26 +0200, Feth AREZKI wrote:
> Of course I don't get sound after that.
>
> Anyone experiencing trouble with this kernel version ?
this has been reported before, try loading i2c-powermac before
snd-powermac, i.e. add i2c-powermac to /etc/modules and before
snd-powermac
.16-9)
([EMAIL PROTECTED]) Thu Apr 20 17:23:17 CEST 2006, I get a kernel oops
whenever snd-powermac is loaded (attached is a pure dmesg extract ).
Of course I don't get sound after that.
Anyone experiencing trouble with this kernel version ?
--
Feth
Unable to handle kernel paging request f
ok got it back to install, but still here nothing but nashing of teeth
when try to use my delta 66 with alsa module ICE1712 (Envy24).
On Mon, 2006-04-10 at 16:19 -0400, caleb storms wrote:
> ok, i posted about a problem i was having with alsa sound driver for
> delta 66 and thought that upgrading
ok, i posted about a problem i was having with alsa sound driver for
delta 66 and thought that upgrading my alsa drivers would help. However
after trying to compile and install alsa from source. Now i have
nothing. i tried building the modules and tried reinstalling the
original alsa package. I
Hi everybody,
In the meantime, I have found the culprit for the problem: it
was indeed a hardware problem and the IDE connector cable (the
one between the harddrive and the IDE card) seems to be
defect. After replacing it, everything works fine!
I first thought, it was the RAM but this does not
Another (and hopefully final) discovery: having played around with
smartmontools, I think now that you first have to enable SMART on
a device before it records errors. I have done this and started
the cp-process again (the one which initially resulted in the
crash). And indeed,
smartctl -a /de
On Sat, 1 Apr 2006, Kaspar Fischer wrote:
> I see that I have 190MB RAM, and running memtest on some 160MB
> of these works fine:
>
> bumbum:/tmp/ramtest/memtester-4.0.5# ./memtester 160
> memtester version 4.0.5 (32-bit)
> Copyright (C) 2005 Charles Cazabon.
> Licensed under the GNU General Publ
First of all, thanks a lot to Rick and Thomas for your advice
and background information!
On 18.03.2006, at 07:03, Rick Thomas wrote:
On Mar 17, 2006, at 9:49 PM, Kaspar Fischer wrote:
On 17.03.2006, at 19:35, Michael Schmitz wrote:
Bad RAM, perhaps? Or other hardware dying?
As to RAM, how
On 3/26/06, Michael Schmitz <[EMAIL PROTECTED]> wrote:
> > Unable to handele kernel paging request for data at address 0x0008
> > Faulting instruction address:0xe2709440
> > Oops : kernel acces of bad area, sig 11 [#1]
> > ...
> > ...
> > NIP [E2709
> Unable to handele kernel paging request for data at address 0x0008
> Faulting instruction address:0xe2709440
> Oops : kernel acces of bad area, sig 11 [#1]
> ...
> ...
> NIP [E2709440] ieee80211_master_star_xmit+0x6c/0x4bc [80211]
> LR [E2709400] ieee80211_master_star_x
t kernel: wlan0.11: Does not support passive scan, disabled")
---
In console I see ( _manually_ copied)
--
Unable to handele kernel paging request for data at address 0x0008
Faulting instruction address:0xe2709440
Oops : kernel acces
> > I bet it does - I still haven't tried a recent 2.6.16 after hearing so
> > many 'doesn't boot' reports here. Color me lazy if you must.
>
> Doesn't boot ? how so ? because of this sound problem ? I'm very curious
> to know if there are any others. I've fixed a lot in the late 2.6.16-rc
> stages
Hi,
> For a more elegant way to do it, see the modprobe.conf man page.
>
> install snd-powermac /sbin/modprobe i2c-powermac; /sbin/modprobe
> --ignore-install snd-powermac
>
> should do what you need.
For some odd reason, this does not work for me.
A simple
alias i2c-keywest i2c-powermac
does
> > I bet it does - I still haven't tried a recent 2.6.16 after hearing so
> > many 'doesn't boot' reports here. Color me lazy if you must.
>
> Doesn't boot ? how so ? because of this sound problem ? I'm very curious
Nope, that wouldn't be fatal anyway I guess. I'll dig through my mailbox
to see w
> I bet it does - I still haven't tried a recent 2.6.16 after hearing so
> many 'doesn't boot' reports here. Color me lazy if you must.
Doesn't boot ? how so ? because of this sound problem ? I'm very curious
to know if there are any others. I've fixed a lot in the late 2.6.16-rc
stages and I exp
Benjamin Herrenschmidt wrote:
Well, in that case it looks like a real bug, then. Disassemble
i2c_smbus_write_byte_data and try to figure out why it crashes there ...
I think it crashes because the sound driver is stupid and tries to tap
an i2c bus before it was bound to one at all, thus de
> yeah, I know how to load a module. I mean, in the boot sequence modules
> are autoloaded, and i2c-powermac is loaded *after* snd-powermac, so the
> oops.
Sorry, I wasn't sure what precisely you were asking about. Add
i2c-powermac to /etc/modules to force loading the module ear
Yves-Alexis Perez wrote:
On Wed, 2006-03-22 at 09:54 +0100, Michael Schmitz wrote:
modprobe i2c-powermac (as root).
yeah, I know how to load a module. I mean, in the boot sequence modules
are autoloaded, and i2c-powermac is loaded *after* snd-powermac, so the
oops.
You only have
> I think his problem is a different bug related to the sound driver
> blowing up if the i2c driver hasn't been loaded first.
Looked like something related to the i2c interface for sure - but that's
all I could guess from the oops without actually looking at the source.
> Mak
On Wed, 2006-03-22 at 09:54 +0100, Michael Schmitz wrote:
> modprobe i2c-powermac (as root).
yeah, I know how to load a module. I mean, in the boot sequence modules
are autoloaded, and i2c-powermac is loaded *after* snd-powermac, so the
oops.
--
Yves-Alexis Perez
--
To UNSUBSCRIBE, email
> > I think it crashes because the sound driver is stupid and tries to tap
> > an i2c bus before it was bound to one at all, thus dereferences NULL...
> > Should work if you make sure the i2c driver is loaded first. The problem
> > was introduced in part because of the driver name change (i2c-keywe
On Wed, 2006-03-22 at 09:08 +1100, Benjamin Herrenschmidt wrote:
> > Well, in that case it looks like a real bug, then. Disassemble
> > i2c_smbus_write_byte_data and try to figure out why it crashes there ...
>
> I think it crashes because the sound driver is stupid and tries to tap
> an i2c bus b
> Well, in that case it looks like a real bug, then. Disassemble
> i2c_smbus_write_byte_data and try to figure out why it crashes there ...
I think it crashes because the sound driver is stupid and tries to tap
an i2c bus before it was bound to one at all, thus dereferences NULL...
Should work if
On Tue, 2006-03-21 at 15:44 +0100, Michael Schmitz wrote:
> > Mar 21 11:23:41 kaluha kernel: Oops: Kernel access of bad area, sig: 11 [#1]
> > Mar 21 11:23:41 kaluha kernel: PREEMPT
>
> You Shalt Not Compile Thine Kernel Using The PREEPMT Option On PowerPC.
> Ever.
Heh... I&
> Mar 21 16:43:43 kaluha kernel: NIP: C01C20BC LR: F265D7FC CTR: C01C2090
> Mar 21 16:43:43 kaluha kernel: REGS: ef247cc0 TRAP: 0300 Not tainted
> (2.6.16)
> Mar 21 16:43:43 kaluha kernel: MSR: 9032 CR:
> 22008244 XER: 2000
> Mar 21 16:43:43 kaluha kernel: DAR: 0002, DSISR: 400
> Mar 21 11:23:41 kaluha kernel: Oops: Kernel access of bad area, sig: 11 [#1]
> Mar 21 11:23:41 kaluha kernel: PREEMPT
You Shalt Not Compile Thine Kernel Using The PREEPMT Option On PowerPC.
Ever.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
Michael Schmitz wrote:
>>Mar 21 11:23:41 kaluha kernel: Oops: Kernel access of bad area, sig: 11 [#1]
>>Mar 21 11:23:41 kaluha kernel: PREEMPT
>>
>>
>
>You Shalt Not Compile Thine Kernel Using The PREEPMT Option On PowerPC.
>Ever.
>
> Michael
>
Michael Schmitz wrote:
>>Mar 21 11:23:41 kaluha kernel: Oops: Kernel access of bad area, sig: 11 [#1]
>>Mar 21 11:23:41 kaluha kernel: PREEMPT
>>
>>
>
>You Shalt Not Compile Thine Kernel Using The PREEPMT Option On PowerPC.
>Ever.
>
> Michael
>
Hi All,
i've just compiled a vanilla 2.6.16 kernel on my powerbook G4 15"
running debian testing.
Everything looks fine except that, when the sound module is loaded i'm
getting a kernel OOPS:
Mar 21 11:23:41 kaluha kernel: Oops: Kernel access of bad area, sig: 11 [#1]
Mar 21
On Mar 17, 2006, at 9:49 PM, Kaspar Fischer wrote:
On 17.03.2006, at 19:35, Michael Schmitz wrote:
Bad RAM, perhaps? Or other hardware dying?
As to RAM, how can I test it? http://www.memtest86.com/ seems
to be for Intel architectures only.
I wish I knew.
I guess this need not be a lin
On 17.03.2006, at 19:35, Michael Schmitz wrote:
Bad RAM, perhaps? Or other hardware dying?
The harddrives themselves are fine: they are less than two
months old and smartmontools' smartctl reports no errors
at all.
The BadCRC seems to indicate otherwise. Though this error should
also be
lo
y bmac_rx_intr,
so the kernel ran out of room receiving data from the network. Seems
non-fatal.
The oops happened in do_select which, again, is the network stack - maybe
there still was a memory problem. Please note that the lost disk interrupt
happened several minutes earlier, so the disk error likely wasn
> The machine then crashed and restarted into read-only mode
> (not in the log because of the read-only, I guess) and fsck
> found the /dev/hdb2 ext2-filesytem to be severally damaged
> (some 1 duplicate blocks).
>
> Do you have any idea what this could be?
Bad RAM, perhaps? Or other hardware
d for more background information: what
does a lost interrupt mean? What is a order-0 page allocation
failure, and the mentioned kernel oops, is it more serious
than its name "oops"?
Also, does this look like something non-powerpc specific
so that I should seek for help on another lis
Hi list,
My machine crashed after /dev/hdb encoutered a "lost interrupt"
and, some hours later (and maybe unrelated) a "page allocation
failure" and a "Oops: kernel access of bad area" occurred.
The details are in the log file below.
What I know is that at 23:0
i just suffered a severe dataloss with my very similiar
configuration. i'm running ubuntu linux hoary with the standard
kernel 2.6.10-5-powerpc on a powerbook g4. i've hooked up a hfsplus
formatted 160gb lacie d2 firewire harddrive. in ubuntu i was
copying two big (1.5gb) files from interna
Hi all
Oops: kernel access of bad area, sig: 11 [#1]
NIP: C0008C90 LR: C0008010 SP: DDB65F20 REGS: ddb65e70 TRAP: 0300Not
tainted
MSR: 9032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 0084, DSISR: 4000
TASK = c1a89530[27966] 'gst-register-0.' THREAD: ddb64000Last syscall:
n page for hibernate.conf, I discovered I could
get it to use normal suspend instead of suspend2. This provided
more helpful messages during shutdown, but as near as I could tell the
basic problem (USB oops on resume) remained uchanged.
I can supply other logs or info upon request.
Thanks,
--I
Hi Itai,
On Wed, Jul 13, 2005 at 06:45:57PM -0700, Itai Seggev wrote:
> I apologize if this is the second email to reach the list, but I think
> my first one didn't make it through.
no problem.
> I'm having some difficulty with suspsend resume.
To raise the chances that somebody can help you,
I've discovered the
hibernate script. It is easier to use, but give the same result. :)
When I resume, I get an oops in the kernel and I can no longer attach
USB devices. The internal USB devices (i.e., keyboard and trackpad),
continue to work. The output is shown below. Any idea what this me
On Tue, May 24, 2005 at 01:34:53AM +0200, Wolfgang Pfeiffer wrote:
> Eddy, Benjamin
>
> On Mon, May 23, 2005 at 10:28:36AM +1000, Benjamin Herrenschmidt wrote:
> > On Mon, 2005-05-23 at 03:01 +0300, Eddy Petrisor wrote:
> > > Hello,
> > >
> > > I have finaly installed 2.6.12-rc4, but I found that
Eddy, Benjamin
On Mon, May 23, 2005 at 10:28:36AM +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2005-05-23 at 03:01 +0300, Eddy Petrisor wrote:
> > Hello,
> >
> > I have finaly installed 2.6.12-rc4, but I found that it oopses when
> > comming back from sleep.
> > Any idea why?
> >
> > boring in
On 5/23/05, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-05-23 at 03:01 +0300, Eddy Petrisor wrote:
> > Hello,
> >
> > I have finaly installed 2.6.12-rc4, but I found that it oopses when
> > comming back from sleep.
> > Any idea why?
> >
> > boring info on:
> going on. You shoul
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
> On Mon, 2005-05-23 at 03:01 +0300, Eddy Petrisor wrote:
>> Hello,
>>
>> I have finaly installed 2.6.12-rc4, but I found that it oopses when
>> comming back from sleep.
>> Any idea why?
>>
>> boring info on:
>
> It's apparently a bug in the USB
On Mon, 2005-05-23 at 03:01 +0300, Eddy Petrisor wrote:
> Hello,
>
> I have finaly installed 2.6.12-rc4, but I found that it oopses when
> comming back from sleep.
> Any idea why?
>
> boring info on:
It's apparently a bug in the USB HID code when CONFIG_USB_SUSPEND is
enabled, though so far, I h
ay 23 01:46:45 localhost kernel: Oops: kernel access of bad area, sig: 11 [#1]
May 23 01:46:45 localhost kernel: NIP: D24FDEE8 LR: D2496498 SP:
CB6F1D90 REGS: cb6f1ce0 TRAP: 0300Not tainted
May 23 01:46:45 localhost kernel: MSR: 0200b032 EE: 1 PR: 0 FP: 1 ME:
1 IR/DR: 11
May 23 01:46:45 loca
> On Thu, 2005-05-05 at 23:35 -0400, Keenan Pepper wrote:
>> I fixed it!
>>
>> I changed it to use the same device node for sound as for
>> chip->node, and it started beeping at me! Apparently sometime
>> between 2.6.8 and 2.6.12-rc3 the KIOCSOUND ioctl was implemented,
>> because it sure didn't be
1 19:16:12 localhost kernel: kernel BUG in hfsplus_bnode_put at
fs/hfsplus/bnode.c:625!
May 21 19:16:13 localhost kernel: Oops: Exception in kernel mode,
sig: 5 [#1]
May 21 19:16:13 localhost kernel: NIP: E97FC458 LR: E97FD0A0 SP:
C33BFCF0 REGS: c33bfc40 TRAP: 0700Not tainted
May 21 19:16:13
Ciao Jack Malmostoso, nel tuo messaggio dicevi:
> Read that, thanks. I downloaded the 2.6.12-rc4 tarball and compiled it,
> but I get an oops in reiserfs_panic.
>
> Already posted to lkml, I'll wait for an answer.
Solved problem: this bug has been introduced between rc
On May 08 2005, Colin Leroy wrote:
> On 07 May 2005 at 20h05, Rogério Brito wrote:
> > Yesterday, I got a quite scary ooops and, today, after trying a newer
> > kernel, I got many messages in my dmesg logs.
>
> I've had problems mounting my iPod with Firewire, whereas USB works ok.
> Do you have t
On 07 May 2005 at 20h05, Rogério Brito wrote:
Hi,
> The drive is an IDE HD in a firewire enclosure and it seems to work
> well for the first few operations. Then, the kernel generates loads
> of messages, when I try to do some simple things.
>
> Yesterday, I got a quite scary ooops and, today,
some simple things.
Yesterday, I got a quite scary ooops and, today, after trying a newer
kernel, I got many messages in my dmesg logs.
The Oops that I got yesterday was:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Linux version 2.6.12-rc3-2 ([EMAIL PROTECTED])
On Thu, 2005-05-05 at 23:35 -0400, Keenan Pepper wrote:
> I fixed it!
>
> I changed it to use the same device node for sound as for chip->node,
> and it started beeping at me! Apparently sometime between 2.6.8 and
> 2.6.12-rc3 the KIOCSOUND ioctl was implemented, because it sure didn't
> beep b
Hi all,
starting mol on 2.6.11.5 gets an reproducable oops:
Oops: kernel access of bad area, sig: 11 [#8]
NIP: C00051B8 LR: C00044CC SP: E1A6FF20 REGS: e1a6fe70 TRAP: 0300Not tainted
MSR: 9032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 0085, DSISR: 4000
TASK = ea8db050[13771]
code
removed recently?
Following debugging output may help to locate the problem:
Nov 28 18:47:29 powerbook kernel: Oops: kernel access of bad area, sig: 11 [#1]
Nov 28 18:47:29 powerbook kernel: NIP: 0C00 LR: CD8A799C SP: C5361D90 REGS:
c5361ce0 TRAP: 0400Not tainted
Nov 28 18:47:29
t; happens pretty much the same way with both versions. I can provide an
> oops dump, but I'll have to hand copy it - figured I'd find out first if
> it was a known problem or not. This system runs 2.6 kernels that I build
> just fie, but they have the CMD64x module built int
Subject says most of what needs to be. I tried using the packaged
kernels on my G3 blue-and-white (it's got a rev.2 logic board) oopses
when the module for the onboard CMD646 IDE controller gets loaded up. It
happens pretty much the same way with both versions. I can provide an
oops dump
Rob Weir wrote:
Hrm, are you sure? I was of the understanding that suspend-to-ram
doesn't work at all on ibook g4's (yet), and that suspend-to-ram
required Guido's patch. I sure would love to be proved wrong, tho :)
Sorry, I didn't realize you were talking of G4's. I meant for G3's, as
mine
On Tue, Jun 29, 2004 at 11:41:40PM +0200, Jaume Sabater said
> Sam Halliday wrote:
>
> >err... by the way, any good docs on setting that up on an iBook? i thought
> >suspend was all ACPI specific... and the best i can seem to do in the
> >kernel
> >options is apm emulation.
>
> CONFIG_PMAC_PBOO
Sam Halliday wrote:
err... by the way, any good docs on setting that up on an iBook? i thought
suspend was all ACPI specific... and the best i can seem to do in the kernel
options is apm emulation.
CONFIG_PMAC_PBOOK and probably CONFIG_PMAC_APM_EMU is all you need. Then
just install pbbutton
Jaume Sabater wrote:
> Warren A. Layton wrote:
> >>>Do you have CONFIG_SERIAL_PMACZILOG=y/m ?
> >>>
> >>>That's what caused my iBook to oops on suspend with 2.6.7-rc2. I'm not
> >>>sure if it has been fixed in 2.6.7 (final).
> >
Warren A. Layton wrote:
Do you have CONFIG_SERIAL_PMACZILOG=y/m ?
That's what caused my iBook to oops on suspend with 2.6.7-rc2. I'm not
sure if it has been fixed in 2.6.7 (final).
I just did a quick diff between the pmac_zilog.{c,h} files in 2.6.7-rc2
and 2.6.7 (final) an
On Tue, Jun 29, 2004 at 06:12:19PM +0200, Jaume Sabater wrote:
> Warren A. Layton wrote:
>
> >>Any other evil parameter? :-)
> >
> >Do you have CONFIG_SERIAL_PMACZILOG=y/m ?
> >
> >That's what caused my iBook to oops on suspend with 2.6.7-rc2. I'm
Warren A. Layton wrote:
Any other evil parameter? :-)
Do you have CONFIG_SERIAL_PMACZILOG=y/m ?
That's what caused my iBook to oops on suspend with 2.6.7-rc2. I'm not
sure if it has been fixed in 2.6.7 (final).
Hmmm... I have. Now disabled and compiling the kernel, which will tak
> preempt support, but still the same kernel oops. Anyway, I'll try again
> and let you know.
>
> Any other evil parameter? :-)
Do you have CONFIG_SERIAL_PMACZILOG=y/m ?
That's what caused my iBook to oops on suspend with 2.6.7-rc2. I'm not
sure if it has been fixed in
Frank Klingenhoefer wrote:
CONFIG_PREEMPT=y
You used the evil P word!
Enabling preemption was [is ?] known for erratic behavior.
That was the first thing I thought, so I compiled the kernel without
preempt support, but still the same kernel oops. Anyway, I'll try again
and let you
Jaume Sabater wrote:
[...]
> CONFIG_PREEMPT=y
You used the evil P word!
Enabling preemption was [is ?] known for erratic behavior.
Frank
tweak a little to get
something usable though,
it's used to extract the console content for braille displays ...
Even after a kernel oops?
--
Jaume Sabater
http://linuxsilo.net
"Ubi sapientas ibi libertas"
> The only thing you can do, as far as I know, is to open a terminal
> console via serial port and then copy-paste from that console.
If you're only looking for a console capture then try
cat /dev/vcsa > file
it should contain the console text, you may have to tweak a little to get
something usabl
Luca Bigliardi - shammash wrote:
i've ibook 2.2 + 2.6.7 vanilla + pbbuttonsd 0.5.9-1 + libc6 2.3.2.ds1-13
and all works fine.
let's take a look at .config...
Attached to this email is my .config.
Thanks for your help.
--
Jaume Sabater
http://linuxsilo.net
"Ubi sapientas ibi libertas"
#
# Au
Sébastien FRANÇOIS wrote:
So, anybody knows how to get the kernel oops message into my logs files?
are not they in /var/log/ksymoops ?
The only thing you can do, as far as I know, is to open a terminal
console via serial port and then copy-paste from that console.
P.S. I had to copy it
> > So, anybody knows how to get the kernel oops message into my logs files?
are not they in /var/log/ksymoops ?
seb
_
Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger
http://www.ifrance.com/
painful (I'll do it if there isn't another
> way ;-)).
>
> So, anybody knows how to get the kernel oops message into my logs files?
You'll have to just write it down manually, I guess. It sucks, but it
is a huge help to the kernel developers in debugging your problem.
Jaume Sabater wrote:
I have an iBook G3 800 MHz (rev 2.2, afaik) running GNU/Debian Linux Sid
with kernel 2.6.7 vanilla and pbbuttonsd 0.6.0-1 package. When the
system tries to suspend (automatically or forced by me) then I get a
(long) kernel oops and I have to reboot.
By the way, here you
Hi everyone!
I have an iBook G3 800 MHz (rev 2.2, afaik) running GNU/Debian Linux Sid
with kernel 2.6.7 vanilla and pbbuttonsd 0.6.0-1 package. When the
system tries to suspend (automatically or forced by me) then I get a
(long) kernel oops and I have to reboot.
I have not been able to find
ying to get it to sleep, but it doesn't
> >work. I've patched the 2.6.7-rc2 kernel using this patch at
> >http://honk.physik.uni-konstanz.de/~agx/linux-ppc/kernel/pmdisk-2.6.7-
> >rc2.diff but I get this message when I try to do an "echo -n "disk"
> >
1 - 100 of 182 matches
Mail list logo
